WO2024173735A1 - Rationalisation de mobilité entre réseaux de différentes générations - Google Patents

Rationalisation de mobilité entre réseaux de différentes générations Download PDF

Info

Publication number
WO2024173735A1
WO2024173735A1 PCT/US2024/016059 US2024016059W WO2024173735A1 WO 2024173735 A1 WO2024173735 A1 WO 2024173735A1 US 2024016059 W US2024016059 W US 2024016059W WO 2024173735 A1 WO2024173735 A1 WO 2024173735A1
Authority
WO
WIPO (PCT)
Prior art keywords
sessions
platform
transferrable
session
transferable
Prior art date
Application number
PCT/US2024/016059
Other languages
English (en)
Inventor
Haibo Qian
Fred Rink
Michael Brown
Original Assignee
Microsoft Technology Licensing, Llc
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
Priority claimed from US18/203,494 external-priority patent/US20240284268A1/en
Application filed by Microsoft Technology Licensing, Llc filed Critical Microsoft Technology Licensing, Llc
Publication of WO2024173735A1 publication Critical patent/WO2024173735A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00222Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between different packet switched [PS] network technologies, e.g. transferring data sessions between LTE and WLAN or LTE and 5G
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface

Definitions

  • Embodiments described herein relate to establishing an “any-G” network, where “any-G” involves the support and transfer of sessions between any of the 2G/3G, 4G and 5G platforms. More specifically, embodiments described herein relate to the movement of a user across the platforms and moving to or from 2G/3G form or to 5G by way of a 4G platform to allow for relatively seamless transitions, avoiding the time-out failures, as discussed below.
  • the MME may communicate with the different platforms through different gateways.
  • the MME controls the transfers of sessions from the 4G platform to the 2G/3G platform and/or from the 4G platform to the 5G platform.
  • the MME in embodiments described herein, is enhanced beyond the standard to smooth the transition of sessions from the 2G/3G platform to the 5G platform and vice versa through the 4G platform.
  • the MME classifies the different sessions on the UE as anchored in GGSN, PGW or SMF. In this manner, the MME is able, when needed, to transfer the sessions that are transferrable and to terminate the ones that cannot be transferred. By terminating the ones that cannot be transferred, the device can begin reestablishing the connection without waiting, e.g., without waiting for the timeout failure to occur.
  • Fig. 1 illustrates an exemplary, non-limiting embodiment of a high-level system and environment in accordance with various aspects described herein.
  • Fig. 2 depicts an illustrative embodiment of a method related to transferring control from one platform to another having a different platform technology in accordance with various aspects described herein.
  • Fig. 3 depicts an illustrative embodiment of a method related to determining the capability of one or more gateways in accordance with various aspects described herein.
  • Fig. 4 illustrates timing diagram showing the transfer scenario from 4G to 2G/3G in the idle mode in accordance with various aspects described herein.
  • Fig. 5 illustrates timing diagram showing the transfer scenario from 4G to 2G/3G in the connected mode in accordance with various aspects described herein.
  • Fig. 6 illustrates timing diagram showing the transfer scenario from 4G to 5 G in the idle mode in accordance with various aspects described herein.
  • Fig. 7 illustrates timing diagram showing the transfer scenario from 4G to 5G in the connected mode in accordance with various aspects described herein.
  • Fig. 8 is a block diagram of an exemplary, non-limiting embodiment of a computing environment in accordance with various aspects described herein.
  • Fig. 9 is a block diagram of an exemplary, non-limiting embodiment of a communication device in accordance with various aspects described herein.
  • MME mobility management entity
  • the MME When a user travels between a 2G/3G network and a 5G network via a 4G network, if the mobility management entity (MME) does not know the type of gateways that are used by user equipment, the MME will try to transfer the sessions to a gateway that cannot handle the session.
  • existing MMEs generally do not track information related to the session anchor point’s ability with regard to supporting sessions from all radio technologies. Consequently, when a user moves from one location to another and wants to transfer connectivity from 2G/3G to 5G or vice versa, equipment used by the user, i.e., the user equipment (UE), is expected to initiate an initial/new registration with the new network.
  • UE user equipment
  • sessions initially anchored in 2G/3G may not be transferred seamlessly to 5G.
  • sessions initially anchored in 5G may not be seamlessly transferred to 2G/3G. Instead, these sessions must be re-established. As a result, some sessions may be transferred, and others may not. For example, if a session is created on a GGSN/PGW node, which correlates to a node supporting 2G/3G and 4G, and the UE moves to AMF, which is related to a node supporting 5G, then the MME will attempt to transfer the session to the 5G side.
  • Embodiments described herein relate to establishing an “any-G” network, where “any-G” involves the support and transfer of sessions between any of the 2G/3G, 4G and 5G platforms. More specifically, embodiments described herein relate to the movement of a UE across the platforms and moving to or from 2G/3G form or to 5G by way of a 4G platform to allow for relatively seamless transitions, avoiding the time-out failures, as discussed below.
  • Fig. 1 illustrates an environment 100 for implementing embodiments of the present innovation.
  • the environment 100 comprises a user device 102, also referred to as user equipment 102 or just UE 102.
  • the UE 102 relates to a mobile computing device such as a mobile phone, a laptop computer system, a connected car, or the like.
  • a mobile computing device such as a mobile phone, a laptop computer system, a connected car, or the like.
  • the UE 102 may physically move to or from a second location, such as shown by UE 103.
  • UE 103 is in dashed lines to indicate movement to that second location.
  • UE 102 may originally connect to a 2G/3G platform 104. Those skilled in the art will understand how such connectivity may be established through an RNC or the like. Also, as will be appreciated when connected to the 2G/3G platform, sessions may be anchored in the GGSN technology. As shown, the UE 102 may, either initially or following movement, connect to 4G platform 106. It is possible that the UE 102 may move from 2G/3G 104 to 4G platform 106. According to aspects of embodiments herein, the UE 102 may move to a new geographic location (such movement is depicted by UE 103 in Fig. 1) and connect to 5G platform 108. As shown, such movement may cause session transfers of user data sessions from 2G/3G platform 104 to 5G platform 108 by way of 4G platform 106.
  • the system when certain connections are established by the UE 102 or UE 103 through 106, the system includes a backend mobility management entity (MME) 110.
  • MME mobility management entity
  • the MME 110 is a network component for cellular networks, especially for 4G platforms, responsible for managing mobility related functions such as tracking of the location of the devices and managing handovers between calls.
  • the MME may communicate with the different platforms, by way of SGSN 118 to reach 2G/3G platform 104, and AMF 120 to reach platform 108, and communicates through GGSN/PGW node 112 or PGW/SMF 114 to route packets to and from other networks such as the Public Data Network (PDN) 116 and/or other devices, not shown.
  • PDN Public Data Network
  • the 2G/3G platform 104 may communicate with SGSN node 118 to route packets through GGSN/PGW 112.
  • 5G platform 108 may communicate with AMF node 120 to route packets through PGW/SMF node 114.
  • the MME 110 controls the transfers of sessions from the 4G platform 106 to the 2G/3G platform 104 when the UE 102 transfers into a 2G/3G platform 104 area. Further, the MME 110 can control the transfer of sessions from the 4G platform 106 to the 5G platform 108 when the UE 102 transfers into a 5G platform 108 area.
  • the combined GGSN/PGW node/gateway 112 may be used in order to support 2G/3G and 4G mobility. As a result, some of the 2G/3G sessions may be anchored in GGSN or in PGW. In order to support 4G to 5G mobility, combined PGW/SMF node/gateway 114 may be used.
  • some of the 5G sessions may be anchored in SMF or in PGW. These nodes and gateways are described in the 3GPP standard. It shall be noted that there can be a gateway that is a combined GGSN/PGW/SMF. If a session is anchored on such a gateway, the session can be transferred to 2G/3G, 4G and 5G platform. The method detailed in this disclosure covers such a scenario.
  • the MME 110 in embodiments described herein, is enhanced beyond the standard to smooth the transition of sessions from the 2G/3G platform 104 to the 5G platform 108 and vice versa.
  • the MME 110 in embodiments, classifies the different sessions on the UE as anchored in GGSN, PGW or SMF. In this manner, the MME is able, when needed to transfer the sessions that are transferrable and to terminate the ones that cannot be transferred. By terminating the ones that cannot be transferred, the device can begin reestablishing the connection without waiting, e.g., without waiting for the timeout failure to occur.
  • Fig. 2 depicts an illustrative embodiment of a method 200 related to transferring control from one platform to another having a different platform technology in accordance with various aspects described herein.
  • a general order of the operations for the method 200 is shown in Fig. 2. While a number of operations are shown, the method 200 may include more or fewer steps or may arrange the order of the steps differently than those shown in Fig. 2.
  • the method 200 can be executed as computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Further, the method 200 can be performed by gates or circuits associated with a processor, an ASIC, an FPGA, a SOC or other hardware device.
  • the method 200 shall be explained with reference to the systems, components, devices, modules, software, data structures, data characteristic representations, signaling diagrams, methods, etc., described in conjunction with other figures described herein.
  • Method 200 generally begins with establish operation 202 where the UE is established on the MME. Those skilled in the art will appreciate how to establish a UE on an MME to handle mobility for that device.
  • receive operation 204 receives an indication to transfer or initiate a handoff from one platform to another.
  • Receive operation 204 is known to those skilled in the art and can be initiated by the device or by an intermediate network component recognizing the need to handoff the UE to another node or network. Such event occurs when the UE is moving from one location to another, which is covered by a different network platform as shown in Fig. 1.
  • a handoff request is received when the device is in active or connected mode, e.g., when the UE device is actively being used, such as during a phone call and/or when an application on the device is sending/receiving data packets.
  • the UE is considered to be in idle mode, and thus the receive operation 204 receives a transfer of control request, such as through a location update signal or a registration request.
  • the location update signal occurs when the device moves into a 2G/3G platform area.
  • a registration request occurs when the device moves into a 5G platform area.
  • determine operation 206 determines the different active sessions that can be transferred.
  • different sessions may be established within the network, each one having different communication processes that may be occurring, e.g., different applications may be actively communicating with the network using different session identifiers.
  • the anchoring of each session occurs during the initial instantiation of the session.
  • Determine operation 206 evaluates each session, and the anchor information for each session, to determine if it can be transferred to the new network or not.
  • determine step 208 may determine the sessions that cannot be transferred. Both determine operations are discussed in more detail below in conjunction with Fig. 3.
  • operation 210 includes identifications of those sessions that can be transferred in a response to the transfer request. Such inclusion allows for the next process step to receive and continue the session without termination. More specifically, when in idle mode and transferring from a 4G platform area to a 2G/3G platform area, the session information related to sessions that can transfer will be included in the SGSN context response signal. Likewise, when in idle mode and transferring from a 4G platform area to a 5G platform area, the session information related to sessions that can transfer will be included in the context response to the registration request. Otherwise, when in connected mode and transferring from 4G platform area to either 2G/3G or 5G areas, then the session information related to sessions that can transfer will be included in the forward relocation request signal.
  • deactivate operation 212 deactivates or terminates all sessions that cannot be transferred. By actively terminating the sessions, the UE is able to re-establish the connection for those sessions as would be required in direct transfer from 2G/3G to 5G in the past.
  • the deactivation or termination of non-transferrable sessions occurs substantially simultaneously with the transfer of transferrable sessions. That is, the deactivation is performed actively without waiting for a timeout error.
  • Fig. 3 depicts an illustrative embodiment of a method 300 related to determining whether different sessions can be transferred from one platform to another having a different platform technology in accordance with various aspects described herein.
  • method 300 relates to marking the sessions, within the MME according to the gateway such sessions were initially established, e.g., anchored. Such process may also be considered classifying the session. Using the classification, the method 200 discussed above is able to determine those sessions that can be transferred, e.g., at step 206 and/or those sessions that cannot be transferred at step 208.
  • Method 300 relates to one particular embodiment of classifying the different sessions.
  • Method 300 begins with query operation 302 which queries against the canonical node name of the gateway to get the service parameter of the gateway.
  • This process step uses the NAPTR query to get such information.
  • NAPTR stands for Name Authority Pointer type of resource record in the DNS or Domain Name System of the Internet.
  • Those skilled in the art will appreciate the ability to implement a NAPTR query for the anchor gateway of each session to identify specific information relating to the gateway, to determine the capability of the gateway.
  • determine operation 304 the method 300 determines if the NAPTR response includes a service parameter having “x-3gpp-ggsn” in the response.
  • GGSN Gateway GPRS Support Node
  • Determine operation 308 determines if the NAPTR response includes a service parameter having “nc-smf ’ in the response. If so, flow branches YES to conclude operation 310 to indicate that the session was anchored using SMF (Session Management Function) and has the SMF function or capability, such as used in conjunction with the 5G protocol. Conclude operation 310 may also set or mark the session as SMF transferrable to 5G such that the session can transfer from 4G platform areas to a 5G platform area without terminating the session.
  • SMF Session Management Function
  • Conclude operation 310 may also set or mark the session as SMF transferrable to 5G such that the session can transfer from 4G platform areas to a 5G platform area without terminating the session.
  • the “nc-smf’ is just one particular example.
  • store operation 312 stores any information related to session transferability to the MME. Consequently, when needed, the MME will be able to identify those sessions that are transferable and those that must be terminated. As shown, it may be that both determine operation 304 and determine operation 308 determine that a session may be marked as GGSN transferable and SMF transferable such that the session may be transferred gracefully to either 2G/3G or 5G platforms without termination and would be so marked. Also, it is possible that the session is not transferable gracefully, e.g., when it does not have either the “x-3gpp-ggsn” or the “nc-smf ’ service parameter. If so, then flow will pass to store operation 312 but nothing will be marked in that case.
  • the gateway is a pure PGW and does not have GGSN or SMF capability at all. In this last case, the session can only stay on 4G platform, but this is not common.
  • store operation 312 essentially marks and/or stores session data for each session as transferrable to GGSN and/or transferrable to SMF depending on the capability of the gateway used for the session, if there is any such information.
  • the capability of a gateway can be administratively defined on the MME. This is offered as an alternative to the DNS query, which uses the name of the gateway to get the NAPTR record to determine the capabilities. If the network operator does not prefer to use DNS, they can define the capability of each gateway via static configuration on the MME. For example, a gateway could be defined as PGW/GGSN or PGW/SMF or PGW or GGSN/PGW/SMF.
  • Fig. 4 illustrates a timing diagram as a UE 402 moves from one location, essentially connected to a 4G platform, to another location and needs to transfer to 2G/3G platform.
  • Fig. 4 illustrates the control operations while in idle mode.
  • a UE is considered to be in idle mode when not actively using the network for voice or data services but is still registered or connected to the network and can receive incoming calls or data sessions.
  • a Routing Area Update signal will be sent to the network.
  • the UE 402 communicates through the Base Station System or Radio Network Controller (BSS/RNC) 404 to the SGSN 406 (Serving GPRS Support Node).
  • BSS/RNC Base Station System or Radio Network Controller
  • the SGSN communicates to the MME 408, which then communicates with the SGW 410, which in turn communicates with the PGW 412.
  • the UE 402 is established/registered on the MME 408, as indicated by box 414, such that the MME 408 may control the mobility of the UE 402 and the transfer of connectivity between networks.
  • a routing area update signal 416a is communicated to the BSS/RNC 404 which passes the signal 416b the SGSN 406.
  • the routing area update (RAU) is commonly delivered to the BSS/RNC to inform the network about changes in location of the UE.
  • an SGSN context request signal 418 requests information from the MME 408, such as the device location or session information.
  • the MME will create a response to the SGSN.
  • the MME 408 evaluates the existing sessions for the UE and identifies those sessions that are transferrable to a 2G/3G platform as indicated by box 420. Identifying these sessions as transferrable may, in embodiments, relate to the method steps described above in conjunction with Fig. 3. In alternative embodiments, other methods may be used to identify the transferable sessions. For instance, it is contemplated that future sessions may include transferability information during setup such that the MME 408 can simply look at the setup information to determine transferability.
  • the MME 408 will send the SGSN context response signal 422, which will include identification information for those sessions that can be transferred. It may not include session information for those that will not be transferred.
  • the SGSN will respond with an SGSN context ack signal 424.
  • MME 408 deactivates the sessions that cannot be transferred, e.g., by communicating deactivate signal 426 to the SGW 410.
  • the SGW 410 will communicate a deactivate signal 428 to the PGW 412.
  • the deactivate signals 426 and 428 will essentially deactivate or terminate any session that cannot be transferred, such as sessions anchored in SMF. Such termination allows the UE 402 to begin reestablishing those sessions as needed on the new platform.
  • signals 430 continue the routing area update (RAU). Continuation of the RAU 430 occurs following the Context Ack signal step 424. While it is shown as happening after the deactivation process steps 426 and 428, it may occur before, after or in parallel with the deactivation process.
  • the SGSN 406 communicates an acceptance of the update at 432 indicating the active sessions, which is communicated at 434 to the UE 402 by the BSS/RNC 404.
  • Fig. 5 illustrates a timing diagram as a UE 502 moves from one location, essentially connected to a 4G platform, to another location and needs to transfer to 2G/3G platform in the connected mode.
  • the UE 502 In connected mode, the UE 502 is actively using the network for data and/or voices services and is exchanging data with the network.
  • the UE 502, in connected mode may communicate through an eNB 504 to MME 506.
  • the MME 506 may communicate with a SGSN 508, which then communicates with a BSS/RNC 510, which can then communication with the SGW512 and the PGW 514.
  • the UE 502 is established/registered on the MME 506, as indicated by box 516, such that the MME 506 may control the mobility of the UE 502 and the transfer of connectivity between networks.
  • a handover signal 518 is communicated from the eNB to the MME 506.
  • Such a handover signal 518 is known and relates to the eNB sensing movement of the UE such that a handoff or handover is requested.
  • a forward relocation request is generated by the MME 506.
  • the MME 506 evaluates the existing sessions for the UE 502 and identifies those sessions that are transferrable to a 2G/3G platform as indicated by box 520. Identifying these sessions as transferrable may, in embodiments, relate to the method steps described above in conjunction with Fig. 2 or discussed above in conjunction with Fig. 3 and Fig. 4.
  • the MME 506 forwards the relocation request signal 522 to the SGSN 508 which forwards to the RNC/BSS 510.
  • the signals 522 and 524 will include identification information for those sessions that can be transferred. Such signals may not include session information for those that will not be transferred.
  • signals 526 and 528 will continue the handoff or handover 526 and will continue to complete the RAU procedure 528.
  • MME 506 deactivates any sessions that cannot be transferred, e.g., by communicating deactivate signal 530 to the SGW 512.
  • the SGW 512 will communicate a deactivate signal 532 to the PGW 514.
  • the deactivate signals 530 and 532 will essentially deactivate or terminate any session that cannot be transferred, such as sessions anchored in SMF. Such termination allows the UE to begin reestablishing those sessions as needed on the new platform without further delay.
  • Fig. 6 illustrates a timing diagram as a UE 602 has moved from one location, essentially connected to a 4G platform, to another location and needs to transfer to 5G platform according to another scenario contemplated herein.
  • Fig. 6 illustrates the control operations while in idle mode.
  • a UE is considered to be in idle mode when not actively using the network for voice or data services but is still registered or connected to the network and can receive incoming calls or data sessions.
  • the UE will send a registration request, where the device is requesting information from the network.
  • the UE 602 in this scenario, communicates through the gNB 604 to the AMF 606.
  • the AMF 606 communicates to the MME 608, which then communicates with the SGW 610, which in turn communicates with the PGW 612.
  • the UE 602 is established/registered on the MME 608, as indicated by box 614, such that the MME 608 may control the mobility of the UE 602 and the transfer of connectivity between networks.
  • a registration request 616a is communicated to the gNB 604 which passes the signal 616b to the AMF 606.
  • the registration request is a known request to those skilled in the art.
  • a context request signal 618 requests information from the MME 608, such as the device location or session information or other context information.
  • the MME 608 will create a response to the AMF 606.
  • the MME 608 evaluates the existing sessions for the UE 602 and identifies those sessions that are transferrable to a 5G platform as indicated by box 620. Identifying these sessions as transferrable may, in embodiments, relate to the method steps described above in conjunction with Figs. 2, 3, 4 and 5.
  • the MME 608 will send the context response signal 622, which will include identification information for those sessions that can be transferred. It may not include session information for those that will not be transferred.
  • the AMF 606 will respond with a context ack signal 624. Subsequently, as will be appreciated by those skilled in the art, signals 626 continue the mobility registration and session startup for transferrable sessions.
  • MME 608 deactivates the sessions that cannot be transferred, e.g., by communicating deactivate signal 630 to the SGW 610.
  • the SGW 610 will communicate a deactivate signal 632 to the PGW 612.
  • the deactivate signals 630 and 632 will essentially deactivate or terminate any session that cannot be transferred, such as sessions anchored in GGSN. Such termination allows the UE 602 to begin reestablishing those sessions as needed on the new platform.
  • the AMF 606 communicates an acceptance of the registration at 434 indicating the active sessions and PDU session status, which is also then communicated at 636 to the UE 602 by the gNB 604.
  • Fig. 7 illustrates a timing diagram as a UE 702 moves from one location, essentially connected to a 4G platform, to another location and needs to transfer to 5G platform in the connected mode.
  • the UE 702 In connected mode, as discussed above, the UE 702 is actively using the network for data and/or voices services and is exchanging data with the network.
  • the UE 702, in connected mode may communicate through an eNB 704 to an MME 706.
  • the MME 706 may communicate with an AMF 708, which then communicates with a gNB 710, which can then communicate with the SGW 712 and the PGW 714.
  • the UE 702 is established/registered on the MME 706, as indicated by box 718, such that the MME 706 may control the mobility of the UE 702 and the transfer of connectivity between networks.
  • a handover signal 720 is communicated from the eNB 704 to the MME 706.
  • Such a handover signal 720 is known and relates to the eNB 704 sensing movement of the UE 702 such that a handoff or handover is requested.
  • a forward relocation request is generated by the MME 706.
  • the MME 706 evaluates the existing sessions for the UE 702 and identifies those sessions that are transferrable to a 5G platform as indicated by box 722. Identifying these sessions as transferrable may, in embodiments, relate to the method steps described above in conjunction with Fig. 2 or discussed above in conjunction with Figs. 3, 4, 5 and 6.
  • the MME 706 forwards the relocation request signal 724 to the AMF 708 which forwards the handover request 726 to the gNB 710.
  • the signals 724 and 726 will include identification information for those sessions that can be transferred. Such signals may not include session information for those that will not be transferred.
  • signals 728 and 730 will continue the handoff or handover 728 and will continue to complete the mobility registration procedure 730.
  • MME 706 deactivates the sessions that cannot be transferred, e.g., by communicating deactivate signal 732 to the SGW 712.
  • the SGW 712 will communicate a deactivate signal 734 to the PGW 714.
  • the deactivate signals 732 and 734 will essentially deactivate or terminate any session that cannot be transferred, such as sessions anchored in GGSN. Such termination allows the UE 702 to begin reestablishing those sessions as needed on the new platform.
  • a number of benefits are provided by the system and method in accordance with various aspects described herein. For instance, users may move from network to network more seamlessly since devices will more quickly recognize the deactivation of some sessions, causing the reestablishment procedure to occur sooner, reducing timeout failures and the like. Not only will less time be lost, but the risk of losing data will also be a benefit.
  • Fig. 8 illustrates a block diagram of a computing environment in accordance with various aspects described herein.
  • computing environment 800 can be used in the implementation of such as MMEs, UE, and the like.
  • MMEs Mobility Management Entity
  • UE User Equipment
  • Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software.
  • program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
  • a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.
  • Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media.
  • Computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.
  • Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • DVD digital versatile disk
  • magnetic cassettes magnetic tape
  • magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information.
  • tangible and/or non-transitory media are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.
  • Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.
  • Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media.
  • modulated data signal or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals.
  • communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
  • the example environment can comprise a computer 802, the computer 802 comprising a processing unit 804, a system memory 806 and a system bus 808.
  • the system bus 808 couples system components including, but not limited to, the system memory 806 to the processing unit 804.
  • the processing unit 804 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 804.
  • the system bus 808 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures.
  • the system memory 806 comprises ROM 810 and RAM 812.
  • a basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 802, such as during startup.
  • the RAM 812 can also comprise a high-speed RAM such as static RAM for caching data.
  • the computer 802 further may further comprise an internal hard disk drive (HDD) 814 (e.g., EIDE, SATA), which internal HDD 814 can also be configured for external use in a suitable chassis (not shown), and/or a magnetic floppy disk drive (FDD) 816, (e.g., to read from or write to a removable diskette 818) and/or an optical disk drive 820, (e.g., reading a CD-ROM disk 822 or, to read from or write to other high capacity optical media such as the DVD).
  • the HDD 814, magnetic FDD 816 and optical disk drive 820 can be connected to the system bus 808 by a hard disk drive interface 824, a magnetic disk drive interface 826 and an optical drive interface 828, respectively.
  • the hard disk drive interface 824 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.
  • the drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth.
  • the drives and storage media accommodate the storage of any data in a suitable digital format.
  • computer-readable storage media refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.
  • a number of program modules can be stored in the drives and RAM 812, comprising an operating system 830, one or more application programs 832, other program modules 834 and program data 836. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 812.
  • the systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.
  • a user can enter commands and information into the computer 802 through one or more wired/wireless input devices, e.g., a keyboard 838 and a pointing device, such as a mouse 840.
  • Other input devices can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like.
  • IR infrared
  • These and other input devices are often connected to the processing unit 804 through an input device interface 842 that can be coupled to the system bus 808, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.
  • a monitor 844 or other type of display device can be also connected to the system bus 808 via an interface, such as a video adapter 846. It will also be appreciated that in alternative embodiments, a monitor 844 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 802 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 844, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.
  • the computer 802 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 848.
  • the remote computer(s) 848 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 802, although, for purposes of brevity, only a remote memory/storage device 850 is illustrated.
  • the logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 852 and/or larger networks, e.g., a wide area network (WAN) 854.
  • LAN local area network
  • WAN wide area network
  • Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.
  • the computer 802 can be connected to the LAN 852 through a wired and/or wireless communication network interface or adapter 856.
  • the adapter 856 can facilitate wired or wireless communication to the LAN 852, which can also comprise a wireless AP disposed thereon for communicating with the adapter 856.
  • the computer 802 can comprise a modem 858 or can be connected to a communications server on the WAN 854 or has other means for establishing communications over the WAN 854, such as by way of the Internet.
  • the modem 858 which can be internal or external and a wired or wireless device, can be connected to the system bus 808 via the input device interface 842.
  • program modules depicted relative to the computer 802 or portions thereof can be stored in the remote memory/storage device 850. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.
  • the computer 802 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone.
  • This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies.
  • Wi-Fi Wireless Fidelity
  • BLUETOOTH® wireless technologies can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
  • Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires.
  • Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station.
  • Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity.
  • a Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet).
  • Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real -world performance similar to the basic lOBaseT wired Ethernet networks used in many offices.
  • the communication device 900 can serve as an illustrative embodiment of devices such as user computer device 102 as well as other devices.
  • communication device 900 can operate as a UE as described herein.
  • the communication device 900 can comprise a wireline and/or wireless transceiver 902 (herein transceiver 1002), a user interface (UI) 904, a power supply 914, a location receiver 916, a motion sensor 918, an orientation sensor 920, and a controller 906 for managing operations thereof.
  • the transceiver 902 can support short-range or long-range wireless access technologies such as Bluetooth®, WiFi, or cellular communication technologies, just to mention a few. Cellular technologies can include, for example, CDMA- IX, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise.
  • the transceiver 902 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.
  • the UI 904 can include a depressible or touch-sensitive keypad or touchscreen 908 for manipulating operations of the communication device 1000.
  • the keypad 908 can be an integral part of a housing assembly of the communication device 900 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®.
  • the keypad 908 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys.
  • the UI 904 can further include a display 910 which is any suitable display technology for conveying images to an end user of the communication device 900. In an embodiment where the display 910 is touch-sensitive, a portion or all of the keypad 908 can be presented by way of the display 910 with navigation features.
  • the display 910 can use touch screen technology to also serve as a user interface for detecting user input.
  • the communication device 900 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger.
  • GUI graphical user interface
  • the display 910 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user’ s finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface.
  • the display 910 can be an integral part of the housing assembly of the communication device 900 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.
  • the UI 904 can also include an audio system 912 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high-volume audio (such as speakerphone for hands free operation).
  • the audio system 912 can further include a microphone for receiving audible signals of an end user.
  • the audio system 912 can also be used for voice recognition applications.
  • the UI 904 can further include an image sensor 913 such as a charged coupled device (CCD) camera for capturing still or moving images.
  • CCD charged coupled device
  • the power supply 914 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 900 to facilitate long-range or short-range portable communications.
  • the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.
  • the location receiver 916 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 900 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation.
  • GPS global positioning system
  • the motion sensor 918 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 900 in three-dimensional space.
  • the orientation sensor 920 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 900 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).
  • the communication device 900 can use the transceiver 902 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements.
  • the controller 906 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 900.
  • computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication
  • first is for clarity only and doesn’t otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.
  • the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, nonvolatile memory, disk storage, and memory storage.
  • nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory.
  • Volatile memory can comprise random access memory (RAM), which acts as external cache memory.
  • RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).
  • SRAM synchronous RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM Synchlink DRAM
  • DRRAM direct Rambus RAM
  • the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.
  • the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like.
  • the illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers.
  • program modules can be located in both local and remote memory storage devices.
  • information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth.
  • This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth.
  • the generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user.
  • an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.
  • the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer.
  • an application running on a server and the server can be a component.
  • One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal).
  • a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.
  • the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter.
  • article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media.
  • computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive).
  • magnetic storage devices e.g., hard disk, floppy disk, magnetic strips
  • optical disks e.g., compact disk (CD), digital versatile disk (DVD)
  • smart cards e.g., card, stick, key drive
  • example and exemplary are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion.
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations.
  • terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream.
  • the foregoing terms are utilized interchangeably herein and with reference to the related drawings.
  • the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.
  • artificial intelligence e.g., a capacity to make inference based, at least, on complex mathematical formalisms
  • processor can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory.
  • a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • PLC programmable logic controller
  • CPLD complex programmable logic device
  • processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment.
  • a processor can also be implemented as a combination of computing processing units.

Landscapes

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

Abstract

Selon des aspects, la présente invention concerne le maintien d'une connexion réseau pendant un déplacement d'un emplacement à un autre entre différentes technologies, par exemple de la norme 2G/3G à la norme 5G, et vice versa. Une entité de gestion de mobilité (MME), par exemple sur une plateforme 4G, commande les transferts de sessions de la plateforme 4G à une plateforme 2G/3G lorsqu'un UE se déplace de la plateforme 4G à la plateforme 2G/3G et/ou de la plateforme 4G à une plateforme 5G. La MME classifie différentes sessions sur l'UE comme ancrées dans un GGSN, une PGW ou une SMF. Lorsque cela est nécessaire, la MME est alors apte à transférer les sessions qui sont transférables et à fermer celles qui ne peuvent pas être transférées. Par fermeture de celles qui ne peuvent pas être transférées, le dispositif peut commencer à rétablir la connexion sans attendre, par exemple, sans attendre qu'un échec après temporisation se produise.
PCT/US2024/016059 2023-02-17 2024-02-16 Rationalisation de mobilité entre réseaux de différentes générations WO2024173735A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363446730P 2023-02-17 2023-02-17
US63/446,730 2023-02-17
US18/203,494 US20240284268A1 (en) 2023-02-17 2023-05-30 Streamlining mobility between different g-networks
US18/203,494 2023-05-30

Publications (1)

Publication Number Publication Date
WO2024173735A1 true WO2024173735A1 (fr) 2024-08-22

Family

ID=90368092

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/016059 WO2024173735A1 (fr) 2023-02-17 2024-02-16 Rationalisation de mobilité entre réseaux de différentes générations

Country Status (1)

Country Link
WO (1) WO2024173735A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6112249A (en) * 1997-05-30 2000-08-29 International Business Machines Corporation Non-disruptively rerouting network communications from a secondary network path to a primary path
US10084731B2 (en) * 2015-03-16 2018-09-25 Webtext Holdings Limited Method and system for transferring messages between messaging systems
US20200053828A1 (en) * 2018-08-13 2020-02-13 Jayshree Bharatia Network Initiated UPF sessions Transfer
US20200068449A1 (en) * 2017-03-20 2020-02-27 Huawei Technologies Co., Ltd. Inter-Communications-System Handover Method, Device, and System
US20210092657A1 (en) * 2019-08-15 2021-03-25 Samsung Electronics Co., Ltd. Method and system for network handover on transport layer

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6112249A (en) * 1997-05-30 2000-08-29 International Business Machines Corporation Non-disruptively rerouting network communications from a secondary network path to a primary path
US10084731B2 (en) * 2015-03-16 2018-09-25 Webtext Holdings Limited Method and system for transferring messages between messaging systems
US20200068449A1 (en) * 2017-03-20 2020-02-27 Huawei Technologies Co., Ltd. Inter-Communications-System Handover Method, Device, and System
US20200053828A1 (en) * 2018-08-13 2020-02-13 Jayshree Bharatia Network Initiated UPF sessions Transfer
US20210092657A1 (en) * 2019-08-15 2021-03-25 Samsung Electronics Co., Ltd. Method and system for network handover on transport layer

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL LLC: "Default PDP context after inter-system change with only LIPA PDN Connection", 3GPP DRAFT; C1-111068, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Salt Lake City; 20110221, 14 February 2011 (2011-02-14), XP050480492 *

Similar Documents

Publication Publication Date Title
US10667207B2 (en) Access point assisted roaming
US20210022198A1 (en) Connection Reestablishment Method and Apparatus
EP1484866B1 (fr) Pré-authentification sélective avec des points d'accès primaires anticipés sans fil
CN107046696B (zh) 一种通信网络切换的方法及移动终端
TWI446816B (zh) 使用存取點資訊之小區重選
WO2018176442A1 (fr) Procédé d'accès, dispositif de réseau, dispositif terminal et dispositif amf
US10433229B2 (en) Codec-specific handover thresholds
US11375418B2 (en) Condition handover method, related devices and computer-readable storage medium
WO2019095088A1 (fr) Procédé et dispositif de commutation
WO2018119805A1 (fr) Procédé et dispositif pour régler un paramètre de sélection de réseau d'un téléphone mobile
WO2018133519A1 (fr) Procédé et appareil d'enregistrement de cellule
WO2019029618A1 (fr) Procédé de commutation de réseau d'appel vocal ims, dispositif de stockage et terminal mobile
KR20180008503A (ko) 상이한 근접 클라이언트 디바이스들 상에 설치된 클라이언트 애플리케이션들에 대한 등록들 갱신
WO2021185280A1 (fr) Procédé et appareil de communication
US9578677B2 (en) Method and apparatus for management of cellular connections
US20240334276A1 (en) Apparatuses and methods for facilitating communication services via connectionless technology
WO2020164513A1 (fr) Procédé, dispositif et système de traitement d'informations
US20240284268A1 (en) Streamlining mobility between different g-networks
WO2024173735A1 (fr) Rationalisation de mobilité entre réseaux de différentes générations
WO2020088320A1 (fr) Procédé de recherche rapide d'un réseau de haute qualité, et dispositif terminal
US20210168685A1 (en) Method and apparatus to facilitate access in networks
CN111903155B (zh) 具有核心网络改变的rat内切换
US20240292295A1 (en) Cell measurement method, cell measurement configuration method and apparatus, device, and medium
US11949748B1 (en) Method and system for managing a blocking call based on a timeout
WO2024031288A1 (fr) Appareil et procédé de transmission d'informations, dispositif de communication et support de stockage

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

Country of ref document: EP

Kind code of ref document: A1