KR20190033846A - Methods for controlling access of UE and Apparatuses thereof - Google Patents

Abstract

The present invention relates to an access procedure and access control method of a terminal connected through a relay using a mobile communication network-based side link, and an apparatus thereof. The present disclosure provides a method, which is a method for a terminal to access to a network, comprising the steps of: performing a layer 2 relay-based side link connection; and performing a network access through side connection.

Description

[0001] The present invention relates to a method and an apparatus for controlling access to a UE,

 BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an access connection procedure and an access control method and apparatus for a terminal connected through a relay using a side link based on a mobile communication network.

The present disclosure provides a method and apparatus for performing a network connection through a side connection and performing a side link connection based on a layer 2 relay in a method for a terminal to access a network.

1 is a diagram illustrating a control plane protocol stack for one-to-one side link communication.
2 is a diagram illustrating a connection procedure of a remote terminal through an L3 relay.
3 is a diagram showing DIRECT_COMMUNICATION_REQUEST message content.
4 is a diagram illustrating an example of a control plane wireless protocol stack based on a layer 2 relay terminal.
5 is a diagram showing another example of a control plane wireless protocol stack based on a layer 2 relay terminal.
6 is a diagram illustrating an example of a network registration procedure through a side link connection between a remote terminal and an L2 relay terminal.
7 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
FIG. 8 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

As used herein, a wireless communication system refers to a system for providing various communication services such as voice, packet data, and the like. A wireless communication system includes a user equipment (UE) and a base station (BS).

The user terminal is a comprehensive concept that means a terminal in a wireless communication, and it is a comprehensive concept which means a mobile station (MS) in GSM, a mobile station (MS) in UT (User Terminal), a Subscriber Station (SS), a wireless device, and the like.

A base station or a cell generally refers to a station that communicates with a user terminal and includes a Node-B, an evolved Node-B, a gNode-B, a Low Power Node A sector, a site, various types of antennas, a base transceiver system (BTS), an access point, a point (for example, a transmission point, a reception point, a transmission / reception point) (RRH), a radio unit (RU), and a small cell, as well as a relay cell, a relay node, a megacell, a macrocell, a microcell, a picocell, a femtocell, an RRH,

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. Macro cell, micro cell, picocell, femtocell, small cell, or 2) the wireless region itself in connection with the wireless region. 1), all of the devices that interact to configure the wireless area to be cooperatively controlled by the same entity are all pointed to the base station. A point, a transmission / reception point, a transmission point, a reception point, and the like are examples of the base station according to the configuration method of the radio area. 2 may direct the base station to the wireless region itself to receive or transmit signals at the point of view of the user terminal or in the vicinity of the neighboring base station.

In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or a transmission point or a transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .

Herein, the user terminal and the base station are used in a broad sense as two (uplink or downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, and are not limited by a specific term or word Do not.

Here, an uplink (UL, or uplink) means a method of transmitting / receiving data to / from a base station by a user terminal, and a downlink (DL or downlink) .

The time division duplex (TDD) scheme, which is transmitted using different time periods, can be used for the uplink and downlink transmission, and a frequency division duplex (FDD) scheme in which different frequencies are used, a TDD scheme and an FDD scheme A hybrid method can be used.

In the wireless communication system, the uplink and the downlink are configured with reference to one carrier or carrier pair to form a standard.

The uplink and the downlink transmit control information through a control channel such as a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), and the like. The physical downlink shared channel (PDSCH), the physical uplink shared channel (PUSCH) It is composed of the same data channel and transmits data.

A downlink may refer to a communication or communication path from a multipoint transmission / reception point to a terminal, and an uplink may refer to a communication or communication path from a terminal to a multiple transmission / reception point. At this time, in the downlink, the transmitter may be a part of the multiple transmission / reception points, and the receiver may be a part of the terminal. Also, in the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.

Hereinafter, a situation in which a signal is transmitted / received through a channel such as PUCCH, PUSCH, PDCCH, and PDSCH is expressed as 'PUCCH, PUSCH, PDCCH and PDSCH are transmitted and received'.

Meanwhile, the High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.

The base station performs downlink transmission to the UEs. The base station includes downlink control information, such as scheduling, required for reception of a downlink data channel, which is a primary physical channel for unicast transmission, and physical downlink control information for transmitting scheduling grant information for transmission in an uplink data channel. A control channel can be transmitted. Hereinafter, the transmission / reception of a signal through each channel will be described in a form in which the corresponding channel is transmitted / received.

