WO2006116941A1

WO2006116941A1 - Realizing method and system for ip-based network area message service

Info

Publication number: WO2006116941A1
Application number: PCT/CN2006/000872
Authority: WO
Inventors: Xiaoqin Duan
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-04-30
Filing date: 2006-04-29
Publication date: 2006-11-09
Also published as: CN1859607A; CN100466760C

Abstract

A realizing method for IP-based network area message service, the core is: setting address information of message service receiving side of presetting calling/called network area in IP-based network area. IP-Message-GW of IP-based network area acquires the address information of the message service receiving side, the IP-Message-GW transmits the received message to the message service receiving side based on the acquired address information. Also, two realizing systems for IP-based network area message service. The IP-Message-GW of the present invention doesn’t need to analyze short message service center address information of IP-based network area, such as IMS network, from message entity of message. The present invention enable the message to satisfy message format of SIP signaling, according with using habit of IMS network area user, reducing occupying length of message entity. Accordingly, improving message service realizing activity, advancing development of message service interwork.

Description

TECHNICAL FIELD The present invention relates to the field of network communication technologies, and particularly to an implementation method based on an IP network domain message service and two implementation systems based on an IP network domain message service. BACKGROUND OF THE INVENTION With the development of broadband networks, mobile communications will not be limited to traditional voice communications, and multimedia services combining multiple media types such as audio, video, pictures and text will gradually be developed, through with presence (presentation services), The combination of short message, WEB (web) browsing, location information, PUSH (push service), file sharing and other data services can meet the diverse needs of mobile users.

Driven by a variety of applications, standards organizations such as 3GPP and 3GPP2 have introduced an architecture based on IMS (IP-based Multimedia Subsystem), which aims to: Implement a variety of standardized open structures in mobile networks. The multimedia application provides mobile users with more choices and richer experiences.

In the 3GPP Release 5 (R5) phase, an IP Multimedia Subsystem domain, referred to as IMS, is superimposed on the packet domain network, and is CSCF (Call State Control Function), MGCF (Media Gateway Control Function), MRF (Media Resource Function). ) and HSS (Home Subscriber Server) and other functional entities, where CSCF can be divided into three logical entities: S-CSCF (Serving CSCF), P-CSCF (Proxy CSCF) and I-CSCF (Query CSCF), S-CSCF It is the service switching center of IMS, which performs session control, maintains session state, manages user information, and generates billing information. The P-CSCF is the access point for the terminal user to access the IMS, completes the user registration, and is responsible for QoS control and security management. The I-CSCF is responsible for interworking between the IMS domains, managing the allocation of the S-CSCF, and hiding the network topology and the external network. Configuration, generating billing data, etc. MGCF The control gateway implements interworking between the IMS network and other networks. The MRF provides media resources such as audio and video, codec and multimedia conference bridge. The HSS is a user database that stores subscription data and configuration information of the IMS user.

Since the structure of the IMS network is independent of the underlying bearer network, the 3GPP definition, such as the packet network defined in 3GPP2, the WLAN network, and the NGN, the network, etc., achieve independence from the terminal type and is independent of the access network type. Sex. Therefore, the IMS can be applied only to 3GPP related networks and applications, and other types of access networks and bearer network services and applications can also be implemented by using the IMS architecture, so that IMS provides a universal for future multimedia applications. The service enablement platform is an important step in the evolution of the All IP Network service provider system.

At present, the 3GPP proposes an IMS network architecture in which an IMS-based message service communicates with a conventional short message service, as shown in FIG.

In Figure 1, SME (Short Message Entity), SM-SC (Short Message Service Center), GMSC/SMS-IWMSC (Gateway Mobile Switching Center/Short Message Gateway), HSS HLR (Home Subscriber Server/Home Location Register), CGF/CDF (Billing Gateway Function/Charging Data Function) and OCS (Online Billing System) are functional entities for implementing Short Message Service (SMS) in existing Circuit Switched/Packet Switched (CS/PS) network domains.

The SM-SC is used to store and forward short messages; the GMSC is used to query the HSS/HLR for routing information when the mobile user receives the short message; the SMS-IWMSC is used to check whether the mobile user is allowed to belong to the SM-SC in the case of roaming. Send a short message. Usually, the three logical entities of SM-SC, GMSC and SMS-IWMSC are physically implemented by an integrated physical device.

The HSS/HLR is used to store data information of mobile users, including routing information, and CGF/CDF is used to collect and process billing information of the user's offline billing, and then transmit it to the billing center, OCS. The bill information used to collect and process the mobile subscriber's online billing is then passed to the billing center. The IP-Message-GW in Figure 1 is a new network entity that implements IP user equipment and GMSC/SMS by interworking the IP network message protocol with the existing WCDMA/GSM network short message protocol. Communication between IWMSCs.

