WO2008151538A1

WO2008151538A1 - Method, device and system for achieving barring service

Info

Publication number: WO2008151538A1
Application number: PCT/CN2008/071096
Authority: WO
Inventors: Youzhu Shi; Qing Zhou
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-06-08
Filing date: 2008-05-27
Publication date: 2008-12-18
Also published as: CN101321081A; CN101321081B

Abstract

A method, device and system for achieving a barring service are provided. The method includes: during a session, receiving the subsequent session message of a session original request message, and performing the process of the interdictory service according to a parameter related to an interdictory service in the subsequent session message.

Description

Method, device and system for realizing limited service

Technical field

The present invention relates to communication technologies, and more particularly to a method, apparatus and system for implementing restricted services.

Background technique

At present, with the continuous maturity of packet technology, traditional telecommunication networks based on circuit switching are developing toward packet telecommunication-based broadband telecommunication networks.

In the traditional telecommunication network, in addition to providing call services to users, the network also provides supplementary service services, such as: Call Forwarding (CF), and Outgoing Call Barring (OCB) services.

Correspondingly, packet telecommunication networks also need to provide users with services similar to supplementary services in traditional circuit networks, such as: CDIV (Communication Diversion), Outgoing Call Barring (OCB), and so on. In a packet telecommunication network, the user terminal may be a legacy terminal or a packet terminal. The packet terminal may be a SIP (Session Initiation Protocol) terminal or a packet non-SIP terminal, such as an H323 terminal. In the Next Generation Network (NGN), services with traditional service features provided to user terminals are collectively referred to as public switched telephone networks/integrated services digital network analog services.

( PSTN/ISDN simulation services ).

In the above-mentioned analog service, there is a type of restricted service that can restrict the incoming or outgoing calls of the user, such as Anonymous Communication Rejection (ACR), Incoming Communication Barring (ICB), and outgoing call restriction service. (OCB, Outgoing Call Barring), etc. After the user signs a certain restricted service, the corresponding restriction condition can be set, and a certain type of incoming or outgoing call is required to be restricted by activating the corresponding restriction condition.

In the existing packet telecommunication network technology, if the above-mentioned restricted service needs to be implemented, when the session request message is initiated, it is usually determined according to the session request message whether the restriction process needs to be performed. For example: Terminal A signs the incoming call restriction service and restricts the incoming call of terminal B. If terminal B initiates to terminal A For the call, the network may determine that the incoming call of the terminal is required to be restricted according to the parameter that the terminal has signed the restriction condition in the service, thereby denying the terminal to establish a session with the terminal. Here, the restriction condition may be to limit the incoming call of the terminal B, and the parameter may be the user identifier of the terminal B.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: In practical applications, the parameters in the above restrictions may change during the call, so that the session that should not be restricted before becomes a limit. Conversation. For example, terminal A subscribes to the outgoing call restriction service and restricts the call to terminal C; terminal B subscribes to the unconditional call forwarding service (CFU), and needs to forward the call to terminal C when there is an incoming call. At this time, if terminal A initiates a call to terminal B, terminal B forwards the call to terminal C, and the parameter in the terminal A restriction condition is changed from the user identifier of terminal B to the user identifier of terminal C.

For another example: Terminal A signs an incoming call to restrict the service and restricts the incoming call of terminal C. At this time, if terminal B calls terminal A, and in the process of establishing a session, terminal B activates the call forwarding service, and forwards the call to terminal C, and the parameter in the restriction condition of terminal A is changed by the user identifier of terminal B. User ID of terminal C.

For example: Terminal A signs the call restriction service, restricts the call to terminal C, and terminal B signs the same vibration service, and terminal C and terminal B belong to the same same vibration group. At this time, if terminal A calls terminal B, the network will simultaneously send the call to terminal B and terminal C. In the case where the terminal C responds first, the parameter in the terminal A restriction condition is changed from the terminal B to the terminal C.

In summary, regardless of the circumstances under which the parameters in the constraints change, the session that should not be previously restricted should become restricted, in which case the network should limit the session. However, in the prior art, the network does not process this after the session request, so that the user is not provided with a limited service.

Summary of the invention

The embodiments of the present invention provide a method, an apparatus, and a system for implementing a service restriction, which may continue to provide a restricted service for a subscription terminal after the session initial request message.

The technical solution proposed by the method embodiment of the present invention is: A method of implementing a restricted service, the method comprising the steps of:

During the session, the subsequent session message of the session initial request message is received, and the process of restricting the service is performed according to the parameter related to the restricted service in the subsequent session message.

The technical solution proposed by the device embodiment of the present invention is:

A device for implementing a restricted service, the device comprising:

a receiving unit, receiving a subsequent session message of the session initial request message;

The processing unit performs a process of restricting the service according to the parameter related to the restricted service in the subsequent session request.

The technical solution proposed by the system embodiment of the present invention is:

A system for implementing restricted services, the system comprising:

Restricting the service control module, receiving a subsequent session message of the session initial request message, and performing a process of restricting the service according to the parameter related to the restricted service in the subsequent session message;

The session control module provides a session routing function, and the forwarding terminal and the session message that restricts the interaction of the service control module.

In summary, the embodiment of the present invention provides a method, an apparatus, and a system for implementing a service restriction, which may receive a subsequent session message of a session initial request message, and perform a restriction according to a parameter related to the restricted service in the subsequent session message. The processing of the service, so as to continue to provide restricted services for the contracted terminal after the initial session request message.

DRAWINGS

1 is a flow chart of Embodiment 1 of the method of the present invention;

2 is a schematic diagram of a message flow according to Embodiment 2 of the method of the present invention;

3 is a schematic diagram of a message flow according to Embodiment 3 of the method of the present invention;

4 is a schematic view showing the basic structure of an embodiment of the apparatus of the present invention;

Figure 5 is a schematic diagram showing the basic structure of an embodiment of the system of the present invention.

detailed description

FIG. 1 is a flowchart of Embodiment 1 of implementing a method for restricting services. As shown in FIG. 1, this embodiment can To include the following steps:

Step 101: Receive a subsequent session message of the session initial request message during the session.

When a terminal initiates a session for another terminal, the entities on the session signaling path between the two terminals and the terminal will perform the session flow. The first session message of the session process is generally the session initial message of the session initiation, that is, the initial request message (SIP, Ses-Isation Protocol), such as: SIP INVITE message. , SIP SUBSCRIBE message, SIP message (SIP MESSAGE) message, etc. All session messages after the session initial message can be collectively referred to as subsequent session messages, such as: re-INVITE message, acknowledgment (ACK) message, notification (INFO) message, REFER message, response code message, and the like.

However, regardless of the specific session process, an entity on the session signaling path in the network needs to receive subsequent session messages of the session initial request message in order to implement the restricted service. In an actual application, an entity that implements a restricted service may be a server, such as an application server (AS). At this point, the AS is required to receive subsequent messages for the initial session request. Of course, the implementation of the restricted service can also be only one functional module in the AS, or other entities in the session path.

However, regardless of which entity or module receives the subsequent session message, the method for receiving the subsequent session message of the session initial request message may be:

When the session initial request message during the session is received, the own address is added to the session initiation request message to join the session signaling path, and the subsequent session message is received from the session signaling path.

That is to say, an entity that can implement restricted services, such as an AS, adds its own address to the message to join the session signaling path when receiving the initial session request message from the network. Thereafter, all subsequent session messages exchanged between the terminals performing the session will be transmitted according to the session signaling path and will also arrive at the AS.

Step 102: Perform processing of restricting services according to parameters related to the restricted service in the subsequent session message.

The processing of the restricted service described in this step may be: The related parameters are matched with the parameters in the existing restriction conditions. If the matching is successful, the session failure information is sent to the terminal.

In actual applications, when a terminal subscribes to a restricted service, the entity that implements the restricted service saves the restrictions and parameters of the session that the terminal wants to restrict. For example, if terminal A subscribes to the call restriction service and needs to restrict the call to terminal B, then the restriction condition may be "restrict call to terminal B" and the parameter is the user identifier of terminal B. In this way, if the parameters related to the restricted service in the subsequent session message are the same as the user identifier of the terminal B, it may be determined that the restriction condition of the terminal A subscription is met, and the session failure information should be sent to notify the terminal that the session is restricted.

The parameters related to the restricted service in the subsequent session message may be the user identifier, for example: the calling user identifier, the called user identifier, the original calling user identifier, the original called user identifier, the forwarding user identifier, the forwarded user identifier, Transfer the user ID or the user ID after the number change.

The user identifier associated with the restricted service in the subsequent session message is related to the specific session. For example, terminal A subscribes to the outgoing call restriction service and restricts the call to terminal C. Terminal B subscribes to the unconditional call forwarding service, and needs to forward the call to terminal C when there is an incoming call. At this time, if terminal A initiates a call to terminal B, and terminal B forwards the call to terminal C, and the subsequent session message received by the entity that implements the restricted service, the parameter related to the restricted service should be the user identifier of terminal C. , that is, the called user ID.

Here, if the parameters related to the restricted service and the parameters in the existing restriction conditions are successfully matched in the subsequent session message, the session needs to be restricted, that is, the session failure information is sent to the terminal. However, after the message that the session failed to be sent, the session can still exist. For example, terminal A subscribes to the outgoing call restriction service and restricts the call to terminal C. Terminal B subscribes to the unconditional call forwarding service, and needs to forward the call to terminal C when there is an incoming call. At this time, if the terminal A initiates a call to the terminal B, the terminal B forwards the call to the terminal C, and the parameter in the terminal A restriction condition is changed from the user identifier of the terminal B to the user identifier of the terminal C, and the subsequent session message and the restriction The service-related parameter is the user ID of terminal C. The entity that receives the subsequent session message and restricts the service may determine that the session should be restricted according to the parameter related to the restricted service, send the session failure information to the terminal B, and establish the network with the terminal B. Standing a conversation. In this case, the session initiated by the terminal A is only restricted from the session with the terminal C, but the session with the terminal B can still be maintained.

The entity that implements the restricted service can also further dismantle the session after sending the information of the session failure, and end the session. Thus, terminal A cannot talk to terminal C or to terminal B.

Of course, if the parameters related to the restricted service in the subsequent session message do not match the parameters in the existing restriction condition, the existing session flow can be continued. The existing session process belongs to the prior art and will not be described here.

In addition, in actual applications, the parameters related to the restricted service in the subsequent session message may be carried in a Reques tURI domain, an S IP header field, or a message body. The restricted service may include: an anonymous call restriction service, an incoming call restriction service, or an outgoing call restriction service.

In order to better illustrate the method for implementing the restricted service, the following describes the method embodiment 2 and the method embodiment 3.

In the second embodiment of the method, the terminal A503 subscribes to the outgoing call restriction service, and restricts the call to the terminal C. The terminal B subscribes to the unconditional call forwarding service, and needs to forward the call to the terminal C when there is an incoming call.

The system corresponding to this embodiment may include: a restricted service control module 501, a session control module 502, a terminal A503, a network 504 to which the terminal B belongs, and a terminal C505. The session control module 502 can provide a session routing function, and the forwarding terminal A 503 and the session information that restricts the service control module 501, such as a P-CSCF, an S-CSCF, an I-CSCF, etc.; The entity that implements the restricted service can be an AS server or the like. Of course, the network to which the terminal B belongs and the network to which the terminal C belongs may also include entities similar to the above, which are not listed here.

2 is a schematic diagram of a message flow of an embodiment of the method. As shown in FIG. 2, this embodiment may include the following steps:

Step 201: The terminal A503 sends a session initial request message to the session control module 502, where the parameter related to the restricted service carried by the session initial request message is the user identifier of the terminal B.

Step 202: The session control module 502 sends a session initial request message to the restricted service control mode. Block 501.

Here, the terminal A503 may carry the user identifier of the terminal B in the Reques tURI domain, the SIP header field, or the message body, and the SIP header field may be a P-As ser ted-Ident domain, a Refer-To domain, and a Referred - By field, From field, To field, P_Preferred - Ident i ty field, P_As soc ia ted - URI field, P-Ca l led-Par ty-ID field, Hi s tory-Info field, and so on.

Step 203: The restriction service control module 501 determines that the parameter related to the restricted service in the session initial request message does not match the parameter in the existing restriction condition, and adds the own address to the session initial request message.

Here, since the parameter related to the restricted service in the session initial request message is the user identifier of the terminal B, and the parameter in the existing restriction condition is the user identifier of the terminal C, the restriction service control module determines that the session should not be restricted. Continue with the subsequent session process.

However, unlike the prior art, the restricted service control module also needs to add its own address to the session initial request message and join the session signaling path to receive subsequent session messages. In the actual application, the restricted service control module can add its own address to a certain field of the message, such as: Record-Route header field.

Step 204: The restricted service control module 501 sends a session initial request message with its own address added to the session control module 502.

Step 205: The session control module 502 forwards the initial request message to the network to which the terminal B belongs.

504.

Step 206: The network 504 to which the terminal B belongs forwards the session initial request message to the terminal C505, and carries the user identifier of the terminal C505 as a parameter related to the restricted service in the session initial request message.

In this step, since the terminal B subscribes to the unconditional call forwarding service, the network 504 to which the terminal B belongs can directly forward the session initial request message sent to the terminal B to the terminal C505.

Similar to the step 201, the user identifier of the terminal C505 can also be carried in the Reques tURI domain and the like, and details are not described herein again. Step 207: The terminal C505 sends a session response 183 message to the network 504 to which the terminal B belongs. The session response 183 message carries the user identifier of the terminal C as a parameter related to the restricted service.

Step 208: The network 504 to which the terminal B belongs will respond to the message 183 message session control module 502. Step 209: The session control module 502 forwards the session response 183 message to the restricted service control module 501.

Step 210: The restriction service control module 501 determines that the parameter related to the restricted service carried in the session response 183 message matches the parameter in the existing restriction condition.

In this step, since the parameter related to the restricted service carried in the session response 183 message is the user identifier of the terminal C, and the parameter in the terminal A restriction condition is also the user identifier of the terminal C, it can be determined that the session is the terminal A. Limited.

Step 211: The restricted service control module 501 sends a message 603 indicating that the session failed to the session control module 502.

Step 212: The session control module 502 forwards to the terminal A 503 a message indicating that the session failed. In practical applications, sending a message indicating that the session has failed may also use no other messages, such as 480, 5 X X messages, etc., instead of 603 messages.

In addition, in this embodiment, the information indicating that the session fails is sent to the terminal by using the steps 211 and 212. However, in actual applications, the information indicating that the session fails may be sent to the terminal in the foregoing manner, and other methods are used. For example: Send the session failure information to both parties at the same time.

Step 213: The restricted service control module 501 sends a CANCEL message to the session control module 502 to tear down the session.

Step 214: The session control module 502 forwards the CANCEL message of the teardown session to the network 504 to which the terminal B belongs.

Step 215: The network 504 to which the terminal B belongs sends a CANCEL message for tearing down the session to the terminal C505. Step 216: The terminal C505 returns a 200 response message to the network 504 to which the terminal B belongs.

Step 217: The network 504 to which the terminal B belongs returns a 200 response message to the session control module 502. Step 218: The session control module 502 returns a 200 response message to the restricted service control module 501. In this embodiment, the teardown session is implemented by using steps 213 to 218. In a practical application, the specific manner of dismantling the session may also be determined by the user who applies the solution in this embodiment, and details are not described herein again.

In this embodiment, the address of the service control module 501 may be added to the Record-Route or Route header field of the message, and the user identifier of the terminal may be carried in the Reques tURI domain, the SIP header field, or the message body. It can be determined by the user who applies the solution of this embodiment, and details are not described herein again.

In the third embodiment of the method, the terminal A subscribes to the incoming call restriction service, and restricts the call from the terminal C; the terminal B calls the terminal A, and activates the call forwarding service that has been contracted after the session is established, and transfers the call to the terminal C. .

The system corresponding to the embodiment of the method may include: a restricted service control module 501, a session control module 502, a terminal A503, a network 504 to which the terminal B belongs, and a terminal B506. The session control module 502 can provide a session routing function, and the forwarding terminal and the session message that restricts the interaction of the service control module, such as a P-CSCF, an S-CSCF, an I-CSCF, etc.; Entity, can be an AS server, etc. The network to which Terminal B and Terminal C belong may also include entities similar to those described above, which are not listed here.

FIG. 3 is a schematic diagram of a message flow of an embodiment of the method. As shown in FIG. 3, this embodiment may include the following steps:

Step 301: The terminal B506 sends a session initial request message to the network 505 to which the terminal B belongs, and the parameter related to the restricted service carried in the session initial request message is the user identifier of the terminal B.

Similar to the method embodiment 2, the user identifier of the terminal B may also be carried in the Reques tURI domain, the SIP header field, or the message body. The SIP header field may be a PA ssert ed-1 den tity domain or a Re fe r-To domain. , Referred - By field, From field, To field, P-Pref erred-Ident ty field, P_As soc ia ted - URI field, P_Ca l led - Par ty - ID field, Hi s tory - Inf o field, etc.

Step 302: The network 504 to which the terminal B belongs forwards the session initial request message to the session control module.

502. Step 303: The session control module 502 forwards the session initial request message to the restricted service control module 501.

Step 304: The restriction service control module 501 determines that the parameter related to the restricted service in the session initial request message does not match the parameter in the existing restriction condition, and adds the own address to the session initial request message.

Step 305: The restricted service control module 501 sends a session initial request message with its own address to the session control module 502.

Step 306: The session control module 502 forwards the session initial request message to the terminal A503. Step 307: The terminal A503 and the terminal B506 establish a session.

Step 308: The terminal B506 activates the call forwarding service that has been contracted by itself.

In this embodiment, the terminal B 506 activates the call forwarding service after establishing a session with the terminal A 503. In actual applications, the terminal B 506 can activate the call forwarding service at any time.

Step 309: The terminal B506 sends a re-session request message to the network 504 to which the terminal B belongs, and the re-session request message carries the parameter related to the restricted service, that is, the user identifier of the terminal C.

Step 310: The network 504 to which the terminal B belongs forwards the re-session request message to the session control module.

502.

Step 311: The session control module 502 forwards the re-session request message to the restricted service control module 501.

Step 312: The restriction service control module 501 determines that the parameter related to the restricted service carried in the re-session request message is the same as the parameter in the existing restriction condition.

In this step, since the parameter related to the restricted service carried in the re-session request message is the user identifier of the terminal C, and the parameter in the terminal A restriction condition is also the user identifier of the terminal C, it can be determined that the session is the terminal A. limited. In actual applications, if the parameters are determined to be different in this step, the existing subsequent session process can be continued.

Step 31 3: The restricted service control module 501 sends a message 603 indicating that the session failed to the session control module 502.

Step 314: The session control module 502 forwards the 603 message indicating the session failure to the network 504 to which the terminal B belongs.

Step 315: The network 504 to which the terminal B belongs sends a message 603 indicating that the session has failed to the terminal B 506.

Similar to the method embodiment 2, in this embodiment, the address of the restricted service control module 501 may be added to the Re c 0 r d-Rou te or Rou te header field of the message, and the user identifier of the terminal may be carried in the Reques tURI. In the domain, the sip header field, or the message body, the specific situation may be determined by the user who applies the solution in this embodiment, and details are not described herein again.

