Message processing and cloud phone login authentication method and device, electronic equipment and medium

Abstract

The present disclosure relates to a message processing and cloud mobile phone login authentication method and device, electronic equipment and medium, and belongs to the technical field of communication. The message processing method comprises the following steps: receiving a message synchronization request sent by a 5G message center, wherein the message synchronization request comprises a message to be received and a destination number; obtaining cached authentication information, wherein the authentication information comprises a message session authentication identifier corresponding to a user number of a registered user; determining that a user corresponding to the destination number is a registered user and the user corresponding to the destination number is in an online state according to the user number of the registered user; if so, sending the message to be received to a cloud mobile phone platform message client arranged in a cloud mobile phone platform, so that the cloud mobile phone platform message client displays the message to be received, and sending the message to be received to a cloud mobile phone client of the user corresponding to the destination number for display.

Description

[0001] This application is a divisional application of the Chinese patent application No. 202310773548.9, titled "Message processing and cloud phone login authentication method and device, electronic equipment and medium", filed on June 27, 2023, with the Chinese Patent Office. TECHNICAL FIELD

[0002] The present disclosure relates to the technical field of communication, and in particular to a message processing and cloud phone login authentication method and device, electronic equipment and medium. BACKGROUND

[0003] A cloud phone is a specific implementation mode of a virtualization technology, which finally provides a user with an operating system in the cloud. At present, the cloud phone realizes the cloud-side mobile phone function, and the focus is on the realization of general mobile phone application computing, storage and data layer cloud, but the message function in the communication field is limited or even missing due to the dependence and limitation of the cloud phone and the local phone permission. SUMMARY

[0004] The present disclosure provides a message processing and cloud phone login authentication method, device, electronic equipment and medium to at least solve the problem of limited or missing message function in the related art.

[0005] The technical solution of the present disclosure is as follows:

[0006] According to a first aspect of the embodiments of the present disclosure, a message processing method is provided, comprising: receiving a message sending request sent by a cloud phone platform message client arranged in a cloud phone platform, wherein the message sending request comprises a message to be sent, a message session authentication identifier of an online user and a destination number of the message to be sent; obtaining cached authentication information, wherein the authentication information comprises a message session authentication identifier corresponding to a user number of a registered user; performing a first check on the received message session authentication identifier according to the message session authentication identifier corresponding to the user number of the registered user; and after the first check is passed, sending the message to be sent and the destination number to a fifth generation mobile communication technology (5G) message center to which the destination number belongs, so that the 5G message center sends the message to be sent to a mobile terminal or a message platform corresponding to the destination number.

[0007] According to a second aspect of the embodiments of the present disclosure, a message processing method is provided, including: receiving a message synchronization request sent by a 5G message center, the message synchronization request including a message to be received and a destination number; obtaining cached authentication information, the authentication information including a message session authentication identifier corresponding to a user number of a registered user; determining that a user corresponding to the destination number is a registered user and the user corresponding to the destination number is in an online state according to the user number of the registered user, and then sending the message to be received to a cloud phone platform message client arranged in a cloud phone platform, so that the cloud phone platform message client displays the message to be received and sends the message to be received to a cloud phone client of the user corresponding to the destination number for display.

[0008] According to a third aspect of the embodiments of the present disclosure, a cloud phone login authentication method is provided, including: receiving a single sign-on authentication request sent by a cloud phone platform message client arranged in a cloud phone platform, the single sign-on authentication request including a 5G message single sign-on token, the 5G message single sign-on token being sent by a cloud phone client to the cloud phone platform message client through the cloud phone platform; sending the single sign-on authentication request to the cloud phone platform; receiving a user number of a registered user corresponding to the 5G message single sign-on token sent by the cloud phone platform, the user number of the registered user corresponding to the 5G message single sign-on token being sent by the cloud phone platform after the 5G message single sign-on token received is authenticated successfully; generating a message session authentication identifier corresponding to the user number of the registered user, and caching the message session authentication identifier corresponding to the user number of the registered user as authentication information; and sending the message session authentication identifier corresponding to the user number of the registered user to the cloud phone platform message client for caching.

[0009] According to a fourth aspect of the embodiments of the present disclosure, a message processing method is provided, including: generating a message sending request, the message sending request including a message to be sent, a message session authentication identifier of an online user, and a destination number of the message to be sent; sending the message sending request to a 5G message cloud service platform, so that the 5G message cloud service platform performs a first check on the received message session authentication identifier according to a message session authentication identifier corresponding to a user number of a registered user in cached authentication information, and sends the message to be sent to a mobile terminal or a message platform corresponding to the destination number through a 5G message center to which the destination number belongs after the first check is passed.

[0010] According to a fifth aspect of the embodiments of the present disclosure, a message processing method is provided, including: receiving a message to be received sent by a 5G message cloud service platform, the message to be received being sent by the 5G message cloud service platform after receiving a message synchronization request sent by a 5G message center, determining that a user corresponding to a destination number is a registered user according to a user number of the registered user in cached authentication information, and the user corresponding to the destination number being in an online state, the message synchronization request including the message to be received and the destination number; displaying the message to be received; and sending the message to be received to a cloud mobile phone client of the user corresponding to the destination number for display.

[0011] According to a sixth aspect of the embodiments of the present disclosure, a cloud mobile phone login authentication method is provided, including: receiving a 5G message single sign-on token sent by a cloud mobile phone client, the 5G message single sign-on token being generated by a cloud mobile phone platform after the cloud mobile phone client logs in successfully, the 5G message single sign-on token corresponding to a user number of a currently logged-in registered user; sending a single sign-on authentication request to a 5G message cloud service platform, the single sign-on authentication request including the 5G message single sign-on token; receiving a message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G message cloud service platform, the message session authentication identifier corresponding to the user number of the currently logged-in registered user being generated by the 5G message cloud service platform after receiving the 5G message single sign-on token corresponding to the user number of the currently logged-in registered user sent by the cloud mobile phone platform according to the single sign-on authentication request; and caching the message session authentication identifier corresponding to the user number of the registered user.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a cloud mobile phone login authentication method is provided, including: receiving a single sign-on authentication request sent by a 5G message cloud service platform, the single sign-on authentication request including a 5G message single sign-on token; authenticating the 5G message single sign-on token; after the authentication is passed, sending a user number of a currently logged-in registered user corresponding to the 5G message single sign-on token to the 5G message cloud service platform, so that the 5G message cloud service platform generates a message session authentication identifier corresponding to the user number of the registered user, caches the message session authentication identifier corresponding to the user number of the registered user as authentication information, and sends the message session authentication identifier corresponding to the user number of the registered user to a cloud mobile phone platform message client for caching.

[0013] According to an eighth aspect of embodiments of the present disclosure, a message processing apparatus is provided, comprising: a first receiving module configured to receive a message sending request sent by a cloud phone platform message client arranged in a cloud phone platform, wherein the message sending request comprises a message to be sent, a message session authentication identifier of an online user, and a destination number of the message to be sent; a first obtaining module configured to obtain cached authentication information, wherein the authentication information comprises a message session authentication identifier corresponding to a user number of a registered user; a first checking module configured to perform a first check on the received message session authentication identifier according to the message session authentication identifier corresponding to the user number of the registered user; and a first sending module configured to, after the first check is passed, send the message to be sent and the destination number to a fifth generation mobile communication technology (5G) message center to which the destination number belongs, so that the 5G message center sends the message to be sent to a mobile phone terminal corresponding to the destination number or a message platform.

[0014] According to a ninth aspect of embodiments of the present disclosure, a message processing apparatus is provided, comprising: a second receiving module configured to receive a message synchronization request sent by a 5G message center, wherein the message synchronization request comprises a message to be received and a destination number; a second obtaining module configured to obtain cached authentication information, wherein the authentication information comprises a message session authentication identifier corresponding to a user number of a registered user; and a second sending module configured to, according to a determination that the user corresponding to the destination number is a registered user and the user corresponding to the destination number is in an online state, send the message to be received to a cloud phone platform message client arranged in a cloud phone platform, so that the cloud phone platform message client displays the message to be received and sends the message to be received to a cloud phone client of the user corresponding to the destination number for display.

[0015] According to a tenth aspect of the embodiments of the present disclosure, a cloud phone login authentication device is provided, which comprises: a third receiving module configured to receive a single sign-on authentication request sent by a cloud phone platform message client arranged in a cloud phone platform, wherein the single sign-on authentication request comprises a 5G message single sign-on token, and the 5G message single sign-on token is sent by the cloud phone platform to the cloud phone platform message client through a cloud phone client; a third sending module configured to send the single sign-on authentication request to the cloud phone platform; a fourth receiving module configured to receive a user number of a registered user corresponding to the 5G message single sign-on token sent by the cloud phone platform after the cloud phone platform authenticates the received 5G message single sign-on token successfully; a first generating module configured to generate a message session authentication identifier corresponding to the user number of the registered user, and cache the message session authentication identifier corresponding to the user number of the registered user as authentication information; and a fourth sending module configured to send the message session authentication identifier corresponding to the user number of the registered user to the cloud phone platform message client for caching.

[0016] According to an eleventh aspect of the embodiments of the present disclosure, a message processing device is provided, which comprises: a second generating module configured to generate a message sending request, wherein the message sending request comprises a to-be-sent message, a message session authentication identifier of an online user, and a destination number of the to-be-sent message; and a fifth sending module configured to send the message sending request to a 5G message cloud service platform, so that the 5G message cloud service platform performs a first check on the received message session authentication identifier according to a message session authentication identifier corresponding to a user number of a registered user in cached authentication information, and sends the to-be-sent message to a mobile terminal or a message platform corresponding to the destination number through a 5G message center to which the destination number belongs after the first check is passed.

[0017] According to a twelfth aspect of the embodiments of the present disclosure, a message processing device is provided, which comprises: a fifth receiving module configured to receive a to-be-received message sent by a 5G message cloud service platform, wherein the to-be-received message is sent by the 5G message cloud service platform after the 5G message cloud service platform receives a message synchronization request sent by a 5G message center, determines that a user corresponding to a destination number is a registered user according to a registered user's user number in cached authentication information, and determines that the user corresponding to the destination number is in an online state; the message synchronization request comprises the to-be-received message and the destination number; a first displaying module configured to display the to-be-received message; and a sixth sending module configured to send the to-be-received message to a cloud phone client of the user corresponding to the destination number for display.

[0018] According to a thirteenth aspect of embodiments of the present disclosure, a cloud phone login authentication apparatus is provided, comprising: a sixth receiving module configured to receive a 5G message single sign-on token sent by a cloud phone client, the 5G message single sign-on token being generated by a cloud phone platform after the cloud phone client logs in successfully, and the 5G message single sign-on token corresponding to a user number of a currently logged-in registered user; a seventh sending module configured to send a single sign-on authentication request to a 5G message cloud service platform, the single sign-on authentication request comprising the 5G message single sign-on token; a seventh receiving module configured to receive a message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G message cloud service platform, the message session authentication identifier corresponding to the user number of the currently logged-in registered user being generated by the 5G message cloud service platform after receiving the 5G message single sign-on token corresponding to the user number of the currently logged-in registered user sent by the cloud phone platform according to the single sign-on authentication request; and a caching module configured to cache the message session authentication identifier corresponding to the user number of the registered user.

[0019] According to a fourteenth aspect of embodiments of the present disclosure, a cloud phone login authentication apparatus is provided, comprising: an eighth receiving module configured to receive a single sign-on authentication request sent by a 5G message cloud service platform, the single sign-on authentication request comprising a 5G message single sign-on token; an authentication module configured to authenticate the 5G message single sign-on token; and an eighth sending module configured to, after the authentication is passed, send a user number of a currently logged-in registered user corresponding to the 5G message single sign-on token to the 5G message cloud service platform, so that the 5G message cloud service platform generates a message session authentication identifier corresponding to the user number of the registered user, caches the message session authentication identifier corresponding to the user number of the registered user as authentication information, and sends the message session authentication identifier corresponding to the user number of the registered user to a cloud phone platform message client for caching.

[0020] According to a fifteenth aspect of embodiments of the present disclosure, an electronic device is provided, comprising: a processor; a memory for storing executable instructions of the processor; wherein the processor is configured to execute the instructions to implement the message processing method according to the first aspect of embodiments of the present disclosure, or implement the message processing method according to the second aspect of embodiments of the present disclosure, or implement the cloud phone login authentication method according to the third aspect of embodiments of the present disclosure, or implement the message processing method according to the fourth aspect of embodiments of the present disclosure, or implement the message processing method according to the fifth aspect of embodiments of the present disclosure, or implement the cloud phone login authentication method according to the sixth aspect of embodiments of the present disclosure, or implement the cloud phone login authentication method according to the seventh aspect of embodiments of the present disclosure.

[0021] According to a sixteenth aspect of the embodiments of the present disclosure, a computer readable storage medium is provided, when instructions in the computer readable storage medium are executed by a processor of an electronic device, the electronic device can perform the message processing method according to the first aspect of the embodiments of the present disclosure, or implement the message processing method according to the second aspect of the embodiments of the present disclosure, or implement the cloud phone login authentication method according to the third aspect of the embodiments of the present disclosure, or implement the message processing method according to the fourth aspect of the embodiments of the present disclosure, or implement the message processing method according to the fifth aspect of the embodiments of the present disclosure, or implement the cloud phone login authentication method according to the sixth aspect of the embodiments of the present disclosure, or implement the cloud phone login authentication method according to the seventh aspect of the embodiments of the present disclosure.

[0022] The technical solutions provided by the embodiments of the present disclosure at least have the following beneficial effects:

[0023] The message processing method provided by the embodiments of the present disclosure, in the process of receiving messages by the cloud phone, the 5G message cloud service platform in the basic message platform judges whether the user corresponding to the destination number is a registered user and an online state according to the cached authentication information, and when it is determined that the user corresponding to the destination number is a registered user and is in an online state, the to-be-received message is sent to the cloud phone platform message client corresponding to the destination number for display, and the to-be-received message is pushed to the corresponding cloud phone client for display through the cloud phone platform message client. The embodiments of the present disclosure realize the authentication of message interaction based on the cached authentication information, and the cloud phone client can use the 5G message and short message service consistent with the native phone experience, realize the cloud of the cloud phone message function, and solve the problem of limited or missing message function caused by the dependence and limitation of the cloud phone and the local phone permission.

[0024] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0025] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure, and do not constitute an improper limitation of the present disclosure.

[0026] Figure 1 is a schematic diagram of an implementation scenario of a cloud phone according to an exemplary embodiment.

[0027] Figure 2 is a schematic diagram of cloud computing, storage and data layer of a mobile phone according to another exemplary embodiment.

[0028] Figure 3Fig. 6 is a schematic diagram illustrating interaction between a cloud and a cloud phone application according to another exemplary embodiment.

[0029] Figure 4 Fig. 7 is a schematic diagram of communication of a 5G message center according to another exemplary embodiment.

[0030] Figure 5 Fig. 8 is a schematic diagram of an overall architecture of clouding of cloud phone messages according to another exemplary embodiment.

[0031] Figure 6 Fig. 9 is a schematic diagram of an H5 implementation according to another exemplary embodiment.

[0032] Figure 7 Fig. 10 is a flowchart of a message processing method according to another exemplary embodiment.

[0033] Figure 8 Fig. 11 is a flowchart of a message processing method according to another exemplary embodiment.

[0034] Figure 9 Fig. 12 is a flowchart of a message processing method according to another exemplary embodiment.

[0035] Figure 10 Fig. 13 is a flowchart of a message processing method according to another exemplary embodiment.

[0036] Figure 11 Fig. 14 is a flowchart of a cloud phone login authentication method according to another exemplary embodiment.

[0037] Figure 12 Fig. 15 is a flowchart of a message processing method according to another exemplary embodiment.

[0038] Figure 13 Fig. 16 is a flowchart of a message processing method according to another exemplary embodiment.

[0039] Figure 14 Fig. 17 is a flowchart of a cloud phone login authentication method according to another exemplary embodiment.

[0040] Figure 15 Fig. 18 is a flowchart of a cloud phone login authentication method according to another exemplary embodiment.

[0041] Figure 16 Fig. 19 is a signaling interaction diagram of a message processing method according to another exemplary embodiment.

[0042] Figure 17 Fig. 20 is a signaling interaction diagram of a message processing method according to another exemplary embodiment.

[0043] Figure 18 is a signaling interaction diagram of a cloud phone login authentication method according to another exemplary embodiment.

[0044] Figure 19 is a block diagram of a message processing apparatus according to another exemplary embodiment.

[0045] Figure 20 is a block diagram of a message processing apparatus according to another exemplary embodiment.

[0046] Figure 21 is a block diagram of a cloud phone login authentication apparatus according to another exemplary embodiment.

[0047] Figure 22 is a block diagram of a message processing apparatus according to another exemplary embodiment.

[0048] Figure 23 is a block diagram of a message processing apparatus according to another exemplary embodiment.

[0049] Figure 24 is a block diagram of a cloud phone login authentication apparatus according to another exemplary embodiment.

[0050] Figure 25 is a block diagram of a cloud phone login authentication apparatus according to another exemplary embodiment.

[0051] Figure 26 is a block diagram of an electronic device according to another exemplary embodiment. DETAILED DESCRIPTION

[0052] In order for those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be described clearly and completely below with reference to the drawings.

[0053] It should be noted that the terms "first", "second", and the like in the specification and claims of the present disclosure and the above-described drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0054] Cloud phone is a specific implementation mode of virtualization technology, and finally provides a cloud instance (or operating system) for users. Users can remotely control the cloud phone in real time through video streaming, and finally realize the cloud running of Android native application (APP) and mobile games. As shown in Figure 1 The cloud phone product processes all the systems and applications on the user's native phone side to the cloud. Through streaming media, the user's APP end is displayed and accepts operation instructions, reducing the dependence on terminal hardware.

[0055] As shown in Figure 2 The cloud phone currently implements cloud-side mobile phone functions, focusing on cloud computing, storage and data layer of general mobile phone applications, meeting the needs of users for mobile office, game proxy and other applications. The essence of the cloud phone is to provide users with a use experience that can use mobile phone functions in the cloud through a cheaper phone and a special cloud phone application (i.e. cloud phone client). As shown in Figure 3 The cloud (i.e. cloud phone platform) and cloud phone application (i.e. cloud phone client) can interact through video streaming and instruction streaming.

[0056] Since it is a cloud implementation of mobile phone functions, the most basic communication function of the mobile phone has a basic implementation mode in the cloud phone. Taking the message function as an example, the cloud phone can access the message function by calling the short message permission provided by the mobile phone. Users can read and send messages in the message entry of the cloud phone application. However, due to the reading of the short message permission, it needs to be associated with the mobile phone number corresponding to the Subscriber Identity Module (SIM) card inserted in the actual mobile phone. In the cloud phone supporting different mobile phone numbers login mode, the use scenario is very limited. If the mobile phone number associated with the cloud phone login is not consistent with the mobile phone number running on the current mobile phone, the short message permission connection mode will not be available. At the same time, the short message upgrade service 5th Generation Mobile Communication Technology (5G) message launched by the operator cannot be obtained and operated through the mobile phone permission acquisition method. Therefore, the cloud phone product is limited and even missing in the cloud of the message capability in the communication field. Therefore, the present application provides a scheme for realizing the cloud of the message capability.

[0057] As an upgrade of the operator's basic short message service, the existing network has realized the fusion of rich media (such as pictures, audio and video, location and cards, etc.) and short message functions on the platform side. As shown in Figure 4As shown, the 5G Message Center (5GMC) network element connects to both 5G messaging terminals and ordinary mobile terminals, and has the functions of both Rich Communication Suite (RCS) and SMS center. On the other side, it connects to Messaging as a Platform (MaaP) and Chatbot / Chatbot Service Provider (CSP).

[0058] Figure 5 This is a schematic diagram illustrating the overall architecture of cloud phone messaging to the cloud, according to an exemplary embodiment. For example... Figure 5 As shown, the mobile terminal (5G messaging terminal or ordinary mobile terminal) communicates with the 5GMC set up in the basic messaging platform. The 5GMC communicates with the Chatbot / CSP through the MaaP platform. The 5GMC also communicates with the SMS application / service provider (SMS application / Service Provider, referred to as SMS application / SP) through the SMS gateway. The 5GMC also communicates with the 5G messaging cloud service platform set up in the basic messaging platform. The 5G messaging cloud service platform communicates with the cloud phone platform messaging client set up in the cloud phone platform based on lightweight protocols such as Session Initialization Protocol (SIP) or Hyper Text Transfer Protocol (HTTP). The cloud phone platform messaging client communicates with the cloud phone client (i.e., cloud phone application) and interacts through video streams and command streams.

[0059] like Figure 5As shown, on the basic messaging platform side, based on the basic capabilities of SMS and 5G messaging (including user-to-user and user-to-application interactions) aggregated by the operator's basic messaging network element 5GMC, the 5G messaging cloud service provided by the 5G messaging cloud service platform is further overlaid. Through a bypass method, the full range of basic messaging services is pushed and interoperated with cloud phone products. On the cloud phone platform side, the existing messaging entry application is replaced with a new messaging application (i.e., the cloud phone platform messaging client). The new messaging application includes a 5G messaging Hyper Text Markup Language 5 (HTML5 or H5) front-end or a Software Development Kit (SDK) application, implementing entirely new basic communication messaging functions and related user interface (UIUE) processing logic. Through the collaboration between the 5G messaging cloud service platform and the new cloud phone platform messaging client, the cloud phone messaging function is upgraded, resolving the dependency and limitation issues of cloud phone and local phone permissions.

[0060] The implementation mechanisms of the newly deployed 5G messaging cloud service platform on the basic messaging platform side and the new messaging application (i.e., cloud phone platform messaging client) on the cloud phone platform side, as described in the embodiments of this disclosure, will be described in detail below.

[0061] 1. The implementation mechanism of the newly deployed 5G messaging cloud service platform on the basic messaging platform side.

[0062] This disclosed embodiment introduces a 5G messaging cloud service platform via a bypass method, interfacing with existing network standard 5GMC network elements, laying an important foundation for message interoperability with cloud phones. The core mechanism includes:

[0063] 1) 5GMC simultaneously transmits 5G messages and SMS.