When the user equipment UE based on the Session Initiation Protocol (SIP) uses the message service, it must first register with the IP-Message-GW, and the IP-Message-GW notifies the HSS that the UE is registered and the IP-Message-GW address. The HSS saves the above. The status of the registered UE is IP Connected, and stores the address of the UE and the address of its registered IP-Message-GW.

The current specification proposes a method for establishing a secure connection between multiple UEs and IP-Message-GW, including: a security architecture based on GAA (Common Authentication Architecture), a network architecture based on IMS (IP Multimedia Subsystem), and based on The tunnel mode is used to establish a secure connection between the UE and the IP-Message-GW.

For the IMS-based network architecture to establish a secure connection between the UE and the IP-Message-GW, the processing flow of the calling user UE to register with the IP-Message-GW is as shown in FIG. 2.

In Figure 2, in step 1, the calling user UE establishes an IP connection.

Go to step 2. After the UE successfully establishes an IP connection, it registers with the S-CSCF according to the IMS registration process. In the IMS registration process, the functional entities such as I-CSCF and P-CSCF and the messages transmitted between many S-CSCFs and HSSs are involved. For the sake of brevity, they are not listed.

Go to step 3. The S-CSCF checks the filter (filter) information from the HLR/HSS in the IMS registration process.

Go to step 4. After the IMS registration is successful, the S-CSCF notifies the IP-Message-GW UE that the UE has registered to the IMS domain according to the filter information.

Go to step 5. The IP-Message-GW sends a message registration request (IP-IWF-Register Req) message to the HLR/HSS, and registers the UE identity and its own address information in the HLR/HSS. To step 6, the HLR/HSS stores the IP-Message-GW and the address information of the UE, and then returns an Information Registration Response (IP-IWF-Register Res) message to the IP-Message-GW.

Go to step 7. The IP-Message-GW returns a registration success (SIP 200 OK) message to the S-CSCF.

After registering the UE in the IP-Message-GW using the registration procedure in FIG. 2, the SMS-MO (Short Message Move Origination) procedure of the UE of the IMS network domain is as shown in FIG. 3.

In Figure 3, in step 1, the UE registers with the S-CSCF according to the IMS registration procedure.

Go to step 2. The UE sends a message to the S-CSCF based on the SIP (Start Session Protocol) MESSAGE (message) mode.

Go to step 3. The S-CSCF forwards the message to the IP-Message-GW according to the filter information. Go to step 4. The IP-Message-GW returns a SIP 202 Accepted message to the S-CSCF indicating that the message has been received.

Go to step 5. The S-CSCF forwards the SIP 202 to the UE to receive the message.

Go to step 6. The IP-Message-GW parses the message content from the received message, and assembles the parsed message content into standard MAP signaling as a short message to the SMS-IWMSC. The address information of the SMS-IWMSC is the same as the address information of the SM-SC, and the address information of the SM-SC can be parsed from the R-U I (Requested - Resource Identification) part of the MESSAGE or the message body part of the message.

Go to step 7. The SMS-IWMSC forwards the message transfer to the SM-SC. Go to step 8. The SM-SC sends a short message submission report to the SMS-IWMSC.

Go to step 9. The SMS-IWMSC sends a short message submission report to the IP-Message-GW. Go to step 10. The IP-Message-GW uses SIP MESSAGE to send a message submission report to the S-CSCF.

To step 11, the S-CSCF sends a message submission report to the UE using the SIP MESSAGE. Go to step 12, the UE submits a report in response to the received message using the 200 ok message.

To step 13, the 200 ok response message is forwarded to the IP-Message-GW via the S-CSCF. After the SM-SC receives the short message from the SMS-IWMSC, the called identity in the short message sends the short message to the called terminal.

It can be seen from the above description that, for the calling user based on the IMS network domain, the message body of the initial call message needs to carry the address information of the short message service center on the calling network side, does not conform to the message format of the SIP signaling, and needs The user sets the address information of the SM-SC, and does not conform to the usage habits of the IMS network domain users, and occupies a limited length of the message body, which reduces the flexibility of the message service implementation.

