CN108156069A - A kind of integration message system and message treatment method - Google Patents
A kind of integration message system and message treatment method Download PDFInfo
- Publication number
- CN108156069A CN108156069A CN201711435379.9A CN201711435379A CN108156069A CN 108156069 A CN108156069 A CN 108156069A CN 201711435379 A CN201711435379 A CN 201711435379A CN 108156069 A CN108156069 A CN 108156069A
- Authority
- CN
- China
- Prior art keywords
- message
- protocol
- protocol message
- module
- client
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
This application discloses a kind of integration message system and message treatment methods；The integration message system includes：Access platform and business platform；Wherein, access platform connection business platform；Access platform is configured to receive the first protocol message from the transmission client using the access of the first agreement；Business platform is configured to being converted to the first protocol message into the second protocol message supported using the reception client that second protocol accesses；Access platform is additionally configured to send second protocol message to reception client.In this way, multiterminal multi-protocols adaptation is realized, so as to promote user experience.
Description
Technical field
This application involves but be not limited to the communication technology more particularly to a kind of integration message system and message treatment method.
Background technology
With the fast development of global mobile service, it is including short message, Multimedia Message, mobile E-mail and movement
The instant messages class business such as Shi Tongxin has obtained extensive use as the important service except mobile voice.But along with
The development of instant message class business, some problems also show therewith.
Internet producer oneself R ＆ D design client application (APP, Application) and server, using private
Some communication protocol patterns, by the use of the network of operators communication as pipeline, instant messages all in this way and the networking telephone etc.
Function is all realized in the client of producer oneself.The instant message class business of internet producer has been designed to " vertical shaft " at present
Formula architectural framework, the instant message class business of different manufacturers construct different framework agreement and platform.Different manufacturers it is instant
The function of information series business overlaps increasingly severe.However, since the client message of different manufacturers is using nonopen
Proprietary protocol, thus at all can not intercommunication, the client type for leading to instant message class business is numerous, and agreement is various, so as to shadow
The experience of user is rung.
Invention content
It is the general introduction of the theme to being described in detail herein below.This general introduction is not the protection model in order to limit claim
It encloses.
The embodiment of the present application provides a kind of integration message system and message treatment method, realizes multiterminal multi-protocols adaptation, from
And promote user experience.
In a first aspect, the embodiment of the present application provides a kind of integration message system, including：Access platform and business platform；
Wherein, the access platform connects the business platform；
The access platform is configured to receive the first protocol message from the transmission client using the access of the first agreement；
The business platform is configured to being converted to first protocol message into the reception client accessed using second protocol
Hold the second protocol message supported；
The access platform is additionally configured to send the second protocol message to the reception client.
Second aspect, the embodiment of the present application provide a kind of message treatment method, including：
The first protocol message is received from the transmission client using the access of the first agreement；
First protocol message is converted to the second protocol that the reception client accessed using second protocol is supported to disappear
Breath；
The second protocol message is sent to the reception client.
In addition, the embodiment of the present application also provides a kind of computer-readable medium, it is stored with message processing program, the message
The step of message treatment method that above-mentioned second aspect provides is realized when processing routine is executed by processor.
In the embodiment of the present application, integration message system includes：Access platform and business platform；Wherein, access platform
Connect business platform；Access platform is configured to receive the first protocol message from the transmission client using the access of the first agreement；Industry
Business platform configuration is that the first protocol message is converted to the second protocol that the reception client accessed using second protocol is supported to disappear
Breath；Access platform is additionally configured to send second protocol message to reception client.In this way, the present embodiment provides a kind of support multiterminal
The integration message system of multi-protocols access the characteristics of simplifying complicated various types of messages system architecture, merge each business, is realized not
It with the converting transmission between agreement, is convenient for users to operate, and improves user experience.
After attached drawing and detailed description is read and understood, it can be appreciated that other aspects.
Description of the drawings
Fig. 1 is the schematic diagram of integration message system provided by the embodiments of the present application；
Fig. 2 is the exemplary plot of integration message system provided by the embodiments of the present application；
Fig. 3 is the structure diagram of the OTT agreements of the embodiment of the present application；
Fig. 4 is the multi-client register flow path figure of the embodiment of the present application；
Fig. 5 is that the different clients of the embodiment of the present application receive and dispatch the example flow diagram of small message；
Fig. 6 is that the different clients of the embodiment of the present application receive and dispatch another example flow diagram of small message；
Fig. 7 is that the different clients of the embodiment of the present application receive and dispatch the example flow diagram of big message；
Fig. 8 is that the different clients of the embodiment of the present application receive and dispatch another example flow diagram of big message；
Fig. 9 is the flow chart of message treatment method provided by the embodiments of the present application.
Specific embodiment
The embodiment of the present application is described in detail below in conjunction with attached drawing, it should be understood that embodiments described below is only
For instruction and explanation of the application, it is not used to limit the application.
Step shown in the flowchart of the accompanying drawings can be in the computer system of such as a group of computer-executable instructions
It performs.Also, although logical order is shown in flow charts, it in some cases, can be to be different from herein suitable
Sequence performs shown or described step.
The embodiment of the present application provides a kind of integration message system and message treatment method, mobile phone, set-top box, tablet computer
(PAD, Portable Android Device), television set (TV, Television), computer (PC, Personal
) etc. Computer a variety of clients may be used various protocols and access simultaneously, and the conversion realized between different agreement message passes
It is defeated, so as to promote the development of internet mobile immediate communication business, the user satisfaction of user can be greatly improved, improves user
Business experience.
Fig. 1 is the schematic diagram of integration message system provided by the embodiments of the present application.Converged message system provided in this embodiment
System can be deployed on server cluster, however, the application does not limit this.
As shown in Figure 1, integration message system provided by the embodiments of the present application, including：Access platform 11 and business platform
12；Wherein, access platform 11 connects business platform 12.
In the present embodiment, access platform 11 is configured to receive first from the transmission client 10a using the access of the first agreement
Protocol message；Business platform 12 is configured to be converted to the first protocol message and be supported using the reception client that second protocol accesses
Second protocol message；Access platform 11 is additionally configured to send second protocol message to reception client 10b.
In the exemplary embodiment, client (for example, send client 10a, receive client 10b) can include branch
Hold converged communication (RCS) terminal of standard instant messaging agreement and OTT agreements.However, the application does not limit this.
In the exemplary embodiment, business platform 12 can include：Agreement supporting module and business module；Agreement branch
Hold mode block connects business module；Wherein, business module is configured to the end log-on message according to the first protocol message and storage, really
The protocol conversion instruction information of fixed first protocol message, and send protocol conversion instruction information and give agreement supporting module；Agreement branch
Hold mode block is configured to indicate information according to protocol conversion, is converted to second protocol message, and sends second protocol message to connecing
Enter platform 11.
In the exemplary embodiment, business module is also configured as what basis was received from one or more clients
Log-on message and the conflict rule table of storage update end log-on message；Wherein, end log-on message includes at least：One or more
The user online status and registration type of a client, registration type can indicate the access protocol that client is supported；Punching
Prominent rule list records the registration type that can be coexisted in same client.
Illustratively, end log-on message can include：User identifier, user online status, facility information are (for example, equipment
Mark, device capability information etc.), version information, registration type.Wherein, registration type can include：Native、RCS APP、
Pc client, Web client etc., wherein, Native modes and RCS APP modes indicate to access using RCS standard agreements, PC visitors
Family end and Web client can indicate to access using OTT agreements.
In the exemplary embodiment, agreement supporting module is adapted to provide for the conversion between any two following agreements：At the beginning of session
Beginning agreement (SIP), message session trunk protocol (MSRP), hypertext transfer protocol (HTTP), XCAP agreements, access-in management agreement
(AOP), OTT agreements.
In the exemplary embodiment, the protocol Data Unit (PDU) of OTT agreements can include：Message header field, one or
Multiple self-defined message domains；Wherein, any self-defined message domain includes message header part and message body portion.As shown in figure 3,
Include common MM (Multimedia, more matchmakers in the OTT protocol Data Units (PDU, Protocol Data Unit) being transmitted
Body) message header field and customized message field.Wherein, common message header field can include calling and called address (From, To),
Message unique identity (MsgId), type of message (Content-Type), terminal type etc., each message can use.It makes by oneself
Adopted message field can embody the dedicated information of various type of messages.Each self-defined message domain can include message header part and disappear
Cease body portion.For example, client needs one blank message of transmission to delineate direction, then it can be in the first self-defined message domain
The message header part of (part 1) carries background picture mark, and message body portion carries image content；It can be self-defined second
The message header part of message field (part 2) carries direction position coordinates logo, and message body portion carries the lines letter being directed toward in direction
Breath.In this example, OTT agreements are based on binary coding, and code efficiency is higher, and safety is preferable, and protocol stack is smaller, therefore occupy
Bandwidth is small, and FTP client FTP resource occupation is low.
In the exemplary embodiment, business platform 12 can also include：Unified message Queue module connects business mould
Block, unified message Queue module are configured to the first protocol message that storage service module receives.
In the exemplary embodiment, if the size of the first protocol message is less than preset value (for example, 8K), second protocol
Message carries the message content of the first protocol message；If the size of the first protocol message is greater than or equal to preset value, the second association
Discuss the storage address that message carries the first protocol message.
In this illustrative embodiments, business module is also configured as judging the size of the first protocol message；If the
The size of one protocol message is less than preset value, it is determined that protocol conversion instruction information includes the message content of the first protocol message；
If the size of the first protocol message is greater than or equal to preset value, it is determined that protocol conversion instruction information includes the first protocol message
Storage address.Illustratively, protocol conversion instruction information can also include：Send the facility information of client and connecing for use
Enter the access protocol of agreement, the facility information of reception client and use.Agreement supporting module indicates to believe according to protocol conversion
When breath is handled, it can obtain carrying the second protocol message of the message content of the first protocol message, alternatively, carrying the first association
Discuss the second protocol message of the storage address of message.
In the exemplary embodiment, agreement supporting module is also configured as carrying out agreement turn to the first protocol message
It changes, and the second protocol message being converted to is sent to business module；
Business module is also configured as, when the size for judging the first protocol message is greater than or equal to preset value, building
The vertical media transmission channel between reception client 10b passes through media transmission channel and transmits second protocol message.Wherein,
One protocol message can be OTT protocol messages, and second protocol message can be Session Initiation Protocol message.
In the exemplary embodiment, the first protocol message can be OTT protocol messages, and second protocol message can be to melt
Hop communication standard protocol message, for example, Session Initiation Protocol message；Disappear alternatively, the first protocol message can be converged communication standard agreement
Breath, second protocol message can be OTT protocol messages.
Illustrate an example of integration message system provided in this embodiment referring to Fig. 2.As shown in Fig. 2, this example
The integration message system of offer includes：It is uniformly accessed into platform (corresponding to above-mentioned access platform) and business platform；Wherein, industry
Business platform includes：Agreement supporting module, business module and unified message Queue module.
In this example, multi-client may be used different agreement and access integration message system simultaneously.Wherein, client can be with
RCS terminals including supporting standard instant messaging agreement and OTT (Over The Top) agreement.Illustratively, RCS user can be with
Network is accessed by various terminals and uses business.It is different according to the presentation mode that RCS in terminal is serviced, RCS business exist with
Lower two kinds of terminal forms：RCS standard agreements access (for example, primary (Native) terminal, APP clients) and the access of OTT agreements
(for example, computer (PC, Personal Computer) client, webpage (Web) client etc.).Wherein, Native modes refer to
Manufacture indispensability preparatory functions of the RCS as any a terminal, and carried out specific aim in levels such as chip, operating systems and repaiied
Change；APP modes refer to allow in a manner that application program is installed existing terminal (for example, mobile phone, set-top box, tablet computer (PAD,
Portable Android Device)) have RCS functions.
In this example, it is uniformly accessed into platform and is responsible for receiving message from different transmission clients, to different reception clients
The control of end forwarding message and different agreement access distribution policy.As shown in Fig. 2, being uniformly accessed into platform passes through session border
RCS standard agreements are supported in controller (SBC, Session Border Controller) and sip agent (Siproxy) access
Client, (Proxy) and link are acted on behalf of by Http distribute gateway (LAG) and access and support the clients of OTT agreements.
In this example, agreement supporting module can be responsible for the adaptation of various agreements, for example, session initiation protocol (SIP,
Session Initiation Protocol), message session trunk protocol (MSRP, Message Session Relay
Protocol), hypertext transfer protocol (HTTP, Hyper Text Transfer Protocol), XCAP agreements, OTT agreements,
Access-in management agreement (AOP) etc., and the conversion between different agreement is provided.Illustratively, agreement supporting module can include more
A protocol adaptation unit and management interface machine, for being adapted to a kind of agreement, management interface machine provides each protocol adaptation unit
Conversion between different agreement.
In this example, business module is responsible for providing maintenance and the various businesses of the access style and login state of client
Ability, for example, including business processing logics such as instant message, call, picture, files.Illustratively, business module can include
Multiple node traffic modules, client can be connected to corresponding node traffic module according to the ownership place at place.
In this example, business module is stored with end log-on message and conflict rule table.Illustratively, business module stores
The login state table (corresponding above-mentioned end log-on message) of the terminal of registration, wherein user identifier can be included (for example, user
Phone number), user online status, version information, device identification, access style etc..Conflict rule table can record same end
Which registration type (for example, type of access application) can coexist on end, which registration type needs is mutually kicked.Conflict rule table
It can be configured according to business demand.For example, in the conflict rule table shown in table 1, N/A (Not applicable) is represented
It is inapplicable；The type of " ╳ " is indicated in table cannot coexist in same terminal, i.e., PC client on same terminal (for example, computer)
End cannot be registered simultaneously with Web client, cannot register multiple RCS APP clients in same terminal simultaneously, in same terminal
Multiple pc clients cannot be registered simultaneously, can not register multiple Web clients simultaneously.
Table 1
In this example, the initial registration request of business platform processing terminal, when there is endpoint registration, business platform inquiry
The registration type of the terminal, with the presence or absence of conflicting, if there is no conflict, allows this terminal to note with the registered type of the terminal
Volume this type；If there is conflict, the type newly asked, and the login state releasing of the type there will be conflict are registered；Terminal
After the completion of location registration process, the login state table of business platform more new terminal.
In this example, since the user identifier of same type of APP is unique, when user has changed mobile phone or PAD is reset, then
During secondary initiation registration request, being uniformly accessed into platform needs the client for identifying same subscriber to carry out offline processing.OTT terminals are noted
Volume access, business module can record OTT terminal iidentifications.
In this example, unified message Queue module is responsible for the distribution and dump of message.Unified message Queue module can wrap
Include message queue module corresponding with user identifier and device identification.Some user is put using the message of some equipment transmission
Enter in corresponding message queue module.
In this example, after client is accessed using different agreement, the management interface machine of agreement supporting module can basis
The message that unified message Queue module issues is converted into the association that client can support by the end log-on message of business module storage
View message is handed down to purpose user.
Scheme provided by the embodiments of the present application is described in detail below by multiple examples.Under it should be noted that
Multiple examples in face are illustrated based on integration message system shown in Fig. 2.
Fig. 4 is the multi-client register flow path figure of the embodiment of the present application.In this example, RCS customer end As can be supported
SIP standard agreements, OTT customer end Bs can support OTT agreements.
As shown in figure 4, the flow of the present embodiment includes：
S101, RCS customer end A initiate Active Registration to platform is uniformly accessed into；
S102, the agreement supporting module that SIP registration message is forwarded to business platform by platform, agreement branch hold mode are uniformly accessed into
Block parses SIP registration message；
S103, business platform agreement supporting module to business module forward SIP registration message；Business module receives
After SIP registration message, the user online status and registration type of RCS customer end As are recorded；Wherein, registration type can be used for referring to
Show access protocol used by RCS customer end As；
S104, business module call the registration subscribing interface of unified message Queue module；
S105 to S108, unified message Queue module return to location registration process as a result, business module passes through association to business module
It discusses supporting module and is uniformly accessed into platform and return to success response message (200OK) to RCS customer end As；RCS customer end As are completed
Registration.
S109, OTT customer end B initiate Active Registration to platform is uniformly accessed into；
S110, it is uniformly accessed into the agreement supporting module that OTT registration messages are forwarded to business platform by platform；
OTT registration messages are converted to internal standard registration message by S111, agreement supporting module, and notify business mould
Block；
S112, business module call the registration subscribing interface of unified message Queue module；
S113 to S116, unified message Queue module return to location registration process as a result, business module passes through association to business module
It discusses supporting module and is uniformly accessed into platform and return to success response message (200OK) to RCS customer end Bs；RCS customer end Bs are completed
Registration.
In this example, after customer end B completes registration, the corresponding message queue module of customer end B knows the use of customer end B
Family is online；Due to there are communications records between customer end A and customer end B or will communicate, customer end B pair
The message queue module answered needs to know the user online status of customer end A, in order to by unified message Queue module to visitor
Family end A and customer end B notify the user online status of respective opposite end.
The corresponding message queue module of S117, customer end B is to the user online status of business module inquiring client terminal A；
S118, business module are online to the corresponding message queue module return customer end A of customer end B；
Registration notification is pushed to node traffic module belonging to customer end A by S119 to S122, unified message Queue module,
Registration notification is pushed to being uniformly accessed into platform, then by uniting by agreement supporting module as the node traffic module belonging to customer end A
One access platform finally pushes registration notification to customer end A；I.e. customer end A receives the registration notification of customer end B.
Similarly, the corresponding message queue module of customer end A can to business module inquiring client terminal B user in threadiness
State returns to customer end B after line in business module, and registration notification can be pushed to belonging to customer end B by unified message Queue module
Node traffic module, then as the node traffic module belonging to customer end B by agreement supporting module push registration notification to
Platform is uniformly accessed into, then registration notification is pushed to customer end B by being uniformly accessed into platform, is i.e. customer end B receives the registration of customer end A
Notice.
Referring to Fig. 5 to Fig. 8, after the completion of illustrating client registers, transmitting-receiving of the integration message system under different scenes
Message flow.It should be noted that in following example, small message definition is less than the message of 8K, big message for message size
It is defined as the message that message size is greater than or equal to 8K.However, the application does not limit this.
Fig. 5 is that the different clients of the embodiment of the present application receive and dispatch the example flow diagram of small message.In this example, caller RCS
User is accessed using standard SIP protocol, and called subscriber is using OTT registration accesses.
As shown in figure 5, the flow of the present embodiment includes：
S201, user A (this example is calling subscribe) client send standard SIP MESSAGE message and (correspond to above-mentioned
The first protocol message)；
S202, it is uniformly accessed into platform and receives standard SIP MESSAGE message, be forwarded to the agreement of business platform protocol adaptation
Supporting module；
S203, agreement supporting module call inside story to send the node that standard SIP MESSAGE message belongs to user A
Business module；
The node traffic module of S204, user A ownership carries out standard SIP MESSAGE message business logic processing (ratio
Such as, the operations such as authenticating users) after, the corresponding message queue module of write-in user's A clients；
The node traffic module of S205 to S207, user A ownership returns to successfully service response message to user's A clients
(202Accepted)；
After the node traffic module of S208, user A ownership terminates the processing to user A, starting user B, (this example is quilt
Be user) message queue module write operation；It is i.e. that standard SIP MESSAGE message write-in user's B clients is corresponding
Message queue module；
S209, the corresponding message queue module of user's B clients have to the node traffic module notice that user B belongs to newly to disappear
Breath is sent to；
The node traffic module of S210, user B ownership is according to user registration state and registration type, issuing service request
(SIP MESSAGE message) is to the agreement supporting module of business platform protocol adaptation；Wherein, service request can carry agreement and turn
Instruction information is changed, for example, protocol conversion instruction information includes the facility information (for example, mark) and agreement of user's A clients
The facility information and protocol type of type, user's B clients；
The SIP MESSAGE message of former caller (user A clients) is converted into OTT agreements by S211, agreement supporting module
Message (Notify message)；Agreement supporting module group be bundled into the acceptable messaging protocol packet of user's B clients issue conversion after
OTT protocol messages (correspond to above-mentioned second protocol message) are to being uniformly accessed into platform；
S212, it is uniformly accessed into platform OTT protocol messages is successfully issued in user's B clients, the OTT that user B is used
Business presentation is received in client；
S213 to S215, user B clients by be uniformly accessed into platform and agreement supporting module to business module return into
Work(response message (200OK).
Fig. 6 is that the different clients of the embodiment of the present application receive and dispatch another example flow diagram of small message.In this example, caller
User is called RCS user and is accessed using standard SIP using OTT registration accesses.
As shown in fig. 6, the flow of the present embodiment includes：
S301, user A (this example is calling subscribe) client send OTT protocol messages (POST message) and (correspond to upper
The first protocol message stated)；
S302, it is uniformly accessed into platform and receives OTT protocol messages, be forwarded to the agreement branch hold mode of business platform protocol adaptation
Block；
OTT protocol messages are converted to standard SIP MESSAGE message by S303, agreement supporting module, are sent to user A and are returned
The node traffic module of category；
After the node traffic module of S304, user A ownership carries out business logic processing to the message of reception, by disappearing for reception
The corresponding message queue module of breath write-in user's A clients；
The node traffic module of S305 to S307, user A ownership returns to successfully service response message to user's A clients
(202Accepted)；
After the node traffic module of S308, user A ownership terminates the processing to user A, start the corresponding message teams of user B
The write operation of row module；
S309, the node traffic module notice that the message queue module of user B belongs to user B have new information to be sent to；
The node traffic module of S310, user B ownership is according to user registration state and registration type, issuing service request
(SIP MESSAGE message) is to the agreement supporting module of protocol adaptation；Wherein, service request can carry protocol conversion instruction letter
Breath, for example, the facility information and protocol type of protocol conversion instruction information including user's B clients, user's A clients are set
Standby information and protocol type；
The OTT protocol messages of former caller are converted into standard SIP MESSAGE message by S311, agreement supporting module；Agreement
Supporting module group, which is bundled into the acceptable messaging protocol packet of user's B clients and issues transformed SIP MESSAGE message, (to be corresponded to
Above-mentioned second protocol message) to being uniformly accessed into platform；
S312, being uniformly accessed into platform, most SIP MESSAGE message is successfully issued in the client of user B at last, user B
Business presentation is received in the RCS clients used；
S313 to S315, user B clients by be uniformly accessed into platform and agreement supporting module to business module return into
Work(response message (200OK).
Fig. 7 is that the different clients of the embodiment of the present application receive and dispatch the example flow diagram of big message.In this example, caller RCS
User is accessed using standard SIP protocol, and called subscriber is using OTT registration accesses.
As shown in fig. 7, the flow of the present embodiment includes：
S401 to S403, user A (this example is calling subscribe) client send standard SIP INVITE signalings；Pass through system
One access platform is forwarded to the agreement supporting module of business platform protocol adaptation；Agreement supporting module sends out SIP INVITE signalings
It is sent to the node traffic module of user A ownership；
The node traffic module of S404 to S406, user A ownership receives SIP INVITE signalings and returns to success response message
(200OK) is to agreement supporting module；Success response message is returned to user A visitors by agreement supporting module by being uniformly accessed into platform
Family end；
S407 to S408, user A clients according to SIP INVITE signaling negotiations establish media transmission channel, and (MRSP leads to
Road), and the media transmission channel for passing through foundation sends the section that message (corresponding to the first above-mentioned protocol message) belongs to user A
Point business module；
The message that the node traffic module storage of S409, user A ownership receives；
The node traffic module of S410, user A ownership returns to success response message (MRSP 200OK) and gives user A client
End；
After the node traffic module of S411, user A ownership carries out business logic processing to the message of reception, by disappearing for reception
The corresponding message queue module of breath write-in user's A clients；The node traffic module of user A ownership terminates to user's A clients
Processing after, start the write operation of the message queue module of user B；
S412, the corresponding message queue modules of user B have new information to send to the node traffic module notice that user B belongs to
It reaches；
Illustratively, the node traffic module of S413 to S414, user B ownership judges the message size of caller transmission, if
Message size is less than 8K, then according to user registration state and registration type, issues SIP MESSAGE message to the association of protocol adaptation
Supporting module is discussed, SIP MESSAGE message can carry protocol conversion instruction information, and protocol conversion instruction information can such as wrap
Include message content, the facility information of user's B clients and protocol type, the facility information and protocol class of user's A clients
Type；
The SIP MESSAGE message that the node traffic module that user B belongs to issues is converted by S415, agreement supporting module
OTT protocol messages (Notify message) (correspond to above-mentioned second protocol message)；Agreement supporting module group is bundled into user B client
Acceptable messaging protocol packet is held to be issued to and is uniformly accessed into platform；
S416, being uniformly accessed into platform, most OTT protocol messages are successfully issued in the client of user B at last, and user B is used
OTT clients on receive message content and directly present；
S417 to S419, user B clients by be uniformly accessed into platform and agreement supporting module to business module return into
Work(response message (200OK).
Illustratively, the node traffic module of S420 to S421, user B ownership judges that the message of caller transmission is more than 8K,
Then according to user registration state and registration type, SIP MESSAGE message is issued to agreement supporting module, wherein, SIP
MESSAGE message can carry protocol conversion instruction information；Protocol conversion instruction information can such as include business module and store
The URL addresses of message content, the facility information of user's B clients and protocol type, user's A clients facility information and
Protocol type；
The SIP MESSAGE message that the node traffic module that user B belongs to issues is converted by S422, agreement supporting module
OTT protocol messages (correspond to above-mentioned second protocol message)；Agreement supporting module group is bundled into that user's B clients are acceptable to disappear
Breath protocol package, which is issued to, is uniformly accessed into platform；
S423, being uniformly accessed into platform, most OTT protocol messages are successfully issued in the client of user B at last；
S424 to S426, user B clients by be uniformly accessed into platform and agreement supporting module to business module return into
Work(response message (200OK)；
S427, user B clients obtain message content, and the OTT client used in user B according to the URL addresses received
It is presented on end.
It should be noted that in this example, according to the judgement result of message size select to perform S413 to S419 or
Selection performs S420 to S427.
Fig. 8 is that the different clients of the embodiment of the present application receive and dispatch another example flow diagram of big message.In this example, caller
User is called RCS user and is accessed using standard SIP protocol using OTT registration accesses.
As shown in figure 8, the flow of the present embodiment includes：
S501 to S504, user A (this example is calling subscribe) client judge the message size of caller transmission；If message
Size is less than 8K, and user A clients send OTT protocol messages；Business platform protocol adaptation is forwarded to by being uniformly accessed into platform
Agreement supporting module；OTT protocol messages are converted to SIP INVITE requests and are transferred to business module by agreement supporting module；Industry
The message that business module storage receives.
Illustratively, the message size that S505 to S511, the judgement caller of user A clients are transmitted is more than 8K, user A client
End sends HTTP XCAP protocol messages；The agreement supporting module of business platform protocol adaptation is forwarded to by being uniformly accessed into platform；
Agreement supporting module is converted into inside story PUT message, is sent to business module；The message that business module storage receives, and
Storage address is returned to user A clients；User A clients send OTT protocol messages, wherein carrying the storage of message content
Location；The agreement supporting module of business platform protocol adaptation is forwarded to by being uniformly accessed into platform；Agreement supporting module is by OTT agreements
Message is converted to SIP INVITE requests and is transferred to business module；
It should be noted that in this example, selected to perform S501 to S504, Huo Zhexuan according to the judgement result of message size
It selects and performs S505 to S511.
After the node traffic module of S512, user A ownership carries out business logic processing to the message of reception, by disappearing for reception
The corresponding message queue modules of breath write-in user A, and return to successfully service response to user's A clients；The node of user A ownership
After business module terminates the processing to user A, start the write operation of the message queue module of user B；
S513, the node traffic module notice that the message queue module of user B belongs to user B have new information to be sent to；
The node traffic module of S514 to S515, user B ownership judges the message size of caller transmission, if message size
Less than 8K, then according to user registration state and registration type, SIP INVITE signalings are issued to the agreement branch hold mode of protocol adaptation
Block, wherein carrying protocol conversion instruction information, protocol conversion instruction information can such as include message content, user's B clients
Facility information and protocol type, the facility information and protocol type of user's A clients；
S516 to S517, agreement supporting module issue SIP INVITE messages by being uniformly accessed into platform；
After S518 to S520, user's B clients receive message, success response message (200OK) is returned to being uniformly accessed into
Platform；It is uniformly accessed into the node traffic module that success response message is returned to user B ownership by platform by agreement supporting module.
Illustratively, if the node traffic module of S521 to S525, user B ownership determines the message size of caller transmission
More than 8K, then SIPINVITE scheduling requests are issued to agreement supporting module；Agreement supporting module will by being uniformly accessed into platform
SIP INVITE transmitting signaling downwards, wherein carrying the media channel transmission mark for needing to negotiate to establish；The node traffic of user B ownership
Module establishes media transmission channel (MSRP channels) according to SIP session signalings and the negotiation of user B clients, send message content to
The client of user B；User B receives the message content sent by MSRP channels, is received in the RCS clients that user B is used
Business is presented；
S526 to S528, user B clients return to success response message (200OK) to platform is uniformly accessed into, and are uniformly accessed into
Success response message is returned to the node traffic module of user B ownership by platform by agreement supporting module.
It should be noted that in this example, according to the judgement result of message size select to perform S514 to S520 or
Selection performs S521 to S528.
In conclusion integration message system provided in this embodiment, simplifies complicated various types of messages system architecture, fusion
It is the characteristics of each business, user-friendly, improve user experience.Integration message system provided in this embodiment is total using message
Line architecture, framework is simple, deployment is convenient；Moreover, being uniformly accessed into for different type end is adapted to by protocol layer, and by uniformly disappearing
The distribution scheduling of Queue module is ceased, converged message is sent on the different ends of user.Illustratively, integration message system uses
Standard agreement framework and OTT agreement frameworks are combined, the interface of client and internet message platform, and unified be abstracted can be used
OTT interface protocols, client and integration message system can seamlessly transit according to demand.
Fig. 9 is the flow chart of message treatment method provided by the embodiments of the present application.Message processing provided in this embodiment
Method can be performed by above-mentioned integration message system.As shown in figure 9, message treatment method provided in this embodiment, including：
S901, the first protocol message is received from the transmission client using the access of the first agreement；
S902, the first protocol message is converted to the second protocol that the reception client that is accessed using second protocol is supported disappears
Breath；
S903, second protocol message is sent to reception client.
In the exemplary embodiment, S902 can include：
According to the first protocol message and the end log-on message of storage, the protocol conversion instruction letter of the first protocol message is determined
Breath；
Information is indicated according to protocol conversion, is converted to second protocol message.
In the exemplary embodiment, the message treatment method of the present embodiment can also include：
According to the conflict rule table of the log-on message and storage received from one or more clients, the registration of update end
Information；Wherein, end log-on message includes at least：The user online status and registration type of one or more clients, registration
Type can indicate the access protocol that client is supported；Conflict rule token records the registration class that can be coexisted in same client
Type.
In the exemplary embodiment, S902 can include：
If the size of the first protocol message is less than preset value, it is converted to the message content of the first protocol message of carrying
Second protocol message；
If the size of the first protocol message is greater than or equal to preset value, it is converted to the storage for carrying the first protocol message
The second protocol message of address.
In the exemplary embodiment, after S901, the message treatment method of the present embodiment can also include：
Protocol conversion is carried out to the first protocol message, obtains second protocol message；
If the size of the first protocol message is greater than or equal to preset value, the media transmission between client is established and received
Channel transmits second protocol message by media transmission channel.
In the exemplary embodiment, the first protocol message can be OTT protocol messages, and second protocol message can be to melt
Hop communication standard protocol message, such as Session Initiation Protocol message；Disappear alternatively, the first protocol message can be converged communication standard agreement
Breath, second protocol message can be OTT protocol messages.
Related description about message treatment method provided in this embodiment is referred to the description of above system embodiment,
Therefore it is repeated no more in this.
In addition, the embodiment of the present application also provides a kind of computer-readable medium, message processing program is stored with, at the message
The step of reason program realizes message treatment method as described above when being executed by processor.
It will appreciated by the skilled person that whole or certain steps, system, dress in method disclosed hereinabove
Function module or unit in putting may be implemented as software, firmware, hardware and its appropriate combination.In hardware embodiment
In, the division between the function module or unit that refer in the above description not necessarily corresponds to the division of physical assemblies；For example,
One physical assemblies can have multiple functions or a function or step that can be performed by several physical assemblies cooperations.Certain
A little components or all components may be implemented as by processor, the software that is performed such as digital signal processor or microprocessor or
Person is implemented as hardware or is implemented as integrated circuit, such as application-specific integrated circuit.Such software can be distributed in computer
On readable medium, computer-readable medium can include computer storage media (or non-transitory medium) and communication media (or
Fugitive medium).As known to a person of ordinary skill in the art, term computer storage medium is included in store information
Implement in any method or technique of (such as computer-readable instruction, data structure, program module or other data) volatile
Property and non-volatile, removable and nonremovable medium.Computer storage media includes but not limited to RAM, ROM, EEPROM, sudden strain of a muscle
It deposits or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storages, magnetic holder, tape, disk storage
Or other magnetic memory apparatus or it can be used for any other Jie that stores desired information and can be accessed by a computer
Matter.In addition, known to a person of ordinary skill in the art be, communication media generally comprises computer-readable instruction, data structure, journey
Other data in the modulated data signal of sequence module or such as carrier wave or other transmission mechanisms etc, and may include any
Information delivery media.
Although the embodiment disclosed by the application is as above, the content only for ease of understanding the application and use
Embodiment is not limited to the application.Technical staff in any the application fields, is taken off not departing from the application
Under the premise of the spirit and scope of dew, any modification and variation, but the application can be carried out in the form and details of implementation
Scope of patent protection, still should be subject to the scope of the claims as defined in the appended claims.
Claims (15)
1. a kind of integration message system, which is characterized in that including：
Access platform and business platform；
Wherein, the access platform connects the business platform；
The access platform is configured to receive the first protocol message from the transmission client using the access of the first agreement；
The business platform is configured to being converted to first protocol message into the reception client branch accessed using second protocol
The second protocol message held；
The access platform is additionally configured to send the second protocol message to the reception client.
2. system according to claim 1, which is characterized in that the business platform includes：Agreement supporting module and industry
Business module；The agreement supporting module connects the business module；
Wherein, the business module is configured to the end log-on message according to first protocol message and storage, determines described
The protocol conversion instruction information of first protocol message, and send the protocol conversion and indicate information to the agreement supporting module；
The agreement supporting module is configured to indicate information according to the protocol conversion, is converted to second protocol message, concurrently
The second protocol message is sent to the access platform.
3. system according to claim 2, which is characterized in that the business module is additionally configured to according to from one or more
The log-on message and the conflict rule table of storage that a client receives, update the end log-on message；
Wherein, the end log-on message includes at least：The user online status and registration class of one or more of clients
Type, the registration type can indicate the access protocol that the client is supported；The conflict rule token records same client
The registration type that can be coexisted on end.
4. system according to claim 2, which is characterized in that the agreement supporting module is adapted to provide for any two following associations
Conversion between view：Session initiation protocol, message session trunk protocol, hypertext transfer protocol, XCAP agreements, access-in management agreement
AOP, OTT agreement.
5. system according to claim 4, which is characterized in that the protocol Data Unit of the OTT agreements includes：Message header
Domain, one or more self-defined message domains；Wherein, any self-defined message domain includes message header part and message body portion.
6. system according to claim 2, which is characterized in that the business platform further includes：Unified message Queue module,
The business module is connected, the unified message Queue module is configured to store first association that the business module receives
Discuss message.
7. system according to claim 1, which is characterized in that if the size of first protocol message is less than preset value,
Then the second protocol message carries the message content of first protocol message；If the size of first protocol message is more than
Or the storage address equal to the preset value, then the second protocol message carrying first protocol message.
8. system according to claim 2, which is characterized in that the agreement supporting module is additionally configured to assist to described first
It discusses message and carries out protocol conversion, and the second protocol message being converted to is sent to the business module；
The business module is additionally configured to, when the size for judging first protocol message is greater than or equal to preset value, build
The vertical and described media transmission channel received between client transmits the second protocol by the media transmission channel and disappears
Breath.
9. a kind of message treatment method, which is characterized in that including：
The first protocol message is received from the transmission client using the access of the first agreement；
First protocol message is converted to the second protocol message supported using the reception client that second protocol accesses；
The second protocol message is sent to the reception client.
10. according to the method described in claim 9, it is characterized in that, described be converted to first protocol message using
The second protocol message that the reception client of two agreements access is supported, including：
According to first protocol message and the end log-on message of storage, determine that the protocol conversion of first protocol message refers to
Show information；
Information is indicated according to the protocol conversion, is converted to second protocol message.
11. according to the method described in claim 10, it is characterized in that, the method further includes：
According to the conflict rule table of the log-on message and storage received from one or more clients, the end registration is updated
Information；
Wherein, the end log-on message includes at least：The user online status and registration class of one or more of clients
Type, the registration type can indicate the access protocol that the client is supported；The conflict rule token records same client
The registration type that can be coexisted on end.
12. according to the method described in claim 9, it is characterized in that, described be converted to first protocol message using
The second protocol message that the reception client of two agreements access is supported, including：
If the size of first protocol message is less than preset value, it is converted in the message for carrying first protocol message
The second protocol message of appearance；
If the size of first protocol message is greater than or equal to the preset value, it is converted to carrying first agreement and disappears
The second protocol message of the storage address of breath.
13. the according to the method described in claim 9, it is characterized in that, transmission client from using the access of the first agreement
After receiving the first protocol message, the method further includes：
Protocol conversion is carried out to first protocol message, obtains second protocol message；
If the size of first protocol message is greater than or equal to preset value, the media between the reception client are established
Transmission channel transmits the second protocol message by the media transmission channel.
14. the method according to any one of claim 9 to 13, which is characterized in that first protocol message is assisted for OTT
Message is discussed, the second protocol message is converged communication standard protocol message；Alternatively, first protocol message is converged communication
Standard protocol message, the second protocol message are OTT protocol messages.
15. a kind of computer-readable medium, which is characterized in that be stored with message processing program, the message processing program is located
Manage the step of realizing the message treatment method as described in any one of claim 9 to 14 when device performs.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711435379.9A CN108156069A (en) | 2017-12-26 | 2017-12-26 | A kind of integration message system and message treatment method |
| PCT/CN2018/119994 WO2019128682A1 (en) | 2017-12-26 | 2018-12-10 | Convergent messaging system and message processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711435379.9A CN108156069A (en) | 2017-12-26 | 2017-12-26 | A kind of integration message system and message treatment method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108156069A true CN108156069A (en) | 2018-06-12 |
Family
ID=62462921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711435379.9A Pending CN108156069A (en) | 2017-12-26 | 2017-12-26 | A kind of integration message system and message treatment method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108156069A (en) |
| WO (1) | WO2019128682A1 (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109150290A (en) * | 2018-10-23 | 2019-01-04 | 中国科学院信息工程研究所 | A kind of satellite lightweight data transmission protection and ground safety service system |
| CN109274583A (en) * | 2018-09-25 | 2019-01-25 | 南京中兴软件有限责任公司 | A kind of converged communication system and its exchange method |
| WO2019128682A1 (en) * | 2017-12-26 | 2019-07-04 | 中兴通讯股份有限公司 | Convergent messaging system and message processing method |
| CN110875914A (en) * | 2018-09-03 | 2020-03-10 | 中国移动通信有限公司研究院 | Method and device for transmitting messages based on shared session link |
| WO2020135684A1 (en) * | 2018-12-29 | 2020-07-02 | 中兴通讯股份有限公司 | File transmission method between rcs systems, rcs interworking gateway, storage medium, and electronic device |
| CN112532712A (en) * | 2020-11-24 | 2021-03-19 | 青岛海尔科技有限公司 | Protocol transmission method and device, storage medium, and electronic device |
| CN113259231A (en) * | 2021-05-12 | 2021-08-13 | 中移(上海)信息通信科技有限公司 | Gateway equipment, information transmission method and device |
| CN114866604A (en) * | 2022-04-29 | 2022-08-05 | 北京国都互联科技有限公司 | Method and system for multi-type mobile message service fusion control |
| CN116437159A (en) * | 2023-03-14 | 2023-07-14 | 深圳感臻智能股份有限公司 | Data processing method, system and medium based on digital television protocol |
| US11743218B2 (en) | 2021-12-21 | 2023-08-29 | LeapXpert Limited | Message capture in a multi channel communication environment |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114157537A (en) * | 2021-12-08 | 2022-03-08 | 东风悦享科技有限公司 | System and method for realizing multi-source heterogeneous data access by general equipment gateway |
| CN114449013A (en) * | 2021-12-29 | 2022-05-06 | 深圳市巨鼎医疗股份有限公司 | Mutual compatible hospital framework of internet hospital |
| CN115150364A (en) * | 2022-06-29 | 2022-10-04 | 北京飞讯数码科技有限公司 | Service request processing system and method supporting multi-communication protocol concurrent communication |
| CN115314509A (en) * | 2022-07-27 | 2022-11-08 | 上海浦东发展银行股份有限公司 | Synchronization method, device, equipment and storage medium of application registration information |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1794705A (en) * | 2005-07-18 | 2006-06-28 | 华为技术有限公司 | Method and system of instant message user to use other immediate news system |
| US20060195613A1 (en) * | 2005-02-25 | 2006-08-31 | Kabushiki Kaisha Toshiba | Protocol conversion apparatus, communication apparatus, method and program |
| CN101212719A (en) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | Method and system for implementing converged message service in radio communication network |
| CN101552721A (en) * | 2008-04-03 | 2009-10-07 | 中兴通讯股份有限公司 | Convergence service system and service implementation method thereof |
| CN102143444A (en) * | 2010-09-02 | 2011-08-03 | 华为技术有限公司 | Method, relevant equipment and system for pushing service delivery platform message |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108156069A (en) * | 2017-12-26 | 2018-06-12 | 中兴通讯股份有限公司 | A kind of integration message system and message treatment method |
-
2017
- 2017-12-26 CN CN201711435379.9A patent/CN108156069A/en active Pending
-
2018
- 2018-12-10 WO PCT/CN2018/119994 patent/WO2019128682A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060195613A1 (en) * | 2005-02-25 | 2006-08-31 | Kabushiki Kaisha Toshiba | Protocol conversion apparatus, communication apparatus, method and program |
| CN1794705A (en) * | 2005-07-18 | 2006-06-28 | 华为技术有限公司 | Method and system of instant message user to use other immediate news system |
| CN101212719A (en) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | Method and system for implementing converged message service in radio communication network |
| CN101552721A (en) * | 2008-04-03 | 2009-10-07 | 中兴通讯股份有限公司 | Convergence service system and service implementation method thereof |
| CN102143444A (en) * | 2010-09-02 | 2011-08-03 | 华为技术有限公司 | Method, relevant equipment and system for pushing service delivery platform message |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019128682A1 (en) * | 2017-12-26 | 2019-07-04 | 中兴通讯股份有限公司 | Convergent messaging system and message processing method |
| CN110875914B (en) * | 2018-09-03 | 2022-06-07 | 中国移动通信有限公司研究院 | Method and device for transmitting messages based on shared session link |
| CN110875914A (en) * | 2018-09-03 | 2020-03-10 | 中国移动通信有限公司研究院 | Method and device for transmitting messages based on shared session link |
| CN109274583A (en) * | 2018-09-25 | 2019-01-25 | 南京中兴软件有限责任公司 | A kind of converged communication system and its exchange method |
| WO2020063585A1 (en) * | 2018-09-25 | 2020-04-02 | 中兴通讯股份有限公司 | Fusion communication system and interaction method therefor |
| CN109150290A (en) * | 2018-10-23 | 2019-01-04 | 中国科学院信息工程研究所 | A kind of satellite lightweight data transmission protection and ground safety service system |
| WO2020135684A1 (en) * | 2018-12-29 | 2020-07-02 | 中兴通讯股份有限公司 | File transmission method between rcs systems, rcs interworking gateway, storage medium, and electronic device |
| CN112532712A (en) * | 2020-11-24 | 2021-03-19 | 青岛海尔科技有限公司 | Protocol transmission method and device, storage medium, and electronic device |
| CN113259231A (en) * | 2021-05-12 | 2021-08-13 | 中移(上海)信息通信科技有限公司 | Gateway equipment, information transmission method and device |
| US11743218B2 (en) | 2021-12-21 | 2023-08-29 | LeapXpert Limited | Message capture in a multi channel communication environment |
| CN114866604A (en) * | 2022-04-29 | 2022-08-05 | 北京国都互联科技有限公司 | Method and system for multi-type mobile message service fusion control |
| CN114866604B (en) * | 2022-04-29 | 2023-12-29 | 北京国都互联科技有限公司 | Method and system for fusion control of multi-type mobile message service |
| CN116437159A (en) * | 2023-03-14 | 2023-07-14 | 深圳感臻智能股份有限公司 | Data processing method, system and medium based on digital television protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019128682A1 (en) | 2019-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108156069A (en) | A kind of integration message system and message treatment method | |
| CN102893572B (en) | For online communication session registered client computing equipment | |
| KR101252609B1 (en) | Push-type telecommunications accompanied by a telephone call | |
| CN110268729A (en) | To Internet of Things (IOT) equipment supply equipment and/or Line sharing ability | |
| US20170034149A1 (en) | Intelligent Communications Method, Terminal, and System | |
| CN102025719B (en) | Next generation integration between different domains using sequencing applications and IMS peering | |
| CN103517266B (en) | Method for activating mobile terminal on mobile network side and mobile gateway system | |
| CN103597783A (en) | System and method for secure instant messaging | |
| US20130336308A1 (en) | Call Invites | |
| CN106416208A (en) | Answering a call with client through a host | |
| CN102474508A (en) | Hierarchal Structuring Of Nodes In A Peer-To-Peer Network | |
| JP2021012710A (en) | Managing multiple profiles for single account in asynchronous messaging system | |
| CN102958107A (en) | Capability query method, communication terminal and application server | |
| CN109688364A (en) | Video-meeting method, device, server and storage medium | |
| CN102035813A (en) | End-to-end call realizing method, end-to-end call terminal and system | |
| CN110178354A (en) | Message session trunk protocol/hypertext transfer protocol file transmission | |
| CN104125221B (en) | IMS (IP (Internet Protocol) multimedia subsystem) terminal equipment multiple soft-terminal resource sharing and application collaborative device and method | |
| CN102611948A (en) | Method for sharing and issuing audios and videos of mobile internet terminal | |
| WO2015027721A1 (en) | Terminal status subscription method, apparatus and system | |
| CN101442505A (en) | Method and apparatus for implementing scene mode share | |
| CN109644178A (en) | RCS originates bifurcated | |
| WO2011120264A1 (en) | System and method for implementing voice call visualization service | |
| CN105743766B (en) | A kind of group communication method and device | |
| CN107343285B (en) | Management equipment and equipment management method | |
| KR101330910B1 (en) | System and Method for Providing Contents Within Packet Call Waiting Time |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180612 |
|
| RJ01 | Rejection of invention patent application after publication |