CN112020063B - Registration method, terminal and server for rich communication suite RCS service - Google Patents
Registration method, terminal and server for rich communication suite RCS service Download PDFInfo
- Publication number
- CN112020063B CN112020063B CN201910470889.2A CN201910470889A CN112020063B CN 112020063 B CN112020063 B CN 112020063B CN 201910470889 A CN201910470889 A CN 201910470889A CN 112020063 B CN112020063 B CN 112020063B
- Authority
- CN
- China
- Prior art keywords
- registration
- terminal
- registration message
- message
- server
- 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.)
- Active
Links
Images
Classifications
-
- 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
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention provides a registration method, a terminal and a server for a Rich Communication Suite (RCS) service, wherein the registration method for the Rich Communication Suite (RCS) service comprises the following steps: under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server; receiving authentication information fed back by the server according to the first registration message; sending a second registration message carrying a feature identifier to the server according to the authentication information; receiving a first registration success response fed back by the server according to the second registration message; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal. The scheme can effectively reduce the message overhead of the registration flow, improve the registration speed, reduce the probability of network interference on the registration flow, and well solve the problem that the registration failure is easily caused by overlarge registration message in the prior art.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, a terminal, and a server for registering a rich communication suite RCS service.
Background
At present, before using RCS (Rich Communication Suite) service, a terminal needs to register with an RCS Server (RCS Server) first, and after the registration is successful, the functions provided by the RCS service, including sending multimedia messages, making voice calls, and the like, can be used.
There are two types of registrations in the RCS service: first registration and refresh registration. The former is a registration flow which is initiated by a terminal (UE) when logging in each time and interacts with a platform under the condition that corresponding terminal registration information does not exist or is invalid on the platform side; the latter is a refresh registration flow which is initiated at regular time for maintaining timeliness of registration information and interacts with the platform after the terminal logs in each time.
Further, to meet the requirement of abundant terminal messages, the GSMA (global system for mobile communications) standard defines a Feature Tag parameter field in the REGISTER message for describing the service types supported by the terminal, such as 11 optional service types listed in the following table 1:
TABLE 1 Feature Tag parameter types carried by REGISTER messages
The terminal registration is classified into two types, namely first registration and refresh registration, and specifically, the sizes of the message messages in the first registration and refresh registration processes are respectively shown in tables 2 and 3:
table 2 first registration message type and size
Table 3 type and size of refresh registration packet
In the prior art, feature Tag parameters are carried in Contact fields of two REGISTER messages which are registered for the first time and a REGISTER message which is registered for refreshing, and are used for indicating the service capability (set) of the terminal to a platform. The REGISTER message of the terminal at least includes 11 Feature Tag parameters indicating different service capabilities, and the total size is 877 bytes, which is specifically shown in table 4 below:
TABLE 4 size of Feature Tag parameter carried in REGISTER message Contact field
In the first registration and the refresh registration, the message overhead caused by the parameters respectively accounts for 32.3% and 33.0% of the total message of the first registration and the refresh registration.
Since the SIP message is in a text format, the encoding efficiency is low, which causes a large message interaction and a long interaction time in the registration process. In a weak network environment, the long interaction time increases the probability of network interference on the registration process, which may possibly result in registration failure. The Feature Tag field message of the registration message greatly increases the probability of registration failure.
Disclosure of Invention
The invention aims to provide a registration method, a terminal and a server for rich communication suite RCS service, and solves the problem that registration failure is easily caused by overlarge registration message in the prior art.
In order to solve the above technical problem, an embodiment of the present invention provides a method for registering a rich communication suite RCS service, where the method is applied to a terminal, and the method includes:
under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server;
receiving authentication information fed back by the server according to the first registration message;
sending a second registration message carrying a feature identifier to the server according to the authentication information;
receiving a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
Optionally, after receiving a first registration success response fed back by the server according to the second registration message, the registration method further includes:
under the condition of refreshing and registering, sending a third registration message carrying the characteristic identifier to the server;
receiving a second registration success response fed back by the server according to the third registration message;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Optionally, the preset identifier is a preset vocabulary, a preset number or a preset symbol.
The embodiment of the invention also provides a registration method of the rich communication suite RCS service, which is applied to a server and comprises the following steps:
receiving a first registration message which is sent by a terminal and does not carry a characteristic identifier;
feeding back authentication information to the terminal according to the first registration message;
receiving a second registration message which is sent by the terminal according to the authentication information and carries the characteristic identification;
according to the second registration message, feeding back a first registration success response to the terminal so that the terminal completes the first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
Optionally, after feeding back a first registration success response to the terminal according to the second registration message, the method further includes:
receiving a third registration message which is sent by the terminal and carries the characteristic identifier;
feeding back a second registration success response to the terminal according to the third registration message so as to enable the terminal to complete refreshing registration;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Optionally, the preset identifier is a preset vocabulary, a preset number or a preset symbol.
The embodiment of the invention also provides a terminal, which comprises a processor and a transceiver, wherein the processor is used for:
under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server through the transceiver;
receiving authentication information fed back by the server according to the first registration message through the transceiver;
according to the authentication information, sending a second registration message carrying a feature identifier to the server through the transceiver;
receiving, by the transceiver, a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is information of the service type supported by the terminal.
Optionally, the processor is further configured to:
after receiving a first registration success response fed back by the server according to the second registration message through the transceiver, sending a third registration message carrying a feature identifier to the server through the transceiver under the condition of refreshing registration;
receiving, by the transceiver, a second registration success response fed back by the server according to the third registration message;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Optionally, the preset identifier is a preset vocabulary, a preset number, or a preset symbol.
An embodiment of the present invention further provides a server, including a processor and a transceiver, where the processor is configured to:
receiving a first registration message which is sent by a terminal and does not carry a characteristic identifier through the transceiver;
feeding back authentication information to the terminal through the transceiver according to the first registration message;
receiving a second registration message which is sent by the terminal according to the authentication information and carries a feature identifier through the transceiver;
according to the second registration message, feeding back a first registration success response to the terminal through the transceiver so as to enable the terminal to complete the first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
Optionally, the processor is further configured to:
after a first registration success response is fed back to the terminal through the transceiver according to the second registration message, receiving a third registration message which is sent by the terminal and carries a feature identifier through the transceiver;
according to the third registration message, feeding back a second registration success response to the terminal through the transceiver so as to enable the terminal to complete refreshing registration;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Optionally, the preset identifier is a preset vocabulary, a preset number or a preset symbol.
The embodiment of the invention also provides a terminal, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; and when the processor executes the program, the registration method of the rich communication suite RCS service at the terminal side is realized.
The embodiment of the invention also provides a server, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; and when the processor executes the program, the processor realizes the registration method of the rich communication suite RCS service at the server side.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps in the method for registering the rich communication suite RCS service at the terminal side; or
The program realizes the steps in the registration method of the rich communication suite RCS service at the server side when being executed by a processor.
The technical scheme of the invention has the following beneficial effects:
in the above scheme, the registration method of the rich communication suite RCS service sends a first registration message that does not carry a feature identifier to a server by performing first registration; receiving authentication information fed back by the server according to the first registration message; sending a second registration message carrying a feature identifier to the server according to the authentication information; receiving a first registration success response fed back by the server according to the second registration message; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal; the method can effectively reduce the message overhead of the registration process, improve the registration speed, reduce the probability of network interference on the registration process, and well solve the problem that the registration is easy to fail due to overlarge registration message in the prior art.
Drawings
Fig. 1 is a first flowchart illustrating a registration method of a rich communication suite RCS service according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a second method for registering a rich communication suite RCS service according to an embodiment of the present invention;
fig. 3 is a first flowchart illustrating a specific application of a registration method for an RCS service of a rich communication suite according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a specific application flow of a registration method for an RCS service of a rich communication suite according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a server structure according to an embodiment of the present invention.
Detailed Description
To make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
The present invention provides a registration method of rich communication suite RCS service, which is applied to a terminal, as shown in fig. 1, and includes:
step 11: under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server;
step 12: receiving authentication information fed back by the server according to the first registration message;
step 13: sending a second registration message carrying a feature identifier to the server according to the authentication information;
step 14: receiving a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is information of the service type supported by the terminal.
According to the registration method of the rich communication suite RCS service, provided by the embodiment of the invention, a first registration message which does not carry a feature identifier is sent to a server under the condition of first registration; receiving authentication information fed back by the server according to the first registration message; sending a second registration message carrying a feature identifier to the server according to the authentication information; receiving a first registration success response fed back by the server according to the second registration message; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal; the message cost of the registration process can be effectively reduced, the registration speed is improved, the probability that the registration process is interfered by a network is reduced, and the problem that the registration is failed due to overlarge registration message in the prior art is well solved.
Further, after receiving a first registration success response fed back by the server according to the second registration message, the registration method further includes: under the condition of refreshing and registering, sending a third registration message carrying the characteristic identifier to the server; receiving a second registration success response fed back by the server according to the third registration message; the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Therefore, the message overhead of the registration flow can be further reduced, the registration speed is improved, and the probability of network interference on the registration flow is reduced.
Specifically, the preset identifier may be a preset word, a preset number, or a preset symbol, but is not limited thereto.
An embodiment of the present invention further provides a method for registering a rich communication suite RCS service, which is applied to a server, and as shown in fig. 2, the method includes:
step 21: receiving a first registration message which is sent by a terminal and does not carry a feature identifier;
step 22: feeding back authentication information to the terminal according to the first registration message;
step 23: receiving a second registration message which is sent by the terminal according to the authentication information and carries the characteristic identification;
step 24: according to the second registration message, feeding back a first registration success response to the terminal so that the terminal completes the first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
According to the registration method of the rich communication suite RCS service, provided by the embodiment of the invention, a first registration message which is sent by a receiving terminal and does not carry a feature identifier is received; feeding back authentication information to the terminal according to the first registration message; receiving a second registration message which is sent by the terminal according to the authentication information and carries the characteristic identification; according to the second registration message, feeding back a first registration success response to the terminal so as to enable the terminal to complete the first registration; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal; the message cost of the registration process can be effectively reduced, the registration speed is improved, the probability that the registration process is interfered by a network is reduced, and the problem that the registration is failed due to overlarge registration message in the prior art is well solved.
Further, after feeding back a first registration success response to the terminal according to the second registration message, the method further includes: receiving a third registration message which is sent by the terminal and carries the feature identifier; feeding back a second registration success response to the terminal according to the third registration message so as to enable the terminal to complete refreshing registration; the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Therefore, the message overhead of the registration process can be further reduced, the registration speed is improved, and the probability of network interference on the registration process is reduced.
Specifically, the preset identifier may be a preset word, a preset number, or a preset symbol, but is not limited thereto.
The method for registering the rich communication suite RCS service provided in the embodiment of the present invention is further described below with reference to both sides of the terminal and the Server, where the Server takes an RCS Server (RCS Server) as an example, and the preset identifier takes a preset vocabulary unchanged as an example.
In view of the above technical problems, embodiments of the present invention provide a registration method for RCS services, which may specifically be an optimization scheme for a field parameter Feature Tag (i.e., the above Feature identifier) carried in a registration message of an RCS terminal, so that message overhead of a registration procedure can be effectively reduced, registration speed is increased, and probability of network interference on the registration procedure is reduced; specifically, in order to reduce the message size of the RCS terminal registration process, reduce the degree of dependence on the network in the registration process, improve the registration success rate, and save the network overhead, the embodiment of the present invention provides the above registration method.
The scheme provided by the embodiment of the invention is illustrated below.
Example one, for first registration procedure optimization:
the terminal first initiates a first REGISTER message (i.e. the first registration message) to the RCS Server, which replies 401 to the terminal with an authentication challenge (i.e. the authentication message). In the process, the RCS Server does not care which service types are supported by the terminal; therefore, the first REGISTER message sent in the embodiment of the present invention does not carry the Feature Tag parameter, and only carries the Feature Tag parameter in the second REGISTER message (i.e. the second registration message) initiated by the terminal. The RCS Server replies 200 to the terminal (i.e. the first registration success response), and may confirm the service type supported by the terminal after the authentication is successful.
Specifically, as shown in fig. 3, the optimized RCS terminal first registration process includes:
step 31: the terminal sends a first REGISTER message to the RCS Server; this message does not carry the Feature Tag parameter.
Step 32: the RCS Server initiates 401 an authentication challenge to the terminal (i.e. sends authentication information to the terminal);
step 33: the terminal receives the challenge, and initiates a second REGISTER request to the RCS Server (i.e. sends a second REGISTER message to the RCS Server), which indicates that the terminal successfully authenticates the RCS Server. The REGISTER message carries the Feature Tag parameter.
Step 34: the RCS Server authenticates the terminal successfully, replies 200 to the terminal, and the registration process is finished.
By adopting the method of the example, the message registered by the terminal for the first time can be reduced by 877 bytes, the total message registered is reduced by 16.1%, the registration speed is increased, and the probability of network interference on the registration process is reduced.
Example two, optimization is performed for the refresh registration procedure (in this example, the Feature Tag is extended with a new parameter definition "exchanged" for the terminal refresh registration procedure):
in this example, for a refresh registration process which is initiated at regular time for maintaining timeliness of registration information and interacts with a platform after a terminal completes first registration, if a service type supported by the terminal does not change, it is only necessary to fill "exchanged" in a Feature Tag field to indicate that the service type does not change; and the service types supported by the terminal are not changed in 99% of scenes, so that the probability of network interference on the registration process can be greatly reduced.
Specifically, as shown in fig. 4, the optimized RCS terminal refresh registration process includes:
step 41: the terminal sends a REGISTER message (i.e. the third registration message) to the RCS Server; the Feature Tag parameter carried by this message fills in "exchanged".
Step 42: the RCS Server authenticates the terminal successfully, replies 200 to the terminal (i.e., the second registration success response), and the refresh registration process is ended.
In this example, for the refresh registration process, in the case that the service type supported by the terminal is unchanged (unchanged in 99% of scenes), only "unchanged" with a size of 9 bytes is needed to replace the original service type with a total length of 877 bytes, so that the refresh registration message can be reduced by 32.6%, the registration speed is increased, and the probability of network interference on the registration process is reduced.
As can be seen from the above, the scheme provided by the embodiment of the present invention mainly relates to:
(1) In the first registration process, the first REGISTER message does not carry the Feature Tag parameter, and the RCS Server only needs to analyze the second REGISTER message, thereby saving the message interaction amount and reducing the system capacity pressure.
(2) And expanding the Feature Tag message field, and adding an 'unchanged' definition to the Feature Tag message field, wherein the Feature Tag message field is used for updating the REGISTER message of the registration process. When the terminal refreshes a registration flow, if the type of a salesman supported by the terminal is not changed compared with the last registration, only a newly defined 'unchanged' parameter needs to be filled; in fact, almost all the terminals can not change the service types supported in the process of refreshing the registration, so that the scheme can greatly reduce the size of the registration message, shorten the message interaction and analysis time, and reduce the influence coefficient of the network environment on the registration success rate.
To sum up, the scheme provided by the embodiment of the invention is as follows: the first REGISTER message sent by the terminal to the server in the first registration process does not need to carry the Feature Tag parameter, and only needs to carry the Feature Tag parameter in the second REGISTER message; the message size of the first registration process is reduced, the system overhead is reduced, and the influence of the network environment on the registration success rate is reduced;
furthermore, parameter definition extension is carried out on the Feature Tag field of the REGISTER message, so that the condition that the REGISTER message sent by registration at each time needs to carry a complete set of service types supported by the terminal is avoided, the message interaction amount for refreshing the registration is greatly reduced, and the system overhead is reduced.
An embodiment of the present invention further provides a terminal, as shown in fig. 5, including a processor 51 and a transceiver 52, where the processor 51 is configured to:
under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server through the transceiver 52;
receiving, by the transceiver 52, authentication information fed back by the server according to the first registration message;
according to the authentication information, sending a second registration message carrying a feature identifier to the server through the transceiver 52;
receiving, by the transceiver 52, a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is information of the service type supported by the terminal.
The terminal provided by the embodiment of the invention sends a first registration message which does not carry a characteristic identifier to a server through the transceiver under the condition of first registration; receiving authentication information fed back by the server according to the first registration message through the transceiver; sending a second registration message carrying a feature identifier to the server through the transceiver according to the authentication information; receiving, by the transceiver, a first registration success response fed back by the server according to the second registration message; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal; the method can effectively reduce the message overhead of the registration process, improve the registration speed, reduce the probability of network interference on the registration process, and well solve the problem that the registration is easy to fail due to overlarge registration message in the prior art.
Further, the processor is further configured to: after receiving a first registration success response fed back by the server according to the second registration message through the transceiver, sending a third registration message carrying a feature identifier to the server through the transceiver under the condition of refreshing registration; receiving, by the transceiver, a second registration success response fed back by the server according to the third registration message; wherein the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Specifically, the preset identifier may be a preset word, a preset number, or a preset symbol, but is not limited thereto.
The implementation embodiments of the method for registering the rich communication suite RCS service at the terminal side are all applicable to the embodiment of the terminal, and the same technical effect can be achieved.
An embodiment of the present invention further provides a server, as shown in fig. 6, including a processor 61 and a transceiver 62, where the processor 61 is configured to:
receiving a first registration message which is sent by the terminal and does not carry the feature identifier through the transceiver 62;
feeding back authentication information to the terminal through the transceiver 62 according to the first registration message;
receiving a second registration message which is sent by the terminal according to the authentication information and carries a feature identifier through the transceiver 62;
according to the second registration message, feeding back a first registration success response to the terminal through the transceiver 62, so that the terminal completes first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
The server provided by the embodiment of the invention receives a first registration message which is sent by a terminal and does not carry a characteristic identifier through the transceiver; feeding back authentication information to the terminal through the transceiver according to the first registration message; receiving a second registration message which is sent by the terminal according to the authentication information and carries a feature identifier through the transceiver; according to the second registration message, feeding back a first registration success response to the terminal through the transceiver so as to enable the terminal to complete the first registration; wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal; the message cost of the registration process can be effectively reduced, the registration speed is improved, the probability that the registration process is interfered by a network is reduced, and the problem that the registration is failed due to overlarge registration message in the prior art is well solved.
Further, the processor is further configured to: after a first registration success response is fed back to the terminal through the transceiver according to the second registration message, a third registration message which is sent by the terminal and carries a feature identifier is received through the transceiver; according to the third registration message, feeding back a second registration success response to the terminal through the transceiver so as to enable the terminal to complete refreshing registration; wherein the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
Specifically, the preset identifier may be a preset word, a preset number, or a preset symbol, but is not limited thereto.
The implementation embodiments of the method for registering the rich communication suite RCS service on the server side are all applicable to the embodiment of the server, and the same technical effect can be achieved.
The embodiment of the invention also provides a terminal, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; and when the processor executes the program, the processor realizes the registration method of the rich communication suite RCS service at the terminal side.
The implementation embodiments of the method for registering the rich communication suite RCS service at the terminal side are all applicable to the embodiment of the terminal, and the same technical effects can be achieved.
The embodiment of the invention also provides a server, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; and when the processor executes the program, the registration method of the rich communication suite RCS service at the server side is realized.
The implementation embodiments of the method for registering the rich communication suite RCS service on the server side are all applicable to the embodiment of the server, and the same technical effect can be achieved.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps in the method for registering the rich communication suite RCS service at the terminal side; or the program is executed by a processor to realize the steps in the registration method of the rich communication suite RCS service on the server side.
The implementation embodiments of the method for registering the rich communication suite RCS service at the terminal side or the server side are all applicable to the embodiment of the computer-readable storage medium, and the same technical effects can be achieved.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (12)
1. A registration method of rich communication suite RCS service is applied to a terminal, and is characterized by comprising the following steps:
under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server;
receiving authentication information fed back by the server according to the first registration message;
sending a second registration message carrying a feature identifier to the server according to the authentication information;
receiving a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
2. The registration method according to claim 1, wherein after receiving a first registration success response fed back by the server according to the second registration message, the registration method further comprises:
under the condition of refreshing and registering, sending a third registration message carrying the characteristic identifier to the server;
receiving a second registration success response fed back by the server according to the third registration message;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
3. The method of claim 2, wherein the predetermined identifier is a predetermined vocabulary, a predetermined number, or a predetermined symbol.
4. A registration method of Rich Communication Suite (RCS) service is applied to a server, and is characterized by comprising the following steps:
receiving a first registration message which is sent by a terminal and does not carry a characteristic identifier;
feeding back authentication information to the terminal according to the first registration message;
receiving a second registration message which is sent by the terminal according to the authentication information and carries the characteristic identification;
according to the second registration message, feeding back a first registration success response to the terminal so that the terminal completes the first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
5. The registration method according to claim 4, further comprising, after feeding back a first registration success response to the terminal according to the second registration message:
receiving a third registration message which is sent by the terminal and carries the feature identifier;
feeding back a second registration success response to the terminal according to the third registration message so as to enable the terminal to complete refreshing registration;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
6. The registration method of claim 5, wherein the predetermined identifier is a predetermined vocabulary, a predetermined number, or a predetermined symbol.
7. A terminal comprising a processor and a transceiver, wherein the processor is configured to:
under the condition of carrying out first registration, sending a first registration message which does not carry the characteristic identifier to a server through the transceiver;
receiving authentication information fed back by the server according to the first registration message through the transceiver;
sending a second registration message carrying a feature identifier to the server through the transceiver according to the authentication information;
receiving, by the transceiver, a first registration success response fed back by the server according to the second registration message;
wherein, the content of the feature identifier carried in the second registration message is information of the service type supported by the terminal.
8. The terminal of claim 7, wherein the processor is further configured to:
after receiving a first registration success response fed back by the server according to the second registration message through the transceiver, sending a third registration message carrying a feature identifier to the server through the transceiver under the condition of refreshing registration;
receiving, by the transceiver, a second registration success response fed back by the server according to the third registration message;
the content of the feature identifier carried in the third registration message is a preset identifier indicating that the service type supported by the terminal has not changed.
9. A server comprising a processor and a transceiver, wherein the processor is configured to:
receiving a first registration message which is sent by a terminal and does not carry a characteristic identifier through the transceiver;
feeding back authentication information to the terminal through the transceiver according to the first registration message;
receiving a second registration message which is sent by the terminal according to the authentication information and carries a feature identifier through the transceiver;
according to the second registration message, feeding back a first registration success response to the terminal through the transceiver so as to enable the terminal to complete the first registration;
wherein, the content of the feature identifier carried in the second registration message is the information of the service type supported by the terminal.
10. A terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor; a method for registering a rich communication suite, RCS, service according to any of claims 1 to 3, when the processor executes the program.
11. A server comprising a memory, a processor and a computer program stored on the memory and executable on the processor; a method for registering Rich Communication Suite (RCS) service according to any one of claims 4 to 6, wherein the processor executes the program.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of a method of registering a rich communication suite, RCS, service according to any one of claims 1 to 3; or
The program when executed by a processor implements the steps in a method for registration of rich communication suite, RCS, services of any of claims 4 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910470889.2A CN112020063B (en) | 2019-05-31 | 2019-05-31 | Registration method, terminal and server for rich communication suite RCS service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910470889.2A CN112020063B (en) | 2019-05-31 | 2019-05-31 | Registration method, terminal and server for rich communication suite RCS service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112020063A CN112020063A (en) | 2020-12-01 |
| CN112020063B true CN112020063B (en) | 2022-12-13 |
Family
ID=73501115
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910470889.2A Active CN112020063B (en) | 2019-05-31 | 2019-05-31 | Registration method, terminal and server for rich communication suite RCS service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112020063B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116367098A (en) * | 2021-12-27 | 2023-06-30 | 华为技术有限公司 | Information sending method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9642109B2 (en) * | 2013-08-21 | 2017-05-02 | Qualcomm Incorporated | Single network registration where multiple applications access the network using separate processors |
| US10594741B2 (en) * | 2014-08-04 | 2020-03-17 | T-Mobile Usa, Inc. | Suppressing third party registration and third party deregistration actions |
| FR3032854A1 (en) * | 2015-02-13 | 2016-08-19 | Orange | METHOD FOR CONFIGURING A TERMINAL CONNECTED TO A COMMUNICATION NETWORK |
| US10117211B2 (en) * | 2016-03-17 | 2018-10-30 | T-Mobile Usa, Inc. | Communication session registration- and subsidiary-request processing |
| CN109120408A (en) * | 2017-06-26 | 2019-01-01 | 中国电信股份有限公司 | For authenticating the methods, devices and systems of user identity |
-
2019
- 2019-05-31 CN CN201910470889.2A patent/CN112020063B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112020063A (en) | 2020-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102638797B (en) | Access the method for wireless network, terminal, access network node and authentication server | |
| EP1940107A1 (en) | A method for processing data synchronization and client terminal, server and data synchronization system thereof | |
| CN111328108B (en) | 5G service data processing method, device and distribution equipment | |
| US11375410B2 (en) | Method and apparatus for obtaining configuration information, device, storage medium, and system | |
| US8788612B1 (en) | Cache based enhancement to optimization protocol | |
| EP2469429A2 (en) | Method for synchronizing data, system, and apparatus thereof | |
| CN112020063B (en) | Registration method, terminal and server for rich communication suite RCS service | |
| US10771979B2 (en) | Fake base station short message identification | |
| US9582306B2 (en) | Method and system to dynamically instantiate virtual repository for any services | |
| CN103138871B (en) | The server data processing system of application program and method in mobile communcations system | |
| CN103532920A (en) | Cookie update method and cookie update system | |
| CN103313245B (en) | Based on the Network access method of mobile phone terminal, equipment and system | |
| US10735961B1 (en) | Service authentication and network preference with MMS services | |
| US8051129B2 (en) | Arrangement and method for reducing required memory usage between communication servers | |
| WO2021043178A1 (en) | Roaming control method and apparatus, udm device, and storage medium | |
| WO2021027474A1 (en) | Positioning assistance information broadcasting method, positioning server and ran node | |
| US20160149855A1 (en) | Service processing method, system, and relevant device | |
| CN110881017B (en) | Communication service registration method, system, electronic device, authentication method and server | |
| CN112738823A (en) | Interface data interaction method, distributed unit and central unit | |
| CN109548000B (en) | System, method and computer equipment for sharing and purchasing communication service | |
| CN103491159B (en) | Work order analysis asynchronous calling service method and system | |
| US8473625B1 (en) | Preservation of network address translation (NAT) state across wireless sessions | |
| CN112565088B (en) | Message processing method, system, device and network equipment | |
| CN116192970B (en) | Method and system for dynamically acquiring NAS coding and decoding rules based on IMEI | |
| CN103138872B (en) | In a kind of mobile communcations system, the data transmission system of application program is unified method |
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 |