Method and apparatus for transmitting or receiving data in a wireless communication system

Abstract

The present disclosure includes a method for using a location-based service performed by a terminal. The method includes: receiving a radio resource control (RRC) message including protocol information related to the location of the terminal from a base station; acquiring location-related information of the terminal based on the RRC message; and sending a response message including location-related information to the base station, wherein the protocol information is generated by a first location management function (LMF) with a logical connection within the base station or a second LMF located in a core network based on request information for a location-based service received from a client server.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting and receiving data in a wireless communication system. Background Art

[0002] In order to meet the growing demand for wireless data services after the commercialization of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) communication system or a quasi-5G communication system. Therefore, the 5G communication system or the quasi-5G communication system is called a "super 4G network communication system" or a "late evolution (LTE) system". In order to achieve high data rates, it is considered to implement the 5G communication system in an ultra-high frequency band (millimeter wave (mmW)) (e.g., 60GHz). In order to reduce the path loss of radio waves and increase the transmission distance of radio waves in the ultra-high frequency band, for the 5G communication system, technologies such as beamforming, large-capacity multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas are discussed. In addition, in order to improve the network of the system, in the 5G communication system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, collaborative multi-point (CoMP), and interference elimination are being developed. In addition, in 5G communication systems, advanced coding and modulation (ACM) schemes such as hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM), modulation (FQAM) or sliding window superposition coding (SWSC), as well as enhanced network access schemes such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) or sparse code multiple access (SCMA) are being developed.

[0003] The Internet is evolving from a human-centered connection network, through which humans create and consume information, to an Internet of Things (IoT) network, through which distributed elements such as objects exchange and process information. Internet of Everything (IoE) technology is also maturing, and IoE technology is a combination of IoT technology and big data processing technology through connection with cloud servers. In order to realize IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology and security technology are required, so technologies for inter-object connection such as sensor networks, machine-to-machine (M2M) communication or machine type communication (MTC) have been studied recently. In the IoT environment, intelligent Internet technology (IT) services can be provided that collect and analyze data generated by connected objects and create new value in human life. IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services through the fusion and integration of existing information technology (IT) and various industries.

[0004] Accordingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M communications, or MTC are implemented by 5G communication technologies such as beamforming, MIMO, or array antennas. The application of cloud RAN as a big data processing technology can also serve as an example of the fusion of 5G technology and IoT technology.

[0005] As described above, since various services can be provided according to the development of the mobile communication system, a method for efficiently providing the service is required. Summary of the invention

[0006] Technical issues

[0007] The disclosed embodiments provide an apparatus and method capable of efficiently providing services in a mobile communication system.

[0008] Problem Solution

[0009] According to an embodiment of the present disclosure, a method for using location-based services performed by a terminal includes: receiving a radio resource control (RRC) message from a base station, the RRC message including protocol information related to the location of the terminal; obtaining location-related information of the terminal based on the RRC message; and sending a response message including location-related information to the base station, wherein the protocol information is generated by a first location management function (LMF) with a logical connection within the base station or a second LMF located in a core network based on request information for location-based services received from a client server.

[0010] When the terminal is RRC connected to the base station or in an inactive state, the protocol information can be generated by the first LMF, and when the terminal is in an idle state, the protocol information can be generated by the second LMF.

[0011] The RRC message may include an indicator corresponding to the LMF generating the protocol information, or include the protocol information in an Information Element (IE) varying according to the LMF.

[0012] The method may also include determining which LMF generates the protocol information from the first LMF or the second LMF based on the RRC message, wherein the response message is generated to include an indicator, or the protocol information is included in the IE.

[0013] According to an embodiment of the present disclosure, a method for providing location-based services performed by a base station includes: receiving request information for location-based services from an access management function (AMF); receiving protocol information about the request information from a first location management function LMF with a logical connection within the base station; sending an RRC message to a terminal based on the protocol information; receiving a response message including location-related information of the terminal based on the RRC message from the terminal; and sending a response message to the AMF.

[0014] The request information may include identification information about the terminal, or information about a base station to which the terminal is connected.

[0015] The RRC message may include an indicator corresponding to the first LMF, or include protocol information in an information element (IE) corresponding to the first LMF.

[0016] According to an embodiment of the present disclosure, a terminal for using a location-based service includes: a transceiver; and at least one processor, which is connected to the transceiver and configured to receive a radio resource control (RRC) message including protocol information related to the location of the terminal from a base station, obtain location-related information of the terminal based on the RRC message, and send a response message including location-related information to the base station, wherein the protocol information is generated by a first location management function (LMF) with a logical connection within the base station or a second LMF located in a core network based on request information for location-based services received from a client server.

[0017] When the terminal is RRC connected to the base station or in an inactive state, the protocol information may be generated by the first LMF, and when the terminal is in an idle state, the protocol information is generated by the second LMF.

[0018] The RRC message may include an indicator corresponding to the LMF generating the protocol information, or include the protocol information in an information element (IE) varying according to the LMF.

[0019] The at least one processor may be further configured to determine which LMF generates the protocol information from the first LMF or the second LMF based on the RRC message, wherein the response message is generated to include an indicator, or to include the protocol information in an IE.

[0020] According to an embodiment of the present disclosure, a base station for providing location-based services includes: a transceiver; and at least one processor, which is connected to the transceiver and configured to receive request information for location-based services from an access management function (AMF), receive protocol information for the request information from a first location management function (LMF) having a logical connection within the base station, send a radio resource control (RRC) message to a terminal based on the protocol information, receive a response message including location-related information of the terminal based on the RRC message from the terminal, and send the response message to the AMF.

[0021] The request information may include identification information about the terminal, or information about a base station to which the terminal is connected.

[0022] Disclosure of beneficial effects

[0023] The disclosed embodiments provide an apparatus and method capable of efficiently providing services in a mobile communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1a is a diagram showing the structure of a Long Term Evolution (LTE) system according to some embodiments of the present disclosure.

[0025] Figure 1b is a diagram illustrating a radio protocol architecture in an LTE system according to some embodiments of the present disclosure.

[0026] Figure 1c is a diagram showing a structure of a next generation mobile communication system according to some embodiments of the present disclosure.

[0027] Figure 1d is a diagram illustrating a radio protocol architecture of a next generation mobile communication system according to some embodiments of the present disclosure.

[0028] Figure 1e is a block diagram illustrating an internal structure of a terminal according to some embodiments of the present disclosure.

[0029] Figure 1f is a block diagram illustrating a configuration of a New Radio (NR) base station according to some embodiments of the present disclosure.

[0030] Figure 1g is a block diagram illustrating the architecture of a local location management function (LMF) according to some embodiments of the present disclosure.

[0031] Figure 1hA protocol stack for communication between a user equipment (UE) and a Next Generation Radio Access Network (NG RAN) node including a local LMF according to some embodiments of the present disclosure is shown.

[0032] Figure 1i is a diagram showing a protocol stack when a UE and a core network (CN) LMF communicate with each other through an LTE location protocol (LPP) in LTE and NR according to some embodiments of the present disclosure.

[0033] Figure 1j is a diagram illustrating an LPP process through a CN LMF according to some embodiments of the present disclosure.

[0034] Figure 1k is a flow chart when using a local location management function (LLMF) according to some embodiments of the present disclosure.

[0035] Figure 1l A situation is shown in which an access management function (AMF) determines whether to use LLMF or CN LMF according to some embodiments of the present disclosure.

[0036] Figure 1m It shows a case where the AMF determines whether to use LLMF or CN LMF according to some embodiments of the present disclosure.

[0037] Figure 1n It is shown that according to some embodiments of the present disclosure, when the AMF receives a location service (LCS) request from an external client, the AMF uses the LLMF regardless of the state of the UE.

[0038] Figure 2a is a diagram showing the structure of an LTE system according to some embodiments of the present disclosure.

[0039] Figure 2b is a diagram illustrating a radio protocol architecture of an LTE system according to some embodiments of the present disclosure.

[0040] Figure 2c is a diagram showing a structure of a next generation mobile communication system according to some embodiments of the present disclosure.

[0041] Figure 2d is a diagram illustrating a radio protocol architecture of a next generation mobile communication system according to some embodiments of the present disclosure.

[0042] Figure 2e is a block diagram illustrating an internal structure of a terminal according to some embodiments of the present disclosure.

[0043] Figure 2f is a block diagram showing the configuration of an NR base station according to some embodiments of the present disclosure.

[0044] Figure 2g is a signal flow diagram during secondary cell (Scell) addition or modification in carrier aggregation according to some embodiments of the present disclosure.

[0045] Figure 2h is a flow chart illustrating the operation of a UE during Scell ​​addition / modification according to some embodiments of the present disclosure.

[0046] Figure 2i is a detailed flow chart illustrating the operation of a terminal during Scell ​​addition / modification according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0047] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Although the present disclosure is described, detailed descriptions of related well-known functions or configurations that may obscure the main points of the present disclosure are omitted. The terms used herein are defined in consideration of the functions in the present disclosure, but these terms may vary according to the intentions of users or operators, precedents, etc. Therefore, the terms used herein must be defined based on the meaning of the terms and the descriptions in the entire specification.

[0048] In the following, for the convenience of explanation, terms for identifying access nodes, terms indicating network entities, terms indicating messages, terms indicating interfaces between network entities, and terms indicating various identification information used in the present disclosure are exemplified. Therefore, the present disclosure is not limited to the terms described below, but other terms indicating objects having the same technical meaning may be used.

[0049] Hereinafter, for convenience of explanation, some terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard may be used. However, the present disclosure may not be limited to the above terms and names, and may also be applied to systems complying with other standards.

[0050] The advantages and features of the present disclosure and the methods for implementing the same will be apparent with reference to the embodiments of the present disclosure described in detail below in conjunction with the accompanying drawings. However, the present disclosure may be embodied in a number of different forms and should not be construed as being limited to the embodiments of the present disclosure described herein; rather, these embodiments of the present disclosure are provided to make the present disclosure thorough and complete, to fully convey the scope of the present disclosure to those of ordinary skill in the art, and the scope of the present disclosure is limited only by the appended claims. In this specification, the same reference numerals represent the same elements.

[0051] It should be understood that each block and combination of blocks in the flowchart can be implemented by computer program instructions. Since these computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate a device for implementing the functions specified in the flowchart block diagram. Since these computer program instructions can also be stored in a computer executable memory or a computer readable memory, which can guide the computer or other programmable data processing device to operate in a specific manner, the instructions stored in the computer executable memory or the computer readable memory can produce a product including an instruction device that implements the functions specified in the flowchart block diagram. Since the computer program instructions can also be loaded onto a computer or other programmable data processing device, a series of operating steps can be performed on a computer or other programmable data processing device to generate a computer executable process, and therefore the instructions executed on the computer or other programmable data processing device can provide steps for implementing the functions specified in the flowchart block diagram.

