WO2024035004A1 - Location-based terminal mobility management method and device in mobile communication system - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system to support a higher data transmission rate. Specifically, the present disclosure relates to a device for managing the mobility of a terminal on the basis of a detailed location, the device comprising: a transceiver; and a controller coupled to the transceiver, wherein the controller may be configured to: receive setting information for setting at least one cube associated with a three-dimensional space within a cell; receive auxiliary information for location measurement from a location management function (LMF) node; transmit the auxiliary information for location measurement to the terminal; receive concealed information related to the location measurement of the terminal from the terminal; identify an identifier (ID) of a cube related to the terminal on the basis of the concealed information related to the location measurement of the terminal; determine whether it is allowed to apply a mobility management policy based on the identifier of the cube to the terminal; and transmit information about the mobility management policy to the terminal.

Description

Location-based terminal mobility management method and device in mobile communication system

The present disclosure relates to a mobile communication system (or wireless communication system), and specifically, the present disclosure relates to a method for managing the mobility of a terminal in a mobile communication system (or wireless communication system).

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, including sub-6 GHz ("Sub 6GHz") bands such as 3.5 GHz, as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ("Above 6GHz") called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz (THz) bands (e.g., 3 terahertz bands at 95 GHz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

As communication systems develop, demand for methods to more efficiently manage the mobility of terminals is increasing.

Current mobile communication systems do not support terminal mobility management in units smaller than a cell or tracking area (TA). This is because the network entity (or network function) of the core network cannot recognize the detailed location of the terminal in units smaller than cells during the terminal's initial registration procedure. Additional security procedures are required to provide the detailed location of the terminal to the core network during the initial registration process. This is because the initial registration procedure request message transmitted by the terminal is not completely secure, and the detailed location information of the terminal is personal information.

Therefore, below, we propose a method for managing the mobility of a terminal in units smaller than cells. Specifically, we propose a cube as an area unit that is smaller than the cell used inside the 5G system and can specify the three-dimensional location of the terminal. In this regard, a procedure in which the network entity (or network function) of the core network transmits cube map information, zoning the network coverage area into cubes, to the terminal and base station, and detailed location information of the terminal during the registration procedure of the terminal. We specifically propose a procedure for transmitting to the terminal and base station the information necessary to determine on a cube basis, and a procedure for transmitting information about the cube area where the terminal is located to a network entity without leaking personal information.

A method according to an embodiment of the present disclosure includes: a network entity transmitting information related to the location of a terminal to a terminal; and receiving a security message including the location of the terminal from the terminal.

According to various embodiments proposed in this disclosure, it is possible to confirm the three-dimensional position of the terminal in more detailed units than cells or tracking areas. Through this, the network entity can manage the mobility of the terminal based on the three-dimensional location of the terminal, making it possible to manage the mobility of the terminal more efficiently and specifically.

Additionally, according to various embodiments proposed in this disclosure, it is possible to specify the detailed location of the terminal in the initial registration procedure or periodic registration procedure of the terminal. This allows network entities in the core network to apply access and mobility management policies to specific physical areas (areas that are smaller than a cell or tracking area, or areas that cannot be accurately defined only by cell ID (identifier) or TAI). there is.

In addition, according to various embodiments proposed in this disclosure, information requiring personal information security, such as the detailed location of the terminal, can be included and transmitted in the registration request message even before NAS (non-access stratum) security is guaranteed during the initial registration process. This makes it possible to maintain the safety and security of personal information.

1 is a diagram illustrating an example of the structure of a 5G core network related to the present disclosure.

Figure 2 is a diagram explaining a procedure for managing the mobility of a terminal in relation to an embodiment proposed in this disclosure.

FIG. 3 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure.

FIG. 4 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure.

FIG. 5 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure.

FIG. 6 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure.

Figure 7 is a diagram showing the structure of a terminal according to embodiments of the present disclosure.

Figure 8 is a diagram showing the structure of a base station according to embodiments of the present disclosure.

FIG. 9 is a diagram illustrating the structure of a network function (or network entity) according to embodiments of the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. At this time, it should be noted that in the attached drawings, identical components are indicated by identical symbols whenever possible. Additionally, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

In describing the embodiments in this specification, description of technical content that is well known in the technical field to which the present disclosure belongs and that is not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative embodiments it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to what roles. Perform. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

Terms used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and a term referring to various types of identification information. The following are examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

For convenience of description below, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard or the New Radio (NR) standard. However, the present disclosure is not limited by the above terms and names, and can be equally applied to systems complying with other standards.

Hereinafter, the base station (BS) is the entity that performs resource allocation for the terminal, and includes a radio access network (RAN) node, gNode B (next generation node B, gNB), eNode B (evolved node B, eNB), and Node B, may be at least one of a wireless access unit, a base station controller, or a node on a network. In this disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as an eNB may represent a gNB.

Hereinafter, a terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above example.

In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). In addition, the present disclosure provides intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, It can be applied to security and safety-related services, etc.) Additionally, the term terminal can refer to other wireless communication devices as well as mobile phones, NB-IoT devices, and sensors.

Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.

As a representative example of a broadband wireless communication system, the LTE system uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (DL), and SC-FDMA (Single Carrier Frequency Division Multiple Access) in the uplink (UL). ) method is adopted. Uplink refers to a wireless link through which a terminal (or UE) transmits data or control signals to a base station (or eNB, gNB), and downlink refers to a wireless link through which a base station transmits data or control signals to the terminal. The multiple access method described above differentiates each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. .

As a future communication system after LTE, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for 5G communication systems include enhanced mobile broadband communication (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

According to one embodiment, eMBB may aim to provide more improved data transmission rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink from the perspective of one base station. In addition, the 5G communication system may need to provide the maximum transmission rate and at the same time provide an increased user perceived data rate. In order to meet these requirements, 5G communication systems may require improvements in various transmission and reception technologies, including more advanced multiple input multiple output (MIMO) transmission technology. In addition, while the current LTE transmits signals using a maximum of 20 MHz transmission bandwidth in the 2 GHz band, the 5G communication system uses a frequency bandwidth wider than 20 MHz in the 3 to 6 GHz or above 6 GHz frequency band, meeting the requirements of the 5G communication system. Data transfer speed can be satisfied.

At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC may require support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km^2) within a cell. Additionally, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas that cannot be covered by cells, such as the basement of a building, so wider coverage may be required compared to other services provided by the 5G communication system. Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