It should be emphasized that the method embodiment 2 and the method embodiment 3 are only examples in a certain scenario. In the foregoing embodiment, the parameters related to the restricted service in the subsequent session message are changed, and are the same as the parameters in the existing restriction condition, so that the session should never be changed to be restricted, and the restriction is restricted by the service control module. Business process. In practical applications, it leads to changes in the parameters that limit the business-related parameters in the message [艮. For example, the terminal Α subscribes to the call restriction service, restricts the call to the terminal C, and the terminal B signs the same vibration service, and the terminal C and the terminal B belong to the same same vibration group. At this time, terminal A calls terminal B, and after the call arrives at the network to which terminal B belongs, terminal B and terminal C are simultaneously called. If terminal C answers first, terminal A and terminal C will perform the session flow. In this way, the parameter related to the restricted service in the subsequent session message will be the user identifier of the terminal C, which also triggers the restriction service control module to limit the session.

In summary, regardless of the situation of the session, as long as the service control module is restricted from receiving the subsequent session message, the process of restricting the service may be performed by using parameters related to the restricted service in the subsequent session message, thereby providing the terminal with the prior Contracted business restrictions.

In response to the above method, an apparatus and system for implementing restricted services are also presented below. FIG. 4 is a schematic structural diagram of Embodiment 1 of implementing a restricted service device. As shown in FIG. 4, this embodiment includes:

The receiving unit 401 is configured to receive a subsequent session message of the session initial request message.

The processing unit 402 is configured to perform a process of limiting the service according to the parameter related to the restricted service in the subsequent session request.

In an actual application, the processing unit 402 may include:

The matching unit 4021 is configured to match the parameter related to the restricted service in the subsequent session message with the parameter of the restriction condition in the storage unit 4022. If the matching is successful, the sending unit 403 sends the session failure information to the terminal.

The storage unit 4022 is configured to save a parameter of the restriction condition.

Correspondingly, the device further comprises:

The sending unit 403 is configured to send session failure information to the terminal.

In addition, in practical applications, regardless of which units are included in the processing unit 402, the apparatus may further include:

The address loading unit 404 is configured to add the device's own address to the received session initial request message, and send it through the sending unit 403.

When receiving the session initial situation message, the address loading unit 404 adds the device's own address to the received session initial request message, and transmits it through the sending unit 403; the receiving unit 401 receives the subsequent session of the session initial request message. When the message is received, the matching unit 4021 matches the parameter related to the restriction service and the parameter of the restriction condition in the storage unit 4022 in the subsequent session message. If the matching is successful, the sending unit 403 sends the session failure information to the terminal to limit the current time. Conversation.

In addition, in an actual application, the implementation limiting service device may be an application server (AS) or one of the functional modules, that is, the restricted service control module 501.

Figure 5 is a block diagram showing an embodiment of a restricted service system. As shown in FIG. 5, the system can include: The service control module 501 is configured to receive a subsequent session message of the session initial request message, and perform a process of limiting the service according to the parameter related to the restricted service in the subsequent session message.

The structure inside the restricted service control module 501 described herein is the same as that of FIG. 4 and will not be described here.

The session control module 502 is configured to provide a session routing function, and the forwarding terminal 503 and the session message restricting the interaction of the service control module 501.

Here the session control module 502 may be a Call Session Control Function entity (CSCF), comprising a P-CSCF, S-CSCF, I -CSCF 0

The terminal 503 initiates a session, and sends a subsequent session message of the session initial request message to the restricted service control unit 503 through the session control module 502.

The implementation of the restricted service system is actually a contracting restriction on the service terminal side. In actual applications, the system also needs to interact with the network or entity on the other terminal side of the session, and which entities are included on the other terminal side. It is related to the specific situation and belongs to the prior art part, and will not be described here.

In addition, in the embodiment of the system, the interface between the service control module 501 and the session control module 502 is E1, and may be exchanged according to the SIP protocol; the interface between the session control module 502 and the terminal 503 is E2, and may also be in accordance with S. The IP protocol interacts.

When the solution of the embodiment of the present invention is applied, the service control module may receive the subsequent session message, and perform the process of limiting the service according to the parameter related to the restricted service in the subsequent session message. If the parameter related to the restricted service in the subsequent session message matches the parameter in the existing restriction condition, the session failure information is sent to the terminal; otherwise, the existing session flow is continued. In this way, the restricted service control module not only implements the process of restricting the service when receiving the initial session request message, but also provides the restricted service service for the contracted terminal in the subsequent session, and ensures that the validity of the service service is restricted throughout the session process. Conducive to restrict the promotion of business.

All or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, when executed, The steps of the foregoing method embodiments are performed; and the foregoing storage medium includes: various media that can store program codes, such as ROM, RAM, disk or optical disk.

It will be understood by those of ordinary skill in the art that the drawings are only a schematic representation of a preferred embodiment, and that the modules or processes in the drawings are not necessarily required to practice the invention.

It will be understood by those skilled in the art that the modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the embodiment, or may be correspondingly changed in one or more apparatuses different from the embodiment. The modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

In conclusion, the above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Claim

A method for implementing a restricted service, the method comprising the steps of: receiving a subsequent session message of a session initial request message, and performing a restricted service according to a parameter related to the restricted service in the subsequent session message.

2. The method for implementing a restricted service according to claim 1, wherein the performing the restricted service according to the parameter related to the restricted service in the subsequent session message comprises:

The parameters related to the restricted service in the subsequent session message are matched with the parameters in the existing restriction condition. If the matching is successful, the session failure information is sent to the terminal.

The method for implementing a restricted service according to any one of the preceding claims, wherein the method for receiving a subsequent session message of a session initial request message is:

When receiving the session initial request message during the session, the entity receiving the session initial request message adds its own address to the session initial request message to join the session signaling path, and receives the subsequent from the session signaling path. Session message.

The method for implementing a restricted service according to any one of claims 1 to 3, wherein the session initial request message is: a session initial protocol initial request message.

The method for implementing a restricted service according to any one of claims 1 to 3, wherein the parameter related to the restricted service in the subsequent session message is a user identifier.

The method for limiting service according to claim 5, wherein the user identifier comprises: a calling user identifier, a called user identifier, an original calling user identifier, an original called user identifier, and a forwarding user. ID, forwarded user ID, transferred user ID, or user ID after number change.

The method for implementing a restricted service according to any one of claims 1 to 3, wherein the parameter related to the restricted service in the subsequent session message is carried in a Reques tURI domain, a session initial protocol header field, or a message body. in.

8. A device for implementing a restricted service, characterized in that the device comprises:

a receiving unit, configured to receive a subsequent session message of the session initial request message; And a processing unit, configured to perform a restricted service according to a parameter related to the restricted service in the subsequent session request.

9. The apparatus for implementing a service restriction according to claim 8, wherein the processing unit comprises: a matching unit, a storage unit, and a sending unit, where:

The matching unit is configured to match a parameter related to the restricted service in the subsequent session message with a parameter of the restriction condition stored in the storage unit, and if the matching is successful, notify the sending unit to send the information that the session is lost;

The storage unit is configured to save a parameter of the constraint condition;

The sending unit is configured to send session failure information to the terminal.

The device for implementing a service restriction according to claim 8 or 9, wherein the device further comprises:

An address loading unit is configured to add the device's own address to the received session initial request message and send it out through the sending unit.

11. A system for implementing restricted services, characterized in that the system comprises:

And a service control module, configured to receive a subsequent session message of the session initial request message, and perform a process of limiting the service according to the parameter related to the restricted service in the subsequent session message;

The session control module is configured to provide a session routing function, and forward the terminal and the session message that restricts the interaction of the service control module.

The system for implementing a restricted service according to claim 11, wherein the system further comprises:

The terminal is configured to initiate a session, and send a subsequent session message of the session initial request message to the restricted service control unit by using the session control module.

The system for implementing a restricted service according to claim 11, wherein the restricted service control module comprises:

a receiving unit, configured to receive a subsequent session message of the session initial request message;

And a processing unit, configured to perform a restricted service according to a parameter related to the restricted service in the subsequent session request.

14. A system for implementing restricted services according to claim 11 or claim 13, wherein said The processing unit includes: a matching unit, a storage unit, and a sending unit, where:

a matching unit, configured to match a parameter related to the restricted service and a parameter in the storage unit in the subsequent session message, and if the matching is successful, notify the sending unit to send the information that the session fails; the storage unit is configured to save the restriction condition Parameter

The sending unit sends a session failure message to the terminal.

The system for implementing a restricted service according to claim 13, wherein the restricted service control module further comprises: