WO2024035109A1 - Procédé et dispositif destinés à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil - Google Patents

Procédé et dispositif destinés à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil Download PDF

Info

Publication number
WO2024035109A1
WO2024035109A1 PCT/KR2023/011742 KR2023011742W WO2024035109A1 WO 2024035109 A1 WO2024035109 A1 WO 2024035109A1 KR 2023011742 W KR2023011742 W KR 2023011742W WO 2024035109 A1 WO2024035109 A1 WO 2024035109A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
handover
base station
terminal
information
Prior art date
Application number
PCT/KR2023/011742
Other languages
English (en)
Korean (ko)
Inventor
김동연
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2024035109A1 publication Critical patent/WO2024035109A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • This disclosure relates to a method and device for terminal registration and connection management in a wireless communication system.
  • 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave.
  • 'Sub 6GHz' sub-6 GHz
  • mm millimeter wave
  • Wave ultra-high frequency band
  • 6G mobile communication technology which is called the system of Beyond 5G
  • Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.
  • ultra-wideband services enhanced Mobile BroadBand, eMBB
  • ultra-reliable low-latency communications URLLC
  • massive machine-type communications mMTC
  • numerology support multiple subcarrier interval operation, etc.
  • dynamic operation of slot format initial access technology to support multi-beam transmission and broadband
  • definition and operation of BWP Band-Width Part
  • New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information
  • L2 pre-processing L2 pre-processing
  • dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.
  • V2X Vehicle-to-Everything
  • NR-U New Radio Unlicensed
  • UE Power Saving NR terminal low power consumption technology
  • NTN Non-Terrestrial Network
  • IAB provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links.
  • Intelligent factories Intelligent Internet of Things, IIoT
  • Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover
  • 2-step Random Access (2-step RACH for simplification of random access procedures)
  • Standardization in the field of wireless interface architecture/protocol for technologies such as NR is also in progress
  • a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • FD-MIMO full dimensional MIMO
  • array antennas to ensure coverage in the terahertz band of 6G mobile communication technology.
  • multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end.
  • 3rd generation partnership project 3rd generation partnership project
  • a method to enable a terminal to connect to a network (according to one embodiment, a 5G core network) through a satellite access network (satellite RAN) is being discussed.
  • This disclosure proposes a method for network registration and connection management of a terminal.
  • a method of a source base station in a wireless communication system includes receiving measurement report information about at least one neighboring cell from a terminal; Determining whether to perform handover to a target base station based on at least one of the measurement report information or coverage information of the source base station; and transmitting a request for the handover to the source network entity.
  • the request for handover may include a discontinuous coverage indicator indicating that the handover is associated with discontinuous coverage.
  • the source base station includes a transceiver; and a controller, wherein the controller: receives measurement report information about at least one neighboring cell from a terminal, and based on at least one of the measurement report information or coverage information of the source base station, targets It may be configured to determine whether to perform a handover to a base station and transmit a request for the handover to the source network entity.
  • the request for handover may include a discontinuous coverage indicator indicating that the handover is associated with discontinuous coverage.
  • a non-transitory computer-readable medium can store instructions. When executed by the source base station's controller, the instructions may cause the source base station to perform operations.
  • the operations include receiving measurement report information about at least one neighboring cell from the terminal; Determining whether to perform handover to a target base station based on at least one of the measurement report information or coverage information of the source base station; and transmitting a request for the handover to a source network entity.
  • the request for handover may include a discontinuous coverage indicator indicating that the handover is associated with discontinuous coverage.
  • network registration and connection management of a terminal can be efficiently performed.
  • Figure 1 shows the network structure and interface of a 5G system according to an embodiment of the present disclosure.
  • Figure 2 shows the structure of a wireless communication system supporting interworking between a 5G system and an EPS system according to an embodiment of the present disclosure.
  • Figure 3 shows the operation of 5GS and EPS when the terminal moves away from the coverage of the access network according to an embodiment of the present disclosure.
  • 4A and 4B show a handover method according to an embodiment of the present disclosure.
  • Figures 5a and 5b show a handover method according to an embodiment of the present disclosure.
  • Figure 6 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
  • Figure 7 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
  • the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network.
  • a terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above example.
  • connection node a term referring to network entities
  • a term referring to messages a term referring to an interface between network objects
  • a term referring to various types of identification information a term referring to various types of identification information.
  • the following are examples for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.
  • the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard.
  • 3GPP LTE 3rd Generation Partnership Project Long Term Evolution
  • satellite radio access covers a relatively larger area than terrestrial radio access
  • the number of terminals (UEs) communicating with the 5G core network also increases.
  • satellite radio access coverage moves according to the movement of the satellite, so UEs may temporarily lose connection with 5GC.
  • UEs that lose connectivity are deregistered from 5GC, even though satellite coverage may return after a certain period.
  • UEs again request registration and connection to 5GC, and 5GC performs necessary operations and sends signals to UEs. Because the periodic characteristics of the satellite are not taken into account, this is repeated continuously and reduces the efficiency of resource use in the UE, 5GC, and radio access sections.
  • a 5G or 4G access network e.g., a 4G or 5G satellite access network
  • a 5G or 4G access network e.g., a 4G or 5G satellite access network
  • a 4G or 5G satellite access network that provides discontinuous cell coverage in time/space, access coverage characteristics, location of a terminal, and/or access radio capability
  • a 5G or 4G access network e.g., a 4G or 5G satellite access network
  • the terminal's network connection can be efficiently managed by considering radio capabilities.
  • Figure 1 shows the network structure and interface of a 5G system according to an embodiment of the present disclosure.
  • the 5G system 100 includes at least one terminal (user equipment (UE)) 101 and at least one (radio) access network ((R)AN). 102 and may include at least one network entity.
  • UE user equipment
  • R radio access network
  • a network entity included in the network structure of the 5G system in FIG. 1 may include a network function (NF) depending on system implementation.
  • NF network function
  • the network structure of the 5G system 100 may include various network entities.
  • the 5G system 100 includes an authentication server function (AUSF) 108, an access and mobility management function (AMF) 103, and a session management function.
  • SMF authentication server function
  • PCF policy control function
  • AF application function
  • UDM unified data management
  • NDR network exposure function
  • NSSF network slicing selection function
  • EDR edge application service domain storage
  • Each NF of the 5G system 100 supports the following functions.
  • AUSF 108 processes and stores data for authentication of UE 101.
  • the AMF 103 provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF. Specifically, the AMF 103 supports CN inter-node signaling for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), and non-access stratum (NAS) ) Endpoint of signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE accessibility ( reachability (including control and performance of paging retransmissions), mobility management controls (subscriptions and policies), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (AMF events and (for interface to LI system), providing delivery of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, roaming authority check It supports functions such as access authorization, providing delivery of SMS messages between the UE and SMSF, security
  • the DN 110 means, for example, an operator service, Internet access, or a third party service.
  • the DN 110 transmits a downlink protocol data unit (PDU) to the UPF 104 or receives the PDU transmitted from the UE 101 from the UPF 104.
  • PDU downlink protocol data unit
  • the PCF (106) receives information about packet flow from the application server and provides the function of determining policies such as mobility management and session management.
  • PCF 106 supports a unified policy framework to govern network behavior, provides policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and allows users to It supports functions such as implementing a front end to access relevant subscription information for policy decisions within a user data repository (UDR).
  • control plane function(s) e.g., AMF, SMF, etc.
  • UDR user data repository
  • the SMF 105 provides a session management function, and when the UE has multiple sessions, each session can be managed by a different SMF. Specifically, SMF 105 performs session management (e.g., session establishment, modification, and termination, including maintaining tunnels between UPF 104 and (R)AN 102 nodes), UE IP address allocation, and Management (optionally including authentication), selection and control of UP functions, establishment of traffic steering to route traffic to appropriate destinations in UPF 104, termination of interfaces towards policy control functions; Enforcement of policy and control portion of quality of service (QoS), lawful intercept (for SM events and interface to LI system), termination of SM portion of NAS messages, downlink data notification, It supports functions such as initiator of AN-specific SM information (delivered to (R)AN (102) via N2 via AMF (103)), SSC mode determination of the session, and roaming function. Some or all of the functions of SMF 105 may be supported within a single instance of one SMF.
  • session management e.g., session establishment, modification
  • the UDM 109 stores user subscription data, policy data, etc.
  • UDM 109 includes two parts: an application front end (FE) (not shown) and a user data repository (UDR) (not shown).
  • FE application front end
  • UDR user data repository
  • UDM FE includes UDM FE, which is responsible for location management, subscription management, and credential processing, and PCF, which is responsible for policy control.
  • UDR stores data required for functions provided by UDM-FE and policy profiles required by PCF.
  • Data stored within the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data.
  • UDM-FE accesses subscription information stored in UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management. do.
  • the UPF (104) delivers the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102) and receives it from the UE (101) via the (R)AN (102).
  • One uplink PDU is delivered to the DN (110).
  • the UPF 104 is an anchor point for intra/inter radio access technology (RAT) mobility, an external PDU session point for interconnect to a data network, packet routing and User plane portion of forwarding, packet inspection and policy rule enforcement, lawful intercept, traffic usage reporting, uplink classifier to support routing of traffic flows to data network, multi-homed Branching points to support (multi-homed) PDU sessions, QoS handling for the user plane (e.g.
  • RAT radio access technology
  • UPF 104 packet filtering, gating, uplink/downlink rate enforcement), uplink Functions such as traffic verification (SDF mapping between service data flow (SDF) and QoS flow), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering function. Supports. Some or all of the functions of UPF 104 may be supported within a single instance of one UPF.
  • AF 107 supports 3GPP for service provision (e.g., supporting functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control). Interoperates with the core network.
  • RAN 102 supports both evolved E-UTRA (evolved E-UTRA), which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).
  • E-UTRA evolved E-UTRA
  • NR new radio
  • the gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink).
  • radio resource management i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink.
  • dynamic allocation of resources i.e. scheduling
  • Internet protocol (IP) header compression i.e. scheduling
  • encryption and integrity protection of user data streams i.e. scheduling
  • routing to AMF is not determined from the information provided to the UE.
  • selection of AMF upon attachment of the UE user plane data routing to UPF(s), control plane information routing to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), system Scheduling and transmission of broadcast information (from AMF or operating and maintenance (O&M)), setting up measurements and measurement reporting for mobility and scheduling, transport level packet marking in the uplink, Session management, support of network slicing, QoS flow management and data mapping to radio bearers, support of UE in inactive mode, distribution function of NAS messages, NAS node selection function, radio access network sharing, dual connectivity ( Supports features such as dual connectivity and tight interworking between NR and E-UTRA.
  • UE 101 refers to a user device.
  • a user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc.
  • the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, or a multimedia device, or it may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.
  • PC personal computer
  • NEF 111 is provided by 3GPP network functions, e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing. Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s). NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed by the NEF 111 to other NF(s) and AF(s) and used for other purposes such as analysis.
  • 3GPP network functions e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing.
  • Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s).
  • NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed
  • NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
  • FIG. 1 illustrates a reference model for a case where the UE 101 accesses one DN 110 using one PDU session for convenience of explanation, but the present disclosure is not limited thereto.
  • UE 101 can simultaneously access two (ie, local and central) data networks using multiple PDU sessions.
  • two SMFs may be selected for different PDU sessions.
  • each SMF may have the ability to control both the local UPF and the central UPF within the PDU session.
  • UE 101 may simultaneously access two (ie, local and central) data networks provided within a single PDU session.
  • NSSF 114 may select a set of network slice instances serving UE 101. Additionally, the NSSF 114 may determine permitted network slice selection assistance information (NSSAI) and, if necessary, perform mapping on subscribed single-network slice selection assistance information (S-NSSAI). Additionally, the NSSF 114 may determine the configured NSSAI and, if necessary, perform mapping to the subscribed S-NSSAIs. Additionally, the NSSF 114 may determine the AMF set used to serve the UE, or, depending on settings, may query the NRF 115 to determine a list of candidate AMFs.
  • NSSAI permitted network slice selection assistance information
  • S-NSSAI subscribed single-network slice selection assistance information
  • AMF set used to serve the UE or, depending on settings, may query the NRF 115 to determine a list of candidate AMFs.
  • NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
  • the conceptual link connecting NFs in the 5G system is defined as a reference point.
  • the following illustrates reference points included in the 5G system architecture represented in Figure 1.
  • the terminal may refer to the UE 101, and the terms UE and terminal may be used interchangeably. In this case, unless the UE is specifically defined additionally, it should be understood as UE 101.
  • the network and core network included in the embodiments of the present disclosure may be a concept including a network device.
  • a mobility management device or mobility management function
  • a location management device or a location management function
  • a gateway mobile location center etc. may each be configured as separate devices and may be configured to be included in a network device.
  • Figure 2 shows the structure of a wireless communication system supporting interworking between a 5G system and an EPS system according to an embodiment of the present disclosure.
  • Figure 2 is a diagram showing an example of an interworking structure of 5GS and EPS in a non-roaming situation.
  • 5GS is a NR (New Radio) base station (NG-RAN (radio access node) or gNB (next generation node B)) 103 for wireless access of the terminal (UE) 101, and an access and mobility management function (access and mobility management function) It may include a mobility management function (AMF) 105, and in addition, although not shown in FIG. 2, a session management function (SMF), a user plane function (UPF), and a policy control function (policy) It may include control function (PCF), network slice selection function (NSSF), unified data management (UDM), unified data repository (UDR), etc.
  • NG-RAN radio access node
  • gNB next generation node B
  • AMF mobility management function
  • PCF policy control function
  • NSF network slice selection function
  • UDM unified data management
  • UDR unified data repository
  • the EPS is an E-UTRA base station (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or evolved node B (eNB)) 113, a mobility management entity (MME) 115 , serving gateway (SGW) 117, packet data network gateway (PGW) (PGW may be composed of PGW-U and PGW-C), policy and charging rule functions (policy and It may include charging rule function (PCRF), home subscriber server (HSS), etc.
  • UMTS Universal Mobile Telecommunications System
  • eNB evolved node B
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • policy and charging rule functions policy and charging rule functions
  • PCRF charging rule function
  • HSS home subscriber server
  • the AMF (105) and MME (115) may be a Network Function (NF) that manages wireless network access and mobility for the terminal.
  • SMF, SGW, and PGW are NFs that manage sessions for the terminal, and session information may include Quality of Service (QoS) information, charging information, and information about packet processing.
  • QoS Quality of Service
  • the UPF and PGW are NFs that process user plane traffic (e.g., user plane traffic) and are controlled by SMF and SGW.
  • the PCF and PCRF may be NFs that manage operator policy and/or PLMN (public land mobile network) policy for providing services in a wireless communication system.
  • PLMN public land mobile network
  • the PCF can be divided into a PCF in charge of Access and Mobility (AM) policy and UE policy and a PCF in charge of Session Management (SM) policy.
  • the PCF in charge of AM/UE policy and the PCF in charge of SM policy may be logically or physically separate NFs, or may be a single logically or physically NF.
  • UDM and HSS may be NFs that store and manage UE subscriber information (UE subscription).
  • UDR may be an NF or database (DB) that stores and manages data.
  • UDR stores the terminal's subscription information and can provide the terminal's subscription information to UDM.
  • UDR can store operator policy information and provide operator policy information to the PCF.
  • NSSF may be an NF that performs the function of selecting network slice instances serving the terminal or determining Network Slice Selection Assistance Information (NSSAI).
  • NSSAI Network Slice Selection Assistance Information
  • the instance is an NF that exists in the form of software code, and is physically or/from a computing system to perform the function of the NF in a physical computing system (e.g., a specific computing system existing on a core network). It may refer to a state in which logical resources are allocated and the functions of the NF can be executed. For example, AMF Instance, SMF Instance, NSSF Instance, etc. each refer to a state in which physical and/or logical resources can be allocated and used for the operation of AMF, SMF, NSSF, etc. from a specific computing system existing on the core network. You can.
  • an AMF Instance, SMF Instance, or NSSF Instance that is allocated and used physical and/or logical resources for AMF, SMF, and NSSF operations from a specific computing system existing on the network. can perform the same operation.
  • UDM of 5GS and HSS of EPS may be composed of one combo node (referred to as UDM+HSS) 124.
  • the UDM+HSS node 124 can store subscriber information of the terminal.
  • the SMF of 5GS and the PGW-C of EPS may be composed of one combo node (referred to as SMF+PGW-C or PGW-C+SMF) 122.
  • SMF+PGW-C or PGW-C+SMF one combo node
  • the PCF of 5GS and the PCRF of EPS may be composed of one combo node (referred to as PCF + PCRF) 123.
  • the UPF of 5GS and the PGW-U of EPS may be composed of one combo node (referred to as UPF+PGW-U or PGW-U+UPF) 121.
  • UPF+PGW-U or PGW-U+UPF a combo node
  • the terminal 101 can access the EPS MME 115 through the E-UTRA base station 113 and use the EPS network service.
  • the terminal 101 can access the 5GS AMF 105 through the NR base station 103 and use the 5GS network service.
  • the same reference numerals are used for the terminal 101 connected to EPS and the terminal 101 connected to 5GS. This is to mean that the terminal 101 is a terminal that can access EPS and 5GS.
  • one NF or network entity can support different network systems simultaneously, and these NFs, network nodes, or network entities can be referred to as the previously described combo node, combo NF, combined node, integrated NF, or interworking. It can be called an (interworking) node, interworking NF, etc.
  • the NF function illustrated by the combo node may be implemented through interworking between two or more network entities.
  • a "+" symbol or a "/" symbol can be used to indicate NFs that simultaneously support different network systems. For example, if SMF and PGW-C are composed of one combo node, it can be expressed as PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, or SMF+PGW-C.
  • the terminal 101 can establish a session by connecting to a data network (eg, a network providing Internet services) through the 5GS or EPS system.
  • a data network eg, a network providing Internet services
  • the terminal 101 can distinguish each data network using an identifier called a Data Network Name (DNN) or an Access Point Name (APN).
  • DNN can be used in 5GS and APN can be used in EPS.
  • DNN and APN can be used to determine NFs related to the user plane, interfaces between NFs, operator policies, etc. when the terminal 101 connects a network system and a session.
  • the DNN and the APN can be understood as equivalent information and can deliver the same information.
  • the DNN may be used, for example, to select the SMF and UPF(s) for a PDU session, and may be used to select the interface (e.g., N6 interface) between the data network and the UPF for the PDU session. . Additionally, the DNN can be used to determine the mobile communication service provider's policy to apply to the PDU session.
  • the interface e.g., N6 interface
  • combo nodes such as UDM+HSS node, PCF+PCRF node, SMF+PGW-C node, UPF+PGW-C node, etc. will be described with the name “node” omitted for convenience of explanation.
  • the definition of a message defined in one embodiment may be applied in the same sense to other embodiments that use the same message.
  • Figure 3 shows the operation of 5GS and EPS when the terminal moves away from the coverage of the access network.
  • examples of cases where the terminal moves away from the coverage of the access network may include the following two. However, the embodiment is not limited to this, and there may be various cases in which the terminal moves away from the coverage of the access network.
  • Case #1 This is a case where the terminal is stationary on the ground or moving within a certain area, and the currently connected access network moves significantly, causing the terminal to move away from the coverage of the currently connected access network.
  • the access network may be, for example, a satellite access network consisting of mobile satellite (or low-orbit mobile satellite) access.
  • Case #2 This occurs when the terminal leaves the coverage area of the currently connected access network and moves to another location. At this time, the terminal may be moving a long distance using a means of transportation such as a train, ship, or automobile.
  • operations in 5GS and/or EPS may include the following.
  • RAT provided by the Source RAN and/or Target RAN may include satellite access technology and/or terrestrial access technology. Satellite access technology may include, for example, NR satellite access technology, E-UTRAN satellite access technology, and/or NB-IoT satellite access technology, and terrestrial access technology may include, for example, NR access technology, E-UTRAN access technology, and/or Alternatively, it may include NB-IoT access technology.
  • the terminal uses (a) location information of the access network provided by the access network (e.g., in the case of a satellite access network) , ephemeris information), (b) the current location of the terminal or the expected path of the terminal, or (c) coverage information of the access network.
  • Coverage information (c) of the access network is, for example, when the access network is a satellite access network, coverage movement information over time (e.g., providing current location coverage for X time, not providing current location coverage for Y time, providing current location coverage) time remaining, etc.), and/or periodic information of the satellite.
  • the terminal If the terminal recognizes that there is another RAN that the terminal can access at its current location or on the terminal's expected path, it can request registration in the direct access network (Target RAN).
  • the terminal may access the Source RAN and Source Core network entities (e.g., AMF or MME). Coverage information of the access network (e.g., coverage information of the access network in (c) above) may be provided.
  • Source RAN can use this information to determine handover (e.g., Inter-RAT handover, Intra-RAT handover, Xn-based handover, N2-based handover, etc.).
  • Source RAN can deliver this information to the Source Core network entity when requested by the terminal, regardless of whether a handover decision has been made.
  • the Source Core network entity may refer to this information to determine handover (e.g., Inter-RAT handover, Intra-RAT handover, Xn-based handover, N2-based handover, etc.).
  • the handover decision of the Source RAN or Source Core network entity may include selection of another RAN and/or other Core Network entity that the terminal can connect to at its current location or on the expected path of the terminal that the network can expect. .
  • the network can move the terminal's connection within the time required for the network handover (a timer may be set), and if it fails, it can notify the handover requester.
  • the Source/Target access network is not limited to the examples of FIGS.
  • FIGS. 4 and 5 may be either an eNB or a gNB, respectively, and the Source/Target Core Network Function (entity ) is not limited to the examples of Figures 4 and 5, and may be either MME or AMF, respectively. Meanwhile, the procedures or steps of the procedures described in FIGS. 4 and 5 can be combined as long as they do not contradict each other, and the combined procedures may be applied to the handover procedure of the present disclosure.
  • Figures 4a and 4b show a handover method according to an embodiment of the present disclosure.
  • the Source RAN and Source core network entities are eNB and MME, respectively, and the Target RAN and Target core network entities are assumed to be eNB and MME, respectively.
  • E-UTRAN to E-UTRAN handover case E-UTRAN to E-UTRAN handover case
  • the handover in the embodiment of FIGS. 4A and 4B may be an Inter-RAT handover.
  • the handover procedure may include the following steps (or operations).
  • the UE may provide at least one of measurement reports or UE location information to the Source eNB.
  • the measurement report may include measurement results for neighboring cell(s). For example, if the neighboring cell corresponds to a discontinuous coverage cell, coverage information of the cell (e.g., period information of the satellite providing the cell, and/or coverage including the remaining coverage time of the cell) information) may be included in the measurement report.
  • the terminal location information may include the GPS coordinates of the terminal, the Cell ID to which the terminal is connected, tracking area identity (TAI) (or tracking area code (TAC)), and/or PLMN ID.
  • TAI tracking area identity
  • TAC tracking area code
  • the neighboring cell A handover request to the handover target cell (or target RAN providing the target cell) may be directly requested (or delivered) to the source eNB. If there is more than one neighboring cell that provides coverage at the current terminal location, the terminal can select one suitable cell among them.
  • the terminal can determine the target cell in the terminal's AS Layer and provide it to the terminal's NAS Layer, and the terminal's NAS Layer sends a handover request including the identifier of the target cell and/or the identifier of the target RAN to the source eNB.
  • the terminal can select an appropriate TA among them.
  • the terminal can determine the TA to which the target cell belongs in the AS Layer of the terminal and provide it to the NAS Layer of the terminal, and the NAS Layer of the terminal may provide the identifier of the target cell, the identifier of the target TA (e.g., Tracking Area Code (TAC) or A handover request including a tracking area identity (ID) (TAI) and/or an identifier of the target RAN may be provided to the source eNB.
  • TAC Tracking Area Code
  • a handover request including a tracking area identity (ID) (TAI) and/or an identifier of the target RAN may be provided to the source eNB.
  • ID tracking area identity
  • the Source eNB may use the measurement report provided by the terminal, the terminal location information, or the coverage information of the Source eNB stored by the Source eNB (for example, if the Source eNB is a satellite, the period information of the satellite, and/or the corresponding
  • the handover may be determined using at least one of the following (the remaining coverage time of the satellite may be included in the coverage information of the source eNB). For example, through a measurement report received by the Source eNB from the UE, the UE is currently moving away from the coverage provided by the Source eNB (or the Source eNB is moving away from the UE), and a neighbor providing coverage at the current UE location.
  • the source eNB can determine the neighboring cell as the target cell for handover.
  • the Source eNB determines the time required for handover among neighboring cells (e.g., if there is a timer required for handover in the setting information of the Source eNB). Afterwards, a cell that can provide sufficient coverage can be determined as the target cell for handover.
  • Source eNB can send a handover request to the source MME.
  • This request may include at least one of Target eNB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location information.
  • UE location information may include, for example, Target TAC or Target TAI.
  • Target Cell ID may be the identifier of the target cell.
  • the target cell ID may be the identifier of the target cell determined by the source eNB in step 2, or the identifier of the target cell transmitted by the terminal in step 1.
  • Target eNB ID (or Target RAN ID) may be the identifier of the eNB (or RAN) that provides the Target Cell ID.
  • the Target eNB ID (or Target RAN ID) is the identifier of the target eNB (or target RAN) that provides the target cell determined by the Source eNB in Step 2, or the target eNB transmitted by the UE in Step 1. It may be an identifier of (or target RAN).
  • Target TAC (or Target TAI) may be the identifier of the TA to which the target cell supported by the target eNB (or RAN) belongs.
  • Target TAC (or Target TAI) may be the identifier of the TA to which the target cell belongs determined by the source eNB in step 2 or indicated by the identifier of the target cell transmitted by the UE in step 1.
  • Target TAC may be the identifier (eg, TAC or TAI) of the TA transmitted by the terminal in step 1.
  • the source eNB may provide Discontinuous Coverage Indication as an identifier (or indicator) indicating that handover has been decided due to discontinuous coverage of the source eNB.
  • the source eNB may provide Discontinuous Coverage Indication as an indicator that handover has been decided due to discontinuous coverage of the satellite. If the source eNB recognizes the location information of the terminal according to step 1 or other procedures, it can provide the latest information about the location of the terminal through UE location information.
  • Source MME can perform Target MME selection.
  • a handover target MME can be selected based on at least one of target eNB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location information (e.g., UE location information including target TAC). For example, if there is more than one candidate MME to which the target cell can connect, the source MME can select the most appropriate MME based on UE location information.
  • Source MME can request handover from target MME.
  • This request may include at least one of UE Identity, Target eNB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location information (e.g., UE location information including Target TAC).
  • the UE Identity may include, for example, the UE's International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • the request in step 5 may be delivered through a Forward Relocation Request message.
  • Target MME can perform UE Location Verification and decide whether to accept a handover request based on this. If the target MME determines in 6a and/or 6b that the terminal is allowed to use the communication service at the current location of the terminal, it may accept the handover request. If the target MME determines in 6a and/or 6b that the terminal is not permitted to use the communication service at the current location of the terminal, it may reject the handover request.
  • Target MME determines in 6a and/or 6b that it cannot verify the location of the terminal accurately enough to determine whether the terminal is allowed to use the communication service at the current location of the terminal, (1) handover You may decide to reject the request, or (2) accept the handover request and then make a decision again based on the location information of the terminal obtained by performing step 6c.
  • the target MME can determine whether the terminal is allowed to operate by accessing the PLMN operating the target MME at the terminal's current location. For this determination, the target MME may need to verify the current location of the terminal, and in this case, it may need to verify which country the terminal is currently located in.
  • the target MME can check subscriber information from the HSS indicating whether the terminal is allowed to connect to and operate the PLMN at the terminal's current location (which may include the country).
  • the target MME can obtain accurate terminal location information by initiating the Location Service (LCS) procedure supported by 3GPP. If the target MME determines that the handover request should have been rejected as a result of re-performing the judgment of 6a and/or 6b based on the accurate location information of the terminal, a handover cancellation procedure and/or deregistration is performed. The procedure can be initiated. Step 6c may be performed before or after step 14c. For example, if step 6c was performed after the terminal was registered with the target MME in step 14c, and it is determined that the handover request should have been rejected, the target MME may initiate a deregistration procedure for the terminal.
  • LCS Location Service
  • Target MME can send a Create Session Request to the target S-GW.
  • Target S-GW can send Create Session Response to target MME.
  • Target MME can request handover from target eNB.
  • the target eNB corresponds to the eNB indicated by the target eNB ID received in step 5.
  • the target eNB may transmit an acknowledgment of the handover request to the target MME.
  • Target MME can send a Create Indirect Data Forwarding Tunnel Request to the target S-GW.
  • Target S-GW can transmit Create Indirect Data Forwarding Tunnel Response to target MME.
  • Target MME can send a response to the handover request to the source MME. If the target MME decides to reject the handover request in step 6, the target MME can provide the reason for rejection through this response.
  • An example of a reason for rejection may include 'PLMN is not allowed at UE's current location.'
  • the response in step 10 may be delivered through a Forward Relocation Response message.
  • Source MME can send Create Indirect Data Forwarding Tunnel Request to Source S-GW.
  • Source S-GW can transmit Create Indirect Data Forwarding Tunnel Response to Source MME.
  • Source MME can transmit a handover command to the source eNB. If the target MME decides to reject the handover request in step 6, and/or if the source MME receives a reason for rejection from the target MME in step 10, the source MME may inform the source eNB that the handover request has been rejected. According to the contents of step 6 and/or step 10, when the source MME receives a reason for rejection on the grounds that PLMN is not allowed in the current location of the terminal, it sends this to the source eNB as the reason for rejection of the handover request. can be provided.
  • the source MME may transmit a Handover Preparation Failure message, rather than a Handover Command message, to the source eNB, and this message may include a Cause (or S1AP Cause).
  • the Source MME may provide 'PLMN is not allowed at UE's current location' as a Cause (or S1AP Cause) to the Source eNB.
  • the Source MME upon receiving the reason for rejection on the grounds that PLMN is not allowed in the current location of the terminal, transfers the source eNB to another access network that provides coverage in the current location of the terminal. The handover can be reviewed.
  • the source eNB can newly select a neighboring cell that supports a PLMN that is different from the PLMN that supports the target cell selected in step 2, and can perform the procedure again from step 2 for the newly selected neighboring cell.
  • the source eNB may not perform the handover procedure.
  • the source eNB can guide the UE to the RRC Inactive state or RRC Idle state.
  • the operations such as selecting another PLMN or another neighboring cell, inducing a change in the RRC state of the terminal instead of handover, etc. are applied in the same or similar manner even when a reason other than PLMN is not allowed in the current location is received as the reason for rejecting the handover request. You can.
  • Source eNB can transmit a handover command to the terminal.
  • the UE directly requests handover including a target cell identifier and/or target RAN identifier to the Source RAN (Source eNB), and receives a rejection of the handover request in Step 12, this is sent to the UE. It can be delivered.
  • Source RAN may provide the terminal with a reason for the rejection request based on the reason for the rejection request received in step 12.
  • the reason for the handover rejection request may include 'PLMN is not allowed at UE's current location.' The terminal that has received the reason for rejection on the grounds that the PLMN is not allowed in the terminal's current location may consider handover to another access network that provides coverage in the terminal's current location.
  • a neighboring cell that supports a PLMN different from the PLMN that supports the target cell selected in step 1 can be newly selected, and the process can be performed again from step 1 for the newly selected neighboring cell.
  • the terminal may not perform a handover request.
  • the terminal may transition to the Idle state.
  • the terminal may request deregistration from the core network. Operations such as selecting another PLMN or another neighboring cell, changing the status of the terminal instead of handover, or requesting deregistration are the same or similar even if a reason other than that the PLMN is not allowed in the current location is received as the reason for rejecting the handover request. It can be applied.
  • a handover execution phase may be performed.
  • the terminal can transmit handover completion to the target eNB.
  • Target eNB can transmit Handover Notify to target MME.
  • the UE can perform the Tracking Area Update procedure for the target MME through the Target E-UTRAN (eNB).
  • eNB Target E-UTRAN
  • FIGS. 4A and 4B may be omitted and/or additional steps may be further performed. Additionally, steps may be performed in an order other than that illustrated in FIGS. 4A and 4B. Additionally, the steps illustrated in FIGS. 4A and 4B may be combined with the steps illustrated in FIGS. 5A and 5B to be described later as long as they do not contradict each other.
  • Figures 5a and 5b show a handover method according to an embodiment of the present disclosure.
  • the Source RAN and Source core network entities are assumed to be eNB and MME, respectively, and the Target RAN and Target core network entities are assumed to be gNB and AMF, respectively.
  • E-UTRAN to NG-RAN handover case E-UTRAN to NG-RAN handover case
  • the Target eNB is the Target gNB
  • the Target MME is the Target AMF
  • the Target S-GW is the Target SMF (or Target SMF+PGW-C ), which corresponds to the case where HSS is changed to UDM (or UDM+HSS).
  • Descriptions of operations (or steps) that are common to the operations (or steps) described above in FIGS. 4A and 4B may be omitted from the description below of FIGS. 5A and 5B, and the descriptions described above in FIGS. 4A and 4B may be referred to. there is.
  • the handover in the embodiment of FIGS. 5A and 5B may be an Inter-RAT handover.
  • the handover procedure may include the following steps (or operations).
  • the UE may provide at least one of measurement reports or UE location information to the Source eNB.
  • the measurement report may include measurement results for neighboring cells. For example, if the neighboring cell corresponds to a discontinuous coverage cell, coverage information of the cell (e.g., period information of the satellite providing the cell, and/or coverage including the remaining coverage time of the cell) information) may be included in the measurement report.
  • the terminal location information may include the GPS coordinates of the terminal, the Cell ID to which the terminal is connected, TAI (or TAC), and/or PLMN ID.
  • the neighboring cell A handover request to the handover target cell (or target RAN providing the target cell) may be directly requested (or delivered) to the source eNB. If there is more than one neighboring cell that provides coverage at the current terminal location, the terminal can select one suitable cell among them.
  • the terminal can determine the target cell in the terminal's AS Layer and provide it to the terminal's NAS Layer, and the terminal's NAS Layer sends a handover request including the identifier of the target cell and/or the identifier of the target RAN to the source eNB.
  • the terminal can select an appropriate TA among them.
  • the terminal can determine the TA to which the target cell belongs in the AS Layer of the terminal and provide it to the NAS Layer of the terminal, and the NAS Layer of the terminal may provide the identifier of the target cell, the identifier of the target TA (e.g., Tracking Area Code (TAC) or A handover request including a tracking area identity (ID) (TAI) and/or an identifier of the target RAN may be provided to the source eNB.
  • TAC Tracking Area Code
  • a handover request including a tracking area identity (ID) (TAI) and/or an identifier of the target RAN may be provided to the source eNB.
  • ID tracking area identity
  • the Source eNB provides measurement reports provided by the terminal, terminal location information, or coverage information of the Source eNB stored by the Source eNB (e.g., if the Source eNB is a satellite, period information of the satellite, and/or The handover may be determined using at least one of the following (the remaining coverage time of the corresponding satellite may be included in the coverage information of the source eNB). For example, through a measurement report received by the Source eNB from the UE, the UE is currently moving away from the coverage provided by the Source eNB (or the Source eNB is moving away from the UE), and a neighbor providing coverage at the current UE location. If the presence of a cell is identified, the source eNB can determine the neighboring cell as the target cell for handover.
  • the Source eNB determines the time required for handover among neighboring cells (e.g., if there is a timer required for handover in the setting information of the Source eNB). Afterwards, a cell that can provide sufficient coverage can be determined as the target cell for handover.
  • Source eNB can send a handover request to the source MME.
  • This request may include at least one of Target gNB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location information.
  • UE location information may include, for example, Target TAC or Target TAI.
  • Target Cell ID may be the identifier of the target cell.
  • the target cell ID may be the identifier of the target cell determined by the source eNB in step 2, or the identifier of the target cell transmitted by the terminal in step 1.
  • Target gNB ID (or Target RAN ID) is the identifier of the gNB (or RAN) that provides the Target Cell ID.
  • the Target gNB ID (or Target RAN ID) is the identifier of the target gNB (or target RAN) that provides the target cell determined by the Source eNB in Step 2, or the target gNB transmitted by the UE in Step 1 It may be an identifier of (or target RAN).
  • Target TAC (or Target TAI) may be the identifier of the TA to which the target cell supported by the target eNB (or RAN) belongs.
  • Target TAC (or Target TAI) may be the identifier of the TA to which the target cell belongs determined by the source eNB in step 2 or indicated by the identifier of the target cell transmitted by the UE in step 1.
  • Target TAC may be the identifier (eg, TAC or TAI) of the TA transmitted by the terminal in step 1.
  • the source eNB may provide Discontinuous Coverage Indication as an identifier (or indicator) indicating that handover has been decided due to discontinuous coverage of the source eNB.
  • the source eNB may provide Discontinuous Coverage Indication as an indicator that handover has been decided due to discontinuous coverage of the satellite. If the source eNB recognizes the location information of the terminal according to step 1 or other procedures, it can provide the latest information about the location of the terminal through UE location information.
  • Source MME can perform Target AMF selection.
  • the handover target AMF can be selected based on at least one of target gnB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location information (e.g., UE location information including target TAC). For example, if there is more than one candidate AMF to which the target cell can be connected, the source MME can select the most appropriate AMF based on UE location information.
  • Source MME can request handover to target AMF.
  • This request may include at least one of UE Identity, Target gNB ID, Discontinuous Coverage Indication, Target Cell ID, or UE location (e.g., UE location information including Target TAC).
  • the UE Identity may include, for example, the UE's International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • the request in step 5 may be delivered through a Forward Relocation Request message.
  • Target AMF can perform UE Location Verification and decide whether to accept a handover request based on this. If the Target AMF determines in 6a and/or 6b that the terminal is allowed to use the communication service at the current location of the terminal, it may accept the handover request. If the Target AMF determines in 6a and/or 6b that the terminal is not permitted to use the communication service at the current location of the terminal, it may reject the handover request.
  • Target AMF determines in 6a and/or 6b that it cannot verify the location of the terminal accurately enough to determine whether the terminal is allowed to use the communication service at the current location of the terminal, (1) handover You may decide to reject the request, or (2) accept the handover request and then make a decision again based on the location information of the terminal obtained by performing step 6c.
  • Target AMF can determine whether the terminal is allowed to operate by accessing the PLMN that operates the target AMF at the terminal's current location. For this determination, the Target AMF may need to verify the current location of the terminal, and in this case, it may need to verify which country the terminal is currently located in.
  • Target AMF can check subscriber information from UDM (or UDM+HSS) indicating whether the terminal is allowed to connect to and operate the PLMN at the terminal's current location (which may include the country).
  • UDM or UDM+HSS
  • Target AMF can obtain accurate terminal location information by initiating the Location Service (LCS) procedure supported by 3GPP. If the Target AMF determines that the handover request should have been rejected as a result of re-performing the judgment of 6a and/or 6b based on the accurate location information of the terminal, a handover cancellation procedure and/or deregistration is performed. The procedure can be initiated. Step 6c may be performed before or after step 14c. For example, if step 6c was performed after the terminal was registered with the Target AMF in step 14c, and it is determined that the handover request should have been rejected, the Target AMF may initiate a deregistration procedure for the terminal.
  • LCS Location Service
  • Target AMF can send a PDU Session Create SM Context Request to Target SMF (or Target SMF+PGW-C).
  • Target SMF (or Target SMF+PGW-C) can transmit a PDU Session Create SM Context Response to Target AMF.
  • Target AMF can request handover from target gNB.
  • the target gNB corresponds to the gNB indicated by the target gNB ID received in step 5.
  • the target gNB may transmit an acknowledgment of the handover request to the target AMF.
  • Target AMF can send a PDU Session Update SM Context Request to Target SMF (or Target SMF+PGW-C).
  • Target SMF or Target SMF+PGW-C
  • Target AMF can transmit a PDU Session Update SM Context Response.
  • Target AMF can send a response to the handover request to the source MME. If the Target AMF decides to reject the handover request in step 6, the Target AMF can provide the reason for rejection through this response.
  • An example of a reason for rejection may include 'PLMN is not allowed at UE's current location.' As an example, the response in step 10 may be delivered through a Forward Relocation Response message.
  • Source MME can send Create Indirect Data Forwarding Tunnel Request to Source S-GW.
  • Source S-GW can transmit Create Indirect Data Forwarding Tunnel Response to Source MME.
  • Source MME can transmit a handover command to the source eNB. If the Target AMF decides to reject the handover request in step 6, and/or if the Source MME receives a reason for rejection from the Target AMF in step 10, the Source MME may inform the Source eNB that the handover request has been rejected. According to the contents of step 6 and/or step 10, when the source MME receives a reason for rejection on the grounds that PLMN is not allowed in the current location of the terminal, it sends this to the source eNB as the reason for rejection of the handover request. can be provided.
  • the source MME may transmit a Handover Preparation Failure message, rather than a Handover Command message, to the source eNB, and this message may include a Cause (or S1AP Cause).
  • the Source MME may provide 'PLMN is not allowed at UE's current location' as a Cause (or S1AP Cause) to the Source eNB.
  • the Source MME upon receiving the reason for rejection on the grounds that PLMN is not allowed in the current location of the terminal, directs the Source eNB to another access network that provides coverage in the current location of the terminal. The handover can be reviewed.
  • a neighboring cell that supports a PLMN different from the PLMN that supports the target cell selected in step 2 can be newly selected, and the process can be performed again from step 2 for the newly selected neighboring cell.
  • the source eNB may not perform the handover procedure.
  • the source eNB can guide the UE to the RRC Inactive state or RRC Idle state.
  • the operations such as selecting another PLMN or another neighboring cell, inducing a change in the RRC state of the terminal instead of handover, etc. will be applied in the same or similar manner even when a reason other than PLMN is not allowed in the current location is received as the reason for rejecting the handover request. You can.
  • Source eNB can transmit a handover command to the terminal.
  • the UE directly requests handover including a target cell identifier and/or target RAN identifier to the Source RAN (Source eNB), and receives a rejection of the handover request in Step 12, this is sent to the UE. It can be delivered.
  • Source RAN may provide the terminal with a reason for the rejection request based on the reason for the rejection request received in step 12.
  • the reason for the handover rejection request may include 'PLMN is not allowed at UE's current location.' The terminal that has received the reason for rejection on the grounds that the PLMN is not allowed in the terminal's current location may consider handover to another access network that provides coverage in the terminal's current location.
  • a neighboring cell that supports a PLMN different from the PLMN that supports the target cell selected in step 1 can be newly selected, and the process can be performed again from step 1 for the newly selected neighboring cell.
  • the terminal may not perform a handover request.
  • the terminal may transition to the Idle state.
  • the terminal may request deregistration from the core network. Operations such as selecting another PLMN or another neighboring cell, changing the status of the terminal instead of handover, or requesting deregistration are the same or similar even if a reason other than that the PLMN is not allowed in the current location is received as the reason for rejecting the handover request. It can be applied.
  • a handover execution phase may be performed.
  • the terminal can transmit handover completion to the target gNB.
  • Target gNB can transmit Handover Notify to target AMF.
  • the UE can perform the Tracking Area Update procedure for the target AMF through the target RAN (gNB).
  • gNB target RAN
  • FIGS. 5A and 5B may be omitted and/or additional steps may be further performed. Additionally, steps may be performed in an order other than that illustrated in FIGS. 5A and 5B. Additionally, the steps illustrated in FIGS. 5A and 5B may be combined with the steps illustrated in FIGS. 4A and 4B to be described later as long as they do not contradict each other.
  • Figure 6 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
  • the terminal may include a transceiver 610, a control unit 620, and a storage unit 630.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 610 can transmit and receive signals with other entities.
  • the transceiver 610 may receive data from, for example, a base station or network entity.
  • the transceiver 610 may be referred to as a transceiver.
  • the control unit 620 can control the overall operation of the terminal according to the embodiment proposed by the present disclosure.
  • the control unit 620 may control signal flow between each block to perform the operations according to FIGS. 1 to 5 described above.
  • the control unit 620 can control the operations proposed in this disclosure to support the handover procedure.
  • the control unit 620 may be implemented with at least one processor.
  • the control unit 620 may also be referred to as a controller.
  • the storage unit 630 may store at least one of information transmitted and received through the transmitting and receiving unit 610 and information generated through the control unit 620.
  • the storage unit 630 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 5.
  • Storage unit 630 may be referred to as memory.
  • Figure 7 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
  • the base station may include a transceiver unit 710, a control unit 720, and a storage unit 730.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 710 can transmit and receive signals with other entities.
  • the transceiver 710 may receive data from, for example, a terminal or a network entity.
  • the control unit 720 can control the overall operation of the base station according to the embodiment proposed in this disclosure.
  • the control unit 720 may control signal flow between each block to perform the operations according to FIGS. 1 to 5 described above.
  • the controller 720 can control the operations proposed in this disclosure to support the handover procedure.
  • the storage unit 730 may store at least one of information transmitted and received through the transmitting and receiving unit 710 and information generated through the control unit 720.
  • the storage unit 730 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 5.
  • FIG. 8 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
  • the network entity in FIG. 8 may be, for example, one of MME, S-GW, P-GW, HSS, AMF, SMF, PCF, UPF, AUSF, UDM, AF, NSSF, NRF or NEF in FIGS. 1 to 5.
  • the network entity may include a transceiver 810, a control unit 820, and a storage unit 830.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 810 can transmit and receive signals with other entities.
  • the transceiver 810 may receive data from, for example, a terminal, a base station, or another network entity.
  • the control unit 820 can control the overall operation of the network entity according to the embodiment proposed by the present invention.
  • the control unit 820 may control signal flow between each block to perform the operations according to FIGS. 1 to 5 described above.
  • the control unit 820 can control the operations proposed in this disclosure to support the handover procedure.
  • the storage unit 830 may store at least one of information transmitted and received through the transmitting and receiving unit 810 and information generated through the control unit 820.
  • the storage unit 730 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 5.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation se rapporte à un système de communication 5G ou 6G permettant de prendre en charge des débits de transmission de données supérieurs. Un procédé, mis en oeuvre par une station de base source de la présente divulgation, peut comprendre les étapes consistant à : recevoir, en provenance d'un terminal, des informations de rapport de mesure concernant au moins une cellule voisine ; sur la base d'informations de couverture de la station de base source et/ou des informations de rapport de mesure, déterminer s'il faut effectuer un transfert intercellulaire vers une station de base cible ; et transmettre, à une entité de réseau source, une demande de transfert intercellulaire.
PCT/KR2023/011742 2022-08-09 2023-08-09 Procédé et dispositif destinés à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil WO2024035109A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020220099307A KR20240020946A (ko) 2022-08-09 2022-08-09 무선통신 시스템에서 단말의 등록 및 연결 관리의 방법 및 장치
KR10-2022-0099307 2022-08-09

Publications (1)

Publication Number Publication Date
WO2024035109A1 true WO2024035109A1 (fr) 2024-02-15

Family

ID=89852079

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/011742 WO2024035109A1 (fr) 2022-08-09 2023-08-09 Procédé et dispositif destinés à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil

Country Status (2)

Country Link
KR (1) KR20240020946A (fr)
WO (1) WO2024035109A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110110233A (ko) * 2008-12-23 2011-10-06 콸콤 인코포레이티드 폐쇄 가입자 그룹 가입 정보에 기초한 핸드오버 제어
KR20180083262A (ko) * 2017-01-12 2018-07-20 주식회사 케이티 이종 네트워크 핸드오버 제어 방법 및 그 장치
KR20200071004A (ko) * 2018-12-10 2020-06-18 한국전자통신연구원 비지상 네트워크에서의 핸드오버 방법 및 이를 위한 장치
WO2020231123A1 (fr) * 2019-05-15 2020-11-19 Lg Electronics Inc. Procédé et appareil pour effectuer un transfert conditionnel sur la base du temps de service de cellules candidates dans un système de communication sans fil
US20220095179A1 (en) * 2019-06-06 2022-03-24 Huawei Technologies Co., Ltd. Handover Method And Apparatus

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110110233A (ko) * 2008-12-23 2011-10-06 콸콤 인코포레이티드 폐쇄 가입자 그룹 가입 정보에 기초한 핸드오버 제어
KR20180083262A (ko) * 2017-01-12 2018-07-20 주식회사 케이티 이종 네트워크 핸드오버 제어 방법 및 그 장치
KR20200071004A (ko) * 2018-12-10 2020-06-18 한국전자통신연구원 비지상 네트워크에서의 핸드오버 방법 및 이를 위한 장치
WO2020231123A1 (fr) * 2019-05-15 2020-11-19 Lg Electronics Inc. Procédé et appareil pour effectuer un transfert conditionnel sur la base du temps de service de cellules candidates dans un système de communication sans fil
US20220095179A1 (en) * 2019-06-06 2022-03-24 Huawei Technologies Co., Ltd. Handover Method And Apparatus

Also Published As

Publication number Publication date
KR20240020946A (ko) 2024-02-16

Similar Documents

Publication Publication Date Title
US11729854B2 (en) Network assisted connection
WO2018021861A1 (fr) Procédé et appareil pour effectuer une procédure de spécification de cellule pour un nr basé sur une tranche de réseau dans un système de communication sans fil
WO2017023129A1 (fr) Procédé de communication utilisant des informations de contexte de terminal dans un système de communication sans fil, et station de base
WO2022177321A1 (fr) Procédé et appareil pour des améliorations dans et se rapportant à la gestion d'un état de catastrophe dans un système de communication mobile
WO2022158874A1 (fr) Procédé et dispositif de gestion de session dans un système de communication mobile
WO2024035109A1 (fr) Procédé et dispositif destinés à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil
CN116456318A (zh) 通信方法、装置及系统
WO2023191458A1 (fr) Procédé et appareil pour la mise en place d'une politique d'utilisation dans un système de communication sans fil
WO2024147594A1 (fr) Procédé et dispositif de prise en charge d'un service de collecte et d'analyse de données de tranche liées à une politique de terminal
WO2024076174A1 (fr) Procédé et appareil permettant de fournir des informations de politique d'ue dans un système de communication sans fil
WO2024144221A1 (fr) Procédé et dispositif de synchronisation de règle de terminal entre des entités dans un système de communication sans fil
WO2024096376A1 (fr) Procédé et dispositif de fourniture d'un trajet d'accès dans un système de communication sans fil
WO2024096623A1 (fr) Procédé et appareil de gestion de session basée sur des informations de liaison terrestre dans un système de communication sans fil
WO2024144321A1 (fr) Appareil et procédé de transfert inter-rmtp de session à acheminement domestique dans un système de communication sans fil
WO2023075511A1 (fr) Procédé et appareil pour vérifier la conformité avec une politique de sélection d'itinéraire d'équipement utilisateur
WO2024147647A1 (fr) Procédé et appareil pour fournir une politique d'équipement utilisateur (ue) dans un système de communication sans fil
WO2023191461A1 (fr) Procédé de commande de terminal et fonction de gestion d'accès de mobilité (amf) pour la communication avec un satellite de réseau d'accès radio (ran), et dispositif associé
WO2024147691A1 (fr) Procédé et appareil pour fournir une politique d'ue dans un système de communication sans fil
WO2024035088A1 (fr) Procédé et dispositif d'hébergement d'informations de réseau utilisant la direction d'itinérance dans un système de communication sans fil
WO2024085655A1 (fr) Procédé et appareil de sélection de fonction de commande de politique dans un système de communication sans fil prenant en charge un interfonctionnement entre des réseaux
WO2024101895A1 (fr) Procédé et dispositif d'autorisation basés sur une upf dans un système de communication sans fil
WO2022203360A1 (fr) Procédé et dispositif de communication pour prendre en charge l'authentification d'un engin volant sans pilote embarqué dans un système de communication sans fil
WO2023191514A1 (fr) Procédé et dispositif de communication dans un système de communication sans fil avec prise en charge de multiples fonctions de commande d'admission de tranche de réseau
WO2023214781A1 (fr) Procédé de prise en charge de facturation de service informatique en périphérie de terminal itinérant
WO2024035135A1 (fr) Procédé et appareil de gestion de session de service informatique périphérique dans un système de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23852980

Country of ref document: EP

Kind code of ref document: A1