Lastly, in the case of URLLC, it is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, It can be used for services such as unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service that supports URLLC must meet an air interface latency of less than 0.5 milliseconds and may have a packet error rate of less than 10^-5. . Therefore, for services that support URLLC, the 5G system must provide a smaller transmission time interval (TTI) than other services, and at the same time, a design that requires allocating wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.

The three services considered in the above-described 5G communication system, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters can be used between services to satisfy the different requirements of each service. However, the above-described mMTC, URLLC, and eMBB are only examples of different service types, and the service types to which this disclosure is applied are not limited to the above-described examples.

In addition, hereinafter, embodiments of the present disclosure will be described using LTE, LTE-A, LTE Pro, 5G (or NR), or 6G systems as examples, but the present disclosure can also be applied to other communication systems with similar technical background or channel type. Examples may be applied. Additionally, 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 with skilled technical knowledge.

1 is a diagram illustrating an example of the structure of a 5G core network related to the present disclosure.

The 5G system structure that supports edge computing systems may include various network functions (NFs) or network entities. Figure 1 is an example of such a network function or network entity, including an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), Application function (AF), unified data management (UDM), data network (DN), user plane function (UPF), location management function (LMF) ), and in addition, it shows a (radio) access network ((R)AN) and a user equipment (UE) of the 5G core network.

The NFs shown in Figure 1 support the following functions.

AMF: AMF provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF.

DN: DN refers to a network outside of 5GS (5G system) where, for example, operator services, Internet access, or third party services exist. The DN transmits a downlink protocol data unit (PDU) to the UPF or receives an uplink PDU transmitted from the UE from the UPF.

PCF: PCF receives information about packet flow from the application server and provides the function of determining policies such as mobility management and session management. Specifically, PCF supports a unified policy framework to govern network behavior, provides policy rules so that control plane function(s) (e.g. AMF, SMF, etc.) can enforce the policy rules, and provides user data storage ( It supports functions such as implementing a front end to access relevant subscription information for policy decisions within the user data repository (UDR).

SMF: SMF provides a session management function, and when the UE has multiple sessions, each session can be managed by a different SMF.

UDM: UDM stores user subscription data, policy data, etc.

UPF: UPF delivers the downlink PDU received from the DN to the UE via (R)AN, and delivers the uplink PDU received from the UE to the DN via (R)AN.

AF: AF supports the 3GPP core for service provisioning (e.g., supporting functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control). Interoperates with the network.

LMF: LMF supports functions related to measuring the location of the terminal and providing location-related information in conjunction with AMF, UDM, and NEF.

The network functions or network entities shown in FIG. 1 are some of the nodes constituting the 5G core network, and the 5G core network may include more network functions or network entities than this example.

Figure 2 is a diagram explaining a procedure for managing the mobility of a terminal in relation to an embodiment proposed in this disclosure.

Figure 2 shows an example operation of performing mobility management of a terminal in units smaller than a cell unit. Hereinafter, in relation to the present disclosure, a unit smaller than a cell may be defined as a cube. Specifically, Figure 2 shows the process of dividing space into cube units, specifying the location of the terminal in cube units, and tracking the location of the terminal in cube units in a mobile communication network. A cube may have a cube or rectangular parallelepiped shape, and may be specified or expressed by three three-dimensional coordinates.

For example, Table 1 below represents one or more sets of information for defining and using a cube, and for example, this set of information may be defined under the name data type for cube. Data type for cube can be expressed with one or more attributes as shown in Table 1. For example, the shape attribute value can include cube or rectangular cuboid value, and a point list. )'s characteristic value may include a 3D point value to indicate the area and size of the actual cube. In addition, the data type for cube is a cell ID (identifier) as an associated cell(s) characteristic value or an associated tracking area(s) characteristic value to express information on cells or TAs that contain or are adjacent to the cube area. Or, it may include a TA ID. The data type for cube may be information representing one cube, and a plurality of cell IDs or TA IDs may be included for this one cube. Furthermore, the data type for cube can also include a cube's unique identifier (cube ID) as a characteristic value.

Using the cube defined above, a specific region or service area of a mobile communication network can be divided into zones without any gaps (i.e., tessellation with cubes), and these results can be expressed as a cube map. A cube map can be defined as a cube list containing one or more cubes, and the data type for cube map can be defined as shown in Table 2 below.

As shown in Table 2, data type for cube map can be defined as cube list, cube identifier and cell ID, and TA ID. If the data type for cube map includes characteristic values for cell ID or TA ID, the data type for cube map will be understood as expressing the result of zoning (or dividing into zones) the corresponding cell area or TA into cubes. You can. In this case, the data type for cube map may be interpreted as information specific to the cell or TA, and may be invalid information in other cells or TAs.

In the detailed description of the present disclosure, the specific shape of the cube is limited to a cube or rectangular parallelepiped and used in the description of the following embodiments. However, of course, various modifications to the shape of the cube are possible without departing from the scope of the present disclosure. For example, the shape of a cube can be defined as a convex hexahedron or a hexagonal prism, and it is natural that these various cube shapes are also included in the invention proposed in this disclosure. . In this other example, when defining a cube in the form of a hexahedron or a hexagonal prism rather than a convex regular/cube, the value corresponding to the shape, the value of pointList, and the cardinality value in the set of information displayed as data type for cube are It may have different values from Table 1.

In this way, in order for the core network to track the location of the terminal and manage mobility based on cube information and cube map information, new operations and functions are required.

First, an operation is required to set cube map information to network functions and RAN. For example, cube map information can be set to network entities (or network functions) such as LMF, AMF, and RAN through an operation and management (OAM) system.

In addition, an operation is required to transmit all or part of the cube map information in which entities (or functions) such as LMF, AMF, and RAN are set for each to the terminal. For example, LMF can deliver cube map information to the terminal through AMF and RAN.

The LMF may transmit or provide information (e.g., assistance data) necessary to specify the location of the terminal on a cube basis to the AMF, RAN, and the terminal. The information required for specification on a cube basis includes GPS (global positioning system) auxiliary information needed to perform positioning of the terminal, base station transceiver point location information needed to perform 3GPP-based positioning, and related signaling setting information (e.g., It may include at least one of DL/UL positioning reference signal (PRS) setting information) and cube map information. Additionally, the LMF can receive measurement values from the terminal and directly perform an operation to specify the location of the terminal in cube units. The LMF can provide the cube identifier determined as a result of this operation to the AMF.

