Method and device for satellite group-based session management in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to an embodiment of the present disclosure, a data transmission delay can be constantly maintained by performing UPF selection and reselection of a PDU session on the basis of deployment information about a satellite group.

Description

Method and device for satellite constellation-based session management in a wireless communication system

[0001] The present invention relates to a method and apparatus for satellite constellation-based session management in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] Meanwhile, in wireless communication systems, the need for a method to maintain a constant data transmission delay by considering the temporal positions of satellites forming a satellite constellation composed of one or more satellites has arisen.

[0009] An object of the present invention is to provide a method for maintaining a constant data transmission delay by appropriately changing a satellite / user plane function (UPF) entity used for user plane connection by considering the time-dependent positions of satellites forming a satellite constellation composed of one or more satellites in a wireless communication system.

[0010] According to one embodiment of the present disclosure, a method performed by a session management function (SMF) entity in a wireless communication system may include the steps of: transmitting a request message requesting information related to a satellite constellation arrangement to a network exposure function (NEF) entity, the request message including a satellite constellation identity (ID); and receiving information related to the satellite constellation arrangement from the NEF entity, which has obtained the information related to the satellite constellation arrangement based on the satellite constellation ID.

[0011] Meanwhile, in a wireless communication system according to another embodiment of the present disclosure, a method performed by a network exposure function (NEF) entity includes the steps of: receiving a request message requesting information related to satellite constellation arrangement from a session management function (SMF) entity, the request message including a satellite constellation identifier (ID); acquiring information related to the satellite constellation arrangement from a user data repository (UDR) entity based on the request message; and transmitting the information related to the satellite constellation arrangement to the SMF entity; wherein the information related to the satellite constellation arrangement may include at least one of a list of IDs of a plurality of satellites constituting a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about a time when the plurality of satellites are available for connection in a core network (available time information).

[0012] Meanwhile, in a wireless communication system according to another embodiment of the present disclosure, a session management function (SMF) entity may include a transceiver; and a control unit configured to control a network exposure function (NEF) entity to transmit a request message requesting information related to satellite constellation arrangement through the transceiver, wherein the request message includes a satellite constellation identifier (ID), and to receive information related to satellite constellation arrangement from the NEF entity that has obtained the information related to satellite constellation arrangement based on the satellite constellation ID, through the transceiver.

[0013] Meanwhile, in a wireless communication system according to another embodiment of the present disclosure, a network exposure function (NEF) entity comprises: a transceiver; receiving a request message requesting information related to satellite constellation arrangement from a session management function (SMF) entity through the transceiver; wherein the request message includes a satellite constellation identifier (ID); obtaining information related to the satellite constellation arrangement from a user data repository (UDR) entity based on the request message; and controlling transmission of the information related to the satellite constellation arrangement to the SMF entity through the transceiver; wherein the information related to the satellite constellation arrangement may include at least one of a list of IDs of a plurality of satellites constituting a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about a time at which the plurality of satellites are available for connection in a core network (available time information).

[0014] According to one embodiment of the present invention, a method for performing UPF selection and reselection of a PDU session based on satellite constellation arrangement information can be provided.

[0015] FIG. 1 is a diagram illustrating a 5G system structure according to an embodiment of the present disclosure.

[0016] FIG. 2 is a diagram illustrating a 5G system structure when a 5G NF is located on a satellite according to an embodiment of the present disclosure.

[0017] FIG. 3 is a diagram illustrating a 5G system structure in which a 5G NF is located in a satellite constellation network composed of one or more satellites according to one embodiment of the present disclosure.

[0018] FIG. 4 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0019] FIG. 5 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0020] FIG. 6 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0021] FIG. 7 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0022] FIG. 8A is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to one embodiment of the present disclosure.

[0023] FIG. 8b is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to one embodiment of the present disclosure.

[0024] FIG. 8c is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to one embodiment of the present disclosure.

[0025] FIG. 8d is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to one embodiment of the present disclosure.

[0026] FIG. 8e is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to one embodiment of the present disclosure.

[0027] FIG. 8F is a diagram illustrating a method for managing a session in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more satellites, according to an embodiment of the present disclosure.

[0028] FIG. 9 is a diagram illustrating a method for managing a satellite ID, a satellite constellation ID, and an NF ID in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more satellites, according to one embodiment of the present disclosure.

[0029] FIG. 10 is a diagram illustrating a method for managing a satellite ID, a satellite constellation ID, and an NF ID in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more satellites, according to one embodiment of the present disclosure.

[0030] FIG. 11 is a diagram illustrating the structure of a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more mobile satellites, according to one embodiment of the present disclosure, and changes in the structure over time.

[0031] FIG. 12A is a diagram illustrating a method for managing user plane paths in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0032] FIG. 12b is a diagram illustrating a method for managing user plane paths in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0033] FIG. 12c is a diagram illustrating a method for managing a user plane path in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0034] FIG. 13A is a diagram illustrating a method for managing user plane paths in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0035] FIG. 13b is a diagram illustrating a method for managing a user plane path in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0036] FIG. 13c is a diagram illustrating a method for managing user plane paths in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0037] FIG. 13d is a diagram illustrating a method for managing a user plane path in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0038] FIG. 13e is a diagram illustrating a method for managing user plane paths in a 5G system where a 5G NF is located in a satellite constellation network consisting of one or more mobile satellites, according to one embodiment of the present disclosure.

[0039] FIG. 14 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0040] FIG. 15 is a diagram illustrating a network function entity according to one embodiment of the present disclosure.

[0041] The operating principle of the present invention will be described in detail with reference to the attached drawings below.

[0042] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0043] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0044] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined solely by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0045] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0046] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0047] Here, the term '~ unit' used in this embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0048] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0049] For convenience of explanation, this disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE (3rd Generation Partnership Project Long Term Evolution) standard and the 3GPP 5G standard. However, the present invention is not limited to these terms and names and can be equally applied to systems conforming to other standards.

[0050] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, the attached drawings of the present disclosure are provided to aid understanding of the present disclosure, and it should be noted that the present invention is not limited to the forms or arrangements illustrated in the drawings.

[0051] 5G network functions (NFs) can be located on satellites, which may be a single satellite or a constellation of one or more satellites. Evolved 5G systems may place some or all of their system components on one or more satellites. In such a system architecture, a method for providing control plane and user plane connectivity may be required. Specifically, in a constellation network of one or more mobile satellites, where each satellite has a different UPF and may be connected to different local servers, the satellites / UPFs used for user plane connectivity may change location over time. Consequently, the path between the UE and the PSA UPF, and between the PSA UPF and the local server, may become longer depending on the location of the satellite on which the PSA UPF is located, which may result in data transmission delays.

[0052] According to one embodiment of the present disclosure, a method is proposed to maintain a constant data transmission delay by appropriately changing a satellite / UPF used for user plane connection by considering the time-dependent positions of satellites constituting a satellite constellation.

[0053] FIG. 1 is a diagram illustrating a 5G system structure related to an embodiment of the present disclosure.

[0054] Referring to FIG. 1, the 5G system architecture may include various components (e.g., network functions (NFs)). FIG. 1 illustrates at least some of them, including an authentication server function (AUSF) device (110), an access and mobility management function (AMF) device (103), a session management function (SMF) device (104), a policy control function (PCF) device (107), an application function (AF) device (108), a unified data management (UDM) device (106), a data network (DN) (112), a user plane function (UPF) device (105), a (radio) access network (R)AN) (102), and a terminal, for example, a user equipment (UE) (101). In addition, in FIG. 1, a Network Slice Selection Function (NSSF) device (109) and a Network Slice Specific Authentication and Authorization Function (NSSAAF) device (111) are exemplarily illustrated.

[0055] In the embodiment disclosed in FIG. 1, each device may be implemented as a single server or device, or as a network slice instance. When implemented as a network slice instance, it may be implemented as two or more identical or different network slice instances within a single server or device, or one network slice instance may be implemented across two or more servers or devices.

[0056] According to one embodiment, each NF can support the following functions:

[0057] AUSF (110) can process and store data for authentication of a terminal (user equipment, UE or terminal).

[0058] AMF (103) can provide functions for access and mobility management per UE, and one UE can be connected to one AMF by default. Specifically, the AMF (103) provides signaling between core network (CN) nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (e.g., N2 interface), termination of NAS signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision of forwarding of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, and roaming authorization check. It may support functions such as access authorization, provision of SMS message transmission between UE and Short Message Service Function (SMSF), security anchor function (SAF), and / or security context management (SCM). Some or all of these functions of AMF (103) may be supported within a single AMF instance operating as one AMF.

[0059] DN (112) may mean, for example, an operator service, Internet access, or a third-party service. DN (112) may transmit a downlink protocol data unit (PDU) to UPF (105) or receive a PDU transmitted from UE (101) through UPF (105).

[0060] PCF (107) can receive information about packet flow from an application server and provide a function to determine policies such as mobility management and session management. Specifically, PCF (107) can support functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination within a user data repository (UDR).

[0061] The SMF (104) can provide session management functions. When a UE has multiple sessions, each session can be managed by a different SMF. Specifically, the SMF (104) can support functions such as session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF and the AN node), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, traffic steering configuration for routing traffic from the UPF to the appropriate destination, termination of interfaces toward policy control functions, enforcement of the control portion of policies and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiator of AN-specific SM information (delivered to the AN via N2 via the AMF), determination of the SSC mode of the session, and roaming functions. As described above, some or all of the functions of SMF (104) may be supported within a single SMF instance that operates as one SMF.

[0062] The UDM (106) can store user subscription data, policy data, etc. The UDM (106) can include two parts, for example, an application front end (FE) (not shown) and a user data repository (UDR) (not shown).

[0063] The FE may include a UDM FE, which is responsible for location management, subscription management, and credential processing, and a PCF-FE, which is responsible for policy control. The UDR may store data required for the functions provided by the UDM-FE and policy profiles required by the PCF. Data stored in the UDR may include user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE may access subscription information stored in the UDR and support functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.

[0064] UPF (105) can transmit a downlink PDU received from DN (112) to UE (101) via (R)AN (102), and can transmit an uplink PDU received from UE (101) via (R)AN (102) to DN (112). Specifically, the UPF (105) may support an anchor point for intra / inter RAT mobility, an external PDU session point for interconnection to a Data Network, a user plane portion of packet routing and forwarding, packet inspection and policy rule enforcement, an uplink classifier to support lawful intercept, traffic usage reporting, and routing of traffic flows to the Data Network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering functions, etc. Some or all of these functions of UPF (105) may be supported within a single UPF instance operating as a single UPF.

[0065] The AF (108) can interact with the 3GPP core network to provide services (e.g., support functions such as application impact on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control).

[0066] (R)AN(102) may be a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).

[0067] The gNB provides functions for radio resource management (e.g., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink / downlink (e.g., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of AMF (103) upon attachment of the UE (101) if routing to AMF (103) is not determined from information provided to the UE (101), routing of user plane data to UPF (105)(s), routing of control plane information to AMF (103), connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or operating and maintenance (O&M)), measurement and measurement reporting for mobility and scheduling. It can support functions such as configuration, transport level packet marking in uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

[0068] UE (101) may refer to a user equipment. The user equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, the user equipment may be a portable device such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or may be a non-portable device such as a personal computer (PC) or vehicle-mounted device. Hereinafter, the user equipment (UE) or terminal will be referred to as such.

[0069] For clarity of explanation, the network exposure function (NEF) device and the NF repository function (NRF) device are not illustrated in FIG. 1, but all NFs illustrated in FIGS. 2 to 5 described below can interact with the NEF and NRF as needed.

[0070] Let's take a look at NRF. NRF (not shown in Fig. 1) can support service discovery functionality. When receiving a second NF discovery request from a first NF instance, the NRF can perform a second NF discovery operation and provide information about the discovered second NF instance to the first NF instance. In addition, the NRF can maintain available NF instances and the services they support.

[0071] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE accesses one DN using one PDU session, but the present disclosure is not limited thereto.

[0072] A UE (101) can access two (e.g., local and central) data networks simultaneously using multiple PDU sessions. In this case, two SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.

[0073] Additionally, the UE (101) may simultaneously access two (e.g., local and central) data networks provided within a single PDU session.

[0074] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in Figure 1.

[0075] - N1: Reference point between UE and AMF

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

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

[0078] - N4: Reference point between SMF and UPF

[0079] - N5: Reference point between PCF and AF

[0080] - N6: Reference point between UPF and data network

[0081] - N7: Reference point between SMF and PCF

[0082] - N8: Reference point between UDM and AMF

[0083] - N9: Reference point between two core UPFs

[0084] - N10: Reference point between UDM and SMF

[0085] - N11: Reference point between AMF and SMF

[0086] - N12: Reference point between AMF and AUSF

[0087] - N13: Reference point between UDM and authentication server function (AUSF)

[0088] - N14: Reference point between two AMFs

[0089] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.

[0090] In the following description, the term "terminal" may refer to UE (101), and the terms "UE" and "terminal" may be used interchangeably. In this case, unless specifically defined additionally, the term "terminal" should be understood as "UE (101).

[0091] A terminal establishes a session by connecting to a data network (e.g., a network providing Internet services) through a 5G system, and can distinguish each data network using an identifier called a Data Network Name (DNN). The DNN can be used to determine NFs, inter-NF interfaces, and operator policies related to the user plane when the terminal connects to a network system and a session. The DNN can be used, for example, to select SMFs and UPF(s) for a PDU session, and to select interface(s) (e.g., N6 interface) between a data network and UPF for a PDU session. In addition, the DNN can be used to determine a mobile communication operator's policy to be applied to a PDU session.

[0092] Meanwhile, FIG. 2 is a diagram illustrating a 5G system structure in a case where a 5G NF is located on a satellite according to an embodiment of the present disclosure.

[0093] You may refer to the contents of Figure 1, and duplicate contents are omitted.

[0094] Referring to FIG. 2, a UE can be connected to a core network through a RAN. The core network can provide a control plane and a user plane connection to the UE through the RAN. The control plane can be composed of a RAN, an AMF, an SMF, a NEF, a UDR, and an AF, and the user plane can be composed of a RAN, an UPF, and a DN. The control plane and the user plane of the core network can be connected to the SMF and the UPF. 5G NF can be located on a satellite, and FIG. 2 illustrates an example where the UPF is installed on a geostationary orbit (GEO) satellite. The UPF installed on a satellite can be connected to a DN (or local server), and the DN can be located on the same satellite as the UPF, on a different satellite, or on the ground.

[0095] In a 5G system with a configuration where a UPF is located on one GEO satellite and a DN is connected to this satellite, as shown in the example of FIG. 2, the method for a core network to provide a user plane to a UE may be as follows.

[0096] 1. When a UE makes a registration request to the core network or requests PDU Session Establishment / Modification, the AMF can determine that a UPF to which the RAN can connect is installed on the GEO satellite. The AMF can determine the ID of the GEO satellite (e.g., GEO Satellite ID) based on the ID of the RAN (e.g., Global RAN Node ID). The RAN can provide the RAN ID to the AMF via an N2 message.

[0097] 2. AMF may provide the ID of the GEO satellite to SMF along with the registration request and / or PDU session establishment / modification request message.

[0098] 3. Based on the ID of the above GEO satellite, SMF can determine an identifier (Data Network Access Identifier, DNAI) that can access the data network.

[0099] 4. When selecting a UPF during the establishment / modification procedure of a PDU session, the SMF can determine the UPF on which the GEO satellite is installed based on the identifier that can access the data network, and select and / or insert the UPF into the PDU session.

[0100] FIG. 3 is a diagram illustrating a 5G system structure in which a 5G NF is located in a satellite constellation network composed of one or more satellites according to one embodiment of the present disclosure.

[0101] The contents of Figures 1 and 2 may be referenced, and duplicate contents are omitted.

[0102] Referring to FIG. 3, in a satellite constellation network consisting of one or more satellites, a UPF may be located on each satellite. Each satellite and each UPF may be identified by a different satellite ID and a different UPF ID. Additionally, each satellite UPF may be connected to a different local server. Each local server may be identified by a different DN ID. Examples of the DN ID may include at least one of DNAI, DNN (Data Network Name), and S-NSSAI. Each satellite constellation may move in a certain direction over time. Additionally, the entire satellite constellation may move in a certain direction over time.

[0103] FIG. 4 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0104] The contents of Figures 1 to 3 may be referenced, and duplicate contents are omitted.

[0105] Referring to FIG. 4, satellite constellation configuration information can be transmitted, stored, and managed as follows:

[0106] 1. In step S430, AF (420) may provide information related to satellite constellation deployment to NEF (410). The information related to satellite constellation deployment may be composed of at least one of a satellite constellation ID and satellite constellation deployment information. The satellite constellation deployment information may include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship of each satellite, a connection order of each satellite, and information about the time when each satellite is available to connect to the core network (available time information of each satellite). In step S430, the Nnef_SatelliteConstellationDeployment_Create / Update / Delete request message may be used.

[0107] 2. In step S440, NEF (410) can check whether the request of AF (420) is approved and whether the provision of information related to the satellite constellation deployment is approved.

[0108] 3. In step S450, if it is confirmed that provision of the information is permitted in step 2, NEF (410) can provide the information received in step 1 to UDR (400). In step S450, the Nudr_DM_Create / Update / Delete request message can be used to provide the information.

[0109] 4. In step S460, UDR (400) may respond to the information received in step 3 to NEF (410). In step S460, the Nudr_DM_Create / Update / Delete response message may be used as the response.

[0110] 5. In step S470, NEF (410) may respond to AF (420) with the result of providing information according to the request in step 1 based on the response of UDR (400) received in step 4. In step S460, the Nnef_SatelliteConstellationDeployment_Create / Update / Delete response message may be used as the response.

[0111] FIG. 5 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0112] The contents of Figures 1 to 4 may be referenced, and duplicate contents are omitted.

[0113] Referring to FIG. 5, satellite constellation configuration information can be transmitted, stored, and managed as follows:

[0114] 1. In step S501, the SMF (500) may request a subscription to information related to satellite constellation deployment from the NEF (510). When requesting a subscription to information related to satellite constellation deployment from the NEF (510), the SMF (500) may provide a satellite constellation ID.

[0115] 2. In step S502, NEF (510) may retrieve (e.g., obtain) information related to the satellite constellation arrangement stored in UDR (520) in response to a request for subscription to information related to the satellite constellation arrangement of SMF (500) received in step 1. If NEF (510) receives a satellite constellation ID in step 1, NEF (510) may retrieve information related to the arrangement of the corresponding satellite constellation. If NEF (510) already stores information related to the satellite constellation arrangement, steps 2 and 3 may be omitted.

[0116] 3. In step S503, UDR (520) may provide information related to satellite constellation arrangement at the request of NEF (510) of step 2. The information related to satellite constellation arrangement may include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship of each satellite, a connection order of each satellite, and information about the time at which each satellite is available to connect to the core network (available time information of each satellite).

[0117] 4. In step S504, since NEF (510) has received a request for subscription to information related to satellite constellation arrangement from SMF (500) in step 1, if there is a change in the information related to satellite constellation arrangement for the satellite constellation received in step 3, NEF (510) may request UDR (520) to notify of the change or occurrence of the change.

[0118] 5. In step S505, NEF (510) can respond to the request of SMF (500) of step 1. In addition, it can transmit the information received in step 3.

[0119] 6. In step S506, changes may occur in information related to the satellite constellation deployment in UDR (520). For example, through the procedure described in FIG. 4, AF (420) may have requested an update and / or deletion of some or all of the deployment information for a specific satellite constellation.

[0120] 7. In step S507, if there is a change in part or all of the deployment information of a specific satellite group in step 6, the UDR (520) can notify the NEF (510) that requested the subscription of the information related to the satellite deployment. For example, since the NEF (510) requested the UDR (520) to subscribe in step 4, if there is a change in the information related to the satellite deployment corresponding to the satellite group ID, the UDR (520) can notify the NEF (510) of this. The information that the UDR (520) notifies the NEF (510) of can be all of the information related to the satellite deployment, or a changed part thereof.

[0121] 8. In step S508, if NEF (510) has received the notification of step 7 or has been notified from another network component (e.g., NF, UE) that there has been a change in information related to the satellite constellation, it can recognize the change in the information. If NEF (510) has been storing information related to the satellite constellation, it can perform operations such as creation, update, and deletion based on the change.

[0122] 9. In step S509, if there is a change in part or all of the configuration information of a specific satellite group in step 8, the NEF (510) can notify the SMF (500) that requested the subscription of the information related to the satellite configuration. For example, since the SMF (500) requested the NEF (510) to subscribe in step 1, if there is a change in the information related to the satellite configuration corresponding to the satellite group ID, the NEF (510) can notify the SMF (500) of the change in the information. The information that the NEF (510) notifies the SMF (500) of may be all of the information related to the satellite configuration, or a changed part thereof. The SMF (500) can determine whether establishment / modification / release of a PDU session or registration / deregistration of a UE is necessary based on the received change, and can initiate the necessary procedures.

[0123] 10. In step S510, SMF (500) can respond to the notification received from NEF (510) in step 9.

[0124] FIG. 6 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0125] The contents of Figures 1 to 5 may be referenced, and duplicate contents are omitted.

[0126] Referring to FIG. 6, satellite constellation configuration information can be transmitted, stored, and managed as follows:

[0127] 1. In step S601, the SMF (600) may request information related to satellite constellation deployment from the NEF (610). When requesting information related to satellite constellation deployment from the NEF (610), the SMF (600) may provide a satellite constellation ID.

[0128] 2. In step S602, NEF (610) can retrieve information related to satellite constellation arrangement stored in UDR (620) in response to a request for information related to satellite constellation arrangement of SMF (600) received in step 1. If NEF (610) receives a satellite constellation ID in step 1, NEF (610) can retrieve information related to the arrangement of the corresponding satellite constellation. If NEF (610) already stores information related to satellite constellation arrangement, steps 2 and 3 may be omitted.

[0129] 3. In step S603, UDR (620) may provide information related to satellite constellation arrangement at the request of NEF (610) of step 2. The information related to satellite constellation arrangement may include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship of each satellite, a connection order of each satellite, and information about the time at which each satellite is available to connect to the core network (available time information of each satellite).

[0130] 4. In step S604, NEF (610) may request information related to satellite constellation arrangement from AF (630) in response to the request for information related to satellite constellation arrangement of SMF received in step 1. If NEF (610) receives a satellite constellation ID in step 1, it may request information related to the arrangement of the corresponding satellite constellation. If NEF (610) already stores information related to satellite constellation arrangement, steps 4 and 5 may be omitted. If NEF (610) does not receive information related to satellite constellation arrangement from UDR (620) in step 3, it may perform step 4.

[0131] 5. In step S605, AF (630) may provide information related to satellite constellation arrangement at the request of NEF (610) of step 4. The information related to satellite constellation arrangement may include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship of each satellite, a connection order of each satellite, and information about the time at which each satellite is available to connect to the core network (available time information of each satellite).

[0132] 6. In step S606, NEF (610) can check whether the AF (630) is authorized to provide information related to satellite constellation deployment.

[0133] 7. In step S607, NEF (610) may provide the SMF (600) with the information received from UDR (620) in step 3 or the information received from AF (630) in step 5, which is confirmed to be authorized in step 6.

[0134] 8. In step S608, if NEF (610) is confirmed to be authorized in step 6, it can provide the information received in step 5 to UDR (620).

[0135] 9. In step S609, UDR (620) can respond to the information received in step 8.

[0136] FIG. 7 is a diagram illustrating a method for transmitting, storing, and managing satellite constellation arrangement information according to one embodiment of the present disclosure.

[0137] The contents of Figures 1 to 6 may be referenced, and duplicate contents are omitted.

[0138] Referring to Figure 7, satellite constellation configuration information can be transmitted, stored, and managed as follows:

[0139] 1. In step S701, the SMF (700) may request the NEF (710) to cancel a subscription to information related to satellite constellation deployment. The SMF (700) may provide a satellite constellation ID when requesting the NEF (710) to cancel a subscription to information related to satellite constellation deployment. The SMF (700) may request the NEF (710) to cancel a subscription, for example, when there are no PDU sessions remaining associated with the satellite constellation ID.

[0140] 2. In step S702, NEF (710) may respond to a request to cancel a subscription to information related to the satellite constellation arrangement of the SMF received in step 1. NEF (710) may delete the information, for example, if there is no other NF that requires the information related to the satellite constellation arrangement that was stored.

[0141] 3. In step S703, NEF (710) may request UDR (720) to cancel the subscription to information related to satellite constellation deployment from SMF (700) in step 1. NEF (710) may request UDR (720) to cancel the subscription to the information, for example, if there is no other NF that requires information related to the satellite constellation deployment.

[0142] FIGS. 8A to 8F are diagrams illustrating a method for managing a session in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more satellites, according to an embodiment of the present disclosure.

[0143] The contents of Figures 1 to 7 may be referenced, and duplicate contents are omitted.

[0144] Referring to FIGS. 8a to 8f, the following occurs:

[0145] 1. In step S801, the UE (800) can send a PDU Session Establishment Request to the AMF (820).

[0146] 2. In step S802, AMF (820) can select SMF (840).

[0147] 3. In step S803, AMF (820) can determine the satellite constellation ID based on the ID (e.g., Global RAN Node ID) of the RAN (810) connected to the UE (800).

[0148] 4. In step S804, the AMF (820) may transmit a PDU Session Establishment Request to the SMF (840). In the PDU Session Establishment Request, the AMF (820) may transmit a satellite constellation ID to the SMF (840). In step 3, if the AMF (820) can determine a satellite ID that can be connected to the RAN (810) at the current time based on the RAN ID, the AMF (820) may transmit the satellite ID to the SMF (840).

[0149] 5. In step S805, the SMF (840) can check whether there is subscriber information for session management associated with the satellite constellation ID received in step 4 from the UDM (860). The subscriber information for session management associated with the satellite constellation ID may include DNN and / or S-NSSAI information associated with the satellite constellation ID.

[0150] 6. In step S806, SMF (840) can respond to the request of AMF (820) of step 4.

[0151] 7. In step S807, a licensing / authorization procedure for a PDU session may be performed.

[0152] 8. SMF (840) can establish a session management policy association.

[0153] 8a. Specifically, in step S808-1, the SMF (840) can select the PCF (850).

[0154] 8b. In step S808-2, SMF (840) establishes a session policy association with PCF (850) and can receive session management policy information from PCF (850).

[0155] 9. SMF (840) can select UPF (830).

[0156] 9a. Specifically, in step S809-1, the SMF (840) can obtain satellite constellation deployment information corresponding to the satellite constellation ID received in step 4. For example, based on the procedures of FIGS. 4 to 7, the SMF (840) can receive satellite constellation deployment information from the NEF (not shown). The information related to the satellite constellation deployment can include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship of each satellite, a connection order of each satellite, and information about the time at which each satellite is available to connect to the core network (available time information of each satellite).

[0157] 9b. In step S809-2, the SMF (840) may select the UPF (930) based on the satellite constellation arrangement information acquired in step 9a. The SMF (840) may determine the ID of at least one satellite (s) that can be connected to the SMF (840) at the current time based on the satellite constellation arrangement information, and may determine the ID of the DN (e.g., DNAI, DNN, S-NSSAI) that can be connected to the current time and / or the ID of the satellite that can be connected to the RAN at the current time based on the ID of the at least one satellite (s). Based on this, the ID of the UPF (930) corresponding to each satellite may be identified. In addition, the SMF (840) may identify the connection relationship and / or order of the satellite (s) that can be connected to the SMF (840) at the current time based on the satellite constellation arrangement information. Based on the above identification, SMF (840) can determine each UPF(s) as PSA UPF, I-UPF(s).

[0158] 10. SMF (840) can perform N4 Session Establishment and / or Modification procedures with UPF (830)(s).

[0159] 10a. Specifically, in step S810-1, the SMF (840) may provide the UPF (830) with at least one of information related to the time required for insertion / removal / change of the UPF (830), a list of UPF (830)(s) corresponding to satellites constituting the satellite constellation, and N3 and / or N9 Tunnel Information of the UPF (830)(s) corresponding to satellites constituting the satellite constellation.

[0160] 10a-1. The time information required for the above UPF insertion / removal / change may be information that can be determined based on the information regarding the time at which the satellites in step 9a are available for connection to the core network (available time information of each satellite). For example, it may be the time required for a satellite to enter and become connected, or for a satellite to move away and become unconnected (available time duration).

[0161] 10a-2. The list of UPFs (830)(s) corresponding to the satellites constituting the above satellite constellation may include information on all or some of the satellites constituting the satellite constellation (for example, it may include only the satellites that are connectable at the current time determined in step 9b above) and the UPFs corresponding to each, connection information between satellites, and / or the connection order between satellites.

[0162] 10a-3. The N3 and / or N9 Tunnel Information of the UPF (830)(s) corresponding to the satellites constituting the above satellite constellation may correspond to N9 UL CN Tunnel Info and N9 DL CN Tunnel Info in the case of PSA UPF, I-UPF (I-UPF other than N3 terminating point), and in the case of I-UPF corresponding to N3 terminating point among I-UPFs, N3 CN Tunnel Info may correspond instead of N9 UL CN Tunnel Info. The SMF (840) may provide the Tunnel Info allocated through UPF insertion to the UPF (830) of the previous order using the N4 Modification Request message. In addition, if the SMF (840) has already stored the Tunnel Info due to step 10c, it may provide the Tunnel Info to the UPF (830). For example, if the satellite has orbited the entire constellation of satellites more than once and returned, the SMF (840) may already store the Tunnel Info of the UPF (830) corresponding to the satellite.

[0163] 10b. In step S810-2, the UPF (830) may provide the SMF (840) with at least one of information related to the time required for insertion / removal / change of the UPF (830), a list of UPF (830) corresponding to satellites constituting the satellite constellation, and N3 and / or N9 Tunnel Information of the UPF (830) corresponding to satellites constituting the satellite constellation.

[0164] 10b-1. It may be the same value as 10a-1, or it may be a value modified by taking into account the time required for UPF (830) insertion / removal / change and Tunnel Information determination in general.

[0165] 10b-2. It may be the same value as 10a-2, or it may be a value with all or part of the UPF information and / or satellite connection / order information modified.

[0166] 10b-3. It may be a value provided by SMF (840) in 10a-3, a value newly assigned by UPF (830) because SMF (840) did not provide it, or a value provided by SMF (840) but newly assigned by UPF (830).

[0167] 10c. In step S810-3, the SMF (840) can store the N3 / N9 Tunnel Info of each UPF (830) allocated through the above 10a, 10b procedures so that it can be reused in future UPF (830) insertion / removal / change procedures.

[0168] 11. SMF (840) can transmit information necessary to establish a user plane path to AMF (820).

[0169] 11a. In step S811-1, the SMF (840) may provide the AMF (820) with at least one of the time-related information required for insertion / removal / change of the UPF (830) and the N3 CN Tunnel Information of the UPF (830)(s) corresponding to the satellites constituting the satellite constellation. The N3 CN Tunnel Information may be the N3 CN Tunnel Information of the UPF (830) corresponding to the N3 terminating point at the current time. In addition, as the satellite moves, a list of the N3 Cn Tunnel Information of the UPFs (830) that become the N3 terminating points after the current time may be included in order.

[0170] 11b. In step S811-2, AMF (820) can respond that it has received the message of 11a above.

[0171] 12. In step S812, AMF (820) can transmit the message of 11a to RAN (810).

[0172] 13. RAN (810) can allocate N3 AN Tunnel Information.

[0173] 13a. In step S813-1, RAN (810) may allocate N3 AN Tunnel Information(s) based on the information included in the above 12 messages.

[0174] 13b. In step S813-2, if the RAN (810) receives a list of N3 Cn Tunnel Information of UPFs (830) that will become N3 terminating points after the current time in the above-mentioned 12 message, including information related to the time required for insertion / removal / change of UPF (830), and / or as the satellite moves, the RAN (810) may start a timer to prepare for insertion / removal / change of UPF (830). For example, if there is no N3 CN Tunnel Information provided from the SMF (840) when the timer expires, the RAN (810) may recognize that the current satellite constellation is still being used for a PDU session.

[0175] 14. In step S814, a PDU Session Establishment Accept message is transmitted to the UE (800), and resources can be set up between the UE (800) and the RAN (810).

[0176] 15. In step S815, the RAN (810) can transmit the N3 AN Tunnel Info determined in step 13a to the AMF (820). From this time (e.g., after the N3 AN Tunnel Info is transmitted), uplink data can be transmitted from the UE (800) to the RAN (810).

[0177] 16. In step S816, AMF (820) can transmit the N3 AN Tunnel Info received in step 15 to SMF (840).

[0178] 17. SMF (840) can store information so that it can be reused in future UPF (830) insertion / removal / change procedures.

[0179] 17a. Specifically, in step S817-1, the SMF (840) can store the N3 AN Tunnel Info of the RAN (810) received in step 16.

[0180] 17b. In step S817-2, the SMF (840) may start a timer so that a UPF (830) reselection procedure can be performed based on the time (available time duration) required for the satellite to enter and become connected or for the satellite to move away and become unconnectable when the user plane path through the UPF (830)(s) of the above 8 is completed. For example, when the timer has expired, the SMF (840) may determine an I-UPF that is newly added as an N3 terminating point, an I-UPF that is changed to an I-UPF that is not an N3 terminating point, an I-UPF that is newly become a PSA UPF, and a PSA UPF that is removed from the user plane based on the information related to the satellite constellation arrangement described in the above 9a and 10a and / or the information on the UPF (830) selected in the procedures up to 17b, and may initiate a procedure for inserting / removing / changing each of them.

[0181] 18. SMF (840) can provide N3 AN Tunnel Info to UPF (830).

[0182] 18a. In step S818-1, SMF (840) can transmit the N3 AN Tunnel Info received in step 16 to UPF (830).

[0183] 18b. In step S818-2, UPF (830) can respond to step 18a.

[0184] 18c. In step S818-3, the UPF (830) may start a timer to prepare for insertion / removal / change of the UPF (830) based on the information received in step 10a. For example, when the timer expires, the UPF (830) may perform a procedure to release the N3 CN Tunnel and initiate the N9 UL CN Tunnel to change to an I-UPF other than the N3 terminating point, release the N9 UL Tunnel to remove it from the user plane, release the N9 DL CN Tunnel to change from an I-UPF to a PSA UPF, or initiate the N3 CN Tunnel to insert it into a new N3 terminating point. From this time (e.g., when the procedure to insert it into a new N3 terminating point is performed), the UPF (830) may transmit downlink data toward the UE.

[0185] 19. In step S819, SMF (840) may respond to step 16. For example, SMF (840) may transmit a response message to AMF (820).

[0186] 20. In step S820, SMF (840) can notify AMF (820) of the SM Context status of the PDU session.

[0187] 21. In step S821, an IPv6 address setting procedure can be performed from SMF (840) to UE (800).

[0188] 22. In step S822, an SM policy modification procedure may be performed between the SMF (840) and the PCF (850).

[0189] FIG. 9 is a diagram illustrating a method for managing a satellite ID, a satellite constellation ID, and an NF ID in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more satellites, according to one embodiment of the present disclosure.

[0190] The contents of Figs. 1 to 8e may be referenced, and duplicate contents are omitted.

[0191] According to one embodiment of the present disclosure, FIG. 9 may correspond to a method of performing an N4 Node level procedure between an SMF and a UPF in advance so that the SMF can determine a UPF ID corresponding to a satellite ID in 9b of FIGS. 8a to 8f.

[0192] Referring to Figure 9, the following is shown:

[0193] 1. In step S920, the SMF (900) may request the UPF (910) to set up an N4 association. The request may include at least one of a response request for whether the UPF (910) supports a satellite constellation, a response request for the ID of the satellite constellation supported by the UPF (910), an indicator for whether the SMF (900) supports a satellite constellation, and an ID of the satellite constellation supported by the SMF (900).

[0194] 2. UPF (910) can respond to the N4 association setup request to SMF (900). If UPF (910) supports a satellite constellation, it can provide the SMF (900) with a satellite ID and / or a satellite constellation ID corresponding to UPF (910).

[0195] FIG. 10 is a diagram illustrating a method for managing a satellite ID, a satellite constellation ID, and an NF ID in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more satellites, according to one embodiment of the present disclosure.

[0196] The contents of Figures 1 to 9 may be referenced, and duplicate contents are omitted.

[0197] According to one embodiment of the present disclosure, FIG. 10 may correspond to a method of performing an N4 Node level procedure between an SMF and a UPF in advance so that the SMF can determine a UPF ID corresponding to a satellite ID in 9b of FIGS. 8a to 8f.

[0198] Referring to Figure 10, the following is shown:

[0199] 1. In step S1020, UPF (1010) may request N4 association setup from SMF (1000). The request may include a satellite ID and / or satellite constellation ID corresponding to UPF (1010).

[0200] 2. In step S1030, the SMF (1000) may respond to the N4 association setup request to the UPF (1010). If the SMF (1000) supports a satellite constellation, it may provide an indication to the UPF (1010) as to whether the SMF (1000) supports the satellite constellation.

[0201] FIG. 11 is a diagram illustrating the structure of a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more mobile satellites, according to one embodiment of the present disclosure, and changes in the structure over time.

[0202] The contents of Figures 1 to 10 may be referenced, and duplicate contents are omitted.

[0203] According to one embodiment of the present disclosure, FIG. 11 illustrates a satellite constellation 5G system structure at time T0 and a satellite constellation 5G system structure at time T1 when each mobile satellite has moved.

[0204] Looking at the structure at time T0, the satellite UPF that can connect to the RAN at the current time may correspond to UPF#2 (satellite#2). Additionally, the local server that can connect to the SMF at the current time may be the local server connected to UPF#5 (satellite#5). In this situation, the following PDU session management procedure may be performed to provide the terminal with a user plane that connects to the local server via the RAN, UPF#2, UPF#3, UPF#4, and UPF#5:

[0205] 1. RAN can provide AMF with RAN ID (e.g. Global RAN Node ID).

[0206] 2. Based on the RAN ID, the AMF can determine the satellite constellation that can be connected to the RAN and provide the SMF with at least one of the satellite constellation ID and the satellite ID that can be connected to the RAN (e.g., satellite#2).

[0207] 3. Based on the satellite constellation ID and / or satellite ID, the SMF may receive information related to the satellite constellation's satellite configuration through the NEF. The NEF may be retrieved from information stored in the UDR or may be requested from the AF. The information related to the satellite constellation configuration may include at least one of the following: a list of the IDs of each satellite constituting the satellite constellation, the connection relationship between each satellite, the connection order of each satellite, and information regarding the time when each satellite is available to connect to the core network (available time information of each satellite).

[0208] 4. Based on the above satellite constellation ID, satellite ID, and / or satellite constellation configuration information, the SMF can determine the satellite ID, data network ID (e.g., DNAI), and / or the time required for a satellite to enter and become connectable or for a satellite to move away and become unconnectable (available time duration) of the satellite(s) that can be connected at the current time. For example:

[0209] 4a. Based on the above satellite constellation arrangement information, SMF can determine that the satellites that can be connected at the current time include satellite#2, satellite#3, satellite4, and satellite#5, in that order.

[0210] 4b. The SMF can determine the DN ID (e.g., DNAI) of the most suitable local server that can be connected to the above satellites (satellite 2 to satellite #5). For example, the SMF can determine the local server that can be connected to satellite #5 among the above satellites as the most suitable local server.

[0211] 4c. Additionally, the SMF can determine the most suitable satellite (e.g., satellite #2) among the satellites (satellite #2 to satellite #5) that can currently connect to the RAN. The SMF may have received the satellite ID (e.g., satellite #2) that can connect to the RAN from the AMF in 2 above.

[0212] 4d. Based on the above satellite constellation arrangement information, the SMF can determine the next satellite(s) that can be connected when the above satellites (satellite#2 to satellite#5) move. For example, it can be determined that the satellites that will enter after satellite#2 will be satellite#1, satellite#N, satellite#N-1, etc.

[0213] 4e. Based on the satellite configuration information, the SMF can determine the time required for a satellite to enter and establish a connection, or for a satellite to move away and become unreachable (available time duration). Based on the available time duration (deltaT), the timing for performing the I-UPF insertion and removal procedures can be determined.

[0214] 4f. The local server can be identified by its DNAI, which can be connected at the current time, and satellite#5 can be identified by the satellite ID to which the local server is connected.

[0215] 4g. Additionally, SMF can determine that the satellites that can be connected at the current time include satellite#2, satellite#3, satellite#4, and satellite#5, in that order.

[0216] 5. The SMF may select and determine UPF(s) for the user plane configuring the PDU session of the UE based on the satellite ID, data network ID (e.g., DNAI), and / or the time required for the satellite to enter and become connectable or to move away and become unconnectable (available time duration) of the satellite(s) of the above 4. For example, UPF#2, UPF#3, UPF#4, and UPF#5 corresponding to satellite#2, satellite#3, satellite#4, and satellite#5 may be selected. In addition, UPF#5 may be determined as PSA UPF, UPF#4, UPF#3, and UPF#2 may be determined as I-UPF, UPF#2 may be determined as N3 terminating point, and UPF#5 may be determined as N6 terminating point. Accordingly, the SMF may request allocation of N3 CN Tunnel, N3 UL CN Tunnel, and N9 DL CN Tunnel to each UPF. Additionally, it can request RAN to allocate N3 AN Tunnel.

[0217] 6. SMF may start a timer so that when the user plane path through the UPF(s) of the above 5 is completed, a UPF reselection procedure can be performed based on the time (available time duration) required for the satellite to enter and become connected or for the satellite to move away and become unconnectable.

[0218] Looking at the structure at time T1, the satellite UPF that can connect to the RAN at the current time may correspond to UPF#1 (satellite#1). Additionally, the local server that can connect to the SMF at the current time may be the local server connected to UPF#4 (satellite#4). In this situation, the following PDU session management procedure may be performed to provide the terminal with a user plane that connects to the local server via the RAN, UPF#2, UPF#3, UPF#4, and UPF#5:

[0219] 7. If the timer that allows the UPF reselection procedure of 6 above to be performed has expired, the SMF may re-verify the satellite ID and data network ID of the satellite(s) that can be connected at the current time based on the satellite constellation ID, satellite ID, and / or the satellite constellation arrangement-related information. The SMF may re-verify the satellite ID and data network ID of the satellite(s) that can be connected at the current time based on the satellite ID(s) determined in 4 above, for example, the satellite ID(s) determined in 4c, 4d, and 4g and their order. For example, the most suitable satellite (e.g., satellite#1) that can be currently connected to the RAN may be determined based on 4c and 4d, and the most suitable local server (e.g., DN that can be connected to satellite#4) that can be currently connected to the SMF may be determined based on 4d and 4g.

[0220] 8. Based on the above 7, the SMF can reselect and determine the UPF(s) for the user plane configuring the UE's PDU session. For example, UPF#1 corresponding to satellite#1 can be inserted as the I-UPF corresponding to the new N3 terminating point, UPF#2 can be changed to the I-UPF connected to N9, UPF#4 can be changed to a new PSA UPF, and UPF#5 can be removed from the user plane. Accordingly, the SMF can request UPF#1 to allocate the N3 CN Tunnel. In addition, the SMF can request UPF#5 to release the N9 Tunnel. The SMF can request each UPF to allocate the N3 CN Tunnel, the N3 UL CN Tunnel, and the N9 DL CN Tunnel. In addition, the SMF can request the RAN to allocate the N3 AN Tunnel.

[0221] 9. The SMF may start a timer so that when the user plane path through the UPF(s) of the above 8 is completed, a UPF reselection procedure can be performed based on the time (available time duration) required for the satellite to enter and become connected or for the satellite to move away and become unconnectable.

[0222] FIGS. 12A to 12C are diagrams illustrating a method for managing a user plane path in a 5G system where a 5G NF is located in a satellite constellation network composed of one or more mobile satellites, according to one embodiment of the present disclosure.

[0223] The contents of Figures 1 to 11 may be referenced, and duplicate contents are omitted.

[0224] According to one embodiment of the present disclosure, FIGS. 12A to 12C illustrate a PDU session management procedure based on the description (1 to 6 of FIG. 11) of the satellite constellation 5G system structure at time T0 of FIG. 11. In addition, FIGS. 12A to 12C illustrate in more detail the procedure of steps 9 to 18 of FIGS. 8A to 8F.

[0225] 1. In step S1201, SMF (1220) can obtain satellite constellation deployment information. For example, based on the procedures of FIGS. 4 to 7, SMF (1220) can receive satellite constellation deployment information from NEF (not shown). The information related to the satellite constellation deployment can include at least one of a list of IDs of each satellite constituting the satellite constellation, a connection relationship between each satellite, a connection order of each satellite, and information about the time at which each satellite is available to connect to the core network (available time information of each satellite).

[0226] 2. In step S1202, the SMF (1220) may select the UPF (1230) based on the acquired satellite constellation arrangement information. For example, the SMF (1220) may select UPF#2, UPF#3, UPF#4, and UPF#5 corresponding to satellite#2, satellite#3, satellite#4, and satellite#5. In addition, UPF#5 may be determined as a new PSA UPF, UPF#4 as a new UPF at the last, UPF#3 as a new I-UPF in the middle, UPF#2 as a new I-UPF at the first, UPF#2 as the N3 terminating point, and UPF#5 as the N6 terminating point.

[0227] 3. In step S1203, SMF (1220) may send an N4 Session Establishment request to UPF#5 (1250). This request may include at least one of information related to the time required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites forming a satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites forming a satellite constellation.

[0228] 4. In step S1204, UPF#5 (1250) may send an N4 Session Establishment response to SMF (1220). This response may include N9 UL CN Tunnel Info of UPF#5 (PSA UPF).

[0229] 5. In step S1205, SMF (1220) may send an N4 Session Establishment request to UPF#4 (1240). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of PSA UPF received from UPF#5 in step 4.

[0230] 6. In step S1206, UPF#4 (1240) may send an N4 Session Establishment response to SMF (1220). The response may include N9 DL CN Tunnel Info and N9 UL CN Tunnel Info of UPF#4 (the last I-UPF) (1240).

[0231] 7. In step S1207, SMF (1220) may send an N4 Session Modification request to UPF#5 (1250). The request may include the N9 DL CN Tunnel Info of the last I-UPF received from UPF#4 (1240) in step 6.

[0232] 8. In step S1208, UPF#5 (1250) may send an N4 Session Modification response to SMF (1220). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#5 (1250) toward UPF#4 (1240).

[0233] 9. In step S1209, SMF (1220) may send an N4 Session Establishment request to UPF#3 (1230). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of the last UPF received from UPF#4 (1240) in step 6.

[0234] 10. In step S1210, UPF#3 (1230) may send an N4 Session Establishment response to SMF (1220). The response may include N9 DL CN Tunnel Info and N9 UL CN Tunnel Info of UPF#3 (the middle I-UPF).

[0235] 11. In step S1211, SMF (1220) may send an N4 Session Modification request to UPF#4 (1240). The request may include N9 DL CN Tunnel Info of the middle I-UPF received from UPF#3 (1230) in step 10.

[0236] 12. In step S1212, UPF#4 (1240) may send an N4 Session Modification response to SMF (1220). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#4 (1240) toward UPF#3 (1230).

[0237] 13. In step S1213, SMF (1220) may send an N4 Session Establishment request to UPF#2 (1210). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of the middle UPF received from UPF#3 in step 10.

[0238] 14. In step S1214, UPF#2 (1210) may send an N4 Session Establishment response to SMF (1220). The response may include N9 DL CN Tunnel Info and N3 CN Tunnel Info of UPF#2 (the first I-UPF).

[0239] 15. In step S1215, SMF (1220) may send an N4 Session Modification request to UPF#3 (1230). The request may include the N9 DL CN Tunnel Info of the first I-UPF received from UPF#2 in step 14.

[0240] 16. In step S1216, UPF#3 (1230) may send an N4 Session Modification response to SMF (1220). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#3 (1230) toward UPF#2 (1210).

[0241] 17. In step S1217, the SMF (1220) may provide the RAN (1200) with at least one of time-related information (e.g., deltaT) required for UPF insertion / removal / change, and N3 CN Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation through the AMF (not shown). The N3 CN Tunnel Information may be the N3 CN Tunnel Information of the UPF corresponding to the N3 terminating point at the current time. In addition, as the satellite moves, a list of N3 CN Tunnel Information of UPFs that become N3 terminating points after the current time may be included in the transmitted information in order. The N3 CN Tunnel Information may include the N3 CN Tunnel Info of the first I-UPF received from UPF#2 (1210) in step 14. From this time (e.g., when the information is transmitted), uplink data may be transmitted from the UE toward the PSA UPF.

[0242] 18. In step S1218, RAN (1200) may provide N3 AN Tunnel Info to SMF (1220) via AMF (not shown).

[0243] 19. In step S1219, the SMF (1220) may start a timer so that a UPF reselection procedure can be performed based on the time required for the satellite to enter and become connected or for the satellite to move away and become unconnectable (available time duration).

[0244] 20. In step S1220, SMF (1220) may send an N4 Session Modification request to UPF#2 (1210). The request may include the N3 AN Tunnel Info received from RAN (1200) in step 18.

[0245] 21. In step S1221, UPF#2 (1210) may send an N4 Session Modification response to SMF (1220). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#2 (1210) toward the UE.

[0246] FIGS. 13A to 13E are diagrams illustrating a method for managing a user plane path in a 5G system in which a 5G NF is located in a satellite constellation network composed of one or more mobile satellites, according to one embodiment of the present disclosure.

[0247] The contents of Figs. 1 to 12c may be referenced, and duplicate contents are omitted.

[0248] According to one embodiment of the present disclosure, FIGS. 13a to 13e illustrate a PDU session management procedure based on the description (7 to 9 of FIG. 11) of the satellite constellation 5G system architecture at time T1 of FIG. 11. In addition, FIGS. 12a to 12c illustrate in more detail the procedure of steps 9 to 18 of FIGS. 8a to 8f.

[0249] 1. In step S1301, a timer that is set to allow the UPF reselection procedure to be performed in step 19 of FIGS. 12a to 12c described above in SMF (1330) may expire.

[0250] 2. In step S1302, the SMF (1330) may reselect the UPF (1320) based on the satellite constellation arrangement-related information. According to one embodiment of the present disclosure, UPF#1 corresponding to satellite#1 may be selected as the new I-UPF at the first, UPF#2 as the new I-UPF in the middle, UPF#3 as the new I-UPF at the last, and UPF#4 as the new PSA UPF. UPF#1 may be determined as the N3 terminating point, UPF#4 as the N6 terminating point, and UPF#5 may be removed.

[0251] 3. In step S1303, SMF (1330) may send an N4 Modification Establishment request to UPF#4. The request may include information related to the time required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites forming a satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and at least one of N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites forming a satellite constellation.

[0252] 4. In step S1304, UPF#4 (1350) may send an N4 Session Modification response to SMF (1330). The response may include N9 DL CN Tunnel Info and N9 UL CN Tunnel Info of UPF#4 (new PSA UPF) (1350).

[0253] 5. In step S1305, SMF (1330) may send an N4 Session Modification request to UPF#5 (1360). The request may include an indicator indicating that PSA UPF re-selection for a satellite constellation network is in progress, and N9 DL CN Tunnel Info of the new PSA UPF received from UPF#4 (1350) in step 4.

[0254] 6. In step S1306, UPF#5 (1360) can send an N4 Session Establishment response to the SMF. UPF#5 (1360) can recognize that it is a PSA UPF reselection for a satellite constellation network and can decide whether to forward downlink data to the new PSA UPF, and if it decides to forward, it can buffer the data. UPF#5 (1360) can set up an N9 tunnel to forward downlink data using the N9 DL CN Tunnel Info of the new PSA UPF.

[0255] 7. In step S1307, UPF#5 (1360) can forward the downlink data buffered to the forwarding tunnel set in step 6.

[0256] 8. In step S1308, SMF (1330) may send an N4 Session Modification request to UPF#3 (1340). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of new PSA UPF received from UPF#4 (1350) in step 4.

[0257] 9. In step S1309, UPF#3 (1340) may send an N4 Session Modification response to SMF (1330). The response may include N9 DL CN Tunnel Info and N9 UL CN Tunnel Info of UPF#3 (new last I-UPF).

[0258] 10. In step S1310, SMF (1330) may send an N4 Session Modification request to UPF#4 (1350). The request may include N9 DL CN Tunnel Info of the new last I-UPF received from UPF#3 in step 9.

[0259] 11. In step S1311, UPF#4 (1350) may send an N4 Session Modification response to SMF (1330). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#4 (1350) toward UPF#3 (1340).

[0260] 12. In step S1312, SMF (1330) may send an N4 Session Modification request to UPF#2 (1320). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of the new last I-UPF received from UPF#3 (1340) in step 9.

[0261] 13. In step S1313, UPF#2 (1320) may send an N4 Session Modification response to SMF (1330). The response may include N9 DL CN Tunnel Info and N3 CN Tunnel Info of UPF#2 (new middle I-UPF).

[0262] 14. In step S1314, SMF (1330) may send an N4 Session Modification request to UPF#3 (1340). The request may include N9 DL CN Tunnel Info of the new middle I-UPF received from UPF#2 in step 13.

[0263] 15. In step S1315, UPF#3 (1340) may send an N4 Session Modification response to SMF (1330). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#3 (1340) toward UPF#2 (1320).

[0264] 16. In step S1316, SMF (1330) may send an N4 Session Establishment request to UPF#1 (1310). The request may include at least one of time-related information required for UPF insertion / removal / change (e.g., deltaT), a list of UPF(s) corresponding to satellites constituting the satellite constellation (e.g., UPF#1, UPF#2, …, UPF#N), and N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation. The N3 and / or N9 Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation may include N9 UL CN Tunnel Info of the new middle I-UPF received from UPF#2 in step 13.

[0265] 17. In step S1317, UPF#1 (1310) may send an N4 Session Establishment response to SMF (1330). The response may include N9 DL CN Tunnel Info and N3 CN Tunnel Info of UPF#1 (new first I-UPF).

[0266] 18. In step S1318, SMF (1330) may send an N4 Session Modification request to UPF#2 (1320). The request may include N9 DL CN Tunnel Info of the new first I-UPF received from UPF#1 (1310) in step 17.

[0267] 19. In step S1319, UPF#2 (1320) may send an N4 Session Modification response to SMF (1330). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#2 (1320) toward UPF#1 (1310).

[0268] 20. In step S1320, the SMF (1330) may provide the RAN (1300) with at least one of time-related information (e.g., deltaT) required for UPF insertion / removal / change, and N3 CN Tunnel Information of UPF(s) corresponding to satellites constituting the satellite constellation through the AMF (not shown). The N3 CN Tunnel Information may be the N3 CN Tunnel Information of the UPF corresponding to the N3 terminating point at the current time. In addition, as the satellite moves, a list of N3 CN Tunnel Information of UPFs that become N3 terminating points after the current time may be included in the information in order. The N3 CN Tunnel Information may include the N3 CN Tunnel Info of the new first I-UPF received from UPF#1 (1310) in step 17. From this time (e.g., when the information is transmitted), uplink data may be transmitted from the UE toward the PSA UPF.

[0269] 21. In step S1321, RAN (1300) may provide N3 AN Tunnel Info to SMF (1330) via AMF (not shown).

[0270] 22. In step S1322, the SMF (1330) may start a timer so that a UPF reselection procedure can be performed based on the time required for the satellite to enter and become connected or for the satellite to move away and become unconnectable (available time duration).

[0271] 23. In step S1323, SMF (1330) may send an N4 Session Modification request to UPF#1 (1310). This request may include the N3 AN Tunnel Info received from RAN (1300) in step 21.

[0272] 24. In step S1324, UPF#1 (1310) may send an N4 Session Modification response to SMF (1330). From this time (e.g., when the response is transmitted), downlink data may be transmitted from UPF#1 (1310) toward the UE.

[0273] 25. In step S1325, SMF (1330) may send an N4 Session Modification request to UPF#4 (1350). The request may include a request to release the N9 tunnel for downlink data forwarding by releasing the N9 DL CN Tunnel Info of the new PSA UPF allocated for downlink data forwarding in step 4.

[0274] 26. In step S1326, UPF#4 (1350) can send an N4 Session Modification response to SMF (1330).

[0275] 27. In step S1327, SMF (1330) may send an N4 Session Release request to UPF#5 (1360).

[0276] 28. In step S1328, UPF#5 (1360) may send an N4 Session Release response to SMF (1330). For example, as a response to the N4 Session Release request, UPF#5 (1360) may send an N4 Session Release response to SMF (1330).

[0277] Meanwhile, FIG. 14 is a drawing illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0278] Referring to FIG. 14, the terminal may include a transceiver (1410), a control unit (1420), and a storage unit (1430). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0279] The transceiver (1410) can transmit and receive signals with other network entities. For example, the transceiver (1410) can transmit a session establishment request message to a core network entity.

[0280] The control unit (1420) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (1420) can control the signal flow between each block to perform operations according to the flowchart described above.

[0281] The storage unit (1430) can store at least one of the information transmitted and received through the transmission and reception unit (1410) and the information generated through the control unit (1420).

[0282] FIG. 15 is a diagram illustrating a network function entity according to an embodiment of the present disclosure. The network function entity of FIG. 15 may be any one of network entities such as SMF, UPF, NEF, UDR, and AF, according to an embodiment of the present disclosure.

[0283] Referring to FIG. 15, a network function entity may include a transceiver (1510), a control unit (1520), and a storage unit (1530). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0284] The transceiver (1510) can transmit and receive signals with other network entities. For example, in the case of SMF, the transceiver (1510) can transmit a request message including a satellite constellation ID.

[0285] The control unit (1520) can control the overall operation of the network function entity according to an embodiment proposed in the present invention. For example, the control unit (1520) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (1520) can control the transmission, storage, and / or management of satellite constellation information according to an embodiment of the present invention.

[0286] The storage unit (1530) can store at least one of the information transmitted and received through the transceiver unit (1510) and the information generated through the control unit (1520). In the specific embodiments of the present disclosure described above, the components included in the invention are expressed singularly or plurally according to the specific embodiments presented. However, the singular or plural expressions are selected to suit the presented situation for the convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular elements, or even components expressed in singular may be composed of plural elements.

[0287] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. In addition, other modified examples based on the technical idea of ​​the above embodiments can be implemented in various systems such as an FDD LTE system, a TDD LTE system, a 5G or NR system.

Claims

1. A method performed by a session management function (SMF) entity in a wireless communication system, A step of transmitting a request message requesting information related to a satellite constellation arrangement to a network exposure function (NEF) entity, wherein the request message includes a satellite constellation identifier (ID); and A method comprising: receiving information related to the satellite constellation arrangement from the NEF entity that has obtained information related to the satellite constellation arrangement based on the satellite constellation ID; 2. In paragraph 1, Information related to the above satellite constellation deployment, A method characterized by including at least one of a list of IDs of a plurality of satellites forming a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about a time when the plurality of satellites are available to connect to a core network (available time information).

3. In paragraph 1, A step of selecting at least one user plane function (UPF) entity based on information related to the received satellite constellation configuration; A step of transmitting a session formation request message to at least one of the selected UPF entities; and In response to the above session formation request message, the method further comprises the step of receiving a session formation response message; A method characterized in that the session formation request message includes at least one of time-related information required for insertion, removal, or modification of the at least one UPF entity, a list of UPF entities corresponding to satellites forming the satellite constellation, and tunnel information of UPF entities corresponding to satellites forming the satellite constellation.

4. In paragraph 1, A step of transmitting a message including at least one of information related to the time required for insertion, removal, or modification of a UPF entity and tunnel information of a plurality of UPFs corresponding to satellites forming a satellite constellation, to a radio access network (RAN) node via an access and mobility management function (AMF) entity; and A method further comprising: a step of executing a timer for performing a UPF entity reselection procedure based on information about the time at which the plurality of satellites are available to connect to the core network (available time information); 5. In paragraph 4, A step of reselecting a UPF based on the satellite constellation arrangement-related information when the timer for performing the above UPF entity reselection procedure has expired; A step of transmitting a session modification request message to at least one of the reselected UPF entities; and In response to the above session modification request message, the method further comprises the step of receiving a session modification response message; A method characterized in that the above session modification request message includes at least one of time-related information required for insertion, removal, or modification of the at least one UPF entity, a list of UPF entities corresponding to satellites forming the satellite constellation, and tunnel information of UPF entities corresponding to satellites forming the satellite constellation.

6. A method performed by a network exposure function (NEF) entity in a wireless communication system, A step of receiving a request message requesting information related to satellite constellation arrangement from a session management function (SMF) entity, wherein the request message includes a satellite constellation identifier (ID); A step of obtaining information related to the satellite constellation arrangement from a user data repository (UDR) entity based on the request message; and A step of transmitting information related to the satellite constellation arrangement to the above SMF entity; Information related to the above satellite constellation deployment, A method characterized by including at least one of a list of IDs of a plurality of satellites forming a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about a time when the plurality of satellites are available to connect to a core network (available time information).

7. In paragraph 6, A step of transmitting a request message requesting information related to the satellite constellation arrangement to an application function (AF) entity based on the request message; A step of receiving information related to the satellite constellation arrangement from the above AF entity; A step of verifying whether the above AF entity is authorized to provide information related to the deployment of the above satellite constellation; and A method characterized by comprising: a step of transmitting, to the SMF entity, information related to a satellite constellation received from the AF entity, if the AF entity is authorized to provide information related to the satellite constellation; 8. In a wireless communication system, in the session management function (SMF) entity, Transmitter and receiver; and Transmitting a request message requesting information related to satellite constellation arrangement through the transceiver as a network exposure function (NEF) entity, wherein the request message includes a satellite constellation identifier (ID); An SMF entity including a control unit that controls receiving, through the transceiver unit, information related to the satellite constellation arrangement from the NEF entity that has obtained information related to the satellite constellation arrangement based on the satellite constellation ID.

9. In paragraph 8, Information related to the above satellite constellation deployment, An SMF entity characterized by including at least one of a list of IDs of a plurality of satellites forming a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about the time at which the plurality of satellites are available for connection in a core network (available time information).

10. In paragraph 8, The above control unit, Based on the information related to the received satellite constellation configuration, at least one user plane function (UPF) entity is selected, Transmitting a session formation request message through the transceiver to at least one of the above-mentioned selected UPF entities, In response to the above session formation request message, control is provided to receive a session formation response message through the transceiver, An SMF entity characterized in that the session formation request message includes at least one of time-related information required for insertion, removal, or modification of the at least one UPF entity, a list of UPF entities corresponding to satellites forming the satellite constellation, and tunnel information of UPF entities corresponding to satellites forming the satellite constellation.

11. In paragraph 8, The above control unit, Transmitting a message including at least one of information related to the time required for insertion, removal, or modification of a UPF entity and tunnel information of a plurality of UPFs corresponding to satellites forming a satellite constellation, to a radio access network (RAN) node via an access and mobility management function (AMF) entity, through the transceiver, An SMF entity characterized in that it controls to execute a timer for performing a UPF entity reselection procedure based on information about the time at which the plurality of satellites are available to connect to the core network (available time information).

12. In paragraph 11, The above control unit, When the timer for performing the above UPF entity reselection procedure expires, the UPF is reselected based on the satellite constellation arrangement-related information, Transmitting a session modification request message through the transceiver to at least one of the above-described re-selected UPF entities, In response to the above session modification request message, control is provided to receive a session modification response message through the above transceiver, An SMF entity, characterized in that the session modification request message includes at least one of time-related information required for insertion, removal, or modification of the at least one UPF entity, a list of UPF entities corresponding to satellites forming the satellite constellation, and tunnel information of UPF entities corresponding to satellites forming the satellite constellation.

13. In a wireless communication system, in a network exposure function (NEF) entity, Transmitter and receiver; Receive a request message requesting information related to satellite constellation arrangement from a session management function (SMF) entity through the transceiver, wherein the request message includes a satellite constellation identifier (ID); Based on the above request message, information related to the satellite constellation is obtained from a user data repository (UDR) entity, Controlling the above SMF entity to transmit information related to the satellite constellation arrangement through the above transceiver, Information related to the above satellite constellation deployment, An NEF entity characterized by including at least one of a list of IDs of a plurality of satellites forming a satellite constellation, a connection relationship between the plurality of satellites, a connection order of the plurality of satellites, and information about the time at which the plurality of satellites are available for connection in a core network (available time information).

14. In paragraph 13, The above control unit, Based on the above request message, a request message requesting information related to the satellite constellation arrangement is transmitted to the application function (AF) entity through the transceiver, From the above AF entity, information related to the satellite constellation arrangement is received through the transceiver, Verify whether the above AF entity is authorized to provide information related to the deployment of the above satellite constellation, An NEF entity characterized in that, when the AF entity is permitted to provide information related to the satellite constellation arrangement, the SMF entity controls to transmit, through the transceiver, information related to the satellite constellation arrangement received from the AF entity.

Images