WO2017196119A1 - Method and device for using resources in wireless mobile communication system - Google Patents

Abstract

The present invention relates to a 5G or pre-5G communication system for supporting higher data transmission rate compared to a beyond 4G communication system such as LTE. A method for using resources by an electronic device in a wireless mobile communication system can comprise the steps of: setting dedicated wireless access configuration for each service; detecting a first service request; and, on the basis of the setting, transmitting and receiving a signal by means of a dedicated wireless access configuration corresponding to the first service. The present invention is not limited to the embodiment and can pertain to other embodiments.

Description

Method and apparatus for using resources in wireless mobile communication system

The present invention relates to the use of radio resources in a wireless mobile communication system.

In order to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G communication systems or pre-5G communication systems. 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).

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 increase the propagation distance of radio waves, beamforming, massive array multiple input / output (FD-MIMO), and FD-MIMO are used in 5G communication systems. Array antenna, analog beam-forming, and large scale antenna techniques are discussed.

Meanwhile, the radio protocol of the LTE system includes packet data convergence protocol (PDCP) layers, radio link control (RLC) layers, at a terminal and a base station (ENB), respectively. Medium Access Control (MAC) layers are included.

The Packet Data Convergence Protocol (PDCP) layers perform operations such as Internet Protocol (IP) header compression / restore, and the Radio Link Control (RLC) layers are PDCP packet data units. Reconfigure (PDU: Packet Data Unit, PDU) to an appropriate size to perform an Automatic Repeat Request (ARQ) operation.

The MAC layers are connected to several RLC layer devices included in one UE, and perform an operation of multiplexing RLC PDUs to MAC PDUs and demultiplexing MAC PDUs to generate RLC PDUs. The physical layers perform channel coding and modulation on higher layer data, generate OFDM symbols and transmit them through a wireless channel, or demodulate, channel decode, and transmit the OFDM symbols received through a wireless channel to a higher layer.

In the existing LTE system, all services use the same configuration settings across radio resources. An example is shown below.

A default bearer is set, and then a dedicated bearer is set

The default bearer is BE; Each has one IP address (always-on IP connectivity)

All flows are mapped to one radio bearer (RB)

MAC / RLC / PDCP is configured per bearer

  Each signaling radio bearer (SRB) and data radio bearer (DRB)

The service may include applications having different QoS requirements (and combinations thereof), such as BE, eMBB, URLLC, mMTC, VoIP, etc., and may include latency, energy efficiency, power consumption, battery life, data rates, and other combinations of requirements considered important in mobile communications.

Existing LTE is designed for high-speed and high-mobility, and may not be suitable for supporting new services and requirements (eg, delay-tolerant, small data transmission for machine-type communication, MTC).

Therefore, 5G QoS framework requires a RAN (Radio Access Network) design optimized for each service for the connection between the terminal and the base station through a radio interface (Radio interface).

According to an aspect of the present invention, there is provided a method of using a resource of an electronic device in a wireless mobile communication system, the method including setting a dedicated wireless connection configuration for each service; Detecting a first service request; And transmitting and receiving a signal using a dedicated radio access configuration corresponding to the first service based on the setting.

An electronic device according to an embodiment of the present invention, a transmission and reception unit for transmitting and receiving a signal; And a controller configured to set a dedicated radio access configuration for each service, detect a first service request, and transmit and receive a signal using a dedicated radio access configuration corresponding to the first service based on the setting. have.

According to the present technology, by controlling the idle operation of the terminal based on the service and / or requirements, it is possible to optimize the signaling overhead and the terminal power consumption efficiency.

1 is a diagram illustrating an RAN hierarchy option according to an embodiment of the present invention.

2A to 2D are diagrams illustrating various examples of a physical hierarchy structure according to an embodiment of the present invention.

3 is a flowchart illustrating an example of an initial access and idle state operation using a common RAN according to an embodiment of the present invention.

4 is a view for explaining an example of a synchronization signal transmission using a common RAN according to an embodiment of the present invention.

5 is a flowchart illustrating a dedicated RAN setup and use according to an embodiment of the present invention.

6 is a flowchart illustrating an example of transmitting and receiving physical layer configuration information according to an embodiment of the present invention.

7 is a view for explaining an example of transmitting and receiving physical layer configuration information according to an embodiment of the present invention.

8 is a flowchart illustrating another example of receiving physical layer configuration information according to an embodiment of the present invention.

9 is a flowchart illustrating an example of system information transmission and reception according to an embodiment of the present invention.

10 is a flowchart illustrating another example of system information transmission and reception according to an embodiment of the present invention.

11 is a flowchart illustrating another example of system information transmission and reception according to an embodiment of the present invention.

12 is a flowchart for explaining another example of system information transmission and reception according to an embodiment of the present invention.

13 is a diagram illustrating an example of a protocol related to system information content setting for each service according to an exemplary embodiment of the present invention.

14 illustrates an example of MAC layer slicing for reducing system information overhead according to an embodiment of the present invention.

15 is a flowchart illustrating an example of performing PHY / MAC configuration for use by an MS in idle state according to an embodiment of the present invention.

16 is a flowchart illustrating an example of a network operation for enabling a PHY / MAC configuration operation according to an embodiment of the present invention.

17A is a diagram for explaining a connection for using a service in a public space.

FIG. 17B is a diagram illustrating a connection for service use in a PHY / MAC configuration according to an embodiment of the present invention. FIG.

18 is a flowchart illustrating a method of performing an access using a dedicated layer slice for a service according to an embodiment of the present invention.

FIG. 19A is a diagram for describing access according to physical layer configuration for each service according to an embodiment of the present invention. FIG.

19B is a diagram illustrating a connection according to a PRACH setting for each service according to an embodiment of the present invention.

20 is a flowchart illustrating another example of a method for configuring a RAN according to an embodiment of the present invention.

21 is a diagram for describing a method of applying RAN configuration to a control channel according to an embodiment of the present invention.

22 is an exemplary diagram of RAN configuration for each service according to an embodiment of the present invention.

Hereinafter, various embodiments of the present invention will be described in connection with the accompanying drawings. Various embodiments of the present invention may have various changes and various embodiments, and specific embodiments are illustrated in the drawings and related detailed descriptions are described. However, this is not intended to limit the various embodiments of the present invention to specific embodiments, it should be understood to include all modifications and / or equivalents and substitutes included in the spirit and scope of the various embodiments of the present invention. In the description of the drawings, similar reference numerals are used for similar elements.

As used in various embodiments of the present disclosure, an expression such as “comprises” or “comprises,” and the like indicates the existence of a corresponding function, operation, or component disclosed, and additional one or more functions, operations, or the like. It does not restrict the components. In addition, in various embodiments of the present invention, the terms "comprise" or "having" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, It should be understood that it does not exclude in advance the possibility of the presence or addition of one or more other features or numbers, steps, operations, components, parts or combinations thereof.

In various embodiments of the present disclosure, the expression "or" includes any and all combinations of words listed together. For example, "A or B" may include A, may include B, or may include both A and B.

Expressions such as "first," "second," "first," "second," and the like used in various embodiments of the present disclosure may modify various elements of the various embodiments, but limit the corresponding elements. I never do that. For example, the above expressions do not limit the order and / or importance of the corresponding elements. The above expressions may be used to distinguish one component from another. For example, both a first user device and a second user device are user devices and represent different user devices. For example, without departing from the scope of the various embodiments of the present disclosure, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

When a component is said to be "connected" or "connected" to another component, the component may or may not be directly connected to or connected to the other component. It is to be understood that there may be new other components between the other components. On the other hand, when a component is referred to as being "directly connected" or "directly connected" to another component, it will be understood that there is no new other component between the component and the other component. Should be able.

The terminology used in the various embodiments of the present invention is merely used to describe specific embodiments, and is not intended to limit the various embodiments of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of the present disclosure belong. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are ideally or excessively formal unless otherwise defined in various embodiments of the present invention. It is not interpreted in the sense.

Various embodiments of the present invention relate to RAN slices, partitions, or configurations. The subject constituting the RAN slice may be a base station, a network, or a terminal. According to various embodiments, various definitions of RAN slices may be used in each protocol layer (MAC, RLC, PDCP, and RRC) in a radio interface protocol of a wireless communication including an LTE system and a new radio access technology. For example, a common slice that can be used by all services and terminals and a dedicated slice that uses only a specific service or terminal may be configured.

In addition, various embodiments of the present disclosure relate to an operation in which a terminal applies and configures and operates a RAN slice.

