WO2013023501A1 - 一种系统间短消息投递终止后发起释放的方法及设备 - Google Patents

一种系统间短消息投递终止后发起释放的方法及设备 Download PDF

Info

Publication number
WO2013023501A1
WO2013023501A1 PCT/CN2012/078198 CN2012078198W WO2013023501A1 WO 2013023501 A1 WO2013023501 A1 WO 2013023501A1 CN 2012078198 W CN2012078198 W CN 2012078198W WO 2013023501 A1 WO2013023501 A1 WO 2013023501A1
Authority
WO
WIPO (PCT)
Prior art keywords
short message
msc
inter
message delivery
system short
Prior art date
Application number
PCT/CN2012/078198
Other languages
English (en)
French (fr)
Inventor
孙猛
曹小飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013023501A1 publication Critical patent/WO2013023501A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present invention relates to a code division multiple access (CDMA) communication system, and more particularly to a method and apparatus for initiating release after a short message delivery between systems is terminated.
  • CDMA code division multiple access
  • the delayed registration mechanism is automatically enabled when the mobile station moves from one registration area to another.
  • this may cause the location registration to be initiated immediately when the mobile station roams across the location area, thereby causing the paging failure of the mobile station as a called party or increasing the paging duration; wherein the foregoing problem is to expand the range paging.
  • MSCs mobile switching centers
  • the serving MSC receives a short message center-to-point delivery (SMDPP) request message from a short message center (SMC);
  • SMSPP short message center-to-point delivery
  • SMC short message center
  • the serving MSC finds that the location area where the mobile station was last registered is in a border overlapping area between the serving MSC and the neighboring MSC, and the serving MSC sends an inter-system paging (ISPAGE2) request message to the neighboring MSC, and the inter-system paging request is sent.
  • ISPAGE2 inter-system paging
  • CDMASO service option parameter carried in the message is indicated as a short message service (SMS);
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC, that is, sends a paging request message to the mobile station;
  • the mobile station responds to the paging in the neighboring MSC, and the neighboring MSC receives the paging response message.
  • the neighboring MSC instructs the base station to establish a traffic channel, and the service channel is successfully established, and the process is also a service channel assignment;
  • the neighboring MSC returns an inter-system paging response message to the serving MSC, where the inter-system paging response message carries an authentication parameter (AuthParameters);
  • the serving MSC After receiving the inter-system paging response message, the serving MSC authenticates the mobile station according to the authentication parameter in the received inter-system paging response message, and the authentication succeeds;
  • the serving MSC sends an inter-system short message point-to-point delivery (ISSMDPP) request message to the neighboring MSC;
  • ISSMDPP inter-system short message point-to-point delivery
  • the neighboring MSC uses the established service channel to perform short message delivery;
  • the neighboring MSC receives a short message delivery response from the base station
  • the adjacent MSC releases the service channel.
  • the neighboring MSC returns an inter-system short message point-to-point delivery response message to the serving MSC.
  • the MSC After receiving the inter-system short message peer-to-peer delivery response message, the MSC returns a short message point-to-point delivery response message to the short message center.
  • the process of inter-system short message delivery through the newly created service channel is characterized in that: the neighboring MSC receives the inter-system paging request message of the serving MSC, and is established.
  • the service channel returns the inter-system paging response message to the serving MSC, and then waits for the inter-system short message point-to-point delivery request message of the serving MSC to send the short message to the mobile station.
  • the main object of the present invention is to provide a method and device for initiating release after termination of short message delivery between systems, when the serving MSC or the neighboring MSC decides to terminate the inter-system short message.
  • the serving MSC or the neighboring MSC decides to terminate the inter-system short message.
  • the neighboring MSC decides to terminate the inter-system short message.
  • When delivering immediately notify the other party to terminate the inter-system short message delivery process.
  • a method for initiating release after termination of short message delivery between systems including:
  • the serving MSC or the neighboring MSC terminates the inter-system short message delivery, and notifies the opposite MSC to terminate the inter-system short message delivery.
  • the serving MSC terminates the inter-system short message delivery and notifies the adjacent MSC to terminate the short message delivery between the systems.
  • the serving MSC terminates the inter-system short message delivery and notifies the neighboring MSC to terminate the inter-system short message delivery.
  • the serving MSC terminates the inter-system short message delivery and notifies the adjacent MSC to terminate the inter-system short message delivery.
  • the serving MSC terminates the inter-system short message delivery and notifies the adjacent MSC to terminate the inter-system short message delivery.
  • the neighboring MSC receives the release request sent by the base station, the neighboring MSC terminates the inter-system short message delivery, and notifies the serving MSC to terminate the inter-system short message delivery.
  • the neighboring MSC terminates the inter-system short message delivery, and notifies the serving MSC to terminate the inter-system short message delivery.
  • the processing of interest delivery includes:
  • the serving MSC or the neighboring MSC sends a release request message to the opposite end.
  • the method further includes:
  • the inter-system short message delivery is terminated.
  • a device for initiating release after termination of inter-system short message delivery the device is set as: in the process of inter-system short message delivery, in the case that the inter-system short message delivery needs to be terminated, the inter-system short message delivery is terminated, and the notification is The end device terminates the inter-system short message delivery.
  • the device is a serving MSC, and the peer device is an adjacent MSC;
  • the serving MSC is configured to: terminate the inter-system short message delivery when the serving MSC local paging succeeds, or the serving MSC fails to authenticate the mobile station, or the serving MSC cancels the mobile station registration, or the service MSC fails to deliver multiple short messages. And notify the neighboring MSC to terminate the inter-system short message delivery.
  • the device is a neighboring MSC
  • the peer device is a serving MSC.
  • the neighboring MSC is configured to: when the neighboring MSC receives the release request sent by the base station, or fails to deliver multiple short messages of the adjacent MSC, The inter-system short message delivery is terminated, and the service MSC is notified to terminate the inter-system short message delivery.
  • the serving MSC or the neighboring MSC terminates the inter-system short message delivery, and immediately informs the opposite MSC to terminate the inter-system short message delivery, so that the opposite MSC can Release air and system resources in a timely manner to reduce waste of air resources and system resources.
  • 2 is a first embodiment of the present invention, in the process of short message delivery between systems, serving the MSC locally Flowchart of immediate release when paging is successful;
  • FIG. 3 is a flowchart of an immediate release when a serving MSC fails to authenticate a mobile station in a short message delivery process between systems according to a second embodiment of the present invention
  • FIG. 4 is a flowchart of an immediate release when a serving MSC cancels a mobile station registration in a short message delivery process between systems according to a third embodiment of the present invention
  • FIG. 5 is a flowchart of an immediate release when a service MSC fails to deliver multiple short messages in a short message delivery process between systems according to a fourth embodiment of the present invention
  • FIG. 6 is a flowchart of an immediate release when a neighboring MSC receives a release request sent by a base station in a short message delivery process between systems according to a fifth embodiment of the present invention
  • FIG. 7 is a flowchart of an immediate release when a plurality of short message delivery failures of an adjacent MSC fails in the inter-system short message delivery process according to the sixth embodiment of the present invention. detailed description
  • the serving MSC or the neighboring MSC terminates the inter-system short message delivery, and immediately sends a release request message to the opposite MSC to notify the opposite MSC. Termination of inter-system short message delivery can reduce the waste of air resources and system resources.
  • the application scenario shown in the figure is: During the inter-system short message delivery process, the service MSC initiates an immediate release when the local paging succeeds.
  • the monthly service MSC receives the short message point-to-point delivery (for example: SMDPP) request message of the short message center;
  • SMDPP short message point-to-point delivery
  • the serving MSC initiates local paging to the mobile station according to the location area where the mobile station was last registered; 203.
  • the serving MSC finds that the location area where the mobile station is most recently registered is in a border overlapping area between the serving MSC and the neighboring MSC, and the serving MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC.
  • ISPAGE2 inter-system paging
  • the service option parameter (CDMASO) carried in the call request message is indicated as a short message service (SMS);
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC;
  • the serving MSC waits for a paging response between the systems, and the mobile station responds to the paging at the serving MSC, and the serving MSC receives the local paging response.
  • the serving MSC decides to terminate the inter-system short message delivery, and then sends a release (eg, DROPSERVICE) request message to the neighboring MSC, where the release request message carries an identifier of the mobile station, such as an International Mobile Subscriber Identity (IMSI) or a mobile identification number. (MIN);
  • IMSI International Mobile Subscriber Identity
  • MIN mobile identification number.
  • the monthly MSC receives the local paging response indicating that: the mobile station is under the coverage of the serving MSC, so the serving MSC does not need to send short messages through the neighboring MSC, and can directly deliver the short message, therefore,
  • the serving MSC decides to terminate the inter-system short message delivery; 207.
  • the neighboring MSC After receiving the release request message, the neighboring MSC immediately terminates the inter-system short message delivery of the MSC, and returns an inter-system paging response message to the serving MSC, and an inter-system paging response message. Carrying a failure cause value;
  • the neighboring MSC returns a release response message to the serving MSC.
  • the monthly service MSC returns a short message point-to-point delivery response message to the short message center, and ends the processing.
  • the application scenario shown in Figure 3 is: During the inter-system short message delivery process, the serving MSC initiates an immediate release when the mobile station fails to authenticate.
  • the monthly service MSC receives the short message point-to-point delivery of the short message center (for example: SMDPP) request message;
  • the serving MSC finds that the location area where the mobile station is most recently registered is in the boundary overlapping area between the serving MSC and the neighboring MSC, and the serving MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC, and the system searches for The service option parameter carried in the call request message is indicated as a short message service;
  • ISPAGE2 inter-system paging
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC;
  • the mobile station responds to the paging in the adjacent MSC;
  • the neighboring MSC instructs the base station to establish a service channel, and the service channel is successfully established.
  • the neighboring MSC returns an inter-system paging response message to the serving MSC, where the inter-system paging response message carries an authentication parameter (AuthParameters);
  • the serving MSC After receiving the inter-system paging response message, the serving MSC authenticates the mobile station according to the authentication parameter in the received inter-system paging response message, but the authentication fails.
  • the serving MSC determines to terminate the inter-system short message delivery, and then sends a release (eg, DROPSERVICE) request message to the neighboring MSC, where the release request message carries the identifier of the mobile station, such as IMSI or MIN;
  • a release eg, DROPSERVICE
  • the reason for the failure of authentication may be that the mobile station is an illegal user, so the serving MSC should stop providing services to the illegal mobile station;
  • the neighboring MSC After receiving the release request message, the neighboring MSC immediately terminates the inter-system short message delivery of the MSC, and releases the service channel.
  • the neighboring MSC returns a release response message to the serving MSC.
  • the monthly service MSC returns a short message point-to-point delivery response message to the short message center, and ends the processing.
  • the application scenario shown in Figure 4 is: During the inter-system short message delivery process, the serving MSC An immediate release is initiated when the mobile station registration is cancelled.
  • the monthly service MSC receives the short message point-to-point delivery (for example: SMDPP) request message of the short message center;
  • SMDPP short message point-to-point delivery
  • the service MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC, and the service option parameter carried in the inter-system paging request message is indicated as a short message service;
  • ISPAGE2 inter-system paging
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC;
  • the serving MSC receives a registration cancellation (eg, REGCAN) request message sent by a home location register (HLR), requesting cancellation of the mobile station registration;
  • a registration cancellation eg, REGCAN
  • HLR home location register
  • the HLR requires the service MSC to cancel the registration of the mobile station
  • the service MSC cancels the mobile station registration, and returns a registration cancellation response to the HLR.
  • the serving MSC determines to terminate the inter-system short message delivery, and then sends a release (eg, DROPSERVICE) request message to the neighboring MSC, where the release request message carries the identifier of the mobile station, such as IMSI or MIN;
  • a release eg, DROPSERVICE
  • the service MSC cancels the mobile station registration to indicate that the service MSC does not need to provide the mobile station with monthly services, and therefore decides to terminate the inter-system short message delivery;
  • the neighboring MSC After receiving the release request message, the neighboring MSC immediately terminates the inter-system short message delivery of the MSC, and returns an inter-system paging response message to the serving MSC, where the inter-system paging response message carries a failure cause value.
  • the neighboring MSC returns a release response message to the serving MSC. 409.
  • the monthly service MSC returns a short message point-to-point delivery response message to the short message center, and ends the processing.
  • the application scenario shown in Figure 5 is: During the inter-system short message delivery process, the service MSC initiates immediate release when multiple short message delivery fails.
  • the monthly service MSC receives the short message point-to-point delivery (for example: SMDPP) request message of the short message center, and the parameter SMSMSGCOUNT value carried in the short message point-to-point delivery request message is greater than 0;
  • SMDPP short message point-to-point delivery
  • the service MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC, and the service option parameter carried in the inter-system paging request message is indicated as a short message service;
  • ISPAGE2 inter-system paging
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC;
  • the mobile station responds to the paging in the adjacent MSC.
  • the neighboring MSC instructs the base station to establish a traffic channel, and the service channel is successfully established.
  • the neighboring MSC returns an inter-system paging response message to the serving MSC, where the inter-system paging response message carries an authentication parameter.
  • the serving MSC After receiving the inter-system paging response message, the serving MSC authenticates the mobile station according to the authentication parameter in the received inter-system paging response message, and the authentication succeeds;
  • the serving MSC sends an inter-system short message point-to-point delivery (eg, ISSMDPP) request message to the neighboring MSC, where the value of the parameter SMSMSGCOUNT carried in the inter-system short message point-to-point delivery request message is greater than 0, indicating that the subsequent short message delivery is performed. ;
  • an inter-system short message point-to-point delivery eg, ISSMDPP
  • the neighboring MSC uses the established service channel to perform short message delivery. 510.
  • the neighboring MSC receives a short message delivery response from the base station.
  • the neighboring MSC determines that there is a subsequent short message, so the neighboring MSC does not release the traffic channel, waits for the next short message, and the neighboring MSC returns an inter-system short message point-to-point delivery response message to the serving MSC.
  • the serving MSC After receiving the inter-system short message point-to-point delivery response message, the serving MSC returns a short message point-to-point delivery response message to the short message center;
  • the serving MSC determines to terminate the inter-system short message delivery, and then sends a release (eg, DROPSERVICE) request message to the neighboring MSC, where the release request message carries the identifier of the mobile station, such as IMSI or MIN;
  • a release eg, DROPSERVICE
  • the reason why the service MSC decides to terminate the inter-system short message delivery may be: the user status is abnormal or the service MSC determines that there is no subsequent short message delivery;
  • the neighboring MSC After receiving the release request message, the neighboring MSC immediately terminates the inter-system short message delivery of the MSC, and releases the service channel.
  • the neighboring MSC returns a release response message to the serving MSC, and ends the process.
  • the application scenario shown in Figure 6 is: During the inter-system short message delivery process, the neighboring MSC initiates an immediate release when it receives a release request sent by the base station.
  • the monthly service MSC receives the short message point-to-point delivery (for example: SMDPP) request message of the short message center;
  • SMDPP short message point-to-point delivery
  • the serving MSC finds that the location area where the mobile station is most recently registered is in a border overlapping area between the serving MSC and the neighboring MSC, and the serving MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC.
  • ISPAGE2 inter-system paging
  • the service option parameter carried in the call request message is indicated as a short message service;
  • the neighboring MSC receives an inter-system paging request that carries a short message service option parameter. After the message, the mobile station initiates paging under the MSC;
  • the mobile station responds to the paging in the adjacent MSC.
  • the neighboring MSC instructs the base station to establish a service channel, and the service channel is successfully established.
  • the neighboring MSC returns an inter-system paging response message to the serving MSC.
  • the neighboring MSC receives the release request initiated by the base station, releases the service channel, and terminates the short message delivery between the systems;
  • the neighboring MSC Due to the mobile station's reasons (such as the mobile station's refusal to receive short messages) or the wireless side's reasons (such as wireless signal problems, base station anomalies), etc., the neighboring MSC receives the release request initiated by the base station, and then needs to release the traffic channel and therefore cannot be short. Message delivery
  • the neighboring MSC sends a release (eg, DROPSERVICE) request message to the serving MSC, where the release request message carries the identifier of the mobile station, such as IMSI or MIN;
  • a release eg, DROPSERVICE
  • the serving MSC After receiving the release request message, the serving MSC immediately terminates the inter-system short message delivery, and returns a release response message to the neighboring MSC.
  • the monthly service MSC returns a short message point-to-point delivery response message to the short message center, and ends the processing.
  • the application scenario shown in Figure 7 is: During the inter-system short message delivery process, an immediate release is initiated when multiple short message delivery failures of the MSC are failed.
  • the monthly service MSC receives the short message point-to-point delivery of the short message center (for example:
  • SMSMSGCOUNT value is greater than 0;
  • the serving MSC finds that the location area where the mobile station is most recently registered is in a border overlapping area between the serving MSC and the neighboring MSC, and the serving MSC sends an inter-system paging (eg, ISPAGE2) request message to the neighboring MSC. Carrying in the request message
  • ISPAGE2 inter-system paging
  • the service option parameter is indicated as a short message service
  • the neighboring MSC After receiving the inter-system paging request message carrying the short message service option parameter, the neighboring MSC initiates paging to the mobile station under the MSC;
  • the mobile station responds to the paging in the adjacent MSC.
  • the neighboring MSC instructs the base station to establish a service channel, and the service channel is successfully established.
  • the neighboring MSC returns an inter-system paging response message to the serving MSC, where the inter-system paging response message carries an authentication parameter.
  • the serving MSC After receiving the inter-system paging response message, the serving MSC authenticates the mobile station according to the authentication parameter in the received inter-system paging response message, and the authentication succeeds.
  • the serving MSC sends an inter-system short message point-to-point delivery (eg, ISSMDPP) request message to the neighboring MSC, and the value of the parameter SMSMSGCOUNT carried in the inter-system short message point-to-point delivery request message is greater than 0, indicating that the subsequent short message delivery is performed;
  • an inter-system short message point-to-point delivery eg, ISSMDPP
  • the neighboring MSC uses the established service channel to perform short message delivery.
  • the neighboring MSC receives a short message delivery response from the base station.
  • the neighboring MSC determines that there is a subsequent short message, so the neighboring MSC does not release the traffic channel, waits for the next short message, and the neighboring MSC returns an IS short message point-to-point delivery response message to the serving MSC.
  • the serving MSC After receiving the inter-system short message point-to-point delivery response message, the serving MSC returns a short message point-to-point delivery response message to the short message center;
  • the neighboring MSC waits for the next short message to time out.
  • the neighboring MSC decides to terminate the inter-system short message delivery and release the traffic channel.
  • the neighboring MSC sends a release (for example: DROPSERVICE) request message to the serving MSC, where the release request message carries the identifier of the mobile station, such as IMSI or MIN;
  • a release for example: DROPSERVICE
  • the serving MSC returns a release response message to the neighboring MSC, and ends the process.
  • the present invention can be used in different application scenarios.
  • the MSC or the neighboring MSC decides to terminate the inter-system short message delivery, it directly sends a release request message to the other party to notify the other party to terminate the inter-system short message delivery.
  • the present invention provides a system for releasing a short message delivery after the termination of the system, the system comprising: a serving MSC and an adjacent MSC;
  • the monthly MSC or the neighboring MSC is set as follows: In the inter-system short message delivery process, in the case that the inter-system short message delivery needs to be terminated, the inter-system short message delivery is terminated, and the opposite MSC is notified to terminate the inter-system short message delivery.
  • the serving MSC is further configured to: terminate the inter-system short message when the serving MSC local paging succeeds, or the serving MSC fails to authenticate the mobile station, or the serving MSC cancels the mobile station registration, or the service MSC fails to deliver multiple short messages. Deliver and notify the neighboring MSC to terminate inter-system short message delivery;
  • the adjacency MSC is further configured to: when the neighboring MSC receives the release request sent by the base station, or the plurality of short message delivery failures of the adjacent MSC, terminate the inter-system short message delivery, and notify the service MSC to terminate the inter-system short message delivery.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种系统间短消息投递终止后发起释放的方法及设备。所述方法包括：系统间短消息投递过程中，在需要终止系统间短消息投递的情形下，服务MSC或邻接MSC终止系统间短消息投递，并通知对端MSC终止系统间短消息投递。采用本发明能够减少空中资源和系统资源的浪费。

Description

一种系统间短消息投递终止后发起释放的方法及设备 技术领域
本发明涉及码分多址（CDMA )通信系统， 尤其涉及一种系统间短消 息投递终止后发起释放的方法及设备。 背景技术
在 CDMA系统中， 为了解决移动台在边界交叠区域频繁位置登记的问 题， 当移动台从一个登记区移动到另一个登记区时会自动启用延迟登记机 制。 但是， 这会导致当移动台发生跨位置区漫游时， 不能立即发起位置登 记， 从而导致移动台作为被叫时寻呼失败或者增加寻呼时长的问题； 其中， 前述问题是通过扩大范围寻呼来解决的。 但是， 对于发生跨移动交换中心 ( MSC ) 的漫游移动， 则需要通过系统间寻呼功能来解决。
在 3GPP2的协议中， 定义了系统间短消息投递通过新建业务信道实现 的流程。 下面结合图 1介绍一下现有技术中系统间单条短消息投递的流程， 如图 1所示， 该流程包括以下步驟：
101、服务 MSC收到短消息中心（ SMC )的短消息点对点投递（ SMDPP ) 请求消息；
102、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务 MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送系 统间寻呼 （ISPAGE2 )请求消息， 系统间寻呼请求消息中携带的业务选项 参数 ( CDMASO )指示为短消息业务（SMS );
103、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求消 息后， 在本 MSC下对移动台发起寻呼， 即向移动台发送寻呼请求消息；
104、 移动台在邻接 MSC响应寻呼， 邻接 MSC收到寻呼响应消息； 105、 邻接 MSC指示基站建立业务信道， 并且业务信道建立成功， 这 一过程也即业务信道指配；
106、邻接 MSC向服务 MSC返回系统间寻呼响应消息， 所述系统间寻 呼响应消息中携带有鉴权参数 ( AuthParameters );
107、 服务 MSC收到系统间寻呼响应消息后， 根据收到的系统间寻呼 响应消息中的鉴权参数对移动台进行鉴权， 并且鉴权成功；
108、服务 MSC向邻接 MSC发送系统间短消息点对点投递（ ISSMDPP ) 请求消息；
109、 邻接 MSC利用已经建立好的业务信道进行短消息投递；
110、 邻接 MSC收到基站的短消息投递响应；
111、 邻接 MSC释放业务信道；
112、 邻接 MSC向服务 MSC返回系统间短消息点对点投递响应消息；
113、 服务 MSC收到系统间短消息点对点投递响应消息后， 返回短消 息点对点投递响应消息给短消息中心。 发明内容
由现有技术中系统间单条短消息投递的流程可以看出， 系统间短消 息投递通过新建业务信道实现的流程的特点在于： 邻接 MSC 收到服务 MSC的系统间寻呼请求消息， 在建立好业务信道后向服务 MSC返回系 统间寻呼响应消息， 然后等待收到服务 MSC 的系统间短消息点对点投 递请求消息后将短消息下发移动台。 由于整个过程需要由两个 MSC 配 合完成， 且涉及多条消息交互， 所以需要这样一种方式： 在一侧 MSC 决定终止系统间短消息投递后通知对端 MSC立即释放；否则 ,对端 MSC 只能等待定时器超时后释放， 这样会造成空中资源和系统资源的浪费。
有鉴于此， 本发明的主要目的在于提供一种系统间短消息投递终止后 发起释放的方法及设备， 当服务 MSC或邻接 MSC决定终止系统间短消息 投递时 , 立即通知对方终止系统间短消息投递流程。
为达到上述目的， 本发明的技术方案是这样实现的：
一种系统间短消息投递终止后发起释放的方法， 包括：
系统间短消息投递过程中， 在需要终止系统间短消息投递的情形下， 服务 MSC或邻接 MSC终止系统间短消息投递，并通知对端 MSC终止系统 间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为服务 MSC本地 寻呼成功时， 服务 MSC终止系统间短消息投递， 并通知邻接 MSC终止系 统间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为服务 MSC对移 动台鉴权失败时， 服务 MSC终止系统间短消息投递， 并通知邻接 MSC终 止系统间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为服务 MSC取消 移动台登记时， 服务 MSC终止系统间短消息投递， 并通知邻接 MSC终止 系统间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为服务 MSC多条 短消息投递失败时， 服务 MSC终止系统间短消息投递， 并通知邻接 MSC 终止系统间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为邻接 MSC收到 基站发送的释放请求时， 邻接 MSC 终止系统间短消息投递， 并通知服务 MSC终止系统间短消息投递。
进一步地， 当所述需要终止系统间短消息投递的情形为邻接 MSC多条 短消息投递失败时， 邻接 MSC终止系统间短消息投递， 并通知服务 MSC 终止系统间短消息投递。
进一步地，所述服务 MSC或邻接 MSC通知对端 MSC终止系统间短消 息投递的处理包括：
所述服务 MSC或邻接 MSC向对端发送释放请求消息。
所述方法进一步包括：
服务 MSC或邻接 MSC收到对端发来的终止系统间短消息投递的通知 后， 终止系统间短消息投递。
一种系统间短消息投递终止后发起释放的设备， 所述设备设置为： 系 统间短消息投递过程中， 在需要终止系统间短消息投递的情形下， 终止系 统间短消息投递， 并通知对端设备终止系统间短消息投递。
进一步地， 所述设备为服务 MSC, 所述对端设备为邻接 MSC; 其 中，
所述服务 MSC设置为： 当服务 MSC本地寻呼成功、或服务 MSC对移 动台鉴权失败、 或服务 MSC取消移动台登记、 或服务 MSC多条短消息投 递失败时， 终止系统间短消息投递， 并通知邻接 MSC终止系统间短消息投 递。
进一步地， 所述设备为邻接 MSC, 所述对端设备为服务 MSC; 其中， 所述邻接 MSC设置为： 当邻接 MSC收到基站发送的释放请求、 或邻 接 MSC多条短消息投递失败时，终止系统间短消息投递，并通知服务 MSC 终止系统间短消息投递。
由以上技术方案可以看出， 在需要终止系统间短消息投递的情形下， 服务 MSC或邻接 MSC终止系统间短消息投递，并立即通知对端 MSC终止 系统间短消息投递， 这样对端 MSC可以及时释放空中资源和系统资源， 以 减少空中资源和系统资源的浪费。 附图说明
图 1为现有技术中系统间单条短消息投递的流程图；
图 2为本发明第一实施例在系统间短消息投递过程中，服务 MSC本地 寻呼成功时的立即释放的流程图；
图 3为本发明第二实施例在系统间短消息投递过程中，服务 MSC对移 动台鉴权失败时的立即释放的流程图；
图 4为本发明第三实施例在系统间短消息投递过程中，服务 MSC取消 移动台登记时的立即释放的流程图；
图 5为本发明第四实施例在系统间短消息投递过程中，服务 MSC多条 短消息投递失败时的立即释放的流程图；
图 6为本发明第五实施例在系统间短消息投递过程中，邻接 MSC收到 基站发送的释放请求时的立即释放的流程图；
图 7为本发明第六实施例在系统间短消息投递过程中，邻接 MSC多条 短消息投递失败时的立即释放的流程图。 具体实施方式
本发明在系统间短消息投递过程中， 在需要终止系统间短消息投递 的情形下， 服务 MSC或邻接 MSC终止系统间短消息投递， 并立即向对 端 MSC发送释放请求消息， 通知对端 MSC终止系统间短消息投递， 这 样可以减少空中资源和系统资源的浪费。
以下通过几个实施例对本发明技术方案故进一步详细说明。
实施例一
图 所示的应用场景是： 在系统间短消息投递过程中， 服务 MSC 本地寻呼成功时发起立即释放。
图 2所示的流程包括以下步驟：
201、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如： SMDPP )请求消息；
202、 服务 MSC根据移动台最近一次登记时所在的位置区， 对移动 台发起本地寻呼； 203、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务 MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 系统间寻呼请求消息中携带 的业务选项参数（CDMASO )指示为短消息业务（SMS ) ；
204、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
205、 服务 MSC 在等待系统间寻呼响应的过程中， 移动台在服务 MSC响应寻呼， 服务 MSC收到本地寻呼响应；
206、 服务 MSC决定终止系统间短消息投递， 于是向邻接 MSC发 送释放（例如： DROPSERVICE ) 请求消息， 释放请求消息中携带有移 动台的标识， 如国际移动用户识别码（IMSI )或移动识别号码（MIN )； 月良务 MSC收到本地寻呼响应表明： 移动台处在服务 MSC的覆盖范 围下， 因此服务 MSC不需要通过邻接 MSC进行短消息投递， 自己可以 直接进行短消息投递， 因此， 服务 MSC决定终止系统间短消息投递； 207、 邻接 MSC收到释放请求消息后， 立即终止本 MSC的系统间 短消息投递， 并向服务 MSC返回系统间寻呼响应消息， 系统间寻呼响 应消息中携带有失败原因值；
208、 邻接 MSC向服务 MSC返回释放响应消息；
209、 月良务 MSC向短消息中心返回短消息点对点投递响应消息， 结 束处理。
实施例二
图 3 所示的应用场景是： 在系统间短消息投递过程中， 服务 MSC 对移动台鉴权失败时发起立即释放。
图 3所示的流程包括以下步驟：
301、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如： SMDPP )请求消息；
302、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务 MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 系统间寻呼请求消息中携带 的业务选项参数指示为短消息业务；
303、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
304、 移动台在邻接 MSC响应寻呼；
305、 邻接 MSC指示基站建立业务信道， 并且业务信道建立成功；
306、 邻接 MSC向服务 MSC返回系统间寻呼响应消息， 所述系统 间寻呼响应消息中携带有鉴权参数（ AuthParameters ) ；
307、 服务 MSC收到系统间寻呼响应消息后， 根据收到的系统间寻 呼响应消息中的鉴权参数对移动台进行鉴权， 但鉴权失败；
308、 服务 MSC决定终止系统间短消息投递， 于是向邻接 MSC发 送释放（例如： DROPSERVICE ) 请求消息， 释放请求消息中携带有移 动台的标识 , 如 IMSI或 MIN;
鉴权失败的原因可能是移动台为非法用户， 因此服务 MSC 应该停 止对该非法移动台提供服务；
309、 邻接 MSC收到释放请求消息后， 立即终止本 MSC的系统间 短消息投递， 并释放业务信道；
310、 邻接 MSC向服务 MSC返回释放响应消息；
311、 月良务 MSC向短消息中心返回短消息点对点投递响应消息， 结 束处理。
实施例三
图 4 所示的应用场景是： 在系统间短消息投递过程中， 服务 MSC 取消移动台登记时发起立即释放。
图 4所示的流程包括以下步驟：
401、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如： SMDPP )请求消息；
402、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务
MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 所述系统间寻呼请求消息中 携带的业务选项参数指示为短消息业务；
403、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
404、 服务 MSC收到归属位置寄存器 （HLR )发来的登记取消 （例 如： REGCAN )请求消息， 要求取消移动台登记；
出于管理目的或用户状态异常等原因， HLR要求服务 MSC取消移 动台的登记；
405、 服务 MSC取消移动台登记， 并向 HLR返回登记取消响应消
406、 服务 MSC决定终止系统间短消息投递， 于是向邻接 MSC发 送释放（例如： DROPSERVICE ) 请求消息， 释放请求消息中携带有移 动台的标识 , 如 IMSI或 MIN;
服务 MSC取消移动台登记表明： 服务 MSC不需要为该移动台提供 月良务， 因此决定终止系统间短消息投递；
407、 邻接 MSC收到释放请求消息后， 立即终止本 MSC的系统间 短消息投递， 并向服务 MSC 返回系统间寻呼响应消息， 所述系统间寻 呼响应消息中携带有失败原因值；
408、 邻接 MSC向服务 MSC返回释放响应消息； 409、 月良务 MSC向短消息中心返回短消息点对点投递响应消息， 结 束处理。
实施例四
图 5 所示的应用场景是： 在系统间短消息投递过程中， 服务 MSC 多条短消息投递失败时发起立即释放。
图 5所示的流程包括以下步驟：
501、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如： SMDPP ) 请求消息， 短消息点对点投递请求消息中携带的参数 SMSMSGCOUNT的值大于 0;
502、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务
MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 系统间寻呼请求消息中携带 的业务选项参数指示为短消息业务；
503、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
504、 移动台在邻接 MSC响应寻呼；
505、 邻接 MSC指示基站建立业务信道， 并且业务信道建立成功；
506、 邻接 MSC向服务 MSC返回系统间寻呼响应消息， 所述系统 间寻呼响应消息中携带有鉴权参数；
507、 服务 MSC收到系统间寻呼响应消息后， 根据收到的系统间寻 呼响应消息中的鉴权参数对移动台进行鉴权， 并且鉴权成功；
508、 服务 MSC向邻接 MSC发送系统间短消息点对点投递（例如： ISSMDPP )请求消息， 所述系统间短消息点对点投递请求消息中携带的 参数 SMSMSGCOUNT的值大于 0, 表示后续有连发短消息投递；
509、 邻接 MSC利用已经建立好的业务信道， 进行短消息投递； 510、 邻接 MSC收到基站的短消息投递响应；
511、 邻接 MSC确定后续有连发短消息， 所以邻接 MSC不释放业 务信道， 等待下一条短消息， 并且邻接 MSC向服务 MSC返回系统间短 消息点对点投递响应消息；
512、 服务 MSC收到系统间短消息点对点投递响应消息后， 返回短 消息点对点投递响应消息给短消息中心；
513、 服务 MSC决定终止系统间短消息投递， 于是向邻接 MSC发 送释放（例如： DROPSERVICE ) 请求消息， 所述释放请求消息中携带 有移动台的标识， 如 IMSI或 MIN；
服务 MSC 决定终止系统间短消息投递的原因可能是： 用户状态异 常或服务 MSC判断无后继短消息投递；
514、 邻接 MSC收到释放请求消息后， 立即终止本 MSC的系统间 短消息投递， 并释放业务信道；
515、 邻接 MSC向服务 MSC返回释放响应消息， 结束处理。
实施例五
图 6 所示的应用场景是： 在系统间短消息投递过程中， 邻接 MSC 收到基站发送的释放请求时发起立即释放。
图 6所示的流程包括以下步驟：
601、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如： SMDPP )请求消息；
602、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务 MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 系统间寻呼请求消息中携带 的业务选项参数指示为短消息业务；
603、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
604、 移动台在邻接 MSC响应寻呼；
605、 邻接 MSC指示基站建立业务信道， 并且业务信道建立成功；
606、 邻接 MSC向服务 MSC返回系统间寻呼响应消息；
607、 邻接 MSC收到基站发起的释放请求， 释放业务信道并终止系 统间短消息投递；
由于移动台原因 （如移动台拒绝接收短消息） 或无线侧的原因 （如 无线信号问题、 基站异常） 等， 邻接 MSC 收到基站发起的释放请求， 于是需要释放业务信道并因此无法再进行短消息投递；
608、 邻接 MSC向服务 MSC发送释放（例如： DROPSERVICE )请 求消息， 释放请求消息中携带有移动台的标识， 如 IMSI或 MIN；
609、服务 MSC收到释放请求消息后，立即终止系统间短消息投递， 并向邻接 MSC返回释放响应消息；
610、 月良务 MSC向短消息中心返回短消息点对点投递响应消息， 结 束处理。
实施例六
图 7 所示的应用场景是： 在系统间短消息投递过程中， 邻接 MSC 多条短消息投递失败时发起立即释放。
图 7所示的流程包括以下步驟：
701、 月良务 MSC 收到短消息中心的短消息点对点投递 （例如：
SMDPP ) 请求消息， 短消息点对点投递请求消息中携带的参数 SMSMSGCOUNT的值大于 0;
702、 服务 MSC发现移动台最近一次登记时所在的位置区处于服务 MSC与邻接 MSC间的边界交叠区域， 于是服务 MSC向邻接 MSC发送 系统间寻呼 （例如： ISPAGE2 )请求消息， 系统间寻呼请求消息中携带 的业务选项参数指示为短消息业务；
703、 邻接 MSC收到携带有短消息业务选项参数的系统间寻呼请求 消息后， 在本 MSC下对移动台发起寻呼；
704、 移动台在邻接 MSC响应寻呼；
705、 邻接 MSC指示基站建立业务信道， 业务信道建立成功；
706、 邻接 MSC向服务 MSC返回系统间寻呼响应消息， 所述系统 间寻呼响应消息中携带有鉴权参数；
707、 服务 MSC收到系统间寻呼响应消息后， 根据收到的系统间寻 呼响应消息中的鉴权参数对移动台进行鉴权， 并且鉴权成功；
708、 服务 MSC向邻接 MSC发送系统间短消息点对点投递（例如： ISSMDPP )请求消息， 系统间短消息点对点投递请求消息中携带的参数 SMSMSGCOUNT的值大于 0, 表示后续有连发短消息投递；
709、 邻接 MSC利用已经建立好的业务信道进行短消息投递；
710、 邻接 MSC收到基站的短消息投递响应；
711、 邻接 MSC确定后续有连发短消息， 所以邻接 MSC不释放业 务信道， 等待下一条短消息， 并且邻接 MSC向服务 MSC返回 IS短消 息点对点投递响应消息；
712、 服务 MSC收到系统间短消息点对点投递响应消息后， 返回短 消息点对点投递响应消息给短消息中心；
713、 邻接 MSC等待下一条短消息超时；
714、 邻接 MSC决定终止系统间短消息投递， 并释放业务信道；
715、 邻接 MSC向服务 MSC发送释放（例如： DROPSERVICE )请 求消息， 所述释放请求消息中携带有移动台的标识， 如 IMSI或 MIN;
716、 服务 MSC向邻接 MSC返回释放响应消息， 结束处理。
根据上述实施例可以发现， 本发明能够在不同应用场景下， 当服务 MSC或邻接 MSC—旦决定终止系统间短消息投递时， 直接向对方发送 释放请求消息， 通知对方终止系统间短消息投递。
为实现上述方法， 本发明相应提供一种系统间短消息投递终止后发 起释放的系统， 所述系统包括： 服务 MSC和邻接 MSC; 其中，
月良务 MSC或邻接 MSC设置为： 系统间短消息投递过程中， 在需要 终止系统间短消息投递的情形下， 终止系统间短消息投递， 并通知对端 MSC终止系统间短消息投递。
所述服务 MSC进一步设置为： 当服务 MSC本地寻呼成功、 或服务 MSC对移动台鉴权失败、或服务 MSC取消移动台登记、或服务 MSC多 条短消息投递失败时， 终止系统间短消息投递， 并通知邻接 MSC 终止 系统间短消息投递；
所述邻接 MSC进一步设置为： 当邻接 MSC收到基站发送的释放请 求、 或邻接 MSC 多条短消息投递失败时， 终止系统间短消息投递， 并 通知服务 MSC终止系统间短消息投递。
本领域技术人员应当理解， 本发明系统间短消息投递终止后发起释 放的系统是为了实现图 2-7所示的方法而设计的， 因此该系统中的各处 理单元的功能可参照图 2-7所示的方法中的相关描述而理解， 在此不再 赘述。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的 保护范围。

Claims

权利要求书
1、 一种系统间短消息投递终止后发起释放的方法， 其特征在于， 所 述方法包括：
系统间短消息投递过程中，在需要终止系统间短消息投递的情形下， 服务移动交换中心 MSC或邻接 MSC终止系统间短消息投递， 并通知对 端 MSC终止系统间短消息投递。
2、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为服务 MSC 本地寻呼成功时， 服务 MSC终止系统间短消息投递， 并通知邻接 MSC 终止系统间短消息投递。
3、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为服务 MSC 对移动台鉴权失败时， 月良务 MSC 终止系统间短消息投递， 并通知邻接 MSC终止系统间短消息投递。
4、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为服务 MSC 取消移动台登记时，服务 MSC终止系统间短消息投递，并通知邻接 MSC 终止系统间短消息投递。
5、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为服务 MSC 多条短消息投递失败时， 服务 MSC 终止系统间短消息投递， 并通知邻 接 MSC终止系统间短消息投递。
6、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为邻接 MSC 收到基站发送的释放请求时， 邻接 MSC 终止系统间短消息投递， 并通 知月良务 MSC终止系统间短消息投递。
7、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 当所述需要终止系统间短消息投递的情形为邻接 MSC 多条短消息投递失败时， 邻接 MSC 终止系统间短消息投递， 并通知服 务 MSC终止系统间短消息投递。
8、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 所述服务 MSC或邻接 MSC通知对端 MSC终止系统 间短消息投递的处理包括：
所述服务 MSC或邻接 MSC向对端发送释放请求消息。
9、 根据权利要求 1 所述的系统间短消息投递终止后发起释放的方 法， 其特征在于， 所述方法进一步包括：
月良务 MSC或邻接 MSC收到对端发来的终止系统间短消息投递的通 知后， 终止系统间短消息投递。
10、 一种系统间短消息投递终止后发起释放的设备， 其特征在于， 所述设备设置为： 系统间短消息投递过程中， 在需要终止系统间短消息 投递的情形下， 终止系统间短消息投递， 并通知对端设备终止系统间短 消息投递。
11、根据权利要求 10所述的系统间短消息投递终止后发起释放的设 备， 其特征在于， 所述设备为服务 MSC, 所述对端设备为邻接 MSC; 其中，
所述服务 MSC设置为： 当服务 MSC本地寻呼成功、 或服务 MSC 对移动台鉴权失败、 或服务 MSC取消移动台登记、 或服务 MSC多条短 消息投递失败时， 终止系统间短消息投递， 并通知邻接 MSC 终止系统 间短消息投递。
12、根据权利要求 10所述的系统间短消息投递终止后发起释放的设 备， 其特征在于， 所述设备为邻接 MSC, 所述对端设备为服务 MSC; 其中，
所述邻接 MSC设置为： 当邻接 MSC收到基站发送的释放请求、 或 邻接 MSC 多条短消息投递失败时， 终止系统间短消息投递， 并通知服 务 MSC终止系统间短消息投递。
PCT/CN2012/078198 2011-08-16 2012-07-04 一种系统间短消息投递终止后发起释放的方法及设备 WO2013023501A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110234879.2 2011-08-16
CN201110234879.2A CN102958015B (zh) 2011-08-16 2011-08-16 一种系统间短消息投递终止后发起释放的方法及系统

Publications (1)

Publication Number Publication Date
WO2013023501A1 true WO2013023501A1 (zh) 2013-02-21

Family

ID=47714737

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/078198 WO2013023501A1 (zh) 2011-08-16 2012-07-04 一种系统间短消息投递终止后发起释放的方法及设备

Country Status (2)

Country Link
CN (1) CN102958015B (zh)
WO (1) WO2013023501A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103546991B (zh) * 2012-07-09 2017-08-29 中国电信股份有限公司 对系统间短消息业务进行释放的方法和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984449A (zh) * 2006-05-30 2007-06-20 华为技术有限公司 移动交换中心系统间寻呼移动台的方法
CN101166353A (zh) * 2006-10-18 2008-04-23 中兴通讯股份有限公司 一种实现系统间寻呼后移动性限制功能的方法
CN101207929A (zh) * 2007-12-25 2008-06-25 华为技术有限公司 一种系统间寻呼方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4056971B2 (ja) * 2003-12-25 2008-03-05 株式会社エヌ・ティ・ティ・ドコモ 相互接続契約判定システム、相互接続契約判定装置、及び、相互接続契約判定方法
CN101094455B (zh) * 2007-08-04 2012-05-23 中兴通讯股份有限公司 一种实现移动网络中短消息实时传输的方法
US20100075700A1 (en) * 2008-08-27 2010-03-25 Kabushiki Kaisha Toshiba Flexible capacity short message service center (SMSC)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984449A (zh) * 2006-05-30 2007-06-20 华为技术有限公司 移动交换中心系统间寻呼移动台的方法
CN101166353A (zh) * 2006-10-18 2008-04-23 中兴通讯股份有限公司 一种实现系统间寻呼后移动性限制功能的方法
CN101207929A (zh) * 2007-12-25 2008-06-25 华为技术有限公司 一种系统间寻呼方法及系统

Also Published As

Publication number Publication date
CN102958015B (zh) 2018-02-16
CN102958015A (zh) 2013-03-06

Similar Documents

Publication Publication Date Title
US11832206B2 (en) Method and apparatus for supporting access control and mobility management
JP6883775B2 (ja) 改良されたショート・メッセージ送信手順およびハンドオーバ手順
CN108632915B (zh) 一种终端在4g和5g网络间移动的方法、装置和设备
US20190327659A1 (en) Handover using dual active connections
KR101700448B1 (ko) 이동 통신 시스템에서 보안 관리 시스템 및 방법
EP2285157B1 (en) A roaming retrying method under pre-paging mode
KR20180096670A (ko) 이동 통신 시스템에서 단말의 통신 방법 및 장치
US7920521B2 (en) Method and system for foreign agent relocation in wireless network
JP5984278B2 (ja) サービス要求後の遅延
US8300605B2 (en) General access network controller bypass to facilitate use of standard cellular handsets with a general access network
CN105706519A (zh) 移动无线电通信网络中的小数据传输的控制
JP2014516495A (ja) モバイル通信システムにおけるコア・ネットワーク・エンティティに障害が生じた場合のモバイル終端ｃｓサービスの復元
WO2007045177A1 (fr) Procede, systeme et appareil de realisation de desenregistrement de protocole mobile
WO2013034091A1 (zh) 一种sms业务的处理方法及装置
EP4094482A1 (en) Managing a non-conditional procedure during a conditional procedure
US9900818B2 (en) Communication system
US6542476B1 (en) System and method for dynamic timer regeneration
CN105828399B (zh) 一种跟踪区更新方法及装置
WO2023154445A1 (en) Managing radio configurations for a user equipment
WO2013023501A1 (zh) 一种系统间短消息投递终止后发起释放的方法及设备
US20150304895A1 (en) Communication system
WO2011095001A1 (zh) 一种由移动终端主动发起的数据通道建立方法及asn系统
WO2014048368A1 (zh) 确定激活isr的方法及设备
US8732799B2 (en) Method and system for processing authenticator relocation request
US9924434B1 (en) Method and system for diverting WCDs based on unavailability of authentication procedure

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: 12824279

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12824279

Country of ref document: EP

Kind code of ref document: A1