WO2007147357A1 - Procédé et système de transmission d'informations d'emplacement de terminaison d'abonné dans un sous-système multimédia ip - Google Patents
Procédé et système de transmission d'informations d'emplacement de terminaison d'abonné dans un sous-système multimédia ip Download PDFInfo
- Publication number
- WO2007147357A1 WO2007147357A1 PCT/CN2007/070109 CN2007070109W WO2007147357A1 WO 2007147357 A1 WO2007147357 A1 WO 2007147357A1 CN 2007070109 W CN2007070109 W CN 2007070109W WO 2007147357 A1 WO2007147357 A1 WO 2007147357A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- location information
- user
- call
- function entity
- entity
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1095—Inter-network session transfer or sharing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42348—Location-based services which utilize the location information of a target
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1225—Details of core network interconnection arrangements
- H04M7/123—Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1225—Details of core network interconnection arrangements
- H04M7/1235—Details of core network interconnection arrangements where one of the core networks is a wireless network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/10—Mobility data transfer between location register and external networks
Definitions
- the present invention relates to an IP Multimedia Subsystem (IMS) technology, and more particularly to a method and apparatus for communicating user terminal location information in an IP multimedia subsystem.
- IMS IP Multimedia Subsystem
- the network needs to know the registration status of the user on the two networks, so that when there is a call that needs to be connected to the user, the appropriate network can be selected for connection. In addition, the network needs to make all the calls of the user, so that the user can perform auxiliary control when switching between the two networks.
- FIG. 1 is a schematic structural diagram of a prior art anchoring control based on an IMS entity. As shown in FIG. 1, a set of functional entities is added in the IMS domain and the circuit switched (CS) domain, as follows:
- FE-C route redirection function entity
- the CS domain adaptation function entity (FE-B) is configured to receive a CS domain call redirected to the IMS domain and convert the CS domain call into an IMS domain call.
- the route redirection function entity and the CS domain adaptation function entity may be set in the same entity, and the entity is collectively referred to as a redirect/adaptive function.
- Body the interface between the two belongs to the internal interface; it can also be two independent entities.
- FE-D domain selection control function entity
- the domain handover control function entity (FE-A) is used to anchor the call in the IMS domain, and performs handover control when the handover occurs.
- the mobile switching center interacts with the FE-C through the gsmSCF.
- the gsmSCF and the FE-C are usually co-located in the same entity. Therefore, the VMSC and the FE-C can be directly interacted.
- FIG. 2 is a flowchart of a method for a dual-mode user terminal to initiate a call in a CS domain, as shown in FIG. 2, including the following steps:
- Step 200 The dual mode user terminal (UE) sends a call setup message to the VMSC in the CS domain.
- the call setup message carries the called number, the Called Party Number, and the cell ID of the location area of the calling user.
- Step 201 After receiving the call setup message, the VMSC triggers an initial Detect Point (IDP) message and sends the message to the route redirection function entity.
- IDP initial Detect Point
- the IDP message is an Origination Request (ORREQ) message.
- ORREQ Origination Request
- the IDP message and the ORREQ message are collectively referred to as an intelligent trigger message.
- the IDP message should carry the Called Party Number and the cell ID of the location area of the calling user.
- the Cell ID is not used in the prior art, so it is not shown in FIG.
- Step 202 The route redirection function entity allocates an IMS domain routing number (IMRN), and carries the allocated IMRN in a connection (CONNECT) message to the VMSC, thereby redirecting the call to the IMS domain.
- IMRN IMS domain routing number
- CONNECT connection
- Step 203 The VMSC carries the received IMRN and the Called Party Number in an initial message (IAM), and sends the message to the IMS domain media gateway control function (MGCF) entity. In this step, the VMSC routes the call to the IMS domain ingress gateway.
- IAM initial message
- MGCF media gateway control function
- Step 204 The MGCF entity constructs a Session Initiation Protocol (SIP) Session Request (INVITE) message, and carries the received IMRN and Called Party Number in the INVITE message, and sends the call to the called subscriber's home IMS domain to query the call session control.
- SIP Session Initiation Protocol
- INVITE Called Party Number
- I-CSCF Function
- the IMRN carried in the INVITE message is used as the called address.
- Step 205 After receiving the INVITE message, the I-CSCF entity detects that the called address is an IMRN, uses the IMRN as a public service identity (PSI), and routes the INVITE message to the CS adaptation function entity.
- PSI public service identity
- Step 206 The CS adaptation function entity replaces the dual mode user terminal, and sends the received INVITE message to the Serving Call Session Control Function (S-CSCF) entity in the IMS domain, and the CS adaptation function entity replaces the dual mode user terminal in the IMS.
- S-CSCF Serving Call Session Control Function
- Step 207 The S-CSCF triggers the call to the basic service application server (AS) to which the user belongs, and sends the received INVITE message to the basic service AS to perform caller service control.
- AS basic service application server
- Step 208 The basic service After the AS completes the control of the calling service, the INVITE message is returned to the S-CSCF.
- Step 209 The S-CSCF routes the session to the called side network to continue the subsequent call.
- the dual-mode user terminal subscribes to the originating call restriction service, such as restricting all outgoing calls, restricting international long distance, and restricting domestic long distance, etc.
- the control of these services is implemented by the basic service AS of the IMS domain. Then, the basic service AS should have the ability to identify whether the type of the current call of the user meets the conditions of the call restriction, and then perform corresponding service control.
- the basic service AS determines whether the call of the dual-mode user terminal is a long-distance service, the basic service AS needs to know the location information of the dual-mode user terminal that initiates the call, and the location information to which the called user belongs, when these two locations When in the same area, the decision is not long Otherwise, it is determined to be a long-distance service. At this time, if the dual-mode user terminal signs a limited long-distance service, the basic service AS should reject the call.
- the INVITE message received by the basic service AS carries only the location information to which the called user belongs - Called Party Number, and the location information of the dual-mode user terminal where the call is not initiated, therefore, according to the current
- the basic service AS is a dual-mode user terminal that cannot determine whether the originating call from the CS domain meets the initial call restriction service of the subscription, so that subsequent calls in the IMS domain are not based on the dual-mode user.
- the signing of the terminal is carried out, but the call is continued regardless of whether the current call is a restricted call, or the call control is performed according to other policies in the IMS domain, thereby reducing the quality of service control.
- the IMS domain cannot obtain the location information of the current location of the dual-mode user terminal, so that the basic service AS cannot obtain the calling party. If the location information of the current location of the user is not available, the subsequent call can be properly controlled according to the signing situation of the calling user.
- the SIP: INVITE message carries a P-Access-Network-Info header field, where the header field carries the cell identifier of the location area of the user, The header field is transmitted with the call message to the calling user's home IMS domain and other trusted domains.
- the P-CSCF also adds a visited network identifier P-Visited-Network-ID header field to the INVITE message, and the header field carries the network identifier of the network where the P-CSCF is located.
- the P-Access-Network-Info header field carries the location information of the mobile user, since the header domain information is filled in by the user terminal itself, the network trust cannot be obtained, therefore, The location information carried by the header field is not used for location-related services, such as the control of the originating call restriction service.
- the basic service AS in the IMS domain cannot be judged.
- the user terminal that initiates the call is disconnected from the initial call restriction service of the subscription, so that subsequent calls in the IMS domain are not performed according to the subscription situation of the user terminal, thereby reducing the quality of service control.
- an object of the embodiments of the present invention is to provide a method for transmitting location information of a user terminal in an IP multimedia subsystem, which can obtain trusted location information of the user terminal and transmit the information to the related entity in the IMS domain.
- Another object of the embodiments of the present invention is to provide an apparatus for transmitting user terminal location information in an IP multimedia subsystem, which can obtain trusted user terminal location information and transmit it to
- a method for transmitting user terminal location information in an IP multimedia subsystem IMS is a method for transmitting user terminal location information in an IP multimedia subsystem IMS
- a location information acquiring module for acquiring location information of the user terminal is set in the IMS domain, and the method includes:
- the location information obtaining module carries the obtained user terminal location information in the session initiation protocol SIP signaling, and sends the information to the IP multimedia subsystem IMS domain.
- An apparatus for transmitting user terminal location information in an IP multimedia subsystem IMS at least comprising: a location information acquisition module, the location information acquisition module receiving user terminal location information, and carrying the user terminal location information in a session initiation protocol
- the existing SIP signaling interface module in the device is sent to the IP multimedia subsystem IMS network.
- a location information acquiring module for acquiring location information of the user terminal is set in the IMS domain, and the location information acquiring module carries the obtained user terminal location information in the tongue initiation protocol SIP letter. Order, sent to IP multimedia subsystem
- the IMS domain realizes obtaining trusted user terminal location information and transmitting it to related entities in the IMS domain.
- FIG. 1 is a schematic structural diagram of a prior art anchoring control based on an IMS entity
- FIG. 2 is a flow chart of a prior art dual mode user terminal initiating a call in a CS domain
- FIG. 3 is a flowchart of the method of the present invention
- FIG. 5 is a flow chart of the second embodiment of the present invention. Mode for carrying out the invention
- a location information acquiring module for acquiring location information of the user terminal is set in the IMS domain, and the location information acquiring module carries the obtained location information of the user terminal in the SIP signaling of the tongue initiation protocol, and sends the information to the IP address.
- Multimedia Subsystem IMS Domain Multimedia Subsystem IMS Domain.
- Step 300 Set a location information obtaining block for acquiring location information of the user terminal in the IMS domain.
- the location information obtaining module may be configured in a route redirection function entity, or in a CS adaptation entity, or a redirect/adaptive function entity, or a registration or call related entity such as an application server/MGCF/P in the IMS domain. -CSCF, etc., or an independent entity.
- the location information obtaining module may obtain the location information of the user terminal from the received call setup request, or may move the location center from a home subscriber server (HSS) or a gateway.
- User location information is obtained from a location information management entity such as GLMC.
- the location information of the user terminal referred to herein includes at least location information of the calling user terminal.
- the VMSC carries the Called Party Number in the IDP message sent to the visited network in the route redirection function entity according to the CAMEL protocol.
- the allocated IMRN obtains a cell identifier of a location area of the calling user corresponding to the IMRN;
- the route redirecting function entity receives the Called Party Number and the location of the calling user carried in the received IDP message after receiving the IDP message.
- the area cell identifier is sent to the CS adaptation function entity, and the CS adaptation function entity is requested to allocate the IMRN.
- the CS adaptation function entity saves the Called Party Number carried in the IDP message and the cell identifier of the location area where the calling user is located, and allocates and saves the saved The Called Party Number and the IMRN corresponding to the location identifier of the calling user, that is, the IMRN corresponding to the current call, and return the allocated IMRN to the redirecting functional entity; if the location information obtaining module is set in the route redirection function entity, or The CS adaptation entity, or the redirecting/adapting functional entity, or an independent entity, can directly query the location server such as the HSS or the GMLC to obtain the location information of the user terminal. If the query is made to the HSS, the user data request (User Data Request) message is queried on the Sh interface.
- the location server such as the HSS or the GMLC
- the HSS If there is user terminal location information in the HSS, it returns directly. If it does not exist, it can further query the location server, for example, by arbitrarily The ATI (Any Time Interrogation) message is queried to the VMSC or the SGSN. It should be noted that, here, a method for obtaining the location information of the user terminal by using the location information obtaining module of the present invention is emphasized, and how to obtain the information of the prior art is not described herein.
- the location information obtaining module is set in the MGCF, after the MGCF receives the call setup request from the user terminal, if the call setup request carries the cell identifier of the location area where the calling user is located, the cell identifier of the location area of the calling user is used as The location information of the calling user; if the call setup request does not carry the cell identifier of the location area of the calling user, the MGCF may obtain the location information of the user terminal from the location server or the home subscriber server in the IMS domain, and serve as the master Call the user's location information.
- Step 301 The location information acquiring module carries the obtained user terminal location information in the SIP signaling of the tongue initiation protocol, and sends the information to the IP multimedia subsystem IMS domain.
- the IMS domain can perform the service control in the IMS domain by using the obtained location information of the calling user terminal.
- the basic service AS in the IMS domain determines to initiate the call according to the location information of the calling user. Whether the user terminal satisfies the initial call restriction service of the contract, and the like.
- the method of the present invention acquires the location information of the calling user terminal through the preset location information acquiring module, and transmits the location information of the calling user to the related entity in the IMS domain, further implementing the location information according to the user terminal.
- the subsequent calls in the IMS domain are reasonably controlled to improve the quality of service control.
- Step 400 The UE sends a call setup message to the VMSC in the CS domain.
- the call setup message carries the called number, that is, the Called Party Number, and the current location area cell identifier of the user.
- Step 401 After receiving the call setup message, the VMSC triggers the IDP message and sends the message to the route redirection function entity.
- the Called Party Number should be carried in the IDP message.
- the IDP message is an Origination Request (ORREQ) message.
- ORREQ Origination Request
- the IDP message and the ORREQ message are collectively referred to as an intelligent trigger message.
- Steps 402 to 403 The route redirection function entity saves the received Cell ID, allocates an IMRN corresponding to the Cell ID, and carries the allocated IMRN in the CONNECT message to return to the VMSC, thereby redirecting the call to the IMS domain.
- Step 404 The VMSC carries the received IMRN and the Called Party Number in the IAM and sends the message to the IMS domain MGCF entity.
- the VMSC routes the call to the IMS domain ingress gateway according to the received IMRN.
- Step 405 The MGCF entity constructs a SIP:INVITE message, and will receive the IMRN and
- the Called Party Number is carried in the INVITE message and sent to the called user.
- the IMS domain is entered into the O I-CSCF entity.
- the IMRN carried in the INVITE message is used as the called address.
- Step 406 After receiving the INVITE message, the I-CSCF entity detects that the called address is
- the IMRN is treated as a PSI, and the INVITE message is routed to the CS adaptation function entity.
- the CS adaptation function entity carries the received IMRN in the QUERY message and sends it to the route redirection function entity, and the route redirection function entity carries the Cell ID corresponding to the IMRN in the response (RESPONSE) message, and returns Adapt the CS to the functional entity.
- Step 409 The CS adaptation function entity replaces the received Called Party Number with the IMRN in the INVITE message, and carries the obtained Cell ID in the SIP:INVITE message. Instead of the UE initiating a new session to the S-CSCF entity in the IMS domain.
- the CS adaptation function entity may use the existing P-Access-Network-Info header field or some other header field in the SIP:INVITE message to carry the Cell ID.
- the CS adaptation function entity may also start the CS domain by using the existing P-Visit-Network-ID header field in the SIP:INVITE message or some other header field.
- a call identity is sent to identify that the call originated from the CS domain, such that the IMS domain service control entity can trust the location information.
- Steps 410 to 411 The S-CSCF entity triggers the call to the application server to which the user belongs, such as the basic service AS, and sends the received INVITE message to the basic service AS to perform caller service control, and the basic service AS completes the caller. After the service is controlled, the INVITE message is returned to the S-CSCF entity.
- the application server to which the user belongs such as the basic service AS
- the basic service AS completes the caller.
- the basic service AS learns the location of the user according to the current location area cell identifier of the calling user carried in the P-Access-Network-Info header field in the INVITE message, and learns according to the Called Party Number.
- the called party belongs to the location, so that the initial call restriction service control can be performed.
- the basic service AS If the initial call service restriction is not required, the basic service AS returns the session to the S-CSCF entity after completing the caller service control; if the initial call service restriction is required, the rejection response is returned.
- Step 412 The S-CSCF entity routes the session to the called side network, or sends the rejection information to the calling party.
- the Called Party Number is carried in the SIP:INVITE message.
- the cell ID of the current location area of the calling user carried in step 409 can be deleted. It should be noted that whether to delete the cell ID of the current location area of the calling user is determined by the operator, and the deletion is to prevent other operator networks from obtaining the location information of the calling party.
- the CS adaptation function entity in the visited network rectifies the work by using the route.
- the entity ID is exchanged, and the cell ID of the location of the calling user corresponding to the IMRN is obtained by using the route redirection function to the IMRN, and the obtained Called Party Number and the Cell ID are carried in the SIP: INVITE message.
- the IMS domain initiates a session in the IMS domain to the called user.
- the basic service AS learns the location of the user according to the current location area cell identifier of the calling user carried in the INVITE message, and the Called Party Number knows the called home location, so that the IMS domain is based on the calling party.
- the user's signing situation correctly implements subsequent call control.
- FIG. 5 is a flowchart of Embodiment 2 of the present invention.
- the specific implementation includes the following steps: Step 500: The UE sends a call setup message to the VMSC in the CS domain.
- the call setup message carries the called number, that is, the Called Party Number, and the current location area cell identifier of the user.
- Step 501 After receiving the call setup message, the VMSC triggers the IDP message and sends the message to the route redirecting function entity.
- the IDP message should carry the Called Party Number, the Cell ID of the location of the calling user.
- the above IDP message is an Origination Request (ORREQ) message.
- Step 502 The route redirection function entity applies for IMRN to the CS adaptation function entity.
- the route redirection function entity carries the received Called Party Number and the Cell ID of the location of the calling user in the QUERY message, and sends the message to the CS adaptation function entity.
- Step 503 The CS adaptation function entity allocates the IMRN, and saves the received Called Party Number and the Cell ID of the location of the calling user.
- the assigned IMRN corresponds to the saved Called Party Number and the Cell ID of the location where the calling user is located.
- Step 504 The CS adaptation function entity returns the IMRN in the RESPONSE message to the route redirection function entity.
- Step 505 The route redirection function entity returns the received IMRN to the VMSC, thereby redirecting the call to the IMS domain.
- Step 506 The VMSC carries the received IMRN in the IAM and sends it to the IMS domain MGCF entity.
- the VMSC routes the call to the IMS domain ingress gateway according to the received IMRN.
- Step 507 The MGCF entity constructs a SIP: INVITE message, and carries the received IMRN in the INVITE message, and sends it to the ingress I-CSCF entity of the called user's home IMS domain.
- the IMRN carried in the INVITE message is used as the called address.
- Step 508 After receiving the INVITE message, the I-CSCF entity detects that the called address is an IMRN, uses the IMRN as a PSI, and routes the INVITE message to the CS adaptation function entity.
- Step 509 The CS adaptation function entity uses the received IMRN, carries the Called Party Number corresponding to the IMRN, and the Cell ID of the location where the calling user is located in the INVITE message, and replaces the IMRN with a Called Party Number instead of the UE.
- a new tongue is initiated to the S-CSCF entity.
- the CS adaptation function entity can use the existing P-Access-Network-Info header field or some other header field in the SIP:INVITE message to carry the Cell ID.
- the CS adaptation function entity may also start the CS domain by using the existing P-Visited-Network-ID header field in the SIP:INVITE message or some other header field.
- a call identity is sent to identify that the call originated from the CS domain.
- Step 510 to step 511 The S-CSCF entity triggers the call to the basic service AS to which the user belongs, and sends the received INVITE message to the basic service AS to perform caller service control. After the basic service AS completes the caller service control, , return the INVITE message to the S-CSCF Body.
- the basic service AS learns the location of the user according to the current location area cell identifier of the calling user carried in the P-Access-Network-Info header field in the INVITE message, and learns according to the Called Party Number.
- the called home location so that the initial call restriction service control can be performed, and the existing INVITE message can also be present.
- the P-Visited-Network-ID header field or some other header field carries the credibility identifier of the location information, and is used to identify whether the cell identifier of the current location area of the calling user carried in the INVITE message is trusted.
- the basic service AS If the initial call service restriction is not required, the basic service AS returns the session to the S-CSCF entity after completing the caller service control; if the initial call service restriction is required, the rejection response is returned.
- Step 512 The S-CSCF entity routes the session to the called side network, or sends the rejection information to the calling party.
- the Called Party Number is carried in the SIP:INVITE message.
- the cell ID of the current location area of the calling user carried in the SIP:INVITE message can be deleted. It should be noted that whether to delete the cell ID of the current location area of the calling user is determined by the operator, and the deletion is to prevent other operator networks from obtaining the location information of the calling party. .
- the CS adaptation function entity in the visited network receives the request from the redirecting function entity, saves the Called Party Number carried in the request, and the cell identifier of the location area of the calling user, and allocates and saves the Called Party. Number and the IMRN corresponding to the cell identifier of the location area of the calling user; the CS adaptation function entity carries the obtained Called Party Number and Cell ID in the SIP: INVITE message instead of the UE in the IMS domain to initiate the IMS domain to the called user. Conversation.
- the basic service AS learns the location of the user according to the current location area cell identifier of the calling user carried in the INVITE message, and learns the called home location according to the Called Party Number, so that the IMS domain is based on the IMS domain.
- the signing of the calling user correctly implements the subsequent call control.
- the processing method of the present invention is as follows: In the SIP ⁇ tongue/registration request initiated by the user terminal, the location information may be carried in the P-Access- In the network-Info header field, when an entity in the IMS network, such as a P-CSCF or a location information acquisition module in an AS, receives the SIP ⁇ tongue/registration request, the location server is queried to obtain the real location information of the user. Then, the obtained real location information is carried in the SIP session/registration request, and the content in the P-Access-Network-Info header field may be replaced by the obtained real location information, or may be carried by using another header field or parameter.
- the subsequent entities of the IMS domain can obtain the real location information of the user from the SIP signaling and perform service control by using the real location information of the user, where the service may be an initial call restriction service, or a roaming restriction service, or other business.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Mobile Radio Communication Systems (AREA)
Description
在 IP多媒体子***中传递用户终端位置信息的方法及装置 技术领域
本发明涉及 IP多媒体子***( IMS )技术, 尤指一种在 IP多媒体子 ***中传递用户终端位置信息的方法及装置。 发明背景
在无线网络从第二代( 2G )网络演进到 3G网络的过程中 , 会有很长 一段时期存在 3G网络与 2G网络双网并存的状况 , 在双网并存的情况下 , 双网之间的互操作成为了一个有待研究的课题。
网络需要获知用户在两个网络的注册状况 , 这样当有呼叫需要接续 到用户时, 可以选择合适的网络来进行接续。 另外, 网络需 苗定用户 的所有呼叫, 以方便用户在两个网络之间进行切换时可以进行辅助控 制。
为了解决上述问题, 第三代合作伙伴计划 (3GPP )和 3GPP2标准 组织都提出了一种基于 IMS实体进行锚定控制的方案,分别检测用户在 两个网络的注册、 会话状态, 并根据用户的注册、 会话状态进行用户的 路由及切换控制。图 1是现有技术基于 IMS实体进行锚定控制的组成结 构示意图, 如图 1所示, 在 IMS域和电路交换 ( CS )域新增一组功能 实体, 如下:
路由改向功能实体(FE-C ), 用于将 CS域呼叫改向至 IMS域进行呼 叫锚定控制;
CS域适配功能实体(FE-B ), 用于接收改向到 IMS域的 CS域呼叫并 将该 CS域呼叫转为 IMS域呼叫。 通常, 路由改向功能实体与 CS域适配功 能实体可以设置在同一实体中 , 本文将该实体合称为改向 /适配功能实
体, 二者间的接口属于内部接口; 也可以是两个独立实体。
域选择控制功能实体(FE-D ), 用于在 IMS域根据用户的注册状态、 呼叫状态等各种策略进行决策, 并控制呼叫路由到选定的接续域;
域切换控制功能实体(FE-A ), 用于在 IMS域锚定呼叫, 切换发生 时进行切换控制。
拜访移动交换中心( VMSC )通过 gsmSCF, 与 FE-C交互, 在实际组 网中, 通常 gsmSCF与 FE-C合设在同一实体中, 因此, 可以认为 VMSC 和 FE-C直接交互。
在图 1所示的架构下, 图 2是现有技术双模用户终端在 CS域发起呼叫 的流程图, 如图 2所示, 包括以下步骤:
步骤 200: 双模用户终端(UE )在 CS域向 VMSC发送呼叫建立消息。 该呼叫建立消息中携带有被叫号码即呼叫对端号码( Called Party Number ) , 以及主叫用户所在位置区小区标识( Cell ID ) 。
步骤 201: VMSC收到呼叫建立消息后 ,触发初始检测点( IDP, Initial Detect Point ) 消息并发送给路由改向功能实体。
在 CDMA网络中, 上述 IDP消息为始呼请求(ORREQ, Origination Request ) 消息, 本文将 IDP消息和 ORREQ消息合称为智能触发消息。
按照移动网络增强型逻辑定制应用 (CAMEL )协议, 在 IDP消息 中应该携带有 Called Party Number、 主叫用户所在位置区小区标识, 现 有技术中没有使用 Cell ID, 因此图 2中未示出。
步骤 202: 路由改向功能实体分配 IMS域路由号码(IMRN ) , 并将 分配的 IMRN携带在连接 ( CONNECT )消息中返回给 VMSC, 从而将呼 叫改向到 IMS域。
步骤 203: VMSC将接收到的 IMRN及 Called Party Number携带在初始 消息(IAM ) 中, 并发送给 IMS域媒体网关控制功能(MGCF ) 实体。
本步骤中, VMSC将呼叫路由到了 IMS域入口网关。
步骤 204: MGCF实体构造会话发起协议 ( SIP )会话请求( INVITE ) 消息, 将接收到的 IMRN及 Called Party Number携带在该 INVITE消息中, 并发送给被叫用户归属 IMS域的入口询问呼叫会话控制功能( I-CSCF ) 实体。
此时 , INVITE消息中携带的 IMRN被作为被叫地址。
步骤 205: I-CSCF实体收到 INVITE消息后, 检测到被叫地址为 IMRN,将该 IMRN作为一个公有业务标识( PSI, Public Service Identity ) , 并将该 INVITE消息路由到 CS适配功能实体。
步骤 206: CS适配功能实体代替双模用户终端, 将接收到的 INVITE 消息发送给 IMS域中的服务呼叫会话控制功能(S-CSCF )实体, CS适配 功能实体代替双模用户终端在 IMS域发起会话请求。
步骤 207: S-CSCF将呼叫触发到用户所属的基本业务应用服务器 ( AS ) , 并将接收到的 INVITE消息发送给该基本业务 AS, 进行主叫业 务控制。
步骤 208: 基本业务 AS完成主叫业务控制后, 将 INVITE消息返回给 S-CSCF。
步骤 209: S-CSCF将会话路由到被叫侧网络, 继续后续呼叫。
如果双模用户终端签约有始呼限制业务, 比如限制所有出呼、 限制 国际长途、 限制国内长途等, 而对这些业务的控制是由 IMS域的基本业 务 AS实现的。 那么, 基本业务 AS应该有能力识别出用户当前呼叫的类 型是否满足限呼的条件, 才能进行相应的业务控制。
以基本业务 AS判断双模用户终端的呼叫是否为长途业务为例,基本 业务 AS需要知道发起呼叫的双模用户终端所在的位置信息 ,以及被叫用 户所归属的位置信息, 当这两个位置在同一个区域内时, 则判定不是长
途业务; 否则, 判定为长途业务, 此时, 若该双模用户终端签约有限制 长途业务, 那么基本业务 AS应该要拒绝本次呼叫。
然而, 在步骤 205中, 基本业务 AS接收到的 INVITE消息中仅携带有 被叫用户所归属的位置信息 - Called Party Number, 而没有发起呼叫的 双模用户终端所在的位置信息, 因此, 按照现有技术实现呼叫的方法, 基本业务 AS是不能判断出来自 CS域的发起呼叫的双模用户终端是否满 足签约的始呼限制业务的, 这样, 后续在 IMS域的呼叫不会根据该双模 用户终端的签约情况进行, 而是不论当前呼叫是否为限制呼叫均继续呼 叫, 或者按照 IMS域中的其它策略进行呼叫控制, 从而降低了业务控制 质量。
从现有在双网网络中实现呼叫的方法来看,双模用户终端在 CS域发 起呼叫时, IMS域不能获得该双模用户终端当前所在位置的位置信息, 使得基本业务 AS无法得到主叫用户当前所在位置的位置信息,也就不能 才艮据该主叫用户的签约情况, 正确对后续呼叫进行合理控制。
另外, 当用户在 IMS域发起域内呼叫时, 在 SIP:INVITE消息中会携 带接入网络信息( P- Access-Network-Info ) 头域, 该头域中携带有用户 所在位置区小区标识, 该头域会随呼叫消息传送到主叫用户归属 IMS域 和其它信任域。 当 INVITE消息传递到主叫侧的 P-CSCF, P-CSCF还会在 该 INVITE消息中添加拜访网络标识 P-Visited-Network-ID头域,该头域携 带 P-CSCF所在网络的网络标识。
在 IMS域内发起的呼叫中,虽然 P- Access-Network-Info头域中携带有 移动用户的位置信息, 但是, 由于该头域信息是用户终端自身填写的, 不能得到网络的信任, 因此, 目前并没有使用该头域携带的位置信息进 行位置相关业务的控制, 如始呼限制业务的控制。
综上所述, 按照现有技术的方法, IMS域中的基本业务 AS是不能判
断出发起呼叫的用户终端是否满足签约的始呼限制业务的 ,这样,在 IMS 域的后续呼叫不会根据该用户终端的签约情况进行, 从而降低了业务控 制质量。 发明内容
有鉴于此,本发明实施例的目的在于提供一种在 IP多媒体子***中 传递用户终端位置信息的方法, 能够获取可信的用户终端位置信息并传 递给 IMS域中的相关实体。
本发明实施例的另一目的在于提供一种在 IP 多媒体子***中传递 用户终端位置信息的装置, 能够获取可信的用户终端位置信息并传递给
IMS域中的相关实体。
为达到上述目的, 本发明的技术方案具体是这样实现的:
一种在 IP多媒体子*** IMS中传递用户终端位置信息的方法, 在
IMS域中设置用于获取用户终端位置信息的位置信息获取模块, 该方法 包括:
所述位置信息获取模块将获得的用户终端位置信息携带在会话发 起协议 SIP信令中, 发送给 IP多媒体子*** IMS域。
一种在 IP多媒体子*** IMS中传递用户终端位置信息的装置, 该 装置至少包括: 位置信息获取模块, 该位置信息获取模块接收用户终端 位置信息 , 并将该用户终端位置信息携带在会话发起协议 SIP信令中 , 通过该装置中的现有的 SIP信令接口模块发送给 IP多媒体子*** IMS 网络。
由上述技术方案可见, 本发明实施例中, 在 IMS域中设置用于获取 用户终端位置信息的位置信息获取模块, 该位置信息获取模块将获得的 用户终端位置信息携带在^舌发起协议 SIP信令中 ,发送给 IP多媒体子系
统 IMS域, 实现了获取可信的用户终端位置信息并传递给 IMS域中的相 关实体。
附图简要说明
图 1是现有技术基于 IMS实体进行锚定控制的组成结构示意图; 图 2是现有技术双模用户终端在 CS域发起呼叫的流程图; 图 3是本发明方法的流程图;
图 4是本发明实施例一的流程图;
图 5是本发明实施例二的流程图。 实施本发明的方式
本发明实施例中, 在 IMS域中设置用于获取用户终端位置信息的位 置信息获取模块, 该位置信息获取模块将获得的用户终端位置信息携带 在^舌发起协议 SIP信令中, 发送给 IP多媒体子*** IMS域。
为使本发明的目的、 技术方案及优点更加清楚明白, 以下参照附图 并举较佳实施例, 对本发明进一步详细说明。
图 3是本发明方法的流程图, 包括以下步骤:
步骤 300:在 IMS域中设置用于获取用户终端位置信息的位置信息获 块。
该位置信息获取模块可以设置在路由改向功能实体中、 或者 CS适 配实体中、 或者改向 /适配功能实体、 或者 IMS域中的与注册或呼叫相 关的实体如应用服务器/ MGCF/P-CSCF等中、 或者为一独立实体。
位置信息获取模块可以从接收到的呼叫建立请求中获取所述用户 终端位置信息, 也可以从归属用户服务器(HSS )或网关移动定位中心
( GLMC )等位置信息管理实体中获取用户终端位置信息。 这里所说的 用户终端位置信息至少包括主叫用户终端的位置信息。
如果位置信息获取模块设置在路由改向功能实体或改向 /适配功能 实体中,按照 CAMEL协议, VMSC在发送给拜访网络中的路由改向功能 实体的 IDP消息中, 携带有 Called Party Number, 主叫用户所在位置区小 区标识, 路由改向功能实体会保存接收到的 Cell ID, 并分配 IMRN; 拜 访网络中的 CS适配功能实体通过与路由改向功能实体交互,利用路由改 向功能实体分配的 IMRN获取与该 IMRN对应的主叫用户所在位置区小 区标识;
如果位置信息获取模块设置在 CS适配实体或改向 /适配功能实体 中, 路由改向功能实体接收到 IDP消息后, 将接收到的 IDP消息中携带的 Called Party Number及主叫用户所在位置区小区标识发送给 CS适配功能 实体, 并请求 CS适配功能实体分配 IMRN; CS适配功能实体保存 IDP消 息中携带的 Called Party Number及主叫用户所在位置区小区标识, 分配 与该保存的 Called Party Number及主叫用户所在位置区小区标识对应的 即与本次呼叫对应的 IMRN , 并将分配的 IMRN返回给改向功能实体; 如果位置信息获取模块设置在路由改向功能实体中、或者 CS适配实 体中、 或者改向 /适配功能实体、 或者为一独立实体, 可以直接向 HSS或 GMLC等位置服务器进行查询, 以获取用户终端位置信息。 若向 HSS查 询 , 则通过 Sh接口上的用户数据请求( User Data Request ) 消息查询 , HSS中如果存在用户终端位置信息, 则直接返回, 如果不存在, 则可以 进一步向位置服务器查询, 比如通过任意时刻查询 (ATI, Any Time Interrogation ) 消息向 VMSC或 SGSN进行查询等。 需要说明的是, 这里 强调的是通过本发明的位置信息获取模块获取用户终端位置信息的一 种手段, 具体如何获取属于现有技术, 这里不再赘述。
如果位置信息获取模块设置在 MGCF中 , MGCF接收来自用户终端 的呼叫建立请求后, 如果该呼叫建立请求中携带有主叫用户所在位置区 小区标识, 则将该主叫用户所在位置区小区标识作为主叫用户的位置信 息; 如果该呼叫建立请求中未携带主叫用户所在位置区小区标识, 则 MGCF可以从 IMS域中的位置服务器或归属用户服务器中获得该用户 终端的位置信息, 并作为主叫用户的位置信息。
步骤 301 : 所述位置信息获取模块将获得的用户终端位置信息携带 在^舌发起协议 SIP信令中, 发送给 IP多媒体子*** IMS域。
在 IMS域的后续呼叫中, IMS域可以利用获得的主叫用户终端的位 置信息在 IMS域中进行业务控制 , 比如 IMS域中的基本业务 AS根据该主 叫用户的位置信息, 判断出发起呼叫的用户终端是否满足签约的始呼限 制业务等。
本发明方法通过预先设置的位置信息获取模块获取主叫用户终端 的位置信息, 并将主叫用户的位置信息传递给 IMS域中的相关实体, 进 一步实现了根据该用户终端的位置信息 , 对在 IMS域后续呼叫进行合理 控制, 提高了业务控制质量。
下面以用户在 CS域向 IMS域发起呼叫为例, 结合实施例具体描述本 发明方法的实现, 图 4是本发明实施例一的流程图, 具体实现包括以下 步骤:
步骤 400: UE在 CS域向 VMSC发送呼叫建立消息。
该呼叫建立消息中携带有被叫号码即 Called Party Number, 以及用 户当前位置区小区标识。
步骤 401: VMSC收到呼叫建立消息后, 触发 IDP消息并发送给路由 改向功能实体。
按照 CAMEL协议, 在 IDP消息中应该携带有 Called Party Number,
主叫用户所在位置的 Cell ID。
在 CDMA网络中, 上述 IDP消息为始呼请求(ORREQ, Origination Request ) 消息, 本文将 IDP消息和 ORREQ消息合称为智能触发消息。
上述步骤 400 ~步骤 401与现有技术的具体实现完全一致。
步骤 402 ~步骤 403: 路由改向功能实体保存接收到的 Cell ID、 分配 与该 Cell ID对应的 IMRN, 并将分配的 IMRN携带在 CONNECT消息中返 回给 VMSC, 从而将呼叫改向到 IMS域;
步骤 404: VMSC将接收到的 IMRN及 Called Party Number携带在 IAM 中, 并发送给 IMS域 MGCF实体。
本步骤中 , VMSC根据接收到的 IMRN将呼叫路由到了 IMS域入口网 关。
步骤 405: MGCF实体构造 SIP:INVITE消息 , 将接收到的 IMRN及
Called Party Number携带在该 INVITE消息中, 并发送给被叫用户归属
IMS域的入 O I-CSCF实体。
此时 , INVITE消息中携带的 IMRN被作为被叫地址。
步骤 406: I-CSCF实体收到 INVITE消息后, 检测到被叫地址为
IMRN, 将该 IMRN作为一个 PSI, 并将该 INVITE消息路由到 CS适配功能 实体。
步骤 407 ~步骤 408: CS适配功能实体利用 IMRN与路由改向实体之 间交互, 以获取主叫用户当前位置区小区标识。
CS适配功能实体将接收到的 IMRN携带在询问 (QUERY ) 消息中, 并发送给路由改向功能实体, 路由改向功能实体将该 IMRN对应的 Cell ID携带在响应 (RESPONSE ) 消息中, 返回给 CS适配功能实体。
步骤 409: CS适配功能实体将接收到的 Called Party Number替换 INVITE消息中的 IMRN , 并将获得的 Cell ID携带在 SIP:INVITE消息中,
代替 UE在 IMS域向 S-CSCF实体发起新的会话。
CS适配功能实体可以使用该 SIP:INVITE消息中的现有的 P- Access-Network-Info头域或其它某个头域来携带 Cell ID。 另夕卜, 为了 区分于普通 IMS域始发会话, CS适配功能实体还可以通过该 SIP:INVITE 消息中的现有的 P- Visited-Network-ID头域或其它某个头域携带 CS域始 发呼叫标识, 以标识此呼叫是从 CS域始发的, 这样 IMS域业务控制实体 可以信任上述位置信息。
步骤 410 ~步骤 411 : S-CSCF实体将呼叫触发到用户所属的应用服务 器如基本业务 AS, 并将接收到的 INVITE消息发送给该基本业务 AS, 进 行主叫业务控制, 基本业务 AS完成主叫业务控制后, 将 INVITE消息返 回给 S-CSCF实体。
本步骤中, 基本业务 AS收到 INVITE消息后, 根据该 INVITE消息中 的 P-Access-Network-Info头域携带的主叫用户当前位置区小区标识, 获 知用户所在位置, 并根据 Called Party Number获知被叫归属位置, 从而 可以进行始呼限制业务控制。
如果无需进行始呼业务限制 , 基本业务 AS完成主叫业务控制之后, 将会话返回给 S-CSCF实体; 如果需要进行始呼业务限制, 则返回拒绝响 应。
步骤 412: S-CSCF实体将会话路由到被叫侧网络, 或向主叫发送拒 绝信息。
本步骤中 , 在 SIP:INVITE消息中携带 Called Party Number。
而可以将在步骤 409中携带的主叫用户当前位置区小区标识删除。 需要说明的是, 是否删除主叫用户当前位置区小区标识由运营商自行决 定, 删除是为了不让其它运营商网络获得主叫位置信息。
从实施例一可见,拜访网络中的 CS适配功能实体通过与路由改向功
能实体交互,利用路由改向功能实体分配的 IMRN获取与该 IMRN对应的 主叫用户所在位置的 Cell ID, 并代替 UE, 将获得的 Called Party Number 及 Cell ID携带在 SIP:INVITE消息中, 在 IMS域向被叫用户发起在 IMS域 的会话。 而在后续 IMS域的呼叫中,基本业务 AS根据该 INVITE消息中携 带的主叫用户当前位置区小区标识, 获知用户所在位置, 并 Called Party Number获知被叫归属位置,从而使得 IMS域根据主叫用户的签约情 况, 正确实现了后续呼叫控制。
图 5是本发明实施例二的流程图 , 具体实现包括以下步骤: 步骤 500: UE在 CS域向 VMSC发送呼叫建立消息。
该呼叫建立消息中携带有被叫号码即 Called Party Number, 以及用 户当前位置区小区标识。
步骤 501: VMSC收到呼叫建立消息后, 触发 IDP消息并发送给路由 改向功能实体。
按照 CAMEL协议, 在 IDP消息中应该携带有 Called Party Number, 主叫用户所在位置的 Cell ID。
在 CDMA网络中, 上述 IDP消息为源始请求(ORREQ, Origination Request ) 消息。
上述步骤 500 ~步骤 501与现有技术的具体实现完全一致。
步骤 502: 路由改向功能实体向 CS适配功能实体申请 IMRN。
路由改向功能实体将接收到的 Called Party Number及主叫用户所在 位置的 Cell ID携带在 QUERY消息中, 发送给 CS适配功能实体。
步骤 503: CS适配功能实体分配 IMRN, 保存接收到的 Called Party Number及主叫用户所在位置的 Cell ID。
该分配的 IMRN与保存的 Called Party Number及主叫用户所在位置 的 Cell ID是对应的。
步骤 504: CS适配功能实体将 IMRN携带在 RESPONSE消息中返回给 路由改向功能实体。
步骤 505: 路由改向功能实体将接收到的 IMRN返回给 VMSC, 从而 将呼叫改向到 IMS域。
步骤 506: VMSC将接收到的 IMRN携带在 IAM中 , 并发送给 IMS域 MGCF实体, VMSC根据接收到的 IMRN将呼叫路由到了 IMS域入口网 关。
步骤 507: MGCF实体构造 SIP:INVITE消息, 将接收到的 IMRN携带 在该 INVITE消息中, 并发送给被叫用户归属 IMS域的入口 I-CSCF实体。
此时 , INVITE消息中携带的 IMRN被作为被叫地址。
步骤 508: I-CSCF实体收到 INVITE消息后, 检测到被叫地址为 IMRN, 将该 IMRN作为一个 PSI, 并将该 INVITE消息路由到 CS适配功能 实体。
步骤 509: CS适配功能实体利用接收到的 IMRN, 将与该 IMRN对应 的 Called Party Number及主叫用户所在位置的 Cell ID携带在该 INVITE消 息中,并将 IMRN更换为 Called Party Number,代替 UE在 IMS域向 S-CSCF 实体发起新的 ^舌。
同样, CS适配功能实体可以使用该 SIP:INVITE消息中的现有的 P- Access-Network-Info头域或其它某个头域来携带 Cell ID。 另夕卜, 为了 区分于普通 IMS域始发会话, CS适配功能实体还可以通过该 SIP:INVITE 消息中的现有的 P-Visited-Network-ID头域或其它某个头域携带 CS域始 发呼叫标识, 以标识此呼叫是从 CS域始发的。
步骤 510 ~步骤 511 : S-CSCF实体将呼叫触发到用户所属的基本业务 AS, 并将接收到的 INVITE消息发送给该基本业务 AS, 进行主叫业务控 制, 基本业务 AS完成主叫业务控制后, 将 INVITE消息返回给 S-CSCF实
体。
本步骤中, 基本业务 AS收到 INVITE消息后, 根据该 INVITE消息中 的 P-Access-Network-Info头域携带的主叫用户当前位置区小区标识, 获 知用户所在位置, 并根据 Called Party Number获知被叫归属位置, 从而 可以进行始呼限制业务控制, 还可以在该 INVITE消息中的现有
P-Visited-Network-ID头域或其它某个头域中携带位置信息的可信性标 识,用于标识该 INVITE消息中携带的主叫用户当前位置区小区标识是否 可信。
如果无需进行始呼业务限制 , 基本业务 AS完成主叫业务控制之后, 将会话返回给 S-CSCF实体; 如果需要进行始呼业务限制, 则返回拒绝响 应。
步骤 512: S-CSCF实体将会话路由到被叫侧网络, 或向主叫发送拒 绝信息。
本步骤中 , 在 SIP:INVITE消息中携带 Called Party Number。
而可以将 SIP:INVITE消息中携带的主叫用户当前位置区小区标识 删除。 需要说明的是, 是否删除主叫用户当前位置区小区标识由运营商 自行决定, 删除是为了不让其它运营商网络获得主叫位置信息。 。
从实施例二可见,拜访网络中的 CS适配功能实体接收到来自改向功 能实体的请求, 保存请求中携带的 Called Party Number及主叫用户所在 位置区小区标识, 并分配与保存的 Called Party Number及主叫用户所在 位置区小区标识对应的 IMRN; CS适配功能实体将获得的 Called Party Number及 Cell ID携带在 SIP:INVITE消息中 ,代替 UE在 IMS域向被叫用户 发起在 IMS域的会话。 而在后续 IMS域的呼叫中, 基本业务 AS根据该 INVITE消息中携带的主叫用户当前位置区小区标识, 获知用户所在位 置, 并根据 Called Party Number获知被叫归属位置, 从而使得 IMS域根据
主叫用户的签约情况, 正确实现了后续呼叫控制。
除此之外, 当用户在 IMS域发起域内呼叫或进行注册时, 本发明的 处理方法为: 在用户终端发起的 SIP^ 舌 /注册请求中可能会将自身的位 置信息携带在 P- Access-Network-Info头域中,当设置在 IMS网络中某实体 如 P-CSCF或某 AS中的位置信息获取模块, 收到该 SIP^ 舌 /注册请求后, 查询位置服务器, 得到用户真实位置信息; 然后将获得的真实位置信息 携带在该 S I P会话 /注册请求中, 可以是用获得的真实位置信息替换 P-Access-Network-Info头域中的内容, 也可以使用另外一个头域或参数 来携带获得的真实位置信息; 之后, 将 SIP信令继续传递给 IMS域中的下 一个实体。 这样, IMS域的后续实体都可以从 SIP信令中获取该用户真实 位置信息并利用该用户的真实位置信息进行业务控制, 所说的业务可以 是始呼限制业务, 或漫游限制业务, 或其它业务。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的 保护范围, 凡在本发明的精神和原则之内所做的任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1.一种在 IP多媒体子*** IMS中传递用户终端位置信息的方法, 其特征在于,在 IMS域中设置用于获取用户终端位置信息的位置信息获 取模块, 该方法包括:
所述位置信息获取模块将获得的用户终端位置信息携带在会话发 起协议 SIP信令中, 发送给 IP多媒体子*** IMS域。
2. 根据权利要求 1 所述的方法, 其特征在于, 所述获取用户终端 位置信息的方法为: 从接收到的信令中获取, 或从位置服务器或归属用 户服务器中获得。
3. 根据权利要求 1 所述的方法, 其特征在于, 该方法具体包括以 下步骤:
A. 所述位置获取模块从接收到的智能触发消息中获取用户的位置 信息;
B. 将获得的用户的位置信息携带在 SIP信令中发送给 IMS域。
4. 根据权利要求 3 所述的方法, 其特征在于, 所述位置信息获取 模块设置在路由改向功能实体中, 所述步骤 A具体包括:
All.拜访移动交换中心 VMSC接收来自用户终端的携带有用户的 位置信息的呼叫建立请求;
A12. 该 VMSC 将接收到用户的位置信息发送给所述改向功能实 体, 路由改向功能实体保存该用户的位置信息;
A13. 该路由改向功能实体分配与本次呼叫对应的 IP多媒体子*** IMS 或路由号码 IMRNo
5. 根据权利要求 4所述的方法, 其特征在于, 所述步骤 B具体包 括:
Bll. 所述路由改向功能实体将分配的 IMRN返回给所述 VMSC, 所述 VMSC根据接收到的 IMRN将呼叫路由至 IMS域入口网关;
B12. 所述 IMS域入口网关利用接收到的 IMRN构造会话发起协议 SIP 会话请求消息, 并经 IMS 域的入口询问会话呼叫会话控制功能 I-CSCF实体路由至 IMS域中的 CS适配功能实体;
B13. 该 CS适配功能实体利用接收到的 IMRN与所述路由改向功能 实体交互, 获取与该 IMRN对应的用户的位置信息;
B14. 该 CS适配功能实体将获得的用户的位置信息携带在该 SIP会 话请求消息中发起呼叫。
6. 根据权利要求 3 所述的方法, 其特征在于, 所述位置信息获取 模块设置在 CS适配功能实体中, 所述步骤 A具体包括:
A21. VMSC接收来自用户终端的携带有用户的位置信息的呼叫建 立请求;
A22. 该 VMSC将接收到的用户的位置信息发送给改向功能实体, 路由改向功能实体将接收到的用户的位置信息发送给 CS 适配功能实 体, 并请求分配 IMRN;
A23. 该 CS适配功能实体保存接收到用户的位置信息,并分配与该 本次呼叫对应的 IMRN。
7. 根据权利要求 6所述的方法, 其特征在于, 所述步骤 B具体包 括:
B21. 所述 CS适配功能实体将分配的 IMRN经路由改向功能实体发 送给所述 VMSC, 所述 VMSC根据接收到的 IMRN将呼叫路由至 IMS 或入口网关;
B22. 所述 IMS域入口网关利用接收到的 IMRN构造 SIP ^舌请求 消息, 并经 IMS域的入口 I-CSCF实体路由至所述 CS适配功能实体;
B23. 所述 CS适配功能实体将自身保存的、与接收到的 IMRN对应 的用户的位置信息携带在所述 SIP会话请求消息中发起呼叫。
8. 根据权利要求 1 所述的方法, 其特征在于, 所述位置信息获取 模块设置在 IMS域媒体网关控制功能 MGCF中 ,所述步骤 A具体包括:
A31. 所述 MGCF接收来自用户终端的呼叫建立请求后, 将该呼叫 建立请求消息中携带的用户所在位置区小区标识作为用户的位置信息; 或者从位置服务器或归属用户服务器中获得该用户终端的位置信息 , 并 作为用户的位置信息。
9. 根据权利要求 1 所述的方法, 其特征在于, 该方法具体包括以 下步骤:
a. 所述位置信息获取模块接收到 SIP会话 /注册请求后,向位置服务 器或 HSS请求 SIP会话 /注册的用户终端的位置信息;
b. 将获得的用户终端的位置信息携带在该 SIP会话 /注册请求中, 发送给 IMS域中的下一个实体。
10. 根据权利要求 5、 7或 9所述的方法, 其特征在于, 该方法还 包括:
所述 IMS域中的应用服务器 AS根据接收到的用户的位置信息 , 进 行业务控制。
11. 根据权利要求 10所述的方法, 其特征在于, 所述业务为始呼 限制业务, 或漫游限制业务, 或其它业务。
12. 根据权利要求 1 ~ 9任一项所述的方法, 其特征在于, 所述用 户的位置信息为用户所在位置区小区标识。
13. 根据权利要求 1 ~ 9任一项所述的方法, 其特征在于, 所述用 户 的位置信息携 带在所述 SIP 会话 /注册请求消 息的 P- Access-Network-Info头域或其它头域中。
14. 根据权利要求 13所述的方法, 其特征在于, 在所述 SIP会话 请求消息的现有 P-Visited-Network-ID 头域或其它头域中, 进一步携带 有:
CS域始发呼叫标识, 用于标识呼叫始发于 CS域;
或位置信息的可信性标识 ,用于标识所述 SIP会话请求消息中携带 的主叫用户当前位置区小区标识是否可信。
15. 根据权利要求 4或 6所述的方法, 其特征在于, 所述路由改 向功能实体和 CS适配功能实体为独立实体, 或设置在同一实体中并分 别作为两个功能模块。
16. 一种在 IP多媒体子*** IMS 中传递用户终端位置信息的装 置, 其特征在于, 该装置至少包括: 位置信息获取模块, 该位置信息获 ^莫块接收用户终端位置信息, 并将该用户终端位置信息携带在会话发 起协议 SIP信令中, 通过该装置中的现有的 SIP信令接口模块发送给 IP 多媒体子*** IMS网络。
17. 根据权利要求 16所述的装置, 其特征在于, 所述装置为路由 改向功能实体, 所述位置信息获取模块设置在路由改向功能实体;
或者, 所述装置为电路域 CS适配实体, 所述位置信息获取模块设 置在 CS适配实体中;
或者, 所述装置为改向 /适配功能实体, 所述位置信息获取模块设置 在改向 /适配功能实体中;
或者, 所述装置为 IMS域中与注册或呼叫相关的实体, 所述位置信 息获取模块设置在 IMS域中与注册或呼叫相关的实体中;
或者, 所述装置为一独立实体。
18. 根据权利要求 17所述的装置 ,其特征在于 , 所述 IMS域中与 注册或呼叫相关的实体包括: 应用服务器、 或 MGCF、 或 P-CSCF。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07721730A EP2034681A4 (en) | 2006-06-15 | 2007-06-13 | METHOD AND SYSTEM FOR TRANSMITTING SUBSCRIBER TERMINATION LOCATION INFORMATION IN IP MULTIMEDIA SUBSYSTEM |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200610087154.4A CN101090562B (zh) | 2006-06-15 | 2006-06-15 | 在ip多媒体子***中传递用户终端位置信息的方法及装置 |
CN200610087154.4 | 2006-06-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007147357A1 true WO2007147357A1 (fr) | 2007-12-27 |
Family
ID=38833081
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070109 WO2007147357A1 (fr) | 2006-06-15 | 2007-06-13 | Procédé et système de transmission d'informations d'emplacement de terminaison d'abonné dans un sous-système multimédia ip |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2034681A4 (zh) |
CN (1) | CN101090562B (zh) |
WO (1) | WO2007147357A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011076088A1 (en) * | 2009-12-23 | 2011-06-30 | Huawei Technologies Co.,Ltd. | System and method for event driven operations in a communications system |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101217796B (zh) * | 2008-01-09 | 2011-10-26 | 中兴通讯股份有限公司 | 一种ip多媒体子***集中控制业务中终呼的实现方法 |
RU2513914C2 (ru) * | 2009-06-18 | 2014-04-20 | Телефонактиеболагет Л М Эрикссон (Пабл) | Способы и устройства в телекоммуникационной сети |
CN103516750A (zh) * | 2012-06-25 | 2014-01-15 | 北京智慧风云科技有限公司 | 云端服务器共享位置信息的***及云端服务器 |
CN105992150B (zh) * | 2015-03-03 | 2019-02-05 | ***通信集团公司 | 一种用户位置的获取方法及装置 |
EP3409033A4 (en) * | 2016-01-29 | 2019-07-10 | Telefonaktiebolaget LM Ericsson (publ) | METHOD AND APPARATUS FOR FACILITATING LOCATION BASED SERVICES AND / OR LOCATION-BASED POLICY CONTROL |
CN107809497B (zh) * | 2016-09-09 | 2021-01-15 | 中国电信股份有限公司 | 号码资源池管理方法和*** |
CN108156577A (zh) * | 2016-12-02 | 2018-06-12 | 中兴通讯股份有限公司 | 基于VoLTE的用户终端UE计费方法、装置及*** |
CN109150799A (zh) * | 2017-06-16 | 2019-01-04 | ***通信集团公司 | 一种获取被叫位置信息的方法及装置 |
CN114866507A (zh) * | 2022-06-13 | 2022-08-05 | 厦门亿联网络技术股份有限公司 | 通话方法、通话装置及电子设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030154400A1 (en) * | 2002-02-13 | 2003-08-14 | Tarja Pirttimaa | Method and network element for providing secure access to a packet data network |
US20040117657A1 (en) * | 2002-07-10 | 2004-06-17 | Bajko Gabor | Method for setting up a security association |
WO2004071104A2 (en) * | 2003-02-10 | 2004-08-19 | Nokia Corporation | Mobile network having ip multimedia subsystem (ims) entities and solutions for providing simplification of operations and compatibility between different ims entities |
CN1756242A (zh) * | 2004-09-30 | 2006-04-05 | 华为技术有限公司 | Ip多媒体子***中利用电路交换承载业务的***及方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003094563A1 (en) * | 2002-05-06 | 2003-11-13 | Nokia Corporation | System and method for handling sessions of specific type in communication networks |
EP1435749A1 (en) * | 2002-12-30 | 2004-07-07 | Evolium S.A.S. | Location based call barring |
EP1680938A1 (en) * | 2003-10-17 | 2006-07-19 | Nortel Networks Limited | Method for obtaining location information for emergency services in wireless multimedia networks |
-
2006
- 2006-06-15 CN CN200610087154.4A patent/CN101090562B/zh not_active Expired - Fee Related
-
2007
- 2007-06-13 EP EP07721730A patent/EP2034681A4/en not_active Ceased
- 2007-06-13 WO PCT/CN2007/070109 patent/WO2007147357A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030154400A1 (en) * | 2002-02-13 | 2003-08-14 | Tarja Pirttimaa | Method and network element for providing secure access to a packet data network |
US20040117657A1 (en) * | 2002-07-10 | 2004-06-17 | Bajko Gabor | Method for setting up a security association |
WO2004071104A2 (en) * | 2003-02-10 | 2004-08-19 | Nokia Corporation | Mobile network having ip multimedia subsystem (ims) entities and solutions for providing simplification of operations and compatibility between different ims entities |
CN1756242A (zh) * | 2004-09-30 | 2006-04-05 | 华为技术有限公司 | Ip多媒体子***中利用电路交换承载业务的***及方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2034681A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011076088A1 (en) * | 2009-12-23 | 2011-06-30 | Huawei Technologies Co.,Ltd. | System and method for event driven operations in a communications system |
US9071921B2 (en) | 2009-12-23 | 2015-06-30 | Futurewei Technologies, Inc. | System and method for event driven operations in a communications system |
Also Published As
Publication number | Publication date |
---|---|
EP2034681A4 (en) | 2010-01-06 |
CN101090562B (zh) | 2012-05-02 |
EP2034681A1 (en) | 2009-03-11 |
CN101090562A (zh) | 2007-12-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9544338B2 (en) | Call handling for IMS registered user | |
WO2007147357A1 (fr) | Procédé et système de transmission d'informations d'emplacement de terminaison d'abonné dans un sous-système multimédia ip | |
EP1770949A2 (en) | Method and communication system for circuit switch users accessing IP multimedia subsystem | |
CN101156395B (zh) | 一种跨域路由控制方法 | |
CN101175248B (zh) | Ip多媒体子***集中控制业务的紧急呼叫***及方法 | |
WO2006063536A1 (fr) | Procede et systeme pour maintenir la continuite d'une session | |
EP2073479A1 (en) | Method and system for call continuity | |
US8380211B2 (en) | CS domain call terminating system, method and network device | |
WO2007036147A1 (fr) | Procede et systeme d'etablissement d'un appel initial dans le service de la continuite de service vocal | |
US9055397B2 (en) | Method for usage of VPLMN infrastructure by an HPLMN to terminate an IMS session set up for a roaming user | |
WO2007079688A9 (fr) | Procede, appareil et systeme de mise en communication de l'utilisateur appele | |
EP1974519A1 (en) | Method and apparatus for providing ims services to circuit-switched controlled terminals | |
WO2007124643A1 (fr) | Procédé, système et appareil d'optimisation d'ancrage en continuité d'appel vocal | |
KR20060113284A (ko) | 이종망간에 음성 서비스를 지원하는 아이엠에스 시스템 및그에 따른 호 설정 방법 | |
WO2008017237A1 (fr) | Procede, systeme et serveur d'application pour le routage d'appel de domaine circuit vers un domaine paquet | |
WO2012079451A1 (zh) | 用户漫游方法及ics增强网络 | |
WO2009092245A1 (zh) | 多媒体会话连续性业务的起呼方法 | |
CN101330455B (zh) | Ip多媒体子***集中业务用户不可及前转实现方法 | |
JP5165075B2 (ja) | Imsに登録されたユーザのための呼処理 | |
WO2008049320A1 (fr) | Procédé, système et dispositif de transport | |
KR20080069881A (ko) | 인터넷 프로토콜 멀티미디어 서브시스템에서 음성 호 연속서비스 제공 방법 및 시스템 | |
WO2009015532A1 (fr) | Procédé destiné à transmettre une communication d'une mise hors tension d'un utilisateur avec un service centralisé de sous-système multimédia ip | |
WO2007016863A1 (fr) | Procédé et système de commande d'un trajet d'acheminement de session |
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: 07721730 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007721730 Country of ref document: EP |