WO2020145696A1 - Method for transmitting and receiving signal related to ebi in wireless communication system, and apparatus therefor - Google Patents

Abstract

A method for transmitting and receiving a signal for an access and mobility management function (AMF) in a wireless communication system, in one embodiment, comprises the steps of: determining, by the AMF, the number of EPS bearer IDs (EBIs); and collecting, by the AMF, at least one EBI from among EBIs allocated to protocol data unit (PDU) sessions, on the basis of the determined result, wherein the EBI allocated to the PDU session moved from a non-3GPP access to a 3GPP access, from among the EBIs allocated to the PDU sessions, is preferentially collected.

Description

Method for transmitting and receiving signal related to EBI in wireless communication system and apparatus therefor

The following description relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting and receiving signals related to EPS bearer ID (EBI).

Wireless communication systems have been widely deployed to provide various types of communication services such as voice and data. Generally, a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of the multiple access system include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency (SC-FDMA). division multiple access (MC), multi-carrier frequency division multiple access (MC-FDMA) systems.

In a wireless communication system, various radio access technologies (RATs) such as LTE, LTE-A, and WiFi are used, and 5G is included therein. The three main requirements areas of 5G are: (1) Enhanced Mobile Broadband (eMBB) area, (2) Massive Machine Type Communication (mMTC) area, and (3) Super-reliability and It includes the area of ultra-reliable and low latency communications (URLLC). Some use cases may require multiple areas for optimization, and other use cases may focus on only one key performance indicator (KPI). 5G supports these various use cases in a flexible and reliable way.

eMBB goes far beyond basic mobile Internet access, and covers media and entertainment applications in rich interactive work, cloud or augmented reality. Data is one of the key drivers of 5G, and it may not be possible to see dedicated voice services for the first time in the 5G era. In 5G, voice is expected to be handled as an application program simply using the data connection provided by the communication system. The main causes for increased traffic volume are increased content size and increased number of applications requiring high data rates. Streaming services (audio and video), interactive video and mobile internet connections will become more widely used as more devices connect to the internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing in mobile communication platforms, which can be applied to both work and entertainment. And, cloud storage is a special use case that drives the growth of uplink data rates. 5G is also used for remote work in the cloud, requiring much lower end-to-end delay to maintain a good user experience when a tactile interface is used. Entertainment For example, cloud gaming and video streaming are another key factor in increasing demand for mobile broadband capabilities. Entertainment is essential for smartphones and tablets anywhere, including high mobility environments such as trains, cars and airplanes. Another use case is augmented reality and information retrieval for entertainment. Here, augmented reality requires a very low delay and an instantaneous amount of data.

In addition, one of the most anticipated 5G use cases relates to the ability to seamlessly connect embedded sensors in all fields, namely mMTC. It is predicted that by 2020, there are 20 billion potential IoT devices. Industrial IoT is one of the areas where 5G plays a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.

URLLC includes new services that will transform the industry through ultra-reliable/low-latency links, such as remote control of the main infrastructure and self-driving vehicles. Reliability and level of delay are essential for smart grid control, industrial automation, robotics, drone control and coordination.

Next, a number of use cases will be described in more detail.

5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means to provide streams rated at hundreds of megabits per second to gigabit per second. This fast speed is required to deliver TV in 4K (6K, 8K and above) resolutions as well as virtual and augmented reality. Virtual Reality (VR) and Augmented Reality (AR) applications include almost immersive sports events. Certain application programs may require special network settings. For VR games, for example, game companies may need to integrate the core server with the network operator's edge network server to minimize latency.

Automotive is expected to be an important new driver for 5G, along with many use cases for mobile communications to vehicles. For example, entertainment for passengers requires simultaneous high capacity and high mobility mobile broadband. The reason is that future users continue to expect high quality connections regardless of their location and speed. Another example of application in the automotive field is the augmented reality dashboard. It identifies objects in the dark over what the driver sees through the front window and superimposes information that tells the driver about the distance and movement of the object. In the future, wireless modules will enable communication between vehicles, exchange of information between the vehicle and the supporting infrastructure, and exchange of information between the vehicle and other connected devices (eg, devices carried by pedestrians). The safety system guides alternative courses of action to help the driver drive more safely, reducing the risk of accidents. The next step will be remote control or a self-driven vehicle. This is very reliable and requires very fast communication between different self-driving vehicles and between the vehicle and the infrastructure. In the future, self-driving vehicles will perform all driving activities, and drivers will focus only on traffic beyond which the vehicle itself cannot identify. The technical requirements of self-driving vehicles require ultra-low delays and ultra-high-speed reliability to increase traffic safety to levels beyond human reach.

Smart cities and smart homes, referred to as smart societies, will be embedded in high-density wireless sensor networks. The distributed network of intelligent sensors will identify the conditions for cost and energy-efficient maintenance of a city or home. Similar settings can be made for each assumption. Temperature sensors, window and heating controllers, burglar alarms and consumer electronics are all connected wirelessly. Many of these sensors are typically low data rates, low power and low cost. However, for example, real-time HD video may be required in certain types of devices for surveillance.

The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of a distributed sensor network. The smart grid interconnects these sensors using digital information and communication technologies to collect information and act accordingly. This information can include supplier and consumer behavior, so smart grids can improve efficiency, reliability, economics, production sustainability and the distribution of fuels like electricity in an automated way. The smart grid can be viewed as another sensor network with low latency.

The health sector has a number of applications that can benefit from mobile communications. The communication system can support telemedicine that provides clinical care from a distance. This helps to reduce barriers to distance and can improve access to medical services that are not continuously available in remote rural areas. It is also used to save lives in critical care and emergency situations. A mobile communication based wireless sensor network can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Thus, the possibility of replacing cables with wireless links that can be reconfigured is an attractive opportunity in many industries. However, achieving this requires that the wireless connection operate with cable-like delay, reliability and capacity, and that management be simplified. Low latency and very low error probability are new requirements that need to be connected to 5G.

Logistics and freight tracking are important use cases for mobile communications that enable the tracking of inventory and packages from anywhere using location-based information systems. Logistics and cargo tracking use cases typically require low data rates, but require wide range and reliable location information.

The present invention discloses various embodiments related to EBI recovery, allocation, and the like.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary knowledge in the technical field to which the present invention belongs from the following description. Will be able to.

An embodiment of the present invention provides a method for transmitting and receiving a signal of an Access and Mobility Management function (AMF) in a wireless communication system, wherein the AMF determines the number of EPS bearer IDs (EBIs); And recovering at least one EBI among EBIs allocated to Protocol Data Unit (PDU) sessions by the AMF based on the determination result, and among the EBIs allocated to the PDU sessions, non- This is a method in which the EBI allocated to the PDU session moved from 3GPP access to 3GPP access is first recovered.

An embodiment, an Access and Mobility Management function (AMF) device in a wireless communication system, comprising: at least one processor; It includes at least one memory operably connected to the at least one processor, and the at least one processor determines the number of EPS bearer IDs (EBIs) and a Protocol Data Unit (PDU) session based on the determination result. At least one of the EBI allocated to the EBI is recovered, and among the EBIs allocated to the PDU session, the EBI allocated to the PDU session moved from non-3GPP access to 3GPP access is preferentially recovered.

The determination of the number of EBIs may be a determination as to whether the number of EBIs allocated to the PDU session related to 3GPP access exceeds the maximum number of EBIs available for the UE.

The determination of the number of EBIs may be performed based on the movement from the non-3GPP access of the PDU session to which the EBI is allocated to 3GPP access.

The movement may be performed in the UE Requested PDU Session Establishment procedure.

The determination of the number of EBIs may be performed based on re-activation in 3GPP access of a PDU session associated with non-3GPP access to which the EBI is assigned.

The reactivation may be performed in the Network Triggered Service Request procedure.

The reactivation may correspond to user plane activation of a PDU session.

The AMF may request the SMF to release EPS QoS parameters corresponding to the at least one EBI.

The request may be performed by Nsmf_PDUSession_UpdateSMContext request.

According to the present invention, EBI can be efficiently managed.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those skilled in the art from the following description. will be.

The drawings attached to this specification are intended to provide an understanding of the present invention, and to illustrate various embodiments of the present invention and to explain the principles of the present invention together with the description of the specification.

1 is a view showing a schematic structure of an Evolved Packet System (EPS) including an Evolved Packet Core (EPC).

2 is an exemplary diagram showing the architecture of a typical E-UTRAN and EPC.

3 is an exemplary diagram showing the structure of a radio interface protocol in a control plane.

4 is an exemplary diagram showing the structure of a radio interface protocol in a user plane.

5 is a flow diagram for explaining a random access process.

6 is a diagram illustrating a connection process in a radio resource control (RRC) layer.

7 is a diagram for explaining a 5G system.

8 to 9 are diagrams for explaining the embodiment(s) of the present invention.

10 illustrates a communication system 1 applied to the present invention.

11 illustrates a wireless device that can be applied to the present invention.

12 illustrates a signal processing circuit for a transmission signal.

13 shows another example of a wireless device applied to the present invention.

14 illustrates a portable device applied to the present invention.

15 illustrates a vehicle or an autonomous vehicle applied to the present invention.

16 illustrates a vehicle applied to the present invention.

17 illustrates an XR device applied to the present invention.

18 illustrates a robot applied to the present invention.

19 illustrates an AI device applied to the present invention.

The following embodiments are combinations of components and features of the present invention in a predetermined form. Each component or feature can be considered to be optional, unless expressly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, some components and/or features may be combined to form an embodiment of the present invention. The order of the operations described in the embodiments of the present invention can be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments.

Certain terms used in the following description are provided to help the understanding of the present invention, and the use of these specific terms may be changed to other forms without departing from the technical spirit of the present invention.

In some cases, in order to avoid obscuring the concept of the present invention, well-known structures and devices may be omitted, or block diagrams centered on the core functions of each structure and device may be illustrated. In addition, throughout this specification, the same components will be described using the same reference numerals.

Embodiments of the present invention may be supported by standard documents disclosed in connection with at least one of the Institute of Electrical and Electronics Engineers (IEEE) 802 series system, 3GPP system, 3GPP LTE and LTE-A system and 3GPP2 system. That is, steps or parts that are not described in order to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the documents. Also, all terms disclosed in this document may be described by the standard document.

The following technology can be used in various wireless communication systems. For clarity, 3GPP LTE and 3GPP LTE-A systems are mainly described below, but the technical spirit of the present invention is not limited thereto.

The terms used in this document are defined as follows.

-UMTS (Universal Mobile Telecommunications System): 3GPP-based 3GPP (Global System for Mobile Communication) based 3G Generation mobile communication technology.

-EPS (Evolved Packet System): An IP (Internet Protocol) based PS (packet switched) core network EPC (Evolved Packet Core) and a network system composed of access networks such as LTE/UTRAN. UMTS is an evolved network.

-NodeB: GERAN/UTRAN base station. It is installed outdoors and has a coverage of macro cells.

-eNodeB: E-UTRAN base station. It is installed outdoors and has a coverage of macro cells.

-UE (User Equipment): User equipment. The UE may be referred to in terms of a terminal, a mobile equipment (ME), a mobile station (MS), and the like. Further, the UE may be a portable device such as a laptop, a mobile phone, a PDA (Personal Digital Assistant), a smart phone, a multimedia device, or a non-portable device such as a personal computer (PC) or a vehicle-mounted device. In the context of MTC, the term UE or terminal may refer to an MTC device.

-HNB (Home NodeB): It is installed indoors as a base station of a UMTS network, and its coverage is on a micro cell scale.

-HeNB (Home eNodeB): It is installed indoors as a base station of EPS network, and the coverage is on a micro cell scale.

-MME (Mobility Management Entity): a network node of the EPS network that performs mobility management (Mobility Management; MM), session management (SM) functions.

-PDN-GW (Packet Data Network-Gateway)/PGW: a network node of an EPS network that performs UE IP address allocation, packet screening and filtering, and charging data collection.

-SGW (Serving Gateway): A network node of the EPS network that performs a function such as mobility anchor, mobility, packet routing, idle mode packet buffering, and triggering the MME to page the UE.

-NAS (Non-Access Stratum): upper stratum of the control plane between the UE and the MME. As a functional layer for signaling and traffic messages between the UE and the core network in the LTE/UMTS protocol stack, it supports the mobility of the UE and establishes a session management procedure to establish and maintain the IP connection between the UE and the PDN GW. Supporting is the main function.

-PDN (Packet Data Network): A network where a server supporting a specific service (eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server) is located.

-PDN connection: A logical connection between a UE and a PDN, expressed as one IP address (one IPv4 address and/or one IPv6 prefix).

-RAN (Radio Access Network): a unit including a NodeB, an eNodeB in a 3GPP network, and a Radio Network Controller (RNC) that controls them. It exists between UEs and provides connectivity to the core network.

-HLR (Home Location Register)/HSS (Home Subscriber Server): database containing subscriber information in 3GPP network. The HSS can perform functions such as configuration storage, identity management, and user state storage.

-Public Land Mobile Network (PLMN): A network configured for the purpose of providing mobile communication services to individuals. It can be configured separately for each operator.

-Proximity Service (or ProSe Service or Proximity based Service): Discovery between physically adjacent devices and mutual direct communication or communication through a base station or communication through a third device. At this time, user plane data is exchanged through a direct data path without going through a 3GPP core network (eg, EPC).

Evolved Packet Core (EPC)

1 is a view showing a schematic structure of an Evolved Packet System (EPS) including an Evolved Packet Core (EPC).

EPC is a core element of System Architecture Evolution (SAE) to improve the performance of 3GPP technologies. SAE is a research task to determine the network structure that supports mobility between various types of networks. SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies on an IP basis and providing improved data transmission capability.

Specifically, the EPC is a core network of an IP mobile communication system for a 3GPP LTE system, and can support packet-based real-time and non-real-time services. In an existing mobile communication system (i.e., a 2G or 3G mobile communication system), the core network is provided through two distinct sub-domains: circuit-switched (CS) for voice and packet-switched (PS) for data. The function was implemented. However, in the 3GPP LTE system, which is an evolution of the 3G mobile communication system, the sub-domains of CS and PS are unified into one IP domain. That is, in the 3GPP LTE system, the connection between the terminal having the IP capability (capability), the IP-based base station (e.g., eNodeB (evolved Node B)), EPC, application domain (e.g., IMS ( IP Multimedia Subsystem)). That is, EPC is an essential structure for implementing end-to-end IP services.

The EPC may include various components, and in FIG. 1, corresponding to some of them, Serving Gateway (SGW), Packet Data Network Gateway (GDN), Mobility Management Entity (MME), Serving GPRS (General Packet) Radio Service (Supporting Node), ePDG (enhanced Packet Data Gateway).

The SGW (or S-GW) is an element that functions as a boundary point between a radio access network (RAN) and a core network, and maintains a data path between the eNodeB and the PDN GW. In addition, when the terminal moves over an area served by the eNodeB, the SGW serves as a local mobility anchor point. That is, for mobility within the E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network defined after 3GPP Release-8), packets may be routed through the SGW. SGW also provides mobility with other 3GPP networks (RAN defined before 3GPP Release-8, e.g. UTRAN or GERAN (Global System for Mobile Communication (GSM)/Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.

The PDN GW (or P-GW) corresponds to the termination point of the data interface towards the packet data network. The PDN GW can support policy enforcement features, packet filtering, and charging support. Also, mobility management between 3GPP networks and non-3GPP networks (for example, untrusted networks such as Interworking Wireless Local Area Network (I-WLAN), Code Division Multiple Access (CDMA) networks or trusted networks such as WiMax) Can serve as an anchor point for.

Although the SGW and the PDN GW are configured as separate gateways in the example of the network structure of FIG. 1, two gateways may be implemented according to a single gateway configuration option.

The MME is an element that performs signaling and control functions to support access to the network connection of the UE, allocation of network resources, tracking, paging, roaming, and handover. The MME controls control plane functions related to subscriber and session management. The MME manages a number of eNodeBs and performs signaling for the selection of a conventional gateway for handover to other 2G/3G networks. In addition, the MME performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.

SGSN handles all packet data such as user mobility management and authentication to other 3GPP networks (eg GPRS networks).

The ePDG serves as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).

As described with reference to FIG. 1, a terminal having IP capability provides an IP service network provided by an operator (ie, an operator) via various elements in the EPC based on 3GPP access as well as non-3GPP access. (Eg, IMS).

In addition, FIG. 1 shows various reference points (eg, S1-U, S1-MME, etc.). In the 3GPP system, a conceptual link connecting two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point. Table 1 below summarizes the reference points shown in FIG. 1. In addition to the examples in Table 1, various reference points may exist according to a network structure.

Reference point	Explanation
S1-MME	Reference point for the control plane protocol between E-UTRAN and MME
S1-U	Reference point between E-UTRAN and Serving GW for the per bearer user plane tunneling and inter eNodeB path switching during handover during inter-eNB path switching and user plane tunneling per bearer
S3	A reference point between the MME and the SGSN that provides user and bearer information exchange for mobility between 3GPP access networks in idle and/or active states. This reference point can be used for PLMN-in- or PLMN-to-PLMN-to-PLMN-to-PLMN handover) (It enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state .This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).)
S4	(Reference point between SGW and SGSN providing related control and mobility support between GPRS core and SGW's 3GPP anchor function. It also provides related control and mobility support between GPRS Core if no direct tunnel is established. and the 3GPP Anchor function of Serving GW.In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.)
S5	A reference point that provides user plane tunneling and tunnel management between SGW and PDN GW. It provides user plane tunnelling and tunnel management between Serving GW and PDN GW.It is used when a connection to a PDN GW where SGW is not co-located is required due to UE mobility and required PDN connectivity. for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.)
S11	Reference point between MME and SGW
SGi	Reference point between PDN GW and PDN. The PDN may be a public or private PDN external to the operator, or may be, for example, an intra-operator PDN for providing an IMS service. This reference point corresponds to Gi of 3GPP access (It is the reference point between the PDN GW and the packet data network.Packet data network may be an operator external public or private packet data network or an intra operator packet data network, eg for provision of IMS services.This reference point corresponds to Gi for 3GPP accesses.)

Among the reference points illustrated in FIG. 1, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides trusted non-3GPP access and related control and mobility support between PDN GWs to the user plane. S2b is a reference point providing a user plane with support for related control and mobility between ePDG and PDN GW.

2 is an exemplary diagram showing the architecture of a typical E-UTRAN and EPC.

As shown, the eNodeB provides routing to the gateway, scheduling and transmission of paging messages, scheduling and transmission of broadcaster channels (BCH), and resources in the uplink and downlink while a Radio Resource Control (RRC) connection is active. The UE can perform functions for dynamic allocation to UE, configuration and provision for measurement of eNodeB, radio bearer control, radio admission control, and connection mobility control. Within the EPC, paging generation, LTE_IDLE state management, user plane encryption, SAE bearer control, NAS signaling encryption and integrity protection can be performed.

3 is an exemplary view showing a structure of a radio interface protocol in a control plane between a terminal and a base station, and FIG. 4 is an exemplary view showing a structure of a radio interface protocol in a user plane between a terminal and a base station. .

The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol consists of a horizontal physical layer, a data link layer, and a network layer, and vertically a user plane and control for data information transmission. It is divided into a control plane for signal transmission.

The protocol layers are based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems, L1 (first layer), L2 (second layer), L3 (third layer) ).

Hereinafter, each layer of the radio protocol in the control plane shown in FIG. 3 and the radio protocol in the user plane shown in FIG. 4 will be described.

The first layer, the physical layer, provides an information transfer service using a physical channel. The physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. Then, data is transferred between different physical layers, that is, between the physical layer of the transmitting side and the receiving side through a physical channel.

The physical channel is composed of several subframes on the time axis and several sub-carriers on the frequency axis. Here, one sub-frame (sub-frame) is composed of a plurality of symbols (Symbol) and a plurality of sub-carriers on the time axis. One subframe is composed of a plurality of resource blocks, and one resource block is composed of a plurality of symbols and a plurality of subcarriers. The transmission time interval (TTI), which is a unit time for data transmission, is 1 ms corresponding to one subframe.

The physical channels existing in the physical layer of the transmitting side and the receiving side are 3GPP LTE, according to the data channel PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) and control channel PDCCH (Physical Downlink Control Channel), It can be divided into a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and a Physical Uplink Control Channel (PUCCH).

Various layers exist in the second layer.

First, the medium access control (MAC) layer of the second layer serves to map various logical channels to various transport channels, and also multiplexes logical channels to map multiple logical channels to one transport channel. (Multiplexing). The MAC layer is connected to the upper layer RLC layer by a logical channel, and the logical channel is a control channel that transmits information of a control plane according to the type of information to be transmitted. It is divided into a traffic channel that transmits information of a user plane.

The radio link control (RLC) layer of the second layer divides data received from the upper layer (segmentation) and concatenation to adjust the data size so that the lower layer is suitable for transmitting data in a wireless section. Plays a role.

The packet data convergence protocol (PDCP) layer of the second layer is an IP that contains relatively large and unnecessary control information in order to efficiently transmit in a wireless section having a small bandwidth when transmitting an IP packet such as IPv4 or IPv6. It performs a header compression function that reduces the packet header size. In addition, in the LTE system, the PDCP layer also performs a security function, which is composed of encryption that prevents third-party data interception and integrity protection that prevents third-party data manipulation.

The radio resource control (hereinafter referred to as RRC) layer located at the top of the third layer is defined only in the control plane, and configuration and reset (Re) of radio bearers (abbreviated as RB) Responsible for control of logical channels, transport channels, and physical channels in relation to -configuration and release. At this time, RB means a service provided by the second layer for data transmission between the terminal and the E-UTRAN.

If there is an RRC connection (RRC connection) between the RRC layer of the terminal and the RRC layer of the wireless network, the terminal is in an RRC connected state (Connected Mode), otherwise it is in an RRC idle mode (Idle Mode).

Hereinafter, an RRC state of the UE and an RRC connection method will be described. The RRC state means whether the RRC of the terminal is in a logical connection with the RRC of the E-UTRAN, and if it is connected, it is called an RRC_CONNECTED state, and if not connected, it is called an RRC_IDLE state. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the corresponding terminal in a cell unit, and thus can effectively control the terminal. On the other hand, the terminal in the RRC_IDLE state cannot be detected by the E-UTRAN, and is managed by the core network in units of a tracking area (TA), which is a larger area unit than the cell. That is, the terminal in the RRC_IDLE state is identified only in the presence of the corresponding terminal in a larger regional unit than the cell, and in order to receive a normal mobile communication service such as voice or data, the terminal must transition to the RRC_CONNECTED state. Each TA is classified through TAI (Tracking Area Identity). The terminal may configure a TAI through a tracking area code (TAC), which is information broadcast in a cell.

When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell, then establishes an RRC connection in the cell and registers the terminal's information in the core network. After this, the terminal stays in the RRC_IDLE state. The UE staying in the RRC_IDLE state selects (re)cells as necessary and looks at system information or paging information. This is said to be camped on the cell. When the terminal staying in the RRC_IDLE state needs to establish an RRC connection, it makes an RRC connection with the RRC of the E-UTRAN through the RRC connection procedure and transitions to the RRC_CONNECTED state. There are several cases in which the terminal in the RRC_IDLE state needs to establish an RRC connection, for example, if a user's call attempt, data transmission attempt is required, or if a paging message is received from E-UTRAN. And sending a response message.

The non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.

Hereinafter, the NAS layer illustrated in FIG. 3 will be described in detail.

The eSM (evolved Session Management) belonging to the NAS layer performs functions such as Default Bearer Management and Dedicated Bearer Management, and controls the UE to use the PS service from the network. Default Bearer resource is characterized in that it is allocated from the network when it is connected to the network when it first accesses a specific Packet Data Network (PDN). At this time, the network allocates an IP address that the terminal can use so that the terminal can use the data service, and also allocates the QoS of the default bearer. LTE supports two types: a bearer with a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission and reception, and a non-GBR bearer with a best effort QoS characteristic without guaranteeing bandwidth. In the case of the default bearer, a non-GBR bearer is assigned. In the case of a dedicated bearer, a bearer having QoS characteristics of GBR or Non-GBR may be allocated.

The bearer allocated to the terminal in the network is called an EPS (evolved packet service) bearer, and when assigning the EPS bearer, the network allocates one ID. This is called EPS Bearer ID. One EPS bearer has QoS characteristics of a maximum bit rate (MBR) and/or a guaranteed bit rate (GBR).

5 is a flowchart illustrating a random access process in 3GPP LTE.

The random access process is used for the UE to obtain UL synchronization with a base station or to allocate UL radio resources.

The UE receives a root index and a physical random access channel (PRACH) configuration index from the eNodeB. Each cell has 64 candidate random access preambles defined by a ZC (Zadoff-Chu) sequence, and a root index is a logical index for a UE to generate 64 candidate random access preambles.

The transmission of the random access preamble is limited to specific time and frequency resources for each cell. The PRACH configuration index indicates a specific subframe and a preamble format capable of transmitting a random access preamble.

The UE transmits a randomly selected random access preamble to the eNodeB. The UE selects one of 64 candidate random access preambles. Then, the corresponding subframe is selected by the PRACH setting index. The UE transmits the selected random access preamble in the selected subframe.

The eNodeB that has received the random access preamble sends a random access response (RAR) to the UE. The random access response is detected in two stages. First, the UE detects a PDCCH masked with a random access-RNTI (RA-RNTI). The UE receives a random access response in a Medium Access Control (MAC) Protocol Data Unit (PDU) on the PDSCH indicated by the detected PDCCH.

6 shows a connection process in a radio resource control (RRC) layer.

As shown in FIG. 6, the RRC state is indicated according to whether the RRC is connected. The RRC state refers to whether the entity of the RRC layer of the UE has a logical connection with an entity of the RRC layer of the eNodeB, and when connected, is referred to as an RRC connected state. The state that is not set is called an RRC idle mode.

Since the UE in the connected state has an RRC connection, the E-UTRAN can detect the existence of the corresponding terminal in a cell unit, and thus can effectively control the UE. On the other hand, the idle mode (idle state) UE can not be identified by the eNodeB, the core network (Core Network) is managed by the tracking area (Tracking Area) unit that is a larger area than the cell. The tracking area is a collection unit of cells. That is, the idle mode (idle state) UE is only identified whether it exists in a large area unit, and in order to receive a normal mobile communication service such as voice or data, the terminal must transition to a connected state.

When the user first turns on the power of the UE, the UE first searches for an appropriate cell and then stays in an idle state in that cell. When the UE staying in the idle mode (idle state) needs to make an RRC connection, it finally makes an RRC connection with the RRC layer of the eNodeB through an RRC connection procedure and transitions to an RRC connected state. .

There are several cases in which the UE in the idle mode needs to establish an RRC connection, for example, a user's call attempt or uplink data transmission is required, or a paging message is received from the EUTRAN. In this case, a response message is transmitted.

In order for an idle mode UE to establish an RRC connection with the eNodeB, an RRC connection procedure must be performed as described above. The RRC connection process is largely the process in which the UE sends an RRC connection request message to the eNodeB, the process in which the eNodeB sends the RRC connection setup message to the UE, and the UE completes the RRC connection setting to the eNodeB. (RRC connection setup complete). This process will be described in more detail with reference to FIG. 6 as follows.

1) When the UE in the idle mode (Idle state) wants to establish an RRC connection for reasons such as a call attempt, data transmission attempt, or response to paging of an eNodeB, the UE first sends an RRC connection request message. Send to eNodeB.

2) When the RRC connection request message is received from the UE, when the radio resource is sufficient, the eNB accepts the RRC connection request of the UE and transmits a response message, an RRC connection setup message, to the UE .

3) When the UE receives the RRC connection setup message, it transmits an RRC connection setup complete message to the eNodeB. When the UE successfully transmits the RRC connection establishment message, the UE makes an RRC connection with the eNodeB and transitions to the RRC connection mode.

In the conventional EPC, the MME is divided into an Access and Mobility Management Function (AMF) and a Session Management Function (SMF) in the Next Generation system (or 5G CN (Core Network)). Therefore, NAS interaction with the UE and mobility management (MM) are performed by AMF, and session management (SM) is performed by SMF. In addition, the SMF manages the user plane function (UPF), which is a gateway for user traffic, that is, a user-plane function, which is controlled by the SMF in the control-plane part of the S-GW and P-GW in the conventional EPC. The user-plane part can be considered to be in charge of the UPF. There may be more than one UPF between the RAN and the DN (Data Network) for routing of user traffic. That is, the conventional EPC may be configured as illustrated in FIG. 7 in 5G. In addition, as a concept corresponding to PDN connection in the conventional EPS, a protocol data unit (PDU) session is defined in a 5G system. PDU session refers to an association between a UE and a DN providing PDU connectivity service of Ethernet type or unstructured type as well as IP type. In addition, UDM (Unified Data Management) performs a function corresponding to the HSS of the EPC, and PCF (Policy Control Function) performs a function corresponding to the PCRF of the EPC. Of course, the functions can be provided in an extended form to satisfy the requirements of the 5G system. For details on 5G system architecture, each function, and each interface, TS 23.501 is applied.

The 5G system is working on TS 23.501, TS 23.502 and TS 23.503. Therefore, in the present invention, the above standard is used as a key for 5G systems. Also, for more detailed architecture and contents related to NG-RAN, TS 38.300, etc. shall apply. The 5G system also supports non-3GPP access. Therefore, in section 4.2.8 of TS 23.501, the architecture and network elements for supporting non-3GPP access are described, and in section 4.12 of TS 23.502, non-3GPP access Procedures for supporting are described. An example of non-3GPP access is WLAN access, which may include both trusted and untrusted WLANs. AMF (Access and Mobility Management Function) of 5G system performs Registration Management (RM) and Connection Management (CM) for non-3GPP access as well as 3GPP access. In this way, the same AMF serves the UE for 3GPP access and non-3GPP access belonging to the same PLMN, so that one network function integrates and manages authentication, mobility management, and session management for UEs registered through two different accesses. Can apply.

Meanwhile, to support N26-based EPS interworking, EBI allocation (or assignment or allocation) as shown in FIG. 8 is defined. Referring to FIG. 8, PGW-C + SMF (or H-SMF when home-routed) is EBI (based on operator policy, S-NSSAI, User Plane Security Enforcement information, etc.) in QoS flow(s) in the PDU session. If it is determined that EPS bearer ID(s)) needs to be allocated, PGW-C + SMF calls Namf_Communication_EBIAssignment Request (PDU Session ID, ARP list) (via V-SMF Nsmf_ PDUSession_Update in case of home routed case).

When the V-SMF receives the Nsmf_PDUSession_Update request from the H-SMF for the EPS bearer ID allocation request, the V-SMF should call Namf_Communication_EBIAssignment Request (PDU Session ID, ARP list). If PGW-C + SMF (or H-SMF for home routing roaming) provides multiple PDU sessions for the same DNN, but provides different S-NSSAI for the UE, SMF is provided by the common UPF (PSA) EBI should only be requested for PDU sessions. If another UPF (PSA) provides the corresponding PDU session, the SMF selects one of the UPF (PSA) for this decision according to the operator policy.

Steps 3 to 6 of FIG. 8 can be applied only when the AMF needs to revocation the previously assigned EBI to the UE to provide a new SMF request from the EBI to the same UE.

In step 3 of FIG. 8, if there is no EBI available to the AMF, the AMF recovers the EBI allocated to the QoS flow(s) based on the ARP(s) and S-NSSAI stored in the PDU session establishment procedure. Or, you can cancel/withdraw (assign). When the EBI allocation is recalled, the AMF requests the associated SMF (called SMF serving the released resources) to release the mapped EPS QoS parameter corresponding to the recovered EBI, Nsmf_PDUSession_UpdateSMContext (EBI(s) to be revoked) Call The AMF stores the connection of the assigned EBI and ARP pair corresponding to the PDU session ID and SMF address.

Upon receiving the request of step 3, "SMF providing the released resource", (R)AN and UE to inform the removal of the mapped EPS QoS parameters corresponding to the recovered EBI, Namf_Communication_N1N2Message Transfer (N2 SM information (PDU Session ID, EBI(s) to be revoked), N1 SM container (PDU Session Modification Command (PDU Session ID, EBI(s) to be revoked))) is called (step 4). In the home routing roaming scenario, the H-SMF notifies the V-SMF to remove the mapped EPS bearer context corresponding to the EBI to be canceled, including the EBI to be canceled.

In step 5, if the UE is in the CM-CONNECTED state, AMF sends an N2 PDU session request (N2 SM information received from SMF, NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) message (R) To AN. In addition, detailed descriptions related to FIG. 8 are described in TS 23.502v15.4.1 (4.11.1.4.1 EPS bearer ID allocation, 4.11.1.4.2 EPS bearer ID transfer and 4.11.1.4.3 EPS bearer ID revocation). Reference is made to the prior art of the present invention.

Meanwhile, in the case of non-3GPP access PDU Session (ie, PDU Session associated with non-3GPP access), N26-based EPS Interworking is not used. That is, N26 based EPS interworking is for interworking between EPS/5GS of 3GPP access PDU Session (ie, PDU Session associated with 3GPP access). Therefore, if the EBI is assigned to the non-3GPP access PDU Session (this is in case the PDU Session is moved to 3GPP access or re-activated through 3GPP access), or if the EBI is assigned to the 3GPP access PDU Session, this PDU Session When moving to this non-3GPP access, whether to recover the EBI is a problem to be solved, and S2-1810709 (Discussion on EBI allocation for interworking from 5GC-N3IWF to EPS), S2-1811637 (EBI handling for non-3GPP access), S2-1812244 (Discussion on EBI allocation for interworking from 5GC-N3IWF to EPS).

In the above-mentioned documents such as S2-1810709, there is a method for allocating an EBI (EPS bearer ID) regardless of the type of access for which a PDU session is generated, and when the PDU session is created in 3GPP access, the PDU session is non-allocated. There is also a method of not recovering the EBI immediately even if moving to -3GPP access. In this case, an allocated EBI may exist for a non-3GPP PDU session, and an EBI processing method considering this is required. In particular, if there is a maximum number of EBIs that can be allocated to the UE, and this has already allocated the maximum EBIs to the UE, the AMF may perform step 3 (If the) in section 4.11.1.4.1 of the TS 23.502 (EPS bearer ID allocation). AMF has no available EBIs, the AMF may revoke an EBI that was assigned to QoS flow(s) based on the ARP(s) and S-NSSAI stored during PDU Session establishment, EBIs information in the UE context and local policies) As described above, when the EBI allocation request is received from the SMF, the EBI allocation operation may be performed after recovering the previously allocated EBI.

The following table excerpt from TS 24.301v15.5.0 for the maximum number of EBIs that can be assigned to a UE (or The UE's maximum number of active EPS bearer contexts in a PLMN or available EBI(s) for UE or enough EBI(s) for UE) See 2.

Example

Hereinafter, the EBI number and allocation method according to embodiments of the present invention will be described based on the description related to the allocation/recovery of the EBI. Hereinafter, allocating or retrieving the EBI to the PDU session may be interpreted as allocating or retrieving the EBI to the QoS flow of the PDU Session.

The AMF according to an embodiment may determine the number of EPS bearer IDs (EBIs) (S901 in FIG. 9). Here, the determination of the number of EBIs is the number of EBIs allocated to the PDU session related to 3GPP access to the UE. It may be a judgment as to whether or not to exceed the maximum number of EBIs available. Based on the determination result, the AMF may retrieve at least one EBI among EBIs assigned to Protocol Data Unit (PDU) sessions (S902 in FIG. 9).

At this time, among the EBIs allocated to the PDU sessions, the EBI allocated to the PDU session moved from non-3GPP access to 3GPP access may be preferentially recovered. If there is no discrimination point for other conditions, it is to recover the EBI for a PDU session transferred from non-3GPP access to 3GPP access. Since the EMF recovery operation of the AMF is performed to match the maximum number of EBIs that can be allocated to the UE, for example, if the maximum number of EBIs that can be allocated to the UE is 8 and the number of EBIs allocated to the 3GPP access PDU session is 10, 2 EBI can be recovered. According to the prior art, the maximum number of EBIs that can be allocated to the UE is 8, and the concept of not distinguishing between non-3GPP and 3GPP, that is, managing the total amount of EBI without considering access. In 5G, the service is provided based on the QoS flow, not the bearer. The number of PDU sessions that one UE can create per PDU Session is 15, and the number of QoS flows that can be included in one PDU Session is 63, whereas the bearer ID is It is relatively small, about 15. Therefore, in managing the total amount of EBI, the EBI allocated to the flow that has passed to non-3GPP (for example, WiFi), which is not passed to the EPS, is preferentially recovered, thereby increasing the efficiency of using the EBI that is relatively insufficient compared to the QoS flow. have.

In connection with the determination of the number of EBIs, the EBI is defined as defined in the UE Requested PDU Session Establishment (Non-roaming and Roaming with Local Breakout) procedure (section 4.3.2.2.1 of TS 23.502). If the assigned PDU session is moved from non-3GPP access to 3GPP access, or EBI-assigned PDU session related to non-3GPP access, as defined in the network trigger service request procedure (section 4.2.3.3 of TS 23.502). When re-activated in 3GPP access, the AMF may be to check whether the number of EBIs allocated to PDU sessions related to 3GPP access exceeds the maximum number of EBIs available for the UE. If exceeded, the AMF can retrieve the EBI assigned to the QoS flow(s) based on the ARP(s) and S-NSSAI, EBI information of UE context and local policy. When the EBI allocation is recalled, the AMF requests Nsmf_PDUSession_UpdateSMContext (EBI(s) to be revoked) to request the associated SMF (SMF serving the released resources) to release the mapped EPS QoS parameter corresponding to the recovered EBI. Call Thereafter, steps 4-6 defined in FIG. 8 are executed.

That is, the determination of the number of EBIs may be performed based on the movement from the non-3GPP access of the PDU session to which the EBI is allocated to 3GPP access, and the movement may be performed in the UE Requested PDU Session Establishment procedure. . Alternatively, the determination of the number of EBIs may be performed based on re-activation in 3GPP access of a PDU session related to non-3GPP access to which EBI is assigned, and the reactivation is a Network Triggered Service Request procedure It may be performed in. Here, the reactivation may correspond to user plane activation of the PDU session.

Subsequently, the AMF may request the SMF to release the EPS QoS parameter corresponding to the at least one EBI, and this request may be performed by Nsmf_PDUSession_UpdateSMContext request.

On the other hand, with respect to the EBI allocation procedure of FIG. 8, if there is no EBI available to the AMF in step 3, the AMF is assigned to QoS flow(s) based on the ARP(s) and S-NSSAI stored in the PDU session establishment procedure. The old EBI can be recovered (revoke or canceled/withdrawn). To determine if there is an EBI(s) available for the UE, the AMF considers the EBI(s) allocated for PDU session(s) associated only with 3GPP access. This means that the AMF does not count EBI(s) for PDU sessions associated with non-3GPP access. If the number of EBIs allocated by the AMF to the UE is stored/managed in the UE context, the AMF can count and store/manage only the number of EBIs allocated to the 3GPP access PDU Session.

If the EBI allocation is recovered, the AMF requests Nsmf_PDUSession_UpdateSMContext (EBI(s) to be) to request the related SMF (called SMF serving the released resources) to release the mapped EPS QoS parameter corresponding to the recovered EBI. revoked). The AMF may store the allocated EBI and ARP pair connections corresponding to the PDU session ID and SMF address.

The following Tables 3 to 5 are added based on the procedures defined in TS 23.502, and Figure 4.11.1.4.1-1 corresponds to FIG. 8.

Example communication system to which the present invention is applied

Without being limited thereto, various descriptions, functions, procedures, suggestions, methods and/or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication/connection (eg, 5G) between devices. have.

Hereinafter, with reference to the drawings will be illustrated in more detail. In the following drawings/description, the same reference numerals may exemplify the same or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise indicated.

10 illustrates a communication system 1 applied to the present invention.

