WO2008046313A1 - Procédé de resélection pour un terminal d'utilisateur appelé dans un service de redirection, et système et appareil correspondants - Google Patents

Procédé de resélection pour un terminal d'utilisateur appelé dans un service de redirection, et système et appareil correspondants Download PDF

Info

Publication number
WO2008046313A1
WO2008046313A1 PCT/CN2007/002972 CN2007002972W WO2008046313A1 WO 2008046313 A1 WO2008046313 A1 WO 2008046313A1 CN 2007002972 W CN2007002972 W CN 2007002972W WO 2008046313 A1 WO2008046313 A1 WO 2008046313A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
pnm
called
service request
user terminal
Prior art date
Application number
PCT/CN2007/002972
Other languages
English (en)
Chinese (zh)
Inventor
Dongming Zhu
Xiaoyan He
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008046313A1 publication Critical patent/WO2008046313A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of redirection technologies in a communication system, and in particular, to a personal network management
  • PNM Personal Network Management
  • the Universal Mobile Telecommunications System (UMTS) core network is divided into Circuit Switched (CS) domains and packets.
  • CS Circuit Switched
  • IMS IP Multimedia Subsystem
  • the CS domain is used to provide users with connections for circuit-type services, including the Mobile Switching Center (MSC) and the Gateway Mobile Switching Center (GMSC).
  • MSC Mobile Switching Center
  • GMSC Gateway Mobile Switching Center
  • the MSC is used to complete the switching and signaling control functions of the circuit-switched service; the MSC used by the GMSC to perform the mobile subscriber route addressing function in the network may be configured or divided with the MSC.
  • the PS domain is used to provide a connection for a packet type service to a user, including: a GPRS Support Node (GSN) and a Breakout Gateway (BG).
  • the GSN is used to complete the transmission of the packet of the packet service user.
  • the GSN includes a Serving GPRS Support Node (SGSN) and a GPRS Gateway Support Node (GGSN).
  • the SGSN is used to provide the connection between the core network and the wireless access system, complete the mobility management and session management functions of the packet data service, and manage the mobile and communication services of the mobile user in the mobile network.
  • the GGSN acts as a mobile communication system and other public.
  • the interface between the data networks also has the function of querying location information. Both SGSN and GGSN provide charging information.
  • BG is used to finish Interworking between two general packet radio packets (General Packet Radio Service, GPRS) ensures the security of network interworking.
  • GPRS General Packet Radio Service
  • IMS is a subsystem superimposed on the existing packet domain in the Wideband Code Division Multiple Access (WCDMA) network added in the fifth version of 3GPP.
  • WCDMA Wideband Code Division Multiple Access
  • the packet domain is used for its upper layer control signaling and media transmission.
  • the bearer channel, the session initiation protocol (SIP) is introduced as the service control protocol, and the SIP is simple, easy to expand, and the media combination is convenient.
  • the service control is separated from the bearer control to provide rich multimedia services.
  • the functional entities include a Call Session Control Function (CSCF) entity that controls functions such as user registration and session control, and an Application Server (AS) that provides various business logic control functions. Centrally manages user subscription data.
  • CSCF Call Session Control Function
  • AS Application Server
  • HSS Home Subscriber Server
  • MGCF Media Gateway Control Function
  • the user passes the current local proxy CSCF (Proxy-CSCF, P-CSCF). ) access
  • the IMS, session and service trigger control and the service control interaction with the AS are performed by the home domain service CSCF ( Serving-CSCF, S-CSCF) of its place of registration.
  • Serving-CSCF Serving-CSCF, S-CSCF
  • the HSS is the most important database for each user in the IMS domain. It stores all the information related to the subscription. It is used to support the processing of calls and sessions by various network entities, including: user identification, number, and addressing information. Security information; user's location information and user's description information.
  • a home network can have one or more HSSs. Depending on the number of mobile subscription users, the capacity of the network equipment, and the specific networking conditions, the HSS provides a business hall interface for user data maintenance, that is, adding, modifying, and deleting user subscriptions. Data, etc. At the same time, the HSS supports the user data download of the HSS and the interface between the CSCF (Interrogating-CSCF, I-CSCF)/S-CSCF and the interface Sh between the HSS and the AS.
  • CSCF Interrogating-CSCF
  • I-CSCF Interrogating-CSCF
  • S-CSCF Session Control Function
  • the Home Location Register was the entity that holds the user's CS domain and PS domain data.
  • the HLR supports the interface between the HLR and the GMSC MSC, the interface between the HLR and the VLR, the HLR and the SGSN.
  • the interface between the HLR and the GGSN is generally considered to be a superset of the HLR. The two are combined.
  • the HSR is embedded in the HSS.
  • the registered message is delivered to the HLR/HSS, and the user's subscription data is downloaded therefrom for subsequent business operations, and the AS can subscribe to the data of the IMS domain through the interface between the HSS and the AS and can Part of the CS, PS domain data, but in the actual network layout does not rule out the HLR and HSS separation.
  • a user may have multiple devices at the same time to run communication services.
  • These devices can be circuit domain devices, IMS domain devices, PSTN terminals, and they can also belong to different operators. Telecommunications are provided by different operators. Services, while these devices may have different capabilities, which limit the application of certain devices or specific media types, such as video and image support.
  • PNM a service called PNM, which is user-centric and centrally manages the same user's device or the device that can be used by the user, so that the user can fully utilize the terminal or terminal peripherals of different capabilities to obtain more. Good business experience.
  • the main focus is on the management of user equipment (UE) in the personal network (PN), and provides two types of services: redirection service and private network service between UEs in the PN.
  • the redirection service means that the user specifies one or more specific UEs in the PN in advance. If multiple UEs are specified, the UEs have different priorities, and all subsequent service requests sent to any UE in the PN are terminated. These specified specific UEs, for example, redirect all video call requests destined for any UE within the PN to the UE with the largest screen within the PN.
  • Figure 1 shows the implementation architecture of the PNM service in the IMS domain.
  • the HSS has an interface with the PNM AS, which can directly interact.
  • the PNM AS has an interface with the S-CSCF and can directly interact.
  • the UE has an interface with the PNMAS and can directly interact.
  • the IMS domain user terminal acts as a called party, and the redirecting service process includes the following steps: Step 201: The I-CSCF of the called home domain receives the service request.
  • Step 202 The I-CSCF of the called home domain sends a request for querying the S-CSCF currently serving the called UE to the HSS of the called UE home domain.
  • Step 203 After receiving the query request, the HSS returns an S-CSCF address currently serving the called UE to the I-CSCF.
  • Step 205 After receiving the forwarding service request, the S-CSCF detects the iFC with the matching condition.
  • Step 206 The S-CSCF sends a redirect service request to the PNM AS according to the iFC.
  • Step 208 The PNM AS returns the address of the UE with the highest priority as the new target address information to the S-CSCF.
  • Step 209 The S-CSCF server initiates a service request to the new target UE according to the new target address information.
  • Figure 3 shows the implementation architecture of the PNM service in the CS domain.
  • the HSS has an interface with the gsmSCF and the GMSC, and can directly interact with each other.
  • the mobile switching center (VMSC) has an interface with the GMSC and can directly interact.
  • the gsmSCF interacts with the UE indirectly through other network elements.
  • the redirecting service process includes the following steps: Step 401: The GMSC of the called gateway office receives a call request carrying the called UE number information; Step 402: The GMSC will acquire the called A request for routing information of the UE is sent to the HSS;
  • Step 403 The HSS returns a subscription information of the called UE's Customized Application for Mobile Network Enhanced Logic (Camel) to the GMSC, where the T-CSI related to the PNM redirect service is included;
  • Camel Customized Application for Mobile Network Enhanced Logic
  • Step 404 The GMSC sends a redirect service request to the PNM server according to the gsm service control function (gsmSCF) address included in the T_CSI, and completes the service trigger.
  • gsmSCF gsm service control function
  • Step 405 The PNM server performs the redirection service logic, selects a UE with the highest priority specified by the user, and sends a route redirection message to the GMSC, where the number information of the redirected UE is changed, that is, the redirection number.
  • Step 406 The GMSC initiates a call request to the new called party according to the redirected number.
  • the PNM server receives the redirect service request and performs the redirect service logic, it selects the highest priority ⁇ specified by the user as the redirection number. Code, but if the UE with the highest priority cannot successfully connect to this service request, the processing ends. Therefore, all service requests sent to any UE in the PNM are terminated to the UE with the highest priority specified by the user, and once the UE with the highest priority cannot successfully connect to the service request, the service request is The processing ends unsuccessfully, which will largely reduce the session connection rate.
  • the object of the present invention is to provide a method, a system, and a device for reselecting a called user terminal in a PNM redirection service, which are used to solve the problem that the session connection rate is reduced due to the failure of the called user terminal to connect to the service request in the prior art.
  • the PNM server After receiving the redirect service request from the first PNM service triggering entity, the PNM server selects the first called user terminal from the priority list to perform service connection;
  • the second called user terminal is reselected from the priority list to continue the service connection.
  • the embodiment of the present invention further provides a system for reselecting a called user terminal in a personal network management PM redirection service, where the system includes: a PNM server and one or more PNM service triggering entities; the PNM service triggering entity, configured to receive services Requesting, triggering the PNM server to execute the redirect service logic;
  • the PNM server is configured to perform redirection service logic, and select a first called user terminal to perform service connection from the priority list. When determining that the current service connection fails, select the second called user terminal to continue from the priority list. Conduct business continuity.
  • the embodiment of the invention further provides a redirection service triggering device, the device comprising:
  • a first detecting unit configured to detect a service request processing result of the called user terminal
  • the forwarding unit is configured to send a service processing failure response to the PNM server when the first detecting unit detects that the called user terminal fails to process the service request.
  • the embodiment of the present invention further provides a personal network management PNM server, where the PNM server includes: a connection unit, configured to select a called user terminal to perform service connection from the priority list when determining that the current service connection fails.
  • the embodiment of the invention further provides a method for selecting a called user terminal in a PNM redirection service in a personal network, the method comprising the following steps:
  • the service domain selection server SDS of the circuit switched CS domain After receiving the domain selection request for the CS domain called service request addressed to the served user, the service domain selection server SDS of the circuit switched CS domain determines whether to forward the called service request to the IMS domain for PNM weight according to the condition. Targeted business processing;
  • the SDS determines that the called service request needs to be routed to the IMS domain for PNM redirection service processing, it indicates that the called service request is routed to the IMS domain, otherwise, the connection of the called service continues in the CS domain. .
  • the embodiment of the invention further provides a system for reselecting a called user terminal in a personal network management PNM redirection service, the system comprising:
  • a service domain selection server the server is located in the circuit switched CS domain, and is configured to determine, according to the condition, whether to route the called service request to the domain selection request for the CS domain called service request addressed to the served user.
  • the IMS domain performs PNM redirection service processing. If it is determined that the called service request needs to be routed to the IMS domain for PM redirection service processing, it indicates that the called service request is routed to the IMS domain. Otherwise, the indication continues to be in the CS.
  • the domain performs the connection of the called service;
  • a PNM service triggering entity where the entity is located in an IMS domain, and after receiving the called service request, triggering the PNM server to perform a redirect service logic;
  • PNM server which is located in the IMS domain and is used to perform redirected business logic.
  • the embodiment of the present invention further provides a service domain selection server, where the server is located in a circuit switched CS domain, and the server includes:
  • the routing unit is configured to: after receiving the domain selection request for the CS domain called service request sent to the served user, determine, according to the condition, whether to forward the called service request to the IMS domain for PNM redirection service processing, such as ⁇ judging that the called service request needs to be routed to the IMS domain for PNM redirection service processing, indicating that the called service request is routed to the IMS domain, otherwise, the indication continues The connection of the called service is performed in the cs domain.
  • the PNM server in the present invention determines that the currently called user terminal cannot successfully connect to the service request, and reselects a called user terminal to continue the service connection. This method greatly improves the session connection. rate. DRAWINGS
  • FIG. 2 is a flow chart of implementing a PNM redirection service in an IMS domain in the prior art
  • FIG. 3 is a schematic diagram of a PNM service implementation architecture of a CS domain in the prior art
  • FIG. 4 is a flow chart of implementing a PNM redirection service in a CS domain in the prior art
  • FIG. 5 is a specific flowchart of the method implementation in the present invention.
  • FIG. 6 is a specific flowchart of Embodiment 1 of the present invention.
  • FIG. 7 is a specific flowchart of Embodiment 2 of the present invention.
  • FIG. 8 is a specific flowchart of Embodiment 3 of the present invention.
  • FIG. 9 is a specific flowchart of Embodiment 4 of the present invention.
  • FIG. 10 is a specific flowchart of Embodiment 5 of the present invention.
  • FIG. 12 is a specific flowchart of Embodiment 6 of the present invention.
  • Figure 13 is a schematic structural view of the system of the present invention.
  • FIG. 14 is a schematic structural diagram of a redirect service triggering apparatus according to the present invention.
  • FIG. 15 is a schematic structural diagram of a PNM server according to the present invention.
  • Figure 16 is a schematic structural view of the system of the present invention.
  • FIG. 17 is a schematic structural diagram of a service domain selection server according to the present invention.
  • FIG. 18 is a schematic structural diagram of a transfer redirection trigger device according to the present invention. detailed description
  • the calling user side initiates a service to any called user terminal in the personal network PN
  • the service request reaches the PNM service triggering entity S-CSCF or the GMSC of the network to which the called user terminal belongs
  • the entity sends a redirect request to the PNM AS
  • the PNM AS performs the redirect service logic according to the request, from the priority list. Selecting a called user terminal to perform service connection. If the called user terminal cannot successfully connect to the service request, the PNM AS selects a called user terminal to continue the service from the priority list when detecting that the current service connection fails. Continued.
  • Step 501 After receiving the service request of the calling party, the PNM service triggering entity of the network to which the called user terminal belongs triggers the PNM server to perform the redirect service logic, and the PNM server selects a called user terminal from the priority list to perform service connection.
  • the implementation process of this step is:
  • the first PNM service triggering entity After receiving the service request, the first PNM service triggering entity sends a redirect service request to the PNM server; the PNM server selects a called user terminal from the priority list, and sends the service request to the selected network of the called user terminal.
  • the PNM service triggering entity; the PNM service triggering entity sends the service request to the selected called user terminal.
  • the specific implementation of the foregoing process may have two solutions.
  • the solution 1 includes the following steps: Step 5011: After receiving the service request from the calling side, the first PNM service triggering entity sends a redirect service request to the PNM server.
  • Step 5012 After receiving the redirect service request, the PNM server determines whether the redirect information is included. If yes, go to step 5015. Otherwise, go to step 5013.
  • Step 5013 The PNM server selects a called user terminal from the priority list. If the called user terminal is the called user terminal included in the calling side service request, the PNM server sends a service request to the first PNM service triggering entity. Step 5016: If the called user terminal does not include the called user terminal included in the calling party service request, the PNM server triggers the service request message including the redirecting information and the called user terminal address information by using the first PNM service. The PNM service triggering entity sent by the entity to the network to which the called user terminal belongs;
  • Step 5014 The PNM service triggering entity sends a redirect service request to the PNM server, where Containing the redirect information and the called user terminal address information, returning to step 5012;
  • Step 5015 The PNM server returns a service request to the PNM service triggering entity of the network to which the called user terminal belongs.
  • Step 5016 The PNM service triggering entity sends the service request message to the called user terminal.
  • Option 2 includes the following steps:
  • Step 50111 After receiving the service request of the calling side, the first PNM service triggering entity sends a redirect service request to the PNM server.
  • Step 50112 The PNM server selects a called user terminal from the priority list. If the called user terminal is the called user terminal included in the service request, the PNM server sends a service request to the first PNM service triggering entity. Step 50114: If the called user terminal is not the called user terminal included in the service request, the PNM server sends a service request message including the redirect information and the selected called user terminal address information to the selected one.
  • Step 50113 The PNM service triggering entity receives the service request, and judges that the PNM server is no longer triggered according to the redirect information included in the request.
  • Step 50114 The PNM service triggering entity sends the service request message to the selected called user terminal.
  • Step 502 When the PNM server determines that the current service connection fails, the selected user terminal is selected from the priority list to continue the service connection.
  • the process in which the PNM server selects a called user terminal to continue the service connection from the priority list includes: the PNM server selects a called user terminal from the priority list, and sends the service request to the PNM service of the network to which the called user terminal belongs. Triggering an entity; the PNM service triggering entity sends the service request to the selected called user terminal.
  • Step 5021 First, the PNM server determines whether there is a called user terminal that is currently in the active state that has not been selected in the priority list. If not, the PNM server ends the current service request processing; if yes, the PNM server Selecting a called user terminal from the priority list, and sending a service request message including the redirecting information and the called user terminal address information to the PNM service triggering entity of the network to which the called user terminal belongs;
  • the PNM server may send a service request message to the network of the called user terminal by using the first PNM service triggering entity in this step.
  • the PNM server controls the received message according to the Proxy Server mode in the SIP protocol.
  • the PNM server determines whether the received service processing failure message corresponds to the redirect service request in step 5011 for the first time, and if corresponding, the PNM server The service processing failure message is controlled according to the B2BUA mode; otherwise, the service processing failure message is controlled according to the Proxy Server mode;
  • the second PNM service triggering entity is the PNM service triggering entity of the network to which the user terminal that fails the service connection in step 502
  • the PNM server may send the service request message to the PM service triggering entity of the network to which the called user terminal belongs by using the second PNM service triggering entity, and if the selected user terminal belongs to the PNM of the network to which the called user terminal belongs in step 5013 or step 5021.
  • the service triggering entity is the S-CSCF of the IMS domain, and the PM servers in steps 501 and 502 control the received message according to the B2BUA mode.
  • the PNM server sends a service request message to the PNM service triggering entity of the network to which the called user terminal belongs through the first PNM service triggering entity, and if the first PNM service triggering entity is the GMSC of the CS domain,
  • the PNM server sends a dynamic detection point to the first PNM service triggering entity.
  • the PNM server sends a service request message to the PNM service of the network to which the called user terminal belongs through the second PNM service triggering entity.
  • step 5011, step 5014 or step 5022 is the GMSC of the CS domain, then when performing step 5013, step 5015 or step 5023, the PNM server proceeds to The PNM service triggering entity sends a dynamic detection point;
  • Step 5022 The PNM service triggering entity sends a redirect service request to the PNM server, where the redirect information and the called user terminal address information are included.
  • Step 5023 The PNM server returns a service request to the PNM service triggering entity of the network to which the called user terminal belongs.
  • Step 5024 The PNM service triggering entity sends the service request message to the called user terminal.
  • Option 2 includes the following steps:
  • Step 50211 The PNM server selects a called user terminal from the priority list, and sends a service request message including the redirecting information and the called user terminal address information to the PNM service triggering entity of the network to which the called user terminal belongs;
  • the PNM server Before performing this step, the PNM server also needs to determine whether there is a currently-called activated user terminal that has not been selected in the priority list. If not, the PNM server ends the current service request processing; The PNM server selects a called user terminal from the priority list, and sends a service request message including the redirecting information and the called user terminal address information to the PNM service triggering entity of the network to which the called user terminal belongs;
  • the PNM server may send a service request message to the network of the called user terminal by using the first PNM service triggering entity in this step.
  • the PNM service triggering entity and if the first PNM service triggering entity is an S-CSCF of the IMS domain, the PNM server in step 50112 and step 50211 controls the received message according to the B2BUA mode in the SIP protocol; when this step is PNM The server sends a service request message to the PNM service triggering entity of the network to which the called user terminal belongs by using the first PNM service triggering entity, and if the first PNM service triggering entity is the GMSC of the CS domain, when performing step 50112, the PNM Server to the first A PNM service triggering entity sends a dynamic detection point.
  • Step 50212 The PNM service triggering entity that receives the service request returned by the PNM server determines that the PNM server is no longer triggered according to the redirect information included in the request, and sends the service request message to the selected called user terminal.
  • step 501 and step 502 after the called user terminal receives the service request message, the service connection is performed. If the service connection fails, the called user terminal does not answer or is in a busy or inaccessible state, and the called user terminal belongs to The PNM service triggering entity of the network sends a service processing failure message sent by the called user terminal or other network element in the network or according to internal logic to determine that the called user terminal does not successfully process the service request, and then sends the service request to the PNM server.
  • the message that the service processing fails, the sending process includes the following two situations:
  • the PNM server sends a service request message to the PNM service triggering entity of the network to which the called user terminal belongs by using the first PNM service triggering entity, in step 5021 or step 50211, if the first PNM service triggering entity is the GMSC of the CS domain, The PNM service triggering entity of the network to which the called user terminal belongs determines that the called user terminal does not successfully process the current service request, and then sends a service processing failure message to the first PNM service triggering entity, and the first PNM service triggering entity receives the service processing failure response.
  • the event that the service connection fails is reported to the PNM server; if the first PNM service triggering entity is the S-CSCF of the IMS domain, the PNM service triggering entity of the network to which the called user terminal belongs determines that the called user terminal is not successfully processed. After the service request, the first PNM service triggering entity sends a service processing failure message, and the first PNM service triggering entity sends the response to the PNM server after receiving the service processing failure message;
  • the second PNM server triggers the weight of the network to which the called user terminal belongs in step 5013 or step 5021.
  • the directional service triggering entity is the GMSC of the CS domain
  • the PNM service triggering entity of the network to which the called user terminal belongs determines that the called user terminal fails to process the service request, and reports the event that the service connection fails to the PNM server according to the dynamic detection point;
  • the PNM service triggering entity of the network to which the called user terminal belongs in step 5013 or step 5021 is the S-CSCF of the IMS domain, the PNM of the network to which the called user terminal belongs
  • the service triggering entity determines that the called user terminal does not successfully process the service request and sends a service processing failure message to the PM server.
  • step 502 the PNM server determines that the service connection fails according to the received service processing failure message or the service connection failure event.
  • the PM server sends a service request message to the PNM service triggering entity of the network to which the called user terminal belongs by using the first PNM service triggering entity, in step 5013, step 5021, step 50112,
  • the PNM server may restart the preset timer.
  • the PNM server receives the service failure and success message according to the PNM server before the timer expires, or the PNM server receives the service before the timer expires. Processing the failure message to determine that the service connection failed;
  • the PNM server When the PNM server forwards the service request message to the PNM service triggering entity of the network to which the called user terminal belongs by using the second PNM service triggering entity, the PNM server restarts the preset in step 5013, step 5015 or step 5023.
  • the timer of the PNM server in step 502 is that the PNM server does not receive the service processing failure and success message before the timer expires, or the PNM server receives the service processing failure message before the timer expires to determine that the service connection fails. .
  • the redirect information when the service request adopts the session initiation protocol SIP, the redirect information may be added by expanding the SIP message.
  • the redirecting information when the user message is added to the user to indicate the UUI cell or other parameters, or by adding the forwarding cause value in the forwarding information, when the service request adopts the existing protocol as the ISUP, the redirecting information may pass.
  • the UUI carries or is implemented by increasing the value of the forward cause in the forwarding information.
  • the PNM service triggering entity When the service request carries the redirect information by using the extended SIP message, and if the PNM service triggering entity of the network to which the called user terminal belongs in step 50112 and step 50211 is the S-CSCF of the IMS domain, step 50113 or step 50212
  • the PNM service triggering entity compares the redirect information in the received service request message with the initial filtering rule (iFC) that triggers the PNM server in the S-CSCF, and determines that the PNM server is no longer triggered when the matching fails.
  • iFC initial filtering rule
  • step 5013 step 5021, step 50112, step 50211, the called user terminal is selected according to the priority order from the currently activated active user terminal that has not been selected in the priority list, or from the priority list.
  • the called user terminal currently in the active state in the priority list of the called user terminal is randomly selected.
  • the present invention also provides a method for reselecting a called user terminal in a personal network management PNM service.
  • the PNM server is deployed only in the IMS domain, and the service domain selection server (SDS) of the circuit domain is received for sending
  • SDS service domain selection server
  • the device determines whether to forward the called service request to the IMS domain for PNM redirection service processing, and determines that the called service request is required.
  • the service domain selection server may determine Determining whether the redirected information is included in the domain selection request to determine whether the called service request needs to be routed to the IMS domain for PNM redirect service processing, and when the request does not include the redirect information, the called service is Request routing to the IMS domain.
  • Step 1101 After receiving the domain selection request for the CS domain called service request sent to the served user, the SDS determines, according to the condition, whether to route the called service request to the IMS domain.
  • the SDS may only route the called service request to the IMS domain according to the PNM server deployment in the IMS domain; or further, according to the redirected information included in the called service request, the called service request is not routed to The IMS domain sends the called service request to the called user terminal through the GMSC of the network to which the called user terminal belongs in the called service request, and the called party uses the called The terminal is connected to the service.
  • Step 1102 After receiving the called service request sent by the SDS route, the PNM service triggering entity (the first PNM service triggering entity) of the IMS domain triggers the PNM server to perform the redirect service logic, and the PNM server selects a called party from the priority list.
  • the user terminal performs service connection.
  • this step includes:
  • Step S21 After receiving the called service request sent by the SDS route, the first PNM service triggering entity triggers the PNM server to perform the redirect service logic according to the redirected information included in the called service request.
  • the first redirecting service triggering entity passes the ADS and the visited mobile switching center (VMSC) The called service request is sent to the called user terminal.
  • VMSC visited mobile switching center
  • Step S22 When the PNM server executes the redirect service logic, select a called user terminal from the priority list, and if the selected called user terminal is the called user terminal included in the received redirect service request, the PNM server Sending the called service request including the redirecting information to the first PNM service triggering entity, performing step S24; if the called user terminal is not the called user terminal included in the redirected service request, the PNM service will contain the modified Sending the called service request of the information and the selected called user terminal address information to the GMSC or S-CSCF of the network to which the called user terminal belongs;
  • the ⁇ server sends the called service request including the redirect information and the selected called i3 ⁇ 4 terminal address information to the GMSC or S-CSCF of the network to which the called user terminal belongs, through the first service triggering entity.
  • the PNM server controls the reception message according to the B2BUA mode in the SIP protocol.
  • Step S23 After receiving the called service request, the GMSC or the S-CSCF sends the called service request to the selected called user terminal, and the called user terminal performs service connection and jumps out of the process;
  • Step S24 When the first PNM service triggering entity receives the called service request sent by the PNM server, the first PNM service triggering entity sends the called service request to the GMSC of the network to which the called user terminal belongs.
  • the called user terminal, the called user terminal performs service connection.
  • step S22 There are two cases for the reselection in step S22: One is that the called user terminal selected by the PNM server in step S22 is a CS domain terminal, and the PNM server in step S22 will contain the redirected information and the selected called user terminal.
  • the implementation process of sending the called service request message of the address information to the GMSC of the network to which the called user terminal belongs and the step S23 includes:
  • Step S221 The PNM server sends a called service request message including the redirecting information and the selected called user terminal address information to the first PNM service triggering entity.
  • Step S222 The first PNM service triggering entity sends a called service request containing the redirecting information to the GMSC of the network to which the selected CS domain terminal belongs;
  • Step S231 The GMSC detects that the CS domain terminal subscribes to the service domain selection service by querying, and sends the called service request to the SDS.
  • Step S232 The SDS includes the redirecting information according to the called service request, and returns the called service request message to the GMSC, where the GMSC sends the called service request to the CS domain terminal, where CS domain terminal performs service connection;
  • the SDS routes the called service request to the IMS domain, and after receiving the called service request, the redirect service triggering entity of the IMS domain includes the redirecting information according to the called service request, and is no longer
  • the PNM server is triggered to be sent, and the called service request is sent to the terminal through the ADS, and the terminal performs service connection.
  • the called user terminal selected by the PNM server in step S22 is an IMS domain terminal
  • the PNM server sends a called service request message including the redirecting information and the selected called user terminal address information to the PNM server in step S22.
  • the S-CSCF of the network to which the called user terminal belongs and the implementation process of step S23 specifically include:
  • Step S221 The PNM server sends, to the first PNM service triggering entity, a called service request that includes the redirected information and the selected called user terminal address information.
  • Step S222 The first PNM service triggering entity sends the called service to the S-CSCF of the network to which the selected IMS domain terminal belongs.
  • Step S231 The S-CSCF no longer triggers the PNM server according to the redirect information included in the request. And sending the called service request to the selected IMS domain terminal, where the IMS domain terminal performs service connection.
  • Step 1103 In the process of the service connection of the called user terminal, if the service connection fails, the PNM server selects a called user terminal from the priority list to continue the service connection when determining that the current service connection fails.
  • the PNM server determines whether the current service connection is successful.
  • the method is similar to the foregoing step 502. The difference is that when the terminal that fails to connect to the service is a CS domain terminal, the PNM service triggering entity of the IMS domain sends a failure response to the PNM server of the IMS domain.
  • the PNM server selects a called user terminal from the priority list to continue the service connection according to the failure response.
  • step S221, step S222, step S231, and step S232 If the called user terminal selected by the PNM server is a CS domain terminal, the subsequent processing flow is the same as step S221, step S222, step S231, and step S232. If the called user terminal selected by the PNM server is an IMS domain terminal, the subsequent processing flow is the same as step S221, step S222, and step S231.
  • the called user terminal selects in priority order from the currently activated active user terminal that has not been selected in the priority list, or from the called user terminal.
  • the called user terminal currently active in the priority list is randomly selected.
  • the redirect information in the service request is added by adding a new header field or a new parameter by extending the SIP message, or by increasing the forwarding cause value in the forwarding information;
  • the redirect information is implemented by adding the user to the user to indicate the UUI cell or other parameters in the message by expanding the CAP protocol or by increasing the forwarding cause value in the forwarding information;
  • the service request adopts the existing protocol as ISUP the redirected information is carried by the UUI or by increasing the forwarding cause value in the forwarding information.
  • User A has signed up for the PNM service. He has five active user ends, a, b, c, d, and f.
  • the UEs are arranged in the order of priority from high to low, the network adopts a policy of local reselection, and the CS domain terminal UEe of another user B first initiates a call to the CS domain terminal f of user A, where UEa is an IMS domain terminal.
  • the UEb is a CS domain terminal, and the UEc is an IMS domain terminal.
  • the UEa and the UEb cannot successfully establish a call due to busy and no response, respectively, and the PNM server performs reselection according to the priority list until the UEc successfully establishes the call.
  • Step 601 The GMSCf receives the service request message IAM (f);
  • Step 602 The GMSCf sends an SRI message for obtaining the UEf routing information to the HSSf.
  • Step 604 The GMSCf triggers the CAEML service of the called side according to the T_CSI data, and sends a redirect request message InitialDP to the PNM AS.
  • Step 605 The PNM AS determines that the current PNM redirection service triggers the first trigger because the PNM AS triggers the PNM redirection caused by the PNM redirection.
  • the highest priority UEa The highest priority UEa;
  • Step 606 The PNM AS sends a dynamic detection point EDP-R for detecting the call processing result to the GMSCf and a service request message Connect(a) containing the UEa address information, where the message includes that the current call redirection is caused by the redirect service.
  • Route redirection information which can be carried by the redirectionlnformation parameter or by adding a cell to the Connect (a) message through the CAP protocol, and the PNM server simultaneously monitors the start timer of the call processing result;
  • Step 607 The GMSCf sends a service request message IAM (a) requesting to query the S-CSCFa address information to the MGCFa, where the message includes route redirection information indicating that the call redirection caused by the redirect service has occurred in the current call, the information It can be carried in the UUI in the ISUP protocol, or in the redirectionlnformation of the ISUP, or by adding a new value of the cell in the IAM (a) message;
  • Step 608 The MGCFa queries the address information of the S-CSCFa, and forwards the service request message INVITE(a) to the S-CSCFa, where the message includes the route modification indicating that the call has been redirected.
  • To information which can be carried by adding a new forwarding cause value in the history-info header field in the SIP protocol or by adding a new header field or a new parameter by extending the SIP protocol;
  • Step 609 Since UEa is also a network element registered in the PN, the S-CSCFa sends a redirect request message INVITE (a) to the PNM AS according to the iFC;
  • Step 610 PNM AS: According to the message type (INVITE) and the route redirection information that is included in the redirection of the current call, it is determined that the current trigger is not triggered by the first call to the PNMAS, and the UE is no longer used. Choice, does not change the routing information of this business request;
  • Step 611 The PNM AS returns the service request message INVITE ( a ) to the S-CSCFa, and restarts the timer for monitoring the call processing result;
  • Step 612 The S-CSCFa forwards the service request message INVITE ( a ) to the UEa;
  • Steps 613 to 614 The UEa is currently in a busy state, and the UEa sends a service request to process the unsuccessful 486 response message, and the response message returns to the PNM AS according to the same path as the original signaling but in the opposite direction. Stop timer counting;
  • Step 615 The PNM AS matches the original service request message according to the message type (486) and parameters in the message, such as CalllD, and reselects a UEb having a lower priority than the UEa, and starts a timer for monitoring the call processing result;
  • Step 616 The PNM AS sends a service request message INVITE(b) containing the UEb address information and the route redirection information caused by the redirection service to the S-CSCFa.
  • Step 617 The PNM AS sends the PNMb to the MGCFb.
  • a service request message INVITE (b) requesting to query the GMSCb address information, the message carrying the route redirection information indicating that the redirected service has been redirected by the current call, the information may be in the history-info of the SIP protocol. Add a new forwarding cause value in the header field to implement or extend the SIP protocol, and add a new header field or new parameters to implement;
  • Step 618 The MGCFb performs a message type conversion, and sends a service request message IAM (b) to the GMSCb, where the route redirection information indicating that the current call has been redirected is carried, and the information may be carried or passed in the UUI in the ISUP protocol. Expand the ISUP protocol, add new cells in the IAM (b) message to carry this information or increase the value of the redirectioninformation by adding the reason to realise;
  • Steps 619 ⁇ 620 The GMSCb obtains the UEb routing information from the HSSb, and the HSSb returns the T-CSI data.
  • Step 621 The GMSCb sends a redirection request message intialDP to the PNMAS according to the T-CSI, where the route redirection information indicating that the current call has been redirected is carried, and the information may be carried or extended by the redirectionlnformation parameter in the InitialDP message. Adding a cell to the InitialDP message carries this information to implement;
  • Step 622 The PNMAS sends the dynamic redirecting point EDP-R to the GMSCb according to the routing redirect information of the redirected routing in the initial DP, and does not perform the selection of other priority UEs to monitor whether the UEb is busy or not answered or not. And the event, and restarting the timer for monitoring the result of the call processing;
  • Step 623 The PNM AS sends a service request message to the GMSCb indicating to continue to call the UEb. Continue (b);
  • Step 624 The GMSCb obtains routing information of the UEb.
  • Step 625 The GMSCb sends a service request message IAM (b) to the UEb, and the message is sent to the end office, and the end office sends a service request message to the UEb.
  • IAM service request message
  • Step 626 The assignment circuit is completed. After the UEb rings, the UEb does not respond, and the end office sends a service request to the GMSCb to process the unsuccessful Rel response message.
  • Step 627 The GMSCb reports the event to the PNM AS according to the dynamic detection point, that is, sends an EventReportBCSM response message that the service request processing is unsuccessful to the PNM AS.
  • Step 628 The PNM AS reselects a UEc that is lower than the current called priority, and starts a timer for monitoring the result of the call processing.
  • Step 629 The PNMAS sends a service request message Connect (c) and a dynamic detection point to the GMSCb, where the message includes the address information of the UEc and the route redirection information indicating that the current call is redirected;
  • Step 630 The GMSCb sends a service request message IAM (c) requesting to query the S-CSCFc address information to the MGCFc, where the route carries the route redirection information that can identify the redirection of the current call.
  • Step 631 The MGCFc obtains the address information of the S-CSCFc, and sends the converted service request message INVITE (c) to the S-CSCFc, where the message carries the converted route redirection information that can identify the redirection of the current call. ;
  • Step 632 The S-CSCFc sends a redirect request message INVITE (c) to the PNM AS according to the iFC of UEc;
  • Step 633 The PNMAS decides not to select other priority UEs according to the message type and the route redirection information carried therein;
  • Step 634 The PNMAS returns the service request message to the S-CSCFc, and restarts the timer.
  • Step 636 643 The PNMAS stops the timer and establishes a successful call between UEe and UEc.
  • User A has signed up for the PNM service. He has five active user terminals UEs of a, b, c, d, f, and is arranged in descending order of priority.
  • the network adopts a strategy of reselection at the originating end.
  • the CS domain terminal UEe of another user B first initiates a call to the CS domain terminal f of the user A, where UEa is the IMS domain terminal, UEb is the CS domain terminal, UEc is the IMS domain terminal, and UEa and UEb are busy and no response respectively, respectively.
  • the call cannot be successfully established, and the PNM server reselects according to the priority list until UEc successfully establishes the call.
  • Step 701 The GMSCf receives the service request message IAM (f);
  • Step 702 The GMSCf sends an SRI message for obtaining the UEf routing information to the HSSf.
  • Step 704 The GMSCf triggers the CAEML service of the called side according to the T_CSI data, and sends a service request message InitialDP to the P M AS.
  • Step 705 The PNM server determines that the PNM redirect service triggers the first trigger, because the initial DPDP message does not include the route redirection information that is caused by the PNM redirection in the current call, and then reselects according to the priority list.
  • the current highest priority UEa Step 706:
  • the PNMAS sends a dynamic detection point EDP-R for detecting the call processing result and a service request message Connect(a) including the UEa address information to the GMSCf, where the message includes that the current call redirection is caused by the redirect service.
  • Route redirection information which may be carried by the redirectionlnformation parameter or by adding a cell in the Connect (a) message by extending the CAP protocol, and the PNM server starts a timer for monitoring the result of the call processing;
  • Step 707 The GMSCf sends a service request message IAM (a) requesting to query the address information of the S-CSCFa to the MGCFa, where the message includes route redirection information indicating that the redirected service has been redirected by the current call. It can be carried in the UUI in the ISUP protocol, or in the redirectionlnformation of the ISUP, or by adding a new value of the cell in the IAM (a) message;
  • Step 708 The MGCFa queries the address information of the S-CSCFa, and forwards the service request message INVITE(a) to the S-CSCFa, where the message includes the route redirection information indicating that the current call has been redirected.
  • a new forwarding cause value is added to the history-info header field in the SIP protocol to carry or be added by adding a new header field or a new parameter by extending the SIP protocol;
  • Step 709 Since UEa is also a network element registered in the PN, the S-CSCFa sends a redirect request message INVITE (a) to the PNM AS according to the iFC;
  • Step 710 The PNM AS determines, according to the message type (INVITE) and the route redirection information that is included in the redirection of the current call, and determines that the current trigger is not triggered by the first call to the PNM AS, and then the UE is not used. Choice, does not change the routing information of this business request;
  • Step 711 The PNM AS returns the service request message INVITE ( a ) to the S-CSCFa
  • Steps 713-714 The UEa is currently in a busy state, and the UEa sends a service request to process the unsuccessful 486 response message, and the response returns to the PNMAS according to the same path as the original signaling but in the opposite direction;
  • Step 715 The PNM AS responds according to the 486 response message.
  • the parameters such as CallldD and the matching initial service request determine that the UE reselection process is not required this time, and the 486 response cancellation steps 716 to 717 are sent to the S-CSCFa: the S-CSCFa sends the 486 response message to the MGCFa, and the MGCFa will Transmitting the message to the CS domain service request to process the unsuccessful Rel response message, and sending the message to the GMSCf;
  • Step 718 The GMSCf sends a service request to the PNM AS according to the dynamic detection point to process the unsuccessful response message EventReportBCSM;
  • Step 719 The PNM AS reselects a UEb with a lower priority than the UEa according to the priority list. At this time, the timer has not expired, and the PNMAS restarts the timer.
  • Step 720 The PNMAS sends a service request message Connect (b) containing the UEb address information to the GMSCf, where the message includes a route indicating that the call redirection is caused by the redirect service.
  • the message direction information which can be carried by the redirectionlnformation parameter in the Connect (b) message or by adding the cell in the Connect (b) message by extending the CAP protocol;
  • Step 721 The GMSCf sends a service request message IAM (b) to the GMSCb, and the message includes the route redirection information that identifies the redirection of the current call.
  • the information can be carried by the UU1 in the ISUP protocol, or by extending the ISUP.
  • the protocol adds a new cell carry in the IAM (b) message, or carries it in the redirectioninformation by adding a new forwarding cause value;
  • Steps 722 to 723 The GMSCb sends an SRI message for obtaining the routing information of the UEb to the HSSb, and the HSSb returns the T_CSI data.
  • Step 724 The GMSCb sends a redirect request message InitialDP to the PNM AS according to the T-CSI, where the route redirection information indicating that the current call has been redirected is included, and the information may be carried or passed in the redirectionlnformation parameter in the InitialDP message.
  • the extended CAP protocol adds cells in the InitialDP message to carry;
  • Step 725 The PNM AS does not perform the selection of other priority UEs according to the routing redirect information existing in the initial DP that identifies the current call.
  • Step 726 The PNM AS sends a service request message to the GMSCb indicating to continue to call the UEb. Continue (b);
  • Step 727 The GMSCb obtains the routing information of the UEb.
  • Step 728 The GMSCb sends a service request message IAM (b) to the UEb, and the message is sent to the end office, and the end office sends a service request message to the UEb.
  • Step 730 The GMSCb sends the Rel response message to the GMSCf.
  • Step 731 The GMSCf sends a service request to the PNM AS to process an unsuccessful EventReportBCSM response message.
  • Step 732 The PNM AS reselects a UEc with a lower priority than the UEb. At this time, the timer does not time out, and the timer is restarted.
  • Step 733 The PNM AS sends a service request message Connect (c) to the GMSCf, where the message includes the address information of the UEc and the route redirection information indicating that the current call is redirected;
  • Step 734 The GMSCb sends a service request message IAM (c) requesting to query the S-CSCFc address information to the MGCFc, where the route redirection information capable of identifying the redirection of the current call is carried.
  • Step 735 The MGCFc obtains the address of the S-CSCFc. And transmitting, to the S-CSCFc, the converted service request message INVITE (c), where the message carries the converted route redirection information capable of identifying that the call has been redirected;
  • Step 736 The S-CSCFc sends a redirect request message INVITE (c) to the PNM AS according to the iFC of the UEc.
  • Step 737 The PNM AS decides not to select other priority UEs according to the message type and the route redirection information carried therein;
  • Step 738 The PNM AS returns a service request message to the S-CSCFc
  • Step 739 The S-CSCFc forwards the service request message to the UEc.
  • Steps 740 to 750 The PNMAS stops the timer, establishing a successful call between UEe and UEc.
  • User A has signed the PNM service. He has five active user terminals UEs of a, b, c, d, f, and is arranged in descending order of priority.
  • the network adopts the policy of local reselection, and the other user.
  • the CS domain terminal UEe of B first initiates a call to the CS domain terminal f of the user A, where the UEa is the IMS domain terminal and the UEb is the CS domain terminal.
  • the PNM server timer expires, the UEa does not respond, and the PNM server performs the weight according to the priority list.
  • UEb is selected, the UEb call is not successfully established.
  • UEe actively terminates the call.
  • Step 801 The GMSCf receives the service request message IAM (f);
  • Step 802 The GMSCf sends an SRI message for obtaining the UEf routing information to the HSSf.
  • Step 804 The GMSCf triggers the CAEML service of the called side according to the T CSI data, and sends a service request message InitialDP to the PNM AS.
  • Step 805 The PNM server determines that the PNM redirect service triggers the first trigger, because the initial DPDP message does not include the route redirection information that is caused by the PNM redirection.
  • the current highest priority UEa The current highest priority UEa;
  • Step 806 The PNM AS sends a dynamic detection point EDP-R for detecting the call processing result to the GMSCf and a service request message Connect(a) including the UEa address information, where the message includes that the current call redirection is caused by the redirect service.
  • Route redirection information which may be carried by the redirectionlnformation parameter or by adding a cell in the Connect (a) message by extending the CAP protocol, and the PNM server starts the timer at the same time;
  • Step 807 The GMSCf sends a service request message IAM (a) requesting to query the address information of the S-CSCFa to the MGCFa, where the message includes the route redirection information indicating that the call redirection caused by the redirect service has occurred in the current call. It can be carried in the UUI in the ISUP protocol, or in the redirectionlnformation of the ISUP, or by adding a new value of the cell in the IAM (a) message;
  • Step 808 The MGCFa query obtains the address information of the S-CSCFa, and forwards the service request message INVITE(a) to the S-CSCFa, where the message includes the route redirection information indicating that the current call has been redirected, and the information may pass A new forwarding cause value is added to the history-info header field in the SIP protocol to carry or be added by adding a new header field or a new parameter by extending the SIP protocol;
  • Step 809 Since the UEa is also a network element registered in the PN, the S-CSCFa sends a redirect request message INVITE(a) to the PNM AS according to the iFC;
  • Step 810 The PNM AS determines, according to the message type (INVITE) and the route redirection information that indicates that the current call has been redirected, and determines that the current trigger is not the first time the current call is triggered to the PNMAS, and the UE is no longer performed. Select, do not change the routing information of this business request;
  • Step 811 The PNMAS returns the service request message INVITE ( a ) to the S-CSCFa, and restarts the timer.
  • Step 812 The S-CSCFa forwards the service request message INVITE(a) to the UEa;
  • Step 813 When the PNMAS still fails to receive any response message indicating whether the service processing is successful, the PNM server stops the timer timing, reselects a low priority UEb according to the priority list, and restarts the timer.
  • Steps 814-815 The PNM AS sends a disconnect request message Cancel to the S-CSCFa, and cancels the service request processing;
  • Step 816 The PNM AS sends a service request message INVITE(b) containing the UEb address information and the route redirection information caused by the redirection service to the S-CSCFa.
  • Step 817 The PNM AS sends the PNMb to the MGCFb.
  • a service request message INVITE (b) requesting to query the GMSCb address information, the message carrying the route redirection information identifying the call redirection caused by the redirection service of the current call, the information may be histoiy-info in the SIP protocol. Add a new forwarding cause value in the header field to implement or extend the SIP protocol, and add a new header field or new parameters to implement;
  • Step 818 The MGCFb performs message type conversion, and sends the service request message IAM (b) to the GMSCb, where the route redirection information indicating that the current call has been redirected is carried, and the information may be carried or passed in the UUI in the ISUP protocol.
  • the ISUP protocol is extended, and a new cell is added to the IAM (b) message to carry the information or by increasing the value of the redirectioninformation forwarding cause;
  • Steps 819 ⁇ 820 The GMSCb sends an SRJ message for obtaining the UEb routing information to the HSSb, and the HSSb returns the T_CSI data.
  • Step 821 The GMSCb sends a redirection request message intialDP to the PNM AS according to the T CSI data, where the route redirection information indicating that the current call has been redirected is carried, and the information is available. Carrying or extending the CAP protocol in the redirectionlnformation parameter in the InitialDP message, and adding the information in the InitialDP message carries the information to implement;
  • Step 822 The PNMAS sends the dynamic redirecting point EDP-R to the GMSCb according to the routing redirect information of the redirected call in the initial DP, and does not perform the selection of other priority UEs to monitor whether the UEb is busy or not answered or not. And events, and restart the timer;
  • Step 823 The PNM AS sends a service request message to the GMSCb indicating to continue to call the UEb. Continue (b);
  • Step 824 The GMSCb obtains the routing information of the UEb.
  • Step 825 The GMSCb sends a service request message IAM (b) to the UEb, and the message is sent to the end office, and the end office sends a service request message to the UEb.
  • IAM service request message
  • Steps 826 to 827 At this time, the UEe actively releases the current call for some reason, and the UEe sends a service request release message Rel to the GMSCf. After receiving the message, the GMSCf reports the event to the PNM AS according to the dynamic detection point by sending an initialDP message.
  • Step 828 The PNM AS stops the timer timing, and decides to initiate a release procedure to the called party.
  • Steps 829-830 The network control releases the called side, and the current service processing is terminated.
  • User A has signed the PNM service. He has three active user terminals UE, a, b, and f.
  • the UEa and UEb are activated and arranged in descending order of priority.
  • the network adopts the strategy of reselecting at the originating end.
  • the CS domain terminal UEe of another user B first initiates a call to the CS domain terminal f of the user A, where the UEa is the IMS domain terminal and the UEb is the CS domain terminal.
  • the UEa is unable to successfully connect the call due to being busy, and the PNM server according to the priority list.
  • the UEb is reselected.
  • the PNM server timer expires, no response is successfully received. If all the activated UEs have not successfully connected the call, the PNM server control initiates the call to both the calling party and the called party.
  • the call release process terminates the business process.
  • Step 901 The GMSCf receives the service request message IAM (f);
  • Step 902 The GMSCf sends an SRI message for acquiring the UEf routing information to the HSSf.
  • Step 904 The GMSCf triggers the CAEML service of the called side according to the T-CSI data, and sends a service request message InitialDP to the PNM AS.
  • Step 905 The PNM server determines that the PNM redirect service triggers the first trigger, because the initial DPDP message does not include the route redirection information that is caused by the PNM redirection.
  • the current highest priority UEa The current highest priority UEa;
  • Step 906 The PNM AS sends a dynamic detection point EDP-R for detecting the call processing result to the GMSCf and a service request message Connect(a) containing the UEa address information, where the message includes that the current call redirection is caused by the redirect service.
  • Route redirection information which may be carried by the redirectionlnformation parameter or by adding a cell in the Connect (a) message by extending the CAP protocol, and the PNM server starts the timer at the same time;
  • Step 907 The GMSCf sends a service request message IAM (a) requesting to query the address information of the S-CSCFa to the MGCFa, where the message includes route redirection information indicating that the redirected service has been redirected by the current call. It can be carried in the UUI in the ISUP protocol, or in the redirectionlnformation of the ISUP, or by adding a new value of the cell in the IAM (a) message;
  • Step 908 The MGCFa queries the address information of the S-CSCFa, and forwards the service request message INVITE(a) to the S-CSCFa, where the message includes the route redirection information indicating that the current call has been redirected.
  • a new forwarding cause value is added to the history-info header field in the SIP protocol to carry or be added by adding a new header field or a new parameter by extending the SIP protocol;
  • Step 909 Since UEa is also a network element registered in the PN, the S-CSCFa sends a redirect request message INVITE(a) to the PNMAS according to the iFC;
  • Step 910 The PNM AS determines, according to the message type (INVITE) and the route redirection information that indicates that the current call has been redirected, and determines that the current trigger is not triggered by the first call to the PNM AS, and then the UE is not performed. Choice, does not change the routing information of this business request;
  • Step 911 The PNM AS returns the service request message INVITE ( a ) to the S-CSCFa.
  • Step 912. The S-CSCFa forwards the service request message INVITE C a ) to the UEa;
  • Steps 913 914 914 UEa is currently in a busy state, UEa sends a service request to process an unsuccessful 486 response message, and the response returns to the PNMAS according to the same path as the original signaling but in the opposite direction;
  • Step 915 PNMAS according to the 486 response message
  • the parameters such as CalllD and the matching initial service request determine that the UE reselection process is not required, and the 486 response message is sent to the S-CSCFa.
  • Steps 916 to 917 The S-CSCFa sends the 486 response message to the MGCFa, and the MGCFa will Transmitting the message to the CS domain service request to process the unsuccessful Rel response message, and sending the message to the GMSCf;
  • Step 918 The GMSCf sends a service request to the PNM AS according to the dynamic detection point to process the unsuccessful response message EventReportBCSM;
  • Step 919 The PNM AS reselects a UEb with a lower priority than the UEa according to the priority list. At this time, the timer has not expired, and the PNMAS restarts the timer.
  • Step 920 The PNM AS sends a service request message Connect (b) with the UEb address information to the GMSCf, where the message includes the route redirection information indicating that the redirection of the call is caused by the redirection service, and the information can be accessed through Connect.
  • the redirectionlnformation parameter in the message carries or adds a cell carry in the Connect (b) message by extending the CAP protocol;
  • Step 921 The GMSCf directly sends a service request message IAM (b) to the GMSCb, where the message includes the route redirection information that identifies the redirection of the current call, and the information can be carried by the UUI in the ISUP protocol, or by extending the ISUP.
  • the protocol adds a new cell carry in the IAM (b) message, or carries it in the redirectioninformation by adding a new forwarding cause value;
  • Steps 922 to 923 The GMSCb sends an SRJ message for obtaining the UEb routing information to the HSSb, and the HSSb returns the T_CSI data.
  • Step 924 The GMSCb sends a redirect request message InitialDP to the PNM AS according to the T_CSI data, where the route redirection information indicating that the current call has been redirected is included, and the information may be carried in the redirectionlnformation parameter in the InitialDP message or extended.
  • the CAP protocol adds a cell to the InitialDP message to carry;
  • Step 925 The PNMAS is redirected according to the identifier existing in the initialDP. Routing redirection information, no other priority UE selection;
  • Step 926 The PNM AS sends a service request message to the GMSCb indicating to continue to call the UEb. Continue (b);
  • Step 927 The GMSCb obtains the routing information of the UEb.
  • Step 928 The GMSCb sends a service request message IAM (b) to the UEb, and the message is sent to the end office, and the end office sends a service request message to the UEb.
  • IAM service request message
  • Step 929 When the timer expires, the PNM AS still does not receive any response message that the service request is successfully processed.
  • the PNM AS determines that all activated UEs (UEa, UEb) have been traversed, and then decides to initiate a call to both parties. Terminated process processing;
  • Step 930 The PNM AS sends a Release Call message that is released by the service request to the GMSCf.
  • User A has signed the PNM service. He has three terminals a, b, and f, and all three terminals are IMS terminals. UEa and UEb are activated and arranged in descending order of priority. The network uses the originating end. Re-election strategy. The user B on the other side first initiates a call to the terminal f of the user A. If the UEa is unable to successfully connect the call, the PNM AS reselects the UEb according to the priority list. If the UEb successfully connects before the PNM AS timer expires, the session is successfully established.
  • Step 1001 The original called S-CSCF(f) receives the session establishment request INVITE message.
  • Step 1003 The S-CSCF(f) forwards the INVITE message to the PNM AS.
  • Step 1004 the PNM AS selects the current highest priority according to the user-set priority list.
  • Step 1005 the PNM AS sends a new service request INVITE message to the S-CSCF (f), and In this message, the route redirection information of the redirected call is added, and the information may be carried by adding a new forwarding cause value in the history-info header field in the SIP protocol or adding a new header field by extending the SIP protocol. Or a new parameter to carry, and the PNM AS starts a timer that monitors the result of the call processing;
  • Step 1006 The S-CSCF(f) forwards the service request INVITE message to the S-CSCF (a).
  • Step 1008 The S-CSCF (a) sends a service request INVITE message to the UEa.
  • Step 1009 1011 UEa is currently in a busy state, and UEa sends a service request to process an unsuccessful 486 response message, and the response returns to the PNM according to the same path as the original signaling but in the opposite direction.
  • Step 1012 after receiving the 486 response, the PNMAS checks that the previously set timer has not expired, and then reselects a UEb having a lower priority than the UEa according to the priority list;
  • Step 1013 The PNMAS sends a new service request INVITE message to the S-CSCF (f), and also adds the route redirection information that the call has been redirected in the message, in the same manner as step 1005, and the PNMAS restarts monitoring. Call processing a knotted timer;
  • Step 1014 the S-CSCF(f) forwards the service request INVITE message to the S-CSCF(b); Step 1015, although the UEb also subscribes to the PNM service, the S-CSCF(b) indicates that the current call occurs according to the INVITE message. After redirecting the route redirect information, it is determined that the iFC does not need to be triggered to send the INVITE to the PNMAS again;
  • Step 1016 The S-CSCF (b) sends a service request INVITE message to the UEb.
  • Steps 1017 ⁇ 1019 the UEb successfully returns a 200 response message, and the response returns to the PNM AS according to the same path as the original signaling but in the opposite direction;
  • Step 1020 1022 after receiving the 200 response, the PNM AS checks that the previously set timer has not expired, stops the timer, and establishes a successful call between the terminal of user B and the UEb of user A.
  • the PNM AS determines whether to perform the redirection according to whether the INVITE message includes the redirection information.
  • the S-CSCF passes the INVITE message according to whether the INVITE message contains the redirection information. Match the iFC to determine if the PNM AS is to be triggered again. The judgments made by other processes and logical entities are completely consistent with the second embodiment.
  • the AS can easily match the iFC matching message with the iFC by adding a new SIP header field or adding a new parameter. This way avoids the S-CSCF repeatedly triggering the PNM AS.
  • the mechanism by which GMSC triggers gsmSCF is not flexible enough, and the existing mechanism has been fixed, so it is difficult to avoid multiple triggers for gsmSCF in the CS domain.
  • User A has signed the PNM service. He has both a and b terminals, where UEa is the CS terminal, UEb is the IMS terminal, and UEa activates the redirect service.
  • PNMAS is deployed only in IMS in the network.
  • the user B on the other side first initiates a call to the UEb of the user A, and the PNM AS selects the UEa to perform the connection, and the connection succeeds before the PNM AS timer expires, and the session is successfully established.
  • Step 1201 the original called S-CSCF (b) receives the session establishment request INVITE message; Step 1202, because the UEb subscribes to the PNM service, the S-CSCF checks whether the INVITE message contains information that does not trigger the PNMAS, since the change is not included. To the information, where S-CSCF(b) determines that the PNMAS is normally triggered;
  • Step 1203 the S-CSCF (b) forwards the INVITE message to the PNM AS.
  • Step 1204 the PNM AS selects the current highest priority according to the user-set priority list.
  • Step 1205 The PNM AS sends a new service request INVITE message to the S-CSCF (b), and adds the route redirection information that the call has been redirected in the message, and the information may pass the history- in the SIP protocol. Add a new forwarding cause value in the info header field to carry or add a new header field or a new parameter by extending the SIP protocol, and the PNM AS starts monitoring the call processing result.
  • Step 1206 the S-CSCF (b) forwards the INVITE request to the MGCF (a);
  • Step 1207 The MGCF(a) performs message type conversion, and sends a service request message IAM(a) to the GMSC (a), where the route redirection information indicating that the current call has been redirected is carried, and the information may be in the ISUP protocol.
  • the UUI carries or extends the ISUP protocol, and adds a new cell in the IAM (b) message to carry the information or by increasing the value of the redirectioninformation forwarding cause;
  • Steps 1208 to 1209 the GMSC(a) obtains the routing information of the UEa from the HSSa, and the HSSa returns the T_CSI data.
  • Step 1210 The GMSC (a) sends a redirection request message intialDP to the CS domain SDS according to the T_CSI, where the route redirection information indicating that the current call has been redirected is carried, and the information may be carried in the redirectioninformation parameter in the InitialDP message or Expand the CAP protocol, add cells in the InitialDP message to carry this information to implement or carry it through the UUI;
  • Step 1211 The SDS of the CS domain sends a service request message Connect to the GMSC (a) to route the request to the IMS domain, where the message includes the public service identifier PSI address information of the IMS domain SDS and the route indicating that the current call is redirected. Redirection information;
  • the SDS may also perform specific CAMEL service logic according to the information including the redirect information, not routing the request to the IMS domain, but returning a CONTINUE message to the GMSC (a), and continuing to route the request to the UEa;
  • Step 1212 The GMSC (a) sends a service request message IAM to the MGCF (a) requesting to be routed to the IMS domain SDS, where the PSI address information of the IMS domain SDS and the route redirection information capable of identifying the redirection of the current call are carried;
  • Steps 1213 ⁇ 1214, MGCF(a) converts the ISUP message into a SIP INVITE message and forwards the request message to the I-CSCF, the I-CSCF obtains the address information of the IMS domain SDS, and sends the converted service request message to the IMS domain SDS.
  • INVITE the message carrying the PSI address information of the IMS domain SDS and the converted route redirection information capable of identifying the redirection of the current call;
  • the IMS domain SDS passes the forwarding history information in the converted SIP INVITE message or with the CS domain.
  • the SDS exchanges the original called number information after the redirection, and restores the original called number according to the same, and inserts it into the service request message INVITE, and sends it to the S-CSCF of the user terminal a;
  • Step 1215 although the UEa also subscribes to the PNM service, the S-CSCF (a) determines that the INVITE does not need to be triggered to send the INVITE to the PNM AS again according to the route redirection information that the INVITE message carries to indicate that the call has been redirected. But need to directly connect to UEa;
  • Step 1216 the S-CSCF (a) directly selects the circuit domain connection through the access domain selection server.
  • Step 1217 the UEa returns a response message after successfully connecting, and the response returns to the PNM AS according to the same path as the original signaling but in the opposite direction;
  • Steps 1218 ⁇ 1220 after receiving the successful response, the PNMAS checks that the previously set timer has not expired, then stops the timer, and establishes a successful call between the terminal of user B and UEa of user A.
  • the failure re-election is not considered. If the failure re-election occurs, it is similar to the case where the PNM AS is deployed in the IMS and CS domains respectively. Refer to Embodiment 4.
  • the present invention provides a system for reselecting a called user terminal in a PNM redirection service, where the system includes: one or more PNM service triggering entities 1301 and a PNM server 1302, wherein the PNM service triggering entity 1301 is configured to receive services.
  • the called user terminal currently in the active state in the priority list of the called user terminal is randomly selected.
  • the PNM service triggering entity 1301 is configured to: when the service request does not include the redirect information, trigger the PNM server to execute the redirect service logic.
  • the PNM service triggering entity 1301 is further configured to: when the redirecting information is included in the service request, return the service request to the called user terminal in the sending the service request.
  • the PNM service triggering entity 1301 is configured to: trigger a PNM service by sending a redirect service request.
  • the PNM server 1302 is configured to: when the redirect service request does not include the redirect information, execute the redirect service logic, select a called user terminal from the priority list, and A service request containing the redirected information and the selected called user terminal address information is sent to the PNM service triggering entity of the network to which the called user terminal belongs.
  • the PNM server 1302 is further configured to: when the redirecting service request includes the redirecting information, send a service request to the PNM service triggering entity that sends the redirecting service request.
  • the PNM server 1302 is further configured to: send a dynamic monitoring point to the PNM service triggering entity 1301, where the PNM service triggering entity 1301 is further configured to: when the service connection fails, send a service processing failure to the PNM server according to the dynamic monitoring point. response.
  • the PNM service triggering entity 1301 is further configured to: when the service connection fails, send a service processing failure response to the PNM server.
  • the PNM server 1302 is configured to: determine that the current service connection fails by receiving a service processing failure response sent by the PNM service triggering entity.
  • the PNM server 1302 is configured to: receive a service failure response or a successful response sent by the PNM service triggering entity before the preset timer expires, or receive a service failure response sent by the PNM service triggering entity before the timer expires. , to determine the current business connection failure.
  • the PNM server 1302 is configured to: select the called user terminal in priority order from the currently activated active user terminal that has not been selected in the priority list, or is currently in the priority list.
  • the called user terminal is randomly selected from the called user terminal in an active state.
  • the present invention further provides a redirection service triggering apparatus, which can be applied to a system for reselecting a called user terminal in a PNM redirection service, where the apparatus includes a first detecting unit 1401 and a forwarding unit 1402, where A detecting unit 1401 is configured to detect a service request processing result of the called user terminal, and a forwarding unit 1402 is configured to send a service failure response to the PNM server when the first detecting unit detects that the called user terminal does not successfully process the service request.
  • the first detecting unit 1401 is configured to: detect that the called user terminal successfully processes the service request or fails to process the service request according to the received service processing success or failure response.
  • the forwarding unit 1402 is configured to: send a service processing failure response to the PNM server according to the dynamic detection point delivered by the PNM server.
  • the redirecting service triggering device further includes a triggering unit 1403, configured to receive a service request, and trigger the PNM server to execute the redirecting service logic.
  • the triggering unit 1403 includes a receiving unit 14031 and an executing unit 14032, wherein the receiving unit 14031 is configured to receive a service request, and the executing unit 14032 is configured to trigger the PNM server to execute the redirecting service logic.
  • the triggering unit 1403 further includes a matching unit 14033, configured to match information carried in the service request with a local triggering policy. Then, the executing unit 14032 is configured to: trigger the PNM when the matching result of the matching unit is that the PNM server needs to be triggered. The server performs the redirect business logic.
  • the present invention further provides a PNM server, which can be applied to a system for reselecting a called user terminal in a PNM redirection service, where the server includes a connection unit 1501, which is used to prioritize when the current service connection fails.
  • the server includes a connection unit 1501, which is used to prioritize when the current service connection fails.
  • the level list select a called user terminal to perform service connection.
  • the splicing unit 1501 includes a second detecting unit 15011 and a reselecting unit 15012, where the second detecting unit 15011 is configured to determine that the current service connection fails according to the service failure response sent by the PNM service triggering entity, and the reselecting unit 15012 is configured to When the second detecting unit determines that the current service connection fails, a selected user terminal is selected from the priority list to perform service connection.
  • the second detecting unit 15011 is further configured to: receive a service processing failure or a successful response sent by the PNM service triggering entity before receiving the preset timer, or receive a PNM service triggering entity before the timer expires. The business failed to respond, determining that the current service connection failed.
  • the PNM server further includes a first processing unit 1502, configured to receive a redirect service request sent by the PNM service triggering entity, and determine whether the redirect service request includes redirect information, where the redirect service request does not include When the redirecting information is sent to the reselecting unit, when the redirecting service request includes the redirecting information, the service request is returned to the PNM service triggering entity; then the reselecting unit 15012 is further used for When receiving the service request, select a called user terminal from the priority list to perform service connection.
  • the first processing unit 1502 includes a first receiving unit 15021, a determining unit 15022, and a first sending The sending unit 15023, the first receiving unit 15021 is configured to receive a redirect service request sent by the PNM service triggering entity, and the determining unit 15022 is configured to determine whether the redirecting service request includes the redirecting information.
  • the unit 15023 is configured to: when the determining unit determines that the redirecting service request does not include the redirecting information, send the service request to the reselecting unit, and when the determining unit determines that the redirecting service request includes the redirecting information, The service request is returned to the PNM service triggering entity.
  • the present invention further provides a system for reselecting a called user terminal in a personal network management PNM redirection service, where the system includes a service domain selection server 1601, a PNM service triggering entity 1602, and a PNM server 1603, where
  • the service domain selection server 1601 is located in the circuit domain, and is configured to determine, according to the condition, whether to forward the called service request to the IMS domain according to the condition, after receiving the domain selection request for the CS domain called service request sent to the served user.
  • the PNM redirects the service processing, and when it is determined that the called service request needs to be routed to the IMS domain for PNM redirection service processing, the indication is that the called service request is routed to the IMS domain, otherwise the indication continues to be performed in the CS domain.
  • the connection of the called service is performed.
  • the service domain selection server determines whether the called service request needs to be routed to the IMS domain for PNM redirection service processing by determining whether the domain selection request includes the redirection information.
  • the called service request is routed to the IMS domain; the PNM service trigger entity 1 602, located in the IMS domain, after receiving the called service request, triggering the PNM server to perform redirection service logic; the PNM server 1603 is located in the IMS domain, and is configured to perform a redirection service, and select from the priority list.
  • a called user terminal performs service connection; when it is determined that the current service connection fails, a selected user terminal is selected from the priority list to continue the service connection.
  • the service domain selection server 1601 is configured to: after receiving the called service request, if the redirected information is not included in the called service request, routing the called service request to the IMS domain.
  • the service domain selection server 1601 is further configured to: after receiving the called service request, when the redirected information is included in the called service request, send the called service request message to the called service request The called user terminal.
  • the PNM service triggering entity 1602 is configured to: after receiving the called service request, in the When the service request does not include the redirect information, the redirect service request is sent to the PNM server.
  • the PNM service triggering entity 1602 is further configured to: after receiving the called service request, include the redirecting information in the called service request, and the called user terminal in the called service request is a CS domain terminal And sending the called service request message to the called user terminal by using the ADS and the VMSC.
  • the called user terminal When the PNM server performs reselection, the called user terminal is selected in priority order from the currently activated active user terminal that has not been selected in the priority list, or from the called user terminal.
  • the called user terminal currently active in the priority list is randomly selected.
  • the present invention further provides a service domain selection server, where the server is located in a circuit domain, and the server includes: a routing unit 1701, configured to receive a domain selection request for a CS domain called service request sent to a served user.
  • the service domain selection server determines whether the domain selection request includes the redirect information to determine whether the The called service request is routed to the IMS domain for PNM redirect service processing, and when the request does not include the redirect information, the called service request is routed to the IMS domain.
  • the server further includes a connection unit 1702, configured to: when receiving the called service request from the circuit domain, if the called service request includes the redirect information, send the called service request to the called service request.
  • the called user terminal configured to: when receiving the called service request from the circuit domain, if the called service request includes the redirect information, send the called service request to the called service request.
  • the called user terminal configured to: when receiving the called service request from the circuit domain, if the called service request includes the redirect information, send the called service request to the called service request.
  • the present invention further provides a transit redirection triggering device, which is located in an IMS domain, and includes a triggering unit 1801, configured to receive a called service request from a circuit domain, if the called service is used. If the request does not include the redirect information, the redirect service request is sent to the PNM server of the IMS domain.
  • a transit redirection triggering device located in an IMS domain, and includes a triggering unit 1801, configured to receive a called service request from a circuit domain, if the called service is used. If the request does not include the redirect information, the redirect service request is sent to the PNM server of the IMS domain.
  • the device further includes a connection unit 1802, configured to receive a called service request from the circuit domain, if the called service request includes redirection information, and the called party in the called service request
  • a connection unit 1802 configured to receive a called service request from the circuit domain, if the called service request includes redirection information, and the called party in the called service request
  • the called service request message is sent to the called user terminal by using the ADS and the VMSC.
  • the user terminal (UE) appearing in this document is activated or in an active state, that is, the user terminal is a UE that is previously designated by the user as a request in the terminating personal network (PN).
  • PN terminating personal network

Landscapes

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

Abstract

L'invention concerne un procédé de resélection pour un terminal d'utilisateur appelé dans un service de redirection pour la gestion de réseau personnel (PNM), ce procédé étant appliqué dans le réseau central d'un système de communication mobile. Le procédé selon l'invention comprend les étapes suivantes : après réception de la demande de service envoyée à l'utilisateur appelé, une entité de déclenchement de service PNM faisant partie d'un réseau dans lequel se trouve le terminal d'utilisateur appelé déclenche le serveur PNM pour que ce dernier exécute une logique de redirection, et ce serveur PNM sélectionne un premier terminal d'utilisateur appelé dans une liste de priorité pour la connexion; lorsque cette connexion de service échoue, le serveur PNM sélectionne un deuxième terminal d'utilisateur dans la liste de priorité pour la connexion. Cette invention peut améliorer la vitesse de connexion pour des sessions.
PCT/CN2007/002972 2006-10-17 2007-10-17 Procédé de resélection pour un terminal d'utilisateur appelé dans un service de redirection, et système et appareil correspondants WO2008046313A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200610139178 2006-10-17
CN200610139178.X 2006-10-17
CN200710103143.5 2007-04-27
CN2007101031435A CN101064965B (zh) 2006-10-17 2007-04-27 重定向业务中被叫用户终端重选的方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2008046313A1 true WO2008046313A1 (fr) 2008-04-24

Family

ID=38965589

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002972 WO2008046313A1 (fr) 2006-10-17 2007-10-17 Procédé de resélection pour un terminal d'utilisateur appelé dans un service de redirection, et système et appareil correspondants

Country Status (2)

Country Link
CN (1) CN101064965B (fr)
WO (1) WO2008046313A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103747430B (zh) * 2013-12-31 2018-10-19 华为技术有限公司 呼叫控制设备和处理用户业务的方法
CN104135549B (zh) * 2014-08-19 2017-12-12 中国人民解放军信息工程大学 一种支持多样化寻址方式的数据传输方法及装置
US20170236088A1 (en) * 2016-02-15 2017-08-17 DeliveryCircle LLC Delivery method and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1440610A (zh) * 2000-05-04 2003-09-03 Mci全球通讯公司 因特网协议电话网络中动态网关选择的方法和系统
JP2004032453A (ja) * 2002-06-26 2004-01-29 Nippon Telegr & Teleph Corp <Ntt> パケット通信システムとこのシステムで使用されるパケット転送装置及びパケット転送制御プログラム
CN1759574A (zh) * 2003-01-27 2006-04-12 Raza微电子公司 在异构网络中分类和重定向数据分组的方法和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7860114B1 (en) * 1999-11-08 2010-12-28 Verizon Business Global Llc Method and system for dynamic gateway selection in an IP telephony network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1440610A (zh) * 2000-05-04 2003-09-03 Mci全球通讯公司 因特网协议电话网络中动态网关选择的方法和系统
JP2004032453A (ja) * 2002-06-26 2004-01-29 Nippon Telegr & Teleph Corp <Ntt> パケット通信システムとこのシステムで使用されるパケット転送装置及びパケット転送制御プログラム
CN1759574A (zh) * 2003-01-27 2006-04-12 Raza微电子公司 在异构网络中分类和重定向数据分组的方法和设备

Also Published As

Publication number Publication date
CN101064965A (zh) 2007-10-31
CN101064965B (zh) 2010-04-21

Similar Documents

Publication Publication Date Title
JP4545436B2 (ja) ネットワーク識別される非常セッションを取り扱う方法及びシステム
EP2131557B1 (fr) Procédé, système et élément de réseau pour traitement du service après invalidation de données d&#39;élément et survenue d&#39;un incident
ES2384525T3 (es) Método para realizar la activación del registro de usuarios en un subsistema multimedia IP
WO2008046319A1 (fr) Procédé et système pour assurer la continuité d&#39;un appel vocal lors de la gestion d&#39;une affaire urgente
EP2388970B1 (fr) Système, procédé et appareil pour l&#39;enregistrement d&#39;équipement d&#39;utilisateur et l&#39;activation pour PNM
AU2001258380A1 (en) Method and system for handling a network-identified emergency session
WO2007036147A1 (fr) Procede et systeme d&#39;etablissement d&#39;un appel initial dans le service de la continuite de service vocal
WO2007098713A1 (fr) Procédé et système d&#39;appel d&#39;urgence
WO2007036123A1 (fr) Procede et systeme de communication pour un utilisateur du domaine cs accedant au domaine ims
WO2008028416A1 (fr) Procédé de commande de transfert intercellulaire d&#39;appel et système de communication mettant en oeuvre ce procédé et dispositif utilisateur
WO2008154842A1 (fr) Procédé et dispositif pour fournir un service de transfert d&#39;appel pour les utilisateurs
WO2007079688A9 (fr) Procede, appareil et systeme de mise en communication de l&#39;utilisateur appele
WO2012025007A1 (fr) Procédé et système pour l&#39;obtention d&#39;une capacité d&#39;équipement utilisateur par un équipement utilisateur, un serveur de données d&#39;abonné résidentiel et un élément de réseau central
WO2009024006A1 (fr) Contrôleur de session locale, sous-système multimédia ip et procédé d&#39;enregistrement de session
WO2009129725A1 (fr) Procédé, système et dispositif pour assurer des services
WO2007124643A1 (fr) Procédé, système et appareil d&#39;optimisation d&#39;ancrage en continuité d&#39;appel vocal
WO2007124641A1 (fr) Procédé et dispositif permettant de percevoir un utilisateur qui déclenche un service supplémentaire
CN101018400A (zh) 一种基于话音业务连续性的实现呼叫业务的系统和方法
WO2007025473A1 (fr) Systeme de terminaison d&#39;appel de domaine cs, procede et reseau
WO2012024908A1 (fr) Procédé et système permettant de rapporter la capacité d&#39;un terminal
WO2009039688A1 (fr) Procédé de transfert d&#39;appel tardif dans un service centralisé d&#39;un sous-système de réseau central multimédia ip
WO2007041929A1 (fr) Système et méthode de fourniture au réseau cs de service du réseau ims
US9509547B2 (en) Selection of service domain in IMS centralised services
WO2007128238A1 (fr) Procédé, entité, système de détection des états de services non ims exécutés par des utilisateurs et d&#39;information de ceux-ci
WO2008046313A1 (fr) Procédé de resélection pour un terminal d&#39;utilisateur appelé dans un service de redirection, et système et appareil correspondants

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

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

Country of ref document: EP

Kind code of ref document: A1