WO2022235100A1 - 망간의 단말 이동성을 지원하는 방법 및 장치 - Google Patents
망간의 단말 이동성을 지원하는 방법 및 장치 Download PDFInfo
- Publication number
- WO2022235100A1 WO2022235100A1 PCT/KR2022/006469 KR2022006469W WO2022235100A1 WO 2022235100 A1 WO2022235100 A1 WO 2022235100A1 KR 2022006469 W KR2022006469 W KR 2022006469W WO 2022235100 A1 WO2022235100 A1 WO 2022235100A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- terminal
- information
- amf
- context
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 82
- 230000004044 response Effects 0.000 claims abstract description 38
- 238000004891 communication Methods 0.000 abstract description 45
- 230000005540 biological transmission Effects 0.000 abstract description 15
- 238000007726 management method Methods 0.000 description 40
- 230000006870 function Effects 0.000 description 25
- 238000005516 engineering process Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 20
- 238000012546 transfer Methods 0.000 description 18
- 230000008569 process Effects 0.000 description 16
- 230000001413 cellular effect Effects 0.000 description 14
- 238000010295 mobile communication Methods 0.000 description 11
- 238000003860 storage Methods 0.000 description 10
- 238000013473 artificial intelligence Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 239000002699 waste material Substances 0.000 description 8
- 238000004590 computer program Methods 0.000 description 4
- 230000004913 activation Effects 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010801 machine learning Methods 0.000 description 2
- 241000760358 Enodes Species 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
- H04W36/385—Reselection control by fixed network equipment of the core network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- 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/042—Public Land Mobile systems, e.g. cellular systems
-
- 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/10—Small scale networks; Flat hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Definitions
- the present disclosure relates to a method and apparatus for supporting UE mobility between networks. More specifically, a method and apparatus for supporting UE mobility between a private cellular network (SNPN; standalone non-public network) and another cellular network (eg, a general public cellular network or other private cellular network (SNPN)). It's about SNPN; standalone non-public network
- another cellular network eg, a general public cellular network or other private cellular network (SNPN)
- 5G mobile communication technology defines a wide frequency band to enable fast transmission speed and new services. It can also be implemented in the very high frequency band ('Above 6GHz') called Wave).
- 6G mobile communication technology which is called a system after 5G communication (Beyond 5G)
- Beyond 5G in order to achieve transmission speed 50 times faster than 5G mobile communication technology and ultra-low latency reduced by one-tenth, Tera Implementations in the Terahertz band (such as, for example, the 95 GHz to 3 THz band) are being considered.
- ultra-wideband service enhanced Mobile BroadBand, eMBB
- high reliability / ultra-low latency communication Ultra-Reliable Low-Latency Communications, URLLC
- massive-scale mechanical communication massive Machine-Type Communications, mMTC
- Beamforming and Massive MIMO to increase the propagation distance and mitigate the path loss of radio waves in the ultra-high frequency band with the goal of service support and performance requirements, and efficient use of ultra-high frequency resources
- various numerology eg, operation of multiple subcarrier intervals
- New channel coding methods such as LDPC (Low Density Parity Check) code for data transmission and polar code for reliable transmission of control information, L2 pre-processing, dedicated dedicated to specific services Standardization of network slicing that provides a network has progressed.
- LDPC Low Density Parity Check
- the Intelligent Factory Intelligent Internet of Things, IIoT
- IAB Intelligent Internet of Things
- IAB Intelligent Internet of Things
- 2-step RACH for simplifying random access procedures
- 5G baseline for the grafting of Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies Standardization of the system architecture/service field for architecture (eg, Service based Architecture, Service based Interface), Mobile Edge Computing (MEC) receiving services based on the location of the terminal, etc. is also in progress.
- NFV Network Functions Virtualization
- SDN Software-Defined Networking
- the network access process of the terminal is performed in order to minimize this, a procedure for bringing the context information of the terminal stored in the existing serving network to the target network is implemented.
- SNPN locally configured private cellular network
- PLMN public land mobile network
- SNPN private cellular network
- SNPN private cellular network
- the temporary ID of the terminal allocated from the existing serving network is transmitted to the target network, and a new Access and Mobility Management Function (AMF) of the target network is transmitted to the terminal.
- AMF Access and Mobility Management Function
- the context of the terminal can be stored from the old AMF of the serving network.
- the context (UE context) of the UE may include information for mobility management (MM) of the UE, Subscription Permanent Identifier (SUPI) information of the UE, and/or security related information.
- MM mobility management
- SUPI Subscription Permanent Identifier
- the UE context is information (PDU Session level context) for SM (session management) serviced by the UE, for example, PDU (Protocol Data Unit) session ID and SMF (Session Management Function) ID for managing the PDU session. Alternatively, it may further include address information and the like.
- the UE context further includes at least one of association information with another NF (Network Function) (eg, information for AM policy association, information for UE policy association, and/or information for UE NWDAF association) or event subscription information. can do.
- the UE context may include, for example, all or part of the items (parameters) included in Table 5.2.2.2.2-1 (UE Context in AMF) of IEEE TS 23.502.
- the present disclosure discloses a method for reducing inefficiency due to failure of an activation attempt according to the SM context of the UE.
- the present disclosure provides routing of the initial NAS (Non Access Stratum) message sent by the terminal from the RAN to the appropriate AMF when the terminal sends an initial NAS message such as a registration request message to the AMF while moving between SNPN networks in the idle state. discloses a method for doing so.
- NAS Non Access Stratum
- a method of a first AMF entity includes: receiving, from a terminal, through a base station, a registration request message for a first network of a first AMF entity - The registration request message is assigned by a second AMF including temporary ID information of the terminal; transmitting, to the second AMF entity, a context request message for requesting context information for the terminal based on the registration request message; and receiving, from the second AMF entity, a response message corresponding to the context request message, wherein at least one of a first network of the first AMF entity or a second network of the second AMF entity is connected to the SNPN.
- the response message includes at least a part of context information stored in the second AMF entity, and the context information includes information for mobility management of the terminal, authentication-related context information, and a session for a service provided to the terminal. It may include at least one of information for management and event subscription related information for the terminal.
- a method of a second AMF entity includes, from the first AMF entity, receiving a context request message for requesting context information for a terminal that has transmitted a registration request message to the first AMF entity; and transmitting, to the first AMF entity, a response message corresponding to the context request message, wherein at least one of a first network of the first AMF entity or a second network of the second AMF entity is SNPN.
- the response message includes at least a part of context information stored in the second AMF entity
- the context information includes information for mobility management of the terminal, authentication-related context information, and a session for a service provided to the terminal. It may include at least one of information for management and event subscription related information for the terminal.
- AMF access and mobility management function
- a registration request message for network registration from a terminal moved from a first network that is a standalone non-public network (SNPN) to a second network receiving, wherein the registration request message includes temporary ID (identifier) information of the terminal and network ID (NID) information of the first network to which the temporary ID information is allocated; identifying a first AMF entity belonging to the first network based on the temporary ID information and the NID information; transmitting, to the first AMF entity, a request message for requesting context information of the terminal; and receiving, from the first AMF entity, a response message including the context information.
- SNPN non-public network
- the method includes: when the mobility of the terminal from the first network to the second network is an inter-SNPN movement, updating a registration state including a list of PDU (protocol data unit) session IDs to be released The method may further include sending a message to the first AMF entity.
- PDU protocol data unit
- the list of PDU session IDs may be obtained from the context information.
- the method may further include: deleting session management (SM) context information associated with the list of PDU session IDs from the context information.
- SM session management
- the first AMF entity may request a first session management function (SMF) entity belonging to the first network to release session management (SM) context information associated with the list of PDU session IDs.
- SMS session management function
- the temporary ID information may be a globally unique temporary identifier (5G-GUTI).
- 5G-GUTI globally unique temporary identifier
- the first AMF entity may be selected by the base station receiving the registration request message.
- the method may further include: transmitting a registration acknowledgment message including temporary ID information of the terminal newly allocated by the second network to the terminal.
- an access and mobility management function includes a transceiver; and a control unit connected to the transceiver, wherein the control unit: receives a registration request message for network registration from a terminal moving from a first network that is a standalone non-public network (SNPN) to a second network, and - the registration request the message includes temporary ID (identifier) information of the terminal and network ID (NID) information of the first network to which the temporary ID information has been allocated; based on the temporary ID information and the NID information, the first Identify a first AMF entity belonging to a network, transmit a request message requesting context information of the terminal to the first AMF entity, and receive a response message including the context information from the first AMF entity can be configured.
- SNPN standalone non-public network
- control unit Update registration status including a list of protocol data unit (PDU) session IDs to be released when mobility of the terminal from the first network to the second network is an inter-SNPN movement and send a message to the first AMF entity.
- PDU protocol data unit
- the list of PDU session IDs may be obtained from the context information.
- the controller may be further configured to: delete session management (SM) context information associated with the list of PDU session IDs from the context information.
- SM session management
- the first AMF entity may request a first session management function (SMF) entity belonging to the first network to release session management (SM) context information associated with the list of PDU session IDs.
- SMS session management function
- the temporary ID information may be a globally unique temporary identifier (5G-GUTI).
- 5G-GUTI globally unique temporary identifier
- the first AMF entity may be selected by the base station receiving the registration request message.
- the newly selected new AMF requests the context for the terminal from the old AMF that has allocated the temporary ID, and the old AMF provides information about the terminal, that is, the UE context to the new will be forwarded to the AMF. Therefore, according to an embodiment of the present disclosure, when authentication is successfully performed for the registration request message sent by the terminal, there is no need to perform a separate authentication process for the UE.
- the new AMF obtains information about the PDU session that the terminal received service from and the SMF that manages the PDU session from the context for the session included in the UE context, and the PDU session Attempts to activate again.
- the networks serviced by the new AMF and the old AMF are different networks, and if one of the two networks is SNPN, roaming is not supported between the two networks, so the process of reactivating the PDU session must fail.
- there are problems of wasting network resources and delaying network access time due to attempts and failures to allocate resources of the access network unnecessarily.
- unnecessary resource waste and network connection delay can be prevented by limiting PDU session activation attempts that are inevitably failing by adjusting the processing for the UE SM context that cannot but fail in advance. .
- the RAN when the terminal moves between SNPN networks in the idle state and sends an initial NAS message such as a registration request message to the AMF, the RAN routes the initial NAS message sent by the terminal to the appropriate AMF. There is an effect that it is not necessary to perform a procedure for acquiring unnecessary UE context between AMFs.
- FIG. 1 is a diagram showing the structure of a communication network having an interface between AMFs of each communication network for interworking between communication networks including SNPN according to an embodiment of the present disclosure.
- FIG. 2 is a diagram for explaining a process for routing an Initial NAS message to an appropriate AMF based on a temporary ID of a terminal allocated by a SNPN, according to an embodiment of the present disclosure.
- 3A and 3B are diagrams for explaining a procedure for a terminal to register a network in a newly moved communication network when a communication network to which a temporary ID of the terminal is allocated is an SNPN, according to an embodiment of the present disclosure.
- FIG. 4 is a diagram for explaining a procedure for a terminal to register a network in a newly moved communication network when a communication network to which a temporary ID of the terminal is allocated is an SNPN, according to another embodiment of the present disclosure.
- 5A and 5B are diagrams for explaining a procedure for a terminal to register a network with a newly moved SNPN when a communication network to which a temporary ID of the terminal is allocated is a PLMN, according to an embodiment of the present disclosure.
- FIG. 6 is a diagram for describing a procedure for a terminal to register a network with a newly moved SNPN when a communication network to which a temporary ID of the terminal is allocated is a PLMN, according to another embodiment of the present disclosure.
- FIG. 7 illustrates a method of a first AMF entity according to an embodiment of the present disclosure.
- FIG. 8 illustrates a method of a second AMF entity according to an embodiment of the present disclosure.
- FIG. 9 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
- FIG. 10 is a diagram illustrating a structure of a base station according to an embodiment of the present invention.
- FIG. 11 is a diagram illustrating the structure of a network entity according to an embodiment of the present invention.
- each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions.
- These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions.
- These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory.
- the instructions stored in the flowchart block(s) may also be possible for the instructions stored in the flowchart block(s) to produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s).
- the computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It may also be possible for instructions to perform the processing equipment to provide steps for performing the functions described in the flowchart block(s).
- each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in the blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it may be possible that the blocks are sometimes performed in a reverse order according to a corresponding function.
- ' ⁇ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and ' ⁇ unit' performs certain roles. do.
- '-part' is not limited to software or hardware.
- ' ⁇ unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors.
- ' ⁇ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and programs. Includes procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
- components and ' ⁇ units' may be combined into a smaller number of components and ' ⁇ units' or further separated into additional components and ' ⁇ units'.
- components and ' ⁇ units' may be implemented to play one or more CPUs in a device or secure multimedia card.
- ' ⁇ unit' may include one or more processors.
- the base station is a subject performing resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network.
- the terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.
- UE user equipment
- MS mobile station
- a cellular phone a smart phone
- computer or a multimedia system capable of performing a communication function.
- the present disclosure describes a technique for a terminal to receive broadcast information from a base station in a wireless communication system.
- the present disclosure relates to a communication technique that converges a 5th generation (5G) communication system for supporting a higher data rate after the 4th generation (4G) system with an Internet of Things (IoT) technology, and a system thereof.
- the present disclosure provides intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied to
- Terms referring to, terms referring to messages, terms referring to components of an apparatus, and the like are exemplified for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms having equivalent technical meanings may be used.
- FIG. 1 is a diagram showing the structure of a communication network having an interface between AMFs of each communication network for interworking between communication networks including SNPN according to an embodiment of the present disclosure.
- At least one of the two communication networks is an SNPN network.
- the AMFs in charge of registration management and mobility management of each network are shared with each other or are connected to each other through the N14 interface between the AMFs of each network. Therefore, registration and mobility-related UE context for a terminal registered in one communication network can be shared according to the request of the AMF of another communication network connected through the N14 interface, and interworking between the two communication networks is possible.
- FIG. 2 is a diagram for explaining a process for routing an Initial NAS message to an appropriate AMF based on a temporary ID of a terminal allocated by a SNPN, according to an embodiment of the present disclosure.
- a temporary ID (eg, 5G-GUTI (Globally Unique Temporary Identity)) may be assigned from the old AMF 240 ((operation 241) )).
- the terminal moves to Network B, the terminal is based on the network information (eg, PLMN ID, NID (network id)) broadcast in the RAN (eg, 5G-(R) AN) Network
- the network information eg, PLMN ID, NID (network id)
- the terminal may operate as in the idle state (operation 201). That is, the terminal may be in an idle state.
- the terminal may transfer the registration request message to the moved network, Network B, to the RAN 210 through the RRC message (operation 202).
- GUAMI Globally Unique AMF ID
- the terminal sends along with the registration request message to the RAN 210 so that the RAN 210 can find an appropriate AMF and route the registration request message , 5G-GUTI) and the NID of Network A, which is the SNPN assigned to the UE with 5G-GUTI, can be transmitted through the RRC message.
- identification information included in the AN parameter may be used by the base station to find an appropriate AMF.
- identification information eg, 5G-GUTI and/or NID
- the registration request message may be used to identify the terminal as well as the AMF.
- AMF and, in one embodiment, the NID of Network A may be used to identify Network A, which is an SNPN. This may be distinguished from the PLMN ID for identifying the PLMN.
- the RAN receiving the GUAMI (or 5G-GUTI) and the NID can route the GUAMI (or the GUAMI obtained from the 5G-GUTI) and the AMF corresponding to the NID (valid), the received Registration request message It can be transmitted to the old AMF 240 indicated by the GUAMI and the NID (ie, the old AMF 240 identified by the GUAMI and the NID) to perform the registration process.
- the UE also transmits the NID along with the GUAMI (or 5G-GUTI) to the RAN when transmitting the Registration request message through the RRC message when the 5G-GUTI is allocated from the SNPN.
- the operation of the terminal including the NID together with the GUAMI (or 5G-GUTI) in the AN parameter is equally applied not only to the registration request but also to other initial NAS messages.
- the UE For example, for service request, deregistration request, and control plane service request messages, when the UE carries the corresponding initial NAS message in an RRC message and delivers it to the RAN, the GUAMI (or 5G-GUTI) and the NID are included. AN parameters are loaded together and sent.
- GUAMI or 5G-GUTI
- the registration request message may be transmitted to the selected AMF (operation 212).
- the terminal creates the registration request message
- the 5G-GUTI allocated from the old AMF 240 and the NID of network A, which is the SNPN allocated with the 5G-GUTI, are included in the registration request message, and the network A used Integrity protection can be applied to the registration request message by using the security key.
- the new AMF may request the UE context for the corresponding terminal including the registration request message received from the terminal from the old AMF based on the 5G-GUTI and NID information included in the registration request message (operation 221).
- the terminal may transmit a UE context transfer request message (eg, UEContextTransfer message) including a Registration request message received from the terminal to the old AMF in order to request the UE context.
- the old AMF having received the UE context request, authenticates the registration request message, and when it is correctly authenticated, it may transmit a response to the request together with the UE context to the new AMF (operation 242).
- the old AMF may transmit a UE context transfer response message (eg, a UEContextTransfer Response message) including the UE context to the new AMF.
- the new AMF may not perform a separate authentication procedure for the terminal, and may share a security context for secure message transmission and reception between the terminal and the new AMF ( action 222). Then, the new AMF may inform the old AMF that the UE context is successfully transferred, and that the terminal is registered through the new AMF (operation 223). In one embodiment, the new AMF may transmit a registration status update message (eg, RegistrationStatusUpdate message) to the old AMF in order to inform that the UE context is successfully transferred, and that the terminal is registered through the new AMF.
- a registration status update message eg, RegistrationStatusUpdate message
- the new AMF may acquire information of the PDU session in which the terminal is receiving a service from the network from the UE context delivered in operation 242 .
- the new AMF may acquire information such as the PDU session ID and the SMF's ID or the IP address of the SMF that managed the PDU session ID, and may perform a procedure of reactivating the PDU session through the SMF.
- the terminal notifies that the registered AMF has been changed to the new AMF, so that the terminal can continue to use the PDU session even after the new registration procedure.
- the new AMF selects an appropriate v-SMF from network B, which is a network to which it belongs, and selects the selected v- By sending the PDUSession_UpdateSMContext to the SMF through the SMF, the terminal notifies that the registered AMF is changed to the new AMF and informs that the new network, network B, will use the PDU session service through the v-SMF, and the v-SMF is By selecting v-UPF for servicing the PDU session, setting for servicing the PDU session in a new network can be performed.
- the v-SMF attempts to send the information of v-SMF and v-UPF to the SMF in the SM context update request for the PDU session received from the AMF.
- the process of reactivating the PDU session as described above necessarily fails (operation 224).
- the new AMF acquires information that the old AMF is making an event subscription for the terminal from the UE context received in operation 242 .
- PCF ID and address information for event subscription to notify when policy is modified from PCF (Policy Control Function), or event subscription to notify when subscription information is modified from UDM (Unified Data Management) It acquires UDM ID and address information, and notifies that the AMF registered by the terminal has been changed to a new AMF, so that the service can be continuously received.
- PCF ID and address information for event subscription to notify when policy is modified from PCF (Policy Control Function) or event subscription to notify when subscription information is modified from UDM (Unified Data Management) It acquires UDM ID and address information, and notifies that the AMF registered by the terminal has been changed to a new AMF, so that the service can be continuously received.
- PCF Policy Control Function
- UDM Unified Data Management
- the registration procedure is delayed due to the procedure of modifying the SM context as in operation 224, which inevitably fails, and modifying the event subscription, or unnecessary operation is performed in a new network, thereby wasting resources.
- a method for eliminating such delay and resource waste will be dealt with in a later embodiment.
- the new AMF assigns a new 5G-GUTI value to the terminal and transfers the result of the registration of the terminal to the terminal (operation 225), and in response to this, the registration process is completed by performing registration complete (operation 203).
- the new AMF may complete the registration procedure by transmitting a registration accept message including a 5G-GUTI newly allocated to the terminal to the terminal, and receiving a registration complete message from the terminal.
- 3A and 3B are diagrams for explaining a procedure for a terminal to register a network in a newly moved communication network when a communication network to which a temporary ID of the terminal is allocated is an SNPN, according to an embodiment of the present disclosure.
- a temporary ID (eg, 5G-GUTI) may be allocated from the old AMF 340 (operation 341 ).
- Network B the terminal moves between Network A and Network B through network information (eg, PLMN ID, NID) broadcast from the RAN, or moves between different SNPNs or SNPN and PLMN It can be recognized that the movement between Accordingly, recognizing that handover is not supported, the terminal may operate as in the idle state (operation 301).
- the terminal transfers the registration request message to the Network B, which is the mobile network, to the RAN 310 through an RRC message (operation 302), and the RAN 310 selects the new AMF 320 to The registration request message may be transmitted (operation 312).
- the terminal creates the registration request message
- the 5G-GUTI allocated from the old AMF 340 and the NID of network A, which is the SNPN to which the 5G-GUTI is allocated are included in the registration request message, and the network A used Integrity protection can be applied to the registration request message by using the security key.
- the terminal may transmit a UE context transfer request message (eg, UEContextTransfer message) including a Registration request message received from the terminal to the old AMF in order to request the UE context.
- UEContextTransfer message eg, UEContextTransfer message
- an indication or a terminal to transmit only the Authentication-related UE context of the terminal An indication to deliver only the MM UE context including SUPI or an indication not to deliver the SM UE context may be included in the message of operation 322 (operation 321).
- the new AMF may separately include 5G-GUTI and NID information to quickly determine the UE context request to which the old AMF is transmitted.
- the Authentication-related UE context includes the SUPI of the terminal.
- Authentication-related UE context is a Routing indicator, ausf group ID, UDM group ID, PCF group ID, SUPI-unautheticatedindicator, GPSI, 5G-GUTI, PEI, Internal Group ID list, security-related information such as access type or security information It may further include at least one of.
- the old AMF that has received the UE context request performs authentication on the registration request message, and when it is correctly authenticated, the old AMF may transmit a response to the request together with the UE context to the new AMF (operation 343).
- the old AMF is an indication that only the authentication-related UE context including the SUPI of the terminal is to be delivered, or an indication that only the MM UE context including the SUPI of the terminal is delivered or the SM UE context is not delivered
- new AMF According to the request of the UE context, including only Authentication-related UE context including SUPI, including only MM UE context including SUPI, or excluding SM UE context, can be delivered to the new AMF (320), and also the old AMF is event subscription One piece of information (and/or association information with another NF) may also be delivered to the new AMF while excluding it.
- the old AMF includes an Authentication-related UE context or MM UE context including the SUPI of the terminal, and excludes SM UE context and/or event subscription information, UE context transfer response message (eg, UEContextTransfer Response) message) to the new AMF.
- UE context transfer response message eg, UEContextTransfer Response
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the terminal, in which the SM UE context and/or event subscription information is excluded, to the new AMF.
- the old AMF in operation 343 is In the UE context, only the Authentication-related UE context including SUPI, or only the MM UE context including SUPI, or SM UE context is excluded and delivered to the new AMF 320, and the old AMF event subscription information (and / Or, association information with other NFs) may be delivered to the new AMF while also excluded.
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the UE, excluding the SM UE context and/or event subscription information, to the new AMF.
- a preset condition eg, the new AMF that the old AMF requested the UE context belongs to a network different from itself, and at least one of its own network or the network to which the new AMF belongs. is recognized as the SNPN
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the UE, excluding the SM UE context and/or event subscription information, to the new AMF.
- the new AMF may not perform a separate authentication procedure for the terminal, and may share a security context for secure message transmission and reception between the terminal and the new AMF.
- the new AMF may inform the old AMF that the UE context is successfully transferred, and that the terminal is registered through the new AMF (operation 324).
- the new AMF may transmit a registration status update message (eg, RegistrationStatusUpdate message) to the old AMF in order to inform that the UE context is successfully transferred, and that the terminal is registered through the new AMF.
- a registration status update message eg, RegistrationStatusUpdate message
- the new AMF may send an indication that all PDU sessions for the terminal may be released. Even if the terminal acquires information such as the list of PDU session IDs served by the terminal and the ID and address of the SMF that manages each in operation 343, the new AMF includes a list of all PDU session IDs, or all PDUs
- the indication that the session may be released can be delivered to the old AMF, and the old AMF 340 that has received the indication that the list of PDU sessions to be released or that all PDU sessions may be released is to release the PDU session to the corresponding SMFs. may be requested (act 344).
- the operation of requesting a local release from each SMF for the PDU session in the SM context of the terminal in operation 344 may be performed after receiving the list or indication of the PDU session in operation 324, but depending on the embodiment, operation 342 It may be executed immediately after deciding not to send the UE's SM context to the new AMF.
- the new AMF assigns a new 5G-GUTI value to the terminal and transfers the result of the registration of the terminal to the terminal (operation 325), and in response to this, the registration process is completed by performing registration complete (operation 303).
- the new AMF may complete the registration procedure by transmitting a registration accept message including a 5G-GUTI newly allocated to the terminal to the terminal, and receiving a registration complete message from the terminal.
- FIG. 4 is a diagram for explaining a procedure for a terminal to register a network in a newly moved communication network when a communication network to which a temporary ID of the terminal is allocated is an SNPN, according to another embodiment of the present disclosure.
- a temporary ID (eg, 5G-GUTI) may be allocated from the old AMF 340 (operation 441).
- Network B the terminal moves between Network A and Network B through network information (eg, PLMN ID, NID) broadcast from the RAN, or moves between different SNPNs or SNPN and PLMN If it is recognized that the movement is between the two, it recognizes that handover is not supported accordingly, and the terminal may operate as in the idle state (operation 401).
- network information eg, PLMN ID, NID
- the terminal transfers a registration request message to the network B, which is the mobile network, to the RAN 410 through an RRC message (operation 402), and the RAN 410 selects the new AMF 420,
- the registration request message may be transmitted (operation 412).
- the terminal creates the registration request message
- the 5G-GUTI allocated from the old AMF 440 and the NID of network A, which is the SNPN allocated with the 5G-GUTI, are included in the registration request message, and the network A used Integrity protection can be applied to the registration request message by using the security key.
- the new AMF that has received the registration request message knows that access is possible because there is an interface between the old AMF 440 based on the GUAMI and NID information obtained through 5G-GUTI included in the registration request message, Including the registration request message received from the terminal, the UE context for the corresponding terminal may be requested from the old AMF (operation 421).
- the terminal may transmit a UE context transfer request message (eg, UEContextTransfer message) including a Registration request message received from the terminal to the old AMF in order to request the UE context.
- the new AMF may separately include 5G-GUTI and NID information to quickly determine the UE context request to which the old AMF is delivered.
- the old AMF that has received the UE context request performs authentication on the registration request message, and when it is correctly authenticated, it may transmit a response to the request together with the UE context to the new AMF (operation 442).
- the new AMF receiving the UE context recognizes that its own network and the network to which 5G-GUTI is assigned to the terminal are different networks, and if it recognizes that it or the old AMF is in the SNPN type network, the received terminal's
- the event subscription information (and/or association information with other NFs) of all SM contexts and old AMFs may be deleted (operation 422).
- the new AMF may delete the SM UE context and/or event subscription information.
- the new AMF may not perform a separate authentication procedure for the terminal, and a security context can be shared for secure message transmission and reception between the terminal and the new AMF.
- a security context can be shared for secure message transmission and reception between the terminal and the new AMF.
- the UE context is successfully transferred to inform the old AMF that the UE is registered through the new AMF (operation 424).
- the new AMF may transmit a registration status update message (eg, RegistrationStatusUpdate message) to the old AMF in order to inform that the UE context is successfully transferred, and that the terminal is registered through the new AMF.
- a registration status update message eg, RegistrationStatusUpdate message
- the new AMF may send an indication that all PDU sessions for the terminal may be released.
- the new AMF includes a list of all PDU session IDs based on information such as the list of PDU session IDs obtained in step 442 and the ID and address of the SMF that manages each, or An indication that all PDU sessions may be released may be delivered to the old AMF together with, for example, a registration status update message.
- the old AMF 440 may request the corresponding SMFs to release the corresponding PDU session (operation 443).
- the new AMF assigns a new 5G-GUTI value to the terminal and transfers the result of the registration of the terminal to the terminal (operation 425), and in response to this, the registration process is completed by performing registration complete (operation 403).
- the new AMF may complete the registration procedure by transmitting a registration accept message including a 5G-GUTI newly allocated to the terminal to the terminal, and receiving a registration complete message from the terminal.
- 5A and 5B are diagrams for explaining a procedure for a terminal to register a network with a newly moved SNPN when a communication network to which a temporary ID of the terminal is allocated is a PLMN, according to an embodiment of the present disclosure.
- a temporary ID (eg, 5G-GUTI) may be allocated from the old AMF 540 (operation 541 ).
- Network B which is an SNPN network
- the terminal moves between Network A and Network B through network information (eg, PLMN ID, NID) broadcast from the RAN, moving between different SNPNs or SNPN It can be recognized that it is a movement between and PLMN. Accordingly, recognizing that handover is not supported, the terminal may operate as in the idle state (operation 501).
- the terminal transfers a registration request message to the network B, which is the mobile network, to the RAN 510 through an RRC message (operation 502), and the RAN 510 selects the new AMF 520 and The registration request message may be transmitted (operation 512).
- the terminal creates the registration request message
- the 5G-GUTI allocated from the old AMF 540 is included in the registration request message and integrity protection is applied to the registration request message using the security key used in network A. can do.
- the new AMF that has received the registration request message When it is identified that the new AMF that has received the registration request message has only the GUAMI acquired through 5G-GUTI included in the registration request message and there is no NID information, it is connected to the old AMF 540 in the public network (PLMN).
- PLMN public network
- the terminal When it is found that access is possible because there is an interface in the terminal, it can request the UE context for the corresponding terminal from the old AMF including the registration request message received from the terminal (operation 522).
- the terminal may transmit a UE context transfer request message (eg, UEContextTransfer message) including a Registration request message received from the terminal to the old AMF in order to request the UE context.
- UEContextTransfer message eg, UEContextTransfer message
- the new AMF recognizes that its own network and the network to which 5G-GUTI is assigned to the terminal are different networks, and if at least one of its own network and the network of the old AMF is SNPN or a network to which 5G-GUTI is assigned If the new AMF is in the SNPN network while this PLMN, an indication to deliver only the authentication-related UE context of the terminal or an indication to deliver only the MM UE context including the SUPI of the terminal, or the SM UE context, an indication not to deliver the above operation It may be included in the message of 522 (operation 521).
- the new AMF may be delivered by separately including 5G-GUTI in order to quickly determine the UE context request to which the old AMF is delivered.
- the new AMF may separately transmit 5G-GUTI and information indicating no NID (no NID information) in order to quickly determine the UE context request to which the old AMF is transmitted.
- the old AMF having received the UE context request, authenticates the registration request message, and when it is correctly authenticated, it may transmit a response to the request together with the UE context to the new AMF (operation 543).
- the old AMF is an indication that only the authentication-related UE context including the SUPI of the terminal is to be delivered, or an indication that only the MM UE context including the SUPI of the terminal is delivered or the SM UE context is not delivered
- new AMF According to the request of the UE context, including only Authentication-related UE context including SUPI, including only MM UE context including SUPI, or excluding SM UE context, can be delivered to the new AMF (520), and also the old AMF is event subscription One piece of information (and/or association information with another NF) may also be delivered to the new AMF while excluding it.
- the old AMF includes an Authentication-related UE context or MM UE context including the SUPI of the terminal, and excludes SM UE context and/or event subscription information, UE context transfer response message (eg, UEContextTransfer Response) message) to the new AMF.
- UE context transfer response message eg, UEContextTransfer Response
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the terminal, in which the SM UE context and/or event subscription information is excluded, to the new AMF.
- the old AMF in step 543 can include only Authentication-related UE context including SUPI in the UE context, include only MM UE context including SUPI, or exclude SM UE context and deliver it to the new AMF 520, and also the information that the old AMF has event subscription ( and/or association information with other NFs) may also be transmitted to the new AMF.
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the UE, excluding the SM UE context and/or event subscription information, to the new AMF.
- a preset condition eg, the new AMF that the old AMF requested the UE context belongs to a network different from itself, and at least one of its own network or the network to which the new AMF belongs. is recognized as the SNPN
- the old AMF may transmit only the Authentication-related UE context or MM UE context including the SUPI of the UE, excluding the SM UE context and/or event subscription information, to the new AMF.
- the new AMF may not perform a separate authentication procedure for the terminal, and may share a security context for secure message transmission/reception between the terminal and the new AMF. (Act 523). Then, the new AMF may inform the old AMF that the UE context is successfully transferred, and that the terminal is registered through the new AMF (operation 524). In one embodiment, the new AMF may transmit a registration status update message (eg, RegistrationStatusUpdate message) to the old AMF in order to inform that the UE context is successfully transferred, and that the terminal is registered through the new AMF.
- a registration status update message eg, RegistrationStatusUpdate message
- the new AMF may send an indication that all PDU sessions for the terminal may be released. Even if the terminal acquires information such as the list of PDU session IDs served by the terminal and the ID and address of the SMF that manages each in operation 543, the new AMF includes a list of all PDU session IDs, or all PDUs
- the indication that the session may be released can be delivered to the old AMF, and the old AMF 540 that has received the indication that the list of PDU sessions to be released or that all PDU sessions may be released is to release the PDU session to the corresponding SMFs. may be requested (act 544).
- the operation of requesting a local release from each SMF for the PDU session in the SM context of the terminal in operation 544 may be performed after receiving the list or indication of the PDU session in operation 524, but depending on the embodiment, the operation 542, it may be executed immediately after deciding not to send the UE's SM context to the new AMF.
- the new AMF allocates a new 5G-GUTI value and transfers the result of the registration of the terminal to the terminal (operation 525), and in response to this, the registration process is completed by performing registration complete (operation 503).
- the new AMF may complete the registration procedure by transmitting a registration accept message including a 5G-GUTI newly allocated to the terminal to the terminal, and receiving a registration complete message from the terminal.
- FIG. 6 is a diagram for describing a procedure for a terminal to register a network with a newly moved SNPN when a communication network to which a temporary ID of the terminal is allocated is a PLMN, according to another embodiment of the present disclosure.
- a temporary ID (eg, 5G-GUTI) may be allocated from the old AMF 640 (operation 641 ).
- Network B the terminal moves between Network A and Network B through network information (eg, PLMN ID, NID) broadcast from the RAN, or moves between different SNPNs or SNPN and PLMN
- network information eg, PLMN ID, NID
- the terminal recognizes that handover is not supported accordingly, and the terminal may operate as in the idle state (operation 601).
- the terminal transfers the registration request message to the network B, which is the moving network, to the RAN 610 through an RRC message (operation 602), and the RAN 610 selects the new AMF 620 to The registration request message may be transmitted (operation 612).
- the terminal creates the registration request message
- the 5G-GUTI allocated from the old AMF 640 is included in the registration request message, and integrity protection is applied to the registration request message using the security key used in network A. can do.
- the new AMF Upon receiving the registration request message, the new AMF acquires the GUAMI through the 5G-GUTI included in the registration request message and identifies that the NID is not included in the registration request message. When it is found that access is possible because there is an interface between the , it can request the UE context for the corresponding terminal from the old AMF including the registration request message received from the terminal (621).
- the terminal may transmit a UE context transfer request message (eg, UEContextTransfer message) including a Registration request message received from the terminal to the old AMF in order to request the UE context.
- the new AMF may separately include 5G-GUTI and information indicating no NID (no NID information).
- the old AMF that has received the UE context request performs authentication on the registration request message, and when it is correctly authenticated, the old AMF may transmit a response to the request together with the UE context to the new AMF (operation 642).
- the new AMF receiving the UE context recognizes that its own network and the network to which 5G-GUTI is assigned to the terminal are different networks, and if at least one of its own network and the network of the old AMF is SNPN or 5G- If the network to which the GUTI is assigned is the PLMN while the new AMF is in the SNPN network, all SM contexts of the received terminal and the event subscription information (and/or association information with other NFs) of the old AMF may be deleted ( action 622).
- the new AMF may delete the SM UE context and/or event subscription information.
- the new AMF may not perform a separate authentication procedure for the terminal, and may share a security context for secure message transmission/reception between the terminal and the new AMF.
- the UE context may be successfully transferred to inform the old AMF that the UE has been registered through the new AMF (operation 624).
- the new AMF may transmit a registration status update message (eg, RegistrationStatusUpdate message) to the old AMF in order to inform that the UE context is successfully transferred, and that the terminal is registered through the new AMF.
- a registration status update message eg, RegistrationStatusUpdate message
- the new AMF may send an indication that all PDU sessions for the terminal may be released.
- the new AMF includes a list of all PDU session IDs based on the information such as the list of PDU session IDs obtained in step 642 and the ID and address of the SMF that manages each, or An indication that all PDU sessions may be released may be delivered to the old AMF together with, for example, a registration status update message.
- the old AMF 640 may request the corresponding SMFs to release the corresponding PDU session (operation 643).
- the new AMF assigns a new 5G-GUTI value to the terminal and transfers the result of the registration of the terminal to the terminal (operation 625), and in response to this, the registration process is completed by performing registration complete (operation 603).
- the new AMF may complete the registration procedure by transmitting a registration accept message including a 5G-GUTI newly allocated to the terminal to the terminal, and receiving a registration complete message from the terminal.
- FIG. 7 illustrates a method of a first AMF entity according to an embodiment of the present disclosure.
- the first AMF entity may correspond to the new AMF of the network B of FIGS. 2 to 6
- the second AMF entity may correspond to the old AMF of the network A of FIGS. 2 to 6
- the terminal may correspond to the UE of FIGS. 2 to 6
- the base station may correspond to the 5G-(R)AN of FIGS. 2 to 6 .
- the first AMF entity may receive a registration request message for the first network of the first AMF entity from the UE through the base station ( 7010 ).
- the registration request message reception operation may refer to, for example, the registration request message reception operation of FIGS. 2 to 6 .
- the first AMF entity may transmit a context request message for requesting context information for the terminal to the second AMF entity based on the registration request message ( 7020 ).
- the context request message transmission operation may refer to, for example, the UEContextTransfer message transmission operation of FIGS. 2 to 6 .
- the first AMF entity may receive a response message corresponding to the context request message from the second AMF entity ( 7030 ).
- the response message reception operation may refer to, for example, the UEContextTransfer Response message reception operation of FIGS. 2 to 6 .
- the registration request message may include temporary ID information of the terminal allocated by the second AMF.
- At least one of the first network of the first AMF entity or the second network of the second AMF entity may correspond to the SNPN.
- the response message may include at least a portion of the context information stored in the second AMF entity.
- the context information may include at least one of information for mobility management of the terminal, authentication-related context information, information for session management for a service provided to the terminal, or event subscription-related information for the terminal.
- the registration request message may include network ID information identifying the second network
- the context request message may include temporary ID information and network ID information. have.
- the context request message may include an indication requesting to transmit only authentication-related context information including the SUPI of the terminal, and the response message may include only authentication-related context information including the SUPI of the terminal.
- the first AMF entity when the response message includes information for session management for a service provided to the terminal and event subscription-related information for the terminal, the first AMF entity provides information for session management and the event subscription-related information. can be deleted.
- the first AMF entity may transmit a request to release all PDU sessions for the terminal to the second AMF entity.
- FIG. 8 illustrates a method of a second AMF entity according to an embodiment of the present disclosure.
- the first AMF entity may correspond to the new AMF of the network B of FIGS. 2 to 6
- the second AMF entity may correspond to the old AMF of the network A of FIGS. 2 to 6
- the terminal may correspond to the UE of FIGS. 2 to 6
- the base station may correspond to the 5G-(R)AN of FIGS. 2 to 6 .
- the second AMF entity may receive, from the first AMF entity, a context request message for requesting context information on the terminal that has transmitted the registration request message to the first AMF entity ( 8010 ).
- the context request message reception operation may refer to, for example, the UEContextTransfer message reception operation of FIGS. 2 to 6 .
- the second AMF entity may transmit a response message corresponding to the context request message to the first AMF entity (8020).
- the response message transmission operation may refer to, for example, the UEContextTransfer Response message transmission operation of FIGS. 2 to 6 .
- At least one of the first network of the first AMF entity or the second network of the second AMF entity may correspond to the SNPN.
- the response message may include at least a portion of the context information stored in the second AMF entity.
- the context information may include at least one of information for mobility management of the terminal, authentication-related context information, information for session management for a service provided to the terminal, or event subscription-related information for the terminal.
- the registration request message when the second network of the second AMF entity is SNPN, the registration request message includes network ID information for identifying the second network, and the context request message includes temporary ID information and network ID information of the terminal can do.
- the authentication-related message including the SUPI of the terminal in the response message may include the step of including only context information.
- the response message includes information for session management and Event subscription related information may not be included.
- the second AMF entity may receive, from the first AMF entity, a request for releasing all PDU sessions for the terminal.
- FIG. 9 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
- the terminal may include a transceiver 910 , a controller 920 , and a storage 930 .
- the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.
- the transceiver 910 may transmit/receive signals to and from other network entities.
- the transceiver 910 may receive, for example, system information from a base station, and may receive a synchronization signal or a reference signal.
- the controller 920 may control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the controller 920 may control the signal flow between blocks to perform the operations according to FIGS. 2 to 7 described above. Specifically, the controller 920 may control the operation proposed by the present invention to support UE mobility according to an embodiment of the present invention.
- the storage unit 930 may store at least one of information transmitted and received through the transceiver 910 and information generated through the control unit 920 .
- the storage unit 930 may store temporary ID information of the terminal, ID information of the network, and the like.
- FIG. 10 is a diagram illustrating a structure of a base station according to an embodiment of the present invention.
- the base station may include a transceiver 1010 , a control unit 1020 , and a storage unit 1030 .
- the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.
- the transceiver 1010 may transmit/receive signals to and from other network entities.
- the transceiver 1010 may transmit, for example, system information to the terminal, and may transmit a synchronization signal or a reference signal.
- the controller 1020 may control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the controller 1020 may control the signal flow between blocks to perform the operations according to FIGS. 2 to 7 described above. Specifically, the controller 1020 may control the operation proposed by the present invention to support UE mobility according to an embodiment of the present invention.
- the storage unit 1030 may store at least one of information transmitted and received through the transceiver 1010 and information generated through the control unit 1020 .
- the storage unit 1030 may store information/data/commands for performing the operations according to FIGS. 2 to 7 .
- FIG. 11 is a diagram illustrating the structure of a network entity according to an embodiment of the present invention.
- the network entity of FIG. 11 may be, for example, one of the AMF, SMF, UPF, UDM or AUSF entities of networks A and/or network B of FIGS. 1 to 7 .
- the network entity may include a transceiver 1110 , a control unit 1120 , and a storage unit 1130 .
- the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.
- the transceiver 1110 may transmit/receive a signal to/from another network entity.
- the transceiver 1110 may transmit/receive data and a request/response to/from another network entity, for example.
- the controller 1120 may control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the controller 1120 may control the signal flow between blocks to perform the operations according to FIGS. 2 to 7 described above. Specifically, the controller 1120 may control the operation proposed by the present invention to support UE mobility according to an embodiment of the present invention.
- the storage unit 1130 may store at least one of information transmitted/received through the transceiver 1110 and information generated through the control unit 1120 .
- the storage unit 1030 may store information/data/commands for performing the operations according to FIGS. 2 to 7 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (15)
- AMF (access and mobility management function) 엔티티의 방법에 있어서,SNPN (standalone non-public network)인 제1 네트워크로부터 제2 네트워크로 이동된 단말로부터, 네트워크 등록을 위한 등록 요청 메시지를 수신하는 단계 -상기 등록 요청 메시지는 상기 단말의 임시 ID (identifier) 정보 및 상기 임시 ID 정보를 할당한 상기 제1 네트워크의 네트워크 ID (NID) 정보를 포함함-;상기 임시 ID 정보 및 상기 NID 정보에 기초하여, 상기 제1 네트워크에 속하는 제1 AMF 엔티티를 식별하는 단계;상기 제1 AMF 엔티티로, 상기 단말의 컨텍스트 정보를 요청하는 요청 메시지를 전송하는 단계; 및상기 제1 AMF 엔티티로부터, 상기 컨텍스트 정보를 포함하는 응답 메시지를 수신하는 단계를 포함하는, 방법.
- 제1항에 있어서, 상기 방법은:상기 단말의 상기 제1 네트워크로부터 상기 제2 네트워크로 이동(mobility)이 SNPN 간 이동인 경우, 릴리즈 될 PDU(protocol data unit) 세션 ID의 리스트를 포함하는 등록 상태 업데이트 메시지를 상기 제1 AMF 엔티티로 전송하는 단계를 더 포함하는, 방법.
- 제2항에 있어서,상기 PDU 세션 ID의 리스트는 상기 컨텍스트 정보로부터 획득되는, 방법.
- 제2항에 있어서, 상기 방법은:상기 PDU 세션 ID의 리스트와 연관된 SM (session management) 컨텍스트 정보를 상기 컨텍스트 정보로부터 삭제하는 단계를 더 포함하는, 방법.
- 제2항에 있어서,상기 제1 AMF 엔티티는 상기 제1 네트워크에 속하는 제1 SMF(session management function) 엔티티에게 상기 PDU 세션 ID의 리스트와 연관된 SM (session management) 컨텍스트 정보를 릴리즈하도록 요청하는, 방법.
- 제1항에 있어서,상기 임시 ID 정보는 5G-GUTI(globally unique temporary identifier)인, 방법.
- 제1항에 있어서,상기 제1 AMF 엔티티는 상기 등록 요청 메시지를 수신한 기지국에 의해 선택되는, 방법.
- 제1항에 있어서, 상기 방법은:상기 제2 네트워크에 의해 새로 할당된 상기 단말의 임시 ID 정보를 포함하는 등록 승인 메시지를 상기 단말로 전송하는 단계를 더 포함하는, 방법.
- AMF (access and mobility management function)에 있어서,트랜시버; 및상기 트랜시버에 연결된 제어부를 포함하며, 상기 제어부는:SNPN (standalone non-public network)인 제1 네트워크로부터 제2 네트워크로 이동된 단말로부터, 네트워크 등록을 위한 등록 요청 메시지를 수신하고 -상기 등록 요청 메시지는 상기 단말의 임시 ID (identifier) 정보 및 상기 임시 ID 정보를 할당한 상기 제1 네트워크의 네트워크 ID (NID) 정보를 포함함-,상기 임시 ID 정보 및 상기 NID 정보에 기초하여, 상기 제1 네트워크에 속하는 제1 AMF 엔티티를 식별하고,상기 제1 AMF 엔티티로, 상기 단말의 컨텍스트 정보를 요청하는 요청 메시지를 전송하고,상기 제1 AMF 엔티티로부터, 상기 컨텍스트 정보를 포함하는 응답 메시지를 수신하도록 구성되는, AMF 엔티티.
- 제9항에 있어서, 상기 제어부는:상기 단말의 상기 제1 네트워크로부터 상기 제2 네트워크로 이동(mobility)이 SNPN 간 이동인 경우, 릴리즈 될 PDU(protocol data unit) 세션 ID의 리스트를 포함하는 등록 상태 업데이트 메시지를 상기 제1 AMF 엔티티로 전송하도록 더 구성되는, AMF 엔티티.
- 제10항에 있어서,상기 PDU 세션 ID의 리스트는 상기 컨텍스트 정보로부터 획득되는, AMF 엔티티.
- 제10항에 있어서, 상기 제어부는:상기 PDU 세션 ID의 리스트와 연관된 SM (session management) 컨텍스트 정보를 상기 컨텍스트 정보로부터 삭제하도록 더 구성되는, AMF 엔티티.
- 제10항에 있어서,상기 제1 AMF 엔티티는 상기 제1 네트워크에 속하는 제1 SMF(session management function) 엔티티에게 상기 PDU 세션 ID의 리스트와 연관된 SM (session management) 컨텍스트 정보를 릴리즈하도록 요청하는, AMF 엔티티.
- 제1항에 있어서,상기 임시 ID 정보는 5G-GUTI(globally unique temporary identifier)인, AMF 엔티티.
- 제1항에 있어서,상기 제1 AMF 엔티티는 상기 등록 요청 메시지를 수신한 기지국에 의해 선택되는, AMF 엔티티.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22799143.7A EP4319296A1 (en) | 2021-05-07 | 2022-05-06 | Method and device for supporting ue mobility between networks |
CN202280033393.9A CN117280754A (zh) | 2021-05-07 | 2022-05-06 | 用于支持在网络之间的ue移动性的方法和设备 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2021-0059524 | 2021-05-07 | ||
KR1020210059524A KR20220152049A (ko) | 2021-05-07 | 2021-05-07 | 망간의 UE mobility를 지원하는 방법 및 장치 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022235100A1 true WO2022235100A1 (ko) | 2022-11-10 |
Family
ID=83932327
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/006469 WO2022235100A1 (ko) | 2021-05-07 | 2022-05-06 | 망간의 단말 이동성을 지원하는 방법 및 장치 |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP4319296A1 (ko) |
KR (1) | KR20220152049A (ko) |
CN (1) | CN117280754A (ko) |
WO (1) | WO2022235100A1 (ko) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115955684A (zh) * | 2022-12-13 | 2023-04-11 | 武汉博易讯信息科技有限公司 | 一种4g和5g交互场景的信令关联方法及系统 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20210038352A (ko) * | 2019-09-30 | 2021-04-07 | 삼성전자주식회사 | Ue의 이동성 절차 처리 방법 및 ue |
-
2021
- 2021-05-07 KR KR1020210059524A patent/KR20220152049A/ko active Search and Examination
-
2022
- 2022-05-06 EP EP22799143.7A patent/EP4319296A1/en active Pending
- 2022-05-06 WO PCT/KR2022/006469 patent/WO2022235100A1/ko active Application Filing
- 2022-05-06 CN CN202280033393.9A patent/CN117280754A/zh active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20210038352A (ko) * | 2019-09-30 | 2021-04-07 | 삼성전자주식회사 | Ue의 이동성 절차 처리 방법 및 ue |
Non-Patent Citations (4)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17)", 3GPP STANDARD; 3GPP TS 23.502 V17.0.0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 31 March 2021 (2021-03-31), pages 1 - 646, XP052000251 * |
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of Non-Public Networks (NPN) (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-07 V17.0.0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 31 March 2021 (2021-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 248, XP052000256 * |
OPPO: "Onboarding indication over RRC and NAS", 3GPP TSG SA WG2 MEETING #143-E; S2-2100690, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 18 February 2021 (2021-02-18), Electronic meeting; 20210224 - 20210309, XP052173015 * |
QUALCOMM INCORPORATED, ERICSSON: "SNPN selection for access to SNPNs using credentials from an entity separate from the SNPN", 3GPP TSG CT WG1 MEETING #129-E; C1-212072, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 11 April 2021 (2021-04-11), Electronic meeting; 20210419 - 20210423, XP051994850 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115955684A (zh) * | 2022-12-13 | 2023-04-11 | 武汉博易讯信息科技有限公司 | 一种4g和5g交互场景的信令关联方法及系统 |
CN115955684B (zh) * | 2022-12-13 | 2023-08-11 | 武汉博易讯信息科技有限公司 | 一种4g和5g交互场景的信令关联方法及系统 |
Also Published As
Publication number | Publication date |
---|---|
KR20220152049A (ko) | 2022-11-15 |
CN117280754A (zh) | 2023-12-22 |
EP4319296A1 (en) | 2024-02-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020071689A1 (ko) | 사설 이동통신망 및 사업자 이동통신망 접속을 지원하는 장치 및 방법 | |
WO2018230941A1 (ko) | 단말의 망 접속 방법 및 이동성 지원과 데이터 전달 방법 및 장치 | |
WO2022216049A1 (en) | Method and apparatus for configuring temporary user equipment (ue) external identifier in wireless communication system | |
WO2022235100A1 (ko) | 망간의 단말 이동성을 지원하는 방법 및 장치 | |
WO2021141288A1 (ko) | 단말의 사설망 접속 제어 방법 | |
WO2022225335A1 (ko) | 이동 통신 시스템에서 단말 간 연결을 통한 네트워크 접속 요청의 인증을 위한 방법 및 장치 | |
WO2023055101A1 (en) | Method and apparatus for network slice admission control for interworking with epc in wireless network | |
WO2022177354A1 (en) | Method and device for continuity of modem service | |
WO2022173222A1 (en) | Method and apparatus for supporting multicast service in wireless communication system | |
EP4275366A1 (en) | Method and apparatus for improvements in and relating to management of a disaster condition in a mobile communication system | |
WO2023075374A1 (en) | Method and device for exemption from network slice bitrate limitations in wireless communication system | |
WO2023214773A1 (ko) | 무선 통신 시스템에서 단말의 인증을 지원하는 방법 및 장치 | |
WO2023075354A1 (en) | Method and device for supporting alternative network slice in wireless communication system | |
WO2023200260A1 (en) | Method and apparatus for handling pemc switchover in wireless communication system | |
WO2023136611A1 (en) | Methods and systems for handling of edge enabler client registration during service continuity | |
WO2023080748A1 (en) | Method and device for supporting efficient network slicing in wireless communication system | |
WO2023080751A1 (en) | Improvements in and relating to prose | |
WO2022240191A1 (en) | Method and apparatus for proximity services in a telecommunication network | |
WO2024106960A1 (en) | Method and apparatus for using radio resources during emergency session in communication system | |
WO2023219344A1 (en) | Method and apparatus to optimize conditional pscell addition and change in wireless communication systems | |
WO2023146359A1 (ko) | 에지 컴퓨팅 시스템을 위한 통신 방법 및 장치 | |
WO2023014170A1 (ko) | 무선 통신 시스템에서 로밍 단말의 데이터를 송신하기 위한 방법 및 장치 | |
WO2024005535A1 (en) | Methods and user equipment for managing protocol data unit session | |
WO2023191389A1 (ko) | 무선 통신 시스템에서 브로드캐스트 서비스를 제공하는 방법 및 장치 | |
WO2022231210A1 (en) | A method and apparatus for location management in a wireless network |
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: 22799143 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022799143 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022799143 Country of ref document: EP Effective date: 20231023 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280033393.9 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18559547 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |