WO2020032544A1

WO2020032544A1 - Method and device for wireless node communication in wireless communication system

Info

Publication number: WO2020032544A1
Application number: PCT/KR2019/009807
Authority: WO
Inventors: 김상범; 김성훈
Original assignee: 삼성전자 주식회사
Priority date: 2018-08-07
Filing date: 2019-08-06
Publication date: 2020-02-13

Abstract

In a method for a terminal to control access to a network in a wireless communication system according to an embodiment, the method may include: a step for triggering access to the network in an access-stratum (AS) layer; a step for determining whether a blocking timer for an access category corresponding to the triggered access is being driven in the AS layer; and a step for determining, when the blocking timer expires, that the blocking of the access category has been alleviated in the AS layer.

Description

Method and apparatus for wireless node communication in wireless communication system

The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for smoothly providing a service in a wireless communication system. More specifically, the present invention relates to a method and apparatus for transmitting and receiving data by a wireless node of a wireless communication system.

In order to meet the increasing demand for wireless data traffic since the commercialization of 4G communication system, efforts are being made to develop an improved 5G communication system or a pre-5G communication system. For this reason, a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE). The 5G communication system defined by 3GPP is called New Radio (NR) system. In order to achieve high data rates, 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and to increase the transmission distance of radio waves, beamforming, massive array multiple input / output (Full-Dimensional MIMO) and FD-MIMO in 5G communication systems Array antenna, analog beam-forming, and large scale antenna techniques have been discussed and applied to NR systems. In addition, in order to improve the network of the system, 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation And other technology developments are being made. In addition, in 5G systems, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC), Advanced Coding Modulation (ACM), and FBMC (Filter Bank Multi Carrier) and NOMA are advanced access technologies. Non-orthogonal multiple access and sparse code multiple access have been developed.

Meanwhile, the Internet is evolving from a human-centered connection network where humans create and consume information, and an Internet of Things (IoT) network that exchanges and processes information between distributed components such as things. Internet of Everything (IoE) technology, in which big data processing technology through connection with cloud servers and the like, is combined with IoT technology, is also emerging. In order to implement the IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between things, a machine to machine , M2M), Machine Type Communication (MTC), etc. are being studied. In an IoT environment, intelligent Internet technology (IT) services that provide new value in human life by collecting and analyzing data generated from connected objects may be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing IT (iInformation Technology) technology and various industries. It can be applied to.

Accordingly, various attempts have been made to apply the 5G communication system to the IoT network. For example, 5G communication such as a sensor network, a machine to machine (M2M), a machine type communication (MTC), and the like are implemented by techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access network (cloud RAN) as the big data processing technology described above may be an example of convergence of 5G technology and IoT technology.

As described above and various services can be provided according to the development of the mobile communication system, there is a demand for a method for effectively providing these services.

The disclosed embodiment is to provide an apparatus and method capable of effectively providing a service in a mobile communication system.

In the wireless communication system according to an embodiment of the present invention, a terminal performs access control on a network, wherein the above-described method includes: triggering access to the network at an access-stratum (AS) layer; Determining whether a block timer for the access category corresponding to the triggered access is running; and determining, at the AS layer, that the block for the access category has been levied when the block timer expires. Include.

According to the method for performing access control of the terminal according to the embodiment, the access control of the network of the terminal can be efficiently performed.

1 is a diagram illustrating an integrated access and backhaul (IAB) node to which an embodiment is applied.

2 is a flowchart illustrating an IAB to which an embodiment is applied.

3 is a flowchart illustrating a method of obtaining system information broadcasted by a neighboring IAB node for configuring an IAB according to an embodiment.

4 is a flowchart illustrating a method of performing access to a neighboring IAB node for configuring an IAB according to an embodiment.

5 is a flowchart illustrating a method of obtaining changed IAB configuration information, according to an exemplary embodiment.

6 is a block diagram illustrating an internal structure of a terminal according to an embodiment.

7 is a block diagram illustrating a configuration of a base station according to an embodiment.

8 is a diagram illustrating a structure of a next generation mobile communication system to which an embodiment is applied.

9 is a diagram for describing a process of performing access control of a connected mode or inactive mode terminal according to an embodiment.

10 is a flowchart illustrating a process of performing access control by a connected mode or inactive mode terminal according to an embodiment.

11 is a flowchart illustrating a process of performing an access control for an AS-triggered event by a connected mode or inactive mode terminal according to an embodiment.

12 is a flowchart illustrating an operation of a terminal AS according to an embodiment.

13 is a flowchart illustrating an operation of a terminal NAS according to an embodiment.

FIG. 14 is a flowchart illustrating a process of performing access control when a NAS performs access category mapping for an AS-triggered event according to an embodiment.

15 is a block diagram illustrating an internal structure of a terminal according to an embodiment.

16 is a block diagram illustrating a configuration of a base station according to an embodiment.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In describing the embodiments, descriptions of technical contents that are well known in the art to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. This is to more clearly communicate without obscure the subject matter of the present disclosure by omitting unnecessary description.

For the same reason, some of the components in the accompanying drawings are exaggerated, omitted or schematically illustrated. In addition, the size of each component does not reflect the actual size entirely. In each figure, the same or corresponding components are given the same reference numerals.

Advantages and features of the present disclosure, and methods of accomplishing the same will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various forms, and the present embodiments are merely provided to make the disclosure of the present disclosure complete, and those skilled in the art to which the present disclosure belongs. It is provided to fully inform the person having the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

It will be appreciated that each block of the flowchart illustrations and combinations of flowchart illustrations may be performed by computer program instructions. Since these computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, those instructions executed through the processor of the computer or other programmable data processing equipment may be described in flow chart block (s). It will create means to perform the functions. These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, and thus the computer usable or computer readable memory. It is also possible for the instructions stored in to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block (s). Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions for performing the processing equipment may also provide steps for performing the functions described in the flowchart block (s).

In addition, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of order. For example, the two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the corresponding function.

In this case, the term '~ part' used in the present embodiment refers to software or a hardware component such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and '~ part' performs certain roles. do. However, '~' is not meant to be limited to software or hardware. May be configured to reside in an addressable storage medium or may be configured to play one or more processors. Thus, as an example, '~' means components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, and the like. Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Functions provided within components and 'parts' may be combined into a smaller number of components and 'parts' or further separated into additional components and 'parts'. In addition, the components and '~' may be implemented to play one or more CPUs in the device or secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

1 is a conceptual diagram illustrating an integrated access and backhaul (IAB) node to which an embodiment is applied.

According to an embodiment, a mobile communication network includes a plurality of base stations and core network devices. Each base station and core network devices can carry control and data traffic over a wired backhaul interface. The IAB is a technology for replacing the wired backhaul according to an embodiment with the wireless backhaul using the RAN node. The wireless backhaul described above may eliminate the cost and time required to install a wired network in order to establish a wired backhaul. In addition, it is possible to establish a mobile communication network in a relatively short time in an urgently needed service area.

The IAB nodes 1a-15, 1a-20, and 1a-25 are RAN nodes that serve as wireless backhauls for carrying data traffic as well as a wireless access base station supporting terminals 1a-30 and 1a-35. Can mean. In an embodiment, the IAB node requesting traffic forwarding is called a child IAB node, and the IAB node forwarding the requested traffic is called a parent IAB node. An IAB node can be child, parent, or both. The IAB donor 1a-10 may refer to a RAN node connected to the core network 1a-05 and providing wireless backhaul function to the IAB nodes 1a-15, 1a-20, and 1a-25. Since the IAB nodes 1a-15, 1a-20, and 1a-25 are not directly connected to the core network, they can be connected to the IAB donor 1a-10 directly or via another IAB node. 1a-10) can send or receive control or data traffic to the core network. Each IAB node is connected to terminals located within a service area, and can transmit and receive data from the IAB donor 1a-10 or to the IAB donor 1a-10.

When a new IAB node 1 (1a-25) is created, the new IAB node 1 (1a-25) identifies the neighboring IAB nodes (1a-15, 1a-20) or IAB donor (1a-10), and the most appropriate node. You can perform the process of connecting to. In the present disclosure, this is called an IAB setup process. The present disclosure proposes an embodiment of a detailed process required in the IAB setup process. In particular, according to one embodiment, separate system information for the IAB node is defined, through which configuration information of the IAB node may be provided. In addition, the present disclosure proposes separate access control, separate random access resources, and separate RRC signaling for the IAB setup process according to an embodiment.

2 is a diagram illustrating an operation of an IAB to which an embodiment is applied.

IAB node 1 (1b-05) is a newly created node. On the other hand, IAB node 2 (1b-10) and IAB node 3 (1b-15) are nodes that have completed the existing IAB setup. In this embodiment, for example, the IAB donor 1b-20 is detected at the IAB node 2 (1b-10) and the IAB node 3 (1b-15), but not at the IAB node 1 (1b-05). Explain the scenario. Instead, IAB node 1 (1b-05) can detect adjacent IAB node 2 (1b-10) and IAB node 3 (1b-15). However, the disclosure can also be applied to scenarios where the IAB donor 1b-20 is sensed at IAB node 1 1b-05.

In steps 1b-25, IAB donor 1b-20, IAB node 2 (1b-10), and IAB node 3 (1b-15) are always periodically broadcast system information, i.e., Master Information Block (MIB) or Through the System Information Block 1 (SIB1), IAB-related essential information can be broadcast. Since the size of the information that can be stored in the MIB or SIB1 is limited, the above-mentioned essential information may need to be minimized. The essential information may normally indicate whether a node providing the above-described information supports the IAB function. According to an embodiment of the present disclosure, the IAB donor or the IAB node may include at least one of the following information as essential information.

First information: an indicator indicating whether or not the IAB function is supported

Second information: an indicator indicating whether a current IAB connection is available

Even if the cell supports the IAB function, it may be forbidden to add a new IAB node when it is already connected with many neighboring IAB nodes or when the wireless backhaul is congested. In this case, the indicator described above is set.

Third information: Barring configuration information for access for IAB setup

If you are already connected to many adjacent IAB nodes or if the wireless backhaul is congested, you need to control the addition of new IAB nodes. Access for IAB setup is mapped to a separately defined access category or access identity, and the cell can broadcast barring configuration information for the aforementioned access category or access identity. If the third information is provided, the second information may not be needed.

Fourth information: capability information of the wireless backhaul currently available through the IAB function

New IAB nodes may have the ability to expect in terms of latency and maximum possible data rate when connected to an IAB donor or a particular neighboring IAB node. If an IAB donor or neighboring IAB node provides this kind of information, it can be used to determine that node. However, in order to minimize latency or maximum possible data rate information, it may be necessary to quantize it. An embodiment of the present disclosure proposes an IAB category indicating a specific range of the above-described latency or maximum possible data rate information. In an embodiment, an IAB node supporting up to X data rate may broadcast IAB category 2 while an IAB node supporting up to Y data rate may be broadcast. Latency may be indicated as a separate category in a similar concept or as a category combined with the above-described data rate.

Fifth information: IAB hop count information to the cell

For new IAB nodes, the hop count from the IAB donor to the neighboring IAB node may be important. Higher hop counts mean higher latency. If you need to provide services with low latency, you may not be connected to neighboring IAB nodes with high hop counts. Thus, neighboring IAB nodes can provide hop count information. If the hop count is 0, this may mean that the node is an IAB donor.

6th information: an indicator indicating whether a corresponding cell is an IAB node or an IAB donor

The fifth information may also indicate whether the corresponding node is an IAB node or an IAB donor. However, since the fifth information indicates hop number information, a plurality of bits may be required. The IAB donor needs only the sixth information, which is a one-bit indicator. This is useful in terms of signaling overhead.

The essential information may have any size, even with the above-listed information. In addition, there may be additional configuration information required for the IAB setup process. For example, configuration information actually required for an IAB setup process such as random access, access control (Barring), and adaptation layer configuration information for the purpose of IAB setup may be included. This can be contrasted with the SIB1 containing information indicating whether the IAB node broadcasting it supports the IAB function. Therefore, this information is preferably transmitted through a separate SIBx, not the above-described MIB or SIB1.

General terminals have no reason to receive the above-described information. Therefore, if more specific information is stored in a separate SIBx for IAB only, it is possible to minimize the terminal from reading unnecessary information. In one embodiment, all remaining views may be included in the SIBx except for an indicator indicating whether to support the IAB function.

In step 1b-30, the new IAB node 1b-05 receives the SIB1 from the neighbor cell and, upon confirming the indicator described above from the SIB1, may additionally begin the procedure of acquiring the SIBx. SIB1 may include scheduling information of the above-described SIBx. SIBx belongs to the on-demand SI. That is, SIBx belongs to SIB that can be broadcast only upon request.

In step 1b-30, the new IAB node 1b-05 may request the above-described SIBx to the neighboring IAB node through msg1 (Message 1, SI request dedicated preamble) or msg3 (Message 3). However, SIBx may be transmitted periodically, at the discretion of the IAB node. The IAB nodes receive the above-described SIBx according to the scheduling information obtained from SIB1, and the general terminal does not need to receive them. The above-described SIBx may include the following information.

See description above

Third information: Barring configuration information for access for IAB setup.

See description above

Fourth information: capability information of a wireless backhaul that is currently supportable via IAB functionality. See description above

Fifth information: IAB hop count information to the cell. See description above

Sixth information: an indicator indicating whether the cell is an IAB node or an IAB donor. See description above

Seventh information: configuration information for determining an adjacent IAB node to be connected

In order for a new IAB node to connect with an adjacent IAB node, the new IAB node must be located within the service area of the adjacent IAB node. Therefore, a formula similar to S criteria for selecting or reselecting existing cells may be required. The seventh information may include minimum required Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) information that can be connected to the neighboring IAB node described above. In an embodiment, the new IAB node is a neighboring IAB node. The RSRP or RSRQ value measured by the reference signal of the reference signal must be larger than the minimum required RSRP or RSRQ value described above including a predetermined correction value to select the neighboring IAB node described above. It may be included in the existing SIB2, SIB3s or SIB4.

Eighth Information: Separate Random Access Resource for IAB Setup

The IAB setup is an operation for configuring the IAB wireless backhaul network, and may be of high importance. Therefore, a separate random access resource for the IAB is required. One embodiment of the present disclosure proposes to provide a separate random access preamble or random access frequency / time resource for the IAB.

Ninth information: Adaptation layer setting information

Traffic transmission between IAB nodes is done through a new adaptation layer. Therefore, the adjacent IAB node can broadcast the configuration information for the above-described adaptation layer.

In steps 1b-40, the new IAB node 1 1b-05 may select one neighboring IAB node according to a given equation. In order to calculate the above-described formula, the necessary information can be broadcast by neighboring IAB nodes using system information. The seventh information described above may correspond to this. In addition, at least one of the Public Land Mobile Network (PLMN) lists broadcasted by the IAB node 2 (1b-10) in SIB1 should be a PLMN supported by the IAB node 1 (1b-05). If none of the PLMNs belonging to the above-described PLMN list belong to the above-mentioned Home Public Land Mobile Network (HPLMN) or Equivalent HPLMN (EHPLMN) of IAB node 1 (1b-05), the above-described IAB node 1 (1b-05) ) Cannot be connected to the IAB node 2 1b-10 described above.

In step 1b-40, the new IAB node 1 (1b-05) may select the neighboring IAB node 2 (1b-10) and determine whether to allow access using the barring configuration information broadcasted by the node described above. have. New IAB node 1 (1b-05) can map access for IAB setup with a separately defined access category or access identity.

In steps 1b-45, the new IAB node 1 (1b-05) may perform a barring check using the barring configuration information for the aforementioned access category or access identity broadcasted by the neighboring IAB node 2 (1b-10). have.

A barring check based on an access identity and an access category will be described in more detail below. The access identity may be indication information defined within 3GPP, that is, specified in a standard document. The access identity may be used to indicate a specific access as shown in Table 1 below. For example, access identities can be used to indicate accesses classified as Access Class 11 through 15, multimedia services with priority (MPS), and mission critical services (MCS). have. Access Class 11 through 15 may direct access for operators only or for public use. In Table 1 below, the access class information may be information stored in a subscriber identity module / universal subscriber identity module (SIM / USIM) of a terminal or an IAB node.

Access categories can be divided into two types. For example, one kind may be a standardized access category. The above-mentioned category may be a category defined at the RAN level, ie specified in the standard document. This allows different operators to apply the same standardized access category. In the present disclosure, a category corresponding to Emergency may belong to a standardized access category. All accesses may correspond to at least one of the standardized access categories.

Another kind may be an operator-specific (non-standardized) access category. The aforementioned categories are defined outside 3GPP and may not be specified in the standard document. Thus, what an operator-specific access category means may vary from operator to operator. That is, the category and the nature of the existing ACDC (Application specific Congestion control for Data Communication) may be the same. Any access triggered on the terminal NAS may not be mapped to an operator-specific access category. The main difference from the existing ACDC is that the above-mentioned categories do not correspond only to the application, but also correspond to other elements besides the application, that is, service type, call type, terminal type, user group, signaling type, slice type, or a combination of the above elements. Can be. That is, it is possible to control whether to grant access to accesses belonging to other elements. The above-described access category may be used to indicate a specific access as shown in Table 2 below. Access categories 0 through 7 can be used to indicate a standardized access category, and access categories 32 through 63 can be used to indicate an operator-specific access category.

The operator server may provide the terminal NAS with information about operator-specific access category information (Management Object, MO) through NAS signaling or application level data transmission. The above information may indicate which element each operator-specific category corresponds to, such as an application. For example, the access category 32 may specify in the above-described information that the access category 32 corresponds to an access corresponding to a Facebook application. The base station may provide the terminal with the category list for providing the barring configuration information and the barring configuration information corresponding to each category using the system information. The terminal may include logical blocks of the NAS and the AS. In the present disclosure, the terminal described above may be matched with an IAB node requesting IAB setup.

The terminal NAS may map the triggered access to one or more of the above-described access identities and one of the above access categories according to a predetermined rule. In the case of an IAB node requesting IAB setup, a NAS and an AS may not be clearly distinguished as in a general terminal. Thus, in the case of an IAB node, certain logical blocks in the IAB may map access associated with IAB setup to one or more access identities and one access category. The above-described mapping operation may be performed in all RRC states, that is, in the connected mode (RRC_CONNECTED), the standby mode (RRC_IDLE), and the inactive mode (RRC_INACTIVE). The characteristics of each RRC state are listed as follows.

RRC_IDLE:

A UE specific DRX may be configured by upper layers;

UE controlled mobility based on network configuration;

The UE:

Monitors a Paging channel;

Performs neighboring cell measurements and cell (re-) selection;

-Acquires system information.

RRC_INACTIVE:

A UE specific DRX may be configured by upper layers or by RRC layer;

UE controlled mobility based on network configuration;

The UE stores the AS context;

The UE:

Monitors a Paging channel;

Performs neighboring cell measurements and cell (re-) selection;

Performs RAN-based notification area updates when moving outside the RAN-based notification area;

-Acquires system information.

RRC_CONNECTED:

The UE stores the AS context.

Transfer of unicast data to / from UE.

At lower layers, the UE may be configured with a UE specific DRX .;

For UEs supporting CA, use of one or more SCells, aggregated with the SpCell, for increased bandwidth;

-For UEs supporting DC, use of one SCG, aggregated with the MCG, for increased bandwidth;

Network controlled mobility, i.e. handover within NR and to / from E-UTRAN.

The UE:

Monitors a Paging channel;

Monitors control channels associated with the shared data channel to determine if data is scheduled for it;

Provides channel quality and feedback information;

Performs neighboring cell measurements and measurement reporting;

-Acquires system information.

The terminal NAS may transmit the mapped access identity and the access category to the terminal AS together with a service request.

If the terminal AS is provided with access identity or access category information with a message received from the terminal NAS in all RRC states, a barring check operation for determining whether this is allowed before performing the wireless connection caused by the above-described message. Can be performed. In the case of an IAB node requesting IAB setup, a NAS and an AS may not be clearly distinguished as in a general terminal. Therefore, in the case of an IAB node, a predetermined logical block in the IAB may perform a barring check for access related to the IAB setup. Through the barring check operation described above, if the above-described wireless connection is allowed, the IAB node may request the network to establish an RRC connection.

