[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

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

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

Info

Publication number
WO2023241198A1
WO2023241198A1 PCT/CN2023/088429 CN2023088429W WO2023241198A1 WO 2023241198 A1 WO2023241198 A1 WO 2023241198A1 CN 2023088429 W CN2023088429 W CN 2023088429W WO 2023241198 A1 WO2023241198 A1 WO 2023241198A1
Authority
WO
WIPO (PCT)
Prior art keywords
rich media
applet
message
information
management platform
Prior art date
Application number
PCT/CN2023/088429
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 WO2023241198A1 publication Critical patent/WO2023241198A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10—Multimedia information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method, device and system.
  • the sender can send messages to the recipient without the consent of the recipient.
  • the development threshold for mini programs is low, so many entities can develop and utilize rich media messaging systems to directly distribute rich media messaging mini programs to users. Therefore, when the entity that develops the rich media messaging applet or the source of the rich media messaging applet is not trustworthy or the trustworthiness cannot be confirmed, the user directly running the received rich media messaging applet may bring risks and losses to the user. .
  • Embodiments of the present application provide a communication method, device, and system that enable users to run rich media messaging applets in a safe and controllable environment to avoid risks and losses to users.
  • the first 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 obtains first information, where the first information includes information about the first rich media message applet and/or the first rich media message applet; and the rich media message terminal sends a message to the first applet management platform.
  • a first request message wherein the first request message includes part or all of the first information, and the first request message is used to request the first applet management platform to verify the first rich media message applet, and the first applet
  • the management platform is an applet management platform that can provide a rich media message applet verification function.
  • the rich media message terminal receives a first response message from the first applet management platform.
  • the first response message includes the first response message from the first applet management platform. Verification results of the rich media message applet, the rich media message terminal performs corresponding operations on the first rich media message applet based on the verification results.
  • the rich media message terminal can interact with the first applet management platform to verify the first rich media message applet, and perform corresponding operations on the first rich media message applet according to the verification results.
  • This method allows users to run the obtained rich media message applet in a safe and controllable environment to avoid risks and losses to users.
  • the first request message is used to request the first applet management platform to verify the security of the first rich media message applet, or the first request message is used to request The first applet management platform verifies whether the rich media messaging terminal is allowed to run the first rich media messaging applet.
  • the method further includes: the rich media messaging terminal determining, based on the first information, to request verification of the first rich media messaging applet from the first applet management platform.
  • the rich media message terminal determines, based on the first information, the first rich media message applet to be verified by requesting the first applet management platform, including: the rich media message terminal obtains The second information includes the security source information of the rich media messaging applet and/or the public key used to verify the signature of the first rich media messaging applet, or the second information includes a verification policy indicating the need to The first applet platform requests verification of the first rich media message applet; the rich media message terminal determines to request verification of the first rich media message applet from the first applet management platform based on the first information and the second information.
  • the rich media messaging terminal determines, based on the first information and the second information, to request the first applet management platform to verify the first rich media messaging applet, including: when When the sender identification of the first information is not included in the secure source information, the rich media message terminal determines to request verification of the first rich media message applet from the first applet platform; or, when the public key is used to verify the first rich media message When the signature in the applet's information fails, the rich media message terminal determines to request verification of the first rich media message applet from the first applet platform; or when the verification policy indicates that it needs to request verification of the first rich media message applet from the first applet platform. When launching the media message applet, the rich media message terminal determines to request verification of the first rich media message applet from the first applet platform.
  • the user of the rich media message terminal can flexibly set the second information, and the rich media message terminal determines whether to request verification of the first rich media message applet from the first applet management platform based on the user's settings, thereby improving the user experience. .
  • the rich media message terminal obtains the first information, including: the rich media terminal obtains the first information from the second applet management platform, or the rich media terminal obtains the first information from the second applet management platform.
  • a management platform other than the applet management platform obtains the first information, or the rich media terminal obtains the first information from a rich media device other than the rich media terminal.
  • the rich media messaging terminal obtains the first information from the second applet management platform, including: the rich media messaging terminal acquires the unified resource positioning corresponding to the second applet management platform the rich media message terminal obtains the web page corresponding to the URL, the web page includes the first information and/or the applet query entry, and the applet query entry is used to obtain the first information.
  • the rich media message terminal obtains the first information, including: the rich media message terminal receives the first rich media message, and the first rich media message includes the first information.
  • the first rich media message may be actively sent by other devices or platforms to the rich media message terminal, or the rich media message terminal first sends a query message related to the first rich media message applet to other devices or platforms, and the other devices or The platform returns the first rich media message including the query result to the rich media message terminal.
  • the verification results include one of the following: a first verification result, a second verification result, a third verification result, and a fourth verification result, wherein the first verification result indicates The first rich media message applet passes the verification, the second verification result indicates that the first rich media message applet fails the verification, the third verification result indicates that the first rich media message applet partially passes the verification, and the fourth verification result indicates that the first rich media message applet partially passes the verification.
  • the program management platform queries and obtains the information of the rich media message applet stored locally and/or the rich media message applet according to the first request message.
  • the first applet management platform performs hierarchical verification on the first rich media message applet.
  • the rich media message terminal can perform different operations based on the different verification results returned by the first applet management platform to improve the user experience. .
  • the verification result is the first verification result or the fourth verification result
  • the rich media message terminal performs corresponding operations on the first rich media message applet according to the verification result, including: The rich media message terminal runs the first rich media message applet according to the verification result; or the verification result is the second verification result.
  • the rich media messaging terminal performs corresponding operations on the first rich media messaging applet based on the verification results, including: the rich media messaging terminal determines to run the first rich media messaging applet based on user instructions or local security settings; or , the rich media messaging terminal determines to refuse to run the first rich media messaging applet based on user instructions or local security settings.
  • the verification result is the first verification result or the fourth verification result
  • the rich media message terminal performs corresponding operations on the first rich media message applet according to the verification result, including:
  • the rich media message terminal provides user information to the first rich media message applet.
  • the user information is information related to the user corresponding to the rich media message terminal and is used to indicate the user of the first rich media message applet.
  • the rich media message terminal can provide the user information of the rich media message terminal to the first rich media message applet, so that the user can use the first rich media message applet without authentication.
  • Program service this method ensures that the first rich media messaging applet can be run, and at the same time facilitates users to use the first rich media messaging applet.
  • the second aspect provides a communication method, which can be executed by the first applet management platform, or can also be executed by components (such as chips or circuits) of the first applet management platform, which is not limited.
  • the method may include: the first applet management platform receives a first request message from the rich media message terminal, wherein the first request message includes part of the first information or all of the information, and the first information includes the first rich media message applet. program information and/or the first rich media message applet.
  • the first request message is used to request the first applet management platform to verify the first rich media message applet.
  • the first applet management platform is capable of providing rich media messages.
  • a mini program management platform for mini program verification the first mini program management platform verifies the first rich media message mini program according to the first request message and obtains the verification result; the first mini program management platform sends a first response to the rich media message terminal message, the first response message contains the verification result.
  • the first applet management platform receives the first request message sent by the rich media message terminal to request verification of the first rich media message applet, and the first applet management platform interacts with the rich media message terminal to verify the first rich media message applet.
  • the first request message is used to request the first applet management platform to verify the security of the first rich media message applet, or the first request message is used to request The first applet management platform verifies whether the rich media messaging terminal is allowed to run the first rich media messaging applet.
  • the first applet management platform verifies the first rich media message applet according to the first request message, and obtains the verification results, including: the first applet management platform Query the information of the rich media message applet stored locally on the first applet management platform according to the first request message; the first applet management platform obtains the verification result according to the query result.
  • the first applet management platform can query the information of the rich media message applet stored locally by the first applet management platform according to the first request message
  • the verification result includes a fourth verification result, which is the information of the rich media messaging applet and/or the rich media messaging applet stored locally by the first applet management platform, or, if the first applet management platform locally saves
  • the information of the first rich media message applet can be queried, and the verification result can be obtained by comparing the information of the rich media message applet stored locally on the first applet management platform with the first request message, and the verification result includes the first verification result or the second verification
  • the first verification result indicates that the first rich media message applet passes the verification
  • the second verification result indicates that the first rich media message applet fails the verification
  • the third verification result indicates that the first rich media message applet does not pass the verification Partially verified.
  • the first applet management platform verifies the first rich media message applet according to the first request message, and obtains the verification results, including: the first applet management platform
  • the third information is obtained locally, and the third information includes the contract information and/or configuration information corresponding to the rich media message terminal; the first applet management platform obtains the verification result according to the first request message and the third information.
  • the contract information corresponding to the rich media message terminal is an agreement to provide and use services signed between the user of the rich media message terminal and a rich media message service provider (such as an operator).
  • the contract information may include the contract information of the rich media message terminal.
  • the configuration information can be information configured unilaterally by the operator in the rich media messaging system, For example, users of rich media messaging terminals are allowed to use rich media messaging applets in certain areas or certain time periods, or rich media messaging terminals can only run rich media messaging applets provided by operators, or, Rich media messaging terminals can only run rich media messaging applets obtained from the operator platform.
  • the first applet management platform verifies the first rich media message applet according to the first request message, and obtains the verification results, including: the first applet management platform Obtain the first rich media message applet according to the first request message; the first applet management platform performs a security scan on the acquired first rich media message applet; the first applet management platform obtains the verification result according to the scan result.
  • the verification result includes a first verification result or a second verification result or a third verification result
  • the first verification result indicates that the first rich media message applet passes the verification
  • the first verification result indicates that the first rich media messaging applet fails the verification
  • the third verification result indicates that the first rich media messaging applet partially passes the verification.
  • the first applet management platform performs hierarchical verification on the first rich media message applet.
  • the rich media message terminal can perform different operations based on the different verification results returned by the first applet management platform to improve the user experience. .
  • the information of the first rich media messaging applet includes at least one of the following: the download address of the first rich media messaging applet, the download address of the first rich media messaging applet, The logo, the name of the first rich media messaging applet, the address of the icon of the first rich media messaging applet, the version of the first rich media messaging applet, the developer information of the first rich media messaging applet, the first rich media The provider information of the messaging applet, the signature information of the developer of the first rich media messaging applet, and the signature information of the provider of the first rich media messaging applet.
  • the first request message and the first request response message are rich media messages.
  • a communication device which is used to perform the method in any possible implementation manner of the first aspect or the second aspect.
  • the device may include units and/or modules for performing the method in any possible implementation of the first aspect or the second aspect, such as a processing unit and/or a communication unit.
  • the device is a communication device (such as a rich media messaging terminal, or an applet management platform).
  • 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 communication equipment (such as a rich media message terminal, or an applet management platform).
  • 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 fourth aspect provides a communication device, which includes: at least one processor configured to execute computer programs or instructions stored in a memory to perform the method in any possible implementation of the first aspect or the second aspect.
  • 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 messaging terminal, or an applet management platform).
  • a communication device such as a rich media messaging terminal, or an applet management platform.
  • the device is a chip, chip system or circuit used in communication equipment (such as a rich media message terminal, or an applet management platform).
  • a fifth 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 sixth 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 first aspect or the second aspect. .
  • a seventh aspect provides a computer program product containing instructions, which when the computer program product is run on a computer, causes the computer to execute the method in any of the possible implementations of the first aspect or the second aspect.
  • An eighth aspect provides a communication system, including at least one of the aforementioned rich media message terminal, a first applet management platform, and a second applet management platform.
  • 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 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of obtaining information of the first rich media message applet provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of another method of obtaining information of the first rich media messaging applet provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a communication device 1100 provided by an embodiment of the present application.
  • FIG. 9 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 Communications Services (RCS) messages follow the rich media communications launched by the Global System for Mobile Communication Association (GSMA) Fusion.07 (rich communication convergence.07, RCC.07) 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 traditional SMS 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. 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) is an application installed on the terminal device, and the host application can usually 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 is downloaded from the network side by the rich media messaging application and run directly (such as interpreted and executed) without being installed on the terminal device. Users need to run and enter the rich media messaging applet through the rich media messaging client.
  • the applet engine built into the rich media messaging application (which is used to interpret and execute the rich media messaging applet) is decoupled from the rich media messaging applet, such that 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 other business processing (such as bank card balance inquiry, bank card transfer, purchase of financial products, credit card repayment) and other services. These businesses, in In the embodiment of this application, it is called "rich media message applet service”.
  • WebView It can be simply regarded as a browser control that can be nested on the interface. Users usually use a browser to browse web pages. WebView is an embedded browser that is embedded in native applications. Users may not even realize that they are using a browser. Traditional browsers are divided into two parts, UI (address bar, navigation bar) and browser engine. Webview is the browser engine in native applications. Webview is just a visual component, which is the visual part of the native APP. The content displayed using webview does not need to be stored locally and can be obtained directly from the server. JS code running in webview has the ability to call native system APIs without the limitations of traditional browser sandboxes.
  • 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 platform, and a rich media message terminal.
  • rich media message terminal It can directly communicate with the mini program management platform, or the rich media message terminal can also communicate with the mini program management platform 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 message 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 upload and storage in industry messages for industry customers’ Chatbots and messages. Enables industry customers to provide users with messaging services in multiple media formats.
  • the rich media messaging application server can also support rich media messaging applet business permission verification, 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 mini program management platform is mainly used to review, verify, publish, summarize and store rich media message mini program information, provide rich media message mini program query services for terminal devices, and provide rich media message mini program query services for terminal devices. Packages are stored etc.
  • the mini program management platform can also be called a mini program management server, or a rich media mini program management server or a rich media mini program management platform. The following is unified and is described as a mini program management platform. The specific introduction to the mini program management platform 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 (domainname 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 domainname 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), and 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. As shown in Figure 3, this communication system takes the architecture of a rich media messaging system as an example. As shown in Figure 3, compared with Figure 2, in the system shown in Figure 3, a small program management platform is added.
  • the mini program management platform may be a secure mini program management platform or a non-secure mini program management platform.
  • the secure mini program management platform is provided by operators or third-party security entities
  • the non-secure mini program management platform is provided by industry customers or non-secure third-party entities.
  • the mini program management platform can be deployed independently, or it can be deployed independently. It can be built into 5GMC or deployed independently from 5GMC (such as deployed in MaaP, or deployed independently, and can interoperate with 5G MC), without restrictions.
  • Operation management Mainly used to review whether the rich media message applet complies with the rich media message applet development specifications, verify the rich media message applet, and publish the rich media message applet. Users can query it only 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. Should The query results may include rich media messaging applet information queried based on rich media messaging applet keywords, 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 platform can be directly connected to the rich media message center. For the description of each device, please refer to the previous description and will not be repeated here.
  • Step 1 The sender sends a rich media message, which is sent to the rich media message processing function of the calling party through the calling side IMS access function.
  • the calling message processing function returns a response that the rich media message has been received;
  • Step 2 The calling rich media message processing function sends a rich media message to the rich media message processing function to which the receiver belongs, and the called rich media message processing function returns a response that the rich media message has been received;
  • Step 3 The called rich media message processing function sends a rich media message to the receiver, and the receiver returns a response of successfully receiving the rich media message;
  • Step 4 The receiving direction sends a delivery report message to the calling rich media message processing function and delivers it hop by hop. Finally, the sending direction returns a response to the calling rich media message processing function for receiving the delivery report.
  • the development threshold for mini programs is low, so many entities can develop and utilize rich media messaging systems to directly distribute rich media messaging mini programs to users. Therefore, when the entity that develops the rich media messaging applet is not secure or the source of the rich media messaging applet is not secure, the user directly running the received rich media messaging applet will bring risks and losses to the user.
  • this application proposes a communication method that can effectively solve the above technical problems.
  • the methods provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
  • Figure 5 is a schematic diagram of a communication method provided by an embodiment of the present application. The method may include the following steps.
  • the rich media messaging terminal acquires first information, where the first information includes information about the first rich media messaging applet and/or the first rich media messaging applet.
  • the information of the first rich media messaging applet includes the download address of the first 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 first rich media messaging applet also includes at least one of the following: the identification of the first rich media messaging applet, the name of the first rich media messaging applet, the address of the icon of the rich media messaging applet, The version of the No.1 rich media messaging applet, the developer information of the No.1 rich media messaging applet, the provider information of the No.1 rich media messaging applet, the developer signature of the No.1 rich media messaging applet, the No.1 rich media The signature of the messaging applet's provider.
  • the provider information of the first rich media messaging applet may include at least one of the following: trademark, business type, contact information, website, etc.
  • the information about the first rich media messaging applet may also include at least one of the following: the purpose of the first rich media messaging applet, and the description of the first rich media messaging applet.
  • the rich media message terminal can obtain the first information in any of the following ways.
  • Method 1 The rich media terminal obtains the first information from the second applet management platform, where the second applet management platform locally stores the information of the first rich media message applet and/or the first rich media message applet.
  • the first rich media message applet is sent to the rich media message terminal through the method of sending a rich media message file.
  • the second mini program management platform may be a trusted mini program management platform or a non-trusted mini program management platform.
  • a trusted mini program management platform can be understood as the operator's mini program management platform, or a third-party mini program management platform trusted by the operator, or a third-party mini program management platform trusted by the provider (source).
  • An untrustworthy mini program management platform can be understood as a third-party mini program management platform whose provider (source) is not trustworthy or whose credibility cannot be confirmed.
  • the applet for saving rich media messages in the second applet management platform can be considered a safe applet.
  • whether the rich media messaging applet is safe refers to whether the rich media messaging applet will bring risks and losses to the data security, terminal system security, privacy, etc. of rich media messaging users.
  • the first rich media messaging applet is a safe applet, it means that the applet does not have the function of unauthorized access to the rich media messaging terminal, does not have the function of unauthorized use or destruction of the rich media messaging terminal, and does not have the function of unauthorized access to the rich media messaging terminal.
  • the rich media message terminal can obtain the first information from the second applet management platform by sending a rich media message.
  • An exemplary description will be given below with reference to FIG. 6 .
  • Figure 6 is a schematic diagram of obtaining the first information from the second applet management platform provided by this application, which may include the following steps:
  • Step 1 The rich media message terminal sends the first query request message to the rich media message center.
  • the first query request message contains query information.
  • the rich media message center receives the first query request message from the rich media message terminal.
  • the query information includes keywords used to describe the information of the first rich media message applet, or includes relevant information of the first rich media message applet, or includes the first rich media message applet queried by the rich media message terminal. Information about the requirements that the program needs to satisfy.
  • 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 first rich media messaging applet, the type of the first rich media messaging applet, and the provision of the first rich media messaging applet The name of the provider, the service content description or function description of the first rich media messaging applet, the language supported by the rich media messaging client, or the version of the rich media messaging client, etc.
  • Step 2 The rich media message center sends a second query request message to the second applet management platform, where the second query request message contains query information.
  • the second applet management platform receives the second query request message from the rich media message center.
  • Step 3 The second applet management platform locally obtains the information of the first rich media messaging applet and/or the first rich media messaging applet itself based on the query information.
  • Step 4 The second applet management server sends a second query response message to the rich media message center.
  • the second query response message contains the information of the first rich media message applet and/or the first rich media message applet itself.
  • the rich media message center receives the second query response message from the applet management server.
  • Step 5 The rich media message center sends a first query response message to the rich media message terminal.
  • the first query response message contains the information of the first rich media message applet and/or the first rich media message applet itself.
  • the rich media message terminal receives the first query response message from the rich media message center.
  • Step 6 The rich media messaging terminal displays the information of the first rich media messaging applet and/or presents the relevant interface of the first rich media messaging applet.
  • the rich media message terminal displays the information of the first rich media message applet to the corresponding user of the rich media message terminal in the form of a card or text, so that the user can interactively download and run the applet.
  • the relevant interface of the first rich media messaging applet includes an icon for triggering the execution of the first rich media messaging applet.
  • the first query request message, the second query request message, the first query response message and the second query response message are all rich media messages.
  • the second applet management platform may not send the first information based on the query request of the rich media message terminal, but actively send a rich media message containing the first information to the rich media message terminal.
  • the specific process is I won’t go into details here.
  • the rich media messaging terminal can first obtain the uniform resource locator (URL) corresponding to the second mini program management platform (that is, the link to the web page corresponding to the second mini program management platform), Afterwards, the rich media message terminal obtains the first information from the second applet management platform according to the URL corresponding to the second applet management platform. For example, the rich media message terminal can obtain the first information by using the built-in webview or built-in browser in the rich media message terminal based on the URL corresponding to the second applet management platform.
  • URL uniform resource locator
  • Figure 7 is a schematic diagram of obtaining the first information from the second applet management platform provided by this application, which may include the following steps:
  • Step 1 The rich media messaging terminal obtains the URL corresponding to the second mini program management platform.
  • the rich media messaging terminal can obtain the URL corresponding to the second applet management platform in the following manner.
  • the operator can configure the URL to the rich media messaging terminal in advance through the mobile phone card.
  • the rich media messaging terminal obtains the URL through the configuration server.
  • the configuration server actively configures the URL to the rich media messaging terminal, such as through an over-the-air (OTA) configuration mechanism such as Open Mobile Alliance (OMA) device management, and delivers the configuration to the rich media messaging terminal.
  • OTA over-the-air
  • OMA Open Mobile Alliance
  • the specific implementation can be found in the OMA device management standard, which will not be described here.
  • 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
  • Configure the server network domain name (such as 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 messaging terminal sends a message, such as an HTTP/HTTPS message, to the configuration server to request configuration information.
  • the configuration server sends the configuration information to the rich media messaging terminal.
  • the configuration information includes the URL.
  • the operator can configure the URL to the rich media message terminal through rich media messaging.
  • the rich media message terminal receives the rich media message from the rich media message center, and the rich media message includes the URL.
  • Step 2 The rich media messaging terminal uses the built-in Webview or built-in browser to request the mini program web page from the second mini program management platform according to the URL.
  • the rich media message terminal is automatically triggered according to the URL or is triggered by a user corresponding to the rich media message terminal to request the applet web page from the second applet management platform.
  • Step 3 The built-in Webview or built-in browser of the rich media messaging terminal receives the mini program web page returned by the second mini program management platform.
  • the web page contains information or a list of the first rich media message applet, and/or, a query entry for the applet.
  • the user corresponding to the rich media message terminal can obtain the information of the first rich media message applet or the first rich media message applet itself through the applet query entrance from the applet management platform.
  • step 2 the user corresponding to the rich media message terminal can enter the keyword of the first rich media message applet information in the built-in Webview or the query entry of the browser, or enter the first rich media message applet information.
  • the relevant information of the media message applet, or the demand information to be satisfied by the first rich media message applet that is entered into the rich media message terminal query triggers a request for a web page to the second applet management platform.
  • the applet management platform in step 3 The returned web page may contain information about the first rich media messaging applet and/or the first rich media messaging applet itself.
  • the web page may also contain a query entry for the applet.
  • the rich media messaging terminal automatically triggers a web page request to the second mini program management platform in step 2
  • the web page returned by the mini program management platform in step 3 includes the mini program query entry.
  • Step 4 The rich media messaging terminal displays the web page to the user.
  • the rich media terminal obtains the first information from the first platform, where the first platform is a management platform other than the second applet management platform. Specifically, the rich media terminal receives the rich media message from the first platform, and the rich media terminal receives the first information from the first platform.
  • Media messages include primary information.
  • the first platform can be a platform that provides services such as banking or insurance.
  • the rich media message may be a rich media message sent by the first platform after the rich media terminal sends a query request related to the first rich media message applet to the first platform, or may be a rich media message actively sent by the first platform.
  • the rich media message terminal obtains the first information from other rich media message devices. Specifically, the rich media message terminal receives the rich media message from other rich media message devices, and the rich media message includes the first information. For example, the user of rich media message terminal A sends the first information to rich media message device B through rich media message terminal A.
  • the rich media message device may be a device other than the rich media message terminal that can send rich media messages, and this application does not limit this.
  • the rich media message device may be other rich media message terminals other than the rich media message terminal, or may be a rich media message server.
  • the rich media terminal may also receive rich media messages from other senders.
  • the rich media messages include the first information. This application does not do anything to the sender of the rich media messages. limited.
  • the rich media message terminal sends a first request message to the first applet management platform, where the first request message includes part of or all the information of the first information, and the first request message is used to request verification of the first rich media message applet.
  • the first mini program management platform is a mini program management platform that can provide the usability verification function of rich media messaging mini programs.
  • the first applet management platform receives the first request message from the rich media message terminal and executes S540.
  • first mini program management platform and the second mini program management platform are different mini program management platforms.
  • the rich media messaging applet availability verification function that the first applet management platform can provide includes verifying the security of the first rich media messaging applet, or verifying whether the rich media messaging terminal is allowed to run the first rich media messaging applet. program.
  • This application does not specifically limit the function of the first mini program management platform to verify the rich media message applet.
  • the scope or content of the function of the first mini program management platform to verify the rich media message applet can be increased according to actual needs.
  • the first request message is used to request the first applet management platform to verify the availability of the first rich media messaging applet, including requesting the first applet management platform to verify the security of the first rich media messaging applet, and/or , requesting the first applet management platform to verify whether the rich media messaging terminal is allowed to run the first rich media messaging applet.
  • part or all of the information about the first rich media messaging applet included in the first request message may be keywords used to describe the information about the first rich media messaging applet, or the first rich media messaging applet related information, or query the demand information to be met by the first rich media messaging applet, or the first rich media messaging applet itself.
  • the first request message may be a rich media message or an HTTP/HTTPS message.
  • the information of the first applet management platform (such as the address of the first applet management platform) can be configured by the mobile phone card to the rich media messaging terminal, or configured by the configuration server.
  • the configuration server can actively configure the configuration to the rich media messaging terminal, such as through OTA configuration mechanisms such as OMA device management, and deliver the configuration to the rich media messaging terminal.
  • OMA device management standard For specific implementation, please refer to the OMA device management standard.
  • 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
  • the server network domain name (such as 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 messaging terminal sends a message, such as an HTTP/HTTPS message, to the configuration server to request configuration information.
  • the configuration server sends the configuration information to the rich media messaging terminal.
  • the configuration information includes information about the first applet management platform.
  • the method may also include:
  • the rich media messaging terminal determines, based on the first information, to request the first applet management platform to verify the first rich media messaging applet.
  • the rich media message terminal can determine whether to request verification of the first rich media message applet from the first applet management platform based on the first information. If verification is required, S520 is executed. If the rich media message terminal If it is determined according to the first information that the first rich media messaging applet can be run, then the rich media messaging terminal can directly run the first rich media messaging applet.
  • the user of the rich media message terminal can choose to click the icon of the first rich media message applet, and the rich media message terminal performs steps in response to this operation S530. That is to say, if the user of the rich media messaging terminal does not click the icon of the first rich media messaging applet, the rich media messaging terminal will not initiate the verification process.
  • the rich media message terminal executes step S530.
  • the rich media messaging terminal determines whether to request the first applet management platform to verify the availability of the first rich media messaging applet based on the first information, which means that the rich media messaging terminal determines based on the first information and
  • the local security policy configuration determines whether to request the first applet management platform to verify the availability of the first rich media messaging applet.
  • the security policy can be a verification-free level.
  • the verification-free level can be divided into high, medium, and low. Among them, for the same rich media messaging applet, the lower the verification level, the easier it is for the rich media messaging applet to pass verification, and the higher the verification level, the more difficult it is for the rich media messaging applet to pass verification.
  • the local verification-free level of the rich media message terminal when the local verification-free level of the rich media message terminal is set to a low level (such as only verifying developer information), even if the first rich media message applet may have some other risks, as long as the rich media message Based on the first information, the terminal determines that the first rich media messaging applet meets the local verification-free level requirements (that is, it passes local verification), then the rich media messaging terminal considers that the first rich media messaging applet does not need to be managed by the first applet.
  • the platform requests further availability verification.
  • the rich media messaging terminal verifies the availability of the first rich media messaging applet based on the first information and the second information (ie, the security policy configuration of the rich media messaging terminal), where the second information is used to determine the content to be sent to the first applet.
  • the program management platform requests verification of the availability of the first rich media messaging applet.
  • the second information may include security source information that provides the rich media messaging applet and/or a public key used to verify the signature of the rich media messaging applet, where the security source information includes security service provider information, secure links, etc., or , the second information may include a verification policy, which indicates whether it is necessary to request verification of the first rich media messaging applet from the first applet platform.
  • the rich media message terminal will not verify the availability of the first rich media message applet with the first applet management platform.
  • the rich media messaging terminal determines whether to verify the availability of the first rich media messaging applet with the first applet management platform based on the security source information in the second information. For example, when the sender identification of the information of the first rich media messaging applet is not included in the secure source information, the rich media messaging terminal needs to verify the availability of the first rich media messaging applet with the first applet management platform.
  • the sender identification can be a service number or a personal number of a platform such as a bank or insurance company.
  • the rich media message terminal uses the public key in the second information to verify the signature in the first rich media message applet information, and the rich media message terminal determines whether to verify the first rich media message with the first applet management platform based on the verification result.
  • Availability of media messaging applets For example, the signature in the first rich media messaging applet information includes the signature information of the first rich media messaging applet provider, which uses a private key to encrypt a ciphertext generated by the sender (for example, the second applet Management platform) sends the signature along with the data to the rich media message terminal, and the rich media message terminal uses the public key corresponding to the private key to decrypt the signature, thereby verifying the identity of the sender and whether the plaintext data has been tampered with. Then, if the rich media message terminal fails to pass the signature verification of the provider in the information of the first rich media applet using the public key, the rich media message terminal determines to request verification of the first rich media message applet from the first applet platform. Program Availability.
  • the second information can be configured by the mobile phone card to the rich media message terminal, or configured by the configuration server.
  • the configuration server can actively configure the configuration to the rich media messaging terminal, such as through OTA configuration mechanisms such as OMA device management, and deliver the configuration to the rich media messaging terminal.
  • OMA device management For specific implementation, please refer to the OMA device management standard.
  • 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). Configure the server network domain name (such as fully qualified domain name (fully qualified domain name, FQDN)).
  • MCC mobile country code
  • MNC mobile network code
  • IMSI international mobile subscriber identity
  • the built configuration server network domain name is config.rcs.mnc.mcc.pub.3gppnetwork.org.
  • the rich media messaging terminal sends a message, such as an HTTP/HTTPS message, to the configuration server to request configuration information.
  • the configuration server sends the configuration information to the rich media messaging terminal.
  • the configuration information includes second information.
  • the rich media messaging terminal determines whether to verify the availability of the first rich media messaging applet with the first applet management platform based on the verification policy in the second information. For example, if the verification policy indicates to the first applet If the program platform requests verification of the first rich media messaging applet, then the rich media messaging terminal will verify the availability of the first rich media messaging applet with the first applet management platform.
  • the rich media message terminal determines that the first rich media message applet can be directly run, the rich media message terminal runs the first rich media message applet.
  • the rich media messaging terminal determines that it is necessary to further verify the availability of the first rich media messaging applet with the first applet management platform, it continues to execute S520.
  • the rich media message terminal runs the first rich media message applet according to the first information. It can be understood as follows. If the first information does not include the first rich media message applet, the rich media message terminal is running the first rich media message applet. Before launching the applet, you need to download the first rich media messaging applet according to the download address of the first rich media messaging applet in the first information, and then run the first rich media messaging applet. If the first information includes the first rich media messaging applet itself, the rich media messaging terminal can directly run the first rich media messaging applet. This application involves the description of running the first rich media message applet. Whether the download operation needs to be performed first can be determined based on the specific information contained in the first message, which will not be explained one by one below.
  • S540 The first applet management platform verifies the first rich media message applet according to the first request message and obtains the verification result.
  • the verification results in this application include a first verification result, a second verification result, and a third verification result, wherein the first verification result indicates that the first rich media message applet passed verification, and the second verification result indicates that the first rich media message applet passed the verification.
  • the media message applet failed to pass the verification the third verification result indicates that the first rich media message applet partially passed the verification
  • the fourth verification result is that the first applet management platform obtained the query based on the first request message and saved it in the first applet.
  • the program manages the information of the rich media messaging applet of the platform and/or the rich media messaging applet (ie, implicitly indicates that the first rich media messaging applet passes the verification).
  • the first applet management platform verifies the information including the first rich media message applet one by one in the first information. If all the information of the first rich media messaging applet passes verification, the verification result is the first verification result. If any information in the first rich media message applet fails to be verified, the verification result is the second verification result. If part of the information in the first rich media messaging applet passes verification and part of the information does not pass verification, the verification result is the third verification result, for example, the identity of the provider or developer in the information of the first rich media messaging applet After passing the verification, but unable to verify whether other information in the first rich media message applet is safe, the verification result is the third verification result.
  • the first verification result indicates that the first rich media message applet is a safe applet
  • the second verification result indicates that the first rich media message applet is a safe applet.
  • the applet is an unsafe applet
  • the third verification result indicates that the first rich media messaging applet is a partially secure applet. If the first request message requests verification of whether the rich media messaging terminal is allowed to run the first rich media messaging applet, the first verification result indicates that the rich media messaging terminal is allowed to run the first rich media messaging applet, and the second verification result indicates that the rich media messaging terminal is not allowed to run the first rich media messaging applet.
  • the media messaging terminal runs the first rich media messaging applet.
  • the first applet management platform verifies the availability of the first rich media messaging applet according to the first request message, including any of the following implementation methods.
  • the first request message may request verification of the security of the first rich media messaging applet, and then the first applet management platform verifies and queries whether the first rich media messaging applet is stored locally based on the first request message. information, and generate verification results for the first rich media messaging applet based on the query results.
  • the rich media message terminal queries the first rich media message applet based on the first request message, and the first applet management platform determines the first rich media message applet based on the query result. Whether the program passes verification.
  • the rich media messaging terminal can query the rich media messaging applet information stored locally on the first applet management platform according to the first request message
  • the verification result is the fourth verification result
  • the fourth verification result is The result is that the rich media message terminal queries the locally saved rich media message applet information and/or the rich media message applet based on the first request message, or the information of the first rich media message contained in the first request message. Compare and verify with the information of the rich media message applet stored locally on the platform queried by the rich media message terminal based on the first request message.
  • the comparison results are consistent, it indicates that the first rich media message applet has passed the verification, that is, the verification result is the first Verification result; if the information of the first rich media messaging applet is not queried locally, it means that the first rich media messaging applet has not passed the verification, that is, the verification result is the second verification result.
  • the second applet management platform directly verifies the availability of the first rich media message applet on the local platform according to the first request message verification.
  • the first applet management platform can be verified in the following ways.
  • the first request message can request verification whether the first rich media messaging applet is allowed to run, and the first applet management platform locally obtains the third information according to the first request message, and the third information includes the rich media messaging terminal corresponding to Contract information and/or configuration information, the first applet management platform determines the verification result of the first rich media message applet based on the first request message and the third information.
  • the contract information corresponding to the rich media message terminal is an agreement to provide and use services signed between the user of the rich media message terminal and a rich media message service provider (such as an operator).
  • the contract information may include the contract information of the rich media message terminal.
  • the configuration information can be information configured unilaterally by the operator in the rich media messaging system, for example , users of rich media messaging terminals are allowed to use rich media messaging applet services in certain areas or certain types of users or during a certain period of time, or rich media messaging terminals can only run rich media messaging applet services provided by operators, or rich media messaging applets Media messaging terminals can only run rich media messaging applets obtained from the operator platform.
  • the configuration information in the third information includes that the rich media messaging terminal can only run the rich media messaging applet obtained from the operator platform. If the first applet management platform determines that the source of the first rich media message applet is the operator platform according to the first request message, the verification result obtained by the rich media message terminal is the first verification result. If the first applet management platform determines according to the first request message Once the request message determines that the source of the first rich media message applet is not the operator platform, the verification result obtained by the rich media message terminal is the second verification result.
  • the first request message can request verification of the security of the first rich media message applet, and the first applet management platform can obtain it locally based on part or all of the first information contained in the first request message.
  • the information of a corresponding rich media message applet herein referred to as the information of the second rich media message applet
  • the first applet management platform directly uses the obtained information of the second rich media message applet as the fourth verification result.
  • the first applet management platform locally compares the information of the first rich media messaging applet with the information of the second rich media messaging applet, and determines the verification result of the first rich media messaging applet based on the comparison results, example , if the comparison results are all the same, then the first mini program management platform confirms that the verification result is the first verification result. If the comparison results are not the same, then the first mini program management platform confirms that the verification result is the second verification result. If the comparison result If part is the same and part is different, the first mini program management platform confirms that the verification result is the third verification result.
  • the first request message can request verification of the security of the first rich media message applet.
  • the first applet management platform obtains the first rich media message applet itself based on the first information, and locally processes the first rich media message.
  • the applet performs a security scan and determines the verification result of the first rich media messaging applet based on the scan results.
  • the first applet management platform will This download address downloads the first rich media messaging applet to the local computer. If the first information includes the first rich media messaging applet, the first applet management platform obtains the first rich media messaging applet from the storage unit that stores the first information.
  • the first applet management platform confirms that the verification result is the first verification result; otherwise, the first applet management platform confirms that the verification result is the second verification result or the third verification result. Validation results.
  • the first applet management platform can save the verification result of the first rich media message applet locally, so that other rich media message terminals can subsequently request verification of the first rich media message applet from the first applet management platform.
  • the first applet management platform can directly return the verification results based on the locally saved information.
  • the first applet management platform sends a first response message to the rich media message terminal.
  • the first response message includes the verification result of the first rich media message applet by the first applet management platform.
  • the rich media message terminal receives the first response message from the first applet management platform.
  • S560 The rich media message terminal performs corresponding operations on the first rich media message applet according to the verification result.
  • the rich media message terminal can run the corresponding rich media message applet. Specifically, when the verification result is the first verification result, the rich media message terminal runs the first rich media message applet; when the verification result is the fourth verification result, the rich media message terminal runs the rich media message applet included in the fourth verification result. program or a rich media message applet obtained based on the information of the rich media message applet in the fourth verification result.
  • the user information can also be provided to the first rich media messaging applet,
  • the user information is information related to the user corresponding to the rich media messaging terminal, and is used to indicate the user of the first rich media messaging applet.
  • the server corresponding to the first rich media messaging applet provides services to the user based on the user information.
  • the function of providing user information to the first rich media messaging applet is that based on the security of rich media messages and trust in the operator, the first rich media messaging applet defaults to the fact that the user information provided by the rich media messaging terminal is safe.
  • the user information can be provided to the service device corresponding to the first rich media message applet.
  • the rich media message applet server that is, the server device corresponding to the first rich media message applet
  • the rich media message applet The server may be exempted from authenticating the user of the first rich media messaging applet based on the user information. For example, there is no need to initiate an authentication process for the user of the first rich media messaging applet, so that the user no longer needs to perform the authentication process of entering an account/password.
  • the rich media messaging applet service (such as bank card balance inquiry); for example, the user information includes the user ID and the signature of the user ID by the first applet management platform, and the rich media messaging applet server verifies that the signature passes Afterwards, it is confirmed that the user of the first rich media messaging applet is exempt from authentication; for example, the user information may also include a token provided by the first platform, and the server passes the first applet management platform or the corresponding verification center. After the verification token is passed, it is confirmed that users of the first rich media messaging applet are exempt from authentication.
  • the rich media messaging terminal provides user information to the first rich media messaging applet, which is equivalent to providing security credential information to the first rich media messaging applet.
  • the user information includes the user identification, which may be a unique identifier assigned by the network operator in the wireless communication system to the mobile phone card used by the user.
  • the unique identifier is an International Mobile Subscriber Identity (IMSI) or a Subscriber Permanent Identifier (Subscription Permanent Identifier, SUPI).
  • the user information may also be a Generic Public Subscription Identifier (GPSI).
  • the verification result of the first rich media message applet is the fourth verification result
  • the rich media message terminal runs the rich media message applet included in the fourth verification result or according to the first
  • user information may also be provided to the second rich media message applet.
  • the user information is information related to the user corresponding to the rich media message terminal. , used to indicate the user of the rich media messaging applet related to the fourth verification result. It can be understood that based on the security of rich media messages and trust in operators, the second rich media message applet defaults that the user information provided by the rich media message terminal is safe, and the user information can be provided related to the fourth verification result.
  • the server corresponding to the rich media messaging applet, and the server corresponding to the second rich media messaging applet provide services for the user based on the user information. It is the same as the role of the rich media messaging terminal in providing user information to the first rich media messaging applet, and will not be described again here.
  • the rich media messaging terminal provides user information corresponding to the rich media messaging terminal to the first rich media messaging applet.
  • the rich media messaging terminal can carry the user information corresponding to the rich media messaging terminal when opening the applet (for example, passing the user ID or other verification parameters in the applet entry function), or the rich media messaging terminal can carry the user information when opening the applet.
  • Register a callback function with the rich media message applet The subsequent rich media message applet uses the callback function to obtain the user information corresponding to the rich media message terminal from the rich media message terminal.
  • the rich media message applet provides the secure user information to the applet service side. , when the mini program service side provides services to rich media message terminal users, there is no need to perform verification operations on the rich media message terminal users again (that is, users are exempted from authentication).
  • the rich media message terminal displays the first rich media message applet and the verification result for corresponding to the rich media message terminal.
  • the user is prompted for a verification result (such as a security prompt).
  • a verification result such as a security prompt
  • the rich media message terminal displays the first rich media message applet and the verification result. After the user confirms the verification result prompt, the first rich media message applet does not run. program, or, run but do not upload the user information of the rich media messaging terminal to the first rich media messaging applet (that is, turn off authentication exemption).
  • the rich media message terminal can obtain the information of the first rich media message applet, determine whether to request the second applet management platform to verify the availability of the first rich media message applet, and manage the rich media message applet.
  • the platform interactively verifies the availability of the first rich media messaging applet, runs the first rich media messaging applet based on the verification results, and transmits user information to the first rich media messaging applet based on the verification results.
  • the rich media messaging terminal can download and run the applet on the premise of ensuring that the first rich media messaging applet can run, thereby avoiding risks and losses caused by opening applets of unknown security to the user.
  • user information can also be provided based on the security verification results for users to use the service of the first rich media messaging applet without authentication.
  • each step in the above-mentioned Figure 5 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. 8 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 terminal in the aforementioned embodiments (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7), or can be a component of the rich media message terminal (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 S520 in Figure 5
  • the operation of sending the first request message to the first applet management platform and the operation of receiving the first response message from the first applet management platform in S550 can also be used to send the first request message to the rich media message center in step 1 in Figure 6
  • the operation of sending the first query request message and the operation of receiving the first query response message from the rich media message center in step 5 can also be used to perform the operation of sending and/or receiving data or messages by the rich media message terminal in Figure 7 .
  • 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 operations of S530 and S560 in FIG. 5 , and may also be used to perform the operation of step 6 in FIG. 6 , and may also be used to perform the operation of step 4 in FIG. 7 .
  • the transceiver unit 1100 is used to obtain the first information, and the first information includes the information of the first rich media message applet and/or the first rich media message applet; the transceiver unit 1100 is also used to send a message to the first rich media message applet.
  • the first applet management platform sends a first request message, where the first request message includes part or all of the first information.
  • the first request message is used to request the first applet management platform to verify the first rich media message applet.
  • the first applet management platform is a management platform that can provide rich media message applet verification functions; the transceiver unit 1100 is also used to receive a first response message from the first applet management platform, where the first response message includes the first applet
  • the program management platform verifies the first rich media messaging applet, and the processing unit 1120 is used by the rich media messaging terminal to perform corresponding operations on the first rich media messaging applet based on the verification results.
  • the processing unit 1120 is also configured to determine, based on the first information, the first rich media messaging applet to be requested from the first applet management platform for verification.
  • the first request message is used to request the first applet management platform to verify the security of the first rich media messaging applet, or the first request message is used to request the first applet management platform to verify whether the rich media messaging terminal is allowed Run the first rich media messaging applet.
  • the transceiver unit 1100 is also configured to obtain second information, where the second information includes the security source information of the rich media messaging applet and/or the public key used to verify the signature of the first rich media messaging applet, or,
  • the second information includes a verification strategy, which indicates that the first rich media messaging applet is to be requested to be verified from the first applet platform;
  • the processing unit 1120 is also configured to determine based on the first information and the second information to determine that the first applet is to be verified.
  • the management platform requests verification of the first rich media messaging applet.
  • the processing unit 1120 is also configured to determine that the first rich media message applet is to be verified by requesting the first applet platform; or, when using When the public key fails to verify the signature in the information of the first rich media messaging applet, the processing unit 1120 is also used to determine whether to request the first applet platform to verify the first rich media messaging applet; or when the verification policy points to the first rich media messaging applet. When the applet platform requests verification of the first rich media message applet, the processing unit 1120 is also used to determine whether to request verification of the first rich media message applet from the first applet platform.
  • the information of the first rich media messaging applet includes at least one of the following: the download address of the first rich media messaging applet, the identity of the first rich media messaging applet, the name of the first rich media messaging applet, The address of the icon of the first rich media messaging applet, the version of the first rich media messaging applet, the developer information of the first rich media messaging applet, the provider information of the first rich media messaging applet, the first rich media messaging applet The signature information of the developer of the mini program and the signature information of the provider of the first rich media messaging mini program.
  • the transceiver unit 1100 is also used for the rich media terminal to obtain the first information from the second applet management platform, or the rich media terminal obtains the first information from a management platform other than the second applet management platform, or, The rich media terminal obtains the first information from a rich media messaging device other than the rich media messaging terminal.
  • the transceiver unit 1100 is also used to obtain the uniform resource locator URL corresponding to the second applet management platform; the transceiver unit 1100 is also used to obtain the web page corresponding to the URL, and the web page includes the first information and/or the applet.
  • the program query entrance and the mini program query entrance are used to obtain the first information.
  • the transceiver unit 1100 is also configured to receive a first rich media message, where the first rich media message includes the first information.
  • the verification results include one of the following: a first verification result, a second verification result, a third verification result, and a fourth verification result, where the first verification result indicates that the first rich media message applet has passed verification, and the second verification result indicates that the first rich media message applet has passed the verification.
  • the result indicates that the first rich media message applet failed to pass the verification
  • the third verification result indicates that the first rich media message applet partially passed the verification
  • the fourth verification result is that the first applet management platform obtained the query based on the first request message and saved it in Local rich media message applet information and/or rich media message applet.
  • the verification result is the first verification result or the fourth verification result
  • the processing unit 1120 is configured to determine to run the first rich media messaging applet according to user instructions or local security settings; or, the processing unit 1120 is configured to execute the first rich media messaging applet according to user instructions. Or local security settings determine to deny running the first Rich Media Messaging applet.
  • the verification result is the first verification result or the fourth verification result
  • the transceiver unit 1110 is further configured to provide user information to the first rich media messaging applet, where the user information is information related to the user corresponding to the rich media messaging terminal. , used to indicate the user of the first rich media messaging applet.
  • the device 1100 may be the first applet management platform in the aforementioned embodiment, or may be a component (such as a chip) of the first applet management platform.
  • the device 1100 can implement implementation corresponding to the above method.
  • the first applet in the example manages the steps or processes executed by the platform.
  • the transceiver unit 1110 may be used to perform transceiver-related operations of the first applet management platform 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 operations in Figure 5 The operation of receiving the first request message from the rich media message terminal in S520, and the operation of sending the first response message to the rich media message terminal in S550.
  • the processing unit 1120 may be used to perform operations related to processing of the first applet management platform 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, processing Unit 1120 may be used to perform the operations of step 540 in FIG. 5 .
  • the transceiver unit 1110 is configured to receive a first request message from a rich media message terminal, where the first request message includes part of or all of the first information, and the first information includes the first rich media
  • the information of the message applet and/or the first rich media message applet, the first request message is used to request the first applet management platform to verify the first rich media message applet, and the first applet management platform is capable of providing rich media message applet.
  • An applet management platform for media message applet verification; the processing unit 1120 is used to verify the first rich media message applet according to the first request message and obtain the verification result; the transceiver unit 1110 is also used to send messages to the rich media message terminal
  • the first response message contains the verification result.
  • the first request message is used to request the first applet management platform to verify the security of the first rich media messaging applet, or the first request message is used to request the first applet management platform to verify whether the rich media messaging terminal is allowed Run the first rich media messaging applet.
  • the information of the first rich media messaging applet includes at least one of the following: the download address of the first rich media messaging applet, the identity of the first rich media messaging applet, the name of the first rich media messaging applet, The version of the first rich media messaging applet, the developer information of the first rich media messaging applet, the provider information of the first rich media messaging applet, the signature information of the developer of the first rich media messaging applet, the first rich Signature information of the provider of the media messaging applet.
  • the processing unit 1120 is also configured to query the rich media message applet information stored locally on the first applet management platform according to the first request message; the processing unit 1120 is also configured to obtain the verification result based on the query result.
  • the verification result includes a fourth verification result
  • the fourth verification result is locally saved
  • the information of the rich media message applet and/or the rich media message applet or if the first applet management platform can query the information of the rich media message applet stored locally by the first applet management platform according to the first request message , compare the information of the locally saved rich media message applet with the first request message to obtain the verification result.
  • the verification result includes the first verification result or the second verification result or the third verification result.
  • the first verification result indicates the first rich media message applet.
  • the program passes the verification
  • the second verification result indicates that the first rich media messaging applet fails the verification
  • the third verification result indicates that the first rich media messaging applet partially passes the verification.
  • the transceiver unit 1110 is also configured to obtain third information, which includes the subscription information and/or configuration information corresponding to the rich media message terminal; the processing unit 1120 is also configured to obtain the third information according to the first request message and the third information. Get verification results.
  • the transceiving unit 1110 is also configured to obtain the first rich media messaging applet according to the first request message; the processing unit 1120 is also configured to perform a security scan on the obtained first rich media messaging applet; the processing unit 1120, Also used to get verification results based on scan results.
  • the verification result includes a first verification result or a second verification result or a third verification result.
  • the first verification result indicates that the first rich media messaging applet passed the verification
  • the second verification result indicates that the first rich media messaging applet failed.
  • Verification the third verification result indicates that the first rich media message applet partially passes verification.
  • 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 terminal in the above embodiment (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7), and can be used to execute Various processes and/or steps corresponding to the rich media message terminal in the above method embodiments, for example, S510-S530, S550-S560 in Figure 5, Step 1, Step 5-Step 6 in Figure 6, and Figure 7 Step 1-Step 4.
  • the device 1100 may be specifically the second applet management platform in the above embodiments, and may be used to execute various processes and/or steps corresponding to the second applet management platform in the above method embodiments, for example, in Figure 5 S530-S550. 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 terminal (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7) in the above method, or the device 1100 of each of the above solutions has the function of implementing the above.
  • 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 8 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. 9 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 terminal (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7) in each of the above method embodiments.
  • the device 1200 is used to implement the operations performed by the first applet management platform 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 when 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) can be integrated in the processor.
  • Embodiments of the present application also provide a computer-readable storage medium on which is stored the information executed by a rich media message terminal (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7) for implementing the above method embodiments.
  • a rich media message terminal such as the rich media message terminal in Figure 5, Figure 6, and Figure 7.
  • Embodiments of the present application also provide a computer-readable storage medium on which are stored computer instructions for implementing the methods executed by the first applet management platform in each of the above method embodiments.
  • 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 terminal (such as the rich media message terminal in Figure 5, Figure 6, and Figure 7) in each of the above method embodiments. ) 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 first applet management platform in each of the above method embodiments.
  • Embodiments of the present application also provide a communication system, including the aforementioned rich media message terminal (the rich media message terminal in Figure 5, Figure 6, and Figure 7), a first applet management platform, and a second applet management platform. at least one of.
  • 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 mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection of 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)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Multimedia (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种通信方法、装置以及系统。该通信方法包括：富媒体消息终端获取第一信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序；富媒体消息终端向能够提供富媒体消息小程序验证功能的第一小程序管理平台发送第一请求消息，用于请求对第一富媒体消息小程序进行验证，其中，第一请求消息包括第一信息的部分信息或全部信息；富媒体消息终端接收来自第一小程序管理平台的第一响应消息，该第一响应消息包含对第一富媒体消息小程序的验证结果，富媒体消息终端根据验证结果对第一富媒体消息小程序执行后续操作。该方法可以使用户在安全、可控的环境下运行获取到的富媒体消息小程序，避免给用户带来风险和损失。

Description

通信方法、装置以及系统
本申请要求于2022年6月15日提交中国国家知识产权局、申请号为202210682078.0、申请名称为“通信方法、装置以及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、装置以及系统。
背景技术
在富媒体消息系统中，发送方不需接收方同意即可向接收方发送消息。目前，小程序的开发门槛低，因此很多实体都可以开发并利用富媒体消息系统直接向用户分发富媒体消息小程序。因此，当开发富媒体消息小程序的实体或者富媒体消息小程序的获取来源不可信或无法确认是否可信时，用户直接运行接收到的富媒体消息小程序可能会给用户带来风险和损失。
发明内容
本申请实施例提供一种通信方法、装置以及系统，能够使用户在安全、可控的环境下运行富媒体消息小程序，避免给用户带来风险和损失。
第一方面，提供了一种通信方法，该方法可以由富媒体消息终端执行，或者，也可以由富媒体消息终端的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：富媒体消息终端获取第一信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序；富媒体消息终端向第一小程序管理平台发送第一请求消息，其中，第一请求消息包括第一信息的部分信息或全部信息，第一请求消息用于请求第一小程序管理平台对第一富媒体消息小程序进行验证，第一小程序管理平台为能够提供富媒体消息小程序验证功能的小程序管理平台，富媒体消息终端接收来自第一小程序管理平台的第一响应消息，第一响应消息包括第一小程序管理平台对第一富媒体消息小程序的验证结果，富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作。
基于上述技术方案，富媒体消息终端可以与第一小程序管理平台交互验证第一富媒体消息小程序，并根据验证结果针对第一富媒体消息小程序执行相应操作。该方法可以使用户在安全、可控的环境下运行获取到的富媒体消息小程序，避免给用户带来风险和损失。
结合第二方面，在第二方面的某些实现方式中，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序的安全性，或者，第一请求消息用于请求第一小程序管理平台验证是否允许富媒体消息终端运行第一富媒体消息小程序。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：富媒体消息终端基于第一信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序。
结合第一方面，在第一方面的某些实现方式中，富媒体消息终端根据第一信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序，包括：富媒体消息终端获取第二信息，第二信息包括富媒体消息小程序的安全源信息和/或用于验证第一富媒体消息小程序的签名的公钥，或者，第二信息包括验证策略，验证策略指示需要向第一小程序平台请求验证第一富媒体消息小程序；富媒体消息终端根据第一信息和第二信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序。
结合第一方面，在第一方面的某些实现方式中，富媒体消息终端根据第一信息和第二信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序，包括：当第一信息的发送方标识未包含在安全源信息中时，富媒体消息终端确定待向第一小程序平台请求验证第一富媒体消息小程序；或者，当使用公钥验证第一富媒体消息小程序的信息中的签名失败时，富媒体消息终端确定待向第一小程序平台请求验证第一富媒体消息小程序；或者，当验证策略指示待向第一小程序平台请求验证第一富媒体消息小程序时，富媒体消息终端确定待向第一小程序平台请求验证第一富媒体消息小程序。
基于上述技术方案，富媒体消息终端的用户可以灵活设置第二信息，富媒体消息终端基于用户的设置确定是否待向第一小程序管理平台请求验证第一富媒体消息小程序，从而提升用户体验。
结合第一方面，在第一方面的某些实现方式中，富媒体消息终端获取第一信息，包括：富媒体终端从第二小程序管理平台获取第一信息，或者，富媒体终端从第二小程序管理平台之外的管理平台获取第一信息，或者，富媒体终端从富媒体终端之外的富媒体设备获取第一信息。
结合第一方面，在第一方面的某些实现方式中，富媒体消息终端从第二小程序管理平台获取第一信息，包括：富媒体消息终端获取第二小程序管理平台对应的统一资源定位符URL；富媒体消息终端获取URL对应的网页(web)页面，web页面包括第一信息和/或小程序查询入口，小程序查询入口用于获取第一信息。
结合第一方面，在第一方面的某些实现方式中，富媒体消息终端获取第一信息，包括：富媒体消息终端接收第一富媒体消息，第一富媒体消息包括第一信息。
示例的，第一富媒体消息可以是其他设备或平台主动发送给富媒体消息终端，或者，富媒体消息终端先向其他设备或平台发送第一富媒体消息小程序相关的查询消息，其他设备或平台向富媒体消息终端返回包括查询结果的第一富媒体消息。
结合第一方面，在第一方面的某些实现方式中，验证结果包括以下一项：第一验证结果、第二验证结果、第三验证结果、第四验证结果，其中，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证，第四验证结果为第一小程序管理平台根据第一请求消息查询得到保存在本地的富媒体消息小程序的信息和/或富媒体消息小程序。
基于上述技术方案，第一小程序管理平台对第一富媒体消息小程序进行分级验证，富媒体消息终端可以基于第一小程序管理平台返回的不同的验证结果，执行不同的操作，提升用户体验。
结合第一方面，在第一方面的某些实现方式中，验证结果为第一验证结果或者第四验证结果，富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作，包括：富媒体消息终端根据验证结果运行第一富媒体消息小程序；或，验证结果为第二验证结果 或者第三验证结果，富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作，包括：富媒体消息终端根据用户指示或本地安全设置，确定运行第一富媒体消息小程序；或者，富媒体消息终端根据用户指示或本地安全设置，确定拒绝运行第一富媒体消息小程序。
结合第一方面，在第一方面的某些实现方式中，验证结果为第一验证结果或者第四验证结果，富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作，包括：富媒体消息终端向第一富媒体消息小程序提供用户信息，该用户信息为与富媒体消息终端对应的用户有关的信息，用于指示第一富媒体消息小程序的使用者。
基于上技术方案，基于第一富媒体消息小程序的验证结果富媒体消息终端可以向第一富媒体消息小程序提供富媒体消息终端的用户信息，用于用户免认证使用第一富媒体消息小程序的服务，该方法在确保可以运行第一富媒体消息小程序的前提下，同时方便了用户使用第一富媒体消息小程序。
第二方面，提供了一种通信方法，该方法可以由第一小程序管理平台执行，或者，也可以由第一小程序管理平台的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：第一小程序管理平台接收来自富媒体消息终端的第一请求消息，其中，第一请求消息包括第一信息的部分信息或全部信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序，第一请求消息用于请求第一小程序管理平台对第一富媒体消息小程序进行验证，第一小程序管理平台为能够提供富媒体消息小程序验证的小程序管理平台；第一小程序管理平台根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果；第一小程序管理平台向富媒体消息终端发送第一响应消息，第一响应消息包含验证结果。
基于上述技术方案，第一小程序管理平台接收富媒体消息终端发送的第一请求消息，以请求验证第一富媒体消息小程序，第一小程序管理平台与富媒体消息终端交互验证第一富媒体消息小程序，并返回验证结果。该方法可以使用户在安全、可控的环境下运行获取到的富媒体消息小程序，避免给用户带来风险和损失。
结合第二方面，在第二方面的某些实现方式中，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序的安全性，或者，第一请求消息用于请求第一小程序管理平台验证是否允许富媒体消息终端运行第一富媒体消息小程序。
结合第二方面，在第二方面的某些实现方式中，第一小程序管理平台根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果，包括：第一小程序管理平台根据第一请求消息查询第一小程序管理平台本地保存的富媒体消息小程序的信息；第一小程序管理平台根据查询结果得到验证结果。
结合第二方面，在第二方面的某些实现方式中，若第一小程序管理平台根据所述第一请求消息能够查询到第一小程序管理平台本地保存的富媒体消息小程序的信息，该验证结果包含第四验证结果，第四验证结果为第一小程序管理平台本地保存的富媒体消息小程序的信息和/或富媒体消息小程序，或者，若第一小程序管理平台在本地能够查询到第一富媒体消息小程序的信息，比较第一小程序管理平台本地保存的富媒体消息小程序的信息与第一请求消息得到验证结果，验证结果包含第一验证结果或第二验证结果或第三验证结果，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证。
结合第二方面，在第二方面的某些实现方式中，第一小程序管理平台根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果，包括：第一小程序管理平台在本地获取第三信息，第三信息包括富媒体消息终端对应的签约信息和/或配置信息；第一小程序管理平台根据第一请求消息和第三信息得到验证结果。
示例的，富媒体消息终端对应的签约信息为富媒体消息终端的用户与富媒体消息业务提供方(例如运营商)签订的提供和使用服务的约定，其中，该签约信息可以包括该富媒体终端的用户是否有偿或者无偿使用运营商提供的富媒体消息小程序服务，或者能使用哪些提供方提供的富媒体消息小程序；配置信息可以为运营商单方面在富媒体消息系统中配置的信息，例如，某些区域或者某类用户或者某个时间段允许富媒体消息终端的用户使用富媒体消息小程序服务，或者，富媒体消息终端只能运行运营商提供的富媒体消息小程序，或者，富媒体消息终端只能运行从运营商平台获取的富媒体消息小程序。
结合第二方面，在第二方面的某些实现方式中，第一小程序管理平台根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果，包括：第一小程序管理平台根据第一请求消息获取第一富媒体消息小程序；第一小程序管理平台对获取的第一富媒体消息小程序进行安全扫描；第一小程序管理平台根据扫描结果得到验证结果。
结合第二方面，在第二方面的某些实现方式中，验证结果包含第一验证结果或第二验证结果或第三验证结果，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证。
基于上述技术方案，第一小程序管理平台对第一富媒体消息小程序进行分级验证，富媒体消息终端可以基于第一小程序管理平台返回的不同的验证结果，执行不同的操作，提升用户体验。
结合第一方面至第二方面，在某些实现方式中，第一富媒体消息小程序的信息包括以下至少一项：第一富媒体消息小程序的下载地址、第一富媒体消息小程序的标识、第一富媒体消息小程序的名称、第一富媒体消息小程序的图标的地址、第一富媒体消息小程序的版本、第一富媒体消息小程序的开发者信息、第一富媒体消息小程序的提供商信息、第一富媒体消息小程序的开发者的签名信息、第一富媒体消息小程序的提供商的签名信息。
结合第一方面至第二方面，在某些实现方式中，第一请求消息和第一请求响应消息为富媒体消息。
第三方面，提供一种通信装置，该装置用于执行上述第一方面或第二方面任一种可能实现方式中的方法。具体地，该装置可以包括用于执行第一方面或第二方面任一种可能实现方式中的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为通信设备(如富媒体消息终端，又如小程序管理平台)。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(如富媒体消息终端，又如小程序管理平台)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第四方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面或第二方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为通信设备(如富媒体消息终端，又如小程序管理平台)。
在另一种实现方式中，该装置为用于通信设备(如富媒体消息终端，又如小程序管理平台)的芯片、芯片系统或电路。
第五方面，提供一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第六方面，提供一种计算机可读存储介质，该计算机可读介质存储用户设备执行的程序代码，该程序代码包括用于执行上述第一方面或第二方面任一种可能实现方式中的方法。
第七方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面或第二方面任一种可能实现方式中的方法。
第八方面，提供一种通信系统，包括前述的富媒体消息终端、第一小程序管理平台、第二小程序管理平台中的至少一项。
附图说明
图1是适用于本申请实施例的一通信系统的示意图。
图2是适用于本申请实施例的另一通信系统的示意图。
图3是适用于本申请实施例的另一通信系统的示意图。
图4是适用于本申请实施例的另一通信系统的示意图。
图5是本申请实施例提供的一种通信方法的示意图。
图6是本申请实施例提供的一种获取第一富媒体消息小程序的信息的示意图。
图7是本申请实施例提供的另一种获取第一富媒体消息小程序的信息的示意图。
图8是本申请实施例提供的一种通信装置1100的示意性图。
图9是本申请实施例提供另一种通信装置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 Communications Services，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消息。富媒体消息可用于物联网设备之间，因此，富媒体消息也可称为5G物联网消息。可以理解，消息的具体命名不对本申请实施例的保护范围造成限定。下文为统一，用富媒体消息进行描述。
2、聊天机器人(Chatbot)：富媒体消息中行业消息应用的呈现形式，模拟人类智能对话，向用户提供行业消息服务功能。
3、小程序(MiniApp)：是一种基于web技术(web technology)(如JavaScript)实现的、不需要在终端设备安装即可在终端设备上的宿主移动应用程序(或宿主客户端)中运行的应用程序。其中，宿主移动应用程序(或宿主客户端)是安装在终端设备上的应用程序，宿主应用程序通常可以运行多个(种)小程序。
4、富媒体消息小程序：是以终端设备(或称为富媒体消息终端)上运行的富媒体消息应用程序(或富媒体消息客户端)为宿主应用程序(或宿主客户端)的小程序，也就是说，富媒体消息小程序由富媒体消息应用程序从网络侧下载后直接运行(如解释执行)，无需被安装到终端设备上。用户需要通过富媒体消息客户端运行和进入富媒体消息小程序。富媒体消息应用程序中内置的小程序引擎(用于解释执行富媒体消息小程序)和富媒体消息小程序解耦，例如，二者均可独立于对方升级。富媒体消息小程序运行后，可与富媒体小程序对应的服务器进行交互，实现其他业务办理(如银行卡余额查询，银行卡转账、购买理财产品、信用卡还款)等业务，这些业务，在本申请实施例中称为“富媒体消息小程序服务”。
5、网页视图(WebView)：可以简单的看作一个可以嵌套到界面上的一个浏览器控件。用户通常是用浏览器来浏览网页，webview是一个嵌入式的浏览器，是嵌入在原生应用中的，用户可能都意识不到在使用浏览器。传统浏览器分为两个部分，UI(地址栏、导航栏)和浏览器引擎。webview就是原生应用中的浏览器引擎。webview只是一个可视化的组件，是作为原生APP的视觉部分。用webview展示的内容是不需要存储在本地的，可以直接从服务器获取。运行在webview中的JS代码有能力调用原生的系统API，没有传统浏览器沙箱的限制。
为便于理解本申请实施例，下面结合图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)或域名系统(domainname 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所示的系统中，增加了小程序管理平台。
小程序管理平台可以为安全的小程序管理平台，也可以为非安全的小程序管理平台。其中，安全的小程序管理平台是由运营商或者第三方安全实体等提供，非安全的小程序管理平台是由行业客户或非安全第三方实体等提供，小程序管理平台可独立部署，或者也可内置在5GMC或者独立于5GMC部署(如部署在MaaP，或者独立部署，可与5G MC互通)，不予限制。下面介绍小程序管理平台可包括逻辑功能模块。
1)运营管理：主要用于审核富媒体消息小程序是否符合富媒体消息小程序开发规范、验证富媒体消息小程序、发布富媒体消息小程序，发布后用户才能查询到。
2)小程序包存储(即富媒体消息小程序包存储)：主要用于存储富媒体消息小程序包。
3)富媒体消息小程序目录(即富媒体消息小程序目录)：主要用于汇总与存储富媒体消息小程序信息。该富媒体消息小程序信息可包括该富媒体消息小程序的基本信息，如包括标识(identifier，ID)、名称、图标、版本等。该富媒体消息小程序信息还可包括富媒体消息小程序的详细信息，如包括富媒体消息小程序的提供商(行业客户)、业务类型、联系方式、网站，以及富媒体消息小程序用途、开发方信息等。
可以理解，小程序目录和Chatbot目录可以相同，也可以不同，不予限制。以小程序目录和Chatbot相同为例，一种可能的情况，在富媒体消息系统的架构中，包括一目录，该目录可以用于汇总Chatbot数据信息，即实现图2中所述的Chatbot目录的功能，还可以用于汇总与存储富媒体消息小程序信息，即实现图3中所述的小程序目录的功能。
4)小程序查询服务(即富媒体消息小程序查询服务)：主要用于处理富媒体消息终端的富媒体消息小程序查询请求，提供匹配、排序等算法服务，向用户返回查询结果。该 查询结果可包括根据富媒体消息小程序关键字查询到的富媒体消息小程序信息，如：ID、名称、图标、版本等。
图4是适用于本申请实施例的另一通信系统的示意图。如图4所示，该通信系统以富媒体消息系统的架构为例。如图4所示，与图3相比，在图4所示的系统中，小程序管理平台可直接与富媒体消息中心对接。关于各设备的描述，可参考前面的描述，此处不再赘述。
目前，在富媒体消息系统中，发送方不需要接收方同意即可向接收方发送消息。具体流程如下：
步骤1：发送方发送富媒体消息，经过主叫侧IMS接入功能发送到主叫所归属的富媒体消息处理功能，主叫消息处理功能返回已收到富媒体消息的应答；
步骤2：主叫富媒体消息处理功能向接收方所归属的富媒体消息处理功能发送富媒体消息，被叫富媒体消息处理功能返回已收到富媒体消息的应答；
步骤3：被叫富媒体消息处理功能向接收方发送富媒体消息，接收方返回成功收到富媒体消息的应答；
步骤4：接收方向主叫富媒体消息处理功能发送递送报告消息，逐跳传递，最终发送方向主叫富媒体消息处理功能返回收到递送报告的应答。
目前，小程序的开发门槛低，因此很多实体都可以开发并利用富媒体消息系统直接向用户分发富媒体消息小程序。因此，当开发富媒体消息小程序的实体不安全或者富媒体消息小程序的获取来源不安全时，用户直接运行接收到的富媒体消息小程序会给用户带来风险和损失。
有鉴于此，本申请提出一种通信方法，能够有效解决上述技术问题。下文将结合附图详细说明本申请实施例提供的方法。
图5是本申请实施例提供的一种通信方法的示意图。该方法可以包括如下步骤。
S510，富媒体消息终端获取第一信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序。
可选地，第一富媒体消息小程序的信息包括第一富媒体消息小程序的下载地址。这样，富媒体消息终端(或者富媒体消息终端中的富媒体消息客户端)可以根据第一富媒体消息小程序的下载地址下载第一富媒体消息小程序。
可选地，第一富媒体消息小程序的信息还包括以下至少一项：第一富媒体消息小程序的标识、第一富媒体消息小程序的名称、富媒体消息小程序的图标的地址、第一富媒体消息小程序的版本、第一富媒体消息小程序的开发者信息、第一富媒体消息小程序的提供商信息、第一富媒体消息小程序的开发者签名、第一富媒体消息小程序的提供商的签名。示例的，第一富媒体消息小程序的提供商信息可包括以下至少一项：商标、业务类型、联系方式、网站等。
可以理解，上述为示例性说明，本申请实施例不限于此。例如，第一富媒体消息小程序的信息还可以包括以下至少一项：第一富媒体消息小程序的用途、第一富媒体消息小程序的描述。
示例的，富媒体消息终端可以通过以下任意方式获取第一信息。
方式一：富媒体终端从第二小程序管理平台获取第一信息，其中，该第二小程序管理平台本地保存有第一富媒体消息小程序的信息和/或第一富媒体消息小程序。
示例的，第二小程序管理平台发送第一富媒体消息小程序是通过富媒体消息发送文件的方法将第一富媒体消息小程序发送给富媒体消息终端的。
可以理解的是，第二小程序管理平台可以为可信的小程序管理平台，也可以为非可信的小程序管理平台。其中，可信的小程序管理平台可以理解为运营商的小程序管理平台，或运营商信任的第三方小程序管理平台，或提供方(来源)可信的第三方小程序管理平台。不可信的小程序管理平台可以理解为提供方(来源)不可信或无法确认是否可信的第三方小程序管理平台。
可以理解，如果第二小程序管理平台为可信的小程序管理平台，那么第二小程序管理平台中的保存富媒体消息小程序可以认为是安全的小程序。本申请中富媒体消息小程序的是否安全是指富媒体消息小程序是否会对富媒体消息用户的数据安全、终端系统安全、隐私等带来风险和损失。例如，第一富媒体消息小程序是安全的小程序，则表示该小程序不存在未授权访问富媒体消息终端的功能，不存在未授权使用或破坏富媒体消息终端的功能、不存在未授权获取富媒体消息终端的信息的功能、不会修改或破坏富媒体消息终端的文件的功能等。
在一种实现方式中，富媒体消息终端可以通过发送富媒体消息从第二小程序管理平台获取第一信息。下面结合图6示例性进行描述。
图6是本申请提供的一种从第二小程序管理平台获取第一信息的示意图，可以包括以下步骤：
步骤1：富媒体消息终端向富媒体消息中心发送第一查询请求消息。第一查询请求消息包含查询信息。对应的，富媒体消息中心接收来自富媒体消息终端的第一查询请求消息。
其中，该查询信息，包括用于描述第一富媒体消息小程序的信息的关键字，或包括第一富媒体消息小程序的相关信息，或包括富媒体消息终端查询的第一富媒体消息小程序要满足的需求信息。
可选地，查询信息包括以下至少一项或以下至少一项包含的关键字：第一富媒体消息小程序的名称、第一富媒体消息小程序的类型、第一富媒体消息小程序的提供商的名称、第一富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本等。
步骤2：富媒体消息中心向第二小程序管理平台发送第二查询请求消息，第二查询请求消息包含查询信息。对应的，第二小程序管理平台接收来自富媒体消息中心的第二查询请求消息。
步骤3：第二小程序管理平台根据查询信息在本地获取第一富媒体消息小程序的信息和/或第一富媒体消息小程序本身。
步骤4：第二小程序管理服务器向富媒体消息中心发送第二查询响应消息，第二查询响应消息包含第一富媒体消息小程序的信息和/或第一富媒体消息小程序本身。对应的，富媒体消息中心接收来自小程序管理服务器的第二查询响应消息。
步骤5：富媒体消息中心向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含第一富媒体消息小程序的信息和/或第一富媒体消息小程序本身。对应的，富媒体消息终端接收来自富媒体消息中心的第一查询响应消息。
步骤6：富媒体消息终端显示第一富媒体消息小程序的信息和/或呈现第一富媒体消息小程序的有关界面。
示例的，富媒体消息终端以卡片或者文本方式将第一富媒体消息小程序的信息显式给富媒体消息终端对应的用户，以供用户交互下载、运行小程序。
示例的，第一富媒体消息小程序的有关界面包括用于触发运行第一富媒体消息小程序的图标。
可以理解，在该实现方式中，第一查询请求消息、第二查询请求消息、第一查询响应消息和第二查询响应消息均为富媒体消息。
在另一种实现方式中，第二小程序管理平台也可能不是基于富媒体消息终端的查询请求发送第一信息，而是主动向富媒体消息终端发送包含第一信息的富媒体消息，具体过程这里不再赘述。
在又一种实现方式中，富媒体消息终端可以先获取第二小程序管理平台对应的统一资源定位符(uniform resource locator，URL)(即第二小程序管理平台对应的web页面的链接)，之后，富媒体消息终端根据第二小程序管理平台对应的URL从第二小程序管理平台获取第一信息。示例的，富媒体消息终端可以基于第二小程序管理平台对应的URL，通过使用富媒体消息终端中内置webview或者内置浏览器获取第一信息。下面结合图7示例性进行描述。
图7是本申请提供的一种从第二小程序管理平台获取第一信息的示意图，可以包括以下步骤：
步骤1：富媒体消息终端获取第二小程序管理平台对应的URL。
示例的，富媒体消息终端可以通过以下方式获取第二小程序管理平台对应的URL。
1)运营商可以通过手机卡将该URL提前配置到富媒体消息终端。
2)富媒体消息终端通过配置服务器获取该URL。
示例的，配置服务器主动配置该URL给富媒体消息终端，如通过开放移动联盟(open mobile alliance，OMA)设备管理等空中下载(over the air，OTA)配置机制，下发配置到富媒体消息终端，具体实现可以参见OMA设备管理标准，这里不赘述。
示例的，富媒体消息终端可根据国际移动用户识别码(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消息，以请求配置信息，对应的，配置服务器向富媒体消息终端发送配置信息。其中，配置信息包括该URL。
3)运营商可以通过富媒体消息将该URL配置到富媒体消息终端。
示例的，富媒体消息终端接收来自富媒体消息中心的富媒体消息，该富媒体消息中包括该URL。
步骤2：富媒体消息终端使用内置的Webview或内置浏览器，根据该URL向第二小程序管理平台请求小程序web页面。
示例的，富媒体消息终端根据该URL自动触发或在富媒体消息终端对应的用户触发下向第二小程序管理平台请求小程序web页面。
步骤3：富媒体消息终端内置的Webview或内置浏览器接收第二小程序管理平台返回的小程序web页面。
可选地，该web页面包含第一富媒体消息小程序的信息或列表，和/或，小程序查询入口。其中，富媒体消息终端对应的用户可以通过小程序查询入口从小程序管理平台获取第一富媒体消息小程序的信息或第一富媒体消息小程序本身。
示例的，如果步骤2中由用户触发，那么富媒体消息终端对应的用户可以在内置的Webview或浏览器的查询入口中输入第一富媒体消息小程序的信息的关键字，或输入第一富媒体消息小程序的相关信息，或输入富媒体消息终端查询的第一富媒体消息小程序要满足的需求信息，向第二小程序管理平台触发请求web页面，对应的，步骤3中小程序管理平台返回的web页面可以包含第一富媒体消息小程序的信息和/或第一富媒体消息小程序本身，可选地，web页面还可以包含小程序查询入口。
示例的，如果步骤2中由富媒体消息终端自动触发向第二小程序管理平台触发请求web页面，对应的，步骤3中小程序管理平台返回的web页面包含小程序查询入口。
步骤4：富媒体消息终端向用户显示web页面。
可以理解，图6和图7中获取第一富媒体消息小程序的信息和/或第一富媒体消息小程序本身的方式或步骤仅为方式一可能实现方式的示例性说明，本申请实施例不限于此。
方式二：富媒体终端从第一平台获取第一信息，其中，第一平台为第二小程序管理平台之外的管理平台，具体的，富媒体终端从第一平台接收富媒体消息，该富媒体消息包括第一信息。例如，第一平台可以为银行或保险等提供服务的平台。该富媒体消息可能是富媒体终端向第一平台发送与第一富媒体消息小程序相关的查询请求后，第一平台发送的富媒体消息，也可能是第一平台主动发送的富媒体消息。
方式三：富媒体消息终端从其他富媒体消息设备获取第一信息，具体的，富媒体消息终端从其他富媒体消息设备接收富媒体消息，该富媒体消息包括第一信息。例如，富媒体消息终端A的用户通过富媒体消息终端A向富媒体消息设备B发送第一信息。
可以理解的是，富媒体消息设备可以为除所述富媒体消息终端之外的可以发送富媒体消息的设备，本申请对此不做限制。例如，富媒体消息设备可以为除所述富媒体消息终端之外的其他富媒体消息终端，也可以富媒体消息服务器。
可以理解，除上述第一平台或者其他富媒体终端外，富媒体终端还可能从其他发送方接收富媒体消息，该富媒体消息包括第一信息，本申请对该富媒体消息的发送方不做限定。
还可以理解，上述方式一至方式三中富媒体终端获取第一信息的方式仅为示例性说明，本申请实施例不限于此。
S520，富媒体消息终端向第一小程序管理平台发送第一请求消息，其中，第一请求消息包括第一信息的部分信息或全部信息，第一请求消息用于请求验证第一富媒体消息小程序的可用性，第一小程序管理平台为能够提供富媒体消息小程序可用性验证功能的小程序管理平台。对应的，第一小程序管理平台接收来自富媒体消息终端的第一请求消息，执行S540。
可以理解的是，第一小程序管理平台与第二小程序管理平台为不同的小程序管理平台。
示例的，第一小程序管理平台能够提供的富媒体消息小程序可用性验证功能包括，验证第一富媒体消息小程序的安全性，或者，验证是否允许富媒体消息终端运行第一富媒体消息小程序。本申请对第一小程序管理平台验证富媒体消息小程序的功能不作具体限定，可以根据实际需要增加第一小程序管理平台验证富媒体消息小程序的功能的范围或内容。
示例的，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序的可用性包括，请求第一小程序管理平台验证第一富媒体消息小程序的安全性，和/或，请求第一小程序管理平台验证是否允许富媒体消息终端运行第一富媒体消息小程序。
示例的，第一请求消息中包括的第一富媒体消息小程序的信息的部分或全部信息可以为用于描述第一富媒体消息小程序的信息的关键字，或第一富媒体消息小程序的相关信息，或查询第一富媒体消息小程序要满足的需求信息，或第一富媒体消息小程序本身。
示例的，第一请求消息可以为富媒体消息，也可以为HTTP/HTTPS消息。示例的，第一小程序管理平台的信息(例如第一小程序管理平台的地址)可以由手机卡配置到富媒体消息终端，或通过配置服务器配置。例如，可以是配置服务器主动配置给富媒体消息终端，如通过OMA设备管理等OTA配置机制，下发配置到富媒体消息终端，具体实现参见OMA设备管理标准。又例如，富媒体消息终端可根据国际移动用户识别码(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消息，以请求配置信息，对应的，配置服务器向富媒体消息终端发送配置信息。其中，配置信息包括第一小程序管理平台的信息。
可选地，在S520之前，该方法还可以包括：
S530，富媒体消息终端基于第一信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序。
也就说，在S520之前，富媒体消息终端可以基于第一信息判断是否待向第一小程序管理平台请求验证第一富媒体消息小程序，如果需要验证，则执行S520，如果富媒体消息终端根据第一信息确定可以运行第一富媒体消息小程序，则富媒体消息终端直接运行第一富媒体消息小程序即可。
在一种可能的实现方式中，富媒体消息终端接收到第一信息后，富媒体消息终端的用户可以选择点击第一富媒体消息小程序的图标后，富媒体消息终端响应于该操作执行步骤S530。也就是说，如果富媒体消息终端的用户不点击第一富媒体消息小程序的图标，则富媒体消息终端不会发起验证流程。在又一种可能的实现方式中，富媒体消息终端接收到第一信息后，响应于接收到第一信息，富媒体消息终端执行步骤S530。
在另一种可能的实现方式中，富媒体消息终端基于第一信息判断是否待向第一小程序管理平台请求验证第一富媒体消息小程序的可用性，是指富媒体终端基于第一信息和本地的安全策略配置，判断是否待向第一小程序管理平台请求验证第一富媒体消息小程序的可用性，其中安全策略可以为免验证级别，如免验证级别可以分为高、中、低，其中，对应同一富媒体消息小程序而言，验证级别越低表示该富媒体消息小程序越容易通过验证，验证级别越高表示该富媒体消息小程序越难通过验证。例如，根据本地的安全策略配置，当富媒体消息终端本地的免验证级别设置的较低(如只验证开发商信息)，即使第一富媒体消息小程序可能存在一些其他风险，只要富媒体消息终端基于第一信息确定第一富媒体消息小程序满足本地的免验证级别要求(即：通过了本地验证)，那么富媒体消息终端就认为第一富媒体消息小程序不待向第一小程序管理平台请求进一步的可用性验证。也就是说，对于不同的富媒体消息终端，由于本地的免验证级别设置的不同，有可能对于同一富媒体 消息小程序，有些富媒体消息判断待向第一小程序管理平台请求验证该富媒体消息小程序的可用性，有些富媒体消息判断不向第一小程序管理平台请求验证该富媒体消息小程序的可用性。该实现方式也可以与上述两种实现方式相结合。例如，富媒体消息终端接收到第一信息后，富媒体消息终端的用户可以选择点击第一富媒体消息小程序的图标后，触发富媒体消息终端本地验证第一富媒体消息小程序，如果本地验证不通过，富媒体消息终端再执行步骤S530。或者，富媒体消息终端接收到第一信息后，响应于接收第一信息，富媒体消息终端本地验证第一富媒体消息小程序，如果本地验证不通过，再执行步骤S530。
示例的，富媒体消息终端根据第一信息和第二信息(即富媒体消息终端的安全策略配置)验证第一富媒体消息小程序的可用性，其中，第二信息用于确定待向第一小程序管理平台请求验证第一富媒体消息小程序的可用性。示例的，第二信息可以包括提供富媒体消息小程序的安全源信息和/或用于验证富媒体消息小程序签名的公钥，其中安全源信息包括安全服务商的信息、安全链接等，或者，第二信息可以包括验证策略，该验证策略指示是否需要向第一小程序平台请求验证第一富媒体消息小程序。
可选地，第一富媒体消息小程序的信息只要通过了第二信息中的任一验证条件，富媒体消息终端即不向第一小程序管理平台验证第一富媒体消息小程序的可用性。
例如，富媒体消息终端基于第二信息中安全源信息确定是否待向第一小程序管理平台验证第一富媒体消息小程序的可用性。具体举例来说，第一富媒体消息小程序的信息的发送方标识未包含在安全源信息中时，则富媒体消息终端待向第一小程序管理平台验证第一富媒体消息小程序的可用性。例如，发送方标识可以为银行或保险等平台的服务号码或个人号码。
再例如，富媒体消息终端使用第二信息中的公钥，验证第一富媒体消息小程序信息中的签名，富媒体消息终端根据验证结果确定是否待向第一小程序管理平台验证第一富媒体消息小程序的可用性。具体举例来说，第一富媒体消息小程序信息中的签名包括第一富媒体消息小程序提供商的签名信息，该提供商用私钥加密生成的一个密文，发送方(例如第二小程序管理平台)把签名随数据发送给富媒体消息终端，富媒体消息终端用该私钥对应的公钥解密签名，从而验证发送方的身份、以及明文数据是否被篡改。那么，如果富媒体消息终端使用该公钥未通过第一富媒体小程序的信息中的提供商的签名验证，则富媒体消息终端确定待向第一小程序平台请求验证第一富媒体消息小程序的可用性。
可选地，第二信息可以由手机卡配置到富媒体消息终端，或通过配置服务器配置。例如，可以是配置服务器主动配置给富媒体消息终端，如通过OMA设备管理等OTA配置机制，下发配置到富媒体消息终端，具体实现参见OMA设备管理标准。又例如，富媒体消息终端可根据国际移动用户识别码(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消息，以请求配置信息，对应的，配置服务器向富媒体消息终端发送配置信息。其中，配置信息包括第二信息。
又例如，富媒体消息终端基于第二信息中的验证策略确定是否待向第一小程序管理平台验证第一富媒体消息小程序的可用性。具体举例来说，如果该验证策略指示向第一小程 序平台请求验证第一富媒体消息小程序，则富媒体消息终端待向第一小程序管理平台验证第一富媒体消息小程序的可用性。
可以理解，在S530中如果富媒体消息终端判断可以直接运行第一富媒体消息小程序，则富媒体消息终端运行第一富媒体消息小程序。另外，在S530中如果富媒体消息终端判断需要进一步向第一小程序管理平台验证第一富媒体消息小程序的可用性，则继续执行S520。
本申请中富媒体消息终端根据第一信息运行第一富媒体消息小程序可以有以下理解，如果第一信息中不包括第一富媒体消息小程序，则富媒体消息终端在运行第一富媒体消息小程序前，需要根据第一信息中的第一富媒体消息小程序的下载地址先下载第一富媒体消息小程序，然后再运行第一富媒体消息小程序。如果第一信息中包括第一富媒体消息小程序本身，则富媒体消息终端可以直接运行第一富媒体消息小程序。本申请中涉及运行第一富媒体消息小程序描述的地方，可以根据第一信息包含的具体信息判断是否需要先执行下载操作，后文不再一一解释。
S540，第一小程序管理平台根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果。
可选地，本申请中验证结果包括第一验证结果、第二验证结果、第三验证结果，其中，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证，第四验证结果为第一小程序管理平台根据所述第一请求消息查询得到的保存在第一小程序管理平台的富媒体消息小程序的信息和/或富媒体消息小程序(即隐式指示第一富媒体消息小程序通过验证)。示例地，以第一小程序管理平台对第一信息中包括第一富媒体消息小程序的信息一一进行验证为例进行说明。如果第一富媒体消息小程序的信息全部验证通过，则验证结果为第一验证结果。如果第一富媒体消息小程序的信息中的任一信息都没有验证通过，则验证结果为第二验证结果。如果第一富媒体消息小程序的信息中的一部分信息通过验证，一部分信息没有通过验证，则验证结果为第三验证结果，例如，第一富媒体消息小程序的信息中提供商或者开发者身份通过验证，但无法验证第一富媒体消息小程序的信息中的其它信息是否安全，则验证结果为第三验证结果。
具体的，如果第一请求消息请求验证第一富媒体消息小程序的安全性，则第一验证结果指示第一富媒体消息小程序为安全的小程序，第二验证结果指示第一富媒体消息小程序为不安全的小程序，第三验证结果指示第一富媒体消息小程序为部分安全的小程序。如果第一请求消息请求验证是否允许富媒体消息终端运行第一富媒体消息小程序，则第一验证结果指示允许富媒体消息终端运行第一富媒体消息小程序，第二验证结果指示不允许富媒体消息终端运行第一富媒体消息小程序。
可选地，第一小程序管理平台根据第一请求消息验证第一富媒体消息小程序的可用性，包括以下任一实现方式。
在一种实现方式中，第一请求消息可以请求验证第一富媒体消息小程序的安全性，则第一小程序管理平台根据第一请求消息验证查询本地是否保存有第一富媒体消息小程序的信息，并根据查询结果生成第一富媒体消息小程序的验证结果。该实现方式可以理解为富媒体消息终端基于第一请求消息到第一小程序管理平台查询第一富媒体消息小程序的相关信息，第一小程序管理平台根据查询结果确定第一富媒体消息小程序是否通过验证。
示例的，在该实现方式中，如果富媒体消息终端根据第一请求消息能够查询到第一小程序管理平台本地保存的富媒体消息小程序的信息，则验证结果第四验证结果，第四验证结果为富媒体消息终端根据第一请求消息查询到的本地保存的富媒体消息小程序的信息和/或富媒体消息小程序，或者，将第一请求消息中包含的第一富媒体消息的信息和富媒体消息终端根据第一请求消息查询到的平台本地保存的富媒体消息小程序的信息进行比较验证，如果比较结果一致表明该第一富媒体消息小程序通过验证，即验证结果为第一验证结果；如果在本地没有查询到第一富媒体消息小程序的信息，即表明该第一富媒体消息小程序没有通过验证，即验证结果为第二验证结果。
在另一种实现方式中，第二小程序管理平台根据第一请求消息验证直接在本地平台验证第一富媒体消息小程序的可用性。示例的，该实现方式中，第一小程序管理平台具体可以通过以下方式进行验证。
方式一：第一请求消息可以请求验证是否允许运行第一富媒体消息小程序，则第一小程序管理平台根据第一请求消息在本地获取第三信息，第三信息包括富媒体消息终端对应的签约信息和/或配置信息，第一小程序管理平台根据第一请求消息和第三信息确定第一富媒体消息小程序的验证结果。
其中，富媒体消息终端对应的签约信息为富媒体消息终端的用户与富媒体消息业务提供方(例如运营商)签订的提供和使用服务的约定，其中，该签约信息可以包括该富媒体终端的用户是否有偿或者无偿使用运营商提供的富媒体消息小程序服务，或者能使用哪些提供方提供的富媒体消息小程序；配置信息可以为运营商单方面在富媒体消息系统中配置的信息，例如，某些区域或者某类用户或者某个时间段允许富媒体消息终端的用户使用富媒体消息小程序服务，或者，富媒体消息终端只能运行运营商提供的富媒体消息小程序，或者，富媒体消息终端只能运行从运营商平台获取的富媒体消息小程序。
示例的，以第三信息中的配置信息包括富媒体消息终端只能运行从运营商平台获取的富媒体消息小程序为例进行说明。如果第一小程序管理平台根据第一请求消息确定第一富媒体消息小程序的来源为运营商平台，则富媒体消息终端得到验证结果为第一验证结果，如果第一小程序管理平台根据第一请求消息确定第一富媒体消息小程序的来源不是运营商平台，则富媒体消息终端得到验证结果为第二验证结果。
方式二：第一请求消息可以请求验证第一富媒体消息小程序的安全性，则第一小程序管理平台可以根据第一请求消息中包含的第一信息的部分信息或全部信息，从本地获取一个对应的富媒体消息小程序的信息(这里称为第二富媒体消息小程序的信息)，第一小程序管理平台将该获取的第二富媒体消息小程序的信息直接作为第四验证结果，或者，第一小程序管理平台在本地对比第一富媒体消息小程序的信息和第二富媒体消息小程序的信息，并根据比对结果确定第一富媒体消息小程序的验证结果，示例的，如果对比结果均相同，则第一小程序管理平台确认验证结果为第一验证结果，如果对比结果均不相同，则第一小程序管理平台确认验证结果为第二验证结果，如果对比结果一部分相同，一部分不相同，则第一小程序管理平台确认验证结果为第三验证结果。
方式三：第一请求消息可以请求验证第一富媒体消息小程序的安全性，第一小程序管理平台基于第一信息获取第一富媒体消息小程序本身，并在本地对第一富媒体消息小程序进行安全扫描，并根据扫描结果确定第一富媒体消息小程序的验证结果。
可以理解，如果第一信息中包括第一富媒体消息小程序的信息，且第一富媒体消息小程序的信息中包含第一富媒体消息小程序的下载地址，则第一小程序管理平台根据该下载地址将第一富媒体消息小程序下载到本地。如果第一信息中包括第一富媒体消息小程序，则第一小程序管理平台从存储第一信息的存储单元中获取第一富媒体消息小程序。
示例的，如果第一富媒体消息小程序扫描结果正常，则第一小程序管理平台确认验证结果为第一验证结果，否则，第一小程序管理平台确认验证结果为第二验证结果或第三验证结果。
可选地，第一小程序管理平台可以将对第一富媒体消息小程序的验证结果保存在本地，以便后续其他富媒体消息终端向第一小程序管理平台请求验证第一富媒体消息小程序时，第一小程序管理平台可以直接基于本地保存的信息返回验证结果。
S550，第一小程序管理平台向富媒体消息终端发送第一响应消息，第一响应消息包括第一小程序管理平台对第一富媒体消息小程序的验证结果。对应的，富媒体消息终端接收来自第一小程序管理平台的第一响应消息。
S560，富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作。
示例的，如果第一富媒体消息小程序的验证结果为第一验证结果或第四验证结果，则富媒体消息终端可以运行相应的富媒体消息小程序。具体的，当验证结果为第一验证结果，富媒体消息终端运行第一富媒体消息小程序，当验证结果为第四验证结果，富媒体消息终端运行第四验证结果中包括的富媒体消息小程序或根据第四验证结果中的富媒体消息小程序的信息获取的富媒体消息小程序。
可选地，如果第一富媒体消息小程序的验证结果为第一验证结果，当富媒体消息终端运行第一富媒体消息小程序时，还可以向第一富媒体消息小程序提供用户信息，该用户信息为与富媒体消息终端对应的用户有关的信息，用于指示第一富媒体消息小程序的使用者。第一富媒体消息小程序对应的服务器基于该用户信息为该用户提供服务。
具体地，向第一富媒体消息小程序提供用户信息的作用是，基于富媒体消息的安全性及对运营商的信任，第一富媒体消息小程序默认富媒体消息终端提供的用户信息是安全的，可以将该用户信息提供给第一富媒体消息小程序对应的服务设备，当富媒体消息小程序服务器(即第一富媒体消息小程序对应的服务端设备)后，富媒体消息小程序服务器可以基于该用户信息免于认证第一富媒体消息小程序的使用者，例如，不用发起对第一富媒体消息小程序使用者的认证流程，这样用户不用再执行输入账号/密码的认证过程，即可直接使用富媒体消息小程序服务(如银行卡余额查询)；示例性地，用户信息包含用户标识和第一小程序管理平台对用户标识的签名，富媒体消息小程序服务器验证签名通过后，确认对第一富媒体消息小程序的使用者免认证；示例性地，用户信息还可以包含第一平台提供的token(令牌)，服务器通过第一小程序管理平台或相应的验证中心验证token通过后，确认对第一富媒体消息小程序的使用者免认证。如此，换句话说，富媒体消息终端向第一富媒体消息小程序提供用户信息，等于向第一富媒体消息小程序提供了安全凭证信息。
示例的，用户信息包含用户标识可以为无线通信系统中网络运营商为用户使用的手机卡分配的一个唯一的标识符。例如，该唯一的标识符为国际移动用户识别码(International Mobile Subscriber Identity，IMSI)，或用户永久标识(Subscription Permanent Identifier，SUPI)。或者，该用户信息也可以为一般公共订阅标识符(Generic Public Subscription Identifier，GPSI)。
可选地，如果第一富媒体消息小程序的验证结果为第四验证结果，当富媒体消息终端运行第四验证结果中包括的运行第四验证结果中包括的富媒体消息小程序或根据第四验证结果中的富媒体消息小程序的信息获取的富媒体消息小程序时，也可以向第二富媒体消息小程序提供用户信息，该用户信息为与富媒体消息终端对应的用户有关的信息，用于指示与第四验证结果相关的富媒体消息小程序的使用者。可以理解，基于富媒体消息的安全性及对运营商的信任，第二富媒体消息小程序默认富媒体消息终端提供的用户信息是安全的，可以将该用户信息提供与第四验证结果相关的富媒体消息小程序对应的服务器，第二富媒体消息小程序对应的服务器基于该用户信息为该用户提供服务。与上文中富媒体消息终端向第一富媒体消息小程序提供用户信息的作用一样，这里不再赘述。
举例说明富媒体消息终端如何向第一富媒体消息小程序提供富媒体消息终端对应的用户信息。例如，富媒体消息终端在打开小程序的时候可以携带富媒体消息终端对应的用户信息(例如在小程序入口函数中传递用户标识或者其他验证参数)，或者，富媒体消息终端在打开小程序时向富媒体消息小程序注册回调函数，后续富媒体消息小程序使用该回调函数从富媒体消息终端获取富媒体消息终端对应的用户信息，富媒体消息小程序给小程序服务侧提供该安全用户信息，小程序服务侧给富媒体消息终端用户提供服务时无需再次执行对该富媒体消息终端用户的验证操作(即用户免认证)。
示例的，第一富媒体消息小程序的验证结果为第二验证结果或第三验证结果，则富媒体消息终端显示第一富媒体消息小程序和验证结果，以用于向富媒体消息终端对应的用户进行验证结果提示(如安全性提示)，用户确认验证结果提示后，根据与用户的交互结果确定是否运行第一富媒体消息小程序，或者，第一富媒体消息小程序的验证结果为第二验证结果或第三验证结果，富媒体消息终端根据在本地预设的安全设置(例如，用户预先设置允许富媒体消息终端下载或运行验证结果为第二验证结果或第三验证结果的富媒体消息小程序)，确定是否运行第一富媒体消息小程序。例如，第一富媒体消息小程序的验证结果为第二验证结果，则富媒体消息终端显示第一富媒体消息小程序和验证结果，用户确认验证结果提示后，不运行第一富媒体消息小程序，或者，运行但不向第一富媒体消息小程序上传富媒体消息终端的用户信息(即关闭免认证)。
上文结合图5详细介绍了富媒体消息终端验证富媒体消息小程序可用性的具体流程，该方法可通过如图4所示的架构实现。基于上述实施例，富媒体消息终端可以获取第一富媒体消息小程序的信息、确定是否待向第二小程序管理平台请求验证第一富媒体消息小程序的可用性、与富媒体消息小程序管理平台交互验证第一富媒体消息小程序的可用性、根据验证结果运行第一富媒体消息小程序、以及基于验证结果向第一富媒体消息小程序传递用户信息。这样，使得富媒体消息终端可以能够在确保第一富媒体消息小程序可以运行的前提下，下载并运行小程序，避免给用户因打开未知安全性的小程序所带来风险和损失。同时，还可以基于安全验证结果可以提供用户信息，用于用户免认证使用第一富媒体消息小程序的服务，在确保可以运行第一富媒体消息小程序的前提下，同时方便用户使用第一富媒体消息小程序。
可以理解，上述图5中各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还可以理解，在本申请的各实施例中涉及到一些消息名称，其命名不对本申请实施例的保护范围造成限定。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，上述各个方法实施例中，由设备实现的方法和操作，也可以由可由设备的组成部件(例如芯片或者电路)来实现，不作限定。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图8是本申请实施例提供的一种通信装置1100的示意图。该装置1100包括收发单元1110和处理单元1120。收发单元1110可以用于实现相应的通信功能。收发单元1110还可以称为通信接口或通信单元。处理单元1120可以用于进行处理操作，如生成查询消息、运行富媒体消息小程序等。
可选地，该装置1100还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1120可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中核心网设备或用户设备的动作。
在第一种设计中，该装置1100可以是前述实施例中的富媒体消息终端(如图5、图6、图7中的富媒体消息终端)，也可以是富媒体消息终端的组成部件(如芯片)。该装置1100可实现对应于上文方法实施例中的富媒体消息终端执行的步骤或者流程。其中，收发单元1110可用于执行上文方法实施例中富媒体消息终端的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1110可用于执行图5中的S520中向第一小程序管理平台发送第一请求消息的操作、S550中接收来自第一小程序管理平台的第一响应消息的操作，还可以用于执行图6中的步骤1中向富媒体消息中心发送第一查询请求消息的操作、步骤5中接收来自富媒体消息中心的第一查询响应消息的操作，还可以用于执行图7中的富媒体消息终端发送和/或接收数据或消息的操作。处理单元1120可用于执行上文方法实施例中富媒体消息终端的数据和/或信息处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1120可用于执行图5中的S530和S560的操作，还可以用于执行图6中的步骤6的操作，还可以用于执行图7中的步骤4的操作。
一种可能的实现方式，收发单元1100，用于获取第一信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序；收发单元1100，还用于向第一小程序管理平台发送第一请求消息，其中，第一请求消息包括第一信息的部分信息或全部信息，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序，第一小程序管理平台为能够提供富媒体消息小程序验证功能的管理平台；收发单元1100，还用于接收来自第一小程序管理平台的第一响应消息，第一响应消息包括第一小程序管理平台对第一富媒体消息小程序的验证结果，处理单元1120，用于富媒体消息终端根据验证结果针对第一富媒体消息小程序执行相应操作。
可选地，处理单元1120，还用于基于第一信息确定待向第一小程序管理平台请求验证第一富媒体消息小程序。
示例的，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序的安全性，或者，第一请求消息用于请求第一小程序管理平台验证是否允许富媒体消息终端运行第一富媒体消息小程序。
可选地，收发单元1100，还用于获取第二信息，第二信息包括富媒体消息小程序的安全源信息和/或用于验证第一富媒体消息小程序的签名的公钥，或者，第二信息包括验证策略，验证策略指示待向第一小程序平台请求验证第一富媒体消息小程序；处理单元1120，还用于根据第一信息和第二信息判断确定待向第一小程序管理平台请求验证第一富媒体消息小程序。
可选地，当第一信息的发送方标识未包含在安全源信息中时，处理单元1120，还用于确定待向第一小程序平台请求验证第一富媒体消息小程序；或者，当使用公钥验证第一富媒体消息小程序的信息中的签名失败时，处理单元1120，还用于确定待向第一小程序平台请求验证第一富媒体消息小程序；或者，当验证策略指向第一小程序平台请求验证第一富媒体消息小程序时，处理单元1120，还用于确定待向第一小程序平台请求验证第一富媒体消息小程序。
示例的，第一富媒体消息小程序的信息包括以下至少一项：第一富媒体消息小程序的下载地址、第一富媒体消息小程序的标识、第一富媒体消息小程序的名称、第一富媒体消息小程序的图标的地址、第一富媒体消息小程序的版本、第一富媒体消息小程序的开发者信息、第一富媒体消息小程序的提供商信息、第一富媒体消息小程序的开发者的签名信息、第一富媒体消息小程序的提供商的签名信息。
可选地，收发单元1100，还用于富媒体终端从第二小程序管理平台获取第一信息，或者，富媒体终端从第二小程序管理平台之外的管理平台获取第一信息，或者，富媒体终端从富媒体消息终端之外的富媒体消息设备获取第一信息。
可选地，收发单元1100，还用于获取第二小程序管理平台对应的统一资源定位符URL；收发单元1100，还用于获取URL对应的web页面，web页面包括第一信息和/或小程序查询入口，小程序查询入口用于获取第一信息。
可选地，收发单元1100，还用于接收第一富媒体消息，第一富媒体消息包括第一信息。
示例的，验证结果包括以下一项：第一验证结果、第二验证结果、第三验证结果、第四验证结果，其中，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证，第四验证结果为第一小程序管理平台根据第一请求消息查询得到的保存在本地的富媒体消息小程序的信息和/或富媒体消息小程序。
可选地，验证结果为第一验证结果或者第四验证结果，处理单元1120用于根据用户指示或本地安全设置，确定运行第一富媒体消息小程序；或者，处理单元1120用于根据用户指示或本地安全设置，确定拒绝运行第一富媒体消息小程序。
可选地，验证结果为第一验证结果或者第四验证结果，收发单元1110还用于向第一富媒体消息小程序提供用户信息，该用户信息为与富媒体消息终端对应的用户有关的信息，用于指示第一富媒体消息小程序的使用者。
在第二种设计中，该装置1100可以是前述实施例中的第一小程序管理平台，也可以是第一小程序管理平台的组成部件(如芯片)。该装置1100可实现对应于上文方法实施 例中的第一小程序管理平台执行的步骤或者流程。其中，收发单元1110可用于执行上文方法实施例中第一小程序管理平台的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1110可用于执行图5中的S520中接收来自富媒体消息终端的第一请求消息的操作、S550中向富媒体消息终端发送第一响应消息的操作。处理单元1120可用于执行上文方法实施例中第一小程序管理平台的处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1120可用于执行图5中的步骤540的操作。
一种可能的实现方式，收发单元1110，用于接收来自富媒体消息终端的第一请求消息，其中，第一请求消息包括第一信息的部分信息或全部信息，第一信息包括第一富媒体消息小程序的信息和/或第一富媒体消息小程序，第一请求消息用于请求第一小程序管理平台对第一富媒体消息小程序进行验证，第一小程序管理平台为能够提供富媒体消息小程序验证的小程序管理平台；处理单元1120，用于根据第一请求消息对第一富媒体消息小程序进行验证，得到验证结果；收发单元1110，还用于向富媒体消息终端发送第一响应消息，第一响应消息包含验证结果。
示例的，第一请求消息用于请求第一小程序管理平台验证第一富媒体消息小程序的安全性，或者，第一请求消息用于请求第一小程序管理平台验证是否允许富媒体消息终端运行第一富媒体消息小程序。
示例的，第一富媒体消息小程序的信息包括以下至少一项：第一富媒体消息小程序的下载地址、第一富媒体消息小程序的标识、第一富媒体消息小程序的名称、第一富媒体消息小程序的版本、第一富媒体消息小程序的开发者信息、第一富媒体消息小程序的提供商信息、第一富媒体消息小程序的开发者的签名信息、第一富媒体消息小程序的提供商的签名信息。
可选地，处理单元1120，还用于根据第一请求消息查询第一小程序管理平台本地保存的富媒体消息小程序的信息；处理单元1120，还用于根据查询结果得到验证结果。
示例的，若第一小程序管理平台根据第一请求消息能够查询到第一小程序管理平台本地保存的富媒体消息小程序的信息，验证结果包含第四验证结果，第四验证结果为本地保存的富媒体消息小程序的信息和/或富媒体消息小程序，或者，若第一小程序管理平台根据第一请求消息能够查询到第一小程序管理平台本地保存的富媒体消息小程序的信息，比较本地保存的富媒体消息小程序的信息与第一请求消息得到验证结果，验证结果包含第一验证结果或第二验证结果或第三验证结果，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证。
可选地，收发单元1110，还用于获取第三信息，第三信息包括富媒体消息终端对应的签约信息和/或配置信息；处理单元1120，还用于根据第一请求消息和第三信息得到验证结果。
可选地，收发单元1110，还用于根据第一请求消息获取第一富媒体消息小程序；处理单元1120，还用于对获取的第一富媒体消息小程序进行安全扫描；处理单元1120，还用于根据扫描结果得到验证结果。
示例的，验证结果包含第一验证结果或第二验证结果或第三验证结果，第一验证结果指示第一富媒体消息小程序通过验证，第二验证结果指示第一富媒体消息小程序未通过验证，第三验证结果指示第一富媒体消息小程序部分通过验证。
可以理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还可以理解，这里的装置1100以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置1100可以具体为上述实施例中的富媒体消息终端(如图5、图6、图7中的富媒体消息终端)，可以用于执行上述各方法实施例中与富媒体消息终端对应的各个流程和/或步骤，例如，图5中的S510-S530、S550-S560，图6中的步骤1、步骤5-步骤6，图7中的步骤1-步骤4。或者，装置1100可以具体为上述实施例中的第二小程序管理平台，可以用于执行上述各方法实施例中与第二小程序管理平台对应的各个流程和/或步骤，例如，图5中的S530-S550。为避免重复，在此不再赘述。
上述各个方案的装置1100具有实现上述方法中富媒体消息终端(如图5、图6、图7中的富媒体消息终端)所执行的相应步骤的功能，或者，上述各个方案的装置1100具有实现上述方法中第二小程序管理平台所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元1110还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图8中的装置可以是前述实施例中的设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图9是本申请实施例提供另一种通信装置1200的示意图。该装置1200包括处理器1210，处理器1210用于执行存储器1220存储的计算机程序或指令，或读取存储器1220存储的数据，以执行上文各方法实施例中的方法。可选地，处理器1210为一个或多个。
可选地，如图9所示，该装置1200还包括存储器1220，存储器1220用于存储计算机程序或指令和/或数据。该存储器1220可以与处理器1210集成在一起，或者也可以分离设置。可选地，存储器1220为一个或多个。
可选地，如图9所示，该装置1200还包括收发器1230，收发器1230用于信号的接收和/或发送。例如，处理器1210用于控制收发器1230进行信号的接收和/或发送。
作为一种方案，该装置1200用于实现上文各个方法实施例中由富媒体消息终端(如图5、图6、图7中的富媒体消息终端)执行的操作。
作为另一种方案，该装置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或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还可以理解的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由富媒体消息终端(如图5、图6、图7中的富媒体消息终端)执行的方法的计算机指令。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由第一小程序管理平台执行的方法的计算机指令。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由富媒体消息终端(如图5、图6、图7中的富媒体消息终端)执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由第一小程序管理平台执行的方法。
本申请实施例还提供一种通信系统，包括前述的富媒体消息终端(如图5、图6、图7中的富媒体消息终端)、第一小程序管理平台、第二小程序管理平台中的至少一项。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的 相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    富媒体消息终端获取第一信息，所述第一信息包括第一富媒体消息小程序的信息和/或所述第一富媒体消息小程序；
    所述富媒体消息终端向第一小程序管理平台发送第一请求消息，其中，所述第一请求消息包括所述第一信息的部分信息或全部信息，所述第一请求消息用于请求所述第一小程序管理平台对所述第一富媒体消息小程序进行验证，所述第一小程序管理平台为能够提供富媒体消息小程序验证功能的管理平台；
    所述富媒体消息终端接收来自所述第一小程序管理平台的第一响应消息，所述第一响应消息包括所述第一小程序管理平台对所述第一富媒体消息小程序的验证结果；
    所述富媒体消息终端根据所述验证结果针对所述第一富媒体消息小程序执行相应操作。
  2. 根据权利要求1所述的方法，其特征在于，所述第一请求消息用于请求所述第一小程序管理平台验证所述第一富媒体消息小程序的安全性，或者，所述第一请求消息用于请求所述第一小程序管理平台验证是否允许所述富媒体消息终端运行所述第一富媒体消息小程序。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述富媒体消息终端基于所述第一信息确定待向所述第一小程序管理平台请求验证所述第一富媒体消息小程序。
  4. 根据权利要求3所述的方法，其特征在于，所述富媒体消息终端根据所述第一信息确定待向所述第一小程序管理平台请求验证所述第一富媒体消息小程序，包括：
    所述富媒体消息终端获取第二信息，所述第二信息包括所述富媒体消息小程序的安全源信息和/或用于验证所述第一富媒体消息小程序的签名的公钥，或者，所述第二信息包括验证策略，所述验证策略指示需要向所述第一小程序平台请求验证所述第一富媒体消息小程序；
    所述富媒体消息终端根据所述第一信息和所述第二信息确定待向所述第一小程序管理平台请求验证所述第一富媒体消息小程序。
  5. 根据权利要求4所述的方法，其特征在于，所述富媒体消息终端根据第一信息和所述第二信息确定待向所述第一小程序管理平台请求验证所述第一富媒体消息小程序，包括：
    当所述第一信息的发送方标识未包含在所述安全源信息中时，所述富媒体消息终端确定待向所述第一小程序平台请求验证所述第一富媒体消息小程序；
    或者，
    当使用所述公钥验证所述第一富媒体消息小程序的信息中的签名失败时，所述富媒体消息终端确定待向所述第一小程序平台请求验证所述第一富媒体消息小程序；
    或者，
    当所述验证策略指示向所述第一小程序平台请求验证所述第一富媒体消息小程序时，所述富媒体消息终端确定待向所述第一小程序平台请求验证所述第一富媒体消息小程序。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一富媒体消息小程序的信息包括以下至少一项：
    所述第一富媒体消息小程序的下载地址、所述第一富媒体消息小程序的标识、所述第一富媒体消息小程序的名称、所述第一富媒体消息小程序的图标的地址、所述第一富媒体消息小程序的版本、所述第一富媒体消息小程序的开发者信息、所述第一富媒体消息小程序的提供商信息、所述第一富媒体消息小程序的开发者的签名信息、所述第一富媒体消息小程序的提供商的签名信息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述富媒体消息终端获取第一信息，包括：
    所述富媒体终端从第二小程序管理平台获取所述第一信息，或者，
    所述富媒体终端从所述第二小程序管理平台之外的管理平台获取所述第一信息，或者，
    所述富媒体消息终端从所述富媒体消息终端之外的富媒体消息设备获取所述第一信息。
  8. 根据权利要求7所述的方法，其特征在于，所述富媒体消息终端从第二小程序管理平台获取所述第一信息，包括：
    所述富媒体消息终端获取所述第二小程序管理平台对应的统一资源定位符URL；
    所述富媒体消息终端获取所述URL对应的网页页面，所述网页页面包括所述第一信息和/或小程序查询入口，所述小程序查询入口用于获取所述第一信息。
  9. 根据权利要求1至7中任一项所述的方法，其特征在于，所述富媒体消息终端获取第一信息，包括：
    所述富媒体消息终端接收第一富媒体消息，所述第一富媒体消息包括所述第一信息。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述验证结果包括以下一项：
    第一验证结果、第二验证结果、第三验证结果、第四验证结果，其中，所述第一验证结果指示所述第一富媒体消息小程序通过验证，所述第二验证结果指示所述第一富媒体消息小程序未通过验证，所述第三验证结果指示所述第一富媒体消息小程序部分通过验证，所述第四验证结果为所述第一小程序管理平台根据所述第一请求消息查询得到的保存在本地的富媒体消息小程序的信息和/或富媒体消息小程序。
  11. 根据权利要求10所述的方法，其特征在于，
    所述验证结果为所述第一验证结果或者所述第四验证结果，所述富媒体消息终端根据所述验证结果针对所述第一富媒体消息小程序执行相应操作，包括：所述富媒体消息终端根据所述验证结果运行所述第一富媒体消息小程序；
    或，
    所述验证结果为所述第二验证结果或者所述第三验证结果，所述富媒体消息终端根据所述验证结果针对所述第一富媒体消息小程序执行相应操作，包括：所述富媒体消息终端根据用户指示或本地安全设置，确定运行所述第一富媒体消息小程序；或者，所述富媒体消息终端根据用户指示或本地安全设置，确定拒绝运行所述第一富媒体消息小程序。
  12. 根据权利要求10或11所述的方法，其特征在于，所述验证结果为所述第一验证结果或者所述第四验证结果，所述富媒体消息终端根据所述验证结果针对所述第一富媒体 消息小程序执行相应操作，包括：
    所述富媒体消息终端向所述第一富媒体消息小程序提供用户信息，所述用户信息为与所述富媒体消息终端对应的用户有关的信息，用于指示所述第一富媒体消息小程序的使用者。
  13. 一种通信方法，其特征在于，包括：
    第一小程序管理平台接收来自富媒体消息终端的第一请求消息，其中，所述第一请求消息包括第一信息的部分信息或全部信息，所述第一信息包括第一富媒体消息小程序的信息和/或所述第一富媒体消息小程序，所述第一请求消息用于请求所述第一小程序管理平台对所述第一富媒体消息小程序进行验证，所述第一小程序管理平台为能够提供富媒体消息小程序验证功能的管理平台；
    所述第一小程序管理平台根据所述第一请求消息对所述第一富媒体消息小程序进行验证，得到验证结果；
    所述第一小程序管理平台向所述富媒体消息终端发送第一响应消息，所述第一响应消息包含所述验证结果。
  14. 根据权利要求13所述的方法，其特征在于，所述第一请求消息用于请求所述第一小程序管理平台验证所述第一富媒体消息小程序的安全性，或者，所述第一请求消息用于请求所述第一小程序管理平台验证是否允许所述富媒体消息终端运行所述第一富媒体消息小程序。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一富媒体消息小程序的信息包括以下至少一项：
    所述第一富媒体消息小程序的下载地址、所述第一富媒体消息小程序的标识、所述第一富媒体消息小程序的名称、所述第一富媒体消息小程序的版本、所述第一富媒体消息小程序的开发者信息、所述第一富媒体消息小程序的提供商信息、所述第一富媒体消息小程序的开发者的签名信息、所述第一富媒体消息小程序的提供商的签名信息。
  16. 根据权利要求13至15中任一项所述的方法，其特征在于，所述第一小程序管理平台根据所述第一请求消息对所述第一富媒体消息小程序进行验证，得到验证结果，包括：
    所述第一小程序管理平台根据所述第一请求消息查询所述第一小程序管理平台本地保存的富媒体消息小程序的信息；
    所述第一小程序管理平台根据查询结果确定所述验证结果。
  17. 根据权利要求16所述的方法，其特征在于，
    若所述第一小程序管理平台根据所述第一请求消息能够查询到所述第一小程序管理平台本地保存的富媒体消息小程序的信息，所述验证结果包含第四验证结果，所述第四验证结果为所述本地保存的富媒体消息小程序的信息和/或富媒体消息小程序，
    或者，
    若所述第一小程序管理平台根据所述第一请求消息能够查询到所述第一小程序管理平台本地保存的富媒体消息小程序的信息，比较所述本地保存的富媒体消息小程序的信息与所述第一请求消息得到验证结果，所述验证结果包含第一验证结果或第二验证结果或第三验证结果，所述第一验证结果指示所述第一富媒体消息小程序通过验证，所述第二验证结果指示所述第一富媒体消息小程序未通过验证，所述第三验证结果指示所述第一富媒体消息小程序部分通过验证。
  18. 根据权利要求13至15中任一项所述的方法，其特征在于，所述第一小程序管理平台根据所述第一请求消息对所述第一富媒体消息小程序进行验证，得到验证结果，包括：
    所述第一小程序管理平台获取第三信息，所述第三信息包括所述富媒体消息终端对应的签约信息和/或配置信息；
    所述第一小程序管理平台根据所述第一请求消息和所述第三信息确定所述验证结果。
  19. 根据权利要求13至15中任一项所述的方法，其特征在于，所述第一小程序管理平台根据所述第一请求消息对所述第一富媒体消息小程序进行验证，得到验证结果，包括：
    所述第一小程序管理平台根据所述第一请求消息获取所述第一富媒体消息小程序；
    所述第一小程序管理平台对获取的所述第一富媒体消息小程序进行安全扫描；
    所述第一小程序管理平台根据扫描结果确定所述验证结果。
  20. 根据权利要求13至15、18、19中任一项所述的方法，其特征在于，所述验证结果包含第一验证结果或第二验证结果或第三验证结果，所述第一验证结果指示所述第一富媒体消息小程序通过验证，所述第二验证结果指示所述第一富媒体消息小程序未通过验证，所述第三验证结果指示所述第一富媒体消息小程序部分通过验证。
  21. 一种通信方法，其特征在于，包括：
    富媒体消息终端获取第一信息，所述第一信息包括第一富媒体消息小程序的信息和/或所述第一富媒体消息小程序；
    所述富媒体消息终端向第一小程序管理平台发送第一请求消息，其中，所述第一请求消息包括所述第一信息的部分信息或全部信息，所述第一请求消息用于请求所述第一小程序管理平台对所述第一富媒体消息小程序进行验证，所述第一小程序管理平台为能够提供富媒体消息小程序验证功能的管理平台；
    所述第一小程序管理平台接收所述第一请求消息，并根据所述第一请求消息对所述第一富媒体消息小程序进行验证，得到验证结果，以及向所述富媒体消息终端发送第一响应消息，所述第一响应消息包含所述验证结果；
    所述富媒体消息终端接收所述第一响应消息，并根据所述验证结果针对所述第一富媒体消息小程序执行相应操作。
  22. 根据权利要求21所述的方法，其特征在于，所述第一请求消息用于请求所述第一小程序管理平台验证所述第一富媒体消息小程序的安全性，或者，所述第一请求消息用于请求所述第一小程序管理平台验证是否允许所述富媒体消息终端运行所述第一富媒体消息小程序。
  23. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    所述富媒体消息终端基于所述第一信息确定待向所述第一小程序管理平台请求验证所述第一富媒体消息小程序。
  24. 根据权利要求21至23中任一项所述的方法，其特征在于，所述验证结果包括以下一项：
    第一验证结果、第二验证结果、第三验证结果、第四验证结果，其中，所述第一验证结果指示所述第一富媒体消息小程序通过验证，所述第二验证结果指示所述第一富媒体消息小程序未通过验证，所述第三验证结果指示所述第一富媒体消息小程序部分通过验证，所述第四验证结果为所述第一小程序管理平台提供的对应于所述第一请求消息的所述第一富媒体消息小程序的信息和/或所述第一富媒体消息小程序。
  25. 根据权利要求1至24中任一项所述的方法，其特征在于，所述第一请求消息和所述第一请求响应消息为富媒体消息。
  26. 一种通信装置，其特征在于，包括执行如权利要求1至20中任一项所述方法的单元或模块。
  27. 一种通信装置，其特征在于，包括至少一个处理器，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至11中任一项所述的方法；或者，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求12至20中任一项所述的方法。
  28. 一种通信系统，其特征在于，包括富媒体消息终端和第一小程序管理平台，
    其中，所述富媒体消息终端用于执行如权利要求1至12中任一项所述的方法，所述第一小程序管理平台用于执行如权利要求13至20中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，包括计算机程序，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至12中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求13至20中任一项所述的方法。
  30. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码，其特征在于：
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求1至12中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求13至20中任一项所述的方法。
PCT/CN2023/088429 2022-06-15 2023-04-14 通信方法、装置以及系统 WO2023241198A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210682078.0A CN117278514A (zh) 2022-06-15 2022-06-15 通信方法、装置以及系统
CN202210682078.0 2022-06-15

Publications (1)

Publication Number Publication Date
WO2023241198A1 true WO2023241198A1 (zh) 2023-12-21

Family

ID=89192149

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088429 WO2023241198A1 (zh) 2022-06-15 2023-04-14 通信方法、装置以及系统

Country Status (2)

Country Link
CN (1) CN117278514A (zh)
WO (1) WO2023241198A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190080079A1 (en) * 2016-11-10 2019-03-14 Boe Technology Group Co., Ltd Method and device for verifying security of application
CN111597113A (zh) * 2020-05-18 2020-08-28 北京百度网讯科技有限公司 小程序的验证方法、装置、设备及存储介质
CN111597114A (zh) * 2020-05-18 2020-08-28 北京百度网讯科技有限公司 小程序的验证方法、装置、设备及存储介质
CN113342639A (zh) * 2021-05-19 2021-09-03 国家计算机网络与信息安全管理中心 小程序安全风险评估方法和电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190080079A1 (en) * 2016-11-10 2019-03-14 Boe Technology Group Co., Ltd Method and device for verifying security of application
CN111597113A (zh) * 2020-05-18 2020-08-28 北京百度网讯科技有限公司 小程序的验证方法、装置、设备及存储介质
CN111597114A (zh) * 2020-05-18 2020-08-28 北京百度网讯科技有限公司 小程序的验证方法、装置、设备及存储介质
CN113342639A (zh) * 2021-05-19 2021-09-03 国家计算机网络与信息安全管理中心 小程序安全风险评估方法和电子设备

Also Published As

Publication number Publication date
CN117278514A (zh) 2023-12-22

Similar Documents

Publication Publication Date Title
US8584231B2 (en) Service opening method and system, and service opening server
KR102154384B1 (ko) 포털 인증
US9154955B1 (en) Authenticated delivery of premium communication services to trusted devices over an untrusted network
US9300663B2 (en) Communication session transfer between devices
US8201232B2 (en) Authentication, identity, and service management for computing and communication systems
US8646057B2 (en) Authentication and authorization of user and access to network resources using openid
US9258344B2 (en) Multi-hop single sign-on (SSO) for identity provider (IdP) roaming/proxy
JP4673364B2 (ja) エンティティの第１のｉｄおよび第２のｉｄの検証方法
WO2016188256A1 (zh) 一种应用接入鉴权的方法、系统、装置及终端
US8923820B2 (en) Modified messaging server call flow for secured mobile-to-mobile messaging
US20170126878A1 (en) Method and apparatus of providing messaging service and callback feature to mobile stations
US11564094B1 (en) Secondary device authentication proxied from authenticated primary device
US20130227646A1 (en) Methods and apparatus for large scale distribution of electronic access clients
WO2019196699A1 (zh) 一种获取安全策略的方法及设备
US11658963B2 (en) Cooperative communication validation
JP2010506464A (ja) 複数の装置間で携帯電話アカウントの加入契約情報を共有するための方法及び装置
US11678176B1 (en) Electronic subscriber identity module (eSIM) transfer via activation code
US11570620B2 (en) Network profile anti-spoofing on wireless gateways
WO2017041562A1 (zh) 一种识别终端设备用户身份的方法和装置
EP3541106A1 (en) Methods and apparatus for euicc certificate management
US9154949B1 (en) Authenticated delivery of premium communication services to untrusted devices over an untrusted network
WO2023241198A1 (zh) 通信方法、装置以及系统
US20160044028A1 (en) Message authentication
CN112000493B (zh) 一种数据处理系统、方法及电子设备和存储介质
WO2021136511A1 (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: 23822769

Country of ref document: EP

Kind code of ref document: A1