CN113132337B - SIP (Session initiation protocol) registration method and device of cluster terminal - Google Patents
SIP (Session initiation protocol) registration method and device of cluster terminal Download PDFInfo
- Publication number
- CN113132337B CN113132337B CN202010039915.9A CN202010039915A CN113132337B CN 113132337 B CN113132337 B CN 113132337B CN 202010039915 A CN202010039915 A CN 202010039915A CN 113132337 B CN113132337 B CN 113132337B
- Authority
- CN
- China
- Prior art keywords
- sip
- token
- registration
- module
- terminal
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
- H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a SIP (session initiation protocol) registration method and device of a cluster terminal, wherein the method comprises the following steps: when a terminal receives an SIP registration failure message after initiating session initiation protocol SIP registration, resolving a registration failure reason from the SIP registration failure message; and when the registration failure reason is token verification failure, the terminal acquires the token from the network side again and performs SIP registration again by using the acquired token. By applying the technical scheme disclosed by the application, the problem that SIP re-registration always fails after TOKEN verification fails can be effectively solved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a Session Initiation Protocol (SIP) registration method and apparatus for a cluster terminal.
Background
In the mode of the existing 3GPP trunking application layer standard (session Critical Push To Talk over LTE, MCPTT), the implementation scheme of terminal login and SIP registration is as follows:
the terminal authenticates And logs in the User equipment management And control center (User And Device Controller, UDC), And the UDC can issue a TOKEN (TOKEN) to an Operation Management (OM) module of the terminal after the Device authentication And login succeeds. The OM module sends a broadcast of successful login, and triggers the SIP module to perform SIP registration with a Multimedia Dispatch Center (MDC). Before SIP registration, the SIP module will acquire TOKEN from OM module, and carry it in SIP registration (SIP REGISTER) message, and send it to MDC. After receiving the SIP REGISTER message, the MDC analyzes the user information and TOKEN, and at the same time obtains the TOKEN information of the user from the UDC, and performs verification, and if the verification fails, returns a terminal SIP registration failure message (SIP 403 fortiden message), where a warning code (warning code) carried therein is 387, to notify the terminal TOKEN that the verification fails. When SIP registration fails, the group call service, the point call service, the video point call return monitoring service and the like of the user all fail, and the SIP module performs SIP re-registration processes of small period and large period of the SIP.
The inventor finds that when the implementation scheme is adopted, the SIP re-registration always fails after the TOKEN check fails. After the inventor conducts research and analysis on the prior art, the reasons for the problems are as follows:
in practical application, when the primary server and the standby server are switched, the air interface transmission is wrong, or other unknown factors exist, so that after the terminal OM module successfully logs in, the TOKEN sent to the terminal OM module by the UDC is inconsistent with the TOKEN stored by the UDC. Thus, SIP registration fails due to TOKEN check failure. In this case, since the TOKEN used by the terminal for SIP registration and the corresponding TOKEN on the UDC side are always inconsistent, the registration cannot be successful no matter how many times of SIP re-registration is performed thereafter.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and an apparatus for SIP registration of a trunking terminal, which can effectively solve the problem that SIP re-registration always fails after TOKEN check fails.
In order to achieve the above purpose, the embodiment of the present invention provides a technical solution:
a SIP registration method of a cluster terminal comprises the following steps:
when a terminal receives an SIP registration failure message after initiating session initiation protocol SIP registration, resolving a registration failure reason from the SIP registration failure message;
and when the registration failure reason is token verification failure, the terminal acquires the token from the network side again and performs SIP registration again by using the acquired token.
Preferably, the terminal acquires the token from the network side again, and performing SIP registration again by using the acquired token includes:
the SIP module of the terminal informs the operation management OM module of the terminal of the failure of token verification;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, informing the SIP module that the login is successful;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
Preferably, the method further comprises:
and when the registration failure reason is not token verification failure, the terminal performs SIP registration again by using the current locally stored token.
An SIP registration device of a cluster terminal, comprising:
the SIP module is used for analyzing a registration failure reason from the SIP registration failure message when the SIP registration failure message is received after the terminal initiates the SIP registration of the session initiation protocol; and when the registration failure reason is token verification failure, triggering the operation management OM module to acquire the token from the network side again, and performing SIP registration again by using the acquired token.
Preferably, the SIP module is specifically configured to trigger the OM module to obtain a token from the network side again, and perform SIP registration again by using the obtained token, and includes:
the SIP module informs the OM module of token verification failure;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, informing the SIP module that the login is successful;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
Preferably, the SIP module further comprises:
and when the registration failure reason is not the token check failure, the SIP registration is carried out again by using the current locally-stored token.
The present application also discloses a non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the steps of the SIP registration method of a cluster terminal as described above.
The application also discloses an electronic device comprising the non-volatile computer-readable storage medium as described above, and the processor having access to the non-volatile computer-readable storage medium.
According to the technical scheme, the SIP registration method and the SIP registration device for the cluster terminal can effectively solve the problem that SIP re-registration always fails after TOKEN verification fails.
Drawings
FIG. 1 is a schematic flow chart of a method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a specific SIP registration flow implemented according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a schematic method flow diagram of an embodiment of the present invention, and as shown in fig. 1, an SIP registration method for a trunking terminal implemented in the embodiment mainly includes:
In this step, in order to solve the problem that SIP registration cannot be successfully performed all the time due to inconsistency between tokens in the terminal and the server, the reason for SIP registration failure needs to be analyzed, different failure conditions are distinguished, and the different failure conditions are processed respectively, instead of performing SIP registration again directly after SIP registration failure.
And 102, when the reason of the registration failure is token verification failure, the terminal acquires the token from the network side again and performs SIP registration again by using the acquired token.
In this step, when the terminal knows that the reason for the registration failure is token verification failure, it obtains a new token from the network side again, and initiates SIP registration again by using the obtained token. Therefore, because the token is newly acquired from the network side at present, SIP registration is reinitiated based on the token, and SIP registration failure caused by inconsistency between the token used for registration and the token of the network side can be effectively avoided.
Preferably, the terminal may obtain the token from the network side again by using the following method, and perform SIP registration again by using the obtained token:
the SIP module of the terminal informs the operation management OM module of the terminal of the failure of token verification;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, informing the SIP module that the login is successful;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
Preferably, in order to improve the compatibility of the present application with the existing system, when the terminal resolves that the reason for the registration failure is not the token verification failure, an existing failure handling mechanism may be used to perform corresponding handling, that is, the method further includes:
and when the registration failure reason is not token verification failure, the terminal performs SIP registration again by using the current locally stored token.
Fig. 2 is a schematic diagram of a specific flow of SIP registration when token verification fails based on the foregoing embodiment. As shown in fig. 2, when a terminal successfully initiates SIP registration to a multimedia scheduling center (MDC), and receives a SIP registration failure message with warning code 387 from the MDC, the SIP module notifies the OM module of token verification failure through broadcasting, the OM module re-initiates user registration to the UDC according to the notification, after the registration is successful, the UDC issues a new token to the terminal, the OM module of the terminal broadcasts the registration success to the SIP module, the SIP module acquires the new token from the OM module according to the notification, and re-initiates SIP registration by using the new token, thereby avoiding the problem that SIP registration cannot be successful all the time due to inconsistency of tokens in the terminal and the server.
Corresponding to the above method embodiment, the present application further provides a corresponding device embodiment, where the SIP registration device of the trunking terminal includes:
the SIP module is used for analyzing a registration failure reason from the SIP registration failure message when the SIP registration failure message is received after the terminal initiates the SIP registration of the session initiation protocol; and when the registration failure reason is token verification failure, triggering the operation management OM module to acquire the token from the network side again, and performing SIP registration again by using the acquired token.
Preferably, the SIP module is specifically configured to trigger the OM module to obtain a token from a network side again, and perform SIP registration again by using the obtained token, and includes:
the SIP module informs the OM module of token verification failure;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, informing the SIP module that the login is successful;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
Preferably, the SIP module further comprises:
and when the registration failure reason is not the token check failure, the SIP registration is carried out again by using the current locally-stored token.
The present application also discloses a non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the steps of the SIP registration method of a cluster terminal as described above.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (6)
1. A SIP registration method of a cluster terminal is characterized by comprising the following steps:
when a terminal receives an SIP registration failure message after initiating session initiation protocol SIP registration, resolving a registration failure reason from the SIP registration failure message;
and when the registration failure reason is token verification failure, the terminal acquires the token from the network side again and performs SIP registration again by using the acquired token.
2. The method of claim 1, wherein: the terminal acquires the token from the network side again, and the SIP registration is carried out again by using the acquired token comprises the following steps:
the SIP module of the terminal informs the operation management OM module of the terminal of the failure of token verification;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, informing the SIP module that the login is successful;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
3. The method of claim 1, wherein: the method further comprises:
and when the registration failure reason is not token verification failure, the terminal performs SIP registration again by using the current locally stored token.
4. An SIP registration apparatus for a trunking terminal, comprising:
the SIP module is used for analyzing a registration failure reason from the SIP registration failure message when the SIP registration failure message is received after the terminal initiates the SIP registration of the session initiation protocol; and when the registration failure reason is token verification failure, triggering the operation management OM module to acquire the token from the network side again, and performing SIP registration again by using the acquired token.
5. The apparatus of claim 4, wherein: the SIP module is specifically configured to trigger the OM module to acquire a token from a network side again, and perform SIP registration again by using the acquired token, and includes:
the SIP module informs the OM module of token verification failure;
the OM module triggers to log in the network side again according to the notice so as to obtain a new token; when the login is successful, the SIP module is informed of successful login;
and the SIP module acquires the new token from the OM module according to the notification and initiates SIP registration to a network side, wherein the corresponding SIP registration request carries the new token.
6. The apparatus of claim 4, wherein: the SIP module further comprises:
and when the registration failure reason is not the token check failure, the SIP registration is carried out again by using the current locally-stored token.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010039915.9A CN113132337B (en) | 2020-01-15 | 2020-01-15 | SIP (Session initiation protocol) registration method and device of cluster terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010039915.9A CN113132337B (en) | 2020-01-15 | 2020-01-15 | SIP (Session initiation protocol) registration method and device of cluster terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113132337A CN113132337A (en) | 2021-07-16 |
| CN113132337B true CN113132337B (en) | 2022-06-07 |
Family
ID=76771163
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010039915.9A Active CN113132337B (en) | 2020-01-15 | 2020-01-15 | SIP (Session initiation protocol) registration method and device of cluster terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113132337B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1913533A (en) * | 2006-09-05 | 2007-02-14 | 北京天地互连信息技术有限公司 | Remote video monitoring system based on session initialize protocol and its implementing method |
| WO2008035173A1 (en) * | 2006-09-20 | 2008-03-27 | Gemalto S.A. | A sip communication with a secure personal token for interacting with personal data. |
| CN103733701A (en) * | 2011-02-23 | 2014-04-16 | T移动美国公司 | System and method for subscribing for internet protocol multimedia subsystems (ims) services registration status |
| CN104168267A (en) * | 2014-07-23 | 2014-11-26 | 中国科学院信息工程研究所 | Identity authentication method for accessing SIP security video monitoring system |
| CN106162574A (en) * | 2015-04-02 | 2016-11-23 | 成都鼎桥通信技术有限公司 | Group system is applied universal retrieval method, server and terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ES2623474T3 (en) * | 2009-04-13 | 2017-07-11 | Blackberry Limited | System and method to determine the confidence of SIP messages |
-
2020
- 2020-01-15 CN CN202010039915.9A patent/CN113132337B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1913533A (en) * | 2006-09-05 | 2007-02-14 | 北京天地互连信息技术有限公司 | Remote video monitoring system based on session initialize protocol and its implementing method |
| WO2008035173A1 (en) * | 2006-09-20 | 2008-03-27 | Gemalto S.A. | A sip communication with a secure personal token for interacting with personal data. |
| CN103733701A (en) * | 2011-02-23 | 2014-04-16 | T移动美国公司 | System and method for subscribing for internet protocol multimedia subsystems (ims) services registration status |
| CN104168267A (en) * | 2014-07-23 | 2014-11-26 | 中国科学院信息工程研究所 | Identity authentication method for accessing SIP security video monitoring system |
| CN106162574A (en) * | 2015-04-02 | 2016-11-23 | 成都鼎桥通信技术有限公司 | Group system is applied universal retrieval method, server and terminal |
Non-Patent Citations (2)
| Title |
|---|
| On using multiple classifier systems for Session Initiation Protocol (SIP) anomaly detection;Anil Mehta .etl;《 2012 IEEE International Conference on Communications (ICC)》;20121029;全文 * |
| 基于SIP协议的多媒体通信系统的设计与实现;任子龙;《中国优秀硕士学位论文全文数据库》;20190815;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113132337A (en) | 2021-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108712485B (en) | Resource subscription method and device for Internet of things equipment | |
| US20210036907A1 (en) | Methods and apparatuses for pushing a message | |
| US8254872B2 (en) | Simplified method for IMS registration in the event of emergency calls | |
| US11563649B2 (en) | NF service consumer restart detection using direct signaling between NFs | |
| US9408110B2 (en) | Apparatus and method for handling error for service flow modification a broadband wireless communication network | |
| US10382931B2 (en) | Method for improved handling of emergency calls in a roaming scenario, telecommunications network, program and computer program product | |
| CN110674096B (en) | Node troubleshooting method, device and equipment and computer readable storage medium | |
| CN109525620B (en) | Message pushing system, method and device | |
| EP2555545A1 (en) | Method and system for selecting mobility management entity of terminal group | |
| EP4366334A1 (en) | Message processing method, electronic device, and storage medium | |
| EP3930379B1 (en) | Voice switching method and apparatus | |
| CN113132337B (en) | SIP (Session initiation protocol) registration method and device of cluster terminal | |
| CN105656912A (en) | Mobile intelligent terminal APP request process control method | |
| CN112637850A (en) | Method and system for processing authentication abnormity and user terminal | |
| CN115412974B (en) | Shunting communication method, device, equipment and readable storage medium | |
| CN110572350B (en) | Method and equipment for carrying out IMS service registration | |
| CN112491775B (en) | Monitoring method and device for cluster voice multicast group call | |
| CN110209474B (en) | Task processing method and device | |
| CN115349119A (en) | Method and apparatus for enhanced 5GC recovery when deploying a Network Function (NF) set in a network | |
| KR101646019B1 (en) | Apparatus, system and method for providing defect analysis service | |
| CN110121215B (en) | Data connection establishment method and device of 5G terminal and 5G terminal | |
| CN112469114B (en) | Session initial protocol registration method and device | |
| CN111866762A (en) | Special bearer establishing method and user equipment | |
| CN112114838A (en) | Software version upgrading method, terminal and base station | |
| CN111294949B (en) | Method and device for receiving and sending policy information, terminal and base station |
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 |