Referring to FIG. 10, the communication system 1 applied to the present invention includes a wireless device, a base station and a network. Here, the wireless device means a device that performs communication using a wireless access technology (eg, 5G NR (New RAT), Long Term Evolution (LTE)), and may be referred to as a communication/wireless/5G device. Although not limited to this, the wireless device includes a robot 100a, a vehicle 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a hand-held device 100d, and a home appliance 100e. ), Internet of Thing (IoT) device 100f, and AI device/server 400. For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include a UAV (Unmanned Aerial Vehicle) (eg, a drone). XR devices include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, Head-Mounted Device (HMD), Head-Up Display (HUD) provided in vehicles, televisions, smartphones, It may be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, or the like. The mobile device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, smart glasses), a computer (eg, a notebook, etc.). Household appliances may include a TV, a refrigerator, and a washing machine. IoT devices may include sensors, smart meters, and the like. For example, the base station and the network may also be implemented as wireless devices, and the specific wireless device 200a may operate as a base station/network node to other wireless devices.

The wireless devices 100a to 100f may be connected to the network 300 through the base station 200. AI (Artificial Intelligence) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300. The network 300 may be configured using a 3G network, a 4G (eg, LTE) network, or a 5G (eg, NR) network. The wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but may also directly communicate (e.g. sidelink communication) without going through the base station/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. Vehicle to Vehicle (V2V)/Vehicle to everything (V2X) communication). In addition, the IoT device (eg, sensor) may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.

Wireless communication/ connections 150a, 150b, and 150c may be achieved between the wireless devices 100a to 100f/base station 200 and the base station 200/base station 200. Here, the wireless communication/connection is various wireless access such as uplink/downlink communication 150a and sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, IAB (Integrated Access Backhaul)). It can be achieved through technology (eg, 5G NR), and wireless devices/base stations/wireless devices, base stations and base stations can transmit/receive radio signals to each other through wireless communication/ connections 150a, 150b, 150c. For example, the wireless communication/ connections 150a, 150b, 150c can transmit/receive signals through various physical channels.To do this, based on various proposals of the present invention, for the transmission/reception of wireless signals, At least some of various configuration information setting processes, various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), resource allocation processes, and the like may be performed.

Example wireless device to which the present invention is applied

11 illustrates a wireless device that can be applied to the present invention.

Referring to FIG. 11, the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE, NR). Here, {the first wireless device 100, the second wireless device 200} is shown in FIG. 10 {wireless device 100x, base station 200} and/or {wireless device 100x), wireless device 100x }.

The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and/or one or more antennas 108. The processor 102 controls the memory 104 and/or transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate the first information/signal, and then transmit the wireless signal including the first information/signal through the transceiver 106. In addition, the processor 102 may receive the wireless signal including the second information/signal through the transceiver 106 and store the information obtained from the signal processing of the second information/signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, memory 104 may be used to perform some or all of the processes controlled by processor 102, or instructions to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. You can store software code that includes Here, the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 106 can be coupled to the processor 102 and can transmit and/or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and/or receiver. The transceiver 106 may be mixed with a radio frequency (RF) unit. In the present invention, the wireless device may mean a communication modem/circuit/chip.

The second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208. Processor 202 controls memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information/signal, and then transmit a wireless signal including the third information/signal through the transceiver 206. In addition, the processor 202 may receive the wireless signal including the fourth information/signal through the transceiver 206 and store the information obtained from the signal processing of the fourth information/signal in the memory 204. The memory 204 may be connected to the processor 202, and may store various information related to the operation of the processor 202. For example, the memory 204 is an instruction to perform some or all of the processes controlled by the processor 202, or to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. You can store software code that includes Here, the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 206 can be coupled to the processor 202 and can transmit and/or receive wireless signals through one or more antennas 208. Transceiver 206 may include a transmitter and/or receiver. Transceiver 206 may be mixed with an RF unit. In the present invention, the wireless device may mean a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described in more detail. Without being limited to this, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). The one or more processors 102 and 202 may include one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. Can be created. The one or more processors 102, 202 may generate messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. The one or more processors 102, 202 generate signals (eg, baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, suggestions and/or methods disclosed herein. , To one or more transceivers 106, 206. One or more processors 102, 202 may receive signals (eg, baseband signals) from one or more transceivers 106, 206, and descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein PDUs, SDUs, messages, control information, data, or information may be obtained according to the fields.

The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) May be included in one or more processors 102, 202. Descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software, and firmware or software may be implemented to include modules, procedures, functions, and the like. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein are either firmware or software set to perform or are stored in one or more processors 102, 202 or stored in one or more memories 104, 204. It can be driven by the above processors (102, 202). The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein may be implemented using firmware or software in the form of code, instructions and/or instructions.

The one or more memories 104, 204 may be coupled to one or more processors 102, 202, and may store various types of data, signals, messages, information, programs, codes, instructions, and/or instructions. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer readable storage medium, and/or combinations thereof. The one or more memories 104, 204 may be located inside and/or outside of the one or more processors 102, 202. Also, the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as a wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, radio signals/channels, and the like referred to in the methods and/or operational flowcharts of this document to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, and the like referred to in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein from one or more other devices. have. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202, and may transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, the one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and one or more transceivers 106, 206 may be described, functions described herein through one or more antennas 108, 208. , It may be set to transmit and receive user data, control information, radio signals/channels, etc. referred to in procedures, suggestions, methods and/or operation flowcharts. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports). The one or more transceivers 106 and 206 process the received wireless signal/channel and the like in the RF band signal to process the received user data, control information, wireless signal/channel, and the like using one or more processors 102 and 202. It can be converted to a baseband signal. The one or more transceivers 106 and 206 may convert user data, control information, and radio signals/channels processed using one or more processors 102 and 202 from a baseband signal to an RF band signal. To this end, the one or more transceivers 106, 206 may include (analog) oscillators and/or filters.

Signal processing circuit example to which the present invention is applied

12 illustrates a signal processing circuit for a transmission signal.

Referring to FIG. 12, the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. have. Although not limited to this, the operations/functions of FIG. 12 may be performed in processors 102, 202 and/or transceivers 106, 206 of FIG. The hardware elements of FIG. 12 may be implemented in the processors 102, 202 and/or transceivers 106, 206 of FIG. 11. For example, blocks 1010 to 1060 may be implemented in processors 102 and 202 of FIG. 11. Also, blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 11, and block 1060 may be implemented in the transceivers 106 and 206 of FIG. 11.

The codeword may be converted into a wireless signal through the signal processing circuit 1000 of FIG. 12. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (eg, UL-SCH transport block, DL-SCH transport block). The radio signal may be transmitted through various physical channels (eg, PUSCH, PDSCH).

Specifically, the codeword may be converted into a scrambled bit sequence by the scrambler 1010. The scramble sequence used for scramble is generated based on the initialization value, and the initialization value may include ID information of the wireless device. The scrambled bit sequence may be modulated by a modulator 1020 into a modulation symbol sequence. The modulation method may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), and the like. The complex modulated symbol sequence may be mapped to one or more transport layers by the layer mapper 1030. The modulation symbols of each transport layer may be mapped to the corresponding antenna port(s) by the precoder 1040 (precoding). The output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the precoding matrix W of N*M. Here, N is the number of antenna ports and M is the number of transport layers. Here, the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transformation) on complex modulation symbols. Further, the precoder 1040 may perform precoding without performing transform precoding.

The resource mapper 1050 may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbol, DFT-s-OFDMA symbol) in the time domain, and may include a plurality of subcarriers in the frequency domain. The signal generator 1060 generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices through each antenna. To this end, the signal generator 1060 may include an Inverse Fast Fourier Transform (IFFT) module and a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc. .

The signal processing process for the received signal in the wireless device may be configured as the inverse of the signal processing processes 1010 to 1060 of FIG. 12. For example, the wireless device (eg, 100 and 200 in FIG. 11) may receive a wireless signal from the outside through an antenna port/transceiver. The received radio signal may be converted into a baseband signal through a signal restorer. To this end, the signal recoverer may include a frequency downlink converter (ADC), an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Thereafter, the baseband signal may be restored to a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scramble process. The codeword can be restored to the original information block through decoding. Accordingly, the signal processing circuit (not shown) for the received signal may include a signal restorer, a resource de-mapper, a post coder, a demodulator, a de-scrambler and a decoder.

Wireless device application example to which the present invention is applied

13 shows another example of a wireless device applied to the present invention. The wireless device may be implemented in various forms according to use-example/service (see FIG. 10).

Referring to FIG. 13, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 11, and various elements, components, units/units, and/or modules ). For example, the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional elements 140. The communication unit may include a communication circuit 112 and a transceiver(s) 114. For example, the communication circuit 112 can include one or more processors 102,202 and/or one or more memories 104,204 of FIG. For example, the transceiver(s) 114 may include one or more transceivers 106,206 and/or one or more antennas 108,208 of FIG. 11. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls the overall operation of the wireless device. For example, the controller 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130. In addition, the control unit 120 transmits information stored in the memory unit 130 to the outside (eg, another communication device) through the wireless/wired interface through the communication unit 110, or externally (eg, through the communication unit 110). Information received through a wireless/wired interface from another communication device) may be stored in the memory unit 130.

The additional element 140 may be variously configured according to the type of wireless device. For example, the additional element 140 may include at least one of a power unit/battery, an input/output unit (I/O unit), a driving unit, and a computing unit. Although not limited to this, wireless devices include robots (FIGS. 10, 100A), vehicles (FIGS. 10, 100B-1, 100B-2), XR devices (FIGS. 10, 100C), portable devices (FIGS. 10, 100D), and household appliances. (Fig. 10, 100e), IoT device (Fig. 10, 100f), digital broadcasting terminal, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate/environment device, It may be implemented in the form of an AI server/device (Figs. 10 and 400), a base station (Figs. 10 and 200), and a network node. The wireless device may be mobile or may be used in a fixed place depending on use-example/service.

In FIG. 13, various elements, components, units/parts, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface, or at least some of them may be connected wirelessly through the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (eg, 130, 140) are connected through the communication unit 110. It can be connected wirelessly. Further, each element, component, unit/unit, and/or module in the wireless devices 100 and 200 may further include one or more elements. For example, the controller 120 may be composed of one or more processor sets. For example, the control unit 120 may include a set of communication control processor, application processor, electronic control unit (ECU), graphic processing processor, and memory control processor. As another example, the memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory (non- volatile memory) and/or combinations thereof.

Hereinafter, the implementation example of FIG. 13 will be described in more detail with reference to the drawings.

Examples of mobile devices to which the present invention is applied

14 illustrates a portable device applied to the present invention. The portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, a smart glass), and a portable computer (eg, a notebook). The mobile device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).

Referring to FIG. 14, the mobile device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ). The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 in FIG. 13, respectively.

The communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other wireless devices and base stations. The control unit 120 may perform various operations by controlling the components of the portable device 100. The controller 120 may include an application processor (AP). The memory unit 130 may store data/parameters/programs/codes/commands necessary for driving the portable device 100. Also, the memory unit 130 may store input/output data/information. The power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, and the like. The interface unit 140b may support connection between the mobile device 100 and other external devices. The interface unit 140b may include various ports (eg, audio input/output ports, video input/output ports) for connection with external devices. The input/output unit 140c may receive or output image information/signal, audio information/signal, data, and/or information input from a user. The input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.

For example, in the case of data communication, the input/output unit 140c acquires information/signal (eg, touch, text, voice, image, video) input from a user, and the obtained information/signal is transmitted to the memory unit 130 Can be saved. The communication unit 110 may convert information/signals stored in the memory into wireless signals, and transmit the converted wireless signals directly to other wireless devices or to a base station. In addition, after receiving a radio signal from another wireless device or a base station, the communication unit 110 may restore the received radio signal to original information/signal. After the restored information/signal is stored in the memory unit 130, it can be output in various forms (eg, text, voice, image, video, heptic) through the input/output unit 140c.

Examples of vehicles or autonomous vehicles to which the present invention is applied

15 illustrates a vehicle or an autonomous vehicle applied to the present invention. Vehicles or autonomous vehicles can be implemented as mobile robots, vehicles, trains, aerial vehicles (AVs), ships, and the like.

15, the vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and autonomous driving. It may include a portion (140d). The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110/130/140a through 140d correspond to blocks 110/130/140 in FIG. 13, respectively.

The communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with external devices such as other vehicles, a base station (e.g. base station, road side unit, etc.) and a server. The controller 120 may perform various operations by controlling elements of the vehicle or the autonomous vehicle 100. The controller 120 may include an electronic control unit (ECU). The driving unit 140a may cause the vehicle or the autonomous vehicle 100 to travel on the ground. The driving unit 140a may include an engine, a motor, a power train, wheels, brakes, and steering devices. The power supply unit 140b supplies power to the vehicle or the autonomous vehicle 100 and may include a wired/wireless charging circuit, a battery, and the like. The sensor unit 140c may obtain vehicle status, surrounding environment information, user information, and the like. The sensor unit 140c includes an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt sensor, a weight sensor, a heading sensor, a position module, and a vehicle forward /Reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illumination sensor, pedal position sensor, and the like. The autonomous driving unit 140d maintains a driving lane, automatically adjusts speed, such as adaptive cruise control, and automatically moves along a predetermined route, and automatically sets a route when a destination is set. Technology, etc. can be implemented.

For example, the communication unit 110 may receive map data, traffic information data, and the like from an external server. The autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the acquired data. The controller 120 may control the driving unit 140a such that the vehicle or the autonomous vehicle 100 moves along the autonomous driving path according to a driving plan (eg, speed/direction adjustment). During autonomous driving, the communication unit 110 may acquire the latest traffic information data non-periodically from an external server, and may acquire surrounding traffic information data from nearby vehicles. Also, during autonomous driving, the sensor unit 140c may acquire vehicle status and surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and driving plan based on newly acquired data/information. The communication unit 110 may transmit information regarding a vehicle location, an autonomous driving route, and a driving plan to an external server. The external server may predict traffic information data in advance using AI technology or the like based on the information collected from the vehicle or autonomous vehicles, and provide the predicted traffic information data to the vehicle or autonomous vehicles.

AR/VR and vehicle example to which the present invention is applied

16 illustrates a vehicle applied to the present invention. Vehicles can also be implemented as vehicles, trains, aircraft, ships, and the like.

Referring to FIG. 16, the vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input/output unit 140a, and a position measurement unit 140b. Here, blocks 110 to 130/140a to 140b correspond to blocks 110 to 130/140 in FIG. 13, respectively.

The communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other vehicles or external devices such as a base station. The controller 120 may control various components of the vehicle 100 to perform various operations. The memory unit 130 may store data/parameters/programs/codes/commands supporting various functions of the vehicle 100. The input/output unit 140a may output an AR/VR object based on information in the memory unit 130. The input/output unit 140a may include a HUD. The location measuring unit 140b may acquire location information of the vehicle 100. The location information may include absolute location information of the vehicle 100, location information within the driving line, acceleration information, location information with surrounding vehicles, and the like. The position measuring unit 140b may include GPS and various sensors.

For example, the communication unit 110 of the vehicle 100 may receive map information, traffic information, and the like from an external server and store them in the memory unit 130. The location measuring unit 140b may acquire vehicle location information through GPS and various sensors and store it in the memory unit 130. The control unit 120 may generate a virtual object based on map information, traffic information, and vehicle location information, and the input/output unit 140a may display the generated virtual object on a glass window in the vehicle (1410, 1420). In addition, the controller 120 may determine whether the vehicle 100 is normally operating in the driving line based on the vehicle location information. When the vehicle 100 deviates abnormally from the driving line, the control unit 120 may display a warning on the glass window in the vehicle through the input/output unit 140a. In addition, the control unit 120 may broadcast a warning message about driving abnormalities to nearby vehicles through the communication unit 110. Depending on the situation, the control unit 120 may transmit the location information of the vehicle and the information on the driving/vehicle abnormality to the related organization through the communication unit 110.

XR device example to which the present invention is applied

17 illustrates an XR device applied to the present invention. The XR device may be implemented as an HMD, a head-up display (HUD) provided in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like.

Referring to FIG. 17, the XR device 100a may include a communication unit 110, a control unit 120, a memory unit 130, an input/output unit 140a, a sensor unit 140b, and a power supply unit 140c. . Here, blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 in FIG. 13, respectively.

The communication unit 110 may transmit and receive signals (eg, media data, control signals, etc.) with other wireless devices, portable devices, or external devices such as a media server. Media data may include images, images, and sounds. The controller 120 may control various components of the XR device 100a to perform various operations. For example, the controller 120 may be configured to control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata creation and processing. The memory unit 130 may store data/parameters/programs/codes/instructions necessary for driving the XR device 100a/creating an XR object. The input/output unit 140a acquires control information, data, and the like from the outside, and may output the generated XR object. The input/output unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain XR device status, surrounding environment information, user information, and the like. The sensor unit 140b may include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and/or a radar, etc. have. The power supply unit 140c supplies power to the XR device 100a, and may include a wire/wireless charging circuit, a battery, and the like.

For example, the memory unit 130 of the XR device 100a may include information (eg, data, etc.) necessary for the generation of an XR object (eg, AR/VR/MR object). The input/output unit 140a may obtain a command for operating the XR device 100a from the user, and the control unit 120 may drive the XR device 100a according to a user's driving command. For example, when a user tries to watch a movie, news, etc. through the XR device 100a, the control unit 120 transmits the content request information through the communication unit 130 to another device (eg, the mobile device 100b) or Media server. The communication unit 130 may download/stream content such as a movie or news from another device (eg, the mobile device 100b) or a media server to the memory unit 130. The controller 120 controls and/or performs procedures such as video/image acquisition, (video/image) encoding, and metadata creation/processing for content, and is obtained through the input/output unit 140a/sensor unit 140b An XR object may be generated/output based on information about a surrounding space or a real object.

In addition, the XR device 100a is wirelessly connected to the portable device 100b through the communication unit 110, and the operation of the XR device 100a may be controlled by the portable device 100b. For example, the portable device 100b may operate as a controller for the XR device 100a. To this end, the XR device 100a may acquire 3D location information of the portable device 100b, and then generate and output an XR object corresponding to the portable device 100b.

Robot example to which the present invention is applied

18 illustrates a robot applied to the present invention. Robots can be classified into industrial, medical, household, military, etc. according to the purpose or field of use.

Referring to FIG. 18, the robot 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input/output unit 140a, a sensor unit 140b, and a driving unit 140c. Here, blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 in FIG. 13, respectively.

The communication unit 110 may transmit and receive signals (eg, driving information, control signals, etc.) with other wireless devices, other robots, or external devices such as a control server. The controller 120 may control various components of the robot 100 to perform various operations. The memory unit 130 may store data/parameters/programs/codes/commands supporting various functions of the robot 100. The input/output unit 140a obtains information from the outside of the robot 100 and outputs information to the outside of the robot 100. The input/output unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain internal information of the robot 100, surrounding environment information, user information, and the like. The sensor unit 140b may include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and a radar. The driving unit 140c may perform various physical operations such as moving a robot joint. In addition, the driving unit 140c may cause the robot 100 to run on the ground or fly in the air. The driving unit 140c may include an actuator, a motor, a wheel, a brake, a propeller, and the like.

Example AI device to which the present invention is applied

19 illustrates an AI device applied to the present invention. AI devices can be fixed devices or mobile devices, such as TVs, projectors, smartphones, PCs, laptops, digital broadcasting terminals, tablet PCs, wearable devices, set-top boxes (STBs), radios, washing machines, refrigerators, digital signage, robots, vehicles, etc. It can be implemented as a possible device.

Referring to FIG. 19, the AI device 100 includes a communication unit 110, a control unit 120, a memory unit 130, an input/output unit 140a/140b, a running processor unit 140c, and a sensor unit 140d It may include. Blocks 110 to 130/140a to 140d correspond to blocks 110 to 130/140 in FIG. 13, respectively.

The communication unit 110 uses wired/wireless communication technology to communicate with external devices such as other AI devices (eg, FIGS. 10, 100x, 200, 400) or AI servers (eg, 400 of FIG. 10) with wired and wireless signals (eg, sensor information). , User input, learning model, control signals, etc.). To this end, the communication unit 110 may transmit information in the memory unit 130 to an external device or transmit a signal received from the external device to the memory unit 130.

The controller 120 may determine at least one executable action of the AI device 100 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. Then, the control unit 120 may control the components of the AI device 100 to perform the determined operation. For example, the controller 120 may request, search, receive, or utilize data of the learning processor unit 140c or the memory unit 130, and may be determined to be a predicted operation or desirable among at least one executable operation. Components of the AI device 100 may be controlled to perform an operation. In addition, the control unit 120 collects history information including the user's feedback on the operation content or operation of the AI device 100 and stores it in the memory unit 130 or the running processor unit 140c, or the AI server ( 10, 400). The collected history information can be used to update the learning model.

The memory unit 130 may store data supporting various functions of the AI device 100. For example, the memory unit 130 may store data obtained from the input unit 140a, data obtained from the communication unit 110, output data from the running processor unit 140c, and data obtained from the sensing unit 140. In addition, the memory unit 130 may store control information and/or software code necessary for operation/execution of the control unit 120.

The input unit 140a may acquire various types of data from the outside of the AI device 100. For example, the input unit 140a may acquire training data for model training and input data to which the training model is applied. The input unit 140a may include a camera, a microphone, and/or a user input unit. The output unit 140b may generate output related to vision, hearing, or touch. The output unit 140b may include a display unit, a speaker, and/or a haptic module. The sensing unit 140 may obtain at least one of the internal information of the AI device 100, the surrounding environment information of the AI device 100, and user information using various sensors. The sensing unit 140 may include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and/or a radar, etc. have.

The learning processor unit 140c may train a model composed of artificial neural networks using the training data. The learning processor unit 140c may perform AI processing together with the learning processor unit of the AI server (FIGS. 10 and 400 ). The learning processor unit 140c may process information received from an external device through the communication unit 110 and/or information stored in the memory unit 130. Also, the output value of the running processor unit 140c may be transmitted to an external device through the communication unit 110 and/or stored in the memory unit 130.

Various embodiments of the present invention as described above have been mainly described for 3GPP systems, but can be applied to various mobile communication systems in the same manner.

Claims (13)

1. In the method of transmitting and receiving a signal of the Access and Mobility Management function (AMF) in a wireless communication system,

   Determining the number of EPS bearer IDs (EBIs) by the AMF; And

   Based on the determination result, the AMF recovering at least one EBI among EBIs assigned to Protocol Data Unit (PDU) sessions;

   It includes,

   Among the EBIs allocated to the PDU sessions, a method in which the EBI allocated to the PDU session moved from non-3GPP access to 3GPP access is first recovered.
2. According to claim 1,

   The determination of the number of EBIs is a determination as to whether or not the number of EBIs allocated to a PDU session related to 3GPP access exceeds the maximum number of EBIs available for the UE.
3. According to claim 1,

   The determination of the number of EBIs is performed based on the movement from non-3GPP access to 3GPP access of the PDU session to which the EBI is assigned.
4. According to claim 3,

   The movement is performed in the UE Requested PDU Session Establishment procedure.
5. According to claim 1,

   The determination of the number of EBIs is performed based on re-activated in 3GPP access of a PDU session related to non-3GPP access to which EBI is assigned.
6. The method of claim 5,

   The reactivation is performed in the Network Triggered Service Request procedure.
7. The method of claim 6,

   The reactivation corresponds to user plane activation of a PDU session.
8. According to claim 1,

   The AMF requests the SMF to release the EPS QoS parameter corresponding to the at least one EBI.
9. The method of claim 8,

   The request is performed by Nsmf_PDUSession_UpdateSMContext request.
10. In an Access and Mobility Management function (AMF) device in a wireless communication system,

    At least one processor;

    And at least one memory operably connected to the at least one processor,

    The at least one processor determines the number of EPS bearer IDs (EBIs), and retrieves at least one EBI among EBIs assigned to a Protocol Data Unit (PDU) session based on the determination result,

    Among the EBIs allocated to the PDU session, the EBI allocated to the PDU session moved from non-3GPP access to 3GPP access is first recovered.
11. The method of claim 10,

    The determination of the number of EBIs is to determine whether the number of EBIs allocated to PDU sessions related to 3GPP access exceeds the maximum number of EBIs available for the UE.
12. The method of claim 10,

    The determination of the number of EBIs is performed when the PDU session to which the EBI is assigned is performed based on movement from non-3GPP access to 3GPP access.
13. The method of claim 12,

    The movement is performed in the UE Requested PDU Session Establishment procedure, the device.

Images