The operator may want to allow only certain types of services from among accesses corresponding to at least one of Access Class 11 through 15. Accordingly, the barring configuration information of the access category may be configured with ac-barringFactor and ac-barringTime.

The NAS is responsible for processes not directly related to wireless connection, i.e., authentication, service request, session management, while the AS may be responsible for processes related to wireless connection. The network can provide management object information to the NAS using OAM (application level data messages) or NAS messages. The above information may indicate which element each operator-specific access category corresponds to, such as an application. The NAS may use the information described above to determine which operator-specific category the triggered access maps to. Triggered access may include a new MMTEL service (voice call, video call), SMS transmission, new PDU session establishment, existing PDU session change, and the like. When the service is triggered, the NAS may map an access identity and an access category corresponding to the above-described property of the service. The service described above may not be mapped to any access identity, or may be mapped to one or more access identities. In addition, the above-described service may be mapped to one access category.

Under the assumption that it can be mapped with one access category, the NAS can first check whether the above-mentioned service is mapped with the operator-specific access category provided by the management object. If not mapped to any operator-specific access category, the NAS can map to one of the standardized access categories.

Under the assumption that it can map to multiple access categories, one service can be mapped to one operator-specific access category and one standardized access category. However, if it does not map to any operator-specific access category, the NAS can map to one of the standardized access categories. In the above mapping rule, the emergency service may be an exception.

The NAS may send a new session request or service request to the AS along with the mapped access identity and access category. The NAS can send a new session request in connected or inactive mode and a service request in standby mode. The AS may receive barring configuration information from system information broadcasted by the network. An exemplary embodiment of the ASN.1 structure of the barring configuration information is shown in Table 3 below, a detailed description thereof will be described later.

The AS may determine whether the service request is allowed by using the access identity, the access category information mapped by the NAS, and the corresponding barring setting information received from the network. In the present disclosure, the operation of determining whether the service request is allowed may mean a barring check. The terminal may receive system information including the access control configuration information and store the configuration information. Barring configuration information may be provided for each PLMN and access category. BarringPerCatList IE can be used to provide barring configuration information of access categories belonging to one PLMN. To this end, the PLMN id and barring configuration information of each access category may be included in the above-described IE in the form of a list. The barring setting information for each access category may include an access category id (or index) indicating a specific access category, a uac-BarringForAccessIdentity field, a uac-BarringFactor field, and a uac-Barringtime field.

The barring check operation can be as follows. First, each bit constituting uac-BarringForAccessIdentity may correspond to one access identity. If the above-described bit value is indicated as '0', access associated with the above-described access identity may be allowed. For at least one of the mapped access identities, access may be allowed if at least one of the corresponding bits in uac-BarringForAccessIdentity is '0'. For at least one of the mapped access identities, if any one of the corresponding bits in uac-BarringForAccessIdentity is not '0', an additional barring check may be additionally performed using the uac-BarringFactor field. The range of uac-BarringFactor α may be 0 ≦ α <1. The terminal AS derives one random value rand with 0 ≤ rand <1, and if the above-described random value is smaller than uac-BarringFactor, access is not prohibited. Otherwise, access may be regarded as prohibited. If it is determined that access is prohibited, the terminal AS may delay the access attempt for a predetermined time derived using the following equation. The terminal AS may drive a timer having the above-described time value. In the present disclosure, the timer described above may mean a barring timer.

If the above-described access is prohibited, the terminal AS may inform the terminal NAS of this. When the derived predetermined time expires, the terminal AS may notify the terminal NAS of requesting access again (barring alleviation). From this time, the terminal NAS may request access to the terminal AS again.

According to the predetermined rule described above, if a service request is allowed, the AS may request an RRC connection establishment or RRC connection resume from the network or transmit data related to a new session.

Assuming that a separate access category is defined for access for IAB setup, the aforementioned access category may need to be classified as either a standardized access category or an operator-defined access category.

If the new access category corresponding to the access for IAB setup described above is classified as an operator-defined access category, information about operator-defined access category information for the IAB node through NAS signaling or application level data transmission from the operator server ( Management Object, MO) may be provided. The above-described information may include information about which operator-defined access category number corresponds to the access for the IAB setup, as shown in Table 1 and Table 2 above. If the above information is not provided to the IAB node, the IAB node may map the access for IAB setup to a given standardized access category. The above-described predetermined access category may mean a standardized access category corresponding to MO-signalling. The IAB node receiving the IAB setup request may broadcast barring configuration information corresponding to the new operator-defined access category through system information.

If a new access category corresponding to an access for IAB setup is classified as a standardized access category, as shown in Table 1 and Table 2 above, it is determined in advance which standardized access category number corresponds to the access for IAB setup described above. Can be specified.

The IAB node receiving the IAB setup request can broadcast the barring configuration information corresponding to the new standardized access category through the system information. Typically one access may be mapped to multiple access categories. In one embodiment, in a NR access control, if a triggered access is mapable to an operator-defined access standard and a standardized access category, the operator-defined access category could be mapped in preference to the standardized access category. However, in the present disclosure, even though the IAB setup access can be mapped to a predetermined operator-defined access category and a dedicated standardized access category for the IAB setup access, the IAB node requesting the IAB setup is always a new standardized access category for the IAB setup access. You can to

Meanwhile, a separate access identity can be defined for access for IAB setup. When an access for IAB setup is triggered, the IAB node that triggers the access for IAB setup can map the aforementioned access to a new access identity. In addition, the above-described access can be mapped to a predetermined access category.

The predetermined access category may mean a standardized access category corresponding to MO-signalling or a new access category for separate IAB setup. The barring configuration information described above may be provided for each access category, and the configuration information may include bitmap information indicating whether to allow access for each access identity. The bitmap information may also include information on whether a separate access identity is allowed for access for new IAB setup. If indicated as allowed, the access can be considered to be allowed without performing a barring check.

Alternatively, the IAB node can map the access for IAB setup to an existing access identity. In the present disclosure, an access for IAB setup may be mapped to a specific access identity. When considered that access identity 11 corresponds to PLMN use, access identity 12 to security services, access identity 13 to public utilities (eg water / gas suppliers), access identity 14 to emergency services, and access identity 15 to PLMN staff, IAB Nodes can map access for IAB setup to access identity 11 or 15.

If the above-described access is allowed, IAB node 1 (1b-05) may attempt random access to the selected neighboring IAB node 2 (1b-10) using an IAB dedicated random access preamble. The reason for defining a separate access category or access identity is to allow you to consider IAB setup differently from other accesses. This is because the IAB setup constitutes a backhaul network, which can be a high priority.

In steps 1b-50, the IAB node 1 (1b-05) may perform random access using a separate random access preamble and random access frequency / time resources for the IAB. The total number of IAB dedicated random access preambles described above may be set equal to the total number of child IAB nodes that IAB node 2 (1b-10) can connect as a parent node. Although the above-described IAB node 2 (1b-10) indicates that the IAB is supported through the system information, the above-described IAB dedicated random access preamble may not be set. In this case, the above-described IAB node 1 (1b-05) may attempt random access using a general random access preamble.

In operation 1b-55, the IAB node 2 (1b-10) receiving the preamble may transmit a random access response (RAR) to the IAB node 1 (1b-05). If the above-mentioned RAR is not received or if the received RAR does not include the ID value of the transmitted preamble described above, IAB node 1 (1b-05) may postpone retransmission of the preamble for a specific time. have. The specific time described above may be derived through the backoff value stored in the MAC PDU of the RAR. For example, the backoff value described above may be a value between 0 and 1, and the specific value described above may be a random value between 0 and backoff. In the case of random access for IAB setup, the above-described specific time can be derived by multiplying the above-described stored backoff value by the scaling value provided as system information.

In steps 1b-60, the IAB node 1 1b-05 that has successfully received the RAR may send msg3. The above-described msg3 may include a predetermined RRC message. The neighbor IAB node 2 1b-10 may forward msg3 received with the radio resource indicated by the above-described RAR to the IAB donor 1b-20. In the present exemplary embodiment, a scenario in which IAB node 1 (1b-05) is connected to the IAB donor 1b-20 through a single hop, that is, IAB node 2 (1b-10), is described. 1b-05 may be connected to the IAB donor 1b-20 through one or more multiple hops. In this case, the control or data traffic of the above-described IAB node 1 (1b-05) may be forwarded to the IAB donor 1b-20 via a plurality of hops sequentially.

In steps 1b-65, for the above-described forwarding, a capsulation or an F1AP (F1 Application Protocol) message may be used in the adaptation layer for each hop-to-hop interval. The predetermined RRC message may be used to request the IAB setup from the IAB donor 1b-20 described above. The RRCSetupRequest message may be used as the predetermined RRC message. In general, the RRCSetupRequest message may be used to initialize the RRC establishment. The above-described predetermined RRC message may include a cause value indicating that the above-mentioned message is intended for IAB setup. In one embodiment, the RRCSetupRequest message may include a establishment cause value. In this case, a new cause value indicating IAB setup may be newly defined.

Since Msg3 is limited in size, it may not be possible to define a new cause value indicating the IAB setup described above. Therefore, in this case, an existing specific cause value may be used as the establishment cause value of the RRCSetupRequest message for IAB setup. In one embodiment, highPriorityAccess or MO-signalling may be set. Instead, a cause value or an indicator indicating that the above-described IAB setup is used may be included in the RRCSetupComplete message stored in msg5 (message 5).

In addition to the cause value indicating the IAB setup, an ID indicating the IAB node 1 (1b-05) may be included. The above-described ID may be used to determine the IAB node 1 (1b-05) between the IAB node 2 (1b-10) and the IAB donor (1b-20). When the connection establishment between IAB node 1 (1b-05) and IAB donor (1b-20) is completed, IAB nodes or IAB nodes to which IAB donor (1b-20) forwards traffic from IAB node 1 (1b-05) The setup message indicating that the above-described IAB node 1 (1b-05) may be supported may be transmitted to the neighboring IAB node (ie IAB node 2) forming direct connection with 1 (1b-05). At this time, the above-described ID may be used.