[0064] Building upon its 5G messaging and SMS capabilities, 5GMC adds a synchronization mechanism to push all information to the 5G messaging cloud service platform in real time. Furthermore, to reduce synchronization overhead, in addition to simple full copying, the synchronization mechanism can also employ a subscription push mechanism, which synchronizes only the 5G messages and SMS messages of users subscribed to by the 5G messaging cloud service platform.

[0065] 2) 5GMC receives and processes message push requests for cloud services through the standard interface of the existing 5G messaging network.

[0066] To support interoperability of information between cloud phones, 5GMC can receive message push requests from the 5G messaging cloud service platform according to the existing standard inter-platform 5G messaging SIP interoperability interface. Following established standard functions, it can then push 5G messages or SMS messages to its access terminals.

[0067] 3) The ability to connect the 5G messaging cloud service platform with the cloud phone platform.

[0068] Based on the cloud phone integration model, the 5G messaging cloud service platform provides supporting access service capabilities. For access authentication of cloud phone clients, the mobile phone number logged in by the cloud phone client itself is used as the foundation. The 5G messaging cloud service platform then interfaces with the cloud phone platform, overlaying internal single sign-on and authorization mechanisms to achieve access authentication for 5G messaging services.

[0069] If the cloud phone platform's messaging client adopts the WebView H5 integration mode, the 5G messaging cloud service platform has a built-in 5G messaging H5 mode web service module to complete the rendering, page generation, and push of the relevant H5 front-end messaging interface. In the relevant message interaction process, a downlink message queue telemetry transport (MQTT) notification + uplink HTTP information retrieval mechanism, suitable for H5 front-end programming language (JavaScript, JS), is used to achieve business functions consistent with the native mobile terminals of 5G messaging and SMS services.

[0070] If the cloud phone platform's messaging client adopts the SDK application replacement method, the 5G messaging cloud service platform focuses on server-side message encoding and decoding and related message routing and forwarding processing, without involving front-end logic. Both 5G messaging and SMS interactions are uniformly carried out using the SIP protocol.

[0071] 2. The implementation mechanism of the new messaging application (i.e., the cloud phone platform messaging client) deployed on the cloud phone platform side.

[0072] The new messaging application can be implemented in the following two ways:

[0073] The first method is the deep customization mode: the cloud phone platform is upgraded through the SDK application mode.

[0074] Specifically, the existing cloud phone platform messaging application will be directly upgraded, implementing message protocol stack encoding / decoding and UI / UX related logic processing via a messaging app or SDK. The new messaging app or SDK will be extended based on the 5G messaging standard SIP protocol stack, while also carrying rich media and SMS content.

[0075] The second approach is the lightweight H5 cloud service model: the cloud phone platform integrates the message H5 front-end through the WebView component.

[0076] Specifically, the WebView component is a control used to display web pages. It is based on the WebKit engine and therefore has the ability to render web pages. For example...Figure 6 As shown, the H5 implementation is optimized based on common Web technologies, minimizing the adaptation workload on the cloud phone platform side. It adopts lighter and more universal protocols such as HTTP+MQTT, and through the H5 mode, all message logic (including UI / UX implementation) is centrally implemented on the 5G messaging cloud service platform side. To maintain consistency between the messaging experience and native mobile phone usage in H5 mode, unlike the typical approach where all H5 page logic is implemented internally, the cloud phone platform messaging client allocates independent storage space resources for the message WebView component and uses JavaScript capabilities to call and implement message notification and other functions within the cloud phone platform messaging client.

[0077] The technical solutions in the embodiments of this disclosure will be further described clearly and completely below with reference to the accompanying drawings.

[0078] Figure 7 This is a flowchart illustrating a message processing method according to an exemplary embodiment. The execution entity of the message processing method in this disclosure is a message processing apparatus provided in this disclosure. This message processing apparatus can be installed in an electronic device, such as a 5G message cloud service platform within a basic messaging platform, to execute the message processing method of this disclosure. Figure 7 As shown, the message processing method of this embodiment is a process of a cloud phone initiating a message, which may specifically include the following steps:

[0079] S701 receives a message sending request from a cloud phone platform message client set in the cloud phone platform. The message sending request includes the message to be sent, the message session authentication identifier of the online user, and the destination number of the message to be sent.

[0080] In this embodiment, when a user (i.e., a user who has successfully logged into the cloud phone client and is online, such as user A) initiates a message through the message entry point of the cloud phone client (i.e., the cloud phone platform message client set in the cloud phone platform), the cloud phone platform message client generates a message sending request and sends the message sending request to the 5G message cloud service platform. The message sending request may specifically include, but is not limited to, the message to be sent, the message session authentication identifier of the online user (e.g., user A), and the destination number of the message to be sent (e.g., mobile phone number B). Specifically, the message sending request can be an HTTP request.

[0081] The message to be sent is the content of the message entered by the user (e.g., user A) through the cloud phone client to the cloud phone platform message client. The message session authentication identifier for the online user (e.g., user A) is obtained by the cloud phone platform message client based on the message session authentication identifiers (e.g., message session authentication identifier A, message session authentication identifier B, etc.) corresponding to the user numbers (e.g., mobile number A, mobile number B, etc.) of registered users (e.g., user A, user B, etc.) cached in the cloud phone login authentication process. The destination number (e.g., mobile number B), also known as the called mobile number, is the number entered by the user (e.g., user A) through the cloud phone client to the cloud phone platform message client.

[0082] The 5G messaging cloud service platform receives the message sending request from the cloud mobile phone platform messaging client.

[0083] It should be noted that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie. The message to be sent can be an SMS or a 5G message.

[0084] S702, retrieve cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0085] In this embodiment of the disclosure, the 5G messaging cloud service platform obtains the authentication information cached in the cloud phone login authentication process. The authentication information includes the message session authentication identifier (e.g., message session authentication identifier A, message session authentication identifier B, etc.) corresponding to the user number (e.g., mobile phone number A, mobile phone number B, etc.) of the registered user (e.g., user A, user B, etc.). That is, it includes registered user - user number - message session authentication identifier.

[0086] S703 performs a first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user.

[0087] In this embodiment of the disclosure, the 5G messaging cloud service platform performs a validity check on the message session authentication identifier in the received message sending request based on the cached authentication information, which is recorded as the first check. If a message session authentication identifier that matches the message session authentication identifier in the message sending request can be found in the authentication information, the first check passes.

[0088] S704 After the first verification passes, the message to be sent and the destination number are sent to the 5G Message Center of the destination number, so that the 5G Message Center can send the message to be sent to the mobile terminal or message platform corresponding to the destination number.

[0089] In this embodiment of the disclosure, if the first verification passes, the 5G messaging cloud service platform sends (i.e., pushes) the message to be sent and the destination number to the 5GMC to which the destination number belongs, according to the destination number in the message sending request, through the standard interface of the existing network. The 5GMC completes the subsequent message push according to the standard Mobile Terminated (MT) message procedure, that is, the 5GMC sends the message to be sent to the mobile terminal corresponding to the destination number as an SMS or 5G message, or the 5GMC sends the message to be sent to the MaaP platform corresponding to the destination number as a 5G message.

[0090] It should be noted that when the cloud phone platform messaging client is deployed in a deeply customized mode, the cloud phone platform upgrades through the SDK application mode and uses the SIP protocol for message interaction between the cloud phone platform messaging client and the 5G messaging cloud service platform.

[0091] In summary, the message processing method of this disclosure embodiment, during the message initiation process of a cloud phone, involves the 5G messaging cloud service platform set up in the basic messaging platform verifying the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. Upon successful verification, the message initiated by the cloud phone is sent to the mobile terminal or messaging platform corresponding to the destination number via the 5G messaging center. This disclosure embodiment achieves message interaction authentication based on cached authentication information, enabling the cloud phone client to use 5G messaging and SMS services with a consistent experience as a native mobile phone. It realizes the cloud phone's messaging function being migrated to the cloud, solving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0092] Figure 8 This is a flowchart illustrating a message processing method according to another exemplary embodiment. For example... Figure 8 As shown, the message processing method in this embodiment is a process of a cloud phone initiating a message. Figure 7 Based on the illustrated embodiment, the specific steps may include:

[0093] S801 receives a message sending request from a cloud phone platform message client set in the cloud phone platform. The message sending request includes the message to be sent, the online user's message session authentication identifier, and the destination number of the message to be sent.

[0094] S802, retrieve cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0095] S803 performs a first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user.

[0096] In this embodiment, the specific process of steps S801-S803 can be found in the relevant descriptions of steps S701-S703 in the above embodiments, and will not be repeated here.

[0097] S804: After the first verification passes, the message to be sent is stored in the message queue corresponding to the user number.

[0098] In this embodiment of the disclosure, if the first verification passes, the 5G messaging cloud service platform stores the message to be sent in the message sending request into the message queue corresponding to the user number of the currently online user, and waits to send it out.

[0099] S805 sends the message to be sent and the destination number to the 5G messaging center to which the destination number belongs, so that the 5G messaging center can send the message to be sent to the mobile terminal or messaging platform corresponding to the destination number.

[0100] In this embodiment of the disclosure, the 5G messaging cloud service platform sends the messages to be sent stored in the message queue to the 5GMC to which the destination number belongs. For details, please refer to the relevant description in step S704 of the above embodiment, which will not be repeated here.

[0101] The message processing method of this disclosure may also include the process of displaying the message to be sent on the cloud mobile phone platform message client and the cloud mobile phone client, which may specifically include two implementation methods.

[0102] The first method involves the 5G messaging cloud service platform notifying the cloud phone platform message client to retrieve the message. See steps S806-S809 for details.

[0103] S806 sends message retrieval notification messages to the cloud phone platform message client.

[0104] In this embodiment of the disclosure, the 5G messaging cloud service platform sends a message retrieval notification message to the cloud phone platform messaging client to notify the cloud phone platform messaging client that it can retrieve messages to obtain messages to be sent.

[0105] S807 receives message retrieval requests sent by the cloud phone platform's message client. The message retrieval request includes a message session authentication identifier.

[0106] In this embodiment of the disclosure, after receiving the message retrieval notification message, the cloud phone platform message client sends a message retrieval request to the 5G messaging cloud service platform. The message retrieval request includes at least a message session authentication identifier, and specifically, it can be an HTTP request initiated by the cloud phone platform message client through the WebView frontend.

[0107] S808 performs a second verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user.

[0108] In this embodiment of the disclosure, the 5G messaging cloud service platform performs a validity check on the message session authentication identifier in the received message retrieval request based on the cached authentication information; this is referred to as the second check. If a message session authentication identifier matching the message session authentication identifier in the message retrieval request can be found in the authentication information, the second check passes.

[0109] S809, after the second verification passes, the message to be sent is sent to the cloud phone platform message client so that the cloud phone platform message client can display the message to be sent, and the message to be sent is also sent to the cloud phone clients of online users for display.

[0110] In this embodiment, if the second verification passes, the 5G messaging cloud service platform sends the message to be sent stored in the message queue to the cloud phone platform messaging client. The cloud phone platform messaging client displays the message to be sent and sends it to the currently online user's logged-in cloud phone client via video stream. The cloud phone client receives and displays the message to be sent. The 5G messaging cloud service platform can also send the message to be sent to the cloud phone platform messaging client via HTTP response, and the cloud phone platform messaging client displays the message page content based on the message to be sent.

[0111] The second method, where the 5G messaging cloud service platform notifies the cloud phone platform message client to display the message directly, is described in the following steps:

[0112] The first verified response message is sent to the cloud phone platform message client so that the cloud phone platform message client can display the message to be sent, and the message to be sent is also sent to the cloud phone clients of online users for display.

[0113] In this embodiment, when sending a message sending request, the cloud phone platform messaging client can cache the message to be sent entered by the user. The 5G messaging cloud service platform sends a first verified response message to the cloud phone platform messaging client. After receiving the first verified response message from the 5G messaging cloud service platform, the cloud phone platform messaging client can directly display the cached message to be sent and send the message to be sent to the currently online user's logged-in cloud phone client via video stream. The cloud phone client receives and displays the message to be sent.

[0114] In summary, the message processing method provided in this disclosure, during the message initiation process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform to verify the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. Upon successful verification, the message initiated by the cloud phone is sent through the 5G messaging center to the mobile terminal or messaging platform corresponding to the destination number. The cloud phone platform message client is also notified to display the message initiated by the cloud phone either by pulling or by direct display. This disclosure implements message interaction authentication based on cached authentication information, enabling the cloud phone client to use 5G messaging and SMS services with a consistent experience as a native mobile phone. It achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0115] Figure 9 This is a flowchart illustrating a message processing method according to another exemplary embodiment. The execution entity of the message processing method in this disclosure is a message processing apparatus provided in this disclosure. This message processing apparatus can be installed in an electronic device, such as a 5G message cloud service platform within a basic messaging platform, to execute the message processing method of this disclosure. Figure 9 As shown, the message processing method of this embodiment is a process for a cloud phone to receive messages, which may specifically include the following steps:

[0116] S901 receives a message synchronization request sent by the 5G message center. The message synchronization request includes the message to be received and the destination number.

[0117] In this embodiment of the disclosure, after the 5GMC to which the destination number (i.e., the called number) belongs receives a 5G message or SMS (i.e., a message to be received by the cloud phone) pushed by the basic network, it triggers the synchronization copy logic: it sends a message synchronization request to the 5G messaging cloud service platform, which includes the message to be received and the destination number. The 5G messaging cloud service platform receives the message synchronization request sent by the 5GMC.

[0118] S902, retrieve cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0119] In this embodiment of the disclosure, the 5G messaging cloud service platform obtains the authentication information cached in the cloud phone login authentication process. The authentication information includes the message session authentication identifier (e.g., message session authentication identifier A, message session authentication identifier B, etc.) corresponding to the user number (e.g., mobile phone number A, mobile phone number B, etc.) of the registered user (e.g., user A, user B, etc.). That is, it includes registered user - user number - message session authentication identifier.

[0120] It should be noted here that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie.

[0121] S903: If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is online, then the message to be received is sent to the cloud phone platform message client set in the cloud phone platform, so that the cloud phone platform message client can display the message to be received, and the message to be received is sent to the cloud phone client of the user corresponding to the destination number for display.

[0122] In this embodiment, the 5G messaging cloud service platform determines whether the user corresponding to the destination number in the received message synchronization request is a registered user and whether they are online, based on cached authentication information. If a user number matching the destination number in the message synchronization request can be found in the authentication information, the user corresponding to that destination number is determined to be a registered user, and the online status of that user is obtained. If the user corresponding to the destination number is a registered user and is online, the 5G messaging cloud service platform sends the message to be received to the cloud phone platform messaging client set in the cloud phone platform. The cloud phone platform messaging client displays the message to be received and sends it to the cloud phone client currently logged in by the user corresponding to the destination number via video stream. The cloud phone client receives and displays the message to be received. The 5G messaging cloud service platform can send the message to be received to the cloud phone platform messaging client via HTTP response, and the cloud phone platform messaging client displays the message page content based on the message to be received.

[0123] It should be noted that when the cloud phone platform messaging client is deployed in a deeply customized mode, the cloud phone platform upgrades through the SDK application mode and uses the SIP protocol for message interaction between the cloud phone platform messaging client and the 5G messaging cloud service platform.

[0124] In summary, the message processing method provided in this disclosure, during the message receiving process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform. Based on cached authentication information, the platform determines whether the user corresponding to the destination number sent by the cloud phone platform message client is a registered user and is online. If the user corresponding to the destination number is confirmed to be registered and online, the platform sends the message to be received to the corresponding cloud phone platform message client for display. The platform also pushes the message to be received to the corresponding cloud phone client for display. This disclosure implements message interaction authentication based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as on a native mobile phone. This achieves cloud-based messaging functionality for cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0125] Figure 10 This is a flowchart illustrating a message processing method according to another exemplary embodiment. For example... Figure 10 As shown, the message processing method in this embodiment is a process of a cloud phone receiving messages. Figure 9 Based on the illustrated embodiment, the specific steps may include:

[0126] S1001 receives a message synchronization request sent by the 5G message center. The message synchronization request includes the message to be received and the destination number.

[0127] S1002, retrieve cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0128] In this embodiment, the specific process of steps S1001-S1002 can be found in the relevant descriptions of steps S901-S902 in the above embodiments, and will not be repeated here.

[0129] Step S903 in the above embodiment, "If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is online, then the message to be received is sent to the cloud phone platform message client set in the cloud phone platform, so that the cloud phone platform message client can display the message to be received, and the message to be received is sent to the cloud phone client of the user corresponding to the destination number for display," may specifically include the following steps:

[0130] S1003: If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is online, then a message retrieval notification message will be sent to the cloud phone platform message client.

[0131] In this embodiment, the 5G messaging cloud service platform determines whether the user corresponding to the destination number in the received message synchronization request is a registered user and whether they are online, based on cached authentication information. If a user number matching the destination number in the message synchronization request can be found in the authentication information, the user corresponding to the destination number is determined to be a registered user, and the online status of the user corresponding to the destination number is obtained. If the user corresponding to the destination number is a registered user and is online, the 5G messaging cloud service platform sends a message retrieval notification message to the cloud phone platform messaging client to notify the cloud phone platform messaging client that it can retrieve messages to receive the messages to be received.

[0132] S1004 Receives a message retrieval request sent by the cloud phone platform message client. The message retrieval request includes the message session authentication identifier of the user corresponding to the destination number.

[0133] In this embodiment of the disclosure, after receiving the message retrieval notification message, the cloud phone platform message client sends a message retrieval request to the 5G messaging cloud service platform. The message retrieval request includes at least the message session authentication identifier of the user corresponding to the destination number. Specifically, the message retrieval request can be an HTTP request initiated by the cloud phone platform message client through the WebView frontend.

[0134] S1005, perform a third verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the cache.

[0135] In this embodiment of the disclosure, the 5G messaging cloud service platform performs a validity check on the message session authentication identifier in the received message retrieval request based on the cached authentication information; this is referred to as the third check. If a message session authentication identifier matching the message session authentication identifier in the message retrieval request can be found in the authentication information, the third check passes.

[0136] S1006 After the third verification passes, the message to be received is sent to the cloud phone platform message client so that the cloud phone platform message client can display the message to be received, and the message to be received is sent to the cloud phone client of the user corresponding to the destination number for display.

[0137] In this embodiment, if the third verification passes, the 5G messaging cloud service platform sends the message to be received to the cloud phone platform messaging client. The cloud phone platform messaging client displays the message to be received and sends it via video stream to the cloud phone client logged in by the currently online user. The cloud phone client receives and displays the message to be received. The 5G messaging cloud service platform can also send the message to be received to the cloud phone platform messaging client via HTTP response, and the cloud phone platform messaging client displays the message page content based on the message to be received.

[0138] S1007: If the user corresponding to the destination number is determined to be an unregistered user based on the user number of a registered user, then the message to be received is discarded.

[0139] In this embodiment of the disclosure, if it is determined that the user corresponding to the destination number is an unregistered user, the 5G messaging cloud service platform directly discards the message to be received.

[0140] S1008: If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is in an offline state, then the message to be received is cached as an offline message.

[0141] In this embodiment of the disclosure, if it is determined that the user corresponding to the destination number is a registered user but the user is offline, the 5G messaging cloud service platform caches the message to be received as an offline message and pushes the message to be received when it detects that the user is online.

[0142] In summary, the message processing method provided in this disclosure, during the message receiving process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform determining the registered user and online status of the user corresponding to the destination number sent by the cloud phone platform message client based on cached authentication information. If the user corresponding to the destination number is determined to be a registered user and online, the message to be received is sent to the corresponding cloud phone platform message client for display. The message to be received is also pushed to the corresponding cloud phone client for display via the cloud phone platform message client. If the user corresponding to the destination number is determined to be an unregistered user, the message to be received is discarded. If the user corresponding to the destination number is determined to be a registered user but is offline, the message to be received is cached as an offline message. This disclosure implements message interaction authentication based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as a native mobile phone. It achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0143] Figure 11This is a flowchart illustrating a cloud phone login authentication method according to another exemplary embodiment. The executing entity of the cloud phone login authentication method in this disclosure is the cloud phone login authentication device provided in this disclosure. This cloud phone login authentication device can be installed in an electronic device, such as a 5G messaging cloud service platform within a basic messaging platform, to execute the cloud phone login authentication method of this disclosure. Figure 11 As shown, the cloud phone login authentication method of this disclosure embodiment may specifically include the following steps:

[0144] S1101, Receive a single sign-on authentication request sent by the cloud phone platform message client set in the cloud phone platform. The single sign-on authentication request includes a 5G message single sign-on token, which is sent by the cloud phone platform to the cloud phone platform message client through the cloud phone client.

[0145] In this embodiment, the single sign-on module in the cloud phone platform generates a 5G Messaging single sign-on token after successful login on the cloud phone client and sends the token to the client. This token corresponds to the user number of the currently logged-in registered user. The cloud phone client determines the user number and sends the 5G Messaging single sign-on token to the cloud phone platform's messaging client. The cloud phone platform's messaging client receives the token and triggers the single sign-on process when the user clicks on it: it sends a single sign-on authentication request to the 5G Messaging cloud service platform, the request including the 5G Messaging single sign-on token.

[0146] S1102 sends the single sign-on authentication request to the cloud phone platform.

[0147] In this embodiment of the disclosure, the 5G Messaging Cloud Service Platform sends a single sign-on authentication request to the single sign-on module in the cloud phone platform, and the single sign-on module in the cloud phone platform receives the single sign-on authentication request sent by the 5G Messaging Cloud Service Platform.

[0148] S1103, Receive the user number of the registered user corresponding to the 5G message single sign-on token sent by the cloud phone platform. The user number of the registered user corresponding to the 5G message single sign-on token is sent by the cloud phone platform after the received 5G message single sign-on token has been authenticated.

[0149] In this embodiment, after receiving a single sign-on authentication request from the 5G Messaging Cloud Service Platform, the single sign-on module in the cloud phone platform authenticates the 5G Messaging single sign-on token in the request. Upon successful authentication, it sends the user number of the currently logged-in registered user corresponding to the 5G Messaging single sign-on token to the 5G Messaging Cloud Service Platform. The 5G Messaging Cloud Service Platform receives the user number of the registered user corresponding to the 5G Messaging single sign-on token from the cloud phone platform.

[0150] It should be noted that the 5G Messaging Cloud Service Platform can also cache the association between 5G Messaging Single Sign-On Tokens and the corresponding registered user numbers, and generate the message page corresponding to that user number.

[0151] S1104, Generate a message session authentication identifier corresponding to the user number of the registered user, and cache the message session authentication identifier corresponding to the user number of the registered user as authentication information.

[0152] In this embodiment of the disclosure, the 5G messaging cloud service platform assigns a corresponding message session authentication identifier to the user number of the registered user received for this login session. The user number and the message session authentication identifier are in one-to-one correspondence, and the message session authentication identifier corresponding to the user number of the registered user is cached as authentication information.

[0153] It should be noted here that the message session authentication identifier can be either a message session authentication token or a message session authentication cookie.

[0154] S1105 sends the message session authentication identifier corresponding to the registered user's user number to the cloud phone platform message client for caching.

[0155] In this embodiment, the 5G messaging cloud service platform sends the message session authentication identifier corresponding to the registered user's user number to the cloud phone platform messaging client. The cloud phone platform messaging client caches the message session authentication identifier corresponding to the registered user's user number and pushes it to the cloud phone client via video streaming. Alternatively, the 5G messaging cloud service platform can send the message session authentication identifier corresponding to the registered user's user number to the cloud phone platform messaging client by sending relevant associated message page information. The cloud phone platform messaging client then displays content based on the associated message page information.

[0156] It should be noted that the single sign-on module in the cloud phone platform authenticates the 5G Messaging single sign-on token in the single sign-on authentication request. If authentication fails, the 5G Messaging cloud service platform sends an authentication failure response to the cloud phone platform's messaging client. The cloud phone platform's messaging client then re-applies for a new 5G Messaging single sign-on token from the cloud phone platform's single sign-on module. After the 5G Messaging single sign-on token is re-acquired, the aforementioned single sign-on authentication request to the 5G Messaging cloud service platform is retried.

[0157] Before the single sign-on module in the cloud phone platform generates the 5G message single sign-on token, the process includes the cloud phone client's login procedure: the cloud phone client sends a login request to the cloud phone platform, including the user's number and user information. The cloud phone platform receives the login request from the cloud phone client, authenticates the user information in the login request, and if it successfully determines that the user's number corresponds to the currently logged-in user, the cloud phone client logs in successfully. The single sign-on module in the cloud phone platform then generates the 5G message single sign-on token corresponding to the user's number.

[0158] In summary, the cloud phone login authentication method of this disclosure, through single sign-on and authorization mechanisms, caches authentication information for subsequent interactive authentication in the message sending and receiving process. This disclosure achieves message interaction authentication based on the cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as on a native mobile phone. It realizes the cloud phone's messaging function being migrated to the cloud, solving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0159] Figure 12 This is a flowchart illustrating a message processing method according to another exemplary embodiment. The execution entity of the message processing method in this disclosure is the message processing apparatus provided in this disclosure. This message processing apparatus can be installed in an electronic device, such as a cloud phone platform message client in a cloud phone platform, to execute the message processing method of this disclosure. Figure 12 As shown, the message processing method of this embodiment is a process of a cloud phone initiating a message, which may specifically include the following steps:

[0160] S1201, Generate a message sending request. The message sending request includes the message to be sent, the online user's message session authentication identifier, and the destination number of the message to be sent.

[0161] S1202, a message sending request is sent to the 5G messaging cloud service platform, so that the 5G messaging cloud service platform can perform a first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the cached authentication information, and after the first verification is passed, the message to be sent is sent to the mobile terminal or messaging platform corresponding to the destination number through the 5G messaging center to which the destination number belongs.

[0162] As a feasible implementation method, the message processing method of this disclosure embodiment may further include the following steps: receiving a first verification passed response message sent by the 5G messaging cloud service platform, wherein the first verification passed response message is generated by the 5G messaging cloud service platform after the first verification is passed; displaying the message to be sent; and sending the message to be sent to the cloud mobile client of the online user for display.

[0163] As another feasible implementation, the message processing method of this disclosure embodiment may further include the following steps: receiving a message retrieval notification message sent by a 5G messaging cloud service platform; sending a message retrieval request to the 5G messaging cloud service platform, the message retrieval request including a message session authentication identifier; receiving a message to be sent sent by the 5G messaging cloud service platform, the message to be sent being sent after the 5G messaging cloud service platform performs a second verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user; displaying the message to be sent; and sending the message to be sent to the cloud mobile client of the online user for display.

[0164] It should be noted that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie. The message to be sent can be an SMS or a 5G message.

[0165] In this embodiment of the disclosure, the specific process of each of the above steps can be found in the above description. Figure 7 , Figure 8 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0166] In summary, the message processing method provided in this disclosure, during the message initiation process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform to verify the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. Upon successful verification, the message initiated by the cloud phone is sent through the 5G messaging center to the mobile terminal or messaging platform corresponding to the destination number. The cloud phone platform message client is also notified to display the message initiated by the cloud phone either by pulling or by direct display. This disclosure implements message interaction authentication based on cached authentication information, enabling the cloud phone client to use 5G messaging and SMS services with a consistent experience as a native mobile phone. It achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0167] Figure 13 This is a flowchart illustrating a message processing method according to another exemplary embodiment. The execution entity of the message processing method in this disclosure is the message processing apparatus provided in this disclosure. This message processing apparatus can be installed in an electronic device, such as a cloud phone platform message client in a cloud phone platform, to execute the message processing method of this disclosure. Figure 13 As shown, the message processing method of this embodiment is a process for a cloud phone to receive messages, which may specifically include the following steps:

[0168] S1301, Receive a message to be received from the 5G Messaging Cloud Service Platform. The message to be received is sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request from the 5G Messaging Center. The platform determines that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online. The message synchronization request includes the message to be received and the destination number.

[0169] S1302, Displaying messages to be received.

[0170] S1303: Send the message to be received to the cloud mobile client of the user corresponding to the destination number for display.

[0171] Specifically, step S1301, "receiving messages to be received from the 5G Messaging Cloud Service Platform," may include the following steps: receiving a message retrieval notification message from the 5G Messaging Cloud Service Platform. This message retrieval notification message is sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request from the 5G Messaging Center and determining, based on the user number of the registered user in the cached authentication information, that the user corresponding to the destination number is a registered user and that the user corresponding to the destination number is online; sending a message retrieval request to the 5G Messaging Cloud Service Platform, the message retrieval request including the message session authentication identifier of the user corresponding to the destination number; and receiving messages to be received from the 5G Messaging Cloud Service Platform. These messages are sent by the 5G Messaging Cloud Service Platform after a third verification of the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

[0172] It should be noted that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie. The message to be received can be an SMS or a 5G message.

[0173] In this embodiment of the disclosure, the specific process of each of the above steps can be found in the above description. Figure 9 , Figure 10 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0174] In summary, the message processing method provided in this disclosure, during the message receiving process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform determining the registered user and online status of the user corresponding to the destination number sent by the cloud phone platform message client based on cached authentication information. If the user corresponding to the destination number is determined to be a registered user and online, the message to be received is sent to the corresponding cloud phone platform message client for display. The message to be received is also pushed to the corresponding cloud phone client for display via the cloud phone platform message client. If the user corresponding to the destination number is determined to be an unregistered user, the message to be received is discarded. If the user corresponding to the destination number is determined to be a registered user but is offline, the message to be received is cached as an offline message. This disclosure implements message interaction authentication based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as a native mobile phone. It achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0175] Figure 14This is a flowchart illustrating a cloud phone login authentication method according to another exemplary embodiment. The executing entity of the cloud phone login authentication method in this embodiment is the cloud phone login authentication device provided in this embodiment. This cloud phone login authentication device can be installed in an electronic device, such as a cloud phone platform message client installed in a cloud phone platform, to execute the cloud phone login authentication method of this embodiment. Figure 14 As shown, the cloud phone login authentication method of this disclosure embodiment may specifically include the following steps:

[0176] S1401, Receive the 5G message single sign-on token sent by the cloud phone client. The 5G message single sign-on token is generated by the cloud phone platform after successful login on the cloud phone client. The 5G message single sign-on token corresponds to the user number of the currently logged-in registered user.

[0177] S1402, a single sign-on authentication request is sent to the 5G Messaging Cloud Service Platform. The single sign-on authentication request includes a 5G Messaging single sign-on token.

[0178] S1403, Receive the message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G Messaging Cloud Service Platform. The message session authentication identifier corresponding to the user number of the currently logged-in registered user is generated by the 5G Messaging Cloud Service Platform after receiving the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token sent by the Cloud Phone Platform according to the Single Sign-On Authentication Request.

[0179] S1404, cache the message session authentication identifier corresponding to the user number of the registered user.

[0180] It should be noted here that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie.

[0181] In this embodiment of the disclosure, the specific process of each of the above steps can be found in the above description. Figure 11 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0182] In summary, the cloud phone login authentication method provided in this disclosure caches authentication information through single sign-on and authorization mechanisms for subsequent interactive authentication in message sending and receiving processes. This disclosure achieves message interaction authentication based on the cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. It realizes the cloud phone's messaging function being migrated to the cloud, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0183] Figure 15This is a flowchart illustrating a cloud phone login authentication method according to another exemplary embodiment. The executing entity of the cloud phone login authentication method in this embodiment is the cloud phone login authentication device provided in this embodiment. This cloud phone login authentication device can be installed in an electronic device, such as a cloud phone platform, to execute the cloud phone login authentication method of this embodiment. Figure 15 As shown, the cloud phone login authentication method of this disclosure embodiment may specifically include the following steps:

[0184] S1501 receives a single sign-on authentication request sent by the 5G Messaging Cloud Service Platform. The single sign-on authentication request includes a 5G Messaging single sign-on token.

[0185] S1502, authenticates the 5G message single sign-on token.

[0186] S1503 After authentication is successful, the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token is sent to the 5G Messaging Cloud Service Platform. The 5G Messaging Cloud Service Platform generates a message session authentication identifier corresponding to the user number of the registered user, caches the message session authentication identifier corresponding to the user number of the registered user as authentication information, and sends the message session authentication identifier corresponding to the user number of the registered user to the cloud phone platform message client for caching.

[0187] Prior to step S1501, "receiving the single sign-on authentication request sent by the 5G messaging cloud service platform", the cloud phone login authentication method of this embodiment further includes the following steps:

[0188] Receive login requests from cloud phone clients, including the user's number requesting login; after successful login on the cloud phone client, generate a 5G messaging single sign-on token corresponding to the user's number; send the 5G messaging single sign-on token to the 5G messaging cloud service platform through the cloud phone client and the cloud phone platform messaging client.

[0189] It should be noted here that the message session authentication identifier may include, but is not limited to, a message session authentication token or a message session authentication cookie.

[0190] In this embodiment of the disclosure, the specific process of each of the above steps can be found in the above description. Figure 11 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0191] In summary, the cloud phone login authentication method provided in this disclosure caches authentication information through single sign-on and authorization mechanisms for subsequent interactive authentication in message sending and receiving processes. This disclosure achieves message interaction authentication based on the cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. It realizes the cloud phone's messaging function being migrated to the cloud, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0192] To clearly illustrate the message processing method of the embodiments of this disclosure, the following is combined with... Figure 16 The signaling interaction diagram shown illustrates an exemplary implementation of the message processing method according to an embodiment of this disclosure. For example... Figure 16 As shown, the message processing method of this disclosure includes:

[0193] S1601, the cloud phone platform message client sends a message sending request to the 5G message cloud service platform. The message sending request includes the message to be sent, the message session authentication identifier of the online user, and the destination number of the message to be sent.

[0194] S1602, the 5G messaging cloud service platform performs the first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

[0195] S1603: After the first verification is passed, the 5G messaging cloud service platform stores the message to be sent in the message queue corresponding to the user's number.

[0196] S1604, the 5G messaging cloud service platform sends message retrieval notification messages to the cloud phone platform messaging client.

[0197] S1605, the cloud phone platform message client sends a message retrieval request to the 5G message cloud service platform, and the message retrieval request includes a message session authentication identifier.

[0198] S1606, the 5G messaging cloud service platform performs a second verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

[0199] S1607, after the second verification is passed, the 5G messaging cloud service platform sends the message to be sent to the cloud phone platform messaging client.

[0200] S1608, the cloud phone platform message client displays messages to be sent and sends these messages to online users' cloud phone clients for display.

[0201] S1609, the 5G messaging cloud service platform sends the message to be sent and the destination number to the 5G messaging center to which the destination number belongs.

[0202] S1610, the 5G messaging center sends the message to be sent to the mobile terminal or messaging platform corresponding to the destination number.

[0203] To clearly illustrate the message processing method of the embodiments of this disclosure, the following is combined with... Figure 17 The signaling interaction diagram shown illustrates an exemplary implementation of the message processing method according to an embodiment of this disclosure. For example... Figure 17 As shown, the message processing method of this disclosure includes:

[0204] S1701, the 5G messaging center sends a message synchronization request to the 5G messaging cloud service platform. The message synchronization request includes the message to be received and the destination number.

[0205] S1702, if the 5G messaging cloud service platform determines that the user corresponding to the destination number is an unregistered user based on the user number of the registered user in the authentication information, then the message to be received will be discarded.

[0206] S1703, the 5G messaging cloud service platform determines that the user corresponding to the destination number is a registered user but is offline based on the user number of the registered user in the authentication information, and then caches the message to be received as an offline message.

[0207] S1704, the 5G messaging cloud service platform determines that the user corresponding to the destination number is a registered user based on the user number of the registered user in the authentication information, and if the user corresponding to the destination number is online, then it sends a message retrieval notification message to the cloud phone platform message client.

[0208] S1705, the cloud phone platform message client sends a message retrieval request to the 5G message cloud service platform. The message retrieval request includes the message session authentication identifier of the user corresponding to the destination number.

[0209] S1706, the 5G messaging cloud service platform performs a third verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

[0210] S1707: After the third verification is passed, the 5G messaging cloud service platform will send the message to be received to the cloud phone platform message client.

[0211] S1708, the cloud phone platform message client displays messages to be received and sends these messages to online users' cloud phone clients for display.

[0212] To clearly illustrate the cloud phone login authentication method of this disclosure embodiment, the following is combined with... Figure 18 The signaling interaction diagram shown illustrates an exemplary implementation of the cloud phone login authentication method according to an embodiment of this disclosure. For example... Figure 18 As shown, the cloud phone login authentication method of this disclosure includes:

[0213] S1801, the cloud phone client sends a login request to the cloud phone platform. The login request includes the user's number and user information.

[0214] S1802, the cloud phone platform authenticates the user information in the login request. If it successfully identifies the currently logged-in user corresponding to the requested user number, the cloud phone client login is successful. The single sign-on module in the cloud phone platform generates a 5G message single sign-on token corresponding to the requested user number.

[0215] S1803, the single sign-on module in the cloud phone platform sends the 5G message single sign-on token to the cloud phone client.

[0216] S1804, the cloud phone client determines the currently logged-in user's number and sends the 5G message single sign-on token to the cloud phone platform message client.

[0217] S1805, the cloud phone platform messaging client sends a single sign-on authentication request to the 5G messaging cloud service platform, and the single sign-on authentication request includes a 5G messaging single sign-on token.

[0218] S1806, the 5G Messaging Cloud Service Platform sends a single sign-on authentication request to the cloud phone platform.

[0219] S1807, the cloud phone platform authenticates the 5G Messaging Single Sign-On Token in the Single Sign-On Authentication Request. After successful authentication, the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token is sent to the 5G Messaging Cloud Service Platform.

[0220] S1808, the 5G Messaging Cloud Service Platform assigns a corresponding message session authentication identifier to the registered user's number for this login session, and caches the message session authentication identifier corresponding to the registered user's number as authentication information.

[0221] S1809, the 5G messaging cloud service platform sends the message session authentication identifier corresponding to the registered user's number to the cloud phone platform message client for caching.

[0222] Figure 19 This is a block diagram illustrating a message processing apparatus according to an exemplary embodiment. Figure 19As shown, the message processing device 1900 of this embodiment may specifically include: a first receiving module 1901, a first acquiring module 1902, a first verification module 1903, and a first sending module 1904.

[0223] The first receiving module 1901 is used to receive a message sending request sent by a message client set in the cloud phone platform. The message sending request includes the message to be sent, the message session authentication identifier of the online user, and the destination number of the message to be sent.

[0224] The first acquisition module 1902 is used to acquire cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0225] The first verification module 1903 is used to perform a first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user.

[0226] The first sending module 1904 is used to send the message to be sent and the destination number to the 5G message center to which the destination number belongs after the first verification is passed, so that the 5G message center can send the message to be sent to the mobile terminal or message platform corresponding to the destination number.

[0227] In one embodiment of this disclosure, the first sending module 1904 is further configured to: after the first verification is passed, send the response message of the first verification to the cloud mobile platform message client so that the cloud mobile platform message client can display the message to be sent, and send the message to be sent to the cloud mobile client of the online user for display.

[0228] In one embodiment of this disclosure, the first sending module 1904 is further configured to: after the first verification passes, send a message retrieval notification message to the cloud mobile platform message client; receive a message retrieval request sent by the cloud mobile platform message client, the message retrieval request including a message session authentication identifier; perform a second verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user; after the second verification passes, send the message to be sent to the cloud mobile platform message client so that the cloud mobile platform message client can display the message to be sent, and send the message to be sent to the cloud mobile client of the online user for display.

[0229] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, the message to be sent is an SMS or a 5G message.

[0230] In one embodiment of this disclosure, the first sending module 1904 is further configured to: store the message to be sent in the message queue corresponding to the user number before sending the message to be sent to the 5G message center to which the destination number belongs.

[0231] In the embodiments disclosed herein, the specific manner in which each module in the message processing apparatus of the above embodiments performs its operations has been described in detail in the embodiments relating to the message processing method, and will not be repeated here.

[0232] In summary, the message processing apparatus provided in this disclosure, during the message initiation process of a cloud phone, involves a 5G messaging cloud service platform within the basic messaging platform verifying the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. Upon successful verification, the cloud phone initiates the message and sends it through the 5G messaging center to the mobile terminal or messaging platform corresponding to the destination number. It also notifies the cloud phone platform message client to display the message initiated by the cloud phone either by pulling or by direct display. This disclosure implements message interaction authentication based on cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. This achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0233] Figure 20 This is a block diagram illustrating a message processing apparatus according to an exemplary embodiment. Figure 20 As shown, the message processing device 1900 of this embodiment may specifically include: a second receiving module 2001, a second acquiring module 2002, and a second sending module 2003.

[0234] The second receiving module 2001 is used to receive message synchronization requests sent by the 5G message center. The message synchronization request includes the message to be received and the destination number.

[0235] The second acquisition module 2002 is used to acquire cached authentication information, which includes the message session authentication identifier corresponding to the user number of the registered user.

[0236] The second sending module 2003 is used to determine that the user corresponding to the destination number is a registered user based on the user number of the registered user, and that the user corresponding to the destination number is online. Then, it sends the message to be received to the cloud mobile platform message client set in the cloud mobile platform so that the cloud mobile platform message client can display the message to be received, and sends the message to be received to the cloud mobile client of the user corresponding to the destination number for display.

[0237] In one embodiment of this disclosure, the second sending module 2003 is further configured to: determine, based on the user number of the registered user, that the user corresponding to the destination number is a registered user and that the user corresponding to the destination number is online, then send a message retrieval notification message to the cloud mobile platform message client; receive a message retrieval request sent by the cloud mobile platform message client, the message retrieval request including the message session authentication identifier of the user corresponding to the destination number; perform a third verification on the received message session authentication identifier based on the cached message session authentication identifier corresponding to the user number of the registered user; and after the third verification passes, send the message to be received to the cloud mobile platform message client.

[0238] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, the message to be received is an SMS or a 5G message.

[0239] In one embodiment of this disclosure, the second sending module 2003 is further configured to: if the user corresponding to the destination number is determined to be an unregistered user based on the user number of a registered user, then discard the message to be received.

[0240] In one embodiment of this disclosure, the second sending module 2003 is further configured to: determine that the user corresponding to the destination number is a registered user based on the user number of the registered user, and if the user corresponding to the destination number is in an offline state, then cache the message to be received in the form of an offline message.

[0241] In the embodiments disclosed herein, the specific manner in which each module in the message processing apparatus of the above embodiments performs its operations has been described in detail in the embodiments relating to the message processing method, and will not be repeated here.

[0242] In summary, the message processing apparatus provided in the embodiments of this disclosure, during the message receiving process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform. Based on cached authentication information, the platform determines whether the user corresponding to the destination number sent by the cloud phone platform message client is a registered user and is online. If the user is confirmed to be registered and online, the message to be received is sent to the corresponding cloud phone platform message client for display. The platform also pushes the message to be received to the corresponding cloud phone client for display. If the user is not registered, the message is discarded. If the user is registered but offline, the message is cached as an offline message. This embodiment of the disclosure implements message interaction authentication based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as a native mobile phone. This achieves cloud-based messaging functionality for cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0243] Figure 21 This is a block diagram illustrating a cloud phone login authentication device according to an exemplary embodiment. Figure 21 As shown, the cloud phone login authentication device 2100 of this embodiment may specifically include: a third receiving module 2101, a third sending module 2102, a fourth receiving module 2103, a first generating module 2104, and a fourth sending module 2105.

[0244] The third receiving module 2101 is used to receive a single sign-on authentication request sent by the cloud phone platform message client set in the cloud phone platform. The single sign-on authentication request includes a 5G message single sign-on token, which is sent by the cloud phone platform to the cloud phone platform message client through the cloud phone client.

[0245] The third sending module 2102 is used to send the single sign-on authentication request to the cloud phone platform.

[0246] The fourth receiving module 2103 is used to receive the user number of the registered user corresponding to the 5G message single sign-on token sent by the cloud phone platform. The user number of the registered user corresponding to the 5G message single sign-on token is sent by the cloud phone platform after the 5G message single sign-on token is authenticated.

[0247] The first generation module 2104 is used to generate a message session authentication identifier corresponding to the user number of a registered user, and cache the message session authentication identifier corresponding to the user number of a registered user as authentication information.

[0248] The fourth sending module 2105 is used to send the message session authentication identifier corresponding to the user number of the registered user to the cloud mobile phone platform message client for caching.

[0249] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie.

[0250] In the embodiments disclosed herein, the specific methods by which each module in the cloud phone login authentication device of the above embodiments performs its operations have been described in detail in the embodiments relating to the cloud phone login authentication method, and will not be repeated here.

[0251] In summary, the cloud phone login authentication device provided in this disclosure caches authentication information through single sign-on and authorization mechanisms for subsequent interactive authentication in message sending and receiving processes. This disclosure achieves message interaction authentication based on the cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. This realizes the cloud-based messaging functionality of cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0252] Figure 22 This is a block diagram illustrating a message processing apparatus according to an exemplary embodiment. Figure 19 As shown, the message processing apparatus 1900 of this embodiment may specifically include: a second generation module 2201 and a fifth sending module 2202.

[0253] The second generation module 2201 is used to generate a message sending request, which includes the message to be sent, the message session authentication identifier of the online user, and the destination number of the message to be sent.

[0254] The fifth sending module 2202 is used to send a message sending request to the 5G messaging cloud service platform, so that the 5G messaging cloud service platform can perform a first verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the cached authentication information, and after the first verification is passed, send the message to be sent to the mobile terminal or messaging platform corresponding to the destination number through the 5G messaging center to which the destination number belongs.

[0255] In one embodiment of this disclosure, the fifth sending module 2202 is further configured to: receive a first verification passed response message sent by the 5G Messaging Cloud Service Platform, wherein the first verification passed response message is generated by the 5G Messaging Cloud Service Platform after the first verification is passed; display the message to be sent; and send the message to be sent to the cloud mobile client of the online user for display.

[0256] In one embodiment of this disclosure, the fifth sending module 2202 is further configured to: receive a message retrieval notification message sent by the 5G Messaging Cloud Service Platform; send a message retrieval request to the 5G Messaging Cloud Service Platform, the message retrieval request including a message session authentication identifier; receive a message to be sent sent by the 5G Messaging Cloud Service Platform, the message to be sent being sent after the 5G Messaging Cloud Service Platform performs a second verification on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user; display the message to be sent; and send the message to be sent to the cloud mobile client of the online user for display.

[0257] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, the message to be sent is an SMS or a 5G message.

[0258] In the embodiments disclosed herein, the specific manner in which each module in the message processing apparatus of the above embodiments performs its operations has been described in detail in the embodiments relating to the message processing method, and will not be repeated here.

[0259] In summary, the message processing apparatus provided in this disclosure, during the message initiation process of a cloud phone, involves a 5G messaging cloud service platform within the basic messaging platform verifying the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. Upon successful verification, the cloud phone initiates the message and sends it through the 5G messaging center to the mobile terminal or messaging platform corresponding to the destination number. It also notifies the cloud phone platform message client to display the message initiated by the cloud phone either by pulling or by direct display. This disclosure implements message interaction authentication based on cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. This achieves cloud-based messaging functionality for cloud phones, resolving the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0260] Figure 23 This is a block diagram illustrating a message processing apparatus according to an exemplary embodiment. Figure 23 As shown, the message processing device 1900 of this embodiment may specifically include: a fifth receiving module 2301, a first display module 2302 and a sixth sending module 2303.

[0261] The fifth receiving module 2301 is used to receive messages to be received sent by the 5G Messaging Cloud Service Platform. The messages to be received are sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request sent by the 5G Messaging Center, and after determining that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online. The message synchronization request includes the messages to be received and the destination number.

[0262] The first display module 2302 is used to display messages to be received.

[0263] The sixth sending module 2303 is used to send the message to be received to the cloud mobile client of the user corresponding to the destination number for display.

[0264] In one embodiment of this disclosure, the fifth receiving module 2301 is further configured to: receive a message retrieval notification message sent by the 5G Messaging Cloud Service Platform, wherein the message retrieval notification message is sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request sent by the 5G Messaging Center, and after determining that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online; send a message retrieval request to the 5G Messaging Cloud Service Platform, wherein the message retrieval request includes the message session authentication identifier of the user corresponding to the destination number; and receive a message to be received sent by the 5G Messaging Cloud Service Platform, wherein the message to be received is sent by the 5G Messaging Cloud Service Platform after passing the third verification of the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

[0265] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, the message to be received is an SMS or a 5G message.

[0266] In the embodiments disclosed herein, the specific manner in which each module in the message processing apparatus of the above embodiments performs its operations has been described in detail in the embodiments relating to the message processing method, and will not be repeated here.

[0267] In summary, the message processing apparatus provided in the embodiments of this disclosure, during the message receiving process of a cloud phone, involves a 5G messaging cloud service platform set up in the basic messaging platform. Based on cached authentication information, the platform determines whether the user corresponding to the destination number sent by the cloud phone platform message client is a registered user and is online. If the user is confirmed to be registered and online, the message to be received is sent to the corresponding cloud phone platform message client for display. The platform also pushes the message to be received to the corresponding cloud phone client for display. If the user is not registered, the message is discarded. If the user is registered but offline, the message is cached as an offline message. This embodiment of the disclosure implements message interaction authentication based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with a consistent experience as a native mobile phone. This achieves cloud-based messaging functionality for cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0268] Figure 24 This is a block diagram illustrating a cloud phone login authentication device according to an exemplary embodiment. Figure 24 As shown, the cloud phone login authentication device 2100 of this embodiment may specifically include: a sixth receiving module 2401, a seventh sending module 2402, a seventh receiving module 2403 and a cache module 2404.

[0269] The sixth receiving module 2401 is used to receive the 5G message single sign-on token sent by the cloud mobile client. The 5G message single sign-on token is generated by the cloud mobile platform after the cloud mobile client successfully logs in. The 5G message single sign-on token corresponds to the user number of the currently logged-in registered user.

[0270] The seventh sending module 2402 is used to send a single sign-on authentication request to the 5G Messaging Cloud Service Platform. The single sign-on authentication request includes a 5G Messaging single sign-on token.

[0271] The seventh receiving module 2403 is used to receive the message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G Messaging Cloud Service Platform. The message session authentication identifier corresponding to the user number of the currently logged-in registered user is generated by the 5G Messaging Cloud Service Platform after receiving the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token sent by the cloud mobile phone platform according to the Single Sign-On Authentication Request.

[0272] The caching module 2404 is used to cache the message session authentication identifier corresponding to the user number of a registered user.

[0273] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie.

[0274] In the embodiments disclosed herein, the specific methods by which each module in the cloud phone login authentication device of the above embodiments performs its operations have been described in detail in the embodiments relating to the cloud phone login authentication method, and will not be repeated here.

[0275] In summary, the cloud phone login authentication device provided in this disclosure caches authentication information through single sign-on and authorization mechanisms for subsequent interactive authentication in message sending and receiving processes. This disclosure achieves message interaction authentication based on the cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. This realizes the cloud-based messaging functionality of cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0276] Figure 25 This is a block diagram illustrating a cloud phone login authentication device according to an exemplary embodiment. Figure 25 As shown, the cloud phone login authentication device 2100 of this embodiment may specifically include: an eighth receiving module 2501, an authentication module 2502 and an eighth sending module 2503.

[0277] The eighth receiving module 2501 is used to receive a single sign-on authentication request sent by the 5G Messaging Cloud Service Platform. The single sign-on authentication request includes a 5G Messaging single sign-on token.

[0278] The authentication module 2502 is used to authenticate the 5G message single sign-on token.

[0279] The eighth sending module 2503 is used to send the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token to the 5G Messaging Cloud Service Platform after authentication is successful. This allows the 5G Messaging Cloud Service Platform to generate a message session authentication identifier corresponding to the user number of the registered user, cache the message session authentication identifier corresponding to the user number of the registered user as authentication information, and send the message session authentication identifier corresponding to the user number of the registered user to the cloud phone platform message client for caching.

[0280] In one embodiment of this disclosure, the message session authentication identifier is a message session authentication token or a message session authentication cookie.

[0281] In one embodiment of this disclosure, the eighth receiving module 2501 is further configured to: receive a login request sent by a cloud mobile client before receiving a single sign-on authentication request sent by the 5G Messaging Cloud Service Platform, wherein the login request includes the user number requesting login; generate a 5G Messaging single sign-on token corresponding to the user number after the cloud mobile client successfully logs in; and send the 5G Messaging Single Sign-on Token to the 5G Messaging Cloud Service Platform through the cloud mobile client and the cloud mobile platform messaging client.

[0282] In the embodiments disclosed herein, the specific methods by which each module in the cloud phone login authentication device of the above embodiments performs its operations have been described in detail in the embodiments relating to the cloud phone login authentication method, and will not be repeated here.

[0283] In summary, the cloud phone login authentication device provided in this disclosure caches authentication information through single sign-on and authorization mechanisms for subsequent interactive authentication in message sending and receiving processes. This disclosure achieves message interaction authentication based on the cached authentication information, enabling cloud phone clients to use 5G messaging and SMS services with a consistent experience as native mobile phones. This realizes the cloud-based messaging functionality of cloud phones and solves the problem of limited or missing messaging functions caused by the dependency and limitations of cloud phone and local phone permissions.

[0284] Figure 26 This is a block diagram illustrating an electronic device 2600 according to an exemplary embodiment.

[0285] like Figure 26 As shown, the above-mentioned electronic device 2600 includes:

[0286] The memory 2601 and the processor 2602 are connected by a bus 2603 that connects different components (including the memory 2601 and the processor 2602). The memory 2601 stores a computer program. When the processor 2602 executes the program, it implements the message processing method or the cloud phone login authentication method of the present disclosure embodiment.

[0287] Bus 2603 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0288] Electronic device 2600 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by electronic device 2600, including volatile and non-volatile media, removable and non-removable media.

[0289] Memory 2601 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 2604 and / or cache memory 2605. Electronic device 2600 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 2606 can be used to read and write non-removable, non-volatile magnetic media (… Figure 26 Not shown; usually referred to as a "hard drive"). Although Figure 26 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 2603 via one or more data media interfaces. Memory 2601 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this disclosure.

[0290] A program / utility 2608 having a set (at least one) of program modules 2607 may be stored, for example, in memory 2601. Such program modules 2607 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 2607 typically perform the functions and / or methods described in the embodiments of this disclosure.

[0291] Electronic device 2600 can also communicate with one or more external devices 2609 (e.g., keyboard, pointing device, display 2611, etc.), and with one or more devices that enable a user to interact with the electronic device 2600, and / or with any device that enables the electronic device 2600 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 2612. Furthermore, electronic device 2600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 2613. Figure 26As shown, network adapter 2613 communicates with other modules of electronic device 2600 via bus 2603. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 2600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0292] The processor 2602 performs various functional applications and data processing by running programs stored in the memory 2601.

[0293] It should be noted that the implementation process and technical principles of the electronic device in this embodiment are explained in the foregoing description of the message processing method or cloud phone login authentication method of this disclosure embodiment, and will not be repeated here.

[0294] In the electronic device provided in this embodiment, during the message initiation process of a cloud phone, the 5G messaging cloud service platform set in the basic messaging platform verifies the message session authentication identifier sent by the cloud phone platform message client based on cached authentication information. After successful verification, the message initiated by the cloud phone is sent to the mobile terminal or messaging platform corresponding to the destination number through the 5G messaging center. During the message reception process of the cloud phone, the 5G messaging cloud service platform, based on cached authentication information, determines that the user corresponding to the destination number sent by the 5G messaging center is a registered user who is online. Upon this determination, the platform sends the message to be received to the cloud phone platform message client, which then displays the message and forwards it to the cloud phone client corresponding to the destination number for display. In the cloud phone login authentication process, authentication information is cached through single sign-on and authorization mechanisms for use in subsequent message sending and receiving processes. This embodiment of the disclosure implements authentication for message interaction based on cached authentication information, enabling the use of 5G messaging and SMS services on the cloud phone client with the same experience as the native mobile phone. It realizes the cloud phone's messaging function on the cloud and solves the problem of limited or missing messaging functions caused by the dependence and limitation of cloud phone and local phone permissions.

[0295] To implement the above embodiments, this disclosure also proposes a computer-readable storage medium.

[0296] When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the message processing method or the cloud phone login authentication method as described above. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, or optical data storage device, etc.

[0297] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0298] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A message processing method, characterized in that, include: Receive a message synchronization request sent by the 5G message center, wherein the message synchronization request includes the message to be received and the destination number; Obtain cached authentication information, which includes a message session authentication identifier corresponding to the user number of a registered user; If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is online, then the message to be received is sent to the cloud phone platform message client set in the cloud phone platform, so that the cloud phone platform message client can display the message to be received, and the message to be received is sent to the cloud phone client of the user corresponding to the destination number for display.

2. The method according to claim 1, characterized in that, The step of determining that the user corresponding to the destination number is a registered user based on the user number of the registered user, and that the user corresponding to the destination number is online, then sending the message to be received to the cloud phone platform message client set in the cloud phone platform includes: If the user corresponding to the target number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the target number is online, then a message retrieval notification message will be sent to the cloud mobile platform message client. Receive a message retrieval request sent by the cloud mobile platform message client, wherein the message retrieval request includes the message session authentication identifier of the user corresponding to the destination number; A third verification is performed on the received message session authentication identifier based on the message session authentication identifier corresponding to the user number of the registered user in the cache; After the third verification is passed, the message to be received is sent to the cloud mobile platform message client.

3. The method according to claim 2, characterized in that, The message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, The message to be received is either an SMS or a 5G message.

4. The method according to claim 1, characterized in that, Also includes: If the user corresponding to the destination number is determined to be an unregistered user based on the user number of the registered user, then the message to be received is discarded.

5. The method according to claim 1, characterized in that, Also includes: If the user corresponding to the destination number is determined to be a registered user based on the user number of the registered user, and the user corresponding to the destination number is in an offline state, then the message to be received is cached as an offline message.

6. A cloud phone login authentication method, characterized in that, include: Receive a single sign-on authentication request sent by a cloud phone platform message client set in the cloud phone platform, wherein the single sign-on authentication request includes a 5G message single sign-on token, wherein the 5G message single sign-on token is sent by the cloud phone platform to the cloud phone platform message client through the cloud phone client; The single sign-on authentication request is sent to the cloud mobile platform; The cloud phone platform receives the user number of the registered user corresponding to the 5G message single sign-on token, which is sent by the cloud phone platform after the cloud phone platform has authenticated the received 5G message single sign-on token. Generate a message session authentication identifier corresponding to the user number of the registered user, and cache the message session authentication identifier corresponding to the user number of the registered user as authentication information; The message session authentication identifier corresponding to the registered user's user number is sent to the cloud mobile platform message client for caching.

7. The method according to claim 6, characterized in that, The message session authentication identifier is either a message session authentication token or a message session authentication cookie.

8. A message processing method, characterized in that, include: The system receives a message to be received from the 5G Messaging Cloud Service Platform. The message to be received is sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request from the 5G Messaging Center. The platform determines that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online. The message synchronization request includes the message to be received and the destination number. Display the message to be received; The message to be received is sent to the cloud mobile client of the user corresponding to the destination number for display.

9. The method according to claim 8, characterized in that, The message to be received from the 5G messaging cloud service platform includes: The system receives a message retrieval notification message sent by the 5G Messaging Cloud Service Platform. The message retrieval notification message is sent by the 5G Messaging Cloud Service Platform after receiving the message synchronization request sent by the 5G Messaging Center, and after determining that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online. A message retrieval request is sent to the 5G message cloud service platform, and the message retrieval request includes the message session authentication identifier of the user corresponding to the destination number; The system receives the message to be received from the 5G Messaging Cloud Service Platform. The message to be received is sent by the 5G Messaging Cloud Service Platform after the third verification of the received message session authentication identifier is passed, based on the message session authentication identifier corresponding to the user number of the registered user in the authentication information.

10. The method according to claim 9, characterized in that, The message session authentication identifier is a message session authentication token or a message session authentication cookie; and / or, The message to be received is either an SMS or a 5G message.

11. A cloud phone login authentication method, characterized in that, include: Receive a 5G message single sign-on token sent by the cloud phone client. The 5G message single sign-on token is generated by the cloud phone platform after the cloud phone client successfully logs in. The 5G message single sign-on token corresponds to the user number of the currently logged-in registered user. A single sign-on authentication request is sent to the 5G Messaging Cloud Service Platform, and the single sign-on authentication request includes the 5G Messaging Single Sign-on Token. The system receives a message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G Messaging Cloud Service Platform. The message session authentication identifier corresponding to the user number of the currently logged-in registered user is generated by the 5G Messaging Cloud Service Platform after receiving the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token sent by the Cloud Phone Platform in accordance with the Single Sign-On Authentication Request. Cache the message session authentication identifier corresponding to the user number of the registered user.

12. The method according to claim 11, characterized in that, The message session authentication identifier is either a message session authentication token or a message session authentication cookie.

13. A cloud phone login authentication method, characterized in that, include: Receive a single sign-on authentication request sent by the 5G Messaging Cloud Service Platform, wherein the single sign-on authentication request includes a 5G Messaging single sign-on token; Authenticate the 5G message single sign-on token; After successful authentication, the user number of the currently logged-in registered user corresponding to the 5G Messaging Single Sign-On Token is sent to the 5G Messaging Cloud Service Platform. The 5G Messaging Cloud Service Platform generates a message session authentication identifier corresponding to the user number of the registered user, caches the message session authentication identifier corresponding to the user number of the registered user as authentication information, and sends the message session authentication identifier corresponding to the user number of the registered user to the cloud mobile phone platform message client for caching.

14. The method according to claim 13, characterized in that, The message session authentication identifier is either a message session authentication token or a message session authentication cookie.

15. The method according to claim 13, characterized in that, Before receiving the single sign-on authentication request sent by the 5G messaging cloud service platform, the process also includes: Receive a login request sent by a cloud mobile client, wherein the login request includes the user number requesting login; After successful login to the cloud mobile client, a 5G message single sign-on token corresponding to the user's number is generated; The 5G messaging single sign-on token is sent to the 5G messaging cloud service platform via the cloud phone client and the cloud phone platform messaging client.

16. A message processing apparatus, characterized in that, include: The second receiving module is used to receive a message synchronization request sent by the 5G message center. The message synchronization request includes the message to be received and the destination number. The second acquisition module is used to acquire cached authentication information, which includes a message session authentication identifier corresponding to the user number of a registered user. The second sending module is used to determine, based on the user number of the registered user, that the user corresponding to the destination number is a registered user and that the user corresponding to the destination number is online. If so, the module sends the message to be received to the cloud phone platform message client set in the cloud phone platform so that the cloud phone platform message client can display the message to be received, and sends the message to be received to the cloud phone client of the user corresponding to the destination number for display.

17. A cloud phone login authentication device, characterized in that, include: The third receiving module is used to receive a single sign-on authentication request sent by the cloud phone platform message client set in the cloud phone platform. The single sign-on authentication request includes a 5G message single sign-on token, which is sent by the cloud phone platform to the cloud phone platform message client through the cloud phone client. The third sending module is used to send the single sign-on authentication request to the cloud mobile phone platform; The fourth receiving module is used to receive the user number of the registered user corresponding to the 5G message single sign-on token sent by the cloud mobile phone platform. The user number of the registered user corresponding to the 5G message single sign-on token is sent by the cloud mobile phone platform after the 5G message single sign-on token has been authenticated. The first generation module is used to generate a message session authentication identifier corresponding to the user number of the registered user, and cache the message session authentication identifier corresponding to the user number of the registered user as authentication information; The fourth sending module is used to send the message session authentication identifier corresponding to the user number of the registered user to the cloud mobile phone platform message client for caching.

18. A message processing apparatus, characterized in that, include: The fifth receiving module is used to receive a message to be received sent by the 5G Messaging Cloud Service Platform. The message to be received is sent by the 5G Messaging Cloud Service Platform after receiving a message synchronization request sent by the 5G Messaging Center, and after determining that the user corresponding to the destination number is a registered user based on the user number of the registered user in the cached authentication information, and that the user corresponding to the destination number is online. The message synchronization request includes the message to be received and the destination number. The first display module is used to display the message to be received; The sixth sending module is used to send the message to be received to the cloud mobile client of the user corresponding to the destination number for display.

19. A cloud phone login authentication device, characterized in that, include: The sixth receiving module is used to receive a 5G message single sign-on token sent by the cloud mobile client. The 5G message single sign-on token is generated by the cloud mobile platform after the cloud mobile client successfully logs in. The 5G message single sign-on token corresponds to the user number of the currently logged-in registered user. The seventh sending module is used to send a single sign-on authentication request to the 5G Messaging Cloud Service Platform, wherein the single sign-on authentication request includes the 5G Messaging Single Sign-on Token; The seventh receiving module is used to receive the message session authentication identifier corresponding to the user number of the currently logged-in registered user sent by the 5G messaging cloud service platform. The message session authentication identifier corresponding to the user number of the currently logged-in registered user is generated by the 5G messaging cloud service platform after receiving the user number of the currently logged-in registered user corresponding to the 5G messaging single sign-on token sent by the cloud mobile phone platform according to the single sign-on authentication request. The caching module is used to cache the message session authentication identifier corresponding to the user number of the registered user.

20. A cloud phone login authentication device, characterized in that, include: The eighth receiving module is used to receive a single sign-on authentication request sent by the 5G Messaging Cloud Service Platform, wherein the single sign-on authentication request includes a 5G Messaging Single Sign-on Token. The authentication module is used to authenticate the 5G message single sign-on token; The eighth sending module is used to send the user number of the currently logged-in registered user corresponding to the 5G message single sign-on token to the 5G message cloud service platform after authentication is successful. This allows the 5G message cloud service platform to generate a message session authentication identifier corresponding to the user number of the registered user, cache the message session authentication identifier corresponding to the user number of the registered user as authentication information, and send the message session authentication identifier corresponding to the user number of the registered user to the cloud mobile phone platform message client for caching.

21. An electronic device, characterized in that, include: processor; Memory for storing the executable instructions of the processor; The processor is configured to execute the instructions to implement the message processing method as described in any one of claims 1-5, or the cloud phone login authentication method as described in any one of claims 6-7, or the message processing method as described in any one of claims 8-10, or the cloud phone login authentication method as described in any one of claims 11-12, or the cloud phone login authentication method as described in any one of claims 13-15.

22. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the message processing method as described in any one of claims 1-5, or the cloud mobile phone login authentication method as described in any one of claims 6-7, or the message processing method as described in any one of claims 8-10, or the cloud mobile phone login authentication method as described in any one of claims 11-12, or the cloud mobile phone login authentication method as described in any one of claims 13-15.

Images