In addition, for the message originated in the IMS domain, first, the IP-Message-GW needs to convert the message into standard MAP signaling, and then sends the MAP signaling to the SMS-IWMSC/SM-SC in the IMS network. The MAP signaling is transmitted by the SM-SC to a legacy network, such as a CS/PS network domain, to implement message interworking between the IMS and the legacy network. In this way, in order to be able to communicate with the traditional network, the IMS network needs to add network elements of the traditional network such as SMS-IWMSC/SM-SC/GMSC, especially for the network operator. In the case of a new network operator based on the IMS network, the network construction cost and the maintenance cost for the interworking of the message service are increased, which is not conducive to the development of the message service interworking. SUMMARY OF THE INVENTION A first main object of the present invention is to provide an implementation method based on an IP network domain message service, which can improve the implementation flexibility of a message service based on an IP network domain.

To achieve the above objective, the present invention provides an implementation method based on an IP network domain message service, including:

a. setting a message service receiving end of the predetermined primary/called network domain in the IP network domain Address information;

b. The IP-Message-GW based on the IP network domain obtains the address information of the receiving end of the message service;

c. The IP-Message-GW sends the message it receives to the receiving end of the message service according to the obtained address information.

The predetermined called network domain includes: a circuit domain based on circuit switching/packet switching.

The IP network domain includes: a network domain based on an IP multimedia subsystem.

Preferably, the step b specifically includes:

Bl l, the IP-Message-GW determines, according to the predetermined information carried in the message received by the IP-Message-GW, a message that needs to be sent to the predetermined called network domain;

The IP-Message-GW acquires the address information of the message service receiving end corresponding to the message that needs to be sent to the predetermined called network domain;

Or the step b includes:

B21. The S-CSCF determines, according to the predetermined information carried in the message received by the S-CSCF, a message that needs to be sent to the predetermined called network domain, and sends the determined message to the IP-Message-GW; b22, the IP-Message The GW acquires the address information of the message service receiving end corresponding to the message that needs to be sent to the predetermined called network domain.

The predetermined information may include: a called identifier;

And the step bl specifically includes:

The IP-Message-GW determines a message to be transmitted to the predetermined called network domain according to the format of the called identifier in the received message service.

The step b2 may specifically include:

The IP-Message-GW acquires the address information according to the address information of the message service receiving end of the pre-set host/called network domain stored therein; or

IP-Message-GW eliminates the need to pre-set the primary/called network domain with other storage The message interaction of the network entity of the address information of the receiving end of the information service acquires the address information of the receiving end of the message service of the primary/called network domain.

The message service receiving end may include: a message interworking gateway that is scheduled to be called the network domain; and the step C specifically includes:

The IP-Message-GW assembles the message according to its interface protocol with the message interworking gateway, and sends the assembled message according to the address information of the set message interworking gateway.

The address information of the set message interworking gateway includes: an address of a uniquely set message interworking gateway;

Or include: Correspondence between the called identity and the message interworking gateway address.

Preferably, the interface protocol is: SMPP protocol or CMPP protocol.

The method may further include:

The message interworking gateway determines a short message service center of the called network domain corresponding to the called identifier in the received message, and transmits the received message to the short message service center, where the short message service center receives The message is stored and forwarded.

The receiving end of the message service includes: a short message service center of the calling network domain; the step a specifically includes:

A short message service center in the calling network domain is built in the IP-Message-GW. The step c may specifically include:

The IP-Message-GW, which has a short message service center built in the calling network domain, parses, stores, and forwards the messages it receives.

The receiving end of the message service may include: a short message service center of the calling network domain; and the address information of the receiving end of the message service of the predetermined predetermined calling domain domain includes:

Correspondence between the calling subscriber identity and the short message service center address information of the calling network domain Department.

The step C may specifically include:

The IP-Message-GW assembles the message into MAP signaling, and determines address information of the short message service center of the calling network domain according to the calling subscriber identity and the correspondence, and passes the MAP signaling through SMS. - The IWMSC is sent to the calling network domain short message service center.

The message service receiving end may include: a short message service center of the called network domain; and the address information of the pre-set predetermined message network receiving end of the called network domain includes:

Correspondence between the called subscriber identity and the short message service center address information of the called network domain.

A second main objective of the present invention is to provide an implementation system based on an IP network domain message service, which can avoid the construction of a traditional network element device entity in an IP-based network and reduce the maintenance of the network device.

To achieve the above objective, a system for implementing an IP network domain service includes: an IP network domain and a called network domain; the IP network domain includes an IP-Message-GW, and the called network domain The short message service center is included in the system, wherein the IP-Message-GW is connected to the short message service center;

The IP-Message-GW obtains the called network according to the corresponding relationship between the called user identifier in the received message and the called user identifier set by the user and the short message service center address in the called network domain, or querying other network entities. The short message service center address in the domain sends the received message to the corresponding short message service center in the called network domain.

A short message service center can be integrated in the IP-Message-GW.

A third main objective of the present invention is to provide another implementation system based on IP network domain message service, which can facilitate message routing in the calling network domain and improve the called network. The security of the domain itself.

To achieve the above objective, a system for implementing an IP network domain service includes: an IP network domain and a called network domain; the IP network domain includes an IP-Message-GW, and the called network domain The short message service center is included in the network domain; the called network domain further includes: a message interworking gateway respectively connected to the IP-Message-GW and the short message service center;

The IP-Message-GW sends the received message to the corresponding message interworking gateway according to the address information of the message interworking gateway set in the user;

The message interworking gateway forwards the message from the IP-Message-GW to the corresponding short message service center.

The message interworking gateway can be: a short message platform. .

According to the description of the foregoing technical solution, the IP-Message-GW in the present invention can call the caller without parsing the short message service center address information based on the IP network domain, such as the IMS network domain, from the message body of the message. The message submitted by the calling user in the network domain is directly sent to the message receiving end in the primary/called network domain, such as the SM-SC in the called network domain, the MIG or the SM-SC in the calling network domain, so that the IP-based The message originated by the network domain satisfies the message format of the SIP signaling, conforms to the usage habits of the users of the IMS network domain, and reduces the length of the occupied message body, thereby improving the implementation flexibility of the message service based on the IP network domain;

In addition, in the present invention, the message is directly routed to the called network domain by the IP-Message-GW, thereby avoiding the construction of the traditional network element device entity in the IP-based network, and reducing the maintenance work of the network device;

Further, in the present invention, by routing the message submitted by the calling user in the IP network domain to the message interworking gateway of the called network domain, the message routing of the calling network domain is further facilitated, and the security of the called network domain is improved. , thereby further improving the flexibility of message service implementation, and further promoting the development of message service interworking. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a network architecture of an IMS-based message service interworking with a conventional short message service;

2 is a flowchart of processing of an IP user registering to an IP-Message-GW;

3 is a short message mobile originating flow chart of a UE in an IMS network domain in the prior art; FIG. 4 is a schematic diagram of a system architecture on which a first embodiment of the present invention is based;

Figure 5 is a flow chart of the first embodiment of the present invention;

6 is a schematic diagram of a system architecture on which a second embodiment of the present invention is based;

Figure 7 is a flow chart of a second embodiment of the present invention;

Figure 8 is a flow chart of a third embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION The present invention will be further described in detail below with reference to the accompanying drawings.

The main idea of the present invention is to obtain the address information of the receiving end of the message service based on the IP-Message-GW of the IP network domain, based on the address information of the receiving end of the message service in the IP network domain. The IP-Message-GW sends the message it receives to the message service receiving end according to the obtained address information.

₀ further described below based on the technical solution of the present invention, the core idea of the present invention provides

The present invention is applicable to the case where an IP client based on an IP access mobile network uses an IP network domain such as an IMS network domain based message type service.

The invention can firstly set the address information of the message service receiving end of the master/called network domain in the IP-Message-GW, so that the MESSAGE is received in the IP-Message-GW. When it is determined, the MESSAGE request is determined to be sent to a legacy network, that is, a message based on the CS/PS network domain, and the MESSAGE request is sent according to the address information of the stored message service receiving end.

Here, the IP-Message-GW may determine whether the message needs to be sent to the CS PS-based network domain according to the called identifier information carried in the MESSAGE request, such as determining whether the format of the called identifier is a TEL URI format, and if it is a TEL URI In the format, the IP-Message-GW determines that the MESSAGE request needs to be sent to the CS/PS based network domain.

In addition, when the MESSAGE request is forwarded by the S-CSCF, the S-CSCF can judge the called identity information carried in the MESSAGE request, and only when the MESSAGE message needs to be sent to the CS/PS-based network domain, the S-CSCF Forwarding to the IP-Message-GW, at this time, the IP-Message-GW may not judge the MESSAGE request, and directly send the MESSAGE request to the address of the stored message service receiving end, that is, whether the message needs to be sent to the CS/PS based communication. The process of the network domain can also be implemented by other network entities.

In addition, the address information of the receiving end of the message service of the primary/called network domain may also be stored in other network device entities of the calling network domain, such as a network routing query entity.

When receiving the MESSAGE request, the IP-Message-GW obtains the address information of the message service receiving end of the called network domain by interacting with the entity.

In order to minimize and hide the network topology of the called operator, the operator of the called network domain may request the IMS network domain to access the SM of the called user through a message interworking gateway, such as MIG (Message Interworking Gateway). -SC, its network architecture is shown in Figure 4.