In steps 1b-70, the IAB node 1 (1b-05) and the IAB donor (1b-20) establish a non-access stratum (NAS) registration / authentication (NAS container of RRCSetupComplete message) and security settings through a predetermined RRC message. (Security Mode Command message / Security Mode Complete message) can be performed. Accordingly, similarly to the LTE system, security may be achieved between the IAB node 1 1b-05 and the IAB donor 1b-20. On the other hand, for IAB node 2 1b-10 forwarding traffic from IAB node 1 1b-05, authentication may be required for IAB node 1 1b-05. Without any authentication or security procedure, it is not possible to continue forwarding traffic from IAB node 1 (1b-05) to the IAB donor (1b-20). Therefore, when the registration, authentication, and security process between the IAB node 1 (1b-05) and the IAB donor (1b-20) is completed, the IAB donor (1b-20) sends a message to the IAB node 1 (1b-05). It is possible to send an indicator that IAB node 1 (1b-05) may continue to be supported to IAB node 2 (1b-10), which forwards traffic of the " At this time, IAB node 2 (1b-10) may support other IAB nodes other than IAB node 1 (1b-05). Therefore, an ID that can distinguish between IAB nodes is required. The ID may be included in the initial RRC message for the initial IAB node 1 (1b-05) by the setup process, or the Temporary C-RNTI (Cell-Radio Network) that the IAB node 2 (1b-10) includes in the RAR message. Temporary Identifier) value may be used. If the Temporary C-RNTI value included in the RAR message is utilized, IAB Node 1 (1b-05) includes the Temporary C-RNTI value included in the RAR in the RRCSetupRequest message, via IAB Node 2 (1b-10). Can be sent to the IAB donor (1b-20). After IAB node 1 (1b-05) attempts random access for IAB setup to IAB node 2 (1b-10), IAB node 2 (1b-10) is described in detail from the IAB donor 1b-20 for a predetermined time. If IAB does not receive the information about the supported support, IAB node 2 (1b-10) may disconnect from the IAB node 1 (1b-05).

Through the above-described setup process, the IAB node 1 (1b-05) can configure a wireless backhaul with the IAB donor (1b-20) through the IAB node 2 (1b-10). However, congestion in the wireless backhaul interval, capability change of the IAB node or IAB donor (1b-20), IAB node departure / down that serves as a hop due to a specific cause, no traffic in a specific wireless backhaul interval for a predetermined time, etc. If this occurs, the routing for the wireless backhaul described above may be readjusted or the capabilities or settings available at a particular IAB node may change. Therefore, depending on where the change occurred, the IAB node or IAB donor 1b-20 should inform the IAB nodes involved in the wireless backhaul configuration described above.

In step 1b-75, if the IAB donor 1b-20 determines that a reset / release is necessary for a predetermined cause, in step 1b-80, the IAB donor 1b-20 may be sent through a predetermined RRC message. This can be used to inform IAB nodes that require routing reset / release. In addition, setting information necessary for resetting / resetting routing may also be provided.

In steps 1b-85, if one IAB node constituting the wireless backhaul determines that routing reset / release is necessary according to a predetermined cause, the IAB node sends a message to the IAB donor 1b-20 through a predetermined RRC message. This may be informed, and neighbor IAB nodes associated with the radio backhaul may be informed by a predetermined RRC message or system information. Due to the structure of the IAB, RRC connections between IAB nodes may be very limited. Therefore, it may be advantageous to inform the reset / release of IAB routing through system information.

In an embodiment of the present disclosure, as shown in steps 1b-90, IAB routing reset / release may be indicated through paging downlink control information (DCI) or paging. Downlink Control Information (DCI) is an L1 message transmitted on a Physical Downlink Control Channel (PDCCH), and a paging DCI may be a DCI including paging information, in particular, a system information change indicator. The paging DCI in the present disclosure is an indicator indicating IAB routing reset / release, or an indicator indicating that IAB related system information that may cause routing reset / release has been changed, or an SIB or SI message including IAB related system information. It may include an indicator indicating that has changed.

In steps 1b-95 and 1b-105, the IAB node may broadcast the changed system information. The child IAB node may need to monitor paging from the parent IAB node according to a predetermined paging frame (PF) and paging occsion (PO). In one embodiment, the above-described PF and PO may have the following characteristics.

1) Each IAB node has a unique International Mobile Subscriber Identity (IMSI) value and is derived by applying the above-described IMSI value and parameter values provided by neighboring IAB nodes transmitting paging,

2) It is set as system information regardless of the ID of the IAB nodes, or predetermined;

3) All IAB nodes have the same IMSI value and are derived by applying the above-described IMSI value and parameter values provided by the neighboring IAB node transmitting paging.

In 2) and 3) described above, all IAB nodes may have the same PF and PO. Here, the PF is a radio frame starting with the PO, and the PO may be a plurality of time slots through which paging DCI or paging may be transmitted, that is, a subframe or an Orthogonal Frequency Division Multiplexing (OFDM) symbol. .

Since the general terminal does not need to receive system information about routing resetting / release, it may define a new P-RNTI dedicated to the IAB node to indicate the paging DCI or paging described above. The above-described P-RNTI may use a predefined value. The general terminal does not need to decode the DCI encoded with the new P-RNTI described above.

In step 1b-100, the IAB node that receives the paging DCI or paging indicating IAB routing reset / release may receive SIB1 and, if necessary, receive SIBx. SIBx may be provided on-demand. In one embodiment, if the SIB1 received from the neighboring IAB node indicates that it no longer supports IAB through the first information, or indicates that the IAB connection is no longer possible through the second information, then in SIBx The seventh information provided may be used to find another neighboring IAB node to support the wireless backhaul.

In steps 1b-110, IAB node 1 1b-05 may determine the change of the connected IAB node.

In steps 1b-115, IAB node 1 (1b-05) terminates the connection with existing IAB node 2 (1b-10) and decides to establish a new wireless backhaul connection with another neighboring IAB node 3 (1b-15). In this case, a disconnection process may be performed with the IAB node 2 (1b-10) that is connected for the existing wireless backhaul.

In step 1b-120, to inform release, IAB node 1 1b-05 may send a related MAC CE or L1 signaling or Adaptation layer control message at IAB node 2 1b-10. In addition, the IAB node 1 (1b-05) may transmit an RRC message requesting the IAB donor (1b-20) to disconnect the IAB node 2 (1b-10) and the connection to the new IAB node. The above-described IAB node 1 (1b-05) may trigger the IAB setup process at the new neighbor IAB node 3 (1b-15).

Due to the above-described routing reset or release, it is necessary to reset terminals that have been transmitting and receiving data from the IAB node 1 (1b-05). In steps 1b-125, intra-cell handover may be performed for terminals in the aforementioned connection mode state for bearer reset, security reset, retransmission reset, reset or reset of each L2 layer.

In steps 1c-05, the IAB node may initiate the process of selecting an adjacent IAB node (or IAB donor) for the wireless backhaul configuration.

In step 1c-10, the above-described IAB node may search for an adjacent IAB node or IAB donor that satisfies a predetermined signal quality. In one embodiment, the IAB node may preferentially select adjacent IAB nodes that provide the largest signal strength. The above-described signal quality may be derived by measuring a single side band (SSB) signal periodically transmitted by an adjacent IAB node. If the signal strength of the IAB donor satisfies a predetermined value or more, the IAB donor may be selected in preference to the neighboring IAB node. The above-described constant signal strength may be provided or predefined through system information.

In steps 1c-15, the IAB node may receive SIB1 from the selected neighboring IAB node (or IAB donor).

In step 1c-20, the 0IAB node may determine whether it can connect from SIB1 to the neighbor IAB node for wireless backhaul configuration. If the indicator (first information described above) indicating whether to support the IAB function is not included in SIB1, the above-described cell is a cell that does not support the IAB. In addition, even if the IAB function is supported, it is difficult to additionally support the above-described new IAB node when supporting other neighboring IAB nodes with the maximum number of connectable IAB nodes or when network congestion occurs. Therefore, the new IAB node can be suppressed or rejected from requesting the IAB connection with the second information or the third information described above. The above-described second information and third information may also be provided to SIB1. In addition, the above-described SIB1 may include scheduling information for SIBx.

In step 1c-25, if it is determined that the IAB node cannot connect, it may select another neighboring IAB node (or IAB donor).

In step 1c-30, if it is determined that the IAB node is connectable, the IAB node may receive the SIBx including detailed configuration information for configuring the wireless backhaul. The above-described SIBx may include configuration information actually required for the IAB setup process, such as random access, access control (Barring), and adaptation layer configuration information for the purpose of IAB setup. The SIBx described above may be provided in an on-demand manner since it does not need to be broadcast at all times periodically.

In steps 1d-05, the IAB node may transmit one random access preamble to the selected neighboring IAB node (or IAB donor). Through the system information, an IAB dedicated random access preamble may be provided, otherwise, a general random access preamble may be applied.

In steps 1d-10, the IAB node may receive a RAR from an adjacent IAB node.

In step 1d-15, the IAB node may transmit msg 3 using a radio resource indicated by the RAR. The above-described msg3 message may include an RRCSetupRequest, and the above-described RRC message may include a cause value indicating IAB setup. In the present exemplary embodiment, the RRCSetupRequest message for RRC establishment is reused, but a new RRC message for IAB setup may be defined.

In steps 1d-20, the IAB node may receive msg4 from the neighboring IAB node described above.

In steps 1d-25, the IAB node may send a msg5 message. The above-mentioned message may include cause value indicating IAB setup. This is a problem of size limitation of msg3, because the above-described cause value may not be included in msg3.

In step 1e-05, the IAB node may receive paging DCI or paging from the adjacent IAB node constituting the IAB.

In steps 1e-10, the IAB node may receive SIB1 from the neighboring IAB node described above.

In steps 1e-15, the IAB node may receive SIBx from the neighboring IAB node described above.

In steps 1e-20, the IAB node may determine whether the IAB node change / reset is necessary through the received SIB1 and SIBx described above.

In steps 1e-25, if the IAB node needs to be changed, the IAB node may perform a process of disconnecting an existing neighboring IAB node. The above-described release process may be requested by the IAB node to the above-described neighboring IAB node using a predetermined MAC CE, L1 signaling, Adaptation layer control message, or the like, or may be triggered by the neighboring IAB node using the RRCRelease message.

In step 1e-30, the IAB node may perform an IAB setup process with another neighboring IAB node after the above-described release process is completed.

Referring to FIG. 6, the terminal may include a radio frequency (RF) processor 1f-10, a baseband processor 1f-20, a storage unit 1f-30, and a controller 1f-40. have.

The RF processor 1f-10 may perform a function for transmitting and receiving a signal through a wireless channel such as band conversion and amplification of the signal. That is, the RF processor 1f-10 up-converts the baseband signal provided from the baseband processor 1f-20 into an RF band signal and transmits the same through an antenna, and baseband the RF band signal received through the antenna. Can be down converted to a signal. For example, the RF processor 1f-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), and the like. have. In FIG. 6, only one antenna is illustrated, but the above-described terminal may include a plurality of antennas. In addition, the RF processor 1f-10 may include a plurality of RF chains. In addition, the RF processor 1f-10 may perform beamforming. For the above-described beamforming, the RF processor 1f-10 may adjust phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor may perform MIMO (Multi Input Multi Output), and may receive multiple layers when performing the MIMO operation.

The baseband processor 1f-20 may perform a conversion function between the baseband signal and the bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processor 1f-20 may generate complex symbols by encoding and modulating a transmission bit string. In addition, when receiving data, the baseband processor 1f-20 may restore the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1f-10. For example, in accordance with an orthogonal frequency division multiplexing (OFDM) scheme, during data transmission, the baseband processor 1f-20 generates complex symbols by encoding and modulating a transmission bit string, and performs the above-described complex symbols on subcarriers. After mapping to, OFDM symbols may be configured through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 1f-20 divides the baseband signal provided from the RF processor 1f-10 into OFDM symbol units and is mapped to subcarriers through a fast fourier transform (FFT) operation. After recovering the signals, the received bit stream may be restored by demodulation and decoding.

The baseband processor 1f-20 and the RF processor 1f-10 may transmit and receive signals as described above. Accordingly, the baseband processor 1f-20 and the RF processor 1f-10 described above may be referred to as a transmitter, a receiver, a transceiver, or a communicator. Furthermore, at least one of the baseband processor 1f-20 and the RF processor 1f-10 may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processor 1f-20 and the RF processor 1f-10 may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies described above may include a wireless LAN (eg, IEEE 802.11), a cellular network (eg, LTE), and the like. In addition, the different frequency bands described above may include a super high frequency (SHF) (eg, 2.NRHz, NRhz) band and a millimeter wave (eg, 60 GHz) band. The terminal may transmit and receive signals to and from the base station using the baseband processor 1f-20 and the RF processor 1f-10. Here, the signal may include control information and data.

The storage unit 1f-30 may store data such as a basic program, an application program, and setting information for the operation of the terminal described above. In particular, the storage unit 1f-30 may store information related to the second access node performing wireless communication using the second wireless access technology. The storage unit 1f-30 may provide the stored data according to the request of the controller 1f-40 described above. The storage unit 1f-30 may be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, and the like. In addition, the storage unit 1f-30 may be configured of a plurality of memories. In one embodiment, the storage unit 1f-30 may store a program for supporting beam-based cooperative communication.

The controller 1f-40 controls the overall operations of the terminal described above. For example, the controller 1f-40 may transmit and receive a signal through the baseband processor 1f-20 and the RF processor 1f-10. In addition, the control unit 1f-40 can record and read data in the storage unit 1f-40. To this end, the controller 1f-40 may include at least one processor. For example, the controller 1f-40 may include a communication processor (CP) for performing control for communication and an application processor (AP) for controlling a higher layer such as an application program.

7 is a block diagram illustrating a configuration of a main station in a wireless communication system according to an embodiment.

As shown in FIG. 7, the base station includes an RF processor 1g-10, a baseband processor 1g-20, a backhaul communication unit 1g-30, a storage unit 1g-40, and a controller 1g-50. It may include.

The RF processor 1g-10 may perform a function for transmitting and receiving a signal through a wireless channel such as band conversion and amplification of the signal. That is, the RF processor 1g-10 up-converts the baseband signal provided from the baseband processor 1g-20 into an RF band signal and transmits the same through an antenna, and baseband the RF band signal received through the antenna. Can be downconverted to a signal. For example, the RF processor 1g-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. In FIG. 7, only one antenna is shown, but the above-described first access node may have a plurality of antennas. In addition, the RF processor 1g-10 may include a plurality of RF chains. In addition, the RF processor 1g-10 may perform beamforming. For the beamforming described above, the RF processor 1g-10 may adjust the phase and the magnitude of each of the signals transmitted and received through the plurality of antennas or antenna elements. The RF processor may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processor 1g-20 may perform a conversion function between the baseband signal and the bit string according to the physical layer standard of the first wireless access technology. For example, during data transmission, the baseband processor 1g-20 may generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processor 1g-20 may restore the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1g-10. For example, in accordance with the OFDM scheme, during data transmission, the baseband processor 1g-20 generates complex symbols by encoding and modulating a transmission bit stream, maps the above-described complex symbols to subcarriers, and then IFFT. OFDM symbols may be configured through operation and CP insertion. In addition, upon receiving data, the baseband processor 1g-20 divides the baseband signal provided from the RF processor 1g-10 into OFDM symbol units and restores signals mapped to subcarriers through an FFT operation. The received bit stream may be restored by performing demodulation and decoding. The baseband processor 1g-20 and the RF processor 1g-10 may transmit and receive signals as described above. Accordingly, the baseband processor 1g-20 and the RF processor 1g-10 described above may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

The backhaul communication unit 1g-30 may provide an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1g-30 converts the bit string transmitted from the above-described main base station to another node, for example, an auxiliary base station, core network, etc., into a physical signal, and converts the physical signal received from the above-described other node. Can be converted to a bit string.

The storage unit 1g-40 may store data such as a basic program, an application program, and setting information for the operation of the main station described above. In particular, the storage unit 1g-40 may store information on a bearer allocated to the connected terminal, a measurement result reported from the connected terminal, and the like. In addition, the storage unit 1g-40 may store information that is a criterion for determining whether to provide or terminate multiple connections to the terminal. The storage 1g-40 may provide stored data at the request of the controller 1g-50.

The controller 1g-50 controls the overall operations of the main station described above. For example, the controller 1g-50 may transmit and receive signals through the baseband processor 1g-20 and the RF processor 1g-10 or through the backhaul communication unit 1g-30. In addition, the controller 1g-50 may record and read data in the storage 1g-40. To this end, the controller 1g-50 may include at least one processor.

8 is a diagram illustrating a structure of a next generation mobile communication system to which an embodiment is applied. Referring to FIG. 8, a radio access network of a next generation mobile communication system (New Radio, NR, or 5G) includes a next generation base station (New Radio Node B, hereinafter referred to as gNB) 2a-10 and an AMF 2a-05, New Radio Core Network. It can be composed of). The user terminal (New Radio User Equipment, NR UE or terminal) 2a-15 may access an external network through the gNB 2a-10 and the AMF 2a-05.

In FIG. 8, the gNB may correspond to an eNB (Evolved Node B) of the LTE system. The gNB is connected to the NR UE through a radio channel and may provide superior service than the existing Node B (2a-20). In the next generation mobile communication system, since all user traffic is serviced through a shared channel, an apparatus for collecting and scheduling state information such as buffer states, available transmit power states, and channel states of UEs is required. 2a-10) may be in charge. One gNB can typically control multiple cells. In order to implement ultra-high speed data transmission compared to LTE, the mobile station may have a conventional maximum bandwidth or more, and an additional beamforming technique may be further combined using an orthogonal frequency division multiplexing (OFDM) as a wireless access technology. In addition, an adaptive modulation & coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the UE can be applied. The AMF 2a-05 may perform functions such as mobility support, bearer setup, QoS setup, and the like. The AMF 2a-05 may be connected to a plurality of base stations as a device for various control functions as well as a mobility management function for a terminal. In addition, the next generation mobile communication system may be linked to the LTE system, and the AMF 2a-05 may be connected to the MME 2a-25 through a network interface. The MME 2a-25 may be connected to the eNB 2a-30 which is an existing base station. The terminal supporting the LTE-NR Dual Connectivity may transmit and receive data while maintaining the connection to the eNB 2a-30 as well as the gNB 2a-10 (2a-35).

In the embodiment described with reference to FIG. 9, a method of effectively providing access control configuration information based on an access identity and an access category is proposed. An access identity is an indication of information defined within 3GPP, that is, specified in a standard document. The above-described access identity is used to indicate a specific access as shown in Table 4 below. The access identity may indicate mainly access classes 11 to 15 classified as access classes, multimedia priorities (MPS), and special purpose services (MCS). Access Class 11 to 15 described above may direct access for operators or for public use only.

Access categories can be divided into two types. One kind is the standardized access category. The above-mentioned categories are the categories defined at the RAN level, ie specified in the standard document. This allows different operators to apply the same standardized access category. In the present disclosure, a category corresponding to Emergency may belong to the standardized access category described above. All accesses may correspond to at least one of the standardized access categories described above.

Another kind is the operator-specific (non-standardized) access category. The aforementioned categories are defined outside 3GPP and are not specified in the standard document. Thus, the meaning of one operator-specific access category for each operator may be different. This is the same as the category in the existing ACDC (Application specific Congestion control for Data Communication). At the terminal NAS, any access triggered may not be mapped to an operator-specific access category. The main difference from the existing ACDC is that the above-mentioned categories correspond not only to the application but also to other elements besides the application, that is, service type, call type, terminal type, user group, signaling type, slice type, or a combination of the above-described elements. Can be. That is, it is possible to control whether to grant access to accesses belonging to other elements. The above-described access category may be used to indicate a specific access as shown in Table 5 below. Access categories 0 through 7 can be used to indicate a standardized access category, and access categories 32 through 63 can be used to indicate an operator-specific access category.

The operator server 2b-25 may provide the terminal NAS b-10 with information about operator-specific access category information (Management Object, MO) through NAS signaling or application level data transmission. The above information may indicate which element each operator-specific category corresponds to, such as an application. For example, the access category 32 may specify in the above-described information that the access category 32 corresponds to an access corresponding to a Facebook application. The base station 2b-20 may provide the terminal 2b-05 with a category list for providing barring configuration information and barring configuration information corresponding to each category using the system information. The terminal 2b-05 may include logical blocks of the NAS 2b-10 and the access stratum 2b-15.

The terminal NAS 2b-10 may map the triggered access to one or more of the above-described access identities and one of the above-described access categories according to a predetermined rule. The above-described mapping operation may be performed in all RRC states, that is, in the connected mode (RRC_CONNECTED), the standby mode (RRC_IDLE), and the inactive mode (RRC_INACTIVE). The characteristics of each RRC state can be listed as follows.

RRC_IDLE:

A UE specific DRX may be configured by upper layers;

UE controlled mobility based on network configuration;

The UE:

Monitors a Paging channel;

Performs neighboring cell measurements and cell (re-) selection;

-Acquires system information.

RRC_INACTIVE:

A UE specific DRX may be configured by upper layers or by RRC layer;

UE controlled mobility based on network configuration;

The UE stores the AS context;

The UE:

Monitors a Paging channel;

Performs neighboring cell measurements and cell (re-) selection;

-Acquires system information.

RRC_CONNECTED:

The UE stores the AS context.

Transfer of unicast data to / from UE.

At lower layers, the UE may be configured with a UE specific DRX .;

Network controlled mobility, i.e. handover within NR and to / from E-UTRAN.

The UE:

Monitors a Paging channel;

Provides channel quality and feedback information;

Performs neighboring cell measurements and measurement reporting;

-Acquires system information.

Alternatively, in the access category mapping described above, one access may be additionally mapped to one operator-specific access category if it can be mapped to one standardized access category. The above-described terminal NAS 2b-10 may transmit the above-described mapped access identity and access category to the above-described terminal AS 2b-15 together with the service request.

If the terminal AS 2b-15 is provided with the above-described access identity or access category information together with the message received from the terminal NAS 2b-10 in all RRC states, performing the wireless connection caused by the above-described message. You can perform a barring check operation to determine whether this is allowed before.

If the wireless connection is allowed through the barring check operation described above, the terminal 2b-05 may request the RRC connection establishment from the network. In one embodiment, the NAS 2b-10 of the connected mode or inactive mode terminal may transmit the access identity and the access category to the terminal AS 2b-15 for the following reason (2b-30). In the present disclosure, the following reasons are collectively referred to as 'new session request'.

new MMTEL (Multimedia Telephony) voice or video session

-sending of SMS (SMS over IP, or SMS over NAS)

new PDU session establishment

existing PDU session modification

-service request to re-establish the user plane for an existing PDU session

On the other hand, the NAS 2b-10 of the standby mode terminal may transmit an access identity and an access category to the terminal AS 2b-15 at the time of a service request.

The terminal AS 2b-15 may determine whether the access triggered by the terminal NAS 2b-10 is allowed using the barring configuration information described above (barring check).

The operator may want to allow only certain types of services from among accesses corresponding to at least one of Access Class 11 through 15. Accordingly, one embodiment of the present disclosure may be characterized in that the access to the access class 11, 12, 13, 14, 15 that is indicated by the access identity is determined whether to allow access according to the attribute distinguished by the access category. To this end, an embodiment proposes a method of configuring barring configuration information of an access identity or an access category. In the present disclosure, for example, it is assumed that the barring setting information of the above-described access category is composed of an ac-barringFactor and an ac-barringTime like the conventional barring setting information of ACB (Access Class Barring) or ACDC.

10 is a diagram for describing a process of performing access control by a connected mode or inactive mode terminal according to an embodiment.

Referring to FIG. 10, the terminal 2c-05 includes a NAS 2c-10 and an AS 2c-15. The NAS described above is responsible for processes not directly related to the wireless connection, i.e., authentication, service request, session management, while the AS described above may be responsible for processes related to the wireless connection.

In steps 2c-25, the network 2c-20 may provide management object information to the NAS described above using an OAM (application level data message) or NAS message. The above information may indicate which element, such as an application, each operator-specific access category corresponds to. The NAS 2c-10 may use the information described above to determine which operator-specific category the triggered access maps to. The triggered access described above may correspond to a new MMTEL service (voice call, video call), SMS transmission, new PDU session establishment, existing PDU session change, and the like.

In operation 2c-30, when the service is triggered, the NAS 2c-10 may map an access identity and an access category corresponding to the attribute of the service described above. The service described above may not be mapped to any access identity, or may be mapped to one or more access identities. In addition, the above-described service may be mapped to one access category. Assuming that it can be mapped to one access category, it can be checked first whether or not the above-described service is mapped to an operator-specific access category provided by the above-described management object. If it does not map to any operator-specific access category, it can be mapped to one of the standardized access categories described above. Assuming that you can map to multiple access categories, one service maps to one operator-specific access category and one standardized access category. However, if it is not mapped to any operator-specific access category, it can be mapped to one of the standardized access categories described above. In an embodiment, the emergency service may be an exception in the above-described mapping rule.

In step 2c-40, the NAS 2c-10 sends a new session request or service request to the AS 2c-15 together with the mapped access identity and access category described above. The NAS 2c-10 may transmit a new session request in the connected mode or the inactive mode and a service request in the standby mode.

In operation 2c-35, the AS 2c-15 may receive barring configuration information from system information broadcast by the network. An example of the ASN.1 structure of the barring configuration information described above is the following code, a detailed description thereof will be described later.

In steps 2c-45, the AS 2c-15 permits the above-described service request, using the access identity and access category information mapped by the NAS 2c-10 and the corresponding barring configuration information received from the network described above. Can be determined. In the present disclosure, an operation of determining whether the above-described service request is allowed is called a barring check. The terminal 2c-05 may receive the system information including the above-described access control setting information and store the above-mentioned setting information. The barring configuration information described above may be provided for each PLMN and for each access category. BarringPerCatList IE can be used to provide barring configuration information of access categories belonging to one PLMN. To this end, the PLMN id and barring configuration information of each access category may be included in the above-described IE in the form of a list. The barring configuration information for each access category may include an access category id (or index) indicating a specific access category, a uac-BarringForAccessIdentity field, a uac-BarringFactor field, and a uac-Barringtime field.

Hereinafter, an embodiment of the barring check operation described above will be described in detail. First, each bit constituting uac-BarringForAccessIdentity corresponds to one access identity, and when the above-described bit value is indicated as '0', access associated with the above-described access identity is allowed. For at least one of the mapped access identities described above, access may be allowed if at least one of the corresponding bits in uac-BarringForAccessIdentity is '0'. If at least one of the corresponding bits in the uac-BarringForAccessIdentity is not '0' for at least one of the mapped access identities described above, an additional barring check may be performed using the uac-BarringFactor field. The above-described range of uac-BarringFactor α may be 0 ≦ α <1. The terminal AS derives one random value rand with 0 ≤ rand <1, and if the above-mentioned random value is smaller than the above-described uac-BarringFactor, access may not be prohibited. Otherwise, access may be regarded as prohibited. If it is determined that access is prohibited, the above-described terminal AS 2c-15 may delay the access attempt for a predetermined time derived using Equation 2 below. The terminal AS 2c-15 may drive a timer having the above-described time value. In the present disclosure, the above-described timer is called a barring timer.

If the above-mentioned access is prohibited, the above-mentioned terminal AS 2c-15 may inform the above-mentioned terminal NAS 2c-10. When the derived predetermined time expires, the above-described terminal AS 2c-15 may inform the terminal NAS 2c-10 that it can request access again (barring alleviation). From this time, the above-described terminal NAS 2c-10 may request access to the above-mentioned terminal AS 2c-15 again.

In step 2c-50, according to the predetermined rule described above, if the service request is allowed, the above-described AS 2c-15 requests the RRC connection establishment or RRC connection resume from the above-mentioned network, or new Send data related to session.

In the next generation mobile communication system, the access may be triggered in the terminal AS. In an embodiment, the terminal in the inactive mode may trigger an RNA update (RAN Notification Area) or Resume process in a state where the terminal NAS is not involved. RNA update is an operation similar to a tracking area update (TAU), in which the UE reports RNA to the RAN periodically or periodically when the UE moves out of a predetermined cell or cell group area (RNA) at the RAN level. . Resume is a process in which the terminal in the inactive mode switches to the connected mode in order to start transmitting and receiving data again. In general, three levels of RRC message transmission and reception may be required. In the present disclosure, access as described above by way of example is referred to as an AS-triggered event.

Referring to FIG. 11, the terminal 2d-05 includes a terminal NAS 2d-10 and an AS 2d-15. In general, the terminal NAS 2d-10 triggers an access in LTE, but in the next generation mobile communication system, the terminal AS 2d-15 may trigger a specific access.

In step 2d-25, the base station 2d-20 may provide the barring configuration information to the terminals in the service area by using the system information. The barring configuration information described above may be provided for each access category.

In step 2d-30, the above-described terminal AS (2d-15) may trigger a specific access, such as RNA update or Resume.

In steps 2d-35, the terminal AS 2d-15 may map one corresponding access category to the above-described access. The terminal AS 2d-15 may perform barring check by using the barring configuration information corresponding to the mapped access category described above. Barring check has been described with reference to the preceding drawings. According to the result of the barring check described above, in step 2d-40, if the terminal AS 2d-15 is deemed to be prohibited from access described above, the terminal AS 2d-15 derives one barring time, and has a timer having the aforementioned time value, i.e. You can start the barring timer. While the above-described timer is running, it can be regarded as barred for access corresponding to the above-described access category. Accordingly, the terminal AS 2d-15 may not trigger the AS-triggered event for which access is prohibited until the above-described timer expires. The terminal NAS 2d-10 does not trigger the access-prohibited NAS-triggered event until the above-described timer expires, or even if triggered, the terminal AS 2d-15 sets the above-described NAS-triggered event to prohibit access. Can be considered. In an embodiment, with regard to which range of access categories the timer described above applies to, various options may be proposed as follows.

