Method and apparatus for network registration of mobile base station

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method for network registration of a mobile base station by an access and mobility management function (AMF) in a wireless communication system is provided. The method may comprise the steps of: receiving, from a base station, a registration request message for a terminal, wherein the registration request message includes requested network slice selection assistance information (NSSAI), and the requested NSSAI includes at least one piece of single-NSSAI (S-NSSAI); and transmitting a registration rejection message for the terminal to the base station when the at least one piece of S-NSSAI supports mobile gNB with wireless access backhaul (MWAB) and the base station is an integrated access and backhaul (IAB)-node, a mobile base station relay (MBSR)-node, or an MWAB-node.

Description

Method and device for network registration of a mobile base station

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present disclosure relates to a method and device for a mobile base station to register with a wireless network.

[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 (THz) band (for example, 3 THz 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 meet 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 could serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing this technology.

[0008] In a wireless communication system, when users suddenly flock to a specific area and network service provision is not smooth, mobile base stations can be used to temporarily provide insufficient wireless resources to provide smooth network service to users.

[0009] To provide network services to terminals, mobile base stations must also utilize network services. Therefore, they must register with their home network. This registration process requires a different network registration procedure than that of regular terminals.

[0010] The present disclosure provides methods for a procedure for a mobile base station to register with a network and devices for performing the same.

[0011] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0012] According to one embodiment of the present disclosure, in a wireless communication system, a method for network registration of a mobile base station by an Access and Mobility Management Function (AMF) is provided. The method may include the steps of: receiving a registration request message for a terminal from a base station, wherein the registration request message includes requested network slice selection assistance information (NSSAI), and the requested NSSAI includes at least one single-NSSAI (S-NSSAI); and, if the at least one S-NSSAI supports Mobile gNB with Wireless Access Backhaul (MWAB) and the base station is an Integrated Access and Backhaul (IAB) node, a Mobile Base Station Relay (MBSR) node, or an MWAB node, transmitting a registration rejection message for the terminal to the base station.

[0013] According to one embodiment of the present disclosure, in a wireless communication system, a method for network registration of a mobile base station by a base station is provided. The method may include the steps of: receiving, from a terminal, a first registration request message including a requested network slice selection assistance information (NSSAI), wherein the requested NSSAI includes at least one single-NSSAI (S-NSSAI); and, if the at least one S-NSSAI supports MWAB (Mobile gNB with Wireless Access Backhaul), transmitting a second registration request message to the terminal to an AMF supporting the MWAB.

[0014] According to one embodiment of the present disclosure, in a wireless communication system, an Access and Mobility Management Function (AMF) for network registration of a mobile base station is provided. The AMF may include a transceiver and at least one processor connected to the transceiver. The at least one processor may be configured to receive a registration request message for a terminal from a base station, wherein the registration request message includes a requested network slice selection assistance information (NSSAI), and the requested NSSAI includes at least one single-NSSAI (S-NSSAI); and when the at least one S-NSSAI supports MWAB (Mobile gNB with Wireless Access Backhaul) and the base station is an IAB (Integrated Access and Backhaul) node, an MBSR (Mobile Base Station Relay) node, or an MWAB node, transmit a registration rejection message for the terminal to the base station.

[0015] One embodiment of the present invention provides a device and method capable of effectively providing a service in a wireless communication system.

[0016] The present disclosure provides methods for a procedure for a mobile base station to register with a network and devices for performing the same.

[0017] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0018] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 2 illustrates the deployment of a mobile base station according to one embodiment of the present disclosure.

[0020] FIG. 3 illustrates the structure of a mobile base station according to one embodiment of the present disclosure.

[0021] FIG. 4 illustrates a protocol stack for an N2 interface according to one embodiment of the present disclosure.

[0022] FIG. 5 illustrates a protocol stack for an N3 interface according to one embodiment of the present disclosure.

[0023] FIG. 6 illustrates the structure of an IAB node according to one embodiment of the present disclosure.

[0024] FIG. 7 illustrates a network environment in which IAB-nodes, MWAB-nodes, and MBSR-nodes coexist according to one embodiment of the present disclosure.

[0025] FIG. 8a, FIG. 8b, and FIG. 8c illustrate a network registration procedure of a terminal according to one embodiment of the present disclosure.

[0026] Figure 9 illustrates the configuration of a terminal according to one embodiment of the present disclosure.

[0027] FIG. 10 illustrates a configuration of a network entity according to one embodiment of the present disclosure.

[0028] Hereinafter, preferred embodiments of the present invention 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, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

[0029] In describing the embodiments herein, 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 invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0030] 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.

[0031] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together 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 only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0032] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0033] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, in the following, LTE (long-term evolution), LTE-A (LTE-advanced) or 5G (5 th Although the present disclosure may be described as an example of a 5G (new radio (NR)) system, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include the 5G (new radio (NR)) mobile communication technology developed after LTE-A, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0034] 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).

[0035] 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.

[0036] Here, the term '~ unit' used in the present embodiments 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 reproduce 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, properties, 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 reproduce one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0037] Wireless communication systems have evolved from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0038] As a representative example of a broadband wireless communication system, the LTE system uses the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink. The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above-described multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources to be transmitted, including data or control information, so that they do not overlap with each other (i.e., so that orthogonality is established).

[0039] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC).

[0040] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0041] At the same time, massive Machine Type Communications (mMTC) is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting a large number of terminals within a cell, improving terminal coverage, extending battery life, and reducing terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0042] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must provide extremely low latency and high reliability. For example, services supporting URLLC must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide a shorter transmission time interval (TTI) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0043] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0044] According to various embodiments of the present disclosure, phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used merely to distinguish the corresponding element from other corresponding elements and do not limit the corresponding elements in any other respect (e.g., importance or order).

[0045] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0046] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs (network functions) in a 5G core network (CN), and since a related description may refer to a standard specification (e.g., TS 23.501), a detailed description will be omitted.

[0047] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0048] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0049] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure. More specifically, FIG. 1 illustrates an example of the configuration of a 5G system. Referring to FIG. 1, a 5G network may include at least one of the following network entities (NEs) or network functions (NFs).

[0050] According to one embodiment, the (R)AN ((Radio) Access Network) is an entity that performs radio resource allocation of a terminal, and may include at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0051] According to one embodiment, the terminal may include a User Equipment (UE), a Next Generation UE (NG UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, an Internet of Things (IoT) device, or a multimedia system capable of performing a communication function.

[0052] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0053] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network can virtualize all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0054] According to one embodiment of the present disclosure, 5GC may include one or more NFs illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the NFs illustrated in FIG. 1.

[0055] In one embodiment, the Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0056] According to one embodiment, a Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a User Equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining tunnels between a User Plane Function (UPF) and a RAN required for this, selecting and controlling a User Plane (UPF), controlling traffic processing in the UPF, and controlling collection of charging data.

[0057] According to one embodiment, the Policy Control Function (PCF) may be a network function that applies a mobile communication operator's service policy, charging policy, and policy for PDU Session to a terminal.

[0058] In one embodiment, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting UEs, and managing subscription information.

[0059] In one embodiment, the Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Furthermore, NEF may provide the ability to provide information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0060] In one embodiment, the User Plane Function (UPF) may be a function that acts as a gateway to transmit user data (e.g., PDU) to the Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF may perform network functions such as serving as an anchor between Radio Access Technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report generation, and buffering.

[0061] According to one embodiment, the Network Repository Function (NRF) can perform the function of storing profiles of NFs and discovering NFs.

[0062] According to one embodiment, the Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0063] According to one embodiment, the Network Slice Selection Function (NSSF) may perform a function of selecting a Network Slice Instance provided to a terminal.

[0064] In one embodiment, the Network Data Analytics Function (NWDAF) can collect data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. In one embodiment, the collected data can be analyzed using a machine learning (ML) model, and the analyzed results can be provided back to the NFs to help each NF provide efficient network services.

[0065] In one embodiment, an Application Function (AF) can communicate with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. Depending on the deployment entity, an AF can be classified as an internal AF or an external AF. An internal AF deployed by a network operator can communicate directly with network function providers (NFs) within the network operator. An AF deployed by a third-party service provider (3rd-party service provider) may need to go through an NEF to communicate with NFs within the network operator.

[0066] According to one embodiment, the DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0067] According to one embodiment, the Network Slice Admission Control Function (NSACF) can limit the number of PDU sessions of registered terminals of each slice, thereby performing the function of managing resources.

[0068] According to one embodiment, the Network Slice-Specific Authentication and Authorization Function (NSSAAF) can create a slice authentication context for a terminal and perform slice-specific authentication and authorization procedures.

[0069] According to one embodiment, the Edge Application Server Discovery Function (EASDF) can create a domain name system (DNS) context for a PDU session and can perform a function of storing a UE IP (internet protocol) address, DNS message processing rules, etc. in the context.

[0070] In one embodiment, a Service Communication Proxy (SCP) can perform indirect communication functions such as service discovery, call response, etc.

[0071] In one embodiment, the terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such an IoT device may be referred to as an ambient IoT device (or Ambient IoT).

[0072] 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.

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

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

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

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

[0077] - N6: Reference point between UPF and DN

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

[0079] Additionally, in 3GPP systems, the 5G system architecture may include service-based interfaces such as the following examples.

[0080] - Nnssf: Service-based interface by NSSF

[0081] - Nnssaaf: Service-based interface by NSSAAF (Network Slice-Specific Authentication and Authorization Function)

[0082] - Nnef: Service-based interface by NEF

[0083] - Nausf: Service-based interface by AUSF

[0084] - Nnrf: Service-based interface by NRF

[0085] - Namf: Service-based interface by AMF

[0086] - Npcf: Service-based interface by PCF

[0087] - Nsmf: Service-based interface by SMF

[0088] - Nupf: Service-based interface by UPF

[0089] - Nudm: Service-based interface by UDM

[0090] - Naf: Service-based interface by AF

[0091] - Nasaf: Service-based interface by AUSF

[0092] - Neasdf: Service-based interface by EASDF (Edge Application Server Discovery Function)

[0093] - Nnwdaf: Service-based interface by NWDAF

[0094] According to various embodiments of the present disclosure, mobile communication service providers have proposed a method of providing network services to people within or within a short distance of a public transportation vehicle (e.g., bus, train, etc.) by installing mobile base stations on such vehicles. Mobile base stations can be temporarily installed in locations where crowds suddenly arise, providing network services to a large number of people. Furthermore, since the base stations move together with people traveling together, such as buses and trains, handovers do not occur, providing uninterrupted network services.

[0095] The present disclosure proposes a method for a mobile base station to register with its own home network in order to provide network services to a user.

[0096] FIG. 2 illustrates the deployment of a mobile base station according to one embodiment of the present disclosure.

[0097] Mobile gNBs with Wireless Access Backhaul (MWAB) can be installed on mobile vehicles, such as buses or trains. These mobile gNBs can provide network services to passengers onboard the vehicle or to those nearby.

[0098] Mobile base stations can communicate with the core network to communicate with the data network. Because they are mobile base stations, they can utilize wireless access backhaul to connect to the core network. Wireless access backhaul can utilize terrestrial network (TN) gNBs, such as ground-based base stations, or non-terrestrial network (NTN) gNBs, such as satellites.

[0099] FIG. 3 illustrates the structure of a mobile base station according to one embodiment of the present disclosure.

[0100] A mobile base station can be configured to include two components, an MWAB-gNB and an MWAB-UE. The MWAB-gNB can serve as a base station and provide wireless access to a terminal. The MWAB-gNB and the terminal can provide wireless access for network services to the terminal using an NR Uu interface. The MWAB-UE can register with the MWAB's HPLMN (Home PLMN) to use network services. The MWAB-UE's home network may be different from the home network of the terminal to which the mobile base station provides services. The MWAB-UE can establish a wireless network connection with its own HPLMN to enable the mobile base station to transmit and receive data over a data network. The MWAB-UE can register with the MWAB's HPLMN as a terminal. After registering with the network, it can create a PDU session to transmit and receive data over the data network. This PDU Session can be named BH PDU Session (Backhaul PDU Session) because MWAB-gNB will later use it as a wireless access backhaul.

[0101] The HPLMN of a mobile base station and the HPLMN of the terminal to which the mobile base station provides network services may be different. That is, a mobile base station may receive requests to provide network services to its customers from a PLMN different from its own HPLMN. Therefore, the MWAB-UE can use the BH PDU Session generated by the MWAB-UE to transmit and receive data with N2 / N3 or OAM between its own HPLMN and a PLMN different from its own. The MWAB-gNB can use the BH PDU Session generated by the MWAB-UE to establish N2 and N3 connections based on IP connectivity with the AMF and UPF of the terminal's HPLMN, respectively.

[0102] FIG. 4 illustrates a protocol stack for an N2 interface according to one embodiment of the present disclosure.

[0103] MWAB-gNB can use the PDU Session generated by MWAB-UE to create an N2 connection using the AMF of the terminal's HPLMN and the IP / SCTP-based NG-AP protocol. This is only an example and does not limit the use of other protocols.

[0104] FIG. 5 illustrates a protocol stack for an N3 interface according to one embodiment of the present disclosure.

[0105] MWAB-gNB can use the PDU Session generated by MWAB-UE to create an N3 connection using the terminal's HPLMN UPF and the IP / UPD-based GTP-U protocol. This is only an example and does not limit the use of other protocols.

[0106] FIG. 6 illustrates the structure of an IAB node according to one embodiment of the present disclosure.

[0107] The Integrated Access Backhaul (IAB) node is a relay node used to expand the wireless coverage of a base station. IAB nodes are broadly divided into the IAB-donor gNB and the IAB-node. The IAB-donor gNB can connect to the 5GC and provide the IAB-node with connectivity to the 5GC.

[0108] An IAB node can be configured to include two components: an IAB-UE and a gNB-DU. The IAB-UE can be connected to the IAB-donor gNB via NR Uu. Using this connection, the IAB-DU can connect to the IAB-donor-CU of the IAB-donor gNB to provide network services to the UE. The IAB-node can provide NR Uu wireless connectivity for 5GC connections to other IAB-nodes.

[0109] FIG. 7 illustrates a network environment in which IAB-nodes, MWAB-nodes, and MBSR-nodes coexist according to one embodiment of the present disclosure.

[0110] MBSR (Mobile Base Station Relay) node can have the same structure as IAB-node.

[0111] The IAB-node and MBSR-node are connected to the gNB-DU and gNB-CU via the F1 connection using NR Uu wireless connection. The N2 and N3 connections are connected to the 5GC via a wired connection through the IAB-donor gNB. The F1 connection may transmit less data and may be less important than the N2, N3, and OAM connections. On the other hand, the MWAB node, unlike the IAB-node and MBSR-node, uses NR Uu wireless connection to connect to N1, N2, and OAM. In other words, since the amount and importance of data transmitted via NR Uu wireless connection, which is more vulnerable than wired connection, are different between the IAB-node (MBSR-node) and the MWAB-node, the IAB-node can utilize multiple NR Uu hops, but the MWAB-node limits the NR Uu hop to one hop.

[0112] That is, in the case of the IAB-node or MBSR-node in Fig. 7, it is possible to connect to the IAB-donor node using another IAB-node, but in the case of the MWAB-node, the MWAB-node must be connected only to the gNB. If the MWAB-node connects to the IAB-node, MBSR-node, or another MWAB-node, this means connecting to the 5GC using an NR Uu wireless network of two or more hops.

[0113] FIG. 8a, FIG. 8b, and FIG. 8c illustrate a network registration procedure of a terminal (810) according to one embodiment of the present disclosure.

[0114] In step 1, a terminal (i.e., UE) (810) may transmit a registration request message to a base station (R)AN (820). The Registration Request message may include one or more of the following parameters: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, [last visited TAI (if available)], Security parameters, [Requested NSSAI], [Mapping Of Requested NSSAI], [Default Configured NSSAI Indication], [UE Radio Capability Update], [UE MM Core Network Capability], [PDU Session status], [List Of PDU Sessions To Be Activated], [Follow-on request], [MICO mode preference], [Requested Active Time], [Requested DRX parameters for E-UTRA and NR], [Requested DRX parameters for NB-IoT], [extended idle mode DRX parameters], [LADN (local area data network) DNN (data network name)(s) or Indicator Of Requesting LADN Information], [NAS message container], [Support for restriction of use of Enhanced Coverage], [Preferred Network Behavior], [UE paging probability information], [Paging Subgrouping Support Indication],[UE Policy Container (list of PSIs, indication of UE support for ANDSP, operating system identifier, Indication of URSP Provisioning Support in EPS, UE capability of reporting URSP rule enforcement to network, UE capability of supporting VPLMN-specific URSP rules)] and [UE Radio Capability ID], [Release Request indication], [Paging Restriction Information], PEI, [PLMN with Disaster Condition], [Requested Periodic Update time], [Unavailability Period Duration], [Start of Unavailability Period], [Unavailability Type])).,

[0115] If (R)AN(820) is NG-RAN, AN(Access Network) parameters may include the following values: 5G-S-TMSI or GUAMI, Selected PLMN ID (or PLMN ID and NID) and NSSAI information, Establishment cause.

[0116] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​is a type of terminal ID and is an abbreviated form of 5G-GUTI (5G Globally Unique Temporary Identifier). 5G-S-TMSI consists of an AMF Set ID, AMF Pointer, and 5G-TMSI and is used in wireless signaling procedures.

[0117] GUAMI (Globally Unique AMF Identifier) ​​is a type of AMF ID that can identify one or more AMFs. GUAMI consists of MCC, MNC, AMF Region ID, AMF Set ID, and AMF Pointer.

[0118] A Public Land Mobile Network (PLMN) ID is the mobile carrier's ID. It consists of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).

[0119] NID (Network identifier) ​​is an ID used to identify a SNPN (Stand-alone Non-public Network). The PLMN ID and NID are used together to identify the SNPN.

[0120] The values ​​included in NSSAI (Network Slice Selection Assistance Information) Information are determined by the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter provided by AMF.

[0121] The establishment cause value indicates the purpose for which the terminal (810) requested the creation of an RRC (Radio Resource Control) connection.

[0122] If the terminal (810) is an IAB (Integrated access and backhaul) node connecting to 5GS, the AN parameter must include IAB-Indication.

[0123] If the terminal (810) is part of a Mobile Base Station Relay (MBSR) node, the AN parameter must include an MBSR Indication.

[0124] The Registration type value indicates the purpose for which the terminal (810) requests registration. The Registration type value can be set to one of the following values: Initial Registration, Mobility Registration Update, Periodic Registration Update, Emergency Registration, Disaster Roaming Initial Registration, or Disaster Roaming Mobility Registration Update.

[0125] SUCI (Subscription Concealed Identifier) ​​is a form of terminal ID that includes a concealed SUPI (Subscription Permanent Identifier) ​​value to prevent leakage of the SUPI value.

[0126] 5G-GUTI (5G Globally Unique Temporary Identifier) ​​is a type of terminal ID assigned by AMF to the terminal (810). 5G-GUTI consists of GUAMI and 5G-TMSI.

[0127] PEI (Permanent Equipment Identifier) ​​identifies ME (Mobile Equipment). If the terminal (810) supports at least one 3GPP access technology (i.e., NG-RAN, E-UTRAN, UTRAN, or GERAN), the PEI format must be set to IMEI (International Mobile Equipment Identity) or IMEISV (International Mobile Equipment Identity-Software Version).

[0128] The last visited TAI (Tracking Area Identity) indicates the TAI value that the terminal (810) last visited. The last visited TAI value is used as a reference by the AMF to determine the RA (Registration Area) of the terminal (810).

[0129] Security parameters values ​​are used for authentication and integrity protection of the terminal (810).

[0130] The Requested NSSAI value includes a S-NSSAI(s) (Single Network Slice Selection Assistance Information) value corresponding to the Network Slice(s) that the terminal (810) wishes to use. If the terminal (810) is an MWAB-UE, the S-NSSAI(s) included in the Requested NSSAI may be an S-NSSAI(s) that supports MWAB operation.

[0131] The Mapping Of Requested NSSAI value contains the value of HPLMN S-NSSAI.

[0132] When a terminal (810) uses E-UTRA (Evolved UTRA), the terminal indicates whether it supports CIoT (Cellular IoT) 5GS optimizations. The support for 5GS optimizations indicated by the terminal (810) affects AMF selection.

[0133] If the terminal (810) performs initial registration or disaster roaming registration, the terminal (810) must indicate its identity in the Registration Request message as follows.

[0134] i. If the terminal (810) has a valid EPS (Evolved Packet System) GUTI, the 5G-GUTI mapped to it.

[0135] ii. If possible, the native 5G-GUTI allocated by the PLMN with which the terminal (810) is attempting to register.

[0136] iii. If possible, a native 5G-GUTI allocated by the equivalent PLMN of the PLMN in which the terminal (810) is attempting to register.

[0137] iv. If available, native 5G-GUTI allocated by another PLMN.

[0138] v. If all of the above is not possible, the terminal (810) must include its SUCI in the Registration Request message.

[0139] In the present disclosure, the terminal (810) may include HPLMN information (HPLMN ID and terminal GPSI of the HPLMN) in the registration request message. In addition, the terminal (810) may include information regarding a follow-on request in the registration request message to inform the network that the terminal will immediately create a PDU Session after registration.

[0140] Additionally, if the terminal (810) is an MWAB-UE, and the terminal registers with the network for MWAB operation, the S-NSSAI and DNN configured for MWAB for each PLMN can be added to the registration request message. The S-NSSAI and DNN configured for MWAB for each PLMN can be added to the registration request message as NAS parameters.

[0141] In step 2, if the base station NG-RAN (820) does not include 5G-S-TMSI or GUAMI in the AN parameters or these values ​​indicate an invalid AMF, the (R)AN can select an AMF based on the Requested NSSAI.

[0142] The base station (820) can know that the terminal (810) registers with the network for MWAB operation based on the NSSAI included as an AN parameter. Therefore, when selecting an AMF, an AMF that supports MWAB can be selected. That is, the base station (820) can select an AMF that supports MWAB if at least one S-NSSAI included in the requested NSSAI included in the registration request message supports MWAB.

[0143] In one embodiment, when the base station (820) is one of an IAB-donor node, an IAB node, an MBSR node, or another MWAB-gNB node, and the terminal (810) requesting registration is an MWAB-UE, the base station (820) may reject the registration request of the terminal because the MWAB-UE connects to the 5GC using an NR Uu wireless network of two or more hops. That is, the base station (820) may transmit a registration rejection message to the terminal (810). The registration rejection message may include a rejection cause indicating that two or more NR Uu hops are required for the terminal to the NG-RAN.

[0144] If the NG-RAN node rejects the registration request, all subsequent procedures may be cancelled.

[0145] In step 3, the NG-RAN (820) may transmit a Registration Request message to the selected AMF (i.e., New AMF) (830). At this time, the NG-RAN (820) may include N2 parameters and LTE-M Indication in the Registration Request message. The N2 parameter may include one or more of the following values: Selected PLMN ID (PLMN ID and NID if NPN), Location Information and Cell Identity of the UE, and UE Context Request.

[0146] The selected AMF (830) can determine that the terminal (810) requests registration for MWAB Operation based on the NSSAI requested by the terminal. That is, the selected AMF (830) can identify that the terminal (810) requests registration for MWAB Operation if at least one S-NSSAI included in the requested NSSAI included in the registration request message supports MWAB. If the NG-RAN (820) that transmitted the Registration Request message is an IAB-node, an MBSR-node, or an MWAB-node, the following operations can be performed:

[0147] i. The selected AMF (830) or base station (820) may reject the registration request of the terminal (810). The registration rejection message may include a Cause value (more than or equal to two NR Uu hops).

[0148] ii. The selected AMF (830) or base station (820) can request the terminal (810) to connect to another base station (not an IAB-node, MBSR-node, or MWAB-node).

[0149] If the selected AMF (830) rejects the registration request of the terminal (810), the selected AMF (830) can transmit a registration rejection message to the terminal (810) through the base station (820).

[0150] If the AMF or NG-RAN node rejects the registration request, all subsequent procedures may be cancelled.

[0151] In step 4, if the selected AMF (830) is a new AMF, it may transmit a Namf_Communication_UEContextTransfer message to the old AMF (840), or transmit a Nudsf_UnstructuredDataManagement_Query to the Unstructured Data Storage Function (UDSF). And in step 5, the selected AMF (830) may receive a Namf_Communication_UEContextTransfer response message from the old AMF (840). This message may include one or more of the following values: SUPI, UE Context in AMF. Alternatively, the selected AMF (830) may receive a Nudsf_UnstructuredDataManagement_Query message from the UDSF. This message may include terminal-related data.

[0152] In step 6, if the selected AMF (830) has not received SUCI from the terminal and the old AMF (840), the selected AMF (830) can transmit an Identity request message requesting SUCI to the terminal (810). Then, in step 7, the selected AMF (830) can receive an Identity response message including the terminal SUCI from the terminal (810).

[0153] In step 8, the selected AMF (830) can perform authentication of the terminal (810). The selected AMF (830) can select the AUSF (870) based on the SUPI or SUCI of the terminal (810).

[0154] In step 9, if authentication of the terminal (810) is required, the selected AMF (830) can request authentication of the terminal (810) from the AUSF (870) selected in step 8.

[0155] If a terminal NAS security context does not exist for the terminal (810), NAS security initiation can be performed.

[0156] The selected AMF (830) may perform a Next Generation Application Protocol (NGAP) procedure to provide a security context to the 5G-AN. The 5G-AN may store the security context provided by the selected AMF (830) and transmit an acknowledgement thereof to the selected AMF (830).

[0157] In step 10, the selected AMF (830) may send a Namf_Communication_RegistrationStatusUpdate message to the old AMF (840). This message may include the PDU Session ID(s) that are released due to a slice that the selected AMF (830) cannot provide.

[0158] In step 11, the selected AMF (830) can transmit and receive an Identity Request message and an Identity Response message requesting PEI of the terminal (810).

[0159] In step 12, the selected AMF (830) may perform N5g-eir_EquipmentIdentityChenk_Get to check the terminal ME Identity with the equipment identity register (EIR).

[0160] In step 13, if necessary, the selected AMF (830) can perform UDM selection based on terminal SUPI. UDM (880) can perform UDR instance selection.

[0161] In step 14a, if the selected AMF (830) has not registered the terminal (810) with the UDM (880), the AMF (830) can register the terminal (810) with the UDM (880) by sending the Nudm_UECM_Registration message to the UDM (830).

[0162] The AMF (830) selected in step 14b can obtain subscriber information (e.g., Access and Mobility Subscription data) of the terminal (810) from the UDM (880).

[0163] The AMF (830) selected in step 14c can send a Nudm_SDM_Subscribe message to the UDM (880).

[0164] In step 14d, the old AMF (840) can receive a Nudm_UECM_DeregistrationNotify message from the UDM (880). And in step 14e, the old AMF (840) can send a Nudm_SDM_Unsubscribe message to the UDM (880).

[0165] In step 15, the selected AMF (830) can perform PCF selection.

[0166] In step 16, the selected AMF (830) can perform an AM (Access and Mobility) policy association establishment / modification procedure with the selected PCF (850).

[0167] In step 17, the selected AMF (830) can send an Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext message to the SMF (860).

[0168] If the registration message includes a list of PDU sessions to be activated (List Of PDU Sessions To Be Activated), the selected AMF (830) can activate the user plane connection(s) of the corresponding PDU session(s) by sending an Nsmf_PDUSession_UpdateSMContext Request message to the SMF (860).

[0169] If the PDU Session status indicates that the PDU Session(s) have been released, the selected AMF (830) may request the release of the corresponding PDU Session(s) by sending an Nsmf_PDUSession_ReleaseSMContext Request message to the SMF (860).

[0170] In step 18, the selected AMF (830) may transmit a UE Context Notification Request message to N3IWF / TNGF (Non-3GPP InterWorking Function / Trusted Non-3GPP Gateway Function). And in step 19, the selected AMF (830) may receive a UE Context Notification Response message from N3IWF / TNGF.

[0171] In step 19a, the selected AMF (830) may register by sending a Nudm_UECM_Registration message to the UDM (880) after receiving the UE Context Notification Response message from the N3IWF / TNGF in step 19. At this time, the Access Type may be set to "non-3GPP access".

[0172] In step 19b, the UDM (880) may send a Nudm_UECM_DeregistrationNotify message to the old AMF (840). And in step 19c, the old AMF (840) may send a Nudm_SDM_Unsubscribe message to the UDM (880).

[0173] The AMF (830) selected in step 21 may transmit a Registration Accept message to the terminal (810). The Registration Accept message may include one or more of the following values: 5G-GUTI, Registration Area, [Mobility restrictions], [PDU Session status], [Allowed NSSAI], [Mapping Of Allowed NSSAI], [Partially Allowed NSSAI], [Mapping Of Partially Allowed NSSAI], [TAI List for S-NSSAIs in Partially Allowed NSSAI], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], [NSSRG Information], [NSAG Information], [rejected S-NSSAIs], [TAI List for any rejected S-NSSAI Partially in the RA], [Pending NSSAI], [Mapping Of Pending NSSAI], [Periodic Registration Update timer], [Active Time], [Strictly Periodic Registration Timer Indication], [LADN Information], [MICO Indication], [IMS Voice over PS session supported Indication], [Emergency Service Support indicator], [Accepted DRX parameters for E-UTRA and NR], [Accepted DRX parameters for NB-IoT], [extended idle mode DRX parameters], [Paging Time Window],[Network support of Interworking without N26], [Access Stratum Connection Establishment NSSAI Inclusion Mode], [Network Slicing Subscription Change Indication], [Operator-defined access category definitions], [List of equivalent PLMNs], [Enhanced Coverage Restricted information], [Supported Network Behaviour], [Service Gap Time], [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID deletion], [WUS Assistance Information], [AMF PEIPS Assistance Information], [Truncated 5G-S-TMSI Configuration], [Connection Release Supported], [Paging Cause Indication for Voice Service Supported], [Paging Restriction Supported], [Reject Paging Request Supported], [Paging Restriction Information acceptance / rejection], ["List of PLMN(s) to be used in Disaster Condition"], [Disaster Roaming wait range information], [Disaster Return wait range information], [Forbidden TAI(s)], [List of equivalent SNPNs], [Registered NID], [Unavailability Period Support],[MBSR authorization information], [Return To Coverage Notification Not Required], [Unavailability Period Duration], [Start of Unavailability Period], [S-NSSAI location availability information], [Mapping Of Alternative NSSAI], [Slice Usage Policy], [Maximum Time Offset].,

[0174] In step 21b, the selected AMF (830) can perform UE policy association establishment with the PCF (850).

[0175] The terminal (810) that received the Registration Accept message in step 22 can transmit a registration complete message to the selected AMF (830).

[0176] In step 23, the selected AMF (830) can transmit and receive UDM (880) and Nudm_SDM_info.

[0177] In step 23a, when the terminal (810) registers using 3GPP access, if the selected AMF (830) does not release the signaling connection to the (R)AN (820), RRC inactive assistance information can be transmitted to the (R)AN (820).

[0178] In step 24, the selected AMF (830) can send a Nudm_UECM_Update message to the UDM (880).

[0179] And in step 25, if the terminal (810) indicates that it can perform Network Slice-Specific Authentication and Authorization (NSSAA) in the UE MM (mobility management) Core Network Capability, and if there is an S-NSSAI requiring NSSAA among the requested S-NSSAIs, the selected AMF (830) can initiate the NSSAA procedure.

[0180] Figure 9 illustrates the configuration of a terminal according to one embodiment of the present disclosure.

[0181] A terminal according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the terminal, a transceiver (900) including a transmitter and a receiver, and a memory (910). Of course, the terminal is not limited to the above-described examples, and the terminal may include more or fewer components than those illustrated in FIG. 4.

[0182] According to one embodiment of the present disclosure, the transceiver (900) can transmit and receive signals with network entities or other terminals. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (900) can receive signals via a wireless channel, output them to the processor (920), and transmit the signals output from the processor (920) via the wireless channel. The transceiver (900) may be referred to as a transceiver.

[0183] According to one embodiment of the present disclosure, the processor (920) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (920), the memory (910), and the transceiver (900) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (920) and the transceiver (900) can be electrically connected. In addition, the processor (920) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0184] According to one embodiment of the present disclosure, the memory (910) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (910) provides the stored data upon request of the processor (920). The memory (910) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (410). In addition, the processor (920) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (910).

[0185] FIG. 10 illustrates a configuration of a network entity according to one embodiment of the present disclosure.

[0186] The network entity may be one of the (R)AN (e.g., base station) (820), New AMF (830), Old AMF (840), PCF (850), SMF (860), AUSF (870), and UDM (880) disclosed in FIG. 8.

