Random access procedures in next-generation networks

Abstract

To provide an enhanced random access procedure that supports beamforming for New Radio (NR) networks. In one embodiment, an NR node transmits a downlink transmission beam during a downlink sweeping subframe. A user equipment selects an optimal downlink transmission beam transmitted by a cell during the downlink sweeping subframe and determines an optimal downlink receiving beam from the optimal downlink transmission beam. The user equipment determines a random access preamble and a physical random access channel (PRACH) resource through resource selection from the optimal downlink transmission beam, and transmits the random access preamble to the NR node on the determined PRACH resource.

Description

[Technical Field]

[0001] (Citation of related applications) This application is U.S. Provisional Application No. 62 / 350,379 (filed June 15, 2016, title "R andom Access Procedures in Next Gen Netw orks) and U.S. Provisional Application No. 62 / 400,813 (filed September 28, 2016) Claiming priority rights under the name "NR Random Access," both applications are subject to the same law. The entirety of these is incorporated herein by reference.

[0002] (Field) This application applies to random access procedures on a device. [Background technology]

[0003] NextGen Network is not limited to mMTC, eMBB, and UR / LL. It is expected to support a diverse set of use cases, including network / RAN. Rising involves operators dealing with the diverse and sometimes contradictory requirements of these use cases. This is a concept proposed to make it possible to satisfy the requirements. However, random action Traditional procedures such as SECs use network / RAN slicing architectures. Not designed for porting. Configured for network / RAN slicing. A new random access procedure optimized for NextGen networks There is a need to develop a J.

[0004] New radio (NR) access technology currently operates at frequencies up to 100 GHz. Research is being conducted to identify and develop technical components for the system. The formation of a frame reduces the increased path loss in these high-frequency NR (HF-NR) systems. It is expected to be adopted to compensate. However, omnidirectional or sector-based Existing random access procedures based on beam transmission include beam sweeping and beam pairing. The functions required for accessing beamforming bases such as beam training and beam formation are Do not port. Enhanced random beamforming to support beamforming for NR networks. There is a need for access procedures. [Overview of the project] [Means for solving the problem]

[0005] This summary describes a series of concepts, which will be further explained in the following embodiments for carrying out the invention. Provided for implementation in a simplified form. This summary covers the scope of the claimed subject matter. This is not intended to limit the scope. The aforementioned necessity is related to the nextgen network. This application, which targets random access procedures within a system, largely satisfies these requirements.

[0006] One aspect is performing random access in a beam sweep network with cells. A device containing non-transient memory that includes instructions is described. The network is downlink Includes a sweep subframe, an uplink sweep subframe, and a normal sweep subframe. The device also includes a processor operably coupled to non-transient memory. The processor is Optimal downlink transmission BEE transmitted by the cell during the downlink sweep subframe The processor is configured to execute instructions to select the optimal downlink transmission. It can also be configured to execute instructions to determine the optimal downlink receiving beam from the beam. The processor randomly selects resources from the optimal downlink transmission beam. The access preamble and physical random access channel (PRACH) resources are determined. It is further configured to execute the specified instructions. The processor uses PRACH resources and And via the uplink transmission beam of the uplink subframe, selected random It is also configured to execute instructions that transmit access preambles to nodes.

[0007] Another aspect is the non-transient nature of instructions that perform random access in a network. A device containing memory is described. The device is operably coupled to non-transient memory and Configuration for Common Physical Random Access Channel (PRACH) resources on the network This also includes processors configured to execute instructions to retrieve parameters. The system selects a preamble from the cell based on the device type and service type. The processor is also configured to execute instructions via a common PRACH resource. It is also configured to execute instructions that transmit the selected preamble to the node. The assessor monitors the downlink control channel for random access responses (RARs). The processor is further configured to execute instructions via nodes on the network. Then, the device type and service type associated with the selected preamble It can also be further configured to execute instructions that receive random access responses.

[0008] Another aspect is the non-transient nature of instructions that perform random access in a network. A device containing memory is described. The device is operably coupled to non-transient memory and Common physical random access channel (PRACH) resources for slice identification on a gridwork A processor configured to execute instructions to obtain configuration parameters for the resources is also included. The processor is also configured to execute instructions to randomly select a preamble from a slice of the network based on the device type and service type. The processor is further configured to execute instructions to transmit the randomly selected preamble to a node via a slice-specific PRACH resource. The processor is further configured to execute instructions to monitor a downlink control channel for a random access response (RAR). The processor is still further configured to execute instructions to receive an RAR associated with the device type via a node on the network .

[0009] In another aspect, a device including a non-transitory memory including instructions to perform random access in a network is described. The device includes a processor operatively coupled to the non-transitory memory and configured to execute instructions to select a preamble from a cell based on the device type and service type. The processor is also configured to execute instructions to transmit the selected preamble and an accompanying message without permission. The processor is further configured to execute instructions to monitor a downlink control channel for a random access response (RAR). The processor is still further configured to execute instructions to receive a connection setup message and an uplink permission from a node. The processor is still further configured to execute instructions to transmit a status message about the connection via the received uplink permission ​​​​​​​​​​The processor is further configured to execute instructions that transmit the node. It is configured to execute instructions that receive downlink data and control signaling from It can be done.

[0010] Therefore, in order for the detailed explanation to be more deeply understood, and for the technical field in question In order for the contribution to be more deeply recognized, certain embodiments of the present invention are outlined in a fairly broad sense. Ta. [Brief explanation of the drawing]

[0011] To facilitate a more solid understanding of this application, similar elements are shown here using the same numbering. Refer to the accompanying drawings, which are to be used as references. These drawings are to be construed as limiting the present application. It is not meant to be a 'should,' but rather as an example. [Figure 1A] Figure 1A illustrates an exemplary communication system according to one embodiment of the present invention. [Figure 1B] Figure 1B illustrates an exemplary device configured for wireless communication according to one embodiment of the present invention. [Figure 1C] Figure 1C illustrates a diagram of a wireless access network and a core network according to one embodiment of the present invention. [Figure 1D] Figure 1D illustrates a diagram of a wireless access network and a core network according to another embodiment of the present application. [Figure 1E] Figure 1E illustrates a diagram of a wireless access network and a core network according to yet another embodiment of the present application. [Figure 1F] Figure 1F illustrates a block diagram of an exemplary computing system according to one embodiment of the present invention that communicates with one or more networks as described above in Figures 1A, 1C, 1D, and 1E. [Figure 2A] Figure 2A is a schematic diagram illustrating the RRC protocol state machine. [Figure 2B]Figure 2B is a schematic diagram illustrating the system information acquisition procedure. [Figure 3] Figure 3 is a schematic diagram of the measurement model used in LTE. [Figure 4] Figure 4 is a schematic diagram of a two-layer structure for DL. [Figure 5] Figure 5 is a schematic diagram of a two-layer structure for UL. [Figure 6] Figure 6 is a schematic diagram illustrating the random access preamble format. [Figure 7] Figure 7 is a schematic diagram illustrating the PRACH resource definition. [Figure 8] Figure 8 is a schematic diagram illustrating a contention-based random access procedure. [Figure 9] Figure 9 is a schematic diagram of the structure for LTE DL multi-antenna transmission. [Figure 10] Figure 10 is a schematic diagram of cell coverage with a sector beam and multiple high-gain narrow beams. [Figure 11] Figure 11 is a schematic diagram of a virtual cell. [Figure 12] Figure 12 is a schematic diagram illustrating the transition from RRC_IDLE to RRC_CONNECTED. [Figure 13] Figure 13 is a schematic diagram illustrating the concept of network slicing. [Figure 14] Figure 14 is a schematic diagram illustrating an exemplary configuration that supports RAN slicing. [Figure 15] Figure 15 is a schematic diagram illustrating the common PRACH resource. [Figure 16] Figure 16 is a schematic diagram illustrating a common PRACH resource that supports multiple numerology systems. [Figure 17] Figure 17 is a schematic diagram illustrating an exemplary common PRACH resource configuration supporting one mMTC, two eMBBs, and four UR / LLPRACH resources. [Figure 18]Figure 18 is a schematic diagram illustrating an exemplary common PRACH resource configuration with "stacked" mMTC PRACH resources. [Figure 19] Figure 19 is a schematic diagram illustrating the PRACH resources specific to a slice. [Figure 20] Figure 20 is a schematic diagram illustrating a random access procedure that uses a common PRACH resource. [Figure 21] Figure 21 is a schematic diagram illustrating the service-based partitioning of the random access preamble. [Figure 22] Figure 22 is a schematic diagram illustrating the MAC CE service type. [Figure 23] Figure 23 is a schematic diagram illustrating a random access procedure that uses a slice-specific PRACH resource. [Figure 24] Figure 24 is a schematic diagram illustrating a random access procedure involving permissionless transmission. [Figure 25A] Figures 25A-C are schematic diagrams illustrating the random access preamble format for permissionless transmission. [Figure 25B] Figures 25A-C are schematic diagrams illustrating the random access preamble format for permissionless transmission. [Figure 25C] Figures 25A-C are schematic diagrams illustrating the random access preamble format for permissionless transmission. [Figure 26] Figure 26 is a schematic diagram of beamforming within an HF-NR network. [Figure 27] Figure 27 is a schematic diagram of a sweep subframe with one beam enabled per sweep slot. [Figure 28] Figure 28A-B is a schematic diagram of a sweep subframe in which multiple beams are enabled per sweep slot. [Figure 29] Figure 29 is a schematic diagram of the built-in DL / UL sweep subframe. [Figure 30] Figure 30 is a schematic diagram of the frame structure with an integrated DL / UL sweep subframe. [Figure 31] Figure 31 is a schematic diagram of the frame structure with a separate DL / UL sweep subframe. [Figure 32] Figure 32 is a schematic diagram of the relationship between UL / DL beams. [Figure 33] Figure 33 is a schematic diagram of the sweep subframe information elements. [Figure 34] Figure 34 is a schematic diagram of the alternative sweep subframe information element. [Figure 35] Figure 35 is a schematic diagram of the NR master information block. [Figure 36] Figure 36 is a schematic diagram of the cell selection procedure for a beam-sweeping NR network. [Figure 37] Figure 37 is a schematic diagram of trigger transmission for other SIs. [Figure 38] Figure 38 is a schematic diagram of an exemplary random access preamble format. [Figure 39] Figure 39 is a schematic diagram of the association between the selected DL Tx beam and PRACH time resources. [Figure 40] Figure 40 is a schematic diagram of the correlation between selected DL Tx beams and PRACH time resources for the built-in DL / UL sweep subframe. [Figure 41] Figure 41 is a schematic diagram of the partitioning of the random access preamble that implicitly signals the "best" DL Tx beam. [Figure 42] Figure 42 is a schematic diagram of the random access response window. [Figure 43] Figure 43 is a schematic diagram of the timing of RAR authorization. [Figure 44] Figure 44 is a schematic diagram of the proposed measurement model for the beam-sweeping NR network. [Figure 45] Figure 45 is a schematic diagram of the graphical user interface of the embodiment. [Figure 46] Figure 46 is a schematic diagram of a graphical user interface in another embodiment. [Modes for carrying out the invention]

[0012] Modes for carrying out the invention can be found by referring to the various figures, embodiments, and aspects of this specification. This will be discussed. This explanation provides detailed examples of possible implementations, but the details are examples only. It is intended that this does not limit the scope of this application.

[0013] In this specification, "one embodiment," "a certain embodiment," "one or more embodiments," and "a References such as "aspects" refer to specific features, structures, or characteristics described in relation to the embodiments. This means that it is included in at least one embodiment of the present disclosure. Furthermore, various The term "embodiment" in this context does not necessarily refer to the same embodiment. That is, as can be shown by some embodiments, but not by other embodiments. Various characteristics are explained.

[0014] (abbreviation) The following provides an acronym for terms and phrases commonly used in this application: AS = Access Layer CDMA = Code Division Multiple Access CN = Core Network CMAS = Commercial Mobile Alert System C-RNTI = Cell Radio Network Temporary Identifier DL = Downlink DL-SCH = Downlink Shared Channel DRX = Discontinuous reception EAB = Extended Access Control eMBB = Extended Mobile Broadband eNB = Evolutionary Node B ETWS = Earthquake and Tsunami Warning System E-UTRA = Evolved Universal Terrestrial Radio Access E-UTRAN = Evolved Universal Terrestrial Wireless Access Network FFS = Further research target GERAN=GSM(registered trademark) EDGE Wireless Access Network GSM (Registered Trademark) G = Global System for Mobile Communications IE = Information element IMT = International Mobile Telecommunications KPI = Key Performance Indicator LTE = Long-Term Evolution MACM = Media Access Control MAC CE = Media Control Element MBB = Mobile Broadband MBMS = Multimedia Broadcast Multicast Service MCL=maximum coupling loss MIB = Master Information Block MME = Mobile Management Entity MTC = Machine Type Communication mMTC = Massive Machine Type Communication NAS = Non-Access Layer NR = New RAT PDCCH = Physical Downlink Control Channel PHY=physical layer PRACH = Physical Random Access Channel PUCCH = Physical Uplink Control Channel QoS = Quality of Service RACH = Random Access Channel RAN = Wireless Access Network (3GPP) RAR = Random Access Response RA-RNTI = Random Access Radio Network Temporary Identifier RAT = Wireless Access Technology RE = Resource Element RNTI = Wireless Network Temporary Identifier RRC = Wireless Resource Control SC-PTM = Single Cell Point to Multipoint SI = System Information SIB = System Information Block SMARTER = Feasibility studies on new services and market technologies SR = Scheduling Request sTAG = Secondary Timing Advance Group TA = Timing Advance TDD=time division duplex TRP = Transmission and Reception Point TTI = Transmission Time Interval UE = User Equipment UpPTS = Uplink Pilot Time Slot UL = Uplink UL-SCH = Uplink Shared Channel UTRAN = Universal Terrestrial Radio Access Network UR / LL=Ultra reliability / low latency URLLC = Highly reliable and low-latency communication.

[0015] The Third Generation Partnership Project (3GPP) focuses on wireless access, core transformers, and more. Port network and service capabilities (codecs, security, and services) Developing technical standards for cellular telecommunications network technology, including quality control work. Recent wireless access technology (RAT) standards include WCDMA (registered trademark) (generally). 3G (commonly referred to as 4G), LTE (commonly referred to as 4G), and LTE-Advance Includes the d standard. 3GPP is the next generation of wireless technology called NR, also known as "5G". We have begun working on the standardization of next-generation cellular technology. 3GPP NR standard development is for next-generation wireless It is expected to include a definition of access technology (new RAT), which is below 6GHz. Providing new flexible wireless access and new ultra-mobile access beyond 6GHz. It is expected to include providing roadband wireless access. Flexible wireless access This consists of new non-backward compatible wireless access in a new spectrum below 6GHz. This is expected to address a broad set of 3GPP NR use cases with diverse requirements. Different operating modes can be multiplexed together within the same spectrum. It is expected to include: Ultra-mobile broadband, for example, for indoor use and Providing an opportunity for ultra-mobile broadband access for hotspots It is expected to include ultrawave, centimeter-wave, and millimeter-wave spectra. Specifically, ultrawave Mobile broadband, with centimeter wave and millimeter wave specific design optimizations, is 6GHz. It is expected to share a common design framework with flexible wireless access that is below the standard. ru.

[0016] 3GPP identifies various use cases that NRs are expected to support. Therefore, it meets various user experience requirements for data rate, latency, and mobility. This brings about the following general categories of use cases: Enhanced Mobile Broadband (For example, broadband access in high-density areas, ultra-high broadband indoors) Access, broadband access in crowds, 50+ Mbps everywhere, ultra low Cost broadband access, mobile broadband in vehicles, critical communications, mass Machine-type communication, network operation (e.g., network slicing, routing) (Simulation, mobility and interworking, energy saving), and extended vehicle- To-everything (eV2X) communication. Specific services within these categories. Some of its applications include, for example, surveillance and sensor networks, and remote device monitoring. Remote control, two-way remote control, personal cloud computing, video streaming Wireless cloud-based office, emergency responder connectivity, car e-call, disaster alerts Real-time games, multiplayer video calls, autonomous driving, augmented reality, haptic internet, and virtual reality. All of these use cases and others are discussed herein. ru.

[0017] (General architecture) Figure 1A shows an exemplary diagram in which the methods and apparatus described and claimed herein may be embodied. An embodiment of the communication system 100 is illustrated. As shown, the exemplary communication system 100 This includes the Wireless Transmission / Receiving Unit (WTRU) 102a, 102b, 102c, and / or 102d (which may be generally or collectively referred to as WTRU102) and wireless access Network (RAN) 103 / 104 / 105 / 103b / 104b / 105b and A-Network 106 / 107 / 109 and Public Switched Telephone Network (PSTN) 10 8 may include the Internet 110 and other networks 112, but the disclosed actual The implementation configuration can consist of any number of WTRUs, base stations, networks, and / or network components. It will be understood that the primes should be considered. WTRU102a, 102b, 102c, 10 Each of 2d and 102e is an optional device configured to operate and / or communicate in a wireless environment. It may be a device of the type WTRU102a, 102b, 102c, 102d and 102e are depicted in Figure 1A-1E as handheld wireless communication devices, Using the various use cases considered for 5G wireless communication, each WTRU is an example of This includes user equipment (UE), mobile stations, fixed or mobile subscriber units, Pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, etc. Bullet, netbook, notebook computer, personal computer, wireless Wearable devices such as consumer electronics, smartwatches, or smart clothing. Medical or e-health devices, robots, industrial equipment, drones, cars, trucks, trains, Or configured to transmit and / or receive wireless signals, including those from vehicles such as airplanes. It may be equipped with or embodied in any type of device or apparatus. It is understood that this is the case.

[0018] The communication system 100 may include both base station 114a and base station 114b. 4a wirelessly interacts with at least one of WTRU102a, 102b, or 102c. - Take the face, core network 106 / 107 / 109, internet 110, and / or access to one or more communication networks such as other networks 112 It may be any type of device configured to facilitate. Base station 114b is RR H (Remote Wireless Head) 118a, 118b and / or TRP (Transmission and Reception Point) 1 Interface with at least one of 19a or 119b via wired and / or wireless The network takes the core network 106 / 107 / 109, the internet 110, and / To facilitate access to one or more communication networks such as other networks 112. It can be any type of device configured to do so. RRH118a, 118b are Interface wirelessly with at least one of the WTRU102c and corenet Work 106 / 107 / 109, Internet 110, and / or other network Optionally configured to facilitate access to one or more communication networks such as 112. It may be a device of the type. TRP119a, 119b are among the WTRU102d. It interfaces wirelessly with at least one of the core networks 106 / 107 / 109, the Internet 110, and / or other networks 112, one or more Any type of device configured to facilitate access to a communication network It is possible. For example, base stations 114a and 114b are transceiver base stations (BTS) and nodes. -B, eNodeB, Home NodeB, Home eNodeB, Service Site Controller This could be an access point (AP), a wireless router, etc. Each of the base stations 114a and 114b Each is described as a single element, but base stations 114a and 114b can have any number of interconnections. It will be understood that this may include base stations and / or network elements.

[0019] Base station 114a includes base station controller (BSC), wireless network controller ( This also includes other base stations and / or network elements (not shown), such as RNCs, relay nodes, etc. It may be part of RAN103 / 104 / 105. Base station 114b is a base station controller. Other bases such as Torola (BSC), Wireless Network Controller (RNC), and relay nodes. RAN103b / 104b may also include local and / or network elements (not shown). It may be part of / 105b. Base station 114a may be a specific cell (not shown). It may be configured to transmit and / or receive radio signals within a geographical area. Base station 11 4b refers to wired and / or wireless communication within a specific geographical area which may be called a cell (not shown). The cell can be configured to transmit and / or receive signals. It can be divided. For example, a cell associated with base station 114a can be divided into three sectors. Therefore, in one embodiment, the base station 114a may, for example, perform the following for each cell sector. It may include one or three transceivers. In one embodiment, the base station 114a has multiplexed input / output ( MIMO technology can be employed, and therefore, multiple transceivers can be used for each sector of the cell. .

[0020] The base station 114a connects to any suitable wireless communication link (e.g., radio frequency (RF), microwave). Air waves (which can include infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc.) via interface 115 / 116 / 117, WTRU102a, 102b, 10 It can communicate with one or more of the 2c devices. Air interface 115 / 116 / 11 7 can be established using any suitable radio access technology (RAT).

[0021] Base station 114b can use any suitable wired (e.g., cable, optical fiber, etc.) or wireless connection. Communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV)) Wired or air interface 115b / (possibly visible light, centimeter wave, millimeter wave, etc.) Via 116b / 117b, RRH118a, 118b and / or TRP119 It can communicate with one or more of a, 119b. Air interface 115b / 1 16b / 117b can be established using any suitable radio access technology (RAT). .

[0022] RRH118a, 118b and / or TRP119a, 119b are any suitable Wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV)) Air interface 115c / 116c (can emit visible light, centimeter wave, millimeter wave, etc.) It can communicate with one or more of WTRU102c and 102d via / 117c. The 115c / 116c / 117c air interface is suitable for any suitable wireless access. It can be established using RAT technology.

[0023] More specifically, as described above, the communication system 100 is a multiple access system. It can be obtained from one or more types of DMA such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. A network access method can be adopted. For example, RAN103 / 104 / 105 and WTRU Base station 114a or RAN103b / 104b / 1 within 102a, 102b, 102c RRH118a, 118b and TRP1 in 05b and WTRU102c, 102d 19a and 119b use broadband CDMA (WCDMA®) respectively. , air interface 115 / 116 / 117 or 115c / 116c / 117c A universal mobile telecommunications system (UMTS) with terrestrial radio access (UT) can be established. Wireless technologies such as RA can be implemented. WCDMA (registered trademark) is a high-speed packet access technology. This may include communication protocols such as HSPA and / or evolved HSPA (HSPA+). HSPA stands for High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​A This may include High-Speed ​​Packet Access (HSUPA).

[0024] In one embodiment, base station 114a and WTRU 102a, 102b, 102c, or RR within RAN103b / 104b / 105b and WTRU102c, 102d H118a, 118b and TRP119a, 119b are, respectively, Long Term Evolution LTE (LTE) and / or LTE-Advanced (LTE-A) Use the air interface 115 / 116 / 117 or 115c / 116c / 1 Advanced UMTS terrestrial radio access (E-UTRA) and other wireless technologies that can establish 17c It can be equipped with. In the future, the air interface 115 / 116 / 117 will be based on 3GPP NR technology. It is possible to implement this.

[0025] In one embodiment, RAN103 / 104 / 105 and WTRU102a, 102b , base stations 114a within 102c, or RAN103b / 104b / 105b and WT RRH118a, 118b and TRP119a, 119 within RU102c, 102d b is IEEE 802.16 (for example, Worldwide Interoperability Standards). Microwave access (WiMAX), CDMA2000, CDMA2000 00 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard IS-95, provisional IS-856, global standards for mobile communications GSM (registered trademark), GSM (registered trademark) evolved high-speed data rate (ED It can implement wireless technologies such as GE, GSM (registered trademark), and EDGE (GERAN).

[0026] In Figure 1A, base station 114c is, for example, a wireless router, home node B, home eN This could be an odeB or access point, such as a company, home, vehicle, campus, etc. Any suitable RAT can be used to facilitate wireless connectivity within a local area. In this configuration, base stations 114c and WTRU102e are equipped with IEEE 802.11 and other wireless technologies. By implementing linear technology, a wireless local area network (WLAN) can be established. In this configuration, base stations 114c and WTRU102d are equipped with IEEE 802.15 and other wireless technologies. By implementing linear technology, a wireless personal area network (WPAN) can be established. In one embodiment, the base station 114c and WTRU 102e are cellular-based RAT (For example, WCDMA®, CDMA2000, GSM®, LTE, Using LTE-A, etc., picocells or femtocells can be established. As shown in Figure 1A. Therefore, base station 114b may have a direct connection to the internet 110. Then, base station 114c connects to the internet via core network 106 / 107 / 109. You may not be asked to access T110.

[0027] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b are , voice, data, applications, and / or Voice over Internet The protocol (VoIP) service is supported by WTRU102a, 102b, 102c, and 102d. Any type of network configured to provide to one or more of the following It can communicate with core networks 106 / 107 / 109. For example, core network 106 / 107 / 109 are call control, billing services, and mobile location-based services. , provide prepaid calls, internet connectivity, video distribution, etc., and / or It can implement high-level security features such as user authentication.

[0028] Although not shown in Figure 1A, RAN103 / 104 / 105 and / or RAN10 3b / 104b / 105b and / or core network 106 / 107 / 109 This refers to RAN103 / 104 / 105 and / or RAN103b / 104b / 105b It can communicate directly or indirectly with other RANs that employ the same or different RAT. This will be understood. For example, RAN103 / 1 which can utilize E-UTRA wireless technology In addition to connecting to 04 / 105 and / or RAN103b / 104b / 105b The core networks 106 / 107 / 109 also utilize GSM® wireless technology. It can communicate with another RAN (not shown) that is used.

[0029] Core networks 106 / 107 / 109 are WTRU102a, 102b, 102c It also serves as a gateway for 102d and 102e, and PSTN108, Access to network 110 and / or other networks 112 is possible. PST N108 includes a circuit-switched telephone network that provides basic telephone services (POTS). To obtain. The Internet 110 uses the Transmission Control Protocol (TCP), User Datagrams The TCP / IP Internet Protocol suite includes the U.S. Protocol (UDP) and the U.S. Interconnected consoles that use common communication protocols such as the Internet Protocol (IP) This may include a global system of computer networks and devices. 112 is owned and / or operated by another service provider, wired or This may include wireless communication networks. For example, network 112 is RAN103 / 1 04 / 105 and / or RAN103b / 104b / 105b and the same RAT or It may include separate core networks connected to one or more RANs that employ different RATs. ru.

[0030] Among WTRU102a, 102b, 102c, and 102d in the communication system 100 Some or all of them may include multimode capability, e.g., WTRU102a, 102b 102c, 102d, and 102e are different wireless networks via different wireless links. It may include multiple transceivers for communicating with the network. For example, the WTR shown in Figure 1A. The U102e is a base station 114a that can employ cellular-based wireless technology and IEEE 8 It can be configured to communicate with a base station 114c that may employ 02 wireless technology.

[0031] Figure 1B shows a wireless communication according to an embodiment illustrated herein, such as WTRU102. This is a block diagram of an exemplary apparatus or device configured for a signal, as shown in Figure 1B. As shown, the exemplary WTRU102 includes a processor 118, a transceiver 120, and a transmission / reception unit. Element 122, speaker / microphone 124, keypad 126, display / Touchpad / indicator 128, non-removable memory 130, removable memory Mori 132, power supply 134, Global Positioning System (GPS) chipset 136, and others It may include peripheral devices 138. WTRU102 remains consistent with the embodiment, as described above. It will be understood that this may include any secondary combination of elements. Furthermore, embodiments This includes base stations 114a and 114b, and / or, but not limited to, transmitting and receiving. Telecommunications Station (BTS), Node-B, Service Establishment Controller, Access Point (AP) Home Node-B, Evolved Home Node-B (eNodeB), Home Evolved Node- Base stations such as B(HeNB), Home Evolution Node-B gateways, and proxy nodes. The nodes that stations 114a and 114b may represent are shown in Figure 1B and described herein. Consider that it may include some or all of the elements.

[0032] Processor 118 is a general-purpose processor, special-purpose processor, conventional processor, digital processor A DSP (Digital Signal Processor), multiple microprocessors, one associated with a DSP core. The above microprocessors, controllers, microcontrollers, and application-specific integrated circuits ASICs (Application-Specific Integrated Circuits), Field-Programmable Gate Arrays (FPGAs), and any other It may be an integrated circuit (IC), a state machine, etc. The processor 118 is a signal coding , data processing, power control, input / output processing, and / or WTRU102 within a wireless environment It may implement any other functionality that enables it to operate. The processor 118 transmits / Can be coupled to the receiving element 122 or the transceiver 120. Figure 1B shows the processor. Although 118 and the transceiver 120 are depicted as separate components, the processor 11 The 8 and transceiver 120 can be integrated together in an electronic package or chip. It will be understood.

[0033] The transmission / reception element 122 is transmitted via the air interfaces 115 / 116 / 117, Transmit signals to or receive signals from a base station (e.g., base station 114a). It can be configured as follows. For example, in one embodiment, the transmission / receiving element 122 transmits an RF signal This may be an antenna configured to transmit and / or receive. (As shown in Figure 1A) However, RAN103 / 104 / 105 and / or core network 106 / 107 / 109 uses the same RAT as RAN103 / 104 / 105 or a different RAT. It will be understood that it may be able to communicate directly or indirectly with other RANs. For example, the EU In addition to being connected to RAN103 / 104 / 105 which can utilize TRA wireless technology, A network 106 / 107 / 109 employs another GSM (registered trademark) wireless technology. It can also communicate with RAN (not shown).

[0034] Core networks 106 / 107 / 109 are WTRU102a, 102b, 102c It also serves as a gateway for 102d, PSTN108, Internet It can access network 110 and / or other networks 112. PSTN 108 is This may include a circuit-switched telephone network that provides basic telephone services (POTS). Network 110 uses the Transmission Control Protocol (TCP) and the User Datagram Protocol. UDP, and Internet Protocol Suite (TCP / IP) Interconnected computer networks that use common communication protocols such as IP (Internet Protocol) It may include a global system of work and devices. Network 112 may include other Wired or wireless network owned and / or operated by a service provider It may include work. For example, network 112 is the same as RAN103 / 104 / 105. A separate core network connected to one or more RANs that may employ one RAT or different RATs. This may include twerking.

[0035] Among WTRU102a, 102b, 102c, and 102d in the communication system 100 Some or all of them may include multimode capability, e.g., WTRU102a, 102b 102c and 102d are different wireless networks via different wireless links. It may include multiple transceivers for communication. For example, the WTRU102c shown in Figure 1A. This includes a base station 114a that can employ cellular-based wireless technology and IEEE 802 wireless technology. It can be configured to communicate with a base station 114b that may employ the technique.

[0036] Figure 1B shows a wireless communication according to an embodiment illustrated herein, such as WTRU102. This is a block diagram of an exemplary apparatus or device configured for a signal, as shown in Figure 1B. As shown, the exemplary WTRU102 includes a processor 118, a transceiver 120, and a transmission / reception unit. Element 122, speaker / microphone 124, keypad 126, display / Touchpad / indicator 128, non-removable memory 130, removable memory Mori 132, power supply 134, Global Positioning System (GPS) chipset 136, and others It may include peripheral devices 138. WTRU102 remains consistent with the embodiment and includes the aforementioned features. It will be understood that this may include any secondary combination of primes. Furthermore, the embodiments are base stations 114a and 114b, and / or, but not limited to, transmitting and receiving Base Station (BTS), Node-B, Service Establishment Controller, Access Point (AP), Home Node-B, Evolved Home Node-B (eNodeB), Home Evolved Node-B Base stations such as (HeNB), Home Evolution Node-B gateways, and proxy nodes. The nodes that 114a and 114b may represent are shown in Figure 1B and described herein. Consider that it may include some or all of the elements.

[0037] Processor 118 is a general-purpose processor, special-purpose processor, conventional processor, digital processor A DSP (Digital Signal Processor), multiple microprocessors, associated with DSP cores One or more microprocessors, controllers, microcontrollers, application-specific Integrated circuits (ASICs), field-programmable gate arrays (FPGAs), arbitrary Other types of integrated circuits (ICs), state machines, etc., may be used. The processor 118 is a signal Encoding, data processing, power control, input / output processing, and / or WTRU102 wireless It can perform any other functionality that enables it to operate within the environment. Processor 118 The transmission / receiving element 122 can be coupled to a transceiver 120. Figure 1B shows the process. The sesser 118 and the transceiver 120 are described as separate components, but the process The 118 and the transceiver 120 can be integrated together in an electronic package or chip. They will understand this.

[0038] The transmission / reception element 122 is transmitted via the air interfaces 115 / 116 / 117, Transmit signals to or receive signals from a base station (e.g., base station 114a). It can be configured as follows. For example, in one embodiment, the transmission / receiving element 122 transmits an RF signal It may be an antenna configured to transmit and / or receive. In one embodiment, The transmission / reception element 122 transmits and / or transmits IR, UV, or visible light signals, for example. This can be an emitter / detector configured to receive. In a further embodiment, transmission The receiving element 122 may be configured to transmit and receive both RF and optical signals. The transmission / reception element 122 transmits and / or transmits any combination of wireless or wired signals. It will be understood that it may be configured to receive or receive

[0039] In addition, although the transmission / reception element 122 is depicted as a single element in Figure 1B, WT RU102 may include any number of transmission / reception elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, in an embodiment, WTRU102 is Transmits and receives radio signals via air interfaces 115 / 116 / 117. It may include two or more transmission / reception elements 122 (e.g., multiple antennas).

[0040] The transceiver 120 modulates the signal transmitted by the transmission / receiving element 122. Furthermore, it may be configured to demodulate the signal received by the transmission / reception element 122. Thus, the WTRU102 may have multimode capability. Therefore, transceiver 12 0 means that WTRU102 is a multiple R, such as UTRA and IEEE 802.11. It may include multiple transceivers to enable communication via AT.

[0041] The WTRU102 has a processor (118), a speaker / microphone (124), and a keypad (1). 26, and / or display / touchpad / indicator 128 (e.g., LCD) Display (LCD) display unit or organic light-emitting diode (OLED) display unit It can be coupled to (a) and can receive user input data from there. Processor 118 is User data is transmitted to speaker / microphone 124, keypad 126, and / or data Output can be sent to the display / touchpad / indicator 128. In addition, the processor 11 8 is any non-removable memory 130 and / or removable memory 132, etc. Information can be accessed from a suitable type of memory and data can be stored there. Non-removable Possible non-removable memory 130 is random access memory (RAM), read-only. Includes memory (ROM), hard disk, or any other type of memory storage device. It is visible. Removable memory 132 is the subscriber identification module (SIM) card. This may include memory sticks, secure digital (SD) memory cards, etc. In this configuration, processor 118 is a WTR on a server or home computer (not shown). Access information from memory that is not physically located on U102, and store the data within it. obtain.

[0042] The processor 118 can receive power from the power supply 102, and other components within the WTRU 102 Power supply 134 may be configured to distribute and / or control power to the conductor. Any suitable device for supplying power to TRU102 may be. For example, power supply 134 is This may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0043] The processor 118 provides location information about the current location of the WTRU 102 (e.g., longitude). It can also be coupled to a GPS chipset 136 which can be configured to provide (and latitude). In addition to, or instead of, information from GPS chipset 136, WTRU102 via air interfaces 115 / 116 / 117, to the base station (for example, base station 1 Location information is received from 14a, 114b) and / or from two or more nearby base stations. The location can be determined based on the timing of the signal being transmitted. WTRU102 is, Location information can be obtained through any preferred location determination method while remaining consistent with the embodiment. This will be understood.

[0044] Processor 118 provides additional features, functionality, and / or wired or wireless connectivity. This may include one or more software and / or hardware modules provided. It can be further coupled with other peripheral devices 138. For example, peripheral devices 138 may include an accelerometer, a bi Various sensors such as ometric (e.g., fingerprint) sensors, e-compasses, satellite transceivers, Digital camera (for photos or videos), Universal Serial Bus (USB) port or other interconnection interfaces, vibration devices, TV transmitters and receivers, hands-free headphones Doset, Bluetooth® module, frequency modulation (FM) wireless unit Digital music players, media players, video game player modules, and more. This may include internet browsers, etc.

[0045] WTRU102 is used in sensors, consumer electronics, smartwatches, or smart clothing, etc. Wearable devices, medical or e-health devices, robots, industrial equipment, drones , embodied in other devices or equipment such as vehicles like cars, trucks, trains, or airplanes. It is possible. WTRU102 may have one of the peripheral devices 138. Such devices or devices via one or more interconnection interfaces such as faces It can be connected to other components, modules, or systems of the vice.

[0046] Figure 1C is a diagram of the RAN103 and core network 106 according to one embodiment. Yes. As mentioned above, RAN103 employs UTRA wireless technology and an air interface. It can communicate with WTRU102a, 102b, and 102c via S115. RA N103 can also communicate with the core network 106. As shown in Figure 1C, RAN 103, respectively, connects to WTRU102a, 10 via air interface 115. Node-B140a, 1 may include one or more transceivers for communicating with 2b, 102c. May include 40b and 140c. Each of nodes B140a, 140b, and 140c is RA It may be associated with a specific cell (not shown) within N103. RAN103 is RNC14 2a and 142b may also be included. RAN103 remains consistent with the embodiment, and any number of no It will be understood that this may include Code-B and RNC.

[0047] As shown in Figure 1C, nodes B140a and B140b communicate with RNC142a. Obtain. In addition, node-B140c can communicate with RNC142b. Node-B140 a, 140b, and 140c are connected via the Iub interface to the individual RNC142a. It can communicate with 142b. RNC142a and 142b communicate via the Iur interface. They can communicate with each other. Each of RNC142a and 142b is an individual node to which it is connected. It can be configured to control D-B140a, 140b, and 140c. In addition, RNC1 42a and 142b each control external loop power, load, reception, and packet scheduling. Tühring, handover control, macro diversity, security features, data encryption It may be configured to perform or support other functionalities such as transformation.

[0048] The core network 106 shown in Figure 1C is connected to the media gateway (MGW) 144 Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SG) SN)148, and / or Gateway GPRS Support Node (GGSN)150 It may include the following. Each of the aforementioned elements is described as part of the core network 106, Any of these elements can be used by entities other than the core network operator. Therefore, it will be understood that it may be owned and / or operated.

[0049] RNC142a within RAN103 connects to the core network via the IuCS interface. It can be connected to MSC146 in workpiece 106. MSC146 is connected to MGW144. MSC146 and MGW144 are compatible with WTRU102a, 102b, and 102c. , provides access to circuit exchange networks such as PSTN108, WTRU102a, This can facilitate communication between 102b, 102c and conventional terrestrial communication devices.

[0050] RNC142a within RAN103 connects to the core network via the IuPS interface. It can also be connected to SGSN148 in workpiece 106. SGSN148 is connected to GGSN150. It can be connected to SGSN148 and GGSN150, WTRU102a, 102b 102c provides access to packet-switched networks such as the Internet 110. This facilitates communication between WTRU102a, 102b, 102c and IP-enabled devices. ru.

[0051] As described above, core network 106 is owned by other service providers and Network 112 which may include and / or other wired or wireless networks being operated It can also be connected to.

[0052] Figure 1D is a diagram of the RAN104 and core network 107 according to one embodiment. Yes. As mentioned above, RAN104 employs E-UTRA wireless technology and air interface It can communicate with WTRU102a, 102b, and 102c via face 116. RAN104 can also communicate with core network 107.

[0053] RAN104 may include eNode-B160a, 160b, and 160c, but RAN It is understood that 104 may include any number of eNode-B, as is consistent with the embodiment. It will be. Each of the eNode-B160a, 160b, and 160c is an air interface One of the devices for communicating with WTRU102a, 102b, and 102c via Face 116. The above transceivers may be included. In one embodiment, eNode-B160a, 160b, 1 60c can implement MIMO technology. Therefore, eNode-B160a can, for example, Using multiple antennas, the radio signal is transmitted to the WTRU102a, and from there the radio signal It can receive.

[0054] Each of eNode-B160a, 160b, and 160c is a specific cell (not shown). ) may be associated with, wireless resource management decisions, handover decisions, uplink and / Alternatively, it can be configured to handle user scheduling, etc., in the downlink. It is possible. As shown in Figure 1D, eNode-B160a, 160b, 160c are They can communicate with each other via the X2 interface.

[0055] The core network 107 shown in Figure 1D is a Mobility Management Gateway (MME). 162, Serving Gateway 164, Packet Data Network (PDN) This may include the network 166. Each of the aforementioned elements is part of the core network 107 and They are described as such, but any of these elements is the core network operator or It will be understood that it may be owned and / or operated by an external entity.

[0056] MME162 connects to eNode-B1 in RAN104 via the S1 interface. It can be connected to 60a, 160b, and 160c respectively, and acts as a control node. It is possible. For example, MME162 can recognize the user of WTRU102a, 102b, and 102c. Proof, Bearer activation / deactivation, WTRU102a, 102b, 102c initial MME162 may be responsible for selecting a specific serving gateway during the attachment period. It also supports RAN104 and other wireless technologies such as GSM® or WCDMA®. The technology provides control plane functionality for switching between other RANs (not shown) that employ the technology. It can be provided.

[0057] The serving gateway 164, via the S1 interface, connects to RAN104. It can be connected to eNode-B160a, 160b, and 160c, respectively. Serving Gateway 164 generally handles user data packets as WTRU102a, 102b, Routing and forwarding to / from 102c is possible. Serving gateway 164 is e User plane anchors and downlink data during Node-B handover are WTRU Paging triggers when available for 102a, 102b, and 102c, WT RU102a, 102b, and 102c also perform other functions such as context management and memory. It is possible.

[0058] Serving gateway 164 interacts with WTRU102a, 102b, and 102c. - Provides access to packet-switched networks such as Net 110, and WTRU102a PDN gateway that can facilitate communication between 102b, 102c and IP-enabled devices It can also be connected to 166.

[0059] The core network 107 can facilitate communication with other networks. For example, the core network Network 107 is used with WTRU102a, 102b, 102c, and PSTN108, etc. It provides access to the road switching network and follows WTRU102a, 102b, 102c and It can facilitate communication with the next-generation terrestrial communication device. For example, the core network 107, It serves as an interface between core network 107 and PSTN108. This includes an IP gateway (for example, an IP Multimedia Subsystem (IMS) server). It can be seen or communicated with. In addition, the core network 107 is WTRU10 2a, 102b, 102c are owned and / or operated by other service providers. Access to network 112, which may include other wired or wireless networks. It can be provided.

[0060] Figure 1E is a diagram of the RAN105 and core network 109 according to one embodiment. Yes. The RAN105 adopts IEEE 802.16 wireless technology and uses an air interface. Access to communicate with WTRU102a, 102b, and 102c via S117 It could be a Service Network (ASN). As will be discussed further below, Different functional entities and cores of WTRU102a, 102b, 102c, and RAN105 The communication link to network 109 can be defined as a reference point.

[0061] As shown in Figure 1E, RAN105 is connected to base stations 180a, 180b, and 180c. This may include the ASN gateway 182, but RAN 105 remains consistent with the embodiment. It will be understood that this may include any number of base stations and ASN gateways. Each of the local stations 180a, 180b, and 180c is associated with a specific cell within RAN105. And via air interface 117, WTRU102a, 102b, 102c It may include one or more transceivers for communication. In one embodiment, base station 180a, 1 80b and 180c can implement MIMO technology. Therefore, base station 180a can, for example Then, using multiple antennas, the wireless signal is transmitted to the WTRU102a, and from there the wireless signal The signal can be received. Base stations 180a, 180b, and 180c are handoff triggers, tunnel Establishment, wireless resource management, traffic classification, quality of service (QoS) policy enforcement, etc. It can also provide reliability management functions. The ASN gateway 182 serves as a traffic aggregation point. It can perform roles such as paging, subscriber profile caching, and core networking. They may be responsible for routing to Twerk 109, etc.

[0062] Air interface between WTRU102a, 102b, 102c and RAN105 117 can be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition Then, WTRU102a, 102b, and 102c each connect to the core network 109 and A logical interface (not shown) can be established. WTRU102a, 102b, 102 The logical interface between c and core network 109 is used for authentication, authorization, and IP hosting. Defined as an R2 reference point that can be used for configuration management and / or mobility management. It is possible.

[0063] The communication links between base stations 180a, 180b, and 180c are WTRU hands. See R8, which includes protocols for facilitating data transfer between overboard and base stations. It can be defined as a point. Base stations 180a, 180b, 180c and ASN gateway 18 The communication link between 2 and WTRU10 can be defined as the R6 reference point. The R6 reference point is WTRU10 Based on the mobility events associated with 2a, 102b, and 102c respectively, This may include protocols to facilitate tidal management.

[0064] As shown in Figure 1E, RAN105 can be connected to the core network 109. The communication link between RAN105 and core network 109 is, for example, used for data transfer and It can be defined as an R3 reference point that includes protocols for promoting mobility management capabilities. Core network 109 is Mobile IP Home Agent (MIP-HA) 184 This may include an authentication, authorization, and accounting (AAA) server 186 and a gateway 188. Each of the elements described is depicted as part of the core network 109, but these elements Any of ours are owned by entities other than the core network operator. It will be understood that it may be operated or run.

[0065] MIP-HA may be responsible for IP address management, including WTRU102a, 102b, etc. 102c and 102c roam between different ASNs and / or different core networks. This can make it possible to do so. MIP-HA184 is compatible with WTRU102a, 102b, and 102 c provides access to packet-switched networks such as the Internet 110, and WT This can facilitate communication between RU102a, 102b, 102c and IP-enabled devices. Server A 186 may be responsible for supporting user authentication and user services. Gateway 188 can facilitate interaction with other networks. For example, Gateway 188 connects to WTRU102a, 102b, and 102c, and PSTN10 It provides access to the circuit exchange network, including WTRU102a, 102b, and 10 This can facilitate communication between 2c and conventional terrestrial communication devices. In addition, gateway 188 WTRU102a, 102b, 102c are owned by other service providers Network 11 which may include other wired or wireless networks that are called and / or operated It may provide access to 2.

[0066] Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point. Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point. Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point. Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point. Although not shown in FIG. 1E, RAN 105 can be connected to other ASNs, and it will be understood that core network 109 can be connected to other core networks. The communication link between RAN 105 and other ASNs may include a protocol for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs and can be defined as an R4 reference point. The communication link between core network 109 and other core networks may include a protocol for facilitating interworking between the home core network and the visited core network and can be defined as an R5 reference point.

[0067] The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A, 3B, 3C, 3D, and 3E are provided as an example only, and the subject matter disclosed and claimed herein can be embodied or implemented in any similar communication system, whether currently defined or defined in the future. The core network entities described herein and illustrated in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in a certain existing 3GPP specification. However, in the future, those entities and functionalities may be identified by other names, and it is understood that an entity or function may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Therefore, the specific network entities and functionalities described and illustrated in FIGS. 3A,​​​​​​​​​​​​​, PSTN108, Internet110, or some other network112 Communication networks, such as those shown in Figures 1A, 1C, 1D, and 1E, which are either functional entities or other entities. Exemplary computing system 90 in which one or more devices of the network can be embodied This is a diagram of a lock. The computing system 90 includes a computer or server. The acquisition mainly concerns the location or means by which such software is stored or accessed. Moreover, it is controlled by computer-readable instructions, which may be in the form of software. Such computer-readable instructions can be found in computing system 9. It can be executed within processor 91 to run 0. Processor 91 is a general-purpose processor Processor, special-purpose processor, conventional processor, digital signal processor (DSP), Multiple microprocessors, one or more microprocessors associated with a DSP core, Torola, microcontrollers, application-specific integrated circuits (ASICs), field processing FPGA (FPGA) circuits, any other type of integrated circuit (IC), state It could be a machine, etc. The processor 91 performs signal coding, data processing, power control, input / output The power processing and / or computing system 90 operates within a communication network. The coprocessor 81 may implement any other functionality that makes it possible to do so. Whether it can fulfill the role, or whether it can support the processor 91, a different discretion from the main processor 91 The processor is a processor. Processor 91 and / or coprocessor 81 are disclosed herein. The methods and apparatus shown may receive, generate, and process data related to them.

[0069] During operation, processor 91 fetches, decodes, and executes instructions, and computes Information is transmitted to other resources via the system bus 80, which is the main data transfer path of the system. To, and from there, transfer. Such a system bus is a computing system The system bus connects the components within the M90 ​​and defines the medium for data exchange. 80 is typically a data line for sending data and a line for sending addresses. The address line, for sending interrupts, and for operating the system bus. It includes control lines. An example of such a system bus 80 is PCI (peripheral components It is a bus (interconnection).

[0070] The memory connected to the system bus 80 includes random access memory (RAM) 82, It includes read-only memory (ROM) 93. Such memory stores and reads information. Includes circuitry that allows it to be extracted. ROM93 is generally easy to modify. This includes stored data that cannot be processed. Data stored in RAM82 is processed by processor 9 It may be read or modified by one or another hardware device. Yes, it is possible. Access to RAM82 and / or ROM93 is via the memory controller 92. It can be controlled by the memory controller 92 when an instruction is executed, the virtual address It can provide an address translation function that converts to a physical address. The memory controller 92 Notes on isolating processes within the system and separating system processes from user processes. It may also provide protection functions. Therefore, a program that starts in the first mode may itself Only memory mapped by the process's virtual address space can be accessed. Unless memory sharing between processes is configured, it is not possible to access memory within the virtual address space of another process.

[0071] In addition, computing system 90 may include a peripheral device controller 83 responsible for communicating instructions from processor 91 to peripheral devices such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[0072] A display 86 controlled by a display controller 96 is used to display visual output generated by computing system 90. Such visual output may include text, graphics, video graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes electronic components required to generate video signals transmitted to the display 86.

[0073] Furthermore, computing system 90 connects computing system 90 to an external communication network such as the RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112 of FIGS. 1A, 1B, 1C, 1D, and 1E, enabling computing system 90 to communicate with other nodes or functional entities of those networks. It may include, for example, a communication circuit such as a network adapter 97, which can be used in this purpose. This may be used alone or in combination with the processor 91 in a device described herein, It can be used to carry out the transmission and reception steps of a code or functional entity. .

[0074] Any of the apparatus, systems, methods, and processes described herein or It all boils down to computer-executable instructions stored on a computer-readable storage medium. It can be embodied in the form of (for example, program code), and its instructions are to the processor 118 When executed by a processor such as 91, the processor receives the following instructions as described herein. It is understood that a system, method, and process should be implemented and / or put into practice. Specifically, any of the steps, operations, or functions described herein may be used in this context. It is implemented in the form of computer executable instructions, such as wireless and / or wired networks. On the processor of a device or computing system configured for network communication It is possible. Computer-readable storage media can store information in any non-transient manner. Volatile and non-volatile substances implemented by tangible or physical methods or techniques. Media, including both removable and non-removable media, but such computers A readable storage medium does not contain signals. A computer-readable storage medium is RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROI M, Digital Multipurpose Disc (DVD) or other optical disc storage device, magnetic cassette A magnetic tape, magnetic disk storage device or other magnetic storage device, or desired information It can be used to store information and can be accessed by a computer system. This includes, but is not limited to, any other tangible or physical medium through which it can be transmitted. stomach.

[0075] As shown in Figure 2A, in LTE, the terminal is LTE-RRC_CONNECTED And RRC_IDLE can be in two different states. RRC_CON NECTED has a Wireless Resource Control (RRC) context. User Equipment (UE) The cell to which the UE belongs is identified, and the UE is identified, i.e., the signal between the UE and the network The Cell Radio Network Temporary Identifier (C-RNTI) used for ringing purposes is configured It is done. RRC_CONNECTED is intended for data transfer to / from the UE. It will be done.

[0076] Furthermore, RRC_IDLE has RRC components within the Wireless Access Network (RAN). There is no text, and the UE does not belong to a specific cell. Any data transfer is RRC_ This cannot be done in IDLE. In RRC_IDLE, the UE monitors the paging channel. It monitors and detects changes in incoming calls and system information. Discontinuous reception (DRX) is UE Used to conserve power. When transitioning to RRC_CONNECTED, RRC The context needs to be established in both the RAN and UE.

[0077] System information (SI) is for the Advanced Universal Terrestrial Radio Access Network (EU) This is information broadcast by TRAN, and it is active within the network. It needs to be acquired by the UE so that it can be set and operate. SI is, Master Information Block (MIB) and several systems It is divided into mInformationBlocks (SIBs). MIBs and SIBs Level descriptions are provided in 3GPP TS36.300. Detailed descriptions are provided in 3GPP T It is available in S36.331. Table 1 provides some MIB and SIB information. .

[0078] [Table 1] Physical Random Access Channel (PRACH) configuration and general randomness within the system The access parameters are PRACH-Config and RA of SIB2 as shown below. This is defined within CH-ConfigCommon IE. RACH-ConfigCommon IE

[0079] [Table 1-1] PRACH-Config Information Elements

[0080] [Table 1-2] Figure 2B illustrates the system information acquisition procedure. Here, the UE is 3GPP Apply the system information acquisition procedure described in TS 36.331 to E-UTRA The access layer (AS) and non-access layer (NAS) relationship broadcast by N The procedure retrieves system information for UE and RR in RRC_IDLE. This applies to UE in C_CONNECTED.

[0081] The UE applies the system information acquisition procedure for the following instances: (i) When a cell is selected (for example, when the power is turned on), and when a cell is re-selected. (ii) After handover is complete (iii) After entering E-UTRA from another radio access technology (RAT) (iv) When returning from outside coverage (v) When a notification is received that system information has changed. (vi) ETWS notification, CMAS notification, and / or EAB parameter changes When receiving instructions regarding the existence of such a notification (vii) When a request is received from the upper layer of CDMA2000 (viii) When the maximum effective duration is exceeded.

[0082] Section 10.6 of 3GPP 36.300 describes the measurement models currently used in LTE. Define the model. This model is shown in Figure 3.

[0083] A: Measurement (sample) inside the physical layer.

[0084] Layer 1 filtering: Internal layer 1 filtering of the input measured at point A. Filtering is implementation-dependent. Measurement is implemented (input A and layer 1 filtering). The way in which this is actually performed within the physical layer is not constrained by the standard. Measurement A below -D will, in turn, be discussed below.

[0085] B: Measurements reported to layer 3 by layer 1 after layer 1 filtering.

[0086] Layer 3 filtering: Filtering performed on the measurement provided at point B. Layer 3 The filter behavior is standardized, and the layer 3 filter configuration is provided by RRC signaling. The filtering reporting cycle in C is equal to one measurement cycle in B.

[0087] C: Measurement after processing within the Layer 3 filter. The reporting rate is the same as the reporting rate in B. This measurement is used as input for the evaluation of one or more reporting criteria.

[0088] Evaluation of reporting criteria: This checks whether an actual measurement report is required at point D. To evaluate, for example, two measurements at reference point C are used to compare different measurements. It can be based on more than one flow, which is illustrated by inputs C and C'. UE evaluates the reporting criteria each time new measurement results are reported at points C and C'. It shall be deemed worthy. The reporting standards are standardized, and the structure is RRC signaling (UE measurement). Provided by [company name].

[0089] D: Measurement report information (message) transmitted over the wireless interface.

[0090] Layer 1 filtering will introduce a certain level of measurement averaging. UE is required. The method and time for accurately performing the measurement are as follows: the output at B is 3GPP TS 36. 133,Requirements for support of radio re Source Management (Release 13), V13.2.0 The implementation will likely be specific to the point where the performance requirements set out are met. The settings and parameters are specified in 3GPP TS 36.331, and the difference between B and C is No delay will be introduced to the availability of the sample. Measurements at points C and C' will be used in the event evaluation. This is the input used for valuation.

[0091] Layer 2 is 3GPP 36.300 [3GPP TS36.300, Overall d [Description;Stage2(Release13),V13.3.0] Therefore, it is divided into the following sublayers: Media Access Control (MAC), Wireless Link Control RLC and Packet Data Convergence Protocol (PDCP). Downlink and The PDCP / RLC / MAC architectures for the uplink are shown in Figure 4, respectively. This is shown in Figure 5.

[0092] The physical layer random access preamble shown in Figure 6 is a TCP cyclic prefix of length It consists of a sequence portion of the length TSEQ and the Parameter value is the "Error" below. Listed under "!Reference not found", frame structure and random access It depends on the configuration. The upper layers control the preamble format.

[0093] [Table 2] Figure 6 illustrates the PRACH resource definition.

[0094]

number

[0095]

number

[0096] k0 corresponds to the first resource element (RE) of the PRACH resource.

[0097]

number

[0098]

number

[0099] In the uplink, the carrier frequency f0 is centered between the two UL subcarriers.

[0100] The random access preamble is as described in 3GPP TS 36.211. , generated from one or more root Zadoff-Chu sequences. The work consists of a set of preamble sequences that the UE can use. Starting with the configured root sequence index, 64 are available within each cell. There are several preambles. The UE is the maximum number of cycles that can be made for each root sequence. Assign a ring shift, and then, until all 64 preambles are identified, proceed to the next logical loop. This set of preambles is identified by proceeding to the `sequence` sequence.

[0101] The u-th root Zadoff-Chu sequence is defined as follows:

[0102]

number

[0103] [Table 3] From the u-th root Zadoff-Chu sequence, zero correlation zoon of length NCS-1 The random access preamble with is defined by a cyclic shift as follows .

[0104]

Number

[0105]

Number

[0106]

Number

[0107] NCS ≤ d u < For NZC / 3, the parameters are obtained as follows.

[0108]

Number

[0109]

Number

[0110] The baseband PRACH signal is a time-continuous signal as defined in 3GPP TS 36. Defined by 211.

[0111]

number

[0112] βPRACH is an amplitude multiplier used in power control.

[0113] NZC is the length of the Zadoff-Chu sequence.

[0114] xu,v(n) is the length with root u and cyclic shift v -NZC Zadoff- This is a Chu sequence.

[0115] • The fixed offset determines the frequency location of the preamble within its assigned PRB. It is a set.

[0116] K = Δf / ΔfRA is the sub-carriage between the RACH preamble and uplink data transmission. This explains the difference in transmission interval.

[0117]

number

[0118] Random access baseband parameters ΔfRA and · are "Error! Reference source not found". It is defined as "cannot be found".

[0119] [Table 4] In LTE, random access procedures are performed for the following events: Initial access from RRC_IDLE; RRC connection re-establishment procedure; Handover; DL data in RRC_CONNECTED requesting a random access procedure Incoming call; For example, when the UL synchronization status is "not synchronized"; UL data in RRC_CONNECTED requesting a random access procedure Incoming call; For example, if the UL synchronization status is "not synchronized" or if there are no available SRs When there are no PUCCH resources available; Position within RRC_CONNECTED when requesting a random access procedure For the target; For example, when timing advance is required for UE positioning.

[0120] Random access procedures can take two different forms: Contention-based (applicable to the first 5 events); Non-contention-based (handover, DL data incoming, positioning, and secondary typing) To obtain timing advance alignment for the ming advance group (sTAG) (Applicable only to [specific group / group]).

[0121] Contention-based random access employs the procedure shown in Figure 8. .

[0122] Step 1 in Figure 8 shows the random access preamble on RACH in the uplink. Let's explain the process. Here, the transmission of the RACH preamble is the transmission timing of the eNB to the UE. This makes it possible to estimate the value.

[0123] Step 2 in Figure 8 shows the random access response generated by MAC on DL-SCH. Let me explain the answer. Here, the network adjusts the timing of UE transmission. It transmits advanced commands. Furthermore, the network is used in step 3 below. Allocate the necessary UL resources to the UE.

[0124] Step 3 in Figure 8 illustrates the first scheduled UL transmission on UL-SCH. The transmission of mobile device identification to the network will utilize UL-SCH.

[0125] Step 4 in Figure 8 explains contention resolution on DL. Message transmission occurs from the network to the UE on the DL-SCH.

[0126] Contention-free random access, downlink data incoming, handover, And it is used only to re-establish uplink synchronization during positioning. In this case, Only the first two steps of the above procedure are applicable. This is because When executing a random access procedure that does not include contention resolution, Because it is not necessary. Random access procedures from the perspective of the PHY and MAC layers. For more detailed explanations, please refer to 3GPP TS 36.213 and 3GPP TS 36.213, respectively. It is available on 36.321.

[0127] Random access response is a random access response permission [3GPP TS 36.213] This includes a 20-bit UL permission called ]. These start from the MSB and end from the LSB. The 20-bit content is as follows: Hopping flag -1 bit Fixed-size resource block allocation - 10 bits Shortened modulation and encoding scheme - 4-bit TPC command for scheduled push - 3 bits.

[0128] Physical layer measurements are defined in 3GPP TS 36.300 as shown below.

[0129] Physical layer measurements that support mobility are classified as follows: Within E-UTRAN (within frequency range, between frequencies); Between E-UTRAN and GERAN / UTRAN (between RATs); Between E-UTRAN and non-3GPP RAT (3GPP access system mobility) ).