The AMF can deliver the cube map information received from the LMF and the auxiliary information necessary for measuring the cube-level position of the terminal to the terminal through the RAN. Additionally, AMF can determine whether the terminal supports cube-level mobility management based on signaling received from the terminal. In addition, AMF can check subscriber information for the corresponding terminal in conjunction with UDM and check whether the network allows cube-level mobility management for the terminal. Additionally, AMF can apply or enforce AM policies (access and mobility management policy) applied on a cube basis to the corresponding terminal.

The RAN uses set cube map information or cube map information received from LMF through AMF (e.g., cell-specific cube map or TA-specific cube map information), or auxiliary information required for cube unit UE location measurement (e.g., At least one of GPS assistance information, signaling configuration information such as base station transceiver point location information and related DL/UL PRS configuration information required to perform 3GPP-based positioning, and cube map information) may be transmitted to the terminal. The method by which the RAN transmits the above-described information to the terminal is through periodic broadcasting (e.g., periodically transmitted by including in a SIB (system information block)), or when the terminal transmits an on-demand SIB during the initial access procedure. When requested, the response may include transmitting cube map information or auxiliary information necessary for cube-level terminal location measurement. Additionally, the RAN can perform AM policy enforcement applied on a cube basis to the terminal based on information received from the AMF.

The terminal may perform an operation to determine the cube identifier (cube ID) of the cube in which the terminal is located based on information received from the network (cube map information and auxiliary information required for cube-level terminal location measurement).

In addition, the terminal can perform a concealment operation for the cube identifier based on information set in the Universal Subscriber Identify Module (USIM) or the universal integrated circuit card (UICC) within the terminal, and the terminal can use the hidden cube identifier ( concealed cube ID) can be transmitted to AMF through RAN. This concealment operation can be performed using the home network public key set in the terminal.

In addition, the terminal may not directly determine the cube identifier based on information set within the terminal or information received from the network, but may provide the network function or network entity (e.g., LMF or AMF) with the measurement values required to calculate the terminal location. there is.

Additionally, the terminal can monitor its own location based on cube map information and transmit the cube identifier information where the terminal is located to the AMF according to specific conditions (cube identifier reporting conditions received from the network).

At the request of the AMF or LMF, the UDM can perform a revealing or de-concealment operation on the cube identifier or the location-related measurement value of the terminal concealed with the home network public key. In addition, UDM stores subscriber information related to whether cube-level mobility management is allowed for the terminal and can provide related information to AMF or LMF.

Below, the procedures for cube-level mobility management described above will be described in detail.

FIG. 3 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure. Figure 3 explains in detail the cube-level mobility management procedure.

0. The OAM system sets cube map information to network entities (or network functions) such as RAN, AMF, and LMF. When cube map information is set to the RAN, the OAM can set only the cube map information corresponding to the coverage area or cell area of the RAN to the RAN. For example, cube map information set in the RAN may include only information corresponding to the cell ID broadcasted by the RAN. When cube map information is set to AMF, OAM can set only cube map information corresponding to the AMF service area defined by the TA(s) of AMF to AMF. For example, when the AMF service area is expressed as a TA ID list, cube map information set for AMF may include cube map information corresponding to the corresponding TA ID. Alternatively, when the OAM sets a cube map for a specific terminal to the AMF, the cube map may include only information corresponding to the registration area of the terminal. For example, if the registration area of the terminal set by the AMF is expressed as a TA ID list, cube map information corresponding to the TA ID list may be set to the AMF for each terminal. When the OAM sets cube map information to the LMF, cube map information corresponding to the service area of the LMF may be set to the LMF.

1. The LMF transmits or provides the AMF with auxiliary data (or auxiliary information) necessary to measure the location of the terminal in cube units. This auxiliary data (or information) refers to information necessary to measure the location of the UE in the UE or RAN, and information on at least one of the following may be included in the auxiliary data (or information).

[TAI, Cell ID, TA-specific cube map information, cell-specific cube map information, DL-PRS configuration information for RAN transmitter/receiver point(s) (Transmission/Reception point(s), TRP(s)) , SSB (Synchronization Signal Block) for RAN TRPs, spatial direction information of the DL-PRS, geographic coordinates information for TRPs]

The conditions under which LMF provides such auxiliary data (or auxiliary information) may be as follows. If the LMF receives an auxiliary data request from an AMF, a request from an external application function (AF) (via the NEF), or the LMF's service area overlaps a cube-level mobility management area, the LMF is within the LMF service area. Auxiliary data may be provided to AMF.

2. AMF transmits to the RAN the auxiliary data required to measure the location of the terminal in cube units received from the LMF.

3. The RAN transmits to the terminal at least one of the information previously received and set from the OAM (e.g., cube map information including a cube ID list) and auxiliary data required to measure the location of the terminal in cube units received from the AMF. do.

The RAN can transmit the above-described information to the terminal in two ways as follows. The RAN can periodically broadcast the information by including it in a broadcast message. Alternatively, when the RAN transmits an on-demand system information block (SIB) message including a cube-level positioning or cube-level mobility management indicator or flag to the RAN, the RAN's response message includes the auxiliary data and sends the RAN to the RAN. can be sent to.

4. The terminal calculates the location coordinates of the terminal through terminal location measurement/calculation using at least one of the information received from the RAN, the GPS module mounted inside the terminal, and the sensor, and compares it with the cube map information to determine where the terminal is located. Decide on a cube. The terminal may perform an operation to transmit the corresponding cube ID to the RAN and AMF.

Specifically, the terminal performs concealment of the determined cube ID using the home network public key set in the terminal and generates a concealed cube ID. For example, if the cube ID concealment indication is set in the USIM within the terminal, the terminal can calculate and generate a concealed cube ID using the home network public key stored in the USIM. If the cube ID hiding indicator is not set in the USIM, the terminal can encrypt the cube ID using another encryption method.

5. The terminal transmits the generated concealed cube ID to AMF. Concealed cube ID may be transmitted and included in the terminal's registration request message. When transmitting a concealed cube ID to the AMF, the terminal includes a fine grained MM (mobility management) support indication and the method by which the terminal encrypted the cube ID or the cube ID concealment method (e.g., home At least one of the network public key usage, encryption scheme information, etc.), and terminal identifier can be provided to AMF along with the concealed cube ID.