There are no restrictions on multiple access schemes applied in wireless communication systems. (TDMA), Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Non-Orthogonal Multiple Access (NOMA) Various multiple access schemes such as OFDM-CDMA can be used. Here, the NOMA includes Sparse Code Multiple Access (SCMA) and Low Density Spreading (LDS).

One embodiment of the present invention relates to asynchronous wireless communications that evolve into LTE / LTE-Advanced, IMT-2020 over GSM, WCDMA, HSPA, and synchronous wireless communications such as CDMA, CDMA- Can be applied.

In this specification, a MTC (Machine Type Communication) terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement. Alternatively, the MTC terminal may refer to a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.

In other words, the MTC terminal in this specification may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC-related operations. Alternatively, the MTC terminal may support enhanced coverage over the existing LTE coverage or a UE category / type defined in the existing 3GPP Release-12 or lower that supports low power consumption, or a newly defined Release-13 low cost low complexity UE category / type. Or a further Enhanced MTC terminal defined in Release-14.

In this specification, NarrowBand Internet of Things (NB-IoT) terminal means a terminal supporting wireless access for cellular IoT. The objectives of NB-IoT technology include improved indoor coverage, support for large-scale low-rate terminals, low latency sensitivity, ultra-low cost, low power consumption, and optimized network architecture.

Enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC) have been proposed as typical usage scenarios in NR (New Radio), which is under discussion in 3GPP.

In this specification, a frequency, a frame, a subframe, a resource, a resource block, a region, a band, a subband, a control channel, a data channel, a synchronization signal, various reference signals, various signals, May be interpreted as past or presently used meanings or various meanings used in the future.

In the prior art, relay-based side-link communication

For one-to-many-side link (D2D) communication in the conventional LTE technology, the terminal does not establish or maintain a logical connection with the receiving terminals. For one-to-one side-link communications, the upper layer (e.g., the PC5 signaling protocol) establishes and maintains a logical connection. The control plane protocol stack for establishing, maintaining, and releasing logical connections for one-to-one side link communications is shown in FIG.

In the conventional LTE technology, a relay using a side link (ProSe UE-to-Network Relay) provides an L3 forwarding function capable of relaying any type of IP traffic between a remote terminal and a network. For convenience of description, in the conventional LTE, a relay using a side link (ProSe UE-to-Network Relay) is indicated as an L3 relay or an L3 relay terminal. Only one single carrier (i.e., public secure ProSe carrier) operation is supported for the remote terminal and the L3 relay terminal (i.e., the UU interface between the terminal and the base station and the terminal PC5 interface are the same carrier for the L3 relay and the remote terminal) Only.

The remote terminal must be authorized by the higher layer and may be in the coverage of public safety ProSe carriers. Or L3 relay discovery, seletion, and public safety ProSe carriers for communication. The L3 relay terminal is always in coverage.

In conventional LTE technology, the base station may broadcast a minimum and / or maximum Uu link quality (RSRP) threshold for initiating the L3 relay discovery procedure.

When the terminal is in RRC IDLE, the terminal can autonomously start or stop the L3 relay discovery procedure using the threshold when the base station broadcasts the resource pool.

The remote terminal can determine when to start monitoring for L3 relay discovery. The remote terminal may send an L3 relay discovery solicitation message on RRC IDLE or RRC CONNECTED. The base station may broadcast a threshold value, which is used to determine if the remote terminal can send an L3 relay discovery solicitation message to connect or communicate with the L3 relay terminal. For example, at the cell coverage edge, the communication quality will be lower than the threshold, and the L3 relay can be solicited. The RRC CONNECTED remote terminal may use the broadcasted threshold to indicate to the base station that it is the remote terminal and desires to participate in L3 relay discovery and / or communication. For example, through a side link terminal information message.

In the prior art, a procedure for transmitting and receiving data to and from the network through the relay L3 of the remote terminal is as shown in FIG.

1. The ProSe UE-to-Network Relay performs initial E-UTRAN Attach and / or establishes a PDN connection for relaying (if no appropriate PDN connection for this relaying exists). In case of IPv6, the ProSe UE-to-Network Relay obtains the IPv6 prefix via prefix delegation function from the network.

2. The Remote UE performs discovery of a ProSe UE-to-Network Relay using Model A or Model B discovery.

3. The Remote UE selects a ProSe UE-to-Network Relay and establishes a connection for one-to-one ProSe Direct Communication. If there is no PDN connection associated with the ProSe Relay UE ID or an additional PDN connection for relaying is needed, the ProSe UE-to-Network Relay initiates a new PDN connection establishment procedure for relaying.

4. IPv6 prefix or IPv4 address is allocated for the remote UE. From this point the uplink and downlink relaying can start.

5. The ProSe UE-to-Network Relay sends a Remote User Report (Remote User ID, IP info) message to the MME for the PDN connection associated with the relay. The Remote User ID is an identity of the remote UE user (provided via User Info) 3. The MME stores the Remote User IDs and related IP info in the ProSe UE-to-Network Relay's EPS bearer context for the PDN connection associated with the relay.

6. The MME forwards the UE-to-Network Relay UE to the S-GW and the S-GW forwards the message to the UE-to-Network Relay UE. The MME may report multiple Remote UEs in one Remote UE Report message.

As described above, the L3 relay terminal relays any type of IP traffic between the remote terminal and the network. Accordingly, when the remote terminal desires to access the network through the side link one-to-one communication as in step 3 of FIG. 2, the IP address assignment of the remote terminal is performed by using the IP configuration information and the security information for data security on the side link . 3 shows message content for a side-link one-to-one communication request.

L2 relay-based side-link communication

The L3 relay provided in the conventional LTE technology has an advantage that it can relay any type of IP traffic between the remote terminal and the network, but it can not provide reachability to the remote terminal in the network, and can not control the power consumption, There has been a problem that it is difficult to control the QoS for the remote terminal and the access of the remote terminal can not be controlled effectively. Therefore, it is difficult to apply the side-link-based relay to terminals that require efficient power control and QoS control like wearable terminals. To solve this problem, 3GPP can consider a study on Layer 2-based relay technology. However, since a specific method for network access through a layer 2-based relay terminal is not provided, it has not been possible to effectively control the network. In the future, when many wearable terminals attempt to access the network through the layer 2 relay, this may cause problems in network operation.

The L3 relay provided in the conventional LTE technology can not provide reachability to the remote terminal in the network and it is difficult to control power consumption or QoS control for the corresponding traffic and there is a problem that the access of the remote terminal can not be controlled effectively . Therefore, it is difficult to apply the side-link-based relay to terminals that require efficient power control and QoS control like wearable terminals. In order to solve this problem, it is possible to consider a layer 2-based relay technology. However, since a specific procedure for the remote terminal to access the network through the layer 2 relay based on the side link is not provided, There was an uncontrollable problem.

In order to solve the above problems, the present invention aims at providing a specific procedure for a remote terminal to access a network through a side link connection based on a layer 2 relay. And in particular, to provide a method and apparatus capable of effectively performing access control in a network connection process.

Embodiments provided below may be implemented individually or in combination of each other. The present invention can be applied not only to LTE based side link connection but also to side link connection based on next generation mobile communication (5G mobile communication). Hereinafter, a signaling radio bearer is used as a reference, but the method provided by the present invention can be applied to a data radio bearer.

For convenience of description, an L2 relay terminal can be denoted as a relay terminal in the following description.

The data of the relay terminal is relayed between the remote terminal and the network through the relay terminal from the RLC upper layer. Uu PDCP is terminated between the remote terminal and the base station, and the RLC, MAC, PHY and non-3GPP transport layers are terminated on each link.

4 shows an example of a control plane radio protocol stack based on a layer 2 relay terminal.

5 shows another example of a control plane wireless protocol stack based on a layer 2 relay terminal.

6 shows an example of a network registration procedure through a side link connection between a remote terminal and an L2 relay terminal. The following description is based on this.

One. The network registration of the relay terminal eRelay-UE and the remote terminal eRemote-UE is performed individually according to the existing network registration procedure. The terminal context is assigned to each MME. Each UE is assigned a GUTI. L2 relay authentication information is transmitted from the MME of the relay terminal to the base station.