As can be seen from Figure 4, the MIG is added in the called legacy network domain. The MIG is connected to the IP-Message-GW in the calling IMS network domain through the XI interface, and through the X2 interface and the SM-in the called traditional network domain. SC connection. The originating call of the calling subscriber UE#1 in the IMS network domain The message is sent to the IP-Message-GW through the S-CSCF, and the IP-Message-GW obtains the address of the MIG corresponding to the called identifier in the message according to the correspondence between the preset called identification information and the MIG address information of the called network domain. Then, the message of the UE#1 is directly routed to the MIG of the called network domain, and the MIG further uses the correspondence between the information in the called identifier stored in the self-identification and the called user's home SM-SC, or Query other network entities, such as the network route query entity, obtain the SM-SC to which the called user belongs, route the message to the SM-SC to which the called user belongs, and transmit the message to the called party through the SM-SC to which the called user belongs. user.

When multiple SM-SCs are built in the called network domain, it is only necessary to open a MIG to the calling network domain to access the called network domain, thereby facilitating message routing of the calling network domain, and improving the Call the network domain's own security.

The address information of the receiving end of the message service of the primary/called network domain set in the IP-Message-GW or the address information of the receiving end of the message service of the primary/called network stored by other network device entities in the IMS network domain may be the called identifier The correspondence between the caller ID and the SM-SC address information to which the called user belongs may be the correspondence between the called identifier and the SM-SC address information to which the called user belongs, and may be a message interworking gateway between the called identifier and the called user. The correspondence relationship of the address information may also be directly the address information of one MIG that is only open, that is, the address information of the MIG that is uniquely set.

The network architecture of FIG. 4 of the present invention only lists the case where the calling network domain is an IMS domain, and the network architecture is also applicable to the case where the calling network domain is an IP-based domain under the non-IMS framework, that is, the calling user passes. The tunneling mode or the GAA mode is used to access the IP-Message-GW. The implementation principle is the same as the above description process, and will not be described in detail here.

In the network architecture of FIG. 4, for the interface X2 between the MG and the SM-SC, the protocol may adopt an IP-based protocol, such as SM-SC and SME (Short Message Entities short message entity) recommended by 3GPP TS 23.039. SMPP (Short Message Peer) To Peer point-to-point short message protocol. For the interface XI between the IP-Message-GW and the MIG, the protocol can also adopt the SMPP protocol or adopt its extended protocol, such as the CMPP protocol.

As operators develop short message services, in addition to developing peer-to-peer (Peer to Peer) short message services, they also develop short message services for the Internet, that is, end users can not only send short messages to a terminal, or Accept short messages from a terminal, or send short messages to an SP (Service Provider) on the Internet, or accept short messages from an SP, short messages from the end user and the SP. In the interworking network framework, there is a message intercommunication gateway similar to G, such as China Mobile's mobile Monternet SMS platform, China Unicom's Unicom unlimited messaging platform, in addition, the MIG above SMS platform can be directly used as the MIG. Therefore, in the implementation of the interworking requirement between the IMS-based message service and the traditional short message service, the network architecture provided by the present invention not only does not affect the upgrade of the traditional network, but also can fully utilize the existing network resources.

The invention will now be described in detail by way of specific examples.

The first embodiment of the present invention is based on the network architecture shown in FIG. 4. According to the network architecture, the processing flow for the IMS network user to send a short message to the traditional network in this embodiment is as shown in FIG. 5:

In Figure 5, in step 1, the UE registers with the S-CSCF according to the IMS registration procedure. In the IMS registration process, the functional entities such as I-CSCF and P-CSCF and the messages transmitted between many S-CSCFs and HSSs are involved. For the sake of brevity, they are not listed here.

Go to step 2. The UE sends a message to the S-CSCF based on the SIP MESSAGE mode.

Go to step '3. Based on the filter information, the S-CSCF forwards the message to the IP-Message-GW. Go to step 4. The IP-Message-GW returns a SIP 202 reception message to the S-CSCF, indicating that the message has been accepted.

To step 5, the S-CSCF forwards the SIP 202 reception message to the UE. Go to step 6. When the IP-Message-GW determines that the message needs to be routed to the legacy network, the IP-Message-GW addresses the MIG in the traditional network where the called party is located according to the called identity information, and then assembles the message. The message conforming to the interface protocol between the IP-Message-GW and the MIG, such as the message of the CMPP protocol, sends a submit message to the MIG, and the message contains the content of the message body of the SIP MESSAGE.

Here, the IP-Message-GW may determine, according to the called identification information carried in the message, whether the message needs to be sent to the CS/PS-based network domain, such as determining whether the format of the called identifier is a TEL URI format, and if it is a TEL In the URI format, the IP-Message-GW determines that the message needs to be sent to the CS/PS based network domain.

In addition, when the message is forwarded by the S-CSCF, the S-CSCF can judge the called identity information carried in the message, and only when the message needs to be sent to the CS/PS-based network domain, the S-CSCF goes to the IP- Message-GW forwards. At this time, the IP-Message-GW may not judge the message, and directly send the message to the address of the stored message service receiving end, that is, the process of determining whether the message needs to be sent to the CS/PS-based network domain. It can also be implemented by other network entities.

In addition, when receiving the message, the IP-Message-GW can obtain the MG address information corresponding to the called identifier in the message through the correspondence between the called identifier stored by the IP-Message-GW and the MIG address information of the called network domain. The IP-Message-GW can also interact with the related storage entity that stores the correspondence between the called identifier and the MIG address information of the called network domain in the IMS network domain to obtain the called network domain corresponding to the called identifier of the message. MIG address information.

Go to step 7. The MIG addresses the called party according to the called identifier in the submit message message, and the correspondence between the information in the called identifier set by itself and the SM-SC to which the called user belongs, or by querying other network entities. The user's 'home SM-SC' and forwards the submit message message to the SM-SC. The information in the above called identifier may be information such as a number segment. Here, if the interface XI between the IP-Message-GW and the MIG uses the same interface protocol as the interface X2 between the MIG and the SM-SC, the MIG can directly forward the IP-Message-GW Submit message to the SM-SC. Otherwise, the MIG needs to convert the message of the XI interface into a message conforming to the X2 interface and then send it to the SM-SC.

Step 8: After receiving the submit message message, the called subscriber's home SM-SC stores and forwards the message, and returns a message submission response message (Message Submit Response) to the MIG.

Go to step 9. The MIG returns a message submission response message to the IP-Message-GW.

Go to step 10. The IP-Message-GW uses SIP MESSAGE to send a message submission report to the S-CSCF.

Go to step 11. The S-CSCF sends a message submission report to the UE using the SIP MESSAGE. Go to step 12, the UE submits a report in response to the received message using the 200 ok message.

To step 13, the 200 ok response message is forwarded to the -Message-GW via the S-CSCF. In the above description for FIG. 5, since the IP-Message-GW can directly send the message submitted by the calling user of the IMS network domain to the MIG in the called network domain, the message is routed to the called party by the MIG in the called network domain. The SM-SC in the network domain avoids the construction of the traditional network element device entity in the IMS network domain, and reduces the maintenance of the network device in the IMS network domain. Meanwhile, the UE in the IMS network domain does not need to send the MESSAGE. The SM-SC address information is carried in the MESSAGE, conforming to the message format of the SIP signaling and the usage habits of the users of the IMS network domain.

The invention can also integrate the SM-SC/SMS-IWMSC/GMSC function in the IP-Message-GW, and directly convert the SIP MESSAGE and MAP signaling by the IP-Message-GW, and the stored and forwarded function of the converted short message. . This embodiment will be described below by means of the second embodiment.

The system composition based on the second embodiment of the present invention is as shown in FIG. 6, in the figure IP-Message- The GW is connected to the SM-SC in the called network domain, where the SM-SC/SMS-rWMSC/GMSC function is integrated, and the IP-Message-GW parses the message content from the received MESSAGE and assembles it into a standard MAP letter. The message of the format is obtained according to the relationship between the called user identifier in the received message and the relationship between the called user identifier set by the user and the short message service center address in the called network domain, or by querying other network entities to obtain the called network. The corresponding short message service center address in the domain is sent to the corresponding short message service center in the called network domain.

In this embodiment, the flow of implementing the message service based on the IP multimedia subsystem by the IP-Message-GW integrating the SM-SC/SMS-IWMSC/GMSC function is as shown in FIG. 7.

In Figure 7, in step 1, the UE registers with the S-CSCF according to the IMS registration procedure. In the IMS registration process, the functional entities such as I-CSCF and P-CSCF and the messages transmitted between many S-CSCFs and HSSs are involved. For the sake of brevity, it is not listed.

Go to step 3. Based on the filter information, the S-CSCF forwards the message to the IP-Message-GW. Go to step 4. The IP-Message-GW returns a SIP 202 receive message to the S-CSCF, indicating that the message sent by the S-CSCF has been accepted.

Go to step 5. The S-CSCF forwards the SIP 202 to the UE to receive the message.

Go to step 6. When the IP-Message-GW determines that the MESSAGE needs to be routed to the legacy network, the IP-Message-GW parses the message content from the received MESSAGE and assembles the message into a standard MAP signaling format. And then store the message (Message Store ) and forward it.

Here, the IP-Message-GW may determine whether the message needs to be sent to the CS/PS-based network domain according to the called identifier information carried in the MESSAGE request, such as determining whether the format of the called identifier is a TEL URI format, if TEL UI format, then The IP-MESSAGE-GW determines that the MESSAGE request needs to be sent to the CS/PS based network domain.

Go to step 7. IP-Message-GW uses SIP MESSAGE to send a message to the S-CSCF to submit a report.

Go to step 8. The S-CSCF sends a short message submission report to the UE using the SIP MESSAGE. Go to step 9. The UE submits a report by using the 200 ok message in response to the received short message.

Go to step 10, 200 ok response message is forwarded to the IP-Message-GW via the S-CSCF. In this embodiment, the IP-Message-GW can directly implement the conversion of MESSAGE and MAP signaling, and the storage and forwarding function of the converted short message, thereby reducing the maintenance work on the network device entity in the IMS network domain, and When the SIP MESSAGE is sent, the UE in the IMS network domain does not need to carry the SM-SC address information in the MESSAGE, and conforms to the message format of the SIP signaling and the usage habits of the users of the IMS network domain.

The present invention can also directly obtain the address information of the SM-SC/SMS-IWMSC related network entity in the calling network domain by using the IP-Message-GW of the calling IMS network domain, thereby implementing the message service based on the IP multimedia subsystem, This will be described in detail by the third embodiment.

The system on which the third embodiment of the present invention is based is the same as the second embodiment. In this embodiment, the mapping relationship between the calling user identification information and the SM-SC/SMS-IWMSC address information to which the calling user belongs is configured in the IP-Message-GW, or the IP-Message-GW receives the corresponding relationship. In the case of MESSAGE, the short message service center address in the calling network domain corresponding to the calling user is obtained by interacting with other storage entities in the IMS network domain, and the IP-Message-GW starts the calling user according to the corresponding relationship. The call message is directly routed to the SM-SC/SMS-IWMSC to which the calling party belongs in the calling network domain. The specific implementation process is as shown in FIG. 8.

In Figure 8, in step 1, the UE registers with the S-CSCF according to the IMS registration procedure. In the IMS registration process, the functional entities such as I-CSCF and P-CSCF and the messages transmitted between many S-CSCFs and HSSs are involved. For the sake of brevity, it is not listed.

Go to step 3. Based on the filter information, the S-CSCF forwards the message to the IP-Message-GW. Go to step 4. The IP-Message-GW returns a SIP 202 reception message to the S-CSCF, indicating that the message has been accepted.

Go to step 5. The S-CSCF forwards the SIP 202 to the UE to receive the message.

Go to step 6. When the IP-Message-GW determines that the message needs to be routed to the legacy network, the IP-Message-GW parses the message content from the received message and installs it into the standard iVLAP signaling format. The short message is then obtained according to the calling identifier carried in the message, and the corresponding SMS-IWMSC/SM-SC address information in the calling network domain is obtained, and then the IP-Message-GW forwards the assembled MAP signaling to the SMS-IWMS.

In step 6, the IP-Message-GW may determine, according to the called identification information carried in the message, whether the message needs to be sent to the CS/PS-based network domain, such as determining whether the format of the called identifier is a TEL URI format. In the case of the TEL URI format, the IP-Message-GW determines that the message needs to be sent to the CS/PS based network domain.

In addition, when the message is forwarded by the S-CSCF, the S-CSCF can judge the called identity information carried in the message, and only when the message needs to be sent to the CS/PS-based network domain, the S-CSCF goes to the IP- Message-GW forwards. At this time, the IP-Message-GW may not judge the message, and directly send the message to the address of the stored message service receiving end, that is, the judgment The process of disconnecting a message to a CS/PS based network domain may also be implemented by other network entities.

In addition, when receiving the message, the IP-Message-GW can obtain the corresponding caller ID in the message through the correspondence between the calling party identifier stored by the IP-Message-GW and the SM-SC address information to which the calling user belongs. The SM-SC/SMS-IWMSC address information to which the calling user belongs; the IP-Message-GW can also interact with the related storage entity in the IMS network domain to obtain the calling user corresponding to the calling party identifier of the message. SM-SC/SMS-IWMSC address information.

Go to step 7. The SMS-IWMSC forwards the short message to the SM-SC.

Go to step 8. The SM-SC sends a short message submission report to the SMS-IWMSC.

Go to step 11. The S-CSCF sends a short message submission report to the UE using the SIP MESSAGE. Go to step 12, the UE submits a report by using the 200 ok message in response to the received short message. Go to step 13, 200 ok response message is forwarded to the IP-Message-GW via the S-CSCF. In the above description for FIG. 8, the IP-Message-GW can directly assemble the messages that need to be sent to the legacy network into MAP signaling and send them to the SMS-IWMSC in the calling network domain, thereby avoiding the traditional construction in the IMS network. The network element device entity reduces the maintenance of the network device in the IMS network. At the same time, the UE in the IMS network domain does not need to carry the SM-SC address information in the message, and conforms to the message format of the SIP signaling. The usage habits of IMS network domain users.

The description in the above three embodiments is described by taking the calling network domain as an IMS network domain as an example. The technical solution is also applicable to the IP network domain in the non-IMS architecture, that is, the calling user passes through the tunnel mode. Or GAA access to IP-Message-GW The implementation principle is based on the same as the above described process, and will not be described in detail herein.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are included in the present invention, should be included in the present invention. Within the scope of protection.

Claims

Claim

A method for implementing a message service based on an IP network domain, comprising: a. setting address information of a message service receiving end of a predetermined master/called network domain in an IP network domain;

2. The method for implementing an IP network domain message service according to claim 1, wherein the predetermined called network domain comprises: a circuit domain based on circuit switching/packet switching.

3. The method for implementing an IP network domain message service according to claim 1, wherein the IP network domain comprises: a network domain based on an IP multimedia subsystem.

The method for implementing the IP network domain message service according to claim 1, wherein the step b specifically includes:

Bll, the IP-Message-GW determines, according to the predetermined information carried in the message received by the IP-Message-GW, a message that needs to be sent to the predetermined called network domain;

Or the step b includes:

The method for implementing the IP network domain message service according to claim 4, wherein the predetermined information comprises: a called identifier;

And the step bl specifically includes:

The method for implementing the IP network domain message service according to claim 4 or 5, wherein the step b2 specifically includes:

The IP-Message-GW acquires the address information of the message service receiving end of the master/called network domain by interacting with other network entities storing the address information of the message receiving end of the main/called network domain of the preset.

The method for implementing the message service based on the IP network domain according to claim 6, wherein the receiving end of the message service comprises: a message interworking gateway for the predetermined called network domain;

And the step c specifically includes:

The IP-Message-GW assembles the message according to an interface protocol with the message interworking gateway, and sends the assembled message according to the address information of the set message interworking gateway.

The method for implementing the IP network domain message service according to claim 7, wherein the address information of the set message interworking gateway comprises: an address of a uniquely set message interworking gateway;

The method for implementing the IP network domain message service according to claim 7, wherein the interface protocol is: SMPP protocol or CMPP protocol.

The method for implementing the IP network domain message service according to claim 7, wherein the method further comprises:

The method for implementing the IP network domain message service according to claim 4 or 5, wherein the message service receiving end comprises: a short message service center of the calling network domain;

The step a specifically includes:

A short message service center in the calling network domain is built in the IP-Message-GW.

The method for implementing the IP network domain message service according to claim 11, wherein the step c specifically includes:

The method for implementing the IP network domain message service according to claim 6, wherein the message service receiving end comprises: a short message service center of the calling network domain; and the pre-set reservation The address information of the receiving end of the message service of the calling network domain includes:

The correspondence between the calling subscriber identity and the short message service center address information of the calling network domain.

The method for implementing the IP network domain message service according to claim 13, wherein the step c specifically includes:

The IP-Message-GW assembles the message into MAP signaling, and determines address information of the short message service center of the calling network domain according to the calling subscriber identity and the corresponding relationship, and passes the MAP signaling to the SMS- The IWMSC is sent to the calling network domain short message service. Heart.

The method for implementing the IP network domain message service according to claim 6, wherein the message service receiving end comprises: a short message service center of the called network domain; and the pre-set reservation The address information of the receiving end of the message service of the called network domain includes:

An implementation system for an IP network domain message service, comprising: an IP network domain and a called network domain, wherein the IP network domain includes an IP-Message-GW, and the called network domain includes a short message. a service center, where the IP-Message-GW is connected to the short message service center;

The system for implementing an IP network domain message service according to claim 16, wherein the short message service center is integrated in the IP-Message-GW.

18. An implementation system based on an IP network domain message service, comprising: an IP network domain and a called network domain, wherein the IP network domain includes an IP-Message-GW, and the called network domain includes a short message. a service center, where the called network domain further includes: a message interworking gateway respectively connected to the IP-Message-GW and the short message service center;

The message interworking gateway forwards the message from the IP-Message-GW to the corresponding short Message business center.

The system for implementing an IP network domain message service according to claim 18, wherein the message interworking gateway is: a short message platform.