[0052] In addition, each block may represent a module, segment or portion of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions recorded in the blocks may not occur in the order shown. For example, depending on the functions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order.

[0053] The term "~ unit" used in the present embodiment refers to a software or hardware component that performs certain tasks, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "~ unit" does not mean to be limited to software or hardware. The term "~ unit" can be configured to be in an addressable storage medium or can be configured to operate one or more processors. Therefore, for example, "~ unit" may include components, such as software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided in components and "~ units" can be combined into fewer components and "~ units", or further separated into additional components and "~ units". In addition, components and "~ units" can be implemented to operate one or more central processing units (CPUs) in a device or a secure multimedia card. In addition, the unit in the embodiment may include one or more processors.

[0054] Although the present disclosure is described, detailed description of related well-known functions or configurations that may obscure the gist of the present disclosure is omitted. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0055] In the following, for the sake of convenience of explanation, terms used to identify access nodes, terms indicating network entities, terms indicating messages, terms indicating interfaces between network entities, and terms indicating various identification information used in the present disclosure are exemplified. Therefore, the present disclosure is not limited to the terms described below, but other terms indicating objects with the same technical meanings may be used. For example, in the following, a terminal may refer to a media access control (MAC) entity for each primary cell group (MCG) or secondary cell group (SCG) present in the terminal.

[0056] Hereinafter, for convenience of explanation, some terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard may be used. However, the present disclosure may not be limited to the terms and names and may also be applied to systems complying with other standards.

[0057] Hereinafter, a base station is an entity that performs resource allocation for a terminal, and may include at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. However, the present disclosure is not limited to the above embodiments.

[0058] Specifically, the present disclosure may be applied to 3GPP NR (5G mobile communication standard). In addition, the present disclosure may be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail commerce, security and safety-related services) based on 5G communication technology and Internet of Things (IoT) related technologies. In the present disclosure, for ease of explanation, eNB may be used interchangeably with gNB. That is, a base station described as an eNB may refer to a gNB. In addition, the term "terminal" may refer to other wireless communication devices as well as mobile phones, NB-IoT devices, and sensors.

[0059] Wireless communication systems have evolved beyond the voice-based services initially provided to broadband wireless communication systems that provide high-speed and high-quality packet data services using communication standards such as High Speed ​​Packet Access (HSPA) of the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), Advanced LTE (LTE-A), LTE-Pro, High Rate Packet Data (HRPD) of 3GPP2, Ultra Mobile Broadband (UMB), and 802.16e of the Institute of Electrical and Electronics Engineers (IEEE).

[0060] The LTE system, which is a representative example of a broadband wireless communication system, adopts an orthogonal frequency division multiplexing (OFDM) scheme for a downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme for an uplink (UL). The uplink is a wireless link through which a terminal (e.g., a user equipment (UE) or a mobile station (MS)) sends data or a control signal to a base station (e.g., an eNode B or a base station (BS)), and the downlink is a wireless link through which a base station sends data or a control signal to a terminal. In the multiple access scheme, time-frequency resources for carrying data or control information are allocated and operated in a manner to prevent resource overlap, that is, orthogonality is established between users so that the data or control information of each user can be identified.

[0061] As a future communication system after LTE, the 5G communication system should be able to freely reflect the various needs of users and service providers, and therefore should support services that meet various needs at the same time. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC).

[0062] According to some embodiments, eMBB may be intended to provide a higher data rate than that supported by LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 gigabits per second (Gbps) in the downlink and a peak data rate of 10Gbps relative to one base station in the uplink. In addition, the 5G communication system should be able to provide the terminal with an enhanced user-perceived data rate while providing the peak data rate. In order to meet this requirement, various transmission and reception technologies including further enhanced MIMO transmission technology must be improved in the 5G communication system. In addition, the LTE system sends signals by using a maximum transmission bandwidth of 20 megahertz (MHz) in a frequency band of 2 gigahertz (GHz). In comparison, the 5G communication system sends signals by using a frequency bandwidth wider than 20MHz in a frequency band of 3GHz to 6GHz or higher, so the data rate requirements necessary for the 5G communication system can be met.

[0063] In addition, in the 5G communication system, mMTC is considered to support application services such as the Internet of Things (IoT). In order for mMTC to effectively provide IoT, access to multiple terminals within a single cell, improved coverage of the terminal, increased battery time, reduced terminal costs, etc. may be required. IoT is attached to various sensors and various devices to provide communication functions, so it should be able to support multiple terminals within the cell (e.g., 1,000,000 terminals / km2). In addition, since the terminal supporting mMTC may be located in a shadow area that is not covered by the cell, such as in the basement of a building, a wider coverage may be required than other services provided by the 5G communication system. Since the terminal supporting mMTC should include an inexpensive terminal and it is difficult to frequently replace the battery of the terminal, a very long battery life (e.g., 10-15 years) may be required.

[0064] Finally, URLLC is a cellular-based wireless communication service for mission-critical purposes and can be used for remote control of robots or machines, industrial automation, drones, remote health care, emergency alerts, etc. Therefore, the communication provided by URLLC may have to provide very low latency (ultra-low latency) and very high reliability (ultra-high reliability). For example, services supporting URLLC should meet the requirements of an air interface latency of less than 0.5 milliseconds and a packet error rate of 10-5 or less at the same time. Therefore, for services supporting URLLC, the 5G system should provide a transmission time interval (TTI) that is smaller than that of other services, and may require a design for implementing wide resource allocation in the frequency band to ensure the reliability of the communication link.

[0065] Considering three services for a 5G communication system, namely, Embb, URLLC, and mMTC, they can be multiplexed and transmitted in one system. In this case, in order to meet the different needs of the services, different transmission and reception schemes and transmission / reception parameters can be used between the services. However, mMTC, URLLC, and eMBB are examples of different service types, and the service types applied by the present disclosure are not limited thereto.

[0066] In addition, although the embodiments of the present disclosure will be described based on LTE, LTE-A, LTE Pro or 5G (or NR, next generation mobile communication) systems, the embodiments of the present disclosure can be applied to other communication systems with similar technical backgrounds or channel types. In addition, the embodiments of the present disclosure can be applied to other communication systems through some modifications without departing from the scope of the present disclosure determined based on a person of ordinary skill in the art.

[0067] In the present disclosure, a method will be described for adding a region-based location management function server so that a terminal distinguishes between two entities corresponding to a location management function server in an existing core network and the added region-based location management function server, and uses different entities when necessary.

[0068] According to the disclosed embodiment, in a wireless communication system, a location management function server for determining a terminal location is located at a radio access network end, so when a base station uses a terminal location service, the waiting time can be reduced.

[0069] Figure 1a is a diagram showing an LTE system structure according to some embodiments of the present disclosure.

[0070] Reference Figure 1a The radio access network of the LTE system may include next generation base stations (hereinafter referred to as evolved Node Bs (ENBs), Node Bs or base stations) 1a-05, 1a-10, 1a-15 and 1a-20, a mobility management entity (MME) 1a-25 and a serving gateway (S-GW) 1a-30. A user terminal (hereinafter referred to as user equipment (UE) or terminal) 1a-35 may access an external network through the ENBs 1a-05 to 1a-20 and the S-GW 1a-30.

[0071] exist Figure 1a In the present invention, ENB 1a-05 to 1a-20 may correspond to an existing Node B of a Universal Mobile Telecommunications System (UMTS). The ENB may be connected to a UE 1a-35 via a wireless channel and may perform more complex functions than an existing Node B. In an LTE system, all user services including real-time services such as Voice over Internet Protocol (VoIP) may be served through a shared channel. Therefore, it may be necessary to collect state information of the UE such as buffer status, available transmission power status, channel status, etc. and schedule the device for such state information, and the ENB 1a-05 to 1a-20 may perform the function. One ENB may generally control multiple cells. For example, in order to achieve a data rate of 100Mbps, an LTE system may use orthogonal frequency division multiplexing (OFDM) as a radio access technology (RAT) on a bandwidth of, for example, 20MHz. In addition, the ENB may use an adaptive modulation and coding (AMC) scheme, which determines the modulation scheme and channel coding rate according to the channel status of the terminal. The S-GW 1a-30 is a device that provides data bearers and may generate or remove data bearers under the control of the MME 1a-25. The MME is a device that performs various control functions for terminals and a mobility management function and can be connected to a plurality of base stations.

[0072] Figure 1bis a diagram illustrating a radio protocol architecture in an LTE system according to some embodiments of the present disclosure.

[0073] Reference Figure 1b In each of the terminal and the ENB, the radio protocol of the LTE system may include a packet data convergence protocol (PDCP) 1b-05 / 1b-40, a radio link control (RLC) 1b-10 / 1b-35, and a medium access control (MAC) 1b-15 / 1b-30. PDCP may be responsible for operations such as IP header compression / decompression. The main functions of PDCP may be summarized as follows. However, the present disclosure is not limited to the following examples.

[0074] -Header compression and decompression: Robust Header Compression (ROHC) only

[0075] -Transfer user data

[0076] - In-sequence delivery of upper layer protocol data units (PDUs) during PDCP re-establishment for RLC Acknowledged Mode (AM)

[0077] - For separated bearers in Dual Connectivity (DC) (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0078] - Duplicate detection of lower layer service data units (SDUs) during PDCP re-establishment for RLC AM

[0079] - Retransmission of PDCP SDUs at handover and, for split bearers in DC, retransmission of PDCP PDUs during PDCP data recovery procedure for RLC AM

[0080] -Encryption and decryption

[0081] - Timer-based SDU discard in uplink

[0082] According to some embodiments, RLC 1b-10 or 1b-35 may reconfigure PDCP PDU with an appropriate size and may perform an automatic repeat request (ARQ) operation, etc. The main functions of RLC may be summarized as follows. However, the present disclosure is not limited to the following examples.

[0083] -Transmit upper layer PDU

[0084] -ARQ (error correction through ARQ (only for AM data transmission))

[0085] - Concatenation, segmentation and reassembly of RLC SDUs (only for Unacknowledged Mode (UM) and AM data transmission)

[0086] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0087] - Reordering of RLC data PDUs (only for UM and AM data transmission)

[0088] - Duplicate detection (for UM and AM data transmission only)

[0089] -Protocol error detection (for AM data transmission only)

[0090] -RLC SDU discard (only for UM and AM data transmission)

