WO2024035021A1 - Method and apparatus for providing coverage information in wireless communication system - Google Patents

Method and apparatus for providing coverage information in wireless communication system Download PDF

Info

Publication number
WO2024035021A1
WO2024035021A1 PCT/KR2023/011536 KR2023011536W WO2024035021A1 WO 2024035021 A1 WO2024035021 A1 WO 2024035021A1 KR 2023011536 W KR2023011536 W KR 2023011536W WO 2024035021 A1 WO2024035021 A1 WO 2024035021A1
Authority
WO
WIPO (PCT)
Prior art keywords
coverage information
coverage
information
terminal
authentication
Prior art date
Application number
PCT/KR2023/011536
Other languages
French (fr)
Korean (ko)
Inventor
김동연
박중신
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2024035021A1 publication Critical patent/WO2024035021A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • This disclosure relates to a method and device for providing coverage information in a wireless communication system.
  • 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave.
  • 'Sub 6GHz' sub-6 GHz
  • mm millimeter wave
  • Wave ultra-high frequency band
  • Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth.
  • THz Terahertz
  • ultra-wideband services enhanced Mobile BroadBand, eMBB
  • ultra-reliable low-latency communications URLLC
  • massive machine-type communications mMTC
  • numerology support multiple subcarrier interval operation, etc.
  • dynamic operation of slot format initial access technology to support multi-beam transmission and broadband
  • definition and operation of BWP Band-Width Part
  • New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information
  • L2 pre-processing L2 pre-processing
  • dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.
  • V2X Vehicle-to-Everything
  • NR-U New Radio Unlicensed
  • UE Power Saving NR terminal low power consumption technology
  • NTN Non-Terrestrial Network
  • IAB provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links.
  • Intelligent factories Intelligent Internet of Things, IIoT
  • Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover
  • 2-step Random Access (2-step RACH for simplification of random access procedures)
  • Standardization in the field of wireless interface architecture/protocol for technologies such as NR is also in progress
  • a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • FD-MIMO full dimensional MIMO
  • array antennas to ensure coverage in the terahertz band of 6G mobile communication technology.
  • multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end.
  • the 3rd generation partnership project (3GPP) is developing a method that allows a terminal to connect to a network (according to one embodiment, a 5G core network) through a satellite access network (satellite RAN).
  • This disclosure provides a method and device for providing coverage information in a wireless communication system.
  • a method of operating an access and mobility management function (AMF) in a wireless communication system provides coverage information of a satellite radio access network (RAN) to a network exposure function (NEF) ( Transmitting an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information, from a coverage information server, a UE (UE) corresponding to the coverage information delivery ID receiving at least one of an authentication result and coverage information of user equipment) and transmitting at least one of an authentication result and coverage information to the UE.
  • RAN satellite radio access network
  • NEF network exposure function
  • FIG. 1 is a diagram showing the network structure and interface of a 5G system according to an embodiment of the present disclosure.
  • Figure 2 is a diagram showing the 5GS and EPS network structure and interface according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating the structure of a wireless communication system for non-roaming supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating the structure of a local breakout roaming wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
  • FIG. 5 is a diagram illustrating the structure of 5G system non-roaming according to an embodiment of the present disclosure.
  • FIG. 6 is a diagram illustrating the structure of local breakout roaming in a 5G system according to an embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating a registration procedure for coverage map transfer according to an embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating a coverage map transfer procedure using a mobility management function according to an embodiment of the present disclosure.
  • FIG. 9 is a diagram illustrating a method of transferring coverage map information in a PDU session management procedure according to an embodiment of the present disclosure.
  • FIG. 10 is a diagram illustrating a method of transferring coverage map information in a PDN connection management procedure according to an embodiment of the present disclosure.
  • Figure 11 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
  • Figure 12 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
  • FIG. 13 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
  • a method of operating an access and mobility management function (AMF) in a wireless communication system provides coverage information of a satellite radio access network (RAN) to a network exposure function (NEF) ( Transmitting an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information, from a coverage information server, a UE (UE) corresponding to the coverage information delivery ID receiving at least one of an authentication result and coverage information of user equipment) and transmitting at least one of an authentication result and coverage information to the UE.
  • RAN satellite radio access network
  • NEF network exposure function
  • a method of operating a user equipment (UE) in a wireless communication system includes sending a registration request message including a coverage information delivery ID and a coverage information request to an access and mobility management function (AMF). Transmitting and receiving at least one of the authentication result and coverage information of the UE from the AMF.
  • AMF access and mobility management function
  • an access and mobility management function includes a communication unit (transceiver) and at least one controller operably coupled to the communication unit,
  • the control unit sends a network exposure function (NEF) an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information of a satellite radio access network (RAN) transmits an authentication request message), receives at least one of an authentication result and coverage information of a UE (user equipment) corresponding to the coverage information transfer ID from a coverage information server, and provides authentication to the UE. It is configured to transmit at least one of result and coverage information.
  • NEF network exposure function
  • a user equipment includes a communication unit (transceiver) and at least one controller operably coupled to the communication unit, the control unit , Transmits a registration request message including a coverage information delivery ID and a coverage information request to an access and mobility management function (AMF), and receives at least one of the authentication result and coverage information of the UE from the AMF. configured to receive.
  • a communication unit transmitter
  • AMF access and mobility management function
  • New Radio NR
  • 3GPP 3rd Generation Partnership Project
  • Packet Core 5G System Packet Core 5G System
  • core network 5G
  • 5G 5G
  • NG Core Next Generation Core
  • the main gist of the present disclosure can be applied to other communication systems with similar technical background with slight modifications without significantly departing from the scope of the present disclosure. It is possible, and this will be possible at the discretion of a person skilled in the technical field of the present disclosure.
  • connection node terms referring to network entities, terms referring to messages, terms referring to the interface between network entities, and various identification information. Terms referring to these are exemplified for convenience of explanation. Therefore, it is not limited to the terms used in the present disclosure, and other terms referring to objects having equivalent technical meaning may be used.
  • the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network.
  • a terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.
  • UE user equipment
  • MS mobile station
  • UL uplink
  • UL refers to a wireless transmission path of a signal transmitted from a terminal to a base station.
  • each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions.
  • These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions.
  • These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s).
  • Computer program instructions can also be mounted 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 process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram 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).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s).
  • the term ' ⁇ unit' used in the embodiments of the present disclosure refers to software or hardware components such as FPGA (field programmable gate array) or ASIC (Application Specific Integrated Circuit), and ' ⁇ unit' refers to what role perform them.
  • ' ⁇ part' is not limited to software or hardware.
  • the ' ⁇ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, ' ⁇ part' 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.
  • components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'.
  • the components and 'parts' may be implemented to reproduce one or more central processing units (CPUs) within a device or a secure multimedia card.
  • ' ⁇ part' may include one or more processors.
  • Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced.
  • Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.
  • the LTE system uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (DL), and SC-FDMA (Single Carrier Frequency Division Multiple Access) in the uplink (UL). ) method is adopted.
  • Uplink refers to a wireless link in which a terminal (UE (User Equipment) or MS (Mobile Station)) transmits data or control signals to a base station (eNode B, or base station (BS)), and downlink refers to a wireless link in which the base station transmits data or control signals to the base station (eNode B, or base station (BS)). It refers to a wireless link that transmits data or control signals.
  • the above multiple access method usually distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. You can.
  • the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported.
  • Services considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is.
  • eMBB aims to provide more improved data transmission speeds than those supported by existing LTE, LTE-A or LTE-Pro.
  • eMBB in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink from the perspective of one base station.
  • the 5G communication system must provide the maximum transmission rate and at the same time provide increased user perceived data rate.
  • improvements in various transmission and reception technologies are required, including more advanced multi-antenna (Multi Input Multi Output, MIMO) transmission technology.
  • MIMO Multi Input Multi Output
  • the 5G communication system uses a frequency bandwidth wider than 20MHz in the 3 ⁇ 6GHz or above 6GHz frequency band to transmit the data required by the 5G communication system. Transmission speed can be satisfied.
  • mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems.
  • IoT Internet of Things
  • mMTC requires support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs.
  • the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km2) within a cell.
  • terminals that support mMTC are likely to be located in shadow areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system.
  • Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.
  • URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency situations. Services used for emergency alerts, etc. can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service that supports URLLC must satisfy an air interface latency of less than 0.5 milliseconds and has a packet error rate of less than 10-5. Therefore, for services supporting URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, a design that requires allocating wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.
  • TTI Transmit Time Interval
  • the three services of the 5G communication system namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters can be used between services to satisfy the different requirements of each service.
  • the 5G communication system is not limited to the three services mentioned above.
  • satellite radio access covers a relatively larger area than terrestrial radio access
  • the number of UEs communicating with the 5G core network also increases.
  • satellite radio access coverage moves according to the movement of the satellite, so UEs may temporarily lose connection to the core network.
  • UEs that lose connectivity may be disconnected from the core network, although satellite coverage may return after a certain period.
  • the UEs request registration and connection to the core network again, and the core network performs the necessary operations and sends signals to the UEs. Since the periodic characteristics of the satellite are not taken into account, this is repeated continuously and reduces the efficiency of resource use of the UE, core network, and radio access section.
  • This disclosure provides a method and device for delivering satellite coverage information to a terminal and core network in 5GS and EPS, where satellite cell coverage moves over time. More specifically, it provides a method and device that can efficiently manage UE registration and connection by considering satellite access coverage characteristics, UE mobility, network terminal registration and session management capabilities, and satellite access radio capabilities. .
  • FIG. 1 is a diagram showing the network structure and interface of a 5G system according to an embodiment of the present disclosure.
  • a network entity included in the network structure of the 5G system in FIG. 1 may include a network function (NF) depending on system implementation.
  • NF network function
  • the network structure of the 5G system 100 may include various network entities.
  • the 5G system 100 includes an authentication server function (AUSF) 108, an access and mobility management function (AMF) 103, and a session management function.
  • UE user equipment
  • Each NF of the 5G system 100 supports the following functions.
  • AUSF 108 processes and stores data for authentication of UE 101.
  • the AMF 103 provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF. Specifically, the AMF 103 supports CN inter-node signaling for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), and non-access stratum (NAS) ) Endpoint of signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE accessibility ( reachability (including control and performance of paging retransmissions), mobility management controls (subscriptions and policies), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (AMF events and (for interface to LI system), providing delivery of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, roaming authority check It supports functions such as access authorization, providing delivery of SMS messages between the UE and SMSF, security
  • the DN 110 means, for example, an operator service, Internet access, or a third party service.
  • the DN 110 transmits a downlink protocol data unit (PDU) to the UPF 104 or receives the PDU transmitted from the UE 101 from the UPF 104.
  • PDU downlink protocol data unit
  • the PCF (106) receives information about packet flow from the application server and provides the function of determining policies such as mobility management and session management.
  • PCF 106 supports a unified policy framework to govern network behavior, provides policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and allows users to It supports functions such as implementing a front end to access relevant subscription information for policy decisions within a user data repository (UDR).
  • control plane function(s) e.g., AMF, SMF, etc.
  • UDR user data repository
  • the SMF 105 provides a session management function, and when the UE has multiple sessions, each session can be managed by a different SMF. Specifically, SMF 105 performs session management (e.g., session establishment, modification, and termination, including maintaining tunnels between UPF 104 and (R)AN 102 nodes), UE IP address allocation, and Management (optionally including authentication), selection and control of UP functions, establishment of traffic steering to route traffic to appropriate destinations in UPF 104, termination of interfaces towards policy control functions; Enforcement of policy and control portion of quality of service (QoS), lawful intercept (for SM events and interface to LI system), termination of SM portion of NAS messages, downlink data notification, It supports functions such as initiator of AN-specific SM information (delivered to (R)AN (102) via N2 via AMF (103)), SSC mode determination of the session, and roaming function. Some or all of the functions of SMF 105 may be supported within a single instance of one SMF.
  • session management e.g., session establishment, modification
  • the UDM 109 stores user subscription data, policy data, etc.
  • UDM 109 includes two parts: an application front end (FE) (not shown) and a user data repository (UDR) (not shown).
  • FE application front end
  • UDR user data repository
  • UDM FE includes UDM FE, which is responsible for location management, subscription management, and credential processing, and PCF, which is responsible for policy control.
  • UDR stores data required for functions provided by UDM-FE and policy profiles required by PCF.
  • Data stored within the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data.
  • UDM-FE accesses subscription information stored in UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management. do.
  • the UPF (104) delivers the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102) and receives it from the UE (101) via the (R)AN (102).
  • One uplink PDU is delivered to the DN (110).
  • the UPF 104 is an anchor point for intra/inter RAT mobility, an external PDU session point for interconnect to a data network, packet routing and forwarding, and packet inspection ( User plane portion of inspection and policy rule enforcement, lawful intercept, traffic usage reporting, and uplink classifier to support routing of traffic flows to the data network, multi-homed Branching points to support PDU sessions, QoS handling for the user plane (e.g.
  • UPF 104 packet filtering, gating, uplink/downlink rate enforcement), uplink traffic verification (service data) It supports functions such as service data flow (SDF mapping between SDF and QoS flows), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering function.
  • SDF mapping between SDF and QoS flows service data flow
  • transport level packet marking in uplink and downlink downlink packet buffering
  • downlink data notification triggering function Some or all of the functions of UPF 104 may be supported within a single instance of one UPF.
  • AF 107 supports 3GPP for service provision (e.g., supporting functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control). Interoperates with the core network.
  • RAN 102 supports both evolved E-UTRA (evolved E-UTRA), which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).
  • E-UTRA evolved E-UTRA
  • NR new radio
  • the gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink).
  • radio resource management i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink.
  • dynamic allocation of resources i.e. scheduling
  • Internet protocol (IP) header compression i.e. scheduling
  • encryption and integrity protection of user data streams i.e. scheduling
  • routing to AMF is not determined from the information provided to the UE.
  • selection of AMF upon attachment of the UE user plane data routing to UPF(s), control plane information routing to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), system Scheduling and transmission of broadcast information (from AMF or operating and maintenance (O&M)), setting up measurements and measurement reporting for mobility and scheduling, transport level packet marking in the uplink, Session management, support of network slicing, QoS flow management and data mapping to radio bearers, support of UE in inactive mode, distribution function of NAS messages, NAS node selection function, radio access network sharing, dual connectivity ( Supports features such as dual connectivity and tight interworking between NR and E-UTRA.
  • UE 101 refers to a user device.
  • a user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc.
  • the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, or a multimedia device, or it may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.
  • PC personal computer
  • NEF 113 is provided by 3GPP network functions, e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing. Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s). NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed by the NEF 111 to other NF(s) and AF(s) and used for other purposes such as analysis.
  • 3GPP network functions e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing.
  • Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s).
  • NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed
  • NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
  • FIG. 1 illustrates a reference model for a case where the UE 101 accesses one DN 110 using one PDU session for convenience of explanation, but the present disclosure is not limited thereto.
  • UE 101 can simultaneously access two (ie, local and central) data networks using multiple PDU sessions.
  • two SMFs may be selected for different PDU sessions.
  • each SMF may have the ability to control both the local UPF and the central UPF within the PDU session.
  • UE 101 may simultaneously access two (ie, local and central) data networks provided within a single PDU session.
  • NSSF 114 may select a set of network slice instances serving UE 101. Additionally, the NSSF 114 may determine permitted network slice selection assistance information (NSSAI) and, if necessary, perform mapping on subscribed single-network slice selection assistance information (S-NSSAI). Additionally, the NSSF 114 may determine the configured NSSAI and, if necessary, perform mapping to the subscribed S-NSSAIs. Additionally, the NSSF 114 may determine the set of AMFs used to serve the UE, or, depending on settings, may query the NRF 115 to determine a list of candidate AMFs.
  • NSSAI permitted network slice selection assistance information
  • S-NSSAI subscribed single-network slice selection assistance information
  • the NSSF 114 may determine the configured NSSAI and, if necessary, perform mapping to the subscribed S-NSSAIs. Additionally, the NSSF 114 may determine the set of AMFs used to serve the UE, or, depending on settings, may query the NRF 115 to determine a list of candidate AMF
  • NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
  • the conceptual link connecting NFs in the 5G system is defined as a reference point.
  • the following illustrates reference points included in the 5G system architecture represented in Figure 1.
  • the terminal may refer to the UE 101, and the terms UE and terminal may be used interchangeably. In this case, unless the UE is specifically defined additionally, it should be understood as UE 101.
  • Figure 2 is a diagram showing the 5GS and EPS network structure and interface according to an embodiment of the present disclosure.
  • the network structure of 5GS and EPS may include a coverage map information network function (CM NF) and a coverage map information server (CMS).
  • CM NF coverage map information network function
  • CMS coverage map information server
  • the CM NF may provide the function of receiving information related to access network coverage (which may include satellite access coverage) and providing it to the terminal and core network entity. Specifically, when the CM NF receives a request for coverage-related information of the access network from a terminal, 5GC network entity, or EPC network entity, it evaluates and translates the requested information and provides coverage-related information to CMS. You may request provision. In addition, when the CM NF receives coverage-related information and authentication data for delivering coverage-related information from CMS, it can evaluate and convert the coverage-related information and provide it to the terminal, 5GC network entity, or EPC network entity. .
  • CM NF may exist in the same software or device as NEF, or may exist in separate software or device.
  • Figure 2 shows an example that exists in the same device as the NEF, but is not limited to this.
  • the CM NF when the CM NF exists in the same device as the NEF, the CM NF can support the same interfaces supported by the NEF.
  • CM NF can communicate with each 5GC network entity in the same way using the interface used by NEFs such as N29, N30, and N51 to communicate with 5GC network entities.
  • the CM NF can communicate with the DN using the N33 interface that the NEF uses to communicate with the DN.
  • the terminal can be connected to 5GC (5G Core Network) using NG-RAN or gNB.
  • NG-RAN can be connected to UPF and N3 interface
  • UPF and DN can be connected to N6 interface.
  • the terminal can be connected to the EPC (Evolved Packet Core Network) using (R)AN or eNB.
  • (R)AN and the Serving Gateway can be connected to the S1 (or S1-U) interface
  • the Serving Gateway and The PDN Gateway can be connected to the S5 interface
  • the PDN Gateway and DN can be connected to the SGi interface.
  • CMS can provide coverage-related information to terminals, 5GC network entities, and EPC network entities.
  • CMS may be a server that manages coverage-related information, for example, by an operator operating a 5GC or EPC network or an operator operating a satellite access network.
  • CMS can perform authentication on whether coverage-related information can be received for the requested terminal or entity.
  • CMS can provide coverage-related information to authenticated terminals or entities.
  • CMS can be recognized as a DN from the perspective of 5GS and EPS, and therefore can equally support the interface connecting 5GC and EPC entities and DN.
  • NEF can communicate with CMS over the N33 interface
  • UPF can communicate with CMS over the N6 interface
  • PDN gateway can communicate with CMS over the SGi interface.
  • FIG. 3 is a diagram illustrating the structure of a wireless communication system for non-roaming supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
  • 5GS is a NR (New Radio) base station (NG-RAN (radio access node) or gNB (next generation node B)) 103 for wireless access of the terminal (UE) 101, and an access and mobility management function (access and mobility management function) It may include mobility management function (AMF) (105), policy control function (PCF), network exposure function (NEF), and coverage map information network function (CM NF).
  • AMF mobility management function
  • PCF policy control function
  • NEF network exposure function
  • CM NF coverage map information network function
  • SMF session management function
  • UPF user plane function
  • NSSF network slice selection function
  • UDM unified data management
  • UDM unified data repository
  • the EPS is an E-UTRA base station (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or evolved node B (eNB)) 113, a mobility management entity (MME) 115 , serving gateway (SGW) 117, packet data network gateway (PGW) (PGW may be composed of PGW-U and PGW-C), home subscriber server (home subscriber server, HSS), Service Capability Exposure Function (SCEF), etc.
  • E-UTRA base station Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or evolved node B (eNB)
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • SCEF Service Capability Exposure Function
  • the AMF (105) and MME (115) may be a Network Function (NF) that manages wireless network access and mobility for the terminal.
  • SMF, SGW, and PGW are NFs that manage sessions for the terminal, and session information may include Quality of Service (QoS) information, charging information, and information about packet processing.
  • QoS Quality of Service
  • the UPF and PGW are NFs that process user plane traffic (e.g., user plane traffic) and are controlled by SMF and SGW.
  • the PCF and PCRF may be NFs that manage operator policy (operator policy and/or PLMN policy) for providing services in a wireless communication system.
  • the PCF can be divided into a PCF in charge of Access and Mobility (AM) policy and UE policy and a PCF in charge of Session Management (SM) policy.
  • the PCF in charge of AM/UE policy and the PCF in charge of SM policy may be logically or physically separate NFs, or may be a single logically or physically NF.
  • UDM and HSS may be NFs that store and manage UE subscriber information (UE subscription).
  • UDR may be an NF or database (DB) that stores and manages data.
  • UDR stores the terminal's subscription information and can provide the terminal's subscription information to UDM.
  • UDR can store operator policy information and provide operator policy information to the PCF.
  • NSSF may be an NF that performs the function of selecting network slice instances serving the terminal or determining Network Slice Selection Assistance Information (NSSAI).
  • NSSAI Network Slice Selection Assistance Information
  • An instance is an NF that exists in the form of software code, and is used to perform the functions of the NF in a physical computing system (e.g., a specific computing system that exists on a core network) from a computing system to a physical or/and It can refer to a state in which logical resources are allocated and NF functions can be executed.
  • AMF Instance, SMF Instance, NSSF Instance, etc. each refer to a state in which physical and/or logical resources can be allocated and used for the operation of AMF, SMF, NSSF, etc. from a specific computing system existing on the core network. can do.
  • an AMF Instance, SMF Instance, or NSSF that uses physical and/or logical resources for AMF, SMF, and NSSF operations is allocated from a specific computing system existing on the network. Instance can perform the same operation.
  • UDM of 5GS and HSS of EPS may be composed of one combo node (referred to as UDM+HSS) 124.
  • the UDM+HSS node 124 can store subscriber information of the terminal.
  • the SMF of 5GS and the PGW-C of EPS may be composed of one combo node (referred to as SMF+PGW-C or PGW-C+SMF) 122.
  • SMF+PGW-C or PGW-C+SMF one combo node
  • the UPF of 5GS and the PGW-U of EPS may be composed of one combo node (referred to as UPF+PGW-U or PGW-U+UPF) 121.
  • UPF+PGW-U or PGW-U+UPF one combo node
  • NEF of 5GS and SCEF of EPS can be composed of one combo node (referred to as NEF+SCEF or SCEF+NEF).
  • NEF+SCEF or SCEF+NEF the expression of the abbreviation can be understood as the same device regardless of whether NEF+SCEF or SCEF+NEF is used.
  • CM NF may exist in the same software or device as NEF, or may exist in separate software or device.
  • Figure 3 shows an example that exists in the same device as NEF+SCEF, but is not limited to this.
  • the terminal 101 can access the EPS MME 115 through the E-UTRA base station 113 and use the EPS network service. Additionally, the terminal 101 can access the 5GS AMF 105 through the NR base station 103 and use the 5GS network service.
  • the same reference numerals are used for the terminal 101 connected to EPS and the terminal 101 connected to 5GS. This is to mean that the terminal 101 is a terminal that can access EPS and 5GS.
  • one NF or network entity can support different network systems simultaneously, and these NFs, network nodes, or network entities can be referred to as the previously described combo node, combo NF, combined node, integrated NF, or interworking. It can be called an (interworking) node, interworking NF, etc.
  • the NF function illustrated by the combo node may be implemented through interworking between two or more network entities.
  • a "+" symbol or a "/" symbol can be used to indicate NFs that simultaneously support different network systems. For example, if SMF and PGW-C are composed of one combo node, it can be expressed as PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, or SMF+PGW-C.
  • the terminal 101 can establish a session by connecting to a data network (eg, a network providing Internet services) through the 5GS or EPS system.
  • a data network eg, a network providing Internet services
  • the terminal 101 can distinguish each data network using an identifier called a Data Network Name (DNN) or an Access Point Name (APN).
  • DNN can be used in 5GS and APN can be used in EPS.
  • DNN and APN can be used to determine NFs related to the user plane, interfaces between NFs, operator policies, etc. when the terminal 101 connects a network system and a session.
  • the DNN and the APN can be understood as equivalent information and can deliver the same information.
  • the DNN may be used, for example, to select the SMF and UPF(s) for a PDU session, and may be used to select the interface (e.g., N6 interface) between the data network and the UPF for the PDU session. . Additionally, the DNN can be used to determine the mobile communication service provider's policy to apply to the PDU session.
  • the interface e.g., N6 interface
  • combo nodes such as UDM+HSS node, NEF+SCEF node, SMF+PGW-C node, UPF+PGW-C node, etc. will be described with the name “node” omitted for convenience of explanation.
  • the definition of a message defined in one embodiment may be applied in the same sense to other embodiments that use the same message.
  • FIG. 4 is a diagram illustrating the structure of a local breakout roaming wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
  • the local breakout roaming system may consist of a home operator network (Home Public Land Mobile Network, HPLMN, or H-PLMN) and a visited operator network (Visited Public Land Mobile Network, VPLMN, or V-PLMN).
  • Home Public Land Mobile Network HPLMN, or H-PLMN
  • VPLMN Visited Public Land Mobile Network
  • VPLMN's 5GS may include NG-RAN, AMF, and V-PCF, and may also include SMF, UPF, and NEF.
  • VPLMN's EPS may include E-UTRAN, MME, SGW, PGW, SCEF, etc.
  • HPLMN's 5GS may include H-PCF, UDM, etc.
  • HPLMN's EPS may include HSS, etc.
  • FIG. 5 is a diagram illustrating the structure of 5G system non-roaming according to an embodiment of the present disclosure.
  • CM NF may exist in the same software or device as NEF, or may exist in separate software or device.
  • Figure 4 shows an example that exists in the same device as the NEF, but is not limited to this.
  • Nsmf Service-based interface exhibited by SMF
  • FIG. 6 is a diagram illustrating the structure of local breakout roaming in a 5G system according to an embodiment of the present disclosure.
  • 5G systems may include a Security Edge Protection Proxy (SEPP).
  • SEPP Security Edge Protection Proxy
  • HPLMN 5GC NF and VPLMN 5GC NF can communicate through home SEPP (hSEPP, HSEPP, H-SEPP) and visiting SEPP (vSEPP, VSEPP, V-SEPP).
  • FIG. 7 is a diagram illustrating a registration procedure for coverage map transfer according to an embodiment of the present disclosure.
  • the terminal can send a registration request to the AMF.
  • the registration request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container, and CMS address.
  • ⁇ CMT ID is a unique ID that can identify the terminal no matter what type of network (e.g., 5GC or EPC) or operator network (e.g., different PLMN) the terminal connects to CMS. It can mean.
  • the CMT ID can be linked to UDM's subscriber information data (subscription data) through a prior contract or promise between the operator operating the CMS and the operator operating the mobile communication network (core network).
  • the CMT ID can be stored or set in the device or USIM within the terminal.
  • ⁇ CMT Data Container can be configured in a format that allows the terminal and CM NF to read or edit the data inside the container.
  • the terminal may include coverage information (coverage data) needed by the terminal or a request (coverage data request) expressing necessary coverage information in the CMT Data Container.
  • the terminal may include the coverage data request directly in the registration request message without including it in the CMT Data Container.
  • the NF eg, AMF
  • the coverage information type coverage data type
  • coverage information This may include coverage data required area, coverage data required trajectory, coverage data required position, coverage information accuracy (required accuracy level), etc.
  • ⁇ CMS address may be, for example, the FQDN of the CMS.
  • the main authentication procedures required during the terminal registration process can be performed.
  • AMF can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from the UDM or whether it is allowed to obtain information related to the movement of the satellite.
  • AMF can request subscriber information of the terminal from UDM. This request may include at least one of SUPI, CMT ID, and UE Location Information.
  • the terminal location information is information received by the AMF from the terminal or RAN and may include the terminal's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc. SUPI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
  • UDM can provide subscriber information of the terminal to AMF.
  • This subscriber information may refer to information indicating permission to transmit coverage map information among subscriber information related to access and mobility management.
  • AMF can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is allowed to be transmitted in the subscriber information of the terminal exists, the AMF determines whether the terminal provides coverage information. It can be determined that it can be received. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , AMF may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information.
  • AMF can accept the terminal's registration request.
  • the terminal may notify AMF of completion of registration.
  • a coverage map information transfer procedure may be performed.
  • the coverage map information delivery procedure may be initiated by at least one entity among AMF, MME, SMF, and SMF+PGW-C.
  • FIG. 8 is a diagram illustrating a coverage map transfer procedure using a mobility management function according to an embodiment of the present disclosure.
  • Figure 8 illustrates how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the mobility management function.
  • Network entities responsible for mobility management functions may include AMF, MME, etc.
  • AMF Access map information delivery procedure
  • MME Mobility Management Function
  • FIG. 8 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 8 may be performed in another network entity (eg, AMF, MME, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 8, the operation of transmitting a request for coverage data or transmitting coverage data is performed in the CM NF implemented in NEF, and the operation of converting the coverage data request or converting the coverage data is performed in the CM NF implemented in NEF.
  • the functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in AMF.
  • the AMF determines that the terminal is a terminal capable of receiving coverage information, or determines that the terminal is a terminal capable of receiving coverage information and requires additional authentication procedures, etc. (refer to the details described in Figure 7) Coverage information delivery procedures can be initiated in situations (including).
  • AMF may request authentication from CM NF to deliver coverage information. (If additional authentication is not required to deliver coverage information, you can request coverage information delivery.)
  • This request includes at least one of GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information. may be included.
  • GPSI, CMT ID, CMT Data Container, CMS address, and UE Location Information may each be information received from the terminal as described in FIG. 7, and can be provided to the CM NF if AMF determines it is necessary even if not received from the terminal. .
  • the AMF uses the UE Location Information to deliver coverage information. It can be included in the authentication request for
  • CM NF can evaluate the information included in the authentication request for delivering AMF's coverage information and translate and generate it into content to be requested from CMS.
  • the generated information can be included in CMT Data and provided to CMS.
  • CM NF can analyze and edit the coverage data request received and provided by AMF from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage.
  • the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created.
  • Q1 to Q5 may or may not include P1 to P3.
  • Q1 to Q5 may be included in CMT Data and provided to CMS.
  • CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by the AMF to the CM NF includes a Cell ID or TAI, the CM NF may convert it into geographical location coordinates (eg, GPS coordinates or GNSS coordinates).
  • geographical location coordinates eg, GPS coordinates or GNSS coordinates.
  • ⁇ CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It may be AMF or LMF) and can be used by request.
  • request information e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates
  • NWDAF Network Access Management Function
  • CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, transmission of coverage information may be requested.) This request includes at least one of GPSI, CMT ID, CMT Data (may include a coverage data request), and UE Location Information. may be included. GPSI, CMT ID, CMT Data Container (which may include a coverage data request), and UE Location Information may be information received from the terminal as described in FIG. 7 or from AMF as described in step 2, respectively, and may be received from the terminal or Even if it is not received from AMF, it can be provided to CMS if CM NF determines it is necessary. Coverage data request may refer to CMT Data generated by CM NF in step 3. If the CM NF did not perform step 3, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 2 as is.
  • CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information.
  • CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), and UE Location Information in the authentication procedure.
  • CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal.
  • 5a to 5f may be repeated once or more depending on the authentication method used by CMS.
  • CMS can send a response to the authentication request to CM NF.
  • This response may include GPSI, CMT ID, and authentication message.
  • CM NF can deliver an authentication response to AMF.
  • AMF can deliver an authentication response to the terminal.
  • the terminal may transmit a response to the authentication response received from the CMS to the AMF.
  • This response may include GPSI, CMT ID, and authentication message.
  • AMF may deliver a response to CM NF.
  • CM NF can deliver a response to CMS.
  • CMS can send a response to the authentication request to CM NF.
  • This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
  • ⁇ Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 4. Even if CMS does not receive a coverage data request in step 4, it can provide coverage information to CMS at its discretion.
  • the result of authentication for coverage information delivery may include at least one of whether authentication succeeds or fails and the reason for the authentication result.
  • CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
  • CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal.
  • the generated coverage information can be included in the CMT Data Container and provided to AMF.
  • the generated coverage information may not be included in the CMT Data Container but may be included in the authentication response message in step 8. In this case, the AMF can read the coverage information directly.
  • the reverse conversion process of the conversion process performed in step 3 may be performed.
  • CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level.
  • CM NF provides coverage data for the 5 location coordinates received from CMS (e.g. For example, whether coverage exists by time at locations Q1 to Q5, etc.) can be provided to the AMF.
  • step 3 if the CM NF has converted the terminal location information into a format that the CMS can interpret, the coverage data provided by the CMS must be converted back to a format that the network entity can interpret. You can. More specifically, in step 3, the UE Location Information provided by AMF to CM NF included Cell ID or TAI, and CM NF converted it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates) and requested it from CMS. In this case, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to AMF.
  • the UE Location Information provided by AMF to CM NF included Cell ID or TAI, and CM NF converted it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates) and requested it from CMS.
  • CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to AMF.
  • ⁇ CM NF provides information necessary for the creation of coverage data (e.g., converting the geographic location coordinates of the terminal into location information of the terminal) to other network entities (e.g., it may be NWDAF, AMF, LMF). It is available upon request.
  • CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data) may be included. AMF performs deregistration of the terminal, response to the mobility registration update request of the terminal, and power saving mode of the terminal based on the results of authentication and/or coverage data for delivering coverage information. mode) can make judgments about application, etc.
  • ⁇ Coverage data may refer to CMT Data generated by CM NF in step 7. If the CM NF did not perform step 7, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 6 as is.
  • the result of authentication for coverage information delivery may include at least one of whether authentication succeeds or fails and the reason for the authentication result.
  • the result of authentication for delivering coverage information may be the same as the result of authentication for delivering coverage information received from CMS in step 6, or may be determined by the CM NF based on the content received in step 6. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 8, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received, an indicator is additionally provided indicating that deregistration of the terminal is not needed, or a reason for deregistration of the terminal is not needed. may also be provided.
  • AMF may request that the CM NF be notified if changes occur related to the results of certification for delivering coverage data and/or coverage information.
  • CM NF may request AMF to receive notification when changes occur related to access and mobility of the terminal.
  • AMF may request that CM NF no longer receive notifications of changes related to coverage data and/or the results of certification for the delivery of coverage information.
  • CM NF may request that AMF no longer receive notifications of changes related to access and mobility of the terminal.
  • AMF can deliver a response to the authentication request for delivering coverage information to the terminal.
  • This response may include at least one of GPSI, CMT ID, authentication message, and authentication result for delivering coverage information.
  • the result of authentication for coverage information delivery may include at least one of whether authentication succeeds or fails and the reason for the authentication result.
  • the result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the CM NF in step 8, or may be determined by the AMF based on the content received in step 8. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 8, the AMF is configured to operate in a state in which the terminal has not received coverage information. If it is determined that registration management or session management can be received, an indicator is additionally provided indicating that deregistration of the terminal is not needed, or a reason for deregistration of the terminal is not needed.
  • AMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge.
  • Information related to the capabilities of the terminal may be provided by being included in information such as UE Capability in a registration request message sent from the terminal to the AMF.
  • CM NF may request AMF to deliver coverage information to the terminal.
  • This request may include at least one of GPSI, CMT ID, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message as is. In this case, the AMF may read the coverage information directly.
  • AMF can deliver coverage information to the terminal.
  • a UE Configuration Update procedure may be performed, and at this time, at least one of GPSI, CMT ID, and CMT Data Container (coverage data) may be included. Coverage information may not be included in the CMT Data Container but may be included in the message.
  • the terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the result of authentication for delivering coverage information received in step 11.
  • the terminal For example, if the terminal is moving away from the coverage of the currently connected access network and can know that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to that access network. can be moved.
  • the terminal if it is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this coverage data that it has stored, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
  • an indicator indicating that the terminal is not allowed at the current location with an authentication result of failure in step 11, or that deregistration of the terminal is not necessary. (or the reason for notifying this) is received, and if the terminal determines that it can receive registration management or session management without receiving coverage information, it can continue to maintain connection to the core network without deregistering the terminal. .
  • the terminal may initiate a deregistration procedure.
  • FIG. 9 is a diagram illustrating a method of transferring coverage map information in a PDU session management procedure according to an embodiment of the present disclosure.
  • the method of FIG. 9 has the feature that the operation performed by the AMF during the registration procedure in FIGS. 7 and 8 is replaced by the operation performed by the SMF during the PDU session establishment procedure. Accordingly, some of the methods of FIG. 9 may include operations common to the methods of FIGS. 7 and 8, and some descriptions may be omitted.
  • FIG. 9 illustrates how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the session management function.
  • the network entity responsible for the session management function may include SMF, etc., and FIG. 9 illustrates the case of SMF as an example, but is not limited thereto.
  • Figure 9 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 9 may be performed in another network entity (e.g., SMF, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 9, the operation of transmitting a request for coverage data or delivering coverage data is performed in the CM NF implemented in NEF, and the conversion of the coverage data request or the conversion of coverage data is performed in the CM NF implemented in NEF.
  • the functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in SMF.
  • the terminal may transmit a PDU session establishment request to the AMF.
  • This request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), and CMS address.
  • CMT Cross Map Transfer
  • CMT Data Container coverage data request
  • CMS address CMS address
  • AMF may send a request to create a session management context for a PDU session to the SMF.
  • This request may include at least one of CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information.
  • CMT ID, CMT Data Container, CMS address, and UE Location Information may be information received from the terminal as described in Figures 7 and 8, respectively. Even if not received from the terminal, they can be provided to the CM NF if AMF determines it is necessary. there is. For example, even if the AMF has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by CMS and/or CM NF, it uses the UE Location Information to deliver coverage information. It can be included in the authentication request for
  • the SMF can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from the UDM or whether it is allowed to obtain information related to the movement of the satellite.
  • the SMF can request the subscriber information of the terminal from the UDM. This request may include at least one of SUPI, DNN, S-NSSAI, CMT ID, and UE Location Information.
  • the terminal location information is information received by the AMF from the terminal or RAN and may include the terminal's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc.
  • SUPI, DNN, S-NSSAI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
  • UDM can provide subscriber information of the terminal to SMF.
  • This subscriber information may refer to information indicating permission to transmit coverage map information among session management-related subscriber information.
  • the SMF can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is permitted to be transmitted in the subscriber information of the terminal exists, the SMF determines whether the terminal provides coverage information. It can be determined that it can be received. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , the SMF may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information. SMF may request authentication for delivering coverage information to CM NF.
  • This request includes GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, UE Location Information, PEI, UE.
  • At least one IP address may be included. For example, if a terminal is using one or more PDU sessions using the same CMT ID, or if more than one terminal is using the same CMT ID, SMF The UE IP address (or PDU Session ID) can be provided to identify the session.
  • GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, and UE IP address may be information received from the terminal and/or AMF as described in Figures 7 and 8, respectively, and may be received from the terminal and/or AMF Even if it is not received, it can be provided to CM NF if SMF determines it is necessary. For example, even if the SMF has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by the CMS and/or CM NF, it uses the UE Location Information to deliver the coverage information. It can be included in the authentication request for
  • CM NF can evaluate the information included in the authentication request for delivering SMF's coverage information and translate and generate the content to be requested from CMS.
  • the generated information can be included in CMT Data and provided to CMS.
  • CM NF can analyze and edit the coverage data request received and provided by SMF from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage.
  • the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created.
  • Q1 to Q5 may or may not include P1 to P3.
  • Q1 to Q5 may be included in CMT Data and provided to CMS.
  • CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by the SMF to the CM NF includes Cell ID or TAI, the CM NF may convert it into geographical location coordinates (eg, GPS coordinates or GNSS coordinates).
  • geographical location coordinates eg, GPS coordinates or GNSS coordinates.
  • ⁇ CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It can be used by requesting it from AMF, SMF, or LMF).
  • request information e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates
  • NWDAF Network Access Management Function
  • CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, you can request coverage information transmission.) This request includes GPSI, CMT ID, CMT Data (may include coverage data request), UE Location Information, PEI, At least one of the UE IP addresses may be included. GPSI, CMT ID, CMT Data Container (which may include a coverage data request), UE Location Information, PEI, and UE IP address are received from the terminal as described in Figures 7 and 8, respectively, or as described in steps 2 and 4. As such, it may be information received from AMF and/or SMF, and even if not received from the terminal, AMF, and/or SMF, it may be provided to CMS if CM NF determines it is necessary. Coverage data request may refer to CMT Data generated by CM NF in step 5. If the CM NF did not perform step 5, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 4 as is.
  • CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information.
  • CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), UE Location Information, PEI, and UE IP address in the authentication procedure.
  • the CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal or the UE IP address. 7a to 7h may be repeated once or more depending on the authentication method used by CMS.
  • CMS can send a response to the authentication request to CM NF.
  • This response may include GPSI, CMT ID, and authentication message.
  • CM NF can deliver an authentication response to SMF.
  • SMF can deliver an authentication response to AMF.
  • AMF can deliver an authentication response to the terminal.
  • the terminal may transmit a response to the authentication response received from the CMS to the AMF.
  • This response may include GPSI, CMT ID, and authentication message.
  • AMF can deliver a response to SMF.
  • SMF can deliver a response to CM NF.
  • CM NF can deliver a response to CMS.
  • CMS can send a response to the authentication request to CM NF.
  • This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
  • ⁇ Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 6. Even if CMS does not receive a coverage data request in step 6, it can provide coverage information to CMS at its discretion.
  • the result of authentication for coverage information delivery may include at least one of whether authentication succeeds or fails and the reason for the authentication result.
  • CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
  • CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal.
  • the generated coverage information can be included in the CMT Data Container and provided to the SMF.
  • the generated coverage information may not be included in the CMT Data Container but may be directly included in the authentication response message in step 8.
  • the SMF if delivered to the AMF may also be included in the AMF
  • the reverse conversion process of the conversion process performed in step 5 may be performed.
  • CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level.
  • CM NF provides coverage data for the 5 location coordinates received from CMS (e.g. For example, whether coverage exists by time at locations Q1 to Q5, etc.) can be provided to the SMF.
  • step 5 if the CM NF has converted the terminal location information into a format that the CMS can interpret, the coverage data provided by the CMS must be converted back into a format that the network entity can interpret. You can. More specifically, in step 4, the UE Location Information provided by the SMF to the CM NF included Cell ID or TAI, and the CM NF converted it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates) and requested it from CMS. In this case, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to SMF.
  • geographic location coordinates e.g., GPS coordinates or GNSS coordinates
  • ⁇ CM NF provides information necessary for the creation of coverage data (e.g., converting the geographic location coordinates of the terminal into location information of the terminal) to other network entities (e.g., it may be NWDAF, AMF, LMF). It is available upon request.
  • CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data), CMT Data Container (coverage data) may be included. SMF performs terminal deregistration, PDU session release, user plane resource release, and power saving mode of the terminal based on the results of authentication and/or coverage data for delivering coverage information. mode) can make judgments about application, etc.
  • ⁇ Coverage data may refer to CMT Data generated by CM NF in step 9. If the CM NF did not perform step 9, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 8 as is.
  • the result of authentication for coverage information delivery may include at least one of whether authentication succeeds or fails and the reason for the authentication result.
  • the result of the authentication for coverage information delivery may be the same as the result of the authentication for coverage information delivery received from CMS in step 8, or may be determined by the CM NF based on the content received in step 8. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 8, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received in the A cause may be provided for deregistration not needed and/or PDU Session release not needed.
  • CMS may request SMF to be notified when changes related to session management occur through UDM.
  • CMS may request that SMF no longer receive notifications of changes related to session management through UDM.
  • the SMF may request that the CM NF be notified when changes occur related to the results of authentication for delivering coverage data and/or coverage information.
  • CM NF may request SMF to receive notification when changes related to session management occur.
  • the SMF may request that the CM NF no longer receive notification of changes related to coverage data and/or the results of authentication for the delivery of coverage information.
  • the CM NF may request that the SMF no longer receive notifications of changes related to session management.
  • the SMF can continue the PDU session establishment procedure and deliver the authentication result and coverage information for delivering coverage information to the terminal.
  • the SMF may provide the AMF with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message as is. In this case, the AMF may read the coverage information directly.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • the result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the CM NF in step 10, or may be determined by the SMF based on the content received in step 10. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 10, the SMF is configured to operate in a state in which the terminal has not received coverage information.
  • an indicator indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDU session release (release) is not needed is additionally provided, or the terminal's A cause may be provided for deregistration not needed and/or PDU Session release not needed.
  • SMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge.
  • Information related to such UE capabilities may be provided by being included in information such as UE Capability in the PDU session establishment request message sent from the UE or AMF to the SMF.
  • AMF may provide the RAN with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • the result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the SMF in step 15a, or may be determined by the AMF based on the content received in step 15a. For example, if the SMF provides a reason of not allowed at current location with an authentication result of failure in step 15a, the AMF provides the reason for not allowing the terminal to receive coverage information. If it is determined that registration management or session management is possible, an indicator is additionally provided indicating that deregistration of the terminal is not needed and/or PDU session release is not needed, or registration of the terminal is provided.
  • a cause may be provided for deregistration not needed and/or PDU Session release not needed.
  • AMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge.
  • Information related to the capabilities of the terminal may be provided by being included in information such as UE Capability in a registration request message or PDU session establishment request message sent from the terminal to the AMF.
  • the RAN may provide the UE with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message.
  • the terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the authentication result for delivering the coverage information received together.
  • the terminal For example, if the terminal is moving away from the coverage of the currently connected access network and can know that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to that access network. can be moved.
  • the terminal if it is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this coverage data that it has stored, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
  • the terminal performs registration management or session without receiving coverage information. If it is determined that it can be managed, it can continue to maintain connection to the core network without deregistering the terminal or releasing the PDU session.
  • the terminal if the terminal receives an authentication result of failure in step 15c and determines that the terminal cannot operate without receiving coverage data, the terminal initiates a deregistration procedure or a PDU session release procedure. can do.
  • SMF can notify CMS if an event for which CMS has requested notification occurs in step 11.
  • This notification may include at least one of GPSI, CMT ID, and UE IP address.
  • FIG. 10 is a diagram illustrating a method of transferring coverage map information in a PDN connection management procedure according to an embodiment of the present disclosure.
  • the method of FIG. 10 has the feature that the operations performed by AMF during the registration procedure in FIGS. 7, 8, and 9 are replaced by the operations performed by SMF+PGW-C during the PDN connection establishment procedure. Accordingly, some of the methods of FIG. 10 may include common operations with the methods of FIGS. 7, 8, and 9, and some descriptions may be omitted.
  • Figure 10 explains how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the session management function.
  • the network entity responsible for the session management function may include SMF+PGW-C, etc.
  • SMF+PGW-C the case of SMF+PGW-C is explained as an example, but is not limited thereto.
  • FIG. 10 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 10 may be performed in another network entity (e.g., SMF, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 10, the operation of transmitting a request for coverage data or delivering coverage data is performed in the CM NF implemented in NEF, and the conversion of the coverage data request or the conversion of coverage data is performed in the CM NF implemented in the NEF.
  • the functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in SMF+PGW-C.
  • the terminal can connect to the MME through RAN and perform the Attach procedure.
  • Attach procedure In addition to 0a to 0d, other procedures required for the attach procedure may be performed and may be omitted from the description.
  • the UE can send an Attach request to the MME through the RAN.
  • This request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), and CMS address.
  • CMT Cross Map Transfer
  • CMT Data Container coverage data request
  • CMS address CMS address
  • the MME can request session creation from SMF+PGW-C.
  • This request may include at least one of CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information.
  • CMT ID, CMT Data Container, CMS address, and UE Location Information may be information received from the terminal as described in Figures 7, 8, and 9, respectively.
  • the MME determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by the CMS and/or CM NF, it uses the UE Location Information to deliver the coverage information. It can be included in the authentication request for
  • SMF+PGW-C can respond to a session creation request.
  • the MME can transmit an Attach acceptance through the RAN.
  • the UE can respond with Attach completion to the MME through the RAN.
  • SMF+PGW-C can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from UDM or whether it is allowed to obtain information related to the movement of the satellite.
  • SMF+PGW-C can request subscriber information of the terminal from UDM. This request may include at least one of SUPI, DNN, S-NSSAI, CMT ID, and UE Location Information.
  • Terminal location information is information received by the MME from the UE or RAN and may include the UE's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc.
  • SUPI, DNN, S-NSSAI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
  • UDM can provide terminal subscriber information to SMF+PGW-C.
  • This subscriber information may refer to information indicating permission to transmit coverage map information among session management-related subscriber information.
  • SMF+PGW-C can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is allowed to be transmitted in the subscriber information of the terminal exists, SMF+PGW-C It may be determined that the terminal can receive coverage information. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , SMF+PGW-C may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information.
  • SMF+PGW-C can request authentication from CM NF to deliver coverage information. (If additional authentication is not required to deliver coverage information, you can request coverage information delivery.)
  • This request includes GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, UE Location Information, PEI, UE.
  • At least one IP address may be included. For example, when a terminal is using more than one PDN connection using the same CMT ID, or when more than one terminal is using the same CMT ID, SMF connects a specific terminal and/or a specific PDN connection used by a specific terminal.
  • the UE IP address (or PDU connection ID) can be provided for identification.
  • GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, and UE IP address may be information received from the terminal and/or MME as described in Figures 7, 8, and 9, respectively. /Or, even if it is not received from the MME, it can be provided to the CM NF if SMF+PGW-C is deemed necessary. For example, even if SMF+PGW-C has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to delivery of coverage information performed by CMS and/or CM NF, it provides UE Location Information. It can be included in the authentication request for delivering coverage information.
  • CM NF can evaluate the information included in the authentication request for delivering coverage information of SMF+PGW-C and translate and generate the content to be requested from CMS.
  • the generated information can be included in CMT Data and provided to CMS.
  • CM NF can analyze and edit the coverage data request received and provided by SMF+PGW-C from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage.
  • the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created.
  • Q1 to Q5 may or may not include P1 to P3.
  • Q1 to Q5 may be included in CMT Data and provided to CMS.
  • CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by SMF+PGW-C to CM NF includes Cell ID or TAI, CM NF can convert it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates). there is.
  • geographic location coordinates e.g., GPS coordinates or GNSS coordinates.
  • ⁇ CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It can be used by requesting it from AMF, MME, SMF+PGW-C, or LMF).
  • request information e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates
  • NWDAF Network Access Management Function
  • CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, you can request coverage information transmission.) This request includes GPSI, CMT ID, CMT Data (may include coverage data request), UE Location Information, PEI, At least one of the UE IP addresses may be included.
  • GPSI, CMT ID, CMT Data Container (which may include a coverage data request), UE Location Information, PEI, and UE IP address are received from the terminal as described in Figures 7, 8, and 9, respectively, and in step 0b and As described in step 2, this may be information received from the MME and/or SMF+PGW-C, and may be provided to CMS if the CM NF determines it is necessary even if it is not received from the terminal, MME, and/or SMF+PGW-C. You can.
  • Coverage data request may refer to CMT Data generated by CM NF in step 3. If the CM NF did not perform step 3, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 2 as is.
  • CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information.
  • CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), UE Location Information, PEI, and UE IP address in the authentication procedure.
  • the CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal or the UE IP address.
  • 5a to 5f may be repeated once or more depending on the authentication method used by CMS.
  • CMS can send a response to the authentication request to CM NF through SMF+PGW-C.
  • This response may include GPSI, CMT ID, and authentication message.
  • SMF+PGW-C can deliver an authentication response to the MME through SGW.
  • the MME can deliver an authentication response to the terminal.
  • the terminal may transmit a response to the authentication response received from CMS to the MME.
  • This response may include GPSI, CMT ID, and authentication message.
  • the MME can deliver a response to SMF+PGW-C through SGW.
  • SMF+PGW-C can deliver a response to CMS through CM NF.
  • CMS can send a response to the authentication request to CM NF.
  • This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
  • ⁇ Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 4. Even if CMS does not receive a coverage data request in step 4, it can provide coverage information to CMS at its discretion.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
  • CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal.
  • the generated coverage information can be included in the CMT Data Container and provided to SMF+PGW-C.
  • the generated coverage information may not be included in the CMT Data Container but may be directly included in the authentication response message in step 8. In this case, the coverage information can be read directly by SMF+PGW-C (if delivered to the MME, the MME may also be included). there is.
  • the reverse conversion process of the conversion process performed in step 3 may be performed.
  • the CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level. It can be analyzed that 5 location coordinates are needed to do this.
  • the CM NF provides coverage data for the 5 location coordinates received from CMS (e.g., by time at positions Q1 to Q5). (existence of coverage, etc.) can be provided to SMF+PGW-C.
  • the coverage data provided by the CMS must be converted back into a format that the network entity can interpret. You can. More specifically, the UE Location Information provided by SMF+PGW-C to CM NF in Step 4 included Cell ID or TAI, and CM NF converted this into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates). If a request is made to CMS, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to SMF+PGW-C.
  • the UE Location Information provided by SMF+PGW-C to CM NF in Step 4 included Cell ID or TAI, and CM NF converted this into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates).
  • ⁇ CM NF may be another network entity (e.g., NWDAF, AMF, MME, LMF) that provides information necessary for the generation of coverage data (e.g., an operation to convert the geographical location coordinates of the terminal into location information of the terminal). ) can be used by request.
  • NWDAF wireless fidelity
  • AMF Access Management Function
  • MME Mobility Management Entity
  • LMF Layer Management Function
  • CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data), CMT Data Container (coverage data) may be included. SMF+PGW-C performs terminal deregistration, PDN connection release, user plane resource release, and bearer based on the results of authentication and/or coverage data for delivering coverage information. ) It is possible to make a decision on release, application of the terminal's power saving mode, etc.
  • ⁇ Coverage data may refer to CMT Data generated by CM NF in step 7. If the CM NF did not perform step 7, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 6 as is.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • the result of authentication for delivering coverage information may be the same as the result of authentication for delivering coverage information received from CMS in step 6, or may be determined by the CM NF based on the content received in step 6. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 6, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received in It may also provide a reason for deregistration not needed and/or PDN connection release not needed.
  • CMS may request SMF+PGW-C to be notified when changes related to session management occur through UDM.
  • CMS may request that SMF+PGW-C no longer receive notification of changes related to session management through UDM.
  • SMF+PGW-C may request that CM NF be notified if changes occur related to the results of authentication for delivering coverage data and/or coverage information.
  • CM NF may request SMF+PGW-C to receive notification when changes related to session management occur.
  • SMF+PGW-C may request that CM NF no longer receive notification of changes related to coverage data and/or the results of authentication for delivery of coverage information.
  • CM NF may request that SMF+PGW-C no longer receive notifications of changes related to session management.
  • SMF+PGW-C can deliver authentication results and coverage information to the terminal while continuing the PDN connection establishment procedure (which may include the procedure of modifying the bearer without QoS update initiated by the PDN GW). there is.
  • SMF+PGW-C can provide at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) to the MME through SGW.
  • GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) can be included and provided in the PCO (or ePCO). Coverage information may not be included in the CMT Data Container but may be included in the message.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • the result of authentication for delivering coverage information is the same as the result of authentication for delivering coverage information received from CM NF in Step 8, or the result determined by SMF+PGW-C based on the content received in Step 8. It may be possible. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 8, SMF+PGW-C allows the terminal to provide coverage information.
  • an indicator is added indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDN connection release (release) is not needed. It may also provide a reason for deregistration of the terminal not needed (deregistration not needed) and/or PDN connection release not needed (PDN connection release not needed).
  • SMF+PGW-C receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it performs registration management or session management without the terminal receiving coverage information. You can judge that you can receive it.
  • Information related to these UE capabilities may be provided by being included in information such as UE Capability in the PDN connection establishment request message sent from the UE or MME to the SMF+PGW-C.
  • the MME may provide at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) to the UE through RAN.
  • GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) can be included and provided in the PCO (or ePCO). Coverage information may not be included in the CMT Data Container but may be included in the message.
  • the result of authentication for coverage information delivery may include at least one of success or failure of authentication and the cause of the authentication result.
  • the result of authentication for transmitting coverage information may be the same as the result of authentication for transmitting coverage information received from SMF+PGW-C in step 13a, or may be determined by the MME based on the content received in step 13a. there is. For example, if SMF+PGW-C provides a reason of not allowed at current location with an authentication result of failure in step 13a, the MME sends coverage information to the terminal.
  • an indicator is additionally provided indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDN connection release (release) is not needed. Alternatively, it may provide a reason for deregistration of the terminal not needed (deregistration not needed) and/or PDN connection release not needed (PDN connection release not needed).
  • the MME receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge. Information related to such UE capabilities may be provided by being included in information such as UE Capability in a registration request message or PDN connection establishment request message sent from the UE to the MME.
  • the UE may provide at least one of GPSI, CMT ID, authentication message, and CMT Data Container (coverage data) to the MME through the RAN.
  • GPSI, CMT ID, authentication message, and CMT Data Container (coverage data) may be included and provided in the PCO (or ePCO).
  • the MME can provide at least one of GPSI, CMT ID, authentication message, and CMT Data Container to SMF+PGW-C through SGW.
  • GPSI, CMT ID, authentication message, and CMT Data Container can be included and provided in PCO (or ePCO).
  • the terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the authentication result for delivering the coverage information received together.
  • the terminal For example, if the terminal is moving away from the coverage of the currently connected access network, and if it can be seen that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to the corresponding access network. can be moved.
  • the terminal if it is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this stored coverage data, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
  • the terminal if the terminal receives an authentication result of failure in step 13b and determines that the terminal will not be able to operate without receiving coverage data, the terminal initiates a deregistration procedure or a PDN disconnection procedure. can do.
  • SMF+PGW-C can notify CMS in step 9 if an event for which CMS has requested notification occurs.
  • This notification may include at least one of GPSI, CMT ID, and UE IP address.
  • the network and core network included in the embodiments of the present disclosure may be a concept including a network device.
  • a mobility management device or mobility management function
  • a location management device or a location management function
  • a gateway mobile location center etc. may each be configured as separate devices and may be configured to be included in a network device.
  • Figure 11 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
  • the terminal may include a terminal receiving unit 1110, a terminal transmitting unit 1120, and a terminal processing unit (control unit) 1130.
  • the terminal receiving unit 1110 and the terminal transmitting unit 1120 may be referred to together as a transmitting and receiving unit. According to the above-described communication method of the terminal, the terminal receiving unit 1110, terminal transmitting unit 1120, and terminal processing unit 1130 may operate.
  • the components of the terminal are not limited to the examples described above.
  • the terminal may include more components (eg, memory, etc.) or fewer components than the components described above.
  • the terminal receiving unit 1110, the terminal transmitting unit 1120, and the terminal processing unit 1130 may be implemented in the form of a single chip.
  • the terminal receiver 1110 and the terminal transmitter 1120 can transmit and receive signals to and from the base station.
  • the signal may include control information and data.
  • the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency.
  • this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
  • the transceiver may receive a signal through a wireless channel and output it to the terminal processing unit 1130, and transmit the signal output from the terminal processing unit 1130 through a wireless channel.
  • Memory (not shown) can store programs and data necessary for the operation of the terminal. Additionally, the memory may store control information or data included in signals obtained from the terminal. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
  • the terminal processing unit 1130 can 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 1130 may be implemented as a circuit, an application-specific integrated circuit, or at least one processor.
  • the terminal processing unit 1130 may be implemented as a control unit or one or more processors.
  • Figure 12 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
  • the base station may include a base station receiving unit 1210, a base station transmitting unit 1220, and a base station processing unit (control unit) 1230.
  • the base station receiving unit 1210 and the base station transmitting unit 1220 may be referred to together as a transmitting and receiving unit. According to the above-described communication method of the base station, the base station receiving unit 1210, base station transmitting unit 1220, and base station processing unit 1230 of the base station may operate. However, the components of the base station are not limited to the above examples. For example, the base station may include more components (eg, memory, etc.) or fewer components than the components described above. In addition, the base station receiving unit 1210, the base station transmitting unit 1220, and the base station processing unit 1230 may be implemented in the form of a single chip.
  • the base station receiver 1210 and the base station transmitter 1220 can transmit and receive signals to and from a terminal and/or network entity.
  • the signal may include control information and data.
  • the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency.
  • this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
  • the transceiver may receive a signal through a wired or wireless channel and output it to the base station processing unit 1230, and transmit the signal output from the base station processing unit 1230 through a wired or wireless channel.
  • Memory can store programs and data necessary for the operation of the base station. Additionally, the memory may store control information or data included in signals obtained from the base station. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
  • the base station processing unit 1230 can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure.
  • the base station processing unit 1230 may be implemented as a control unit or one or more processors.
  • FIG. 13 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
  • a network entity may include a network entity receiving unit 1310, a network entity transmitting unit 1320, and a network entity processing unit (control unit) 1330.
  • network entities may include AMF, SMF, UPF, DN, NSSF, NEF, AUSF, NRF, PCF, UDM, AF, etc.
  • the network entity receiving unit 1310 and the network entity transmitting unit 1320 may be referred to together as a transmitting/receiving unit. According to the communication method of the network entity described above, the network entity receiving unit 1310, the network entity transmitting unit 1320, and the network entity processing unit 1330 of the network entity may operate. However, the components of the network entity are not limited to the examples described above. For example, a network entity may include more components (eg, memory, etc.) or fewer components than the components described above. In addition, the network entity receiving unit 1310, the network entity transmitting unit 1320, and the network entity processing unit 1330 may be implemented in the form of a single chip.
  • the network entity receiving unit 1310 and the network entity transmitting unit 1320 may transmit and receive signals with a base station and/or other network entities.
  • the signal may include control information and data.
  • the transceiver may receive a signal through a wired or wireless channel and output it to the network entity processing unit 1330, and transmit the signal output from the network entity processing unit 1330 through a wired or wireless channel.
  • Memory may store programs and data necessary for the operation of the network entity. Additionally, the memory may store control information or data included in signals obtained from a network entity. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
  • the network entity processing unit 1330 may control a series of processes so that the network entity can operate according to the above-described embodiment of the present disclosure.
  • the network entity processing unit 1330 may be implemented as a control unit or one or more processors.
  • a computer-readable storage medium that stores one or more programs (software modules) may be provided.
  • One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution).
  • 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.
  • These programs may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.
  • non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may
  • the program may be distributed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present disclosure.
  • a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present disclosure.
  • Embodiments of the present disclosure may be implemented by combining some or all of the content included in each embodiment within the scope without impairing the essence of the present disclosure.

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method for operating an access and mobility management function (AMF) in a wireless communication system, according to one embodiment, comprises the steps of: transmitting, to a network exposure function (NEF), an authentication request message including a coverage information transmission ID and a coverage information request for transmitting coverage information of a satellite radio access network (RAN); receiving, from a coverage information server, the authentication result and/or the coverage information of a user equipment (UE) corresponding to the coverage information transmission ID; and transmitting, to the UE, the authentication result and/or the coverage information.

Description

무선통신 시스템에서 커버리지 정보 제공 방법 및 장치Method and device for providing coverage information in a wireless communication system
본 개시는 무선통신 시스템에서 커버리지 정보를 제공하는 방법 및 장치에 관한 것이다.This disclosure relates to a method and device for providing coverage information in a wireless communication system.
5G 이동통신 기술은 빠른 전송 속도와 새로운 서비스가 가능하도록 넓은 주파수 대역을 정의하고 있으며, 3.5 기가헤르츠(3.5GHz) 등 6GHz 이하 주파수('Sub 6GHz') 대역은 물론 28GHz와 39GHz 등 밀리미터파(㎜Wave)로 불리는 초고주파 대역('Above 6GHz')에서도 구현이 가능하다. 또한, 5G 통신 이후(Beyond 5G)의 시스템이라 불리어지는 6G 이동통신 기술의 경우, 5G 이동통신 기술 대비 50배 빨라진 전송 속도와 10분의 1로 줄어든 초저(Ultra Low) 지연시간을 달성하기 위해 테라헤르츠(Terahertz, THz) 대역(예를 들어, 95GHz에서 3 테라헤르츠 대역과 같은)에서의 구현이 고려되고 있다.5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz (THz) bands (e.g., 3 terahertz bands at 95 GHz) is being considered.
5G 이동통신 기술의 초기에는, 초광대역 서비스(enhanced Mobile BroadBand, eMBB), 고신뢰/초저지연 통신(Ultra-Reliable Low-Latency Communications, URLLC), 대규모 기계식 통신 (massive Machine-Type Communications, mMTC)에 대한 서비스 지원과 성능 요구사항 만족을 목표로, 초고주파 대역에서의 전파의 경로손실 완화 및 전파의 전달 거리를 증가시키기 위한 빔포밍(Beamforming) 및 거대 배열 다중 입출력(Massive MIMO), 초고주파수 자원의 효율적 활용을 위한 다양한 뉴머롤로지 지원(복수 개의 서브캐리어 간격 운용 등)와 슬롯 포맷에 대한 동적 운영, 다중 빔 전송 및 광대역을 지원하기 위한 초기 접속 기술, BWP(Band-Width Part)의 정의 및 운영, 대용량 데이터 전송을 위한 LDPC(Low Density Parity Check) 부호와 제어 정보의 신뢰성 높은 전송을 위한 폴라 코드(Polar Code)와 같은 새로운 채널 코딩 방법, L2 선-처리(L2 pre-processing), 특정 서비스에 특화된 전용 네트워크를 제공하는 네트워크 슬라이싱(Network Slicing) 등에 대한 표준화가 진행되었다.In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.
현재, 5G 이동통신 기술이 지원하고자 했던 서비스들을 고려하여 초기의 5G 이동통신 기술 개선(improvement) 및 성능 향상(enhancement)을 위한 논의가 진행 중에 있으며, 차량이 전송하는 자신의 위치 및 상태 정보에 기반하여 자율주행 차량의 주행 판단을 돕고 사용자의 편의를 증대하기 위한 V2X(Vehicle-to-Everything), 비면허 대역에서 각종 규제 상 요구사항들에 부합하는 시스템 동작을 목적으로 하는 NR-U(New Radio Unlicensed), NR 단말 저전력 소모 기술(UE Power Saving), 지상 망과의 통신이 불가능한 지역에서 커버리지 확보를 위한 단말-위성 직접 통신인 비 지상 네트워크(Non-Terrestrial Network, NTN), 위치 측위(Positioning) 등의 기술에 대한 물리계층 표준화가 진행 중이다. Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system 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 for technology is in progress.
뿐만 아니라, 타 산업과의 연계 및 융합을 통한 새로운 서비스 지원을 위한 지능형 공장 (Industrial Internet of Things, IIoT), 무선 백홀 링크와 액세스 링크를 통합 지원하여 네트워크 서비스 지역 확장을 위한 노드를 제공하는 IAB(Integrated Access and Backhaul), 조건부 핸드오버(Conditional Handover) 및 DAPS(Dual Active Protocol Stack) 핸드오버를 포함하는 이동성 향상 기술(Mobility Enhancement), 랜덤액세스 절차를 간소화하는 2 단계 랜덤액세스(2-step RACH for NR) 등의 기술에 대한 무선 인터페이스 아키텍쳐/프로토콜 분야의 표준화 역시 진행 중에 있으며, 네트워크 기능 가상화(Network Functions Virtualization, NFV) 및 소프트웨어 정의 네트워킹(Software-Defined Networking, SDN) 기술의 접목을 위한 5G 베이스라인 아키텍쳐(예를 들어, Service based Architecture, Service based Interface), 단말의 위치에 기반하여 서비스를 제공받는 모바일 엣지 컴퓨팅(Mobile Edge Computing, MEC) 등에 대한 시스템 아키텍쳐/서비스 분야의 표준화도 진행 중이다.In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.
이와 같은 5G 이동통신 시스템이 상용화되면, 폭발적인 증가 추세에 있는 커넥티드 기기들이 통신 네트워크에 연결될 것이며, 이에 따라 5G 이동통신 시스템의 기능 및 성능 강화와 커넥티드 기기들의 통합 운용이 필요할 것으로 예상된다. 이를 위해, 증강현실(Augmented Reality, AR), 가상현실(Virtual Reality, VR), 혼합 현실(Mixed Reality, MR) 등을 효율적으로 지원하기 위한 확장 현실(eXtended Reality, XR), 인공지능(Artificial Intelligence, AI) 및 머신러닝(Machine Learning, ML)을 활용한 5G 성능 개선 및 복잡도 감소, AI 서비스 지원, 메타버스 서비스 지원, 드론 통신 등에 대한 새로운 연구가 진행될 예정이다.When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.
또한, 이러한 5G 이동통신 시스템의 발전은 6G 이동통신 기술의 테라헤르츠 대역에서의 커버리지 보장을 위한 신규 파형(Waveform), 전차원 다중입출력(Full Dimensional MIMO, FD-MIMO), 어레이 안테나(Array Antenna), 대규모 안테나(Large Scale Antenna)와 같은 다중 안테나 전송 기술, 테라헤르츠 대역 신호의 커버리지를 개선하기 위해 메타물질(Metamaterial) 기반 렌즈 및 안테나, OAM(Orbital Angular Momentum)을 이용한 고차원 공간 다중화 기술, RIS(Reconfigurable Intelligent Surface) 기술 뿐만 아니라, 6G 이동통신 기술의 주파수 효율 향상 및 시스템 네트워크 개선을 위한 전이중화(Full Duplex) 기술, 위성(Satellite), AI(Artificial Intelligence)를 설계 단계에서부터 활용하고 종단간(End-to-End) AI 지원 기능을 내재화하여 시스템 최적화를 실현하는 AI 기반 통신 기술, 단말 연산 능력의 한계를 넘어서는 복잡도의 서비스를 초고성능 통신과 컴퓨팅 자원을 활용하여 실현하는 차세대 분산 컴퓨팅 기술 등의 개발에 기반이 될 수 있을 것이다.In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .
나아가, 위성통신 기술의 고도화로 인해 제한적으로만 도입되었던 위성통신 기술을 이동통신망에 통합하기 위한 노력이 진행되고 있다. 특히, 3GPP(3rd generation partnership project)에서는 단말이 위성 액세스 네트워크(satellite RAN)를 통해 네트워크(일 실시예에 따르면, 5G 코어 네트워크)에 연결될 수 있도록 하는 방안을 개발 중에 있다.Furthermore, due to the advancement of satellite communication technology, efforts are being made to integrate satellite communication technology, which has been introduced only to a limited extent, into mobile communication networks. In particular, the 3rd generation partnership project (3GPP) is developing a method that allows a terminal to connect to a network (according to one embodiment, a 5G core network) through a satellite access network (satellite RAN).
본 개시는 무선통신 시스템에서 커버리지 정보를 제공하는 방법 및 장치를 제공한다.This disclosure provides a method and device for providing coverage information in a wireless communication system.
본 개시의 일 실시예에 따른 무선통신 시스템에서 AMF(access and mobility management function)의 동작 방법은, NEF(network exposure function)에게, 위성 무선 액세스 네트워크(satellite radio access network(RAN))의 커버리지 정보(coverage information) 전달을 위한 커버리지 정보 전달 ID와 커버리지 정보 요청을 포함하는 인증 요청 메시지(authentication request message)를 전송하는 단계, 커버리지 정보 서버(coverage information server)로부터, 상기 커버리지 정보 전달 ID에 대응되는 UE(user equipment)의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하는 단계 및 상기 UE에게, 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 전송하는 단계를 포함한다. A method of operating an access and mobility management function (AMF) in a wireless communication system according to an embodiment of the present disclosure provides coverage information of a satellite radio access network (RAN) to a network exposure function (NEF) ( Transmitting an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information, from a coverage information server, a UE (UE) corresponding to the coverage information delivery ID receiving at least one of an authentication result and coverage information of user equipment) and transmitting at least one of an authentication result and coverage information to the UE.
본 개시의 일 실시예에 따르면, 서비스를 효과적으로 제공할 수 있다. According to an embodiment of the present disclosure, services can be effectively provided.
도 1은 본 개시의 일 실시예에 따른 5G 시스템의 네트워크 구조 및 인터페이스를 나타낸 도면이다.1 is a diagram showing the network structure and interface of a 5G system according to an embodiment of the present disclosure.
도 2 본 개시의 일 실시예에 따른 5GS 및 EPS 네트워크 구조 및 인터페이스를 나타낸 도면이다.Figure 2 is a diagram showing the 5GS and EPS network structure and interface according to an embodiment of the present disclosure.
도 3는 본 개시의 일 실시예에 따른 5GS와 EPS 간의 인터워킹을 지원하는 비-로밍(non-roaming)을 위한 무선 통신 시스템의 구조를 도시하는 도면이다.FIG. 3 is a diagram illustrating the structure of a wireless communication system for non-roaming supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
도 4은 본 개시의 일 실시예에 따른 5GS와 EPS 간의 인터워킹을 지원하는 로컬 브레이크아웃 로밍(local breakout roaming) 무선 통신 시스템의 구조를 도시하는 도면이다.FIG. 4 is a diagram illustrating the structure of a local breakout roaming wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
도 5는 본 개시의 일 실시예에 따른 5G 시스템 비-로밍(non-roaming)의 구조를 도시하는 도면이다.FIG. 5 is a diagram illustrating the structure of 5G system non-roaming according to an embodiment of the present disclosure.
도 6은 본 개시의 일 실시예에 따른 5G 시스템 로컬 브레이크아웃 로밍(local breakout roaming)의 구조를 도시하는 도면이다.FIG. 6 is a diagram illustrating the structure of local breakout roaming in a 5G system according to an embodiment of the present disclosure.
도 7은 본 개시의 일 실시예에 따른 커버리지 맵 정보 전달(coverage map transfer)을 위한 등록(registration) 절차를 도시하는 도면이다.FIG. 7 is a diagram illustrating a registration procedure for coverage map transfer according to an embodiment of the present disclosure.
도 8은 본 개시 의 일 실시예에 따른 이동성 관리 기능(mobility management function)을 이용한 커버리지 맵 정보 전달(coverage map transfer) 절차를 도시하는 도면이다.FIG. 8 is a diagram illustrating a coverage map transfer procedure using a mobility management function according to an embodiment of the present disclosure.
도 9는 본 개시의 일 실시예에 따른 PDU 세션 관리 절차에서 커버리지 맵 정보 전달(coverage map transfer)하는 방법 도시하는 도면이다.FIG. 9 is a diagram illustrating a method of transferring coverage map information in a PDU session management procedure according to an embodiment of the present disclosure.
도 10은 본 개시의 일 실시예에 따른 PDN connection 관리 절차에서 커버리지 맵 정보 전달(coverage map transfer)하는 방법을 도시하는 도면이다.FIG. 10 is a diagram illustrating a method of transferring coverage map information in a PDN connection management procedure according to an embodiment of the present disclosure.
도 11은 본 개시의 일 실시예에 따른 단말의 구조를 도시한 도면이다.Figure 11 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
도 12는 본 개시의 일 실시예에 따른 기지국의 구조를 도시한 도면이다.Figure 12 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
도 13은 본 개시의 일 실시예에 따른 네트워크 엔티티의 구조를 도시한 도면이다.FIG. 13 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
본 개시의 일 실시예에 따른 무선통신 시스템에서 AMF(access and mobility management function)의 동작 방법은, NEF(network exposure function)에게, 위성 무선 액세스 네트워크(satellite radio access network(RAN))의 커버리지 정보(coverage information) 전달을 위한 커버리지 정보 전달 ID와 커버리지 정보 요청을 포함하는 인증 요청 메시지(authentication request message)를 전송하는 단계, 커버리지 정보 서버(coverage information server)로부터, 상기 커버리지 정보 전달 ID에 대응되는 UE(user equipment)의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하는 단계 및 상기 UE에게, 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 전송하는 단계를 포함한다.A method of operating an access and mobility management function (AMF) in a wireless communication system according to an embodiment of the present disclosure provides coverage information of a satellite radio access network (RAN) to a network exposure function (NEF) ( Transmitting an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information, from a coverage information server, a UE (UE) corresponding to the coverage information delivery ID receiving at least one of an authentication result and coverage information of user equipment) and transmitting at least one of an authentication result and coverage information to the UE.
본 개시의 일 실시예에 따른 무선통신 시스템에서 UE(user equipment)의 동작 방법은, AMF(access and mobility management function)에게, 커버리지 정보(coverage information) 전달 ID와 커버리지 정보 요청을 포함하는 등록 요청 메시지를 전송하는 단계 및 상기 AMF로부터, 상기 UE의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하는 단계를 포함한다. A method of operating a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure includes sending a registration request message including a coverage information delivery ID and a coverage information request to an access and mobility management function (AMF). Transmitting and receiving at least one of the authentication result and coverage information of the UE from the AMF.
본 개시의 일 실시예에 따른 무선통신 시스템에서 AMF(access and mobility management function)는, 통신부(transceiver) 및 상기 통신부와 작동 가능하게 결합된(operably coupled) 적어도 하나의 제어부(controller)를 포함하고, 상기 제어부는, NEF(network exposure function)에게, 위성 무선 액세스 네트워크(satellite radio access network(RAN))의 커버리지 정보(coverage information) 전달을 위한 커버리지 정보 전달 ID와 커버리지 정보 요청을 포함하는 인증 요청 메시지(authentication request message)를 전송하고, 커버리지 정보 서버(coverage information server)로부터, 상기 커버리지 정보 전달 ID에 대응되는 UE(user equipment)의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하며, 상기 UE에게, 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 전송하도록 구성된다. In a wireless communication system according to an embodiment of the present disclosure, an access and mobility management function (AMF) includes a communication unit (transceiver) and at least one controller operably coupled to the communication unit, The control unit sends a network exposure function (NEF) an authentication request message including a coverage information delivery ID and a coverage information request for delivering coverage information of a satellite radio access network (RAN) transmits an authentication request message), receives at least one of an authentication result and coverage information of a UE (user equipment) corresponding to the coverage information transfer ID from a coverage information server, and provides authentication to the UE. It is configured to transmit at least one of result and coverage information.
본 개시의 일 실시예에 따른 무선통신 시스템에서 UE(user equipment)는, 통신부(transceiver) 및 상기 통신부와 작동 가능하게 결합된(operably coupled) 적어도 하나의 제어부(controller)를 포함하고, 상기 제어부는, AMF(access and mobility management function)에게, 커버리지 정보(coverage information) 전달 ID와 커버리지 정보 요청을 포함하는 등록 요청 메시지를 전송하고, 상기 AMF로부터, 상기 UE의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하도록 구성된다. In a wireless communication system according to an embodiment of the present disclosure, a user equipment (UE) includes a communication unit (transceiver) and at least one controller operably coupled to the communication unit, the control unit , Transmits a registration request message including a coverage information delivery ID and a coverage information request to an access and mobility management function (AMF), and receives at least one of the authentication result and coverage information of the UE from the AMF. configured to receive.
이하, 첨부된 도면을 참조하여 본 개시의 바람직한 실시예들을 상세히 설명한다. 이 때, 첨부된 도면에서 동일한 구성 요소는 가능한 동일한 부호로 나타내고 있음에 유의해야 한다. 또한 본 개시의 요지를 흐리게 할 수 있는 공지 기능 및 구성에 대한 상세한 설명은 생략할 것이다.Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. At this time, it should be noted that in the attached drawings, identical components are indicated by identical symbols whenever possible. Additionally, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.
본 개시의 이점 및 특징, 그리고 그것들을 달성하는 방법은 첨부되는 도면과 함께 상세하게 후술되어 있는 실시예들을 참조하면 명확해질 것이다. 그러나 본 개시는 이하에서 개시되는 실시예들에 한정되는 것이 아니라 서로 다른 다양한 형태로 구현될 수 있으며, 단지 본 실시예들은 본 개시의 개시가 완전하도록 하고, 본 개시가 속하는 기술분야에서 통상의 지식을 가진 자에게 개시의 범주를 완전하게 알려주기 위해 제공되는 것이며, 본 개시는 청구항의 범주에 의해 정의될 뿐이다. 명세서 전체에 걸쳐 동일 참조 부호는 동일 구성 요소를 지칭한다. 또한 본 개시를 설명함에 있어서 관련된 기능 또는 구성에 대한 구체적인 설명이 본 개시의 요지를 불필요하게 흐릴 수 있다고 판단된 경우 그 상세한 설명은 생략한다. 그리고 후술되는 용어들은 본 개시에서의 기능을 고려하여 정의된 용어들로서 이는 사용자, 운용자의 의도 또는 관례 등에 따라 달라질 수 있다. 그러므로 그 정의는 본 명세서 전반에 걸친 내용을 토대로 내려져야 할 것이다. The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification. Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.
본 개시의 실시예들을 설명함에 있어서, 이동통신 규격 표준화 단체인 3GPP(3rd Generation Partnership Project)가 명시하고 있는 5G 이동통신 규격 상의 무선 접속망인 New Radio (NR)과 코어 망인 패킷 코어 5G System, 혹은 5G Core Network, 혹은 NG Core(Next Generation Core)를 주된 대상으로 하지만, 본 개시의 주요한 요지는 유사한 기술적 배경을 가지는 여타의 통신 시스템에도 본 개시의 범위를 크게 벗어 나지 아니 하는 범위에서 약간의 변형으로 적용 가능하며, 이는 본 개시의 기술 분야에서 숙련된 기술적 지식을 가진 자의 판단으로 가능 할 것이다.In describing embodiments of the present disclosure, New Radio (NR), a wireless access network based on the 5G mobile communication standard specified by the 3rd Generation Partnership Project (3GPP), a mobile communication standard standardization organization, and Packet Core 5G System, a core network, or 5G Although the main target is Core Network, or NG Core (Next Generation Core), the main gist of the present disclosure can be applied to other communication systems with similar technical background with slight modifications without significantly departing from the scope of the present disclosure. It is possible, and this will be possible at the discretion of a person skilled in the technical field of the present disclosure.
이하, 설명의 편의를 위하여, 3GPP 규격(5G, NR, LTE 또는 이와 유사한 시스템의 규격)에서 정의하고 있는 용어 및 명칭들이 일부 사용될 수 있다. 하지만, 본 개시가 용어 및 명칭들에 의해 한정되는 것은 아니며, 다른 규격에 따르는 시스템에도 동일하게 적용될 수 있다.Hereinafter, for convenience of explanation, some terms and names defined in the 3GPP standard (standard for 5G, NR, LTE, or similar systems) may be used. However, the present disclosure is not limited by terms and names, and can be equally applied to systems that comply with other standards.
이하, 설명에서 사용되는 접속 노드(node)를 식별하기 위한 용어, 망 객체(network entity, 네트워크 엔티티)들을 지칭하는 용어, 메시지들을 지칭하는 용어, 네트워크 엔티티들 간 인터페이스를 지칭하는 용어, 다양한 식별 정보들을 지칭하는 용어 등은 설명의 편의를 위해 예시된 것이다. 따라서, 본 개시에서 사용하는 용어들에 한정되는 것은 아니며, 동등한 기술적 의미를 가지는 대상을 지칭하는 다른 용어가 사용될 수 있다.Hereinafter, terms used in the description to identify the connection node, terms referring to network entities, terms referring to messages, terms referring to the interface between network entities, and various identification information. Terms referring to these are exemplified for convenience of explanation. Therefore, it is not limited to the terms used in the present disclosure, and other terms referring to objects having equivalent technical meaning may be used.
이하, 기지국은 단말의 자원할당을 수행하는 주체로서, gNode B, eNode B, Node B, BS (Base Station), 무선 접속 유닛, 기지국 제어기, 또는 네트워크 상의 노드 중 적어도 하나일 수 있다. 단말은 UE (User Equipment), MS (Mobile Station), 셀룰러폰, 스마트폰, 컴퓨터, 또는 통신 기능을 수행할 수 있는 멀티미디어 시스템을 포함할 수 있다. 본 개시에서 하향링크(Downlink; DL)는 기지국이 단말에게 전송하는 신호의 무선 전송경로이고, 상향링크는(Uplink; UL)는 단말이 기국에게 전송하는 신호의 무선 전송경로를 의미한다. Hereinafter, the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.
이때, 처리 흐름도 도면들의 각 블록과 흐름도 도면들의 조합들은 컴퓨터 프로그램 인스트럭션들에 의해 수행될 수 있음을 이해할 수 있을 것이다. 이들 컴퓨터 프로그램 인스트럭션들은 범용 컴퓨터, 특수용 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비의 프로세서에 탑재될 수 있으므로, 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비의 프로세서를 통해 수행되는 그 인스트럭션들이 흐름도 블록(들)에서 설명된 기능들을 수행하는 수단을 생성하게 된다. 이들 컴퓨터 프로그램 인스트럭션들은 특정 방식으로 기능을 구현하기 위해 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비를 지향할 수 있는 컴퓨터 이용 가능 또는 컴퓨터 판독 가능 메모리에 저장되는 것도 가능하므로, 그 컴퓨터 이용가능 또는 컴퓨터 판독 가능 메모리에 저장된 인스트럭션들은 흐름도 블록(들)에서 설명된 기능을 수행하는 인스트럭션 수단을 내포하는 제조 품목을 생산하는 것도 가능하다. 컴퓨터 프로그램 인스트럭션들은 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비 상에 탑재되는 것도 가능하므로, 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비 상에서 일련의 동작 단계들이 수행되어 컴퓨터로 실행되는 프로세스를 생성해서 컴퓨터 또는 기타 프로그램 가능한 데이터 프로세싱 장비를 수행하는 인스트럭션들은 흐름도 블록(들)에서 설명된 기능들을 실행하기 위한 단계들을 제공하는 것도 가능하다.At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted 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 process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram 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). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.
이때, 본 개시의 실시예에서 사용되는 '~부'라는 용어는 소프트웨어 또는 FPGA(field Programmable Gate Array) 또는 ASIC(Application Specific Integrated Circuit)과 같은 하드웨어 구성요소를 의미하며, '~부'는 어떤 역할들을 수행한다. 그렇지만 '~부'는 소프트웨어 또는 하드웨어에 한정되는 의미는 아니다. '~부'는 어드레싱할 수 있는 저장 매체에 있도록 구성될 수도 있고 하나 또는 그 이상의 프로세서들을 재생시키도록 구성될 수도 있다. 따라서, 일 예로서 '~부'는 소프트웨어 구성요소들, 객체지향 소프트웨어 구성요소들, 클래스 구성요소들 및 태스크 구성요소들과 같은 구성요소들과, 프로세스들, 함수들, 속성들, 프로시저들, 서브루틴들, 프로그램 코드의 세그먼트들, 드라이버들, 펌웨어, 마이크로코드, 회로, 데이터, 데이터베이스, 데이터 구조들, 테이블들, 어레이들, 및 변수들을 포함한다. 구성요소들과 '~부'들 안에서 제공되는 기능은 더 작은 수의 구성요소들 및 '~부'들로 결합되거나 추가적인 구성요소들과 '~부'들로 더 분리될 수 있다. 뿐만 아니라, 구성요소들 및 '~부'들은 디바이스 또는 보안 멀티미디어카드 내의 하나 또는 그 이상의 CPU (central processing unit)들을 재생시키도록 구현될 수도 있다. 또한 실시예에서 '~부'는 하나 이상의 프로세서를 포함할 수 있다.At this time, the term '~unit' used in the embodiments of the present disclosure refers to software or hardware components such as FPGA (field programmable gate array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to what role perform them. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' 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. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. In addition, the components and 'parts' may be implemented to reproduce one or more central processing units (CPUs) within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.
무선 통신 시스템은 초기의 음성 위주의 서비스를 제공하던 것에서 벗어나 예를 들어, 3GPP의 HSPA(High Speed Packet Access), LTE(Long Term Evolution 또는 E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2의 HRPD(High Rate Packet Data), UMB(Ultra Mobile Broadband), 및 IEEE의 802.16e 등의 통신 표준과 같이 고속, 고품질의 패킷 데이터 서비스를 제공하는 광대역 무선 통신 시스템으로 발전하고 있다. Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.
광대역 무선 통신 시스템의 대표적인 예로, LTE 시스템에서는 하향링크(Downlink; DL)에서는 OFDM(Orthogonal Frequency Division Multiplexing) 방식을 채용하고 있고, 상향링크(Uplink; UL)에서는 SC-FDMA(Single Carrier Frequency Division Multiple Access) 방식을 채용하고 있다. 상향링크는 단말(UE(User Equipment) 또는 MS(Mobile Station))이 기지국(eNode B, 또는 base station(BS))으로 데이터 또는 제어신호를 전송하는 무선링크를 뜻하고, 하향링크는 기지국이 단말로 데이터 또는 제어 신호를 전송하는 무선 링크를 뜻한다. 상기와 같은 다중 접속 방식은, 통상 각 사용자 별로 데이터 또는 제어정보를 실어 보낼 시간-주파수 자원을 서로 겹치지 않도록, 즉 직교성 (Orthogonality)이 성립하도록, 할당 및 운용함으로써 각 사용자의 데이터 또는 제어정보를 구분할 수 있다.As a representative example of a broadband wireless communication system, the LTE system uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (DL), and SC-FDMA (Single Carrier Frequency Division Multiple Access) in the uplink (UL). ) method is adopted. Uplink refers to a wireless link in which a terminal (UE (User Equipment) or MS (Mobile Station)) transmits data or control signals to a base station (eNode B, or base station (BS)), and downlink refers to a wireless link in which the base station transmits data or control signals to the base station (eNode B, or base station (BS)). It refers to a wireless link that transmits data or control signals. The above multiple access method usually distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. You can.
LTE 이후의 향후 통신 시스템으로서, 즉, 5G 통신 시스템은 사용자 및 서비스 제공자 등의 다양한 요구 사항을 자유롭게 반영할 수 있어야 하기 때문에 다양한 요구사항을 동시에 만족하는 서비스가 지원되어야 한다. 5G 통신시스템을 위해 고려되는 서비스로는 향상된 모바일 광대역 통신(enhanced Mobile Broadband, eMBB), 대규모 기계형 통신(massive Machine Type Communication, mMTC), 초신뢰 저지연 통신(Ultra Reliability Low Latency Communication, URLLC) 등이 있다. As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is.
eMBB는 기존의 LTE, LTE-A 또는 LTE-Pro가 지원하는 데이터 전송 속도보다 더욱 향상된 데이터 전송 속도를 제공하는 것을 목표로 한다. 예를 들어, 5G 통신 시스템에서 eMBB는 하나의 기지국 관점에서 하향링크에서는 20Gbps의 최대 전송 속도(peak data rate), 상향링크에서는 10Gbps의 최대 전송 속도를 제공할 수 있어야 한다. 또한 5G 통신 시스템은 최대 전송 속도를 제공하는 동시에, 증가된 단말의 실제 체감 전송 속도(User perceived data rate)를 제공해야 한다. 이와 같은 요구 사항을 만족시키기 위해, 더욱 향상된 다중 안테나 (Multi Input Multi Output, MIMO) 전송 기술을 포함하여 다양한 송수신 기술의 향상을 요구한다. 또한 LTE가 사용하는 2GHz 대역에서 최대 20MHz 전송대역폭을 사용하여 신호를 전송하는 반면에, 5G 통신시스템은 3~6GHz 또는 6GHz 이상의 주파수 대역에서 20MHz 보다 넓은 주파수 대역폭을 사용함으로써 5G 통신시스템에서 요구하는 데이터 전송 속도를 만족시킬 수 있다. eMBB aims to provide more improved data transmission speeds than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink from the perspective of one base station. In addition, the 5G communication system must provide the maximum transmission rate and at the same time provide increased user perceived data rate. In order to meet these requirements, improvements in various transmission and reception technologies are required, including more advanced multi-antenna (Multi Input Multi Output, MIMO) transmission technology. In addition, while LTE transmits signals using a maximum of 20MHz transmission bandwidth in the 2GHz band, the 5G communication system uses a frequency bandwidth wider than 20MHz in the 3~6GHz or above 6GHz frequency band to transmit the data required by the 5G communication system. Transmission speed can be satisfied.
동시에, 5G 통신 시스템에서 사물 인터넷(Internet of Thing, IoT)와 같은 응용 서비스를 지원하기 위해 mMTC가 고려되고 있다. mMTC는 효율적으로 사물 인터넷을 제공하기 위해 셀 내에서 대규모 단말의 접속 지원, 단말의 커버리지 향상, 향상된 배터리 시간, 단말의 비용 감소 등이 요구된다. 사물 인터넷은 여러 가지 센서 및 다양한 기기에 부착되어 통신 기능을 제공하므로 셀 내에서 많은 수의 단말(예를 들어, 1,000,000 단말/km2)을 지원할 수 있어야 한다. 또한 mMTC를 지원하는 단말은 서비스의 특성상 건물의 지하와 같이 셀이 커버하지 못하는 음영지역에 위치할 가능성이 높으므로 5G 통신시스템에서 제공하는 다른 서비스 대비 더욱 넓은 커버리지를 요구할 수 있다. mMTC를 지원하는 단말은 저가의 단말로 구성되어야 하며, 단말의 배터리를 자주 교환하기 힘들기 때문에 10~15년과 같이 매우 긴 배터리 생명시간(battery life time)이 요구될 수 있다. At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km2) within a cell. Additionally, due to the nature of the service, terminals that support mMTC are likely to be located in shadow areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system. Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.
마지막으로, URLLC의 경우, 특정한 목적(mission-critical)으로 사용되는 셀룰라 기반 무선 통신 서비스이다. 예를 들어, 로봇(Robot) 또는 기계 장치(Machinery)에 대한 원격 제어(remote control), 산업 자동화(industrial automation), 무인 비행장치(Unmaned Aerial Vehicle), 원격 건강 제어(Remote health care), 비상 상황 알림(emergency alert) 등에 사용되는 서비스 등을 고려할 수 있다. 따라서 URLLC가 제공하는 통신은 매우 낮은 저지연 및 매우 높은 신뢰도 제공해야 한다. 예를 들어, URLLC을 지원하는 서비스는 0.5 밀리초 보다 작은 무선 접속 지연시간(Air interface latency)를 만족해야 하며, 동시에 10-5 이하의 패킷 오류율(Packet Error Rate)의 요구사항을 갖는다. 따라서, URLLC을 지원하는 서비스를 위해 5G 시스템은 다른 서비스보다 작은 전송 시간 구간(Transmit Time Interval, TTI)를 제공해야 하며, 동시에 통신 링크의 신뢰성을 확보하기 위해 주파수 대역에서 넓은 리소스를 할당해야 하는 설계사항이 요구될 수 있다.Lastly, URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency situations. Services used for emergency alerts, etc. can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service that supports URLLC must satisfy an air interface latency of less than 0.5 milliseconds and has a packet error rate of less than 10-5. Therefore, for services supporting URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, a design that requires allocating wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.
5G 통신 시스템의 세가지 서비스들, 즉 eMBB, URLLC, mMTC는 하나의 시스템에서 다중화되어 전송될 수 있다. 이 때, 각각의 서비스들이 갖는 상이한 요구사항을 만족시키기 위해 서비스간에 서로 다른 송수신 기법 및 송수신 파라미터를 사용할 수 있다. 물론 5G 통신 시스템은 전술한 세가지 서비스들에 제한되지 않는다.The three services of the 5G communication system, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters can be used between services to satisfy the different requirements of each service. Of course, the 5G communication system is not limited to the three services mentioned above.
위성 라디오 액세스는 지상 라디오 액세스 보다 상대적으로 넓은 영역을 커버하기 때문에, 5G 코어네트워크와 통신하는 UE의 수도 그만큼 많아진다. 이 때, 위성 라디오 액세스 커버리지는 위성의 이동에 따라 이동하게 되어 UE들은 일시적으로 코어 네트워크와의 연결이 끊길 수 있다. 연결을 잃은 UE들은 위성 커버리지가 일정한 주기가 지나면 다시 돌아올 수 있음에도 불구하고, 코어 네트워크와의 연결이 해제될 수 있다. 다시 위성 커버리지가 돌아왔을 때, UE들은 다시 코어 네트워크에 등록과 연결을 요청하며, 코어 네트워크는 필요한 동작을 수행하고 UE들에게 신호를 보내게 된다. 이는 위성의 주기적 특성이 고려되지 않았기 때문에, 계속해서 반복되게 되며 UE와 코어 네트워크 그리고 라디오 액세스 구간의 자원 사용의 효율성을 떨어뜨린다. 본 개시에서는 위성 셀 커버리지가 시간에 따라 이동하는 5GS 및 EPS에서 단말과 코어네트워크에 위성 커버리지 정보를 전달하는 방법 및 장치를 제공한다. 보다 구체적으로, 위성 액세스 커버리지 특성, UE의 이동성, 네트워크의 단말 등록 및 세션 관리 능력, 및 위성 액세스 라디오 능력 등을 고려하여 UE의 등록 및 연결을 관리를 효율적으로 할 수 있는 방법 및 장치를 제공한다.Because satellite radio access covers a relatively larger area than terrestrial radio access, the number of UEs communicating with the 5G core network also increases. At this time, satellite radio access coverage moves according to the movement of the satellite, so UEs may temporarily lose connection to the core network. UEs that lose connectivity may be disconnected from the core network, although satellite coverage may return after a certain period. When satellite coverage returns, the UEs request registration and connection to the core network again, and the core network performs the necessary operations and sends signals to the UEs. Since the periodic characteristics of the satellite are not taken into account, this is repeated continuously and reduces the efficiency of resource use of the UE, core network, and radio access section. This disclosure provides a method and device for delivering satellite coverage information to a terminal and core network in 5GS and EPS, where satellite cell coverage moves over time. More specifically, it provides a method and device that can efficiently manage UE registration and connection by considering satellite access coverage characteristics, UE mobility, network terminal registration and session management capabilities, and satellite access radio capabilities. .
본 개시의 일 실시예에 따르면, 위성 셀 커버리지가 시간에 따라 이동하는 5GS 및 EPS에서, 위성 액세스 커버리지 특성, UE의 이동성, 네트워크의 단말 등록 및 세션 관리 능력, 및 위성 액세스 라디오 능력 등을 고려하여 UE의 등록 및 연결을 관리할 수 있다.According to an embodiment of the present disclosure, in 5GS and EPS, where satellite cell coverage moves over time, considering satellite access coverage characteristics, mobility of UE, terminal registration and session management capabilities of the network, and satellite access radio capabilities, etc. Registration and connection of UE can be managed.
도 1은 본 개시의 일 실시예에 따른 5G 시스템의 네트워크 구조 및 인터페이스를 나타낸 도면이다.1 is a diagram showing the network structure and interface of a 5G system according to an embodiment of the present disclosure.
도 1의 5G 시스템의 네트워크 구조에 포함된 네트워크 엔티티(entity)는 시스템 구현에 따라 네트워크 기능(network function: NF)를 포함할 수 있다.A network entity included in the network structure of the 5G system in FIG. 1 may include a network function (NF) depending on system implementation.
도 1을 참조하면, 5G 시스템(100)의 네트워크 구조는 다양한 네트워크 엔티티들을 포함할 수 있다. 일 예로, 5G 시스템(100)은 인증 서버 기능(authentication server function: AUSF)(108), 액세스 및 이동성 관리 기능((core) access and mobility management function: AMF)(103), 세션 관리 기능(session management function: SMF)(105), 정책 제어 기능(policy control function: PCF)(106), 어플리케이션 기능(application function: AF)(107), 통합된 데이터 관리(unified data management: UDM)(109), 데이터 네트워크(data network: DN)(110), 네트워크 노출 기능(network exposure function: NEF)(113), 네트워크 슬라이싱 선택 기능(network slicing selection function: NSSF)(114), 네트워크 저장소 기능(Network Repository Function: NRF)(115), 에지 어플리케이션 서비스 도메인 저장소(edge application service domain repository: EDR, 미도시), 에지 어플리케이션 서버(edge application server: EAS, 미도시), EAS 디스커버리 기능(EAS discovery function: EASDF, 미도시), 네트워크 데이터 분석 기능(Network Data Analytics Function: NWDAF, 미도시), 사용자 평면 기능(user plane function: UPF)(104), (무선) 액세스 네트워크((radio) access network: (R)AN)(102), 및 단말, 즉, 사용자 장치(user equipment: UE)(101)를 포함할 수 있다.Referring to FIG. 1, the network structure of the 5G system 100 may include various network entities. As an example, the 5G system 100 includes an authentication server function (AUSF) 108, an access and mobility management function (AMF) 103, and a session management function. function: SMF) (105), policy control function (PCF) (106), application function (AF) (107), unified data management (UDM) (109), data Network (data network: DN) (110), network exposure function (NEF) (113), network slicing selection function (NSSF) (114), network repository function (Network Repository Function: NRF) ) (115), edge application service domain repository (EDR, not shown), edge application server (EAS, not shown), EAS discovery function (EAS discovery function: EASDF, not shown) , Network Data Analytics Function (NWDAF, not shown), user plane function (UPF) (104), (wireless) access network ((radio) access network: (R)AN) (102) ), and a terminal, that is, a user equipment (UE) 101.
5G 시스템(100)의 각 NF들은 다음과 같은 기능을 지원한다.Each NF of the 5G system 100 supports the following functions.
AUSF(108)는 UE(101)의 인증을 위한 데이터를 처리하고 저장한다. AUSF 108 processes and stores data for authentication of UE 101.
AMF(103)는 UE 단위의 접속 및 이동성 관리를 위한 기능을 제공하며, 하나의 UE 당 기본적으로 하나의 AMF에 연결될 수 있다. 구체적으로, AMF(103)는 3GPP 액세스 네트워크들 간의 이동성을 위한 CN 노드 간 시그널링, 무선 액세스 네트워크(radio access network: RAN) CP 인터페이스(즉, N2 인터페이스)의 종단(termination), NAS(non access stratum) 시그널링의 종단(N1), NAS 시그널링 보안(NAS 암호화(ciphering) 및 무결성 보호(integrity protection)), AS 보안 제어, 등록 관리(등록 영역(registration area) 관리), 연결 관리, 아이들 모드 UE 접근성(reachability) (페이징 재전송의 제어 및 수행 포함), 이동성 관리 제어(가입 및 정책), 인트라-시스템 이동성 및 인터-시스템 이동성 지원, 네트워크 슬라이싱의 지원, SMF 선택, 합법적 감청(lawful intercept)(AMF 이벤트 및 LI 시스템으로의 인터페이스에 대한), UE와 SMF 간의 세션 관리(session management: SM) 메시지의 전달 제공, SM 메시지 라우팅을 위한 트랜스패런트 프록시(transparent proxy), 액세스 인증(access authentication), 로밍 권한 체크를 포함한 액세스 허가(access authorization), UE와 SMSF 간의 SMS 메시지의 전달 제공, 보안 앵커 기능(security anchor function: SAF) 및/또는 보안 컨텍스트 관리(security context management: SCM) 등의 기능을 지원한다. AMF(103)의 일부 또는 전체의 기능들은 하나의 AMF의 단일 인스턴스(instance) 내에서 지원될 수 있다.The AMF 103 provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF. Specifically, the AMF 103 supports CN inter-node signaling for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), and non-access stratum (NAS) ) Endpoint of signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE accessibility ( reachability (including control and performance of paging retransmissions), mobility management controls (subscriptions and policies), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (AMF events and (for interface to LI system), providing delivery of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, roaming authority check It supports functions such as access authorization, providing delivery of SMS messages between the UE and SMSF, security anchor function (SAF), and/or security context management (SCM). Some or all of the functions of AMF 103 may be supported within a single instance of one AMF.
DN(110)은 예를 들어, 운영자 서비스, 인터넷 접속 또는 서드파티(3rd party) 서비스 등을 의미한다. DN(110)은 UPF(104)로 하향링크 프로토콜 데이터 유닛(protocol data unit: PDU)을 전송하거나, UE(101)로부터 전송된 PDU를 UPF(104)로부터 수신한다. DN 110 means, for example, an operator service, Internet access, or a third party service. The DN 110 transmits a downlink protocol data unit (PDU) to the UPF 104 or receives the PDU transmitted from the UE 101 from the UPF 104.
PCF(106)는 어플리케이션 서버로부터 패킷 흐름에 대한 정보를 수신하여, 이동성 관리, 세션 관리 등의 정책을 결정하는 기능을 제공한다. 구체적으로, PCF(106)는 네트워크 동작을 통제하기 위한 단일화된 정책 프레임워크 지원, 제어평면 기능(들)(예를 들어, AMF, SMF 등)이 정책 규칙을 시행할 수 있도록 정책 규칙 제공, 사용자 데이터 저장소(user data repository: UDR) 내 정책 결정을 위해 관련된 가입 정보에 액세스하기 위한 프론트 엔드(front end) 구현 등의 기능을 지원한다.The PCF (106) receives information about packet flow from the application server and provides the function of determining policies such as mobility management and session management. Specifically, PCF 106 supports a unified policy framework to govern network behavior, provides policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and allows users to It supports functions such as implementing a front end to access relevant subscription information for policy decisions within a user data repository (UDR).
SMF(105)는 세션 관리 기능을 제공하며, UE가 다수 개의 세션을 가지는 경우 각 세션 별로 서로 다른 SMF에 의해 관리될 수 있다. 구체적으로, SMF(105)는 세션 관리(예를 들어, UPF(104)와 (R)AN(102) 노드 간의 터널(tunnel) 유지를 포함하여 세션 확립, 수정 및 해지), UE IP 주소 할당 및 관리(선택적으로 인증 포함), UP 기능의 선택 및 제어, UPF(104)에서 트래픽을 적절한 목적지로 라우팅하기 위한 트래픽 스티어링(traffic steering) 설정, 정책 제어 기능(policy control functions)를 향한 인터페이스의 종단, 정책 및 QoS(quality of service)의 제어 부분 시행, 합법적 감청(lawful intercept)(SM 이벤트 및 LI 시스템으로의 인터페이스에 대한), NAS 메시지의 SM 부분의 종단, 하향링크 데이터 통지(downlink data notification), AN 특정 SM 정보의 개시자(AMF(103)를 경유하여 N2를 통해 (R)AN(102)에게 전달), 세션의 SSC 모드 결정, 로밍 기능 등의 기능을 지원한다. SMF(105)의 일부 또는 전체의 기능들은 하나의 SMF의 단일 인스턴스(instance) 내에서 지원될 수 있다.The SMF 105 provides a session management function, and when the UE has multiple sessions, each session can be managed by a different SMF. Specifically, SMF 105 performs session management (e.g., session establishment, modification, and termination, including maintaining tunnels between UPF 104 and (R)AN 102 nodes), UE IP address allocation, and Management (optionally including authentication), selection and control of UP functions, establishment of traffic steering to route traffic to appropriate destinations in UPF 104, termination of interfaces towards policy control functions; Enforcement of policy and control portion of quality of service (QoS), lawful intercept (for SM events and interface to LI system), termination of SM portion of NAS messages, downlink data notification, It supports functions such as initiator of AN-specific SM information (delivered to (R)AN (102) via N2 via AMF (103)), SSC mode determination of the session, and roaming function. Some or all of the functions of SMF 105 may be supported within a single instance of one SMF.
UDM(109)은 사용자의 가입 데이터, 정책 데이터 등을 저장한다. UDM(109)은 2개의 부분, 즉 어플리케이션 프론트 엔드(front end: FE)(미도시) 및 사용자 데이터 저장소(user data repository: UDR)(미도시)를 포함한다.The UDM 109 stores user subscription data, policy data, etc. UDM 109 includes two parts: an application front end (FE) (not shown) and a user data repository (UDR) (not shown).
FE는 위치 관리, 가입 관리, 자격 증명(credential)의 처리 등을 담당하는 UDM FE와 정책 제어를 담당하는 PCF를 포함한다. UDR은 UDM-FE에 의해 제공되는 기능들을 위해 요구되는 데이터와 PCF에 의해 요구되는 정책 프로필을 저장한다. UDR 내 저장되는 데이터는 가입 식별자, 보안 자격 증명(security credential), 액세스 및 이동성 관련 가입 데이터 및 세션 관련 가입 데이터를 포함하는 사용자 가입 데이터와 정책 데이터를 포함한다. UDM-FE는 UDR에 저장된 가입 정보에 액세스하고, 인증 자격 증명 처리(authentication credential processing), 사용자 식별자 핸들링(user identification handling), 액세스 인증, 등록/이동성 관리, 가입 관리, SMS 관리 등의 기능을 지원한다.FE includes UDM FE, which is responsible for location management, subscription management, and credential processing, and PCF, which is responsible for policy control. UDR stores data required for functions provided by UDM-FE and policy profiles required by PCF. Data stored within the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. UDM-FE accesses subscription information stored in UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management. do.
UPF(104)는 DN(110)으로부터 수신한 하향링크 PDU를 (R)AN(102)을 경유하여 UE(101)에게 전달하며, (R)AN(102)을 경유하여 UE(101)로부터 수신한 상향링크 PDU를 DN(110)으로 전달한다. 구체적으로, UPF(104)는 인트라(intra)/인터(inter) RAT 이동성을 위한 앵커 포인트, 데이터 네트워크(Data Network)로의 상호연결(interconnect)의 외부 PDU 세션 포인트, 패킷 라우팅 및 포워딩, 패킷 검사(inspection) 및 정책 규칙 시행의 사용자 평면 부분, 합법적 감청(lawful intercept), 트래픽 사용량 보고, 데이터 네트워크로의 트래픽 플로우의 라우팅을 지원하기 위한 상향링크 분류자(classifier), 멀티-홈(multi-homed) PDU 세션을 지원하기 위한 브랜치 포인트(branching point), 사용자 평면을 위한 QoS 핸들링(handling)(예를 들어 패킷 필터링, 게이팅(gating), 상향링크/하향링크 레이트 시행), 상향링크 트래픽 검증 (서비스 데이터 플로우(service data flow: SDF)와 QoS 플로우 간 SDF 매핑), 상향링크 및 하향링크 내 전달 레벨(transport level) 패킷 마킹, 하향링크 패킷 버퍼링 및 하향링크 데이터 통지 트리거링 기능 등의 기능을 지원한다. UPF(104)의 일부 또는 전체의 기능들은 하나의 UPF의 단일 인스턴스(instance) 내에서 지원될 수 있다.The UPF (104) delivers the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102) and receives it from the UE (101) via the (R)AN (102). One uplink PDU is delivered to the DN (110). Specifically, the UPF 104 is an anchor point for intra/inter RAT mobility, an external PDU session point for interconnect to a data network, packet routing and forwarding, and packet inspection ( User plane portion of inspection and policy rule enforcement, lawful intercept, traffic usage reporting, and uplink classifier to support routing of traffic flows to the data network, multi-homed Branching points to support PDU sessions, QoS handling for the user plane (e.g. packet filtering, gating, uplink/downlink rate enforcement), uplink traffic verification (service data) It supports functions such as service data flow (SDF mapping between SDF and QoS flows), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering function. Some or all of the functions of UPF 104 may be supported within a single instance of one UPF.
AF(107)는 서비스 제공(예를 들어, 트래픽 라우팅 상에서 어플리케이션 영향, 네트워크 능력 노출(network capability exposure)에 대한 접근, 정책 제어를 위한 정책 프레임워크와의 상호동작 등의 기능을 지원)을 위해 3GPP 코어 네트워크와 상호 동작한다. AF 107 supports 3GPP for service provision (e.g., supporting functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control). Interoperates with the core network.
(R)AN(102)은 4G 무선 액세스 기술의 진화된 버전인 진화된 E-UTRA(evolved E-UTRA)와 새로운 무선 액세스 기술(new radio: NR)(예를 들어, gNB)을 모두 지원하는 새로운 무선 액세스 네트워크를 총칭한다.(R)AN 102 supports both evolved E-UTRA (evolved E-UTRA), which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB). A general term for a new wireless access network.
gNB은 무선 자원 관리를 위한 기능들(즉, 무선 베어러 제어(radio bearer control), 무선 허락 제어(radio admission control), 연결 이동성 제어(connection mobility control), 상향링크/하향링크에서 UE에게 자원의 동적 할당(dynamic allocation of resources)(즉, 스케줄링)), IP(internet protocol) 헤더 압축, 사용자 데이터 스트림의 암호화(encryption) 및 무결성 보호(integrity protection), UE에게 제공된 정보로부터 AMF로의 라우팅이 결정되지 않는 경우, UE의 어태치(attachment) 시 AMF의 선택, UPF(들)로의 사용자 평면 데이터 라우팅, AMF로의 제어 평면 정보 라우팅, 연결 셋업 및 해지, 페이징 메시지의 스케줄링 및 전송(AMF로부터 발생된), 시스템 브로드캐스트 정보의 스케줄링 및 전송(AMF 또는 운영 및 유지(operating and maintenance: O&M)로부터 발생된), 이동성 및 스케줄링을 위한 측정 및 측정 보고 설정, 상향링크에서 전달 레벨 패킷 마킹(transport level packet marking), 세션 관리, 네트워크 슬라이싱의 지원, QoS 흐름 관리 및 데이터 무선 베어러로의 매핑, 비활동 모드(inactive mode)인 UE의 지원, NAS 메시지의 분배 기능, NAS 노드 선택 기능, 무선 액세스 네트워크 공유, 이중 연결성(dual connectivity), NR과 E-UTRA 간의 밀접한 상호동작(tight interworking) 등의 기능을 지원한다.The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink). dynamic allocation of resources (i.e. scheduling), Internet protocol (IP) header compression, encryption and integrity protection of user data streams, routing to AMF is not determined from the information provided to the UE. In this case, selection of AMF upon attachment of the UE, user plane data routing to UPF(s), control plane information routing to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), system Scheduling and transmission of broadcast information (from AMF or operating and maintenance (O&M)), setting up measurements and measurement reporting for mobility and scheduling, transport level packet marking in the uplink, Session management, support of network slicing, QoS flow management and data mapping to radio bearers, support of UE in inactive mode, distribution function of NAS messages, NAS node selection function, radio access network sharing, dual connectivity ( Supports features such as dual connectivity and tight interworking between NR and E-UTRA.
UE(101)는 사용자 기기를 의미한다. 사용자 장치는 단말(terminal), ME(mobile equipment), MS(mobile station) 등의 용어로 언급될 수 있다. 또한, 사용자 장치는 노트북, 휴대폰, PDA(personal digital assistant), 스마트폰, 멀티미디어 기기 등과 같이 휴대 가능한 기기일 수 있고, 또는 PC(personal computer), 차량 탑재 장치와 같이 휴대 불가능한 기기일 수도 있다. UE 101 refers to a user device. A user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc. Additionally, the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, or a multimedia device, or it may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.
NEF(113)는 3GPP 네트워크 기능들에 의해 제공되는, 예를 들어, 제3자(3rd party), 내부 노출(internal exposure)/재노출(re-exposure), 어플리케이션 기능, 에지 컴퓨팅(Edge Computing)을 위한 서비스들 및 능력들을 안전하게 노출하기 위한 수단을 제공한다. NEF(111)는 다른 NF(들)로부터 (다른 NF(들)의 노출된 능력(들)에 기반한) 정보를 수신한다. NEF(111)는 데이터 저장 네트워크 기능으로의 표준화된 인터페이스를 이용하여 구조화된 데이터로서 수신된 정보를 저장할 수 있다. 저장된 정보는 NEF(111)에 의해 다른 NF(들) 및 AF(들)에게 재노출(re-expose)되고, 분석 등과 같은 다른 목적으로 이용될 수 있다. NEF 113 is provided by 3GPP network functions, e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing. Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s). NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed by the NEF 111 to other NF(s) and AF(s) and used for other purposes such as analysis.
NRF (115)는 서비스 디스커버리 기능을 지원한다. NF 인스턴스로부터 NF 디스커버리 요청 수신하고, 발견된 NF 인스턴스의 정보를 NF 인스턴스에게 제공한다. 또한, 이용 가능한 NF 인스턴스들과 그들이 지원하는 서비스를 유지한다. NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
한편, 도 1에서는 설명의 편의상 UE(101)가 하나의 PDU 세션을 이용하여 하나의 DN(110)에 엑세스하는 경우에 대한 참조 모델을 예시하나, 본 개시는 이에 한정되지 않는다.Meanwhile, FIG. 1 illustrates a reference model for a case where the UE 101 accesses one DN 110 using one PDU session for convenience of explanation, but the present disclosure is not limited thereto.
UE(101)는 다중의 PDU 세션을 이용하여 2개의(즉, 지역적(local) 그리고 중심되는(central)) 데이터 네트워크에 동시에 액세스할 수 있다. 이때, 서로 다른 PDU 세션을 위해 2개의 SMF들이 선택될 수 있다. 다만, 각 SMF는 PDU 세션 내 지역적인 UPF 및 중심되는 UPF를 모두 제어할 수 있는 능력을 가질 수 있다. UE 101 can simultaneously access two (ie, local and central) data networks using multiple PDU sessions. At this time, two SMFs may be selected for different PDU sessions. However, each SMF may have the ability to control both the local UPF and the central UPF within the PDU session.
또한, UE(101)는 단일의 PDU 세션 내에서 제공되는 2개의(즉, 지역적인 그리고 중심되는) 데이터 네트워크에 동시에 액세스할 수도 있다.Additionally, UE 101 may simultaneously access two (ie, local and central) data networks provided within a single PDU session.
NSSF(114)는 UE(101)를 서빙하는 네트워크 슬라이스 인스턴스들의 세트를 선택할 수 있다. 또한, NSSF(114)는 허여된 NSSAI(network slice selection assistance information)를 결정하고, 필요한 경우, 가입된 S-NSSAI(single-network slice selection assistance information)들에 대한 매핑을 수행할 수 있다. 또한, NSSF(114)는 설정된 NSSAI를 결정하고, 필요한 경우, 가입된 S-NSSAI들에 대한 매핑을 수행할 수 있다. 또한, NSSF(114)는 UE를 서비스하는데 사용되는 AMF 세트를 결정하거나, 설정에 따라 NRF(115)에 문의하여 후부(candidate) AMF의 목록을 결정할 수 있다. NSSF 114 may select a set of network slice instances serving UE 101. Additionally, the NSSF 114 may determine permitted network slice selection assistance information (NSSAI) and, if necessary, perform mapping on subscribed single-network slice selection assistance information (S-NSSAI). Additionally, the NSSF 114 may determine the configured NSSAI and, if necessary, perform mapping to the subscribed S-NSSAIs. Additionally, the NSSF 114 may determine the set of AMFs used to serve the UE, or, depending on settings, may query the NRF 115 to determine a list of candidate AMFs.
NRF(115)는 서비스 디스커버리 기능을 지원한다. NF 인스턴스로부터 NF 디스커버리 요청 수신하고, 발견된 NF 인스턴스의 정보를 NF 인스턴스에게 제공한다. 또한, 이용 가능한 NF 인스턴스들과 그들이 지원하는 서비스를 유지한다. NRF 115 supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.
3GPP 시스템에서는 5G 시스템 내 NF들 간을 연결하는 개념적인 링크를 참조 포인트(reference point)라고 정의한다. 다음은 도 1에서 표현된 5G 시스템 아키텍처에 포함되는 참조 포인트를 예시한다.In the 3GPP system, the conceptual link connecting NFs in the 5G system is defined as a reference point. The following illustrates reference points included in the 5G system architecture represented in Figure 1.
- N1: UE와 AMF 간의 참조 포인트- N1: Reference point between UE and AMF
- N2: (R)AN과 AMF 간의 참조 포인트- N2: Reference point between (R)AN and AMF
- N3: (R)AN과 UPF 간의 참조 포인트- N3: Reference point between (R)AN and UPF
- N4: SMF와 UPF 간의 참조 포인트- N4: Reference point between SMF and UPF
- N5: PCF와 AF 간의 참조 포인트- N5: Reference point between PCF and AF
- N6: UPF와 데이터 네트워크 간의 참조 포인트- N6: Reference point between UPF and data network
- N7: SMF와 PCF 간의 참조 포인트- N7: Reference point between SMF and PCF
- N8: UDM과 AMF 간의 참조 포인트- N8: Reference point between UDM and AMF
- N9: 2개의 코어 UPF들 간의 참조 포인트- N9: Reference point between two core UPFs
- N10: UDM과 SMF 간의 참조 포인트- N10: Reference point between UDM and SMF
- N11: AMF와 SMF 간의 참조 포인트- N11: Reference point between AMF and SMF
- N12: AMF와 AUSF 간의 참조 포인트- N12: Reference point between AMF and AUSF
- N13: UDM과 인증 서버 기능(authentication server function, AUSF) 간의 참조 포인트- N13: Reference point between UDM and authentication server function (AUSF)
- N14: 2개의 AMF들 간의 참조 포인트- N14: Reference point between two AMFs
- N15: 비-로밍 시나리오의 경우, PCF와 AMF 간의 참조 포인트, 로밍 시나리오의 경우 방문 네트워크(visited network) 내 PCF와 AMF 간의 참조 포인트- N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios
- N23: PCF와 NWDAF 간의 참조 포인트- N23: Reference point between PCF and NWDAF
- N34: NSSF와 NWDAF 간의 참조 포인트- N34: Reference point between NSSF and NWDAF
이하의 설명에서 단말은 UE(101)를 의미할 수 있으며, UE 또는 단말의 용어가 혼용되어 사용될 수 있다. 이런 경우 특별히 단말을 부가적으로 정의하지 않는 한 UE(101)로 이해되어야 한다.In the following description, the terminal may refer to the UE 101, and the terms UE and terminal may be used interchangeably. In this case, unless the UE is specifically defined additionally, it should be understood as UE 101.
도 2 본 개시의 일 실시예에 따른 5GS 및 EPS 네트워크 구조 및 인터페이스를 나타낸 도면이다.Figure 2 is a diagram showing the 5GS and EPS network structure and interface according to an embodiment of the present disclosure.
도 2를 참조하면, 5GS 및 EPS의 네트워크 구조는 커버리지 맵 정보 네트워크 기능(Coverage Map information Network Function: CM NF), 커버리지 맵 정보 서버(Coverage Map information Server: CMS)을 포함할 수 있다. Referring to FIG. 2, the network structure of 5GS and EPS may include a coverage map information network function (CM NF) and a coverage map information server (CMS).
CM NF는 액세스 네트워크 커버리지(위성 액세스 커버리지를 포함할 수 있다)와 관련된 정보를 수신하여, 단말과 코어 네트워크 엔티티에 제공하는 기능을 제공할 수 있다. 구체적으로, CM NF는 단말, 5GC 네트워크 엔티티, 또는 EPC 네트워크 엔티티로부터 액세스 네트워크의 커버리지 관련 정보에 대한 요청을 수신한 경우, 요청 정보를 평가(evaluate)하고 변환(translate)하여 CMS에게 커버리지 관련 정보의 제공을 요청할 수 있다. 또한 CM NF는 CMS로부터 커버리지 관련 정보와 커버리지 관련 정보 전달을 위한 인증(authentication) 데이터를 수신한 경우, 커버리지 관련 정보를 평가하 변환하여, 단말, 5GC 네트워크 엔티티, 또는 EPC 네트워크 엔티티에게 제공할 수 있다. The CM NF may provide the function of receiving information related to access network coverage (which may include satellite access coverage) and providing it to the terminal and core network entity. Specifically, when the CM NF receives a request for coverage-related information of the access network from a terminal, 5GC network entity, or EPC network entity, it evaluates and translates the requested information and provides coverage-related information to CMS. You may request provision. In addition, when the CM NF receives coverage-related information and authentication data for delivering coverage-related information from CMS, it can evaluate and convert the coverage-related information and provide it to the terminal, 5GC network entity, or EPC network entity. .
CM NF는 NEF와 동일한 소프트웨어 또는 장치에 존재할 수도 있고, 별도의 소프트웨어 또는 장치에 존재할 수도 있다. 도 2에서는 NEF와 동일한 장치에 존재하는 예를 도시하였으며, 이에 한정되지 않는다. 도 2의 예와 같이 CM NF가 NEF와 동일한 장치에 존재하는 경우, CM NF는 NEF가 지원하는 인터페이스를 동일하게 지원할 수 있다. 예를 들어, CM NF는 N29, N30, N51 등의 NEF가 5GC 네트워크 엔티티와 통신할 때 사용하는 인터페이스를 이용하여, 동일하게 각각의 5GC 네트워크 엔티티와 통신할 수 있다. 또한, CM NF는 NEF가 DN과 통신할 때 사용하는 N33 인터페이스를 이용하여 DN과 통신할 수 있다.CM NF may exist in the same software or device as NEF, or may exist in separate software or device. Figure 2 shows an example that exists in the same device as the NEF, but is not limited to this. As in the example of FIG. 2, when the CM NF exists in the same device as the NEF, the CM NF can support the same interfaces supported by the NEF. For example, CM NF can communicate with each 5GC network entity in the same way using the interface used by NEFs such as N29, N30, and N51 to communicate with 5GC network entities. Additionally, the CM NF can communicate with the DN using the N33 interface that the NEF uses to communicate with the DN.
단말은 NG-RAN 또는 gNB를 이용하여 5GC (5G Core Network)에 연결될 수 있으며, 구체적으로는 NG-RAN은 UPF와 N3 인터페이스로 연결될 수 있고, UPF와 DN은 N6 인터페이스로 연결될 수 있다.The terminal can be connected to 5GC (5G Core Network) using NG-RAN or gNB. Specifically, NG-RAN can be connected to UPF and N3 interface, and UPF and DN can be connected to N6 interface.
단말은 (R)AN 또는 eNB를 이용하여 EPC (Evolved Packet Core Network)에 연결될 수 있으며, 구체적으로는 (R)AN과 Serving Gateway는 S1 (또는 S1-U) 인터페이스로 연결될 수 있고, Serving Gateway와 PDN Gateway는 S5 인터페이스로 연결될 수 있으며, PDN Gateway와 DN은 SGi 인터페이스로 연결될 수 있다.The terminal can be connected to the EPC (Evolved Packet Core Network) using (R)AN or eNB. Specifically, (R)AN and the Serving Gateway can be connected to the S1 (or S1-U) interface, and the Serving Gateway and The PDN Gateway can be connected to the S5 interface, and the PDN Gateway and DN can be connected to the SGi interface.
CMS는 단말, 5GC 네트워크 엔티티, EPC 네트워크 엔티티에게 커버리지 관련 정보를 제공할 수 있다. CMS는 예를 들어, 5GC 또는 EPC 네트워크를 운영하는 사업자 또는 위성 액세스 네트워크를 운영하는 사업자 등이 커버리지 관련 정보를 관리하는 서버일 수 있다. CMS는 단말 또는 코어 네트워크 엔티티가 커버리지 관련 정보를 요청하면, 요청한 단말 또는 엔티티에 대하여 커버리지 관련 정보를 수신할 수 있는지 여부에 대한 인증(authentication)을 수행할 수 있다. CMS는 인증된 단말 또는 엔티티에게 커버리지 관련 정보를 제공할 수 있다.CMS can provide coverage-related information to terminals, 5GC network entities, and EPC network entities. CMS may be a server that manages coverage-related information, for example, by an operator operating a 5GC or EPC network or an operator operating a satellite access network. When a terminal or core network entity requests coverage-related information, CMS can perform authentication on whether coverage-related information can be received for the requested terminal or entity. CMS can provide coverage-related information to authenticated terminals or entities.
CMS는 5GS와 EPS 입장에서 DN으로 인식될 수 있으며, 따라서 5GC 및 EPC 엔티티와 DN을 연결하는 인터페이스를 동일하게 지원할 수 있다. 예를 들어, NEF는 CMS와 N33 인터페이스를 통해 통신할 수 있으며, UPF는 N6 인터페이스를 통해 CMS와 통신할 수 있고, PDN gateway는 CMS와 SGi 인터페이스를 통해 통신할 수 있다.CMS can be recognized as a DN from the perspective of 5GS and EPS, and therefore can equally support the interface connecting 5GC and EPC entities and DN. For example, NEF can communicate with CMS over the N33 interface, UPF can communicate with CMS over the N6 interface, and PDN gateway can communicate with CMS over the SGi interface.
도 3는 본 개시의 일 실시예에 따른 5GS와 EPS 간의 인터워킹을 지원하는 비-로밍(non-roaming)을 위한 무선 통신 시스템의 구조를 도시하는 도면이다.FIG. 3 is a diagram illustrating the structure of a wireless communication system for non-roaming supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
5GS는 단말(UE)(101)의 무선 접속을 위한 NR(New Radio) 기지국(NG-RAN(radio access node) 또는 gNB(next generation node B))(103), 액세스 및 이동성 관리 기능(access and mobility management function, AMF)(105), 정책 제어 기능(policy control function, PCF), 네트워크 노출 기능(network exposure function: NEF), 커버리지 맵 정보 네트워크 기능(Coverage Map information Network Function: CM NF)를 포함할 수 있으며, 그 외에 도 3에 도시하지 않았으나 세션 관리 기능(session management function, SMF), 사용자 평면 기능(user plane function, UPF), 네트워크 슬라이스 선택 기능(network slice selection function, NSSF), 통합된 데이터 관리(unified data management, UDM), 통합된 데이터 저장소(unified data repository, UDR) 등을 포함할 수 있다. 5GS is a NR (New Radio) base station (NG-RAN (radio access node) or gNB (next generation node B)) 103 for wireless access of the terminal (UE) 101, and an access and mobility management function (access and mobility management function) It may include mobility management function (AMF) (105), policy control function (PCF), network exposure function (NEF), and coverage map information network function (CM NF). In addition, although not shown in FIG. 3, session management function (SMF), user plane function (UPF), network slice selection function (NSSF), and integrated data management (unified data management, UDM), unified data repository (UDR), etc.
EPS는 E-UTRA 기지국(E-UTRAN(Evolved UMTS(Universal Mobile Telecommunications System) Terrestrial Radio Access Network), 또는 eNB(evolved node B))(113), 이동성 관리 엔티티(mobility management entity, MME)(115), 서빙 게이트웨이(serving gateway, SGW)(117), 패킷 데이터 네트워크 게이트웨이(packet data network gateway, PGW)(PGW는 PGW-U와 PGW-C로 구성될 수 있다), 홈 가입자 서버(home subscriber server, HSS), 서비스 능력 노출 기능(Service Capability Exposure Function, SCEF) 등을 포함할 수 있다. The EPS is an E-UTRA base station (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or evolved node B (eNB)) 113, a mobility management entity (MME) 115 , serving gateway (SGW) 117, packet data network gateway (PGW) (PGW may be composed of PGW-U and PGW-C), home subscriber server (home subscriber server, HSS), Service Capability Exposure Function (SCEF), etc.
일 실시예에 따르면, 상기 AMF(105) 및 MME(115)는 단말에 대한 무선망 접속(Access) 및 이동성(Mobility)을 관리하는 NF(Network Function)가 될 수 있다. SMF, SGW 및 PGW는 단말에 대한 세션(Session)을 관리하는 NF이며, 세션 정보에는 서비스 품질(Quality of Service, QoS) 정보, 과금(charging) 정보, 패킷 처리에 대한 정보를 포함할 수 있다. 또한 상기 UPF 및 PGW는 사용자 평면 트래픽(예: User Plane 트래픽)을 처리하는 NF이며, SMF 및 SGW에 의해 제어를 받는다. 상기 PCF 및 PCRF는 무선 통신 시스템에서 서비스를 제공하기 위한 사업자 정책(Operator policy 및/또는 PLMN policy)을 관리하는 NF일 수 있다. 추가로 PCF는 액세스 및 이동성(Access and Mobility, AM) 정책 및 UE 정책을 담당하는 PCF와 세션 관리(Session Management, SM) 정책을 담당하는 PCF로 나뉠 수 있다. AM/UE 정책 담당 PCF와 SM 정책 담당 PCF는 논리적 내지 물리적으로 분리된 NF이거나 또는 논리적 내지 물리적으로 하나의 NF일 수 있다. UDM 및 HSS는 단말의 가입자 정보(UE subscription)를 저장 및 관리하는 NF일 수 있다. UDR은 데이터를 저장 및 관리하는 NF 내지 데이터베이스(Database, DB)일 수 있다. UDR은 단말의 가입 정보를 저장하고, UDM에게 단말의 가입 정보를 제공할 수 있다. 또한, UDR은 사업자 정책 정보를 저장하고, PCF에게 사업자 정책 정보를 제공할 수 있다. NSSF는 단말을 서비스하는 네트워크 슬라이스 인스턴스(network slice instances)를 선택하거나, NSSAI(Network Slice Selection Assistance Information)를 결정하는 기능을 수행하는 NF일 수 있다.According to one embodiment, the AMF (105) and MME (115) may be a Network Function (NF) that manages wireless network access and mobility for the terminal. SMF, SGW, and PGW are NFs that manage sessions for the terminal, and session information may include Quality of Service (QoS) information, charging information, and information about packet processing. Additionally, the UPF and PGW are NFs that process user plane traffic (e.g., user plane traffic) and are controlled by SMF and SGW. The PCF and PCRF may be NFs that manage operator policy (operator policy and/or PLMN policy) for providing services in a wireless communication system. Additionally, the PCF can be divided into a PCF in charge of Access and Mobility (AM) policy and UE policy and a PCF in charge of Session Management (SM) policy. The PCF in charge of AM/UE policy and the PCF in charge of SM policy may be logically or physically separate NFs, or may be a single logically or physically NF. UDM and HSS may be NFs that store and manage UE subscriber information (UE subscription). UDR may be an NF or database (DB) that stores and manages data. UDR stores the terminal's subscription information and can provide the terminal's subscription information to UDM. Additionally, UDR can store operator policy information and provide operator policy information to the PCF. NSSF may be an NF that performs the function of selecting network slice instances serving the terminal or determining Network Slice Selection Assistance Information (NSSAI).
인스턴스(Instance)는 NF가 소프트웨어의 코드 형태로 존재하며, 물리적인 컴퓨팅 시스템(예를 들어, 코어 네트워크 상에 존재하는 특정한 컴퓨팅 시스템)에서 NF의 기능을 수행하기 위해, 컴퓨팅 시스템으로부터 물리적 또는/및 논리적인 자원을 할당 받아서 NF의 기능을 실행 가능한 상태를 의미할 수 있다. 예를 들어, AMF Instance, SMF Instance, NSSF Instance 등은 각각 코어 네트워크 상에 존재하는 특정한 컴퓨팅 시스템으로부터 AMF, SMF, NSSF 등의 동작을 위해 물리적 또는/및 논리적 자원을 할당받아 사용할 수 있는 상태를 의미할 수 있다. 따라서, 물리적인 AMF, SMF, NSSF 장치가 존재하는 경우와 네트워크 상에 존재하는 특정한 컴퓨팅 시스템으로부터 AMF, SMF, NSSF 동작을 위해 물리적 또는/및 논리적 자원을 할당 받아 사용하는 AMF Instance, SMF Instance, NSSF Instance는 동일한 동작을 수행할 수 있다.An instance is an NF that exists in the form of software code, and is used to perform the functions of the NF in a physical computing system (e.g., a specific computing system that exists on a core network) from a computing system to a physical or/and It can refer to a state in which logical resources are allocated and NF functions can be executed. For example, AMF Instance, SMF Instance, NSSF Instance, etc. each refer to a state in which physical and/or logical resources can be allocated and used for the operation of AMF, SMF, NSSF, etc. from a specific computing system existing on the core network. can do. Therefore, when a physical AMF, SMF, or NSSF device exists, an AMF Instance, SMF Instance, or NSSF that uses physical and/or logical resources for AMF, SMF, and NSSF operations is allocated from a specific computing system existing on the network. Instance can perform the same operation.
5GS의 UDM과 EPS의 HSS는 하나의 콤보 노드(UDM+HSS 로 지칭)(124)로 구성될 수 있다. UDM+HSS 노드(124)는 단말의 가입자 정보를 저장할 수 있다. 5GS의 SMF와 EPS의 PGW-C는 하나의 콤보 노드(SMF+PGW-C 또는 PGW-C+SMF로 지칭)(122)로 구성될 수 있다. 여기서 5GS의 SMF와 EPS의 PGW-C가 하나의 콤보 노드로 구성되는 것을 의미하기 위한 것이므로, 약어의 표현은 SMF+PGW-C와 PGW-C+SMF 중 어느 것을 사용하더라도 동일한 장치로 이해될 수 있다.UDM of 5GS and HSS of EPS may be composed of one combo node (referred to as UDM+HSS) 124. The UDM+HSS node 124 can store subscriber information of the terminal. The SMF of 5GS and the PGW-C of EPS may be composed of one combo node (referred to as SMF+PGW-C or PGW-C+SMF) 122. Here, it is meant to mean that the SMF of 5GS and the PGW-C of EPS are composed of one combo node, so the expression of the abbreviation can be understood as the same device regardless of whether SMF+PGW-C or PGW-C+SMF is used. there is.
5GS의 UPF와 EPS의 PGW-U는 하나의 콤보 노드(UPF+PGW-U 또는 PGW-U+UPF로 지칭)(121)로 구성될 수 있다. 여기서 5GS의 UPF와 EPS의 PGW-U가 하나의 콤보 노드로 구성되는 것을 의미하기 위한 것이므로, 약어의 표현은 UPF+PGW-U와 PGW-U+UPF 중 어느 것을 사용하더라도 동일한 장치로 이해될 수 있다.The UPF of 5GS and the PGW-U of EPS may be composed of one combo node (referred to as UPF+PGW-U or PGW-U+UPF) 121. Here, it is meant to mean that the UPF of 5GS and the PGW-U of EPS are composed of one combo node, so the expression of the abbreviation can be understood as the same device regardless of whether UPF+PGW-U or PGW-U+UPF is used. there is.
5GS의 NEF와 EPS의 SCEF는 하나의 콤보 노드(NEF+SCEF 또는 SCEF+NEF로 지칭)로 구성될 수 있다. 여기서 5GS의 NEF와 EPS의 SCEF 가 하나의 콤보 노드로 구성되는 것을 의미하기 위한 것이므로, 약어의 표현은 NEF+SCEF 와 SCEF+NEF 중 어느 것을 사용하더라도 동일한 장치로 이해될 수 있다. CM NF는 NEF와 동일한 소프트웨어 또는 장치에 존재할 수도 있고, 별도의 소프트웨어 또는 장치에 존재할 수도 있다. 도 3에서는 NEF+SCEF와 동일한 장치에 존재하는 예를 도시하였으며, 이에 한정하지 않는다.NEF of 5GS and SCEF of EPS can be composed of one combo node (referred to as NEF+SCEF or SCEF+NEF). Here, since it is meant to mean that the NEF of 5GS and the SCEF of EPS are composed of one combo node, the expression of the abbreviation can be understood as the same device regardless of whether NEF+SCEF or SCEF+NEF is used. CM NF may exist in the same software or device as NEF, or may exist in separate software or device. Figure 3 shows an example that exists in the same device as NEF+SCEF, but is not limited to this.
단말(101)은 E-UTRA 기지국(113)을 통해 EPS의 MME(115)에 접속하여 EPS 네트워크 서비스를 이용할 수 있다. 또한, 단말(101)은 NR 기지국(103)을 통해 5GS의 AMF(105)에 접속하여 5GS 네트워크 서비스를 이용할 수 있다. 도 1에서 EPS에 접속한 단말(101)과 5GS에 접속한 단말(101)에 대해서는 동일한 참조부호를 사용하였다. 이는 단말(101)이 EPS에 접속할 수도 있고, 5GS에 접속할 수도 있는 단말임을 의미하기 위함이다. The terminal 101 can access the EPS MME 115 through the E-UTRA base station 113 and use the EPS network service. Additionally, the terminal 101 can access the 5GS AMF 105 through the NR base station 103 and use the 5GS network service. In Figure 1, the same reference numerals are used for the terminal 101 connected to EPS and the terminal 101 connected to 5GS. This is to mean that the terminal 101 is a terminal that can access EPS and 5GS.
이와 같이, 하나의 NF 또는 네트워크 엔터티가 서로 다른 네트워크 시스템을 동시에 지원할 수 있으며, 이러한 NF, 네트워크 노드 또는 네트워크 엔터티를 앞서 설명한 콤보 노드, 콤보 NF, 통합된(combined) 노드, 통합된 NF, 인터워킹(interworking) 노드, 인터워킹 NF 등으로 부를 수 있다. 또한 상기 콤보 노드로 예시된 NF의 기능은 둘 이상의 네트워크 엔터티들 간의 인터워킹을 통해 구현될 수도 있다. 뿐만 아니라, 도시와 설명의 편의상 "+" 기호 또는 "/" 기호를 이용하여 서로 다른 네트워크 시스템을 동시에 지원하는 NF를 표시할 수도 있다. 예를 들어, SMF와 PGW-C가 하나의 콤보 노드로 구성되는 경우, PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, 또는 SMF+PGW-C로 표현될 수 있다.In this way, one NF or network entity can support different network systems simultaneously, and these NFs, network nodes, or network entities can be referred to as the previously described combo node, combo NF, combined node, integrated NF, or interworking. It can be called an (interworking) node, interworking NF, etc. Additionally, the NF function illustrated by the combo node may be implemented through interworking between two or more network entities. In addition, for convenience of illustration and explanation, a "+" symbol or a "/" symbol can be used to indicate NFs that simultaneously support different network systems. For example, if SMF and PGW-C are composed of one combo node, it can be expressed as PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, or SMF+PGW-C.
단말(101)은 5GS 또는 EPS 시스템을 통해 데이터 네트워크(예를 들면, 인터넷 서비스를 제공하는 네트워크)에 접속하여 세션을 수립할 수 있다. 이때, 단말(101)은 데이터 네트워크 이름(Data Network Name, DNN) 또는 액세스 포인트 이름(Access Point Name, APN)이라는 식별자를 이용하여 각각의 데이터 네트워크를 구별할 수 있다. 데이터 네트워크 구별을 위해 5GS에서는 DNN을, EPS에서는 APN을 사용할 수 있다. DNN과 APN은 단말(101)이 네트워크 시스템과 세션을 연결함에 있어서 사용자 평면(user plane)과 관련된 NF, NF간 인터페이스, 사업자 정책 등을 결정하는데 사용될 수 있다. 상기 DNN과 상기 APN은 등가의 정보로 이해될 수 있으며, 동일한 정보를 전달할 수 있다. 상기 DNN은 예를 들어 PDU 세션에 대해 SMF와 UPF(들)을 선택하는데 이용될 수 있으며, PDU 세션에 대해 데이터 네트워크와 UPF 간의 인터페이스(예컨대, N6 인터페이스)(들)을 선택하는데 이용될 수 있다. 또한 상기 DNN은 PDU 세션에 적용하기 위한 이동 통신 사업자의 정책(policy)을 결정하는데 이용될 수 있다.The terminal 101 can establish a session by connecting to a data network (eg, a network providing Internet services) through the 5GS or EPS system. At this time, the terminal 101 can distinguish each data network using an identifier called a Data Network Name (DNN) or an Access Point Name (APN). To distinguish data networks, DNN can be used in 5GS and APN can be used in EPS. DNN and APN can be used to determine NFs related to the user plane, interfaces between NFs, operator policies, etc. when the terminal 101 connects a network system and a session. The DNN and the APN can be understood as equivalent information and can deliver the same information. The DNN may be used, for example, to select the SMF and UPF(s) for a PDU session, and may be used to select the interface (e.g., N6 interface) between the data network and the UPF for the PDU session. . Additionally, the DNN can be used to determine the mobile communication service provider's policy to apply to the PDU session.
하기 실시 예들에서 UDM+HSS 노드, NEF+SCEF 노드, SMF+PGW-C 노드, UPF+PGW-C 노드 등과 같은 콤보 노드는 설명의 편의상 "노드"의 명칭을 생략하여 기술하기로 한다. 그리고 하기 실시 예들에서 한 실시 예에서 정의된 메시지의 정의는 동일한 메시지를 이용하는 다른 실시 예에서도 동일한 의미로 적용될 수 있다. In the following embodiments, combo nodes such as UDM+HSS node, NEF+SCEF node, SMF+PGW-C node, UPF+PGW-C node, etc. will be described with the name “node” omitted for convenience of explanation. And in the following embodiments, the definition of a message defined in one embodiment may be applied in the same sense to other embodiments that use the same message.
도 4은 본 개시의 일 실시예에 따른 5GS와 EPS 간의 인터워킹을 지원하는 로컬 브레이크아웃 로밍(local breakout roaming) 무선 통신 시스템의 구조를 도시하는 도면이다.FIG. 4 is a diagram illustrating the structure of a local breakout roaming wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure.
로컬 브레이크아웃 로밍 시스템은 홈 사업자 네트워크(Home Public Land Mobile Network, HPLMN 또는 H-PLMN)와 방문 사업자 네트워크(Visited Public Land Mobile Network, VPLMN, 또는 V-PLMN)으로 구성될 수 있다.The local breakout roaming system may consist of a home operator network (Home Public Land Mobile Network, HPLMN, or H-PLMN) and a visited operator network (Visited Public Land Mobile Network, VPLMN, or V-PLMN).
VPLMN의 5GS는 NG-RAN, AMF, V-PCF를 포함할 수 있으며, 그 외에 SMF, UPF, NEF 등을 포함할 수 있다. VPLMN의 EPS는 E-UTRAN, MME, SGW, PGW, SCEF 등을 포함할 수 있다.VPLMN's 5GS may include NG-RAN, AMF, and V-PCF, and may also include SMF, UPF, and NEF. VPLMN's EPS may include E-UTRAN, MME, SGW, PGW, SCEF, etc.
HPLMN의 5GS는 H-PCF, UDM 등을 포함할 수 있으며, HPLMN의 EPS는 HSS 등을 포함할 수 있다.HPLMN's 5GS may include H-PCF, UDM, etc., and HPLMN's EPS may include HSS, etc.
- S6a: VPLMN의 MME와 HPLMN의 HSS 간의 참조 포인트- S6a: Reference point between MME in VPLMN and HSS in HPLMN
- T6a: VPLMN의 MME와 VPLMN의 SCEF 간의 참조 포인트- T6a: Reference point between MME of VPLMN and SCEF of VPLMN
- N10: VPLMN의 SMF와 HPLMN의 UDM 간의 참조 포인트- N10: Reference point between SMF in VPLMN and UDM in HPLMN
- N24: VPLMN의 PCF와 HPLMN의 PCF 간의 참조 포인트- N24: Reference point between PCF of VPLMN and PCF of HPLMN
- N30: VPLMN의 PCF와 VPLMN의 NEF 간의 참조 포인트- N30: Reference point between PCF of VPLMN and NEF of VPLMN
- N29: VPLMN의 SMF와 VPLMN의 NEF 간의 참조 포인트- N29: Reference point between SMF of VPLMN and NEF of VPLMN
- N51: VPLMN의 AMF와 VPLMN의 NEF 간의 참조 포인트- N51: Reference point between AMF of VPLMN and NEF of VPLMN
- N8: VPLMN의 AMF와 HPLMN의 UDM 간의 참조 포인트- N8: Reference point between AMF in VPLMN and UDM in HPLMN
도 5는 본 개시의 일 실시예에 따른 5G 시스템 비-로밍(non-roaming)의 구조를 도시하는 도면이다.FIG. 5 is a diagram illustrating the structure of 5G system non-roaming according to an embodiment of the present disclosure.
3GPP 시스템에서는 5G 시스템 내 NF들 간의 시그널링을 서비스 기반 인터페이스(service-based interface)라고 정의한다. 다음은 도 4에서 표현된 5G 시스템 비-로밍(non-raoming) 아키텍처에 포함되는 서비스 기반 인터페이스를 예시한다. CM NF는 NEF와 동일한 소프트웨어 또는 장치에 존재할 수도 있고, 별도의 소프트웨어 또는 장치에 존재할 수도 있다. 도 4에서는 NEF와 동일한 장치에 존재하는 예를 도시하였으며, 이에 한정하지 않는다.In the 3GPP system, signaling between NFs in the 5G system is defined as a service-based interface. The following illustrates a service-based interface included in the 5G system non-roaming architecture represented in FIG. 4. CM NF may exist in the same software or device as NEF, or may exist in separate software or device. Figure 4 shows an example that exists in the same device as the NEF, but is not limited to this.
- Nnssf: NSSF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nnssf: Service-based interface provided (exhibited) by NSSF
- Nnef: NEF 및 CM NF/NEF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nnef: Service-based interface provided (exhibited) by NEF and CM NF/NEF
- Nnrf: NRF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nnrf: Service-based interface provided (exhibited) by NRF
- Npcf: PCF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Npcf: Service-based interface provided (exhibited) by PCF
- Nudm: UDM에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nudm: Service-based interface provided (exhibited) by UDM
- Naf: AF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Naf: Service-based interface provided (exhibited) by AF
- Nnssaaf: NSSAAF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nnssaaf: Service-based interface provided (exhibited) by NSSAAF
- Nausf: AUSF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Nausf: Service-based interface provided (exhibited) by AUSF
- Namf: AMF에 의해 제공(exhibited)되는 서비스 기반 인터페이스- Namf: Service-based interface provided (exhibited) by AMF
Nsmf: SMF에 의해 제공(exhibited)되는 서비스 기반 인터페이스Nsmf: Service-based interface exhibited by SMF
도 6은 본 개시의 일 실시예에 따른 5G 시스템 로컬 브레이크아웃 로밍(local breakout roaming)의 구조를 도시하는 도면이다.FIG. 6 is a diagram illustrating the structure of local breakout roaming in a 5G system according to an embodiment of the present disclosure.
5G 시스템은 보안 엣지 보호 프록시(Security Edge Protection Proxy: SEPP)을 포함할 수 있다. HPLMN 5GC NF와 VPLMN 5GC NF는 홈 SEPP (hSEPP, HSEPP, H-SEPP)와 방문 SEPP (vSEPP, VSEPP, V-SEPP)를 통해서 통신할 수 있다.5G systems may include a Security Edge Protection Proxy (SEPP). HPLMN 5GC NF and VPLMN 5GC NF can communicate through home SEPP (hSEPP, HSEPP, H-SEPP) and visiting SEPP (vSEPP, VSEPP, V-SEPP).
- N32: hSEPP와 vSEPP 간의 참조 포인트- N32: Reference point between hSEPP and vSEPP
도 7은 본 개시의 일 실시예에 따른 커버리지 맵 정보 전달(coverage map transfer)을 위한 등록(registration) 절차를 도시하는 도면이다.FIG. 7 is a diagram illustrating a registration procedure for coverage map transfer according to an embodiment of the present disclosure.
1. 단말은 AMF에게 등록 요청을 송신할 수 있다. 등록 요청에는 CMT (Coverage Map Transfer) ID, CMT Data Container, CMS address 중 적어도 하나가 포함될 수 있다. 1. The terminal can send a registration request to the AMF. The registration request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container, and CMS address.
● CMT ID는 단말이 어떤 종류의 네트워크(예를 들어, 5GC 또는 EPC) 또는 어떤 사업자 네트워크(예를 들어, 서로 다른 PLMN)를 통해 CMS에 연결하더라도 단말을 식별할 수 있는 유일한(unique) ID를 의미할 수 있다. CMT ID는 CMS를 운영하는 사업자와 이동 통신 네트워크(코어 네트워크)를 운영하는 사업자 간의 사전 계약 또는 약속으로 UDM의 가입자 정보 데이터(subscription data)와 연동될 수 있다. CMT ID는 단말 내 장치 또는 USIM에 저장 또는 설정될 수 있다. ● CMT ID is a unique ID that can identify the terminal no matter what type of network (e.g., 5GC or EPC) or operator network (e.g., different PLMN) the terminal connects to CMS. It can mean. The CMT ID can be linked to UDM's subscriber information data (subscription data) through a prior contract or promise between the operator operating the CMS and the operator operating the mobile communication network (core network). The CMT ID can be stored or set in the device or USIM within the terminal.
● CMT Data Container는 단말과 CM NF가 컨테이너 내부의 데이터를 읽거나 편집할 수 있는 포맷으로 구성될 수 있다. 단말은 단말에게 필요한 커버리지 정보(coverage data) 또는 필요한 커버리지 정보를 표현하는 요청사항(coverage data request)을 CMT Data Container에 포함시킬 수 있다. 단말은 coverage data request를 CMT Data Container에 포함시키지 않고 바로 등록 요청 메시지에 포함시킬 수도 있으며, 이 경우에는 등록 요청을 수신한 NF(예를 들어 AMF)가 coverage data request를 읽을 수 있다. 단말에게 필요한 커버리지 정보를 표현하는 요청사항의 예로, 커버리지 정보 타입(coverage data type)(예를 들어, 커버리지 맵(coverage map), 경로 예측(trajectory estimation) 등이 해당될 수 있다), 커버리지 정보가 필요한 영역(coverage data required area), 커버리지 정보가 필요한 경로(coverage data required trajectory), 커버리지 정보가 필요한 위치(coverage data required position), 커버리지 정보의 정확도(required accuracy level) 등이 해당될 수 있다.● CMT Data Container can be configured in a format that allows the terminal and CM NF to read or edit the data inside the container. The terminal may include coverage information (coverage data) needed by the terminal or a request (coverage data request) expressing necessary coverage information in the CMT Data Container. The terminal may include the coverage data request directly in the registration request message without including it in the CMT Data Container. In this case, the NF (eg, AMF) that received the registration request can read the coverage data request. As an example of a request expressing the coverage information required for the terminal, the coverage information type (coverage data type) (e.g., coverage map, trajectory estimation, etc. may apply), coverage information This may include coverage data required area, coverage data required trajectory, coverage data required position, coverage information accuracy (required accuracy level), etc.
● CMS address는 예를 들어 CMS의 FQDN일 수 있다.● CMS address may be, for example, the FQDN of the CMS.
2. 단말의 등록 절차에서 필요한 주요 인증 절차가 수행될 수 있다.2. The main authentication procedures required during the terminal registration process can be performed.
3. AMF는 UDM으로부터 단말이 커버리지 정보를 획득하도록 허용되었는지 여부, 또는 위성의 이동과 관련된 정보를 획득하도록 허용되었는지 여부 등을 지시하는 가입자 정보 데이터를 확인할 수 있다.3. AMF can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from the UDM or whether it is allowed to obtain information related to the movement of the satellite.
3a. AMF는 UDM에게 단말의 가입자 정보를 요청할 수 있다. 이 요청에는 SUPI, CMT ID, 단말 위치 정보(UE Location Information) 중 적어도 하나가 포함될 수 있다. 단말 위치 정보에는 AMF가 단말 또는 RAN으로부터 수신한 정보로서 단말의 지리적 위치 좌표(예를 들어 GPS 좌표, GNSS 좌표 등), Cell ID, TAI 등이 포함될 수 있다. SUPI, 및/또는 CMT ID는 단말의 가입자 정보 접근 키(key)에 해당할 수 있다.3a. AMF can request subscriber information of the terminal from UDM. This request may include at least one of SUPI, CMT ID, and UE Location Information. The terminal location information is information received by the AMF from the terminal or RAN and may include the terminal's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc. SUPI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
3b. UDM은 AMF에게 단말의 가입자 정보를 제공할 수 있다. 이 가입자 정보는 액세스 및 이동성 관리 관련 가입자 정보 중에서 커버리지 맵 정보 전달 허용을 지시하는 정보를 의미할 수 있다.3b. UDM can provide subscriber information of the terminal to AMF. This subscriber information may refer to information indicating permission to transmit coverage map information among subscriber information related to access and mobility management.
4. AMF는 단말이 커버리지 정보를 수신할 수 있는지 여부, 및/또는 단말이 커버리지 정보를 수신하기 위해서 추가적인 인증 절차가 필요한지 여부를 판단할 수 있다. 예를 들어, (1) 단말이 CMT ID를 제공, (2) 단말의 가입자 정보에 커버리지 맵 정보 전달이 허용됨을 의미하는 정보가 존재 중 적어도 하나의 조건을 만족하는 경우, AMF는 단말이 커버리지 정보를 수신할 수 있는 것으로 판단할 수 있다. 또다른 예로, 상기 (1), (2)와 (3) 이전에 단말이 커버리지 정보를 수신하기 위한 추가 인증 절차가 수행되지 않았거나 성공적인 인증 결과가 없었던 경우, 중 적어도 하나의 조건을 만족하는 경우, AMF는 단말이 커버리지 정보를 수신할 수 있고, 커버리지 정보를 수신하기 위해 추가적인 인증 절차가 필요한 것으로 판단할 수 있다.4. AMF can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is allowed to be transmitted in the subscriber information of the terminal exists, the AMF determines whether the terminal provides coverage information. It can be determined that it can be received. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , AMF may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information.
5. 단말의 등록 절차가 계속해서 진행된다. 5a, 5b 외의 필요한 절차가 수행될 수 있으며, 도면과 설명에서 생략되었을 수 있다.5. The terminal registration process continues. Necessary procedures other than 5a and 5b may be performed and may be omitted from the drawings and description.
5a. AMF는 단말의 등록 요청을 수락할 수 있다.5a. AMF can accept the terminal's registration request.
5b. 단말은 AMF에게 등록 완료를 통지할 수 있다.5b. The terminal may notify AMF of completion of registration.
단계 4에서 단말이 커버리지 정보를 수신할 수 있는 단말인 것으로 판단된 경우, 커버리지 맵 정보 전달 절차가 수행될 수 있다. 커버리지 맵 정보 전달 절차는 AMF, MME, SMF, SMF+PGW-C 중 적어도 하나의 엔티티에 의해 개시될 수 있다.If it is determined in step 4 that the terminal is capable of receiving coverage information, a coverage map information transfer procedure may be performed. The coverage map information delivery procedure may be initiated by at least one entity among AMF, MME, SMF, and SMF+PGW-C.
도 8은 본 개시의 일 실시예에 따른 이동성 관리 기능(mobility management function)을 이용한 커버리지 맵 정보 전달(coverage map transfer) 절차를 도시하는 도면이다.FIG. 8 is a diagram illustrating a coverage map transfer procedure using a mobility management function according to an embodiment of the present disclosure.
도 8은 이동성 관리 기능을 담당하는 5GC 또는 EPC 네트워크 엔티티에 의해 커버리지 맵 정보 전달 절차가 개시되어 수행되는 방법을 설명한다. 이동성 관리 기능을 담당하는 네트워크 엔티티에는 AMF, MME 등이 포함될 수 있으며, 도 8에서는 AMF인 경우를 일 예로 설명하며, 이에 한정하지 않는다.Figure 8 illustrates how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the mobility management function. Network entities responsible for mobility management functions may include AMF, MME, etc. In FIG. 8, the case of AMF is explained as an example, but is not limited thereto.
도 8은 CM NF가 NEF와 동일한 장치에 구현된 경우를 일 예로 설명하며, 이에 한정하지 않는다. 도 8에서 설명하는 CM NF의 동작의 전체 또는 일부는 다른 네트워크 엔티티 (예를 들어 AMF, MME, NWDAF 등이 포함될 수 있다)에서 수행될 수 있다. 예를 들어, 도 8에서 설명하는 CM NF의 동작 중 커버리지 데이터의 요청을 전달하거나 커버리지 데이터를 전달하는 동작은 NEF에 구현된 CM NF에서 수행되고, 커버리지 데이터 요청의 변환 또는 커버리지 데이터의 변환 동작은 AMF에 구현된 CM NF에서 수행되는 형태로 CM NF의 기능이 서로 다른 네트워크 엔티티에 분산되어 구현되어 있을 수 있다.Figure 8 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 8 may be performed in another network entity (eg, AMF, MME, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 8, the operation of transmitting a request for coverage data or transmitting coverage data is performed in the CM NF implemented in NEF, and the operation of converting the coverage data request or converting the coverage data is performed in the CM NF implemented in NEF. The functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in AMF.
1. AMF는 단말의 등록 절차 중에 단말이 커버리지 정보를 수신할 수 있는 단말임을 판단하였거나, 단말이 커버리지 정보를 수신할 수 있는 단말이며 추가적인 인증 절차가 필요한 것으로 판단한 경우 등 (도 7에서 설명한 내용을 포함한다)의 상황에서 커버리지 정보 전달 절차를 개시할 수 있다.1. During the terminal registration process, the AMF determines that the terminal is a terminal capable of receiving coverage information, or determines that the terminal is a terminal capable of receiving coverage information and requires additional authentication procedures, etc. (refer to the details described in Figure 7) Coverage information delivery procedures can be initiated in situations (including).
2. AMF는 CM NF에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data Container(coverage data request), CMS address, UE Location Information 중 적어도 하나가 포함될 수 있다. GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information은 각각 도 7에서 설명한 것처럼 단말로부터 수신한 정보일 수 있으며, 단말로부터 수신하지 않았더라도 AMF가 필요하다고 판단한 경우 CM NF에게 제공할 수 있다. 예를 들어, AMF는 단말로부터 UE Location Information을 수신하지 않았더라도 단말의 위치 정보가 CMS 및/또는 CM NF가 수행하는 커버리지 정보 전달과 관련된 판단에 필요하다고 판단한 경우, UE Location Information을 커버리지 정보 전달을 위한 인증 요청에 포함시킬 수 있다.2. AMF may request authentication from CM NF to deliver coverage information. (If additional authentication is not required to deliver coverage information, you can request coverage information delivery.) This request includes at least one of GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information. may be included. GPSI, CMT ID, CMT Data Container, CMS address, and UE Location Information may each be information received from the terminal as described in FIG. 7, and can be provided to the CM NF if AMF determines it is necessary even if not received from the terminal. . For example, even if the AMF has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by CMS and/or CM NF, it uses the UE Location Information to deliver coverage information. It can be included in the authentication request for
3. CM NF는 AMF의 커버리지 정보 전달을 위한 인증 요청에 포함된 정보를 평가(evaluate)하여 CMS에 요청할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 정보는 CMT Data에 포함되어 CMS에게 제공될 수 있다. 3. CM NF can evaluate the information included in the authentication request for delivering AMF's coverage information and translate and generate it into content to be requested from CMS. The generated information can be included in CMT Data and provided to CMS.
● 예를 들어, CM NF는 AMF가 단말로부터 수신하여 제공한 coverage data request를 분석하여 편집할 수 있다. 보다 구체적으로 (1) CM NF는 요청 정보의 평가 단계에서 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석할 수 있다. (2) CM NF는 요청 정보의 생성 단계에서 3개의 위치 좌표로 이루어진 경로를 5개의 위치 좌표로 보간(interpolation)하였을 때 얻을 수 있는 5개의 위치 좌표를 생성할 수 있다. 즉, coverage data required trajectory가 P1, P2, P3의 위치 좌표로 이루어져있는 경우, P1-P2-P3로 이루어진 경로 T에 대하여 required accuracy level을 만족할 수 있는 Q1, Q2, Q3, Q4, Q5 위치 좌표를 생성할 수 있다. 이 때, Q1 내지 Q5는 P1 내지 P3를 포함할 수도 있고, 포함하지 않을 수도 있다. Q1 내지 Q5는 CMT Data에 포함되어 CMS에게 제공될 수 있다. ● For example, CM NF can analyze and edit the coverage data request received and provided by AMF from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage. In other words, if the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created. At this time, Q1 to Q5 may or may not include P1 to P3. Q1 to Q5 may be included in CMT Data and provided to CMS.
● 또 다른 예로, CM NF는 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, AMF가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함된 경우, CM NF는 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환할 수 있다. ● As another example, CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by the AMF to the CM NF includes a Cell ID or TAI, the CM NF may convert it into geographical location coordinates (eg, GPS coordinates or GNSS coordinates).
● CM NF는 요청 정보의 생성(예를 들어, Q1 내지 Q5를 계산 및 생성하는 동작, 단말의 위치 정보를 지형적 위치 좌표로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, LMF 일 수 있다)에게 요청하여 사용할 수 있다.● CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It may be AMF or LMF) and can be used by request.
4. CM NF는 CMS에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information 중 적어도 하나가 포함될 수 있다. GPSI, CMT ID, CMT Data Container (coverage data request를 포함할 수 있다), UE Location Information은 각각 도 7에서 설명한 것처럼 단말로부터 수신하였거나 및 단계 2에서 설명한 것처럼 AMF로부터 수신한 정보일 수 있으며, 단말 또는 AMF로부터 수신하지 않았더라도 CM NF가 필요하다고 판단한 경우 CMS에게 제공할 수 있다. coverage data request는 단계 3에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 3을 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 2에서 수신한 coverage data request를 그대로 전달하는 것을 의미할 수 있다.4. CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, transmission of coverage information may be requested.) This request includes at least one of GPSI, CMT ID, CMT Data (may include a coverage data request), and UE Location Information. may be included. GPSI, CMT ID, CMT Data Container (which may include a coverage data request), and UE Location Information may be information received from the terminal as described in FIG. 7 or from AMF as described in step 2, respectively, and may be received from the terminal or Even if it is not received from AMF, it can be provided to CMS if CM NF determines it is necessary. Coverage data request may refer to CMT Data generated by CM NF in step 3. If the CM NF did not perform step 3, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 2 as is.
5. CMS는 CMT ID로 식별되는 단말에 대하여, 커버리지 정보의 수신이 허용된 단말인지 여부를 인증하는 절차를 수행할 수 있다. CMS는 인증 절차에서 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information 중 적어도 하나를 참고할 수 있다. 예를 들어, CMS는 단말의 위치에 따라서 동일한 CMT ID에 대하여 인증 성공 결과를 제공할 수도 있고, 인증 실패 결과를 제공할 수도 있다. 5a 내지 5f는 CMS가 사용하는 인증 방법(method)에 따라서 한 번 또는 그 이상 반복 될 수 있다.5. CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information. CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), and UE Location Information in the authentication procedure. For example, CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal. 5a to 5f may be repeated once or more depending on the authentication method used by CMS.
5a. CMS는 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.5a. CMS can send a response to the authentication request to CM NF. This response may include GPSI, CMT ID, and authentication message.
5b. CM NF는 AMF에게 인증 응답을 전달할 수 있다.5b. CM NF can deliver an authentication response to AMF.
5c. AMF는 단말에게 인증 응답을 전달할 수 있다.5c. AMF can deliver an authentication response to the terminal.
5d. 단말은 AMF에게 CMS로부터 수신한 인증 응답에 대한 응답을 송신할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.5d. The terminal may transmit a response to the authentication response received from the CMS to the AMF. This response may include GPSI, CMT ID, and authentication message.
5e. AMF는 CM NF에게 응답을 전달할 수 있다.5e. AMF may deliver a response to CM NF.
5f. CM NF는 CMS에게 응답을 전달할 수 있다.5f. CM NF can deliver a response to CMS.
6. CMS는 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data (coverage data) 중 적어도 하나가 포함될 수 있다. 6. CMS can send a response to the authentication request to CM NF. This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
● Coverage data는 단계 4의 coverage data request의 내용에 기반하여 단말에게 제공하는 커버리지 정보를 의미할 수 있다. CMS는 단계 4에서 coverage data request를 수신하지 않았더라도, CMS에 판단에 따라 커버리지 정보를 제공할 수 있다.● Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 4. Even if CMS does not receive a coverage data request in step 4, it can provide coverage information to CMS at its discretion.
● 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 예를 들어, CMS는 단말이 현재의 위치에서는 커버리지 정보의 수신이 허용되지 않지만, 다른 위치에서는 커버리지 정보의 수신이 허용될 수 있는 단말에 해당하는 경우, 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공할 수 있다.● The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of whether authentication succeeds or fails and the reason for the authentication result. For example, CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
7. CM NF는 CMS가 제공한 커버리지 정보(coverage data) 를 평가(evaluate)하여 단말에 전달할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되어 AMF에게 제공될 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되지 않고 단계 8에서 인증 응답 메시지에 그대로 포함될 수도 있으며 이 경우, 커버리지 정보를 AMF가 직접 읽을 수 있다. 상기 단계 3에서 수행된 변환 과정의 역변환 과정이 수행될 수 있다.7. CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal. The generated coverage information can be included in the CMT Data Container and provided to AMF. The generated coverage information may not be included in the CMT Data Container but may be included in the authentication response message in step 8. In this case, the AMF can read the coverage information directly. The reverse conversion process of the conversion process performed in step 3 may be performed.
● 예를 들어, 단계 3의 예에서와 같이 CM NF가 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석하여, 총 5개의 위치 좌표를 CMT Data에 포함시켜 CMS에게 커버리지 데이터를 요청했던 경우, CM NF는 CMS로부터 수신한 5개의 위치 좌표에 대한 커버리지 데이터(예를 들어, Q1 내지 Q5 위치에서의 시간 별 커버리지 존재 여부 등)를 AMF에게 제공할 수 있다. ● For example, as in the example of step 3, the CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level. In order to do this, it is analyzed that 5 location coordinates are needed, and when coverage data is requested from CMS by including a total of 5 location coordinates in CMT Data, CM NF provides coverage data for the 5 location coordinates received from CMS (e.g. For example, whether coverage exists by time at locations Q1 to Q5, etc.) can be provided to the AMF.
● 또 다른 예로, 단계 3의 예에서와 같이 CM NF가 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환하였던 경우, CMS가 제공한 커버리지 데이터를 다시 네트워크 엔티티가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, 단계 3에서 AMF가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함되었고, CM NF가 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환하여 CMS에게 요청하였던 경우, CM NF는 CMS로부터 수신한 지형적 위치 좌표를 다시 Cell ID 또는 TAI로 변환하여 AMF에게 제공할 수 있다. ● As another example, as in the example of step 3, if the CM NF has converted the terminal location information into a format that the CMS can interpret, the coverage data provided by the CMS must be converted back to a format that the network entity can interpret. You can. More specifically, in step 3, the UE Location Information provided by AMF to CM NF included Cell ID or TAI, and CM NF converted it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates) and requested it from CMS. In this case, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to AMF.
● CM NF는 커버리지 데이터의 생성(예를 들어, 단말의 지형적 위치 좌표를 단말의 위치 정보로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, LMF 일 수 있다)에게 요청하여 사용할 수 있다.● CM NF provides information necessary for the creation of coverage data (e.g., converting the geographic location coordinates of the terminal into location information of the terminal) to other network entities (e.g., it may be NWDAF, AMF, LMF). It is available upon request.
8. CM NF는 커버리지 정보 전달을 위한 인증 요청에 대하여 응답할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보를 전달할 수 있다.) 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data(coverage data) 중 적어도 하나가 포함될 수 있다. AMF는 커버리지 정보 전달을 위한 인증의 결과 및/또는 coverage data에 기반하여, 단말의 등록 해제(deregistration), 단말의 이동성 등록 업데이트(mobility registration update) 요청에 대한 응답, 단말의 전원 절약 모드(power saving mode) 적용 등에 대한 판단을 수행할 수 있다.8. CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data) may be included. AMF performs deregistration of the terminal, response to the mobility registration update request of the terminal, and power saving mode of the terminal based on the results of authentication and/or coverage data for delivering coverage information. mode) can make judgments about application, etc.
● coverage data 는 단계 7에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 7을 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 6에서 수신한 coverage data 를 그대로 전달하는 것을 의미할 수 있다.● Coverage data may refer to CMT Data generated by CM NF in step 7. If the CM NF did not perform step 7, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 6 as is.
● 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 6에서 CMS로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 6에서 수신한 내용을 기반으로 CM NF가 판단하여 결정한 내용일 수도 있다. 예를 들어, CMS가 단계 8에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공한 경우, CM NF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말의 등록 해제(deregistration)이 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed)의 이유(cause)를 제공할 수도 있다.● The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of whether authentication succeeds or fails and the reason for the authentication result. The result of authentication for delivering coverage information may be the same as the result of authentication for delivering coverage information received from CMS in step 6, or may be determined by the CM NF based on the content received in step 6. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 8, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received, an indicator is additionally provided indicating that deregistration of the terminal is not needed, or a reason for deregistration of the terminal is not needed. may also be provided.
9. AMF는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련되어 변경사항이 발생하였을 경우 통지 받을 수 있도록 요청할 수 있다. CM NF는 AMF에게 단말의 액세스 및 이동성과 관련되어 변경사항이 발생하였을 경우 지 받을 수 있도록 요청할 수 있다. 9. AMF may request that the CM NF be notified if changes occur related to the results of certification for delivering coverage data and/or coverage information. CM NF may request AMF to receive notification when changes occur related to access and mobility of the terminal.
10. AMF는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. CM NF는 AMF에게 단말의 액세스 및 이동성과 관련된 변경사항의 통지를 더 이상 받지 않도록요청할 수 있다. 10. AMF may request that CM NF no longer receive notifications of changes related to coverage data and/or the results of certification for the delivery of coverage information. CM NF may request that AMF no longer receive notifications of changes related to access and mobility of the terminal.
11. AMF는 단말에게 커버리지 정보 전달을 위한 인증 요청에 대한 응답을 전달할 수 있다. 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과 중 적어도 하나가 포함될 수 있다.11. AMF can deliver a response to the authentication request for delivering coverage information to the terminal. This response may include at least one of GPSI, CMT ID, authentication message, and authentication result for delivering coverage information.
● 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 8에서 CM NF로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 8에서 수신한 내용을 기반으로 AMF가 판단하여 결정한 내용일 수도 있다. 예를 들어, CM NF가 단계 8에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공한 경우, AMF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말의 등록 해제(deregistration)이 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed)의 이유(cause)를 제공할 수도 있다. AMF는 단말로부터 커버리지 데이터를 수신하지 않고도 동작할 수 있는 능력(capability)이 있음을 알 수 있는 정보를 수신한 경우, 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단할 수 있다. 이러한 단말의 능력과 관련된 정보는 단말이 AMF에게 송신한 등록 요청 메시지에 UE 능력(UE Capability) 등의 정보에 포함되어 제공될 수 있다.● The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of whether authentication succeeds or fails and the reason for the authentication result. The result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the CM NF in step 8, or may be determined by the AMF based on the content received in step 8. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 8, the AMF is configured to operate in a state in which the terminal has not received coverage information. If it is determined that registration management or session management can be received, an indicator is additionally provided indicating that deregistration of the terminal is not needed, or a reason for deregistration of the terminal is not needed. may also be provided. When AMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge. Information related to the capabilities of the terminal may be provided by being included in information such as UE Capability in a registration request message sent from the terminal to the AMF.
12. CM NF는 AMF에게 커버리지 정보를 단말에게 전달하도록 요청할 수 있다. 이 요청에는 GPSI, CMT ID, CMT Data Container (coverage data) 중 적어도 하나가 포함될 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있으며 이 경우, 커버리지 정보를 AMF가 직접 읽을 수도 있다.12. CM NF may request AMF to deliver coverage information to the terminal. This request may include at least one of GPSI, CMT ID, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message as is. In this case, the AMF may read the coverage information directly.
13. AMF는 커버리지 정보를 단말에게 전달할 수 있다. 이를 위해 단말 설정 업데이트(UE Configuration Update) 절차가 수행될 수 있으며, 이 때 GPSI, CMT ID, CMT Data Container (coverage data) 중 적어도 하나가 포함될 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있다.13. AMF can deliver coverage information to the terminal. For this purpose, a UE Configuration Update procedure may be performed, and at this time, at least one of GPSI, CMT ID, and CMT Data Container (coverage data) may be included. Coverage information may not be included in the CMT Data Container but may be included in the message.
14. 단말은 수신한 커버리지 데이터를 저장 및 처리할 수 있고, 필요한 다른 절차를 수행할 수 있다. 이 때 단말은 단계 11에서 수신한 커버리지 정보 전달을 위한 인증의 결과를 참고할 수 있다.14. The terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the result of authentication for delivering coverage information received in step 11.
● 예를 들어, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 다른 액세스 네트워크의 커버리지에 가까워지고 있음을 알 수 있는 경우, 해당 액세스 네트워크로 연결을 이동시킬 수 있다.● For example, if the terminal is moving away from the coverage of the currently connected access network and can know that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to that access network. can be moved.
● 또 다른 예로, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 연결될 수 있는 다른 액세스 네트워크가 없음을 알 수 있는 경우, 등록 해제 절차를 개시하거나 전원 절약 모드(power saving mode)를 이용하여 현재 연결된 액세스 네트워크의 커버리지가 다시 회복할 때까지 기다릴 수 있다.● As another example, if the terminal is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this coverage data that it has stored, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
● 예를 들어, 단말이 단계 11에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유, 또는 단말의 등록 해제(deregistration)이 필요하지 않음을 알리는 지시자(또는 이를 알리는 이유)를 수신한 경우, 단말은 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말을 등록 해제하지 않고 계속해서 코어네트워크와의 연결을 유지할 수 있다.● For example, an indicator indicating that the terminal is not allowed at the current location with an authentication result of failure in step 11, or that deregistration of the terminal is not necessary. (or the reason for notifying this) is received, and if the terminal determines that it can receive registration management or session management without receiving coverage information, it can continue to maintain connection to the core network without deregistering the terminal. .
또 다른 예로, 단말이 단계 11에서 실패(failure)의 인증 결과를 수신하였고, 단말이 커버리지 데이터를 수신하지 않은 상태에서 동작할 수 없을 것으로 판단한 경우 단말은 등록 해제 절차를 개시할 수 있다.As another example, if the terminal receives an authentication result of failure in step 11 and determines that the terminal will not be able to operate without receiving coverage data, the terminal may initiate a deregistration procedure.
도 9 본 개시의 일 실시예에 따른 PDU 세션 관리 절차에서 커버리지 맵 정보 전달(coverage map transfer)하는 방법 도시하는 도면이다.FIG. 9 is a diagram illustrating a method of transferring coverage map information in a PDU session management procedure according to an embodiment of the present disclosure.
도 9의 방법은 도 7 및 도 8에서 등록 절차 중에 AMF가 수행하는 동작이 PDU 세션 수립 절차 중에 SMF가 수행하는 동작으로 대체되는 특징을 갖고 있다. 따라서, 도 9의 방법의 일부는 도 7 및 도 8의 방법과 공통적인 동작을 포함할 수 있으며, 일부 설명이 생략되었을 수 있다.The method of FIG. 9 has the feature that the operation performed by the AMF during the registration procedure in FIGS. 7 and 8 is replaced by the operation performed by the SMF during the PDU session establishment procedure. Accordingly, some of the methods of FIG. 9 may include operations common to the methods of FIGS. 7 and 8, and some descriptions may be omitted.
도 9는 세션 관리 기능을 담당하는 5GC 또는 EPC 네트워크 엔티티에 의해 커버리지 맵 정보 전달 절차가 개시되어 수행되는 방법을 설명한다. 세션 관리 기능을 담당하는 네트워크 엔티티에는 SMF 등이 포함될 수 있으며, 도 9에서는 SMF인 경우를 일 예로 설명하며, 이에 한정하지 않는다.Figure 9 illustrates how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the session management function. The network entity responsible for the session management function may include SMF, etc., and FIG. 9 illustrates the case of SMF as an example, but is not limited thereto.
도 9은 CM NF가 NEF와 동일한 장치에 구현된 경우를 일 예로 설명하며, 이에 한정하지 않는다. 도 9에서 설명하는 CM NF의 동작의 전체 또는 일부는 다른 네트워크 엔티티 (예를 들어 SMF, NWDAF 등이 포함될 수 있다)에서 수행될 수 있다. 예를 들어, 도 9에서 설명하는 CM NF의 동작 중 커버리지 데이터의 요청을 전달하거나 커버리지 데이터를 전달하는 동작은 NEF에 구현된 CM NF에서 수행되고, 커버리지 데이터 요청의 변환 또는 커버리지 데이터의 변환 동작은 SMF에 구현된 CM NF에서 수행되는 형태로 CM NF의 기능이 서로 다른 네트워크 엔티티에 분산되어 구현되어 있을 수 있다.Figure 9 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 9 may be performed in another network entity (e.g., SMF, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 9, the operation of transmitting a request for coverage data or delivering coverage data is performed in the CM NF implemented in NEF, and the conversion of the coverage data request or the conversion of coverage data is performed in the CM NF implemented in NEF. The functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in SMF.
1. 단말은 AMF에게 PDU 세션 수립 요청을 송신할 수 있다. 이 요청에는 CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), CMS address 중 적어도 하나가 포함될 수 있다.1. The terminal may transmit a PDU session establishment request to the AMF. This request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), and CMS address.
2. AMF는 SMF에게 PDU 세션을 위한 세션 관리 컨텍스트 생성 요청을 송신할 수 있다. 이 요청에는 CMT ID, CMT Data Container(coverage data request), CMS address, UE Location Information 중 적어도 하나가 포함될 수 있다. CMT ID, CMT Data Container, CMS address, UE Location Information은 각각 도 7 및 도 8에서 설명한 것처럼 단말로부터 수신한 정보일 수 있으며, 단말로부터 수신하지 않았더라도 AMF가 필요하다고 판단한 경우 CM NF에게 제공할 수 있다. 예를 들어, AMF는 단말로부터 UE Location Information을 수신하지 않았더라도 단말의 위치 정보가 CMS 및/또는 CM NF가 수행하는 커버리지 정보 전달과 관련된 판단에 필요하다고 판단한 경우, UE Location Information을 커버리지 정보 전달을 위한 인증 요청에 포함시킬 수 있다.2. AMF may send a request to create a session management context for a PDU session to the SMF. This request may include at least one of CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information. CMT ID, CMT Data Container, CMS address, and UE Location Information may be information received from the terminal as described in Figures 7 and 8, respectively. Even if not received from the terminal, they can be provided to the CM NF if AMF determines it is necessary. there is. For example, even if the AMF has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by CMS and/or CM NF, it uses the UE Location Information to deliver coverage information. It can be included in the authentication request for
3. SMF는 UDM으로부터 단말이 커버리지 정보를 획득하도록 허용되었는지 여부, 또는 위성의 이동과 관련된 정보를 획득하도록 허용되었는지 여부 등을 지시하는 가입자 정보 데이터를 확인할 수 있다.3. The SMF can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from the UDM or whether it is allowed to obtain information related to the movement of the satellite.
3a. SMF는 UDM에게 단말의 가입자 정보를 요청할 수 있다. 이 요청에는 SUPI, DNN, S-NSSAI, CMT ID, 단말 위치 정보(UE Location Information) 중 적어도 하나가 포함될 수 있다. 단말 위치 정보에는 AMF가 단말 또는 RAN으로부터 수신한 정보로서 단말의 지리적 위치 좌표(예를 들어 GPS 좌표, GNSS 좌표 등), Cell ID, TAI 등이 포함될 수 있다. SUPI, DNN, S-NSSAI, 및/또는 CMT ID는 단말의 가입자 정보 접근 키(key)에 해당할 수 있다.3a. The SMF can request the subscriber information of the terminal from the UDM. This request may include at least one of SUPI, DNN, S-NSSAI, CMT ID, and UE Location Information. The terminal location information is information received by the AMF from the terminal or RAN and may include the terminal's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc. SUPI, DNN, S-NSSAI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
3b. UDM은 SMF에게 단말의 가입자 정보를 제공할 수 있다. 이 가입자 정보는 세션 관리 관련 가입자 정보 중에서 커버리지 맵 정보 전달 허용을 지시하는 정보를 의미할 수 있다.3b. UDM can provide subscriber information of the terminal to SMF. This subscriber information may refer to information indicating permission to transmit coverage map information among session management-related subscriber information.
4. SMF는 단말이 커버리지 정보를 수신할 수 있는지 여부, 및/또는 단말이 커버리지 정보를 수신하기 위해서 추가적인 인증 절차가 필요한지 여부를 판단할 수 있다. 예를 들어, (1) 단말이 CMT ID를 제공, (2) 단말의 가입자 정보에 커버리지 맵 정보 전달이 허용됨을 의미하는 정보가 존재 중 적어도 하나의 조건을 만족하는 경우, SMF는 단말이 커버리지 정보를 수신할 수 있는 것으로 판단할 수 있다. 또다른 예로, 상기 (1), (2)와 (3) 이전에 단말이 커버리지 정보를 수신하기 위한 추가 인증 절차가 수행되지 않았거나 성공적인 인증 결과가 없었던 경우, 중 적어도 하나의 조건을 만족하는 경우, SMF는 단말이 커버리지 정보를 수신할 수 있고, 커버리지 정보를 수신하기 위해 추가적인 인증 절차가 필요한 것으로 판단할 수 있다. SMF는 CM NF에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data Container(coverage data request), CMS address, UE Location Information, PEI, UE IP address 중 적어도 하나가 포함될 수 있다. 예를 들어, SMF는 단말이 동일한 CMT ID를 사용하여 하나 이상의 PDU 세션을 사용하고 있거나, 하나 이상의 단말이 동일한 CMT ID를 사용하고 있는 경우, 특정 단말 및/또는 특정 단말이 사용하고 있는 특 정 PDU 세션을 식별하기 위하여 UE IP address (또는 PDU Session ID)를 제공할 수 있다. GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, UE IP address는 각각 도 7 및 도 8에서 설명한 것처럼 단말 및/또는 AMF로부터 수신한 정보일 수 있으며, 단말 및/또는 AMF로부터 수신하지 않았더라도 SMF가 필요하다고 판단한 경우 CM NF에게 제공할 수 있다. 예를 들어, SMF는 단말로부터 UE Location Information 을 수신하지 않았더라도 단말의 위치 정보가 CMS 및/또는 CM NF가 수행하는 커버리지 정보 전달과 관련된 판단에 필요하다고 판단한 경우, UE Location Information을 커버리지 정보 전달을 위한 인증 요청에 포함시킬 수 있다.4. The SMF can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is permitted to be transmitted in the subscriber information of the terminal exists, the SMF determines whether the terminal provides coverage information. It can be determined that it can be received. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , the SMF may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information. SMF may request authentication for delivering coverage information to CM NF. (If additional authentication is not required to deliver coverage information, you can request coverage information delivery.) This request includes GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, UE Location Information, PEI, UE. At least one IP address may be included. For example, if a terminal is using one or more PDU sessions using the same CMT ID, or if more than one terminal is using the same CMT ID, SMF The UE IP address (or PDU Session ID) can be provided to identify the session. GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, and UE IP address may be information received from the terminal and/or AMF as described in Figures 7 and 8, respectively, and may be received from the terminal and/or AMF Even if it is not received, it can be provided to CM NF if SMF determines it is necessary. For example, even if the SMF has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by the CMS and/or CM NF, it uses the UE Location Information to deliver the coverage information. It can be included in the authentication request for
5. CM NF는 SMF의 커버리지 정보 전달을 위한 인증 요청에 포함된 정보를 평가(evaluate)하여 CMS에 요청할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 정보는 CMT Data에 포함되어 CMS에게 제공될 수 있다. 5. CM NF can evaluate the information included in the authentication request for delivering SMF's coverage information and translate and generate the content to be requested from CMS. The generated information can be included in CMT Data and provided to CMS.
● 예를 들어, CM NF는 SMF가 단말로부터 수신하여 제공한 coverage data request를 분석하여 편집할 수 있다. 보다 구체적으로 (1) CM NF는 요청 정보의 평가 단계에서 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석할 수 있다. (2) CM NF는 요청 정보의 생성 단계에서 3개의 위치 좌표로 이루어진 경로를 5개의 위치 좌표로 보간(interpolation)하였을 때 얻을 수 있는 5개의 위치 좌표를 생성할 수 있다. 즉, coverage data required trajectory가 P1, P2, P3의 위치 좌표로 이루어져있는 경우, P1-P2-P3로 이루어진 경로 T에 대하여 required accuracy level을 만족할 수 있는 Q1, Q2, Q3, Q4, Q5 위치 좌표를 생성할 수 있다. 이 때, Q1 내지 Q5는 P1 내지 P3를 포함할 수도 있고, 포함하지 않을 수도 있다. Q1 내지 Q5는 CMT Data에 포함되어 CMS에게 제공될 수 있다. ● For example, CM NF can analyze and edit the coverage data request received and provided by SMF from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage. In other words, if the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created. At this time, Q1 to Q5 may or may not include P1 to P3. Q1 to Q5 may be included in CMT Data and provided to CMS.
● 또 다른 예로, CM NF는 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, SMF가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함된 경우, CM NF는 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환할 수 있다. ● As another example, CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by the SMF to the CM NF includes Cell ID or TAI, the CM NF may convert it into geographical location coordinates (eg, GPS coordinates or GNSS coordinates).
● CM NF는 요청 정보의 생성(예를 들어, Q1 내지 Q5를 계산 및 생성하는 동작, 단말의 위치 정보를 지형적 위치 좌표로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, SMF, LMF 일 수 있다)에게 요청하여 사용할 수 있다.● CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It can be used by requesting it from AMF, SMF, or LMF).
6. CM NF는 CMS에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address 중 적어도 하나가 포함될 수 있다. GPSI, CMT ID, CMT Data Container (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address는 각각 도 7 및 도 8에서 설명한 것처럼 단말로부터 수신하였거나 및 단계 2 및 단계 4에서 설명한 것처럼 AMF 및/또는 SMF로부터 수신한 정보일 수 있으며, 단말, AMF, 및/또는 SMF 로부터 수신하지 않았더라도 CM NF가 필요하다고 판단한 경우 CMS에게 제공할 수 있다. coverage data request는 단계 5에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 5을 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 4에서 수신한 coverage data request를 그대로 전달하는 것을 의미할 수 있다.6. CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, you can request coverage information transmission.) This request includes GPSI, CMT ID, CMT Data (may include coverage data request), UE Location Information, PEI, At least one of the UE IP addresses may be included. GPSI, CMT ID, CMT Data Container (which may include a coverage data request), UE Location Information, PEI, and UE IP address are received from the terminal as described in Figures 7 and 8, respectively, or as described in steps 2 and 4. As such, it may be information received from AMF and/or SMF, and even if not received from the terminal, AMF, and/or SMF, it may be provided to CMS if CM NF determines it is necessary. Coverage data request may refer to CMT Data generated by CM NF in step 5. If the CM NF did not perform step 5, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 4 as is.
7. CMS는 CMT ID로 식별되는 단말에 대하여, 커버리지 정보의 수신이 허용된 단말인지 여부를 인증하는 절차를 수행할 수 있다. CMS는 인증 절차에서 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address 중 적어도 하나를 참고할 수 있다. 예를 들어, CMS는 단말의 위치 또는 UE IP address에 따라서 동일한 CMT ID에 대하여 인증 성공 결과를 제공할 수도 있고, 인증 실패 결과를 제공할 수도 있다. 7a 내지 7h는 CMS가 사용하는 인증 방법(method)에 따라서 한 번 또는 그 이상 반복 될 수 있다.7. CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information. CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), UE Location Information, PEI, and UE IP address in the authentication procedure. For example, the CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal or the UE IP address. 7a to 7h may be repeated once or more depending on the authentication method used by CMS.
7a. CMS는 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.7a. CMS can send a response to the authentication request to CM NF. This response may include GPSI, CMT ID, and authentication message.
7b. CM NF는 SMF에게 인증 응답을 전달할 수 있다.7b. CM NF can deliver an authentication response to SMF.
7c. SMF는 AMF에게 인증 응답을 전달할 수 있다.7c. SMF can deliver an authentication response to AMF.
7d. AMF는 단말에게 인증 응답을 전달할 수 있다.7d. AMF can deliver an authentication response to the terminal.
7e. 단말은 AMF에게 CMS로부터 수신한 인증 응답에 대한 응답을 송신할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.7e. The terminal may transmit a response to the authentication response received from the CMS to the AMF. This response may include GPSI, CMT ID, and authentication message.
7f. AMF는 SMF에게 응답을 전달할 수 있다.7f. AMF can deliver a response to SMF.
7g. SMF는 CM NF에게 응답을 전달할 수 있다.7g. SMF can deliver a response to CM NF.
7h. CM NF는 CMS에게 응답을 전달할 수 있다.7h. CM NF can deliver a response to CMS.
8. CMS는 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data (coverage data) 중 적어도 하나가 포함될 수 있다. 8. CMS can send a response to the authentication request to CM NF. This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
● Coverage data는 단계 6의 coverage data request의 내용에 기반하여 단말에게 제공하는 커버리지 정보를 의미할 수 있다. CMS는 단계 6에서 coverage data request를 수신하지 않았더라도, CMS에 판단에 따라 커버리지 정보를 제공할 수 있다.● Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 6. Even if CMS does not receive a coverage data request in step 6, it can provide coverage information to CMS at its discretion.
● 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 예를 들어, CMS는 단말이 현재의 위치에서는 커버리지 정보의 수신이 허용되지 않지만, 다른 위치에서는 커버리지 정보의 수신이 허용될 수 있는 단말에 해당하는 경우, 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공할 수 있다.● The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of whether authentication succeeds or fails and the reason for the authentication result. For example, CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
9. CM NF는 CMS가 제공한 커버리지 정보(coverage data) 를 평가(evaluate)하여 단말에 전달할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되어 SMF에게 제공될 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되지 않고 단계 8에서 인증 응답 메시지에 그대로 포함될 수도 있으며 이 경우, 커버리지 정보를 SMF(AMF까지 전달되는 경우 AMF도 포함될 수 있다)가 직접 읽을 수 있다. 상기 단계 5에서 수행된 변환 과정의 역변환 과정이 수행될 수 있다.9. CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal. The generated coverage information can be included in the CMT Data Container and provided to the SMF. The generated coverage information may not be included in the CMT Data Container but may be directly included in the authentication response message in step 8. In this case, the SMF (if delivered to the AMF may also be included in the AMF) can read the coverage information directly. The reverse conversion process of the conversion process performed in step 5 may be performed.
● 예를 들어, 단계 5의 예에서와 같이 CM NF가 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석하여, 총 5개의 위치 좌표를 CMT Data에 포함시켜 CMS에게 커버리지 데이터를 요청했던 경우, CM NF는 CMS로부터 수신한 5개의 위치 좌표에 대한 커버리지 데이터(예를 들어, Q1 내지 Q5 위치에서의 시간 별 커버리지 존재 여부 등)를 SMF에게 제공할 수 있다. ● For example, as in the example of step 5, the CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level. In order to do this, it is analyzed that 5 location coordinates are needed, and when coverage data is requested from CMS by including a total of 5 location coordinates in CMT Data, CM NF provides coverage data for the 5 location coordinates received from CMS (e.g. For example, whether coverage exists by time at locations Q1 to Q5, etc.) can be provided to the SMF.
● 또 다른 예로, 단계 5의 예에서와 같이 CM NF가 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환하였던 경우, CMS가 제공한 커버리지 데이터를 다시 네트워크 엔티티가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, 단계 4에서 SMF가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함되었고, CM NF가 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환하여 CMS에게 요청하였던 경우, CM NF는 CMS로부터 수신한 지형적 위치 좌표를 다시 Cell ID 또는 TAI로 변환하여 SMF에게 제공할 수 있다. ● As another example, as in the example of step 5, if the CM NF has converted the terminal location information into a format that the CMS can interpret, the coverage data provided by the CMS must be converted back into a format that the network entity can interpret. You can. More specifically, in step 4, the UE Location Information provided by the SMF to the CM NF included Cell ID or TAI, and the CM NF converted it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates) and requested it from CMS. In this case, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to SMF.
● CM NF는 커버리지 데이터의 생성(예를 들어, 단말의 지형적 위치 좌표를 단말의 위치 정보로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, LMF 일 수 있다)에게 요청하여 사용할 수 있다.● CM NF provides information necessary for the creation of coverage data (e.g., converting the geographic location coordinates of the terminal into location information of the terminal) to other network entities (e.g., it may be NWDAF, AMF, LMF). It is available upon request.
10. CM NF는 커버리지 정보 전달을 위한 인증 요청에 대하여 응답할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보를 전달할 수 있다.) 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data(coverage data), CMT Data Container(coverage data) 중 적어도 하나가 포함될 수 있다. SMF는 커버리지 정보 전달을 위한 인증의 결과 및/또는 coverage data에 기반하여, 단말의 등록 해제(deregistration), PDU 세션 해제(release), 사용자 평면 리소스 해제(release), 단말의 전원 절약 모드(power saving mode) 적용 등에 대한 판단을 수행할 수 있다.10. CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data), CMT Data Container (coverage data) may be included. SMF performs terminal deregistration, PDU session release, user plane resource release, and power saving mode of the terminal based on the results of authentication and/or coverage data for delivering coverage information. mode) can make judgments about application, etc.
● coverage data 는 단계 9에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 9를 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 8에서 수신한 coverage data 를 그대로 전달하는 것을 의미할 수 있다.● Coverage data may refer to CMT Data generated by CM NF in step 9. If the CM NF did not perform step 9, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 8 as is.
● 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 8에서 CMS로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 8에서 수신한 내용을 기반으로 CM NF가 판단하여 결정한 내용일 수도 있다. 예를 들어, CMS가 단계 8에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공한 경우, CM NF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말의 등록 해제(deregistration) 및/또는 PDU 세션 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDU 세션 해제(release)가 필요하지 않음(PDU Session release not needed)의 이유(cause)를 제공할 수도 있다.● The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of whether authentication succeeds or fails and the reason for the authentication result. The result of the authentication for coverage information delivery may be the same as the result of the authentication for coverage information delivery received from CMS in step 8, or may be determined by the CM NF based on the content received in step 8. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 8, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received in the A cause may be provided for deregistration not needed and/or PDU Session release not needed.
11. CMS는 SMF에게 UDM을 통하여 세션 관리와 관련된 변경사항이 발생하였을 경우 통지 받을 수 있도록 요청할 수 있다. 11. CMS may request SMF to be notified when changes related to session management occur through UDM.
12. CMS는 SMF에게 UDM을 통하여 세션 관리와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. 12. CMS may request that SMF no longer receive notifications of changes related to session management through UDM.
13. SMF는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련되어 변경사항이 발생하였을 경우 통지 받을 수 있도록 요청할 수 있다. CM NF는 SMF에게 세션 관리와 관련된 변경사항이 발생하였을 경우 지 받을 수 있도록 요청할 수 있다. 13. The SMF may request that the CM NF be notified when changes occur related to the results of authentication for delivering coverage data and/or coverage information. CM NF may request SMF to receive notification when changes related to session management occur.
14. SMF는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. CM NF는 SMF에게 세션 관리와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. 14. The SMF may request that the CM NF no longer receive notification of changes related to coverage data and/or the results of authentication for the delivery of coverage information. The CM NF may request that the SMF no longer receive notifications of changes related to session management.
15. SMF는 PDU 세션 수립 절차를 계속 진행하면서, 단말에게 커버리지 정보 전달을 위한 인증 결과와 커버리지 정보를 전달할 수 있다.15. The SMF can continue the PDU session establishment procedure and deliver the authentication result and coverage information for delivering coverage information to the terminal.
15a. SMF는 AMF에게 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있으며 이 경우, 커버리지 정보를 AMF가 직접 읽을 수도 있다.15a. The SMF may provide the AMF with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message as is. In this case, the AMF may read the coverage information directly.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 10에서 CM NF로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 10에서 수신한 내용을 기반으로 SMF가 판단하여 결정한 내용일 수도 있다. 예를 들어, CM NF가 단계 10에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location) 의 이유를 제공한 경우, SMF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우, 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDU 세션 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDU 세션 해제(release)가 필요하지 않음(PDU Session release not needed)의 이유(cause)를 제공할 수도 있다. SMF는 단말로부터 커버리지 데이터를 수신하지 않고도 동작할 수 있는 능력(capability)이 있음을 알 수 있는 정보를 수신한 경우, 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단할 수 있다. 이러한 단말의 능력과 관련된 정보는 단말 또는 AMF가 SMF에게 송신한 PDU 세션 수립 요청 메시지에 단말 능력(UE Capability) 등의 정보에 포함되어 제공될 수 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. The result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the CM NF in step 10, or may be determined by the SMF based on the content received in step 10. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 10, the SMF is configured to operate in a state in which the terminal has not received coverage information. If it is determined that registration management or session management can be obtained from the terminal, an indicator indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDU session release (release) is not needed is additionally provided, or the terminal's A cause may be provided for deregistration not needed and/or PDU Session release not needed. When SMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge. Information related to such UE capabilities may be provided by being included in information such as UE Capability in the PDU session establishment request message sent from the UE or AMF to the SMF.
15b. AMF는 RAN에게 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있다.15b. AMF may provide the RAN with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 15a에서 SMF로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 15a에서 수신한 내용을 기반으로 AMF가 판단하여 결정한 내용일 수도 있다. 예를 들어, SMF가 단계 15a에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location) 의 이유를 제공한 경우, AMF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우, 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDU 세션 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDU 세션 해제(release)가 필요하지 않음(PDU Session release not needed)의 이유(cause)를 제공할 수도 있다. AMF는 단말로부터 커버리지 데이터를 수신하지 않고도 동작할 수 있는 능력(capability)이 있음을 알 수 있는 정보를 수신한 경우, 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단할 수 있다. 이러한 단말의 능력과 관련된 정보는 단말이 AMF에게 송신한 등록 요청 메시지 또는 PDU 세션 수립 요청 메시지에 단말 능력(UE Capability) 등의 정보에 포함되어 제공될 수 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. The result of the authentication for delivering coverage information may be the same as the result of the authentication for delivering coverage information received from the SMF in step 15a, or may be determined by the AMF based on the content received in step 15a. For example, if the SMF provides a reason of not allowed at current location with an authentication result of failure in step 15a, the AMF provides the reason for not allowing the terminal to receive coverage information. If it is determined that registration management or session management is possible, an indicator is additionally provided indicating that deregistration of the terminal is not needed and/or PDU session release is not needed, or registration of the terminal is provided. A cause may be provided for deregistration not needed and/or PDU Session release not needed. When AMF receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge. Information related to the capabilities of the terminal may be provided by being included in information such as UE Capability in a registration request message or PDU session establishment request message sent from the terminal to the AMF.
15c. RAN은 UE에게 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있다.15c. The RAN may provide the UE with at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data). Coverage information may not be included in the CMT Data Container but may be included in the message.
15d. 단말은 수신한 커버리지 데이터를 저장 및 처리할 수 있고, 필요한 다른 절차를 수행할 수 있다. 이 때 단말은 함께 수신한 커버리지 정보 전달을 위한 인증의 결과를 참고할 수 있다.15d. The terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the authentication result for delivering the coverage information received together.
● 예를 들어, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 다른 액세스 네트워크의 커버리지에 가까워지고 있음을 알 수 있는 경우, 해당 액세스 네트워크로 연결을 이동시킬 수 있다.● For example, if the terminal is moving away from the coverage of the currently connected access network and can know that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to that access network. can be moved.
● 또 다른 예로, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 연결될 수 있는 다른 액세스 네트워크가 없음을 알 수 있는 경우, 등록 해제 절차를 개시하거나 전원 절약 모드(power saving mode)를 이용하여 현재 연결된 액세스 네트워크의 커버리지가 다시 회복할 때까지 기다릴 수 있다.● As another example, if the terminal is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this coverage data that it has stored, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
● 예를 들어, 단말이 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유, 또는 단말의 등록 해제(deregistration)이 필요하지 않음을 알리는 지시자(또는 이를 알리는 이유), 또는 PDU 세션 해제(release)가 필요하지 않음(PDU Session release not needed)을 알리는 지시자(또는 이를 알리는 이유)를 수신한 경우, 단말은 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말을 등록 해제하지 않거나 PDU 세션을 해제하지 않고 계속해서 코어네트워크와의 연결을 유지할 수 있다.● For example, an indicator indicating that the terminal is not allowed at the current location with an authentication result of failure, or that deregistration of the terminal is not necessary (or When receiving an indicator (or reason for notifying this) indicating that PDU Session release is not needed, the terminal performs registration management or session without receiving coverage information. If it is determined that it can be managed, it can continue to maintain connection to the core network without deregistering the terminal or releasing the PDU session.
● 또 다른 예로, 단말이 단계 15c에서 실패(failure)의 인증 결과를 수신하였고, 단말이 커버리지 데이터를 수신하지 않은 상태에서 동작할 수 없을 것으로 판단한 경우 단말은 등록 해제 절차 또는 PDU 세션 해제 절차를 개시할 수 있다.● As another example, if the terminal receives an authentication result of failure in step 15c and determines that the terminal cannot operate without receiving coverage data, the terminal initiates a deregistration procedure or a PDU session release procedure. can do.
SMF는 단계 11에서 CMS가 통지를 요청한 이벤트가 발생한 경우 이를 CMS에게 통지할 수 있다. 이 통지에는 GPSI, CMT ID, UE IP address 중 적어도 하나가 포함될 수 있다.SMF can notify CMS if an event for which CMS has requested notification occurs in step 11. This notification may include at least one of GPSI, CMT ID, and UE IP address.
도 10 본 개시의 일 실시예에 따른 PDN connection 관리 절차에서 커버리지 맵 정보 전달(coverage map transfer)하는 방법을 도시하는 도면이다.FIG. 10 is a diagram illustrating a method of transferring coverage map information in a PDN connection management procedure according to an embodiment of the present disclosure.
도 10의 방법은 도 7, 도 8, 및 도 9에서 등록 절차 중에 AMF가 수행하는 동작이 PDN 연결 수립 절차 중에 SMF+PGW-C가 수행하는 동작으로 대체되는 특징을 갖고 있다. 따라서, 도 10의 방법의 일부는 도 7, 도 8, 및 도 9의 방법과 공통적인 동작을 포함할 수 있으며, 일부 설명이 생략되었을 수 있다.The method of FIG. 10 has the feature that the operations performed by AMF during the registration procedure in FIGS. 7, 8, and 9 are replaced by the operations performed by SMF+PGW-C during the PDN connection establishment procedure. Accordingly, some of the methods of FIG. 10 may include common operations with the methods of FIGS. 7, 8, and 9, and some descriptions may be omitted.
도 10는 세션 관리 기능을 담당하는 5GC 또는 EPC 네트워크 엔티티에 의해 커버리지 맵 정보 전달 절차가 개시되어 수행되는 방법을 설명한다. 세션 관리 기능을 담당하는 네트워크 엔티티에는 SMF+PGW-C 등이 포함될 수 있으며, 도 10에서는 SMF+PGW-C인 경우를 일 예로 설명하며, 이에 한정하지 않는다.Figure 10 explains how the coverage map information delivery procedure is initiated and performed by the 5GC or EPC network entity responsible for the session management function. The network entity responsible for the session management function may include SMF+PGW-C, etc. In FIG. 10, the case of SMF+PGW-C is explained as an example, but is not limited thereto.
도 10은 CM NF가 NEF와 동일한 장치에 구현된 경우를 일 예로 설명하며, 이에 한정하지 않는다. 도 10에서 설명하는 CM NF의 동작의 전체 또는 일부는 다른 네트워크 엔티티 (예를 들어 SMF, NWDAF 등이 포함될 수 있다)에서 수행될 수 있다. 예를 들어, 도 10에서 설명하는 CM NF의 동작 중 커버리지 데이터의 요청을 전달하거나 커버리지 데이터를 전달하는 동작은 NEF에 구현된 CM NF에서 수행되고, 커버리지 데이터 요청의 변환 또는 커버리지 데이터의 변환 동작은 SMF+PGW-C에 구현된 CM NF에서 수행되는 형태로 CM NF의 기능이 서로 다른 네트워크 엔티티에 분산되어 구현되어 있을 수 있다.Figure 10 illustrates the case where CM NF is implemented in the same device as NEF as an example, but is not limited to this. All or part of the CM NF operation described in FIG. 10 may be performed in another network entity (e.g., SMF, NWDAF, etc. may be included). For example, among the operations of the CM NF described in FIG. 10, the operation of transmitting a request for coverage data or delivering coverage data is performed in the CM NF implemented in NEF, and the conversion of the coverage data request or the conversion of coverage data is performed in the CM NF implemented in the NEF. The functions of CM NF may be distributed and implemented in different network entities as they are performed in CM NF implemented in SMF+PGW-C.
0. 단말은 RAN을 통해 MME에 연결되어 Attach 절차를 수행할 수 있다. 0a 내지 0d 외에 Attach 절차에 필요한 다른 절차들이 수행될 수 있으며, 설명에서는 생략되었을 수 있다.0. The terminal can connect to the MME through RAN and perform the Attach procedure. In addition to 0a to 0d, other procedures required for the attach procedure may be performed and may be omitted from the description.
0a. 단말은 RAN을 통해 MME에게 Attach 요청을 송신할 수 있다. 이 요청에는 CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), CMS address 중 적어도 하나가 포함될 수 있다.0a. The UE can send an Attach request to the MME through the RAN. This request may include at least one of CMT (Coverage Map Transfer) ID, CMT Data Container (coverage data request), and CMS address.
0b. MME는 SMF+PGW-C에게 세션 생성을 요청할 수 있다. 이 요청에는 CMT ID, CMT Data Container(coverage data request), CMS address, UE Location Information 중 적어도 하나가 포함될 수 있다. CMT ID, CMT Data Container, CMS address, UE Location Information은 각각 도 7, 도 8, 및 도 9에서 설명한 것처럼 단말로부터 수신한 정보일 수 있으며, 단말로부터 수신하지 않았더라도 MME가 필요하다고 판단한 경우 SMF+PGW-C에게 제공할 수 있다. 예를 들어, MME는 단말로부터 UE Location Information을 수신하지 않았더라도 단말의 위치 정보가 CMS 및/또는 CM NF가 수행하는 커버리지 정보 전달과 관련된 판단에 필요하다고 판단한 경우, UE Location Information을 커버리지 정보 전달을 위한 인증 요청에 포함시킬 수 있다.0b. The MME can request session creation from SMF+PGW-C. This request may include at least one of CMT ID, CMT Data Container (coverage data request), CMS address, and UE Location Information. CMT ID, CMT Data Container, CMS address, and UE Location Information may be information received from the terminal as described in Figures 7, 8, and 9, respectively. Even if not received from the terminal, if the MME determines that it is necessary, SMF+ Can be provided to PGW-C. For example, even if the MME has not received UE Location Information from the terminal, if the MME determines that the location information of the terminal is necessary for the decision related to the delivery of coverage information performed by the CMS and/or CM NF, it uses the UE Location Information to deliver the coverage information. It can be included in the authentication request for
0c. SMF+PGW-C는 세션 생성 요청에 응답할 수 있다.0c. SMF+PGW-C can respond to a session creation request.
0d. MME는 RAN을 통해 Attach 수락을 송신할 수 있다.0d. The MME can transmit an Attach acceptance through the RAN.
0e. 단말은 RAN을 통해 MME에게 Attach 완료로 응답할 수 있다.0e. The UE can respond with Attach completion to the MME through the RAN.
1. SMF+PGW-C는 UDM으로부터 단말이 커버리지 정보를 획득하도록 허용되었는지 여부, 또는 위성의 이동과 관련된 정보를 획득하도록 허용되었는지 여부 등을 지시하는 가입자 정보 데이터를 확인할 수 있다.1. SMF+PGW-C can check subscriber information data indicating whether the terminal is allowed to obtain coverage information from UDM or whether it is allowed to obtain information related to the movement of the satellite.
1a. SMF+PGW-C는 UDM에게 단말의 가입자 정보를 요청할 수 있다. 이 요청에는 SUPI, DNN, S-NSSAI, CMT ID, 단말 위치 정보(UE Location Information) 중 적어도 하나가 포함될 수 있다. 단말 위치 정보에는 MME가 단말 또는 RAN으로부터 수신한 정보로서 단말의 지리적 위치 좌표(예를 들어 GPS 좌표, GNSS 좌표 등), Cell ID, TAI 등이 포함될 수 있다. SUPI, DNN, S-NSSAI, 및/또는 CMT ID는 단말의 가입자 정보 접근 키(key)에 해당할 수 있다.1a. SMF+PGW-C can request subscriber information of the terminal from UDM. This request may include at least one of SUPI, DNN, S-NSSAI, CMT ID, and UE Location Information. Terminal location information is information received by the MME from the UE or RAN and may include the UE's geographic location coordinates (eg, GPS coordinates, GNSS coordinates, etc.), Cell ID, TAI, etc. SUPI, DNN, S-NSSAI, and/or CMT ID may correspond to the subscriber information access key of the terminal.
1b. UDM은 SMF+PGW-C에게 단말의 가입자 정보를 제공할 수 있다. 이 가입자 정보는 세션 관리 관련 가입자 정보 중에서 커버리지 맵 정보 전달 허용을 지시하는 정보를 의미할 수 있다.1b. UDM can provide terminal subscriber information to SMF+PGW-C. This subscriber information may refer to information indicating permission to transmit coverage map information among session management-related subscriber information.
2. SMF+PGW-C 는 단말이 커버리지 정보를 수신할 수 있는지 여부, 및/또는 단말이 커버리지 정보를 수신하기 위해서 추가적인 인증 절차가 필요한지 여부를 판단할 수 있다. 예를 들어, (1) 단말이 CMT ID를 제공, (2) 단말의 가입자 정보에 커버리지 맵 정보 전달이 허용됨을 의미하는 정보가 존재 중 적어도 하나의 조건을 만족하는 경우, SMF+PGW-C는 단말이 커버리지 정보를 수신할 수 있는 것으로 판단할 수 있다. 또다른 예로, 상기 (1), (2)와 (3) 이전에 단말이 커버리지 정보를 수신하기 위한 추가 인증 절차가 수행되지 않았거나 성공적인 인증 결과가 없었던 경우, 중 적어도 하나의 조건을 만족하는 경우, SMF+PGW-C는 단말이 커버리지 정보를 수신할 수 있고, 커버리지 정보를 수신하기 위해 추가적인 인증 절차가 필요한 것으로 판단할 수 있다. SMF+PGW-C는 CM NF에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data Container(coverage data request), CMS address, UE Location Information, PEI, UE IP address 중 적어도 하나가 포함될 수 있다. 예를 들어, SMF는 단말이 동일한 CMT ID를 사용하여 하나 이상의 PDN connection 사용하고 있거나, 하나 이상의 단말이 동일한 CMT ID를 사용하고 있는 경우, 특정 단말 및/또는 특정 단말이 사용하고 있는 특정 PDN 연결을 식별하기 위하여 UE IP address (또는 PDU connection ID)를 제공할 수 있다. GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, UE IP address는 각각 도 7, 도 8, 및 도 9에서 설명한 것처럼 단말 및/또는 MME로부터 수신한 정보일 수 있으며, 단말 및/또는 MME로부터 수신하지 않았더라도 SMF+PGW-C 가 필요하다고 판단한 경우 CM NF에게 제공할 수 있다. 예를 들어, SMF+PGW-C 는 단말로부터 UE Location Information 을 수신하지 않았더라도 단말의 위치 정보가 CMS 및/또는 CM NF가 수행하는 커버리지 정보 전달과 관련된 판단에 필요하다고 판단한 경우, UE Location Information을 커버리지 정보 전달을 위한 인증 요청에 포함시킬 수 있다.2. SMF+PGW-C can determine whether the terminal can receive coverage information and/or whether additional authentication procedures are required for the terminal to receive coverage information. For example, if at least one condition is satisfied: (1) the terminal provides a CMT ID, and (2) information indicating that coverage map information is allowed to be transmitted in the subscriber information of the terminal exists, SMF+PGW-C It may be determined that the terminal can receive coverage information. As another example, if at least one of the following conditions is satisfied: (1), (2), and (3) above, when an additional authentication procedure for the terminal to receive coverage information has not been performed or there has been no successful authentication result. , SMF+PGW-C may determine that the terminal can receive coverage information and that an additional authentication procedure is necessary to receive coverage information. SMF+PGW-C can request authentication from CM NF to deliver coverage information. (If additional authentication is not required to deliver coverage information, you can request coverage information delivery.) This request includes GPSI, CMT ID, CMT Data Container (coverage data request), CMS address, UE Location Information, PEI, UE. At least one IP address may be included. For example, when a terminal is using more than one PDN connection using the same CMT ID, or when more than one terminal is using the same CMT ID, SMF connects a specific terminal and/or a specific PDN connection used by a specific terminal. The UE IP address (or PDU connection ID) can be provided for identification. GPSI, CMT ID, CMT Data Container, CMS address, UE Location Information, PEI, and UE IP address may be information received from the terminal and/or MME as described in Figures 7, 8, and 9, respectively. /Or, even if it is not received from the MME, it can be provided to the CM NF if SMF+PGW-C is deemed necessary. For example, even if SMF+PGW-C has not received UE Location Information from the terminal, if it determines that the location information of the terminal is necessary for the decision related to delivery of coverage information performed by CMS and/or CM NF, it provides UE Location Information. It can be included in the authentication request for delivering coverage information.
3. CM NF는 SMF+PGW-C 의 커버리지 정보 전달을 위한 인증 요청에 포함된 정보를 평가(evaluate)하여 CMS에 요청할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 정보는 CMT Data에 포함되어 CMS에게 제공될 수 있다. 3. CM NF can evaluate the information included in the authentication request for delivering coverage information of SMF+PGW-C and translate and generate the content to be requested from CMS. The generated information can be included in CMT Data and provided to CMS.
● 예를 들어, CM NF는 SMF+PGW-C 가 단말로부터 수신하여 제공한 coverage data request를 분석하여 편집할 수 있다. 보다 구체적으로 (1) CM NF는 요청 정보의 평가 단계에서 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석할 수 있다. (2) CM NF는 요청 정보의 생성 단계에서 3개의 위치 좌표로 이루어진 경로를 5개의 위치 좌표로 보간(interpolation)하였을 때 얻을 수 있는 5개의 위치 좌표를 생성할 수 있다. 즉, coverage data required trajectory가 P1, P2, P3의 위치 좌표로 이루어져있는 경우, P1-P2-P3로 이루어진 경로 T에 대하여 required accuracy level을 만족할 수 있는 Q1, Q2, Q3, Q4, Q5 위치 좌표를 생성할 수 있다. 이 때, Q1 내지 Q5는 P1 내지 P3를 포함할 수도 있고, 포함하지 않을 수도 있다. Q1 내지 Q5는 CMT Data에 포함되어 CMS에게 제공될 수 있다. ● For example, CM NF can analyze and edit the coverage data request received and provided by SMF+PGW-C from the terminal. More specifically, (1) CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests in the evaluation stage of the request information. Although the coverage data required trajectory included 3 location coordinates, the required accuracy level was not satisfied. It can be analyzed that 5 location coordinates are needed to do this. (2) CM NF can generate 5 location coordinates that can be obtained by interpolating a path consisting of 3 location coordinates into 5 location coordinates in the request information creation stage. In other words, if the coverage data required trajectory consists of the position coordinates of P1, P2, and P3, the position coordinates of Q1, Q2, Q3, Q4, and Q5 that can satisfy the required accuracy level for the path T consisting of P1-P2-P3 are can be created. At this time, Q1 to Q5 may or may not include P1 to P3. Q1 to Q5 may be included in CMT Data and provided to CMS.
● 또 다른 예로, CM NF는 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, SMF+PGW-C 가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함된 경우, CM NF는 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환할 수 있다. ● As another example, CM NF can convert terminal location information into a format that CMS can interpret. More specifically, if the UE Location Information provided by SMF+PGW-C to CM NF includes Cell ID or TAI, CM NF can convert it into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates). there is.
● CM NF는 요청 정보의 생성(예를 들어, Q1 내지 Q5를 계산 및 생성하는 동작, 단말의 위치 정보를 지형적 위치 좌표로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, MME, SMF+PGW-C, LMF 일 수 있다)에게 요청하여 사용할 수 있다.● CM NF provides information necessary for generating request information (e.g., calculating and generating Q1 to Q5, converting the location information of the terminal into geographic location coordinates) to other network entities (e.g., NWDAF, It can be used by requesting it from AMF, MME, SMF+PGW-C, or LMF).
4. CM NF는 CMS에게 커버리지 정보 전달을 위한 인증을 요청할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보 전달을 요청할 수 있다.) 이 요청에는 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address 중 적어도 하나가 포함될 수 있다. GPSI, CMT ID, CMT Data Container (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address는 각각 도 7, 도 8, 및 도 9에서 설명한 것처럼 단말로부터 수신하였거나 및 단계 0b 및 단계 2에서 설명한 것처럼 MME및/또는 SMF+PGW-C 로부터 수신한 정보일 수 있으며, 단말, MME, 및/또는 SMF+PGW-C 로부터 수신하지 않았더라도 CM NF가 필요하다고 판단한 경우 CMS에게 제공할 수 있다. coverage data request는 단계 3에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 3을 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 2에서 수신한 coverage data request를 그대로 전달하는 것을 의미할 수 있다.4. CM NF can request authentication from CMS to deliver coverage information. (If additional authentication is not required to transmit coverage information, you can request coverage information transmission.) This request includes GPSI, CMT ID, CMT Data (may include coverage data request), UE Location Information, PEI, At least one of the UE IP addresses may be included. GPSI, CMT ID, CMT Data Container (which may include a coverage data request), UE Location Information, PEI, and UE IP address are received from the terminal as described in Figures 7, 8, and 9, respectively, and in step 0b and As described in step 2, this may be information received from the MME and/or SMF+PGW-C, and may be provided to CMS if the CM NF determines it is necessary even if it is not received from the terminal, MME, and/or SMF+PGW-C. You can. Coverage data request may refer to CMT Data generated by CM NF in step 3. If the CM NF did not perform step 3, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data request received in step 2 as is.
5. CMS는 CMT ID로 식별되는 단말에 대하여, 커버리지 정보의 수신이 허용된 단말인지 여부를 인증하는 절차를 수행할 수 있다. CMS는 인증 절차에서 GPSI, CMT ID, CMT Data (coverage data request를 포함할 수 있다), UE Location Information, PEI, UE IP address 중 적어도 하나를 참고할 수 있다. 예를 들어, CMS는 단말의 위치 또는 UE IP address에 따라서 동일한 CMT ID에 대하여 인증 성공 결과를 제공할 수도 있고, 인증 실패 결과를 제공할 수도 있다. 5a 내지 5f는 CMS가 사용하는 인증 방법(method)에 따라서 한 번 또는 그 이상 반복 될 수 있다.5. CMS can perform a procedure to authenticate whether the terminal identified by the CMT ID is a terminal permitted to receive coverage information. CMS may refer to at least one of GPSI, CMT ID, CMT Data (which may include a coverage data request), UE Location Information, PEI, and UE IP address in the authentication procedure. For example, the CMS may provide an authentication success result or an authentication failure result for the same CMT ID depending on the location of the terminal or the UE IP address. 5a to 5f may be repeated once or more depending on the authentication method used by CMS.
5a. CMS는 SMF+PGW-C를 통해 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.5a. CMS can send a response to the authentication request to CM NF through SMF+PGW-C. This response may include GPSI, CMT ID, and authentication message.
5b. SMF+PGW-C는 SGW를 통해 MME에게 인증 응답을 전달할 수 있다.5b. SMF+PGW-C can deliver an authentication response to the MME through SGW.
5c. MME는 단말에게 인증 응답을 전달할 수 있다.5c. The MME can deliver an authentication response to the terminal.
5d. 단말은 MME에게 CMS로부터 수신한 인증 응답에 대한 응답을 송신할 수 있다. 이 응답에는 GPSI, CMT ID, 및 인증 메시지가 포함될 수 있다.5d. The terminal may transmit a response to the authentication response received from CMS to the MME. This response may include GPSI, CMT ID, and authentication message.
5e. MME는 SGW를 통해 SMF+PGW-C 에게 응답을 전달할 수 있다.5e. The MME can deliver a response to SMF+PGW-C through SGW.
5f. SMF+PGW-C는 CM NF를 통해 CMS에게 응답을 전달할 수 있다.5f. SMF+PGW-C can deliver a response to CMS through CM NF.
6. CMS는 CM NF에게 인증 요청에 대한 응답 송신을 할 수 있다. 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data (coverage data) 중 적어도 하나가 포함될 수 있다. 6. CMS can send a response to the authentication request to CM NF. This response may include at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information (for example, it may be success or failure), and CMT Data (coverage data).
■ Coverage data는 단계 4의 coverage data request의 내용에 기반하여 단말에게 제공하는 커버리지 정보를 의미할 수 있다. CMS는 단계 4에서 coverage data request를 수신하지 않았더라도, CMS에 판단에 따라 커버리지 정보를 제공할 수 있다.■ Coverage data may refer to coverage information provided to the terminal based on the contents of the coverage data request in step 4. Even if CMS does not receive a coverage data request in step 4, it can provide coverage information to CMS at its discretion.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 예를 들어, CMS는 단말이 현재의 위치에서는 커버리지 정보의 수신이 허용되지 않지만, 다른 위치에서는 커버리지 정보의 수신이 허용될 수 있는 단말에 해당하는 경우, 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공할 수 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. For example, CMS determines the current location with an authentication result of failure if the terminal is not permitted to receive coverage information in its current location, but is a terminal that may be permitted to receive coverage information in other locations. You can provide a reason for not allowed at current location.
7. CM NF는 CMS가 제공한 커버리지 정보(coverage data)를 평가(evaluate)하여 단말에 전달할 내용으로 변환(translate) 및 생성(generate)할 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되어 SMF+PGW-C 에게 제공될 수 있다. 생성한 커버리지 정보는 CMT Data Container에 포함되지 않고 단계 8에서 인증 응답 메시지에 그대로 포함될 수도 있으며 이 경우, 커버리지 정보를 SMF+PGW-C (MME까지 전달되는 경우 MME도 포함될 수 있다)가 직접 읽을 수 있다. 상기 단계 3에서 수행된 변환 과정의 역변환 과정이 수행될 수 있다.7. CM NF can evaluate the coverage information (coverage data) provided by CMS and translate and generate content to be delivered to the terminal. The generated coverage information can be included in the CMT Data Container and provided to SMF+PGW-C. The generated coverage information may not be included in the CMT Data Container but may be directly included in the authentication response message in step 8. In this case, the coverage information can be read directly by SMF+PGW-C (if delivered to the MME, the MME may also be included). there is. The reverse conversion process of the conversion process performed in step 3 may be performed.
■ 예를 들어, 단계 3의 예에서와 같이 CM NF가 coverage data request의 하나로 coverage data required trajectory와 required accuracy level이 제공되었는데, coverage data required trajectory에 3개의 위치 좌표가 포함되어 있으나 required accuracy level을 만족하기 위해서는 5개의 위치 좌표가 필요한 것으로 분석할 수 있다. 이때, 총 5개의 위치 좌표를 CMT Data에 포함시켜 CMS에게 커버리지 데이터를 요청했던 경우, CM NF는 CMS로부터 수신한 5개의 위치 좌표에 대한 커버리지 데이터(예를 들어, Q1 내지 Q5 위치에서의 시간 별 커버리지 존재 여부 등)를 SMF+PGW-C 에게 제공할 수 있다. ■ For example, as in the example of step 3, the CM NF provided coverage data required trajectory and required accuracy level as one of the coverage data requests, and the coverage data required trajectory included 3 location coordinates, but did not satisfy the required accuracy level. It can be analyzed that 5 location coordinates are needed to do this. At this time, when coverage data is requested from CMS by including a total of 5 location coordinates in the CMT Data, the CM NF provides coverage data for the 5 location coordinates received from CMS (e.g., by time at positions Q1 to Q5). (existence of coverage, etc.) can be provided to SMF+PGW-C.
■ 또 다른 예로, 단계 3의 예에서와 같이 CM NF가 단말 위치 정보를 CMS가 해석할 수 있는 형식으로 변환하였던 경우, CMS가 제공한 커버리지 데이터를 다시 네트워크 엔티티가 해석할 수 있는 형식으로 변환할 수 있다. 보다 구체적으로, 단계 4에서 SMF+PGW-C 가 CM NF에게 제공한 UE Location Information으로서 Cell ID 또는 TAI가 포함되었고, CM NF가 이를 지형적 위치 좌표(예를 들어, GPS 좌표 또는 GNSS 좌표)로 변환하여 CMS에게 요청하였던 경우, CM NF는 CMS로부터 수신한 지형적 위치 좌표를 다시 Cell ID 또는 TAI로 변환하여 SMF+PGW-C 에게 제공할 수 있다. ■ As another example, as in the example of step 3, if the CM NF has converted the terminal location information into a format that the CMS can interpret, the coverage data provided by the CMS must be converted back into a format that the network entity can interpret. You can. More specifically, the UE Location Information provided by SMF+PGW-C to CM NF in Step 4 included Cell ID or TAI, and CM NF converted this into geographic location coordinates (e.g., GPS coordinates or GNSS coordinates). If a request is made to CMS, CM NF can convert the geographical location coordinates received from CMS back into Cell ID or TAI and provide them to SMF+PGW-C.
■ CM NF는 커버리지 데이터의 생성(예를 들어, 단말의 지형적 위치 좌표를 단말의 위치 정보로 변환하는 동작)에 필요한 정보를 다른 네트워크 엔티티(예를 들어, NWDAF, AMF, MME, LMF 일 수 있다)에게 요청하여 사용할 수 있다.■ CM NF may be another network entity (e.g., NWDAF, AMF, MME, LMF) that provides information necessary for the generation of coverage data (e.g., an operation to convert the geographical location coordinates of the terminal into location information of the terminal). ) can be used by request.
8. CM NF는 커버리지 정보 전달을 위한 인증 요청에 대하여 응답할 수 있다. (커버리지 정보 전달을 위한 추가적인 인증이 필요하지 않은 경우에는 커버리지 정보를 전달할 수 있다.) 이 응답에는 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과(예를 들어 success 또는 failure 일 수 있다), CMT Data(coverage data), CMT Data Container(coverage data) 중 적어도 하나가 포함될 수 있다. SMF+PGW-C 는 커버리지 정보 전달을 위한 인증의 결과 및/또는 coverage data에 기반하여, 단말의 등록 해제(deregistration), PDN connection의 해제(release), 사용자 평면 리소스 해제(release), 베어러(bearer) 해제, 단말의 전원 절약 모드(power saving mode) 적용 등에 대한 판단을 수행할 수 있다.8. CM NF can respond to authentication requests for delivering coverage information. (If additional authentication is not required to deliver coverage information, coverage information can be delivered.) This response includes GPSI, CMT ID, authentication message, and the result of authentication for delivering coverage information (for example, success or failure). At least one of CMT Data (coverage data), CMT Data Container (coverage data) may be included. SMF+PGW-C performs terminal deregistration, PDN connection release, user plane resource release, and bearer based on the results of authentication and/or coverage data for delivering coverage information. ) It is possible to make a decision on release, application of the terminal's power saving mode, etc.
■ coverage data 는 단계 7에서 CM NF가 생성한 CMT Data를 의미할 수 있다. CM NF가 단계 7를 수행하지 않았거나, CM NF가 변환이 필요하지 않다고 판단한 경우에는 단계 6에서 수신한 coverage data 를 그대로 전달하는 것을 의미할 수 있다.■ Coverage data may refer to CMT Data generated by CM NF in step 7. If the CM NF did not perform step 7, or if the CM NF determines that conversion is not necessary, this may mean delivering the coverage data received in step 6 as is.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 6에서 CMS로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 6에서 수신한 내용을 기반으로 CM NF가 판단하여 결정한 내용일 수도 있다. 예를 들어, CMS가 단계 6에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유를 제공한 경우, CM NF는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말의 등록 해제(deregistration) 및/또는 PDN 연결 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDN 연결 해제(release)가 필요하지 않음(PDN connection release not needed)의 이유(cause)를 제공할 수도 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. The result of authentication for delivering coverage information may be the same as the result of authentication for delivering coverage information received from CMS in step 6, or may be determined by the CM NF based on the content received in step 6. For example, if the CMS provides the reason of not allowed at current location along with the authentication result of failure in step 6, the CM NF states that the terminal has not received coverage information. If it is determined that registration management or session management can be received in It may also provide a reason for deregistration not needed and/or PDN connection release not needed.
9. CMS는 SMF+PGW-C에게 UDM을 통하여 세션 관리와 관련된 변경사항이 발생하였을 경우 통지 받을 수 있도록 요청할 수 있다. 9. CMS may request SMF+PGW-C to be notified when changes related to session management occur through UDM.
10. CMS는 SMF+PGW-C에게 UDM을 통하여 세션 관리와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. 10. CMS may request that SMF+PGW-C no longer receive notification of changes related to session management through UDM.
11. SMF+PGW-C 는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련되어 변경사항이 발생하였을 경우 통지 받을 수 있도록 요청할 수 있다. CM NF는 SMF+PGW-C 에게 세션 관리와 관련된 변경사항이 발생하였을 경우 지 받을 수 있도록 요청할 수 있다. 11. SMF+PGW-C may request that CM NF be notified if changes occur related to the results of authentication for delivering coverage data and/or coverage information. CM NF may request SMF+PGW-C to receive notification when changes related to session management occur.
12. SMF+PGW-C 는 CM NF에 대하여, 커버리지 데이터 및/또는 커버리지 정보 전달을 위한 인증의 결과와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. CM NF는 SMF+PGW-C 에게 세션 관리와 관련된 변경사항의 통지를 더 이상 받지 않도록 요청할 수 있다. 12. SMF+PGW-C may request that CM NF no longer receive notification of changes related to coverage data and/or the results of authentication for delivery of coverage information. CM NF may request that SMF+PGW-C no longer receive notifications of changes related to session management.
13. SMF+PGW-C 는 PDN 연결 수립 절차(PDN GW에 의해 개시된 QoS 업데이트 없이 베어러 수정하는 절차가 포함될 수 있다)를 계속 진행하면서, 단말에게 커버리지 정보 전달을 위한 인증 결과와 커버리지 정보를 전달할 수 있다.13. SMF+PGW-C can deliver authentication results and coverage information to the terminal while continuing the PDN connection establishment procedure (which may include the procedure of modifying the bearer without QoS update initiated by the PDN GW). there is.
13a. SMF+PGW-C 는 SGW를 통해 MME에게 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data)는 PCO(또는 ePCO)에 포함되어 제공될 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있다.13a. SMF+PGW-C can provide at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) to the MME through SGW. GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) can be included and provided in the PCO (or ePCO). Coverage information may not be included in the CMT Data Container but may be included in the message.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 8에서 CM NF로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 8에서 수신한 내용을 기반으로 SMF+PGW-C 가 판단하여 결정한 내용일 수도 있다. 예를 들어, CM NF가 단계 8에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location) 의 이유를 제공한 경우, SMF+PGW-C 는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우, 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDN 연결 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDN 연결 해제(release)가 필요하지 않음(PDN connection release not needed)의 이유(cause)를 제공할 수도 있다. SMF+PGW-C 는 단말로부터 커버리지 데이터를 수신하지 않고도 동작할 수 있는 능력(capability)이 있음을 알 수 있는 정보를 수신한 경우, 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단할 수 있다. 이러한 단말의 능력과 관련된 정보는 단말 또는 MME가 SMF+PGW-C 에게 송신한 PDN 연결 수립 요청 메시지에 단말 능력(UE Capability) 등의 정보에 포함되어 제공될 수 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. The result of authentication for delivering coverage information is the same as the result of authentication for delivering coverage information received from CM NF in Step 8, or the result determined by SMF+PGW-C based on the content received in Step 8. It may be possible. For example, if the CM NF provides a reason of not allowed at current location with an authentication result of failure in step 8, SMF+PGW-C allows the terminal to provide coverage information. If it is determined that registration management or session management can be received without receiving delivery, an indicator is added indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDN connection release (release) is not needed. It may also provide a reason for deregistration of the terminal not needed (deregistration not needed) and/or PDN connection release not needed (PDN connection release not needed). When SMF+PGW-C receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it performs registration management or session management without the terminal receiving coverage information. You can judge that you can receive it. Information related to these UE capabilities may be provided by being included in information such as UE Capability in the PDN connection establishment request message sent from the UE or MME to the SMF+PGW-C.
13b. MME는 RAN을 통해 단말에게 GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. GPSI, CMT ID, 인증 메시지, 커버리지 정보 전달을 위한 인증의 결과, CMT Data Container (coverage data)는 PCO(또는 ePCO)에 포함되어 제공될 수 있다. 커버리지 정보는 CMT Data Container에 포함되지 않고 메시지에 그대로 포함될 수도 있다.13b. The MME may provide at least one of GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) to the UE through RAN. GPSI, CMT ID, authentication message, authentication result for delivering coverage information, and CMT Data Container (coverage data) can be included and provided in the PCO (or ePCO). Coverage information may not be included in the CMT Data Container but may be included in the message.
■ 커버리지 정보 전달을 위한 인증의 결과(result of authentication for CMT)에는 인증의 성공 또는 실패 여부, 인증 결과의 이유(cause) 중 적어도 하나가 제공될 수 있다. 커버리지 정보 전달을 위한 인증의 결과는 단계 13a에서 SMF+PGW-C로부터 수신한 커버리지 정보 전달을 위한 인증의 결과를 그대로 전달하거나, 단계 13a에서 수신한 내용을 기반으로 MME가 판단하여 결정한 내용일 수도 있다. 예를 들어, SMF+PGW-C 가 단계 13a에서 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location) 의 이유를 제공한 경우, MME는 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우, 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDN 연결 해제(release)가 필요하지 않음을 알리는 지시자를 추가로 제공하거나 단말의 등록 해제가 필요하지 않음(deregistration not needed) 및/또는 PDN 연결 해제(release)가 필요하지 않음(PDN connection release not needed)의 이유(cause)를 제공할 수도 있다. MME는 단말로부터 커버리지 데이터를 수신하지 않고도 동작할 수 있는 능력(capability)이 있음을 알 수 있는 정보를 수신한 경우, 단말이 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단할 수 있다. 이러한 단말의 능력과 관련된 정보는 단말이 MME에게 송신한 등록 요청 메시지 또는 PDN 연결 수립 요청 메시지에 단말 능력(UE Capability) 등의 정보에 포함되어 제공될 수 있다.■ The result of authentication for coverage information delivery (result of authentication for CMT) may include at least one of success or failure of authentication and the cause of the authentication result. The result of authentication for transmitting coverage information may be the same as the result of authentication for transmitting coverage information received from SMF+PGW-C in step 13a, or may be determined by the MME based on the content received in step 13a. there is. For example, if SMF+PGW-C provides a reason of not allowed at current location with an authentication result of failure in step 13a, the MME sends coverage information to the terminal. If it is determined that registration management or session management can be received without receiving it, an indicator is additionally provided indicating that deregistration of the terminal is not needed (deregistration not needed) and/or PDN connection release (release) is not needed. Alternatively, it may provide a reason for deregistration of the terminal not needed (deregistration not needed) and/or PDN connection release not needed (PDN connection release not needed). When the MME receives information indicating that it has the capability to operate without receiving coverage data from the terminal, it is expected that the terminal will be able to receive registration management or session management without receiving coverage information. You can judge. Information related to such UE capabilities may be provided by being included in information such as UE Capability in a registration request message or PDN connection establishment request message sent from the UE to the MME.
13c. 단말은 RAN을 통해 MME에게 GPSI, CMT ID, 인증 메시지, CMT Data Container (coverage data) 중 적어도 하나를 제공할 수 있다. GPSI, CMT ID, 인증 메시지, CMT Data Container (coverage data)는 PCO(또는 ePCO)에 포함되어 제공될 수 있다.13c. The UE may provide at least one of GPSI, CMT ID, authentication message, and CMT Data Container (coverage data) to the MME through the RAN. GPSI, CMT ID, authentication message, and CMT Data Container (coverage data) may be included and provided in the PCO (or ePCO).
13d. MME는 SGW를 통해 SMF+PGW-C에게 GPSI, CMT ID, 인증 메시지, CMT Data Container 중 적어도 하나를 제공할 수 있다. GPSI, CMT ID, 인증 메시지, CMT Data Container는 PCO(또는 ePCO)에 포함되어 제공될 수 있다.13d. The MME can provide at least one of GPSI, CMT ID, authentication message, and CMT Data Container to SMF+PGW-C through SGW. GPSI, CMT ID, authentication message, and CMT Data Container can be included and provided in PCO (or ePCO).
13e. 단말은 수신한 커버리지 데이터를 저장 및 처리할 수 있고, 필요한 다른 절차를 수행할 수 있다. 이 때 단말은 함께 수신한 커버리지 정보 전달을 위한 인증의 결과를 참고할 수 있다.13e. The terminal can store and process the received coverage data and perform other necessary procedures. At this time, the terminal can refer to the authentication result for delivering the coverage information received together.
■ 예를 들어, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 다른 액세스 네트워크의 커버리지에 가까워지고 있음을 알 수 있는 경우, 해당 액세스 네트워크로 연결을 이동시킬 수 있다.■ For example, if the terminal is moving away from the coverage of the currently connected access network, and if it can be seen that the terminal is approaching the coverage of another access network based on this stored coverage data, it connects to the corresponding access network. can be moved.
■ 또 다른 예로, 단말은 현재 연결된 액세스 네트워크의 커버리지로부터 멀어지고 있는 경우, 저장하고 있던 이 커버리지 데이터를 기반으로 단말이 연결될 수 있는 다른 액세스 네트워크가 없음을 알 수 있는 경우, 등록 해제 절차를 개시하거나 전원 절약 모드(power saving mode)를 이용하여 현재 연결된 액세스 네트워크의 커버리지가 다시 회복할 때까지 기다릴 수 있다.■ As another example, if the terminal is moving away from the coverage of the currently connected access network and it can be known that there is no other access network to which the terminal can be connected based on this stored coverage data, it initiates a deregistration procedure or You can use the power saving mode to wait until coverage of the currently connected access network recovers.
■ 예를 들어, 단말이 실패(failure)의 인증 결과와 함께 현재 위치에서 허용되지 않음(not allowed at current location)의 이유, 또는 단말의 등록 해제(deregistration)이 필요하지 않음을 알리는 지시자(또는 이를 알리는 이유), 또는 PDN 연결 해제(release)가 필요하지 않음(PDN connection release not needed)을 알리는 지시자(또는 이를 알리는 이유)를 수신한 경우, 단말은 커버리지 정보를 전달받지 않은 상태에서 등록 관리 또는 세션 관리를 받을 수 있을 것으로 판단한 경우 단말을 등록 해제하지 않거나 PDN 연결을 해제하지 않고 계속해서 코어네트워크와의 연결을 유지할 수 있다.■ For example, an indicator indicating that the terminal is not allowed at the current location with an authentication result of failure, or that deregistration of the terminal is not necessary (or When receiving an indicator (or reason for notifying this) indicating that PDN connection release is not needed, the terminal performs registration management or session without receiving coverage information. If you determine that you can receive management, you can continue to maintain connection to the core network without deregistering the terminal or disconnecting the PDN.
■ 또 다른 예로, 단말이 단계 13b에서 실패(failure)의 인증 결과를 수신하였고, 단말이 커버리지 데이터를 수신하지 않은 상태에서 동작할 수 없을 것으로 판단한 경우 단말은 등록 해제 절차 또는 PDN 연결 해제 절차를 개시할 수 있다.■ As another example, if the terminal receives an authentication result of failure in step 13b and determines that the terminal will not be able to operate without receiving coverage data, the terminal initiates a deregistration procedure or a PDN disconnection procedure. can do.
SMF+PGW-C는 단계 9에서 CMS가 통지를 요청한 이벤트가 발생한 경우 이를 CMS에게 통지할 수 있다. 이 통지에는 GPSI, CMT ID, UE IP address 중 적어도 하나가 포함될 수 있다.SMF+PGW-C can notify CMS in step 9 if an event for which CMS has requested notification occurs. This notification may include at least one of GPSI, CMT ID, and UE IP address.
본 개시의 실시예들에 포함된 네트워크 및 코어 네트워크는 네트워크 장치를 포함하는 개념일 수 있다. 이동성 관리 장치(또는 이동성 관리 기능), 위치 관리 장치(또는 위치 관리 기능), 게이트웨이 이동 위치 센터 등은 각각 별개의 장치로 구성될 수 있고, 네트워크 장치에 포함되도록 구성될 수 있다.The network and core network included in the embodiments of the present disclosure may be a concept including a network device. A mobility management device (or mobility management function), a location management device (or a location management function), a gateway mobile location center, etc. may each be configured as separate devices and may be configured to be included in a network device.
도 11는 본 개시의 일 실시예에 따른 단말의 구조를 도시한 도면이다. Figure 11 is a diagram showing the structure of a terminal according to an embodiment of the present disclosure.
도 11을 참조하면, 단말은 단말기 수신부(1110), 단말기 송신부(1120) 및 단말기 처리부(제어부)(1130)를 포함할 수 있다. Referring to FIG. 11, the terminal may include a terminal receiving unit 1110, a terminal transmitting unit 1120, and a terminal processing unit (control unit) 1130.
단말기 수신부(1110)와 단말기 송신부(1120)는 함께 송수신부라 칭해질 수 있다. 전술한 단말의 통신 방법에 따라, 단말의 단말기 수신부(1110), 단말기 송신부(1120) 및 단말기 처리부(1130)가 동작할 수 있다. 다만, 단말의 구성 요소가 전술한 예에 한정되는 것은 아니다. 예를 들어, 단말은 전술한 구성 요소들 보다 더 많은 구성 요소(예를 들어, 메모리 등)를 포함하거나 더 적은 구성 요소를 포함할 수도 있다. 뿐만 아니라 단말기 수신부(1110), 단말기 송신부(1120) 및 단말기 처리부(1130)가 하나의 칩(chip) 형태로 구현될 수도 있다. The terminal receiving unit 1110 and the terminal transmitting unit 1120 may be referred to together as a transmitting and receiving unit. According to the above-described communication method of the terminal, the terminal receiving unit 1110, terminal transmitting unit 1120, and terminal processing unit 1130 may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components (eg, memory, etc.) or fewer components than the components described above. In addition, the terminal receiving unit 1110, the terminal transmitting unit 1120, and the terminal processing unit 1130 may be implemented in the form of a single chip.
단말기 수신부(1110) 및 단말기 송신부(1120)(또는, 송수신부)는 기지국과 신호를 송수신할 수 있다. 여기에서, 신호는 제어 정보 및 데이터를 포함할 수 있다. 이를 위해, 송수신부는 전송되는 신호의 주파수를 상승 변환 및 증폭하는 RF 송신기와, 수신되는 신호를 저 잡음 증폭하고 주파수를 하강 변환하는 RF 수신기 등으로 구성될 수 있다. 다만, 이는 송수신부의 일 실시예일뿐이며, 송수신부의 구성 요소가 RF 송신기 및 RF 수신기에 한정되는 것은 아니다.The terminal receiver 1110 and the terminal transmitter 1120 (or transceiver unit) can transmit and receive signals to and from the base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
또한, 송수신부는 무선 채널을 통해 신호를 수신하여 단말기 처리부(1130)로 출력하고, 단말기 처리부(1130)로부터 출력되는 신호를 무선 채널을 통해 전송할 수 있다. Additionally, the transceiver may receive a signal through a wireless channel and output it to the terminal processing unit 1130, and transmit the signal output from the terminal processing unit 1130 through a wireless channel.
메모리(미도시)는 단말의 동작에 필요한 프로그램 및 데이터를 저장할 수 있다. 또한, 메모리는 단말에서 획득되는 신호에 포함된 제어 정보 또는 데이터를 저장할 수 있다. 메모리는 롬(ROM), 램(RAM), 하드디스크, CD-ROM 및 DVD 등과 같은 저장 매체 또는 저장 매체들의 조합으로 구성될 수 있다.Memory (not shown) can store programs and data necessary for the operation of the terminal. Additionally, the memory may store control information or data included in signals obtained from the terminal. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
단말기 처리부(1130)는 전술한 본 개시의 실시 예에 따라 단말이 동작할 수 있도록 일련의 과정을 제어할 수 있다. 단말기 처리부(1130)는 회로 또는 어플리케이션 특정 통합 회로 또는 적어도 하나 이상의 프로세서로 구현될 수 있다. 라고 정의될 수 있다 단말기 처리부(1130)는 제어부나 하나 이상의 프로세서로 구현될 수 있다.The terminal processing unit 1130 can 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 1130 may be implemented as a circuit, an application-specific integrated circuit, or at least one processor. The terminal processing unit 1130 may be implemented as a control unit or one or more processors.
도 12은 본 개시의 일 실시예에 따른 기지국의 구조를 도시한 도면이다. Figure 12 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.
도 12을 참조하면, 기지국은 기지국 수신부(1210), 기지국 송신부(1220), 기지국 처리부(제어부)(1230)를 포함할 수 있다. Referring to FIG. 12, the base station may include a base station receiving unit 1210, a base station transmitting unit 1220, and a base station processing unit (control unit) 1230.
기지국 수신부(1210)와 기지국 송신부(1220)는 함께 송수신부라 칭해질 수 있다. 전술한 기지국의 통신 방법에 따라, 기지국의 기지국 수신부(1210), 기지국 송신부(1220), 기지국 처리부(1230)가 동작할 수 있다. 다만, 기지국의 구성 요소가 전술한 예에 한정되는 것은 아니다. 예를 들어, 기지국은 전술한 구성 요소들 보다 더 많은 구성 요소(예를 들어, 메모리 등)를 포함하거나 더 적은 구성 요소를 포함할 수도 있다. 뿐만 아니라 기지국 수신부(1210), 기지국 송신부(1220), 기지국 처리부(1230)가 하나의 칩(chip) 형태로 구현될 수도 있다.The base station receiving unit 1210 and the base station transmitting unit 1220 may be referred to together as a transmitting and receiving unit. According to the above-described communication method of the base station, the base station receiving unit 1210, base station transmitting unit 1220, and base station processing unit 1230 of the base station may operate. However, the components of the base station are not limited to the above examples. For example, the base station may include more components (eg, memory, etc.) or fewer components than the components described above. In addition, the base station receiving unit 1210, the base station transmitting unit 1220, and the base station processing unit 1230 may be implemented in the form of a single chip.
기지국 수신부(1210) 및 기지국 송신부(1220)(또는, 송수신부)는 단말 및/또는 네트워크 엔티티와 신호를 송수신할 수 있다. 여기에서, 신호는 제어 정보 및 데이터를 포함할 수 있다. 이를 위해, 송수신부는 전송되는 신호의 주파수를 상승 변환 및 증폭하는 RF 송신기와, 수신되는 신호를 저 잡음 증폭하고 주파수를 하강 변환하는 RF 수신기 등으로 구성될 수 있다. 다만, 이는 송수신부의 일 실시예일뿐이며, 송수신부의 구성 요소가 RF 송신기 및 RF 수신기에 한정되는 것은 아니다.The base station receiver 1210 and the base station transmitter 1220 (or transceiver unit) can transmit and receive signals to and from a terminal and/or network entity. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
또한, 송수신부는 유무선 채널을 통해 신호를 수신하여 기지국 처리부(1230)로 출력하고, 기지국 처리부(1230)로부터 출력된 신호를 유무선 채널을 통해 전송할 수 있다. Additionally, the transceiver may receive a signal through a wired or wireless channel and output it to the base station processing unit 1230, and transmit the signal output from the base station processing unit 1230 through a wired or wireless channel.
메모리(미도시)는 기지국의 동작에 필요한 프로그램 및 데이터를 저장할 수 있다. 또한, 메모리는 기지국에서 획득되는 신호에 포함된 제어 정보 또는 데이터를 저장할 수 있다. 메모리는 롬(ROM), 램(RAM), 하드디스크, CD-ROM 및 DVD 등과 같은 저장 매체 또는 저장 매체들의 조합으로 구성될 수 있다. Memory (not shown) can store programs and data necessary for the operation of the base station. Additionally, the memory may store control information or data included in signals obtained from the base station. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
기지국 처리부(1230)는 전술한 본 개시의 실시 예에 따라 기지국이 동작할 수 있도록 일련의 과정을 제어할 수 있다. 기지국 처리부(1230)는 제어부나 하나 이상의 프로세서로 구현될 수 있다.The base station processing unit 1230 can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. The base station processing unit 1230 may be implemented as a control unit or one or more processors.
도 13은 본 개시의 일 실시예에 따른 네트워크 엔티티의 구조를 도시한 도면이다. FIG. 13 is a diagram illustrating the structure of a network entity according to an embodiment of the present disclosure.
도 13을 참조하면, 네트워크 엔티티(network entity)는 네트워크 엔티티 수신부(1310), 네트워크 엔티티 송신부(1320), 네트워크 엔티티 처리부(제어부)(1330)를 포함할 수 있다. 여기서, 네트워크 엔티티는 AMF, SMF, UPF, DN, NSSF, NEF, AUSF, NRF, PCF, UDM, AF 등을 포함할 수 있다.Referring to FIG. 13, a network entity may include a network entity receiving unit 1310, a network entity transmitting unit 1320, and a network entity processing unit (control unit) 1330. Here, network entities may include AMF, SMF, UPF, DN, NSSF, NEF, AUSF, NRF, PCF, UDM, AF, etc.
네트워크 엔티티 수신부(1310)와 네트워크 엔티티 송신부(1320)는 함께 송수신부라 칭해질 수 있다. 전술한 네트워크 엔티티의 통신 방법에 따라, 네트워크 엔티티의 네트워크 엔티티 수신부(1310), 네트워크 엔티티 송신부(1320), 네트워크 엔티티 처리부(1330)가 동작할 수 있다. 다만, 네트워크 엔티티의 구성 요소가 전술한 예에 한정되는 것은 아니다. 예를 들어, 네트워크 엔티티는 전술한 구성 요소들 보다 더 많은 구성 요소(예를 들어, 메모리 등)를 포함하거나 더 적은 구성 요소를 포함할 수도 있다. 뿐만 아니라 네트워크 엔티티 수신부(1310), 네트워크 엔티티 송신부(1320), 네트워크 엔티티 처리부(1330)가 하나의 칩(chip) 형태로 구현될 수도 있다.The network entity receiving unit 1310 and the network entity transmitting unit 1320 may be referred to together as a transmitting/receiving unit. According to the communication method of the network entity described above, the network entity receiving unit 1310, the network entity transmitting unit 1320, and the network entity processing unit 1330 of the network entity may operate. However, the components of the network entity are not limited to the examples described above. For example, a network entity may include more components (eg, memory, etc.) or fewer components than the components described above. In addition, the network entity receiving unit 1310, the network entity transmitting unit 1320, and the network entity processing unit 1330 may be implemented in the form of a single chip.
네트워크 엔티티 수신부(1310) 및 네트워크 엔티티 송신부(1320)(또는, 송수신부)는 기지국 및/또는 다른 네트워크 엔티티와 신호를 송수신할 수 있다. 여기에서, 신호는 제어 정보 및 데이터를 포함할 수 있다. 송수신부는 유무선 채널을 통해 신호를 수신하여 네트워크 엔티티 처리부(1330)로 출력하고, 네트워크 엔티티 처리부(1330)로부터 출력된 신호를 유무선 채널을 통해 전송할 수 있다. The network entity receiving unit 1310 and the network entity transmitting unit 1320 (or transceiving unit) may transmit and receive signals with a base station and/or other network entities. Here, the signal may include control information and data. The transceiver may receive a signal through a wired or wireless channel and output it to the network entity processing unit 1330, and transmit the signal output from the network entity processing unit 1330 through a wired or wireless channel.
메모리(미도시)는 네트워크 엔티티의 동작에 필요한 프로그램 및 데이터를 저장할 수 있다. 또한, 메모리는 네트워크 엔티티에서 획득되는 신호에 포함된 제어 정보 또는 데이터를 저장할 수 있다. 메모리는 롬(ROM), 램(RAM), 하드디스크, CD-ROM 및 DVD 등과 같은 저장 매체 또는 저장 매체들의 조합으로 구성될 수 있다. Memory (not shown) may store programs and data necessary for the operation of the network entity. Additionally, the memory may store control information or data included in signals obtained from a network entity. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.
네트워크 엔티티 처리부(1330)는 전술한 본 개시의 실시 예에 따라 네트워크 엔티티가 동작할 수 있도록 일련의 과정을 제어할 수 있다. 네트워크 엔티티 처리부(1330)는 제어부나 하나 이상의 프로세서로 구현될 수 있다.The network entity processing unit 1330 may control a series of processes so that the network entity can operate according to the above-described embodiment of the present disclosure. The network entity processing unit 1330 may be implemented as a control unit or one or more processors.
본 개시의 청구항 또는 명세서에 기재된 실시 예들에 따른 방법들은 하드웨어, 소프트웨어, 또는 하드웨어와 소프트웨어의 조합의 형태로 구현될(implemented) 수 있다. Methods according to 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.
소프트웨어로 구현하는 경우, 하나 이상의 프로그램(소프트웨어 모듈)을 저장하는 컴퓨터 판독 가능 저장 매체가 제공될 수 있다. 컴퓨터 판독 가능 저장 매체에 저장되는 하나 이상의 프로그램은, 전자 장치(device) 내의 하나 이상의 프로세서에 의해 실행 가능하도록 구성된다(configured for execution). 하나 이상의 프로그램은, 전자 장치로 하여금 본 개시의 청구항 또는 명세서에 기재된 실시 예들에 따른 방법들을 실행하게 하는 명령어(instructions)를 포함한다. When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). 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.
이러한 프로그램(소프트웨어 모듈, 소프트웨어)은 랜덤 액세스 메모리(random access memory), 플래시(flash) 메모리를 포함하는 불휘발성(non-volatile) 메모리, 롬(read only memory, ROM), 전기적 삭제가능 프로그램가능 롬(electrically erasable programmable read only memory, EEPROM), 자기 디스크 저장 장치(magnetic disc storage device), 컴팩트 디스크 롬(compact disc-ROM, CD-ROM), 디지털 다목적 디스크(digital versatile discs, DVDs) 또는 다른 형태의 광학 저장 장치, 마그네틱 카세트(magnetic cassette)에 저장될 수 있다. 또는, 이들의 일부 또는 전부의 조합으로 구성된 메모리에 저장될 수 있다. 또한, 각각의 구성 메모리는 다수 개 포함될 수도 있다. These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.
또한, 프로그램은 인터넷(Internet), 인트라넷(Intranet), LAN(local area network), WAN(wide area network), 또는 SAN(storage area network)과 같은 통신 네트워크, 또는 이들의 조합으로 구성된 통신 네트워크를 통하여 접근(access)할 수 있는 부착 가능한(attachable) 저장 장치(storage device)에 저장될 수 있다. 이러한 저장 장치는 외부 포트를 통하여 본 개시의 실시 예를 수행하는 장치에 접속할 수 있다. 또한, 통신 네트워크상의 별도의 저장장치가 본 개시의 실시 예를 수행하는 장치에 접속할 수도 있다.In addition, the program may be distributed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present disclosure.
상술한 본 개시의 구체적인 실시 예들에서, 개시에 포함되는 구성 요소는 제시된 구체적인 실시 예에 따라 단수 또는 복수로 표현되었다. 그러나, 단수 또는 복수의 표현은 설명의 편의를 위해 제시한 상황에 적합하게 선택된 것으로서, 본 개시가 단수 또는 복수의 구성 요소에 제한되는 것은 아니며, 복수로 표현된 구성 요소라 하더라도 단수로 구성되거나, 단수로 표현된 구성 요소라 하더라도 복수로 구성될 수 있다.In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit 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 may be composed of singular or singular. Even expressed components may be composed of plural elements.
본 개시의 실시예들을 설명하는 도면에서, 설명의 순서가 반드시 실행의 순서와 대응되지는 않으며, 선후 관계가 변경되거나 병렬적으로 실행될 수도 있다. 또한, 본 개시의 실시예들을 설명하는 도면은 본 개시의 본질을 해치지 않는 범위 내에서 일부의 구성 요소가 생략되고 일부의 구성요소만을 포함할 수도 있다. In the drawings explaining the embodiments of the present disclosure, the order of description does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel. Additionally, drawings illustrating embodiments of the present disclosure may omit some components and include only some components within the scope that does not impair the essence of the present disclosure.
본 개시의 실시예들은 본 개시의 본질을 해치지 않는 범위 내에서 각 실시예에 포함된 내용의 일부 또는 전부가 조합되어 실행될 수도 있다.Embodiments of the present disclosure may be implemented by combining some or all of the content included in each embodiment within the scope without impairing the essence of the present disclosure.
한편, 본 명세서와 도면에 개시된 본 개시의 실시예들은 본 개시의 기술 내용을 쉽게 설명하고 본 개시의 이해를 돕기 위해 특정 예를 제시한 것일 뿐이며, 본 개시의 범위를 한정하고자 하는 것은 아니다. 즉, 여기에 개시된 실시예들 이외에도 본 개시의 기술적 사상에 바탕을 둔 다른 변형 예들이 실시 가능하다는 것은 본 개시가 속하는 기술 분야에서 통상의 지식을 가진 자에게 자명한 것이다.Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid 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 in addition to the embodiments disclosed herein, other modifications based on the technical idea of the present disclosure can be implemented.

Claims (14)

  1. 무선통신 시스템에서 AMF(access and mobility management function)의 동작 방법에 있어서,In a method of operating an access and mobility management function (AMF) in a wireless communication system,
    NEF(network exposure function)에게, 위성 무선 액세스 네트워크(satellite radio access network(RAN))의 커버리지 정보(coverage information) 전달을 위한 커버리지 정보 전달 ID와 커버리지 정보 요청을 포함하는 인증 요청 메시지(authentication request message)를 전송하는 단계;An authentication request message containing a coverage information delivery ID and a request for coverage information to deliver coverage information of a satellite radio access network (RAN) to the network exposure function (NEF). transmitting;
    커버리지 정보 서버(coverage information server)로부터, 상기 커버리지 정보 전달 ID에 대응되는 UE(user equipment)의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하는 단계; 및Receiving at least one of an authentication result and coverage information of a user equipment (UE) corresponding to the coverage information delivery ID from a coverage information server; and
    상기 UE에게, 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 전송하는 단계를 포함하는, 방법.A method comprising transmitting at least one of an authentication result and coverage information to the UE.
  2. 제1항에 있어서,According to paragraph 1,
    상기 UE로부터, 상기 커버리지 정보 전달 ID와 상기 커버리지 정보 요청을 포함하는 등록 요청 메시지를 수신하는 단계; Receiving, from the UE, a registration request message including the coverage information delivery ID and the coverage information request;
    UDM(unified data management)에게, 상기 UE의 SUPI(subscription permanent identifier) 및 상기 커버리지 정보 전달 ID 중 적어도 하나를 포함하는 가입자 정보를 요청하는 요청 메시지을 전송하는 단계; Transmitting, to a unified data management (UDM), a request message requesting subscriber information including at least one of a subscription permanent identifier (SUPI) of the UE and the coverage information delivery ID;
    상기 UDM으로부터, 상기 UE에 대한 상기 커버리지 정보 전달의 허용 여부를 지시하는 가입자 정보를 포함하는 응답 메시지를 수신하는 단계; Receiving, from the UDM, a response message including subscriber information indicating whether to allow delivery of the coverage information to the UE;
    상기 가입자 정보에 기초하여, 상기 UE에게 등록 수락(accept) 메시지를 전송하는 단계를 포함하는, 방법.A method comprising transmitting a registration accept message to the UE based on the subscriber information.
  3. 제2항에 있어서,According to paragraph 2,
    상기 커버리지 정보 전달 ID, 상기 가입자 정보 및 상기 UE에 대한 상기 커버리지 정보 서버의 인증 여부 중 적어도 하나 이상에 기초하여, 상기 UE에 대한 추가 인증 필요 여부를 판단하는 단계를 더 포함하는, 방법.The method further comprising determining whether additional authentication is necessary for the UE based on at least one of the coverage information delivery ID, the subscriber information, and whether the coverage information server has authenticated the UE.
  4. 제1항에 있어서,According to paragraph 1,
    상기 인증 요청 메시지는,The authentication request message is,
    상기 커버리지 정보 서버의 주소(coverage information server address), 상기 UE의 위치 정보 중 적어도 하나 이상을 더 포함하고,It further includes at least one of the coverage information server address and location information of the UE,
    상기 커버리지 정보 요청은,The coverage information request is,
    커버리지 정보 타입(coverage information type), 커버리지 정보가 필요한 영역(coverage information required area), 커버리지 정보가 필요한 경로(coverage information required trajectory), 커버리지 정보가 필요한 위치(coverage information required position) 및 커버리지 정보의 정확도(required accuracy level of coverage information) 중 적어도 하나 이상을 포함하는, 방법.Coverage information type, coverage information required area, coverage information required trajectory, coverage information required position, and coverage information accuracy ( A method including at least one of the required accuracy level of coverage information.
  5. 무선통신 시스템에서 UE(user equipment)의 동작 방법에 있어서, In a method of operating a UE (user equipment) in a wireless communication system,
    AMF(access and mobility management function)에게, 커버리지 정보(coverage information) 전달 ID와 커버리지 정보 요청을 포함하는 등록 요청 메시지를 전송하는 단계; 및 Transmitting a registration request message including a coverage information delivery ID and a coverage information request to an access and mobility management function (AMF); and
    상기 AMF로부터, 상기 UE의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하는 단계를 포함하는, 방법.A method comprising receiving, from the AMF, at least one of an authentication result and coverage information of the UE.
  6. 제5항에 있어서,According to clause 5,
    UDM(unified data management) 또는 커버리지 정보 서버(coverage information server)와 인증 절차를 수행하는 단계를 더 포함하는, 방법.The method further includes performing an authentication procedure with a unified data management (UDM) or coverage information server.
  7. 제5항에 있어서,According to clause 5,
    상기 등록 요청 메시지는,The registration request message is,
    커버리지 정보 서버의 주소(coverage information server address), 상기 UE의 위치 정보 중 적어도 하나 이상을 더 포함하고,It further includes at least one of a coverage information server address and location information of the UE,
    상기 커버리지 정보 요청은,The coverage information request is,
    커버리지 정보 타입(coverage information type), 커버리지 정보가 필요한 영역(coverage information required area), 커버리지 정보가 필요한 경로(coverage information required trajectory), 커버리지 정보가 필요한 위치(coverage information required position) 및 커버리지 정보의 정확도(required accuracy level of coverage information) 중 적어도 하나 이상을 포함하는, 방법.Coverage information type, coverage information required area, coverage information required trajectory, coverage information required position, and coverage information accuracy ( A method including at least one of the required accuracy level of coverage information.
  8. 무선통신 시스템에서 AMF(access and mobility management function)에 있어서,In AMF (access and mobility management function) in a wireless communication system,
    통신부(transceiver); 및Transceiver; and
    상기 통신부와 작동 가능하게 결합된(operably coupled) 적어도 하나의 제어부(controller)를 포함하고,Comprising at least one controller operably coupled to the communication unit,
    상기 제어부는,The control unit,
    NEF(network exposure function)에게, 위성 무선 액세스 네트워크(satellite radio access network(RAN))의 커버리지 정보(coverage information) 전달을 위한 커버리지 정보 전달 ID와 커버리지 정보 요청을 포함하는 인증 요청 메시지(authentication request message)를 전송하고, An authentication request message containing a coverage information delivery ID and a request for coverage information to deliver coverage information of a satellite radio access network (RAN) to the network exposure function (NEF). send,
    커버리지 정보 서버(coverage information server)로부터, 상기 커버리지 정보 전달 ID에 대응되는 UE(user equipment)의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하며, Receiving at least one of an authentication result and coverage information of a user equipment (UE) corresponding to the coverage information delivery ID from a coverage information server,
    상기 UE에게, 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 전송하도록 구성되는, AMF.An AMF configured to transmit at least one of an authentication result and coverage information to the UE.
  9. 제8항에 있어서,According to clause 8,
    상기 제어부는,The control unit,
    상기 UE로부터, 상기 커버리지 정보 전달 ID와 상기 커버리지 정보 요청을 포함하는 등록 요청 메시지를 수신하고,Receiving, from the UE, a registration request message including the coverage information delivery ID and the coverage information request,
    UDM(unified data management)에게, 상기 UE의 SUPI(subscription permanent identifier) 및 상기 커버리지 정보 전달 ID 중 적어도 하나를 포함하는 가입자 정보를 요청하는 요청 메시지을 전송하고,Transmitting to a unified data management (UDM) a request message requesting subscriber information including at least one of the subscription permanent identifier (SUPI) of the UE and the coverage information delivery ID,
    상기 UDM으로부터, 상기 UE에 대한 상기 커버리지 정보 전달의 허용 여부를 지시하는 가입자 정보를 포함하는 응답 메시지를 수신하고,Receiving, from the UDM, a response message containing subscriber information indicating whether to allow delivery of the coverage information to the UE,
    상기 가입자 정보에 기초하여, 상기 UE에게 등록 수락(accept) 메시지를 전송하도록 더 구성되는, AMF.AMF, further configured to transmit a registration accept message to the UE based on the subscriber information.
  10. 제9항에 있어서,According to clause 9,
    상기 제어부는,The control unit,
    상기 커버리지 정보 전달 ID, 상기 가입자 정보 및 상기 UE에 대한 상기 커버리지 정보 서버의 인증 여부 중 적어도 하나 이상에 기초하여, 상기 UE에 대한 추가 인증 필요 여부를 판단하도록 더 구성되는, AMF.AMF further configured to determine whether additional authentication for the UE is required based on at least one of the coverage information delivery ID, the subscriber information, and whether the coverage information server has authenticated the UE.
  11. 제8항에 있어서,According to clause 8,
    상기 인증 요청 메시지는,The authentication request message is,
    상기 커버리지 정보 서버의 주소(coverage information server address), 상기 UE의 위치 정보 중 적어도 하나 이상을 더 포함하고,It further includes at least one of the coverage information server address and location information of the UE,
    상기 커버리지 정보 요청은,The coverage information request is,
    커버리지 정보 타입(coverage information type), 커버리지 정보가 필요한 영역(coverage information required area), 커버리지 정보가 필요한 경로(coverage information required trajectory), 커버리지 정보가 필요한 위치(coverage information required position) 및 커버리지 정보의 정확도(required accuracy level of coverage information) 중 적어도 하나 이상을 포함하는, AMF.Coverage information type, coverage information required area, coverage information required trajectory, coverage information required position, and coverage information accuracy ( AMF, including at least one of the required accuracy level of coverage information.
  12. 무선통신 시스템에서 UE(user equipment)에 있어서, In UE (user equipment) in a wireless communication system,
    통신부(transceiver); 및Transceiver; and
    상기 통신부와 작동 가능하게 결합된(operably coupled) 적어도 하나의 제어부(controller)를 포함하고,Comprising at least one controller operably coupled to the communication unit,
    상기 제어부는,The control unit,
    AMF(access and mobility management function)에게, 커버리지 정보(coverage information) 전달 ID와 커버리지 정보 요청을 포함하는 등록 요청 메시지를 전송하고,Send a registration request message including a coverage information delivery ID and a coverage information request to the access and mobility management function (AMF),
    상기 AMF로부터, 상기 UE의 인증 결과 및 커버리지 정보 중 적어도 하나 이상을 수신하도록 구성되는, UE.A UE configured to receive at least one of an authentication result and coverage information of the UE from the AMF.
  13. 제12항에 있어서,According to clause 12,
    상기 제어부는,The control unit,
    UDM(unified data management) 또는 커버리지 정보 서버(coverage information server)와 인증 절차를 수행하도록 구성되는, UE.A UE configured to perform an authentication procedure with a unified data management (UDM) or coverage information server.
  14. 제12항에 있어서,According to clause 12,
    상기 등록 요청 메시지는,The registration request message is,
    커버리지 정보 서버의 주소(coverage information server address), 상기 UE의 위치 정보 중 적어도 하나 이상을 더 포함하고,It further includes at least one of a coverage information server address and location information of the UE,
    상기 커버리지 정보 요청은,The coverage information request is,
    커버리지 정보 타입(coverage information type), 커버리지 정보가 필요한 영역(coverage information required area), 커버리지 정보가 필요한 경로(coverage information required trajectory), 커버리지 정보가 필요한 위치(coverage information required position) 및 커버리지 정보의 정확도(required accuracy level of coverage information) 중 적어도 하나 이상을 포함하는, UE.Coverage information type, coverage information required area, coverage information required trajectory, coverage information required position, and coverage information accuracy ( A UE that includes at least one of the required accuracy level of coverage information.
PCT/KR2023/011536 2022-08-09 2023-08-04 Method and apparatus for providing coverage information in wireless communication system WO2024035021A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2022-0099315 2022-08-09
KR1020220099315A KR20240020951A (en) 2022-08-09 2022-08-09 Method and apparatus for providing coverage information in wireless communication system

Publications (1)

Publication Number Publication Date
WO2024035021A1 true WO2024035021A1 (en) 2024-02-15

Family

ID=89852155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/011536 WO2024035021A1 (en) 2022-08-09 2023-08-04 Method and apparatus for providing coverage information in wireless communication system

Country Status (2)

Country Link
KR (1) KR20240020951A (en)
WO (1) WO2024035021A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174383A1 (en) * 2017-03-21 2018-09-27 엘지전자 주식회사 Session management method and smf node
KR102164230B1 (en) * 2017-06-17 2020-10-12 엘지전자 주식회사 Terminal registration method and apparatus therefor in wireless communication system
KR102425675B1 (en) * 2017-08-14 2022-07-28 삼성전자 주식회사 Method for negotiating provision function and mapping slice information between network and user equipment in 5g system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174383A1 (en) * 2017-03-21 2018-09-27 엘지전자 주식회사 Session management method and smf node
KR102164230B1 (en) * 2017-06-17 2020-10-12 엘지전자 주식회사 Terminal registration method and apparatus therefor in wireless communication system
KR102425675B1 (en) * 2017-08-14 2022-07-28 삼성전자 주식회사 Method for negotiating provision function and mapping slice information between network and user equipment in 5g system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
JEAN-YVES FINE, THALES: "KI #1, KI #2, New solution enabler with coverage information over NAS.", 3GPP DRAFT; S2-2205511; TYPE PCR; FS_5GSAT_PH2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Online; 20220817 - 20220826, 3 August 2022 (2022-08-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052183911 *
QUALCOMM INCORPORATED: "New Solution for KI#1, KI#2: Provision of Coverage Data to a UE", 3GPP DRAFT; S2-2205372, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-Meeting; 20220516 - 20220520, 21 May 2022 (2022-05-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052160834 *

Also Published As

Publication number Publication date
KR20240020951A (en) 2024-02-16

Similar Documents

Publication Publication Date Title
WO2022177347A1 (en) Method and device for edge application server discovery
WO2019070100A1 (en) Method and device for transmitting or receiving information in wireless communication system supporting network slicing
WO2021235880A1 (en) Method and device for providing local data network information to terminal in wireless communication system
WO2021206519A1 (en) Apparatus and method for transmitting bridge management information in wireless communication system
WO2020138981A1 (en) Method and apparatus for providing rule information in wireless communication system
WO2021235878A1 (en) Method and apparatus for improving cellular internet of things (ciot) optimizations in a telecommunication network
WO2021133092A1 (en) Method and apparatus to manage nssaa procedure in wireless communication network
WO2023075214A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
WO2023146310A1 (en) Method and apparatus for supporting change of network slice in wireless communication system
WO2023075299A1 (en) Device and method for providing emergency call service in wireless communication network
WO2022080900A1 (en) Method and device for performing communication over satellite network in wireless communication system
WO2022211519A1 (en) A method for measuring performance for qos
WO2024035021A1 (en) Method and apparatus for providing coverage information in wireless communication system
WO2021230679A1 (en) Method and apparatus for transmitting and receiving signals in wireless communication system
WO2020036428A1 (en) Method for transmitting non ip-data in 5g network
WO2023059127A1 (en) Method and apparatus for traffic processing using traffic classification in wireless communication system
WO2024076174A1 (en) Method and apparatus for providing ue policy information in wireless communication system
WO2024085655A1 (en) Method and apparatus for selecting policy control function in wireless communication system supporting interworking between networks
WO2024096657A1 (en) Method and device for providing congestion information in communication system
WO2023153836A1 (en) Method and device for managing registration and connection of terminal in wireless communication system
WO2023140704A1 (en) Method and device for mapping ue routing selection policy in wireless communication system
WO2024025384A1 (en) Method and apparatus for providing ue policy in wireless communication system
WO2023191502A1 (en) Method and device for providing access path in wireless communication system
WO2024072116A1 (en) Method and device for l4s congestion marking, reporting, and local feedback in wireless communication system
WO2024025359A1 (en) Method and apparatus for minimization of drive tests measurement enhancement

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: 23852901

Country of ref document: EP

Kind code of ref document: A1