[0187] A network entity according to one embodiment of the present disclosure may include a processor (1020) that controls the overall operation of the network entity, a transceiver (1000) including a transmitter and a receiver, and a memory (1010). Of course, the present invention is not limited to the above-described examples, and the network entity may include more or fewer components than those illustrated in FIG. 5.

[0188] According to one embodiment of the present disclosure, the transceiver (1000) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data. The transceiver (1000) may be referred to as a transceiver.

[0189] According to one embodiment of the present disclosure, the processor (1020) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (1020), the memory (1010), and the transceiver (1000) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (1020) and the transceiver (1000) can be electrically connected. In addition, the processor (1020) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0190] According to one embodiment of the present disclosure, the memory (1010) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (1010) provides the stored data upon request of the processor (1020). The memory (1010) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (1010). In addition, the processor (1020) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (1010).

[0191] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

[0192] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0193] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

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

[0195] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0196] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0197] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0198] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a wireless communication system, a method for network registration of a mobile base station by AMF (Access and Mobility Management Function), A step of receiving a registration request message for a terminal from a base station, wherein the registration request message includes requested NSSAI (network slice selection assistance information), and the requested NSSAI includes at least one S-NSSAI (single-NSSAI); and A step of transmitting a registration rejection message for the terminal to the base station when the at least one S-NSSAI supports MWAB (Mobile gNB with Wireless Access Backhaul) and the base station is an IAB (Integrated Access and Backhaul)-node, an MBSR (Mobile Base Station Relay)-node, or an MWAB-node, method.

2. In paragraph 1, The above registration rejection message includes a rejection cause associated with two or more new radio (NR) Uu hops to the radio access network (RAN). method.

3. In paragraph 1, If the at least one S-NSSAI supports the MWAB and the base station is the IAB-node, the MBSR-node or the MWAB-node, further comprising a step of transmitting a message to the terminal through the base station for requesting connection to another base station. method.

4. In paragraph 1, The above registration request message further includes S-NSSAI and DNN (data network name) configured for MWAB for each PLMN (public land mobile) as NAS (non-access stratum) parameters. method.

5. In paragraph 1, The above AMF is an AMF that supports the above MWAB and is selected by the base station. method.

6. In a wireless communication system, a method for network registration of a mobile base station by a base station, A step of receiving a first registration request message including a requested NSSAI (network slice selection assistance information) from a terminal, wherein the requested NSSAI includes at least one S-NSSAI (single-NSSAI); and If at least one S-NSSAI supports MWAB (Mobile gNB with Wireless Access Backhaul), the step of transmitting a second registration request message for the terminal to an AMF supporting MWAB is included. method.

7. In paragraph 6, A step of transmitting a registration rejection message to the terminal when at least one S-NSSAI supports the MWAB and the base station is an IAB (Integrated Access and Backhaul) node, an MBSR (Mobile Base Station Relay) node or an MWAB node, method.

8. In paragraph 7, The above registration rejection message includes a rejection cause associated with two or more new radio (NR) Uu hops to the radio access network (RAN). method.

9. In paragraph 6, If the at least one S-NSSAI supports the MWAB and the base station is an IAB-node, an MBSR-node or an MWAB-node, further comprising a step of transmitting a message to the terminal for requesting connection to another base station. method.

10. In paragraph 6, The first registration request message and the second registration request message further include S-NSSAI and DNN (data network name) configured for MWAB for each PLMN (public land mobile) as NAS (non-access stratum) parameters. method.

11. In a wireless communication system, as an AMF (Access and Mobility Management Function) for network registration of a mobile base station, Transmitter and receiver; and At least one processor coupled to the transceiver, wherein the at least one processor comprises: Receive a registration request message for a terminal from a base station, wherein the registration request message includes requested NSSAI (network slice selection assistance information), and the requested NSSAI includes at least one S-NSSAI (single-NSSAI); and If at least one S-NSSAI supports MWAB (Mobile gNB with Wireless Access Backhaul) and the base station is an IAB (Integrated Access and Backhaul)-node, an MBSR (Mobile Base Station Relay)-node, or an MWAB-node, the base station is configured to transmit a registration rejection message for the terminal to the base station. AMF.

12. In paragraph 11, The above registration rejection message includes a rejection cause associated with two or more new radio (NR) Uu hops to the radio access network (RAN). AMF.

13. In paragraph 11, The at least one processor is further configured to transmit a message to the terminal through the base station to request connection to another base station, when the at least one S-NSSAI supports the MWAB and the base station is the IAB-node, the MBSR-node or the MWAB-node. AMF.

14. In paragraph 11, The above registration request message further includes S-NSSAI and DNN (data network name) configured for MWAB for each PLMN (public land mobile) as NAS (non-access stratum) parameters. AMF.

15. In paragraph 11, The above AMF is an AMF that supports the above MWAB and is selected by the base station. AMF.

Images