Option 1: apply a single barring timer for all access categories

If access corresponding to one access category is deemed to be prohibited through a barring check, one timer can be started. While the above timer is running, access of all access categories cannot be attempted. In this case, an access attempt may be allowed for a predetermined or predefined access category. For example, an emergency call, high priority access, or MT (Mobile Termination) access may attempt to access regardless of timer operation.

-option 2: apply barring timer for each access category

If access corresponding to one access category is deemed to be prohibited through a barring check, one timer can be started. While the above-described timer is running, it may not be possible to attempt to access the corresponding access category. Thus, access belonging to different access categories can be attempted.

-option 3: apply barring timer for each access category group

If access corresponding to one access category is deemed to be prohibited through a barring check, one timer can be started. While the above timer is running, it may not be possible to attempt access to all the access categories of the group to which the corresponding access category belongs. The above-mentioned groups may be specified by various definitions. According to an embodiment, the standardized access category and the operator-defined access category may be one group, a group according to a predetermined priority, or one NAS-triggered event and one AS-triggered event, respectively.

Option 4: Apply barring timers for each standardized access category, and apply a single barring timer for all operator-defined access categories.

If access corresponding to one standardized access category is deemed to be prohibited through a barring check, one timer can be started. While the above-described timer is running, access to the corresponding standardized access category may not be attempted. At this time, access belonging to another access category may be attempted. On the other hand, if an access corresponding to one operator-defined access category is deemed to be prohibited through the barring check, one timer may be started. While the above-described timer is running, it may not be possible to attempt to access all operator-defined access categories.

According to one embodiment of the present disclosure, when access of the above-described AS-triggered event is prohibited, if a predetermined condition is not satisfied, the above-described terminal NAS 2d-10 is not informed, and a barring timer corresponding thereto is not provided. You may not be notified when it expires.

In step 2d-50, the timer may be driven.

In step 2d-45, because the terminal AS 2d-15 does not inform the terminal NAS 2d-10 that access is prohibited for a specific access category or group of access categories, while the above-described timer is running, The terminal NAS 2d-10 may trigger a new access for the specific access category or access category group described above.

In step 2d-55, the terminal NAS 2d-10 may transmit a service request or session management to the terminal AS 2d-15 together with an access category and an access identity corresponding to the aforementioned access.

In step 2d-60, the terminal AS 2d-15 may inform the terminal NAS 2d-10 that the above-described access is not allowed if the barring timer corresponding to the new access described above is already running. As an exception, if the base station has set an access permission using the system information on the access identity provided from the terminal NAS 2d-10 together with the access category, the above-described access may be allowed.

If the above-mentioned barring timer has expired and the above-mentioned terminal NAS 2d-10 has been notified that the above-described access is prohibited, in step 2d-65, the above terminal AS 2d-15 indicates that the above-described timer has expired. The terminal NAS 2d-10 can be informed. This is to prevent the terminal NAS 2d-10 from repeatedly triggering access even when the above-described barring timer is running.

In step 2d-70, the above-described terminal NAS 2d-10 that is reported that the above-described barring timer expires may trigger a new access for the aforementioned access category or access category group.

In step 2d-75, for the above-described access, the terminal AS 2d-15 may perform a barring check and, if deemed to be allowed, may attempt to access the base station. Therefore, the predetermined condition described in the present disclosure refers to an access category or an access category group corresponding to the barring timer described above by the terminal NAS 2d-10 while the terminal AS 2d-15 is driving one barring timer. It may be a case of triggering a new access and requesting access to the terminal AS 2d-15.

An access, access category, or access category group that does not correspond to the running barring timer may perform the above-described separate operation.

In step 2e-05, the terminal AS may recognize a NAS-triggered event or an AS-triggered event. The above-described NAS-triggered event may be triggered by the terminal NAS, and the relevant access category may be delivered to the terminal AS described above. The above-mentioned AS-triggered event is triggered by the terminal AS, such as RNA update or Resume may belong to this.

In step 2e-10, for the NAS-triggered event, the terminal AS described above may perform a barring check. In this case, the terminal AS may use barring configuration information corresponding to the access category provided by the aforementioned terminal NAS and the aforementioned access category broadcast by the base station. In an embodiment, the terminal AS may provide one or more access identities together with the access category provided by the terminal NAS, and if the base station has set access permission to at least one of the above-described access identities using system information It can be considered to allow the above-mentioned access.

In step 2e-15, the terminal AS may determine whether the aforementioned access is prohibited through the barring check described above.

In step 2e-20, if the above-described access is allowed, the terminal AS may perform random access to the base station.

In step 2e-25, if the above-described access is not allowed, the terminal AS may inform the terminal NAS of this and start one timer corresponding to the above-described access category.

In step 2e-30, when the above-mentioned running timer expires, the above-mentioned terminal AS informs the above-mentioned terminal NAS of requesting access again (barring alleviation). From this point, the above-described terminal NAS may request access to the above-mentioned terminal AS again.

In step 2e-35, for the AS-triggered event, the above-mentioned terminal AS may map one corresponding access category. It is also possible to map more than one access identity.

In step 2e-40, the above-described terminal AS may perform a barring check. In this case, the above-described terminal AS may use the barring configuration information corresponding to the mapped access category and the above-described access category broadcast by the base station. The terminal AS may map one or more access identities, and if the base station sets access permission to at least one of the above-described access identities using system information, it may be regarded as granting the aforementioned access. .

In step 2e-45, the terminal AS may determine whether the above-mentioned access is prohibited through the above-described barring check.

In step 2e-50, if the above-described access is not allowed, the terminal AS does not notify the terminal NAS of this, and may drive one timer corresponding to the above-described access category.

In step 2e-55, while the above-mentioned timer is running, if the terminal NAS requests the above-mentioned terminal AS for access belonging to an access category or an access category group corresponding to the above-described timer, the above-mentioned terminal AS is the above-mentioned access. The above-mentioned terminal NAS can be notified that the is prohibited.

In step 2e-60, if the above-mentioned terminal NAS is informed that the above-mentioned access is prohibited while the above-mentioned timer is running, the above-mentioned terminal AS may inform the above-mentioned terminal NAS that the above-described timer has expired.

In step 2e-65, if the above-described access is allowed, the above-described terminal AS may perform random access to the base station.

In step 2f-05, the terminal NAS triggers one access, maps one access category corresponding thereto, and maps one or more access identity.

In step 2f-10, the above-described terminal NAS may transmit the above-described mapped access category and access identity to the terminal AS.

In step 2f-15, the above-described terminal NAS may be reported to the above-mentioned terminal AS that the above-described access is not allowed. At this time, the above-described terminal NAS may not trigger the above-mentioned access again until the above-described terminal AS informs that the corresponding timer expires and can resend the above-mentioned access. However, in addition to the above-described access category, accesses corresponding to other access categories may be triggered.

In step 2f-20, the above-described terminal NAS may determine whether an access that does not correspond to the barring timer being driven, or a specific access such as emergency or high priority access is triggered.

In step 2f-25, if an access that does not correspond to the running barring timer or a specific access such as emergency or high priority access is triggered, the above-described terminal NAS may map to one access category for the above-described access.

In step 2f-30, the above-described terminal NAS may deliver the above-described access category to the above-described terminal AS.

In step 2f-35, the above-described terminal NAS may request the access again by the above-described terminal AS if the access bar corresponding to the barring timer being driven or a specific access such as emergency or high priority access has not been triggered. You can wait until you report it.

Referring to FIG. 14, in step 2g-25, the base station 2g-20 may provide barring configuration information to terminals in a service area by using system information. The barring configuration information described above may be provided for each access category.

In step 2g-30, the above-described terminal AS (2g-15) may trigger a specific access, such as RNA update or resume for data transmission.

In steps 2g-35, the terminal AS 2g-15 may request access category mapping from the terminal NAS 2g-10 for the triggered access described above.

In steps 2g-40, the above-described terminal NAS 2g-10 may map the corresponding access category and access identity to the above-described access.

In step 2g-45, the above-described terminal NAS 2g-10 may transfer the above-described mapped access category and access identity information to the above-described terminal AS 2g-15. At this time, the above-described terminal NAS (2g-10) may include an indicator indicating that the above-mentioned delivered access category and access identity is for access by the request of the terminal AS (2g-15).

In operation 2g-50, the above-described terminal AS 2g-15 may perform barring check by using barring configuration information corresponding to the mapped access category described above. The barring check described above has been described with reference to the preceding drawings.

In step 2g-55, if the above-mentioned access is considered to be prohibited according to the result of the barring check described above, one barring time can be derived and a timer having the above-described time value, i.e., a barring timer can be driven. While the above-described timer is running, it is considered to be barred for access corresponding to the above-mentioned access category.

Therefore, in steps 2g-60, the terminal AS 2g-15 does not trigger the AS-triggered event corresponding to the above timer until the above timer expires. The terminal NAS 2g-10 may instruct that access of the access category corresponding to the above-described timer is prohibited.

In steps 2g-65 and 2g-70, the terminal NAS 2g-10 and the terminal AS 2g-15 may not trigger the forbidden access until the above timer expires.

In step 2g-75, if the above-described barring timer expires, the terminal AS 2g-15 may inform the above-mentioned terminal NAS 2g-10 that the above-described timer has expired. An access, access category, or access category group that does not correspond to the running barring timer may perform the above-described separate operation.

Referring to FIG. 15, the above-described terminal includes a radio frequency (RF) processor 2h-10, a baseband processor 2h-20, a storage unit 2h-30, and a controller 2h-40. can do.

The above-described RF processor 2h-10 may perform a function for transmitting and receiving a signal through a wireless channel such as band conversion and amplification of a signal. That is, the above-described RF processor 2h-10 up-converts the baseband signal provided from the above-described baseband processor 2h-20 into an RF band signal and transmits the same through an antenna, and is received through the above-described antenna. The RF band signal can be down converted to a baseband signal. For example, the RF processor 2h-10 described above includes a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), and the like. can do. In the above drawings, only one antenna is shown, but the above-described terminal may be provided with a plurality of antennas. In addition, the above-described RF processor 2h-10 may include a plurality of RF chains. Furthermore, the above-described RF processor 2h-10 may perform beamforming. For the above-described beamforming, the above-described RF processing unit 2h-10 may adjust phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the above-described RF processor may perform MIMO, and may receive multiple layers when performing the MIMO operation.

The baseband processor 2h-20 described above may perform a baseband signal and bit string conversion function according to the physical layer standard of the system. For example, during data transmission, the baseband processor 2h-20 described above may generate complex symbols by encoding and modulating a transmission bit string. In addition, when receiving data, the baseband processor 2h-20 described above may restore the received bit string by demodulating and decoding the baseband signal provided from the above-described RF processor 2h-10. For example, in accordance with an orthogonal frequency division multiplexing (OFDM) scheme, during data transmission, the above-described baseband processor 2h-20 generates complex symbols by encoding and modulating a transmission bit string, and performs the complex symbols described above. After mapping to subcarriers, OFDM symbols may be configured through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, upon reception of data, the baseband processor 2h-20 described above divides the baseband signal provided from the above-described RF processor 2h-10 in OFDM symbol units and performs subcarriers through a fast Fourier transform (FFT) operation. After the signals mapped to the signals are restored, the received bit stream may be recovered by demodulation and decoding.

The baseband processor 2h-20 and the RF processor 2h-10 described above may transmit and receive signals as described above. Accordingly, the baseband processor 2h-20 and the RF processor 2h-10 described above may be referred to as a transmitter, a receiver, a transceiver, or a communicator. Furthermore, at least one of the baseband processor 2h-20 and the RF processor 2h-10 described above may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processor 2h-20 and the RF processor 2h-10 described above may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies described above may include a wireless LAN (eg, IEEE 802.11), a cellular network (eg, LTE), and the like. In addition, the different frequency bands described above may include a super high frequency (SHF) (eg, 2.NRHz, NRhz) band and a millimeter wave (eg, 60 GHz) band. The terminal may transmit and receive a signal with the base station using the baseband processor 2h-20 and the RF processor 2h-10. Here, the signal may include control information and data.

The storage unit 2h-30 may store data such as a basic program, an application program, and setting information for the operation of the terminal described above. In particular, the above-described storage unit 2h-30 may store information related to the second access node that performs wireless communication using the second wireless access technology. In addition, the above-described storage unit 2h-30 may provide stored data at the request of the above-described control unit 2h-40. The storage unit 2h-30 may be configured with a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, and the like. In addition, the storage unit 2h-30 may include a plurality of memories. In one embodiment, the storage unit 2h-30 may store a program for supporting beam-based cooperative communication.

The above-described control unit 2h-40 controls the overall operations of the above-described terminal. For example, the above-described control unit 2h-40 may transmit and receive signals through the above-described baseband processor 2h-20 and the above-described RF processor 2h-10. In addition, the above-described control unit 2h-40 can record and read data in the above-described storage unit 2h-40. For this purpose, the above-described control unit 2h-40 may include at least one processor. For example, the controller 2h-40 may include a communication processor (CP) for performing control for communication and an application processor (AP) for controlling a higher layer such as an application program.

16 is a block diagram illustrating a configuration of a main station in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 16, the above-described base station includes an RF processor 2i-10, a baseband processor 2i-20, a backhaul communication unit 2i-30, a storage unit 2i-40, and a controller 2i-50. It may include.

The above-described RF processor 2i-10 may perform a function for transmitting and receiving a signal through a wireless channel such as band conversion and amplification of the signal. That is, the above-described RF processor 2i-10 up-converts the baseband signal provided from the above-described baseband processor 2i-20 to an RF band signal and transmits the same through an antenna, and is received through the above-described antenna. The RF band signal can be downconverted to a baseband signal. For example, the above-described RF processor 2i-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. In the above drawings, only one antenna is shown, but the above-described first access node may have a plurality of antennas. In addition, the above-described RF processor 2i-10 may include a plurality of RF chains. In addition, the above-described RF processor 2i-10 may perform beamforming. For the above-described beamforming, the above-described RF processing unit 2i-10 may adjust phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. The RF processor described above may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processor 2i-20 described above may perform a baseband signal and bit string conversion function according to the physical layer standard of the first wireless access technology. For example, during data transmission, the baseband processor 2i-20 described above may generate complex symbols by encoding and modulating a transmission bit string. In addition, when receiving data, the baseband processor 2i-20 described above may restore the received bit string by demodulating and decoding the baseband signal provided from the above-described RF processor 2i-10. For example, according to the OFDM scheme, when transmitting data, the baseband processor 2i-20 described above generates complex symbols by encoding and modulating a transmission bit stream, and maps the above-described complex symbols to subcarriers. , OFDM symbols may be configured through IFFT operation and CP insertion. In addition, upon reception of data, the baseband processor 2i-20 described above divides the baseband signal provided from the above-described RF processor 2i-10 in OFDM symbol units and signals mapped to subcarriers through an FFT operation. After restoring the data, the received bit stream may be restored by demodulation and decoding. The baseband processor 2i-20 and the RF processor 2i-10 described above may transmit and receive signals as described above. Accordingly, the baseband processor 2i-20 and the RF processor 2i-10 described above may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

The backhaul communication unit 2i-30 described above may provide an interface for communicating with other nodes in the network. That is, the above-described backhaul communication unit 2i-30 converts the bit string transmitted from the above-described main base station to another node, for example, an auxiliary base station, core network, etc., into a physical signal, and receives a physical signal received from the above-described other node. The signal can be converted into a bit string.

The storage unit 2i-40 described above may store data such as a basic program, an application program, and setting information for the operation of the main station described above. In particular, the above-described storage unit 2i-40 may store information on a bearer allocated to the connected terminal, a measurement result reported from the connected terminal, and the like. In addition, the above-described storage unit 2i-40 may store information that is a criterion for determining whether to provide or terminate multiple connections to the terminal. In addition, the above-described storage unit 2i-40 may provide stored data at the request of the above-described control unit 2i-50.

The above-described control unit 2i-50 can control the overall operations of the above-described main station. For example, the above-described control unit 2i-50 transmits and receives a signal through the above-described baseband processor 2i-20 and the above-described RF processor 2i-10 or through the above-described backhaul communication unit 2i-30. can do. In addition, the above-described control unit 2i-50 can record and read data in the above-described storage unit 2i-40. To this end, the above-described control unit 2i-50 may include at least one processor.

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

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

Such programs (software modules, software) may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms It can be stored in an optical storage device, a magnetic cassette. Or, it may be stored in a memory composed of some or all of these combinations. In addition, each configuration memory may be included in plural.

In addition, the program is accessed through a communication network composed of a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable storage device that is accessible. Such a storage device may be connected to a device that performs an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device that performs an embodiment of the present disclosure.

In the above-described specific embodiments of the present disclosure, the components included in the invention are expressed in the singular or plural in accordance with the specific embodiments presented. However, the singular or plural expressions are selected to suit the circumstances presented for convenience of description, and the present disclosure is not limited to the singular or plural elements, and the singular or plural elements may be used in the singular or the singular. Even expressed components may be composed of a plurality.

On the other hand, the embodiments of the present disclosure disclosed in the specification and drawings are merely presented specific examples to easily explain the technical contents of the present disclosure and aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it will be apparent to those skilled in the art that other modifications based on the technical spirit of the present disclosure can be implemented. In addition, each of the above embodiments can be combined with each other if necessary to operate. For example, portions of one embodiment of the present disclosure and another embodiment may be combined with each other so that the base station and the terminal may be operated. In addition, although the above embodiments are presented based on the FDD LTE system, other modifications based on the technical spirit of the embodiment may be implemented in other systems such as a TDD LTE system, a 5G, or an NR system.

Claims

In the method for the terminal to perform access control on the network in a wireless communication system,

at an access-stratum (AS) layer, triggering access to the network;

Determining, at the AS layer, whether a blocking timer for an access category corresponding to the triggered access is running; And

And determining, at the AS layer, that the blocking for the access category has been levied when the blocking timer expires.
The method of claim 1,

And transmitting, at the AS layer, information on whether the cutoff timer for the access category corresponding to the triggered access is running, to a non-access-stratum (NAS) layer. How to do it.
The method of claim 2,

And transmitting, at the AS layer, information to the NAS layer that the blocking for the access category has been relaxed based on whether the blocking timer has expired.
The method of claim 2,

At the NAS layer, determining whether to trigger an access corresponding to the access category based on information on whether the cutoff timer for the access category received from the AS layer is running; How to perform control.
The method of claim 3,

At the NAS layer, determining whether to trigger an access corresponding to the access category based on information that the blocking for the access category received from the AS layer has been relaxed; Way.
The method of claim 1,

And the access is an access triggered in response to a request for a radio access network notification area update of the terminal in an inactive mode.
The method of claim 1,

And wherein the access is an access triggered in response to a request for switching the terminal from inactive mode to connected mode.
In the terminal performing the access control to the network,

A transceiver; And

A processor for controlling the transceiver and including an access-stratum (AS) layer, the processor comprising:

Cause the AS layer to trigger access to the network, the AS layer to determine whether a cutoff timer for an access category corresponding to the triggered access is running, and if the AS layer expires And determine that the blocking for the access category has been levied.
The method of claim 8,

The processor further includes a Non-Access-Stratum (NAS) layer, wherein the processor provides information about whether the AS layer is running the shutdown timer for the access category corresponding to the triggered access to the NAS layer. Terminal for delivery to.
The method of claim 9,

The processor is further configured to cause the AS layer to communicate to the NAS layer that the blocking for the access category has been levied based on whether the cutoff timer has expired.
The method of claim 9,

Wherein the processor is further configured to determine whether to perform a trigger of an access corresponding to the access category, based on the information regarding whether the blocking timer for the access category received from the AS layer is running. Terminal.
The method of claim 10,

The processor allows the NAS layer to determine whether to trigger an access corresponding to the access category based on the information that the blocking for the access category received from the AS layer has been relaxed.
The method of claim 8,

And the access is an access triggered in response to a request for a radio access network notification area update of the terminal in an inactive mode.
The method of claim 8,

The access is an access triggered in response to a request to switch the terminal from inactive mode to connected mode.