Transmission apparatus and method for radio access network slice related information

Abstract

This specification relates to an apparatus and method for transmitting RAN slice-related information, disclosing a terminal comprising: a transceiver unit that receives individual control information provided separately for each RAN slice from a network node, and executes a random access procedure using resources constructed separately for each RAN slice based on the individual control information; and a processor that receives the individual control information and controls the random access procedure. The terminal has the following technical advantages: it can transmit control information including system information separately according to different slices, for example, thereby realizing RAN slicing.

Description

Technical Field

[0001] This invention relates to a wireless communication system, and more specifically, to a device and method for transmitting RAN slice-related information. Background Technology

[0002] In 3GPP, Release (Rel)-15 completed the first international 5G NR (New Radio) standard, paving the way for the commercial application of 5G. 5G NR is a radio access technology that can provide data transmission rates higher than LTE E-UTRA (Evolved UMTS Terrestrial Radio Access), meeting various QoS requirements based on specific usage scenarios. In particular, eMBB (enhancement Mobile Broadband), mMTC (massive Machine-Type Communications), and URLLC (Ultra Reliable and Low Latency Communications) have been defined as representative 5G usage scenarios. The provided numerical approach is more flexible than LTE, allowing it to meet the requirements of various scenarios.

[0003] Meanwhile, network slicing technology is being considered. Network slicing is a new concept that can be applied to 5G mobile communications. It can create and provide an independent slice of end-to-end resources from the Radio Access Network (RAN) to the Core Network (CN) based on the different services provided by network resources and network functions. This allows attributes such as network isolation, customization, and independent management and orchestration to be applied to the Radio Access Network (RAN) and Core Network of mobile communications.

[0004] The integration of communication technologies with technologies such as Network Function Virtualization (NFV) and Software Defined Networking (SDN) is evolving towards the formation of network slices. These network slices are optimized within a vast network based on the characteristics of various applications.

[0005] Network slicing physically creates logically separated end-to-end (E2E) networks, including user terminals, wireless access, transmission ports, and 5G core equipment. Through this slicing, a personalized dedicated network is provided for various services with different characteristics and QoS (Quality of Service). In other words, network slicing is a technology that creates a separate slice of the network resources and functions required by a terminal's requested service. Summary of the Invention

[0006] The problem to be solved

[0007] The technical problem of this invention is to provide an apparatus and method for transmitting RAN slice-related information. In 5G mobile communication, to effectively support multiple services—that is, to support multiple services through a single system without requiring separate systems for different services—dynamic resource control through slicing is necessary. However, RAN slicing is more challenging than core network slicing. Conceptually, RAN slicing should allow each slice to operate like an independent unit, isolating and allowing each slice to function independently, so that even if one slice experiences a malfunction, it will not affect other slices. Therefore, a scheme for transmitting information for each RAN slice separately is needed.

[0008] Technical solution

[0009] To achieve the above objectives, in one embodiment of the present invention, a terminal operating a communication system that supports RAN (Radio Access Network) slice information may include: a transceiver unit that, upon receiving individual control information provided separately to each RAN slice from a network node, executes a random access procedure using the individual control information and resources individually configured for each RAN slice; and a processor that receives the individual control information and controls the random access procedure.

[0010] The individual control information is system information, which includes at least one of first control information for a first type of slice and second control information for a second type of slice. The processor controls the random access procedure in the first type of slice based on the first control information and controls the random access procedure in the second type of slice based on the second control information.

[0011] The first control information and the second control information may each include at least one of the following: random access parameter information, random access resource information, initial bandwidth information, TDD (Time Division Duplex) configuration information, frequency slice resource information, time slice resource information, CORESET 0 (Control Resource Set 0), search space, basic SCS (SubCarrier Spacing) of each slice, BWP (BandWidth Part), Service Unit SIBs (System Information Blocks), and RACH (Random Access Channel) information.

[0012] The system information may further include an information value that indicates whether the network node supports RAN slicing.

[0013] The first control information and the second control information have different building elements, or at least one of their building element values ​​is different.

[0014] The system information further includes the identification information of each slice. The processor extracts the first control information based on the first identification code corresponding to the first type of slice and extracts the second control information based on the second identification code corresponding to the second type of slice.

[0015] The system information includes reception control information, which controls the reception of at least one of the first control information and the second control information. The processor can control the reception of at least one of the first control information and the second control information based on the reception control information.

[0016] The receiving control information includes first receiving control information corresponding to the first type of slice and second receiving control information corresponding to the second type of slice.

[0017] The receive control information may include at least one of the following: the location information of the first DM-RS (DeModulation Reference Signal) symbol in the frequency or spatial domain, SIB1 numerology information, SIB1 scheduling CORESET related information, search space information, and PDCCH (Physical Downlink Control Channel) related parameter information.

[0018] When the first control information cannot be used to control communication in the first type of slice, or when the second control information cannot be used to control communication in the second type of slice, the processor can control communication based on default control information and default built resources.

[0019] To achieve the above objectives, in one embodiment of the present invention, a network node operating in a communication system supporting RAN (Radio Access Network) slice information may include: a transceiver unit that sends individual control information provided separately for each RAN slice to a terminal, and provides a random access procedure using resources constructed separately for each RAN slice based on the individual control information; and a processor that receives and sends the individual control information and controls the random access procedure.

[0020] The individual control information is system information, which includes at least one of first control information for a first type of slice and second control information for a second type of slice. The processor controls the random access procedure in the first type of slice based on the first control information and controls the random access procedure in the second type of slice based on the second control information.

[0021] The first control information and the second control information may each include at least one of the following: random access parameter information, random access resource information, initial bandwidth information, TDD (Time Division Duplex) configuration information, frequency slice resource information, time slice resource information, CORESET 0 (Control Resource Set 0), search space, basic SCS (SubCarrier Spacing) of each slice, BWP (BandWidth Part), Service Unit SIBs (System Information Blocks), and RACH (Random Access Channel) information.

[0022] The first control information and the second control information have different building elements, or at least one of their building element values ​​is different.

[0023] The system information further includes identification information for each slice. The processor can include first control information in the system information based on a first identification code corresponding to the first type of slice, and include second control information in the system information based on a second identification code corresponding to the second type of slice.

[0024] The system information includes reception control information, which controls the reception of at least one of the first control information and the second control information.

[0025] The receiving control information includes first receiving control information corresponding to the first type of slice and second receiving control information corresponding to the second type of slice.

[0026] The receive control information may include at least one of the following: the location information of the first DM-RS symbol in the frequency or spatial domain, SIB1 numerology information, SIB1 scheduling CORESET related information, search space information, and PDCCH related parameter information.

[0027] When the terminal needs to handover to another network node, the processor generates handover information to be sent to the terminal; when the other network node supports RAN slice-based communication, it includes at least one of the first handover information of the first type of slice and the second handover information of the second type of slice in the handover information; when the other network node does not support RAN slice-based communication, it includes the basic handover information of the other network node in the handover information; the transceiver unit can send the handover information to the terminal.

[0028] To achieve the above objectives, in a communication system supporting RAN (Radio Access Network) slice information according to one aspect of the present invention, the method for implementing communication through a terminal can be as follows.

[0029] include:

[0030] The steps of receiving individual control information provided separately to each RAN from network nodes; and

[0031] Based on the individual control information, and utilizing the resources individually constructed for each RAN slice, the steps of the random access procedure are executed.

[0032] The individual control information is system information, which includes at least one of first control information and second control information.

[0033] The random access process in the first type of slice is controlled based on the first control information, and the random access process in the second type of slice is controlled based on the second control information.

[0034] Invention Effects

[0035] The apparatus and method of the present invention have the following technical effects: RAN slicing is achieved by separating control information, including system information, for transmission according to different slices, for example. On the one hand, it has the following technical effects: It can assign inherent IDs to different slices (e.g., including eMBB, URLLC, V2X slices, etc.), and divide different services or slices according to each slice ID. For example, when transmitting system information allocated according to different slices, information can be transmitted based on the slice ID. Attached Figure Description

[0036] Figure 1 This is a conceptual diagram of a wireless communication system according to an embodiment of the present invention.

[0037] Figure 2 This is a schematic diagram of an NR system to which the data transmission method of one embodiment of the present invention can be applied.

[0038] Figure 3 A resource grid supported by the wireless access technology applicable to this embodiment is shown.

[0039] Figure 4 The partial bandwidth (BWP) supported by the wireless access technology applicable to this embodiment is shown.

[0040] Figure 5 An example is shown of a synchronization signal block (SSB) in a wireless access technology applicable to this embodiment.

[0041] Figure 6 The random access procedure in the wireless access technology applicable to this embodiment is illustrated.

[0042] Figure 7 A network slicing concept according to one embodiment is illustrated.

[0043] Figure 8 The terminal and network node implemented in an embodiment of the present invention are shown. Detailed Implementation

[0044] This invention can be modified in many ways and has many embodiments. Specific embodiments are illustrated below with reference to the accompanying drawings and described in detail in the specific description. However, this does not limit the invention to specific embodiments, but should be understood as including all modifications, equivalents, and even substitutions falling within the spirit and technical scope of this invention. In the various drawings, similar reference numerals are used for similar building elements.

[0045] In this specification, terms such as "first," "second," "A," and "B" can be used to describe various building elements, but the building elements should not be limited by these terms. These terms are only used to distinguish one building element from other constituent components. For example, without departing from the scope of this invention, a first building element can be referred to as a second building element, and similarly, a second building element can be referred to as a first building element. Furthermore, the term "and / or" includes a combination of multiple related entries or any one of multiple related entries.

[0046] When a construction element is mentioned as being "connected" or "accessed" to other construction elements, it should be understood that it can be directly connected or accessed to the other construction elements, but there may also be other construction elements in between. Conversely, when a construction element is mentioned as being "directly connected" or "directly accessed" to other construction elements, it should be understood that there are no other construction elements in between.

[0047] The terminology used in this specification is for describing specific embodiments only and is not intended to limit the invention. Unless the context clearly indicates otherwise, singular expressions include plural expressions. It should be understood that terms such as "comprising" or "having" in this specification are used to indicate the presence of features, numbers, steps, actions, building elements, components, or combinations thereof described in the specification, and do not preclude the possibility of the presence or addition of one or more other features, numbers, steps, actions, building elements, components, or combinations thereof.

[0048] Unless otherwise defined, the terminology used in this specification includes technical or scientific terms and has the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should be interpreted that terms equivalent to those defined in a general dictionary have the same meaning as they have in related technical articles. Unless expressly defined herein, terms are not to be interpreted in an idealized or overly formal sense.

[0049] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0050] Figure 1 This is a conceptual diagram of a wireless communication system according to an embodiment of the present invention.

[0051] refer to Figure 1 It can be seen that the wireless communication system 100 can be composed of multiple communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6.

[0052] Multiple communication nodes can each support at least one communication protocol. For example, multiple communication nodes can each support communication protocols based on CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), OFDM (Orthogonal Frequency Division Multiplexing), OFDMA (Orthogonal Frequency Division Multiple Access), SC (Single Carrier)-FDMA, NOMA (Non-Orthogonal Multiple Access), SDMA (Space Division Multiple Access), etc.

[0053] The wireless communication system 100 may include multiple base stations 110-1, 110-2, 110-3, 120-1, 120-2 and multiple user equipments 130-1, 130-2, 130-3, 130-4, 130-5, 130-6.

[0054] Base station 110-1, base station 110-2, and base station 110-3 can each form a macrocell. Base station 120-1 and base station 120-2 can each form a small cell. Base station 120-1, terminal 130-3, and terminal 130-4 are within the coverage area of ​​base station 110-1. Terminal 130-2, terminal 130-4, and terminal 130-5 are within the coverage area of ​​base station 110-2. Base station 120-2, terminal 130-4, terminal 130-5, and terminal 130-6 are within the coverage area of ​​base station 110-3. Terminal 130-1 is within the coverage area of ​​base station 120-1. Terminal 130-6 is within the coverage area of ​​base station 120-2.

[0055] Among them, multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can be referred to as Node B, Evolved Node B, Next Generation Node B (gNB), BTS (Base Transceiver Station), Radio Base Station, Radio Transceiver, Access Point, Node, Roadside Unit (RSU), Digital Unit (DU), Cloud Digital Unit (CDU), Radio Remote Head (RRH), Radio Unit (RU), Transmission Point (TP), Transmission and Reception Point (TRP), Relay Node, etc. Multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 can be referred to as terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, etc.

[0056] Multiple communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 can support cellular communication (e.g., LTE (long-term evolution), LTE-A (advanced), and NR (New Radio) as specified in the 3GPP (3rd Generation Partnership Project) standard). Multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can operate in different frequency bands or in the same frequency band. Base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can be connected via ideal backhaul or non-ideal backhaul, respectively, and can exchange information with each other via either ideal or non-ideal backhaul. Multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can be connected to the core network (not shown) via either ideal or non-ideal backhaul. Multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can respectively transmit signals received from the core network to terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6, and can also transmit signals received from terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 to the core network.

[0057] Multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can each support OFDM-based downlink transmission. Furthermore, multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can each support OFDM-based or DFT-Spread-OFDM-based uplink transmission. Furthermore, multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can respectively support MIMO (Multiple Input Multiple Output) transmission (e.g., SU (Single User)-MIMO, MU (Multi User)-MIMO, massive MIMO, etc.), CoMP (Coordinated Multipoint) transmission, carrier aggregation transmission, transmission in unlicensed band, and device-to-device (D2D) communication (or ProSe (proximity services)). Among them, multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 can respectively execute actions corresponding to base stations 110-1, 110-2, 110-3, 120-1, and 120-2 and / or actions supported by base stations 110-1, 110-2, 110-3, 120-1, and 120-2.

[0058] For example, the second base station 110-2 can transmit signals to the fourth terminal 130-4 using SU-MIMO, and the fourth terminal 130-4 can receive signals from the second base station 110-2 using SU-MIMO. Alternatively, the second base station 110-2 can transmit signals to both the fourth terminal 130-4 and the fifth terminal 130-5 using MU-MIMO, and both terminals can receive signals from the second base station 110-2 using MU-MIMO. The first base station 110-1, the second base station 110-2, and the third base station 110-3 can each transmit signals to the fourth terminal 130-4 using CoMP, and the fourth terminal 130-4 can receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 using CoMP. Multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can transmit and receive signals with terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 within their coverage area via CA.

[0059] The first base station 110-1, the second base station 110-2, and the third base station 110-3 can respectively coordinate the D2D communication between the fourth terminal 130-4 and the fifth terminal 130-5. The fourth terminal 130-4 and the fifth terminal 130-5 can respectively perform D2D communication through the coordination of the second base station 110-2 and the third base station 110-3.

[0060] The following describes how, when a method (e.g., signal transmission or reception) is performed by a first communication node in a communication node, a corresponding second communication node can perform a method (e.g., signal reception or transmission) corresponding to the method performed by the first communication node. That is, when the actions of a terminal are described, the corresponding base station can perform actions corresponding to the terminal's actions. Conversely, when the actions of a base station are described, the corresponding terminal can perform actions corresponding to the base station's actions.

[0061] Furthermore, in this context, downlink (DL) refers to communication from the base station to the terminal, and uplink (UL) refers to communication from the terminal to the base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station.

[0062] Recently, with the rapid proliferation of smartphones and IoT (Internet of Things) devices, the volume of information sent and received via communication networks is increasing. Therefore, next-generation wireless access technologies need to consider environments that provide faster services to more users compared to traditional communication systems (or traditional radio access technologies) (e.g., enhanced mobile broadband communication). To this end, discussions are underway regarding the design of communication systems incorporating Machine Type Communication (MTC), which connects multiple instruments and objects to provide services. Furthermore, discussions are also underway regarding the design of communication systems sensitive to reliability and / or latency, such as service and / or terminal communication (e.g., URLLC (Ultra-Reliable and Low-Latency Communication)).

[0063] In this specification, for ease of description, the next-generation wireless access technology is referred to as New RAT (Radio Access Technology), and the wireless communication system using New RAT is referred to as NR (New Radio) system. In this specification, the terms frequency, frame, subframe, resource, resource block, region, frequency band, sub-frequency band, control channel, data channel, synchronization signal, various reference signals, various signals, or various information related to NR can be interpreted as having the meaning previously used, currently used, or to be used in the future.

[0064] Figure 2 This is a schematic diagram of an NR system to which the data transmission method of one embodiment of the present invention can be applied.

[0065] NR, a next-generation wireless communication technology currently being standardized within 3GPP, is a radio access technology that can provide data transmission rates higher than LTE and meet various QoS requirements depending on the specific usage scenario. In particular, eMBB (enhancement Mobile Broadband), mMTC (massive MTC), and URLLC (Ultra Reliable and Low Latency Communications) are defined as representative use cases for NR. It offers a more flexible frame structure than LTE to meet the requirements of various scenarios. NR's frame structure supports multiple subcarrier-based frame structures. The basic subcarrier spacing (SCS) is 15kHz, supporting a total of 5 SCS types at 15kHz*2^n (n=0,1,2,3,4).

[0066] refer to Figure 2 As can be seen, NG-RAN (Next Generation-Radio Access Network) consists of gNBs, which provide control plane (RRC) protocol terminals for the NG-RAN user plane (SDAP / PDCP / RLC / MAC / PHY) and UE (User Equipment). NG-C displays the control plane interface, which serves as the NG2 reference point between NG-RAN and 5GC (5 Generation Core). NG-U displays the user plane interface, which serves as the NG3 reference point between NG-RAN and 5GC.

[0067] The gNB connects via the Xn interface and via the NG interface to form a 5GC. More specifically, the gNB connects via the NG-C interface to form an AMF (Access and Mobility Management Function) and via the NG-U interface to form a UPF (User Plane Function).

[0068] Figure 2In the NR system shown, multiple numerologies can be supported. Among them, numerology can be defined based on the subcarrier spacing and the Cyclic Prefix (CP) overhead. At this time, the basic subcarrier spacing can be scaled to an integer to derive multiple subcarrier spacings. Also, even if an extremely high carrier frequency does not utilize an extremely small subcarrier spacing, the selection of numerology can be independent of the frequency band.

[0069] Also, in the NR system, multiple frame structures based on multiple numerologies can be supported.

[0070] <NR Waveform, Numerology, and Frame Structure>

[0071] In NR, the CP-OFDM waveform is used to implement downlink transmission. This CP-OFDM waveform uses a cyclic prefix, and CP-OFDM or DFT-S-OFDM is used to implement uplink transmission. The OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output). Its advantage is that a receiver with high frequency efficiency and low complexity can be used.

[0072] In addition, in NR, according to the three different scenarios described above, the requirements for data speed, latency speed, coverage, etc. are also different. Therefore, it is necessary to effectively meet the necessary conditions of each different scenario through any frequency band that makes up the NR system. For this purpose, a technology that can effectively multiplex wireless resources based on multiple different numerologies has been proposed.

[0073] Specifically, based on the sub-carrier spacing and the Cyclic Prefix (CP), the numerology of NR transmission is determined. As shown in Table 1 below, taking 15 kHz as a reference, the μ value is used as an exponential value of 2 to achieve exponential change.

[0074]

Table 1

[0075] μ Subcarrier spacing (kHz) Cyclic prefix Supported for data Supported for synch 0 15 Normal Yes Yes 1 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes

[0076] As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the fact that the subcarrier spacing of LTE, which is one of the 4G communication technologies, is fixed at 15 kHz. Specifically, in NR, the subcarrier spacings used for data transmission are 15, 30, 60, and 120 kHz, and the subcarrier spacings used for transmitting synchronization signals are 15, 30, 120, and 240 kHz. Also, the extended CP is only applicable to the 60 kHz subcarrier spacing. In addition, in NR, the frame structure is defined as a frame with a length of 10 ms, and this frame with a length of 10 ms consists of 10 subframes with the same length of 1 ms. A frame can be divided into two half-frames of 5 ms, and each half-frame includes 5 subframes. In the 15 kHz subcarrier spacing, a subframe consists of one time slot, and each time slot consists of 14 OFDM symbols.

[0077] <NR Physical Resources>

[0078] Regarding the physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, etc. can be considered.

[0079] An antenna port is defined as: the symbol-carrying channel on an antenna port can be inferred from the symbol-carrying channels on other antenna ports of the same type. When the large-scale properties of the symbol-carrying channels on one antenna port can be inferred from the symbol-carrying channels on other antenna ports, the two antenna ports are considered to be related to QC / QCL (quasi co-located or quasi co-location). Among them, the large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameter.

[0080] Figure 3 The resource grid supported by the radio access technology to which this embodiment can be applied is shown.

[0081] Reference Figure 3It can be seen that since NR supports multiple digital numerologies in the Resource Grid, there can be a Resource Grid according to each digital numerology. Moreover, the Resource Grid can exist along the antenna port, subcarrier spacing, and heading direction.

[0082] A resource block is composed of 12 subcarriers and is defined only in the frequency domain. Also, a resource element is composed of one OFDM symbol and one subcarrier. Thus, as Figure 3 shown, the size of a resource block can vary according to the subcarrier spacing. And in NR, "Point A", common resource blocks, physical resource blocks, etc. are defined, and "Point A" serves as a common reference point for the resource block grid.

[0083] Figure 4 It shows the partial bandwidth supported by the radio access technology to which this embodiment can be applied.

[0084] Different from LTE, the maximum carrier bandwidth for different subcarrier spacings in NR is configured to be 50 MHz to 400 MHz, while in LTE, the carrier bandwidth is fixed at 20 MHz. Therefore, it is not assumed that all terminals use this carrier bandwidth. Thus, as Figure 4 shown, NR can specify a partial bandwidth (BWP) within the carrier bandwidth for use by the terminal. And the partial bandwidth is related to one digital numerology, consists of a subset of consecutive common resource blocks, and can be dynamically activated according to time. In the terminal, the uplink and downlink respectively consist of up to 4 partial bandwidths, and data is transmitted and received using the activated partial bandwidth at a given time.

[0085] For paired spectrum, the uplink and downlink partial bandwidths are configured independently. To prevent unnecessary frequency re-tuning between the actions of the downlink and uplink, unpaired spectrum can be configured in pairs so that the partial bandwidths of the downlink and uplink share the center frequency.

[0086] <NR Initial Access>

[0087] In NR, the terminal performs cell search and random access procedures to access the base station for communication.

