WO2024035021A1 - Procédé et appareil pour fournir des informations de couverture dans un système de communication sans fil - Google Patents

Procédé et appareil pour fournir des informations de couverture dans un système de communication sans fil 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
English (en)
Korean (ko)
Inventor
김동연
박중신
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2024035021A1 publication Critical patent/WO2024035021A1/fr

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.

Landscapes

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

Abstract

La présente divulgation se rapporte à un système de communication 5G ou 6G permettant de prendre en charge des débits de transmission de données supérieurs. Selon un mode de réalisation, un procédé de fonctionnement d'une fonction de gestion d'accès et de mobilité (AMF) dans un système de communication sans fil comprend les étapes consistant à : transmettre, à une fonction d'exposition de réseau (NEF), un message de demande d'authentification comprenant un ID de transmission d'informations de couverture et une demande d'informations de couverture pour transmettre les informations de couverture d'un réseau d'accès radio par satellite (RAN) ; recevoir, d'un serveur d'informations de couverture, le résultat d'authentification et/ou les informations de couverture d'un équipement utilisateur (UE) correspondant à l'ID de transmission d'informations de couverture ; et transmettre, à l'UE, le résultat d'authentification et/ou les informations de couverture.
PCT/KR2023/011536 2022-08-09 2023-08-04 Procédé et appareil pour fournir des informations de couverture dans un système de communication sans fil WO2024035021A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020220099315A KR20240020951A (ko) 2022-08-09 2022-08-09 무선통신 시스템에서 커버리지 정보 제공 방법 및 장치
KR10-2022-0099315 2022-08-09

Publications (1)

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

Family

ID=89852155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/011536 WO2024035021A1 (fr) 2022-08-09 2023-08-04 Procédé et appareil pour fournir des informations de couverture dans un système de communication sans fil

Country Status (2)

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

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174383A1 (fr) * 2017-03-21 2018-09-27 엘지전자 주식회사 Procédé de gestion de session et nœud smf
KR102164230B1 (ko) * 2017-06-17 2020-10-12 엘지전자 주식회사 무선 통신 시스템에서 단말의 등록 방법 및 이를 위한 장치
KR102425675B1 (ko) * 2017-08-14 2022-07-28 삼성전자 주식회사 5g 시스템에서 네트워크와 단말 간 제공 기능 협상 및 슬라이스 정보 맵핑 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174383A1 (fr) * 2017-03-21 2018-09-27 엘지전자 주식회사 Procédé de gestion de session et nœud smf
KR102164230B1 (ko) * 2017-06-17 2020-10-12 엘지전자 주식회사 무선 통신 시스템에서 단말의 등록 방법 및 이를 위한 장치
KR102425675B1 (ko) * 2017-08-14 2022-07-28 삼성전자 주식회사 5g 시스템에서 네트워크와 단말 간 제공 기능 협상 및 슬라이스 정보 맵핑 방법

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 (ko) 2024-02-16

Similar Documents

Publication Publication Date Title
WO2022177347A1 (fr) Procédé et dispositif de découverte d'un serveur d'applications périphérique
WO2019070100A1 (fr) Dispositif et procédé d'émission ou de réception d'informations dans un système de communication sans fil prenant en charge un découpage de réseau
WO2021235880A1 (fr) Procédé et dispositif de fourniture d'informations d'un réseau de données local à un terminal dans un système de communication sans fil
WO2021206519A1 (fr) Appareil et procédé de transmission d'informations de gestion de pont dans un système de communication sans fil
WO2020138981A1 (fr) Procédé et appareil pour transmettre des informations de règle dans un système de communication sans fil
WO2021235878A1 (fr) Procédé et appareil pour améliorer les optimisations de l'internet des objets cellulaire dans un réseau de télécommunication
WO2021133092A1 (fr) Procédé et appareil permettant de gérer une procédure de transfert intercellulaire dans un système de communication sans fil
WO2023075214A1 (fr) Procédé et appareil pour la prise en charge d'un service d'informatique en périphérie pour un équipement utilisateur en itinérance dans un système de communication sans fil
WO2023146310A1 (fr) Procédé et appareil pour la prise en charge de changement de tranche de réseau dans un système de communication sans fil
WO2023075299A1 (fr) Dispositif et procédé pour fournir un service d'appel d'urgence dans un réseau de communication sans fil
WO2022080900A1 (fr) Procédé et dispositif pour réaliser une communication sur un réseau de satellites dans un système de communication sans fil
WO2022211519A1 (fr) Procédé de mesure de performance pour qos
WO2024035021A1 (fr) Procédé et appareil pour fournir des informations de couverture dans un système de communication sans fil
WO2021230679A1 (fr) Procédé et appareil d'émission et de réception de signaux dans un système de communication sans fil
WO2020036428A1 (fr) Procédé de transmission de données non ip dans un réseau 5g
WO2023059127A1 (fr) Procédé et appareil de traitement de trafic faisant appel à la classification de trafic dans un système de communication sans fil
WO2024076174A1 (fr) Procédé et appareil permettant de fournir des informations de politique d'ue dans un système de communication sans fil
WO2024085655A1 (fr) Procédé et appareil de sélection de fonction de commande de politique dans un système de communication sans fil prenant en charge un interfonctionnement entre des réseaux
WO2024096657A1 (fr) Procédé et dispositif permettant de fournir des informations de congestion dans un système de communication
WO2023153836A1 (fr) Procédé et dispositif destiné à la gestion d'enregistrement et de connexion de terminal dans un système de communication sans fil
WO2023140704A1 (fr) Procédé et dispositif de mappage de politique de sélection de routage d'ue dans un système de communication sans fil
WO2024025384A1 (fr) Procédé et appareil pour fournir une politique d'équipement utilisateur (ue) dans un système de communication sans fil
WO2023191502A1 (fr) Procédé et dispositif de fourniture d'un trajet d'accès dans un système de communication sans fil
WO2024072116A1 (fr) Procédé et dispositif de marquage d'encombrement l4s, de signalement et de rétroaction locale dans un système de communication sans fil
WO2024025359A1 (fr) Procédé et appareil de minimisation d'amélioration de mesure de tests de conduite

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