CN101064644B - Method and system for sensing state of user to perform IMS service and give notice - Google Patents

Abstract

The invention discloses a sensing un-IMS operation state of user and informing method and system, said method includes following steps: a. know the inside story network entity detects the state of un-IP multimedia subsystem IMS grouping operation, and reports it to network region selecting entity NeDS. The invention overcomes defects of current technique, and makes network region selecting entityNeDS in double network operation scene can sense the un-IMS grouping operation state of user for subsequent route control.

Description

A method and system for perceiving and notifying the status of users performing non-IMS services

technical field

The present invention relates to the technical field of CDMA (Code Division Multiple Access), in particular, relates to the technology of sensing and notifying the user's service status in a CDMA network.

Background technique

CDMA technology is evolving from 2G network to 3G network. During this evolution process, the coexistence of 3G network and 2G network will last for a long time. This dual network coexistence situation is shown in Figure 1. The current CDMA2000 network architecture, where:

According to different access technologies, it can be divided into CDMA2000 1X network and CDMA2000 HRPD (High Rate Packet Data high-speed packet data service) network, and the 1X network is divided into CS (Circuit Switch circuit switching) domain and PS (Packet Switch packet switching) network ) domain, and the HRPD network is finally connected to the IMS (IP Multimedia Subsystem) domain.

Under the above architecture, users can perform services such as traditional voice calls and short messages through the CS domain of the 1X network, perform services such as web browsing through the PS domain of the 1X network, and access the IMS domain through the HRPD network for video calls, VoIP (Voice over IP IP-based voice service) and other services.

In the above network architecture, for a hybrid terminal that can access both 1X network and HRPD network, there needs to be a mechanism that allows the user to notify the user of the business that occurs on the HRPD network on the 1X network when performing services on the 1X network, and at the same time It should be able to notify the user of the business occurring on the 1X network when the user conducts business on the HRPD network.

In order to meet the above notification requirements, a "Subscribe" and "Notify" mechanism is defined in the SIP (Session Initiation Protocol) signaling, and a User Agent (UA) of the SIP signaling can give Another UA sends a Subscribe message to subscribe to the latter's various status events such as registration, de-registration, communication capabilities, etc., and the UA that accepts Subscribe can send a Notify message to the previous UA after the event required by the subscription occurs. .

In the IMS network, the SIP signaling is used as the session control signaling, so it also has the above-mentioned subscription notification service capability. On the basis of the above-mentioned subscription notification mechanism, the IMS network adds a unified management framework for subscription notifications, provides a new "Presence" service, and adds a Presence Server (Presence Server) entity in the IMS network. The entity is responsible for accepting subscription applications from various network entities to users, and subscribing to users on its behalf; it also collects various status information of users from terminals and network entities, and reports them to the subscribed network entities.