[0088] The cell search procedure utilizes the Synchronization Signal Block (SSB) transmitted by the base station, enables the terminal to synchronize with the cell of the base station, obtains the physical layer cell ID, and obtains system information.

[0089] Figure 5 An example of a synchronization signal block in a wireless access technology applicable to this embodiment is shown.

[0090] refer to Figure 5 It can be seen that the SSB consists of the PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal) occupying 1 symbol and 127 subcarriers, and the PBCH spanning 3 OFDM symbols and 240 subcarriers.

[0091] The terminal monitors and receives SSBs in both the time and frequency domains.

[0092] A maximum of 64 SSBs can be transmitted within 5ms. Multiple SSBs are transmitted using different beams within 5ms. The terminal uses the specific beam used for transmission as a reference, assuming an SSB transmission period of 20ms for detection. The number of beams available for SSB transmission within 5ms can increase with increasing frequency band. For example, below 3GHz, a maximum of 4 SSB beams can be transmitted; in the 3-6GHz band, a maximum of 8 SSB beams can be transmitted; and above 6GHz, up to 64 different beams can be used to transmit SSBs.

[0093] The SSB consists of two in a time slot, as follows, which determines the starting symbol and the number of repetitions within the time slot based on the subcarrier interval.

[0094] Furthermore, unlike the SS in traditional LTE, SSBs cannot be transmitted at the center frequency of the carrier bandwidth. That is, SSBs can be transmitted even at locations not at the center of the system frequency band, allowing for the transmission of multiple SSBs in the frequency domain during broadband operations. Therefore, the terminal uses a synchronization raster to monitor SSBs, which serves as a candidate frequency location for SSB monitoring. The carrier raster and synchronization raster are redefined in NR. The carrier raster provides the center frequency location information for the initial access channel, while the synchronization raster has a larger frequency spacing compared to the carrier raster to facilitate rapid SSB search by the terminal.

[0095] The terminal can obtain the MIB (Master Information Block) through the PBCH of the SSB. The MIB includes the minimum information for the terminal to receive the Remaining Minimum System Information (RMSI) broadcast by the network. Furthermore, the PBCH can include the position information of the first DM-RS symbol in the time domain, information for the terminal to monitor SIB1 (e.g., SIB1 numeric information, SIB1 CORESET related information, search space information, PDCCH related parameter information, etc.), and offset information between the common resource block and the SSB (the absolute SSB position within the carrier is transmitted via SIB1). The SIB1 numeric information is also applicable to the information used in the random access procedure for accessing the base station after the terminal completes the cell search process. For example, the SIB1 numeric information can be applicable to at least one of information 1 to 4 in the random access procedure.

[0096] As mentioned above, RMSI can mean SIB1 (System Information Block 1), which is broadcast periodically (e.g., every 160ms) within the unit. SIB1 includes the information required for the terminal to initially execute the random access procedure and is transmitted periodically via PDSCH. The terminal needs to receive the numeric information for transmitting SIB1 and the CORESET (Control Resource Set) information for scheduling SIB1 via PBCH to facilitate SIB1 reception. Within the CORESET, the terminal uses SI-RNTI to confirm the SIB1 scheduling information and obtains SIB1 on the PDSCH based on the scheduling information. Other SIBs besides SIB1 can also be transmitted periodically, or transmitted according to the terminal's requirements.

[0097] Figure 6 The random access procedure in the wireless access technology applicable to this embodiment is illustrated.

[0098] refer to Figure 6 As can be seen, upon completing a cell search, the terminal transmits a random access preamble to the base station for random access. This random access preamble is transmitted via PRACH. Specifically, the random access preamble is transmitted to the base station via PRACH, which consists of continuous radio resources, in specific time slots that are repeated periodically. Typically, when the terminal initially accesses a cell, a contention-based random access procedure is implemented; however, during random access, a non-contention-based random access procedure is executed to achieve Beam Failure Recovery (BFR).

[0099] The terminal receives a random access response in response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), UL Grant (Uplink Radio Resources), TC-RNTI (Temporary Cell-Radio Network Temporary Identifier), and TAC (Time Advance Command). A random access response may include random access response information for more than one terminal; therefore, it may include a random access preamble identifier to indicate which terminal the included UL Grant, TC-RNTI, and TAC are valid for. The random access preamble identifier may be the identifier of the random access preamble received by the base station. The TAC may be included as information for the terminal to adjust uplink synchronization. The random access response can be prompted based on the random access identifier on the PDCCH, i.e., RA-RNTI (Random Access-Radio Network Temporary Identifier).

[0100] Upon receiving a valid random access response, the terminal processes the information contained in the random access response and performs a scheduled transmission for the base station. For example, the terminal applies a TAC and stores the TC-RNTI. Furthermore, using a UL Grant, the data stored in the terminal's buffer or newly generated data is transmitted to the base station. At this point, information that identifies the terminal should be included.

[0101] Network slicing Slicing

[0102] Network slicing is a new concept that can be applied to 5G mobile communication. It can create and provide an independent slice of end-to-end resources from the radio access network (RAN) to the core network (CN) based on the different services provided by network resources and network functions. This applies attributes such as network isolation, customization, independent management and orchestration to the radio access network (RAN) and core network of mobile communication.

[0103] The integration of communication technologies with technologies such as Network Function Virtualization (NFV) and Software Defined Networking (SDN) is evolving towards the formation of network slices. These network slices are optimized within a vast network based on the characteristics of various applications.

[0104] Network slicing physically creates logically separated end-to-end (E2E) networks, including UEs, radio access, transmission ports, and 5G core equipment. Through a single physical network, it provides personalized dedicated networks for various services with different characteristics. In other words, network slicing is a technology that creates a separate slice of the network resources and functions required by a terminal's requested service.

[0105] Figure 7 A network slicing concept according to one embodiment is illustrated.

[0106] refer to Figure 7 As can be seen, a network slice consists of an E2E logical network from the UE to a relative node (relative to the UE or relative to the application server). Users can access personalized network slices based on the applications they utilize (eMBB, URLLC, MIoT, V2X, etc.) to receive services. That is, a user's terminal can access more than one network slice simultaneously. Each slice can be identified from the perspective of services and characteristics based on the slice / service type (SST) that matches predictable network actions.

[0107] Mobile communication operators can allocate network resources suitable for a service based on different slices or different sets of specific slices. These network resources can refer to network functions (NFs) or the logical resources or radio resource allocations provided by NFs. A network slice instance (NSI) can be defined as: the network function instance that forms the configured network slice and the set of required resources.

[0108] When describing the embodiments disclosed herein, terms such as slice, service, network slice, network service, application slice, and application service may be used interchangeably.

[0109] Random access process in network slicing

[0110] In NR, the terminal transmits the random access preamble for the RACH occasion (RO) to the network node to transition from the IDLE (RRC_IDLE) state to the ACTIVE (RRC_CONNECTED) state. After the network node receives the random access preamble, it predicts the timing advance (TA) to configure synchronization with the terminal. The terminal transmits the random access preamble at different times based on the delay difference with the network node. Furthermore, to detect multiple random access preambles separately, the network node is configured with various random access preamble formats and monitoring periods for different scenarios.

[0111] When network slicing is applied, mobile communication operators can allocate network resources suitable for a service based on different slices or different sets of specific slices, allowing terminals to access more than one slice. Therefore, terminals can execute random access procedures according to independent slices. RAN slices constitute E2E (End-to-End) network slices, which can be provided separately through frequency band (e.g., 3.5GHz, 28GHz) and / or time division. The frequency and time resources or preamble structures allocated for executing random access procedures according to each different slice can also be different. Here, a scheme for transmitting information separated from each slice is needed.

[0112] Transmit individual control information for RAN slices

[0113] Along with the issue of network neutrality, this further highlights the importance of network slicing technology.

[0114] In 5G mobile communication, to effectively support multiple services—that is, to support multiple services through a single system without requiring separate systems for different services—dynamic resource control via slicing is necessary. However, RAN slicing is more challenging than core network slicing. Conceptually, RAN slicing should enable each slice to operate like an independent unit, isolating and allowing each slice to function independently, so that even if one slice experiences a malfunction, it will not affect other slices.

[0115] To achieve the above objectives, it is crucial to slice the resources managed by a base station from the upper layer down to the physical layer. The upper layer can be implemented according to different functions, making software-based slicing easier. However, the closer to the lower layer, the more difficult it becomes to slice using software. For example, it might be necessary to implement a modem for communication using Software-Defined Radio (SDR). Therefore, a gradual approach can be considered. One such embodiment could include implementing the upper layer through Network Function Virtualization (NFV) and independently scheduling the lower layer based on different services or slices.

[0116] In this case, the following approach is needed to implement RAN slicing: for example, transmitting control information, including system information, separately according to different slices.

[0117] In communication systems that do not apply network slicing, there is no need to consider network slicing. Configuration information (e.g., random access parameters and / or resource information, initial bandwidth part (BWP) information, etc.) that needs to be transmitted from the network node to the UE can be included and transmitted within system information (e.g., MIB (Master Information Block), SIB1 (System Information Block 1) information). However, to implement RAN slicing, since different services or slice types have different characteristics, it is necessary to divide the configuration information or system information according to different slices for transmission. For example, information such as whether the initial bandwidth part (Initial BWP) needs to be configured as a specific BWP for a specific slice or service, or how to construct random access parameters and / or TDD configuration information for a specific slice or service, can be transmitted from the network node to the terminal.

[0118] When RAN slice-related information is transmitted from the network node to the terminal, for example, RAN slice-related information can be transmitted from the network node to the terminal in at least one of the following forms: system information and RRC information, MAC CE (Control Element), and DCI (Downlink Control Information).

[0119] On the one hand, unique IDs are assigned based on different slices (e.g., including eMBB, URLLC, V2X slices, etc.), and different services or slices are allocated according to each slice ID. For example, when transmitting system information allocated according to different slices, the information can be transmitted based on the slice ID.

[0120] In addition, RAN slice-related information can be used for handover between slices. Handover between slices can include: handover between multiple slices provided by the same base station (or unit), handover between slices provided by different base stations (or units), handover from a base station (or unit) providing RAN slices to a base station (or unit) not providing RAN slices, or handover from a base station (or unit) not providing RAN slices to a base station (or unit) providing RAN slices to a specific slice. To achieve handover between slices, parameters can be predetermined for each slice. By transmitting slice-related information from the network node to the terminal, the network node and the terminal can identify these parameters during handover.

[0121] Furthermore, the relevant information of each slice can be transmitted from the network node to the terminal in multiple information formats. For example, the MIB or SIB1 may include ID information of different slices considering various service types (e.g., eMBB, URLLC, V2X, etc.), and each terminal can receive only the information of one or more slices as needed based on the slice ID assigned to each slice.

[0122] On the other hand, for example, network nodes transmit information about available slices to terminals based on system information. Terminals that have the desired service or slice in the available slices utilize that slice, while terminals that do not have the desired service or slice or do not support RAN slices use the default slice.

[0123] System Information Transmission

[0124] To support RAN slicing, network nodes can transmit at least a portion of the system information that is different for each slice. For example, the system information may include MIB or SIB.

