WO2012065496A1 - Procédé et dispositif pour actualiser des numéros de commutation au moment de l'enregistrement - Google Patents

Procédé et dispositif pour actualiser des numéros de commutation au moment de l'enregistrement Download PDF

Info

Publication number
WO2012065496A1
WO2012065496A1 PCT/CN2011/081137 CN2011081137W WO2012065496A1 WO 2012065496 A1 WO2012065496 A1 WO 2012065496A1 CN 2011081137 W CN2011081137 W CN 2011081137W WO 2012065496 A1 WO2012065496 A1 WO 2012065496A1
Authority
WO
WIPO (PCT)
Prior art keywords
stn
update
registration
request message
registration request
Prior art date
Application number
PCT/CN2011/081137
Other languages
English (en)
Chinese (zh)
Inventor
李世涛
陈志峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012065496A1 publication Critical patent/WO2012065496A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and system for updating a handover number upon registration. Background technique
  • PS Packet Domain Switching
  • Packet Switch Packet Switch
  • E-UTRAN E-UTRAN
  • UTRAN-HSPA Packet Switch
  • CS Circuit Switch
  • FIG. 1 is a single mode switching mode (SRVCC) approved by the standards organization.
  • SRVCC single mode switching mode
  • UE1 101 a call is being made between UE1 101 and UE2 106, and is a PS bearer based on IP Multimedia Core Network Subsystem (IMS).
  • IMS IP Multimedia Core Network Subsystem
  • PS access PS access
  • SCC AS Service Centralization and Continuity Application Server
  • the UE1 101 moves to a better area (CS access) of the CS network, and the UE1 101 sends the received signal test report to the mobile management device (MME, Mobility) through the original PS network.
  • MME mobile management device
  • the MME 102 after the MME 102 receives the signal test 4, then performs PS to CS handover, at which time the MME 102 sends a handover notification message to an enhanced mobile switching center (MSC, Mobile Switching) that can cover the UE1 101.
  • MSC Mobile Switching
  • the handover notification message includes an SRVCC (STN-SR, Session Transfer Number for SR-VCC) assigned by the network to the user; the MSC 103 can directly send the IMS to the IMS network 104 if there is an extended SIP interface.
  • STN-SR Session Transfer Number for SR-VCC
  • the IMS handover request command includes the media resource information of the MSC 103, and the MSC 103 returns a handover response to the MME 102;
  • the MME 102 sends a notification that the handover is completed to the user.
  • the MSC 103 sends a handover response to the MME 102, and the MME 102 notifies the user that the handover is complete, and the MSC 103 initiates the handover update on the IMS side simultaneously.
  • the calling user and the called user Switching is not perceived.
  • the switching process of the PS network to the CS network based on the single mode switching mode of FIG. 1 is as shown in FIG. 2, and includes:
  • an IMS session is being performed between the user UE-1 and the UE-2.
  • Step 201 For some reason (such as the change of the UE-1 location), the network environment around the UE-1 is changed.
  • the signal of the PS network accessed by the UE-1 may not be very good, but the surrounding CS network signal
  • the UE-1 sends a network signal test report to the wireless side network element of the original PS network;
  • Step 202 The original PS network radio side network element determines, according to the received network signal test report, whether UE-1 needs to be switched to the CS network.
  • Step 203 When the original PS network radio side network element determines that handover is required, send a handover request to the MME serving the UE-1.
  • Step 204 After receiving the handover request, the MME sends a handover notification to an enhanced MSC that can cover the UE-1, where the network includes an STN-SR allocated by the network to the UE-1, and the STN-SR is a static route to the SCC AS. Number
  • Step 205 After receiving the handover notification, the MSC may send a handover request to the IMS network directly through the SIP interface (if any) or through the MGCF, where the request address is the STN-SR allocated by the network for the UE-1, and the media information is the MSC. Information;
  • Step 206 After receiving the handover request, the IMS side network element will perform the handover request according to the STN-SR. Sent to the SCC AS;
  • Step 207 Since all IMS sessions of the UE-1 are anchored on the SCC AS, the SCC AS finds the ongoing session of the UE-1 according to the calling number in the handover request, that is, the number of the UE-1, and sends the session to the session. Sending a remote update request, and modifying the sent media information of the UE-1 side to the information of the MSC;
  • Step 208 After receiving the remote update request, the UE-2 returns a remote update response to the UE-1 side when agreeing to the remote update request.
  • Steps 209-210 the SCC AS returns a handover request response to the MSC through the IMS side network element.
  • Step 211 After receiving the 204 step handover notification, the MSC may return a handover response to the MME, and the process and the IMS side handover ( Steps 205 ⁇ 210) are performed simultaneously;
  • the MME After receiving the handover response, the MME sends a notification handover message to the UE-1 through the original PS network radio side network element. After receiving the message, the UE-1 can switch to the CS network.
  • the handover on the IMS side (steps 205-210) will take a long time because of the need for remote update, especially when UE-1 and UE-2 are not in the same network, the time will be longer. Therefore, an optimized architecture for SRVCC, namely eSRVCC, is proposed.
  • the architecture of the eSRVCC is as shown in Figure 3.
  • a new network element is added: the ATCF (Access Transfer Control Function) 304.
  • the network element is mainly used to anchor the user's session, and the network element is the same.
  • the service user (UE-1) belongs to the same network.
  • the ATCF When transmitting the handover, the ATCF only needs to perform an internal handover process without notifying the remote end, which greatly saves the handover time.
  • Step 401 When a user (UE-1) connects to a PS network, send a registration request to the IMS network through the PS network; if an eSRVCC is deployed in the PS network, the registration request is routed to the ATCF;
  • Step 402 the ATCF determines whether to anchor the subsequent session according to the information such as the subscription of the user. If it is determined that the anchor is required, the user is assigned a dynamic STN-SR, and the value of the dynamic STN-SR is the route of the ATCF. Address
  • Step 403 The ATCF sends the registration request after inserting the dynamic STN-SR to the IMS network element/intermediary session control function (I/S-CSCF, Interrogating/Serving-Call Session Control Function) entity;
  • I/S-CSCF Interrogating/Serving-Call Session Control Function
  • Step 404 After the I/S-CSCF authentication is successfully registered, return a 200 OK response to the user; Step 405, the ATCF sends the 200 OK response to the UE-1, and the user is successfully registered; Step 406, when I/S- After receiving the registration request from the user, the CSCF initiates a third-party registration to all application servers (AS, Application Servers) that provide services for the user. Since the user is a user who has signed the eSRVCC, one of the third-party registration requests. The message is sent to the SCC AS, which also carries the dynamic STN-SR allocated by the ATCF to the user when the user registers. Step 407, after the SCC AS receives the third-party registration request message and determines that the dynamic STN-SR is included, Sending a data update request to the Home Subscriber Server (HSS), where the dynamic STN-SR is carried;
  • HSS Home Subscriber Server
  • Step 408 In the initial state, the HSS stores a static STN-SR allocated to the user.
  • the value of the static STN-SR is the address of the SCC AS. Since the HSS receives the dynamic STN-SR allocated by the ATCF for the user, the HSS uses The dynamic STN-SR covers the previous static STN-SR and returns an update response to the SCC AS;
  • Step 409 The SCC AS returns a 200 OK response that is successfully registered to the I/S-CSCF.
  • Step 410 The HSS sends an insert subscription data message to the MME, where the dynamic STN is included, because the STN-SR of the user saved by the HSS changes.
  • SR Step 411: The MME saves the dynamic STN-SR to the user data, and returns an insertion subscription data response to the HSS.
  • Figure 5 shows the process of switching using eSRVCC, including:
  • Step 501 For some reason (such as the change of the UE-1 location), the network environment around the UE-1 is changed.
  • the signal of the PS network accessed by the UE-1 may not be very good, but the surrounding CS network The signal is better, so UE-1 sends a network signal test report to the wireless side network element of the original PS network;
  • Step 502 The original PS network radio side network element determines, according to the received network signal test report, whether UE-1 needs to be switched to the CS network.
  • Step 503 When the original PS network radio side network element determines that handover is required, send a handover request to the MME serving UE-1.
  • Step 504 After receiving the handover request, the MME sends a handover notification to the enhanced MSC that can cover the UE-1, where the network includes the STN-SR allocated by the network for the UE-1: for the eSRVCC user, from the registration process (according to FIG. 4 The process can be seen that the STN-SR allocated by the network for UE-1 is a dynamic STN-SR, which points to the address of the ATCF.
  • Step 505 After receiving the handover notification, the MSC may send a handover request to the IMS network directly through the SIP interface (if any) or through the MGCF, where the request address is the dynamic STN-SR, and the media information is the information of the MSC; When the value of the dynamic STN-SR is the address of the ATCF, the MSC directly sends the handover request to the ATCF;
  • Step 506 because the ATCF anchors the user's session, the ATCF finds the ongoing session of the user (UE-1) according to the identity information of the user in the handover request, and sends the media information of the UE-1 side of the session.
  • the information is modified to the MSC.
  • the modification only needs to be notified to the media gateway under the ATCF.
  • the update request is not sent to the remote end.
  • the handover request response is returned to the MSC.
  • Step 507 After receiving the handover notification message of step 504, the MSC may return a handover response to the MME, and the process and the handover to the ATCF (steps 505-506) are performed simultaneously;
  • Steps 508-509 the MME sends a notification handover message to the UE-1 through the original PS network radio side network element. After receiving the message, the UE-1 may switch to the CS.
  • the user can access the IMS from different access networks at the same time, and multiple registrations are independent, and the user's multiple registration information is also saved on the network side.
  • eSRVCC handover can be deployed only in the 3GPP PS network, that is, only when the user accesses the 3GPP PS network, the eSRVCC technology may be used when PS to CS handover occurs.
  • a user accesses from another network, such as a wireless local area network (WLAN) access IMS
  • WLAN wireless local area network
  • ATCF that is, the eSRVCC technology cannot be applied.
  • the user is registered in the scenario.
  • the IMS registration is initiated.
  • the network supports the eSRVCC technology.
  • the ATCF allocates a dynamic STN-SR to the user.
  • the user accesses another network such as WLAN.
  • an IMS registration 2 is also initiated.
  • the registration is independent of registration 1.
  • the WLAN network does not support eSRVCC technology. If there is no ATCF, the specific registration process is as shown in FIG. 6. , including:
  • Steps 601 ⁇ 611, the flow of registration 1 occurs, the registration request includes the registration ID reg-id l, and the process is the same as 401-411 of FIG. 4, wherein the 3GPP PS network that initiates registration 1 supports eSRVCC.
  • the SCC AS saves the dynamic STN-SR to the HSS, and inserts the dynamic STN-SR into the MME through the HSS;
  • Step 613 The P-CSCF2 sends the registration request to the I/S-CSCF serving the UE-1 in the IMS network, where the I/S-CSCF is the same as the I/S-CSCF of the registration 1;
  • Step 614 After the user authentication of the UE-1 is passed by the I/S-CSCF, send a 200 OK response to the UE-1.
  • Step 615 the P-CSCF2 forwards the 200 OK response to the UE-1.
  • Step 616 since the I/S-CSCF receives the registration request of the registration 2 at this time, the I/S-CSCF also needs to send a third-party registration request to the SCC AS. Since the network initiated by the registration 2 does not support the eSRVCC technology, this is There is no dynamic STN-SR in the third-party registration request message;
  • Step 617 Since only one registration data of the user is saved on the SCC AS, the multiple registrations are not distinguished. According to the prior art, the SCC AS finds that there is no dynamic STN-SR in the third-party registration request message, so the SCC AS The static STN-SR assigned to the user is sent to the HSS through a data update request;
  • Step 618 after receiving the data update request, the HSS overwrites the dynamic STN-SR previously saved (registered in the registration 1) with the static STN-SR in the message, and returns an update response to the SCC AS;
  • Step 619 The SCC AS returns a 200 OK response that is successfully registered to the I/S-CSCF.
  • STN-SR is modified to static STN-SR when the user After the IMS session is initiated by the original PS network, if the switch to the CS network needs to be initiated, the dynamic STN-SR is modified to be a static STN-SR, and the user can only perform the SRVCC switch according to the process in FIG. 2, but The eSRVCC switch cannot be performed, which is not desired by users and network operators. Summary of the invention
  • the main purpose of the present invention is to provide a method and apparatus for updating a handover number at the time of registration, which can solve the problem that the STN- is caused by the presence and absence of the eSRVCC technology in the multiple registration scenarios.
  • the SR update is confusing.
  • the present invention provides a method for updating a handover number upon registration, the method comprising: an anchor and associated application server (SCC AS) receiving a third party registration request message; determining that a user currently registering is a first registration, and the third party When the registration request message carries the dynamic single mode switching mode switching number (STN-SR), the STN-SR is updated; it is determined that the currently registered user is not registered for the first time, and has been executed in the previous registration.
  • SCC AS anchor and associated application server
  • the third-party registration request message carries a dynamic STN-SR, according to the dynamic
  • the STN-SR determines whether to perform an update of the STN-SR
  • the third party registration request message does not carry the dynamic STN-SR, it is determined according to the third party registration request message whether to perform the update of the STN-SR.
  • the method further includes: not performing the update of the STN-SR.
  • the determining, according to the dynamic STN-SR, whether to perform the update of the STN-SR includes: the dynamic STN-SR carried in the third-party registration request message and the dynamic STN-SR in the previous registration When the values are not the same, perform the STN-SR update; otherwise, do not execute Update of STN-SR.
  • the method further includes:
  • the value of the P-Access-Network-Info header field of the third-party registration request message is read. If the network indicating that the eSRVCC is not allowed to be deployed, the update of the STN-SR is not performed; if the network indicating that the eSRVCC is allowed to be deployed, Then perform an update of the STN-SR.
  • determining whether to perform the update of the STN-SR according to the third-party registration request message includes:
  • the STN-SR update is not performed;
  • the STN-SR is updated to indicate that the network is allowed to deploy eSRVCC.
  • determining whether to perform the update of the STN-SR according to the third-party registration request message includes:
  • the STN-SR update is not performed.
  • the update of the STN-SR is: SCCAS updates the dynamic STN-SR allocated by the ATCF carried in the third-party registration request message to the HSS; or when the third-party registration request message does not have a dynamic STN- In the SR, the SCC AS updates the static STN-SR allocated by the SCC AS to the user in the HSS; the HSS updates the received STN-SR to the
  • the present invention also provides an apparatus for updating a switching number when registering, comprising: a receiving unit, an analyzing unit, and an updating unit;
  • the receiving unit is configured to receive a third party registration request message;
  • the analyzing unit is configured to perform condition analysis of the STN-SR update after the receiving unit receives the third-party registration request message, and notify the update unit of the analysis result;
  • the updating unit is configured to perform STN-SR update according to the analysis result of the analyzing unit, including:
  • the analyzing unit determines that the user currently registered is the first registration, and when the third party registration request message carries the dynamic STN-SR, the updating unit performs the update of the STN-SR; the analyzing unit determines that the current registration is performed.
  • the user is not registered for the first time and has performed an update of the STN-SR in the previous registration,
  • the third-party registration request message carries the dynamic STN-SR, determine whether to perform the STN-SR update according to the dynamic STN-SR;
  • the third-party registration request message does not carry the dynamic STN-SR, it is determined according to the third-party registration request message whether to perform the update of the STN-SR.
  • the updating unit is further configured to: when the analyzing unit determines that the user currently registered is the first registration, and determines that the third-party registration request message does not carry the dynamic STN-SR, does not perform the STN-SR Update.
  • the updating unit is further configured to: when the analyzing unit determines that the dynamic STN-SR carried in the third-party registration request message is different from the value of the dynamic STN-SR in the previous registration The update of the STN-SR is performed; otherwise, the update of the STN-SR is not performed; the update unit is further configured to: determine, by the analyzing unit, the dynamic STN-SR carried in the third-party registration request message, and the former When the values of the dynamic STN-SRs in one registration are different, and the analyzing unit determines that the value of the P-Access-Network-Info header field of the third-party registration request message is not allowed to deploy the network of the eSRVCC The update of the STN-SR is not performed; when the network indicated to be allowed to deploy the eSRVCC is determined, the update of the STN-SR is performed.
  • the updating unit is further configured to: at the analyzing unit, determine, that the value of the P-Access-Network-Info header field of the third-party registration request message is not allowed to deploy eSRVCC
  • the update of the STN-SR is not performed when the network is determined; the update of the STN-SR is performed when the network indicating that the eSRVCC is allowed to be deployed is determined; and the registration unit carries the registration carried in the third-party registration request message.
  • the ID is the same as the registration ID of the previous registration, the update of the STN-SR is performed; when not, the update of the STN-SR is not performed.
  • the updating unit is further configured to: update the dynamic STN-SR allocated by the ATCF carried in the third-party registration request message to the HSS; or when there is no dynamic STN-SR in the third-party registration request message
  • the SST AS updates the static STN-SR assigned to the user to the HSS.
  • the present invention updates the switching number scheme.
  • the SCC AS receives the third-party registration request message, it performs an analysis to determine whether to perform the STN-SR handover, for example, determining that the currently registered user is the first registration, and the third-party registration request message.
  • the update of the STN-SR is performed; when the user who is currently registering is not the first registration, and the update of the dynamic STN-SR is performed in the previous registration, if the third-party registration request message carries the dynamic
  • the STN-SR determines whether to perform the update of the STN-SR according to the dynamic STN-SR.
  • the third-party registration request message determines whether to perform the update of the STN-SR according to the third-party registration request message. This solves the problem of STN-SR update confusion caused by the existence of support for multiple networks that initiate registration and the lack of support for eSRVCC technology.
  • Figure 1 is an architectural diagram of an existing SRVCC handover
  • Figure 3 is an architectural diagram of an existing eSRVCC handover
  • Figure 4 is a flow chart of registration when the existing eSRVCC handover is implemented
  • Figure 5 is a flow chart of an existing eSRVCC handover session
  • FIG. 7 is a flowchart of a method for updating a handover number according to the present invention
  • FIG. 8 is a flowchart of updating an STN-SR in a multiple registration scenario according to Embodiment 1 of the present invention
  • FIG. 9 is a flowchart of updating an STN-SR in a multiple registration scenario according to Embodiment 2 of the present invention
  • the method for updating a handover number according to the present invention includes:
  • Step 701 The SCC AS receives a third-party registration request message.
  • step 702 it is determined that the user currently registered is the first registration, and the third party registration request message carries the dynamic STN-SR, and the STN-SR is updated.
  • the update of the STN-SR is not performed.
  • step 703 it is determined whether the user who is currently registering is not the first registration, and the update of the dynamic STN-SR is performed in the previous registration. If the third-party registration request message carries the dynamic STN-SR, it is determined according to the dynamic STN-SR. Performing an update of the STN-SR; if the third-party registration request message does not carry the dynamic STN-SR, determining whether to perform the update of the STN-SR according to the third-party registration request message.
  • the determining whether to perform the update of the STN-SR according to the dynamic STN-SR includes: performing the STN-SR when the dynamic STN-SR carried in the third-party registration request message is different from the dynamic STN-SR in the previous registration. Update; otherwise, the STN-SR update is not performed.
  • the P-Access-Network-Info header of the third-party registration request message is optionally read.
  • the value of the domain if the network indicating that the eSRVCC is not allowed to be deployed, does not perform the update of the STN-SR; if the network indicating the eSRVCC is allowed to be deployed, the update of the STN-SR is performed.
  • the first step is to read the value of the P-Access-Network-Info header field of the third-party registration request message. If the network indicating that the eSRVCC is not allowed to be deployed, the update of the STN-SR is not performed. If the network is instructed to allow the eSRVCC to be deployed, , then perform an update of the STN-SR.
  • the network indicating that the eSRVCC is not allowed to be deployed refers to: The network where the user is located when the current registration is initiated does not support eSRVCC.
  • Manner 2 The registration ID carried in the third-party registration request message is read. If the registration ID of the previous registration is the same, the static STN-SR is updated. If the registration ID is not the same as the previous registration, the STN is not executed. -SR update.
  • the update of the STN-SR is: SCCAS updates the dynamic STN-SR allocated by the ATCF carried in the third-party registration request message to the HSS; or when there is no dynamic STN-SR in the third-party registration request message,
  • the SCC AS updates the static STN-SR allocated by the SCC AS to the HSS; the HSS re-updates the received STN-SR to the MME.
  • FIG. 8 is a flowchart of updating an STN-SR in a multiple registration scenario according to Embodiment 1 of the present invention, where UE-1 accesses an IMS network through an E-UTRAN or UTRAN PS network, and E-UTRAN or UTRAN
  • the PS network supports eSRVCC, and the ATCF allocates dynamic STN-SR to the user.
  • the process includes:
  • the registration 1 is the first registration of the user (UE-1)
  • the third-party registration request message includes the dynamic STN-SR allocated by the ATCF to the UE-1
  • the SCC AS executes the STN.
  • the update of the SR that is, through the third party registration, the SCC AS saves the dynamic STN-SR to the HSS, and then inserts the dynamic STN-SR into the MME through the HSS. in;
  • Step 813 The P-CSCF2 sends the registration request of the registration 2 (referred to as the registration request 2) to the I/S-CSCF serving the UE-1 in the IMS network, and the I/S-CSCF is the same as the I/S in the registration 1.
  • CSCF is the same;
  • Step 814 After the user authentication of the UE-1 is passed by the I/S-CSCF, send a 200 OK response to the P-CSCF2.
  • Step 815 the P-CSCF2 forwards the 200 OK response to the UE-1;
  • Step 816 When the registration request 2 is received, the I/S-CSCF also needs to send a third-party registration request to the SCC AS. Since the network that initiates the registration 2 does not support the eSRVCC technology, there is no dynamic STN in the third-party registration request at this time. -SR;
  • Step 817 the SCC AS determines the P-Access-Network-Info header field in the third-party registration request message. If the value indicates that the network initiating the registration 2 is not in compliance with the network in which the eSRVCC is deployed, the SCC AS does not execute the STN-SR. Update (SCC AS does not update the static STN-SR to HSS), which is the case in this embodiment; if its value indicates that the network initiating registration 2 is a network that is deployed with eSRVCC, then the SCC AS performs an update of STN-SR (The SCC AS updates the static STN-SR to the HSS).
  • Update SCC AS does not update the static STN-SR to HSS
  • Steps 818-819 if there is other data to be updated, the SCC AS may send a data update request to the HSS, but the process does not update the STN-SR. If no other data needs to be updated, the SCC AS may not send a data update request to the HSS; Therefore, steps 818-819 are optional; in step 820, the SCC AS returns a registration success 200 OK response to the I/S-CSCF;
  • Steps 821 ⁇ 822 at this time, if the HSS has other data to be updated, the HSS may send an insert subscription data message to the MME, but the process does not update the STN-SR, if there is no other data. If the update is required, the HSS may not send the insertion subscription data message to the MME; Steps 821 ⁇ 822 are optional.
  • FIG. 9 is a flowchart of updating an STN-SR in a multiple registration scenario according to Embodiment 2 of the present invention, where UE-1 accesses an IMS network through an E-UTRAN or UTRAN PS network, and E-UTRAN or UTRAN
  • the PS network supports eSRVCC, and the ATCF allocates dynamic STN-SR to the user.
  • the process includes:
  • the PS network of the UTRAN supports the eSRVCC technology.
  • the registration 1 is the first registration of the user (UE-1)
  • the third-party registration request message includes the dynamic STN-SR allocated by the ATCF to the UE-1, SCC AS.
  • the SCC AS saves the dynamic STN-SR to the HSS, and then inserts the dynamic STN-SR into the MME through the HSS;
  • Step 913 The P-CSCF2 sends the registration request 2 to the I/S-CSCF serving the UE-1 in the IMS network, where the I/S-CSCF is the same as the I/S-CSCF of the registration 1;
  • Step 914 After the I/S-CSCF passes the user authentication of the UE-1, send a 200 OK response to the P-CSCF2.
  • Step 915 P-CSCF2 forwards the 200 OK response to UE-1;
  • Step 916 When the registration request 2 is received, the I/S-CSCF also needs to send a third-party registration request to the SCC AS. Since the network that initiates the registration 2 does not support the eSRVCC technology, there is no dynamic STN in the third-party registration request at this time.
  • Steps 918-919 if there is other data to be updated, the SCC AS may send a data update request to the HSS, but the process does not update the STN-SR. If no other data needs to be updated, the SCC AS may not send a data update request to the HSS;
  • Step 920 The SCC AS returns a registration success 200 OK response to the S-CSCF.
  • Steps 921 to 922 if the HSS has other data to be updated, the HSS may send an insertion subscription data message to the MME, but the process does not update the STN-SR. If no other data needs to be updated, the HSS may not send an insertion to the MME. Sign up for data messages.
  • the present invention provides a switching device.
  • the device is applied to an SCC AS.
  • the present invention includes: a receiving unit, an analyzing unit, and an update unit;
  • a receiving unit configured to receive a third party registration request message
  • An analyzing unit configured to perform condition analysis of the STN-SR update after the receiving unit receives the third-party registration request message, and notify the update unit of the analysis result;
  • the updating unit is configured to perform the STN-SR update according to the analysis result of the analyzing unit, and the method includes: the analyzing unit determines that the currently registered user is the first registration, and the third party registration request message carries the dynamic STN-SR, and executes the STN-SR Update
  • the analysis unit determines that the user currently registered is not the first registration, and has performed the STN-SR update in the previous registration.
  • the third-party registration request message carries the dynamic STN-SR, it is determined according to the dynamic STN-SR. Whether to update the STN-SR;
  • the third-party registration request message is used to determine whether to update the state STN-SR.
  • the updating unit is further configured to: when the analyzing unit determines that the currently registered user is the first registration, and the third-party registration request message does not carry the dynamic STN-SR, the STN-SR update is not performed.
  • the update unit is further configured to determine, according to the dynamic STN-SR whether the update of the STN-SR is performed, the value of the dynamic STN-SR carried in the third-party registration request message and the dynamic STN-SR in the previous registration. When the same is true, the update of the STN-SR is performed; otherwise, the update of the STN-SR is not performed;
  • the analyzing unit determines that the dynamic STN-SR carried in the third-party registration request message is different from the value of the dynamic STN-SR in the previous registration, and the analyzing unit determines the third party
  • the update unit does not perform the update of the STN-SR; when determining the network indicating that the eSRVCC is allowed to be deployed, the update unit performs the STN- SR update.
  • the update unit is further configured to determine, in the analysis unit, that the value of the P-Access-Network-Info header field of the third-party registration request message is not allowed to deploy the eSRVCC.
  • the network is not performing the update of the STN-SR; when determining the network indicating that the eSRVCC is allowed to be deployed, the update of the STN-SR is performed;
  • the update unit is further configured to: when the analysis unit determines that the registration ID carried in the third-party registration request message is the same as the registration ID of the previous registration, the execution state STN -SR update; not the same, does not perform STN-SR update.
  • the update unit is further configured to update the dynamic STN-SR allocated by the ATCF carried in the third-party registration request message to the HSS; or when the third-party registration request message does not move In the STN-SR state, the static STN-SR allocated by the SCC AS to the user is updated to the HSS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un dispositif utilisés pour actualiser des numéros de commutation au moment de l'enregistrement, ledit procédé comprenant les étapes suivantes: un serveur de centralisation de services et d'application en continuité (SCC AS) reçoit un message de demande d'enregistrement d'une tierce partie; ledit serveur actualise le numéro de transfert de session pour la SR-VCC (STN-SR) au moment où il est confirmé que l'utilisateur qui est en cours d'enregistrement est enregistré pour la première fois et le message de demande d'enregistrement d'une tierce partie effectue une STN-SR dynamique; au moment où il est confirmé que l'utilisateur en cours d'enregistrement n'est pas enregistré pour la première fois et qu'il n'y a pas eu actualisation de la STN-SR lors du dernier enregistrement, le SCC AS décide soit d'actualiser la STN-SR en fonction de la STN-SR dynamique, soit d'actualiser le STN-SR en fonction du message de demande d'enregistrement de la tierce partie, si le message de demande d'enregistrement de la tierce partie n'effectue pas la STN-SR dynamique. L'invention permet de résoudre le problème que pose l'actualisation chaotique de la STN-SR
PCT/CN2011/081137 2010-11-16 2011-10-21 Procédé et dispositif pour actualiser des numéros de commutation au moment de l'enregistrement WO2012065496A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010547340.8A CN102469438B (zh) 2010-11-16 2010-11-16 一种注册时更新切换号码的方法和装置
CN201010547340.8 2010-11-16

Publications (1)

Publication Number Publication Date
WO2012065496A1 true WO2012065496A1 (fr) 2012-05-24

Family

ID=46072474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081137 WO2012065496A1 (fr) 2010-11-16 2011-10-21 Procédé et dispositif pour actualiser des numéros de commutation au moment de l'enregistrement

Country Status (2)

Country Link
CN (1) CN102469438B (fr)
WO (1) WO2012065496A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103716784B (zh) 2012-09-28 2018-06-08 中兴通讯股份有限公司 业务接续处理方法及系统
CN110601928B (zh) * 2019-08-22 2021-11-05 深圳震有科技股份有限公司 一种号码分析表的更新方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227647A (zh) * 2008-02-05 2008-07-23 中兴通讯股份有限公司 一种保持多媒体会话连续性业务的切换方法
CN101287150A (zh) * 2007-04-13 2008-10-15 华为技术有限公司 一种会话切换的方法、系统及语音呼叫连续性应用服务器
CN101651896A (zh) * 2008-08-15 2010-02-17 中兴通讯股份有限公司 一种多媒体会话的关联方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2163065B1 (fr) * 2007-06-01 2018-10-24 Orange Basculement de session audiovisuelle d'un premier réseau d'accès vers un deuxième réseau d'accès

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101287150A (zh) * 2007-04-13 2008-10-15 华为技术有限公司 一种会话切换的方法、系统及语音呼叫连续性应用服务器
CN101227647A (zh) * 2008-02-05 2008-07-23 中兴通讯股份有限公司 一种保持多媒体会话连续性业务的切换方法
CN101651896A (zh) * 2008-08-15 2010-02-17 中兴通讯股份有限公司 一种多媒体会话的关联方法

Also Published As

Publication number Publication date
CN102469438B (zh) 2015-09-16
CN102469438A (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
US8180347B2 (en) Domain transferring method for single radio voice call continuity
CN102378148B (zh) 终端、hss、及核心网网元获知终端能力的方法和系统
JP5694348B2 (ja) ハンドオーバー遅延の最適化
JP5646647B2 (ja) 通信ネットワークで用いる方法および装置
KR101414697B1 (ko) 액세스 네트워크들 사이에서의 세션 전송을 위한 방법들 및 장치
EP2366258B1 (fr) Procédé et appareil pour enregistrer à commutation de circuits un abonné dans un ims sur l'interface sgs / gs
EP2625875B1 (fr) Continuité d'appel vocal radio unique pour sessions de rappel d'urgence ou de numérotation par clic
AU2011204099A1 (en) Mobile switching centre server
US8509781B2 (en) Method and system for realizing session handover
US8412283B2 (en) System and method for switching ringing state session with customized alerting tone
CN102769880B (zh) 单一无线语音呼叫连续性域的切换方法及系统
WO2011050698A1 (fr) Système et procédé de commutation de session de sonnerie avec crbt
JP2012514924A (ja) Ｉｍｓベースのホームノードｂにおけるモビリティ
US8982840B2 (en) Handover
WO2012065496A1 (fr) Procédé et dispositif pour actualiser des numéros de commutation au moment de l'enregistrement
JP2015528239A (ja) 回線交換ドメインへのハンドオーバーのための方法、装置、およびシステム
CN101835222B (zh) 终端从家庭基站切换到宏蜂窝系统保持会话的方法和系统
WO2013064105A1 (fr) Procédé et dispositif de commutation d'un support à continuité des appels vocaux radio uniques inverses
CN104936262B (zh) 远端标识的发送、接收方法及装置、传输系统
CN102612017B (zh) 移动网络获取ims控制点信息的方法及系统
WO2012019532A1 (fr) Procédé et système permettant d'ancrer une session
WO2013102393A1 (fr) Procédé et appareil améliorés, pour la mise en œuvre d'une continuité d'appel vocal radio unique inverse
CN102612141B (zh) 移动交换中心获取ims控制点信息的方法及系统
WO2013102394A1 (fr) Dispositif et procédé de mise en œuvre d'une continuité de service de veille unique inverse

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

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

Country of ref document: EP

Kind code of ref document: A1