[go: up one dir, main page]

WO2017196119A1 - Procédé et dispositif d'utilisation de ressources dans un système de communication mobile sans fil - Google Patents

Procédé et dispositif d'utilisation de ressources dans un système de communication mobile sans fil Download PDF

Info

Publication number
WO2017196119A1
WO2017196119A1 PCT/KR2017/004933 KR2017004933W WO2017196119A1 WO 2017196119 A1 WO2017196119 A1 WO 2017196119A1 KR 2017004933 W KR2017004933 W KR 2017004933W WO 2017196119 A1 WO2017196119 A1 WO 2017196119A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
slice
information
terminal
base station
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2017/004933
Other languages
English (en)
Korean (ko)
Inventor
류선희
황지원
정정수
안라연
이성진
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020160064258A external-priority patent/KR102669843B1/ko
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to US16/301,417 priority Critical patent/US11570696B2/en
Publication of WO2017196119A1 publication Critical patent/WO2017196119A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the use of radio resources in a wireless mobile communication system.
  • 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).
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • mmWave ultra-high frequency
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
  • 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.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • ENB base station
  • MAC Medium Access Control
  • 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.
  • 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)
  • SRB signaling radio bearer
  • DRB data radio bearer
  • 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.
  • QoS requirements such as BE, eMBB, URLLC, mMTC, VoIP, etc.
  • 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).
  • new services and requirements eg, delay-tolerant, small data transmission for machine-type communication, MTC.
  • 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).
  • RAN Radio Access Network
  • a method of using a resource of an electronic device in a wireless mobile communication system 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 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.
  • 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.
  • FIG. 1 is a diagram illustrating an RAN hierarchy option according to an embodiment of the present invention.
  • FIGS. 2A to 2D are diagrams illustrating various examples of a physical hierarchy structure according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 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.
  • FIG. 5 is a flowchart illustrating a dedicated RAN setup and use according to an embodiment of the present invention.
  • FIG. 6 is a flowchart illustrating an example of transmitting and receiving physical layer configuration information according to an embodiment of the present invention.
  • FIG. 7 is a view for explaining an example of transmitting and receiving physical layer configuration information according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating another example of receiving physical layer configuration information according to an embodiment of the present invention.
  • FIG. 9 is a flowchart illustrating an example of system information transmission and reception according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 12 is a flowchart for explaining another example of system information transmission and reception according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 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.
  • 19B is a diagram illustrating a connection according to a PRACH setting for each service according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 22 is an exemplary diagram of RAN configuration for each service according to an embodiment of the present invention.
  • 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.
  • 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.
  • the expression “or” includes any and all combinations of words listed together.
  • “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.
  • 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.
  • both a first user device and a second user device are user devices and represent different user devices.
  • 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.
  • a 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.
  • RAN slices partitions, or configurations.
  • the subject constituting the RAN slice may be a base station, a network, or a terminal.
  • 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.
  • MAC protocol layer
  • RLC Radio Link Control
  • PDCP Packet Control Protocol
  • RRC radio access technology
  • various embodiments of the present disclosure relate to an operation in which a terminal applies and configures and operates a RAN slice.
  • 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.
  • a broadcast signal cell search / synchronization (PSS / SSS), SI acquisition, etc.
  • FIG. 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.
  • the RAN slice may be configured with one or more combinations of physical time and frequency resources for exchanging the.
  • 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.
  • each service may be statically set as needed.
  • 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).
  • 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.
  • 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.
  • each slice 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.).
  • a numerology per service eg, subcarrier spacing, bandwidth, etc.
  • time domain In the time domain, it may be defined as a physical channel setting for each service.
  • 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.
  • it may be a time-frequency resource with shared / single numerology or numerology (subcarrier spacing, bandwidth, etc.) that is different for each service.
  • numerology subcarrier spacing, bandwidth, etc.
  • 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.
  • numerology subcarrier spacing, bandwidth, etc.
  • 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.
  • it may be a time-frequency resource with shared / single numerology or numerology (subcarrier spacing, bandwidth, etc.) that is different for each service.
  • numerology subcarrier spacing, bandwidth, etc.
  • 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.
  • numerology subcarrier spacing, bandwidth, etc.
  • 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.
  • each signal may use a fixed position in time / frequency space, or set a transmission position of each signal for each service.
  • 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.
  • different numerology 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.
  • the MAC layer slice may be defined by some or all of the functions performed by the MAC, including the examples described below.
  • the number of processes e.g., in case of mMTC is set to use a small number of processes
  • the number of retransmissions ACK / NACK information, feedback timing, etc.
  • 2) de Multiplexing and (dis) assembly can be considered.
  • 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).
  • IE logical channel configuration information element
  • the MAC layer slice may be defined by some or all of the functions performed by the RRC layer including the examples described below.
  • 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.
  • 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.
  • 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.
  • 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.
  • SRB signaling radio bearer
  • 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.
  • 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.
  • a radio interface protocol PHY, MAC, RLC, PDCP, RRC layer
  • TBS transport block size
  • MIB-eMBB MIB-URLLC
  • MIB-mMTC MIB-mMTC
  • SIBx-eMBB SIBx-URLLC
  • SIBx-mMTC SIBx-mMTC
  • Service setting such as broadcast information transmission cycle and update cycle
  • Different unlicensed band transmission and reception by service (bearer, UE capability, packet traffic class).
  • 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)
  • LBT content-before-talk
  • the manner of setting the RAN 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).
  • a method of determining, by the terminal, a service type to be provided by the information may include the following.
  • a method of determining, by the terminal / base station, a service type to be provided by the information may include the following.
  • the terminal or the base station may include the following method.
  • 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.
  • 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
  • RRC message 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
  • 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.
  • 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.
  • 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)
  • 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.
  • 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.
  • 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 4 below shows a common slice application or a dedicated slice application option for each signal transmitted and received in the connected state.
  • 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.
  • 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.
  • 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.
  • setting information examples 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.
  • 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.
  • 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.
  • Step 1 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.
  • service preference information priority / preference
  • 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.
  • 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.
  • Characteristic is that the service type information of the data can be sent from the base station and the network.
  • Step 1-2 Else if service mode / preference is known (or if the device's service type is specified, e.g. mMTC type device)
  • 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.
  • FIG. 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.
  • a synchronization signal transmission position is fixed in frequency and time space.
  • 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.
  • 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.
  • 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.
  • 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.
  • RRC connection setup and RRC reconfiguration may be performed through a common slice.
  • the paging signal may include information about a service.
  • RRC information transmission and reception may be performed through a common slice.
  • 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.
  • 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.
  • a service dedicated slice may be applied.
  • Table 6 below shows another example of slice configuration for each signal.
  • FIG. 5 is a flowchart illustrating a dedicated RAN setup and use according to an embodiment of the present invention.
  • 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.
  • 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). .
  • 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.
  • information eg, symbol / subframe / frame structure in which a signal is transmitted
  • the terminal may acquire information on the physical channel configuration after synchronization with a specific cell.
  • information on a physical channel configuration may be delivered (defined as a common slice) at a fixed resource location.
  • a physical channel setting transmission position may be fixed in a frequency and time space.
  • PHY configuration information may be delivered as system information (SI) using fixed scheduling of MIB (and SIB).
  • SI system information
  • 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.
  • the terminal may receive an SI transmitted by the base station after synchronizing a signal using a shared or dedicated slice configuration.
  • a base station and a terminal may transmit and receive MIB and SIB at a fixed resource location at all times.
  • the base station may transmit to the terminal by applying different SI-related settings for each service in various ways.
  • the service-only slicing method may include the following.
  • the base station may transmit different contents to the MIB and / or SIB for each service.
  • the DL-bandwidth value of the MIB sent by the base station may be differently designated for each service and transmitted.
  • DL_bandwidth B_URLL is set and its value can be set differently from other services.
  • 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.
  • dedicated scheduling period, receive duration, location in frame / sub-frame, etc.
  • 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.
  • dedicated scheduling period, SI transmission / reception window length, receive duration, location in frame / sub-frame, etc.
  • SIB Service-oriented UEs with battery life or latency critical settings should be able to receive the minimum required SIB at the minimum time.
  • the base station may transmit the MIB contents as a BCCH-BCH message in the protocol and transmit the message on the PBCH channel.
  • the UE may repeatedly receive the PBCH several times.
  • the UE may control the number of repetition receptions according to the coverage and signal strength of the UE.
  • the base station may transmit to the terminal by applying different SI-related settings for each service.
  • 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
  • FIG. 14 shows an example of a MAC configuration slicing protocol for reducing SI overhead.
  • the base station may deliver a PHY / MAC slice configuration to be used by the terminal in idle to the terminal in RRC signaling.
  • the SI information acquisition method of the terminal may include a combination of the various proposals.
  • initial connection eg, transition from idle to connected
  • paging e.g., paging
  • UL RACH operation using the sliced RAN structure
  • a method of performing wireless access and connection establishment in a common RAN slice is as follows.
  • 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.
  • 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.
  • P-RNTI UE-specific PO
  • all terminals can use a common PRACH location in time and frequency regardless of service in the PHY.
  • all terminals and services may use the same RACH procedure / configuration.
  • a method of performing wireless access to a shared slice in downlink (for paging) and a dedicated slice in uplink (RACH) is as follows.
  • RRC based operation may be performed.
  • 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.
  • 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.
  • 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.
  • the terminal may access the network with one or more service capability (and corresponding priority level) information.
  • the terminal may mainly use the eMBB service
  • a dedicated RACH configuration per slice is used, and the PHY configures different PRACH resources in the frequency and time domains for each service.
  • the PHY configures different PRACH resources in the frequency and time domains for each service.
  • 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.
  • a terminal may be delayed when different services (VoIP and mMTC) occur in a common space.
  • 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.
  • 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.
  • 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.
  • the base station may receive paging from the MME and calculate the next P0 based on the information paging to the terminal.
  • 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
  • FIG. 19B shows a connection of a terminal in case of PRACH setting for each service.
  • a downlink access operation and an uplink access operation may be performed using the service dedicated slice and related operations.
  • 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.
  • the service and the requirements provided by the transmission and reception information generated in the terminal or the base station can be determined.
  • 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.
  • 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.
  • a handover control signal signal (signalling) number of transmission and reception
  • the number of cells for which the terminal measures signal strength 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.
  • information may be transmitted and received by applying the slice setting.
  • the specific operation of the terminal may be as follows.
  • 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.
  • 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.
  • 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.
  • the value of the set variable is characterized in that it can use a value optimized for each service and its requirements.
  • the terminal may provide service information to the base station.
  • the service information may be service preference information provided by the terminal upon initial attach.
  • service information may be transmitted to the base station when accessed from idle.
  • 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.).
  • RRC Connection Request e.g. RRC Connection Request, Connection Setup Complete, etc.
  • 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.
  • the RAN slice may be set by service-specific control of an inactivity timer.
  • 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.
  • the control channel eg, PDCCH
  • 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.
  • 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.
  • 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.
  • 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.
  • QoS is a service requirement including data rate, latency, mobility, reliability, power consumption, and connection density.
  • RLC unacknowledged mode e.g. sensor
  • 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
  • MME holds UE Context information even in RRC idle 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.
  • 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.
  • 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.
  • FIG. 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.
  • the terminal and the base station may operate by selecting a slice suitable for a specific situation.
  • 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.
  • 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.)
  • 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.
  • 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.
  • Step 1 Using the common slice between the terminal and the base station, perform the following operation.
  • 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.
  • 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.
  • 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)
  • 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.
  • Operation examples described below may be performed first using a common slice when the terminal initially accesses the network.
  • Network registration is done using a common configuration and on-demand configuration based on subsequent service types.
  • the RRC connection setup message can be received.
  • 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
  • uplink configuration and downlink configuration may be different.
  • SRB can be established and entered into the connected state.
  • RRC signaling can be transmitted and received (e.g. authentication and security configuration related messages).
  • the service type of the corresponding data may be determined.
  • 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.
  • the operation is characterized in that to perform the RRC connection reset operation only when the transmission and reception data occurs.
  • 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.
  • 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.
  • the terminal may select and use a dedicated slice for the corresponding service to perform transmission / reception with the base station.
  • 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.
  • 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.
  • the service type information may be included in the paging message.
  • '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.
  • 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.
  • 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.
  • Step 1 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.).
  • RRC message eg, RRC Release, Suspend, Reconfiguration, etc.
  • Step 2 The IDLE operation is performed according to the slice information received by the terminal.
  • the slice may be a public or service only slice.
  • 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.
  • the common slice operation and the service dedicated operation of the terminal in the IDLE state may include the following examples.
  • an operation of performing synchronization through a dedicated slice it may include at least one of the following operations.
  • the synchronization signal transmission and reception may be different for each slice.
  • a synchronization signal transmission / reception period, a signal time and frequency resource position, and a transmission / reception period may be controlled for each slice.
  • an operation of performing paging through a common slice it may include at least one of the following operations.
  • 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.
  • an operation of performing paging through a dedicate slice it may include at least one of the following operations.
  • paging message transmission and reception may be performed through a service-only slice, and the embodiment may include the following.
  • Terminal adjusts paging monitoring cycle (DRX cycle length) according to main service
  • Shorter paging monitoring cycle for services with high access latency requirements that is, when fast access is required
  • the PDCCH reception time can be set longer.
  • Example 1 Introduce scheduling priority / order in PCCH or PCH according to service
  • 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).
  • 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.
  • 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.
  • the service-only slice operation when the terminal is connected to the base station may include the following example.
  • an embodiment of an operation of performing random access through a dedicate slice may include at least one of the following operations.
  • the paging signal may include information about a service.
  • the time-frequency location of the PRACH resource can be separated for each service.
  • 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.
  • 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.
  • the detailed PRACH procedure may then be similar to the operation of the conventional mobile communication system.
  • an embodiment of an operation of performing an RRC connection setup through a dedicate slice may include at least one of the following operations.
  • 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.
  • the terminal or the transmission data service information may be delivered as part of the RRC message IE or IE.
  • UE common control channel (CCCH) information may be classified for each service.
  • CCCH information for URLL scheduling can be prioritized compared to CCCH for mMTC.
  • 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.
  • the terminal may set an RB for each service type of transmission / reception information, and set PDCP and RLC operations corresponding to the RB.
  • 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).
  • 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).
  • 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.
  • 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.
  • 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.
  • the wireless connection control function corresponding to the RLC layer may be strengthened and used.
  • 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.
  • 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.
  • 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.
  • TTI length, feedback timing, feedback order, etc. can be controlled according to the transmission / reception service type.
  • 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.
  • Storage status report It can be controlled according to transmission / reception service type such as transmission cycle, trigger condition, etc.
  • Power headroom report It can control transmission cycle, trigger condition, etc. according to transmission / reception service type.
  • 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.
  • RRC signaling RB Radio Bearer
  • 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.
  • RB radio bearer
  • Each service / transmission / reception packet may be allocated (or associated) to different DRBs.
  • Priority can be set for each RB based on requirements for each service / transmission / reception packet and QoS.
  • Multiple RBs can be multiplexed on an RB basis with high requirements.
  • the base station and the terminal may configure a new RB or use an existing RB configuration.
  • 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.
  • the control channel may be used in common, and data transmission channels such as PDSCH and PUSCH may be reconfigured for each service.
  • 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.
  • 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.
  • 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.
  • a DL paging based backoff operation may be included.
  • access time can be controlled based on the number of paging receiving terminals.
  • 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.
  • 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.
  • 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.
  • RACH power scaling may be applied according to service priority.
  • an apparatus 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.
  • a controller for example, a processor
  • an apparatus eg, a unit, modules, or functions thereof
  • a method eg, operations
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de communication 5G ou pré-5G destiné à prendre en charge un taux de transmission de données plus élevé qu'un système de communication au-delà de la 4G tel que le réseau LTE. Un procédé d'utilisation de ressources par un dispositif électronique dans un système de communication mobile sans fil peut comprendre les étapes consistant à : définir une configuration d'accès sans fil dédiée pour chaque service ; détecter une première demande de service ; et, sur la base de la définition, transmettre et recevoir un signal au moyen d'une configuration d'accès sans fil dédiée correspondant au premier service. La présente invention ne se limite pas au mode de réalisation précité et peut comprendre plusieurs autres modes de réalisation.
PCT/KR2017/004933 2016-05-13 2017-05-12 Procédé et dispositif d'utilisation de ressources dans un système de communication mobile sans fil Ceased WO2017196119A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/301,417 US11570696B2 (en) 2016-05-13 2017-05-12 Method and device for using resources in wireless mobile communication system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20160059117 2016-05-13
KR10-2016-0059117 2016-05-13
KR10-2016-0064258 2016-05-25
KR1020160064258A KR102669843B1 (ko) 2016-05-13 2016-05-25 무선 이동통신 시스템에서 자원 이용 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2017196119A1 true WO2017196119A1 (fr) 2017-11-16

Family

ID=60267171

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/004933 Ceased WO2017196119A1 (fr) 2016-05-13 2017-05-12 Procédé et dispositif d'utilisation de ressources dans un système de communication mobile sans fil

Country Status (1)

Country Link
WO (1) WO2017196119A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019105095A1 (fr) * 2017-11-28 2019-06-06 中国移动通信有限公司研究院 Procédé de traitement de tranche de réseau et élément de réseau d'accès
CN113038604A (zh) * 2019-12-24 2021-06-25 中国电信股份有限公司 无线资源配置方法、装置和系统、基站

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130072252A1 (en) * 2011-09-20 2013-03-21 Htc Corporation Wireless device and wireless connection method thereof
WO2015127833A1 (fr) * 2014-02-26 2015-09-03 Tencent Technology (Shenzhen) Company Limited Procédé et système pour faciliter l'accès à un réseau sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130072252A1 (en) * 2011-09-20 2013-03-21 Htc Corporation Wireless device and wireless connection method thereof
WO2015127833A1 (fr) * 2014-02-26 2015-09-03 Tencent Technology (Shenzhen) Company Limited Procédé et système pour faciliter l'accès à un réseau sans fil

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP; TSGSSA; Study on Architecture for Next Generation System (Release 14)", 3GPP TR 23.799 V0.4.0, 27 April 2016 (2016-04-27), XP055599751 *
BALAZS BERTENYI: "Summary of ''[5G-AH-05] RAN-Core connectivity, Virtualization & Network Slicing", RP-160251, 3GPP TSG RAN #71, 21 March 2016 (2016-03-21), Gothenburg, Sweden, XP051076209 *
QIAN (CLARA) LI ET AL.: "End-to-End Network Slicing in 5G Wireless Communication Systems", ETSI WORKSHOP ON FUTURE RADIO TECHNOLOGIES - AIR INTERFACES, 28 January 2016 (2016-01-28), XP055395445, Retrieved from the Internet <URL:https://docbox.etsi.org/Workshop/2016/201601_FUTURERADIOTECHNOW_WORKSHOP/S06_ADVANCED_TOPIC_FUTURE_AIR_INTERFACES/END2END_NWK_SLICING_5G_LIRELESS_COMM_SYSTEMS_paper.pdf> *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019105095A1 (fr) * 2017-11-28 2019-06-06 中国移动通信有限公司研究院 Procédé de traitement de tranche de réseau et élément de réseau d'accès
CN113038604A (zh) * 2019-12-24 2021-06-25 中国电信股份有限公司 无线资源配置方法、装置和系统、基站
CN113038604B (zh) * 2019-12-24 2023-03-21 中国电信股份有限公司 无线资源配置方法、装置和系统、基站

Similar Documents

Publication Publication Date Title
WO2023014064A1 (fr) Procédé et appareil de mesure et de rapport de signal d&#39;interférence dans des systèmes de communication sans fil
WO2021010786A1 (fr) Procédé et dispositif de communication d&#39;informations, procédé et dispositif de réception d&#39;un message
WO2019216617A1 (fr) Procédé et appareil pour déclencher une sélection de porteuse de transmission dans un système de communications sans fil
WO2021010759A1 (fr) Procédé et appareil pour l&#39;exploitation efficace de la partie dormante d&#39;une largeur de bande dans un système de communication mobile de nouvelle génération
WO2020055102A1 (fr) Système et procédé d&#39;émission et de réception d&#39;informations de radiomessagerie et de système
WO2016144055A1 (fr) Procédé et appareil pour réaliser et relever des mesures à l&#39;aide d&#39;équipement utilisateur configuré par des porteuses multiples dans des systèmes de communication mobile
WO2019240512A1 (fr) Procédé et système de communication sans fil permettant de gérer un fonctionnement d&#39;une minuterie
WO2022035281A1 (fr) Procédé et appareil d&#39;activation et de réactivation de scell prenant en considération la partie de bande passante actuellement activée et les des informations de configuration de partie de bande passante dans un système de communication mobile de prochaine génération
WO2018016921A1 (fr) Procédés destinés à la transmission et à la réception d&#39;informations de commande de liaison descendante entre station de base et terminal dans un système de communication sans fil, et dispositifs destinés à prendre en charge lesdits procédés
WO2020091452A1 (fr) Procédé et appareil de mise en œuvre de communication dans un système de communication mobile
WO2020166957A1 (fr) Procédé et appareil pour la communication v2x dans un système de communication mobile de prochaine génération
WO2018062957A1 (fr) Procédé et appareil de transmission de données dans un état désactivé ou désactivé rrc
EP3777312A1 (fr) Système et procédé d&#39;émission et de réception d&#39;informations de radiomessagerie et de système
WO2014098534A1 (fr) Appareil et procédé d&#39;émission et de réception dans un système de communication mobile
WO2022146082A1 (fr) Procédé et appareil pour déterminer un temps de traitement d&#39;un ue dans un système de communication sans fil
WO2021261877A1 (fr) Procédé et dispositif d&#39;émission et de réception d&#39;un signal dans un système de communication sans fil
WO2018194239A1 (fr) Appareil et procédé d&#39;émission et de réception d&#39;un signal de réveil dans un système de communication sans fil
WO2017159886A1 (fr) Procédé de transmission de données de liaison montante dans un système de communication sans fil et appareil associé
WO2015020356A1 (fr) Procédé de transmission d&#39;un rapport d&#39;état de tampon dans une communication entre dispositifs et dispositif associé
WO2019132501A1 (fr) Procédé d&#39;accès à un réseau dans un système de communication sans fil, et appareil correspondant
WO2023101492A1 (fr) Procédé et appareil pour générer un ce mac pour une récupération de défaillance de faisceau dans un système de communication sans fil
WO2023055185A1 (fr) Procédé et dispositif pour la transmission/réception d&#39;un pdsch commun de groupe dans un système de communication sans fil
WO2022139512A1 (fr) Procédé et appareil d&#39;émission et de réception de radiorecherche
WO2023140626A1 (fr) Procédé et dispositif de fourniture d&#39;informations de capacité de terminal sur des intervalles simultanés dans un système de communication mobile sans fil
WO2017196119A1 (fr) Procédé et dispositif d&#39;utilisation de ressources dans un système de communication mobile sans fil

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17796419

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17796419

Country of ref document: EP

Kind code of ref document: A1