[0091] -RLC reconstruction

[0092] According to some embodiments, MAC 1b-15 or 1b-30 is connected to several RLC entities configured in one terminal, and can multiplex RLC PDU into MAC PDU and demultiplex RLC PDU from MAC PDU. The main functions of MAC can be summarized as follows. However, the present disclosure is not limited to the following examples.

[0093] - Mapping between logical channels and transport channels

[0094] - Multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) delivered to the physical layer on a transport channel, and demultiplexing MAC SDUs belonging to one or different logical channels from a transport block (TB) delivered from the physical layer on a transport channel

[0095] -Dispatch information report

[0096] - Hybrid ARQ (HARQ) (error correction via HARQ)

[0097] - Priority handling between logical channels of a UE

[0098] - Prioritization between UEs through dynamic scheduling

[0099] -Multimedia Broadcast Multicast Service (MBMS) service identifier

[0100] -Transmission format selection

[0101] -filling

[0102] According to some embodiments, the physical layer (PHY) 1b-20 or 1b-25 may channel encode and modulate higher layer data into OFDM symbols and send the OFDM symbols via a wireless channel, or may demodulate and channel decode OFDM symbols received via a wireless channel and transmit the channel-decoded OFDM symbols to a higher layer. However, the present disclosure is not limited to the following examples.

[0103] Figure 1c is a diagram showing a structure of a next generation mobile communication system according to some embodiments of the present disclosure.

[0104] Reference Figure 1c , the radio access network of the next generation mobile communication system (hereinafter referred to as NR or 5G) may include a next generation base station (hereinafter referred to as a new radio node B (NR gNB) or NR base station) 1c-10 and a new radio core network (NR CN) 1c-05. The new radio user equipment (NR UE) 1c-15 can access an external network via the NR gNB 1c-10 and the NR CN 1c-05.

[0105] exist Figure 1c In the present invention, NR gNB 1c-10 may correspond to an evolved Node B (eNB) of an existing LTE system. NR gNB is connected to NR UE 1c-15 via a wireless channel and may provide much better services than the existing Node B. In the next generation mobile communication system, all user services may be served through shared channels. Accordingly, a device for collecting status information of the UE such as buffer status, available transmission power status, channel status, etc. and scheduling such status information may be required, and NR gNB1c-10 may perform this function. One NR gNB may control multiple cells. In the next generation mobile communication system, in order to achieve high-speed data transmission compared to the current LTE system, a bandwidth larger than the current maximum bandwidth may be applied. In addition, beamforming technology may be additionally used as RAT together with OFDM.

[0106] In addition, according to some embodiments, the NR gNB can use an adaptive modulation and coding (AMC) scheme that determines the modulation scheme and channel coding rate according to the channel state of the terminal. NR CN 1c-05 can perform functions such as mobility support, bearer configuration, and quality of service (QoS) configuration. NR CN 1c-05 is a device that performs various control functions for the terminal and mobility management functions, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can interoperate with the existing LTE system, and the NR CN can be connected to the MME 1c-25 via a network interface. The MME can be connected to the eNB 1c-30, which is an existing base station.

[0107] Figure 1d is a diagram illustrating a radio protocol architecture of a next generation mobile communication system according to some embodiments of the present disclosure.

[0108] Reference Figure 1d, in each of the terminal and the NR base station, the radio protocol of the next-generation mobile communication system may include NR Service Data Adaptation Protocol (SDAP) 1d-01 / 1d-45, NR PDCP 1d-05 / 1d-40, NR RLC 1d-10 / 1d-35 and NR MAC 1d-15 / 1d-30.

[0109] According to some embodiments, the main functions of NR SDAP 1d-01 or 1d-45 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0110] -Transmission of user plane data

[0111] - Mapping between QoS flows and Data Radio Bearers (DRBs) for both downlink (DL) and uplink (UL)

[0112] -Mark QoS flow ID in DL and UL packets

[0113] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0114] For the SDAP entity, the terminal may be configured through a radio resource control (RRC) message as to whether to use the header of the SDAP entity or the function of the SDAP entity for each PDCP entity, bearer, or logical channel. In addition, when the SDAP header is configured, the 1-bit non-access stratum (NAS) reflection QoS configuration indicator and the 1-bit access stratum (AS) reflection QoS configuration indicator of the SDAP header may indicate that the terminal updates or reconfigures the mapping information between the QoS flows and data bearers for UL and DL. According to some embodiments, the SDAP header may include QoS flow ID information indicating QoS. According to some embodiments, the QoS information may be used as data processing priority and scheduling information for supporting smooth services.

[0115] According to some embodiments, the main functions of NR PDCP 1d-05 or 1d-40 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0116] -Header compression and decompression: ROHC only

[0117] -Transfer user data

[0118] - Deliver upper layer PDUs in sequence

[0119] - Out-of-order delivery of upper layer PDUs

[0120] - Reordering of received PDCP PDUs

[0121] - Duplicate detection of lower layer SDU

[0122] -Retransmitted PDCP SDU

[0123] -Encryption and decryption

[0124] - Timer-based SDU discard in uplink

[0125] In the above description, the reordering function of the NR PDCP entity may indicate a function of reordering the PDCP PDUs received from the lower layer based on the PDCP sequence number (SN). The reordering function of the NR PDCP entity may include a function of delivering data to a higher layer in a reordered order, a function of directly delivering data without considering the order, a function of reordering the order and recording the lost PDCP PDUs, a function of reporting the status of the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs.

[0126] According to some embodiments, the main functions of NR RLC 1d-10 or 1d-35 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0127] -Transmission of upper layer PDU

[0128] - In-sequence delivery of upper layer PDUs

[0129] - Out-of-order delivery of upper layer PDUs

[0130] ARQ (error correction through ARQ)

[0131] Concatenation, segmentation, and reassembly of RLC SDUs

[0132] - Re-segmentation of RLC data PDUs

[0133] - Reordering of RLC data PDUs

[0134] - Duplicate detection

[0135] -Protocol error detection

[0136] -RLC SDU discarded

[0137] -RLC reconstruction

[0138] In the above description, the in-sequence delivery function of the NR RLC entity may indicate a function of delivering RLC SDUs received from a lower layer to a higher layer in sequence. When an original RLC SDU is segmented into multiple RLC SDUs and received, the in-sequence delivery function of the NR RLC entity may include the functions of reassembling the RLC SDUs and delivering the RLC SDUs.

[0139] The in-sequence delivery function of the NR RLC entity may include a function of reordering the received RLC PDUs based on the RLC SN or the PDCP SN. In addition, the in-sequence delivery function of the NR RLC entity may include a function of reordering the sequence and recording the lost PDCP PDUs, a function of reporting the status of the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs.

[0140] When there are lost RLC SDUs, the in-sequence delivery function of the NR RLC entity may include the function of delivering only the RLC SDUs preceding the lost RLC SDUs in-sequence to higher layers.

[0141] Furthermore, when a certain timer expires, the in-sequence delivery functionality of the NR RLC entity may include the functionality of delivering in-sequence to higher layers all RLC SDUs received before a certain timer is started, despite the presence of lost RLC SDUs.

[0142] When a certain timer expires, the in-sequence delivery functionality of the NR RLC entity may include the functionality of delivering all RLC SDUs received so far in sequence to higher layers despite the presence of lost RLC SDUs.

[0143] The NR RLC entity may process the RLC PDUs in the order of reception without considering the order of SNs, and may deliver the processed RLC PDUs to the NR PDCP entity in an out-of-order delivery manner.

[0144] When the NR RLC entity receives segments, the NR RLC entity may receive segments stored in a buffer or to be received later, may reconfigure these segments into a complete RLC PDU, and may then deliver the RLC PDU to the NR PDCP entity.

[0145] The NR RLC entity may not include the cascading functionality, and this functionality may be performed by the NR MAC entity or may be replaced by the multiplexing functionality of the NR MAC entity.

[0146] In the above description, the out-of-order delivery function of the NR RLC entity may indicate a function of delivering the RLC SDU received from the lower layer directly to the higher layer regardless of the order. When one original RLC SDU is segmented into multiple RLC SDUs and received, the out-of-order delivery function of the NR RLC entity may include a function of reassembling the RLC SDU and delivering the RLC SDU. The out-of-order delivery function of the NR RLC entity may include a function of storing and sorting the RLC SN or PDCP SN of the received RLC PDU and recording the lost RLC PDU.

[0147] According to some embodiments, NR MAC 1d-15 or 1d-30 may be connected to several NRRLC entities configured in one terminal, and the main functions of NR MAC may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0148] - Mapping between logical channels and transport channels

[0149] -Multiplexing / demultiplexing of MAC SDU

[0150] -Dispatch information report

[0151] -HARQ (error correction through HARQ)

[0152] - Priority handling between logical channels of a UE

[0153] - Prioritization between UEs through dynamic scheduling

[0154] -MBMS service logo

[0155] -Transmission format selection

[0156] -filling

[0157] The NR PHY 1d-20 or 1d-25 may channel encode higher layer data and modulate it into OFDM symbols and send the OFDM symbols through a wireless channel, or may demodulate OFDM symbols received through a wireless channel, channel decode the demodulated OFDM symbols, and transmit the channel-decoded OFDM symbols to a higher layer.

[0158] Figure 1e is a block diagram illustrating an internal structure of a terminal according to some embodiments of the present disclosure.

[0159] Reference Figure 1e , the terminal may include a radio frequency (RF) processor 1e-10, a baseband processor 1e-20, a memory 1e-30, and a controller 1e-40. However, the present disclosure is not limited thereto, and the terminal may include more Figure 1e More or fewer elements than shown.

[0160] The RF processor 1e-10 can perform functions such as signal band conversion or amplification for sending and receiving signals via a wireless channel. That is, the RF processor 1e-10 can up-convert the baseband signal received from the baseband processor 1e-20 into an RF band signal and send the RF band signal via an antenna, and can down-convert the RF band signal received via the antenna into a baseband signal. For example, the RF processor 1e-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. However, the present disclosure is not limited thereto. Although in Figure 1e Only one antenna is shown in the figure, but the terminal may include multiple antennas. Moreover, the RF processor 1e-10 may include multiple RF chains. In addition, the RF processor 1e-10 may perform beamforming. For beamforming, the RF processor 1e-10 may adjust the phase and amplitude of each of the signals transmitted and received via multiple antennas or antenna elements. Moreover, the RF processor 1e-10 may perform multiple-input multiple-output (MIMO) and may receive several layers during MIMO operation.

[0161] The baseband processor 1e-20 performs a conversion function between a baseband signal and a bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor 1e-20 can generate a composite symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 1e-20 can recover the received bit string by demodulating and decoding the baseband signal received from the RF processor 1e-10. For example, according to the OFDM scheme, during data transmission, the baseband processor 1e-20 can generate a composite symbol by encoding and modulating the transmitted bit string, mapping the composite symbol to a subcarrier, and then configuring the OFDM symbol through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 1e-20 can divide the baseband signal received from the RF processor 1e-10 into units of OFDM symbols, recover the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and then recover the received bit string through demodulation and decoding.

[0162] As described above, the baseband processor 1e-20 and the RF processor 1e-10 send and receive signals. Therefore, the baseband processor 1e-20 and the RF processor 1e-10 can each be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor 1e-20 or the RF processor 1e-10 may include multiple communication modules supporting different multiple RATs. In addition, at least one of the baseband processor 1e-20 or the RF processor 1e-10 may include different communication modules to process signals of different frequency bands. For example, different RATs may include a wireless local area network (LAN) (e.g., IEEE 802.11) and a cellular network (e.g., LTE). Moreover, different frequency bands may include ultra-high frequency (SHF) (e.g., 2NRHz or NRHz) bands and millimeter (mm) wave (e.g., 60GHz) bands. The terminal can send and receive signals to and from a base station using the baseband processor 1e-20 and the RF processor 1e-10, and the signal may include control information and data.

[0163] The memory 1e-30 stores data such as basic programs, applications or configuration information for terminal operation. Specifically, the memory 1e-30 can store information related to a second access node that performs wireless communication by using a second RAT. In addition, the memory 1e-30 provides the stored data according to a request from the controller 1e-40. The memory 1e-30 may include a storage medium, such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disc ROM (CD-ROM), or a digital versatile disk (DVD), or a combination thereof. In addition, the memory 1e-30 may include multiple memories.

[0164] The controller 1e-40 controls the overall operation of the terminal. For example, the controller 1e-40 sends and receives signals via the baseband processor 1e-20 and the RF processor 1e-10. In addition, the controller 1e-40 records data to the memory 1e-30 and reads data from the memory 1e-30. Therefore, the controller 1e-40 may include at least one processor. For example, the controller 1e-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling a higher layer such as an application. In addition, at least one element in the terminal may be implemented as a chip.

[0165] Figure 1f is a block diagram showing the configuration of an NR base station according to some embodiments of the present disclosure.

[0166] Reference Figure 1f, the base station may include an RF processor 1f-10, a baseband processor 1f-20, a backhaul communicator 1f-30, a memory 1f-40, and a controller 1f-50. However, the present disclosure is not limited thereto, and the base station may include more Figure 1f More or fewer elements than shown.

[0167] The RF processor 1f-10 can perform functions such as signal band conversion or amplification for sending and receiving signals via a wireless channel. That is, the RF processor 1f-10 up-converts the baseband signal received from the baseband processor 1f-20 into an RF band signal, transmits the RF band signal via an antenna, and down-converts the RF band signal received via the antenna into a baseband signal. For example, the RF processor 1f-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although in Figure 1f Only one antenna is shown in the figure, but the RF processor 1f-10 may include multiple antennas. Moreover, the RF processor 1f-10 may include multiple RF chains. In addition, the RF processor 1f-10 can perform beamforming. For beamforming, the RF processor 1f-10 can adjust the phase and amplitude of each of the signals transmitted and received via multiple antennas or antenna elements. The RF processor can perform downlink MIMO operations by sending at least one layer.

[0168] The baseband processor 1f-20 performs a conversion function between a baseband signal and a bit string according to the physical layer specification of the first RAT. For example, during data transmission, the baseband processor 1f-20 can generate a composite symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 1f-20 can recover the received bit string by demodulating and decoding the baseband signal received from the RF processor 1f-10. For example, according to the OFDM scheme, during data transmission, the baseband processor 1f-20 can generate a composite symbol by encoding and modulating the transmitted bit string, mapping the composite symbol to a subcarrier, and then configuring the OFDM symbol through IFFT operation and CP insertion. In addition, during data reception, the baseband processor 1f-20 can divide the baseband signal received from the RF processor 1f-10 into OFDM symbol units, recover the signal mapped to the subcarrier through FFT operation, and then recover the received bit string through demodulation and decoding. As described above, the baseband processor 1f-20 and the RF processor 1f-10 send and receive signals. Therefore, the baseband processor 1f-20 and the RF processor 1f-10 can each be referred to as a transmitter, a receiver, a transceiver, a communicator, or a wireless communicator. The base station can send and receive signals to and from the terminal by using the baseband processor 1f-20 and the RF processor 1f-10, and the signal can include control information and data.

[0169] The backhaul communicator 1f-30 provides an interface for performing communication with other nodes in the network. That is, the backhaul communicator 1f-30 can convert a bit string sent from the main base station to another node such as a sub-base station or a core network into a physical signal, and can convert a physical signal received from another node into a bit string. The backhaul communicator 1f-30 can be included in the communicator.

[0170] The memory 1f-40 stores data, such as basic programs, applications or configuration information for base station operation. The memory 1f-40 may store information about the bearers allocated to the connected terminals and measurement results reported from the connected terminals. In addition, the memory 1f-40 may store information as a basis for determining whether to provide or suspend multiple connections to the terminal. In addition, the memory 1f-40 provides the stored data according to a request from the controller 1f-50. The memory 1f-40 may include a storage medium, such as a ROM, RAM, a hard disk, a CD-ROM or a DVD, or a combination thereof. In addition, the memory 1f-40 may include a plurality of memories. According to some embodiments, the memory 1f-40 may store a program for executing the buffer status reporting method according to the present disclosure.

[0171] The controller 1f-50 controls the overall operation of the base station. For example, the controller 1f-50 sends and receives signals via the baseband processor 1f-20 and the RF processor 1f-10 or via the backhaul communicator 1f-30. In addition, the controller 1f-50 records data to the memory 1f-40 and reads data from the memory 1f-40. Therefore, the controller 1f-50 may include at least one processor. In addition, at least one element of the base station may be implemented as one chip.

[0172] Figure 1gis a block diagram showing the architecture of a local location management function (LMF) according to some embodiments of the present disclosure. UE 1g-1 may be connected to a radio access network (RAN) node 1g-5. The RAN node 1g-5 may be an LTE eNB or an NR gNB. Therefore, the UE and the RAN node 1g-5 may be connected to each other via LTE-Uu or NR-Uu. The local LMF 1g-10 may be installed in the RAN node 1g-5. Therefore, there may not be a separate interface in the local LMF 1g-10 and the RAN node 1g-5 in which the local LMF 1g-10 exists. The RAN node 1g-5 and the AMF 1g-20 may communicate with each other via the N2 interface. The UE 1g-1 and the AMF 1g-20 may communicate with each other via the N1 interface by using the NAS protocol. In a 5G core network (5GC), there may be an LMF 1g-15, and when all functions are transferred to the local LMF 1g-10, the LMF 1g-15 may not exist. Since LMF is introduced in the existing version, the existing LMF is called CN LMF, and the coexistence of local LMF and CN LMF is considered. The entity requesting location service outside 5GC is called external client 1g-25, and it can trigger location service. External client 1g-25 can be a server that needs location information of UE 1g-1.

[0173] Figure 1h A protocol stack for communication between a UE and a Next Generation (NG) RAN including a local LMF according to some embodiments of the present disclosure is shown. Here, the PHY, MAC, RLC and PDCP layers may perform reference Figure 1d The functions of the PHY, MAC, RLC, and PDCP layers described above are described. In addition, the RRC layer may include messages of location-related protocols, including the LTE Location Protocol (LPP), which is a protocol for generating control signals (hereinafter, location-related protocols are collectively referred to as LPP), and may send them to the lower layers. In addition, the UE and the NG RAN including the local LMF may send location-related control signals and messages through the LPP.

[0174] Figure 1i is a diagram showing a protocol stack when a UE and a CN LMF communicate with each other through LPP in LTE and NR according to some embodiments of the present disclosure. Figure 1i In the NAS layer, the Figure 1hbetween the LPP layer and the RRC layer of the UE shown. The UE may encapsulate the LPP message in a NAS message, and may encapsulate the NAS message in an RRC message. The NG RAN node may analyze the RRC message, and may send the NAS message in the analyzed RRC message to the AMF. The AMF may analyze the NAS message, and may send the LPP message to the CN LMF again. In the direction opposite to the above direction, when the CN LMF generates the LPP message, the CN LMF may send the LPP message to the AMF, and the AMF may encapsulate the LPP message in a NAS message and may send the NAS message to the NG RAN node. The NG RAN node may encapsulate the NAS message including the LPP message in an RRC message, and may send the RRC message to the UE again.

[0175] Figure 1j is a diagram illustrating an LPP procedure through a CN LMF according to some embodiments of the present disclosure. A location service (LCS) request may be performed by an LCS external client. Information for identifying a UE requiring LCS information may be included in the LCS request. The LCS request may be sent to the AMF. The AMF may identify the UE included in the LCS request, may identify a RAN node providing a service, and may send an LCS request including RAN node information (cell and base station identification information) to the CN LMF. From this point on, the CN LMF may perform an LPP procedure with the UE in a one-to-one manner. The LMF may perform the LPP procedure by using Figure 1i The protocol stack in is used to perform communication with the UE. When the LMF sends a message of location request information to the AMF, the AMF may encapsulate the message in a NAS message, and may send the NAS message to the RAN node to which the UE is connected. The RAN node may encapsulate the NAS message in an RRC message, and may send the RRC message to the UE. When the UE receives the RRC message, the UE may process the PDU to obtain a NAS PDU, and may process the NAS PDU to obtain an LPP message. The UE may encapsulate the LPP response message in a NAS message, may add the NAS message again to the RRC message, and may send the RRC message to the RAN node corresponding to the process. The RAN node may process the RRC PDU, and may send the NAS message only to the AMF.

[0176] The AMF may process the NAS PDU and may send an LPP message to the CN LMF. The CN LMF may receive the LPP message and the AMF may receive a response to the LCS request. The AMF may send a response to the LCS request to the LCS external client that triggered the LCS request through the AMF.

[0177] Figure 1kThis is a flowchart when the local location management function (LLMF) is used according to an embodiment of the present disclosure. UE 1k-1 can be connected to the NG RAN node 1k-5, or can be in an inactive / idle state. The LCS external client 1k-20 can request LCS service. The LCS external client 1k-20 can send an LCS request message to the AMF 1k-10 (operation 1k-40). In this case, the LCS external client 1k-20 can send identification information about a specific UE or UE group. The AMF1k-10 that receives the identification information can identify the information of the corresponding UE, can find the currently connected NG RAN node 1k-5 or location, and then can send an LCS request message to the NGRAN node 1k-5 (operation 1k-45). When the AMF 1k-10 sends the LCS request message to the RAN node 1k-5, the interface between the AMF 1k-10 and the CN LMF 1k-15 can be used. The LLMF can receive the LCS request message, and when sending positioning-related messages directly to the UE and receiving positioning-related messages from the UE, the LLMF can perform processes related to UE capabilities related to location information, processes related to the configuration, measurement and execution of positioning methods, and processes related to the sending and receiving of the obtained location information (operations 1k-25).

[0178] When using Figure 1k LLMF in , and there is Figure 1j When LPP operation of UE and CN LMF 1k-15 is performed, UE and NGRAN node 1k-5 should distinguish whether LPP is triggered by CN LMF 1k-15 (operation 1j-3) or through LLMF (operation 1k-50) and encapsulate corresponding PDU / message. Roughly, there can be two embodiments.

[0179] In the first embodiment, regarding the operation of the NG RAN node 1k-5, when the LPP message comes from the CN-LMF 1k-15, the base station can add the received NAS message (including DL LPP) to the dedicatedNAS-Message IE of the RRC (which may include an indicator of the DL LPP message), and can send it to the UE through the RRC DLInformationTransfer message. When the LLMF receives the LCS request directly from the AMF 1k-10, such as Figure 1kAs shown, the base station can add the LPP message to the message IE separated from the NAS message, that is, the localLMFLPP-Message IE of RRC (which may include an indicator of the DL LPP message), and can send it to the UE 1k-1 through the RRC DLInformationTransfer message. Regarding the operation of the UE 1k-1, when the LPP message generated by the UE 1k-1 is a response message to the LPP message included in the dedicatedNAS-Message or a message caused by a process triggered by the LPP message included in the dedicatedNAS-Message, the UE 1k-1 can add the LPP message to the dedicatedNAS-Message IE (which may include an indicator of the UL LPP message). And it can be sent to the NR RAN node (i.e., the serving base station) through the RRC ULInformationTransfer message. When the LPP message generated by UE 1k-1 is a response message to the LPP message included in the localLMFLPP-Message IE (which may include an indicator of a UL LPP message) or a message caused by a process triggered by the LPP message included in the localLMFLPP-Message IE, UE 1k-1 can add the LPP message to the localLMFLPP-Message IE (which may include an indicator of a UL LPP message) and can send it to the NR RAN node (i.e., the serving base station) through the RRC ULInformationTransfer message.

[0180] In another embodiment, regarding the operation of the NG RAN node 1k-5, when the LPP message comes from the CN-LMF 1k-15, the base station may add the received NAS message (including the DL LPP) to the dedicatedNAS-Message IE of the RRC (which may include an indicator of the DL LPP message), and may send it to the UE 1k-1 via the RRC DLInformationTransfer message. When the LLMF receives the LCS request directly from the AMF 1k-10, such as Figure 1kAs shown, the base station may add the LPP message to the dedicatedNAS-Message IE (which may include an indicator of the DL LPP message), may mark or include the localLMFInd indicator, and may send it to the UE 1k-1 through the RRC DLInformationTransfer message. Regarding the operation of the UE 1k-1, when the LPP message generated by the UE 1k-1 is a response message to the LPP message included in the dedicatedNAS-Message without the localLMFInd indicator, or is a message caused by a process triggered by the LPP message included in the dedicatedNAS-Message without the localLMFInd indicator, the UE may add the LPP message to the dedicatedNAS-Message IE (which may include an indicator of the UL LPP message), and may send the LPP message to the NR RAN node (i.e., the serving base station) through the RRC ULInformationTransfer message. When the LPP message generated by UE 1k-1 is a response message to the LPP message included in a dedicatedNAS-Message with a localLMFInd indicator or a message caused by a procedure triggered by the LPP message included in the dedicatedNAS-Message with a localLMFInd indicator, UE 1k-1 may add the LPP message to the dedicatedNAS-Message IE (which may include an indicator of the UL LPP message), may mark or include the localLMFInd indicator, and may send it to the NR RAN node (i.e., the serving base station) through an RRCULInformationTransfer message.

[0181] Although the name of the RRC IE including the LPP message may be different, the dedicatedNAS-Message IE may be any IE that transmits the NAS message. In addition, for localLMFInd, the indicator indicating the LPP message corresponding to the local LMF may be any indicator regardless of its name. In addition, for the localLMFLPP-Message IE, the IE that may include the LPP message corresponding to the local LMF may be any IE having this function regardless of its name.

[0182] Figure 1l1 is a flowchart showing a case where the AMF determines whether to use LLMF or CN LMF according to some embodiments of the present disclosure. In one embodiment, when receiving an LCS request, the AMF may check the state of the UE, may determine whether to use the local LMF or the CN LMF, and may send the LCS request to the determined LMF so that the LMF performs the LPP procedure with the UE. According to whether the determined LMF is the CN LMF or the LLMF, the AMF may determine whether to use the local LMF or the CN LMF according to the reference Figure 1k The above two embodiments described are used to perform the LPP encapsulation operation between the UE and the serving NG RAN node. There may be an LCS request from an external NG RAN node or from the AMF, and when the AMF receives the LCS request, the AMF may check the status of the UE as the LCS target included in the LCS request. When the UE is connected or inactive, the AMF may determine that the LLMF is the LCS request target. When the AMF selects the LLMF as the request target, the AMF may send an LCS request to the LLMF. When the LLMF receives the LCS request, the UE and the LLMF may perform the LPP process according to the communication method between the local LMF and the UE. Specifically, as shown in reference Figure 1k As described in the embodiment of the present invention, a method of adding the LPP message to the localLMFLPP-Message IE of the RRC message and a method of using the dedicatedNAS-Message IE and the localLMFInd indicator may be used. When the LPP process ends, when the LLMF obtains the desired UE location information, the NG RAN node may send an LCS response to the AMF, and the AMF may send an LCS response to the LCS external client.

[0183] Figure 1m 1 is a diagram showing a case where the AMF determines whether to use LLMF or CN LMF according to some embodiments of the present disclosure. In an embodiment, when receiving an LCS request, the AMF may check the state of the UE, and when the UE is in an idle state, the AMF may determine that the CN LMF is the LCS request target. When the AMF selects the CN LMF as the request target, the AMF may send an LCS request to the CN LMF. When the CN LMF receives the LCS request, the CN LMF and the UE may communicate with each other by encapsulating the LPP message in the NAS layer, such as Figure 1j Specifically, as shown in reference Figure 1kAs described in the embodiment, the NG RAN node and the UE may add the LPP message to the dedicatedNAS-Message IE of the RRC message and may send the message. When the LPP process using the NAS layer ends and the CN LMF obtains the desired UE location information, the CN LMF may send an LCS response to the AMF, and the AMF may send an LCS response to the LCS external client.

[0184] Figure 1n 1 is a flow chart showing a case where the AMF uses LLMF regardless of the state of the UE when the AMF receives an LCS request from an LCS external client according to some embodiments of the present disclosure. When the UE is connected or inactive, the UE and the RAN node can communicate with each other without the NAS layer, such as Figure 1l As shown. That is, in this case, AS security implemented by RRC can be applied. When the UE is in an idle state, since it takes time to re-establish AS security, the NAS security factor can be sent to the LLMF together with the LCS request. The UE and the RAN node can encapsulate the LPP message in the dedicatedNAS-Message IE by using the NAS security factor, and can communicate with each other by using NAS security in the NAS message.

[0185] In the present disclosure, a method of configuring factors required to add and modify a secondary cell of a secondary cell (Scell) group will be described.

[0186] According to the disclosed embodiments, in a wireless communication system, as the number of secondary cells to be operated increases, the data size required to signal factors required for adding or modifying the secondary cells can be reduced.

[0187] Figure 2a is a diagram showing the structure of an LTE system according to some embodiments of the present disclosure.

[0188] Reference Figure 2a The radio access network of the LTE system may include next generation base stations (hereinafter referred to as evolved Node B (ENB), Node B or base station) 2a-05, 2a-10, 2a-15 and 2a-20, a mobility management entity (MME) 2a-25 and a serving gateway (S-GW) 2a-30. A user terminal (hereinafter referred to as user equipment (UE) or terminal) 2a-35 may access an external network via the ENB 2a-05 to 2a-20 and the S-GW 2a-30.

[0189] exist Figure 2aIn the present invention, ENB 2a-05 to 2a-20 may correspond to an existing Node B of a Universal Mobile Telecommunications System (UMTS). The ENB may be connected to a UE 2a-35 via a wireless channel and may perform more complex functions than an existing Node B. In an LTE system, all user services including real-time services such as Voice over Internet Protocol (VoIP) may be served through a shared channel. Therefore, it may be necessary to collect state information of the UE such as buffer status, available transmission power status, channel status, etc. and schedule the state information, and the ENB 2a-05 to 2a-20 may perform the function. One ENB may generally control multiple cells. For example, in order to achieve a data rate of 100Mbps, an LTE system may use orthogonal frequency division multiplexing (OFDM) as a radio access technology (RAT) on a bandwidth of, for example, 20MHz. In addition, the ENB may use an adaptive modulation and coding (AMC) scheme that determines the modulation scheme and channel coding rate according to the channel state of the terminal. The S-GW 2a-30 is a device that provides a data bearer, and can generate or remove a data bearer under the control of the MME 2a-25. The MME is a device that performs various control functions for a terminal and a mobility management function, and can be connected to a plurality of base stations.

[0190] Figure 2b is a diagram illustrating a radio protocol architecture of an LTE system according to some embodiments of the present disclosure.

[0191] Reference Figure 2b In each of the terminal and the ENB, the radio protocol of the LTE system may include a packet data convergence protocol (PDCP) 2b-05 / 2b-40, a radio link control (RLC) 2b-10 / 2b-35, and a media access control (MAC) 2b-15 / 2b-30. PDCP may be responsible for operations such as IP header compression / decompression. The main functions of PDCP may be summarized as follows. However, the present disclosure is not limited to the following examples.

[0192] -Header compression and decompression: ROHC only

[0193] -Transfer user data

[0194] - In-sequence delivery of upper layer PDUs during PDCP re-establishment for RLC AM

[0195] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0196] - Repeated detection of lower layer SDUs during PDCP re-establishment for RLC AM

[0197] - Retransmission of PDCP SDUs at handover and, for split bearers in DC, retransmission of PDCP PDUs during PDCP data recovery procedure for RLC AM

[0198] -Encryption and decryption

[0199] - Timer-based SDU discard in uplink

[0200] According to some embodiments, RLC 2b-10 or 2b-35 may reconfigure PDCP PDU with an appropriate size and perform ARQ operations, etc. The main functions of RLC may be summarized as follows. However, the present disclosure is not limited to the following examples.

[0201] -Transmission of upper layer PDU

[0202] -ARQ (error correction through ARQ (only for AM data transmission))

[0203] - Concatenation, segmentation and reassembly of RLC SDU (for UM and AM data transmission only)

[0204] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0205] - Reordering of RLC data PDUs (only for UM and AM data transmission)

[0206] - Duplicate detection (for UM and AM data transmission only)

[0207] -Protocol error detection (for AM data transmission only)

[0208] -RLC SDU discard (only for UM and AM data transmission)

[0209] -RLC reconstruction

[0210] According to some embodiments, MAC 2b-15 or 2b-30 is connected to several RLC entities configured in one terminal, and can multiplex RLC PDU into MAC PDU and demultiplex RLC PDU from MAC PDU. The main functions of MAC can be summarized as follows. However, the present disclosure is not limited to the following examples.

[0211] - Mapping between logical channels and transport channels

[0212] - Multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) delivered to the physical layer on a transport channel, and demultiplexing MAC SDUs belonging to one or different logical channels from a transport block (TB) delivered from the physical layer on a transport channel

[0213] -Dispatch information report

[0214] -HARQ (error correction through HARQ)

[0215] - Priority handling between logical channels of a UE

[0216] - Prioritization between UEs through dynamic scheduling

[0217] -MBMS service logo

[0218] -Transmission format selection

[0219] -filling

[0220] According to some embodiments, the physical layer (PHY) 2b-20 or 2b-25 may channel encode and modulate higher layer data into OFDM symbols and send the OFDM symbols via a wireless channel, or may demodulate and channel decode OFDM symbols received via a wireless channel and transmit the channel-decoded OFDM symbols to a higher layer. However, the present disclosure is not limited to the following examples.

[0221] Figure 2c is a diagram showing a structure of a next generation mobile communication system according to some embodiments of the present disclosure.

[0222] Reference Figure 2c , the radio access network of the next generation mobile communication system (hereinafter referred to as NR or 5G) may include a next generation base station (hereinafter referred to as a new radio node B (NR gNB) or NR base station) 2c-10 and a new radio core network (NRCN) 2c-05. The new radio user equipment (NR UE) 2c-15 can access the external network via the NR gNB 2c-10 and the NR CN 2c-05.

[0223] exist Figure 2c In the present invention, the NR gNB 2c-10 may correspond to the evolved Node B (eNB) of the existing LTE system. The NR gNB is connected to the NR UE 2c-15 via a wireless channel and may provide much better services than the existing Node B. In the next generation mobile communication system, all user services may be served through shared channels. Therefore, a device for collecting status information of the UE such as buffer status, available transmission power status, channel status, etc. and scheduling the status information may be required, and the NR gNB 2c-10 may perform this function. One NR gNB may control multiple cells. In the next generation mobile communication system, in order to achieve high-speed data transmission compared to the current LTE, a bandwidth larger than the current maximum bandwidth may be applied. In addition, beamforming technology may be additionally used as RAT together with OFDM.

[0224] In addition, according to some embodiments, the NR gNB can use an AMC scheme that determines a modulation scheme and a channel coding rate according to the channel state of the terminal. NR CN 2c-05 can perform functions such as mobility support, bearer configuration, and QoS configuration. NR CN 2c-05 is a device that performs various control functions for terminals and mobility management functions, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can interoperate with the existing LTE system, and the NR CN can be connected to the MME 2c-25 via a network interface. The MME can be connected to the eNB 2c-30 which is an existing base station.

[0225] Figure 2d is a diagram illustrating a radio protocol architecture of a next generation mobile communication system according to some embodiments of the present disclosure.

[0226] Reference Figure 2d , in each of the terminal and the NR base station, the radio protocol of the next-generation mobile communication system may include NR Service Data Adaptation Protocol (SDAP) 2d-01 / 2d-45, NR PDCP 2d-05 / 2d-40, NR RLC 2d-10 / 2d-35 and NR MAC 2d-15 / 2d-30.

[0227] According to some embodiments, the main functions of NR SDAP 2d-01 or 2d-45 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0228] -Transmission of user plane data

[0229] - Mapping between QoS flows and DRBs for both DL and UL

[0230] -Mark QoS flow ID in DL and UL packets

[0231] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0232] For the SDAP entity, the terminal may be configured through a radio resource control (RRC) message as to whether to use the header of the SDAP entity or the function of the SDAP entity for each PDCP layer, bearer, or logical channel. In addition, when configuring the SDAP header, a 1-bit NAS reflection QoS configuration indicator and a 1-bit AS reflection QoS configuration indicator may indicate that the terminal of the SDAP header updates or reconfigures the mapping information between the QoS flows and data bearers for UL and DL. According to some embodiments, the SDAP header may include QoS flow ID information indicating QoS. According to some embodiments, QoS information may be used as data processing priority and scheduling information for supporting smooth services.

[0233] According to some embodiments, the main functions of NR PDCP 2d-05 or 2d-40 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0234] -Header compression and decompression: ROHC only

[0235] -Transfer user data

[0236] - In-sequence delivery of upper layer PDUs

[0237] - Out-of-order delivery of upper layer PDUs

[0238] - Reordering of received PDCP PDUs

[0239] - Duplicate detection of lower layer SDU

[0240] -Retransmission of PDCP SDU

[0241] -Encryption and decryption

[0242] - Timer-based SDU discard in uplink

[0243] In the above description, the reordering function of the NR PDCP entity may indicate a function of reordering the PDCP PDUs received from the lower layer based on the PDCP sequence number (SN). The reordering function of the NR PDCP entity may include a function of delivering data to a higher layer in a reordered order, a function of directly delivering data without considering the order, a function of reordering the order and recording the lost PDCP PDUs, and a function of reporting the status of the lost PDCP PDUs to the transmitting side and requesting retransmission of the lost PDCP PDUs.

[0244] According to some embodiments, the main functions of NR RLC 2d-10 or 2d-35 may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0245] -Transmission of upper layer PDU

[0246] - In-sequence delivery of upper layer PDUs

[0247] - Out-of-order delivery of upper layer PDUs

[0248] -ARQ (error correction via ARQ)

[0249] - Concatenation, segmentation and reassembly of RLC SDU

[0250] - Re-segmentation of RLC data PDUs

[0251] Reordering of RLC data PDUs

[0252] - Duplicate detection

[0253] -Protocol error detection

[0254] -RLC SDU discarded

[0255] -RLC reconstruction

[0256] In the above description, the in-sequence delivery function of the NR RLC entity may indicate a function of delivering RLC SDUs received from a lower layer to a higher layer in sequence. When an original RLC SDU is segmented into multiple RLC SDUs and received, the in-sequence delivery function of the NR RLC entity may include the functions of reassembling the RLC SDUs and delivering the RLC SDUs.

[0257] The in-sequence delivery function of the NR RLC entity may include a function of reordering the received RLC PDUs based on the RLC SN or the PDCP SN. In addition, the in-sequence delivery function of the NR RLC entity may include a function of reordering the sequence and recording the lost PDCP PDUs, a function of reporting the status of the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs.

[0258] When there are lost RLC SDUs, the in-sequence delivery function of the NR RLC entity may include the function of delivering only the RLC SDUs preceding the lost RLC SDUs in-sequence to higher layers.

[0259] Furthermore, when a certain timer expires, the in-sequence delivery functionality of the NR RLC entity may include the functionality of delivering in-sequence to higher layers all RLC SDUs received before a certain timer is started, despite the presence of lost RLC SDUs.

[0260] When a certain timer expires, the in-sequence delivery functionality of the NR RLC entity may include the functionality of delivering all RLC SDUs received so far in sequence to higher layers despite the presence of lost RLC SDUs.

[0261] The NR RLC entity may process the RLC PDUs in the order of reception without considering the order of SNs, and may deliver the processed RLC PDUs to the NR PDCP entity in an out-of-order delivery manner.

[0262] When the NR RLC entity receives segments, the NR RLC entity may receive segments stored in a buffer or to be received later, may reconfigure these segments into a complete RLC PDU, and may then deliver the RLC PDU to the NR PDCP entity.

[0263] The NR RLC entity may not include the cascading function, and this function may be performed by the NR MAC layer, or may be replaced by the multiplexing function of the NR MAC entity.

[0264] In the above description, the out-of-order delivery function of the NR RLC entity may indicate a function of delivering the RLC SDU received from the lower layer directly to the higher layer regardless of the order. When one original RLC SDU is segmented into multiple RLC SDUs and received, the out-of-order delivery function of the NR RLC entity may include a function of reassembling the RLC SDU and delivering the RLC SDU. The out-of-order delivery function of the NR RLC entity may include a function of storing and sorting the RLC SN or PDCP SN of the received RLC PDU and recording the lost RLC PDU.

[0265] According to some embodiments, NR MAC 2d-15 or 2d-30 can be connected to several NRRLC entities configured in one terminal, and the main functions of NR MAC may include some of the following functions. However, the present disclosure is not limited to the following examples.

[0266] - Mapping between logical channels and transport channels

[0267] -Multiplexing / demultiplexing of MAC SDU

[0268] -Dispatch information report

[0269] -HARQ (error correction through HARQ)

[0270] - Priority handling between logical channels of a UE

[0271] - Prioritization between UEs through dynamic scheduling

[0272] -MBMS service logo

[0273] -Transmission format selection

[0274] -filling

[0275] The NR PHY 2d-20 or 2d-25 can channel encode higher layer data and modulate it into OFDM symbols and send the OFDM symbols through a wireless channel, or can demodulate OFDM symbols received through a wireless channel, channel decode the demodulated OFDM symbols, and transmit the channel-decoded OFDM symbols to a higher layer.

[0276] Figure 2e is a block diagram illustrating an internal structure of a terminal according to some embodiments of the present disclosure.

[0277] Reference Figure 2e, the terminal may include a radio frequency (RF) processor 2e-10, a baseband processor 2e-20, a memory 2e-30, and a controller 2e-40. However, the present disclosure is not limited thereto, and the terminal may include more Figure 2e More or fewer elements than shown.

[0278] The RF processor 2e-10 can perform functions such as signal band conversion or amplification for sending and receiving signals via a wireless channel. That is, the RF processor 2e-10 can up-convert the baseband signal received from the baseband processor 2e-20 into an RF band signal and send the RF band signal via an antenna, and can down-convert the RF band signal received via the antenna into a baseband signal. For example, the RF processor 2e-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. However, the present disclosure is not limited thereto. Although in Figure 2e Only one antenna is shown in the figure, but the terminal may include multiple antennas. Moreover, the RF processor 2e-10 may include multiple RF chains. In addition, the RF processor 2e-10 can perform beamforming. For beamforming, the RF processor 2e-10 can adjust the phase and amplitude of each of the signals sent and received via multiple antennas or antenna elements. In addition, the RF processor 2e-10 can perform multiple input multiple output (MIMO) and can receive several layers during MIMO operation.

[0279] The baseband processor 2e-20 performs the conversion function between the baseband signal and the bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor 2e-20 can generate a composite symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 2e-20 can recover the received bit string by demodulating and decoding the baseband signal received from the RF processor 2e-10. For example, according to the OFDM scheme, during data transmission, the baseband processor 2e-20 can generate a composite symbol by encoding and modulating the transmitted bit string, mapping the composite symbol to the subcarrier, and then configuring the OFDM symbol through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 2e-20 can divide the baseband signal received from the RF processor 2e-10 into units of OFDM symbols, recover the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and then recover the received bit string through demodulation and decoding.

[0280] As described above, the baseband processor 2e-20 and the RF processor 2e-10 send and receive signals. Therefore, the baseband processor 2e-20 and the RF processor 2e-10 can each be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor 2e-20 or the RF processor 2e-10 may include multiple communication modules supporting different multiple RATs. In addition, at least one of the baseband processor 2e-20 or the RF processor 2e-10 may include different communication modules to process signals of different frequency bands. For example, different RATs may include wireless LANs (e.g., IEEE 802.11) and cellular networks (e.g., LTE). Moreover, different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2NRHz, or NRHz) and millimeter (mm) wave (e.g., 60GHz) bands. The terminal may send and receive signals to and from a base station using the baseband processor 2e-20 and the RF processor 2e-10, and the signal may include control information and data.

[0281] The memory 2e-30 stores data, such as basic programs, applications or configuration information for terminal operation. Specifically, the memory 2e-30 can store information related to a second access node that performs wireless communication using a second RAT. In addition, the memory 2e-30 provides the stored data according to a request from the controller 2e-40. The memory 2e-30 may include a storage medium, such as a ROM, RAM, hard disk, CD-ROM or DVD, or a combination thereof. In addition, the memory 2e-30 may include a plurality of memories.

[0282] The controller 2e-40 controls the overall operation of the terminal. For example, the controller 2e-40 sends and receives signals via the baseband processor 2e-20 and the RF processor 2e-10. In addition, the controller 2e-40 records data to the memory 2e-30 and reads data from the memory 2e-30. Therefore, the controller 2e-40 may include at least one processor. For example, the controller 2e-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling a higher layer such as an application program. In addition, at least one element in the terminal may be implemented as a chip.

[0283] Figure 2f is a block diagram showing the configuration of an NR base station according to some embodiments of the present disclosure.

[0284] Reference Figure 2f , the base station may include an RF processor 2f-10, a baseband processor 2f-20, a backhaul communicator 2f-30, a memory 2f-40, and a controller 2f-50. However, the present disclosure is not limited thereto, and the base station may include more Figure 2fMore or fewer elements than shown.

[0285] The RF processor 2f-10 can perform functions such as signal band conversion or amplification for sending and receiving signals via a wireless channel. That is, the RF processor 2f-10 can up-convert the baseband signal received from the baseband processor 2f-20 into an RF band signal and send the RF band signal via an antenna, and can down-convert the RF band signal received via an antenna into a baseband signal. For example, the RF processor 2f-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although in Figure 2f Only one antenna is shown in the figure, but the RF processor 2f-10 may include multiple antennas. Moreover, the RF processor 2f-10 may include multiple RF chains. In addition, the RF processor 2f-10 can perform beamforming. For beamforming, the RF processor 2f-10 can adjust the phase and amplitude of each of the signals sent and received via multiple antennas or antenna elements. The RF processor can perform downlink MIMO operations by sending at least one layer.

[0286] The baseband processor 2f-20 performs a conversion function between a baseband signal and a bit string according to the physical layer specification of the first RAT. For example, during data transmission, the baseband processor 2f-20 can generate a composite symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 2f-20 can recover the received bit string by demodulating and decoding the baseband signal received from the RF processor 2f-10. For example, according to the OFDM scheme, during data transmission, the baseband processor 2f-20 can generate a composite symbol by encoding and modulating the transmitted bit string, mapping the composite symbol to a subcarrier, and then configuring the OFDM symbol through IFFT operation and CP insertion. In addition, during data reception, the baseband processor 2f-20 can divide the baseband signal received from the RF processor 2f-10 into OFDM symbol units, recover the signal mapped to the subcarrier through FFT operation, and then recover the received bit string through demodulation and decoding. As described above, the baseband processor 2f-20 and the RF processor 2f-10 send and receive signals. Therefore, the baseband processor 2f-20 and the RF processor 2f-10 can each be referred to as a transmitter, a receiver, a transceiver, a communicator, or a wireless communicator. The base station can send and receive signals to and from the terminal by using the baseband processor 2f-20 and the RF processor 2f-10, and the signal can include control information and data.

[0287] The backhaul communicator 2f-30 provides an interface for performing communication with other nodes in the network. That is, the backhaul communicator 2f-30 can convert a bit string sent from the main base station to another node such as a sub-base station or a core network into a physical signal, and can convert a physical signal received from another node into a bit string. The backhaul communicator 2f-30 can be included in the communicator.

[0288] The memory 2f-40 stores data, such as basic programs, applications or configuration information for base station operation. The memory 2f-40 may store information about the bearers assigned to the connected terminals and measurement results reported from the connected terminals. In addition, the memory 2f-40 may store information as a basis for determining whether to provide or suspend multiple connections to the terminal. In addition, the memory 2f-40 provides the stored data according to a request from the controller 2f-50. The memory 2f-40 may include a storage medium, such as a ROM, RAM, a hard disk, a CD-ROM or a DVD, or a combination thereof. In addition, the memory 2f-40 may include a plurality of memories. According to some embodiments, the memory 2f-40 may store a program for executing the buffer status reporting method according to the present disclosure.

[0289] The controller 2f-50 controls the overall operation of the base station. For example, the controller 2f-50 sends and receives signals via the baseband processor 2f-20 and the RF processor 2f-10 or via the backhaul communicator 2f-30. In addition, the controller 2f-50 records data to the memory 2f-40 and reads data from the memory 2f-40. Therefore, the controller 2f-50 may include at least one processor. In addition, at least one element of the base station may be implemented as a chip.

[0290] Figure 2g 1 is a signal flow diagram during Scell ​​addition or modification in carrier aggregation according to some embodiments of the present disclosure. The UE and the base station are connected to each other. When the base station is about to command the UE to add or modify the Scell, the base station may send the following information to the UE through an RRCReconfiguration message.

[0291]

[0292] SCellGroupAddMod can be a field or an information element (IE) that includes information sent by the base station for adding or modifying a Scell. The IE can include a ScellGroupIndex, and the ScellGroupIndex can be an index indicating the group to which the Scell ​​to be added or modified belongs. The ScellGroup can have an SCellGroupCommonConfig, which is a parameter set to be referenced during the configuration of the Scell ​​to be added or modified. The SCellGroupCommonConfig can include information such as ServingCellConfigCommon, ServingCellConfig, and SSB-MTC. ServingCellConfigCommon can be a set of cell-specific factors of the Scell ​​to be added or modified, and ServingCellConfig can be a set of UE-specific factors of the Scell ​​to be added or modified. SSB-MTC is measurement timing configuration information of a synchronization signal block (SSB). In addition, ScellToAddModlist can be a list of Scells to be added or modified. ScellToAddMod can be an element of the list. ScellToAddMod may include sCellIndex indicating the index of the Scell ​​to be added or modified, and may include information such as ServingCellConfigCommon, ServingCellConfig, or SSB-MTC as a unit including configuration factors to be referenced for each Scell. Like the signal of the Scell ​​group, ServingCellConfigCommon includes a common factor for a specific cell, ServingCellConfig includes a UE-specific factor, and SSB-MTC is SSB measurement timing configuration information. When the UE receives the RRCReconfiguration message including the above information, the UE adds or modifies the Scell ​​according to the configuration rule, and may notify the base station of the confirmation through the RRCReconfigurationCompletion message.

[0293] Figure 2h is a flow chart illustrating the operation of a UE during Scell ​​addition / modification according to some embodiments of the present disclosure. Figure 2gWhen the UE sends a Scell ​​addition or modification message via the RRCReconfiguration message in the RRCReconfiguration message and the sCellIndex of ScellToAddMod in ScellToAddModList is not the index of the currently added Scell, the UE may newly add a Scell. In this case, for the factors of ServingCellConfigCommon to be applied to the Scell ​​corresponding to the sCellIndex in ScellToAddModList, the UE may apply the ServingCellConfigCommon indicated in SCellToAddMod or the ServingCellConfigCommon indicated in SCellGroupCommonConfig. In one embodiment, for the factors of ServingCellConfigCommon, the UE may preferentially apply the information indicated in SCellToAddMod, and for the information not indicated in SCellToAddMod, the information indicated in SCellGroupCommonConfig may be applied. When the index of the Scell ​​is not added and the value that the UE has is used, the UE may modify the configuration factors of the existing Scell. In one embodiment, the UE may replace the existing configuration factors by using the ServingCellConfigCommon indicated in ScellToAddMod, and for configuration factors other than the ServingCellConfigCommon indicated in ScellToAddMod, the UE may replace the existing configuration factors by using the ServingCellConfigCommon indicated in SCellGroupCommonConfig. For configuration factors other than the ServingCellConfigCommon indicated in ScellToAddMod or ScellGroupCommonConfig, the UE may use the previous configuration factors of the Scell.

[0294] In addition, according to one embodiment, the ServingCellConfig factors to be applied to the Scell ​​corresponding to the ScellIndex in the ScellToAddModList may be divided into two types of information. The first information of the ServingCellConfig is the information indicated in the SCellToAddMod and has the following characteristics. The first information may be indicated only in the SCellAddMod. In one embodiment, the first information may be CrossCarrierSchedulingConfig, pathlossReferenceLinking, or servingCellMO. The second information of the ServingCellConfig may be the second information of the ServingCellConfig indicated in the SCellToAddMod, or the second information of the ServingCellConfig indicated in the SCellGroupCommonConfig. In one embodiment, for the second information of the ServingCellConfig, the UE may preferentially apply the second information of the ServingCellConfig indicated in the SCellToAddMod, and for factors not indicated, the second information of the ServingCellConfig indicated in the SCellGroupCommonConfig may be applied. The second information may have the following conditions. The second information may be a ServingCellConfig other than the first information.

[0295] In addition, for the SSB-MTC to be applied to the Scell ​​corresponding to the sCellIndex in the ScellToAddModList, the SSB-MTC present in the SCellGroupCommonConfig or the SSB-MTC present in the SCellToAddMod may be used. In one embodiment, for the SSB-MTC of the Scell ​​to be added or modified, the UE may preferentially use the SSB-MTC present in the SCellToAddMod, and with respect to the lower fields not indicated, the SSB-MTC present in the SCellGroupCommonConfig may be used.

[0296] When ScellIndex is the index of the previously configured Scell, in the case where factors exist in the received ScellToAddMod for each field of the Scell, the existing value of each factor may be overwritten with the value present in the received ScellToAddMod. Factors other than the factors present in the received ScellToAddMod may maintain their previous values.

[0297] Figure 2i is a detailed flowchart showing the operation of the terminal during Scell ​​addition / modification according to some embodiments of the present disclosure. When the terminal receives a Scell ​​addition or modification message sent through an RRCReconfiguration message and the sCellIndex of ScellToAddMod in ScellToAddModList is not the index of the currently added Scell, the terminal can re-add the Scell. In this case, for the factors of ServingCellConfigCommon to be applied to the Scell ​​corresponding to the sCellIndex in ScellToAddModList, the terminal can apply the ServingCellConfigCommon indicated in SCellToAddMod or the ServingCellConfigCommon indicated in SCellGroupCommonConfig. In one embodiment, the terminal can give priority to the information indicated in SCellToAddMod, and with respect to the information not indicated in SCellToAddMod, the information indicated in SCellGroupCommonConfig can be applied.

[0298] In addition, in one embodiment, the ServingCellConfig factors to be applied to the Scell ​​corresponding to the sCellIndex in the ScellToAddModList may be divided into two types of information. The first information of the ServingCellConfig is the information indicated in the SCellToAddMod and may have the following characteristics. The first information may be indicated only in the SCellAddMod. According to one embodiment, the first information may be CrossCarrierSchedulingConfig, pathLossReferenceLinking, or servingCellMO. The second information of the ServingCellConfig may be the second information of the ServingCellConfig indicated in the SCellToAddMod or the second information of the ServingCellConfig indicated in the SCellGroupCommonConfig. In one embodiment, for the second information of the ServingCellConfig, the terminal may preferentially apply the second information of the ServingCellConfig indicated in the SCellToAddMod, and for factors not indicated, the second information of the ServingCellConfig indicated in the SCellGroupCommonConfig may be applied. The second information may have the following conditions. The second information may be a ServingCellConfig other than the first information.

[0299] In addition, for the SSB-MTC to be applied to the Scell ​​corresponding to the sCellIndex in ScellToAddModList, the terminal may use the SSB-MTC present in SCellGroupCommonConfig or the SSB-MTC present in SCellToAddMod. In one embodiment, for the SSB-MTC of the Scell ​​to be added or modified, the terminal may give priority to the SSB-MTC present in SCellToAddMod, and for lower fields not indicated, the SSB-MTC present in SCellGroupCommonConfig may be used.

[0300] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0301] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs may include instructions for allowing an electronic device to perform a method according to an embodiment described in the claims or specification of the present disclosure.

[0302] The program (software module or software) may be stored in a random access memory (RAM), a nonvolatile memory including a flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk (CD)-ROM, a digital versatile disk (DVD), other optical storage devices, or a magnetic tape cassette. Alternatively, the program may be stored in a memory configured by combining some or all of the above memories. In addition, each constituent memory may include a plurality of memories.

[0303] In addition, the program can be stored in an attachable storage device accessible through a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), a storage area network (SAN), or a combination thereof. The storage device can be connected to the device according to an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network can be connected to the device according to an embodiment of the present disclosure.

[0304] In the above-mentioned embodiments of the present disclosure, according to the embodiments of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form. However, the conditions provided for ease of description have appropriately selected singular or plural expressions, and the present disclosure is not limited to singular or plural components. A component expressed as a plural number can be configured as a single component, or a component expressed as a singular number can be configured as a plural component.

[0305] It should be understood that the embodiments of the present disclosure described herein should be considered to be merely descriptive and not for the purpose of limitation. That is, it will be understood by those of ordinary skill in the art that various changes in form and detail may be made in the embodiments of the present disclosure without departing from the spirit and scope of the present disclosure. In addition, the embodiments of the present disclosure may be used in combination when necessary. For example, the embodiments of the present disclosure and parts of another embodiment may be combined with each other, and base stations and terminals may be used. In addition, the embodiments of the present disclosure may be applied to other communication systems, and other modifications may be made therein based on the spirit of the above-described embodiments.

Claims

1. A method for using a location-based service (LCS) performed by a terminal, the method include: In the case where the access management function AMF identifies that the terminal is in a connected state or an inactive state and determines that the local location management function LLMF is used for the LCS: Receiving, from a base station, a first radio resource control (RRC) message including protocol information related to a location of the terminal, wherein the protocol information is generated by the LLMF having a logical connection within the base station; acquiring location-related information of the terminal based on the protocol information included in the first RRC message; and sending, in response to the first RRC message, a response message including the location-related information to the base station, In the case where the AMF identifies that the terminal is in an idle state and determines that a core network location management function CN LMF is used for the LCS: receiving, from the base station, a second RRC message including a first NAS message, wherein the first NAS message includes an LTE Location Protocol (LPP) message, wherein the LPP message is generated by the CN LMF; acquiring location-related information of the terminal based on the LPP message included in the first NAS message included in the second RRC message; and In response to the second RRC message, an LPP response message including location-related information of the terminal is sent to the base station.

2. The method according to claim 1, wherein the first RRC message includes an indicator corresponding to the LLMF that generates the protocol information, or includes the protocol information in an information element IE that changes according to the LLMF.

3. The method according to claim 2, further comprising: include: Based on the first RRC message, determining from which LMF of the LLMF or the CN LMF the protocol information is generated, The response message is generated to include the indicator, or the protocol information is included in the IE.

4. A method for providing a location-based service (LCS) performed by a base station, the method include: When the access management function AMF identifies that the terminal is in a connected state or an inactive state and determines that the local location management function LLMF is used for the LCS: Receiving, through the LLMF having a logical connection in the base station, a request message for a location-based service from the AMF; generating, by the LLMF, protocol information based on the request information; Sending a first radio resource control RRC message including the protocol information to the terminal; In response to the first RRC message, receiving, from the terminal, a response message including location-related information of the terminal; as well as sending the response message to the AMF, and In the case where the AMF identifies that the terminal is in an idle state and determines that a core network location management function CN LMF is used for the LCS: receiving, from the AMF, a first non-access stratum (NAS) message including an LTE location protocol (LPP) message, wherein the LPP message is generated by the CN LMF; Sending a second RRC message including the first NAS message to the terminal; In response to the second RRC message, receiving a third RRC message including a second NAS message from the terminal, the second NAS message including an LPP response message, the LPP response message including location-related information of the terminal; and Sending the second NAS message including the LPP response message to the AMF. 5 . The method according to claim 4 , wherein the request information includes identification information about the terminal, or information about a base station to which the terminal is connected. 6 . The method according to claim 4 , wherein the first RRC message includes an indicator corresponding to the LLMF, or includes the protocol information in an information element IE corresponding to the LLMF.

7. A terminal for using a location-based service LCS, the terminal include: Transceiver; a memory storing one or more instructions; as well as at least one processor connected to the transceiver and configured to execute one or more instructions to: In the case where the access management function AMF identifies that the terminal is in a connected state or an inactive state and determines that the local location management function LLMF is used for the LCS: receiving a first radio resource control RRC message including protocol information related to the location of the terminal from a base station, wherein the protocol information is generated by the LLMF having a logical connection within the base station, acquiring location-related information of the terminal based on the protocol information included in the first RRC message, sending, in response to the first RRC message, a response message including the location-related information to the base station, In the case where the AMF identifies that the terminal is in an idle state and determines that a core network location management function CN LMF is used for the LCS: receiving, from the base station, a second RRC message including a first NAS message, wherein the first NAS message includes an LTE Location Protocol (LPP) message, wherein the LPP message is generated by the CN LMF; acquiring location-related information of the terminal based on the LPP message included in the first NAS message included in the second RRC message; and In response to the second RRC message, an LPP response message including location-related information of the terminal is sent to the base station. 8 . The terminal according to claim 7 , wherein the first RRC message includes an indicator corresponding to the LLMF generating the protocol information, or includes the protocol information in an information element IE that changes according to the LLMF.

9. The terminal according to claim 8, wherein the at least one processor is further configured to execute one or more instructions to: determine from which LMF of the LLMF or the CNLMF the protocol information is generated based on the first RRC message, in, The response message is generated to include the indicator, or to include the protocol information in the IE.

10. A base station for providing a location-based service LCS, the base station include: Transceiver; a memory storing one or more instructions; as well as at least one processor connected to the transceiver and configured to execute one or more instructions to: When the access management function AMF identifies that the terminal is in a connected state or an inactive state and determines that the local location management function LLMF is used for the LCS: receiving, through the LLMF having a logical connection in the base station, a request message for a location-based service from the AMF, Generate protocol information based on the request information through the LLMF, sending a first radio resource control RRC message including the protocol information to the terminal, receiving, in response to the first RRC message, a response message including location-related information of the terminal from the terminal, sending the response message to the AMF, and In the case where the AMF identifies that the terminal is in an idle state and determines that a core network location management function CN LMF is used for the LCS: receiving, from the AMF, a first non-access stratum (NAS) message including an LTE location protocol (LPP) message, wherein the LPP message is generated by the CN LMF; Sending a second RRC message including the first NAS message to the terminal; In response to the second RRC message, receiving a third RRC message including a second NAS message from the terminal, the second NAS message including an LPP response message, the LPP response message including location-related information of the terminal; and Sending the second NAS message including the LPP response message to the AMF. 11 . The base station according to claim 10 , wherein the request information includes identification information about the terminal, or information about a base station to which the terminal is connected. 12 . The base station according to claim 10 , wherein the first RRC message includes an indicator corresponding to the LLMF, or includes the protocol information in an information element IE corresponding to the LLMF.

Images