6. AMF receives the concealed cube ID from the terminal, and if the cube ID concealment method uses the home network public key, the AMF can transmit the concealed cube ID to the UDM along with the terminal identifier. Additionally, if the terminal indicates that it supports fine-grained mobility management through a fine-grained MM support indication, the AMF may request related subscriber information from the UDM.

7. UDM performs de-concealment operation for concealed cube ID using home network private key. This operation is performed in UDM's SIDF (subscriber identity de-concealing function).

UDM can also check based on subscriber information whether fine-grained mobility management or cube-level mobility management is allowed for the corresponding terminal. Additionally, the de-concealment operation may be performed only when fine-grained mobility management or cube-level mobility management is allowed for the terminal according to the network operator's policy and subscriber information. For example, if the terminal does not support fine-grained mobility management or cube-level mobility management is not allowed for the terminal, the UDM will not perform a de-concealment operation for the cube ID and provide a rejection response to the AMF. You can.

8. UDM transmits the cube ID to AMF as a result of cube ID de-concealment. UDM can also provide AMF with subscriber information indicating that the terminal is allowed to use fine-grained mobility management or cube-level mobility management. AMF can provide the RAN with the cube ID of the cube area where the terminal is located.

9. AMF can perform AM policy association using the cube ID received from UDM. For example, AMF may provide the PCF with the cube ID of the cube where the terminal is located, and receive policy information that should be applied in the corresponding cube area from the PCF. Policy information that AMF receives from PCF may include at least one of the following:

- Cube-level mobility restriction or service area restriction (allowed cube ID list, non-allowed cube ID list)

- Cube unit RFSP (RAT Frequency Selection Priority) Index value: RAT Frequency Selection Priority value set for the cube area, may correspond to subscriber profile ID for RAT/Frequency Priority

- Per cube UE-AMBR (aggregate maximum bitrate) or UE Slice-MBR (maximum bitrate)

When AMF receives an AM policy including a cube-level RFSP (Radio access type/Frequency of Selection Priority) Index from PCF, it transmits the RFSP Index value to RAN, and RAN selects RAT/Frequency based on RAT Frequency selection priority. can be performed. Additionally, AMF can also provide the RAN with a cube ID that matches the location of the terminal.

10. AMF transmits to the terminal at least one of the cube ID (de-concealed cube ID) obtained from UDM, reporting triggering condition (list of neighbor cube ID list), and flag to perform cube-level mobility tracking.

After step 10, the terminal checks whether the cube ID received from AMF matches the cube ID determined in step 4 in the terminal, and the cube area identified by the cube ID included in the cube ID list included in the reporting triggering condition provided by AMF Monitor whether it is out of bounds. This monitoring can be performed through UE-based positioning as in step 4.

When the terminal leaves the cube area included in the cube ID list included in the reporting triggering condition and enters a new cube area, it re-registers with AMF and transmits the cube ID. At this time, if the registration procedure to be re-performed is a registration update, the NAS signaling security may be guaranteed, so secure NAS signaling is performed without concealment in a separate method as in step 4 in front of the cube ID. It can be sent to AMF through.

FIG. 4 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure. Figure 4 specifically explains operations after the NAS security mode control procedure is completed in relation to the cube-level mobility management procedure.

0. The OAM system sets cube map information to network entities (or network functions) such as RAN, AMF, and LMF. When cube map information is set to the RAN, the OAM can set only the cube map information corresponding to the coverage area or cell area of the RAN to the RAN. For example, cube map information set in the RAN may include only information corresponding to the cell ID broadcasted by the RAN. When cube map information is set in the AMF, the OAM can set only the cube map information corresponding to the AMF service area defined by the TA(s) of the AMF to the AMF. For example, when the AMF service area is expressed as a TA ID list, cube map information set in AMF may include cube map information corresponding to the corresponding TA ID. Alternatively, when the OAM sets the cube map for a specific terminal to the AMF, the cube map may include information corresponding to the registration area of the terminal. For example, if the registration area of the terminal set by the AMF is expressed as a TA ID list, cube map information corresponding to the TA ID list may be set in the AMF for each terminal. When the OAM sets cube map information to the LMF, cube map information corresponding to the service area of the LMF may be set to the LMF.

1. The LMF transmits or provides the AMF with auxiliary data (or auxiliary information) necessary to measure the location of the terminal in cube units. This auxiliary data (or information) refers to information necessary to measure the location of the UE in the UE or RAN, and information on at least one of the following may be included in the auxiliary data (or information).

[TAI, Cell ID, TA-specific cube map information, cell-specific cube map information, DL-PRS configuration information for the transmitter/receiver point(s) of the RAN, SSB for RAN TRPs, spatial direction information of the DL -Geographic coordinate information for PRS and TRPs]

The conditions under which LMF provides such auxiliary data (or information) may be as follows. When the LMF receives an ancillary data request from an AMF, a request from an external AF (via the NEF), or the LMF's service area overlaps a cube-level mobility management area, the LMF sends ancillary data to the AMF within the LMF service area. can be provided.

2. AMF transmits to the RAN the auxiliary data required to measure the location of the terminal in cube units received from the LMF.

3. The RAN transmits to the terminal at least one of the information previously received and set from the OAM (e.g., cube map information including a cube ID list) and auxiliary data required to measure the location of the terminal in cube units received from the AMF. do.

The RAN transmits the above-described information to the UE in two ways as follows. The RAN can periodically broadcast the information by including it in a broadcast message. Alternatively, when the RAN transmits an on-demand system information block (SIB) message including a cube-level positioning or cube-level mobility management indicator or flag to the RAN, the RAN's response message includes the auxiliary data and sends the RAN to the RAN. can be sent to.

4. The terminal calculates the location coordinates of the terminal through terminal location measurement/calculation using at least one of the information received from the RAN, the GPS module mounted inside the terminal, and the sensor, and compares it with the cube map information to determine where the terminal is located. Decide on a cube. The terminal may perform an operation to transmit the corresponding cube ID to the RAN and AMF.

Specifically, if the cube ID hiding indicator is not set in the USIM, or guide information related to cube ID transmission is not received from the RAN, or if the terminal does not directly support cube ID concealment, the terminal determines in the previous step. You can avoid concealing the cube ID and not include it in the initial registration request.

5. The terminal provides AMF with a terminal identifier and an indicator related to support of fine-grained mobility management (fine-grained MM support indication) or an indicator related to support of cube-level mobility management (cube-level MM support indication) or cube-level mobility management support. At least one of the UE capabilities to support cube-level MM may be included and transmitted in the registration request message.

6. AMF performs authentication and security-related procedures in conjunction with the terminal, AUSF, and UDM based on the information received from the terminal. UDM can inform AMF of information about whether fine-grained MM or cube-level MM is supported (or allowed) for the corresponding terminal.

7. If AMF successfully performs the mutual authentication process with the terminal in the previous step, it sends a NAS security mode command to the terminal. At this time, if the AMF receives a fine-grained MM support indication or cube-level MM support indication or UE capability to support cube-level MM from the terminal in step 5, the AMF sends a NAS security mode command to the terminal and requests a flag. The UE location or flag requesting cube ID can be transmitted together.

8. When the terminal receives the flag requesting UE location or flag requesting cube ID from AMF, it creates a NAS container containing the cube ID determined in step 4. The NAS container may include information that can be included in the registration request message, such as cube ID and terminal identifier. Additionally, the terminal can apply ciphering and integrity protection schemes to the corresponding NAS container.

9. The terminal transmits the NAS container containing the cube ID to AMF.

10. When the AMF receives the cube ID from the terminal, it can select the UDM and request subscriber information related to cube-level mobility management for the terminal. The UDM can also provide AMF with subscriber information indicating that the terminal is allowed to fine-grained mobility management or cube-level mobility management.

11. AMF can perform AM policy association using the cube ID received from UDM. For example, AMF may provide the PCF with the cube ID of the cube where the terminal is located and receive policy information that should be applied in the corresponding cube area from the PCF. Policy information that AMF receives from PCF may include at least one of the following:

- Cube-level mobility restriction or service area restriction (allowed cube ID list, non-allowed cube ID list)

- Cube unit RFSP (RAT Frequency Selection Priority) Index value: RAT Frequency Selection Priority value set for the cube area, may correspond to subscriber profile ID for RAT/Frequency Priority

- Per cube UE-AMBR (aggregate maximum bitrate) or UE Slice-MBR (maximum bitrate)

When the AMF receives an AM policy including the cube-level RFSP Index from the PCF, it transfers the RFSP Index value to the RAN, and the RAN can perform RAT/Frequency selection based on RAT Frequency selection priority. Additionally, AMF can provide the RAN with a cube ID that matches the location of the terminal.

12. AMF transmits to the terminal at least one of the cube ID (de-concealed cube ID) obtained from UDM, reporting triggering condition (list of neighbor cube ID list), and flag to perform cube-level mobility tracking.

After step 10, the terminal checks whether the cube ID received from AMF matches the cube ID determined in step 4 in the terminal, and the cube area identified by the cube ID included in the cube ID list included in the reporting triggering condition provided by AMF Monitor whether it is out of bounds. This monitoring can be performed through UE-based positioning as in step 4. When the terminal leaves the cube area included in the cube ID list included in the reporting triggering condition and enters a new cube area, it re-registers with AMF and transmits the corresponding cube ID.

FIG. 5 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure. Figure 5 specifically explains the LMF-based method in relation to the cube-level mobility management procedure.

0. As in the embodiment described above in FIGS. 3 and 4, the OAM system can set cube map information to network entities (or functions) such as RAN, AMF, and LMF. Depending on the operator policy or the method of calculating the location of the terminal to determine the cube ID of the cube area where the terminal is located, cube map information may not be set in the RAN. For example, when using a method of determining the cube ID by finally calculating the location of the terminal in the network (eg, LMF), cube map information may be set only in the AMF and LMF and not in the RAN.

1. LMF transmits or provides AMF with auxiliary data (or auxiliary information) necessary for LMF-based cube unit terminal location measurement. This auxiliary data (or information) refers to information necessary to measure the location of the UE in the UE or RAN, and information on at least one of the following may be included in the auxiliary data (or information).

[TAI, Cell ID, TA-specific cube map information, cell-specific cube map information, DL-PRS configuration information for the transmitter/receiver point(s) of the RAN, SSB for RAN TRPs, spatial direction information of the DL -Geographic coordinate information for PRS and TRPs]

The conditions under which LMF provides such auxiliary data (or information) may be as follows. The LMF receives assistance data requests from the AMF, receives requests from external application functions (via NEF), or when the LMF's service area overlaps with the cube-level mobility management area, the LMF provides assistance to the AMF within the LMF service area. Data can be provided.

2. AMF transmits auxiliary data required for LMF-based cube unit UE location measurement received from LMF to RAN. At this time, the AMF may not provide cube map information (TA-specific cube map information and cell-specific cube map information) among the information received from the LMF to the RAN. For example, when using LMF-based positioning, AMF may not provide cube map information to the RAN.

3. The RAN transmits to the UE the auxiliary data required for LMF-based cube level UE location measurement received from the AMF.

The RAN transmits the above-described information to the UE in two ways as follows. The RAN can periodically broadcast the information by including it in a broadcast message. Alternatively, when the RAN transmits an on-demand system information block (SIB) message including a cube-level positioning or cube-level mobility management indicator or flag to the RAN, the RAN's response message includes the auxiliary data and sends the RAN to the RAN. can be sent to.

4. The terminal uses at least one of the information received from the RAN, the GPS module mounted inside the terminal, and the sensor to generate measurement values necessary for calculating the terminal location (measurement values necessary to determine the location of the terminal in the LMF). The terminal may perform an operation to transmit the corresponding measurement value to the LMF through RAN and AMF.

Specifically, the terminal performs concealment of the generated measurement values using the home network public key set in the terminal, thereby creating a concealed UE measurement. For example, if the UE measurement hidden indicator is set in the USIM within the terminal, the terminal can calculate and generate a concealed UE measurement using the home network public key stored in the USIM. If concealed UE measurement is not set in USIM, the UE can encrypt the measurement value using another encryption method.

5. The terminal transmits the generated concealed UE measurement to AMF. The UE can transmit the concealed UE measurement by including it in the registration request message. When the UE transmits concealed UE measurement to the AMF, the UE indicates the method by which the UE encrypted the measurement value (UE measurement) or the UE measurement concealment method (for example, a fine grained MM support indication) along with an indicator related to support for fine-grained mobility management (fine grained MM support indication). For example, whether a home network public key is used, encryption scheme information, etc.), and at least one of a terminal identifier may be provided.

6. AMF can transmit the concealed UE measurement, UE measurement concealment method, terminal identifier, and fine grained MM support indication received from the terminal to the LMF. Additionally, the AMF can check whether fine grained MM is supported for the terminal by checking the subscriber information of the terminal before transmitting the corresponding information to the LMF. If, as a result of AMF confirmation, the terminal does not support segmented MM, the following operations may not be performed.

7. The LMF receives the received concealed UE measurement and, if the UE measurement concealment method uses the home network public key, can perform a de-concealment request while transmitting the concealed UE measurement to the UDM along with the terminal identifier.

8, 9. The UDM can check whether the LMF's request is permitted, perform de-concealment, and then transmit the UE measurement value (de-concealed UE measurement) along with the UE identifier to the LMF.

NOTE: The operations of steps 6 through 9 may follow a modified procedure as follows: Instead of the AMF transmitting concealed UE measurement to the LMF, the AMF can transmit a de-concealment request to the UDM and obtain de-concealed UE measurement from the UDM. AMF can transmit de-concealed UE measurement values to LMF.

10. LMF calculates the location of the terminal using the acquired UE measurement value (de-concealed UE measurement) and cube map information, and determines the cube ID of the cube area where the terminal is located.

11. The LMF transmits the cube ID (cube ID of the cube area where the terminal is located) determined in the previous operation to the AMF.

12. AMF may provide the received cube ID to the RAN and perform AM policy enforcement for the corresponding terminal as in step 9 of the embodiment described in FIG. 3 above.

13. AMF transmits the acquired cube ID (de-concealed cube ID), reporting triggering condition (list of neighbor cube ID list), and flag to perform cube-level mobility tracking to the terminal. The terminal checks whether the cube ID received from AMF matches the cube ID determined in step 4 in the terminal. The terminal monitors whether it leaves the cube area identified by the cube ID included in the cube ID list included in the reporting triggering condition provided by AMF, and when it detects that it leaves the area, it sends the terminal measurement value to AMF as in the previous operations. (After initial registration, when transmitting terminal measurement values, the concealment operation performed in step 4 may not be performed).

FIG. 6 is a diagram illustrating a procedure for managing the mobility of a terminal based on a detailed location in relation to an embodiment proposed in this disclosure. Figure 6 specifically explains operations after the NAS security mode control procedure is completed in relation to the LMF-based mobility management procedure.

0. As in the embodiment described in FIGS. 3 and 4, the OAM system can set cube map information to network entities (or functions) such as RAN, AMF, and LMF. Depending on the operator policy or the method of calculating the location of the terminal to determine the cube ID of the cube area where the terminal is located, cube map information may not be set in the RAN. For example, when using a method of determining the cube ID by finally calculating the location of the terminal in the network (eg, LMF), cube map information may be set only in the AMF and LMF and not in the RAN.

1. The terminal provides AMF with a terminal identifier and an indicator related to support of fine-grained mobility management (fine-grained MM support indication) or an indicator related to support of cube-level mobility management (cube-level MM support indication) or cube-level mobility management support. At least one of the UE capabilities to support cube-level MM may be included and transmitted in the registration request message.

2. AMF performs the authentication procedure in conjunction with the terminal, AUSF, and UDM based on the information received from the terminal.

3. After completing the authentication process, AMF performs the terminal and NAS security mode setting process.

4. If the information received from the terminal includes fine-grained MM support indication or cube-level MM support indication or UE capability to support cube-level MM, AMF allows fine-grained MM or cube-level MM for the terminal. Subscriber information related to availability can be obtained from UDM. At this time, UDM can provide AMF whether to allow fine-grained MM or cube-level MM based on subscriber information.

5. AMF confirms that it allows fine-grained MM or cube-level MM based on information received from UDM or subscriber information, and provides LMF with a terminal identifier in the cube-level positioning request message indicating that cube-level MM is allowed. It is transmitted including at least one of information, the cell where the terminal is currently located, or TA information.

6. The LMF performs a cube-level positioning operation to specify (or confirm) the location of the terminal in cube units at the request of the AMF. For example, the LMF may perform the operations described in steps 1, 2, and 3 of the embodiment described in FIG. 3 and transmit cube map information and auxiliary data necessary to measure the location of the terminal on a cube basis to the RAN and the terminal.

The terminal may measure the terminal location, determine a cube ID corresponding to the location, and provide it to the LMF, as in the operation described in step 4 of the embodiment described in FIG. 3 (or, unlike the operation of the embodiment described in FIG. 3, The terminal may transmit the cube ID to the LMF through AMF by including it in the NAS container without performing separate concealment for the cube ID). As another example, the LMF performs the operations described in steps 1, 2, and 3 of the embodiment of Figure 5, and the terminal generates measurement values required for position calculation (measurement values necessary to determine the location of the terminal in the LMF) and LMF It can be sent to (via AMF).

7. The LMF determines the cube ID corresponding to the location of the terminal through the cube ID obtained from the terminal in the previous step or the measurement value required for position calculation, and transmits the cube ID to the AMF.

8. AMF can perform AM policy using the cube ID received from LMF. For example, AMF may provide the PCF with the cube ID of the cube where the terminal is located and receive policy information that should be applied in the corresponding cube area from the PCF. Policy information that AMF may receive from PCF may include:

- Cube-level mobility restriction or service area restriction (allowed cube ID list, non-allowed cube ID list)

- Cube unit RFSP (RAT Frequency Selection Priority) Index value: RAT Frequency Selection Priority value set for the cube area, may correspond to subscriber profile ID for RAT/Frequency Priority

- Per cube UE-AMBR (aggregate maximum bitrate) or UE Slice-MBR (maximum bitrate)

When the AMF receives an AM policy including the cube-level RFSP Index from the PCF, it transfers the RFSP Index value to the RAN, and the RAN can perform RAT/Frequency selection based on RAT Frequency selection priority. Additionally, AMF can also provide the RAN with a cube ID that matches the location of the terminal.

9. AMF transmits the cube ID (de-concealed cube ID) obtained from LMF, reporting triggering condition (list of neighbor cube ID list), and flag to perform cube-level mobility tracking to the terminal. The AMF may also transmit a reporting triggering condition to the LMF and make a subscribe request to the cube-level UE mobility tracking notification service that receives notification when the UE location measurement value performed by the LMF meets the reporting triggering condition.

After step 9, the terminal checks whether the cube ID received from AMF matches the cube ID determined in step 6 in the terminal, and the cube area identified by the cube ID included in the cube ID list included in the reporting triggering condition provided by AMF Monitor whether it is out of bounds. The terminal can perform monitoring through LMF and cube-level positioning of the terminal as in step 6. When the terminal or LMF leaves the cube area included in the cube ID list included in the reporting triggering condition and enters a new cube area, AMF transmits a new cube ID. For example, the UE may transmit a registration request message including a new cube ID to the AMF, and the LMF may transmit a cube-level UE mobility tracking notification message including a new cube ID to the AMF.

Combinations and modifications of specific operations of the various embodiments described above may occur in each device. In the method of determining the cube ID corresponding to the terminal location, the terminal directly calculates the location of the terminal using cube map information provided by RAN, AMF, or LMF and auxiliary information required for cube-level terminal location measurement and matches the location of the terminal. You can determine the cube ID.

Alternatively, the terminal may provide measurement values that require location calculation to the RAN or LMF, and the location and cube ID of the terminal may be determined by the RAN or LMF.

In a method for a terminal to transmit a cube ID corresponding to the terminal location or a measurement value required to calculate the terminal location, the terminal performs concealment of the information and then transmits it to the AMF by including it in the initial registration request message, or performs a separate concealment operation. After completing the NAS security mode setting procedure without performing any additional steps, it can be transmitted by including it in the NAS container. In this regard, the AMF immediately uses the cube ID received from the terminal or the measurement value required to calculate the terminal location (using the cube ID for AM policy enforcement or transmitting the measurement value to the LMF to obtain the cube ID) or provided by the UDM You can use the de-concealment service to obtain and use the de-concealed cube ID or measurement value.

Figure 7 is a diagram showing the structure of a terminal according to embodiments of the present disclosure.

As shown in FIG. 7, the terminal of the present disclosure may include a transceiver 710, a memory 720, and a control unit (or processor 730). The terminal's control unit 730, transceiver unit 710, and memory 720 may operate according to the above-described terminal communication method. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the aforementioned components. In addition, the control unit 730, the transceiver unit 710, and the memory 720 may be implemented in the form of a single chip.

The transmitting/receiving unit 710 is a general term for the terminal's receiving unit and the terminal's transmitting unit, and can transmit and receive signals to and from a base station or network entity. Signals transmitted and received from the base station may include control information and data. To this end, the transceiver 710 may be composed of an RF (radio frequency) transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 710, and the components of the transceiver 710 are not limited to the RF transmitter and RF receiver.

Additionally, the transceiver 710 may include a wired or wireless transceiver and may include various components for transmitting and receiving signals. Additionally, the transceiver 710 may receive a signal through a wireless channel and output it to the control unit 730, and transmit the signal output from the control unit 730 through a wireless channel. Additionally, the transceiver 710 may receive a communication signal and output it to the control unit 730, and transmit the signal output from the control unit 730 to a base station or network entity through a wired or wireless network.

The memory 720 can store programs and data necessary for operation of the terminal. Additionally, the memory 720 may store control information or data included in signals obtained from the terminal. The memory 720 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The control unit 730 can control a series of processes so that the terminal can operate according to the above-described embodiment of the present disclosure. The control unit 730 may include at least one processor. For example, the control unit 730 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

Figure 8 is a diagram showing the structure of a base station according to embodiments of the present disclosure. The base station shown in FIG. 8 may correspond to the RAN node previously described in FIG. 1.

As shown in FIG. 8, the base station of the present disclosure may include a transceiver 810, a memory 820, and a control unit (or processor, 830). The control unit 830, transceiver unit 810, and memory 820 of the base station may operate according to the above-described base station communication method. However, the components of the base station are not limited to the above examples. For example, a base station may include more or fewer components than those described above. According to one embodiment, the base station of FIG. 8 may be implemented with the overall functions separated into CU and DU. In this case, the CU and DU may each perform some functions performed by the base station of FIG. 8. In addition, the control unit 830, transceiver 810, and memory 820 of FIG. 8 may be implemented in the form of a single chip.

The transceiving unit 810 is a general term for the receiving unit of the base station and the transmitting unit of the base station, and can transmit and receive signals to and from a terminal and/or network entity. At this time, the transmitted and received signals may include control information and data. To this end, the transceiver 810 may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 810, and the components of the transceiver 810 are not limited to the RF transmitter and RF receiver. The transceiver 810 may include a wired or wireless transceiver and may include various components for transmitting and receiving signals.

Additionally, the transceiver 810 may receive a signal through a communication channel (eg, a wireless channel) and output it to the control unit 830, and transmit the signal output from the control unit 830 through the communication channel. Additionally, the transceiver 810 may receive a communication signal, output it to a processor, and transmit the signal output from the processor to a terminal or network entity through a wired or wireless network.

The memory 820 can store programs and data necessary for the operation of the base station. Additionally, the memory 820 may store control information or data included in signals obtained from the base station. The memory 820 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The control unit 830 can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. The control unit 830 may include at least one processor. Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

FIG. 9 is a diagram illustrating the structure of a network function (or network entity) according to embodiments of the present disclosure. The network function (or network entity) shown in FIG. 9 may correspond to various nodes of the core network previously described in FIG. 1.

As shown in FIG. 9, a network function (or network entity) of the present disclosure may include a transceiver 910, a memory 920, and a control unit (or processor, 930). The control unit 930, transceiver unit 910, and memory 920 of the network function (or network entity) may operate according to the communication method of the network function (or network entity) described above. However, the components of the network function (or network entity) are not limited to the examples described above. For example, a network function (or network entity) may include more or fewer components than those described above.

The transceiving unit 910 is a general term for the receiving unit of a network function (or network entity) and the transmitting unit of a base station, and can transmit and receive signals with a terminal, a base station, and/or other network functions (or network entities). At this time, the transmitted and received signals may include control information and data. To this end, the transceiver 910 can communicate with nodes of the core network through a wired or wireless transceiver. However, this is only an example of the transceiver 910, and the components of the transceiver 910 include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, low-noise amplifies the received signal, and down-converts the frequency. It may be composed of an RF receiver, etc., and may include various configurations for transmitting and receiving signals.

In addition, the transceiver 910 receives a signal through a communication channel (for example, a wireless channel or a core network channel) and outputs it to the control unit 930, and transmits the signal output from the control unit 930 through the communication channel. Can be transmitted. Additionally, the transceiver unit 910 may receive a communication signal and output it to the control unit 930, and transmit the signal output from the control unit 930 to a terminal, base station, or network entity through a wired or wireless network.

The memory 920 may store programs and data necessary for the operation of a network function (or network entity). Additionally, the memory 920 may store control information or data included in signals obtained from a network function (or network entity). The memory 920 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The control unit 930 may control a series of processes so that a network function (or network entity) can operate according to the above-described embodiment of the present disclosure. The control unit 930 may include at least one processor. Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

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

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program may be operated through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

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

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure. For example, part or all of some embodiments may be combined with part or all of one or more other embodiments, and it is natural that the form of such combination also corresponds to the embodiments proposed in 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 patent claims described later, but also by the scope of the claims and their equivalents.

In the detailed description of the present disclosure, specific embodiments have been described, but of course, 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 patent claims described later, but also by the scope of this patent claim and equivalents.

Claims (15)

1. In a wireless communication system, an access mobility and management function (AMF) node is,

   transceiver; and

   Includes a controller coupled to the transceiver,

   The controller is,

   Receive setting information for setting at least one cube associated with a three-dimensional space within a cell,

   Receive auxiliary information for location measurement from a location management function (LMF) node,

   Transmitting auxiliary information for location measurement to the terminal,

   From the terminal, receive concealed information related to location measurement of the terminal,

   Based on hidden information related to location measurement of the terminal, identify the identifier (ID) of the cube related to the terminal,

   Determine whether it is allowed to apply a mobility management policy based on the identifier of the cube to the terminal, and

   An AMF node configured to transmit information about the mobility management policy to the terminal.
2. In claim 1,

   Concealed information related to location measurement of the terminal includes a registration request message including an identifier of a cube hidden by the terminal and an indicator requesting mobility management based on the at least one cube, and

   The identifier of the cube hidden by the terminal is an AMF node that is de-concealed by a unified data management (UDM) node.
3. The method of claim 1, wherein the controller:

   Receiving, from the terminal, a registration request message including an indicator requesting mobility management based on the at least one cube,

   Perform an authentication procedure for the terminal based on the registration request message, and

   Further configured to transmit a non-access stratum (NAS) command message to the terminal based on the result of the authentication procedure,

   Concealed information related to location measurement of the terminal is an AMF node including a NAS container containing an identifier of a cube associated with the terminal determined by the terminal.
4. In claim 1,

   Concealed information related to location measurement of the terminal includes a registration request message including a result of location measurement hidden by the terminal and an indicator requesting mobility management based on the at least one cube,

   The controller is,

   transmitting the results of location measurement hidden by the terminal to the LMF node, and

   AMF node further configured to receive, from the LMF node, an identifier of a cube associated with the terminal determined based on a result of the location measurement.
5. The method of claim 1, wherein the controller:

   Receiving, from the terminal, a registration request message including an indicator requesting mobility management based on the at least one cube,

   Perform an authentication procedure for the terminal based on the registration request message, and

   Further configured to transmit a non-access stratum (NAS) command message to the terminal based on the result of the authentication procedure,

   The identifier of the cube associated with the terminal is an AMF node determined by the LMF based on the results of location measurement of the terminal.
6. In claim 1,

   The hidden information related to the location measurement of the terminal is an AMF node generated based on the identifier of the cube related to the terminal or the result of the location measurement of the terminal, and the home network public key.
7. In a wireless communication system, a terminal (user equipment, UE) is,

   transceiver; and

   Includes a controller coupled to the transceiver,

   The controller is,

   Receive setting information for setting at least one cube associated with a three-dimensional space within a cell from an access mobility and management function (AMF),

   From the AMF, receive auxiliary information for location measurement,

   Based on the setting information and the auxiliary information, generate concealed information related to location measurement of the terminal,

   To the AMF, transmit concealed information related to location measurement of the terminal, and

   A terminal configured to receive, from the AMF, information about a mobility management policy created based on concealed information related to location measurement of the terminal.
8. In claim 7,

   Concealed information related to location measurement of the terminal includes an identifier of a cube hidden by the terminal and an indicator requesting mobility management based on the at least one cube.
9. In claim 7,

   Concealed information related to location measurement of the terminal includes a result of location measurement hidden by the terminal and an indicator requesting mobility management based on the at least one cube.
10. In a wireless communication system, the method performed by an access mobility and management function (AMF) node is:

    Receiving setting information for setting at least one cube associated with a three-dimensional space within a cell;

    Receiving auxiliary information for location measurement from a location management function (LMF) node;

    Transmitting auxiliary information for location measurement to a terminal;

    Receiving concealed information related to location measurement of the terminal from the terminal;

    Identifying an identifier (ID) of a cube related to the terminal based on hidden information related to location measurement of the terminal;

    determining whether it is permitted to apply a mobility management policy based on the identifier of the cube to the terminal; and

    A method comprising transmitting information about the mobility management policy to the terminal.
11. In claim 10,

    Concealed information related to location measurement of the terminal includes a registration request message including an identifier of a cube hidden by the terminal and an indicator requesting mobility management based on the at least one cube, and

    A method in which the identifier of the cube hidden by the terminal is de-concealed by a unified data management (UDM) node.
12. The method of claim 10, wherein the method:

    Receiving, from the terminal, a registration request message including an indicator requesting mobility management based on the at least one cube;

    performing an authentication procedure for the terminal based on the registration request message; and

    Further comprising transmitting a non-access stratum (NAS) command message to the terminal based on the result of the authentication procedure,

    Concealed information related to location measurement of the terminal includes a NAS container containing an identifier of a cube associated with the terminal determined by the terminal.
13. In claim 10,

    Concealed information related to location measurement of the terminal includes a registration request message including a result of location measurement hidden by the terminal and an indicator requesting mobility management based on the at least one cube,

    The method is:

    Transmitting the results of location measurement hidden by the terminal to the LMF node; and

    The method further comprising receiving, from the LMF node, an identifier of a cube associated with the terminal determined based on a result of the location measurement.
14. The method of claim 10, wherein the method:

    Receiving, from the terminal, a registration request message including an indicator requesting mobility management based on the at least one cube;

    performing an authentication procedure for the terminal based on the registration request message; and

    Further comprising transmitting a non-access stratum (NAS) command message to the terminal based on the result of the authentication procedure,

    A method in which the identifier of the cube associated with the terminal is determined by the LMF based on the results of location measurement of the terminal.
15. In claim 10,

    A method in which hidden information related to location measurement of the terminal is generated based on an identifier of a cube related to the terminal or a result of location measurement of the terminal, and a home network public key.

Images