[0130] For measurements within E-UTRAN, two basic UE measurement quantities are supported. do: Reference Signal Received Power (RSRP); Reference signal reception quality (RSRQ).

[0131] In addition, the following UE measurement quantities may be supported: Received Signal Strength Indicator (RSSI); Reference signal-to-noise ratio and interference ratio (RS-SINR).

[0132] RSRP measurement is based on the following signals: Cell-specific reference signal; or, The CSI reference signal within the configured detection signal.

[0133] In LTE, multi-antenna transmission, as shown in Figure 9, is performed from the output of the data modulation. This can be described as mapping to different antenna ports [4G LTE / L TE-Advanced for Mobile Broadband,Erik Da hlman,Stefan Parkvall,and Johan Skold,Ac [Ademic Press, ISBN: 978-0-12-385489-6]. Ante The input to the mapping is a modulation scheme corresponding to one or two transport blocks. Includes VOL (QPSK, 16QAM, 64QAM). The output of the antenna mapping is for each This is a set of symbols for antenna ports. The symbol for each antenna port is followed by O This applies to FDM modulators. Therefore, it is the basic OF corresponding to its antenna port. It is mapped to a DM time-frequency grid.

[0134] Different multi-antenna transmission methods correspond to different so-called transmission modes. These are 10 different transmission modes defined for antenna mapping. Although they differ in terms of their physical structure, the reference signals assumed to be used for demodulation (each, a cell (Specific reference signals or demodulated reference signals) and the CSI feedback on which they depend From the perspective of the ipu (a type of hopping instrument), it is also different.

[0135] The following list shows the transmission modes defined for LTE and the associated multi-channels. Summarize the antenna transmission method: Transmission mode 1: Single antenna transmission Transmission Mode 2: Transmission Diversity Transmission Mode 3: Open-loop codebook-based precoding for two or more layers Transmission diversity in the case of rank 1 transmission Transmission Mode 4: Closed-loop codebook-based precoding Transmission Mode 5: A multi-user MIMO version of Transmission Mode 4 Transmission Mode 6: Closed-loop codebook-based precoding limited to single-layer transmission. Special cases Transmission Mode 7: Release 8 non-codebook-based preprocessor that supports single-layer transmission only. Reading Transmission Mode 8: Release 9 non-codebook-based preprocessor supporting up to two layers. Reading Transmission Mode 9: Release 10 non-codebook-based preamplifier supporting up to 8 layers. coding Transmission Mode 10: Also known as CoMP, this is a different method of downlink multipoint coordination and transmission. Release 11 extension of transmission mode 9 for enhanced support of stages.

[0136] (NR beam-formed access) Currently, 3GPP standardization efforts are working to create a framework for beamformed access. Design is underway. The characteristics of radio channels at higher frequencies are that LTE This is significantly different from the currently deployed channels below 6GHz. A major challenge in designing new radio access technologies (RATs) is greater path loss. This will overcome the problem. In addition to this greater path loss, higher frequencies result in poor performance. It is subjected to an unfavorable scattering environment due to interference caused by diffraction. MIMO / beamforming ensures sufficient signal levels at the receiver end. It is essential.

[0137] Used by digital BFs to compensate for additional path loss at higher frequencies. Relying solely on MIMO digital precoding is problematic when the frequency is below 6GHz. It is considered insufficient to provide similar coverage. Therefore, additional benefits are needed. The use of analog beamforming to achieve this, in conjunction with digital precoding, It can be a substitute. A sufficiently narrow beam is formed using many antenna elements. This is likely to be very different from what is assumed for LTE evaluation. Due to the high beamforming gain, the beam width tends to decrease accordingly, and therefore, A beam with directional antenna gain, specifically in a 3-sector configuration, has a horizontal sector It is not possible to target the entire rear. The limiting factor for the number of simultaneous high-gain beams is the transmitter / receiver. —Including the cost and complexity of the architecture.

[0138] From these observations above, a narrow serving area can be manipulated to target different serving areas. Multiple transmissions in the time domain using coverage beams are necessary. Essentially, The analog beams of the subarray are OFDM symbols or different serving areas within the cell. Time in any appropriate time interval unit defined for the purpose of beam steering across A It can be steered in a single direction with inter-axis resolution, and therefore the number of subarrays , time interval units defined for the purpose of each OFDM symbol or beam steering Determine the number of beam directions and corresponding coverage in the field. In one document, this objective is stated. Providing multiple narrow coverage beams for analog purposes is called "beam sweeping." For hybrid beam formation, beam sweeping provides basic coverage in NR. This is considered essential for providing. This concept is illustrated in Figure 10, and sector-level cells. The coverage is achieved using a sector beam and multiple high-gain narrow beams, massive For analog and hybrid beamforming using MIMO, different serving In the time domain, using a narrow coverage beam that is directed to target an area Multiple transmissions target the entire coverage area within the serving cell in NR. It is essential for [something].

[0139] One concept closely related to beam sweeping is the concept of beam pairing. The ring is used to select the best beam pair between the UE and its serving cell. Therefore, the best beam pair can be used for control signaling or data transmission. For downlink transmission, the beam pair consists of the UE RX beam and the NR node TX. While it will consist of beams, for uplink transmission, the beam pair will be UE TX It will consist of a beam and an NR node RX beam.

[0140] Another related concept is beam training, which is used for beam refinement. For example, as shown in Figure 10, beam sweep and sector beam pairing procedures In this case, a coarser sector beam formation may be applied. Then, beam training continues. For example, the antenna weight vector may be refined, and then between the UE and the NR node The pairing of high-gain, narrow-beam systems continues.

[0141] C-plane latency in LTE-Advanced is 3GPP TR 36.9 This is documented in 12. Figure 12 shows RRC_IDLE to RRC_CONNECTED The transition to [this state] is illustrated.

[0142] [Table 5] NAS configuration is performed in parallel with RRC configuration. Therefore, NAS latency is (status The total delay of steps 11-14 is less than or equal to the total delay of steps 7-10. (Assuming this is the case) it does not appear in the total.

[0143] IMT for 2020 and beyond will continue beyond the current IMT. It is intended to expand and support a diverse range of usage scenarios and applications. These offer a wide range of capabilities for IMT for 2020 and beyond. It will be tightly coupled with different intended use scenarios and applications.

[0144] The usage scenarios for IMT for 2020 and beyond include: eMBB (Enhanced Mobile Broadband) Macro and small cells 1 millisecond latency (air interface) Allocated in WRC-15, which could result in an additional throughput of up to 8 Gbps. spectrum Support for high mobility URLLC (Highly reliable and low-latency communication) Low to medium data rates (50kbps to 10Mbps) <1 millisecond air interface latency 99.999% reliability and availability Low connection establishment wait time Mobility from 0 to 500 km / hour mMTC (Massive Machine Type Communication) Low data rate (1-100kbps) High density of devices (up to 200,000 / km) 2 ) Waiting time: from a few seconds to several hours Low power consumption: Up to 15 years of battery autonomy asynchronous access Network operation Network slicing, routing, movement and interworking, energy —Network operations addressing themes such as cost savings, etc.

[0145] 3GPP TR 38.913[3GPP TR 38.913,Study on Scenarios and Requirements for Next Gene ration Access Technologies;(Release14),V 0.3.0 defines scenarios and requirements for next-generation access technologies. eMBB Key performance indicators (KPIs) for URLLC and mMTC devices are shown in the table. This is summarized in section 6.

[0146] [Table 6] (Network slicing) Figure 13 below provides a high-level diagram illustrating the concept of network slicing. Network slices are logical networks that support the communication service requirements of specific use cases. It consists of a set of work functions. For example, based on subscription or device type, The terminal is directed to the selected slice in a way that meets the operator's or user's needs. It is assumed that this is possible. Network slicing primarily involves dividing the core network. The target is the wireless access network (RAN), but the RAN has multiple slices or different NETs. It is necessary to have specific functionality to even support resource splitting for network slicing. Anything that could be considered essential is not excluded.

[0147] The beam sweep frame structure includes a beam sweep subframe consisting of multiple sweep slots. Each sweep slot can consist of one or more OFDM symbols.

[0148] Uplink (UL) sweep slots and downlink (DL) within the beam sweep subframe A method for associating sweep slots can be used. Sweep subframe information The element (IE) may be used to signal a swept subframe configuration.

[0149] A procedure for performing cell selection within a beam-sweeping NR network is described. ru.

[0150] A mechanism for triggering the transmission of other SIs based on the detection of a random access preamble. The structure is explained. Other SIs are on all DL beam / DL sweep slots, or DL It can be broadcast on some of the beam / DL sweep slots.

[0151] Here, the new RAT(NR) beamforms for control information such as initial access information. It is also a common belief that it will be used. Therefore, in this disclosure, control information A random access procedure assuming beam formation is also disclosed.

[0152] Wireless Access Network (RAN) slicing is being considered in NextGen It is proposed to support a diverse set of use cases and requirements. RAN slide The RAN configured for Singh supports multiple numerology, as shown in Figure 14. Furthermore, each numerology can be optimized for the services offered by the slice.

[0153] For illustrative purposes, eMBB numerology, primarily based on LTE, i.e., 15kHz sub-transmission The transmission interval and 1 millisecond subframe can be assumed. (See Figure 14) Numerology for MTC and UR / LL slices then says, "Error! Reference not found." It will be defined as shown in "not." However, its use is in numerology. It does not require that any of these be based on LTE numerology. The application is subcarrier interval and It is only used for network configurations where the subframe durations are integer multiples of each other. It is not restricted by that.

[0154] [Table 7] A new configuration for PRACH resources, steps in random access procedures It can be used for the transmission of the preamble in 1. PRACH-Config And extensions to RACH-ConfigCommon IE, for example, via SIB2 Then, using broadcast or dedicated signaling, as part of the system information, It is then regulated, which defines the PRACH configuration, RAN slicing and / or A RAN configured to support multiple use cases / services with different requirements. When performing random access procedures within the UE, it is used to control the behavior of the UE. It is possible. A new way to implement random access using the new PRACH resource. However, it can be used.

[0155] (Common PRACH resource) This section defines the common PRACH resource. Open the random access procedure. When starting, the UE uses a common PRACH resource and the data supported by the UE. Regardless of the type of service and / or service, the random access preamble is transmitted. Send. Used to execute the remaining steps of the random access procedure. The source is selected based on the device type and / or the requested service. This is possible. For RANs that support mMTC, eMBB, and UR / LL slices. An exemplary embodiment of the common PRACH resource used is shown in Figure 15.

[0156] In this embodiment of the present invention, a common PRACH resource (one or several PRACH The resource subband (which can be a resource subband) is configured within the eMBB slice, and each PRA The CH resource subband has K eMBB PRBs in the frequency domain, time domain In the INDEX, there are L eMBB(OFDM) symbols (L symbols are one subframe). It occupies (which may be more than 100%) of the available slices. However, the present invention is of the available slices Supports the configuration of a common PRACH resource among any of the following.

[0157] As an alternative, the numerology of the common PRACH resource (subcarrier interval, symbol length, etc.) is shared Can the PRACH resource be extended to the numerology of the slices that make up the resource, or Different numerology can be used (i.e., slices in which a common PRACH resource is composed) (Not based on numerology).

[0158] The common PRACH resource uses TDM and FDM to determine the remaining litho within the slice. It can be multiplexed with the common PRACH resource subband. Subcarrier interval, symbol length, etc. are applicable to all use cases (eMBB, mMTC, UR / L). It may differ from the numerology used by L, etc., and their corresponding resource slices. .

[0159] The slice used for common PRACH resources is determined by the network operator. This can be determined by the deployment scenario, supported services, and the number of different slices. It may depend on esoteric arts, etc. For example, in some scenarios, traditional LTE numerology (i.e. Using Δf=15kHz, T subframe=1ms, common PRA within slice It may be advantageous to configure CH resources. Alternatively, a common PRACH resource can be used. A narrower subcarrier interval may be advantageous for supporting low-complexity IoT devices. To support slices that use longer subframes, or low-latency devices Within a slice that uses a wider subcarrier interval / shorter subframe, which may be advantageous, It can be constructed.

[0160] The first physical resource block allocated to the common PRACH resource subband

[0161]

number

[0162]

number

[0163]

number

[0164]

number

[0165] As an alternative,

[0166]

number

[0167] The bandwidth of common PRACH resources that can be represented within the numerology-dependent PRB is also It can be signaled within the system information. In one embodiment, it is called PRACH-BW. The new IE may be used to signal the bandwidth of common PRACH resources. The exemplary PRACH-Config IE is as shown below, PRACH- Extended to include rice and PRACH-BW IE. And maxSLICES is defined as 3. However, its use is for any number of slices It can be used with rice. Extended PRACH-ConfigInfo IE

[0168] [Table 7-1] For LTE, the subcarrier interval of the random access preamble, i.e., ΔfRA This is 1.25kHz for preamble format 0-3, preamble format It is defined as 7.5kHz for T4. It uses a different numerology than the conventional LTE numerology. For a given slice, one option for defining ΔfRA is the ratio (Δf / Δ This involves expanding the LTE value by a multiple equal to f0), where Δf is the value of a given slice. This is the subcarrier interval, and Δf0 = 15kHz is the subcarrier interval for LTE. For small cell deployment scenarios where cyclic prefixes are used, the PRACH resource The duration can be expanded or contracted by the reciprocal of this multiple. "Error! Reference not found." "Sen" shows an exemplary common PRACH resource configuration for the described NR numerology, and Preamble format AE corresponds to LTE preamble formats 0-4, respectively. Based on this, in Table 8, the numerology of the eMBB slice corresponds to the LTE numerology. BW also corresponds to M When expressed in Hz, it depends on the numerological specific PRB definition and subcarrier interval.

[0169] [Table 8] Physical random access preambles use cyclic prefixes and preamble sequences. It consists of the interval portion. Compared to LTE, it is the length of the cyclic prefix (TCP) and the prefix. The length of a dumble sequence (TSEQ) is given by the base time unit, i.e., Ts = 1 / (150 Defined in terms of 00 x 2048 seconds. TCP values ​​used for different formats. This depends on the deployment scenario, for example, macrocells, small cells, and using different numerology. It does not need to be changed. However, the TSEQ value depends on numerology, therefore Therefore, the size should be appropriately determined for the slice to which the common PRACH resources are allocated. It is.

[0170] Preamble sequence length (TSEQ) is the length of the cyclic prefix, preamble, and The combined duration of the protection period is the duration of the PRACH resource in the time domain. It should be defined as follows: The duration of the protection period is cyclic prefix It is also optimal when it is approximately equal to the duration of the cus. Therefore, for several developments TSEQ for different numerology systems simply extends the duration of common PRACH resources. It may not be possible to scale an object by the same multiple used to reduce it. Furthermore, in scenarios where large cyclic prefixes are used, a common PRACH resource This may need to be extended into additional symbols and adapted to larger cyclic prefixes. Alternatively, the definition of the common PRACH resource is extended in the frequency domain, and This allows the same amount of information to be signaled using a shorter sequence length. It can be made possible.

[0171] In LTE, prach-ConfigIndex IE is preamble format The signaling of subframes that enable random access preamble transmission. It is used to configure the common PRACH resource. Similar mechanisms use this information. It can be used for signaling. This index is for reference construction. It can be used to determine the parameters, and it is a common PRACH resource Depending on the numerology of the slices that make up the structure, numerology-dependent scaling by UE may be required. .

[0172] For illustrative purposes, the parameters of the reference configuration are those defined for LTE. It can be handled. And the numerology of the eMBB slice is the same numerology as the reference configuration. In some cases, namely assuming it is based on LTE, the parameters of the reference configuration are directly It can be used. The configuration of the common PRACH resource shown in Figure 15-19 is as follows: Then, configuration indices as described in Table 5.7.1-2 of 3GPP TS 36.211 Subframe 6, that is, the preamble that occurs in subframes 1 and 6 of all frames. Signaling can be performed using format 0.

[0173] If a common PRACH resource is configured instead for mMTC slices, the configuration INDEX 6 will still be signaled to UE. However, "Era mMTC for preamble format A shown in "Reference source not found". The parameters will be applied.

[0174] The occurrence of the common PRACH resource for the example discussed in the previous paragraph is identical, that is, However, this occurs in subframes 1 and 6 of all frames. The duration of the m depends on the numerology of the slice, so the PRACH resource within each slice The periodicity of the numerology is not identical. "Error! Reference not found" is an example of NR numerology. This shows the periodicity of the common PRACH resources corresponding to configuration index 6 for the procedure.

[0175] [Table 9] In the example above, prach-ConfigIndex IE corresponds to the reference configuration. Used to signal the DEX. How this configuration is interpreted by the UE. This depends on the numerology of the slices in which the common PRACH resource is composed, i.e., UE is Perform any numerology-dependent scaling of the corresponding parameters that may be required.

[0176] As an alternative, the preamble format is also used in numerology. It is defined in such a way that it is implied. For example, the old preamble formats 0-4 are L It can be used for slicing based on TE numerology. Additional preamble formats are available. For supported numerology, it can be defined, for example, the preamble format 5-9 is , can be defined for slices based on exemplary mMTC numerology, preamble format Slices 10-14 may be defined for each slice based on exemplary UR / LL numerology. The implicit NR preamble format is shown in "Error! Reference not found". The definition of the PRACH configuration index then results in "Error! Reference not found". This includes configurations 64-191 as shown, and numerology-dependent random access configurations as signal It could be extended to provide support for ringing.

[0177] [Table 10] The preamble format defined in this table is one in which the PRACH resource has six PRBs. Assume that it occupies. However, the present invention assumes that PRACH occupies any number of PRBs It also supports defining a new preamble format that is configured in this way.

[0178] [Table 11-1]

[0179] [Table 11-2]

[0180] [Table 11-3] (Common PRACH resources to support mixed numerology) In the above embodiment, the common PRACH resource is configured as follows: It is configured to use a single random access subcarrier, which is consistent with the numerology of the slice. It was assumed that this would be done. Alternatively, the common PRACH resource would be used for multiple random access The subcarrier interval, for example, can be configured for simultaneous support of mixed numerology, and This enables the UE to support random access subcarriers for preamble transmission. It allows the use of any of the wave intervals. The UE then uses a common PRAC. Regardless of the numerology of the slices in which the H resource is composed, device type and / or It is possible to use a random access subcarrier interval optimized for service requests. It is likely that supporting this feature within the network will be done by the UE. This can reduce the number of random access subcarrier intervals that need to be supported, U The complexity of E can be reduced, for example, mMTC devices can use ΔfRA, mMTC It may only be required to support =0.625kHz.

[0181] In one embodiment, the common PRACH resource is the broadest BW random access preamplifier. A sufficiently wide BW to adapt to numerology involving Bull, and the longest-lasting random accessory. It would consist of a sufficiently long duration to be suitable for numerology involving spurious bills. U. When using the exemplary NR preamble numerology described above, this is frequency dominance. In the input, there are six UR / LL PRB or 2.16MHz BW, time domain This would correspond to one mMTC subframe or a duration of 2 milliseconds. The common PRACH resource, as shown in Figure 22, consists of four mMTCs. PRACH resource, 4 eMBB PRACH resources, 4 UR / LL P It should be possible to support RACH resources simultaneously.

[0182] The operator, based on network requirements and the expected RACH intensity of a given service, It would be possible to configure the PRACH resources used. For example, to ensure low latency. To do this, the operator can configure four UR / LL PRACH resources. Furthermore, if the density of mMTC devices is low, only one or two of the mMTC resources may be available. However, it can be configured as follows: 1 mMTC PRACH resource, 2 eMBB PRACH Common PRAC supports resources and four UR / LL PRACH resources. The H resource configuration is shown in Figure 23.

[0183] Furthermore, PRACH resources can be "stacked" in the frequency domain. Figure 24 shows , two "stacked" mMTC PRACH resources, two eMBB PRACH resources , and an exemplary common PRACH resource that supports four UR / LL PRACH resources The source code structure is shown.

[0184] In the example above, the additional PRACH resource can be configured to increase capacity. Yes, it is possible. Alternatively, additional PRACH resources can be used to improve reliability rather than capacity. Alternatively, it can be used to increase coverage. For example, additional UR / LL PRA CH resources are used for redundant transmission of random access preambles by UR / LL devices. It is used, thereby potentially increasing the probability of preamble detection. Redundancy is the same as This can be implemented using repetition of a leamble sequence, or by allowing a preamble. Different sets of preambles from the set of subframes may be used. Redundancy is achieved through consecutive subframes. Using PRACH resources within the system in the time domain, or "stacked" PRACH It can be implemented in the frequency domain using H resources. Alternatively, the UE can be each P A preamble can be randomly selected for a RACH opportunity, which means that the UE can perform multiple simultaneous RACHs. will result in performing a random access procedure. The UE will then continue to execute the procedure in which a random access response (RAR) has been received. If multiple RARs are received, the UE may optionally continue multiple random access procedures. <##

[0185] (Slice-specific PRACH resources) In this section, the use of slice-specific PRACH resources for each slice is described. The UE selects a PRACH resource from the appropriate slice based on the device type and / or service requirements. The resources from the selected slice can then be used for the random access procedure, i.e., the completion of steps 1 - 4 in FIGS. 20, 23, and 24. Exemplary embodiments of slice-specific PRACH resources for networks supporting mMTC, eMBB, and UR / LL slices are shown in FIG. 19.

[0186] In this embodiment of the invention, each slice-specific PRACH resource (which can be one or several PRACH resource sub-bands) is shown to occupy K = 6 PRBs in the frequency domain of the corresponding slice and L = 1 (OFDM) i i symbol (L symbols can be in one or more sub-frames) in the time domain. The subscript on terms K and L corresponds to the slice number. However, it is also possible that the slice-specific PRACH resources are restricted to occupy the same number of PRBs and sub-frames within each slice, and the present invention allows different numerologies for different slices to be mutually i ​ It is not restricted to being used only in network configurations that are integer multiples of i. As such, the slice-specific PRACH resource subband is located where the PRACH subband is positioned. Unlike slicing resources (in the frequency domain), numerology (subcarrier interval, Symbol length, etc. may be used. Slice-specific PRACH resources can be TDM and FD. M can be used to multiplex with the remaining resources within the slice. Slice-specific PRAC The numerology (subcarrier interval, symbol length, etc.) used by the H resource subband is all Use cases (eMBB, mMTC, UR / LL, etc.) and their corresponding resources This may differ from the numerology used by Suslice.

[0187] The configuration of a slice-specific PRACH resource is signaled to the UE as part of the system information. It can be signaled. In one embodiment, the reference configuration can be signaled to the UE. The configuration parameters are then based on the numerology of different slices before the UE applies the configuration. It will then be interpreted / expanded / contracted accordingly.

[0188] Alternatively, a slice-specific random access configuration for each slice can be explicitly U E may be signaled. In one embodiment, slice-specific PRACH-Config IE is signaled as part of system information, thereby slicing specific This may allow PRACH resources to be configured independently for each slice. The system information may also include slice-specific RACH-ConfigCommon IE, and These are the remaining parameters used to control the behavior of the random access procedure. It can be used to signal specific PRACH resources and general The random access parameter slice has been extended to support specific configurations. An example RadioResourceConfigCommon IE is shown below. ru. Extended RadioResourceConfigCommon IE

[0189] [Table 11-5]

[0190] [Table 11-6] In this embodiment, maxSLICES is defined as 3. However, the application is It can be used with any number of slices.

[0191] As shown in Figure 13, to configure a slice-specific PRACH resource, net The work is Extended RadioResourceConfigCommon Use IE and apply PRACH-Config-Common for each slice. And PRACH-ConfigIE can be explicitly signaled. The network is For mMTC, eMBB, and UR / LL slices, prach-ConfigI Values ​​3, 6, and 9 for ndex IE, and prach-FreqOffset The values ​​0, 4, and 0 will be signaled for IE, respectively. -ConfigIndex The exemplary values ​​signaled for IE are:

[0192]

number

[0193] When initiating a random access procedure, the UE uses the requested service as a basis. Next, select the PRACH resource. The resources from the corresponding slice are then, It can be used to complete random access procedures. PRACH resource selection and The mechanism for executing the domain access procedure is described further below.

[0194] (Random access procedure) According to further embodiments, LTE contention-based random access procedures The steps are shown in Figure 19. A similar procedure is NextGen Network It can be used to implement contention-based random access within a system. However, the steps of the procedure are strengthened as discussed below. It is possible. For illustrative purposes, a contention-based random access procedure is To establish a network and RRC connection, it can be initiated by the RRC sublayer. Cut.

[0195] Before initiating a random access procedure, the UE takes the required configuration parameters. You will benefit. System information is 3GPP TS 36.331 "Error! Reference source not found". System information acquisition procedures such as those described in "Sen", or NextGen Net Using any other mechanism designed to acquire system information within the network, It can be beneficial.

[0196] In one embodiment, the configuration required to perform a random access procedure The meter is PRACH-Config, which is signaled as part of the system information. It is included in RACH-ConfigCommon IE. Below, the common PRA A network configured to use CH resources or slice-specific PRACH resources. When executing a random access procedure within a network, configure the PRACH resource. Then, these extensions to IE for controlling the behavior of UE are explained.

[0197] The upper layer recognizes the device type and / or service request. This information is The upper layer requests the start of a random access procedure, and the random access procedure When the MAC sublayer requests to use this information when initializing and executing, M It can be provided to the AC sublayer. Alternatively, the device type / service request is not It can be configured with volatile or semi-static parameters, and it is a random access procedure. When the initialization of the JA is performed, it is read by the MAC entity.

[0198] (Random access procedure using a common PRACH resource) In this embodiment, the network is configured to use a common PRACH resource. The scenario is described. The first step is to use a common PRACH resource. Run Some or all of the remaining steps of the dam access procedure may be performed as needed. Service uses resources from a specific slice. Runs using common PRACH resources. A signaling diagram for the dam access procedure is shown in Figure 20.

[0199] Step 0 in Figure 20 relates to initialization. Here, the UE receives the required configuration parameters. Obtain the data. The configuration parameter for the common PRACH resource is PRACH-Con The UE can be signaled using an extension to the IE.

[0200] When a higher layer requests the start of a random access procedure, the MAC entity , the procedure described in Section 5.1.2 of 3GPP TS 36.331, or Run may follow any other procedure designed for random access resource selection. Perform dam access resource selection. When selecting the preamble, MAC entity First, based on the amount of data that the terminal needs to transmit in step 3, group Select. If the group is split into service-specific subsets, MAC will select A preamble is randomly selected from a specific subset of the group of services, and the service A specific subset is selected based on the requested device type / service. Otherwise, MAC entities will be preambled randomly from the selected group. Select this option.

[0201] For beam-centered architectures, eNB uses multiple OFDM symbols, Beamformed initial access information (system information, synchronization, and broadcasting information) It can transmit (such as ping information). The antenna beam is designed to enhance cell coverage, with each O In FDM symbols, it can be steered in a single direction. Another option is minisa A frame (for example, with 12 or fewer than 14 OFDM symbols) is defined, It can be used to transmit initial access information: initial access over - Head time can be reduced by using short mini subframes. For example, initial access symbols can be configured or predefined from the eNB. E can be transmitted periodically or dynamically. Alternatively, beam sweeping can be performed at least in the DL direction. Since it can be used in, each Tx beam in the eNB is also each NR eNB Tx beam To increase the probability of UEs within the coverage of the map, to receive initial access information , the best UE DL Rx beam, the best NR eNB Tx beam, and shortened To reliably identify the initial access latency, beamformed initial access information is used in the system It can be transmitted systematically.

[0202] As shown above, the synchronization signal (cell lookup, i.e., frequency and symbol to the cell) Acquisition of frame synchronization, acquisition of cell frame timing, and determination of cell physical layer cell identification. (For the purpose of setting), broadcast channels (e.g., PBCHs that carry MIBs and various others) The transmission of the SIB (PDSCH) and the DL reference signal can be beamformed.

[0203] The UE uses these beamformed signals received from the eNB to determine the best or Preferred DL Rx beam for UE, and best or preferred DL Tx beam for NR eNB. Identify the beam. In step 1, the UE uses PRACH preamble transmission. The best or preferred NRe NB DL Tx beam information is then fed to the NR eNB. It could backfire.

[0204] UE Tx beam and PRACH preamble in frequency and time domains A mapping between one or more of the RACH resources is possible. B uses this mapping to determine the best or preferred UE's UL Tx beam, i.e. This resulted in a received preamble (potentially among all UL Tx beams). The UE's Tx beam can be derived. The eNB is associated with the received preamble. The UL Rx beam of a good NR eNB can also be identified / recorded. The eNB is, for example, step In step 2, the best or preferred UE's UL Tx beam information can be fed back to the UE. .

[0205] The UE indicates the device type / service request to the network during preamble transmission. To enable this, the preamble group is networked as shown in Figure 21. Based on the slice-specific service provided, it is divided into service-specific subsets. It can be divided. When initializing a random access procedure, the UE is appropriate Select a preamble from a group and service-specific subset.

[0206] Alternatively, a common PRACH resource could be configured to support mixed numerology. In addition, the numerology used to transmit the preamble is for the device type / service request. This will be shown in the network. Figure 21 shows the service base of the random access preamble. The division of the area is illustrated.

[0207] (Random Access Response (RAR) message) Step 1 in Figure 20 deals with preamble transmission. Random Access Procedure In step 1 of the process, the UE transmits the selected random access preamble. The power level at which the signal is transmitted depends on the required device type and / or service. It can depend on S.

[0208] In one embodiment, the UE is as described in Section 5.1.3 of 3GPP TS 36.331. The selected random access preamble is transmitted according to the procedure. The 'mble' is preambleInitialReceivedTargetPower+ DELTA_PREAMBLE+(PREAMBLE_TRANSMISSION_CO UNTER-1) * The parameter PRE is set in powerRampingStep. Power level controlled by AMBLE_RECEIVED_TARGET_POWER It is transmitted in the device. DELTA_PREAMBLE also requires an offset. It can be configured to depend on the chair type and / or service. DELT A_PREAMBLE_VALUE is then used to determine the preamble format and the requested It will be selected based on the device type / service. mMTC, eMBB, Exemplary device / service dependency preambles for UR / LL devices / services The set of offsets is shown in the following "Error! Reference not found". In this example The eMBB value is equal to the value used for LTE.

[0209] [Table 12] For a beam-centered architecture, the UE uses multiple beams to achieve the required configuration. Parameters can be received. The UE performs initial access signaling measurements of the DL beam. Based on this, select the best or preferred UE Rx beam and NR eNB Tx beam. Select the best or preferred NR eNB with feedback along with its Tx beam index. This can be provided to the eNB. By utilizing beam interactions, the UE can provide the following to the previous section. The PRACH preamble can be transmitted using resources selected based on the mechanism, e NB uses a selected beam with high RX antenna array gain directed toward the transmission UE. And then receive it.

[0210] For TDD systems, due to channel interrelationships, (with MIMO capability) UE It applies beamforming weights based on the initial DL access beamforming information, and then, Transmits the formed PRACH preamble and further enhances PRACH Tx performance. It is possible.

[0211] For FDD systems, similar procedures are performed via multiple symbols, PRACH It can be applied at a UE site to transmit beams, and the beam is randomly accessible. To enhance coverage for procedures, a single OFDM symbol It is steered in the direction. For static or semi-static scenarios, this UL beam sweep The beam selection procedure does not need to be performed frequently, and the UE does not need to perform it often. Note that the beam index should be recorded and used over a long period of time. I want it to be done. And the same PRACH preamble, in order to enhance PRACH capacity, It can be reused by different UEs belonging to different spatially separated directional beams. E uses preamble transmission to achieve the best or preferred DL Tx beam of the NR eNB. Information can be fed back to the NR eNB.

[0212] In step 2 of Figure 20, the UE uses DL (Digital Download) to determine the random access response (RAR). Monitor your channel, for example, PDCCH. The network will respond to the required device type. Transmitting RAR using resources from DL slices corresponding to the service. This is possible. The network is based on a preamble selected from a service-specific subset. This determines the required device type / service. This information is used for RAR transmission. This is used by the network when determining which slice to use.

[0213] Alternatively, from the slice corresponding to the slice in which the common PRACH resource is configured DL resources may be used to signal RAR. In this embodiment, R AR handles the remaining random access procedures, namely the transmission of Msg3 and Msg It can be extended to include an IE to indicate the slice that should be used for receiving 4. ru.

[0214] RAR shows the change in uplink timing relative to the current uplink timing. This may include timing advance (TA) commands.

[0215] In one embodiment, the TA command is expressed as a multiple of a basic unit of time such as LTE. Obtain: For example, multiples of 16·Ts. Alternatively, the timing advance command is sl A slice can be expressed as a multiple of a specific base unit of time. A slice can be expressed as a multiple of a specific base unit of time. The following definition applies to the exemplary numerology:

[0216] Ts,mMTC =(Δf / ΔfmMTC)×Ts =2·Ts Ts,eMBB =(Δf / ΔfeMBB)×Ts =Ts Ts,UR / LL =(Δf / ΔfmMTC)×Ts =1 / 2·Ts.

[0217] The TA command is used as a multiple of the reference value of Ts, or as a multiple of a slice-specific value of Ts. Whether or not it can be represented depends on whether it can be standardized / preconfigured in UE, or the system information Signaling can be transmitted via information: that is, if an mMTC service is requested, the TA Regardless of the slice in which the common preamble is constructed, it is expressed as a multiple of Ts,mMTC. It is possible that the TA command also configures the slice in which the common PRACH resource is configured. Alternatively, regardless of the requested service, it can be expressed as a multiple of the reference value of Ts.

[0218] RAR can carry backoff values ​​for random access procedures. An example of off-signaling is when the backoff indicator subheader is included in the RAR. MAC Entity is indicated by the BI field in the backoff indicator subheader. This involves setting backoff parameter values ​​that allow for this behavior. Definition of backoff parameters This can be extended to depend on the device type / service for which the value is requested. The value of the backoff parameter is the BI in the backoff indicator subheader. The selection will be based on the world and the requested device type / service. Exemplary devices / services for MTC, eMBB, and UR / LL devices / services The sets of bis-dependent backoff parameter values ​​are shown in Table 13 below.

[0219] [Table 13] eNB selects the best or preferred UE in the Random Access Response (RAR) message. The UE can feed back its UL Tx beam information. The UE then uses this information. Then, in step 3 of Figure 20, select the Tx beam to be used for message 3 (Msg3) transmission. obtain.

[0220] eNB is the most NR eNB identified from the PRACH preamble transmission in step 1. RAR messages can be transmitted over a good DL Tx beam.

[0221] The UE uses RAR messages to select the best or preferred NR eNB DLTx bee. It is possible to identify Mu.

[0222] Step 3 in Figure 20 illustrates terminal identification and connection request. Here, the UE requests a connection. The message used to establish the relationship is transmitted. The message is received in step 2. Using the UL resources allocated in the authorization that was part of the RAR, the transmission The message is used to help the network establish a connection. It may include one or more Internet Explorer entries.

[0223] In one embodiment, the UE propagates the RRCConnectionRequest message It can be sent. This message includes the establishmentCause field. The field is the establishment cause for RRC connection requests, as provided by the upper layer. It provides the following definition of EstablishmentCause IE. It has been extended to allow the UE to indicate the type of service being requested. The network can perform slice (re)selection in the RAN and / or CN. That information can be used to help make a choice.

[0224] When the random access preamble is divided as illustrated in this example, the service The type of request must be explicitly specified in the RRCConnectionRequest message. There are cases where signaling is not necessary. However, in this scenario, the present invention Extended EstablishmentCause IE is requested Do not exclude signaling for this service type. Extended EstablishmentCause IE

[0225] [Table 13-1] Alternatively, service request types are defined as follows: This can be shown using MAC CE.

[0226] [Table 14]

[0227] [Table 15] UE is the best or preferred UE in RAR messages by NR eNB. Msg3 can be transmitted on a beam identified as a Tx beam.

[0228] The UE can provide feedback to the NR eNB. This is also shown in step 0 of Figure 20. Alternatively, the best or preferred NR eNB DL Tx identified in step 2 of Figure 20. It could be a beam.

[0229] Step 4 in Figure 20 explains contention resolution. Contention resolution is 3G As described in Section 5.1.5 of PP TS 36.321, or NextGen In accordance with any other mechanism designed for contention resolution within a network, It is possible. The eNB is by the UE in step 1 of Figure 20, or in step 3 of Figure 20. The NR eNB transmits message 4 on the best DL Tx beam of the eNB that is communicated to the eNB. obtain.

[0230] The entities that perform the steps illustrated in Figure 20 are shown in Figures 1B and 1F. For wireless and / or network communications or computer systems The software is stored in the memory of the device and executed on its processor. In other words, it can be a logical entity that can be implemented in the form of a computer executable instruction. It is understood that the method illustrated in Figure 20 is the same as the method illustrated in Figures 1B and 1F. Software stored in the memory of a device or computer system (that is, It can be implemented in the form of computer executable instructions, and those computer executable instructions When executed by the device's processor, it performs the steps illustrated in Figure 20. Furthermore, any transmission and reception steps shown in Figure 20 are performed by the device's processor and Under the control of the computer executable instructions (e.g., software) that it executes, the device It is also understood that this can be done through communication circuits.

[0231] (A random access procedure that uses a slice-specific PRACH resource) In a further embodiment, the network uses slice-specific PRACH resources. A scenario is described in which the procedure is configured as follows. Step 1 of the procedure in Figure 23 is: Slice-specific PRA selected by the UE based on device type / service request Use the CH resource. The remaining steps of the random access procedure are selected. Uses resources from a specific slice of service. A signaling diagram for a random access procedure using S is shown in Figure 23. ru.

[0232] Step 0 in Figure 23 illustrates the initialization procedure. The UE receives the required configuration parameters. Obtain the meter. The configuration parameters for a slice-specific PRACH resource are, Ex Using the trended RadioResourceConfigCommon IE , can be signaled to the UE.

[0233] When a higher layer requests the start of a random access procedure, the MAC entity First, select the slice from which the PRACH preamble will be selected. The slice selected is determined based on the requested device type / service. Subsequently, MAC entities are described in section 5.1.2 of 3GPP TS 36.331. The procedure to be revealed, or any procedure designed for random access resource selection Random access resource selection is performed according to other procedures.

[0234] For a specific procedure, different PRACH numerology results in different development scenarios. To support O: Therefore, for each numerology in NR, initial action Each subframe or mini-subframe has a different size and correspondingly a different number. The symbol needs to be supported.

[0235] Step 1 in Figure 23 illustrates preamble transmission. Here, the UE is selected Transmits a random access preamble. The power level at which the preamble is transmitted is required. This may depend on the required device type and / or service. In one embodiment, The power level transmitted by the spool is determined by the slice-specific PowerRampingParam It depends on eters, and it is Extended RadioResourceConf igCommon IE and suggestions for "Error! Reference source not found," etc. The signal is transmitted via the device / service dependency DELTA_PREAMBLE_VALUE. It is ringed. A similar mechanism can be applied to a beam-centered model.

[0236] Again, different PRACH numerology methods yield different results for specific slicing procedures. Required to support the scenario: Therefore, for each numerology in NR, P Each RACH subframe or mini subframe has a different size and correspondingly different... It is necessary to support a certain number of symbols.

[0237] Step 2 in Figure 23 illustrates the reception of a random access response. Here, the UE is R For AR, monitor the DL control channel, e.g., PDCCH. UE is slice special The UE behavior can be controlled using fixed configuration parameters. In one embodiment, the UE When performing this step of the procedure, slice-specific ra-Supervi You can use sionInfo. For example, to determine the size of the RAR window. When this happens, the UE uses Extended RadioResourceConfigComm Slice-specific ra-ResponseWind signaling via IE It will use owSize. The UE will consider RAR reception unsuccessful. In addition, when deciding whether a different random access transmission should be performed for each slice, The `preambleTransMax` parameter will also likely be used.

[0238] RAR may include timing advance (TA) commands. If an indicator subheader is included, the UE will have slice features such as those proposed in Table 13 above. A fixed backoff parameter value can be applied.

[0239] The network uses DL resources corresponding to the UL slice in which the preamble was found. RAR can be transmitted using this method. Therefore, the UE can transmit on the corresponding DL slice. For RAR, only monitoring of the DL control channel, e.g., PDCCH, is required. For example, if UE uses UR / LL slices, random access preamble When transmitting a RU, the UE transmits the D to the RAR on the corresponding UR / LL DL slice. The L control channel, for example, PDCCH, will be monitored.

[0240] Step 3 describes terminal identification and connection request. Here, the UE establishes a connection. Messages used for this purpose, for example, RRCConnectionRequest messages The message is transmitted. The message is part of the RAR received in step 2 of Figure 23. The message is transmitted using the UL resources allocated in the permission granted. xtended EstablishmentCause IE or service type M AC CE is used to assist the network in establishing a connection. It may include one or more Internet Explorer entries.

[0241] In step 4 of the random access procedure shown in Figure 17, contention resolution is performed. Contention resolution is handled by Section 5.1.5 of 3GPP TS 36.321, "Era". —!Reference not found" as explained, or for content resolution It can be implemented according to any other mechanism designed.

[0242] In one embodiment, after the transmission of Msg3, the UE performs mac-ContentionResolution. Set the Response Timer and the content resolution message, i.e., Msg4, Waiting for reception. UE is using the mac-ContentionRe solution Ti mer, Extended RadioResourceConfigCommon The slice signaled via can be set to a specific value. If the resolution is deemed unsuccessful, the UE will attempt another random access transmission. When deciding whether to use it or not, the slice-specific preambleTransMax parameter They will probably use Ta as well.

[0243] (Random access with permissionless transmission) Furthermore, according to a further embodiment, permission is not required as part of a random access procedure. The method for carrying out the transmission will be explained. Permission-free transmission is performed by the control plane (CP) and It can be used to transmit user plane (UP) data. CP / UP data is It may include a connection request message: for example, RRCConnectionRequest, IE, which assists the network in establishing or maintaining connections, "KeepAlive" Messages such as " ", periodic status / health indicators, and infrequent, small data packets. Permission-free messages. The signaling diagram for the random access procedure involving transmission is shown in Figure 24. ru.

[0244] Step 1 in Figure 24 illustrates the transmission of a preamble + permission-free message. The UE transmits a selected random access preamble and a permission-free message. The permission-free message can be multiplexed with the preamble in TDD or FDD format. In one embodiment, permission-free messages are transmitted within OFDM symbols after the preamble. It will likely happen.

[0245] Figure 25A can be used to multiplex the transmission of permission-free messages in TDD format. This is an exemplary random access preamble format. It is used for preamble transmission. The same frequency resources can be used for message transmission. Alternatively, frequency resources Different sets of resources, such as permission-free resources, may be used for message transmission. The location of permission-free resources is included as part of the system information or via dedicated signaling. This can then be signaled to the UE. Permit-free transmission is permitted under MUSA, RSMA, SCMA, etc. A non-orthogonal multiple access scheme can be used. Figure 25B shows C between the sequence and the message. This is a further alternative embodiment that does not include P.

[0246] Alternatively, permission-free messages use different physical resources for preamble transmission. Use a permission-free resource, for example, a permission-free resource adjacent to a PRACH resource. And it can be transmitted within the same OFDM symbol as the preamble. Figure 25C shows an FDD-like Exemplary random access that can be used in formulas to multiplex the transmission of permissionless messages This is a preamble format. According to this application, one or more protection periods are shown in Figures 25A-C. The message, sequence, or what may be provided after the sequence / message shown. This is what is expected.

[0247] The set of parameters is used by the transmitter / receiver as the signature of its transmission for permissionless data transmission. It is possible to modulate / demodulate and encode / decode the transmission. Non-orthogonal U transmissions using permissionless UL transmissions multiplexed to share some or all of the same destinations. Between E units, each UE has a unique signature and They must be transmitted together. The true identification of the UE (C-RNTI, etc.) itself is not necessarily... Please note that it does not need to be part of the signature. Selected PRACH resource The `U` and `preamble` implicitly indicate the signature associated with the permissionless data. It can be transmitted by E.

[0248] In one embodiment, the selected preamble sequence corresponds to a non-orthogonal multiple access scheme. Then, map to a parameter that defines a signature which may be one or more of the following. Possible: Diffusion sequence Scrambling sequence (initial state of the scrambler, etc.) Interleaver pattern Resource mapping patterns.

[0249] For example, a UE can use RSMA signaling for permissionless UL transmission. The initial state of the scrambling sequence used for the data is UL-permitted. It serves as a signature for transmission. According to our solution, The Scrambler ID is the scrambling sequence that the UE should use to transmit its data. Maps to S and interleaving patterns.

[0250] The message portion of the transmission can be used to transmit CP or UP data. In this configuration, the message portion may be used to transmit a connection request message. The message structure is defined for LTE as RRCConnectionRequ Similar to the new message structure defined for est messages or NR RAN. To obtain. Messages, at will, support the network in establishing or maintaining a connection. May include IE that can provide support. Exemplary NR-ConnectionRequest message However, it is defined as follows: NR-ConnectionRequest message

[0251] [Table 15-1] For scenarios where small data packets need to be sent from the UE to the network The UE then sends the NR-GrantlessData message within the transmission message portion. To transmit. An example NR-GrantlessData message is defined below. NR-GrantlessData message

[0252] [Table 15-2] In step 2 of Figure 24, the UE controls the DL control channel, e.g., PD, to the RAR. Monitor CCH. NR-ConnectionRequest messages are shown in Figure 18. If transmitted in step 1, the network will establish a connection, for example, establish a connection. Respond with NR-ConnectionSetup, which includes the necessary IE for this purpose. RAR also includes UL permission for Msg3 transmission. NR - GrantlessData If the message was transmitted in step 1, the network will confirm that the data message was successful. Depending on whether the message was received, it will respond with either an ACK or a NACK.

[0253] Step 3 in Figure 24 illustrates the transmission of UL data and control signaling. Step is applicable only if the connection request was transmitted in step 1 of Figure 18. Then, UE uses the resources provided within UL permission to access any UL data or control Along with your signaling, please also provide the connection status (for example, connection established successfully or connection established unsuccessfully). Send a message to indicate this.

[0254] Step 4 in Figure 24 describes the transmission of DL data and control signaling. Here, DL data and control signaling are transmitted to the UE. UL / DL data The transmission of control signaling can continue to use the established connection.

[0255] The objective of the research project on random access (NR) technology is to handle access up to 100 GHz. Identify the technical components required for a system operating at frequency z. This is to develop [3GPP TR 38.913][RP-161214,Re vision of SI:Study on NewRadio Access Te [technology, NTT DOCOMO]. These high-frequency NR (HF-NR) systems To compensate for the increased path loss in the system, beamforming is expected to be widely used. It is expected. However, existing random transmissions based on omnidirectional or sector-based transmissions Access procedures include, for example, beam sweeping, beam pairing, and beam training. It does not support the functionality required for beamformation-based access. Therefore, Enhanced random access procedure to support beamforming for NR networks There is a need for a supervisor.

[0256] According to another aspect of this application, a solution to enable beam sweeping within an NR network The solution will be discussed. The solution is expected to be used in HF-NR systems. However, their use in systems operating at lower frequencies is excluded. The proposed mechanism is not applicable even if the NR node is used for illustrative purposes or explanation. Even if used, it can be done at an NR node, RRH, or TRP.

[0257] (Beam-swept frame structure) According to one embodiment of this aspect, the sweep subframe is a beam within the NR network. Defined to enable sweeping. A sweep subframe consists of multiple sweep slots. Each sweep slot may consist of one or more OFDM symbols. The DL beam that is enabled uses a synchronization signal and a beam training reference signal (BT-RS). , and can be used to transmit DL physical channels. Effective during a given sweep slot. The UL beam used is a random access preamble, a quality measurement reference signal (SRS), It can be used to transmit BT-RS and UL physical channels.

[0258] To perform beam sweeping, the NR node selects a subset of the beam within each sweep slot. Enable it. In one embodiment, the NR node, as shown in Figure 27, each sweep slot Enable a single beam during the process. In this embodiment, the NR node enables 12 separate beams Using the M, Coverage requests 12 sweep slots to sweep the entire set of beams. Provide a ledge.

[0259] Alternatively, an NR node may enable multiple beams within each sweep slot. Figure 28 A is an embodiment in which one sector consisting of four beams is enabled for each sweep slot. As shown, in this embodiment, the entire set of 12 beams is swept within three sweep slots. Figure 28B shows an implementation in which one beam within each sector is enabled for each sweep slot. This shows the state. In this embodiment, the entire set of 12 beams sweeps within the four sweep slots. Some configurations, such as those shown in Figure 15A, are less affected by inter-beam interference. It is likely to be affected. In such cases, in order to minimize inter-beam interference, adjacent The beam is configured to use non-overlapping subbands, i.e., different frequency resources. It is possible.

[0260] In the FDD system, the UL and DL beams are as shown in Figure 27 or Figure 28, etc. The sweep can be performed simultaneously using the sweep subframe. For example, see the scenario shown in Figure 27. When considering this, in the sweep slot n, the NR node uses beam n to simultaneously transmit It is receiving. And in the sweep slot n+1, beam n+1 is transmitting and receiving. It is used. This process continues until all beams have been swept.

[0261] Alternatively, for the TDD system, the sweep subframe is separate DL and UL sweep. It may be defined with pull slots. Figure 29 shows the protection period that enables Rx / Tx switching. This describes an embodiment of an integrated sweep subframe with DL / UL sweep slots separated by [a specific mechanism / method]. vinegar.

[0262] The sweep subframe may occur periodically or dynamically, as shown in Figure 30. It can be configured. Alternatively, a separate DL / UL sweep subframe can be configured. Figure 3 1 is the DL and UL sweep subframes, respectively, subframe N and (N+3) This describes an embodiment that occurs periodically within the system.

[0263] According to this application, a sweep subframe is used, and an initial access procedure, for example, a cell Signaling required to support search, cell (re)selection, random access, etc. It uses standard subframes to transport data and communicate with UEs that have established a connection. It is anticipated that the sweep subframe will be a small data that does not require the establishment of a full connection. It can also be used for packet transmission and to support mobility, for example, service It is also used to facilitate the detection and measurement of additional beams that can be configured as a beam. It is possible.

[0264] When UL Rx beam sweep is used at an NR node, the UE determines that the NR node is propagating It must be transmitted using the UL Rx beam in the direction of the transmitting UE while it is being received. If beam interaction is supported at the NR node, it is DL Tx beam This is achieved by defining the association between the corresponding UL Rx beam. Yes, it is possible. Figure 32 shows the DL Tx beam and UL sweep slots enabled during DL sweep. This shows an embodiment in which an association is made with the UL Rx beam that is activated during the process. In this example, the UE synchronized with the DL beam transmitted during a given DL sweep slot is UL transmission will be performed in the corresponding UL sweep slot. For example, synchronized to DL beam 0. The UE will perform UL transmission during sweep slot 0 of the UL sweep subframe. To support scenarios where multiple DL beams are enabled during a given sweep slot The UE signals the beam ID of the synchronized DL beam when it performs UL transmission. It is possible. The association between UL / DL beams may be specified in the standard, or N It can be signaled as part of an SI broadcast by an R node. If the relationship is not supported at the NR node, the UL Rx beam will be directed in that direction. Since it is unknown when it is present, UE is among all of the sweep slots of the UL sweep subframe. It may be necessary to repeat the transmission. Support for interoperability by NR nodes is NR It can be signaled as part of an SI broadcast by a node.

[0265] RAN2 requires that the minimum SI be broadcast periodically, and the minimum SI To obtain other SIs defined as all that are not broadcast within, To access a cell, it contains the information necessary to support cell selection. They have agreed to [3GPP TR 38.804, Study on New R adio Access Technology;Radio Interface P rotocol Aspects (Release 14), V0.2.0 1]. This Information is signaled to LTE by MIB, SIB1, and SIB2. This corresponds to IE. We are concerned that the sweep subframe configuration is periodically blown by the NR node. We propose that it be included in the minimum SI to be docast. Sweep subframe configuration An exemplary IE that may be used for gunnering is shown in Figure 33. DL and UL sweeping. An alternative sweep subframe IE that explicitly defines the sweep subframe configuration is shown in Figure 34. Alternatively, a sweep subframe configuration can be defined in the standard specification.

[0266] [Table 16]

[0267] [Table 17] Minimum SI is NR-Physical Broadcast Channel (NR-PBCH) and NR- Using a physical downlink shared channel (NR-PDSCH) during DL sweep slot It is assumed that it will be broadcast. In one embodiment, NR-PBCH is minimal A subset of SI, namely NR-MIB, is used to transmit NR-PDSC. H corresponds to the remaining minimum SIs, i.e., I, NR-SIB1 and NR-SIB2. It will be used to transmit E. We will use NR-MI as shown in Figure 35. We propose including a sweep subframe configuration within B. Alternatively, the sweep subframe configuration The composition may be included in NR-SIB1 or NR-SIB2. The minimum SI is described above. System information acquisition procedures for those that are acquired, or acquisition of SIs within the NR network. It can be obtained using any other mechanism designed for that purpose.

[0268] (Cell selection in beam-swept NR networks) The UE performs cell selection and finds the most suitable cells to camp on. During the process, the UE receives DL beams transmitted by NR cells during the DL sweep subframe. The measurement is performed against it. As part of the cell selection procedure, the UE performs the "best" DL The Tx beam is also determined / selected, and the "best" DL Tx beam is selected with maximum RSRP measurement. It is possible. The UE performs beam pairing during the cell selection procedure, that is, The "best" DL Rx beam to use when receiving the "best" DL Tx beam. It is possible to determine this.

[0269] As part of the cell selection procedure, the UE uses a sweep subframe configuration and a PRACH configuration. , and / or NR cells which may include additional SIs required to access the cell The minimum SI broadcast by can also be obtained. The UE can optionally, if the UE is a cell If broadcasted while the (re)selection procedure is being performed, other SIs will be acquired. You can gain an advantage.

[0270] After selecting the cells to camp on, the UE receives the D transmitted by the selected cells. L beam, and / or DL ​​beam transmitted from any other cell that the UE can detect. Measurements can be continued for DL ​​measurement and / or any other cell selection basis. Based on the criteria, a different cell and / or DL ​​Tx / Rx beam pair may be re-selected. Example The explicit NR cell selection procedure is shown in Figure 36.

[0271] The entities that perform the steps illustrated in Figure 36 are shown in Figures 1B and 1F. For wireless and / or network communications or computer systems The software is stored in the memory of the device and executed on its processor. In other words, it can be a logical entity implemented in the form of a computer executable instruction. It is understood that the method illustrated in Figure 36 is the same as the method illustrated in Figures 1B and 1F. Software stored in the memory of a device or computer system (that is, It can be implemented in the form of computer executable instructions, and those computer executable instructions When executed by the device's processor, it performs the steps illustrated in Figure 23. Furthermore, any transmission and reception steps shown in Figure 36 are performed by the device's processor and Under the control of the computer executable instructions (e.g., software) that it executes, the device It is also understood that this can be done through communication circuits.

[0272] (Transmission of other SIs) According to a further embodiment of this aspect, during the DL sweep subframe, the NR node The minimum SIs that can be broadcast periodically can be very limited. In Rio, until the random access procedure completes successfully, the system blocks within the minimum SI. Other SI[3GPP TR 38.80] is defined as all that are not codecast. Delaying the acquisition of [4] may not always be desirable. The detection of the preamble by the NR node is performed among other SIs during the DL sweep subframe. It is intended to be used to trigger some or all broadcasts. If a subset of other SIs should be broadcast, that subset will be broadcast beforehand. It can be determined or can be determined dynamically, for example, other SIs that should be broadcast. The subset is transmitted by the UE via preamble transmission and "piggyback" data. Other SIs may be required on all DL beam / DL sweep slots, or on DL beams. It can be broadcast on a subset of beam / DL sweep slots, DL beam / DL sweep A subset of the pull slots are the detected preamble and / or the detected preamble. Based on the PRACH, other SIs may be in one or more DL sweep subframes. Multiple DL sweep subframes can be broadcast, and they can also be continuous. This is not always the case. The UE may, at its discretion, perform the entire random access procedure. PDCCH can monitor broadcasts from other SIs. Triggering transmissions from other SIs. An illustrative signaling diagram for this purpose is shown in Figure 37.

[0273] The entities that perform the steps illustrated in Figure 37 are shown in Figures 1B and 1F. For wireless and / or network communications or computer systems The software is stored in the memory of the device and executed on its processor. In other words, it can be a logical entity that can be implemented in the form of a computer executable instruction. It is understood that the method illustrated in Figure 37 is the same as the method illustrated in Figures 1B and 1F. Software stored in the memory of a device or computer system (that is, It can be implemented in the form of computer executable instructions, and those computer executable instructions When executed by the device's processor, it performs the steps illustrated in Figure 37. Furthermore, any transmission and reception steps illustrated in Figure 37 are performed by the device's processor and Under the control of the computer executable instructions (e.g., software) that it executes, the device It is also understood that this can be done through communication circuits.

[0274] (Random access in beam-swept NR networks) To support random access in beam-swept NR networks, UL sweep It is assumed that PRACH resources will be configured during the pull slot. Random access programme The ambile parameters can be optimized based on the swept subframe configuration. An exemplary random access preamble format optimized for the system configuration is provided below. This new preamble is provided in Table 18 below and illustrated in more detail in Figure 38. The parameters for formatting are listed in Table 19 below. In this example, We have a sweep subframe length of 0.125 milliseconds, a subcarrier interval Δf = 480 kHz, Numerology, which involves the corresponding basic unit of time T's = 1 / (480,000 × 2,048). Let's assume that.

[0275] [Table 18]

[0276] [Table 19] The subcarrier interval for the random access preamble, i.e., ΔfRA, is used in LTE. It was selected such that (1 / 12 × Δf) was the length of CP, i.e., TCP was selected to support cell sizes up to 500 meters.

[0277] The NR node is for all UL sweep slots, i.e., for all UL beams. It can be configured with the same PRACH configuration. Alternatively, the NR node can be configured with each UL sweep. Different PRACH configurations can be used for the pull slots. The PRACH configuration is S Uses an IE similar to PRACH-Config IE, which is signaled within IB2. This can be signaled and broadcast to the UE during the DL sweep subframe.

[0278] PRACH-ConfigIndex included in PRACH-Config IE This can be used to determine the random access configuration. Table 20 below shows the NR random access configuration. This shows an example of a multi-access configuration. Optimization for specific use cases, deployment scenarios, etc. Additional random access configurations that may include this will extend the number of configurations defined in this table. This mechanism can be used for signaling.

[0279] [Table 20] (Random access procedure) In another embodiment of this aspect, the UE, before initiating a random access procedure, Cell (re)selection may be implemented. LTE contention-based random access procedure The steps of the JA are discussed above. Concentration in beam-swept NR networks An enhanced procedure for implementing database-based random access is proposed. Prior to initiating random access preamble transmission, the UE sends a random access Three-resource selection is performed, and the random access preamble and PRACH are determined. When an NR node supports beam interactions and is configured with a sweep subframe, PRACH's time resources, i.e., UL sweep slots, are time resources, i.e., The DL beam selected by the UE during the cell selection procedure, i.e., the "best" D From the DL sweep slot used by the NR node to transmit the L Tx beam, It can be determined that the UE transmits to the sweep slot N of the DL sweep subframe. When selecting the DL Tx beam to be transmitted, the corresponding PRACH time resources are shown in Figure 3. As shown in 9, this is likely sweep slot N of the UL sweep subframe.

[0280] Figure 40 shows the definition of an exemplary association when an internal DL / UL sweep subframe is configured. This shows possible methods. The frequency resources of the corresponding PRACH are blocked by the NR node. PRACH-Confi is signaled as part of the minimal SI that is codecast. This can be determined from g IE. Multiple PRACH resources are configured within the UL sweep slot. In this case, the UE may randomly select a PRACH resource from the set of PRACH resources. ru.

[0281] If beam interactions are not supported by the NR node, the selected DL Tx beam It is not possible to create an association between the time resources of the program and PRACH. There is also this. In this scenario, the UE randomly selects a PRACH resource from a set of PRACH resources. Resources can be selected. Alternatively, UE has successfully performed random access procedures in the past. If completed, the UE is selected when the random access procedure successfully completed. A PRACH can be selected that is configured with the same time resources as the PRACH that was selected. For scenarios where the interrelationship is not supported by the NR node, the UE makes the selection. The DL beam is determined from the PRACH from which the random access preamble is detected. It may not always be possible. Therefore, we use the preamble as shown in Figure 41. We propose dividing the space. Given UE is the "best" DL Tx beam. Selected by E, from a subset assigned to the corresponding DL beam, preamble The NR node will then select based on the detected preamble. This will allow us to determine the "best" DL Tx beam for the given UE.

[0282] As shown in Figure 41, by splitting the random access preamble, Implicitly signaling the "best" DL Tx beam is done when an NR node is given U It can also be used in scenarios where multiple UL Rx beams are configured within an L-sweep slot. The UL Rx beam configured within the sweep slot overlaps or targets similar areas of the cell. In this case, a single preamble transmission is detected on the PRACH of multiple UL Rx beams. It is possible. The NR node uses this information to transmit the DL. The Tx beam is determined, not selected by the UE, and monitored by the UE for RAR. This avoids the transmission of RAR over the DL Tx beam.

[0283] In some scenarios, the UE has multiple PRs corresponding to one or more UL sweep slots. Choosing an ACH resource may be advantageous. For example, if the beam interaction is NR node If not supported by, the UE will extract PRACH resources from each of the UL sweep slots. Select a slot, that is, transmit a random access preamble during each UL sweep slot. Obtain. This approach is used when the UE has not succeeded in attempting another random access transmission. Compared to approaches that would require waiting for a RAR response that is deemed appropriate, random access This will allow for a reduction in procedure waiting times.

[0284] If the UE supports beam sweeping, the beam used for the transmitted preamble will be the beam. The "best" U can also be selected. If beam interaction is supported by the UE, then the "best" U The L Tx beam can be determined from the "best" DL Rx beam. Beam phase If the interaction is not supported by the UE, the UE will, for example, randomly, any UL A Tx beam can be selected. Alternatively, the UE has previously used a random access procedure. If successful, the UE will use the random access procedure when it completes successfully. The UL Tx beam used can be selected.

[0285] If the random access response is deemed unsuccessful, the UE will attempt another random access. A cross-transmission can be attempted. Beam interactions are supported by NR nodes and / or UEs. If not enabled, the UE will use UL Tx on subsequent retransmissions of the random access preamble. The beam can be swept. Before switching the UL Tx beam, the UE selects the UL Tx beam. Use the beam to complete power ramping. Use the given beam to perform the maximum number of trials. When it reaches this point, the UE switches the UL Tx beam and PREAMBLE_RECEIV ED_TARGET_POWER preambleInitialReceivedT argetPower+DELTA_PREAMBLE+(PREAMBLE_TRAN SMISSION_COUNTER-1) * Reset powerRampingStep This process involves sweeping all UL Tx beams or randomly activating them. The process may be repeated until the procedure completes successfully.

[0286] In step 1 of the random access procedure, the UE selects PRACH and Using the selected UL Tx beam, the selected random access preamble To transmit. In step 2 of the random access procedure, the UE performs random access. For the response (RAR), monitor the DL control channel, e.g., PDCCH. The UE is, Supports PRACH resources used to transmit random access preambles. For RARs identified using RA-RNTI, PDCCH is monitored. The t_id (0 ≤ t_id < 28) is the time resource of PRACH, i.e., UL sweep. It is anticipated that RA-RNTI will be redefined to accommodate the pull slot. Embodiment Therefore, it could be as follows: RA-RNTI=1+t_id+10 * f_id .

[0287] Redefining RA-RNTI in this way means that NR nodes have beam interactions that are NR Facilitating UL beam pairing in systems not supported by the node The preamble that can be used implicitly signs the time resources of the detected PRACH. It makes it possible to narrate.

[0288] The UE monitors the PDCCH as described above during the random access response window. In the NR network configured for beam sweeping, we have the following, as shown in Figure 42. Define the random access response window as several DL sweep subframes. I propose doing the following: The parameters included in RACH-ConfigCommon IE The `-ra-ResponseWindowSize` parameter is used to signal this value. It can be used.

[0289] The UE matches the transmitted random access preamble with a random access preamble. After successfully receiving a RAR containing a smuggle identifier, monitoring for RARs may be stopped. (Alternative) For example, if the UE transmits multiple random access preambles, the UE will Until all random access procedures that are started have completed successfully (i.e., Includes the random access preamble identifier of the transmitted random access preamble. Until confirmed by RAR, or until timeout (i.e., transmitted random RAR containing the random access preamble identifier in the access preamble is random access Additional RARs may continue to be monitored (if not received within the access response window).

[0290] RAR includes UL permission. When the UL delay field of permission is set to "0" The authorization applies to the first UL sweep subframe after the DL subframe in which the RAR was received. And when set to "1", permission is received as shown in Figure 30. It is assumed that this will be applied to the second sweep subframe after the DL subframe. , the UL sweep slot for permission is pre-emptive in step 1 of the random access procedure. It is the same UL sweep slot used for ambiguous transmission, and therefore, as permitted. I suggest that signaling may not always be explicit.

[0291] Alternatively, RAR authorization schedules resources within a regular UL subframe. It can be used for this purpose, and the timing of Msg3 transmission is based on LTE timing, that is, "The UE, according to the information in the response, is within the first subframe n+k1 where k1≧6 The UL-SCH transport block is to be transmitted, and the UL delay field is zero. It is set so that n+k1 is the first available UL subframe for PUSCH transmission. In this case, the first UL subframe for PUSCH transmission is applied to the TDD serving cell. The subframe is a UL / DL configuration (i.e., parameter subframe) shown by the upper layer. Determined based on the Assignment. UE is when the field is set to 1. In addition, the push transmission is postponed to the next available UL subframe after n+k1. An example of RAR permission is illustrated in Figure 43.

[0292] When performing contention-based random access to LTE, RAR permission is required. The CSI request field is pending. Contention in the NR network This field is expected to be used when performing base random access. The beamformed training reference signal (BT) that the UE measures to calculate the CSI. -RS) is the "best" DL Tx beam (i.e., during the cell (re)selection procedure) (Selected DL Tx beam), or BT-RS is signaled as part of SI This can be determined from the possible beam combinations, or from the BT-RS of the "best" DL Tx beam. It can correspond to the beamset. Alternatively, the BT-RS to be measured is the field in RAR. It can be dynamically signaled using .

[0293] The NR node transmits RAR using the "best" DL Tx beam, and the UE uses the "best" RAR is received using a DL Rx beam paired with a good DL Tx beam. As an attempt, beam pairing may also be performed during the cell (re)selection procedure. It is also possible that beam interactions are supported by NR nodes. In summary, the "best" DL Tx beam was detected by UL, where a random access preamble was found. This can be determined from the Tx beam. Beam interrelationships are supported by NR nodes. If not, the preamble will divide the preamble space as described above. This can be used to implicitly signal the "best" DL Tx beam. .

[0294] In step 3 of the random access procedure, the UE requests a (re)establishment of the connection. Messages that can be used for this purpose, for example, RRCConnectionRequest , transmit RRCConnectionReestablishmentRequest The message was assigned to one of the permissions that was part of the RAR received in step 2. It is transmitted using the provided UL resources. If the CSI request is included in the RAR, U E includes a CSI report in the transmission.

[0295] The UL beam pair used in the preamble is also used in Msg3, and UE is UL beam It is intended to transmit BT-RS, which can be used to support home training. The BT-RS used for transmission can be dynamically signaled as part of the RAR. Alternative As such, the mapping between the preamble and BT-RS can be defined, and the selected preamble The amber is used to "check" BT-RS.

[0296] NR nodes are used to receive the initial transmission and / or retransmission of Msg3. Transmitted BT-RS can be used to refine the UL Rx beam. NR node This is to configure a UL Rx beam that can be used to receive subsequent UL transmissions from the UE. The beam training results from this step can be used, and it is UL sweep subframe. This can occur during a UL subframe and / or a normal UL subframe.

[0297] Step 4 of the random access procedure involves contention resolution. The NR node will include messages in this transmission to (re)establish the connection, such as RRCCon. connectionSetup, RRCConnectionReestablishmen It may include t. We believe that the DL beam pair used for RAR is also used for Msg4. We propose that Msg4 be used for beam refinement / tracing in subsequent UL / DL transmission. It optionally includes beam management feedback / commands that can be used for sweeping, This is also expected to occur during pull subframes and / or normal subframes.

[0298] (Random access procedure optimization) The unified NR random access procedure was described above. In this section, we will discuss a specific type of random access procedure. Optimization for general events, use cases, and deployment scenarios will be explained.

[0299] (Optimized for power-constrained devices and extended coverage use cases) The solutions described above compensate for the increased path loss in HF-NR systems. It can be used to compensate. However, the solution is low frequency NR (LF-N). R) Can be applied to systems, which are power-constrained UEs and / or have high maximum coupling losses. Use cases that may require support for MCL include, for example, extended / extreme coverage. Supports case. For example, a high-gain beam swept during a sweep subframe, It can be used to provide extended coverage for power-constrained UEs. PRACH RIS Appropriate selection of beamforming results in lower Tx compared to when beamforming was not used. In power, this enables reliable detection of the preamble of a power-constrained UE. High-gain beams have several mMTC use cases, such as walls or other building materials. High MC (Multiple Controls) can be obtained in sensor network deployments that require RF signals to penetrate the material. It can also be used to overcome L.

[0300] (Optimization for mobility management) When performing intra-cell mobility, an L2-based beam management procedure is used. This is expected. If beams originating from the same TRP experience the same propagation delay, "rac The "h unnecessary" procedure can be used for mobility within the TRP. via the serving beam The beam management commands that are signaled by the UE control the entire coverage area of ​​the TRP. When moving through, it can be used to add / remove serving beams.

[0301] Beams originating from different TRPs may not experience the same propagation delay. The Seth procedure establishes UL synchronization when implementing inter-TRP mobility. It is expected that contention-based random access procedures will be used. It can be used to enable UE-based inter-TRP mobility. Random access Procedure Msg3 configures a new serving beam between the UE and the target TRP. It is assumed that the beam management commands used to make the request will be signaled. Msg4 of the DOM access procedure then indicates the ACK / NACK of the request. It can be used for: In one embodiment, the request is a DLB that the UE is requesting to add. The beam ID of the request is included, and Msg4 includes the request's ACK / NACK. Alternatively, the request Msg4 may include a request instruction, and Msg4 may include the beam ID of the new DL serving beam. ru.

[0302] Non-contention-based random access procedures are network-based inter-TRP models. It can be used to enable functionality. Signaled via serving beam. The beam management command will specify the beam ID of the DL beam to be added, and the non-contention beam. A dedicated random access program used when executing random access procedures on a machine. It can be used to signal the meter. Alternatively, latency and signaling To reduce overhead, a two-step random access procedure is used. It can be used for intra-cell mobility management. In the previous embodiment, signaling via Msg3 The beam management commands transmitted via Msg4 may be "piggybacked" with the preamble transmission. The beam management commands to be signaled can be signaled via Msg2. When implementing inter-cell mobility, non-contention-based random access procedures RRC signaling, which is transported via a jack, may be used.

[0303] (Measurement model for beam-swept NR networks) The new 5G radio interface, which operates within the millimeter-wave frequency band, is different from the older LTE. All mobility-related procedures should be reconsidered from a beam perspective. Implemented by the UE for the purpose of (e.g., adding / deleting cells and handover) It is especially important to carefully investigate the beam's influence on the measurement. Measurement models for the operation and beam sweep NR networks in LTE This is explained in light of the model. Figure 44 shows the proposed beam sweep NR network. This is a schematic diagram of the measurement model, which will be explained in more detail below.

[0304] In HF-NR with beam motion, the cell can be either one TRP or multiple TRPs. Targeted by multiple beams provided by, each beam is its own reference signal It has a number. Measurement of beam-specific reference signals is beam management (beam training, beam In addition to being used by lower layers for switching etc., TRP / cell level mobility It is also used for [unclear]. When the UE performs measurements on different beams, the UE uses one beam. A set of measurement results can be derived, each corresponding to a beam and its associated elements. Determining the linking behavior to the results is necessary to represent the overall TRP / cell quality. Based on the measurement model used by LTE, the following modifications are proposed.

[0305] Layer 1 filtering: As shown in Figure 44, beambase measurements allow for distinguishable cell IDs and TRP IDs. This is added to the layer 1 filtering along with the beam ID. In the ring, the measurement results for the raw beam from layer 1 filtering were TRP / Cellule The results are converted to Bell measurement results. Several candidate conversion metrics are listed below. ru: 1. Average or weighted moving average of the best beams: RSRP / RSRQ / RS-SINR / R SS 2. The average or weighted moving average of the best N beams: RSRP / RSRQ / RS-SIN R / RSSI (N>=1, weights may be the same or different) 3. Average or weighted moving average of all detected beams: RSRP / RSRQ / RS-S INR / RSSI 4. Mean or weighted moving average RSRP / RSRQ of beams with RSRP exceeding the threshold. / RS-SINR / RSSI 5. Total R of beams with RSRP / RSRQ / RS-SINR / RSSI exceeding the threshold SRP / RSRQ / RS-SINR / RSSI 6. The number of beams with RSRP / RSRQ / RS-SINR / RSSI exceeding the threshold.

[0306] Depending on the UE category and use case, these metrics are used differently. Therefore, various UEs can have different RF / computing / memory capabilities. For example, metrics can be switched via RRC(re)configuration, or It may be statically configured by the operator or manufacturer and stored in on-chip memory. In addition, there are different use cases in NR (e.g., eMBB, mMTC, URLL). C) also prefers the flexible use of these metrics. For example, mMTC devices use data Focusing on energy efficiency rather than rate, RRC(re)configuration is from an overhead perspective. It is expensive, and it is also relatively slow. As a result, the PHY of these metrics And the different impacts on RRC should therefore be carefully considered during implementation. The following is an example of comparing the first three metrics.

[0307] (Best beam) Description: RRC receives the best beam result as the result of the corresponding cell / TRP. Thus, all existing cell-based measurement reporting standards in LTE will be reused. This can be done. Impact on PHY and RRC: It is simple for both PHY and RRC. Therefore, the beam is transparent to the RRC. In this way, all existing cells in LTE The measurement reporting standards and procedures can be reused.

[0308] (N beams) Description: Average measurement of N beams from PHY to RRC for each individual cell / TRP The result. RRC receives the average result as the result of the corresponding cell. PHY and RRC Impact: Several average criteria for N beams need to be introduced into the PHY ( (Probably, there is no need to specify it, and it is simply left to the PHY implementation.) It is simple, and the beam is transparent to the RRC. All existing cell base in LTE The measurement reporting standards and procedures can be reused.

[0309] (All detected beams) Description: All detected beams from PHY to RRC for each individual cell / TRP Measurement results. RRC obtains measurement results specific to all raw beams. To PHY and RRC. Influence: Simple for PHY, but RRC detects all beam-specific measurement results (detected) It processes (which is not scalable when the number of beams is large), so it is more complex than RRC. Yes. Several filtering methods implement cell / TRP-based measurement reporting standards. Before doing so, it is necessary to convert these beam-specific measurement results into cell-specific measurement results. Several new measurement reporting standards based on these beam-specific measurement results have been introduced. It should be done.

[0310] Proposed measurement reporting structure: The following measurement configuration (provided to the UE) is proposed, including the following parameters: Reporting structure: A list of reporting structures, each consisting of the following: Reporting criteria: The criteria for triggering the UE to send a measurement report. This can be either periodic or a single event description; Report format: The quantity (e.g., the number of cells to report) included in the UE's measurement report and associated information.

[0311] For event-based measurement reports, a group of trigger events is defined ( e.g., A1 - A6, etc.). In NR, it is assumed that similar reporting criteria should also be included. An efficient design of the reporting criteria can potentially reduce unnecessary signal overhead and interference in the air interface, still maintain quick, accurate, and reliable measurement results, and facilitate mobility decisions. Examples of reporting trigger criteria in NR may include one or several of the following.

[0312] Event NR - A1: A serving beam or / and TRP better than a threshold. This event can be used to trigger whether to send a measurement report.

[0313] Examples of entry and exit conditions can be defined as Ms - Hys > Thresh (entry condition) and Ms + Hys < Thresh (exit condition).

[0314] Ms is the measurement result of the serving beam without considering any offset (for simultaneous use of multiple beams, a certain type of weighted average method is used, which can be implementation - dependent ). In the case of TRP evaluation, Ms can be the measurement result of the serving TRP to which the serving beam belongs and the value of Ms can be converted from the beam level measurement by using the selected conversion metric (see the above layer 3 filtering).

[0315] Hys is the hysteresis parameter for this event. When the measured value of Ms fluctuates around the target value (Thresh), the measurement report will not be triggered unless the fluctuation is wider than Hys.

[0316] Thresh is the threshold parameter for this event.

[0317] Ms is in dBm for RSRP and RSSI, and in dB for RSRQ and RS-SINR.

[0318] Hys is in dB.

[0319] Thresh is expressed in the same unit as Ms.

[0320] When the entry condition is met, the measurement report can be temporarily stopped to reduce signal overhead and interference in the network, as well as the UE's energy consumption. When the exit condition is met, the measurement report can be resumed unless other events / triggers need to be evaluated.

[0321] Event NR-A2: The serving beam or / and TRP becomes worse than threshold 1, and the neighboring beam or / and TRP becomes better than threshold 2. This event can be used to trigger the start of intra-TRP, inter-TRP, and inter-cell mobility evaluation (beam level or TRP / cell level).

[0322] Examples of entry and exit conditions are Ms + Hys < Thresh1 (entry condition 1), Mn + O fn + Ocn - Hys > Thresh2 (Entry condition 2), Ms - Hys > Thresh1 (Exit condition 1), and Mn + Ofn + Ocn + Hys < Thresh2 (Exit condition 2) can be defined as such.

[0323] Ms and Hys are the same as event NR - A1.

[0324] Mn is the measurement result of an adjacent beam without considering any offset. In the case of adjacent TRP evaluation , Mn can be the measurement result of the adjacent TRP to which the adjacent beam belongs, and the value of Mn<0003​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ If this condition is satisfied over the timer defined duration, beam level, TR P level, or even cell level mobility determination can be made based on the selected neighboring beams, TRP, and cells. When exit condition 1 or 2 is satisfied, the UE can return to the measurement report behavior before entering this event.

[0330] Event NR - A3: The serving beam or / and TRP becomes worse than a threshold. This event can be used to immediately trigger mobility determination without requiring it to be satisfied over a given duration.

[0331] Exemplary entry and exit conditions can be defined as Ms + Hys < Thresh (entry condition) and Ms - Hys > Thresh (exit condition).

[0332] Ms, Hys, Thresh are the same as those for event NR - A1.

[0333] When the entry condition is satisfied, it means that the quality of the serving beam can be significantly lower than the value, suggesting an immediate beam switch. When the exit condition is satisfied, the previous report evaluation criteria for this event, such as continuously measuring the quality of the serving beam over a duration as defined in event NR - A2, can be resumed.

[0334] Measurement events can be based on the expiration of a periodic timer. This can be applied to periodic measurement reports. The UE can be configured with a periodic measurement report timer for a given measurement configuration.

[0335] Content of the measurement report at point D: Not only the measured cell information (e.g., NR cell ID), but also the measurement that meets the measurement reporting criteria. This also includes the TRP / beam information (e.g., TRP ID, beam ID). This may also include TRPs (beams or cells) that experience wireless link failure or weak signal quality. .

[0336] The entities that perform the steps illustrated in Figure 18 are shown in Figures 1B and 1F. For wireless and / or network communications or computer systems The software is stored in the memory of the device and executed on its processor. In other words, it can be a logical entity that can be implemented in the form of a computer executable instruction. It is understood that the method illustrated in Figure 18 is the same as the method illustrated in Figures 1B and 1F. Software stored in the memory of a device or computer system (that is, It can be implemented in the form of computer executable instructions, and those computer executable instructions When executed by the device's processor, it performs the steps illustrated in Figure 20-24. do.

[0337] The GUI and other interfaces assist the user and support the beam sweep frame structure and N Used to control and / or configure functionality related to R random access. This is possible. Figure 45 shows the user's beam sweep frame structure and NR random access. The diagram shows interface 3202, which allows for the visualization and configuration of related functionalities. This is a schematic diagram. Interface 3202 displays the information shown in Figures 1C-D, etc. Please understand that it can be generated using this method.

[0338] Figure 46 allows the user to input parameters corresponding to index values. This is a schematic diagram illustrating GUI2002. Interface 2002 is shown in Figures 1B and 1. It may be generated using symbols such as those shown in F, and its computer executable instructions are equipped When executed by the processor, it performs the steps illustrated in Figure 20-24. Please understand this.

[0339] The system and methods are described in terms of what is currently considered a concrete aspect. However, this application is not limited to the aspects disclosed. In spirit and within the scope of the claims It is intended to cover various modifications and similar sequences, and its scope is to include all of them. The broadest possible interpretation should be given to encompass such modifications and similar structures. This disclosure includes any and all aspects of the following claims.

Claims

1. Apparatus, the apparatus, Non-transient memory containing instructions for performing random access in a network, A processor operably coupled to the aforementioned non-transient memory and The processor is equipped with, An instruction to measure a beam in a downlink sweep subframe, wherein the downlink sweep subframe includes an initial access signal comprising two or more synchronization signals and a master information block (MIB) constituting system information (SI), and the two or more synchronization signals are composed of a synchronization signal and a beam training reference signal, A command to select a first downlink transmission beam based on the measured beam, Instructions for determining the random access preamble associated with the first downlink transmission beam and the physical random access channel (PRACH) resource associated with the first downlink transmission beam, The system is configured to execute an instruction that transmits the random access preamble to a node via the PRACH resource, The random access preamble is selected from a set of random access preambles associated with the first downlink transmission beam based on the device type and service type. The PRACH resource is randomly selected from a set of PRACH resources associated with the first downlink transmission beam.

2. The apparatus according to claim 1, wherein the preamble includes a cyclic prefix period, a Zadoff-Chu sequence period, and a protection period in a continuous manner.

3. The aforementioned processor, Instructions to monitor the downlink control channel for random access responses (RARs), A command to receive the RAR from the node and The apparatus according to claim 1, configured to further perform the following.

4. The PRACH resource is configured in the uplink sweep slot of the uplink subframe, The apparatus according to claim 1, wherein the time resource of the PRACH resource is determined by the first downlink transmission beam.

5. The apparatus according to claim 3, wherein the command to be monitored continues over a period including one or more downlink sweep subframes.

6. The apparatus according to claim 5, wherein the command to be monitored includes identifying the Random Access Radio Network Temporary Identifier (RA-RNTI) of the RAR.

7. The apparatus according to claim 6, wherein the RAR includes a random access preamble identifier that matches the transmitted random access preamble.

8. The apparatus according to claim 1, wherein the network is a new wireless (NR).

9. The apparatus according to claim 1, wherein the apparatus is a user device.

10. The apparatus according to claim 1, wherein the node is a base station.

11. A wireless communication method in a network, Transmitting an initial access signal via a first downlink transmission beam, which includes two or more synchronization signals and a master information block (MIB) constituting system information (SI), wherein the two or more synchronization signals consist of a synchronization signal and a beam training reference signal. A wireless communication method comprising receiving a random access preamble selected from a set of random access preambles associated with the first downlink transmission beam, based on a device type and a service type, via a physical random access channel (PRACH) resource associated with the first downlink transmission beam.

12. The wireless communication method according to claim 11, wherein the preamble successively includes a cyclic prefix period, a Zadoff-Chu sequence period, and a protection period.

13. The wireless communication method according to claim 11, wherein the network is a new wireless (NR).

14. A wireless transceiver unit (WTRU), The system receives configuration parameters associated with a physical random access channel (PRACH), and these configuration parameters indicate multiple random access preambles and multiple PRACH resources. Based on the device type and service type, a random access preamble is selected from the plurality of random access preambles. The selected random access preamble is transmitted via at least one PRACH resource among the plurality of PRACH resources. The downlink control channel is monitored for information associated with the random access response (RAR) in response to the transmission of the selected random access preamble. A wireless transceiver unit equipped with a processor configured in such a way.

15. The plurality of random access preambles comprises a plurality of random access preamble subsets, and the selected random access preamble is associated with the random access preamble subset corresponding to the service type. The wireless transmitting and receiving unit according to claim 14.

16. The configuration parameter associated with the PRAC is received via a broadcast of system information. The wireless transmitting and receiving unit according to claim 14.

17. The service type corresponds to a network slice, and the random access preamble subset associated with the selected random access preamble is associated with the network slice. The wireless transceiver unit according to claim 15.

18. The at least one PRACH resource is randomly selected from a plurality of PRACH resources associated with a first downlink transmit beam based on the measured beam. The wireless transmitting and receiving unit according to claim 14.

Images