2. The relay terminal (eRelay-UE) and the remote terminal (eRemote-UE) perform the ProSe function and service authentication. Service authentication for indirect 3GPP communication is provided. Indirect 3GPP communication refers to signaling and communication in which a relay terminal (L2 relay terminal) exists between a remote terminal and a 3GPP network. (Indirect 3GPP communication: The ProSe function can provide specific information that is used in Step 3 to decrypt the limited discovery message. This may enable only terminals with a particular trust relationship to discover each other.

The relay terminal and the remote terminal can then enter the IDLE mode.

The subsequent steps indicate when both the remote terminal and the relay terminal have gone to the IDL mode after step 1 and step 2 described above.

3. The remote terminal and the relay terminal perform the PC5 discovery procedure. The remote terminal is in the ECM_IDLE state. And the relay terminal may be in the ECM_IDLE or ECM_CONNECTED state.

4. The remote terminal triggers the upper layer to initiate the one-to-one communication with the relay terminal by transmitting the INDIRECT communication request to the relay terminal.

5. The relay terminal requests authorization for performing an indirect 3GPP communication service having an L2 relay role, and transmits a NAS request message (for example, a service request message, an attach request message, a TAU request Message) to the MME of the relay terminal. The NAS request message is encapsulated in an RRC message sent to the base station. The base station derives the relay MME identifier using the relay terminal identifier or relay identifier (e.g., S-TMSI, GUTI) and forwards the NAS message in the interface control message between the base station and the control plane core network entity (MME).

6. The MME performs authentication based on NAS message validation. If necessary, the MME checks the subscription data.

7. The MME transmits a terminal context setup request message including ProSe authentication information to the base station.

8. The base station transmits an RRC connection reconfiguration message including the EPS radio bearer identifier to the relay terminal.

9. The relay terminal transmits an indirect communication response message to the remote terminal.

10. If the indirect communication request is accepted, the remote terminal transmits a service request message NAS request message (for example, a service request message, an attach request message, and a TAU request message) to the MME of the remote terminal. The NAS request message is encapsulated in an RRC message sent to the base station. The base station derives the remote MME identifier using the identifier of the remote terminal (e.g., S-TMSI, GUTI) and forwards the NAS message in the interface control message between the base station and the control plane core network entity (MME).

11. The MME performs authentication based on NAS message validation. If necessary, the MME checks the subscription data.

12. The MME transmits a terminal context setup request message including ProSe authentication information to the base station.

13. The base station transmits an RRC connection reconfiguration message including the EPS radio bearer identifier to the remote terminal.

Hereinafter, an access control procedure when the remote terminal accesses the network through the relay terminal will be described.

For example, when the remote terminal desires to establish an RRC connection to the base station through the L2 relay terminal or to access / connect to the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, The remote terminal may be in the ECM_IDLE state. And the relay terminal may be in the ECM_IDLE or ECM_CONNECTED state.

As another example, when the remote terminal attempts to establish an RRC connection to the base station through the L2 relay terminal, or when it tries to access / connect to the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, The remote terminal may be in the RRC_IDLE state. And the relay terminal may be in the RRC_IDLE or RRC_CONNECTED state.

1) IDLE When the remote terminal transmits upper layer signaling (PC5 signaling or NAS signaling), it performs access barring in the upper layer

The user wants to establish an RRC connection to the base station through the L2 relay terminal while the remote terminal is in the RRC_IDLE state or to access / connect the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, or The uplink transmission by the remote terminal can be triggered.

The remote terminal initiates a one-to-one communication with the relay terminal by transmitting an INDIRECT communication request to the relay terminal as in step 4 of Fig. 6 described above.

As described above, the conventional L3 relay-based direct communication request transmits arbitrary IP traffic and it is not necessary to control the access from the remote terminal because it can not distinguish the traffic transmitted from the remote terminal from the viewpoint of the network with the relay terminal. However, when processing the network connection of the remote terminal through the L2 relay terminal, it is possible to distinguish and process the traffic transmitted from the remote terminal from the viewpoint of the relay terminal and the network, thereby controlling the QoS of the traffic per terminal and stably operating the network It is necessary to separate and perform access control from the remote terminal.

For example, as shown in FIG. 1, PC5 signaling is performed directly without the RRC layer. Therefore, in order to control access based on access barring, an access barring check should be performed in an upper layer (PC5 signaling layer or NAS layer) of the UE.

For example, a base station can define a new SSAC (Serivice Specific Access Control) parameter for access control of a remote terminal and broadcast it.

As another example, the base station can define a new access control parameter for access control in the upper layer of the remote terminal and broadcast the new access control parameter.

SSAC is a method for performing access barring for voice or video in the IMS layer. The SS includes access barring parameter configuration information (ssac-BarringForMMTEL-Voice) for voice and access barring parameter configuration information (ssac-BarringForMMTEL-Video ).

The base station may broadcast (via system information) the access barring parameter configuration information (e.g., ssac-BarringForRemoteUE, AC-BarringForRemoteUE) for the remote terminal to perform access barring at the upper layer of the remote terminal. Or may instruct the relay terminal through dedicated signaling.

The relay terminal can forward the access barring parameter configuration information for the received remote terminal to the remote terminal.

The remote terminal forwards the access barring parameter configuration information for the remote terminal received from the base station or the relay terminal to the upper layer. When the relay terminal and the remote terminal are in the IDLE state after the link, connection or connection, if the corresponding access barring parameter configuration information is changed, the relay terminal forwards the changed system information or the access barring parameter configuration information for the changed remote terminal to the remote terminal.

When the remote terminal initiates the one-to-one communication with the relay terminal by transmitting the INDIRECT communication request to the relay terminal as in step 4 of Fig. 6 described above, or when starting the NAS procedure of the remote terminal as in step 10 of Fig. 6, The upper layer of the terminal checks the access barring according to the access barring parameter configuration for the forwarded remote terminal.

For example, if a random number between 0 and 1 is extracted and the random number is less than the value indicated by the access barring factor (ac-BarringFactor) included in the access barring parameter configuration information, then the cell is considered unbared It is considered to be barred. As another example, the following barring check procedure can be used.

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> If the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11.15, which is valid for the UE according to TS 22.011 [10] and TS 23.122 [11], and

2> for at least one of these valid Access Classes corresponding to the ac- BarringForSpecialAC contained in "AC barring parameter" is set to zero :

3> consider access to the cell as not barred;

2> else:

3> draw a random number ' rand ' uniformly distributed in the range: 0 ≤ rand <1;

3> if ' rand ' is lower than the value indicated by ac- BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ' rand ' that is uniformly distributed in the range 0 ≤ rand <1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac- BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 _* rand ) _* ac- BarringTime ;

If the relay terminal performs the access barring check and access barring, the remote terminal considers that access to the cell (or access to the cell via the relay terminal) is barred. And the procedure is over.

Otherwise, considering that the access to the cell is not barred, it sends an INDIRECT communication request or NAS request message to the relay terminal.

As another example of this, the BS may broadcast an access barring parameter instructing an existing AS (RRC layer) to perform access control of the remote terminal.

This access barring parameter configuration information includes a common access baring parameter (acdc-BarringForCommon), a PLMN access barring parameter (acdc-BarringPerPLMN), a common ACDC-BarringForCommon, an ACDC-BarringParPLNN per PLMN (ACDC- And one or more parameter configuration information among the barring parameters.

The BS transmits information for instructing the upper layer (PC5 signaling layer or NAS layer) to forward the access barring parameter received by the AS layer (RRC) or information for instructing the upper layer of the remote terminal to transmit the information to the remote terminal Information for instructing can be broadcasted. For example, the information may be indicated by the above-described access barring parameter configuration information. For example, the information may be indicated by constructing a bitmap for the access barring parameter configuration information described above. In another example, the information may be provided as one indication information or one bit information for all access barring parameters provided through the system information or for access barring parameters determined by the specified / preconfigured / standard.

The base station may broadcast the above information (via system information). Or may instruct the relay terminal through dedicated signaling.

As a result, the relay terminal can forward the received access barring parameter configuration information to the remote terminal.

As another example, the relay terminal may transmit information for instructing to forward the access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) or information for instructing to the remote terminal or to an upper layer of the remote terminal And transmits the information to the upper layer. The upper layer of the relay terminal transfers this to the upper layer of the remote terminal.

As another example, the relay terminal may transmit information for instructing to forward the access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) or information for instructing to the remote terminal or to an upper layer of the remote terminal The relay terminal transmits the information to the remote terminal.

As another example, the relay terminal may transmit information for instructing to forward the access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) or information for instructing to the remote terminal or to an upper layer of the remote terminal The relay terminal transmits the information to the upper layer of the remote terminal.

When the relay terminal and the remote terminal are in the IDLE state after the link, connection or connection, if the corresponding access barring parameter configuration information is changed, the relay terminal forwards the changed system information or the access barring parameter configuration information for the changed remote terminal to the remote terminal.

When the remote terminal initiates the one-to-one communication with the relay terminal by transmitting the INDIRECT communication request to the relay terminal as in step 4 of Fig. 6 described above, or when starting the NAS procedure of the remote terminal as in step 10 of Fig. 6, The upper layer of the terminal checks the access barring according to the access barring parameter configuration for the forwarded remote terminal.

For example, if a random number between 0 and 1 is extracted and the random number is less than the value indicated by the access barring factor (ac-BarringFactor) included in the access barring parameter configuration information, then the cell is considered unbared It is considered to be barred. As another example, the following barring check procedure can be used.

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> If the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11.15, which is valid for the UE according to TS 22.011 [10] and TS 23.122 [11], and

2> for at least one of these valid Access Classes corresponding to the ac- BarringForSpecialAC contained in "AC barring parameter" is set to zero :

3> consider access to the cell as not barred;

2> else:

3> draw a random number ' rand ' uniformly distributed in the range: 0 ≤ rand <1;

3> if ' rand ' is lower than the value indicated by ac- BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ' rand ' that is uniformly distributed in the range 0 = rand <1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac- BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 _* rand ) _* ac- BarringTime ;

If the relay terminal performs the access barring check and access barring, the remote terminal considers that access to the cell (or access to the cell via the relay terminal) is barred. And the procedure is over.

Otherwise, considering that the access to the cell is not barred, it sends an INDIRECT communication request or NAS request message to the relay terminal.

2) IDLE When the remote terminal transmits upper layer signaling (PC5 signaling or NAS signaling), it instructs AS layer to perform access barring check and performs

The user wants to establish an RRC connection to the base station through the L2 relay terminal while the remote terminal is in the RRC_IDLE state or to access / connect the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, or The uplink transmission by the remote terminal can be triggered.

The remote terminal initiates a one-to-one communication with the relay terminal by transmitting an INDIRECT communication request to the relay terminal as in step 4 of Fig. 6 described above.

As described above, the conventional L3 relay-based direct communication request transmits arbitrary IP traffic and it is not necessary to control the access from the remote terminal because it can not distinguish the traffic transmitted from the remote terminal from the viewpoint of the network with the relay terminal. However, when processing the network connection of the remote terminal through the L2 relay terminal, it is possible to distinguish and process the traffic transmitted from the remote terminal from the viewpoint of the relay terminal and the network, thereby controlling the QoS of the traffic per terminal and stably operating the network It is necessary to separate and perform access control from the remote terminal.

For example, as shown in FIG. 1, PC5 signaling is performed directly without the RRC layer. Therefore, for the access barring-based access control, the remote terminal must instruct / request / inquire to perform the access barring check in the AS layer (RRC layer) before receiving the PC 5 signaling and receive the response / result / confirmation thereto.

The BS may broadcast an access barring parameter instructing the RRC layer to perform an access control of the remote terminal.

This access barring parameter configuration information includes a common access baring parameter (acdc-BarringForCommon), a PLMN access barring parameter (acdc-BarringPerPLMN), a common ACDC-BarringForCommon, an ACDC-BarringParPLNN per PLMN (ACDC- And one or more parameter configuration information among the barring parameters.

The base station may broadcast information for instructing the remote terminal to apply the access barring parameter received by the AS layer (RRC). Alternatively, the BS may transmit information for instructing to forward the access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer), information for instructing the RRC to forward the information to an upper layer of the remote terminal Information to be broadcasted.

For example, the information may be indicated by the above-described access barring parameter configuration information. For example, the information may be indicated by constructing a bitmap for the access barring parameter configuration information described above. In another example, the information may be provided as one indication information or one bit information for all access barring parameters provided through the system information or for access barring parameters determined by the specified / preconfigured / standard.

The base station may broadcast the above information (via system information). Or may instruct the relay terminal through dedicated signaling.

As a result, the relay terminal can forward the received access barring parameter configuration information to the remote terminal.

As another example, the relay terminal may transmit information for instructing the remote terminal to apply the access barring parameter received by the AS layer (RRC) or access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) Information for instructing delivery to the remote terminal, information for instructing the remote terminal, or information for instructing delivery to the upper layer of the remote terminal, is delivered to the upper layer. The upper layer of the relay terminal transfers this to the upper layer of the remote terminal. The remote terminal transmits this to the RRC layer.

As another example, the relay terminal may transmit information for instructing the remote terminal to apply the access barring parameter received at the AS layer (RRC) or access barring parameter received at the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) Upon receiving information for instructing delivery, information for instructing the remote terminal, or information for instructing delivery to the upper layer of the remote terminal, the relay terminal transmits the information to the remote terminal.

As another example, the relay terminal may transmit information for instructing the remote terminal to apply the access barring parameter received by the AS layer (RRC) or access barring parameter received from the AS layer (RRC) to an upper layer (PC5 signaling layer or NAS layer) Upon receiving the information for instructing delivery, information for instructing the remote terminal, or information for instructing delivery to the upper layer of the remote terminal, the relay terminal delivers the information to the upper layer of the remote terminal. The remote terminal transmits this to the RRC layer.

When the relay terminal and the remote terminal are in the IDLE state after the link, connection or connection, if the corresponding access barring parameter configuration information is changed, the relay terminal forwards the changed system information or the access barring parameter configuration information for the changed remote terminal to the remote terminal.

When the remote terminal initiates the one-to-one communication with the relay terminal by transmitting the INDIRECT communication request to the relay terminal as in step 4 of Fig. 6 described above, or when starting the NAS procedure of the remote terminal as in step 10 of Fig. 6, The upper layer of the UE instructs / requests / inquires to perform access barring check with the AS layer (RRC). The RRC checks the access barring access barring according to the instructions.

For example, if a random number between 0 and 1 is extracted and the random number is less than the value indicated by the access barring factor (ac-BarringFactor) included in the access barring parameter configuration information, then the cell is considered unbared It is considered to be barred. As another example, the following barring check procedure can be used.

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> If the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11.15, which is valid for the UE according to TS 22.011 [10] and TS 23.122 [11], and

2> for at least one of these valid Access Classes corresponding to the ac- BarringForSpecialAC contained in "AC barring parameter" is set to zero :

3> consider access to the cell as not barred;

2> else:

3> draw a random number ' rand ' uniformly distributed in the range: 0 ≤ rand <1;

3> if ' rand ' is lower than the value indicated by ac- BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ' rand ' that is uniformly distributed in the range 0 ≤ rand <1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac- BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 _* rand ) _* ac- BarringTime ;

If the relay terminal performs the access barring check and access barring, the remote terminal considers that access to the cell (or access to the cell via the relay terminal) is barred. And instructs / responds to the upper layer.

Otherwise, the access to the cell is regarded as not being barred and indicates it to the upper layer. The upper layer of the remote terminal transmits an INDIRECT communication request or NAS request message to the relay terminal.

3) Other methods

As another example for access control of the remote terminal, a method may be considered in which the IDLE remote terminal includes information for indicating the setting cause of the relay terminal when transmitting the upper layer signaling (PC5 signaling or NAS signaling).

As described above, the conventional L3 relay-based direct communication request transmits arbitrary IP traffic and it is not necessary to control the access from the remote terminal because it can not distinguish the traffic transmitted from the remote terminal from the viewpoint of the network with the relay terminal. However, when processing the network connection of the remote terminal through the L2 relay terminal, it is possible to distinguish and process the traffic transmitted from the remote terminal from the viewpoint of the relay terminal and the network, thereby controlling the QoS of the traffic per terminal and stably operating the network It is necessary to separate and perform access control from the remote terminal.

For example, when the remote terminal in the IDLE state initiates the PC 5 signaling to the relay terminal, the PC 5 signaling message may include setting cause information for the network connection of the remote terminal.

 The user wants to establish an RRC connection to the base station through the L2 relay terminal while the remote terminal is in the RRC_IDLE state or to access / connect the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, or The uplink transmission by the remote terminal can be triggered.

The remote terminal may include setup cause information triggered in the PC 5 signaling message (e.g., an INDIRECT communication request message such as step 4 in FIG. 6). In another example, the remote terminal may include setup cause information when transmitting an RRC message for transmitting the PC5 signaling message.

The set cause information may include the cause such as emergency, highPriorityAccess, mt-Access, mo-Signaling, mo-Data, delayTolerantAccess, mo-VoiceCall Information.

If the relay terminal receives the PC 5 signaling message including the setting cause information from the remote terminal (or receives the RRC message) from the remote terminal in the RRC IDLE state (for convenience of explanation, Upon receipt of the PC 5 signaling message containing the cause information, it may indicate one or more of the following cases: reception of the PC 5 signaling message or receipt of the RRC message.) The relay terminal, when establishing the RRC connection for this purpose, The access barring check can be performed according to the following equation. For example, if the origination signaling is included as a setting reason, the relay terminal can perform access barring through access barring parameter configuration information (for example, ac-BarringForMO-Signaling) for origination signaling. For example, when the originating data is included as a setting cause, the relay terminal can perform access barring through the access barring parameter configuration information (ac-BarringForMO-Data) for the origination data. For example, when the emergency terminal includes the emergency cause, the relay terminal can perform the access barring through the access barring parameter configuration information (ac-BarringForEmergency) for the emergency.

If the relay terminal receives the PC 5 signaling message including the above-mentioned setting cause information from the remote terminal in the RRC IDLE state, the relay terminal sets the received RRC connection request information to the setting cause of the RRC connection request message .

If the relay terminal receives the PC 5 signaling message including the setting cause information described above from the remote terminal in the RRC IDLE state and the setting cause of the relay terminal itself is overlapped, for example, the relay terminal sets the setting cause of the relay terminal to RRC It can be transmitted including the establishment cause of the connection request message. As another example, the relay terminal can transmit the setting cause of the remote terminal by including it in the establishment cause of the RRC connection request message. As another example, it is possible to transmit a setting cause having a high priority among the setting causes of the relay terminal and the remote terminal, including the setting cause of the RRC connection request message. For example, origination signaling may be included as a configuration reason when mo-Signaling and delayTolerantAccess overlap.

As another example for access control of a remote terminal, when a relay terminal is in a specific state when an IDLE remote terminal transmits an upper layer signaling (PC5 signaling or NAS signaling), a relay terminal may transmit information to the remote terminal have.

The user wants to establish an RRC connection to the base station through the L2 relay terminal while the remote terminal is in the RRC_IDLE state or to access / connect the network through indirect communication in which an L2 relay terminal exists between the remote terminal and the 3GPP network, or The uplink transmission by the remote terminal can be triggered.

The remote terminal transmits a PC 5 signaling message (e.g., an INDIRECT communication request message such as step 4 in FIG. 6) to the relay terminal. In another example, the remote terminal transmits an RRC message for transmitting the PC5 signaling message.

At this time, the relay terminal may be in a state in which transition to the RRC connection state is difficult for a certain reason. For example, RRC release message or RRC reject message including wait time value, RRC release message including extended wait time value or RRC reject message reception, radio link failure, RRC connection setup timer operation, RRC connection reset timer operation, Power saving mode may be one or more of the operations. If the relay terminal is unable to transition to the RRC connection state for any reason or for any reason, the relay terminal can transmit a reject / response / failure message for the access request of the remote terminal. The message may contain cause information thereon. The message may include the timer value described above. The timer may be a full timer value (pre-start timer value), or may be the remaining timer value that is left in the state of being started and operating in the terminal. When the remote terminal receives the message, the above-mentioned timer can be operated. The remote terminal does not send PC5 signaling to the relay terminal before the timer expires. The remote terminal can directly transmit an RRC connection request message to the base station.

As described above, the present invention has an effect of effectively controlling the network access of the remote terminal through the L2 relay.

FIG. 7 is a diagram illustrating a configuration of a base station 1000 according to another embodiment.

Referring to FIG. 7, a base station 1000 according to another embodiment includes a control unit 1010, a transmission unit 1020, and a reception unit 1030.

The control unit 1010 controls the overall operation of the base station 1000 according to the concrete procedure for the remote terminal to connect to the network through the layer 2 relay based side link connection do.

The transmitting unit 1020 and the receiving unit 1030 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention to and from the terminal.

FIG. 8 is a diagram illustrating a configuration of a user terminal 1100 according to another embodiment of the present invention.

Referring to FIG. 8, the user terminal 1100 according to another embodiment includes a receiving unit 1110, a control unit 1120, and a transmitting unit 1130.

The receiving unit 1110 receives downlink control information, data, and messages from the base station through the corresponding channel.

In addition, the control unit 1120 determines whether or not the overall operation of the user terminal 1100 according to performing a specific procedure for connecting the network through the side link connection based on the layer 2 relay, .

The transmitter 1130 transmits uplink control information, data, and a message to the base station through the corresponding channel.

The standard content or standard documents referred to in the above-mentioned embodiments constitute a part of this specification, for the sake of simplicity of description of the specification. Therefore, it is to be understood that the content of the above standard content and portions of the standard documents are added to or contained in the scope of the present invention.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (1)

In a method for a terminal to access a network,
Performing a side link connection based on a Layer 2 relay;
And performing a network connection through the side connection.

Images