[0125] On the one hand, the MIB can also transmit different slices, and transmit different SIB1s (or RMSIs) for each different slice. For example, the MIB may include RAN slice action information. RAN slice action information may include information about whether the network node transmitting the MIB supports the RAN slice, and may consist of 1 to 2 bits. Additionally, the MIB may include resource information for obtaining the SIB1 for each slice. For example, the MIB may include first resource information for a first slice and second resource information for a second slice. The terminal receiving the MIB can respond to a decision to utilize the service corresponding to the first slice based on at least one of the first and second resource information, and receive the SIB1 for the first slice through the first resource information. Alternatively, the terminal receiving the MIB can respond to a decision to utilize the service corresponding to the second slice, and receive the SIB1 for the second slice through the second resource information.

[0126] On the other hand, MIB and SIB1 can jointly transmit different slices. MIB can include information on whether RAN slices are supported, and the UE receives different information from SIB1 according to each different slice. For example, more than one configuration information or parameter included in SIB1 can have values ​​for multiple slices respectively.

[0127] On the one hand, different configurations can be defined for each different slice. When configuring SIB1 (RMSI) according to different slices, each SIB1 can individually include the configuration information of its corresponding slice, or, for example, the different information of multiple slices can all be included in a common SIB1 (RMSI). For example, the different information of different slices can include at least one of the following information.

[0128] - Primarily information related to Slice resources in terms of frequency / time.

[0129] -Initial BWP, CORESET 0, Search Space

[0130] - Default SCS for different slices

[0131] -ServingCellConfigCommonSIB

[0132] -RACH related information

[0133] That is, for example, the configuration information of each slice (eMBB, URLLC, V2X, etc.) may include: slice resource information in terms of frequency and time, initial BWP of different slices, CORESET 0, search space, default SCS (subcarrier spacing, e.g., URLLC is set to 60kHz) of different slices, ServingCellConfigCommonSIB (defined as RRC information) and RACH related information (e.g., URLLC slices can be set to a relatively short RO period).

[0134] RAN slicing, based on fundamental concepts, allows for virtual segmentation and utilization, supporting multiple services within a single physical network node system. Slicing configurations must be built separately for each network node and core; through this process, terminals can only view their own zone or slice.

[0135] Use slice information during switching

[0136] At least one network node may or may not support RAN slicing. Therefore, depending on whether RAN slicing is supported, different types of handover procedures can be executed.

[0137] First, a handover procedure can be configured between units using RAN slicing. In this case, RAN slicing-related information can be included in the handover information. Furthermore, RAN slicing-related information can be added to the instructions sent and received between units during the handover process where necessary. Including RAN slicing-related information in the handover information allows a given terminal to continuously slice for previously used services. For example, in the first network node, a terminal that has used eMBB slicing can also use eMBB slicing after handover to the second network node.

[0138] Additionally, a switch can be made from a cell that uses RAN slicing to a cell that does not. In this case, relevant RAN slicing information can be included in the switchover information. For example, for parameters for which additional RAN slicing information was previously used in the cell, a default parameter matching that parameter can be defined and used.

[0139] Alternatively, a unit can switch from one that does not use RAN handover to one that does. In this case, with proper configuration, the unit can receive RAN slice information for the new unit and, during handover, be informed to select appropriate slice parameters based on the application and QoS. Alternatively, with proper configuration, the unit can receive necessary system information during handover to select the appropriate slice.

[0140] Switching between units that do not use RAN slicing can utilize the switching process of traditional technologies.

[0141] RAN Slicing Control Method

[0142] On the one hand, RAN slice control is performed through system information, RRC information, MAC CE, or DCI. For example, the following steps can be performed: First, basic configuration can be set according to the system information. Then, RRC information can be set as needed, and activation / deactivation can be achieved through MAC CE (Control Element). Additionally, highly dynamic changes can be included in the downlink control information (DCI) for implementation.

[0143] Figure 8 The terminal and network node implemented in an embodiment of the present invention are shown.

[0144] refer to Figure 8 As can be seen, terminal 1100 includes a processor (1110), a memory (1120), and a transceiver unit 1130. Processor 1110 can implement the functions, processes, and / or methods described in this specification. The wireless interface protocol layer can be implemented in processor 1110.

[0145] The memory 1120 is connected to the processor 1110 and stores various information used to drive the processor 1110. The transceiver unit 1130 is connected to the processor 1110 and transmits wireless signals to the network node 1200 or receives wireless signals from the network node 1200.

[0146] Network node 1200 includes a processor 1210, a memory 1220, and a transceiver unit 1230. In this embodiment, network node 1200, as a node of a non-terrestrial network, may include an artificial satellite executing the wireless access procedure described in this specification. Alternatively, in this embodiment, network node 1200, as a node of a terrestrial network, may include a base station executing the wireless access procedure described in this specification.

[0147] Processor 1210 can implement the functions, processes, and / or methods described in this specification. The wireless interface protocol layer can be implemented in processor 1210. Memory 1220 is connected to processor 1210 to store various information used to drive processor 1210. Transceiver 1230 is connected to processor 1210 to transmit wireless signals to terminal 1100 or receive wireless signals from terminal 1100.

[0148] Processors 1110 and 1210 may include ASICs (application-specific integrated circuits), other chipsets, logic circuits, and / or data processing devices. Memory 1120 and 1220 may include ROM (read-only memory), RAM (random access memory), flash memory, memory cards, storage media, and / or other storage devices. Transceiver units 1130 and 1230 may include baseband circuitry for processing radio frequency signals. When implementing the embodiments in software, the above methods can be implemented through modules (processes, functions, etc.) that implement the above functions. Modules can be stored in memories 1120 and 1220 and executed by processors 1110 and 1210. Memories 1120 and 1220 can be located internally or externally to processors 1110 and 1210 and can be connected to processors 1110 and 1210 through various known means.

[0149] The foregoing description, based on a flowchart, illustrates a method that can be implemented according to the features of the present invention within the illustrated system. For ease of description, the method is described through a series of steps or blocks; however, the features of the claimed invention are not limited to the steps or blocks within the flowchart, and a step may be performed in a different order or simultaneously with the other steps and the foregoing content. Furthermore, those skilled in the art should understand that the steps shown in the flowchart are not exclusive and may include other steps; deleting one or more steps shown in the flowchart will not affect the scope of the invention.

Claims

1. A terminal, characterized in that: In terminals operating within communication systems that support slice information include: The transceiver unit receives individual control information from network nodes, containing parameters individually set for each slice in a slice set, and executes a random access procedure using resources constructed individually for each slice set based on the individual control information; and A processor configured to control the reception of the individual control information and the random access procedure. The individual control information is received through a single system information block, which is then used collectively for slices within the slice set. The individual control information includes at least one of first control information for the first type of slice and second control information for the second type of slice. The processor is configured to control the random access procedure in the first type of slice based on the first control information, and to control the random access procedure in the second type of slice based on the second control information.

2. The terminal according to claim 1, characterized in that: The first control information and the second control information respectively include at least one of the following: random access parameter information, random access resource information, initial bandwidth information, TDD configuration information, frequency slice resource information, time slice resource information, CORESET 0, search space, default SCS of each slice, BWP, service unit configuration SIBs, and RACH information.

3. The terminal according to claim 1, characterized in that: The individual system information block further includes an information value that indicates whether the network node supports slicing.

4. The terminal according to claim 1, characterized in that: The first control information and the second control information are configured such that their building elements are different, or at least one of the values ​​of their building elements is different.

5. The terminal according to claim 1, characterized in that: The system information further includes the identification information of each slice. The processor extracts the first control information based on the first identification code corresponding to the first type of slice and extracts the second control information based on the second identification code corresponding to the second type of slice.

6. The terminal according to claim 1, characterized in that: The system information includes reception control information, which controls the reception of at least one of the first control information and the second control information. The processor can control the reception of at least one of the first control information and the second control information based on the reception control information.

7. The terminal according to claim 6, characterized in that: The receiving control information includes first receiving control information corresponding to the first type of slice and second receiving control information corresponding to the second type of slice.

8. The terminal according to claim 6, characterized in that: The receive control information includes at least one of the following: the location information of the first DM-RS symbol in the frequency or spatial domain, SIB1 numerology information, SIB1 scheduling CORESET related information, search space information, and PDCCH related parameter information.

9. The terminal according to claim 1, characterized in that: When an intention is made to control communication in the first type of slice but the first control information is unavailable, or when an intention is made to control communication in the second type of slice but the second control information is unavailable, the processor is configured to control communication based on default control information and default build resources.

10. A network node, characterized in that: In network nodes that support communication systems that handle slice information Includes: a transceiver unit that sends individual control information containing parameters individually set for each slice in a slice set to a terminal, and executes a random access procedure using resources constructed individually for each slice set based on the individual control information; and A processor configured to control the transmission and reception of the individual control information and the random access procedure. The individual control information is sent through a single system information block, which is then used collectively for slices within the slice set. The individual control information includes at least one of first control information for the first type of slice and second control information for the second type of slice. The processor is configured to control the random access procedure in the first type of slice based on the first control information, and to control the random access procedure in the second type of slice based on the second control information.

11. The network node according to claim 10, characterized in that: The first control information and the second control information respectively include at least one of the following: random access parameter information, random access resource information, initial bandwidth information, TDD configuration information, frequency slice resource information, time slice resource information, CORESET 0, search space, default SCS of each slice, BWP, service unit SIBs, and RACH information.

12. The network node according to claim 10, characterized in that: The first control information and the second control information are configured such that their building elements are different, or at least one of the values ​​of their building elements is different.

13. The network node according to claim 10, characterized in that: The system information further includes identification information for each slice. The processor includes first control information in the individual control information based on a first identification code corresponding to the first type of slice, and includes second control information in the individual control information based on a second identification code corresponding to the second type of slice.

14. The network node according to claim 10, characterized in that: The system information includes reception control information, which controls the reception of at least one of the first control information and the second control information.

15. The network node according to claim 14, characterized in that: The receiving control information includes first receiving control information corresponding to the first type of slice and second receiving control information corresponding to the second type of slice.

16. The network node according to claim 14, characterized in that: The receive control information includes at least one of the following: the location information of the first DM-RS symbol in the frequency or spatial domain, SIB1 numerology information, SIB1 scheduling CORESET related information, search space information, and PDCCH related parameter information.

17. The network node according to claim 10, characterized in that: When the terminal needs to switch to another network node, the processor generates switching information to be sent to the terminal. When the other network nodes support slice-based communication, the processor includes at least one of the first switching information of the first type of slice and the second switching information of the second type of slice in the switching information; When other network nodes do not support communication based on the slice, the processor includes the default switching information of the other network nodes in the switching information; the transceiver unit sends the switching information to the terminal.

18. A method for implementing communication via a terminal in a communication system that supports slice information, characterized in that: include: The step of receiving individual control information from network nodes, which includes parameters set individually for slices in the slice set; as well as Based on the individual control information, and utilizing the resources constructed separately for each slice set, the steps of the random access procedure are executed. The individual control information is sent through a single system information block, which is then used collectively for slices within the slice set. The individual control information includes at least one of first control information for the first type of slice and second control information for the second type of slice. The random access procedure in the first type of slice is controlled based on the first control information, and the random access procedure in the second type of slice is controlled based on the second control information.

19. The method according to claim 18, The individual system information block also includes an information value that indicates whether the network node supports slicing.

20. The method according to claim 18, The first control information and the second control information are configured such that their building elements are different, or at least one of the values ​​of their building elements is different.

Images