Selective switching or redirection based on interface availability
By transmitting context information on the interface between AMF and MME and selectively performing handover or redirection, the handover quality problem caused by the unavailability of the N26 interface between 5G and LTE systems is solved, and the user equipment is realized in different wireless communication systems Efficient session switching and service continuity between.
Patent Information
- Application Number
- CN201880096786.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2018-06-22
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2038-06-22
AI Technical Summary
The N26 interface between 5G and LTE systems is unavailable in some cases, resulting in the impact of the handover quality and session continuity of user equipment between different wireless communication systems.
By transmitting context information on the interface between the AMF and the MME, selectively performing handover or redirection, the switching or redirection of the call session of the user equipment from the first RAN to the second RAN is achieved using a shared user plane entity, ensuring the session Continuity.
Improves the quality of user equipment call session switching between 5G and 4G wireless communication systems, ensures mobility and service continuity, and maintains efficient handover and redirection processes even when the N26 interface is unavailable.
Smart Images

Figure CN112586036B_ABST
Abstract
Description
Background Art
[0001] The 3rd Generation Partnership Project (3GPP) defines wireless communication standards between user equipment and radio access networks. For example, 3GPP defines standards for implementing an evolved packet system (EPS), which includes an evolved packet core (EPC) to provide wireless connectivity to user equipment in the system. The EPS standard is also known as the fourth generation (4G) standard or the long-term evolution (LTE) standard. 3GPP is in the process of defining the next generation standard, which is called the fifth generation (5G) standard. Wireless communication systems operating according to the 5G standard use existing LTE frequency ranges and additional frequency bands (e.g., millimeter wave bands) to provide high throughput, low latency, high mobility, and high connection density to support data rates of up to 20 gigabits per second. It is initially expected that 5G communication systems will be deployed in conjunction with existing 4G or LTE communication systems, such as "islands". 5G communication systems can also be configured to provide non-guaranteed bit rate services (such as enhanced mobile broadband (eMBB)), and LTE communication systems provide additional services such as LTE voice (VoLTE), and interoperate with wideband code division multiple access (WCDMA) to support high data rate services. In some cases, 5G communication systems will also be deployed in conjunction with systems operating according to earlier standards, such as third generation (3G) standards. BRIEF DESCRIPTION OF THE DRAWINGS
[0002] The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The same reference numerals used in different drawings indicate similar or identical items.
[0003] Figure 1 is a block diagram of a communication system according to some embodiments, the communication system including a first wireless communication system operating according to a first radio access technology (RAT) and a second wireless communication system operating according to a second RAT.
[0004] Figure 2 is a block diagram of a network function virtualization (NFV) architecture according to some embodiments.
[0005] Figure 3 is a block diagram of a wireless communication system that supports selective switching or redirection of call sessions based on availability of interfaces in accordance with some embodiments.
[0006] Figure 4 is a block diagram of a wireless communication system that supports selective handover of a call session to a different Radio Access Network (RAN) based on availability of an interface in accordance with some embodiments.
[0007] Figure 5is a flowchart of a method for selectively performing handover via an interface between an AMF and an MME or performing redirection via a shared network entity according to some embodiments.
[0008] Figure 6 is a block diagram of a portion of a wireless communication system including a RAN node and an AMF according to some embodiments.
[0009] Figure 7 is a first message flow for handover selectively performed using the N26 interface according to some embodiments.
[0010] Figure 8 is a second message flow for handover selectively performed using the N26 interface according to some embodiments.
[0011] Fig. 9 is a third message flow for handover selectively performed using the N26 interface in accordance with some embodiments. DETAILED DESCRIPTION
[0012] The intercommunication between the 5G communication system and other communication systems is provided by standardized interfaces and / or common entities shared by the two systems. For example, the 5G and EPS standards (such as LTE connected to EPC) define the N26 interface between the mobility management function (AMF) in the 5G system and the mobility management entity (MME) in the 4G or LTE system connected to the EPC. In addition, the 4G system and the 5G system can share a user plane entity that implements user plane functionality for a packet data unit (PDU) gateway (PGW-U) operating according to the 4G standard and a user plane function (UPF) operating according to the 5G standard, so as to provide the goal of session and service continuity for mobility between LTE and 5G. In operation, the user equipment switches between different cells, frequencies, radio access technologies, etc. In response to the switching of the user equipment between the 5G system and another communication system (such as LTE connected to EPC), the user connectivity session is maintained by transmitting the context for the user equipment on the N26 interface. However, the N26 interface is not always available between the 5G and LTE systems or between parts of these systems. For example, the N26 interface may be permanently unavailable (e.g., between a 5G AMF node and an MME in an EPC pool area), or temporarily unavailable (e.g., due to a device failure in any communication system). For another example, the N26 interface may be unavailable to the user equipment due to restrictions imposed by the type of user equipment (e.g., dual-registered versus single-registered), the user's subscription, the roaming status of the user equipment, a public land mobile network (PLMN) identifier, etc.
[0013] Whenever handover via the N26 interface is not possible or allowed, redirection to the target system may be performed for the user equipment. For example, a radio resource control (RRC) connection release including target assistance information may be performed towards the target cell, frequency or radio access technology. Instead of transferring the context of the call session over the N26 interface, the MME associated with the target RAN obtains the context of the call session from the core network (e.g., from PGW+UPF) and provides the context to the target RAN. Common user plane elements may also be used to allow session and service continuity for mobile users.
[0014] Figures 1 to 9 Embodiments of a technique are disclosed that improve handover quality and call statistics for a call session involving a user device moving between radio access networks (RANs) in 4G and 5G wireless communication systems by selectively performing a handover or redirection based on knowledge (e.g., determination) of the availability of an interface between an access and mobility management function (AMF) in a 5G system and a mobility management entity (MME) in a 4G system. In response to determining that the interface is available (e.g., based on stored information), a first RAN hands over the user device to a second RAN (in a different wireless communication system) by transmitting context information over an interface between the AMF and the MME. If the stored information indicates that the interface is not available, the call session of the user device is redirected from the first RAN to the second RAN via a shared user plane entity that implements user plane functionality for a packet data unit (PDU) gateway (PGW-U) operating in accordance with a 4G standard and a user plane function (UPF) operating in accordance with a 5G standard.
[0015] Some embodiments of the first RAN store information indicating whether the interface between the AMF and the MME is available for handing over the user equipment to the second RAN. This information may be pre-configured in one or both RANs, may be obtained from an operations and management (O&M) system, may be accessed from a configuration database, and the like. In addition, interface availability may be exchanged between network entities, for example, the first RAN and the core network may exchange inter-system interface availability during establishment of an N2 (NGAP) interface between the 5G RAN and the 5G core network. Interface availability information may also be exchanged during configuration update procedures related to the interface, such as gNB / AMF configuration updates over the N2 interface. In the same manner, interface availability may be exchanged over the S1-MME interface between the LTE RAN and the EPC using a process similar to that described for the 5G RAN and the 5G core network. The exchanged information may include information identifying neighboring 4G cells, tracking areas, public land mobile networks (PLMNs), and the like. For example, the exchanged information may identify an area (such as a cell indicated by a cell identifier), a tracking area indicated by a tracking area identifier, a public land mobile network (PLMN) identifier, an indicator of an MME / AMF pool area of a RAN served by one or more MMEs or AMFs, a RAN core network interface identifier, etc. The information identifying the neighboring node or area may be sent by the 5G RAN to the 5G core network, which replies with information indicating the availability of the N26 interface of the corresponding neighboring node or area. If the first RAN does not have information about the required inter-system interface, such as the N26 interface, the first RAN initiates a handover to the target system via the core network, and the core network responds to the first RAN with information indicating the availability status of the target cell(s), tracking area(s) or PLMN(s). Alternatively, the core network indicates that the N26 interface is not available, and the first RAN determines that the intended target cell(s), area(s) or PLMN is not available. Then, in response to the first RAN receiving a rejection of the requested handover indicating that the reason for the rejection is the unavailability of the interface between the AMF and the MME, the information may be temporarily, permanently or semi-permanently stored or modified. For example, if the first RAN is in a 5G wireless communication system, in response to the first RAN attempting to hand over the user equipment to a second RAN in a 4G wireless communication system, the first RAN stores information indicating that the interface is unavailable. In some embodiments, similar information indicating the state of the interface is also stored in the second RAN in the 4G wireless communication system.
[0016] Figure 11 is a block diagram of a communication system 100 according to some embodiments, the communication system 100 including a first wireless communication system 105 operating according to a first radio access technology (RAT) and a second wireless communication system 110 operating according to a second RAT. In the illustrated embodiment, the first RAT is defined by a fifth generation (5G) standard and the second RAT is defined by a fourth generation (4G) or long term evolution (LTE) standard, although in other embodiments the first RAT and the second RAT may be different.
[0017] The first wireless communication system 105 includes an access and mobility management function (AMF) 115 that manages access control and mobility of devices connected to the communication system 100 via the first wireless communication system 105. The first wireless communication system 105 also includes a session management function (SMF) 120 to establish and manage sessions in the first wireless communication system 105 according to network policies. The association between the user equipment 125 and the first wireless communication system 105 is represented as a packet data unit (PDU) session that can be managed by the SMF 120. The PDU session supports data connectivity between the user equipment 125 and a data network.
[0018] The first wireless communication system 105 also includes one or more user plane functions (UPF) 130 deployed in the first wireless communication system 105 to provide services to users of the first wireless communication system 105. In the illustrated embodiment, the UPF 130 is combined with a packet data network gateway (PGW) to form a single entity. The PGW functionality provides connectivity between the user equipment 125 and one or more external packet data networks. For example, the PGW provides an exit and entry point for services for the user equipment 125. The PGW also performs policy enforcement, packet filtering, charging support, legal interception, and packet screening. One or more radio access networks (RAN) 135 provide wireless connectivity to the user equipment 125 via a corresponding air interface 140. In some cases, the RAN 135 is referred to as the next generation (NG) RAN 135.
[0019] The second wireless communication system 110 includes a mobility management entity 145, which is responsible for paging idle user equipment, performing bearer activation / deactivation, authenticating user equipment, etc. MME 145 is also a termination node for NAS signaling. MME 145 is responsible for selecting a serving gateway (SGW) 150 for user equipment 125 during the initial attachment process and in response to the handover of user equipment 125 to the second wireless communication system 110. SGW 150 is a user plane mobility anchor for handover of user equipment 125 between base stations. SGW 150 routes and forwards user data packets and terminates the downlink data path of idle user equipment, and triggers paging when downlink data arrives at idle user equipment. SGW 150 manages and stores context for user equipment 125, which includes parameters defining one or more bearers, network internal routing information, etc. One or more radio access networks (RAN) 155 provide wireless connectivity to user equipment 125 through corresponding air interfaces 160. In some cases, the RAN 155 is referred to as an Evolved Universal Mobile Telecommunications System (UTRAN) 155 .
[0020] Entities in both the first wireless communication system 105 and the second wireless communication system 110 are able to access a shared entity 165, which combines a home subscriber server (HSS) and a unified data manager (UDM). The HSS is a master user database that stores subscription-related information, such as a subscriber profile associated with a user device 125. The HSS also performs authentication and authorization of the user and provides location and IP information for the user. The UDM handles credentials, location management, subscription management, etc. The UDM stores data including user subscription data, such as subscription identifiers, security credentials, subscription data related to access and mobility, and subscription data related to sessions.
[0021] Some embodiments of the first wireless communication system 105 or the second wireless communication system 110 include other functionalities, such as a policy control function and a network function knowledge base, which are described in detail in the following sections for clarity. Figure 1 Not shown. Some embodiments of the communication system 100 as discussed herein may be implemented using network function virtualization and software defined networking. For example, different network slices may be used to instantiate different instances of AMF 115, SMF 120, PGW+UPF 130, MME 145, SGW 150, or HSS+UDM 165 for different users or devices. Each PDU session is part of one network slice.
[0022] AMF 115 and MME 145 can support interface 170, which is used to transfer information between the first wireless communication system 105 and the second wireless communication system 110. In some cases, interface 170 is called N26 interface. And in response to the user equipment 125 (or other entity) initiating the switching of the user equipment 125 between RAM 135 and RAN 155, interface 170 can be used to transfer context information of the user equipment 125, as shown by the bidirectional arrow 175. However, interface 170 is not always available for transferring information between the first wireless communication system 105 and the second wireless communication system 110. Due to equipment failure (for example, in AMF 115 or MME 145), interface 170 may be temporarily or permanently unavailable. Moreover, depending on the type of user equipment (for example, whether the user equipment is dual-registered or single-registered), interface 170 may be unavailable for user equipment 125. Access to interface 170 may also be restricted based on a subscription associated with user equipment 125, a roaming status of user equipment 125, a public land mobile network (PLMN) associated with user equipment 125, and the like.
[0023] In response to a handover request for a user equipment 125 being rejected due to unavailability of interface 170, a rejection message is generated. Some embodiments of the rejection message include an information element indicating the reason for the rejection, such as "no N26 interface available". The rejection message may also indicate whether the rejection is permanent or temporary, in which case the time interval of unavailability may also be indicated in the rejection message. The rejection of the handover request due to unavailability of interface 170 applies to a rejection area, such as an individual cell served by one of the RANs 135, 155, a tracking area including one or more of the RANs 135, 155, a PLMN associated with the user equipment 125, a network slice used to instantiate one or more entities within the first wireless communication system 105 or the second wireless communication system 110, and the like. Some embodiments of the rejection message include an information element indicating the rejection area. Information indicating the availability or unavailability of interface 170 is stored in a form accessible to the RAN 135, 155, for example, in a database associated with the RAN 135 or RAN 155 (not in a database associated with the RAN 135 or RAN 155). Figure 1 170). Thus, the RAN 135, 155 is able to "learn" whether an interface such as interface 170 is available to support handovers to various neighboring wireless communication systems. As discussed below, in some embodiments, the availability status of other interfaces is preconfigured to a database associated with the RAN 135, 155.
[0024] Based on the availability status of the interface 170, a handover of the user equipment 125 between the first wireless communication system 105 and the second wireless communication system 110 is performed. For example, if the user equipment 125 measurement report triggers a handover from the RAN 135 to the RAN 155, the RAN 135 accesses information indicating the availability status of the interface 170 (e.g., from an associated database of the availability status of the interface to the neighboring cells, tracking areas, PLMNs, network slices, etc.). For example, the RAN 135 may access the database in response to receiving a trigger for a handover for the user equipment 125. The RAN 135 then selectively performs a handover via the interface 170 or performs a redirection via the network entity 165 based on the availability status of the interface 170. If the availability status indicates that the interface 170 is available, the RAN 135 performs a handover via the interface 170. The handover may include data forwarding from the source RAN to the target RAN, including transmission of data over the corresponding air interface.
[0025] However, if the availability status indicates that the interface 170 is not available, the RAN 135 transmits a redirection with a radio resource control (RRC) connection release to the target RAN 155. In that case, context information for the call session is transmitted to the second wireless communication system 110 via the shared entity 165, as indicated by the bidirectional arrow 180. In response to the target RAN 155 receiving the RRC release, the MME 145 obtains the context of the call session from the PGW+UPF 130 via the HSS+UDM 165, and provides the context to the target RAN 155, which creates a new context for the user equipment 125 based on the obtained context information. In some embodiments, the RAN 135 evaluates the availability status of the interface between the AMF 115 and other MMEs associated with other RANs that are candidates for handing over the user equipment 125. If the interface between the AMF 115 and one of the other MMEs is available, the user equipment 125 is handed over via the available interface instead of performing redirection.
[0026] Figure 2 is a block diagram of a NFV architecture 200 according to some embodiments. The NFV architecture 200 is used to implement Figure 1Some embodiments of the communication system 100 shown. The NFV architecture 200 includes hardware resources 201, which include computing hardware 202 (such as one or more processors), storage hardware 203 (such as memory), and network hardware 204 (such as transmitters, receivers, or transceivers). The virtualization layer 205 provides an abstract representation of the hardware resources 201. The abstract representation supported by the virtualization layer 205 can be managed using a virtualization infrastructure manager 210, which is part of the NFV management and orchestration (M&O) module 215. Some embodiments of the manager 210 are configured to collect and forward performance measurements and events that may occur in the NFV architecture 200. For example, performance measurements can be forwarded to an orchestrator (ORCH) 217 implemented in the NFV M&O 215. The hardware resources 201 and the virtualization layer 205 can be used to implement virtual resources 220 including virtual computing 221, virtual storage 222, and virtual networking 223.
[0027] The virtual networking functions (VNF1, VNF2, VNF3) run on the NFV infrastructure (e.g., hardware resources 201) and utilize virtual resources 220. For example, the virtual networking functions (VNF1, VNF2, VNF3) are implemented using virtual machines supported by virtual computing resources 221, virtual memory supported by virtual storage resources 222, or virtual networks supported by virtual network resources 223. The element management system (EMS1, EMS2, EMS3) is responsible for managing the virtual networking functions (VNF1, VNF2, VNF3). For example, the element management system (EMS1, EMS2, EMS3) can be responsible for fault and performance management. In some embodiments, each virtual networking function (VNF1, VNF2, VNF3) is controlled by a corresponding VNF manager 225, which exchanges information and coordinates actions with the manager 210 or the coordinator 217.
[0028] The NFV architecture 200 includes an operations support system (OSS) / business support system (BSS) 230. The OSS / BSS 230 handles network management, including fault management using OSS functionality. The OSS / BSS 230 also handles customer and product management using BSS functionality. Some embodiments of the NFV architecture 200 use a set of descriptors 235 to store descriptions of services, virtual networking functions, or infrastructure supported by the NFV architecture 200. The information in the descriptors 235 can be updated or modified by the NFV M&O 215.
[0029] The NFV architecture 200 is used to implement a network slice 240 that provides user plane or control plane functions, such as Figure 1145, SGW 150, or HSS+UDM 165 shown in the figure. A network slice 240 is a complete logical network that provides communication services and network capabilities, which may vary from slice to slice. A user device may access multiple network slices 240 concurrently. Some embodiments of the user device provide network slice selection assistance information (NSSAI) parameters to the network to assist in selecting a slice instance for the user device. A single NSSAI may result in the selection of multiple slices 240. The NFV architecture 200 may also use device capabilities, subscription information, and local operator policies to select one or more network slices 240 in the network slice 240. NSSAI is a collection of smaller components, single NSSAIs (S-NSSAIs), each of which includes a slice service type (SST) and possibly a slice distinguisher (SD). The slice service type refers to the expected network behavior in terms of characteristics and services (e.g. specifically for broadband or massive IoT), while the slice differentiator can help select between several network slice instances of the same type, for example to isolate traffic related to different services into different subsets of the network slice 240.
[0030] Figure 3 is a block diagram of a wireless communication system 300 that supports selective switching or redirection of a call session based on the availability of an interface according to some embodiments. The wireless communication system 300 represents Figure 1 Some embodiments of the communication system 100 are shown, although for clarity, not all entities of the communication system 100 are shown. Figure 4 In the illustrated embodiment, the user equipment 305 has established a call session with the 5G RAN 310, which includes (or is otherwise accessible to) a database 315 that stores information indicating the availability status of an interface between the AMF 320 and one or more MMEs. For example, the database 315 stores information indicating the availability status of an interface 325 between the AMF 320 and the MME 330. Although for clarity in FIG. Figure 3 Not shown, the 4G RAN attached to the MME 330 may also include or have access to a database that stores information indicating the availability status of an interface between the MME 330 and one or more AMFs (including the AMF 320).
[0031] Some embodiments of the database 315 are dynamically populated with the interface 325 and the AMF 320 and other MMEs associated with the wireless communication system 300 ( Figure 3310 to the 4G RAN 335 connected to the MME 330). For example, the user equipment 305 initiates a handover from the 5G RAN 310 to the 4G RAN 335 connected to the MME 330, and the availability status of the interface 325 is determined and stored in the database 315 based on the response to the handover request. In the illustrated embodiment, the interface 325 is not available to support the handover of the user equipment 305 from the 5G RAN 310 to the 4G RAN 335. Therefore, the AMF 320 responds to the handover request by transmitting a rejection message to the 5G RAN 310. The rejection message includes information indicating that the interface 325 is unavailable, such as an information element identifying the reason for the handover rejection as "N26 interface unavailable". As discussed herein, the rejection message may also include other availability status information, such as the duration of the availability status or the reason why the interface 325 is unavailable. The 5G RAN 310 uses the information in the rejection message to determine that the interface 325 is unavailable, and stores the availability status of the interface 325 in the database 315, so that the availability status can be accessed from the database 315 in response to a subsequent switching request from the user equipment 305 or other user equipment served by the 5G RAN 310.
[0032] Some embodiments of database 315 are preconfigured with availability status information of interfaces including interface 325. For example, the availability status information in database 315 may be preconfigured by obtaining availability status information from an operations and management (O&M) system and accessing availability status information from a configuration database, etc. In some embodiments, availability status information is exchanged between network entities, for example, when an N2 (NGAP) interface is used between 5G RAN 310 and 5G core network ( Figure 3 During the establishment of the 5G RAN 310 and the core network (not shown), the 5G RAN 310 exchanges interface availability status information with the core network. The interface availability status information can also be used in the configuration update process related to the interface (such as, during the 5G RAN 335 and the EPC network ( Figure 3 The information exchanged may include information identifying neighboring 4G cells, tracking areas, public land mobile networks (PLMNs), etc. For example, 5G RAN 310 may send information identifying neighboring nodes or areas to the 5G core network, and the 5G core network may reply with information indicating the availability of the N26 interface for the corresponding neighboring node or area.
[0033] Pre-configuration and dynamic configuration of database 315 can be used in different combinations to modify or update the availability status information in database 315. For example, pre-configuration is used to set up availability status information for an initial set of interfaces. Subsequently, the status information is modified, for example based on information in a rejection message received in response to a handover request. Modifying the availability status information includes adding an entry for a new cell, tracking area identifier, PLMN, or changing the availability status of an entry for an interface associated with a previously identified cell, tracking area, or PLMN. For example, if database 315 is pre-configured with availability status information indicating that interface 325 is available to support handover, but interface 325 subsequently becomes unavailable, the availability status information in the corresponding entry in database 315 is modified to indicate that interface 325 is unavailable. The change in the status of interface 325 can be detected using the information in the rejection message. The availability status of other RANs in an area (such as a cell, tracking area, PLMN, MME / AMF pool, etc.) including target RAN 335 can also be modified based on the change in the status of interface 325.
[0034] 5G RAN 310 determines, for example, using information accessed from database 315, that interface 325 is unavailable to support the requested handover. In response to determining that interface 325 is unavailable, 5G RAN 310 initiates or triggers redirection with RRC connection release to target 4G RAN 335. The redirection indicates one or more of: a cell identifier of 4G RAN 335, a tracking area identifier for a tracking area including 4G RAN 335, a channel used by 4G RAN 335, a radio access technology (such as LTE) used by 4G RAN 335, etc. The redirection is provided to a shared network entity 340 that implements HSS and UDM. Context information for a call session involving user equipment 305 is passed from 5G RAN 310 to 4G RAN 335 via shared network entity 340. User equipment 305 is handed over from 5G RAN 310 to 4G RAN 335, as indicated by arrow 345. Even if interface 325 is unavailable, call session continuity may be preserved by exchanging information via shared network entity 340 .
[0035] Figure 4 is a block diagram of a wireless communication system 400 that supports selective handover of a call session to a different RAN based on the availability of an interface according to some embodiments. The wireless communication system 400 represents Figure 1 Some embodiments of the communication system 100 are shown, although not all entities of the communication system 100 are shown for clarity. Figure 4. In the illustrated embodiment, the user equipment 405 has established a call session with the 5G RAN 410, which includes (or otherwise has access to) a database 415, which stores information indicating the availability status of interfaces between the AMF 420 and a group of MMEs that are associated with potential handover candidate RANs for the user equipment 405. For example, the database 415 stores information indicating the availability status of the interface 425 between the AMF 420 and the MME 430 and then indicating the availability status of the interface 435 between the AMF420 and the MME440. As discussed herein, the availability status of the group of interfaces 425, 435 can be dynamically configured or modified, as well as pre-configured or modified using information requested from or provided by other network entities. Although for clarity in Figure 4 Not shown, the 4G RAN 445, 450 attached to the MME 430, 440 may also include or already have a database that stores information indicating the availability status of the interface between the MME 430, 440 and one or more AMFs (including the AMF 420).
[0036] In the illustrated embodiment, the user equipment 405 requests a handover from the 5G RAN 410 to the 4G RAN 445. In response to receiving the request, the 5G RAN 410 accesses the availability status of the interface 425 from the database 415. The 5G RAN 410 determines, based on the availability status, that the interface 425 is not available to support the handover of the user equipment 405 to the 4G RAN 445. Therefore, the user equipment 405 requests a handover to another candidate 4G RAN 450. One or more additional candidate handover targets are either indicated in the initial request for action handover from the user equipment 405, or the user equipment 405 may provide information identifying the additional candidate handover targets in response to the 5G RAN 410 indicating that the interface 425 is not available. The additional candidate handover targets are identified based on parameters such as signal strength measurements, neighbor lists, priority lists, etc.
[0037] 5G RAN 410 accesses the availability status of interface 435 from database 410 and determines based on the availability status that interface 435 is available to support the requested handover. Therefore, interface 435 is used to transfer context information of the call session from 5G RAN 410 to 4G RAN 450. As shown by arrow 455, user equipment 405 hands over its call session from 5G RAN 410 to 4G RAN 450. Therefore, the handover of user equipment 405 does not need to be redirected via a shared entity (such as a combined HSS+UDM) because 5G RAN 410 is able to identify another candidate 4G RAN 450 connected to MME 440, which has an available interface 435 to AMF 420.
[0038] Figure 5 1 is a flow chart of a method 500 for selectively performing a handover via an interface between an AMF and an MME or performing a redirection via a shared network entity according to some embodiments. Figure 1 The communication system 100 shown, Figure 3 The communication system 300 shown, and Figure 4 In response to a request to switch the user equipment to the 4G RAN, Figure 5 The method 500 shown is implemented in a 5G RAN. However, some embodiments of the method 500 are implemented in a 4G RAN to determine whether to selectively perform a handover to the 5G RAN via an interface between an MME associated with the 4G RAN and an AMF associated with the 5G RAN.
[0039] At block 505, a handover of the user equipment from the 5G RAN to the 4G RAN is initiated. Some embodiments of the user equipment initiate the handover based on a signal strength measurement or a channel quality measurement. However, the handover may be initiated in response to other events, or the handover may be initiated by a network entity.
[0040] At decision block 510, the 5G RAN determines whether an interface (such as an N26 interface) between the AMF associated with the 5G RAN and the MME associated with the 4G RAN is available. If so, the method 500 flows to block 515, and the user equipment is handed over from the 5G RAN to the 4G RAN using the available interface, as discussed herein. If the 5G RAN determines that the interface is not available, the method 500 flows to decision block 520.
[0041] At decision block 520, the 5G RAN determines whether other 4G RANs (e.g., 4G RANs, 4G RAN cells, and / or 4G RAN nodes) are available as targets for the requested handover. In some cases, the other candidate 4G RANs are provided by the user equipment in the initial handover request message. Alternatively, in response to determining (at decision block 510) that the interface for the previously requested handover is not available, the 5G RAN may request identifiers of other candidate 4G RANs from the user equipment. If other 4G RANs are available, the method 500 flows back to decision block 510. If the 5G RAN determines that there are no additional 4G RANs, the method 500 flows to block 525, and redirection is performed to maintain session continuity between the 5G RAN and the 4G RAN by transmitting context information via a shared network entity that combines HSS+UDM functionality.
[0042] In some embodiments, the source cell 5G RAN sends a handover command with target 4G RAN information (e.g., cell / frequency), and the UE detaches from the old cell and synchronizes with the new cell / frequency and accesses the new cell / frequency (e.g., using a random access procedure) and establishes bearers (e.g., SRBs and DRBs with RRC connection reconfiguration), user plane paths, and other required procedures are further performed between the UE and the system (in the RAN and core network) to support the application service(s) that the user is using.
[0043] In some embodiments, the user is detached from the source RAN with an instruction to connect to a given target (RRC connection release with target information, cell / frequency). On the target side, the UE synchronizes to the target RAN (e.g., cell / frequency) and accesses the RAN (usually using random access), and the radio and core network set up resources for the user. The core network is typically accessed using a location update (e.g., a service request procedure) or a new registration (e.g., an attach procedure), and the old context is re-established (from PGW+UPF) or created in the core network.
[0044] Figure 6 6 is a block diagram of a portion 600 of a wireless communication system including a RAN node 605 and an AMF 610 according to some embodiments. The portion 600 of the wireless communication system represents Figure 1 The communication system 100 shown, Figure 3 The communication system 300 and Figure 4 Portions of some embodiments of a communication system 400 are shown.
[0045] The RAN node 605 initiates the establishment procedure by transmitting a Setup Request message 615 including data in one or more information elements to the AMF 610. The AMF 610 responds with a Setup Response message 620 including data in one or more information elements. If the AMF Name information element is included in the Setup Response message 620, the RAN node 605 stores the name of the AMF 610 and identifies the AMF 610 using this information.
[0046] If the Neighbor TA Request List information element is included in the Setup Request message 615, the AMF 610 provides information identifying the requested tracking area list in the Neighbor TA Response List information element of the Setup Response message 620. If the N26 Interface information element is included in the Neighbor TA Response List information element of the Setup Response message 620, the RAN node 605 stores the information and considers the information when deciding whether handover or redirection is performed to send the user equipment to the EPS.
[0047] Some embodiments of the setup request message 615 include the information elements disclosed below: The setup request message 615 is transmitted by the RAN node 605 to convey application layer information for the NG-C interface instance.
[0048] Direction: RAN node 605 → AMF 610
[0049]
[0050]
[0051]
[0052] Range Limitation explain maxnoofTACs The maximum number of TACs is 256. maxnoofBPLMNs The maximum number of broadcast PLMNs. The value is 12.
[0053] Some embodiments of the Setup Response message 620 include the following disclosed information elements: The Setup Response message 620 is transmitted by the AMF 610 to convey application layer information for the NG-C interface instance.
[0054] Direction: AMF 610 → RAN node 605
[0055]
[0056]
[0057]
[0058]
[0059] An embodiment of a Tracking Area (TA) Request List is shown below. The TA Request List information element is used to request information about the TACs required by the RAN node 605 from the 5G core network.
[0060]
[0061] An embodiment of a TA response list is shown below: The TA response list information element indicates whether the tracking areas neighboring the cell of the RAN node 605 have N26 availability.
[0062]
[0063] The cause information element is included in a message such as a reject message transmitted from the AMF 610 to the RAN node 605. In some embodiments, the cause information element includes "N26 interface unavailable" to indicate that the failure of the requested handover is due to the unavailability of the N26 interface for the target tracking area identifier.
[0064]
[0065]
[0066]
[0067]
[0068] The following table describes the meaning of different cause values. In general, a "Not Supported" cause value indicates that the relevant capability is missing. On the other hand, a "Not Available" cause value indicates that the relevant capability exists, but there are insufficient resources to perform the requested action.
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078] Figure 7is a first message flow 700 of a handover selectively performed using an N26 interface according to some embodiments. The message flow 700 is Figure 1 The communication system 100 shown, Figure 3 The communication system 300 and Figure 4 The communication system 400 shown is implemented in some embodiments.
[0079] A PDU session and a quality of service (QoS) flow are established for a user equipment (UE) at block 702. Initially, a PDU session is set up between the user equipment and the 5G RAN.
[0080] The user equipment transmits a handover request message 704 to the AMF to request handover to the 4G RAN. In response to receiving the handover request message 704, the AMF determines whether the N26 interface is available to support the requested handover. If the N26 interface is not available to support the requested handover, the AMF transmits a handover reject message 706 to the 5G RAN. In response to receiving the handover reject message 706, the 5G RAN performs a redirection via a shared network entity (as discussed herein), or attempts to perform a handover to another candidate 4G RAN supported by an available N26 interface. If no available N26 interface is found, the message flow 700 ends here.
[0081] If an N26 interface is available to support the requested handover (or if an available N26 interface is found for another candidate 4G RAN), the message flow 700 continues. The AMF transmits a PDU Session Context Request message 708 to the control plane functionality PGW-C+SMF, which responds with a PDU Session Context Response 710. The AMF then transmits a Relocation Request message 712 to the MME, which in turn transmits a Create Session Request message 714 to the SGW. A Create Session Response message 716 is transmitted from the SGW to the MME. In response to receiving the Create Session Request message 716, the MME transmits a Handover Request message 718 to the 4G RAN, which responds with a Handover Request Acknowledge message 720.
[0082] The MME and SGW exchange requests and responses (at 722) to create an indirect data forwarding tunnel. The MME then transmits a relocation response message 724 to the AMF. The AMF transmits a PDU session update context request message 726 to the PGW-C+SMF, which then performs session modification 728 using the user plane functionality PGW-U+UPF. The PGW-C+SMF transmits a PDU session update context response message 730 to the AMF.
[0083] Figure 8is a second message flow 800 of a handover selectively performed using an N26 interface according to some embodiments. Figure 7 After the first message flow 700 shown in FIG. 8 , the second message flow 800 is executed. For example, Figure 7 As shown, in response to PGW-C+SMF transmitting a PDU session update context response message 730 to AMF, a second message flow 800 begins. Figure 1 The communication system 100 shown, Figure 3 The communication system 300 and Figure 4 The communication system 400 shown is implemented in some embodiments.
[0084] The AMF transmits a handover command 802 to instruct the 5G RAN to handover the user equipment to the 4G RAN. In response to receiving the handover command 802, the 5G RAN transmits a handover command 804 to the user equipment. In the case of home route roaming, the 5G RAN starts downlink data forwarding 806 to the V-UPF, and the V-UPF forwards the data (at 808) to the SGW. The data received at the SGW is forwarded (at 810) to the 4G RAN. In the case of non-roaming or local burst roaming, the 5G RAN starts downlink data forwarding 812 to the PGW-U+UPF, and the PGW-U+UPF forwards the data (at 814) to the SGW. The data received at the SGW is forwarded (at 816) to the 4G RAN.
[0085] The user equipment sends a handover complete message 818 to indicate that the user equipment has completed the handover from the 5G RAN to the 4G RAN. In response to receiving the handover complete message 818, the 4G RAN may forward (at 820) the available downlink data to the user equipment. The user equipment transmits uplink data 822 to the SGW using the prepared bearer. The SGW forwards (at 824) the uplink data to the V-UPF, which then forwards (at 826) the uplink data to the PGW-U+UPF.
[0086] The 4G RAN notifies the MME of the completed handover by transmitting a Handover Notification message 828 to the MME. The MME transmits a Relocation Complete Notification message 830 to the AMF, which responds with a Relocation Complete Confirmation message 832. The MME transmits a Modified Bearer Request message 834 to the SGW, which forwards the Modify Bearer Request message 836 to the PGW-C+SMF. The session modification 838 is performed by the PGW-C+SMF and the PGW-U+UPF. The PGW-C+SMF then transmits a Modify Bearer Response message 840 to the SGW.
[0087] Fig. 9is a third message flow 900 for handover selectively performed using the N26 interface according to some embodiments. Figure 8 After the second message flow 800 shown, the third message flow 900 is executed. For example, Figure 8 As shown, in response to PGW-C+SMF transmitting a modify bearer response message 840 to SGW, a third message flow 900 begins. Figure 1 The communication system 100 shown, Figure 3 The communication system 300 is shown with Figure 4 The communication system 400 shown is implemented in some embodiments.
[0088] Downlink data 902 is transmitted from the PGW-U+UPF to the V-UPF, which then forwards the downlink data (at 904) to the SGW. The prepared bearer is used to deliver the downlink data (at 906) to the user equipment. The SGW transmits a modify bearer response message 908 to the MME. At 910, a tracking area update procedure is performed, and then a bearer activation is performed (e.g., as a dedicated bearer activation procedure 912 initiated by the PGW). Using request response messages exchanged by the MME and the SGW at 914, the indirect data forwarding tunnel is deleted. Using request and response messages exchanged by the AMF and the PGW-C+SMF at 916, the indirect data forwarding tunnel is deleted. Session modification 918 is performed by the PGW-C+SMF and the PGW-U+UPF.
[0089] In some embodiments, certain aspects of the above-mentioned technology can be implemented by one or more processors of a processing system that executes software. The software includes one or more sets of executable instructions stored or tangibly implemented on a non-transient computer-readable storage medium. The software may include instructions and certain data that manipulate one or more processors to perform one or more aspects of the above-mentioned technology when executed by one or more processors. The non-volatile computer-readable storage medium may include, for example, a disk or optical disk storage device, a solid-state storage device such as a flash memory, a cache, a random access memory (RAM), or one or more other non-volatile storage devices, etc. The executable instructions stored on the non-transient computer-readable storage medium may be source code, assembly language code, object code, or other instruction formats that are interpreted or otherwise executable by one or more processors.
[0090] Computer-readable storage media may include any storage media or combination of storage media that a computer system can access during use to provide instructions and / or data to the computer system. Such storage media may include, but are not limited to, optical media (e.g., compact disks (CDs), digital versatile disks (DVDs), Blu-ray disks), magnetic media (e.g., floppy disks, tapes, or magnetic hard drives), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or micro-electromechanical system (MEMS)-based storage media. Computer-readable storage media may be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., a magnetic hard drive), removably attached to a computing system (e.g., an optical disk or flash memory based on a universal serial bus (USB)), or coupled to a computer system via a wired or wireless network (e.g., a network accessible storage (NAS)).
[0091] Note that not all of the above activities or elements in the general description are required, a portion of a particular activity or device may not be required, and one or more other activities may be performed, or elements other than those described may be included. Furthermore, the order in which the activities are listed is not necessarily the order in which the activities are performed. Moreover, the concepts have been described with reference to specific embodiments. However, it will be appreciated by those of ordinary skill in the art that various modifications and changes may be made without departing from the scope of the present disclosure as set forth in the appended claims. Therefore, the specification and drawings should be regarded as illustrative rather than restrictive, and all such modifications are intended to be included within the scope of the present disclosure.
[0092] Benefits, other advantages, and solutions to problems have been described above with respect to specific embodiments. However, benefits, advantages, solutions to problems, and any features that may cause any benefit, advantage, or solution to appear or become more apparent should not be interpreted as key, essential, or necessary features of any or all claims. In addition, the specific embodiments disclosed above are merely illustrative, as the disclosed subject matter can be modified and practiced in different but equivalent ways that are clear to those skilled in the art who benefit from the teachings herein. Except as described in the claims below, there is no intended limitation on the details of the construction or design shown herein. Therefore, it is clear that the specific embodiments disclosed above can be changed or modified, and all such changes are considered to be within the scope of the disclosed subject matter. Therefore, the protection sought herein is as set forth in the claims below.
Claims
1. A method of communication, comprising: accessing, at a first radio access network (RAN), from a database information indicating an availability status of an interface between a mobility management function (AMF) in the first wireless communication system and a mobility management entity (MME) in the second wireless communication system; receiving, at the first RAN, a trigger for handover of a user equipment UE between the first RAN and a second RAN; as well as In response to receiving the trigger from the UE, at the first RAN, based on the availability status, selectively performing the handover via the interface, or transmitting a release to the UE over an air interface to trigger redirection via a network element, the network element being shared by the first wireless communication system and the second wireless communication system.
2. The method of claim 1 , wherein selectively performing the switching comprises: In response to the availability status indicating that the interface is available, a context associated with the user equipment is transmitted from the first RAN to the second RAN via the interface.
3. The method according to claim 2, wherein the source cell sends a handover command with target RAN information of the second RAN, and the UE detaches from the old cell and synchronizes to and accesses the new cell / frequency and establishes a bearer and a user plane path, and wherein other processes are further performed between the UE and the first and second wireless communication systems to support the application service being used by the user equipment.
4. The method of claim 1 , wherein selectively performing the redirection comprises: In response to the availability status indicating that the interface is unavailable, creating a new context associated with the user equipment in the second RAN.
5. The method of claim 4, wherein the user equipment is detached from a source RAN with an instruction to connect to a given target RAN, and wherein the UE is synchronized to and accesses the given target RAN, and a core network establishes resources for the user equipment, and wherein the core network is accessed with a location update or a new registration, and an old context is reestablished or newly created in the core network.
6. The method of claim 1, wherein the shared network element is a user plane entity that implements user plane functionality for a packet data unit (PDU) gateway (PGW-U) and a user plane function (UPF).
7. The method according to any one of claims 1 to 6, further comprising: receiving, at the first RAN, the information indicating the availability status before receiving the trigger for the handover; as well as The information is stored to be accessible by the first RAN.
8. The method according to claim 7, wherein the first RAN is in the first wireless communication system and the second RAN is in the second wireless communication system, the method further comprising: Information identifying an area in the second wireless communication system is provided from the first RAN, the area including the second RAN, and wherein receiving the information indicating the availability status includes receiving information indicating an availability status for the area.
9. The method of claim 8, wherein the information identifying the area comprises at least one of: a cell identifier, a tracking area identifier, a public land mobile network (PLMN) identifier, a network slice identifier, an identifier of an MME / AMF pool area, and a RAN core network interface identifier.
10. The method of claim 9, wherein the information indicating the availability status of the area is received in a reply from the first RAN, the reply providing information identifying the area from the AMF or the MME.
11. The method according to any one of claims 1 to 6, further comprising: receiving a rejection of the request for the switch, wherein the rejection indicates that a reason for the rejection is that the interface is unavailable; as well as In response to receiving the rejection, the availability status of the interface is modified to indicate that the interface is unavailable.
12. The method of claim 11, wherein modifying the availability status comprises: An availability status of an area including the second RAN for the second wireless communication system is modified.
13. A first radio access network (RAN), comprising: a memory for storing information indicating an availability status of an interface between a mobility management function (AMF) in a first wireless communication system and a mobility management entity (MME) in a second wireless communication system; a transceiver configured to selectively transmit a handover command or a redirection command toward a user equipment over an air interface, and to receive at least one message from a user equipment UE over the air interface, the at least one message comprising a trigger for causing a handover or redirection between the first RAN and the second RAN; as well as and a processor to selectively perform the handover via the interface based on the availability status in response to receiving the trigger from the UE, or to transmit a release over an air interface toward the UE to trigger the redirection via a network element shared by the first wireless communication system and the second wireless communication system.
14. The first RAN according to claim 13, wherein the processor is further configured to cause the transmitter to: In response to the availability status indicating that the interface is available, a context associated with the user equipment is transmitted from the first RAN to the second RAN via the interface.
15. The first RAN of claim 13, wherein the shared network element is a shared user plane entity that implements user plane functionality for a packet data unit (PDU) gateway (PGW-U) and a user plane function (UPF).
16. The first RAN according to any one of claims 13 to 15, wherein the transceiver is configured to receive the information indicating the availability status before selectively transmitting the handover command or the redirection command, wherein the memory is configured to store the information in a database, and wherein the processor is configured to access the information from the database.
17. The first RAN according to claim 16, wherein the first RAN is in the first wireless communication system, and the second RAN is in the second wireless communication system, and: wherein the transceiver is configured to provide information identifying a region in the second wireless communication system, the region including the second RAN, and The information indicating the availability status includes: Availability status for the region.
18. The first RAN according to claim 17, wherein the information identifying the area includes at least one of the following: a cell identifier, a tracking area identifier, a public land mobile network (PLMN) identifier, a network slice identifier, an identifier of an MME / AMF pool area, and a RAN core network interface identifier.
19. The first RAN of claim 18, wherein the information indicating the availability status of the area is received in a reply that provides information identifying the area from the AMF or the MME.
20. The first RAN according to any one of claims 13 to 15, wherein: The transceiver is configured to receive a rejection of the request for the handover, wherein the rejection indicates that a reason for the rejection is that the interface is unavailable; and The processor is configured to modify the availability status of the interface to indicate that the interface is unavailable.
21. A method of communication, comprising: receiving, at an access and mobility management function (AMF) in the first wireless communication system or a mobility management entity (MME) in the second wireless communication system, a request for handover of a user equipment between a first radio access network (RAN) and a second RAN, the first RAN operating according to a first radio access technology RAT and the second RAN operating according to a second RAT; and A rejection of the request for handover is provided from the AMF or the MME, the rejection indicating that an N26 interface between the AMF and the MME is not available for handing over the user equipment.
22. The method according to claim 21, further comprising: The interface is determined to be unavailable or available for handing over the user equipment based on one or more of: a type of the user equipment, a subscription status of the user equipment, a roaming status of the user equipment, or a public land mobile network (PLMN) identifier associated with the user equipment.
23. The method of claim 21 , wherein providing the denial of the request for handover comprises: Information is provided indicating whether the interface is permanently or temporarily unavailable.
24. The method of claim 21 , wherein providing the denial of the request for handover comprises: Information indicating whether the interface is not available for switching to at least one of: a cell identified by a cell identifier, a tracking area identified by a tracking area identifier, a PLMN identified by a public land mobile network (PLMN) identifier, a network slice identified by a network slice identifier, an MME / AMF pool area identified by an MME / AMF pool area identifier, and a RAN core network interface identified by a RAN core network interface identifier.
25. The method according to any one of claims 21 to 24, further comprising: Information is provided from the AMF or the MME, the information indicating an availability status of an area including at least one of the first RAN and the second RAN.
26. The method of claim 25, wherein providing the information indicative of the availability status of the zone occurs prior to receiving the request for the switch.
27. The method of claim 26, wherein the first RAN is in the first wireless communication system and the second RAN is in the second wireless communication system, the method further comprising: Information identifying an area in the second wireless communication system is received from the first RAN at the AMF, the area including the second RAN, and wherein providing the information indicating the availability status includes: in response to receiving the information identifying the area in the second wireless communication system, providing the information indicating the availability status.
28. The method of claim 27, wherein the information identifying the area in the second wireless communication system comprises at least one of: a cell identifier, a tracking area identifier, a public land mobile network (PLMN) identifier, a network slice identifier, an identifier of an MME / AMF pool area, or a RAN core network interface identifier.
29. An apparatus for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: accessing information from a database, the information indicating an availability status of an interface between a mobility management function (AMF) in the first wireless communication system and a mobility management entity (MME) in the second wireless communication system; receiving, from a user equipment (UE), a trigger for handover of the UE between a first radio access network (RAN) and a second RAN; as well as In response to receiving the trigger from the UE, the handover is selectively performed via the interface based on the availability status, or a transmission release is triggered to trigger redirection via a network element, the network element being shared by the first wireless communication system and the second wireless communication system.