Specifically, some network elements in IMS and PLMN (Public Land Mobile Network) networks, such as HSS/HLR (Home Subscriber Server/Home Location Register), CSCF (Call Session Control Function Entity), MSC ( Mobile Switching Center), AAA (Authentication Authorization Accounting (Authorization Authorization Accounting (Center)), PS, etc., all have interfaces with the PresenceServer, and they interact through the Presence Network Agent (Presence Network Agent), so that the Presence Server can receive information from these networks. The user can obtain various status events of the user, and the user can also report the status to the Presence Server through the Presence User Agent.

In the prior art, there is another mechanism for anchoring control based on the IMS entity, which detects the registration and session status of the user in the two networks respectively, and performs routing control of the user according to the registration and session status of the user. Its architecture is shown in Figure 2 Show:

As can be seen from Figure 2, the architecture adds a network element named NeDS (Network Domain Selection network domain selection entity) between the IMS domain and the CS domain, and the specific description is as follows:

This entity is a standard ISC (IMS Service Control IMS Service Control) interface between the IMS domain and the I/S-CSCF (query/service-call session control function entity), and a standard Sh interface with the HSS, and its function is equivalent to An AS (Application Server);

There is a standard MAP (Mobile Application Part) interface between this entity and the CS domain entity HLR, and it is a GMSC (Gateway MSC gateway mobile switching center) for the HLR;

There may be an intelligent MAP signaling interface with the CS domain entity MSC, which is an SCP (Service Control Point) for the MSC.

This entity is mainly used to record the registration status of the user in the IMS domain and the call status of the user in the two networks, and make routing decisions according to the recorded registration status and call status of the user during the called process.

The above-mentioned technical solution partially solves the problem that the hybrid terminal knows the business that occurs in another network when the business occurs in one network. When the user performs IMS services such as VoIP and video telephony (VT) in the HRPD network, he can The NeDS entity is notified to the NeDS entity; when the user performs traditional services such as a voice call in the CS domain of the 1X network, it can be notified to the NeDS through the MAP signaling.

However, the above-mentioned architecture still has the following deficiencies:

Because the above architecture is based on SIP signaling, when a user performs non-IMS packet services (such as web page browsing service) in the PS domain of the 1X network, NeDS cannot know the user's service status. If there is a video call from the HRPD network that needs to be connected to the user at this time, NeDS will instruct to deliver the call from the HRPD network because it does not know that the user is doing business on the 1X network. As a result, the user cannot be paged.

Similarly, when a user performs web browsing and other non-SIP signaling-controlled services on the HRPD network, NeDS cannot know the user's service status. At this time, if a voice call needs to be connected to the user from the CS domain, NeDS It can only indicate that the call is delivered from the 1X network, but the user cannot be paged as a result.

Contents of the invention

The purpose of the present invention is to provide a method and system for perceiving the state of the non-IMS service performed by the user and notifying it, so as to solve the problem of perceiving the establishment and termination of the user's non-IMS packet service and notifying the NeDS of the event .

Another object of the present invention is to provide a NeDS to solve the problem of receiving the event of establishing and terminating a non-IMS packet service connection reported by an informed network entity or actively inquiring about the event of establishing and terminating a non-IMS packet service connection by a user.

In order to achieve the above object, the present invention provides the following technical solution: a method for perceiving and notifying the status of a user performing a non-IP multimedia subsystem IMS service, the method comprising the following steps:

The informed network entity detects the status of the user's non-IMS packet service and reports it to the network domain selection entity NeDS;

The informed network entity directly notifies the user terminal of the establishment/termination of the non-IMS packet service connection through the session initiation protocol SIP signaling or short message or notifies the NeDS user terminal through the presence server PresenceServer, or notifies the user terminal of the NeDS /The event of terminating the non-IMS packet service connection is notified by the Presence Server to the NeDS packet data service node PDSN or the authentication authorization charging center AAA, or directly notifies the user of the event of establishing/terminating the non-IMS packet service connection The PDSN or AAA of the NeDS, or notify the mobile switching center MSC of the NeDS of the event of establishing/terminating the non-IMS packet service connection through a short message or triggering an intelligent process through a smart trigger for user subscription;

in,

When the user establishes/terminates the non-IMS packet service, the user terminal sends a Notify message to the NeDS, and the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal sends a PUBLISH message to the NeDS to publish the status of the user's establishment/termination of the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal reports the information of the user establishing/terminating the non-IMS packet service connection to NeDS through a short message; or

When a user establishes/terminates a non-IMS packet service, the user terminal sends a Notify message to the Presence Server, and the message carries information about the user establishing/terminating a non-IMS packet service connection; the Presence Server sends the message to the Presence Server The NeDS sends a Notify message, and the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal sends a PUBLISH message to the Presence Server to publish the state of the user establishing/terminating the non-IMS packet service connection; the Presence Server sends a Notify message to the NeDS , the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the AAA or PDSN sends a message to the PresenceServer, and the message carries the information of the user establishing/terminating the non-IMS packet service connection; the Presence Server sends a Notify message to the NeDS , the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends a charging start/termination message to the AAA; the AAA reports the status information of the user establishment/termination of the non-IMS packet service connection to the NeDS; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends a charging start/termination message to the NeDS, and the message carries the information about the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates a non-IMS packet service, the MSC triggers an intelligent process through a user subscription smart trigger, and sends an origination request message/termination connection message to NeDS, and the message carries the user establishment/termination of a non-IMS packet Information about the business connection; or

When the user establishes/terminates the non-IMS packet service, the MSC sends a short message to the NeDS, and the short message carries the information of the user establishing/terminating the non-IMS packet service connection.

The present invention also provides a system for perceiving and notifying the user's state of non-IP multimedia subsystem IMS service, and the system includes:

The informed network entity is used to detect the status of the non-IMS packet service performed by the user and report it to the network domain selection entity NeDS;

NeDS is used to receive the status information of the non-IMS packet service performed by the user reported by the informed network entity or actively query the status of the non-IMS packet service performed by the user;

The informed network entity directly notifies the user terminal of the establishment/termination of the non-IMS packet service connection through the session initiation protocol SIP signaling or short message or notifies the NeDS user terminal through the presence server PresenceServer, or notifies the user terminal of the NeDS /The event of terminating the non-IMS packet service connection is notified by the Presence Server to the NeDS packet data service node PDSN or the authentication authorization charging center AAA, or directly notifies the user of the event of establishing/terminating the non-IMS packet service connection The PDSN or AAA of the NeDS, or notify the mobile switching center MSC of the NeDS of the event of establishing/terminating the non-IMS packet service connection through a short message or triggering an intelligent process through a smart trigger for user subscription;

When the user establishes/terminates the non-IMS packet service, the user terminal sends a Notify message to the NeDS, and the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal sends a PUBLISH message to the NeDS to publish the status of the user's establishment/termination of the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal reports the information of the user establishing/terminating the non-IMS packet service connection to NeDS through a short message; or

When a user establishes/terminates a non-IMS packet service, the user terminal sends a Notify message to the Presence Server, and the message carries information about the user establishing/terminating a non-IMS packet service connection; the Presence Server sends the message to the Presence Server The NeDS sends a Notify message, and the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the user terminal sends a PUBLISH message to the Presence Server to publish the state of the user establishing/terminating the non-IMS packet service connection; the Presence Server sends a Notify message to the NeDS , the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the AAA or PDSN sends a message to the PresenceServer, and the message carries the information of the user establishing/terminating the non-IMS packet service connection; the Presence Server sends a Notify message to the NeDS , the message carries information about the user establishing/terminating the non-IMS packet service connection; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends a charging start/termination message to the AAA; the AAA reports the status information of the user establishment/termination of the non-IMS packet service connection to the NeDS; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends a charging start/termination message to the NeDS, and the message carries the information about the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates a non-IMS packet service, the MSC triggers an intelligent process through a user subscription smart trigger, and sends an origination request message/termination connection message to NeDS, and the message carries the user establishment/termination of a non-IMS packet Information about the business connection; or

When the user establishes/terminates the non-IMS packet service, the MSC sends a short message to the NeDS, and the short message carries the information of the user establishing/terminating the non-IMS packet service connection.

The present invention also provides a network domain selection entity NeDS. There is an interface between the NeDS and the informed network entity, and the user establishment/termination of the non-IP multimedia subsystem reported by the informed network entity can be received through the interface. The event of IMS packet service connection or the event of actively querying the user to establish/terminate a non-IMS packet service connection;

The informed network entity directly notifies the NeDS user terminal of the event of the user establishing/terminating the non-IMS packet service connection through the session initiation protocol SIP signaling or a short message, or notifies the user of establishing/terminating the non-IMS packet service The connection event is directly notified to the NeDS packet data service node PDSN or the authentication and authorization charging center AAA, or the event of the user establishing/terminating the non-IMS packet service connection is notified by a short message or triggered by a smart trigger for user subscription The intelligent process notifies the NeDS mobile switching center MSC;

When the user establishes/terminates the non-IMS packet service, the NeDS receives the Notify message sent by the user terminal, and the message carries the information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the NeDS receives the PUBLISH message sent by the user terminal, and publishes the status of the user's establishment/termination of the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the NeDS receives the information of the user establishment/termination of the non-IMS packet service connection reported by the user terminal through a short message; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends a charging start/termination message to the AAA; the NeDS receives the status information of the user establishment/termination of the non-IMS packet service connection reported by the AAA; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the NeDS receives the charging start/termination message sent by the PDSN, and the message carries the information about the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the MSC triggers the intelligent process through the user subscription smart trigger, and NeDS receives the call origination request message/termination connection message sent by the MSC, and the message carries the user establishment/termination non-IMS Information on IMS packet service connections; or

When the user establishes/terminates the non-IMS packet service, the NeDS receives a short message sent by the MSC, and the short message carries the information of the user establishing/terminating the non-IMS packet service connection.

The present invention also provides another network domain selection entity NeDS, there is an interface between the NeDS and the presence server Presence Server, and the user establishment/termination of the non-IP multimedia subsystem can be received by the informed network entity through the presence server The event of IMS packet service connection or the event of actively querying the user to establish/terminate a non-IMS packet service connection;

The informed network entity is to notify the user terminal of NeDS through the Presence Server of the event that the user establishes/terminates the non-IMS packet service connection through the session initiation protocol SIP signaling or a short message, or to notify the user to establish/terminate the non-IMS packet service connection event. The packet service connection event is notified by the Presence Server to the NeDS packet data service node PDSN or the authentication authorization charging center AAA;

When the user establishes/terminates the non-IMS packet service, the Presence Server receives the Notify message sent by the user terminal, the message carries the information of the user establishing/terminating the non-IMS packet service connection, and the NeDS receives the The Notify message sent by the Presence Server, the message carries the information that the user establishes/terminates the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, the Presence Server receives the release PUBLISH message sent by the user terminal, publishes the status of the user's establishment/termination of the non-IMS packet service connection, and the NeDS receives the Notify message sent by the Presence Server, The message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When the user establishes/terminates the non-IMS packet service, AAA or PDSN sends a message to the PresenceServer, and the message carries the information of the user establishing/terminating the non-IMS packet service connection; NeDS receives the Notify sent by the Presence Server A message, the message carrying the information about the user establishing/terminating the non-IMS packet service connection.

The present invention overcomes the deficiencies of the prior art, and adopts a technical solution in which a corresponding interface is added between NeDS and an informed network entity, and NeDS obtains the establishment and removal events of the user's non-IMS packet service directly or through the Presence Server through the interface, The network domain selection entity NeDS in the dual-network interoperability scenario can perceive the non-IMS packet service status of the user in the packet domain. The present invention overcomes the shortcomings of the prior art and adopts the method of adding corresponding interface, NeDS obtains the user’s non-IMS packet service establishment and teardown event directly or through the Presence Server through the interface, so that the network domain selection entity NeDS in the dual-network interoperability scenario can perceive the user’s non-IMS packet service in the packet domain. IMS packet service status, so that when a user is performing non-IMS packet services such as surfing the Internet, if there is a circuit domain voice call or an IMS domain voice or video call that needs to be connected to the user, NeDS can select an appropriate network for connection according to the recorded user service status .

Description of drawings

Fig. 1 is the network architecture diagram of existing CDMA2000;

Fig. 2 is the architectural diagram of detecting the states of users in two networks in the prior art;

Fig. 3 is a flowchart of Embodiment 1 of the present invention;

FIG. 4 is a flow chart of Embodiment 2 of the present invention;

Fig. 5 is a flowchart of Embodiment 3 of the present invention;

FIG. 6 is a flow chart of Embodiment 4 of the present invention;

Fig. 7 is the flow chart that MSC according to the fifth embodiment of the present invention downloads the intelligent trigger from HLR when user registers;

FIG. 8 is a flow chart of the MSC notifying the NeDS user status through an intelligent trigger process according to Embodiment 5 of the present invention;

Fig. 9 is a flow chart of Embodiment 6 of the present invention.

Detailed ways

The basic principle of the present invention is that the informed network entity detects the establishment and termination of the user's non-IMS packet service and reports the event to NeDS through a certain mechanism, and NeDS performs subsequent processing after obtaining the user's packet service status.

The specific instructions are as follows:

To obtain the user's packet service status, NeDS first needs a network entity to perceive the establishment and termination of the user's non-IMS packet service, and then notify NeDS through a certain mechanism, so that NeDS can know the establishment and termination of the user's non-IMS packet service event.

In the existing technical solution, the user terminal, PDSN and AAA in the PS domain, and the MSC in the CS domain of the 1X network can all perceive the establishment and teardown events of the user's non-IMS packet service.

However, as mentioned above, in the existing technical solutions, there is no interface between the user terminal, PDSN (Packet DataServing Node), AAA, and NeDS, and although there is an intelligent network interface between the MSC and NeDS, there is no interface in the intelligent network. There is no corresponding trigger rule to trigger packet services.

Therefore, there needs to be an interface between the terminal and the NeDS to enable the terminal to report the establishment and termination events of its user's non-IMS packet service to the NeDS. Specifically, the following two methods can be adopted: one is that the terminal directly establishes contact with NeDS, and notifies NeDS through short messages in the circuit domain or other signaling; the other is using the existing presence mechanism, and NeDS subscribes to the terminal through the Presence Server Its non-IMS packet service establishment and termination events, so that when the terminal occurs non-IMS packet service establishment and termination events, it will notify the Presence Server, and NeDS can actively or passively obtain these events from the Presence Server.

Secondly, the packet domain entity PDSN or AAA also needs to report the establishment and termination of non-IMS packet services to NeDS. In the existing Presence technical solution, there is an interface between PDSN and AAA and the PresenceServer, so NeDS only needs to pass The Presence Server subscribes to these packet domain entities for the establishment and termination events of the user's non-IMS packet service, then when the user establishes and terminates the packet connection, the PDSN or AAA will notify the Presence Server, and NeDS can obtain these events through the Presence Server up. If the AAA supports the Diameter protocol or the NeDS supports the RADIUS protocol, the AAA can also directly notify the NeDS through the RADIUS or Diameter protocol.

In addition, in the existing technical solution, there already exists an intelligent network interface between MSC and NeDS, but it lacks the establishment and teardown event of non-IMS packet service to trigger the intelligent network mechanism, so the trigger rules for non-IMS packets can be added to the intelligent network The detection and triggering mechanism of service establishment and dismantling events, once the user establishes or terminates the packet connection, MSC triggers these rules and reports to NeDS. In addition, a new interface can be newly added between MSC and NeDS to transfer such events, and short messages and other signaling can be used for communication on the interface.

Further description will be made below in conjunction with the accompanying drawings and specific embodiments.

Embodiment 1: NeDS uses the subscription and notification mechanism to obtain the establishment and termination events of the user's non-IMS packet service

NeDS subscribes users to the establishment and termination events of non-IMS packet services. It can directly send a SUBSCRIBE message to the terminal to subscribe, or subscribe through the Presence Server. The process is shown in Figure 3:

1. NeDS sends a SIP SUBSCRIBER message to the terminal or to the terminal through the Presence Server, and the message body indicates the event that the subscriber needs to establish/terminate the non-IMS packet service connection;

2. The terminal returns a 202 Accepted message to NeDS through the Presence Server or directly, indicating acceptance of the subscription;

When a user establishes a packet service connection, then:

1. The terminal sends a SIP Notify message to NeDS through the Presence Server or directly, and the message body indicates that the user has started the packet service;

2. NeDS records the terminal status information and returns a 200OK message to the terminal through the Presence Server or directly to indicate receipt of the notification;

When the user terminates the packet service connection, then:

1. The terminal sends a SIP Notify message to NeDS through the Presence Server or directly, and the message body indicates that the user has terminated the packet service;

2. NeDS records the terminal status information and returns a 200OK message to the terminal through the Presence Server or directly to indicate receipt of the notification;

Other network entities, such as PDSN or AAA, that know the status of user packet services can also notify NeDS through the Presence mechanism. That is, these network entities report the user's packet service status change information through the interface with the Presence Server, and the Presence Server notifies NeDS.

Embodiment 2: The user terminal can also publish the user's non-IMS packet service status to the Presence Server through the PUBLISH (release) message, and then the Presence Server sends a Notify message to the NeDS to notify the NeDS user of the non-IMS packet service status. The specific process is as follows As shown in Figure 4:

First, the event of NeDS user establishing/terminating a non-IMS packet service connection:

1. The event that NeDS establishes/terminates a non-IMS packet service connection to the Presence Server subscriber;

2. Presence Server accepts subscription;

When the user starts group business:

1. The terminal publishes (PUBLISH message) a packet service establishment event to the Presence Server, and the address of the Presence Server is pre-configured in the terminal;

2. The Presence Server returns a release acceptance response to the terminal;

3. The Presence Server notifies the NeDS of the status event of the user establishing a packet service according to the NeDS subscription;

4. NeDS returns notification acceptance;

When the user ends the group service:

1. The terminal issues a packet service termination event to the Presence Server;

2. The Presence Server returns a release acceptance response to the terminal;

3. The Presence Server notifies the NeDS of the status event that the user terminates the packet service according to the NeDS subscription;

4. NeDS returns notification acceptance.

Embodiment 3: The terminal directly reports the user establishment/termination of the non-IMS packet service connection event to NeDS

When the terminal detects that the user starts and terminates the non-IMS packet service, it directly notifies NeDS through signaling such as short message. The specific process is shown in Figure 5:

When the user starts group business:

1. The terminal sends a short message request to the MSC based on the user's subscription attribute and service type judgment. The content of the short message is an event instructing the user to establish a packet service connection. The sending address of the short message is pre-configured in the terminal or SIM card (Subscriber Identify Module user identification card) or the network through the air interface;

2. After MSC receives the short message request, it regards NeDS as a short message center, and sends a MAP short message point-to-point request to NeDS, and the message body contains the above-mentioned information for the user to establish a packet service connection;

3. NeDS records the user status information after receiving the above short message, and returns a response message to MSC;

4. The MSC returns a response message to the terminal;

When the user terminates the packet service:

1. The terminal sends a short message request to the MSC, and the content of the short message is an event indicating that the user has terminated the packet service connection;

2. After receiving the short message request, the MSC regards NeDS as a short message center and sends a short message point-to-point request to NeDS. The message body contains the above-mentioned information that the user terminates the packet service connection;

3. NeDS records user status information after receiving the notification, and returns a response message to MSC;

4. The MSC returns a response message to the terminal.

Embodiment 4: AAA reports user establishment/termination of non-IMS packet service connection event to NeDS

The specific process is shown in Figure 6:

After the packet service connection between the PDSN and the terminal is established:

1. The PDSN sends an accounting start message to the AAA, which includes the user ID, service type and session start flag;

2. After AAA receives the accounting start message, it reports a status notification message to NeDS, which can use the RADIUS protocol or the Diameter protocol;

3. After NeDS receives the status notification message, it records the user status information, and then returns a notification response message to AAA;

4. The AAA returns an Accounting Start Response message to the PDSN.

When the packet service connection between the PDSN and the terminal is terminated:

1. The PDSN sends a charging termination message to the AAA;

2. After receiving the accounting termination message, AAA reports a status notification message to NeDS, and the protocol adopted is consistent with the notification message when the packet service is established;

3. After NeDS receives the status notification message, it records the user status information, and then returns a notification response message to AAA;

4. The AAA returns an Accounting Termination Response message to the PDSN.

In addition, in addition to sending an accounting start/termination message to NeDS through AAA to notify NeDS users of the event of establishing/terminating a sub-IMS packet service connection, the PDSN can also directly send an accounting start/termination message to NeDS.

Embodiment 5: MSC notifies NeDS through an intelligent trigger process when it senses that the state of the user group service has changed

MSC first needs to download the user's smart contract trigger from the HLR when the user registers. The specific process is shown in Figure 7:

1. When the terminal accesses the network, the base station system BS sends a location update request message to the MSC/VLR;

2. MSC/VLR initiates a registration request to HLR, and the request message contains the intelligent processing capability indication parameter of MSC/VLR;

3. The HLR returns the user's subscription data to the MSC/VLR according to the user's subscription attributes and the capabilities of the MSC/VLR, including the user's smart trigger, which includes the trigger rule for the establishment/termination of the packet service;

4. The MSC/VLR saves the user's smart trigger and other subscription data in the VLR, and then returns a location update acceptance message to the base station system.

When the MSC perceives that the user packet service status has changed, it notifies NeDS through an intelligent trigger process. The specific process is shown in Figure 8:

1. The terminal initiates the packet service establishment process, and the BS sends a service establishment request to the MSC, indicating that the service type is packet service;

2. The MSC instructs the BS to establish air interface channel resources;

3. After the BS establishes a packet service connection with the user, it notifies the MSC;

4. The MSC triggers the intelligent process through the user's smart trigger, and regards NeDS as an SCP to send an origination request message to it. The message includes user identification and service type, and notifies the NeDS user to establish a packet service connection;

5. NeDS records user status information and returns a response to MSC;

6. Users perform group business;

7. The user terminates the packet service, and the BS sends a clear connection request to the MSC;

8. The MSC sends a clear connection instruction to the BS;

9. After the packet connection between the BS and the terminal is terminated, send a clear completion notification to the MSC;

10. The MSC triggers an intelligent trigger and sends a service termination ODISCONNECT message to NeDS;

11. NeDS records user status information and returns a response to MSC.

Embodiment 6: MSC notifies NeDS by SMS

MSC notifies NeDS by short message when it senses that the user’s packet service status has changed. The address of NeDS can be pre-configured in the terminal or SIM card, and the terminal will bring it to MSC when it initiates a packet service request; or put the NeDS address in the user Among the subscription data, MSC/VLR downloads from HLR when user registers. The specific process is shown in Figure 9:

Compared with the process shown in Figure 8 above, the difference lies in step 4, step 5, step 10 and step 11, and other steps are the same, and the different steps are explained below:

4. MSC constructs a short message and reports the user's service status to NeDS. The content of the short message is to instruct the user to establish a packet service;

5. NeDS returns a response message to MSC after recording user status information;

10. The MSC constructs a short message and reports the user's service status to NeDS. The content of the short message is to instruct the user to terminate the packet service;

11. The NeDS returns a response message to the MSC after recording the user status information.

Claims (11)

1. A method for sensing and notifying the state of a user performing a non-IP Multimedia Subsystem (IMS) service is characterized by comprising the following steps:

the informed network entity detects the state of the non-IMS grouping service of the user and reports the state to a network domain selection entity NeDS;

the informed network entity directly informs the event of establishing/terminating the non-IMS packet service connection of the user through a Session Initiation Protocol (SIP) signaling or a short message or informs the user terminal of the NeDS through a Presence Server, or informs the event of establishing/terminating the non-IMS packet service connection of the user through the Presence Server to a Packet Data Service Node (PDSN) or an authentication authorization accounting center (AAA) of the NeDS, or directly informs the event of establishing/terminating the non-IMS packet service connection of the user to the PDSN or the AAA of the NeDS, or informs the event of establishing/terminating the non-IMS packet service connection of the user to a Mobile Switching Center (MSC) of the NeDS through a short message notification or triggering an intelligent flow through a user signed intelligent trigger;

wherein,

when a user establishes/terminates a non-IMS packet service, a user terminal sends a Notify message to NeDS, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the user terminal sends a PUB LISH release message to NeDS, and releases the state that the user establishes/terminates the non-IMS packet service connection; or

When a user establishes/terminates the non-IMS packet service, the user terminal reports the information of establishing/terminating the non-IMS packet service connection of the user to NeDS through a short message; or

When a user establishes/terminates a non-IMS packet service, a user terminal sends a Notify message to a Presence Server, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; the Presence Server sends Notify message to the NeDS, the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates a non-IMS packet service, a user terminal sends a PUBLISH PUBLISH message to a Presence Server, and publishes the state of establishing/terminating a non-IMS packet service connection by the user; the Presence Server sends Notify message to the NeDS, the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates the non-IMS packet service, AAA or PDSN sends a message to a PreseneServer, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; the Presence Server sends Notify message to NeDS, the message carries the information of user establishing/terminating non-IMS grouping service connection; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends an accounting start/termination message to the AAA; AAA reports the state information of user establishing/terminating non-IMS grouping service connection to NeDS; or

When a user terminal establishes/terminates the non-IMS packet service connection with a PDSN, the PDSN sends a charging start/termination message to NeDS, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates a non-IMS packet service, an MSC triggers an intelligent process through a user signed intelligent trigger, and sends an initial call request message/a termination connection message to NeDS, wherein the message carries information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the MSC sends a short message to the NeDS, and the short message carries the information of establishing/terminating the non-IMS packet service connection by the user.

2. The method of claim 1, wherein the step of the user terminal sending a Notify message to NeDS when the user establishes/terminates the non-IMS packet service is preceded by:

and the NeDS subscribes the non-IMS grouping service connection event established/terminated by the user to the user terminal.

3. The method of claim 1, wherein the step of the user terminal sending the PUBLISH message to NeDS when the user establishes/terminates the non-IMS packet service further comprises: and configuring the NeDS address in the user terminal.

4. The method according to claim 1, wherein said step of reporting, by the ue, the information that the user establishes/terminates the non-IMS packet service connection to the NeDS through a short message when the user establishes/terminates the non-IMS packet service specifically comprises:

when a user establishes/terminates a non-IMS packet service, the user terminal sends a short message to an MSC, wherein the short message carries information for establishing/terminating the non-IMS packet service connection by the user;

and after receiving the short message, the MSC forwards the short message to the NeDS.

5. The method according to claim 1 or 4, wherein the destination address of the short message is pre-configured in the subscriber terminal or in a subscriber identity module SIM.

6. The method according to claim 1, wherein said step of sending notification message from user terminal to Presence Server when user establishes/terminates non-IMS packet service, or said step of sending PUBLISH message from user terminal to Presence Server when user establishes/terminates non-IMS packet service, further comprises:

and configuring the address of the Presence Server in the user terminal or the SIM.

7. The method of claim 1, wherein the step of the MSC triggering the intelligent flow by the user subscription intelligent trigger when the user establishes/terminates the non-IMS packet service further comprises:

the MSC sends a registration request to a Home Location Register (HLR), and the HLR returns subscription data of a user to the MSC, wherein the subscription data comprises the intelligent trigger of the user and the NeDS address.

8. The method of claim 1, wherein the step of the MSC sending the short message to the NeDS when the subscriber establishes/terminates the non-IMS packet service further comprises:

and configuring the NeDS address in the user terminal or the SIM.

9. A system for sensing and notifying a status of a non-IP multimedia subsystem IMS service performed by a user, the system comprising:

the informed network entity is used for detecting the state of the non-IMS grouping service performed by the user and reporting the state to the network domain selection entity NeDS;

NeDS for receiving the status information of the non-IMS packet service performed by the user reported by the informed network entity or actively querying the status of the non-IMS packet service performed by the user;

the informed network entity directly informs the event of establishing/terminating the non-IMS packet service connection of the user through a Session Initiation Protocol (SIP) signaling or a short message or informs the user terminal of the NeDS through a Presence Server, or informs the event of establishing/terminating the non-IMS packet service connection of the user through the Presence Server to a Packet Data Service Node (PDSN) or an authentication authorization accounting center (AAA) of the NeDS, or directly informs the event of establishing/terminating the non-IMS packet service connection of the user to the PDSN or the AAA of the NeDS, or informs the event of establishing/terminating the non-IMS packet service connection of the user to a Mobile Switching Center (MSC) of the NeDS through a short message notification or triggering an intelligent flow through a user signed intelligent trigger;

when a user establishes/terminates a non-IMS packet service, a user terminal sends a Notify message to NeDS, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the user terminal sends a PUBLISH PUBLISH message to NeDS, and publishes the state of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates the non-IMS packet service, the user terminal reports the information of establishing/terminating the non-IMS packet service connection of the user to NeDS through a short message; or

When a user establishes/terminates a non-IMS packet service, a user terminal sends a Notify message to a Presence Server, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; the Presence Server sends Notify message to the NeDS, the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates a non-IMS packet service, a user terminal sends a PUBLISH PUBLISH message to a Presence Server, and publishes the state of establishing/terminating a non-IMS packet service connection by the user; the Presence Server sends Notify message to the NeDS, the message carries the information of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates the non-IMS packet service, AAA or PDSN sends a message to a Presence Server, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; the Presence Server sends Notify message to NeDS, the message carries the information of user establishing/terminating non-IMS grouping service connection; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends an accounting start/termination message to the AAA; AAA reports the state information of user establishing/terminating non-IMS grouping service connection to NeDS; or

When a user terminal establishes/terminates the non-IMS packet service connection with a PDSN, the PDSN sends a charging start/termination message to NeDS, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates a non-IMS packet service, an MSC triggers an intelligent process through a user signed intelligent trigger, and sends an initial call request message/a termination connection message to NeDS, wherein the message carries information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the MSC sends a short message to the NeDS, and the short message carries the information of establishing/terminating the non-IMS packet service connection by the user.

10. A network domain selection entity NeDS is characterized in that an interface exists between the NeDS and an informed network entity, and an event reported by the informed network entity and used for establishing/terminating a non-IP multimedia subsystem IMS packet service connection by a user or an event used for actively inquiring the establishment/termination of the non-IMS packet service connection by the user can be received through the interface;

the informed network entity directly informs the NeDS user terminal of the event of establishing/terminating the non-IMS grouped service connection of the user through a Session Initiation Protocol (SIP) signaling or a short message, or directly informs the NeDS Packet Data Service Node (PDSN) or an authentication authorization accounting center (AAA) of the event of establishing/terminating the non-IMS grouped service connection of the user, or informs the NeDS Mobile Switching Center (MSC) of the event of establishing/terminating the non-IMS grouped service connection of the user through a short message notification or an intelligent flow triggered by a user signed intelligent trigger;

when a user establishes/terminates a non-IMS packet service, the NeDS receives a Notify message sent by a user terminal, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the NeDS receives a publish PUB LISH message sent by a user terminal, and publishes the state of the user establishing/terminating the non-IMS packet service connection; or

When a user establishes/terminates a non-IMS packet service, the NeDS receives the information of the user establishing/terminating the non-IMS packet service connection reported by a user terminal through a short message; or

When the user terminal establishes/terminates the non-IMS packet service connection with the PDSN, the PDSN sends an accounting start/termination message to the AAA; the NeDS receives the state information of the user establishing/terminating the non-IMS packet service connection reported by AAA; or

When a user terminal establishes/terminates the non-IMS packet service connection with a PDSN, the NeDS receives a charging start/termination message sent by the PDSN, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates a non-IMS packet service, an MSC triggers an intelligent process through a user signed intelligent trigger, a NeDS receives an initial call request message/a termination connection message sent by the MSC, and the message carries information of establishing/terminating the non-IMS packet service connection by the user; or

When a user establishes/terminates the non-IMS packet service, the NeDS receives a short message sent by the MSC, and the short message carries the information of establishing/terminating the non-IMS packet service connection by the user.

11. A network domain selection entity NeDS is characterized in that an interface exists between the NeDS and a Presence Server, and an event that a user establishes/terminates a non-IP multimedia subsystem IMS packet service connection reported by an informed network entity can be received through the Presence Server or the event that the user establishes/terminates the non-IMS packet service connection can be actively inquired;

the informed network entity informs the NeDS user terminal of the event of establishing/terminating non-IMS grouped service connection of the user through a Presence Server through a session initiation protocol SIP signaling or a short message, or informs the NeDS packet data service node PDSN or an authentication authorization accounting center AAA of the event of establishing/terminating non-IMS grouped service connection of the user through the Presence Server;

when a user establishes/terminates a non-IMS packet service, a Presence Server receives a Notify message sent by a user terminal, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user, and a NeDS receives the Notify message sent by the Presence Server, wherein the message carries information for establishing/terminating a non-IMS packet service connection by the user; or

When a user establishes/terminates a non-IMS packet service, a Presence Server receives a PUBLISH PUBLISH message sent by a user terminal, and publishes the state of the connection of the non-IMS packet service established/terminated by the user, and the NeDS receives a Notify message sent by the Presence Server, wherein the message carries the information of the connection of the non-IMS packet service established/terminated by the user; or

When a user establishes/terminates the non-IMS packet service, AAA or PDSN sends a message to a PreseneServer, wherein the message carries the information of establishing/terminating the non-IMS packet service connection by the user; the NeDS receives the Notify message sent by the Presence Server, where the message carries the information for the user to establish/terminate the non-IMS packet service connection.

Images