KR20230115175A - Method and apparatus for supporting emergency services and priority services in wireless communication system - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data rates. This disclosure provides intelligent services based on 5G communication technology and IoT-related technologies (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and safety related services, etc.) ) can be applied. A method for efficiently supporting an emergency service and a priority service in a wireless communication system according to an embodiment of the present disclosure is proposed.

Description

Method and apparatus for supporting emergency service and priority service in wireless communication system

The present disclosure relates to a method and apparatus for supporting emergency service and priority service in a wireless communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speed and new services. It can also be implemented in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called a system after 5G communication (Beyond 5G), in order to achieve transmission speed that is 50 times faster than 5G mobile communication technology and ultra-low latency reduced to 1/10, tera Implementations in Terahertz bands (eg, such as the 3 Terahertz (3 THz) band at 95 GHz) are being considered.

In the early days of 5G mobile communication technology, there was a need for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). Beamforming and Massive MIMO to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, with the goal of satisfying service support and performance requirements, and efficient use of ultra-high frequency resources Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation for slot format, initial access technology to support multi-beam transmission and broadband, BWP (Band-Width Part) definition and operation, large capacity 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, and dedicated services specialized for specific services Standardization of network slicing that provides a network has been progressed.

Currently, discussions are underway to improve and enhance performance of the initial 5G mobile communication technology in consideration of the services that the 5G mobile communication technology was intended to support. NR-U (New Radio Unlicensed) for the purpose of system operation that meets various regulatory requirements in unlicensed bands ), NR terminal low power consumption technology (UE Power Saving), non-terrestrial network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization of the technology is in progress.

In addition, IAB (Industrial Internet of Things (IIoT)), which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, to support new services through linkage and convergence with other industries (Industrial Internet of Things, IIoT) Integrated Access and Backhaul), Mobility Enhancement technology including conditional handover and Dual Active Protocol Stack (DAPS) handover, 2-step random access that simplifies the random access procedure (2-step RACH for Standardization in the field of air interface architecture/protocol for technologies such as NR) is also in progress, and 5G baselines for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies Standardization in the field of system architecture/service is also in progress for an architecture (eg, service based architecture, service based interface), mobile edge computing (MEC) for which services are provided based on the location of a terminal, and the like.

When such a 5G mobile communication system is commercialized, the explosively increasing number of connected devices will be connected to the communication network, and accordingly, it is expected that the function and performance enhancement of the 5G mobile communication system and the integrated operation of connected devices will be required. To this end, augmented reality (AR), virtual reality (VR), mixed reality (MR), etc. to efficiently support extended reality (XR), artificial intelligence (AI) , AI) and machine learning (ML), new research on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication will be conducted.

In addition, the development of such a 5G mobile communication system is a new waveform, Full Dimensional MIMO (FD-MIMO), and Array Antenna for guaranteeing coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technologies such as large scale antennas, metamaterial-based lenses and antennas to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), RIS ( Reconfigurable Intelligent Surface) technology, as well as full duplex technology to improve frequency efficiency and system network of 6G mobile communication technology, satellite, and AI (Artificial Intelligence) are utilized from the design stage and end-to-end (End-to-End) -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI-supported functions and next-generation distributed computing technology that realizes complex services beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources could be the basis for

An embodiment of the present disclosure provides a method and apparatus for supporting emergency service and priority service in a wireless communication system.

A method for providing an emergency service of an access and mobility management function (AMF) in a wireless communication system according to an embodiment of the present disclosure includes receiving an N2 message including an N2 parameter and a registration request from a base station; and when the request type in the registration request is a value indicating emergency registration, performing a user equipment (UE) registration procedure without performing an NSAC procedure and an NSSAA procedure.

According to an embodiment of the present disclosure, a method and apparatus for supporting emergency service and priority service in a wireless communication system may be provided.

1 is a diagram illustrating a network structure (or network architecture) and interfaces of a 5G system according to an embodiment of the present disclosure.
2 shows a terminal registration procedure for an emergency service according to an embodiment.
3 illustrates a method of notifying an AMF and a UE in a UE registration procedure when MPS subscription information or MCX subscription information is changed according to an embodiment.
4 illustrates a method of notifying an AMF and a UE in a UE configuration update procedure when MPS subscription information or MCX subscription information is changed according to an embodiment.
5 illustrates a method for exempting NSSAA in a network registration procedure of a terminal using an MPS or MCX according to an embodiment.
6 illustrates a method in which SMF or PCF notifies AMF and UE of MPS invocation in an MPS invocation procedure according to an embodiment.
7 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.
8 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
9 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
10 is a diagram illustrating a method of finding out whether a new AMF subscribes to an MPS, MCX, or MPS/MCX in a network registration procedure of a terminal according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary description.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is given to the same or corresponding component.

Advantages and features of the present disclosure, and methods of achieving them, will become clear with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, only the present embodiments make the disclosure of the present disclosure complete, and common knowledge in the art to which the present disclosure belongs. It is provided to completely inform the person who has the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can 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, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, 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 possible for the functions mentioned in the blocks to occur out of order. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~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. However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, as an example, '~unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card. Also, in the embodiment, '~ unit' may include one or more processors.

In describing the embodiments of the present disclosure, New Radio (NR), a radio access network on the 5G mobile communication standard specified by the 3rd Generation Partnership Project (3GPP), a mobile communication standardization organization, and the packet core 5G System, or 5G, which is a core network Core Network, or NG Core (Next Generation Core) is the main target, but the main gist of the present disclosure is applied with slight modifications to other communication systems having similar technical backgrounds without significantly departing from the scope of the present disclosure. It is possible, and this will be possible with the judgment of a person skilled in the technical field of the present disclosure.

For convenience of description below, some terms and names defined in the 3GPP standards (5G, NR, LTE, or similar system standards) may be used. However, the present disclosure is not limited by terms and names, and may be equally applied to systems conforming to other standards.

In addition, a term used in the following description for identifying a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network entities, and various identifications Terms referring to information are illustrated for convenience of description. Therefore, it is not limited to the terms used in this disclosure, and other terms that refer to objects having equivalent technical meanings may be used.

In the 5G system, when a UE registers a network, it transmits identifier information about network slices that the UE wants to request, that is, Requested S-NSSAIs (Requested Single-Network Slice Selection Assistance Informations) to an access and mobility management function (AMF). . AMF provides information (Allowed NSSAI) on network slices that can be used by the UE to the UE in consideration of the Requested S-NSSAIs and subscriber information. Even if the UE does not provide the above-described identifier information on the slices to be requested, the AMF may provide the UE with Allowed NSSAI. At this time, Allowed NSSAI may include information on default configured slices (Default Configured NSSAIs) and information on slices set to default among subscription slices included in terminal subscriber information (ie Default Subscribed S-NSSAIs). .

If no slice can be included in the Allowed NSSAI (for example, if the Default Configured NSSAI and Default Subscribed S-NSSAIs are not available or unavailable), the AMF provides a cause code indicating the reason for refusal to register that there is no available slice and Together, it transmits a network registration rejection message to the terminal.

Meanwhile, when a certain slice is to be included in the allowed NSSAI of the UE, a Network Slice Admission Control (NSAC) procedure and a Network Slice-Specific Authentication and Authorization (NSSAA) procedure for the corresponding slice may be performed. In the NSAC procedure, it is determined whether to allow the corresponding slice based on the number of terminals currently registered in a specific slice and the maximum number of registered terminals allowed in the slice (ie, determining whether the slice is included in the Allowed NSSAI). In the NSSAA procedure, an authentication procedure is performed with AAA-S, which is a server that performs authentication for a corresponding slice, through NSSAAF (NSSAA Function) based on credential information of a UE for a corresponding slice. In the case of a slice that requires NSAC and NSSAA procedures, the slice can be included in Allowed NSSAI only when both procedures succeed.

Emergency services refer to a specific service provided to a terminal in an emergency situation, for example, an emergency call service. When registering a network, the terminal may include a parameter indicating registration for emergency service in the registration request message. A terminal performing registration for emergency service does not include information about a desired network slice in a registration request message. The AMF supporting the emergency service stores the slice and data network name (ie, Data Network Name, DNN) for the emergency service as configuration information. When emergency services are provided to the UE, the AMF provides the emergency services to the UE through the corresponding slice and DNN. At this time, the slice is not included in the Allowed NSSAI transmitted to the terminal. Also, a terminal registered for emergency service cannot use a slice other than a slice for emergency service.

A UE performing registration for emergency service may determine that the AMF rejects registration when no slice is included in the Allowed NSSAI even though slices other than the slice for emergency service do not need to be allowed.

An embodiment of the present disclosure is to prevent such a situation, and even if AMF does not include any slice in Allowed NSSAI for a terminal performing registration for emergency service, a method for preventing registration rejection due to this, and provide the device.

If a slice unrelated to the emergency service is included in the Allowed NSSAI for the terminal that has requested registration for the emergency service, the terminal determines that the slice can be used and can request a session through the corresponding slice. However, sessions through other slices and/or DNNs other than the emergency slice and emergency DNN are not allowed to terminals registered for emergency service. Accordingly, when a slice unrelated to emergency service is included in the allowed NSSAI, an unnecessary UE session request may occur. In addition, a terminal performing registration for emergency service includes some slices (eg, Default Configured NSSAI or Default Subscribed NSSAIs) in Allowed NSSAI, even though other slices need not be allowed other than the slice for emergency service. NSAC or NSSAA procedures may be performed to do so. This operation causes unnecessary signaling load on the control plane.

An embodiment of the present disclosure is to prevent such a situation, and provides a method and apparatus for reducing unnecessary signaling in the case of a terminal performing registration for an emergency service.

On the other hand, MPS (Multimedia Priority Service) is a service that allows users defined as service users (for example, government officials, etc.) to preferentially access mobile communication system resources. In addition, MCX (ie, Mission Critical Service) allows users belonging to a mission critical organization to send mission critical applications (eg, mission critical push to talk (MCPTT), mission critical video (MCVideo), mission critical data (MCData), etc.) ) is a service that allows priority access to system resources.

When the terminal needs access to the 5G system, it performs an assess barring check on whether the access is allowed. When the network access stratum (NAS) layer of the terminal detects an access request from a higher layer, the NAS layer classifies the corresponding access into one or more access identities and one access category. At this time, the NAS layer determines an access identity and an access category by referring to a UE profile including a reason for access, types of service requested, and user equipment (UE) configuration information. Then, the NAS layer transfers the determined access identity and access category to the lower protocol layer. The lower protocol layer of the terminal performs access barring check based on the received access identity and access category.

The access identity value corresponding to the MPS or MCX is valid for the terminal based on the UE profile information (access identity information usable in the home network exists in the USIM) or the MPS-related subscriber information or MCX-related subscriber information received from the AMF. judge whether Specifically, when the terminal is roaming, or when the terminal is not roaming, access identity information corresponding to MPS or MCX in the home network is not set in the USIM, the terminal receives MPS-related subscriber information or MCX received from AMF Based on the relevant subscriber information, it is determined whether the Access Identity value corresponding to MPS or MCX is valid for the terminal.

When the UE performs network access corresponding to MPS or MCX in the network registration procedure, the establishment cause for the Radio Resource Control (RRC) layer included in the message transmitted to the base station (Radio Access Network (RAN) node) is assigned priority service Set to a value representing (MPS or MCX). When the establishment cause value is a value indicating priority service, the base station transmits the message to the AMF including the establishment cause. When the establishment cause represents priority services (that is, when the establishment cause includes a value or Information Element (IE) representing priority services), AMF performs priority processing in consideration of this. The terminal may include a value indicating priority service or IE in the establishment cause only when an access identity value corresponding to MPS or MCX is set.

At this time, in a situation where a general terminal not using MPS or MCX is roaming or access identity information corresponding to MPS or MCX is not set in terminal configuration information (eg, USIM), UDM (user data management ), MPS-related subscriber information or MCX-related subscriber information may be added to the subscriber information for the corresponding terminal. Since the corresponding terminal does not know whether subscriber information has been updated prior to network registration, when registering the network for the first time after changing MPS-related subscriber information and MCX-related subscriber information, a value indicating priority service or an IE cannot be included in the establishment cause. Since AMF does not know that it is a terminal using MPS or MCX, it does not perform preferential processing of the registration request message of the terminal (ie, preferential processing of messages from the terminal when the establishment cause indicates MPS or MCX). don't In addition, when the AMF receives an establishment cause indicating MPS or MCX, it treats request slices as an exception to the NSAC procedure, but when it does not receive an establishment cause for MPS or MCX, the NSAC procedure for request slices Some slices may be rejected because exceptions cannot be processed, or a registration request itself may be rejected. Therefore, when MPS-related subscriber information or MCX-related subscriber information is changed, a method for notifying the UE of this is required.

In the 5G system, even for a general terminal without MPS-related subscriber information, the AMF can request the PCF (policy control function) to use the MPS service. However, even in this case, it is necessary to inform the corresponding terminal that the access identity corresponding to the MPS is valid and that the corresponding access identity should be used. Otherwise, when a corresponding terminal performs re-registration due to mobility or the like, a registration rejection situation as mentioned above may occur. Therefore, when the MPS service is activated, a method for notifying the UE of this is required.

On the other hand, in the 5G system, when MPS-related subscriber information or MCX-related subscriber information exists (ie, when the corresponding terminal is subscribed to MPS and MCX, respectively), the message received from the corresponding terminal is preferentially processed (eg, , including headers for priority processing in communication messages between network functions of the control plane, NSSAA exemption, NSAC exemption, etc.) may be performed. This is called subscriber information-based preferential service provision.

Finally, there may be cases in which registration for MPS or MCX is rejected due to the NSSAA procedure. Therefore, by sending the 3 ^rd party server (authentication, authorization, and accounting server, AAA-S) or NSSAAF that performs the NSSAA procedure a parameter notifying that the registration is for MPS or MCX, AAA-S or NSSAAF uses MPS or MCX. In the case of a slice authentication request in the registration process for authentication, authentication must not be rejected even if there is no credential.

In one embodiment of the present disclosure, in the case of registration for emergency service, a method and apparatus for preventing the AMF from rejecting registration even if no slice is included in the Allowed NSSAI are provided.

In addition, in an embodiment of the present disclosure, in case of registration for emergency service, a method for not providing slice information unrelated to emergency service to a terminal without proceeding with a slice-related procedure for slices unrelated to emergency service; and provide the device. Specifically, in the registration accept message delivered to the UE, 1) Allowed NSSAI is not provided, 2) Allowed NSSAI includes identifier information of a slice used for emergency service, or 3) Allowed NSSAI includes information agreed upon with the UE. Predefined slice identifier information indicating emergency registration may be included.

In addition, in an embodiment of the present disclosure, when MPS-related subscriber information or MCX-related subscriber information is changed, a method and apparatus capable of notifying the UE of this change are provided. Furthermore, in the case of a terminal using MPS and / or MCX in a registration procedure, a method and apparatus for exempting NSSAA are provided.

According to an embodiment of the present disclosure, a situation in which a terminal registering for an emergency service in a wireless communication system is rejected due to a situation in which there is no allowed slice can be prevented, and unnecessary network signaling can be prevented from occurring.

In addition, according to an embodiment of the present disclosure, when MPS-related subscriber information or MCX-related subscriber information is changed in a wireless communication system, it is possible to perform an appropriate operation by notifying the terminal and the AMF. Furthermore, in the case of a terminal using MPS and/or MCX in a registration procedure of a wireless communication system, NSSAA may be exempted.

1 is a diagram illustrating a network structure (or network architecture) and interfaces of a 5G system according to an embodiment of the present disclosure.

Referring to FIG. 1, the network structure of a 5G system is UE (User Equipment), (R) AN (Radio Access Network), AMF (Access and Mobility Management Function), SMF (Session Management Function), UPF (User Plane Function) , DN(Data Network), NSSF(Network Slice Selection Function), NEF(Network Exposure Function), AUSF(Authentication Server Function), NRF(Network Repository Function), PCF(Policy Control Function), UDM(Unified Data Management), AF (Application Function), etc. may be included.

Here, UE may mean a terminal. 5G-RAN means a base station that provides a wireless communication function to a terminal. In Figure 1, it is shown as (R) AN. AMF manages the mobility of the terminal. SMF manages the Packet Data Network connection provided to the terminal. This connection is called a PDU (protocol data unit) Session. UPF serves as a gateway to deliver packets transmitted and received by UEs. UPF is connected to the Data Network (DN) and plays a role in delivering data packets generated by the 5G system to the external Data Network. can do.

NSSF performs a function of selecting a Network Slice Instance provided to the UE. NEF can access information that manages the terminal in the 5G network, so it can subscribe to the Mobility Management event of the corresponding terminal, subscribe to the Session Management event of the corresponding terminal, request for session-related information, set the charging information of the corresponding terminal, and It is connected to the 5G core network NFs (Network Functions), such as PDU session policy change request for the terminal, and plays a role in delivering information about the terminal to the corresponding NFs or reporting information about the terminal to the outside. AUSF performs terminal authentication in 3GPP access networks and non-3GPP access networks. NRF performs the function of discovering NF. The PCF applies the mobile communication service provider's service policy, billing policy, and PDU session policy to the terminal. UDM stores and manages data such as subscriber data and policy control data. AF can use the services and functions provided by the 5G network through NEF.

Furthermore, although not shown in FIG. 1, the network of the 5G system may further include other network functions (NFs). For example, a Unified Data Repository (UDR) that stores various function data such as PCF data, UDM data, and NEF data may be further included.

In the 3GPP system, a conceptual link connecting NFs in the 5G system is defined as a reference point. The following are reference points included in the 5G system architecture.

- N1: Reference point between UE and AMF

- N2: Reference point between (R)AN and AMF

- N3: Reference point between (R)AN and UPF

- N4: Reference point between SMF and UPF

- N5: Reference point between PCF and AF

- N6: Reference point between UPF and DN

- N7: Reference point between SMF and PCF

- N8: Reference point between UDM and AMF

- N9: Reference point between two core UPFs

- N10: Reference point between UDM and SMF

- N11: Reference point between AMF and SMF

- N12: Reference point between AMF and AUSF

- N13: Reference point between UDM and AUSF

- N14: Reference point between two AMFs

- N15: Reference point between PCF and AMF in case of non-roaming scenario, reference point between PCF and AMF in visited network in case of roaming scenario

Meanwhile, network slicing in the 5G system is a technology that enables a plurality of virtualized and independent logical networks in one physical network. A network operator may provide services by configuring a virtual end-to-end network called a network slice in order to satisfy specific requirements of services and/or applications. At this time, the network slice is distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). The network transmits a set of slices (eg, allowed NSSAI(s)) allowed to the terminal in a terminal registration procedure (eg, UE registration procedure), and the terminal transmits one S-NSSAI (ie, network slice) among them. Application data may be transmitted and received through a PDU (protocol data unit) session generated through.

One series example of the present disclosure provides a method and apparatus for preventing AMF from rejecting registration even if no slice is included in Allowed NSSAI in case of registration for emergency service.

In addition, in an embodiment of the present disclosure, in case of registering for an emergency service, a slice-related procedure is not performed for slices unrelated to the emergency service, and slice information unrelated to the emergency service is not provided to the terminal. provides Specifically, in the registration accept message delivered to the UE, 1) Allowed NSSAI is not provided, 2) Allowed NSSAI includes identifier information of a slice used for emergency service, or 3) Allowed NSSAI includes information agreed upon with the UE. Predefined slice identifier information indicating emergency registration may be included.

In addition, in an embodiment of the present disclosure, when MPS-related subscriber information or MCX-related subscriber information is changed, a method and apparatus capable of notifying the UE of this change are provided. Furthermore, in the case of a terminal using MPS and / or MCX in a registration procedure, a method and apparatus for exempting NSSAA are provided.

2 shows a terminal registration procedure for emergency service according to an embodiment.

In step 210, the UE 201 may transmit an AN message including an AN parameter and a registration request to the RAN 202. At this time, the registration request includes a UE identifier (SUCI (subscription concealed identifier), 5G-GUTI (5G-globally unique temporary identity), PEI (permanent equipment identifier), etc.), requested NSSAI, UE MM (mobility management) core network capability, etc. this may be included.

When the UE 201 performs registration for emergency services, the UE 201 may include a value indicating emergency registration in the registration request in Request Type.

In step 220, the RAN (202) may select the AMF (203) based on the information in the AN message received from the UE (201). When the UE 201 requests registration for emergency services, that is, when a value indicating emergency registration is included in the Request Type (request type) of the registration request message, the RAN 202 provides emergency services It is possible to select the AMF (203) based on the setting information for.

In step 230, the RAN (202) may deliver an N2 message including an N2 parameter and a registration request to the AMF (203). The N2 parameter may include selected PLMN ID, UE location information, UE context request, and the like.

Also, the N2 message may include a RAN ID.

In step 240, necessary steps in the UE registration procedure may be performed.

In step 250a, the AMF 203 does not perform the NSAC procedure and the NSSAA procedure when the request type in the registration request is a value indicating emergency registration. Furthermore, the AMF 203 does not perform the NSAC procedure and the NSSAA procedure for the corresponding slices even if there are slices available for the UE 201 in the case of a general registration request rather than emergency registration.

In step 250b, when the request type in the registration request is a value indicating emergency registration, the AMF 203 does not include slice information (Allowed NSSAI) available for the terminal in the registration accept message provided to the UE 201. don't Furthermore, when the AMF 203 supports the emergency service and there is no reason to reject the registration request for the emergency service of the UE 201 for other reasons, the registration accept message provided to the UE 201 includes an emergency An indicator indicating that registration for the service is allowed may be included. At this time, the registration accept message does not include slice information (Allowed NSSAI) available to the UE 201 and/or slice information for emergency service in Allowed NSSAI, a predefined slice identifier value indicating registration for emergency service, etc. this may be included.

In step 260, the AMF (203) constructs a registration accept message based on the decision on Allowed NSSAI in step 250b and transmits it to the UE (201).

3 illustrates a method of notifying an AMF and a UE in a UE registration procedure when MPS subscription information or MCX subscription information is changed according to an embodiment.

In step 310, the UE 301 may transmit an AN message including an AN parameter and a registration request to the RAN 302. At this time, the registration request includes a UE identifier (SUCI (subscription concealed identifier), 5G-GUTI (5G-globally unique temporary identity), PEI (permanent equipment identifier), etc.), requested NSSAI, UE MM (mobility management) core network capability, etc. this may be included.

In step 320, the RAN (302) may select the AMF (303) based on the information in the AN message received from the UE (301).

In step 330, the RAN (302) may deliver an N2 message including an N2 parameter and a registration request to the AMF (303). The N2 parameter may include selected PLMN ID, UE location information, UE context request, and the like.

In step 340, when the AMF 303 determines that UE authentication is required, it selects an authentication server function (AUSF) based on the UE identifier (SUCI or SUPI), and performs the authentication procedure for the UE 301 through the selected AUSF. can be done In addition, when there is no security context for NAS communication for the UE 301, a procedure for obtaining it may be performed.

In step 350, the AMF 303 may select the UDM 304 based on SUPI (UE Identifier). Also, the UDM 304 may select a UDR in which subscription information for the UE 301 is stored. The AMF 303 may request the UDM to register for the access type (eg, 3GPP access or non-3GPP access) for which the registration request of the UE 301 was received.

In step 360a, the AMF 303 may request access and mobility subscription information from the UDM 304 by transmitting a Nudm_SDM_Get Request message including UE identifier information and an indicator requesting access and mobility subscription data information to the UDM 304.

In step 360b, the UDM includes access and mobility subscription data in the Nudm_SDM_Get Response message and transmits it to the AMF 303. At this time, the UDM 304 may acquire access and mobility subscription data from the UDR.

When a change occurs in the MPS subscription information (i.e., MPS Priority) stored in UDM (304) or UDR (for example, when MPS subscription information was not existing but newly added to subscriber information), UDM (304) or UDR can set the MPS subscription changed indication value of internally stored access and mobility subscription data to a value indicating that a change has occurred, MPS subscription changed indication, MPS subscription information indicating that a change has occurred in the data transmitted to the AMF 303 etc. can be included.

When a change occurs in the MCX subscription information (i.e., MCX Priority) stored in the UDM (304) or UDR (for example, when there was no MCX subscription information in the subscriber information but was newly added), UDM (304) or UDR can set the internally stored MPS subscription changed indication value of access and mobility subscription data to a value indicating that a change has occurred, and MCX subscription changed indication, MCX subscription information indicating that a change has occurred in data transmitted to the AMF 303 etc. can be included.

When the MPS subscription changed indication is included in the Nudm_SDM_Get Response message received in step 360b, the AMF 303 may operate as follows in step 370.

If, in the MPS subscription information, a value indicating whether the use of access identity 1 of the UE 301 is valid within the PLMN (public land mobile network) is changed from a value indicating validity to a value indicating invalidity, AMF 303 may no longer include header information for priority service in communication with other Network Functions (NFs).

When the MCX subscription changed indication is included in the message received in step 360b, the AMF 303 may operate as follows in step 370.

If, in the MCX subscription information, a value indicating whether the use of access identity 2 of the UE 301 is valid within the PLMN is changed from a value indicating validity to a value indicating invalidity, the AMF 303 transmits another Communication with Network Functions (NFs) may no longer include header information for priority service.

If the message received in step 360b includes the MCX subscription changed indication, in step 370, the AMF 303 exempts the NSAC or NSSAA when calculating an allowable slice for the UE 301, or even if there is no allowable slice, the UE ( 301). If the message received in step 360b includes the MPS subscription changed indication, in step 370, the AMF 303 notifies the UE 301 of the changed information, and the UE 301 informs the UE 301 of the changed information. In order to operate accordingly, information such as MPS subscription changed indication and MPS subscription information may be transmitted.

If the message received in step 360b includes the MCX subscription changed indication, in step 370, the AMF 303 notifies the UE 301 of the changed information, and in order for the UE 301 to operate accordingly, the MCX subscription changed indication, Information such as MPS subscription information may be transmitted.

When the message received in step 370 includes the MPS subscription changed indication or the MCX subscription changed indication, the UE 301 may transmit a registration complete message to the AMF 303 in step 380. The registration complete message may include information indicating that changed MPS subscription information has been received in case of MPS and information indicating that changed MCX subscription information has been received in case of MCX.

When the message received in step 380 includes information indicating that the changed MPS subscription information has been received, the AMF 303 transmits information (Nudm_SDm_Info) indicating that the changed information has been successfully delivered to the UE 301 from the UDM 304 in step 390. send Upon receiving the corresponding information, the UDM 304 changes the MPS subscription changed indication value in the access and mobility subscription data from a value indicating that a change has occurred to a value indicating that there is no change.

When the message received in step 380 includes information indicating that the changed MCX subscription information has been received, the AMF 303 transmits information (Nudm_SDm_Info) indicating that the changed information has been successfully delivered to the UE 301 from the UDM 304 in step 390. is transmitted to the UDM (304). Upon receiving the corresponding information, the UDM 304 changes the MCX subscription changed indication value in the access and mobility subscription data from a value indicating that a change has occurred to a value indicating that there is no change.

In step 395, the UE 301 includes an MPS subscription changed indication in the message received in step 370, and a value indicating whether access identity 1 of the UE 301 is valid in the PLMN is valid in the MPS subscription information. If it is a value representing , and if you want to perform network registration for MPS service, you can perform a registration request to the network again. Alternatively, the UE 301 includes an MCX subscription changed indication in the message received in step 370, and a value indicating whether the access identity 2 of the UE 301 is valid in the PLMN in the MCX subscription information indicates validity. If it is a value, and if you want to perform network registration for the MCX service, you can perform a registration request to the network again.

At this time, the UE 301 includes a parameter indicating a request for priority service in the establishment cause of the AN parameter, and the RAN 302 includes a parameter indicating a request for a high priority service in the establishment cause, the RAN 302 ) is transmitted to the AMF 303 including the establishment cause. When the establishment cause indicates priority service, the AMF 303 may include header information requesting priority processing for communication with other NFs.

When the establishment cause indicates the priority service, the AMF 303 may store information indicating that the UE is using the priority service as a UE context.

When the establishment cause indicates priority service, the AMF 303 does not perform NSAC and NSSAA procedures for slices, or even if the result of the NSAC or NSSAA procedure fails, ignores the result and allows the corresponding slice, or NSAC or NSSAA The NSSAA procedure may include a parameter requesting an exemption from the NSACF or NSSAAF, respectively.

4 illustrates a method of notifying the AMF 403 and the UE 401 in a UE configuration update procedure when MPS subscription information or MCX subscription information is changed according to an embodiment.

In step 410, the UDM 404 may inform the AMF 403 of the change in subscriber information.

At this time, the UDM 404 may acquire access and mobility subscription data from a unified data repository (UDR).

If the UDM 404 or MPS subscription information (i.e., MPS Priority) stored in the UDR is changed (for example, MPS subscription information does not exist in the subscriber information but is newly added), UDM 404 or UDR In the internally stored access and mobility subscription data, the MPS subscription changed indication value can be set to a value indicating that a change has occurred, MPS subscription changed indication, MPS subscription information, etc. can include

If the MCX subscription information (i.e., MCX Priority) stored in the UDM (404) or UDR is changed (for example, if there was no MCX subscription information in the subscriber information but was newly added), the UDM (404) or UDR The MPS subscription changed indication value in internally stored access and mobility subscription data can be set to a value indicating that a change has occurred, MCX subscription changed indication, MCX subscription information, etc. can include

When the message received in step 410 includes the MPS subscription changed indication, the AMF 403 may operate as follows in step 420.

If, in the MPS subscription information, a value indicating whether the use of access identity 1 of the UE 401 within the PLMN is valid is changed from a value indicating validity to a value indicating invalidity, the AMF 403 sends another Communication with Network Functions (NFs) may no longer include header information for priority service.

When the MCX subscription changed indication is included in the message received in step 410, the AMF 403 may operate as follows in step 420.

If, in the MCX subscription information, a value indicating whether the use of access identity 2 of the UE 401 within the PLMN is valid is changed from a value indicating validity to a value indicating invalidity, the AMF 403 sends another Communication with Network Functions (NFs) may no longer include header information for priority service.

If the message received in step 410 includes the MPS subscription changed indication, the AMF may transmit information such as the MPS subscription changed indication and MPS subscription information to inform the terminal of the changed information and allow the terminal to operate accordingly.

If the message received in step 410 includes the MCX subscription changed indication, the AMF may transmit information such as the MCX subscription changed indication and MPS subscription information to inform the terminal of the changed information and allow the terminal to operate accordingly.

When the message received in step 420 includes the MPS subscription changed indication or the MCX subscription changed indication, the UE 401 may transmit a registration complete message to the AMF 403 in step 430 . The registration complete message may include information indicating that changed MPS subscription information has been received in case of MPS and information indicating that changed MCX subscription information has been received in case of MCX.

When the message received in step 430 includes information indicating that the changed MPS subscription information has been received, the AMF 403 transmits information (Nudm_SDm_Info) indicating that the changed information has been successfully delivered to the UE 401 from the UDM 404 in step 440. send Upon receiving the corresponding information, the UDM 404 changes the MPS subscription changed indication value in the access and mobility subscription data from a value indicating that a change has occurred to a value indicating that there is no change.

When the message received in step 430 includes information indicating that the changed MCX subscription information has been received, the AMF 403 transmits information (Nudm_SDm_Info) indicating that the changed information has been successfully delivered to the terminal to the UDM 404 in step 440 to the UDM ( 404). Upon receiving the corresponding information, the UDM 404 changes the MCX subscription changed indication value in the access and mobility subscription data from a value indicating that a change has occurred to a value indicating that there is no change.

In step 450, the UE 401 includes an MPS subscription changed indication in the message received in step 420, and a value indicating whether access identity 1 of the UE 401 is valid in the PLMN is valid in the MPS subscription information. If it is a value representing , and if you want to perform network registration for MPS service, you can perform a registration request to the network again. Alternatively, the UE 401 includes an MCX subscription changed indication in the message received in step 420, and a value indicating whether the access identity 2 of the UE 401 is valid in the PLMN in the MCX subscription information indicates validity. If it is a value, and if you want to perform network registration for the MCX service, you can perform a registration request to the network again.

At this time, the UE 401 includes a parameter indicating a request for priority service in the establishment cause of the AN parameter, and the RAN 402 includes a parameter indicating a request for a high priority service in the establishment cause, the RAN 402 ) is transmitted to the AMF 403 including the establishment cause. When the establishment cause indicates a priority service, the AMF 403 may include header information requesting priority processing for communication with other NFs.

When the establishment cause indicates the priority service, the AMF 403 may store information indicating that the UE is using the priority service as a UE context.

When the establishment cause indicates priority service, the AMF 403 does not perform NSAC and NSSAA procedures for slices, or even if the result of the NSAC or NSSAA procedure fails, ignores the result and allows the corresponding slice, or NSAC or NSSAA The NSSAA procedure may include a parameter requesting an exemption from the NSACF or NSSAAF, respectively.

5 illustrates a method for exempting NSSAA in a network registration procedure of a terminal using an MPS or MCX according to an embodiment.

For network slices requiring NSSAA in step 510, the AMF 503 may perform the NSSAA procedure.

If NSSAA is performed as a result of a UE registration procedure, the AMF 503 may determine which slices are NSSAA targets based on stored UE information (ie, UE Context).

At this time, when information indicating that the UE 501 is using MPS or MCX is stored in the UE Context of the AMF 503, or when the AMF 503 receives an establishment cause indicating a priority service in the terminal registration procedure, the AMF ( 503) may not perform NSSAA, or request a waiver from the NSSAA procedure.

Steps 520 and 530 are used when the UE 501 requests waiver.

Step 540 is used when the AMF 503 performs a waiver request.

In step 520, the AMF 503 may transmit EAP ID Request, S-NSSAI, and [exemption information] to the terminal.

Extensible Authentication Protocol (EAP) is a protocol used for authentication of the S-NSSAI of the UE between the UE and the AAA-S in the NSSA procedure.

In step 510, the AMF 503 stores information indicating that the UE 501 is using MPS or MCX in the UE Context of the AMF 503, or the AMF 503 establishes an establishment cause indicating a priority service in the terminal registration procedure. May include exemption information if received. The exemption information may include an indicator indicating that authentication exemption is required, information required when the terminal performs an authentication exemption request, and the like.

In step 530, the UE 501 may transmit EAP ID Response, S-NSSAI, and exemption information to AAA-S to the AMF 503.

If exemption information is received in step 520 or if the UE 501 is using the MPS or MCX service (that is, if access identity is determined to be 1 or 2), the UE 501 requests AAA-S for authentication exemption in step 530. Exemption information to AAA-S including request information may be included in a message sent to the AMF (503).

In step 540, the AMF (503) receives exemption information to AAA-S from the UE in step 3, or information indicating that the UE is using MPS or MCX is stored in the UE Context of the AMF (503), or in the terminal registration procedure When an establishment cause indicating priority service is received, exemption information to AAA-S may be included in a message sent to the NSSAAF (505). In addition, the message sent to the NSSAAF 505 may include GPSI, S-NSSAI, and EAP ID Response. In case of EAP ID Response, it is not included if steps 520 and 530 are not performed.

In step 550, the NSSAAF 505 converts the message format received from the AMF 503 into an AAA protocol format and delivers it to the AAA-S 506. If the AAA-S 506 is a server belonging to a third party, the corresponding message may be delivered to the AAA-S 506 through a proxy server for the AAA protocol (ie, AAA-P).

In step 560, the AAA-S 506 may include NSSAA result, GPSI, and S-NSSAI in a response message to the NSSAAF 505 and transmit the same.

If exemption information to AAA-S is included in the message received from NSSAAF (505) in step 550, AAA-S (506) succeeds in authentication for the terminal (GPSI) and slice (S-NSSAI) in step 560. Information indicating that it was done can be included in the NSSAA result.

When receiving the exemption information to AAA-S, the AAA-S 506 may stop the authentication process based on the EAP protocol.

In step 570, the NSSAAF 505 converts the message format received from the AAA-S 506 into a format that the NSSAAF can understand and forwards it to the NSSAAF 505. If the AAA-S 506 is a server belonging to a third party, the corresponding message may be delivered to the NSSAAF 505 through a proxy server for the AAA protocol (ie, AAA-P).

In step 580, the AMF 503 may store the S-NSSAI in the UE Context when the NSSAA result of the message received in step 570 is successful. In addition, the AMF 503 may transmit the NSSAA result to the UE 501.

6 illustrates a method in which SMF or PCF notifies AMF and UE of MPS invocation in an MPS invocation procedure according to an embodiment.

In step 610, the AF 609 may transmit a priority indicator to the PCF 608 for MPS invocation. Specifically, the AF 609 may transmit information such as UE identity, DNN, S-NSSAI, media type, media format, flow description, AF Application Identifier, priority indicator, and access type to the PCF 608.

In step 620, the PCF 608, when the priority indicator exists in the message from the AF 609 in step 610, starts a procedure for invocation of the MPS service based on the parameters received from the AF 609 in step 610.

When the priority indicator is present in the message from the AF 609 in step 610, the PCF 608 transmits the priority indicator to the SMF 607 in step 630 to notify that the UE 601 uses the MPS service.

In addition, the PCF 608 may transmit UE Identity, DNN, S-NSSAI, QoS flow description, access type, etc. to the SMF 607.

When the priority indicator is present in the message from the PCF 608 in step 630, the SMF 607 transmits the priority indicator to inform the AMF 603 in step 640 that the UE 601 uses the MPS service.

In addition, the SMF 607 may transmit UE identity, DNN, S-NSSAI, access type, etc. to the AMF 603.

In step 650, the AMF 603 sends an MPS message to the UE 601 when a priority indicator is present in the message from the SMF 607 in step 640 and when it is determined that the UE 601 is a terminal not yet using the MPS service. Information such as invocation command, registration required indicator, and acknowledgment required can be transmitted.

The MPS invocation command is information for informing the terminal that MPS has been invocation and instructing the terminal to operate as a terminal using the MPS service.

The registration required indicator is information for requesting a terminal to re-register to the network as a terminal using MPS.

Acknowledgment require is information requesting notification of whether or not a terminal has been configured as a terminal using MPS.

In step 660, when the UE 601 receives the MPS invocation command in the message from the AMF 603, it operates as the UE 601 using MPS. That is, the UE 601 sets the access identity to 1 and sets the establishment cause to priority services in the message sent to the RAN 602 when performing the network registration procedure and sends it.

When the message from the AMF 603 includes acknowledgment required, the UE 601 transmits a message to the AMF 603 to confirm that the AMF 603 operates as the UE 601 using the MPS. Upon receiving a corresponding message from the terminal, the AMF 603 stores information indicating that the corresponding UE 601 is a terminal operating as an MPS.

In step 670, when the message received in step 650 includes the registration required indicator, the UE 601 performs a registration procedure, and upon execution, sets the establishment cause to priority services in the message sent to the RAN 602 and sends it.

7 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

Referring to FIG. 7 , a terminal may include a terminal receiving unit 710, a terminal transmitting unit 720, and a terminal processing unit (control unit) 730.

The terminal receiver 710 and the terminal transmitter 720 may be referred to as a transceiver. According to the communication method of the terminal described above, the terminal receiving unit 710, the terminal transmitting unit 720, and the terminal processing unit 730 of the terminal may operate. However, the components of the terminal are not limited to the above-described examples. For example, the terminal may include more components (eg, memory, etc.) or fewer components than the aforementioned components. In addition, the terminal receiving unit 710, the terminal transmitting unit 720, and the terminal processing unit 730 may be implemented as a single chip.

The terminal receiver 710 and the terminal transmitter 720 (or transceiver) may transmit and receive signals to and from the base station. Here, the signal may include control information and data. To this end, the transceiver unit may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting the frequency. However, this is only one embodiment of the transceiver, and components of the transceiver are not limited to the RF transmitter and the RF receiver.

In addition, the transmitting/receiving unit may receive a signal through a wireless channel, output the signal to the terminal processing unit 730, and transmit the signal output from the terminal processing unit 730 through the wireless channel.

A memory (not shown) may store programs and data required for operation of the terminal. Also, the memory may store control information or data included in a signal obtained from the terminal. The memory may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The terminal processing unit 730 may control a series of processes so that the terminal can operate according to the above-described embodiment of the present disclosure. The terminal processing unit 730 may be implemented as a circuit or an application-specific integrated circuit or at least one or more processors. The terminal processing unit 730 may be implemented as a control unit or one or more processors.

8 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

Referring to FIG. 8 , a base station may include a base station receiving unit 810, a base station transmitting unit 820, and a base station processing unit (control unit) 830.

The base station receiver 810 and the base station transmitter 820 may be referred to as a transceiver. According to the communication method of the base station described above, the base station receiving unit 810, the base station transmitting unit 820, and the base station processing unit 830 of the base station may operate. However, components of the base station are not limited to the above-described examples. For example, the base station may include more components (eg, memory, etc.) or fewer components than the aforementioned components. In addition, the base station receiving unit 810, the base station transmitting unit 820, and the base station processing unit 830 may be implemented in a single chip form.

The base station receiving unit 810 and the base station transmitting unit 820 (or transceiver) may transmit and receive signals to and from a terminal and/or a network entity. Here, the signal may include control information and data. To this end, the transceiver unit may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting the frequency. However, this is only one embodiment of the transceiver, and components of the transceiver are not limited to the RF transmitter and the RF receiver.

In addition, the transmitting/receiving unit may receive a signal through a wired/wireless channel, output the signal to the base station processing unit 830, and transmit the signal output from the base station processing unit 830 through a wired/wireless channel.

A memory (not shown) may store programs and data necessary for the operation of the base station. Also, the memory may store control information or data included in a signal obtained from the base station. The memory may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The base station processing unit 830 may control a series of processes so that the base station operates according to the above-described embodiment of the present disclosure. The base station processing unit 830 may be implemented as a control unit or one or more processors.

9 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.

Referring to FIG. 9 , a network entity may include a network entity receiving unit 910 , a network entity transmitting unit 920 , and a network entity processing unit (control unit) 930 . Here, the network entities may include AMF, SMF, UPF, DN, NSSF, NEF, AUSF, NRF, PCF, UDM, AF, and the like.

The network entity receiver 910 and the network entity transmitter 920 may be collectively referred to as a transceiver. According to the communication method of the network entity described above, the network entity receiving unit 910, the network entity transmitting unit 920, and the network entity processing unit 930 of the network entity may operate. However, the components of the network entity are not limited to the above examples. For example, a network entity may include more components (eg, memory, etc.) or fewer components than those described above. In addition, the network entity receiving unit 910, the network entity transmitting unit 920, and the network entity processing unit 930 may be implemented in a single chip form.

Network entity receiver 910 and network entity transmitter 920 (or transceiver) may transmit and receive signals to and from base stations and/or other network entities. Here, the signal may include control information and data. The transmitting/receiving unit may receive a signal through a wired/wireless channel, output the signal to the network entity processing unit 930, and transmit the signal output from the network entity processing unit 930 through a wired/wireless channel.

A memory (not shown) may store programs and data required for operation of a network entity. Also, the memory may store control information or data included in a signal obtained from a network entity. The memory may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The network entity processing unit 930 may control a series of processes so that the network entity may operate according to the above-described embodiment of the present disclosure. The network entity processing unit 930 may be implemented as a control unit or one or more processors.

10 is a diagram illustrating a method of finding out whether a new AMF subscribes to an MPS, MCX, or MPS/MCX in a network registration procedure of a terminal according to an embodiment of the present disclosure.

In step 1010, the UE 1001 may transmit an AN message including an AN parameter and a registration request to the RAN 1002. At this time, the registration request includes a UE identifier (SUCI (subscription concealed identifier), 5G-GUTI (5G-globally unique temporary identity), PEI (permanent equipment identifier), etc.), requested NSSAI, UE MM (mobility management) core network capability, etc. this may be included.

In step 1020, the RAN (1002) may select the AMF (1003) based on the information in the AN message received from the UE (1001).

In step 1030, the RAN 1002 may deliver an N2 message including an N2 parameter and a registration request to the AMF 1003. The N2 parameter may include selected PLMN ID, UE location information, UE context request, and the like.

In step 1030, the AMF 1003 may check whether information indicating whether the UE 1001 is subscribed to a priority service is included in the UE Context. Here, the information indicating whether the UE 1001 is subscribed to the priority service may include information indicating whether the UE 1001 is subscribed to the MPS and/or MCX. Based on this information, the AMF 1003 can check whether the UE 1001 is subscribed to the MPS, the MCX, or both the MPS and the MCX in the UE Context. The AMF 1003 preferentially processes the control plane message for the UE 1001 when the UE 1001 is subscribed to the priority service (that is, preferentially processes the corresponding message even in a congestion situation), and the UE 1001 ) may omit NSAC and NSSAA or exempt NSAC and NSSAA for slices requested by ). If the AMF is a newly changed AMF, the AMF may perform steps 1040a and 1040b.

In step 1040a, the new AMF 1003 may determine the old AMF 1004 based on the 5G-GUTI received in step 1030 and request UE Context transmission from the old AMF 1004.

In step 1040b, when the old AMF 1004 receives a UE Context transmission request message from the New AMF 1003, it may transmit the UE Context to the New AMF 1003. At this time, the UE Context may include information indicating whether the UE 1001 is subscribed to a preferential service in the UE Context. Here, the information indicating whether the UE 1001 is subscribed to the priority service may include information indicating whether the UE 1001 is subscribed to the MPS and/or MCX. The New AMF 1003 preferentially processes the control plane message for the UE 1001 when the UE 1001 is subscribed to the priority service (that is, preferentially processes the corresponding message even in a congestion situation), and the UE ( 1001) may omit NSAC and NSSAA or exempt NSAC and NSSAA for slices requested by

In step 1050, when the AMF (1003) determines that UE authentication is required, it selects an authentication server function (AUSF) based on the UE identifier (SUCI or SUPI), and performs the authentication procedure for the UE (1001) through the selected AUSF. can be done In addition, when there is no security context for NAS communication for the UE 1001, a procedure for obtaining it may be performed.

In step 1060, the AMF 1003 may select the UDM 1005 based on SUPI (UE Identifier). Also, the UDM 1005 may select a UDR in which subscription information for the UE 1003 is stored. The AMF 1003 may request the UDM 1005 to register for the access type (eg, 3GPP access or non-3GPP access) for which the registration request of the UE 1003 was received.

In step 1070a, the AMF 1003 may request access and mobility subscription information from the UDM 1005 by transmitting a Nudm_SDM_Get Request message including UE identifier information and an indicator requesting access and mobility subscription data information to the UDM. The AMF 1003 may not request the corresponding information from the UDM 1005 when information indicating whether the UE 1001 is subscribed to the MPS and/or MCX is included in the UE Context. When the AMF 1003 does not include information indicating whether the UE 1001 is subscribed to the MPS and/or MCX is not included in the UE Context, that is, when it does not know whether the UE 1001 subscribes to the MPS and/or MCX, the UDM 1003 ) may include an indicator requesting the information.

In step 1070b, UDM 1005 transmits Nudm_SDM_Get Response message to AMF 1003 including access and mobility subscription data. At this time, the UDM 1005 may acquire access and mobility subscription data from the UDR. At this time, the UDM (1005) determines that the message received from the AMF (1003) in step 1070a includes an indicator requesting MPS subscription information and/or an indicator requesting MCX subscription information, or that the AMF (1003) is a modified AMF. When the notification information is included, MPS subscription information and/or MCX subscription information may be included in the message transmitted to the AMF 1003.

When the message from the UDM 1005 includes MPS subscription information and/or MCX subscription information, the AMF 1003 preferentially processes the control plane message for the UE 1001 (that is, sends the corresponding message even in a congestion situation). Priority processing), NSAC and NSSAA may be omitted or NSAC and NSSAA may be exempted for the slice requested by the UE 1001. When the message from the UDM 1005 includes MPS subscription information and/or MCX subscription information, the AMF 1003 transmits the corresponding information (that is, whether the UE subscribes to the MPS and/or the MCX) to the AMF 1003. It can be stored in the UE context.

In step 1080, the remaining terminal registration procedures are performed.

Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

Such programs (software modules, software) may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of It can be stored on optical storage devices, magnetic cassettes. Alternatively, it may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

In addition, the program accesses through a communication network such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), or a Storage Area Network (SAN), or a communication network composed of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

In the embodiments of the present disclosure, components included in the invention are expressed in singular or plural, depending on the presented embodiment. However, singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

In the drawings describing the embodiments of the present disclosure, the order of explanation does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel. In addition, the drawings describing the embodiments of the present disclosure may omit some components and include only some components within a range not detracting from the essence of the present disclosure.

The embodiments of the present disclosure may be executed by combining some or all of the contents included in each embodiment within the scope of not detracting from the essence of the present disclosure.

On the other hand, the embodiments of the present disclosure disclosed in the present specification and drawings are only presented as specific examples to easily explain the technical content of the present disclosure and help understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other modified examples based on the technical idea of the present disclosure can be implemented.

Claims (1)

In the emergency service providing method of AMF (Access and Mobility management Function) in a wireless communication system,
Receiving an N2 message including an N2 parameter and a registration request from a base station; and
When the request type in the registration request is a value indicating emergency registration, performing a registration procedure of UE (User Equipment) without performing an NSAC procedure and an NSSAA procedure.

Images