CN115002689A - Communication method of 5G message and network element for 5G message communication - Google Patents
Communication method of 5G message and network element for 5G message communication Download PDFInfo
- Publication number
- CN115002689A CN115002689A CN202111151196.0A CN202111151196A CN115002689A CN 115002689 A CN115002689 A CN 115002689A CN 202111151196 A CN202111151196 A CN 202111151196A CN 115002689 A CN115002689 A CN 115002689A
- Authority
- CN
- China
- Prior art keywords
- message
- request message
- terminal device
- request
- robot
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a communication method of a 5G message, which comprises the following steps: receiving a first request message sent by a first message robot, wherein the first request message comprises number information of a sender terminal device associated user and number information of a receiver terminal device associated user; returning a response message of the first request message to the first message robot, wherein the response message carries a message identifier distributed for the first request message; and sending a second request message to a rich media communication service network element, wherein the second request message carries the number information of the associated user of the terminal equipment of the sender, the number information of the associated user of the terminal equipment of the receiver, the message identifier of the first request message and the message content, the second request message is used for indicating the rich media communication service to send a third request message to the terminal equipment of the receiver, and the third request message carries the number information of the associated user of the terminal equipment of the sender, the number information of the associated user of the terminal equipment of the receiver and the message identifier of the first request message.
Description
Technical Field
The present invention relates to the field of mobile communications technologies, and in particular, to a 5G message communication method and a network element for 5G message communication.
Background
The operator sms will evolve to Rich media message (RCS) in 5G message, and at present, 3 operators of china mobile, telecommunication, and unicom have jointly issued 5G message services, wherein 2 aspects of the characteristic of upgrading the Rich media message for C-end user and the message for B-end application side traditional port sms to Rich media, i.e. platform (MaaP) industry, message service, raise the attention of each industry.
In the aspect of 5G message characteristics facing a B-end application side, compared with the traditional port short message, a merchant can perform commercial message interaction experience with a user through 5G message MaaP industrial message service, wherein the commercial message interaction experience is richer in commercial information content, more intuitive and higher in safety. Under the RCS standard advocated by the RCS, the MaaP platform provides 5G message gateway type service capability facing application access, and the capability is equivalent to a short message gateway network element of a short message service. Because the standard MaaP characteristic is only formally released for more than 2 years, the basic RCS message interactive content between the focused application and the user is defined by related functions, part of the traditional short message service capability cannot be integrated in the existing MaaP platform network element, and some operator characteristic services cannot be realized under the existing commercial 5G message system for a while, and the upgrade from the existing network service to the 5G message service is also influenced. Therefore, compared with WeChat public numbers and The like, The 5G message has a gap in The service capability provided for industrial application beyond The diversified service of The operator (English: Over The Top, abbreviated as OTT) message.
Taking the number conversion function provided by the short message gateway as an example, the sending party user can send a point-to-point short message to the receiving party user by using a specific application client, namely the short message received by the receiving party user, and the number of the sending party is displayed as the mobile phone number of the user, but not a specific port number).
The authorized application can be connected with a short message gateway, a short message sending request is pushed to a short message center based on the number conversion function of the short message gateway, finally a point-to-point short message with a number indicating the number of a sender mobile phone is sent to a user by the short message center, namely, the short message sent to a receiver by the user through the application is basically consistent with the core experience of the short message sent to the receiver by the user through the mobile phone directly, the receiver can identify the sender source through the source label description in the short message content, the basic communication service capability range of an operator can be expanded through the service form, the short message is sent through a terminal such as a PC, and the method is widely applied to internal services such as 139 postboxes, flyings and the like.
Under the characteristics of 5G message MaaP, based on the interaction of HTTP and SIP protocols, under the standard specification, both the MaaP platform and RCS application follow the RCS standard, the user code number is identified in the form of a Session Initiation Protocol Uniform Resource Identifier (SIP URI), the user side receives the 5G message sent by the application side, and the SIP URI allocated for an application message robot Chatbot is fixedly displayed.
The MaaP platform and the RCS application center carry out routing based on the SIP URI, and the terminal side displays the SIP number of the application distributed for the application system instead of the number of the user of the sender.
The capability of an application side to initiate point-to-point short messages under the traditional port short message service is not supported under the current 5G message standard and the current network service, and the MaaP platform which is used for butting an application system does not have the capability of converting the code number of an application system of a message initiator to a user number. That is, under the 5G message, the user cannot initiate a peer-to-peer rich media 5G message to the recipient user through the client of a specific application.
Therefore, a communication method of 5G messages under the SIP protocol is needed to realize peer-to-peer communication of 5G messages.
Disclosure of Invention
The embodiment of the invention aims to provide a communication method of a 5G message under an SIP protocol, which can realize point-to-point communication of the 5G message.
In order to solve the above technical problem, the embodiment of the present invention is implemented as follows:
in a first aspect, a method for communicating a 5G message is provided, including: receiving a first request message sent by a first message robot, wherein the first request message comprises number information of a sender terminal device associated user, number information of a receiver terminal device associated user, an identifier of the first message robot, message content, a point-to-point application message type and a URI of the first message robot, and the point-to-point application message type is used for indicating the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot; returning a response message of the first request message to the first message robot, wherein the response message carries a message identifier distributed for the first request message; and sending a second request message to a rich media communication service network element, wherein the second request message carries the number information of the user associated with the sender terminal device, the number information of the user associated with the receiver terminal device, the message identifier of the first request message, and the message content, the second request message is used for indicating the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries the number information of the user associated with the sender terminal device, the number information of the user associated with the receiver terminal device, and the message identifier of the first request message.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the second request message further includes a service signature of the first request message.
With reference to the first aspect and the foregoing implementation manner of the first aspect, in a first possible implementation manner of the first aspect, the method further includes: receiving a second request receipt message sent by the rich media communication service, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message; and sending the second request receipt message to the first message robot, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message.
In a second aspect, a method for communicating a 5G message is provided, including: receiving a message, namely a second request message sent by a platform MaaP, wherein the second request message is generated by a first request message sent by a first message robot, and the second request message carries number information of a sender terminal device associated user, number information of a receiver terminal device associated user, a message identifier of the first request message and message content; and sending a third request message to the terminal equipment of the receiving party, wherein the third request message carries the number information of the user associated with the terminal equipment of the sending party, the number information of the user associated with the terminal equipment of the receiving party and the message identifier of the first request message.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: and recording the association relation between the message identification of the first request message and the URI of the first message robot.
With reference to the second aspect and the foregoing implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the method further includes: receiving a first receipt message returned by the terminal device, wherein the first receipt message carries a message identifier of the first request message; and sending a second request receipt message to the MaaP according to the association relation between the message identifier of the first request message and the URI of the first message robot, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message.
With reference to the second aspect and the foregoing implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the second request message further includes a service signature of the first request message.
In a third aspect, a network element for 5G message communication is provided, including: the system comprises a receiving unit, a first message robot and a second message robot, wherein the receiving unit is used for receiving a first request message sent by the first message robot, the first request message comprises number information of a sender terminal device associated user, number information of a receiver terminal device associated user, an identifier of the first message robot, message content, a point-to-point application message type and a URI of the first message robot, and the point-to-point application message type is used for indicating the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot; a sending unit, configured to return a response message of the first request message to the first message robot, where the response message carries a message identifier allocated to the first request message; the sending unit is further configured to send a second request message to a rich media communication service network element, where the second request message carries number information of the sender terminal device associated user, number information of the receiver terminal device associated user, a message identifier of the first request message, and the message content, the second request message is used to instruct the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries the number information of the sender terminal device associated user, the number information of the receiver terminal device associated user, and the message identifier of the first request message.
Optionally, the network element provided in the third aspect is capable of implementing the first aspect or any possible implementation manner of the first aspect.
In a fourth aspect, there is provided a network element for 5G message communication, comprising: a receiving unit, configured to receive a second request message sent by a platform MaaP, where the second request message is generated from a first request message sent by a first message robot, and the second request message carries number information of a user associated with a sender terminal device, number information of a user associated with a receiver terminal device, a message identifier of the first request message, and a message content; a sending unit, configured to send a third request message to the receiving side terminal device, where the third request message carries number information of a user associated with the sending side terminal device, number information of a user associated with the receiving side terminal device, and a message identifier of the first request message.
With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the network element further includes: and the processing unit is used for recording the association relation between the message identifier of the first request message and the URI of the first message robot.
In a fifth aspect, the present application provides a 5G message communication system, where the system includes a sending terminal device, a receiving terminal device, a first communication network element and a second communication network element, where the first communication network element is configured to implement the method according to the first aspect, and the second communication network element is configured to implement the method according to the second aspect.
In a fifth aspect, an embodiment of the present invention provides a network device, including a processor, a communication interface, a memory, and a communication bus; the processor, the communication interface and the memory complete mutual communication through a bus; the memory is used for storing a computer program; the processor is configured to execute the program stored in the memory to implement the method steps according to the first or second aspect.
In a sixth aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method steps according to the first aspect or the second aspect.
The invention provides a method, a network element and a system for realizing the transmission of a 5G message point-to-point message by an application user based on the MaaP characteristic of the 5G message under the existing 5G message standard networking architecture, can realize the self-service capability of transmitting the point-to-point short message to the user, smoothly upgrade to the 5G message service capability, effectively inherit the innovation of an operator in the field of business short messages, help to develop the business message service of the operator, and can derive more application interaction scenes and business modes.
Further, the point-to-point message initiated by the 5G message terminal user belongs to a standard flow, and is processed by following an RCS (remote control system) standard flow mechanism in order to avoid overlarge modification of a 5G message standard network element and a basic service flow, and the mode is consistent with the short message service mode of the current network port.
Furthermore, the proposal does not change the basic network element networking architecture of the 5G message, does not additionally add an intercommunicating network element with an application system in a main application mode facing internal self-service, accesses the MaaP platform by applying Chatbot, and finishes the message interaction of the application and the user end side related to point-to-point messages by the butt joint of the MaaP platform and the RCS AS, so AS to avoid the customized adaptation requirement on the RCS terminal, and the UNI message definition between the RCS AS and the 5G message terminal at the platform side maintains the standardized definition.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flow chart of prior art 5G message communication provided by an embodiment of the present application.
Fig. 2 is a schematic flowchart of a communication method of a 5G message according to an embodiment of the present application.
Fig. 3 is a schematic flowchart of a method for communicating a 5G message according to another embodiment of the present application.
FIG. 4 is a schematic flow chart diagram of a method of one embodiment of the present application.
Fig. 5 is a schematic flow chart of a method according to another embodiment of the present application.
Fig. 6 is a schematic block diagram of a network element for 5G message communication according to an embodiment of the present application.
Fig. 7 is a schematic block diagram of a network element for 5G message communication according to another embodiment of the present application.
Fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application.
Detailed Description
The embodiment of the invention provides a method and a device for configuring network resources and network equipment.
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
AS shown in fig. 1, in the prior art, after a user initiates a peer-to-peer message request through a terminal device, the MaaP platform AS a docking application system does not have a capability of converting a code number of a message initiator application system into a user number, that is, in a 5G message, the user cannot initiate a peer-to-peer rich media 5G message to a receiver user through a client of a specific application, and a calling number received by the receiver is an SIP URI of the application, because peer-to-peer communication of the 5G message cannot be achieved, AS shown in fig. 1, the application system communicates with the MaaP platform through an HTTP protocol, the MaaP platform communicates with an RCS service network element (RAS AS) through an HTTP protocol, and the RCS AS communicates with a receiver terminal device through an SIP protocol.
The method provided by the application does not change a 5G message basic network element networking framework, does not additionally add an intercommunicating network element with an application system in a main application mode facing internal self-service, accesses the MaaP platform by the application Chatbot, finishes the message interaction of the application and the user side related to point-to-point messages by the butt joint of the MaaP platform and the RCS AS, and further maintains the standardized definition of UNI messages between the RCS AS and the 5G message terminal at the platform side in order to avoid the customized adaptation requirement of the RCS terminal.
As shown in fig. 2, an execution subject of the method provided in the embodiment of the present invention may be a MaaP platform deployed on a server, where the server may be an independent server or a server cluster composed of multiple servers, and the server may be a server capable of performing network operation processing, such as a server configured by a certain network resource. The method 200 may specifically include the following steps:
step S210, receiving a first request message sent by a first message robot, where the first request message includes number information of a sender terminal device associated user, number information of a receiver terminal device associated user, an identifier of the first message robot, message content, a point-to-point application message type, and a URI of the first message robot, where the point-to-point application message type is used to instruct the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot;
step S220, returning a response message of the first request message to the first message robot, wherein the response message carries a message identifier distributed for the first request message;
step S230, sending a second request message to a rich media communication service network element, where the second request message carries the number information of the sender terminal device associated user, the number information of the receiver terminal device associated user, the message identifier of the first request message, and the message content, the second request message is used to instruct the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries the number information of the sender terminal device associated user, the number information of the receiver terminal device associated user, and the message identifier of the first request message.
Specifically, the chat robot chatbot may be a 5G message chat robot (chatbot), a short message and multimedia message sender, a message sender software program, and the like, which is not limited in this application.
Specifically, in step 210, the first request message may specifically initiate a user peer-to-peer message HTTP request to the MaaP platform for the application Chatbot, and based on parameters including a sending party Chatbot URI, a receiving party user TEL, message content, and the like, extend a message ContentType parameter value, increase a peer-to-peer application message type, and simultaneously increase a sending party user number field parameter, for example, the special message ContentType for the peer-to-peer application scenario with the ContentType parameter value may extend a new value, such as < ContentType > application/p2 mapping/vnd.gsma.rcs-ft-HTTP + xml ContentType > (there are multiple contenttypes under the standard, and may extend to/p 2 mapping /) between the first/symbols. The sender number parameter may also be a new extension definition, such as < sendusernumber > +8613902221234 </sendusernumber >,/p 2 mapping/used for indicating a peer-to-peer application message type, < sendusernumber > +8613902221234 </sendusernumber > indicating the number of the sender, and it should be understood that the specific embodiment is not limited in this application.
Specifically, in step 220, after the MaaP platform receives the message, according to the standardized processing flow, the corresponding allocated msgid information is returned in the response message, specifically, the response message of the first request message may be a 200OK message, where the message identifier of the first request message may be msgid information.
Specifically, in step 230, the second request message may be an HTTP request sent by the MaaP platform through a downlink message, and specifically, the HTTP request may include a TEL of the sending user, a TEL of the receiving user, an msgid, a message content, and the like.
Optionally, as an embodiment of the present application, the second request message further includes a service signature of the first request message.
That is, the MaaP platform may add a source tag corresponding to the Chatbot set in the second request message content, such AS sending the second request message through a specific application 139 mailbox, and forward the second request message to the RCS AS.
Specifically, compared with the text mode of the point-to-point short message, the 5G point-to-point message also supports rich media message types such as pictures, voice, video, geographical location, and the like, and takes the rear-end source tag (i.e., the service signature) as an optional function. Except for the text message, the MaaP platform automatically adds the preset application rear-end source label text after the text content of the message according to the configuration of Chatbot, and the rear-end information of the rich media message, and the MaaP platform does not make special adaptation by automatically adding the rear-end label watermark information in the corresponding thumbnail material in the standard material uploading process by applying the Chatbot.
Further, the RCS serving network element records the mapping of the first request message to the corresponding Chatbot URI based on the unique identifier (msgid of the first request message).
Further, the RCS application pushes the corresponding SIP Message to the user 5G Message terminal side according to the standard point-to-point Message processing logic, and the sender number is the TEL number of the user who sent the Message through the application, so that the receiver user terminal displays that the caller is the mobile phone number of the user who sent the Message through the application, in the SIP Message.
Fig. 3 is a schematic flowchart of a method for communicating a 5G message according to another embodiment of the present application, where the method 300 includes:
step 310, receiving a message, that is, a second request message sent by the platform MaaP, where the second request message is generated by a first request message sent by the first message robot, and the second request message carries number information of a sender terminal device associated user, number information of a receiver terminal device associated user, a message identifier of the first request message, and a message content.
Step 320, sending a third request message to the terminal device of the receiving party, where the third request message carries the number information of the user associated with the terminal device of the sending party, the number information of the user associated with the terminal device of the receiving party, and the message identifier of the first request message.
Specifically, the second request message is an HTTP request sent by the MaaP platform through a downlink message, and specifically, the HTTP request may include a TEL of the sender user, a TEL of the receiver user, msgid, message content, and the like.
Specifically, in step 320, the third request Message may be an SIP Message sent by the RCS service network element, where the SIP Message carries the TEL of the terminal device associated user of the sending party and the TEL, msgid of the terminal device associated user of the receiving party.
Optionally, the second request Message further includes a service signature of the first request Message, that is, the SIP Message may also carry a service signature.
Optionally, as an embodiment of the present application, the method further includes: and recording the association relation between the message identification of the first request message and the URI of the first message robot.
Optionally, as an embodiment of the present application, the method further includes: receiving a first receipt message returned by the terminal device, wherein the first receipt message carries a message identifier of the first request message; and sending a second request receipt message to the MaaP according to the association relation between the message identifier of the first request message and the URI of the first message robot, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message.
Specifically, the first receipt Message returned by the terminal device may be an SIP Message receipt Message, where the SIP Message receipt Message carries the msgid of the first request Message; the second response piece message can be an HTTP response piece message carrying the calling Chatbot URI and the msgid of the first request message.
FIG. 4 is a schematic flow chart diagram of a method of one embodiment of the present application. As shown in fig. 4, the method includes, step 401, Chatbot initiating a user point-to-point HTTP request message to MaaP platform, where the request message includes a sender Chatbot URI, a receiver user TEL, message content, etc., as well as a point-to-point application message type and a sender user number.
Step 402, the MaaP platform sends 200OK, the message carries the msgid information of the point-to-point HTTP message in 401.
Step 403, the MaaP platform sends an HTTP request through a downlink message, which may specifically include a TEL of the sender user, a TEL of the receiver user, msgid, message content, and the like.
In step 404, the RCS service network element sends a 200OK return message to the MaaP.
Further, the RCS service network element records the mapping relationship between the message and the corresponding Chatbot URI based on msgid of the point-to-point HTTP message.
Step 405, the RCS service network element sends an SIP message to the UE terminal, where the SIP message carries a TEL of a user associated with the sender terminal device, a TEL of a user associated with the receiver terminal device (i.e., the UE terminal), and an msgid of the point-to-point HTTP message, and optionally, the SIP message may also carry a service signature, that is, a service tag of the point-to-point HTTP message.
In step 406, the UE terminal returns a 200OK message in response to step 405 to the RCS serving network element.
Step 407, the UE terminal sends an SIP Message receipt Message to the RCS application, where the SIP Message receipt Message carries the msgid of the point-to-point HTTP Message.
In step 408, the RCS serving network element returns a 200OK message in response to step 407 to the UE terminal.
Further, the RCS service network element will match the path of the HTTP response message when performing step 409 according to the mapping relationship between msgid and Chatbot URI.
Step 409, HTTP receipt message, which carries the calling Chatbot URI and the msgid of the point-to-point HTTP message.
In step 410, the MaaP platform sends a 200OK message in response to step 409 to the RCS service network element.
Step 411, the MaaP platform sends an HTTP response piece message to Chatbot, which carries the Chatbot URI and the msgid of the peer-to-peer HTTP message.
At step 412, the MaaP platform sends a 200OK message to Chatbot.
It should be understood that, before sending the point-to-point message, authentication of the point-to-point message issued by the user through Chatbot is required, and at present, the authentication includes 2 modes, one mode is oriented to the internal owned service, the authenticity of the point-to-point message sent by the user through application is automatically ensured by the owned service, the MaaP platform opens the authority of the point-to-point message sending function aiming at the Chatbot, the mode is suitable for service upgrade oriented to the internal owned service, the implementation mode is the simplest, and is consistent with the implementation mode of the short message at the port of the existing network.
And in addition, a point-to-point message service can be issued through the MaaP platform in an open mode facing external application, in order to avoid the excessive adaptation requirement on the standardized network element of the MaaP platform, a special point-to-point message application service gateway can be superposed on the MaaP platform to complete the functions of user order confirmation, recording and verification, and is uniformly connected with the MaaP platform to assemble and distribute all point-to-point message signaling.
Fig. 5 is a schematic flow chart of a method according to another embodiment of the present application, as shown in fig. 5, the method including:
at step 501, chatbot initiates a point-to-point message service subscription request to an application service gateway.
Step 502, the application service gateway sends a point-to-point message function order HTTP request to the MaaP platform, and the request message carries the chatbot URI, the TEL of the requesting user and the order content.
Specifically, the subscription content is preset subscription notification information, such as a card message with a suggestion reply, and is a user requesting to send a message to you through application XXX, whether to receive? The proposal reply button is respectively 'accept' and 'not receive', and the specific form can be configured at the application service gateway.
In step 503, MaaP sends a 200OK response to the application service gateway.
Step 504, the MaaP platform sends a downlink order confirmation HTTP message to the RCS service network element, where the message carries the chatbot URI in the chatbot, the TEL of the requesting user, and the order content.
Step 505, the RCS service network element returns a 200OK response to the MaaP platform.
In step 506, the RCS service network element sends a SIP or SMS subscription confirmation message to the terminal device.
Step 507, the UE terminal sends a receiving success response message to the RCS service network element.
In step 508, the RCS service network element sends a SIP or SMS subscription confirmation reply message to the terminal device.
In step 509, the UE terminal sends a reception success response message to the RCS serving network element.
Step 510, the RCS service network element sends an uplink subscription confirmation reply HTTP message to the MaaP platform.
In step 511, the MaaP platform returns a 200OK response to the RCS service network element.
Step 512, the MaaP platform sends a point-to-point message function order reply HTTP request to the application service gateway.
Step 513, the application service gateway sends a 200OK response to the MaaP application.
At step 514, the application service gateway sends a subscription result notification message to the chatbot.
As described above, a point-to-point message service ordering request initiated by an external application Chatbot needs to be connected to a unified application service gateway, a user function ordering confirmation message is pushed to a corresponding user 5G message terminal and received through a standard A2P \ P2A message interaction process of a MaaP platform and an RCS AS, and a related ordering relationship is recorded at the point-to-point application service gateway and an ordering result is notified to the related external application Chatbot. The application service gateway is a trusted internal network element with respect to the MaaP platform, and serves as an interaction proxy for the external application Chatbot. Therefore, the mode is equivalent to a special case of an own service application mode, the problem of authentication of an external application Chatbot is solved, the subsequent point-to-point message interaction process is similar to the own service mode, and only forwarding of a plurality of layers of application service gateways between Chatbot and a MaaP platform is applied, so that the subsequent message interaction process does not describe the mode repeatedly, and the mode is described by taking an own service application Chatbot as a representative.
Fig. 6 shows a schematic block diagram of a network element for 5G message communication according to an embodiment of the present application, and as shown in fig. 6, the network element 600 includes a receiving unit 610, where the receiving unit 610 is configured to receive a first request message sent by a first message robot, and the first request message includes number information of a sender terminal device-associated user, number information of a receiver terminal device-associated user, an identifier of the first message robot, message content, a point-to-point application message type, and a URI of the first message robot, where the point-to-point application message type is used to instruct the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot; a sending unit 620, configured to return a response message of the first request message to the first message robot, where the response message carries a message identifier allocated to the first request message; the sending unit 620 is further configured to send a second request message to a rich media communication service network element, where the second request message carries number information of the sender terminal device associated user, number information of the receiver terminal device associated user, a message identifier of the first request message, and the message content, the second request message is used to instruct the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries number information of the sender terminal device associated user, number information of the receiver terminal device associated user, and the message identifier of the first request message.
Specifically, the network element 600 may be a MaaP platform.
It should be understood that the network element for 5G message communication is configured to perform the method shown in fig. 2, and will not be described herein again.
Fig. 7 shows a schematic block diagram of a network element for 5G message communication according to an embodiment of the present application, and as shown in fig. 7, the network element 700 includes a receiving unit 710, where the receiving unit 710 is configured to receive a second request message sent by a platform MaaP, where the second request message is generated by a first request message sent by a first message robot, and the second request message carries number information of a sender terminal device associated user, number information of a receiver terminal device associated user, a message identifier of the first request message, and message content; a sending unit 720, where the sending unit 720 is configured to send a third request message to the terminal device of the receiving party, and the third request message carries the number information of the user associated with the terminal device of the sending party, the number information of the user associated with the terminal device of the receiving party, and the message identifier of the first request message.
Optionally, the network element 700 further includes: a processing unit 730, wherein the processing unit 730 is configured to record an association relationship between a message identifier of the first request message and a URI of the first message robot.
The message processing system provided in the embodiment of the present invention can implement each process in the embodiment corresponding to the message processing method, and is not described herein again to avoid repetition.
It should be noted that, the message processing system provided in the embodiment of the present invention and the message processing method provided in the embodiment of the present invention are based on the same inventive concept, and achieve the same beneficial effects, so that the specific implementation of the embodiment may refer to the implementation and beneficial effects of the foregoing configuration method of network resources, and repeated details are not described again.
Corresponding to the method for configuring network resources provided in the foregoing embodiment, based on the same technical concept, an embodiment of the present invention further provides a network device, where the network device is configured to execute the method for configuring network resources, and fig. 8 is a schematic structural diagram of a network device for implementing various embodiments of the present invention, as shown in fig. 8. Network devices may vary widely in configuration or performance and may include one or more processors 801 and memory 802, where the memory 802 may have one or more stored applications or data. Wherein the memory 802 may be a transient storage or a persistent storage. The application program stored in memory 802 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for a network device. Still further, the processor 801 may be configured to communicate with the memory 802 to execute a series of computer-executable instructions in the memory 802 on a network device. The network apparatus may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input-output interfaces 805, one or more keyboards 806.
Specifically, in this embodiment, the network device includes a processor, a communication interface, a memory, and a communication bus; the processor, the communication interface and the memory complete mutual communication through a bus; the memory is used for storing a computer program; the processor is used for executing the program stored in the memory and realizing the following method steps: the method described in the above embodiment of fig. 2 or fig. 3.
An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method described in the embodiment of fig. 2 or fig. 3.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a network device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.
Claims (10)
1. A method for communicating a 5G message, comprising:
receiving a first request message sent by a first message robot, wherein the first request message comprises number information of a sender terminal device associated user, number information of a receiver terminal device associated user, an identifier of the first message robot, message content, a point-to-point application message type and a URI of the first message robot, and the point-to-point application message type is used for indicating the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot;
returning a response message of the first request message to the first message robot, wherein the response message carries a message identifier distributed for the first request message;
and sending a second request message to a rich media communication service network element, wherein the second request message carries the number information of the associated user of the sender terminal device, the number information of the associated user of the receiver terminal device, the message identifier of the first request message, and the message content, the second request message is used for indicating the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries the number information of the associated user of the sender terminal device, the number information of the associated user of the receiver terminal device, and the message identifier of the first request message.
2. The communication method according to claim 1, wherein the second request message further includes a traffic signature of the first request message.
3. The communication method of claim 1, wherein the method further comprises:
receiving a second request receipt message sent by the rich media communication service, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message;
and sending the second request receipt message to the first message robot, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message.
4. A method for communicating a 5G message, comprising:
receiving a message, namely a second request message sent by a platform MaaP, wherein the second request message is generated by a first request message sent by a first message robot, and the second request message carries number information of a sender terminal device associated user, number information of a receiver terminal device associated user, a message identifier of the first request message and message content;
and sending a third request message to the terminal equipment of the receiving party, wherein the third request message carries the number information of the user associated with the terminal equipment of the sending party, the number information of the user associated with the terminal equipment of the receiving party and the message identifier of the first request message.
5. The communication method of claim 4, wherein the method further comprises:
and recording the association relation between the message identification of the first request message and the URI of the first message robot.
6. The communication method of claim 5, wherein the method further comprises:
receiving a first receipt message returned by the terminal device, wherein the first receipt message carries a message identifier of the first request message;
and sending a second request receipt message to the MaaP according to the association relation between the message identifier of the first request message and the URI of the first message robot, wherein the second request receipt message carries the URI of the first message robot and the information identifier of the first request message.
7. The communication method according to any one of claims 4 to 6, wherein the second request message further includes a traffic signature of the first request message.
8. A network element for 5G message communication, comprising:
the system comprises a receiving unit, a first message robot and a second message robot, wherein the receiving unit is used for receiving a first request message sent by the first message robot, the first request message comprises number information of a sender terminal device associated user, number information of a receiver terminal device associated user, an identifier of the first message robot, message content, a point-to-point application message type and a URI of the first message robot, and the point-to-point application message type is used for indicating the sender terminal device to send a point-to-point message to the receiver terminal device through the first message robot;
a sending unit, configured to return a response message of the first request message to the first message robot, where the response message carries a message identifier allocated to the first request message;
the sending unit is further configured to send a second request message to a rich media communication service network element, where the second request message carries number information of the sender terminal device associated user, number information of the receiver terminal device associated user, a message identifier of the first request message, and the message content, the second request message is used to instruct the rich media communication service to send a third request message to the receiver terminal device, and the third request message carries the number information of the sender terminal device associated user, the number information of the receiver terminal device associated user, and the message identifier of the first request message.
9. A network element for 5G message communication, comprising:
a receiving unit, configured to receive a second request message sent by a platform MaaP, where the second request message is generated from a first request message sent by a first message robot, and the second request message carries number information of a user associated with a sender terminal device, number information of a user associated with a receiver terminal device, a message identifier of the first request message, and a message content;
a sending unit, configured to send a third request message to the receiving side terminal device, where the third request message carries number information of a user associated with the sending side terminal device, number information of a user associated with the receiving side terminal device, and a message identifier of the first request message.
10. The network element of claim 9, wherein the network element further comprises:
and the processing unit is used for recording the association relation between the message identifier of the first request message and the URI of the first message robot.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111151196.0A CN115002689B (en) | 2021-09-29 | 2021-09-29 | 5G message communication method and network element for 5G message communication |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111151196.0A CN115002689B (en) | 2021-09-29 | 2021-09-29 | 5G message communication method and network element for 5G message communication |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115002689A true CN115002689A (en) | 2022-09-02 |
| CN115002689B CN115002689B (en) | 2023-07-21 |
Family
ID=83017960
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111151196.0A Active CN115002689B (en) | 2021-09-29 | 2021-09-29 | 5G message communication method and network element for 5G message communication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115002689B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090292766A1 (en) * | 2006-02-01 | 2009-11-26 | Morris Robert P | HTTP Publish/Subscribe Communication Protocol |
| US20170070456A1 (en) * | 2014-03-03 | 2017-03-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Streaming Media Content to a User Equipment in an Internet Protocol Multimedia Subsystem |
| CN106506316A (en) * | 2015-09-06 | 2017-03-15 | 中兴通讯股份有限公司 | Information transferring method and device |
| US20190356704A1 (en) * | 2018-05-16 | 2019-11-21 | Telia Company Ab | Methods and apparatuses for associating user identification information to chatbot capable frameworks |
| US10789040B1 (en) * | 2019-06-05 | 2020-09-29 | International Business Machines Corporation | Interaction between two virtual assistants |
| US20200404025A1 (en) * | 2018-02-15 | 2020-12-24 | Samsung Electronics Co., Ltd. | Handling instant message disposition notification (imdn) message in rich communication service (rcs) system |
-
2021
- 2021-09-29 CN CN202111151196.0A patent/CN115002689B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090292766A1 (en) * | 2006-02-01 | 2009-11-26 | Morris Robert P | HTTP Publish/Subscribe Communication Protocol |
| US20170070456A1 (en) * | 2014-03-03 | 2017-03-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Streaming Media Content to a User Equipment in an Internet Protocol Multimedia Subsystem |
| CN106506316A (en) * | 2015-09-06 | 2017-03-15 | 中兴通讯股份有限公司 | Information transferring method and device |
| US20200404025A1 (en) * | 2018-02-15 | 2020-12-24 | Samsung Electronics Co., Ltd. | Handling instant message disposition notification (imdn) message in rich communication service (rcs) system |
| US20190356704A1 (en) * | 2018-05-16 | 2019-11-21 | Telia Company Ab | Methods and apparatuses for associating user identification information to chatbot capable frameworks |
| US10789040B1 (en) * | 2019-06-05 | 2020-09-29 | International Business Machines Corporation | Interaction between two virtual assistants |
Non-Patent Citations (1)
| Title |
|---|
| 陈建婷;: "融合通信系统中多端消息同步方案研究", 无线互联科技 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115002689B (en) | 2023-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11997231B2 (en) | System and method for determining and communicating presence information | |
| US9854008B2 (en) | Real time communication method, terminal device, real time communication server and real time communication system | |
| RU2357380C1 (en) | Method and system for intelligent routing | |
| US10419371B2 (en) | Methods and systems for delayed notifications in communications networks | |
| US20080198839A1 (en) | System and method of communication in an ip multimedia subsystem network | |
| JP2012510231A (en) | Method and apparatus for providing communication history | |
| US10924530B2 (en) | Inter-provider file transfer system and method | |
| CN103546437A (en) | Method, UE (user equipment) and AS (application server) for transceiving offline messages in IMS (IP multimedia system) | |
| US9924042B2 (en) | Uniform RCS voice/videomail services | |
| US10129190B2 (en) | Method and apparatus for messaging service internetworking | |
| CA2626353C (en) | Methods and systems to allow multiple sip applications on a sip client the ability to select specific applications and features on a sip server | |
| FI113995B (en) | Method and apparatus for realizing an improved tone of message | |
| CN115002689B (en) | 5G message communication method and network element for 5G message communication | |
| US9596577B1 (en) | Relaying mobile communications | |
| CN113630732B (en) | Converged communication method, terminal, system and storage medium | |
| US11057517B2 (en) | Method for managing a failure to establish a communication between a first and a second terminal | |
| CN108337215B (en) | File transmission method, system and device and electronic equipment | |
| CN114884913A (en) | Message interaction method and device, electronic equipment, message server and storage medium | |
| CN115967698A (en) | Message sending method, electronic device, and computer-readable storage medium | |
| CN115834679A (en) | Notification message pushing method and system | |
| Blum et al. | Enabling information push for network-and device-agnostic internet services | |
| JP2010021757A (en) | Answering machine system, message providing method for use in the same, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |