Simplified mobility between different G networks

Abstract

Aspects of the present disclosure relate to maintaining a network connection when moving from one location to another between different techniques, such as from 2G / 3G to 5G standards, and vice versa. A Mobility Management Entity (MME) controls transfer of sessions from a 4G platform to a 2G / 3G platform, for example on the 4G platform, and / or transfer of sessions when the UE transfers from the 4G platform to a 5G platform. The MME classifies different sessions on the UE as being anchored in a GGSN, PGW, or SMF. The MME can then transfer the transferable sessions and terminate the sessions that cannot be transferred when needed. By terminating the session that cannot be transferred, the device may begin to reestablish the connection without waiting, such as without waiting for a timeout failure occurring.

Description

Background Art

[0001] Mobile computing devices, such as mobile phones, are more ubiquitous than ever before. Given the varying technologies used across various platforms in different geographic locations, maintaining network connectivity while moving from one location to another is a constant challenge. For example, some platforms utilize 2G / 3G standards, others 4G, and still others exclusively 5G. When 4G was introduced, technologies, protocols, and standards were developed to smoothly transition between 2G / 3G and 4G platforms as users moved from one location to another. Thus, when moving to an area supporting 4G technology and back, users could smoothly transition from areas supported only by legacy 2G / 3G technology without dropping packets or requiring a reconnection. Similarly, with the development of 5G platforms, specific technologies, protocols, and standards were developed to enable users to move between 4G and 5G platforms. Consequently, users moving from areas with 4G technology to areas supporting 5G technology, and vice versa, could experience a relatively smooth transition of connectivity.

[0002] However, when moving directly from 2G / 3G technology to 5G technology or from 5G technology to 2G / 3G technology, the standard requires that the device re-establish the connection or session. However, devices will sometimes move from a 2G / 3G platform to a 5G platform via a 4G platform. Given the generally smooth transitions between 2G / 3G and 4G, and similarly between 4G and 5G, when moving a session originating from 2G / 3G via 4G to 5G, the system strives to connect without incurring a reconnection requirement. However, in doing so, given the eventual requirement for reconnection, the session fails due to timeout issues because the session may not be known in the target system. This sometimes takes several minutes to reconnect. Given that 2G / 3G technology continues to be used continuously, and given that 5G is gaining popularity, such transition failures are more common and problematic.

[0003] It is with respect to these and other general considerations that the various aspects disclosed herein are made.In addition, although relatively specific problems may be discussed, it should be understood that the examples should not be limited to solving specific problems identified elsewhere in the background or this disclosure. Summary of the Invention

[0004] Various aspects of the present disclosure relate to maintaining network connectivity when moving from one location to another between different technologies, such as from 2G / 3G to 5G standards, and vice versa. 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 user mobility across platforms, and moving from 5G to a 2G / 3G form factor or vice versa over a 4G platform, to allow for relatively seamless transitions, thereby avoiding timeout failures, as described below.

[0005] When certain connections are established by a user device or user equipment to a mobility management entity (MME), for example on a 4G platform, the MME can communicate with different platforms through different gateways. The MME controls the transfer of sessions from a 4G platform to a 2G / 3G platform and / or from a 4G platform to a 5G platform. In the embodiments described herein, the MME is enhanced beyond the standard to smoothly transition sessions from a 2G / 3G platform to a 5G platform via a 4G platform, and vice versa. The MME classifies different sessions on the UE as anchored in a GGSN, PGW, or SMF. In this way, the MME is able to transfer transferable sessions and terminate sessions that cannot be transferred when needed. By terminating sessions that cannot be transferred, the device can start to re-establish the connection without waiting, for example, without waiting for a timeout failure to occur.

[0006] This summary is provided to introduce a selection of concepts in a simplified form that will be further described in the detailed description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Additional aspects, features, and / or advantages of the examples will be set forth in part in the following description and in part will be apparent from the description or may be learned through practice of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0008] Figure 1 Exemplary, non-limiting embodiments of high-level systems and environments according to various aspects described herein are shown.

[0009] Figure 2 An illustrative embodiment of a method according to various aspects described herein involving transferring control from one platform to another platform having a different platform technology is depicted.

[0010] Figure 3 An illustrative embodiment of a method according to various aspects described herein involving determining capabilities of one or more gateways is depicted.

[0011] Figure 4 A timing diagram illustrating a transition scenario from 4G to 2G / 3G in idle mode is shown in accordance with various aspects described herein.

[0012] Figure 5 A timing diagram illustrating a transition scenario from 4G to 2G / 3G in connected mode is shown in accordance with various aspects described herein.

[0013] Figure 6 A timing diagram illustrating a transition scenario from 4G to 5G in idle mode is shown in accordance with various aspects described herein.

[0014] Figure 7 A timing diagram illustrating a transition scenario from 4G to 5G in connected mode is shown in accordance with various aspects described herein.

[0015] Figure 8 is a block diagram of an exemplary, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

[0016] Figure 9 is a block diagram of an exemplary, non-limiting embodiment of a communication device in accordance with various aspects described herein. DETAILED DESCRIPTION

[0017] In the following detailed description, reference is made to the accompanying drawings which form a part thereof, and specific embodiments or examples are shown by way of illustration in the accompanying drawings. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the present disclosure. The embodiments may be practiced as methods, systems, or devices. Therefore, the embodiments may take the form of hardware implementations, complete software implementations, or implementations that combine software and hardware aspects. Therefore, the following detailed description should not be considered restrictive, and the scope of the present disclosure is defined by the appended claims and their equivalents.

[0018] When a user travels between a 2G / 3G network and a 5G network via a 4G network, if the Mobility Management Entity (MME) is unaware of the type of gateway used by the user device, the MME will attempt to transfer the session to a gateway that cannot handle the session. In addition, existing MMEs typically do not track information about the session anchor point's ability to support sessions from all radio technologies. Therefore, when a user moves from one location to another and wants to transfer the connection from 2G / 3G to 5G or vice versa, the device used by the user (i.e., user equipment (UE)) is expected to initiate an initial / new registration with the new network. This session transfer is supported when the UE travels between 2G / 3G coverage and 4G coverage, as well as mobility between 4G and 5G. However, sessions originally anchored in 2G / 3G may not be able to be seamlessly transferred to 5G. Similarly, sessions originally anchored in 5G may not be able to be seamlessly transferred to 2G / 3G. Instead, these sessions must be re-established. As a result, some sessions can be transferred while others are not. For example, if a session is created on a GGSN / PGW node associated with a node supporting 2G / 3G and 4G, and the UE moves to an AMF associated with a node supporting 5G, the MME will attempt to transfer the session to the 5G side. However, because the initial gateway is not an SMF gateway, the transfer will ultimately fail after a delay, impacting the user experience. Essentially, existing systems assume that all sessions can and will be transferred and send a success indicator back to the source. However, as described above, not all sessions are successfully transferred, so timeout failures occur for those specific sessions.

[0019] Embodiments described herein relate to establishing an "Any G" network, where "Any G" involves support and transfer of sessions between any of the 2G / 3G, 4G, and 5G platforms. More specifically, embodiments described herein relate to UE mobility across platforms, and moving from 5G to 2G / 3G forms or vice versa over a 4G platform to allow for relatively seamless transitions, thereby avoiding timeout failures, as described below.

[0020] Figure 1 An environment 100 for implementing embodiments of the present innovation is shown. Environment 100 includes a user device 102, also referred to as user equipment 102 or simply UE 102. UE 102 relates to a mobile computing device, such as a mobile phone, a laptop computer system, a connected car, etc. Those skilled in the art will appreciate that different types of UEs 102 can benefit from the innovations described herein. As shown, UE 102 can physically move to or from a second location, such as shown by UE 103. UE 103's movement to the second location is indicated by a dashed line.

[0021] like Figure 1 As shown, the UE 102 may initially connect to the 2G / 3G platform 104. One skilled in the art will understand how such a connection may be established through an RNC or the like. Furthermore, as will be understood, while connected to the 2G / 3G platform, the session may be anchored in the GGSN technology. As shown, the UE 102 may initially or after movement connect to the 4G platform 106. The UE 102 may move from the 2G / 3G 104 to the 4G platform 106. According to aspects of the embodiments herein, the UE 102 may move to a new geographic location (such movement being determined by the UE 102). Figure 1 ) and connected to the 5G platform 108. As shown, this mobility may cause a session transfer of the user data session from the 2G / 3G platform 104 to the 5G platform 108 via the 4G platform 106.

[0022] As shown in the figure, when certain connections are established by UE 102 or UE 103 via 106, the system includes a backend mobility management entity (MME) 110. As is well known, MME 110 is a network component for cellular networks (especially for 4G platforms) that is responsible for managing mobility-related functions, such as tracking the location of the device and managing handovers between calls. Figure 1 In the embodiment, the MME can communicate with different platforms via SGSN 118 to reach 2G / 3G platform 104, and via AMF 120 to reach platform 108, and communicate through GGSN / PGW node 112 or PGW / SMF 114 to route packets to and from other networks (such as public data network (PDN) 116 and / or other devices not shown). Similarly, 2G / 3G platform 104 can communicate with SGSN node 118 to route packets through GGSN / PGW 112. In addition, 5G platform 108 can communicate with AMF node 120 to route packets through PGW / SMF node 114.

[0023] In an embodiment, when UE 102 transitions to the 2G / 3G platform 104 area, MME 110 controls session transfer from 4G platform 106 to 2G / 3G platform 104. Furthermore, when UE 102 transitions to the 5G platform 108 area, MME 110 can control session transfer from 4G platform 106 to 5G platform 108. As is well known, to support 2G / 3G and 4G mobility, a combined GGSN / PGW node / gateway 112 can be used. Consequently, some 2G / 3G sessions can be anchored in the GGSN or PGW. To support 4G to 5G mobility, a combined PGW / SMF node / gateway 114 can be used. Consequently, some 5G sessions can be anchored in the SMF or PGW. These nodes and gateways are described in 3GPP standards. It should be noted that a gateway that functions as a combined GGSN / PGW / SMF can exist. If a session is anchored on such a gateway, the session can be transferred to 2G / 3G, 4G and 5G platforms. The method detailed in this disclosure covers such scenarios.

[0024] In the embodiments described herein, the MME 110 is enhanced beyond the standard to smoothly transition sessions from the 2G / 3G platform 104 to the 5G platform 108, and vice versa. In an embodiment, the MME 110 categorizes different sessions on the UE as being anchored in the GGSN, PGW, or SMF. In this way, the MME is able to transfer transferable sessions when necessary and terminate non-transferable sessions. By terminating non-transferable sessions, the device can begin reestablishing a connection without waiting, for example, for a timeout failure to occur.

[0025] Figure 2 An illustrative embodiment of a method 200 involving transferring control from one platform to another platform having a different platform technology is depicted in accordance with various aspects described herein. Figure 2 The general order of operations of method 200 is shown in FIG. Although multiple operations are shown, method 200 may include more or fewer steps, or the order of the steps may be arranged in a similar manner. Figure 2 The method 200 may be implemented as computer-executable instructions that are executed by a computer system and encoded or stored on a computer-readable medium. Furthermore, the method 200 may be implemented by gates or circuits associated with a processor, ASIC, FPGA, SOC, or other hardware device. Hereinafter, the method 200 will be explained with reference to the systems, components, devices, modules, software, data structures, data characteristic representations, signaling diagrams, methods, and the like described in conjunction with the other figures described herein.

[0026] Method 200 generally begins with a setup operation 202, where a UE is setup on an MME. Those skilled in the art will understand how to setup a UE on an MME to handle mobility for the device.

[0027] Next, a receiving operation 204 receives an indication to transfer or initiate a handover from one platform to another. The receiving operation 204 is known to those skilled in the art and may be initiated by the device or by an intermediate network component that recognizes the need to handover the UE to another node or network. This event occurs when the UE moves from one location to another location covered by a different network platform, such as Figure 1 As shown. A handover request is received when the device is in active mode or connected mode, for example, when the UE device is actively used, such as during a phone call and / or when an application on the device is sending / receiving data packets. Otherwise, the UE is considered to be in idle mode, and thus a receiving operation 204 receives a transfer of control request, such as via a location update signal or a registration request. A location update signal is generated when the device moves to a 2G / 3G platform area. A registration request is generated when the device moves to a 5G platform area.

[0028] Once an indication to transfer control or handover a session is received, a determination operation 206 determines the different active sessions that can be transferred. Essentially, when a device is connected to a network, different sessions may be established within the network, each session having different communication processes that may be occurring, for example, different applications may be actively communicating with the network using different session identifiers. Anchoring of each session occurs during the initial instantiation of the session. The determination operation 206 evaluates each session and the anchoring information for each session to determine whether it can be transferred to the new network. Therefore, as shown, there is an alternative or additional determination step 208 that can determine which sessions cannot be transferred. Below in conjunction with Figure 3 The two determination operations are discussed in more detail.

[0029] Once it is identified that sessions can be transferred and / or cannot be transferred, operation 210 includes the identification of those sessions that can be transferred in response to the transfer request. This inclusion allows the next processing 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, session information related to the sessions that can be transferred will be included in the SGSN context response signal. Similarly, when in idle mode and transferring from a 4G platform area to a 5G platform area, session information related to the sessions that can be transferred will be included in the context response to the registration request. Otherwise, when in connected mode and transferring from a 4G platform area to a 2G / 3G or 5G area, session information related to the sessions that can be transferred will be included in the forward relocation request signal.

[0030] Next, or in parallel, a deactivation operation 212 deactivates or terminates all sessions that cannot be transferred. By proactively terminating the sessions, the UE is able to reestablish connections for those sessions, as would have been required in a direct transfer from 2G / 3G to 5G. In an embodiment, the deactivation or termination of the non-transferable sessions occurs substantially simultaneously with the transfer of the transferable sessions. That is, the deactivation is performed proactively without waiting for a timeout error.

[0031] Finally, the switch or transfer is completed at a completion step 214 .

[0032] Figure 3 An illustrative embodiment of a method 300, in accordance with various aspects described herein, is depicted, involving determining whether different sessions can be transferred from one platform to another platform having different platform technology. At a high level, method 300 involves marking sessions within an MME based on the gateway at which these sessions were initially established, e.g., anchored. This process can also be considered to classify sessions. Using the classification, method 200 discussed above can, for example, determine which sessions can be transferred, at step 206, and / or which sessions cannot be transferred, at step 208.

[0033] Method 300 relates to a specific embodiment for classifying different sessions. Method 300 begins with a query operation 302, which queries the canonical node name of a gateway to obtain the gateway's service parameters. In an embodiment, this process step uses a NAPTR query to obtain such information. NAPTR stands for the Name Authority Pointer type of resource record in the Internet's DNS, or Domain Name System. Those skilled in the art will appreciate that a NAPTR query can be performed for each session's anchor gateway to identify specific information about the gateway and thereby determine the gateway's capabilities.

[0034] Next, at determination operation 304, method 300 determines whether the NAPTR response includes a service parameter with "x-3gpp-ggsn" in the response. If so, the process branches "yes" to assertion operation 306 to indicate that the session is GGSN transferable and, therefore, can be transferred to an area using 2G / 3G protocols. That is, the 2G / 3G session can be anchored on a GGSN (Gateway GPRS Support Node), for example, such an anchored session has GGSN functional capabilities. Assertion operation 306 can also mark or set the session as GGSN transferable to a 2G / 3G system. It will be appreciated by those skilled in the art that there may be other query and response indicators associated with the session that can be used to assert transferability to 2G / 3G, with "x-3gpp-ggsn" being just one specific example.

[0035] Next, in an embodiment, after operations 304 and / or 306, the process proceeds to determination operation 308. Determination operation 308 determines whether the NAPTR response includes a service parameter with "nc-smf" in the response. If included, the process branches "yes" to assertion operation 310 to indicate that the session is anchored using SMF (session management function) and has SMF functions or capabilities, such as being used in conjunction with 5G protocols. Assertion operation 310 may also set or mark the session as SMF transferable to 5G, so that the session can be transferred from the 4G platform area to the 5G platform area without terminating the session. It will be understood by those skilled in the art that there may be other query and response indicators associated with the session that can be used to infer transferability to 5G, and "nc-smf" is only a specific example.

[0036] Next, a store operation 312 stores any information related to session transferability to the MME. Thus, when required, the MME will be able to identify those sessions that can be transferred and those sessions that must be terminated. As shown, both determination operation 304 and determination operation 308 can determine that a session can be marked as GGSN transferable and SMF transferable, such that the session can be gracefully transferred to a 2G / 3G or 5G platform without termination, and will be marked as such. Furthermore, a session may not be able to be gracefully transferred if, for example, it does not have the "x-3gpp-ggsn" or "nc-smf" service parameters. If so, the process will proceed to store operation 312, but nothing will be marked in that case. In summary, in Figure 3 Following the illustrated process 300, all four combinations of markings are possible: transferable to 2G / 3G and 5G; transferable to 2G / 3G but not to 5G; transferable to 5G but not to 2G / 3G; and transferable to neither 2G / 3G nor 5G. In the case where the session is marked as transferable to 2G / 3G and 5G, the gateway has triple capabilities: GGSN / PGW / SMF. In the case where the session is marked as transferable to 2G / 3G but not to 5G, the gateway is a GGSN / PGW. In the case where the session is marked as transferable to 5G but not to 2G / 3G, the gateway is a PGW / SMF. In the case where the session is marked as not transferable to 2G / 3G and 5G, the gateway is a pure PGW and has no GGSN or SMF capabilities at all. In the last case, the session can only stay on the 4G platform, but this is uncommon.

[0037] As described above, the storage operation 312 essentially marks and / or stores the session data for each session as transferable to the GGSN and / or transferable to the SMF, depending on the capabilities of the gateway used for the session, if any such information exists. Alternatively, the capabilities of the gateway can be administratively defined on the MME. This is provided as an alternative to a DNS query that uses the name of the gateway to obtain a NAPTR record to determine the capabilities. If the network operator prefers not to use DNS, they can define the capabilities of each gateway via static configuration on the MME. For example, the gateway can be defined as PGW / GGSN or PGW / SMF or PGW or GGSN / PGW / SMF.

[0038] Figure 4 A timing diagram is shown when a UE 402 moves from one location substantially connected to a 4G platform to another location and needs to transfer to a 2G / 3G platform. Figure 4 The control operation in idle mode is shown. A UE is considered to be in idle mode when it is 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. When the device (UE 402) is in a 2G / 3G platform area, a routing area update signal will be sent to the network. Those skilled in the art will understand that such an update request is sent because the device periodically does so to obtain information and / or notify the network of its location.

[0039] As shown, UE 402 communicates with SGSN 406 (Serving GPRS Support Node) through a Base Station System or Radio Network Controller (BSS / RNC) 404. The SGSN communicates with MME 408, which then communicates with SGW 410, which in turn communicates with PGW 412.

[0040] First, UE 402 is established / registered with MME 408, as shown in block 414, so that MME 408 can control the mobility of UE 402 and the transfer of connections between networks. As UE 402 moves, a routing area update signal 416a is transmitted to BSS / RNC 404, which passes signal 416b to SGSN 406. Routing area updates (RAUs) are typically delivered to BSS / RNC to notify the network of a UE's location change. Next, an SGSN context request signal 418 requests information from MME 408, such as device location or session information.

[0041] In response, the MME will create a response to the SGSN. However, before responding to the SGSN, the MME 408 evaluates the existing sessions for the UE and identifies those sessions that can be transferred to the 2G / 3G platform, as shown in block 420. In an embodiment, identifying these sessions as transferable may involve the above in conjunction with Figure 3 The method steps described. In alternative embodiments, other methods may be used to identify transferable sessions. For example, it is contemplated that future sessions may include transferability information during setup, such that the MME 408 can simply review the setup information to determine transferability.

[0042] Next, the MME 408 will send an 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 sessions that will not be transferred.

[0043] As is well known, the SGSN will respond with an SGSN context confirm signal 424. Next, the MME 408 deactivates the sessions that cannot be transferred, for example, by transmitting a deactivation signal 426 to the SGW 410. In turn, the SGW 410 will transmit a deactivation signal 428 to the PGW 412. The deactivation signals 426 and 428 will essentially deactivate or terminate any sessions that cannot be transferred, such as sessions anchored in the SMF. This termination allows the UE 402 to reestablish those sessions on the new platform as needed.

[0044] Next, as will be understood by those skilled in the art, signal 430 continues with a Routing Area Update (RAU). Continuation of RAU 430 occurs after the context confirmation signal step 424. While shown as occurring after the deactivation process steps 426 and 428, it can occur before, after, or in parallel with the deactivation process. Finally, SGSN 406 transmits an acceptance indicating an update of the active session at 432, which is transmitted by BSS / RNC 404 to UE 402 at 434.

[0045] Figure 5A timing diagram is shown when a UE 502 moves from one location substantially connected to a 4G platform to another location in connected mode and needs to transfer to a 2G / 3G platform. In connected mode, the UE 502 actively uses the network for data and / or voice services and exchanges data with the network. As will be appreciated by those skilled in the art, the UE 502 in connected mode can communicate with the MME 506 via the eNB 504. As described above, the MME 506 can communicate with the SGSN 508, which in turn communicates with the BSS / RNC 510, which in turn can communicate with the SGW 512 and the PGW 514.

[0046] Initially, the UE 502 is established / registered with the MME 506, as shown in block 516, so that the MME 506 can control the mobility of the UE 502 and the transfer of connections between networks. As the UE 502 moves, a handover signal 518 is transmitted from the eNB to the MME 506. This handover signal 518 is known and relates to the eNB sensing the movement of the UE, such that a handover or handover is requested. Next, a forward relocation request is generated by the MME 506. However, before forwarding the relocation request, the MME 506 evaluates the existing sessions for the UE 502 and identifies those sessions that can be transferred to the 2G / 3G platform, as shown in block 520. In an embodiment, identifying these sessions as transferable may involve the above in conjunction with Figure 2 Described or combined with the above Figure 3 and Figure 4 The methodological steps discussed.

[0047] Next, MME 506 forwards relocation request signal 522 to SGSN 508, which forwards it to RNC / BSS 510. Signals 522 and 524 will include identification information for those sessions that can be transferred. Such signals may not include session information for those sessions that will not be transferred.

[0048] Next, signals 526 and 528 will continue to switch or handover 526 and will continue to complete the RAU process 528 as will be understood by those skilled in the art.

[0049] At some point, after forwarding the transmission of the relocation request signal, the MME 506 deactivates any sessions that cannot be transferred, for example, by transmitting a deactivation signal 530 to the SGW 512. The SGW 512 will then transmit a deactivation signal 532 to the PGW 514. The deactivation signals 530 and 532 will essentially deactivate or terminate any sessions that cannot be transferred, such as sessions anchored in the SMF. This termination allows the UE to begin reestablishing those sessions on the new platform as needed without further delay.

[0050] Figure 6 A timing diagram is shown according to another scenario contemplated herein when a UE 602 has moved from one location substantially connected to a 4G platform to another location and needs to transfer to a 5G platform. Figure 6 Figure 2 shows control operations in idle mode. As described above, a UE is considered to be in idle mode when it is 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. In this state, when the UE is in a 5G-capable area, the UE will send a registration request, in which the device is requesting information from the network.

[0051] As will be appreciated by those skilled in the art, in this scenario, the UE 602 communicates with the AMF 606 via the gNB 604. The AMF 606 communicates with the MME 608, which then communicates with the SGW 610, which in turn communicates with the PGW 612.

[0052] First, UE 602 is established / registered with MME 608, as shown in block 614, so that MME 608 can control UE 602's mobility and the transfer of connections between networks. As UE 602 moves, a registration request 616a is transmitted to gNB 604, which passes signal 616b to AMF 606. Registration requests are well known to those skilled in the art. Next, a context request signal 618 requests information from MME 608, such as device location or session information, or other context information.

[0053] In response, the MME 608 will create a response to the AMF 606. However, before responding to the AMF 606, the MME 608 evaluates the existing sessions for the UE 602 and identifies those sessions that can be transferred to the 5G platform, as shown in block 620. In an embodiment, identifying these sessions as transferable may involve the above in conjunction with Figure 2 、 Figure 3 、 Figure 4 and Figure 5 The method steps described.

[0054] Next, the MME 608 will send a context response signal 622, which will include identification information for those sessions that can be transferred. It may not include session information for those sessions that will not be transferred.

[0055] As is well known, the AMF 606 will respond with a context confirmation signal 624. Subsequently, as will be understood by those skilled in the art, a signal 626 continues with the mobility registration and session initiation for the transferable session.

[0056] At the same time, MME 608 deactivates the sessions that cannot be transferred, for example, by transmitting a deactivation signal 630 to SGW 610. SGW 610, in turn, transmits a deactivation signal 632 to PGW 612. Deactivation signals 630 and 632 will essentially deactivate or terminate any sessions that cannot be transferred, such as sessions anchored in the GGSN. This termination allows UE 602 to reestablish those sessions on the new platform as needed.

[0057] Finally, the AMF 606 transmits an acceptance of the registration indicating the active session and PDU session status at 434, which is then transmitted by the gNB 604 to the UE 602 at 636.

[0058] Figure 7 A timing diagram is shown when a UE 702 moves from one location substantially connected to a 4G platform to another location and needs to transition to a 5G platform in connected mode. In connected mode, as described above, the UE 702 actively uses the network for data and / or voice services and exchanges data with the network. As will be appreciated by those skilled in the art, the UE 702 in connected mode can communicate with the MME 706 via the eNB 704. As described above, the MME 706 can communicate with the AMF 708, which in turn communicates with the gNB 710, which in turn can communicate with the SGW 712 and the PGW 714.

[0059] Initially, the UE 702 is established / registered with the MME 706, as shown in block 718, so that the MME 706 can control the mobility of the UE 702 and the transfer of connections between networks. As the UE 702 moves, a handover signal 720 is transmitted from the eNB 704 to the MME 706. This handover signal 720 is known and involves the eNB 704 sensing the movement of the UE 702, such that a handover or handover is requested. Next, a forward relocation request is generated by the MME 706. However, before forwarding the relocation request, the MME 706 evaluates the existing sessions for the UE 702 and identifies those sessions that can be transferred to the 5G platform, as shown in block 722. In an embodiment, identifying these sessions as transferable may involve the above in conjunction with Figure 2 Described or combined with the above Figure 3 、 Figure 4 、 Figure 5 and Figure 6 The methodological steps discussed.

[0060] Next, MME 706 forwards relocation request signal 724 to AMF 708, which forwards handover request 726 to gNB 710. Signals 724 and 726 include identification information for sessions that can be transferred. Such signals may not include session information for sessions that will not be transferred.

[0061] Next, signals 728 and 730 will continue with the handover or handover 728 and will continue to complete the mobility registration process 730 as will be understood by those skilled in the art.

[0062] Next, MME 706 deactivates the sessions that cannot be transferred, for example, by transmitting a deactivation signal 732 to SGW 712. SGW 712, in turn, transmits a deactivation signal 734 to PGW 714. Deactivation signals 732 and 734 will essentially deactivate or terminate any sessions that cannot be transferred, such as sessions anchored in the GGSN. This termination allows UE 702 to reestablish those sessions on the new platform as needed.

[0063] The systems and methods according to various aspects described herein provide numerous benefits. For example, users can move more seamlessly from one network to another because devices will more quickly recognize the deactivation of some sessions, allowing the re-establishment process to occur more quickly, reducing timeout failures, etc. Not only will less time be lost, but the risk of losing data will also be beneficial.

[0064] Figure 8 A block diagram of a computing environment according to various aspects described herein is shown. To provide additional context for various embodiments described herein, Figure 8The following discussion is intended to provide a brief, general description of a suitable computing environment 800 in which various embodiments of the subject disclosure may be implemented. In particular, the computing environment 800 may be used in implementations such as MMEs, UEs, and the like. Each of these devices may be implemented via computer-executable instructions that may be executed on one or more computers and / or combined with other program modules and / or as a combination of hardware and software.

[0065] Generally, program modules include routines, programs, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In addition, those skilled in the art will appreciate that these methods can be practiced with other computer system configurations, including single-processor computer systems or multi-processor computer systems, minicomputers, mainframe computers, as well as personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which can be operatively coupled to one or more associated devices.

[0066] As used herein, processing circuitry includes one or more processors and other specialized circuitry, such as application-specific integrated circuits, digital logic circuits, state machines, programmable gate arrays, or other circuitry that processes input signals or data and generates output signals or data in response. It should be noted that any functions and features described herein in conjunction with the operation of a processor may also be performed by a processing circuit.

[0067] It should be understood that the embodiments of the present invention can also be practiced in a distributed computing environment, where certain tasks are performed by remote processing devices linked through a communications network. In a distributed computing environment, program modules can be located in local memory storage devices and remote memory storage devices.

[0068] Computing devices typically include various media, which may include computer-readable storage media and / or communication media, the two terms being used differently herein as follows. Computer-readable storage media can be any available storage media that can be accessed by a computer and includes both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable storage media can be implemented in conjunction with any method or technology for storing information such as computer-readable instructions, program modules, structured data, or unstructured data.

[0069] Computer-readable storage media may include, 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 device, magnetic cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, or other tangible and / or non-transitory media that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" are used herein as modifiers to apply to storage devices, memories, or computer-readable media and should be understood to exclude and not disclaim all standard storage devices, memories, or computer-readable media that transmit only transient signals themselves.

[0070] Computer-readable storage media can be accessed by one or more local or remote computing devices, eg, via access requests, queries, or other data retrieval protocols, for various operations regarding the information stored by the media.

[0071] Communication media typically embodies computer-readable instructions, data structures, program modules, or other structured or unstructured data in a data signal (such as a modulated data signal, such as a carrier wave or other transport mechanism), and includes any information delivery or transmission media. The term "modulated data signal" or multiple modulated data signals refers to a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal or signals. By way of example, and not limitation, communication media include wired media (such as a wired network or direct-wired connection), and wireless media (such as acoustic, RF, infrared, and other wireless media).

[0072] Reference again Figure 8 , an example environment may include a computer 802, which includes 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 may be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be used as the processing unit 804.

[0073] The system bus 808 can be any of several types of bus structures, which 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 includes ROM 810 and RAM 812. A basic input / output system (BIOS), containing the basic routines that help transfer information between elements within the computer 802, such as during startup, can be stored in a non-volatile memory such as ROM, an erasable programmable read-only memory (EPROM), or an EEPROM. RAM 812 can also include high-speed RAM, such as static RAM for caching data.

[0074] The computer 802 may also include an internal hard disk drive (HDD) 814 (e.g., EIDE, SATA), which may also be configured for external use on a suitable chassis (not shown), and / or a magnetic floppy disk drive (FDD) 816 (e.g., to read from or write to a removable disk 818) and / or an optical drive 820 (e.g., to read from or write to a CD-ROM disk 822 or other high-capacity optical media such as a DVD). The HDD 814, magnetic FDD 816, and optical drive 820 may be connected to the system bus 808 via 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 may include at least one or both of a Universal Serial Bus (USB) and an Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technology. Other external drive connection technologies are within the contemplation of the embodiments described herein.

[0075] The drives and their associated computer-readable storage media provide non-volatile storage for data, data structures, computer-executable instructions, and the like. The drives and storage media accommodate the storage of any data in a suitable digital format for the computer 802. Although the above description of computer-readable storage media refers to hard disk drives (HDDs), removable magnetic disks, and removable optical media (such as CDs or DVDs), it will be understood by those skilled in the art that other types of computer-readable storage media (such as zip drives, cassettes, flash memory cards, magnetic tape cartridges, etc.) may also be used in the example operating environment, and further, any such storage media may contain computer-executable instructions for performing the methods described herein.

[0076] A number of program modules may be stored in the drives and RAM 812, including 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 may also be cached in RAM 812. The systems and methods described herein may be implemented using various commercially available operating systems or combinations of operating systems.

[0077] A user may enter commands and information into the computer 802 through one or more wired / wireless input devices, such as a keyboard 838 and a pointing device such as a mouse 840. Other input devices (not shown) may include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus, a touch screen, and the like. These and other input devices are typically connected to the processing unit 804 through an input device interface 842, which may be coupled to the system bus 808, but may be connected through other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR port, and the like.

[0078] A monitor 844 or other type of display device may also be connected to the system bus 808 via an interface such as a video adapter 846. It should also be understood that in alternative embodiments, the monitor 844 may be any display device (e.g., another computer with a display, a smartphone, a tablet computer, etc.) that receives display information associated with the computer 802 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 844, computers typically include other peripheral output devices (not shown), such as speakers, printers, etc.

[0079] The computer 802 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer 848, via wired and / or wireless communications. The remote computer(s) 848 can be workstations, server computers, routers, personal computers, portable computers, microprocessor-based entertainment devices, peer devices, or other public network nodes, and typically include many or all of the elements described with respect to the computer 802, although for simplicity, only remote memory / storage device 850 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 852 and / or a larger network, such as a wide area network (WAN) 854. Such LAN and WAN networking environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.

[0080] When used in a LAN networking environment, 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 may also include a wireless AP provided thereon for communicating with the adapter 856.

[0081] When used in a WAN networking environment, the computer 802 may include a modem 858, or may be connected to a communications server on the WAN 854, or have other means for establishing communications over the WAN 854 (e.g., over the Internet). The modem 858 may be internal or external and a wired or wireless device that may be connected to the system bus 808 via the input device interface 842. In a networked environment, program modules depicted relative to the computer 802, or portions thereof, may be stored in the remote memory / storage device 850. It will be appreciated that the network connections shown are examples and that other means of establishing a communications link between the computers may be used.

[0082] The computer 802 may be operable to communicate with any wireless device or entity that is operatively configured for wireless communication, such as a printer, scanner, desktop and / or portable computer, portable data assistant, communication satellite, any device or location associated with a wirelessly detectable tag (e.g., a kiosk, newspaper rack, restroom), and telephone. This may include Wireless Fidelity (Wi-Fi) and Wireless technology. Therefore, the communication can be a predefined structure like a conventional network, or just an ad hoc communication between at least two devices.

[0083] Wi-Fi can allow you to connect to the Internet from your couch at home, your room in a hotel, or a conference room at work without wires. Wi-Fi is a wireless technology similar to that used in cellular phones that enables such devices (e.g., computers) to send and receive data anywhere in homes and things, within range of a base station. Wi-Fi networks use radio technology known as IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, and fast wireless connections. Wi-Fi networks 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, for example, in the unlicensed 2.4 and 5 GHz radio bands, or with products that have two frequency bands (dual-band), so the network can provide real-world performance similar to the basic 10BaseT wired Ethernet used in many offices.

[0084] Now go to Figure 9, shows an illustrative embodiment of a communication device 900. The communication device 900 can be used as an illustrative embodiment of a device such as the user computer device 102 and other devices. For example, the communication device 900 can operate as a UE as described herein.

[0085] The communication device 900 may include a wired and / or wireless transceiver 902 (herein, transceiver 1002), a user interface (UI) 904, a power supply 914, a position receiver 916, a motion sensor 918, a direction sensor 920, and a controller 906 for managing its operation. The transceiver 902 may support short-range or long-range wireless access technologies, such as WiFi or cellular communication technology, etc. Cellular technology may include, for example, CDMA-1X, UMTS / HSDPA, GSM / GPRS, TDMA / EDGE, EV / DO, WiMAX, SDR, LTE, and other emerging next-generation wireless communication technologies. The transceiver 902 may also be adapted to support circuit-switched wired access technologies (such as PSTN), packet-switched wired access technologies (such as TCP / IP, VoIP, etc.), and combinations thereof.

[0086] The UI 904 may include a depressible or touch-sensitive keypad or touch screen 908 for manipulating the operation of the communication device 1000. The keypad 908 may be an integral part of the housing assembly of the communication device 900, or may be connected via a wired interface (e.g., a USB cable) or a device that supports, for example, The keypad 908 may be a separate device operatively coupled to a wireless interface of the communication device 900. The keypad 908 may represent a numeric keypad and / or a QWERTY keypad with alphanumeric keys commonly used by telephones. The UI 904 may also include a display 910, which may be any suitable display technology for conveying images to an end user of the communication device 900. In embodiments where the display 910 is touch-sensitive, a portion or all of the keypad 908 may be presented via the display 910 with navigation features.

[0087] The display 910 can also be used as a user interface for detecting user input using touch screen technology. As a touch screen display, the communication device 900 can be suitable for presenting a user interface having graphical user interface (GUI) elements that can be selected by the user using the touch of a finger. The display 910 can be equipped with capacitance, resistance, or other forms of sensing technology to detect how much surface area the 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 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 a separate device communicatively coupled thereto via a wired binding interface (such as a cable) or a wireless interface.

[0088] The UI 904 may also include an audio system 912 that utilizes audio technology to transmit low-volume audio (such as audio heard near a person's ear) and high-volume audio (such as a speakerphone for hands-free operation). The audio system 912 may also include a microphone for receiving audible signals from the end user. The audio system 912 may also be used for speech recognition applications. The UI 904 may also include an image sensor 913, such as a charge-coupled device (CCD) camera for capturing still or moving images.

[0089] The power supply 914 can utilize common energy management technologies, such as replaceable and rechargeable batteries, power conditioning technologies, and / or charging system technologies, for supplying energy to components of the communication device 900 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize an external power source, such as DC power supplied through a physical interface (e.g., a USB port or other suitable binding technology).

[0090] The location receiver 916 may utilize location technology, such as a GPS receiver capable of assisting the Global Positioning System (GPS), to identify the location of the communication device 900 based on signals generated by a constellation of GPS satellites, which may be used to facilitate location services such as navigation. The motion sensor 918 may utilize motion sensing technology, such as an accelerometer, a gyroscope, or other suitable motion sensing technology, to detect the movement of the communication device 900 in three-dimensional space. The direction sensor 920 may utilize direction sensing technology, such as a magnetometer, to detect the direction of the communication device 900 (north, south, west, and east, as well as combinations thereof in degrees, minutes, or other suitable directional measures).

[0091] The communication device 900 can use the transceiver 902 to determine the presence of cellular, WiFi, or wireless networks through sensing techniques, such as using received signal strength indicator (RSSI) and / or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 906 may utilize computing technology such as a microprocessor, a digital signal processor (DSP), a programmable gate array, an application specific integrated circuit, and / or a video processor with associated storage memory such as flash memory, ROM, RAM, SRAM, DRAM, or other storage technology for executing computer instructions, controlling, and processing data provided by the aforementioned components of the communication device 900.

[0092] Unless the context clarifies otherwise, the terms "first," "second," "third," etc., as used in the claims are for clarity only and do not indicate or imply any temporal order. For example, "a first determination," "a second determination," and "a third determination" do not indicate or imply that the first determination will be made before the second determination, or vice versa.

[0093] In this specification, terms such as "storage," "storage device," "data storage," "data storage device," "data storage device," "database," and substantially any other information storage component related to the operation and functionality of a component refer to a "memory component" or an entity embodied in a "memory" or a component that includes a memory. It should be understood that the memory components described herein can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory, as an illustration and not limitation, volatile memory, non-volatile memory, disk storage devices, and memory storage devices. In addition, non-volatile 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 include random access memory (RAM) that acts as an external cache memory. As an illustration and not limitation, 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), synchronous link DRAM (SLDRAM), and direct RAM RAM (DRRAM). Additionally, the disclosed memory components of the systems or methods herein are intended to include, but are not limited to comprising, these and any other suitable types of memory.

[0094] In addition, it should be noted that the disclosed subject matter can be practiced using other computer system configurations, including single-processor or multi-processor computer systems, small computing devices, mainframe computers and personal computers, handheld computing devices (e.g., PDAs, phones, smart phones, watches, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronic devices, etc. The illustrated aspects can also be practiced in distributed computing environments, where tasks are performed by remote processing devices linked through a communications network; however, some aspects (if not all aspects) of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in local and remote memory storage devices.

[0095] In one or more embodiments, information about the use of services may be generated, including services accessed, media consumption history, user preferences, and the like. This information may be obtained through various methods, including user input, detecting communication type (e.g., video content versus audio content), analyzing content streams, sampling, and the like. The generation, acquisition, and / or monitoring of this information may be responsive to authorization provided by a user. In one or more embodiments, analysis of the data may be subject to authorization from the user(s) associated with the data, such as opt-in, opt-out, confirmation requirement, notification, selective authorization based on the type of data, and the like.

[0096] As used in some contexts in this application, in some embodiments, the terms "component", "system" etc. are intended to refer to or include computer-related entities or entities related to operating devices with one or more specific functions, wherein the entity can be a combination of hardware, hardware and software, software or software in execution. As an example, a component can be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a computer-executable instruction, a program and / or a computer running on a processor. As an illustration and not limitation, both the application and the server running on the server can be components. One or more components can reside in a process and / or execution thread, and the component can be located on a computer and / or be distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate via local and / or remote processes, such as according to signals with one or more data packets (for example, data from a component interacting with another component in a local system, a distributed system, and / or data interacting with other systems via a signal across a network such as the Internet). As another example, a component may be a device having a specific functionality provided by a mechanical part operated by an electrical or electronic circuit, which is operated by a software or firmware application executed by a processor, where the processor may be internal or external to the device and executes at least a portion of the software or firmware application. As yet another example, a component may be a device having a specific functionality provided by an electronic component without a mechanical part, where the electronic component may include a processor therein to execute the software or firmware that at least partially imparts the functionality to the electronic component. Although various components have been shown as separate components, it should be understood that multiple components may be implemented as a single component, or a single component may be implemented as multiple components, without departing from the example embodiments.

[0097] In addition, the various embodiments may be implemented as methods, apparatus, or articles 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. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage medium / computer-readable communication medium. For example, computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs)), smart cards, and flash memory devices (e.g., cards, sticks, key drives). Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope or spirit of the various embodiments.

[0098] In addition, the words "example" and "exemplary" are used herein to mean serving as an example or illustration. Any embodiment or design described herein as an "example" or "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. On the contrary, the use of the words "example" or "exemplary" is intended to present concepts in a concrete way. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the aforementioned instances. In addition, the articles "a" and "an" used in this application and the appended claims should generally be interpreted to mean "one or more" unless otherwise specified or clear from the context to point to a singular form.

[0099] In addition, terms such as "user equipment," "mobile station," "mobile," "subscriber station," "access terminal," "terminal," "handset," "mobile device," and the like (and / or terms representing similar terms) may refer to a wireless device used by a subscriber or user of a wireless communication service to receive or transmit data, control, voice, video, sound, gaming, or substantially any data or signaling stream. The foregoing terms may be used interchangeably herein and with reference to the associated drawings.

[0100] Furthermore, the terms "user," "subscriber," "customer," "consumer," and the like are used interchangeably throughout this document unless the context warrants a specific distinction between the terms. It should be understood that such terms may refer to a human entity or an automated component supported by artificial intelligence (e.g., at least the ability to reason based on complex mathematical formalisms), which may provide simulated vision, voice recognition, and the like.

[0101] As used herein, the term "processor" may refer to substantially any computing processing unit or device, including but not limited to: a single-core processor; a single processor with software multi-threaded execution capability; a multi-core processor; a multi-core processor with software multi-threaded execution capability; a multi-core processor with hardware multi-threading technology; a parallel platform; and a parallel platform with distributed shared memory. In addition, a processor may 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), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The processor may utilize nanoscale architectures, such as, but not limited to, transistors, switches, and gates based on molecules and quantum dots, in order to optimize space usage or enhance the performance of user devices. The processor may also be implemented as a combination of computing processing units.

[0102] As used herein, terms such as "data store," "data storage," "database," and substantially any other information storage component related to the operation and functionality of a component refer to a "memory component" or an entity embodied in "memory" or a component that includes memory. It should be understood that the memory components or computer-readable storage media described herein can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory.

[0103] What has been described above merely includes examples of various embodiments. Of course, for purposes of describing these examples, it is not possible to describe every conceivable combination of components or methods, but one of ordinary skill in the art will recognize that many other combinations and permutations of the present embodiments are possible. Therefore, the embodiments disclosed and / or claimed herein are intended to cover all such changes, modifications, and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent the term "includes" is used in the detailed description or claims, such term is intended to be inclusive in a manner similar to the term "comprising," as "comprising" is interpreted when used as a transition word in a claim.

[0104] Although specific embodiments have been shown and described herein, it should be understood that any arrangement that achieves the same or similar purpose may replace the embodiments described or shown in this subject disclosure. This subject disclosure is intended to cover any and all adaptations or variations of various embodiments. The combination of the above-mentioned embodiments and other embodiments not specifically described herein may be used in this subject disclosure. For example, one or more features from one or more embodiments may be combined with one or more features of one or more other embodiments. In one or more embodiments, the features that are stated positively may also be stated negatively and excluded from the embodiments with or without being replaced by another structural and / or functional feature. The steps or functions described in the embodiments of this subject disclosure may be performed in any order. The steps or functions described in the embodiments of this subject disclosure may be performed alone or in combination with other steps or functions of this disclosure, as well as from other embodiments or from other steps not described in this subject disclosure. In addition, more or fewer features than all the features described in the embodiments may also be utilized.

Claims

1. A computing system that performs mobility management entity functions, the computing system comprising: a processing system comprising a processor; as well as A memory storing executable instructions that, when executed by the processing system, facilitate performance of operations comprising: classifying one or more sessions of a user device; receiving an instruction to transfer from a first platform to a second platform; Based on session classification, identify transferable sessions and non-transferable sessions; sending a response signal indicating that the session can be transferred; and The non-transferable session is deactivated.

2. The computing system of claim 1 , wherein the operations further comprise: The transferable session is transferred to the second platform.

3. The computing system of claim 2, wherein the deactivation of the non-transferable session occurs substantially simultaneously with the transfer of the transferable session. 4 . The computing system of claim 1 , wherein the first platform operates with 4G technology and the second platform operates with 2G or 3G technology.

5. The computing system of claim 1, wherein the first platform operates with 4G technology and the second platform operates with 5G technology.

6. The computing system of claim 1 , wherein the classification operation further comprises: Perform domain name service queries to determine the service parameters of different gateways.

7. A method for transferring a session of a user device, comprising: classifying one or more sessions of the user device; receiving an instruction to transfer from a first platform to a second platform; Based on session classification, identify transferable sessions and non-transferable sessions; sending a response signal indicating that the session can be transferred; as well as The non-transferable session is deactivated.

8. The method according to claim 7, further comprising: The transferable session is transferred to the second platform.

9. The method of claim 8, wherein the deactivation of the non-transferable session occurs substantially simultaneously with the transfer of the transferable session.

10. The method of claim 7, wherein the first platform operates with 4G technology and the second platform operates with 2G or 3G technology.

11. The method of claim 7, wherein the first platform operates with 4G technology and the second platform operates with 5G technology.

12. The method according to claim 7, wherein the classification operation further comprises: Perform domain name service queries to determine the service parameters of different gateways.

13. The method of claim 7, wherein the classification further comprises: performing a name authority pointer query for the canonical node name of the gateway for each session to retrieve said service parameters for said gateway; as well as evaluating the service parameter to determine whether the session is anchored in the second platform; as well as If the session is not anchored in the second platform, marking the session as not transferable to the second platform.

14. A non-transitory computer-readable medium storing instructions for transferring a session in conjunction with performing mobility management entity functions, the instructions, when executed by one or more processors of a computing device, causing the computing device to perform a method comprising: classifying one or more sessions of the user device; receiving an instruction to transfer from a first platform to a second platform; Based on session classification, identify transferable sessions and non-transferable sessions; sending a response signal indicating that the session can be transferred; as well as The non-transferable session is deactivated.

15. The non-transitory computer readable medium of claim 14, wherein the method further comprises: The transferable session is transferred to the second platform.

Images