For example, a slice utilization operation in a terminal IDLE state, a terminal in an idle state in a RAN sliced system wakes up, and receives a broadcast signal (cell search / synchronization (PSS / SSS), SI acquisition, etc.) for reception operation and on-demand mobility. An example of the operation to apply is described.

In addition, an example of slice operation operation, power efficiency improvement method, and service information based slice configuration of a CONNECTED terminal will be described. For example, the efficiency of the connected DRX operation can be improved by adjusting the inactivity timer based on the service / requirement of the transmission / reception data.

1 is a diagram illustrating an RAN hierarchy option according to an embodiment of the present invention.

A RAN slice, partition, or configuration will be described with reference to FIG. 1.

According to an embodiment of the present invention, different functions corresponding to MAC, RLC, PDCP, and RRC of a conventional LTE system, parameters and control signaling and user data set for controlling operations related to each function are provided. The RAN slice may be configured with one or more combinations of physical time and frequency resources for exchanging the.

The function and operation of each layer of protocol (corresponding to PDCP, RLC, MAC, PHY etc. according to LTE standard) can be dynamically set by the RRC layer in the control plane, and each other layer (PDCP, RLC) , Layers corresponding to MAC, PHY, etc.) can be set by transmitting information or signals. In addition, each service may be statically set as needed.

For example, the first option may be an RRC for each device, and the RRC may set functions and operations of lower layers.

The second option may be multiple RRC layers / entities / functions in the device, each responsible for controlling the radio resource connection of one service (each 'slice' consisting of lower layer settings). Corresponds to

The following definitions may be used in each layer (PHY, MAC, etc.) of the RAN Slice (or partition / configuration) Protocol.

The physical layer slices are different time-frequency resources defined for each service, and each physical layer slice may be transmitted and received through a separate physical layer channel mapped to each different numerology having a different numerology.

Physical (PHY) layer slice according to an embodiment of the present invention can be defined variously as follows.

a) It may be defined as a per-service resource block.

For example, referring to FIG. 2A, the entire range of the frequency spectrum belonging to the licensed owner may be divided into different blocks having different bandwidths according to necessity or request, depending on the type of service or deployment. has exist.

b) can be defined as a resource allocation for each service in the frequency domain within the system bandwidth range.

For example, referring to FIG. 2B, it may be a static resource allocation, and each slice may have a shared / single numerology or a numerology per service (eg, subcarrier spacing, bandwidth, etc.).

c) In the time domain, it may be defined as a physical channel setting for each service.

For example, referring to FIG. 2C, the resource allocation may be dynamic in the time domain, and the physical channel setting may be fixed in time or dynamically changed per service.

For example, it may be a time-frequency resource with shared / single numerology or numerology (subcarrier spacing, bandwidth, etc.) that is different for each service.

As another example, it may operate as a resource of each time-frequency-space-code-beam and each combination having a different numerology (subcarrier spacing, bandwidth, etc.) that is different for each shared numerology or service.

As another example, a single numerology or each numerology (subcarrier spacing, bandwidth, etc.) that is different for each service may operate as a resource of each time-frequency-space-code-beam and a combination.

d) Dynamic / Puncturing / Overlapped resource allocation.

For example, it may be a time-frequency resource with shared / single numerology or numerology (subcarrier spacing, bandwidth, etc.) that is different for each service.

As another example, it may operate as a resource of each time-frequency-space-code-beam and each combination having a different numerology (subcarrier spacing, bandwidth, etc.) that is different for each shared numerology or service.

As another example, it may operate as a resource of each time-frequency-space-code-beam and each combination having a single numerology or each numerology (subcarrier spacing, bandwidth, etc.) different for each service.

It may be defined as a signal transmitted and received on a physical resource and a physical resource setting of a channel corresponding to the signal.

For example, it can be defined as PSCH / SSCH, PBCH, SIB, control channel (PDCCH) resources, Paging, RACH, RRC signaling resource configuration. For example, each signal may use a fixed position in time / frequency space, or set a transmission position of each signal for each service. In connection with the above configuration, the base station transmits PHY channel (sub-frame, frame, slot, symbol) configuration information, and after synchronization, the terminal receives this information to configure and use the PHY channel resource. The physical layer channel configuration information may be transmitted and received on a predetermined time-frequency resource.

For example, referring to FIG. 2D, different numerology (subcarrier spacing, bandwidth, etc.) may be set and operated for each service.

The MAC layer slice according to an embodiment of the present invention may be variously defined as follows.

It may be defined by a combination of various functions performed in the MAC (for example, whether to perform HARQ / operation or whether to perform a random access operation).

It can be defined by a combination of the set of parameters which can be set in the respective functions and a combination of the operations accordingly.

For example, the MAC layer slice may be defined by some or all of the functions performed by the MAC, including the examples described below.

1) With regard to HARQ, the number of processes (e.g., in case of mMTC is set to use a small number of processes), the number of retransmissions, feedback (ACK / NACK) information, feedback timing, etc. can be considered. 2) (de Multiplexing and (dis) assembly can be considered. (In legacy LTE, RRC controls scheduling of each logical channel, and the method includes information about priority information and prioritized bit rate in a logical channel configuration information element (IE). 3) Consider from idle, while connected (contention-free) in random access, and 4) DRX cycle length / period, Amount of 'on duration' in DRX. , Length of DRX inactivity timer, etc. can be considered.

For example, the MAC layer slice may be defined by some or all of the functions performed by the RRC layer including the examples described below.

1) Mobility control setting of Idle terminal (parameters used to control cell signal strength, cell selection), 2) Mobility control setting of cell connected intensity (cell signal strength measurement period, variable used for control purposes) (Parameters), 3) broadcast information (cell-related system information, master information block) variables used to control transmission.

Meanwhile, the RAN slice or PHY / MAC slice may be a common slice or a dedicated slice.

A PHY slice is an allocation of each and combination of time / frequency / code / beam / spatial resources, which are isolated and divided radio resources, and can operate as a common slice or shared slice or dedicated slice. have.

In addition, the PHY slice may be an isolated and divided access channel, and may operate as a common slice or a shared slice or a dedicated slice.

The MAC slice is an isolated and divided RAN resource configuration and may operate as a common slice or a shared slice or a dedicated slice.

Common or Shared slices can be used by any device of any service type. The public slice may have a static setting or a dynamic setting.

For example, a shared slice may include 1) a setting value for applying (IDLE) when there is no RRC connection between a terminal and a base station (IDLE), or 2) a minimum value allocated for transmitting and receiving corresponding information. It can be defined as a combination of configuration and parameters of a physical (PHY) layer such as bandwidth Bmin, fixed MCS value, coding scheme, time, frequency, spatial resources, and physical layer channels and functions transmitted and received through the corresponding resources. The terminal may transmit and receive a signal transmitted and received at a physical layer slice corresponding to a common MAC slice using the common MAC slice. The physical layer slice may include a specific frequency / time resource used for exchanging information in an idle state. Such a common access control layer slice may be applied to all terminals in common.

The common slice is a combination of PDCP / RLC / MAC / PHY configuration applied to a signaling radio bearer (SRB) message transmitted in a control plane after an RRC connection is established between a terminal and a base station, that is, signaling It may include a common slice in the PDCP, RLC, MAC, PHY layer applied to the message transmitted as the information.

The shared slice may include some or all of the PDCCH, PBCH, PHICH, PCFICH, PUCCH, and PRACH area.

Dedicated or per service slice may be used to mean a slice used for a specific terminal or service, or for a specific purpose.

For example, the service-only slice may be a setting of a radio interface protocol (PHY, MAC, RLC, PDCP, RRC layer) including the following example, or a setting of a terminal and a base station operation using a radio interface protocol.

Example of UE operation setting

 * Adjust the time, power, period, etc. that the terminal spends on signal transmission by service

-Example of UE and base station setting

 * Frequency / time resource of the physical layer configured for each service, physical layer channels and functions transmitted and received through the corresponding resource

  / Example: PDCCH transmission / reception cycle setting for each service

 * Detailed operation setting of MAC function or specific MAC function set for each service

  TTI length setting per service

  Set transport block size (TBS) for each service

 * Detailed operation setting of RRC function or specific RRC function set for each service

  Mobility-related Settings by Service

  / Transmission of broadcasting contents with different contents for each service in different periods

   / Example: Categorize the information transmitted on BCCH logical channel by service

MIB-eMBB, MIB-URLLC, MIB-mMTC, etc.

SIBx-eMBB, SIBx-URLLC, SIBx-mMTC, etc. (x = 1, 2,…)

    Service setting such as broadcast information transmission cycle and update cycle

  * System variables (TTI length, timing alignment, system bandwidth, service priority, etc.) for coexistence operation by service (bearer, UE capability)

  * Different unlicensed band transmission and reception by service (bearer, UE capability, packet traffic class). For example, a variable for content-before-talk (LBT) operation in the physical layer (contention window size, backoff value range, energy / preamble detection threshold, sensing bandwidth, transmission power, etc.) or LBT protocol type (FBE (Frame) -based Equipment (CAT2), Load-based Equipment (LBE) -CAT4, etc.) and setting of the variable or / and LBT protocol (set, suite, package)

  * Set codebooks or tables for different transmission schemes of the various control signals and data signals in the physical layer, or a combination of the transmission schemes or a combination of the transmission schemes for each service (bearer, UE capability, packet traffic class).

  * Different transmission schemes or combinations of the transmission schemes for each DL (Downlink), UL (Uplink), SL (Sidelink) in the physical layer by service (bearer, UE capability, packet traffic class). Or set up a codebook or table for any combination of delivery methods

According to various embodiments of the present disclosure, the manner of setting the RAN slice (common slice and dedicated slice) may include the following example.

Common slices and dedicated slices can be predefined / configured in standard or other ways (static configuration case). The dedicated slice may be dynamically defined / configured according to the needs of the terminal or the base station (dynamic configuration case).

When information requiring transmission and reception occurs in uplink communication, a method of determining, by the terminal, a service type to be provided by the information may include the following.

  / Determine by performing packet inspection on packet data

When information requiring transmission and reception occurs in downlink communication, a method of determining, by the terminal / base station, a service type to be provided by the information may include the following.

  / Receive information from the network or base station about the service and its requirements for providing the service

Example: Some or all of the control information or user data transmitted by the network or base station

In a method of acquiring and using information on a slice configured in the above manner, the terminal or the base station may include the following method.

If you set the slice statically

-Store information on all slices in advance in the terminal and base station and select the appropriate slice if necessary

 For example, a manufacturer, a seller, or a carrier of a terminal may store information about one or more slices in advance in the terminal and the base station.

-Store all slice information to the base station by the carrier, network equipment provider, etc., and transmit the stored information to the terminal: An example of the transmission method is information of all RRC, PDCP, RLC, MAC, PHY layer including It may include a transmission and reception method.

 * The base station transmits part or all of the broadcast information and system information when the terminal searches for and selects an initial cell

 * Transmitted as signaling information (RRC message) from the base station in the process of initial registration (attach / register) to the network and the base station after the terminal is powered on

In addition, a common slice and a service dedicated slice may be mixed in each layer of a protocol used by a terminal or a base station.

In the case of transmission / reception information generation, the terminal and the base station may select a slice suitable for the corresponding service, and transmit the information about the slice to the terminal. The delivery method may take an implicit or explicit manner.

 * Example 1 (implicit): A transmitter selects a service-based specific slice and detects and judges the receiver.

 * Example 2 (explicit): The transmitter directly transmits information about a service type to the receiver.

  / Example: Included in base station RRC signaling (e.g. paging message, etc.)

  / Example: Mapping each slice setting / definition with an index and transmitting and receiving index information

Table 1 below shows an example of RAN slice information.

Table 1 service RAN Slice information 0 Common slice (eg for initial connection) (Slice Settings Information) One eMBB (Slice Settings Information) 2 URLL (Slice Settings Information) 3 mMTC (Slice Settings Information) 4 VoIP (Slice Settings Information) 5 Best Effort (BE) (Slice Settings Information)

<When setting the slice dynamically>

A terminal establishes a connection with a base station using a common slice during initial access, and sets a dedicated slice based on a service type of transmission / reception information generated from the terminal and the base station.

When a base station and a terminal perform a transmission / reception operation by applying a specific slice, a different transmission / reception method or a different transmission / reception operation configured for each service may be used as described in the above table.

Table 2 below shows that the base station and the terminal may have different settings when performing a transmission and reception operation by applying a specific slice.

TABLE 2 Base station / network Terminal Use common slices Use dedicated slices for services Common sending / receiving operation between services Use common slices Use dedicated slices for services Sending / Receiving Operation by Service Sending / Receiving Operation by Service Use service-only slices Send / Receive Operation by Service

The common slice and the dedicated slice are applicable to each of time, frequency, spatial resources allocated for transmitting and receiving information between the terminal and the base station, and physical layer channels and functions transmitted and received through the corresponding resources.

Table 3 below shows a common slice application or a dedicated slice application option for each signal transmitted and received in the IDLE state.

TABLE 3 Signal and Channel Operation Slice Signal type Synchronous signal MIB SIB Paging RACH RRCconnectionrequest / setup Control signal PHY channel PSCH / SSCH PBCH PDSCH PDSCH PRACH PDSCH PDCCH Common x Dedicated x x

Table 4 below shows a common slice application or a dedicated slice application option for each signal transmitted and received in the connected state.

Table 4 Signal and Channel Operation Slice RRM-RLF Operation RRC Settings PDCP Settings RLC Settings MAC settings PHY settings Common x Dedicated x x x x x

In addition to the examples shown in the above table, various combinations of common slices and dedicated slices can be set.

The name of the slicing concept described above may be referred to as other terms having the same meaning without being limited to slice. (E.g. partition, allocation, resource component, etc.)

The term 'service' used in the present invention is not limited to the above examples (eMBB, URLL, mMTC, best effort, VoIP), and various requirements for information transmission performance (transmission delay time, QoS, QoE, data rate, etc.) It can be made of a combination of.

Hereinafter, a system operation plan in a sliced RAN environment having different PHY numerology, MAC configuration, etc. for each service having different requirements according to various embodiments of the present disclosure will be described.

A method of setting a RAN slice performing an idle mode operation for each service is proposed, and through this, it is possible to achieve energy efficiency of a terminal / base station by reducing overhead information transmission and reception.

The following operation describes the steps of performing an Idle operation using the RAN slice.

Configuring some or all of the PHY / MAC Slices based on the operation and configuration information of the physical layer and the MAC layer required for each service or commonly required between services;

 * The configuration information may be a configuration in the RRC, PDCP, RLC, MAC, PHY layer including a variable for controlling the IDLE state operation and related signal transmission and reception operations.

Examples of the setting information include setting for each service of broadcast information content, setting for transmission / reception period and update period for broadcast information, synchronization signal transmission / reception setting, setting for random access operation control and setting for random access resource, paging message Its features include setting of contents and transmission and reception, control channel setting and control signal transmission and reception.

Transmitting or storing information on the slice configuration to a terminal and a base station;

Selecting a slice for performing an IDLE state operation and transmitting and receiving an associated signal at a terminal or a base station;

 * The slice for the idle operation may be selected as a common or service-only slice, and the method of defining each slice and the setting method in the terminal / base station may include methods according to the above proposal.

 The criterion for selecting the slice includes various cases, such as selection based on service information or based on slices used by the base station and the terminal.

Performing an IDLE state operation at a terminal and a base station by applying the slice configuration and transmitting and receiving a radio access signal as necessary;

  The Idle state operation may include PLMN selection, cell selection and reselection, paging message reception, random access, and overall operations performed in the idle state of the mobile communication system. Each of the operations may include a common RAN slice, a dedicate RAN slice, or two. Can be supported in multi.

  The terminal and the base station perform some of the idle operations, for example, system synchronization signal transmission and reception, system information transmission and reception through a common RAN slice, and other idle operations such as paging transmission, random access, call setup, etc. The dedicate RAN slice can be used in different ways for each service.

Additional operation example for the terminal:

Step 0. Determining whether there is information about a service type of information to be primarily transmitted and received by the terminal;

 The information on the service type may be provided service preference information (priority / preference) information stored in the terminal, service information obtained by packet inspection on uplink data, or service information of downlink data transmitted from a base station.

Step 1. Configure the RAN slice that the terminal will use to transmit and receive information;

The RAN slice may be a common slice or a dedicated slice, and may be set in a static or dynamic manner as described above.

In the previous step, the common slice or the dedicated slice may be selected based on the presence or absence of information on the service type or the information on the service type.

Step 1-1. If there is no information on preferred service type (or if the service type of the device is not determined, if there is no service information for transmission / reception information), the following operation may be performed by selecting a common slice.

  Receive / sync / SI;

  / select cell;

If the base station connection operation is for initial attach (registration with network),

  / attempt random access;

  / Request and receive rrc signaling to setup connection with base station;

  Attach request with RRC message;

(In this case, it can send information about service preference / capability, etc.)

  / Connected mode operation

When a terminal already attached / registered to the network performs idle mode operation,

  Receive paging message (at paging occasion):

Characteristic is that the service type information of the data can be sent from the base station and the network.

  / attempt random access;

  / Request and receive rrc signaling to setup connection with base station;

  / send service request;

(In this case, it is possible to convey information about service preference / capability, etc.)

  / Connected mode operation

Step 1-2. Else if service mode / preference is known (or if the device's service type is specified, e.g. mMTC type device)

Use dedicated slice / configuration to perform the above operations;

The order and whether or not the operation is performed may be changed as necessary.

Table 5 below shows an example of slice settings for each signal.

Table 5 Signal and Channel Operation Slice Signal type Synchronous signal MIB SIB Paging RACH RRCconnectionrequest / setup PHY channel PSCH / SSCH PBCH PDSCH PDSCH PRACH PDSCH Common x x x x Dedicated x x

3 is a flowchart illustrating an example of an initial access and idle state operation using a common RAN according to an embodiment of the present invention.

The terminal may acquire symbol timing, physical cell ID, subframe timing, etc. by synchronizing with each cell.

Referring to FIG. 4, it can be seen that in a frame composed of N subframes, for example, a synchronization signal transmission position is fixed in frequency and time space. In the example of FIG. 4, the sync signal may be transmitted through the center x RB of the first frame transmitted every T seconds.

An embodiment of an operation of transmitting and receiving system information through a common slice, and performs PBCH transmission and reception according to the contents set in the slice, and obtains SIBx (x = 1, 2, 3,…) by decoding the PDSCH at the scheduled position. can do.

As an embodiment of an operation of performing random access through a common slice, when the purpose of call setup is Initial attach, random access may be performed through a common slice. In this case, the common slice PRACH configuration information may be obtained from the SIB or determine the PRACH resource information according to a predetermined configuration value. The detailed PRACH procedure may be similar to the operation of the conventional mobile communication system.

As an embodiment of an operation of performing random access through a dedicate slice, when the purpose of call setup is setting MT call through paging or setting MO call for each service, random access may be performed through dedicate slice. The paging signal may include information about a service. In this case, the dedicate slice PRACH configuration information may be obtained from the SIB received from the common slice or the PRACH resource information may be determined according to a predetermined configuration value. The detailed PRACH procedure may be similar to the operation of the conventional mobile communication system.

As an embodiment of an operation of performing RRC connection setup and RRC reconfiguration through a common slice, when the purpose of call setup is Initial attach, RRC and lower layer operation configuration may be performed through a common slice.

As an embodiment of the operation of performing the RRC connection setup and RRC reconfiguration through the dedicate slice, if the purpose of call setup is to set the MT call through paging or the MO call for each service, dedicate slice for the RRC and lower layer operation settings. Can be done via: The paging signal may include information about a service.

As an embodiment of an operation of performing RRC, NAS control message and user data through a common slice, when the purpose of call setup is Initial attach, RRC information transmission and reception may be performed through a common slice.

As an embodiment of an operation of performing RRC, NAS control message and user data through a dedicate slice, when the purpose of call setup is setting MT call through paging or setting MO call for each service, transmitting and receiving RRC information through dedicate slice Can be done. The paging signal may include information about a service.

As an embodiment of an operation of performing a paging message through a common slice, a paging message may be transmitted and received according to the contents set in the common slice. The paging signal may include information on a service.

According to an embodiment of the present invention, a service dedicated slice may be applied.

Table 6 below shows another example of slice configuration for each signal.

Table 6 Signal and Channel Operation Slice Signal type Synchronous signal MIB SIB Paging RACH RRCconnectionrequest / setup PHY channel PSCH / SSCH PBCH PDSCH PDSCH PRACH PDSCH Common x x x x x Dedicated x x x x x x

5 is a flowchart illustrating a dedicated RAN setup and use according to an embodiment of the present invention.

As described above, the terminal may perform an idle mode operation for initial access on the shared slice.

The terminal may transmit the service capability / preferred information to the base station / network by transmitting a connection request message in the RRC connection establishment complete message or by indicating a random access resource (which may mean a preamble sequence).

The base station / network may transmit information on the dedicated RAN slice configuration to the terminal as part of the RRC reconfiguration message content or part of the RRC connection release message content.

For example, the dedicated sync configuration may include variables such as signal transmission location (freq / time), period (e.g., mMTC is set long, URLL / eMBB / VoIP is set short, and fast synchronization is acquired). .

According to an embodiment of the present invention, a method for supporting one or more settings for a physical channel and a method for providing information on a physical channel configuration are provided.

The content of the 'physical channel configuration' may include a time / frequency resource of the physical layer, its structure, and a transmission / reception signal. (E.g. part or all of PDCCH, PBCH, PHICH, PCFICH, PUCCH, PRACH area)

The base station may provide information (eg, symbol / subframe / frame structure in which a signal is transmitted) on how frequency / time resources are set.

The terminal may acquire information on the physical channel configuration after synchronization with a specific cell.

On the other hand, there may be various examples of the method for delivering the physical channel configuration information.

Referring to FIG. 6, as an example, information on a physical channel configuration (PHY configuration) may be delivered (defined as a common slice) at a fixed resource location. Referring to FIG. 7, in a frame composed of N subframes, for example, a physical channel setting transmission position may be fixed in a frequency and time space.

Referring to FIG. 8, as another example, PHY configuration information may be delivered as system information (SI) using fixed scheduling of MIB (and SIB).

Meanwhile, as another example, PHY configuration information may be delivered to the SI using the RAN slice structure.

Table 7 below shows an example of an SI information transmission / reception scheme (overhead reduction scheme) using the RAN slice structure.

TABLE 7 Signal and Channel Operation Slice Signal type Synchronous signal MIB SIB Paging RACH RRCconnectionrequest / setup PHY channel PSCH / SSCH PBCH PDSCH PDSCH PRACH PDSCH Common x x Dedicated x x

The terminal may receive an SI transmitted by the base station after synchronizing a signal using a shared or dedicated slice configuration.

For example, referring to FIG. 9, in a common configuration, a base station and a terminal may transmit and receive MIB and SIB at a fixed resource location at all times.

For example, referring to FIGS. 10 and 11, the base station may transmit to the terminal by applying different SI-related settings for each service in various ways.

10 and 11, the service-only slicing method may include the following.

a) how the base station has different transmission settings

In the RRC, the base station may transmit different contents to the MIB and / or SIB for each service.

For example, the DL-bandwidth value of the MIB sent by the base station may be differently designated for each service and transmitted.

For example, in case of mMTC, the base station sets DL-bandwidth = B_mMTC (unit: Hz), and in case of eMBB, DL-bandwidth = B_eMBB (unit: Hz), wherein the value of B_eMBB is larger than B_mMTC. to be.

In the case of URLLC as well, DL_bandwidth = B_URLL is set and its value can be set differently from other services. In addition, the value of essential information (Phich setting, etc.) included in the MIB may vary for each service, and the SIB may be grouped for each service.

The base station may transmit and receive by applying dedicated scheduling (period, receive duration, location in frame / sub-frame, etc.) for each service to the MIB.

The base station may transmit and receive by applying dedicated scheduling (period, SI transmission / reception window length, receive duration, location in frame / sub-frame, etc.) for each service to the SIB. (Service-oriented UEs with battery life or latency critical settings should be able to receive the minimum required SIB at the minimum time.)

b) a method in which the base station broadcasts the SI content regardless of the service and the terminal controls the SI reception operation;

For example, the base station may transmit the MIB contents as a BCCH-BCH message in the protocol and transmit the message on the PBCH channel. In this case, the UE may repeatedly receive the PBCH several times. In this case, the UE may control the number of repetition receptions according to the coverage and signal strength of the UE.

On the other hand, referring to Figure 12, the base station may transmit to the terminal by applying different SI-related settings for each service. When synchronization is operated in a shared slice (eg, sharing a physical channel configuration), the common configuration for PHY PBCH transmission may be set to one PBCH configuration in which the base station transmits a BCCH-BCH message (MIB). FIG. 13 shows an example of a protocol for setting SI (MIB, SIB) content for each service, and FIG. 14 shows an example of a MAC configuration slicing protocol for reducing SI overhead.

Referring to FIG. 15, the base station may deliver a PHY / MAC slice configuration to be used by the terminal in idle to the terminal in RRC signaling.

On the other hand, the SI information acquisition method of the terminal may include a combination of the various proposals.

Hereinafter, initial connection (eg, transition from idle to connected) operation, paging, and UL RACH operation using the sliced RAN structure will be described.

According to an embodiment, a method of performing wireless access and connection establishment in a common RAN slice is as follows.

In the case of Mobile Terminated (MT) or DL initiated access, the base station receives a Paging Request message from the MME through the S1 interface. P0 is calculated based on the S-TMSI and the UE identity index value, and the RRC message paging is scheduled. The PDCCH is transmitted at P0 calculated for each UE.

Meanwhile, all UEs use the same physical resource to monitor the PDCCH. The resource location for the PDCCH is the same for all terminals. Each UE monitors the PDCCH at P0 for P-RNTI (UE-specific PO). Read the PDSCH and decode the PCH transport block to confirm the paging message. If its ID is included, access is started from uplink.

For uplink access, all terminals can use a common PRACH location in time and frequency regardless of service in the PHY. In the MAC, all terminals and services may use the same RACH procedure / configuration.

According to an embodiment, a method of performing wireless access to a shared slice in downlink (for paging) and a dedicated slice in uplink (RACH) is as follows.

In the case of Mobile Terminated (MT) or DL initiated access, RRC based operation may be performed.

For example, the base station may receive a Paging Request message from the MME through the S1 interface and calculate P0 for related UEs. The base station configures a paging RRC message, and the paging message includes a 'paging record', information about a paged user (UE identity (eg, IMSI / S-TMSI, etc.)) and information about a service (index to indicate service type (e.g., eMBB, URLL, mMTC, etc.). The base station schedules a downlink data channel for RRC message paging. PDCCH is transmitted at P0 calculated for each UE.

All terminals can monitor common PDCCH resources (common search space). The frequency position for the PDCCH is the same for all terminals. Each UE monitors the PDCCH at P- for P-RNTI (UE-specific PO). The terminal reads the PDSCH and decodes the PCH transport block to confirm the paging message.

In RRC idle mode, each 'paging record' is included in the paging message. One of the terminal identifiers assigned by the higher layer of a terminal identifier (ue-Identity) included in the paging record is matched. In response to the detection of the terminal identifier corresponding to the service information in the paging record, the terminal starts uplink access on the dedicated RAN slice / resource element.

The network operation shown in FIG. 16 may be used to enable the operation. That is, the network may provide one or more of the following MT data.

-Type of service

Quality of service, requirements

Priority level

The terminal may access the network with one or more service capability (and corresponding priority level) information. (For example, the terminal may mainly use the eMBB service)

For uplink access (including mobile originated case), a dedicated RACH configuration per slice is used, and the PHY configures different PRACH resources in the frequency and time domains for each service. In the MAC, all terminals use PRACH. If pMB is transmitted for eMBB service and uplink, for example, mMTC may send a RACH sequence longer, but the number of RACH attempts may be limited. Alternatively, the terminal receiving the paging message may perform RACH back-off based on other paged terminal service and priority information.

For example, referring to FIG. 17A, a terminal may be delayed when different services (VoIP and mMTC) occur in a common space. However, referring to 17b, a terminal may perform access when each service occurs through a dedicated slice. In this case, access opportunities may be determined based on priority. 18 illustrates a method of connecting using a dedicated slice according to the embodiment.

According to an embodiment, a method of performing wireless access to a dedicated RAN slice for downlink paging of a terminal and a dedicated RS for uplink access is as follows.

In case of Mobile Terminated (MT) or DL initiated access, the base station may set UE-specific and / or service-specific paging occasion (PO). For example, VoIP and URLL can shorten the DRX cycle, which can be set when sending an RRC Release message. Alternatively, the base station may receive paging from the MME and calculate the next P0 based on the information paging to the terminal. Alternatively, index n (the number of P0s to wait before the base station transmits scheduling information about the UE on the PDCCH) may be provided. The base station may schedule a paging message for each terminal. The scheduling information may be transmitted at the corresponding P0. The terminal may perform the connection (including the MO case). FIG. 19A shows a connection of a terminal in case of physical layer configuration divided by service, and FIG. 19B shows a connection of a terminal in case of PRACH setting for each service.

According to an embodiment, in connection with performing access to a dedicated RAN slice for downlink paging and a dedicated RS for uplink access, a downlink access operation and an uplink access operation may be performed using the service dedicated slice and related operations. have.

Meanwhile, an operation of an idle terminal using a RAN slice according to an embodiment of the present invention is as follows.

UE energy efficiency may be improved by configuring a RAN slice for performing a connected mode operation for each service.

For example, the service and the requirements provided by the transmission and reception information generated in the terminal or the base station can be determined.

In addition, the UE may set a variable controlling the operation of the physical layer and the MAC layer as part or all of the PHY / MAC Slice information. The variable may be configured at the RRC, PDCP, RLC, MAC, and PHY layers including variables for controlling the Connected DRX operation and the handover operation of the mobile terminal. Examples of the variable may include an inactivity timer length (DRX operation start time), a control channel and a signal transmission / reception time of a terminal, a length of a DRX cycle, and the like. In addition, a variable that triggers a handover, such as the number and period of cell signal strength measurement, may include a handover control signal (signalling) number of transmission and reception, the number of cells for which the terminal measures signal strength, and a control signal transmission and reception time.

The terminal may transmit or store the information on the slice configuration to the terminal and the base station. In addition, information may be transmitted and received by applying the slice setting.

The specific operation of the terminal may be as follows.

For example, the terminal may determine a service type of a packet transmitted and received by the terminal, or a service type of data generated at the terminal and the base station. If the terminal determines, it may provide information on the service type to the base station.

In addition, the terminal may determine the importance of the connected mobility for the service. For example, in case of URLL, eMBB, VoIP, etc., the priority and priority of connected mobility are determined to be high priority, and when the service type of a transmission / reception packet generated in a terminal / base station is mMTC, priority of importance and preference of connected mobility is set. Can be set low.

In addition, the mobility operation may be set based on the determination result. For example, in the case of mMTC, it may be set to not support the connection state mobility, and in the case of the URLL service, the cell signal measurement number for the IDLE and CONNECTED state mobility operations may be set, and the number may be higher than that of the mMTC. Can be. In addition, the value of the set variable is characterized in that it can use a value optimized for each service and its requirements. In addition, through the configuration, it is possible to determine whether to support mobility in the terminal and the base station and set the result as part of the RAN slice.

In addition, referring to FIG. 20, the terminal may provide service information to the base station. For example, the service information may be service preference information provided by the terminal upon initial attach. Alternatively, in case of paging or uplink data generation, service information may be transmitted to the base station when accessed from idle. In this case, the RACH resource may be used (PRACH location, preamble, etc.), or may be transmitted when establishing an RRC connection (e.g. RRC Connection Request, Connection Setup Complete, etc.). In addition, when idle access is performed using a dedicated slice, when the base station is determined as a signal reception location, service information may be transmitted to the base station.

 The base station may set the RAN slice based on the service information sent by the terminal, and transmit slice / configuration information to the terminal. For example, it may be transmitted to the terminal through RRC signaling.

Meanwhile, the RAN slice may be set by service-specific control of an inactivity timer.

For example, when the terminal transmits a notification that the base station attempts to access the mMTC data, the base station may set the inactivity timer to x and transmit it to the terminal along with other slice information. The terminal may establish an RRC connection with the base station to start data transmission and reception. The UE MAC may restart the inactivity timer whenever the control channel (eg, PDCCH) indicates new UL / DL data.

According to various embodiments of the present disclosure, the control channel slice design may be performed by applying a common transmission / reception setting or a transmission / reception setting for each service to a signal transmitted and received on the PDCCH channel and the PDCCH, as shown in FIG. 21.

For example, the PDCCH search area may be set for each service and may include a common configuration and a dedicated configuration for each service.

The slice application operation to the control channel is applicable to both the IDLE state operation and the CONNECTED state operation of the terminal.

According to an embodiment of the present invention, a method of shortening a period (RRC CONNECTED period) during which a terminal activates a radio link for improving terminal power efficiency is as follows.

Modem operation mode can be controlled based on QoS requirements characteristic information such as support service type (eMBB, URLLC, mMTC) or RAN Slice-specific Latency.

Information per support service or RAN slice may include at least one of the following information.

1) QoS required by service or RAN Slice

i) QoS is a service requirement including data rate, latency, mobility, reliability, power consumption, and connection density.

2) PHY resource allocation information by service or RAN Slice

i) sub-carrier spacing,

ii) frame structures

3) L2 configuration information by service or by RAN Slice

i) Example of PDCP layer and service vertical based header compression and ciphering operation and omission

ii) operating in RLC unacknowledged mode (e.g. sensor)

acknowledged mode only (e.g. mission critical services).

iii) In MAC / PHY, carrier aggregation operation and omission setting

H-ARQ operation mode control method

spectral efficiency (massive broadband)

coverage (sensor, IoT), reliability (mission critical services)

or latency (tactile Internet).

4) Warming Up Time (WUT) information by service (by RAN Slice)

iv) Time for synchronization procedure operation

Operation time increase / decrease information according to beamforming

v) System Information Receiving Procedure Operation Time

Operation time increase / decrease information according to beamforming

vi) Paging Receive Procedure Operation Time

Operation time increase / decrease information according to beamforming

vii) switching on hardware circuit

viii) including precise-clock,

ix) RF circuit related massive antennas

x) additional high speed core processor.

5) Promotion delay information by service (by RAN Slice): Cost (power consumption and delay time) information required by the UE, including an example of switching from RRC IDLE to CONNECTED, from the low power mode to the data transmission / reception mode

xi) Option information about signaling setting necessary for switching from RRC IDLE to CONNECTED

xii) time and power consumption cost information

xiii) MME holds UE Context information even in RRC idle mode,

S1-AP NAS Service Request and S1-AP Initial Context Setup Request

Operates as a criterion for the terminal and / or base station modem operation mode

The modem operation mode control method based on information for each support service or RAN slice may include at least one of the following operations.

1) Aggregation control operation for QoS based by service or by RAN Slice;

2) Terminal measurement cycle extension / decrement operation

3) RRC connected standby time (Radio Tail) period control operation

RRC connected latency and Radio Tail duration and

Inactivity Timer Control Behavior

i) Controlling terminal connection waiting time reduction by shortening Radio Tail (Inactivity Timer)

ii) Extending terminal connection waiting time by extending Radio Tail (Inactivity Timer)

4) Long DRX operation in terminal connection mode

A. DRX Cycle Expansion and Decrease Control

B. DRX duty cycle expansion and reduction control

In addition, the information proposed in the present invention is also applicable to a communication system using a transmission / reception and beamforming technology in a high frequency band.

According to an embodiment of the present invention, when packets for various types of services are generated at the same time, the service priority is determined and the RAN slice is configured, selected and applied based on the priority, or the requirements are highest (eg high speed / Low latency /.) RAN slice can be set / selected as a service standard and data for other services can be piggybacked and transmitted.

22 is an exemplary diagram of RAN configuration for each service according to an embodiment of the present invention. FIG. 22 shows an example of a RAN slice with L1 and L2 settings optimized for eMBB, mMTC and URLLC services, respectively.

An initial network attach operation of a terminal according to an embodiment of the present invention may be performed in consideration of the following criteria.

1) Storage location of wireless protocol (referred to as 'slice' for convenience) based on service QoS

2) Presence or absence of prior knowledge about the type of service the terminal provides (sends and receives)

Hereinafter, an initial network access operation of a terminal considering the above criteria will be described.

A. If the dedicated slice setting for each service is stored in the terminal and the base station, the terminal and the base station may operate by selecting a slice suitable for a specific situation.

A.1. In this case, if there is no prior knowledge of the service type mainly provided by the terminal, the slice may be selected (the terminal selects or selects according to the command of the base station) according to the transmission / reception data type generated after network registration. In addition, the following procedure for establishing a wireless connection and registering a network using a common slice between the terminal and the base station may be performed. (You can perform operations similar to existing mobile communication systems.)

* Acquires cell ID by receiving synchronization signal

* Receive broadcast information

* (PLMN / cell selection cell selection)

Random access

* RRC connection establishment

* Send and receive RRC signaling signal to SRB (e.g. authentication and security setting related message)

Thereafter, when transmission / reception data occurs in the RRC connection state, the following operation may be performed.

* Send service information (RRC message, etc.) and receive response to base station (for uplink transmission)

* (For downlink transmission) base station transmits service information to the terminal (such as RRC message) and response

User information can be transmitted and received with the selected service-only slice.

A.2. On the other hand, if there is prior knowledge on the type of service provided mainly by the terminal, the terminal informs the base station of the service type information when the terminal performs an initial access procedure for registering with the network, and subsequently transmits and receives information according to the service type. The terminal or the base station may select a slice. The following is an example of a method and operation of a UE informing service type information to a BS / network.

A.2.1. Deliver to base station and network as part of RRC message

Step 1: Using the common slice between the terminal and the base station, perform the following operation.

 * Acquires cell ID by receiving synchronization signal

 * Receive broadcast information

 * (plmn / cell selection)

 Random access

 * RRC connection establishment

Step 2: The terminal sends information on the service type to the base station. The means for delivering the information may be an RRC message (eg, RRC Connection Request, RRC Connection Setup Complete, etc.), or random access resource selection.

Step 3: The base station transmits whether to support the service and slice selection indication information to the terminal. The information includes a method of delivering in an RRC message, and may have a form as shown in the example of A.1.

Thereafter, the terminal IDLE operation may be performed using a shared slice or a dedicated slice, and when connected, a dedicated slice based on service information may be used.

A.2.2. UE selects a cell according to whether the base station supports the service

Step 1: The RRC connection can be established using the common slice between the terminal and the base station as follows.

 * Acquires cell ID by receiving synchronization signal

 * Receive broadcast information (base station transmits whether a specific service is supported as part of broadcast information (SI), and may have the form as shown in the example of item A.1)

 * Selection of plmn / cell supporting terminal service based on the SI contents

 Random access

 * RRC connection establishment

Thereafter, the terminal IDLE operation may be performed using a shared slice or a dedicated slice, and when connected, a dedicated slice based on service information may be used.

The subject of the slice selection may be a slice management entity individually implemented in the RRC layer of the terminal or the base station, or the transceiver.

B. You can dynamically configure slices for each service as needed.

Operation examples described below may be performed first using a common slice when the terminal initially accesses the network.

 * Acquires cell ID by receiving synchronization signal

 * Receive broadcast information

 * (plmn / cell selection cell selection)

 Random access

 * Send RRC connection request message

B.1. In this case, when there is no prior knowledge about the service type mainly provided by the terminal, the following operation may be performed.

-B.1.1. Network registration is done using a common configuration and on-demand configuration based on subsequent service types.

RRC Connection Setup message can be received. At this time, the RRC connection setup message may include a setting for controlling the control channel observation operation of the terminal in the connected state as part of the MAC configuration. (SR setting, BSR setting, etc.) (Inactivity timer start and end time, timer length, etc. to start the connected DRX operation) Meanwhile, uplink configuration and downlink configuration may be different.

According to the received RRC connection setup message, SRB can be established and entered into the connected state.

You can send an RRC Connection Setup Complete message. At this time, a higher layer message (attach request) may be included and transmitted.

RRC signaling can be transmitted and received (e.g. authentication and security configuration related messages).

When transmission / reception data for a specific service occurs in the RRC connection state, the service type of the corresponding data may be determined.

Meanwhile, in the case of uplink transmission information, the information is transmitted to a corresponding service type base station / network, and a detailed method thereof is described below.

The base station and the network inform the terminal by setting or selecting a slice based on the received service information, and the method includes a method using an RRC message.

The terminal may receive slice information through SRB configuration and set up a service-only slice. Then, user information can be transmitted and received.

On the other hand, unlike the existing mobile communication system, the operation is characterized in that to perform the RRC connection reset operation only when the transmission and reception data occurs.

-B.1.2. Network registration is performed by using a common configuration, and receives information about slices and services supported by the base station, and the terminal selects slices according to service types that occur afterwards.

You can receive the RRC Connection Setup message. SRB can be established according to the received RRC connection setup message. Thereafter, the RRC connection Setup Complete message can be transmitted. In this case, the upper layer message may be included. (For example, attach request)

RRC signaling can be transmitted and received to the SRB (e.g. authentication and security configuration related messages).

Configuration information for all slices supported by the base station may be transmitted to the terminal. At this time, it may be delivered in an RRC message (RRC Connection Reconfiguration, etc.). The terminal stores each slice information.

Thereafter, when transmission / reception data generation is detected, the terminal may select and use a dedicated slice for the corresponding service to perform transmission / reception with the base station.

B.2. If there is prior knowledge about a service type mainly provided by the terminal, the following operation may be performed.

The initial access procedure for the UE to register in the network is performed with a common slice, and at this time, the service type information may be informed to the base station. The detailed operation of the UE informing the base station of the service type information may be similar to that of the A.2 item, and unlike the A.2 operation selecting a preset slice, in this case, the UE or the base station is needed as to the transmission / reception information generated. It is a feature of setting this slice. As a specific method for setting a service dedicated slice and transmitting the information by the base station or the terminal, various examples presented in other operations may be used (eg RRC signal transmission and reception).

Signals transmitted and received by the terminal and the base station after the SRB may include a signaling message for network configuration other than the security authentication-related signal, the detailed message and operation may be similar to the existing mobile communication system.

The method for delivering the slice or transmission / reception service type information selected by the terminal and the base station may include the following.

1) How to send as part of an RRC message (IE)

 When the base station informs the service type of the downlink transmission information, the service type information may be included in the paging message.

Example: Sending terminal ID and receiving / receiving information service type together

2) How to indicate with scheduling request (SR) signal of MAC

3) How to indicate with a buffer status report (BSR)

4) How to indicate with other MAC control element information (CE)

5) A method of delivering using a specific resource location or signal of the physical layer

6) How to transmit as part of scheduling information transmitted from the base station

7) A method of indicating by an n-bit indicator indicating the slice / service selected by the terminal or the base station. See Table 8 below.

Table 8 index Service type Supported? 0 (Common slice or signaling etc.) One service type 1, egeMBB One ... ... ... n service type n, eg mMTC 0

(1 = supported, 0 = not supported)

In addition, some or modified forms of the above methods and embodiments may be utilized.

Hereinafter, various embodiments of an operation in which the terminal selects and uses a slice in the IDLE state will be described.

'IDLE operation' referred to in the present invention is characterized in that it includes an operation for transmitting and receiving a synchronization signal, transmission and reception of broadcast information, cell (re) selection, paging message, etc., the detailed operation is similar to the operation of the conventional mobile communication system can do.

In addition, the 'connection operation for transiting from IDLE to CONNECTED state' described below includes a random access and RRC connection establishment operation for requesting connection to a base station after detecting the presence of a transmission / reception service, and a security related signal transmission / reception operation. Etc., and detailed operations thereof may be similar to those of the conventional mobile communication system.

The following is an example of the slice selection operation of the terminal in the IDLE state.

-Selecting a common slice to operate IDLE and using a dedicated slice when establishing a wireless connection (idle to connected)

Step 1. The UE performs IDLE operation using the shared slice. That is, all terminals perform IDLE operations using the same physical layer resources and operation settings regardless of the transmission / reception information service type.

Step 2. Determine the service type of the downlink standby information when receiving the paging message.

Step 3. Perform a connection operation to transit from IDLE to CONNECTED state using a service-only slice. That is, the operation of requesting connection to the base station is different for each service.

-Selecting a dedicated slice for each service to perform IDLE operation and operation for accessing a base station differently for each service

Step 0. The base station sets or selects a slice to be used by the terminal in IDLE.

The slice may be a common slice setting commonly applied to all terminals, or may be set as a service-only slice. In the latter case, the terminal may determine the service type of the information mainly transmitted and received in the connected state, and set the slice based on the result. The detailed criterion may be service information stored in the terminal / base station, or the amount of information transmitted and received by the terminal in a connected state for each service.

Step 1. The slice information is transmitted / transmitted from the base station to the terminal.

The slice information may be delivered as part of an RRC message (eg, RRC Release, Suspend, Reconfiguration, etc.).

Step 2. The IDLE operation is performed according to the slice information received by the terminal.

-How to perform IDLE operation based on the service-only slice used in the last connection state

The slice may be a public or service only slice.

If information having different requirements (or other service types) occurs during the IDLE operation, the service type of the information can be transmitted to the base station, and a common configuration or a service dedicated configuration can be used.

Meanwhile, the common slice operation and the service dedicated operation of the terminal in the IDLE state may include the following examples.

For example, as an embodiment of an operation of performing synchronization through a dedicated slice, it may include at least one of the following operations.

1) The synchronization signal transmission and reception may be different for each slice.

2) A synchronization signal transmission / reception period, a signal time and frequency resource position, and a transmission / reception period may be controlled for each slice.

For example, as an embodiment of an operation of performing paging through a common slice, it may include at least one of the following operations.

1) When the purpose of call setup is MT call setup through paging or MO call setup by service, paging message transmission and reception can be performed through a common slice.

2) A narrowband channel for paging indication may be set or allocated, and the setting method may use an RRC message transmission or a static configuration from a base station to a plurality of terminals.

For example, as an embodiment of an operation of performing paging through a dedicate slice, it may include at least one of the following operations.

1) When the purpose of call setup is setting MT call through paging or setting MO call for each service, paging message transmission and reception may be performed through a service-only slice, and the embodiment may include the following.

-Service-specific setting of Paging message scheduling cycle (DRX cycle)

 * Example 1. For cells with specific services, use different DRX cycle lengths in the cell

 * Example 2. Terminal adjusts paging monitoring cycle (DRX cycle length) according to main service

  Based on the history of transmission / reception services, terminal subscription information, etc.

  Shorter paging monitoring cycle for services with high access latency requirements (that is, when fast access is required)

  / Access latency Set long paging monitoring cycle for services with low requirements i.e. check for paging less frequently

Service-based control of paging frames (PF) or paging occasions (PO)

 * Introduces offset into PO according to DL access speed requirement for each service

-Division of the control channel (PDCCH) reception period of the terminal for each service

 * In case the main service provided by the terminal requires extended cell coverage (for example, mMTC), the PDCCH reception time can be set longer.

-Generation and transmission of paging message for each service at base station

-PCCH or PCH setting

 Example 1. Introduce scheduling priority / order in PCCH or PCH according to service;

 Example 2: Introduction of Service Information to Scheduling Information for PCH

The UE may select or reselect a cell supporting a specific service and use a paging reception setting used in the cell. Paging reception setting information includes a method of transmitting by the cell as broadcast information (system information).

For example, as an embodiment of an operation of performing cell selection and reselection through a dedicate slice, the following operation may be included.

A terminal or a base station may set a parameter for controlling a cell measurement operation for each service of transmission / reception information. For example, when the main service of the terminal is mMTC, the method may include a method of setting a long signal strength measurement period of the neighboring cell (s), and controlling the number of neighboring cells to be measured. (Or, the number of measurements can be set low.) RRC signal transmission and reception may be used as a means for setting the parameters.

On the other hand, the service-only slice operation when the terminal is connected to the base station (signal transmission and reception to move to the IDLE to CONNECTED state) may include the following example.

For example, an embodiment of an operation of performing random access through a dedicate slice may include at least one of the following operations.

1) When the purpose of call setup is MT call setup through paging or MO call setup by service, random access can be performed through a dedicate slice. The paging signal may include information about a service.

2) The time-frequency location of the PRACH resource can be separated for each service.

3) The number of random access attempts can be separated for each service.

4) Variables for setting random access transmission power (offset, etc.), preamble maximum retransmission number, preamble retransmission time point, etc. can be controlled according to the transmission / reception information service.

5) At this time, the dedicate slice PRACH configuration information may be obtained from the SIB received from the common slice or determine the PRACH resource information according to a predetermined configuration value.

6) The detailed PRACH procedure may then be similar to the operation of the conventional mobile communication system.

For example, an embodiment of an operation of performing an RRC connection setup through a dedicate slice may include at least one of the following operations.

1) When the purpose of call setup is MT call setup through paging or MO call setup by service, RRC and lower layer operation setup (logical channel transmission / reception setup, etc.) can be performed through the dedicate slice. The RRC connection setup message transmission and reception setting may include information about a service.

2) The terminal or the transmission data service information may be delivered as part of the RRC message IE or IE.

3) UE common control channel (CCCH) information may be classified for each service. In case of CCCH information for URLL, scheduling can be prioritized compared to CCCH for mMTC.

Hereinafter, various examples of slice selection / setting and use of the connected terminal will be described.

The terminal connected to the base station may set and control the SRB1 and the DRB for each service and requirement. An embodiment of the present invention may include a method of setting a radio bearer (RB) based on service type information of transmission / reception information. Functions and settings of lower layers such as PDCP, RLC, MAC, and PHY can be set differently for each RB. For example, the terminal may set an RB for each service type of transmission / reception information, and set PDCP and RLC operations corresponding to the RB.

Alternatively, the logical channel transmission / reception used by each of the SRB1 and the DRB may be set for each service and for each requirement. The logical channel may be a terminal specific control channel (DCCH) or a service specific DCCH.

The following is an example of the transmission / reception operation for information / packet generated in the idle or connected state.

The terminal can determine the service and requirements. At this time, one or more requirements can be determined (eg error rate, delay time, transmission speed, etc.). If more than one requirement exists, each of them can be prioritized (e.g., prioritizing latency and error rate requirements for URLL services).

In the case of the terminal in the idle state, the procedure for accessing the base station described above may be performed.

The base station may set up a radio bearer for transmitting and receiving information. In this case, functions of each layer may be dynamically set to meet the requirements. Service information may be included in the RRC Connection Request, and based on this information, the base station may configure service-based RAN configuration information (radio bearer configuration information, logical channel configuration information, PDCP, RLC, MAC, physical layer configuration, etc.) in the RRC Connection Setup. Can be transmitted. Alternatively, the terminal and the base station may select the statically set RB.

The following is an example of a service-only slice operation when transmitting and receiving information of a connected terminal.

An embodiment of an operation of performing a function corresponding to a PDCP and an RLC layer of a control plane and a user plane through a dedicate slice may include at least one of the following.

2) integrity and ciphering, header compression for user plane transmit / receive information, RLC operation mode (ARQ feedback status), RLC ARQ operation (feedback transmission / reception conditions, timing, feedback frequency, etc.), segmentation and concatenation operations to transmit / receive services and requirements Control accordingly.

3) For example, when transmitting and receiving best effort (BE) service information (such as ftp file transfer and e-mail), the wireless connection control function corresponding to the RLC layer may be strengthened and used.

(E.g., when determining BE service information, set the maximum number of RLC PDU retransmissions)

If the level of request for transmission delay time is high, such as URLL, but a low error rate is required, the number of RLC PDU retransmissions can be controlled to a maximum value or less.

An embodiment of an operation of performing a MAC function through a dedicate slice may include at least one of the following.

1) The order, multiplexing size, and transport block size (TBS) of multiplexing for each logical channel can be controlled according to the transmission / reception service type.

2) Logical channel allocation and preference can be given to each service, and the scheduling order can be controlled according to the transmission / reception service type according to the preference.

3) HARQ process allocation for each service: TTI length, feedback timing, feedback order, etc. can be controlled according to the transmission / reception service type.

4) A scheduling request (SR) transmission period, a trigger condition, an SR transmission number, and whether to use an sr-ProhibitTimer can be controlled according to a transmission / reception service type.

5) Storage status report (BSR) It can be controlled according to transmission / reception service type such as transmission cycle, trigger condition, etc.

6) Power headroom report (PHR) It can control transmission cycle, trigger condition, etc. according to transmission / reception service type. Other MAC Control Element (CE) Control transmission period, trigger condition, etc. according to transmission / reception service type. can do.

7) You can control the inactivity timer start and end time, timer length, etc. to start the connected DRX operation according to the transmission / reception service type.

Hereinafter, a method of transmitting transmit / receive information having one or more service types in a connected state will be described.

In the uplink transmission, when a plurality of data packets are waiting to be transmitted in the terminal storage device and one or more service types exist (service types vary for each packet), at least one of the following operations may be performed.

1) RRC signaling RB (Radio Bearer) can be established between the UE and the eNB through the access operation.

2) Service type can be determined when up / down data is generated. It may be determined whether a radio bearer (RB) corresponding to a service is set for each packet.

3) Each service / transmission / reception packet may be allocated (or associated) to different DRBs.

4) Priority can be set for each RB based on requirements for each service / transmission / reception packet and QoS.

5) Multiple RBs can be multiplexed on an RB basis with high requirements.

When information of another service type is generated in a terminal connected to a base station and using a service dedicated slice, at least one of the following operations may be performed.

1) When other service information (transmission and reception information having a lower QoS level than that of the eMBB) occurs in a terminal connected for eMBB information transmission and reception, the base station and the terminal may configure a new RB or use an existing RB configuration. In this case, a criterion for determining whether to set RB may be a service requirement of new generation information or a determination of a degree of waste of radio resources when using an existing RB. For example, the control channel may be used in common, and data transmission channels such as PDSCH and PUSCH may be reconfigured for each service.

2) It is possible to determine whether the requirements of the new occurrence information (error rate, latency, coverage, etc.) are satisfied by the currently established RB configuration.

3) By using the existing RB configuration, it is possible to determine wasted resources (power, time / frequency allocation resources, delay time spent on HARQ / ARQ feedback counts, radio resources, the number of signaling transmissions, etc.).

Hereinafter, various embodiments of a load control method for radio resources when a terminal accesses a base station using a shared slice will be described.

As an embodiment, the service access operation may be controlled by a common RRC message.

The operation of the terminal according to the present embodiment is as follows.

The terminal may assign / set priority for each service type. When uplink information is generated, a service and a requirement may be determined (a delay time, an error rate, etc.) and a random access operation may be set according to the priority of the corresponding service. Determining whether there is information to be transmitted in a buffer of the terminal modem (or determining whether an access operation for transmitting / receiving information of another service type is in progress), and the terminal is already performing or is performing an access operation. In addition, information on all service types requiring transmission and reception may be transmitted together with a base station connection request message (eg RRC connection request).

The operation of the base station according to the present embodiment is as follows.

The base station may determine whether the terminal accesses the network based on the service type information transmitted by the terminal and transmit a response message to the terminal.

According to an embodiment, a DL paging based backoff operation may be included.

If the purpose of call setup is MT Call, access time can be controlled based on the number of paging receiving terminals.

For example, the number of paging terminals may be determined by decoding the paging message received by the terminal, and the terminal may control the time of wireless connection connection based on this information. In addition, the wireless connection connection timing may be controlled according to service requirements. It may include a backoff timer setting proportional to the number of terminals, a random backoff timer setting within a specific range, and the like.

According to an embodiment of the present disclosure, a method for separating and allocating random access resources for each service may be included.

The random access resource may include control of a random access preamble, a location of a PRACH time-frequency resource, a variable for setting a random access transmission power (offset, etc.), a preamble maximum retransmission number, and a preamble retransmission timing. In addition, RACH power scaling may be applied according to service priority.

Meanwhile, an apparatus (terminal, base station, etc.) according to an embodiment of the present invention may include a transceiver for transmitting and receiving a signal and a controller (for example, a processor) for implementing operations according to various embodiments of the present disclosure.

According to various embodiments of the present disclosure, at least some of an apparatus (eg, a unit, modules, or functions thereof) or a method (eg, operations) according to various embodiments of the present disclosure may be read by a computer, for example, in the form of a programming module. It may be implemented by instructions stored in a computer-readable storage media. When the instruction is executed by one or more processors, the one or more processors may perform a function corresponding to the instruction. The computer-readable storage medium may be the storage unit, for example. At least some of the programming modules may be implemented (eg, executed) by, for example, the processor. At least some of the programming modules may include, for example, modules, programs, routines, sets of instructions, or processes for performing one or more functions.

The computer-readable recording medium includes magnetic media such as hard disks, floppy disks, and magnetic tapes, and optical recording media such as compact disc read only memory (CD-ROM) and digital versatile disc (DVD). Media, magneto-optical media, such as floppy disks, and program instructions such as read only memory, random access memory, flash memory, Hardware device specifically configured to store and perform modules). The program instructions may also include high-level language code that can be executed by a computer using an interpreter as well as machine code such as produced by a compiler. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the various embodiments of the present invention, and vice versa.

Modules or programming modules according to various embodiments of the present disclosure may include at least one or more of the aforementioned components, omit some of them, or further include additional components. Operations performed by a module, programming module, or other component according to various embodiments of the present disclosure may be executed in a sequential, parallel, repetitive, or heuristic manner. In addition, some operations may be executed in a different order, may be omitted, or other operations may be added.

And the embodiments of the present invention disclosed in the specification and drawings are merely to illustrate the technical contents of according to the embodiments of the present invention and to show specific examples to help the understanding of the embodiments of the present invention, the scope of the embodiments of the present invention It is not intended to be limiting. Therefore, the scope of various embodiments of the present invention should be construed that all changes or modifications derived based on the technical spirit of the various embodiments of the present invention in addition to the embodiments disclosed herein are included in the scope of various embodiments of the present invention.

Claims (6)

A method of using resources of an electronic device in a wireless mobile communication system, Setting a dedicated wireless access configuration for each service; Detecting a first service request; And And transmitting and receiving a signal using a dedicated radio access configuration corresponding to the first service based on the setting. The method of claim 1, The dedicated wireless access configuration for each service may be configured such that at least one of time or frequency resources is divided. The method of claim 1, And receiving information related to the dedicated radio access configuration setting for each service from a base station. An electronic device in a wireless mobile communication system, Transmitting and receiving unit for transmitting and receiving a signal; And An electronic device including a control unit configured to set a dedicated radio access configuration for each service, detect a first service request, and transmit and receive a signal using a dedicated radio access configuration corresponding to the first service based on the setting. . The method of claim 4, wherein The dedicated wireless access configuration for each service may be configured to have an area in which at least one of time or frequency resources is divided. The method of claim 4, wherein The control unit, And controlling to receive information related to a dedicated radio access configuration setting for each service from a base station.

Images