WO2008014718A1 - Procédé et système de partage dynamique de messages courts dans un réseau de sous-systèmes multimédia ip - Google Patents
Procédé et système de partage dynamique de messages courts dans un réseau de sous-systèmes multimédia ip Download PDFInfo
- Publication number
- WO2008014718A1 WO2008014718A1 PCT/CN2007/070363 CN2007070363W WO2008014718A1 WO 2008014718 A1 WO2008014718 A1 WO 2008014718A1 CN 2007070363 W CN2007070363 W CN 2007070363W WO 2008014718 A1 WO2008014718 A1 WO 2008014718A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- short message
- terminal
- sms
- network entity
- called
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
Definitions
- the present invention relates to the field of communications, and more particularly to a method and system for short message forking.
- the short message service can transmit a certain size message between each terminal.
- the message of a certain size is usually called a short message, and the short message service is already in circuit switching (Circuit)
- CS Global System for Mobile Communications/Universal Mobile Telecommunication System Public Land Mobile Network
- GSM/UMTS PLMN Global System for Mobile Communications/Universal Mobile Telecommunication System Public Land Mobile Network
- IP Multimedia IP Multimedia Subsystem
- IMS IP Multimedia Subsystem
- the IMS uses the packet domain as the bearer channel for its upper layer control signaling and media transmission, and introduces a session initiation protocol (Session Initial)
- SIP Session Initiation Protocol
- SIP Session Initiation Protocol
- IMS's network convergence solution enables operators to provide the same services to fixed and mobile users based on a unified core network.
- the network architecture of IMS's fixed network and mobile network core network can not only reduce the complexity of the network structure. Moreover, the operation and maintenance cost of the network can be reduced.
- IP Multimedia Common Identity IP Multimedia Public
- IMPU Service Call Session Control Function Block (Sendee-Call Section Control) Function, abbreviated as S-CSCF) Flexible branching processing based on the capability information and preference information of the terminal. That is, the S-CSCF acts as a forked agent to separately send messages to terminals of multiple shared IMPUs.
- S-CSCF Service Call Session Control Function Block
- the S-CSCF acts as a forked agent to separately send messages to terminals of multiple shared IMPUs.
- multiple terminals share the IMPU ⁇ . Because the terminal has different support capabilities for the short message format, the S-CSCF needs to consider the capabilities of each terminal and the supported short message format when the S-CSCF forks the short message to each terminal.
- the function of message format conversion is defined in a similar application server (Application
- AS SMS Server
- FIG. 1 A schematic diagram of the IP architecture is shown in Figure 1. The functions of each network entity are as follows:
- Short Message Service Short Message Service
- SMSC Short message Center
- SME Session Management Entity
- ME Mobile Equipment
- SMSC Short Message Transmission
- SMS Gateway SMS-Gateway
- SMS-IWMSC/GMSC home location register
- IP Short Message Gateway IP Short Message
- the gateway (referred to as IP-SM-GW) 106 is configured to provide an interworking function for transmitting short messages between the UE and the GSM/UMTS network, and the entity may act as an AS in the IMS.
- IP-SM-GW Home Location Register/Home Subscriber Server
- HLR/HSS HLR/HSS 108
- short message service Short Message
- SMS Service provides routing function, when the SMS is terminated, by the gateway mobile switching center
- GMSC Mobile Network Controller
- the Center (referred to as MSC) 110 is configured to provide a route for the short message to be transmitted from the CS domain to the IMS domain.
- S-CSCF 112 S-CSCF Function
- the S-CSCF checks the triggering rule, finds the address of the IP-SM-GW, and triggers the third-party registration process;
- the IP-SM-GW stores an address of the S-CSCF
- the HSS/HLR stores the E.164 address information of the IP-SM-GW, and returns a response to the IP-SM-GW;
- the S-CSCF returns a response to the UE.
- SMSC forwards SMS messages to SMS Gateway Mobile Switching Center (SMS-Gateway)
- SMS-GMSC MSC, referred to as SMS-GMSC
- the SMS-GMSC sends a routing request to the HLR/HSS, where the routing request includes an indication of the SMS-GMSC branch. a flag for routing IP messages;
- HSS/HLR returns the E.164 address of the registered IP-SM-GW of the user
- SMS-GMSC sends a message to
- IP-SM-GW the mobile station's international ISDN number carrying the UE (Mobile Station)
- MSISDN International ISDN Number
- the S-CSCF forwards the SIP MESSAGE to the UE;
- the S-CSCF forwards the SIP MESS AGE to the IP-SM-GW according to the filtering rule
- SMS-GMSC sends the report status to the HLR/HSS
- SMS-GMSC sends a report to the SM-SC
- the IP-SM-GW acknowledges the message to the S-CSCF through 200 OK.
- the network architecture after adding the called side SMS center on the IP architecture is shown in Figure 4.
- the network architecture shown in Figure 4 is the SMSC shown in Figure 1 by MO-SMSC.
- SMSC is set on the SMS sending end and the SMS receiving end respectively.
- MO-SMSC is the short message center of the short message sending end
- MT-SMSC is the short message center of the short message receiving end.
- the MSC parses the SMS center address in the message and sends it to MO-S via SMS-IWMSC through route analysis.
- the MO-SMSC queries the MT-SMSC through the HSS/HLR, and sends a short message to the MT-SMSC;
- SMS-GMSC to the HSS/HLR takes the called routing information
- the HSS/HLR returns the address of the IP-SM-GW;
- SMS-GMSC sends a short message to IP-SM-GW;
- the IP-SM-GW sends a short message to the S-CSCF registered by the third party;
- the S-CSCF routes the SMS to the UE.
- IMS domain UE sends a short message, and reaches the IP-SM-GW through the S-CSCF;
- the MO-SMSC queries the MT-SMSC through the HSS/HLR, and sends a short message to the MT-SMSC;
- the SMS-GMSC takes the called routing information from the HSS/HLR;
- the HSS/HLR returns the number of the MSC where the called party is currently located;
- SMS-GMSC sends a text message to the MSC where the called party is located;
- the MSC sends a text message to the called party via paging.
- the IMS domain sends a short message, and the short message arrives at the S-CSCF.
- SMS-AS short message application service function block
- SMS-AS filtering rule
- SMS-AS performs caller's service control and necessary redirection (when the called address is encapsulated in the o message body). SMS-AS does not store the SMS, and then sends the SMS back to the S-CSCF. If only the requirements in TISPAN are considered, this step is optional;
- DNS Name Server
- the I-CSCF forwards the short message to the S-CSCF where the called party is located;
- SMS-AS on the called side After the SMS-AS on the called side performs supplementary service processing, it returns a short message to the S-CSCF where the called party is located;
- the IP-SM-GW is used as the interworking process of the IMS text message to the CS domain SMS message under the network architecture of the MGCF location and the short message interworking.
- FIG. 6 A schematic diagram of another network architecture for short message interworking in the prior art is shown in FIG. 6. The structure of the architecture and S
- BGCF BGCF
- BGCF has an egress gateway control function, which can be used as an egress gateway for short messages in this architecture;
- SMS Media Gateway Control Function Block SMS-Media Gateway Control
- SMS-MGCF has the function as a gateway for IMS domain short message and CS domain short message interworking
- SMS-AS has the function of converting the SMS service SMS format and attaching some value-added services
- I-CSCF I-CSCF Function
- the I-CSCF is used as an access point for the home network to shield the network structure.
- the SMS-MGCF and the SMS-AS are combined to form an IP-SM-GW network entity.
- the message is sent to the S-CSCF, and the S-CSCF checks the filtering rules and triggers the service to the AS;
- the IMS core network determines whether the receiver is an IMS user, and the S-CSCF processes according to the process in the IMS. If the Request-URI contains the TEL-URI, the S-CSCF goes to the database to find a corresponding SIP URI. If the SIP URI is not found, the S-CSCF forwards the message to the BGCF;
- the BGCF determines the next hop route based on the SIP request method or any information about the route-specific TelRul that it owns.
- the analysis method can be a public method (such as DNS, ENUM (Telephone Number Mapping working group))
- IP-SM-GW Or IP-SM-GW.
- routing to the IP-SM-GW to the IP-SM-GW;
- IP-SM-GW checks if there is enough information to form an SMS message.
- the IP-SM-GW obtains valid sender and receiver information from the IMS header (eg, the sender may be placed in the asserted id in the format of TelUri);
- SMS-IWMSC forwards SMS to SMS-IWMSC
- the SM-SC sends a delivery report to the SMS-IWMSC;
- SMS-IWMSC sends a delivery report to IP-SM-GW.
- S726 to S736 only occur when the user requests to send a delivery failure report in need of S704, and the delivery fails;
- IP-SM-GW maps the submitted report and sends it to the S-CSCF;
- the S-CSCF sends a report to the UE
- SMS termination process under this architecture can be found in the 'SMS Receiving Process under MS OVER IP Architecture'.
- the present invention is directed to a method and apparatus for short message splitting, which converts a short message sent by a calling party into one or more formats that can be received by one or more called terminals, thereby causing one or more Each of the called terminals can receive a text message in the correct format.
- a short message splitting method where the first network entity acquires the capability information of the terminal or the short message format conversion information corresponding to the terminal, and the method specifically includes:
- the first network entity After receiving the short message that needs to be sent to one or more called terminals, the first network entity converts the short message into the one according to the obtained capability information of the terminal or the short message format conversion information corresponding to the terminal. Or a plurality of text messages of one or more formats that the called terminal can receive.
- a short message fork system comprising:
- the capability information obtaining device is located at the first network entity side, and is configured to acquire capability information of the terminal or SMS format conversion information corresponding to the terminal;
- the short message format conversion device is located at the first network entity side, and after receiving the short message that needs to be sent to one or more called terminals, according to the capability information or terminal corresponding to the terminal acquired by the capability information acquiring device The short message format conversion information is converted into the one or more short messages of the one or more formats that the called terminal can receive.
- the present invention solves the problem that the called party has multiple IMMUs shared by terminals with different capabilities in the IMS domain, and some terminals The problem of not receiving the correct format of the short message is improved, thereby improving the convenience and effectiveness of the connection between the end users.
- FIG. 1 is a schematic diagram showing an IP-based SMS architecture
- FIG. 2 is a schematic diagram showing a registration process of a UE in the architecture shown in FIG. 1;
- FIG. 3 is a schematic diagram showing a process of ending a short message in the architecture shown in FIG. 1;
- FIG. 5 is a flow chart showing the manner of short message routing in the IMS domain specified by TISPAN;
- FIG. 6 is a schematic diagram showing a network architecture of existing short message interworking
- FIG. 7 is a schematic diagram showing an interworking flow from an IMS text message to a CS domain SMS message under the architecture shown in FIG. 6;
- FIG. 8 is a flow chart showing a method of short message splitting according to the present invention.
- FIG. 10 is a block diagram showing a short message fork system according to the present invention.
- FIG. 11 is a flow chart showing a short message splitting method according to Embodiment 1 of the present invention.
- FIG. 12 is a flow chart showing a short message splitting method according to Embodiment 2 of the present invention.
- FIG. 13 is a flow chart showing a short message splitting method according to Embodiment 3 of the present invention.
- FIG. 14 is a flow chart showing a short message splitting method according to Embodiment 4 of the present invention.
- FIG. 16 is a flow chart showing a short message splitting method according to Embodiment 6 of the present invention.
- FIG. 17 is a flow chart showing a short message splitting method according to Embodiment 7 of the present invention.
- the present invention aims to provide a short message bifurcation method and apparatus for converting a short message sent by a calling party into a Or a plurality of text messages of one or more formats that the called terminal can receive, so that one or more called terminals can receive the short message in the correct format.
- the short message splitting method of the present invention mainly includes the following steps:
- Step 1 The short message center or the corresponding network entity on the called side receives the short message
- Step 2 The foregoing short message center or the corresponding network entity constructs a short message corresponding to the format according to the capability information of the called terminal, and instructs the S-CSCF to send the constructed short message to the called terminal.
- the foregoing short message center or the corresponding network entity needs to know the conversion type information of the short message before constructing the short message of the corresponding format.
- the above-mentioned short message center or the corresponding network entity is known to implement the conversion type information of the short message:
- Method 1 the short message center or the corresponding network entity sends a subscription event data packet to the S-CSCF where the called terminal is located, and obtains the capability information of the called terminal from the S-CSCF where the called terminal is located, according to the capability information. Determine the conversion type information of the short message.
- Method 2 The S-CSCF where the called terminal is located determines that the user multi-terminal shares the IMPU, and decides to trigger the above-mentioned short message center or the corresponding network entity to perform the conversion, and carries the type quantity information that the called terminal needs to convert.
- Method 3 the SMS center or the corresponding network entity through other network entities capable of sensing the terminal capabilities, such as device manager (Device
- DM the online server (Presence), after obtaining the capability information of the called terminal, determines the conversion type information of the short message according to the capability information.
- Method 4 the short message center or the corresponding network entity registers the capability information of the terminal after registering with the UE, and after the UE sends the capability information of the called terminal to the short message center or the corresponding network entity, the short message is determined according to the capability information. Conversion type information.
- Method 1 If the terminal is registered with its own capability information, it can be indicated by adding the calling preference information.
- Method 2 If the capability information of the terminal is obtained by using another network entity capable of sensing the capability of the terminal or reporting the capability information after registration by the UE, the terminal identifier (which includes the capability of the called terminal to register) may be obtained. Force information, GRUU, terminal identification, etc.) to indicate.
- FIG. 8 A flow chart of the short message splitting method according to the present invention is shown in FIG. 8. As can be seen from FIG. 8, the complete steps of the IMS domain multi-terminal sharing IMPU/SMS bifurcation method according to the present invention include:
- SMS center or similar functional entity receives the short message
- the SMS center or similar functional entity learns information about how many types of text messages need to be converted into the above-mentioned short message type
- the short message center or the like function entity converts the foregoing short message format, and adds the indication information of the called terminal to the converted short message;
- the short message center or similar functional entity corresponds to different network entities in different network architectures.
- the IP-SM-GW plays such a role
- such a function is realized by the SMS-AS.
- FIG. 9 Another flow chart of the short message splitting method according to the present invention is shown in FIG. 9, and includes the following steps:
- the first network entity acquires capability information of one or more terminals or acquires short message format conversion information from the call control function entity by using other network entities in the network;
- the first network entity After receiving the short message to be sent, the first network entity converts the short message according to the acquired capability information or the short message format, and converts the short message into one or more short messages that can be received by the called terminal;
- the first network entity After the first network entity adds the terminal indication information corresponding to the called terminal to the converted short message, the first network entity sends the short message to the call control function entity where the called terminal is located;
- the first network entity includes at least one of an IP short message gateway and a short message service application server.
- the other network function entities include at least one of a call control function entity, a registered user equipment, and a network entity capable of sensing terminal capabilities.
- a network entity capable of sensing terminal capabilities includes at least one of a device manager and an online server.
- the first network entity may subscribe to the call control function entity or the registered user equipment for capability information of one or more called terminals.
- the first network function entity may acquire capability information of one or more called terminals from a network entity capable of sensing the terminal capability.
- step S902 after receiving the short message to be sent, the call control function entity determines whether one or more called terminals share the IP multimedia public identity, and if so, the call control The function entity sends the foregoing short message and the corresponding short message format conversion information to the first network entity.
- the short message is converted into at least one of an SMS format and a text format.
- FIG. 10 The structure diagram of the short message fork system of the present invention is shown in FIG. 10, and includes the following modules:
- the capability information obtaining apparatus 1002 is located at the first network entity side, and acquires capability information of one or more terminals or acquires short message format conversion information from the call control function entity through other network entities in the network; [159] SMS format conversion The device 1004 is located on the first network entity side, and after receiving the short message to be sent, converting the short message to one or more received by the called terminal according to the capability information or the short message format conversion information acquired by the capability information acquiring device. a text message of one or more formats;
- the SMS splitting device 1006 is located at the first network entity side, and after adding the terminal indication information corresponding to the called terminal to the converted short message, respectively sending the short message to the call control where one or more called terminals are located.
- the short message transmitting device 1008 located at the call control function entity side, sends a short message from the short message fork device to the called terminal according to the terminal indication information.
- the first network entity includes at least one of an IP short message gateway and a short message service application server.
- SMS fork system other network function entities include a call control function entity, after registration At least one of a user device, and a network entity capable of sensing terminal capabilities.
- a network entity capable of sensing terminal capabilities includes at least one of a device manager and an online server.
- the capability information acquiring means may subscribe the capability information of one or more called terminals to the call control function entity or the registered user equipment.
- the capability information acquiring apparatus may acquire capability information of the one or more called terminals from a network entity capable of sensing the terminal capability.
- the capability information acquiring device located on the first network entity side receives the short message format conversion information from the call control function entity, wherein after the call control function entity receives the short message to be sent, Determining whether one or more called terminals share an IP multimedia public identity, if
- the short message and short message format conversion information is sent to the first network entity.
- the short message is converted into at least one of an SMS format and a text format.
- SMS-AS Short Message Service
- the processing flow includes the following steps:
- SMS-AS initiates a subscription to the S-CSCF, and the S-CSCF returns a response to the SMS-AS.
- the S-CSCF sends a NOTIFY message to the SMS-AS, notifying the capability information of each terminal of the SMS-AS, and the SMS-AS returns a response to the S-CSCF.
- FIG. 1 A schematic flowchart of the short message splitting method in the second embodiment of the present invention is shown in FIG.
- the S-CSCF of the called terminal determines that the user multi-terminal shares the IMPU, and decides to trigger the SMS center or the corresponding network entity to perform the conversion, and notifies the short-distance center or the corresponding network entity of the conversion type information of the terminal.
- the processing flow includes the following steps:
- the S-CSCF of the called terminal determines that the user multi-terminal shares the IMPU, and decides to trigger the SMS center or the corresponding network entity to perform the conversion, and the S-CSCF determines the capability information of each terminal to determine how many types of short messages need to be converted, and converts this. Type information is added to the message;
- the S-CSCF sends a message with the conversion type information to the SMS-AS;
- FIG. 180 A schematic flowchart of a short message splitting method according to Embodiment 3 of the present invention is shown in FIG.
- the capability of the terminal is obtained by other network entities, and then the conversion type information is obtained.
- the processing flow includes the following steps:
- SMS-AS subscribes to the capability information of the terminal to other network entities such as DM/Prersence;
- S1304 other network entities such as DM/Prersence notify the SMS-AS terminal of the capability information by SMS;
- SMS-AS receives the above text message
- the SMS-AS determines the type information of the short message to be converted according to the capability information of the user terminal.
- FIG. 14 A schematic flowchart of the short message splitting method in the fourth embodiment of the present invention is shown in FIG. 14. This embodiment is in the existing SMS IP
- the CS domain to the IMS domain share the SMS process of the CS domain after receiving the message from the CS domain. It is assumed that UE1 and UE2 share one IMPU, UE1 only supports SMS messages in SMS format, and UE2 only supports text messages in text format.
- the processing flow includes the following steps: [187] S1402
- the UE is registered to the S-CSCF through the IMS registration process, and the subscription process of the short message is completed, and the subscription process of the terminal capability is performed.
- SMS-IWMSC forwards the short message to the SM-SC
- the SMS-GMSC sends a routing request to the HLR/HSS, which includes an indication flag indicating that S
- MS-GMSC supports IP message routing
- HSS/HLR returns the E.164 address of the IP-Message-GW registered by the user
- the SMS-GMSC sends a short message to the IP-SM-GW, where the MSISDN of the UE is carried;
- the IP-SM-GW converts the above MSISDN into a TelUrl, and obtains the short message information that needs to be converted into two format types, and splits the original short message into two short messages encapsulating the SMS format and the text format and respectively adds corresponding terminals. Instruct, the peer finds the corresponding S-CSCF address according to TelUrl;
- IP-SM-GW separately sends the SMS format and text format SMS to the S-CSCF;
- S1422 the S-CSCF respectively responds to the IP-Message-GW;
- the S-CSCF separately sends the short message of the corresponding format to the terminal with the corresponding capability according to the terminal indication carried in the short message;
- FIG. 15 A schematic diagram of a short message splitting method according to Embodiment 5 of the present invention is shown in FIG. 15.
- the process of receiving the short message from the CS domain in the short message process of the multiple terminals of the shared IMPU from the CS domain to the IMS domain under the framework of the called side short message center is introduced. It is assumed that UE1 and UE2 share one IMPU, UE1 only supports SMS messages encapsulated in SMS format, and UE2 only supports short messages in text format.
- the processing flow includes the following steps:
- the UE is registered to the S-CSCF through the IMS registration process, and the subscription process of the short message is completed, and the subscription process of the terminal capability is performed.
- the MT-SMSC sends a routing request to the HLR/HSS, which includes an indication flag to support IP message routing; [208] S1514, the HSS/HLR returns the E.164 address of the registered IP-SM-GW of the user;
- the MT-SMSC sends a message to the IP-SM-GW, where the MSISDN of the UE is carried;
- the IP-SM-GW converts the MSISDN into a TelUrl and obtains the short message information that needs to be converted into two format types.
- the original short message is forked into two short messages encapsulating the SMS format and the text format, and the corresponding terminal indications are respectively added, and the corresponding S-CSCF address is found according to the TelUrl;
- IP-SM-GW sends SMS to S-CSCF respectively;
- S1522 the S-CSCF respectively responds to the IP-Message-GW;
- the S-CSCF sends the corresponding format short message to the corresponding terminal according to the terminal indication carried in the short message.
- FIG. 16 A schematic diagram of a short message splitting method according to Embodiment 6 of the present invention is shown in FIG. 16.
- the process of receiving the short message from the CS domain is received in the short message process of the multiple terminals of the shared IMPU from the CS domain to the IMS domain. It is assumed that UE1 and UE2 share one IMP U, UE1 only supports SMS messages encapsulated in SMS format, and UE2 only supports text messages in text format. Its processing flow includes the following steps:
- SMSC sends a short message to the SMS-GMSC
- SMSC-GMSC to the HSS/HLR obtains the address of the SMS-MGCF
- SMSC-GMSC sends a short message to SMS-MGCF, and SMS-MGCF returns a response;
- SMS-MGCF routes SMS to I-CSCF
- S 1618-S1620 the I-CSCF to the HSS/HLR take the called S-CSCF address
- the S-CSCF determines that the called user is an IMPU shared by multiple terminals, triggering the SMS-AS to perform the conversion and Forking processing;
- SMS-AS learns that the message needs to be converted into two different format types according to the information on the S-CSCF or through its own judgment. After converting the message into the packaged SMS format and text format and adding the corresponding terminal instructions respectively, The message is sent to the S-CSCF;
- the S-CSCF selects an appropriate message format according to the terminal indication and sends it to different terminals.
- FIG. 17 A schematic flowchart of the short message splitting method in the seventh embodiment of the present invention is shown in FIG. 17.
- This embodiment is a process of receiving a short message from an IMS domain in a short message process of multiple terminals sharing the IMPU from the IMS domain to the IMS domain under the TISPAN architecture. It is assumed that UE1 and UE2 share one IMPU, UE1 only supports SMS messages encapsulated in SMS format, and UE2 only supports text messages in text format.
- the processing flow includes the following steps:
- the S-CSCF receives the short message from the UE, where the short message may be in a text format or may be an encapsulated SMS format.
- the S-CSCF determines, according to the triggering rule, whether it needs to perform the message conversion to the calling SMS-AS and the processing of the calling supplementary service, which is assumed to be processed by the SMS-AS;
- SMS-AS converts the message or processes the supplementary service of the calling party
- the SMS message is sent back to the S-CSCF;
- S-CSCF sends the short message to the I-CSCF
- S1718-S1720, I-CSCF to HSS/HLR obtain the address of the S-CSCF where the called party is located;
- the I-CSCF sends the message to the S-CSCF where the called party is located;
- the S-CSCF judges the called party and finds that the called party has multiple terminals sharing the IMPU, and triggers the short message center on the called side to perform format conversion and Forking processing;
- SMS-AS learns that the message needs to be converted into two different format types according to the information on the S-CSCF or through its own judgment. After converting the message into the packaged SMS format and text format and adding the corresponding terminal instructions respectively, The message is sent to the S-CSCF separately;
- the S-CSCF separately sends the short message of the corresponding format to the terminal with the corresponding capability according to the terminal indication carried in the short message.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Description
说明书 用于 IP多媒体子系统网络的短信分叉方法及系统
[1] 技术领域
[2] 本发明涉及通信领域, 更具体地, 涉及一种短信分叉 (Forking) 方法及系统。
[3] 背景技术
[4] 短信业务可以使各个终端之间传递一定大小的消息, 该一定大小的消息通常称 为短信, 短信业务已经在电路交换 (Circuit
Switched, 简称 CS) 域的蜂窝网络中获得了极其成功的应用。 短信业务的实现引 进了一种叫短信中心的网络实体, 通过短信中心各个终端可以实现短信的转发 、 存储、 延迟发送以及其他增值业务。 同吋, 全球移动通信系统 /通用移动通信 系统公众陆地移动网络 (Global System for Mobile Communications /Universal Mobile Telecommunication System Public Land Mobile Network, 简称 GSM/UMTS PLMN) 需要支持短信在短信中心和终端之间的转发功能。
[5] 第三代移动通信标准化伙伴项目 (3rd Generation Partnership
Project, 简称 3GPP) R5阶段引进了 IP多媒体子系统 (IP Multimedia
Subsystem, 简称 IMS) , IMS是设于现有网络的分组域之上的一个子系统。 IMS 釆用分组域为其上层控制信令和媒体传输的承载通道, 并且引入会话发起协议 (Session Initial
Protocol, 简称 SIP) 作为业务控制协议, 禾 lj用 SIP简单、 易扩展、 媒体组合方便 等特点, 将业务控制与承载控制分离, 从而能够提供丰富的多媒体业务。 IMS的 网络融合方案使运营商能够基于统一的核心网络为固定和移动用户提供相同的 业务, IMS的这种固网和移动网的核心网并存的网络架构, 不仅可以减少网络结 构的复杂度, 而且可以降低网络的运维成本。
[6] 在 IMS系统中, 一个 IP多媒体共有标识 (IP Multimedia Public
Identity, 简称 IMPU) 可以被多个终端所共享。 在各个终端注册的吋候, 可能会 携带终端的能力信息和偏好信息。 服务呼叫会话控制功能块 (Sendee-Call Section Control
Function, 简称 S-CSCF) 可以根据终端的能力信息和偏好信息进行灵活的分叉处 理。 即 S-CSCF充当分叉代理人的角色向多个共享 IMPU的终端分别发送消息。 在 当前短信互通的架构下, 多个终端共享 IMPU吋, 因为终端对短信格式的支持能 力不同, 所以在 S-CSCF向各个终端分叉短信吋, 需要考虑各个终端的能力和支 持的短信格式, 而在当前的架构下, 消息格式转换的功能被定义在类似应用服 务器 (Application
Server, 简称 AS) 的短信网关上实现, 这样现有的 S-CSCF所支持的分叉操作将 不能满足短信分叉吋的需求。
[7] 下面详细介绍在某些已定义的架构下的短信发收流程。
[8] —、 以下描述基于 IP的短消息业务 (Short Message Service OVER IP, 简称 SMS
OVER IP) 架构下的短信接收流程。
[9] 3GPP定义的 SMS OVER
IP架构的示意图如图 1所示。 其中各个网络实体的功能如下:
[10] 短消息服务中心 (Short Message Service
Center, 简称 SMSC) 102, 用于负责在基站和短消息实体 (Short Message
Entity, 简称 SME) 间中继、 储存或转发短消息; 利用 SMSC到移动设备 (Mobil e
Equipment, 简称 ME) 的协议传输来自移动台或发送给移动台的短消息, SMSC 到 ME的协议为短消息传送协议 (Short Message Transmission
Protocol, 简称 SMTP)
[11] SMS网关 (SMS-Gateway
MSC, 简称 SMS-IWMSC/GMSC) 104, 用于负责接收由 SMSC发送的短消息, 向归属位置寄存器 (Home Location
Registe, 简称 HLR) 査询路由信息, 并将短消息传送给接收者所在基站的交换 中心。
[12] IP短信网关 (IP Short Message
Gateway, 简称 IP-SM-GW) 106, 用于提供 UE和 GSM/UMTS网络之间传递短信 的互通功能, 其实体可以用 IMS中的 AS来充当。
[13] 归属位置寄存器 /归属签约用户服务器 (HLR/Home Subscriber
Server, 简称 HLR/HSS) 108, 用于为短消息服务 (Short Message
Center, 简称 GMSC) 发送路由请求消息到 HLR/HSS , 若 UE先前已经通过注册登 记了 IP-SM-GW的地址, 则在路由响应消息中需要把 IP-SM-GW的 E.164格式的地 址返回给 GMSC。
[14] 移动交换中心 (Mobile Switching
Center, 简称 MSC) 110, 用于为短信从 CS域传送到 IMS域提供路由。
[15] 服务呼叫会话控制功能 (Serving-Call Session Control
Function, 简称 S-CSCF) 112, 用于完成实际的会话控制和业务提供等功能。
[16] 上述基于 IP的 SMS架构下的用户设备 (User
Equipment, 简称 UE) 的注册流程如图 2所示, 包括如下步骤:
[17] S202 , UE向 S-CSCF发起 IMS域内的正常注册 /重注册流程;
[18] S204
, S-CSCF检査触发规则, 发现 IP-SM-GW的地址, 触发第三方注册过程;
[19] S206, IP-SM-GW存储 S-CSCF的地址;
[20] S208, IP-SM-GW发起到 HSS/HLR的登记流程;
[21] S210, HSS/HLR存储 IP-SM-GW的 E.164地址信息, 向 IP-SM-GW返回响应;
[22] S212, IP-SM-GW向 S-CSCF返回响应;
[23] S214, S-CSCF向 UE返回响应。
[24] 在上述 SMS OVER
IP架构下的短信终结的处理流程如图 3所示, 包括如下步骤:
[25] S302, UE通过执行上述 IMS注册流程注册到 S-CSCF;
[26] S304 , SMSC转发 SMS消息给 SMS网关移动交换中心 (SMS-Gateway
MSC, 简称 SMS-GMSC) ;
[27] S306
, SMS-GMSC发送路由请求给 HLR/HSS , 该路由请求中包含指示 SMS-GMSC支
持 IP消息路由的标志;
[28] S308 , HSS/HLR返回用户注册吋登记的 IP-SM-GW的 E.164地址;
[29] S310, SMS-GMSC发送消息给
IP-SM-GW, 该消息中携带 UE的移动台国际 ISDN号码 (Mobile Station
International ISDN Number, 简称 MSISDN) ;
[30] S312
, 把 MSISDN转换成电话统一资源定位符 (简称 TelUrl, 其用 URL的语法来表示 传统的 E.164号码, 用于标识占用了某个电话号码的资源) , 并根据 TellM找到 相应的 S-CSCF地址;
[31] S314 , IP-SM-GW发送 SMS到 S-CSCF;
[32] S316 , S-CSCF转发 SIP MESSAGE给 UE;
[33] S318 , UE给 S-CSCF回 200 OK响应;
[34] S320 , S-CSCF发送 200 OK给 IP-SM-GW;
[35] S322 , UE通过 SIP MESSAGE发送递交报告给S-CSCF;
[36] S324 , S-CSCF根据过滤规则转发 SIP MESS AGE给 IP-SM-GW;
[37] S326 , IP-SM-GW发送递交报告给 SMS-GMSC;
[38] S328 , SMS-GMSC发送递交报告状态给 HLR/HSS;
[39] S330 , SMS-GMSC发送递交报告给 SM-SC;
[40] S332 , IP-SM-GW通过 200 OK.给 S-CSCF确认消息;
[41] S334 , S-CSCF通过 200 OK.给 UE确认消息。
[42] 二、 以下描述引入被叫侧短信中心后的网络架构下的短信发送
[43] 在 SMS OVER
IP架构上添加了被叫侧短信中心后的网络架构如图 4所示。 与图 1中所示的网络架 构相比, 图 4所示的网络架构是将图 1中所示的 SMSC由 MO-SMSC
402和 MT-SMSC
404代替。 也就是说, 分别在短信发出端和短信接受端设置了 SMSC。 其中, MO -SMSC是短信发出端的短信中心, MT-SMSC是短信接收端的短信中心。
[44] 在上述图 4所示的网络架构下短信的发送流程如下 (其中, IMS域短信的注册
流程请参见图 2所示
[45] 1、 CS域用户发送短信给 IMS域用户的流程包括如下步骤:
[46] 1 ) CS域 UE发送短信, 经过 MSC;
[47] 2
) MSC解析消息中的短信中心地址, 通过路由分析经过 SMS-IWMSC发给 MO-S
MSC;
[48] 3 ) MO-SMSC通过 HSS/HLR査询到 MT-SMSC, 发送短信给 MT-SMSC;
[49] 4 ) MT-SMSC发送短信给 SMS-GMSC;
[50] 5 ) SMS-GMSC到 HSS/HLR取被叫的路由信息;
[51] 6 ) HSS/HLR返回 IP-SM-GW的地址;
[52] 7 ) SMS-GMSC发送短信给 IP-SM-GW;
[53] 8 ) IP-SM-GW发送短信给由第三方注册吋记录的 S-CSCF;
[54] 9 ) S-CSCF路由短信到 UE。
[55] 2、 IMS域用户发送短信给 CS域用户的流程包括如下步骤:
[56] 1 ) IMS域 UE发送短信, 经过 S-CSCF到达 IP-SM-GW;
[57] 2 ) IP-SM-GW解析消息中的短信中 、地址, 通过路由分析经过 SMS-IWMSC发 给 MO-SMSC;
[58] 3 ) MO-SMSC通过 HSS/HLR査询到 MT-SMSC, 发送短信给 MT-SMSC;
[59] 4 ) MT-SMSC发送短信给 SMS-GMSC;
[60] 5 ) SMS-GMSC到 HSS/HLR取被叫的路由信息;
[61] 6 ) HSS/HLR返回被叫当前所在的 MSC的号码;
[62] 7 ) SMS - GMSC发送短信给被叫所在的 MSC;
[63] 8 ) MSC通过寻呼发送短信给被叫。
[64] TISPAN架构下的 IMS域内短信路由方式的示意图如图 5所示, 该短信路由 方式的处理流程包括以下步骤:
S502, IMS域 UE发送短信, 该短信到达 S-CSCF;
S504
S-CSCF根据过滤规则, 触发该短信到短消息应用服务功能块 (SMS-Applicatio
Sever, 简称 SMS-AS) , 进行主叫的业务控制和必要的重定向 (当被叫的地址是 封装在 o消息体内吋) 。 SMS-AS不进行短信的存储, 再把该短信发回给 S-CSCF, 如果仅考虑 TISPAN中的需求, 这一步可选;
[67] S506 ' S-CSCF进行域名服务器 (Domain Name
Server, 简称 DNS) 解析, 发现 I-CSCF的地址, 发送短信给 I-CSCF;
[68] S508 ' I-CSCF到 UPSF (即 HSS/HLR)査询, 得到被叫所在的 S-CSCF地址;
[69] I-CSCF转发短信给被叫所在的 S-CSCF;
[70] S512 ' 被叫所在的 S-CSCF根据触发规则发送短信到被叫侧的 SMS-AS;
[71] S514
, 被叫侧的 SMS-AS进行补充业务处理后, 返回短信给被叫所在的 S-CSCF;
[72] S516 , 被叫所在的 S-CSCF路由短信到 UE。
[73] 四、 把 IP-SM-GW作为 MGCF位置吋短信互通的网络架构下 IMS文本消息到 CS 域 SMS消息的互通流程。
[74] 现有技术中的另一种短信互通的网络架构的示意图如 6所示。 该架构的结构与 S
MS OVER IP架构的区别在于增加了以下网络实体功能块:
[75] 出口网关控制功能块 (Breakout Gateway Control
Function, 简称 BGCF) 602, BGCF具有出口网关控制功能, 在此架构中可以作 为短信的出口网关;
[76] 短信息媒体网关控制功能块 (SMS-Media Gateway Control
Function, 简称 SMS-MGCF) 604, SMS-MGCF具有作为 IMS域短信和 CS域短信 互通的网关的功能;
[77] 短消息应用服务功能块 (SMS-Application
Sever, 简称 SMS-AS) 606, SMS-AS具有为 SMS业务短信转换格式以及附加一 些增值业务等的功能;
[78] 互通呼叫会话控制功能块 (Inter-Call Session Control
Function, 简称 I-CSCF) 608, I-CSCF是作为归属地用于屏蔽网络结构的接入点
[79] 其中, SMS-MGCF和 SMS-AS合设组成 IP-SM-GW网络实体。
[80] 在上述图 6所示架构下, 由 IMS文本消息到 CS域 SMS消息的互通流程示意图如 图 7所示, 包括如下步骤:
[81] S702, UE根据 IMS的注册流程注册到 S-CSCF;
[82] S704, UE发送 SMS
消息到 S-CSCF, S-CSCF检査过滤规则并触发到 AS的业务;
[83] S706
, 执行完始发侧业务后, IMS核心网要决定接收者是否为 IMS用户, S-CSCF按照 IMS里的流程处理, 若 Request-URI包含了 TEL-URI, S-CSCF就到数据库中找相 应的 SIP URI。 若没有找到 SIP URI, S-CSCF转发消息到 BGCF;
[84] S708
, BGCF根据 SIP请求方法或者本身所拥有的路由特定的 TelRul的任何信息来决定 下一跳路由。 分析方法可以是公有方法 (如 DNS, ENUM (Telephone Number Mapping working group , 电话号码映射工作组) )
或私有数据库査询, 或者本地数据配置。 根据正常的 BGCF流程, 也可以路由消 息到另外一个网络的 BGCF, 可以路由到本网的适当的网关 (MGCF
或 IP-SM-GW)。 本例中路由到 IP-SM-GW;
[85] S710 , 根据接收到的 IMS
Message, IP-SM-GW检査是否有足够的信息来组建 SMS消息。 IP-SM-GW从 IMS 消息头中获得有效的发送者和接收者的信息, (如发送者可能以 TelUri的格式放 在 asserted id中);
[86] S712 , 消息接受信息由 IP-SM-GW发送给 UE。 若不能组建一个有效的 SMS 消息, 要返回适当的失败消息;
[87] S714、 716, 响应消息发送给 UE;
[88] S718 ' IP-SM-GW转发消息给 SMS-IWMSC (通过标准的 MAP信令
[89] S720 ' SMS-IWMSC转发 SMS给 SMS-IWMSC;
[90] S722, SM-SC发送递交报告给 SMS-IWMSC;
[91] S724, SMS-IWMSC发送递交报告给 IP-SM-GW。
[92] 以下的 S726到 S736只有在需要 S704中用户要求发送递交失败报告, 且递交失败 吋才发生;
[93] S726-S728, IP-SM-GW (AS)映射递交报告并且发送给 S-CSCF;
[94] S730, S-CSCF发送报告给 UE;
[95] S732 , UE确认报告;
[96] S734-S736, 确认被 S-CSCF转发给 IP-SM-GW。
[97] 此架构下的短信终结流程参见' MS OVER IP架构下的短信接收流程'。
[98] 在实现本发明的过程中, 发明人发现从以上所述的短信传送流程中, 都未考虑 在多个终端共享 IMPU的情况下, 各个终端的能力不同的情况, 从而使得某些终 端接收到其不能支持的格式的短消息。
[99] 发明内容
[100] 本发明旨在提供一种短信分叉方法及装置, 以将主叫方发出的短信转换一个或 多个被叫终端能够接收的一种或多种格式, 从而使得一个或多个被叫终端中的 每个都能收到正确格式的短信。
[101] 本发明实施例的目的是通过以下技术方案实现的:
[102] 一种短信分叉方法, 第一网络实体获取终端的能力信息或终端对应的短信格式 转换信息, 所述方法具体包括:
[103] 第一网络实体接收到需要发送给一个或多个被叫终端的短信后, 根据获取的所 述终端的能力信息或终端对应的短信格式转换信息, 将所述短信转换为所述一 个或多个被叫终端能够接收的一种或多种格式的短信。
[104] 一种短信分叉系统, 包括:
[105] 能力信息获取装置, 位于第一网络实体侧, 用于获取终端的能力信息或终端对 应的短信格式转换信息;
[106] 短信格式转换装置, 位于所述第一网络实体侧, 在接收到需要发送给一个或多 个被叫终端的短信后, 根据所述能力信息获取装置获取的终端的能力信息或终 端对应的短信格式转换信息, 将所述短信转换为所述一个或多个所述被叫终端 能够接收的一种或多种格式的短信。
[107] 本发明解决了被叫在 IMS域内有多个能力不同的终端共享 IMPU吋, 某些终端
接收不到正确格式的短信的问题, 从而提高了终端用户之间互相联系的方便性 与有效性。
[108] 附图说明
[109] 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本 发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定 。 在附图中:
[110] 图 1是示出基于 IP的 SMS架构的示意图;
[111] 图 2是示出图 1所示架构下的 UE的注册流程示意图;
[112] 图 3是示出图 1所示架构下短信终结流程示意图;
[113] 图 4是示出在 SMS OVER
IP架构上添加了被叫侧短信中心后的网络架构的示意图;
[114] 图 5是示出 TISPAN规定的 IMS域内短信路由方式的流程示意图;
[115] 图 6是示出现有短信互通的网络架构的示意图;
[116] 图 7是示出在图 6所示架构下, 由 IMS文本消息到 CS域 SMS消息的互通流程示意 图;
[117] 图 8是示出根据本发明的短信分叉方法流程图;
[118] 图 9是示出根据本发明短信分叉方法的又一流程图;
[119] 图 10是示出根据本发明的短信分叉系统的结构图;
[120] 图 11是示出根据本发明的实施例一的短信分叉方法的流程示意图;
[121] 图 12是示出根据本发明的实施例二的短信分叉方法的流程示意图;
[122] 图 13是示出根据本发明的实施例三的短信分叉方法的流程示意图;
[123] 图 14是示出根据本发明的实施例四的短信分叉方法的流程示意图;
[124] 图 15是示出根据本发明的实施例五的短信分叉方法的流程示意图;
[125] 图 16是示出根据本发明的实施例六的短信分叉方法的流程示意图; 以及
[126] 图 17是示出根据本发明的实施例七的短信分叉方法的流程示意图。
[127] 具体实施方式
[128] 下面将参考附图并结合实施例详细说明本发明。
[129] 本发明旨在提供一种短信分叉方法及装置, 以将主叫方发出的短信转换成一个
或多个被叫终端能够接收的一种或多种格式的短信, 从而使得一个或多个被叫 终端都能收到正确格式的短信。
[130] 本发明所述的短信分叉方法主要包括以下步骤:
[131] 步骤 1、 被叫侧的短信中心或相应的网络实体收到短信;
[132] 步骤 2、 上述短信中心或相应的网络实体根据被叫终端的能力信息构造对应格 式的短信, 并指示 S-CSCF将构造的短信发往该被叫终端。
[133] 其中, 在上述步骤 (2) 中, 上述短信中心或相应的网络实体在构造对应格式 的短信之前, 需要获知短信的转换类型信息。 上述短信中心或相应的网络实体 获知短信的转换类型信息的实现方法有:
[134] 方法 1、 短信中心或相应的网络实体向被叫终端所在的 S-CSCF发送订阅事件数 据包, 从被叫终端所在的 S-CSCF获得被叫终端的能力信息后, 根据该能力信息 判断得到短信的转换类型信息。
[135] 方法 2、 被叫终端所在的 S-CSCF判断用户多终端共享 IMPU, 决定要触发上述 短信中心或相应网络实体进行转换吋, 带上被叫终端需要转换的类型数量信息
[136] 方法 3、 短信中心或相应的网络实体通过其他能够感知终端能力的网络实体, 如设备管理器 (Device
Manager, 简称 DM) , 在线服务器 (Presence) 获得被叫终端的能力信息后, 根 据该能力信息判断得到短信的转换类型信息。
[137] 方法 4、 短信中心或相应的网络实体通过向 UE注册后订阅终端的能力信息, UE 向短信中心或相应的网络实体发送被叫终端的能力信息后, 根据该能力信息判 断得到短信的转换类型信息。
[138] 其中, 在上述步骤 (2) 中, 指示 S-CSCF将构造的短信发往该被叫终端的具体 实现方法有:
[139] 方法 1、 若终端注册吋带上了自己的能力信息, 则可以通过添加主叫偏好信息 来指不;
[140] 方法 2、 若通过能够感知终端能力的其他网络实体或由 UE注册后上报能力信息 来获得终端的能力信息, 那么可以通过终端标识 (其包括被叫终端注册吋的能
力信息, GRUU, 终端标识等) 来进行指示。
[141] 本发明所述的短信分叉方法的一种流程图如图 8所示。 从图 8中可知, 根据本发 明的 IMS域多终端共享 IMPU吋短信分叉方法的完整步骤包括:
[142] S802, 短信中心或类似功能实体收到短信;
[143] S804
, 短信中心或类似功能实体获知需要将上述短信转换成多少种格式类型的短信 的信息;
[144] S806
, 短信中心或类似功能实体将上述短信进行格式转换, 并在转换后的短信中添 加被叫终端的指示信息;
[145] S808
, 根据上述被叫终端的指示信息, 将上述转换后的短信分发给对应的被叫终端
[146] 其中, 短信中心或类似功能实体在不同的网络架构中对应不同的网络实体。 在 现有技术一和现有技术二中, IP-SM-GW充当了这样的角色, 而在现有技术三和 现有技术四中, 由 SMS-AS实现这样的功能。
[147] 根据本发明所述的短信分叉方法的另一种流程图如图 9所示, 包括以下步骤:
[148] S902
, 第一网络实体通过网络内的其他网络实体获取一个或多个终端的能力信息或 从呼叫控制功能实体获取短信格式转换信息;
[149] S904
, 第一网络实体接收到将要发送的短信后, 根据获取的能力信息或短信格式转 换信息, 将该短信转换为一个或多个被叫终端能够接收的一种或多种格式的短 信;
[150] S906
, 第一网络实体将被叫终端对应的终端指示信息添加到转换后的短信中后, 将 短信发送至被叫终端所在的呼叫控制功能实体;
[151] S908
, 上述呼叫控制功能实体根据终端指示信息将转换后的短信发送给相应的被叫 终端。
[152] 在上述的短信分叉方法中, 第一网络实体包括 IP短信网关和短消息服务应用服 务器中的至少一个。 其他网络功能实体包括呼叫控制功能实体、 注册后的用户 设备、 和能够感知终端能力的网络实体中的至少之一。 能够感知终端能力的网 络实体包括设备管理器和在线服务器中的至少之一。
[153] 在上述的短信分叉方法中, 在步骤 S902中, 第一网络实体可以向呼叫控制功能 实体或注册后的用户设备订阅一个或多个被叫终端的能力信息。
[154] 在上述的短信分叉方法中, 在步骤 S902中, 第一网络功能实体可以从能够感知 终端能力的网络实体中获取一个或多个被叫终端的能力信息。
[155] 在上述的短信分叉方法中, 在步骤 S902中, 呼叫控制功能实体接收到将要发送 的短信后, 判断一个或多个被叫终端是否共享 IP多媒体公有标识, 如果是, 则呼 叫控制功能实体将上述短信和对应的短信格式转换信息发送至第一网络实体。
[156] 在上述的短信分叉方法中, 短信被转换为 SMS格式和文本格式中的至少一种。
[157] 本发明所述的短信分叉系统结构图如图 10所示, 包括如下模块:
[158] 能力信息获取装置 1002, 位于第一网络实体侧, 通过网络内的其他网络实体获 取一个或多个终端的能力信息或从呼叫控制功能实体获取短信格式转换信息; [159] 短信格式转换装置 1004, 位于第一网络实体侧, 在接收到将要发送的短信后, 根据能力信息获取装置获取的能力信息或短信格式转换信息, 将上述短信转换 为一个或多个被叫终端能够接收的一种或多种格式的短信;
[160] 短信分叉装置 1006, 位于第一网络实体侧, 将被叫终端对应的终端指示信息添 加到转换后的短信中后, 将短信分别发送至一个或多个被叫终端所在的呼叫控 制功能实体;
[161] 以及短信发送装置 1008, 位于呼叫控制功能实体侧, 根据上述终端指示信息将 来自短信分叉装置的短信发送给被叫终端。
[162] 在上述的短信分叉系统中, 第一网络实体包括 IP短信网关和短消息服务应用服 务器中的至少一个。
[163] 在上述的短信分叉系统中, 其他网络功能实体包括呼叫控制功能实体、 注册后
的用户设备、 和能够感知终端能力的网络实体中的至少之一。 能够感知终端能 力的网络实体包括设备管理器和在线服务器中的至少之一。
[164] 在上述的短信分叉系统中, 能力信息获取装置可以向呼叫控制功能实体或注册 后的用户设备订阅一个或多个被叫终端的能力信息。
[165] 在上述的短信分叉系统中, 能力信息获取装置可以从能够感知终端能力的网络 实体中获取所述一个或多个被叫终端的能力信息。
[166] 在上述的短信分叉系统中, 位于第一网络实体侧的能力信息获取装置接收来自 呼叫控制功能实体的短信格式转换信息, 其中, 在呼叫控制功能实体接收到将 要发送的短信后, 判断一个或多个被叫终端是否共享 IP多媒体公有标识, 如果是
, 则将短信和短信格式转换信息发送至第一网络实体。
[167] 在上述的短信分叉系统中, 短信被转换为 SMS格式和文本格式中的至少一种。
[168] 实施例一
[169] 本发明所述的实施例一的短信分叉方法的流程示意图如图 11所示。 在该实施例 中, 短信中心或相应的网络实体向被叫终端所在的 S-CSCF进行订阅, 获得终端 能力信息。 其中短信应用服务功能块 (Short Message Service— Application Service, 简称 SMS-AS)为 IMS域的被叫短信中心或相应网络实体。 本实施例中省 略了 P-CSCF和 I-CSCF的相关流程。 其处理流程包括以下步骤:
[170] S1102 -S1108 , 同正常的短信注册流程步骤。
[171] S1110 -S1112, SMS-AS向 S-CSCF发起订阅, S-CSCF向 SMS-AS返回响应。
[172] S1114
-S1116, S-CSCF向 SMS-AS发 NOTIFY消息, 通知 SMS-AS各个终端的能力信息 , SMS-AS向 S-CSCF返回响应。
[173] 实施例二
[174] 本发明所述的实施例二的短信分叉方法的流程示意图如图 12所示。 在该实施例 中, 被叫终端的 S-CSCF判断用户多终端共享 IMPU, 决定要触发短信中心或相应 网络实体进行转换吋, 将终端的转换类型信息通知给短信中心或相应网络实体 。 其处理流程包括以下步骤:
[175] S1202, S-CSCF收到短信。
[176] S1204
, 被叫终端的 S-CSCF判断用户多终端共享 IMPU, 决定要触发短信中心或相应网 络实体进行转换, S-CSCF判断各个终端的能力信息得出需要转换成多少种类型 的短信, 把此转换类型信息添加到消息中;
[177] S1206, S-CSCF把添加了转换类型信息的消息发送给 SMS-AS;
[178] S1208, SMS-AS给 S-CSCF返回响应消息。
[179] 实施例三
[180] 根据本发明所述的实施例三的短信分叉方法的流程示意图如图 13所示。 在该实 施例中, 通过其他网络实体得到终端的能力后进行判断得到转换类型信息。 其 处理流程包括以下步骤:
[181] S1302, SMS-AS向 DM/Prersence等其他网络实体订阅终端的能力信息;
[182] S1304, DM/Prersence等其他网络实体通过短信通知 SMS-AS终端的能力信息;
[183] S1306, SMS-AS收到上述短信;
[184] S1308
, SMS-AS根据用户终端的能力信息来判断需要转换的短信的类型信息。
[185] 实施例四
[186] 本发明所述的实施例四的短信分叉方法的流程示意图如图 14所示。 该实施例是 在现有的 SMS IP
OVER架构下, 从 CS域到 IMS域的共享 IMPU的多个终端的短信流程中收到 CS域 来的短信后的流程处理。 其中, 假设 UE1和 UE2共享一个 IMPU, UE1只支持封 装 SMS格式的短信, 而 UE2只支持文本格式的短信。 其处理流程包括以下步骤: [187] S1402
, UE通过 IMS注册流程注册到 S-CSCF, 且执行了短信注册流程和终端能力的订 阅, 其中终端能力的订阅过程可场景实施例一;
[188] S1404, UE发送短信给 MSC;
[189] S1406, MSC转发短信给 SMS-IWMSC;
[190] S1408, SMS-IWMSC转发短信给 SM-SC;
[191] S1410, SM-SC转发 SMS消息给 SMS-GMSC;
[192] S1412
, SMS-GMSC发送路由请求给 HLR/HSS , 其中包含指示标志, 该指示标志表明 S
MS-GMSC支持 IP消息路由;
[193] S1414 , HSS/HLR返回用户注册吋登记的 IP-Message-GW的 E.164地址;
[194] S1416, SMS-GMSC发送短信给 IP-SM-GW,其中携带 UE的 MSISDN;
[195] S1418
, IP-SM-GW把上述 MSISDN转换成 TelUrl, 并获得所需要转换成两种格式类型 的短信信息, 把原来的短信分叉为封装 SMS格式和文本格式的两条短信并分别 添加对应的终端指示, 同吋根据 TelUrl找到相应的 S-CSCF地址;
[196] S1420, IP-SM-GW分别发送封装 SMS格式和文本格式短信到 S-CSCF;
[197] S1422, S-CSCF分别回响应给 IP-Message-GW;
[198] S1424
, S-CSCF根据短信中携带的终端指示分别把相应格式的短信发送到具有相应能 力的终端上;
[199] S1426, UE分别返回响应给 S-CSCF。
[200] 实施例五
[201] 本发明所述的实施例五的短信分叉方法的示意图如图 15所示。 该实施例是在引 入了被叫侧短信中心架构下, 从 CS域到 IMS域的共享 IMPU的多个终端的短信流 程中收到 CS域来的短信后的流程处理。 其中, 假设 UE1和 UE2共享一个 IMPU, UE1只支持封装 SMS格式的短信, 而 UE2只支持文本格式的短信。 其处理流程包 括以下步骤:
[202] S1502
, UE通过 IMS注册流程注册到 S-CSCF, 且执行了短信注册流程和终端能力的订 阅, 其中终端能力的订阅过程可场景实施例一;
[203] S1504 , UE发送短信给 MSC;
[204] S1506, MSC转发短信给 MO-SMSC;
[205] S1508 , MO-SMSC到 HSS/HLR取得 MT-SMSC的地址;
[206] S1510, MO-SMSC转发 SMS消息给 MT-SMSC;
[207] S1512
, MT-SMSC发送路由请求给 HLR/HSS, 其中包含指示标志支持 IP消息路由; [208] S1514, HSS/HLR返回用户注册吋登记的 IP-SM-GW的 E.164地址;
[209] S1516, MT-SMSC发送消息给 IP-SM-GW,其中携带 UE的 MSISDN;
[210] S1518
, IP-SM-GW把 MSISDN转换成 TelUrl, 并获得所需要转换成两种格式类型的短 信信息。 把原来的短信分叉为封装 SMS格式和文本格式的两条短信并分别添加 对应的终端指示, 同吋根据 TelUrl找到相应的 S-CSCF地址;
[211] S1520 , IP-SM-GW分别发送 SMS到 S-CSCF;
[212] S1522, S-CSCF分别回响应给 IP-Message-GW;
[213] SI 524
, S-CSCF根据短信中携带的终端指示, 分别把相应格式的短信发送到对应终端
[214] S1526, UE分别返回响应给 S-CSCF。
[215] 实施例六
[216] 本发明所述的实施例六的短信分叉方法的示意图如图 16所示。 该实施例是在 IP- SMS-GW处于 MGCF位置架构下, 从 CS域到 IMS域的共享 IMPU的多个终端的短 信流程中收到 CS域来的短信后的流程处理。 其中, 假设 UE1和 UE2共享一个 IMP U, UE1只支持封装 SMS格式的短信, 而 UE2只支持文本格式的短信。 其处理流 程包括以下步骤:
[217] S1602-S1604, SMSC发送短信给 SMS-GMSC;
[218] S1606-S1608, SMSC-GMSC到 HSS/HLR取得 SMS-MGCF的地址;
[219] S1610-S1612, SMSC-GMSC发送短信给 SMS-MGCF, SMS-MGCF返回响应;
[220] S1614-S1616, SMS-MGCF路由短信到 I-CSCF;
[221] S 1618-S1620 , I-CSCF到 HSS/HLR取被叫的 S-CSCF地址;
[222] S1622-S1624 , I-CSCF发送短信给被叫的 S-CSCF;
[223] S1626-S1628
, S-CSCF判断被叫用户是多个终端共享 IMPU的情况, 触发 SMS-AS进行转换和
Forking处理;
[224] S1630-S1632
, SMS- AS根据 S-CSCF带上的信息或通过自身的判断得知需要转换成两种不同格 式类型的短信, 把消息转换成封装 SMS格式和文本格式并且分别添加对应的终 端指示后, 将消息发给 S-CSCF; ;
[225] S 1634-S1636
, S-CSCF根据终端指示选择合适的消息格式发送给不同的终端。
[226] 实施例七
[227] 本发明所述的实施例七的短信分叉方法的流程示意图如图 17所示。 该实施例是 在 TISPAN架构下, 从 IMS域到 IMS域的共享 IMPU的多个终端的短信流程中在收 到 IMS域来的短信后的流程处理。 其中, 假设 UE1和 UE2共享一个 IMPU, UE1只 支持封装 SMS格式的短信, 而 UE2只支持文本格式的短信。 其处理流程包括以下 步骤:
[228] S1702-S1704
, S-CSCF收到 UE来的短信, 其中短信可能是文本格式, 也可能是封装 SMS格式
[229] S1706-S1708
, S-CSCF根据触发规则判断是否需要到主叫的 SMS-AS进行消息的转换和主叫补 充业务的处理, 这里假设需要到 SMS-AS处理;
[230] S1710-S1712
, SMS-AS对消息进行转换或处理主叫的补充业务后, 把短信发回给 S-CSCF;
[231] S1714-S1716, S-CSCF把短信发送给 I-CSCF;
[232] S1718-S1720, I-CSCF到 HSS/HLR取得被叫所在的 S-CSCF的地址;
[233] S1722-S1724, I-CSCF把消息发送给被叫所在的 S-CSCF;
[234] S 1726- 1728
, S-CSCF对被叫进行判断, 发现被叫有多个终端共享 IMPU, 则触发被叫侧的短 信中心进行格式转换和 Forking处理;
[235] S1730-S1732
, SMS- AS根据 S-CSCF带上的信息或通过自身的判断得知需要转换成两种不同格 式类型的短信, 把消息转换成封装 SMS格式和文本格式并且分别添加对应的终 端指示后, 将消息分别发送给 S-CSCF;
[236] S1734-S1736
, S-CSCF根据短信中携带的终端指示, 分别把相应格式的短信发送到具有相应 能力的终端上。
[237] 以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围并不局限于 此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到 的变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保护范围 应该以权利要求的保护范围为准。
Claims
[1] 1、 一种短信分叉方法, 其特征在于, 第一网络实体获取终端的能力信息或 终端对应的短信格式转换信息, 所述方法具体包括:
第一网络实体接收到需要发送给一个或多个被叫终端的短信后, 根据获取 的所述终端的能力信息或终端对应的短信格式转换信息, 将所述短信转换 为所述一个或多个被叫终端能够接收的一种或多种格式的短信。
[2] 2、 根据权利要求 1所述的短信分叉方法, 其特征在于, 所述方法还包括: 所述第一网络实体将对应于所述一个或多个被叫终端的终端指示信息添加 到转换后的所述短信中后, 将所述短信发送给所述被叫终端所在的呼叫控 制功能实体;
所述呼叫控制功能实体根据所述短信中携带的终端指示信息, 将转换后的 所述短信发送给能够接收对应格式短信的所述被叫终端。
[3] 3、 根据权利要求 1所述的短信分叉方法, 其特征在于, 所述一个或多个被 叫终端共享 IP多媒体公有标识。
[4] 4、 根据权利要求 1所述的短信分叉方法, 其特征在于, 所述第一网络实体 包括 IP短信网关和短消息服务应用服务器中的至少一项。
[5] 5、 根据权利要求 1至 4任意一项所述的短信分叉方法, 其特征在于, 所述第 一网络实体获取终端的能力信息或终端对应的短信格式转换信息的过程, 具体包括:
所述第一网络实体从其他网络实体获取终端的能力信息或终端对应的短信 格式转换信息, 所述其他网络功能实体包括呼叫控制功能实体、 注册后的 用户设备和能够感知终端能力的网络实体中的至少一项。
[6] 6、 根据权利要求 5所述的短信分叉方法, 其特征在于, 所述能够感知终端 能力的网络实体包括设备管理器和在线服务器中的至少一项。
[7] 7、 根据权利要求 5所述的短信分叉方法, 其特征在于, 所述第一网络实体 从其他网络实体获取终端的能力信息或终端对应的短信格式转换信息的过 程, 具体包括:
所述第一网络实体向所述呼叫控制功能实体、 注册后的用户设备和能够感
知终端能力的网络实体中的至少一项订阅所述一个或多个被叫终端的能力 信息或终端对应的短信格式转换信息。
[8] 8、 根据权利要求 5所述的短信分叉方法, 其特征在于, 所述第一网络实体 从其他网络实体获取终端的能力信息或终端对应的短信格式转换信息的过 程, 具体包括:
所述呼叫控制功能实体接收到需要发送给一个或多个被叫终端的短信后, 当判断所述一个或多个被叫终端共享 IP多媒体公有标识后, 将所述短信和 所述一个或多个被叫终端对应的短信格式转换信息发送给所述第一网络实 体。
[9] 9、 根据权利要求 1至 4任一项中任意一项所述的短信分叉方法, 其特征在于
, 所述短信被转换为 SMS格式和文本格式中的至少一项。
[10] 10、 一种短信分叉系统, 其特征在于, 包括:
能力信息获取装置, 位于第一网络实体侧, 用于获取终端的能力信息或终 端对应的短信格式转换信息;
短信格式转换装置, 位于所述第一网络实体侧, 在接收到需要发送给一个 或多个被叫终端的短信后, 根据所述能力信息获取装置获取的终端的能力 信息或终端对应的短信格式转换信息, 将所述短信转换为所述一个或多个 所述被叫终端能够接收的一种或多种格式的短信。
[11] 11、 根据权利要求 10所述的短信分叉系统, 其特征在于, 所述短信分叉系 统还包括:
指示信息添加模块, 位于所述第一网络实体侧, 用于将对应于所述一个或 多个被叫终端的终端指示信息添加到所述短信格式转换装置转换后的所述 短信中后, 将所述短信发送给所述短信发送装置;
短信发送装置, 位于呼叫控制功能实体侧, 用于根据所述指示信息添加模 块发送过来的短信中携带的终端指示信息, 将所述短信发送给能够接收对 应格式短信的所述被叫终端。
[12] 12、 根据权利要求 10所述的短信分叉系统, 其特征在于, 所述第一网络实 体包括 IP短信网关和短消息服务应用服务器中的至少一项。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2006101039502A CN101115224B (zh) | 2006-07-28 | 2006-07-28 | 用于ims网络的短信分叉方法及系统 |
CN200610103950.2 | 2006-07-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008014718A1 true WO2008014718A1 (fr) | 2008-02-07 |
Family
ID=38996891
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070363 WO2008014718A1 (fr) | 2006-07-28 | 2007-07-26 | Procédé et système de partage dynamique de messages courts dans un réseau de sous-systèmes multimédia ip |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101115224B (zh) |
WO (1) | WO2008014718A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102014345B (zh) * | 2009-09-08 | 2014-12-10 | 中国移动通信集团公司 | 一种消息转换方法、系统和设备 |
CN103079175B (zh) * | 2011-10-26 | 2019-08-30 | 中兴通讯股份有限公司 | 一种跨业务系统的媒体消息发送方法及系统 |
CN103139171B (zh) * | 2011-11-30 | 2015-07-01 | 中国联合网络通信集团有限公司 | 媒体交换网络系统 |
US9674677B2 (en) * | 2012-07-25 | 2017-06-06 | Hewlett-Packard Development Company, L.P. | Message routing using a home gateway |
CN103457848B (zh) * | 2013-08-15 | 2016-08-24 | 中国联合网络通信集团有限公司 | 呼叫路由方法、装置及系统 |
WO2016176862A1 (zh) * | 2015-05-07 | 2016-11-10 | 华为技术有限公司 | 一种业务处理方法及用户设备 |
CN106792585B (zh) * | 2015-11-19 | 2021-04-30 | 中兴通讯股份有限公司 | 一种短消息传输方法和装置、及系统 |
CN107086951B (zh) * | 2017-04-05 | 2019-12-03 | 中国联合网络通信集团有限公司 | 行业短信的传输方法、短信网关及行业短信接入网关 |
CN113453172B (zh) * | 2020-03-24 | 2022-10-04 | 中国移动通信有限公司研究院 | 短消息的传输方法、装置及设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003097641A2 (en) * | 2002-05-21 | 2003-11-27 | Novartis Ag | 1h-imidazo[4,5-c] quinoline derivatives in the treatment of protein kinase dependent diseases |
CN1482819A (zh) * | 2002-09-12 | 2004-03-17 | 深圳市中兴通讯股份有限公司 | 兼容多种编码格式的phs短消息的方法 |
CN1774009A (zh) * | 2004-11-09 | 2006-05-17 | 日本电气株式会社 | 数据通信终端装置、数据通信系统以及讯息类别控制方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5920822A (en) * | 1996-01-18 | 1999-07-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Formatting of short message service messages in a cellular telephone network |
US7200680B2 (en) * | 2002-03-11 | 2007-04-03 | Ericsson Inc. | Method, apparatus and system for providing multimedia messages to incompatible terminals |
KR100408357B1 (en) * | 2003-01-29 | 2003-12-03 | Hinet Advanced Technology & In | Multimedia messaging service method |
-
2006
- 2006-07-28 CN CN2006101039502A patent/CN101115224B/zh not_active Expired - Fee Related
-
2007
- 2007-07-26 WO PCT/CN2007/070363 patent/WO2008014718A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003097641A2 (en) * | 2002-05-21 | 2003-11-27 | Novartis Ag | 1h-imidazo[4,5-c] quinoline derivatives in the treatment of protein kinase dependent diseases |
CN1482819A (zh) * | 2002-09-12 | 2004-03-17 | 深圳市中兴通讯股份有限公司 | 兼容多种编码格式的phs短消息的方法 |
CN1774009A (zh) * | 2004-11-09 | 2006-05-17 | 日本电气株式会社 | 数据通信终端装置、数据通信系统以及讯息类别控制方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101115224A (zh) | 2008-01-30 |
CN101115224B (zh) | 2010-06-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8184621B2 (en) | Apparatus, system and method for short message routing control | |
JP5080465B2 (ja) | メッセージを変換するための方法及びシステム | |
EP2028815A1 (en) | The method and system for delivering the message service data | |
WO2008014718A1 (fr) | Procédé et système de partage dynamique de messages courts dans un réseau de sous-systèmes multimédia ip | |
US20090075684A1 (en) | Apparatus and method for routing message service | |
EP2016780B1 (en) | Method, short message service center and system for delivery of short message service messages | |
US8499082B2 (en) | Methods, systems, and computer readable media for providing services in a telecommunications network using interoperability specification/session initiation protocol (IOS/SIP) adapter | |
US20100087215A1 (en) | Method, system, and message service interworking module for implementing message service interworking | |
JP2008541617A (ja) | Imsでの付加サービス要求のショート・メッセージ・サービス・カプセル化 | |
US20080125123A1 (en) | Method and system for to enable communication for a wireless device having a plurality of identifiers | |
KR20120039321A (ko) | 회선 교환 망과 인터넷 프로토콜 멀티미디어 서브시스템 망간 로밍 서비스 제공 방법 및 시스템과 그 장치 | |
KR101134835B1 (ko) | Ip 네트워크를 통해 sms 메시지 전달을 지원하는 기기 및 관련 방법 | |
EP1972100A1 (en) | Mobile communications method and system for signalling information relating to network's capabilities | |
JP2009520434A (ja) | ユーザ機器へのデータメッセージの伝送を外部ゲートウェイにより制御するための機構 | |
JP2007534212A (ja) | 電気通信システム | |
WO2007128221A1 (fr) | Procédé et système d'acheminement et d'adressage de message court | |
CN105682058B (zh) | 一种路由短消息的方法及装置 | |
EP2712218B1 (en) | Short message processing method and related system | |
US8335485B2 (en) | Call routing | |
CN101272544B (zh) | 一种实现短消息和即时消息融合的方法及系统 | |
WO2008017235A1 (fr) | Système, périphérique et procédé de routage sms | |
WO2011140882A1 (zh) | 紧急短消息的实现方法和系统 | |
WO2011143985A1 (zh) | 紧急消息的实现方法、装置及系统 | |
JP2009535880A (ja) | アプリケーションサーバが発信する要求のためのs−cscf選択 | |
US20240224003A1 (en) | Utilizing ipsm gateway for delivery unification and domain selection |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07764285 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07764285 Country of ref document: EP Kind code of ref document: A1 |