Communication based on random access

Abstract

The present disclosure provides a method performed by a UE. The method may include: transmitting random access preamble to a base station; receiving response message in response to the random access preamble from the base station; transmitting request message related to fast connection recovery time-sensitive networking to the base station, based on an application of the UE; and receiving information related to dedicated preamble from the base station.

Description

COMMUNICATION BASED ON RANDOM ACCESS

[0001] The present specification relates to a radio communication.

[0002] 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

[0003] Work has started in International Telecommunication Union (ITU) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0004] The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLLC), etc. The NR shall be inherently forward compatible.

[0005] In prior arts, when communication disruption occurs for a User Equipment (UE), time period for securely reconnecting is required to be less than 1 second. However, shorter time period for reconnecting such as 100ms or 10ms was not supported.

[0006] A UE and a base station may perform random access based on a dedicated preamble.

[0007] In one aspect, provided is a method for performing communication by a UE. The method may comprise: transmitting random access preamble to a base station; receiving response message in response to the random access preamble from the base station; transmitting request message related to fast connection recovery time-sensitive networking to the base station, based on an application of the UE; and receiving information related to dedicated preamble from the base station.

[0008] In an embodiment, an apparatus for implementing the above method is provided.

[0009] In one aspect, provided is a method for performing communication by a base station. The method may comprise: transmitting random access preamble to a base station; receiving random access preamble from a UE; transmitting response message in response to the random access preamble to the UE; receiving request message related to fast connection recovery time-sensitive networking from the UE; and transmitting information related to dedicated preamble to the UE.

[0010] In an embodiment, an apparatus for implementing the above method is provided.

[0011] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0012] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0013] FIG. 3 shows an example of UE to which implementations of the present disclosure is applied.

[0014] FIG. 4 shows an example of 5G system architecture to which implementations of the present disclosure is applied.

[0015] FIGS. 5a through 5e shows an example of RACH procedures applicable to an embodiment of the present disclosure.

[0016] FIGS. 6a and 6b illustrate an example of operations of a robot according to an embodiment of the present disclosure.

[0017] FIG. 7 illustrates an example of CBRA with 4-step RA type.

[0018] FIG. 8 illustrates an example of CBRA with 2-step RA type.

[0019] FIGS. 9a and 9b illustrates an example of operations for the first example of the present disclosure.

[0020] FIG. 10 illustrates an example of operations for the second example of the present disclosure.

[0021] FIG. 11 illustrates an example of operations according to an embodiment of the present disclosure.

[0022] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi Carrier Frequency Division Multiple Access (MC-FDMA) system. CDMA may be embodied through radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA may be embodied through radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is a part of a Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in downlink (DL) and SC-FDMA in uplink (UL). Evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).

[0023] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0024] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

[0025] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0026] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0027] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0028] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".

[0029] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0030] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0031] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0032] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0033] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0034] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0035] Three main requirement categories for 5G include (1) a category of enhanced Mobile BroadBand (eMBB), (2) a category of massive Machine Type Communication (mMTC), and (3) a category of Ultra-Reliable and Low Latency Communications (URLLC).

[0036] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, Base Stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0037] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0038] The wireless devices 100a to 100f represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet-of-Things (IoT) device 100f, and an Artificial Intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

[0039] In the present disclosure, the wireless devices 100a to 100f may be called User Equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, a slate Personal Computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0040] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V) / Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0041] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or Device-to-Device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, Integrated Access and Backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0042] NR supports multiples numerologies (and / or multiple Sub-Carrier Spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0043] The NR frequency band may be defined as two types of frequency range, i.e., Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter Wave (mmW).

[0044] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0045] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0046] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0047] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include NarrowBand IoT (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate Personal Area Networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

[0048] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0049] In FIG. 2, The first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / parts, and / or modules.

[0050] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and / or one or more antennas 108.

[0051] The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. Additional and / or alternatively, the memory 104 may be placed outside of the processing chip 101.

[0052] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106 and then store information obtained by processing the second information / signals in the memory 104.

[0053] The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a firmware and / or a software code 105 which implements codes, commands, and / or a set of commands that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more protocols. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.

[0054] Herein, the processor 102 and the memory 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0055] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and / or one or more antennas 208.

[0056] The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. Additional and / or alternatively, the memory 204 may be placed outside of the processing chip 201.

[0057] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 106 and then store information obtained by processing the fourth information / signals in the memory 204.

[0058] The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a firmware and / or a software code 205 which implements codes, commands, and / or a set of commands that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more protocols. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.

[0059] Herein, the processor 202 and the memory 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0060] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Unit (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0061] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a memory control processor.

[0062] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cash memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0063] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0064] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208. Additionally and / or alternatively, the one or more transceivers 106 and 206 may include one or more antennas 108 and 208. The one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0065] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202.

[0066] Although not shown in FIG. 2, the wireless devices 100 and 200 may further include additional components. The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, an Input / Output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The additional components 140 may be coupled to the one or more processors 102 and 202 via various technologies, such as a wired or wireless connection.

[0067] In the implementations of the present disclosure, a UE may operate as a transmitting device in Uplink (UL) and as a receiving device in Downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

[0068] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

[0069] FIG. 3 shows an example of UE to which implementations of the present disclosure is applied.

[0070] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.

[0071] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a Subscriber Identification Module (SIM) card 145, a speaker 146, and a microphone 147.

[0072] The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of DSP, CPU, GPU, a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by Qualcomm®, EXYNOSTMseries of processors made by Samsung®, A series of processors made by Apple®, HELIOTMseries of processors made by MediaTek®, ATOMTMseries of processors made by Intel®or a corresponding next generation processor.

[0073] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0074] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

[0075] The power management module 141 manages power for the processor 102 and / or the transceiver 106. The battery 142 supplies power to the power management module 141.

[0076] The display 143 outputs results processed by the processor 102. The keypad 144 receives inputs to be used by the processor 102. The keypad 144 may be shown on the display 143.

[0077] The SIM card 145 is an　integrated circuit　that is intended to　securely store the　International Mobile Subscriber Identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0078] The speaker 146 outputs sound-related results processed by the processor 102. The microphone 147 receives sound-related inputs to be used by the processor 102.

[0079] FIG. 4 shows an example of 5G system architecture to which implementations of the present disclosure is applied.

[0080] The 5G system (5GS) architecture consists of the following network functions (NF).

[0081] - Authentication Server Function (AUSF)

[0082] - Access and Mobility Management Function (AMF)

[0083] - Data Network (DN), e.g., operator services, Internet access or 3rd party services

[0084] - Unstructured Data Storage Function (UDSF)

[0085] - Network Exposure Function (NEF)

[0086] - Intermediate NEF (I-NEF)

[0087] - Network Repository Function (NRF)

[0088] - Network Slice Selection Function (NSSF)

[0089] - Policy Control Function (PCF)

[0090] - Session Management Function (SMF)

[0091] - Unified Data Management (UDM)

[0092] - Unified Data Repository (UDR)

[0093] - User Plane Function (UPF)

[0094] - UE radio Capability Management Function (UCMF)

[0095] - Application Function (AF)

[0096] - User Equipment (UE)

[0097] - (Radio) Access Network ((R)AN)

[0098] - 5G-Equipment Identity Register (5G-EIR)

[0099] - Network Data Analytics Function (NWDAF)

[0100] - CHarging Function (CHF)

[0101] Furthermore, the following network functions may be considered.

[0102] - Non-3GPP InterWorking Function (N3IWF)

[0103] - Trusted Non-3GPP Gateway Function (TNGF)

[0104] - Wireline Access Gateway Function (W-AGF)

[0105] FIG. 4 depicts the 5G system architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other.

[0106] In FIG. 4, for the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary.

[0107] For clarity, the UDR and its connections with other NFs, e.g., PCF, are not depicted in FIG. 4. For clarity, the NWDAF and its connections with other NFs, e.g., PCF, are not depicted in FIG. 4.

[0108] The 5G system architecture contains the following reference points:

[0109] - N1: Reference point between the UE and the AMF.

[0110] - N2: Reference point between the (R)AN and the AMF.

[0111] - N3: Reference point between the (R)AN and the UPF.

[0112] - N4: Reference point between the SMF and the UPF.

[0113] - N6: Reference point between the UPF and a Data Network.

[0114] - N9: Reference point between two UPFs.

[0115] The following reference points show the interactions that exist between the NF services in the NFs.

[0116] - N5: Reference point between the PCF and an AF.

[0117] - N7: Reference point between the SMF and the PCF.

[0118] - N8: Reference point between the UDM and the AMF.

[0119] - N10: Reference point between the UDM and the SMF.

[0120] - N11: Reference point between the AMF and the SMF.

[0121] - N12: Reference point between the AMF and the AUSF.

[0122] - N13: Reference point between the UDM and the AUSF.

[0123] - N14: Reference point between two AMFs.

[0124] - N15: Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario.

[0125] - N16: Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network).

[0126] - N22: Reference point between the AMF and the NSSF.

[0127] In some cases, a couple of NFs may need to be associated with each other to serve a UE.

[0128] <Random Access Channel (RACH) Procedure>

[0129] FIGS. 5a through 5e shows an example of RACH procedures applicable to an embodiment of the present disclosure.

[0130] Referring to FIGS. 5a through 5e, a RACH procedure is described, according to one embodiment of the present disclosure. The embodiments of FIGS. 5a through 5e may be combined with various embodiments of the present disclosure.

[0131] In one embodiment of the disclosure, where RF requirements (e.g., Tx RF performance requirements and / or Rx RF performance requirements) are described, the UE may satisfy those RF requirements. For example, a UE may be tested to satisfy RF requirements (e.g., Tx RF performance requirements and / or Rx Rf performance requirements) according to one embodiment of the disclosure. In one embodiment of the disclosure, a UE that meets these RF requirements may perform the RACH procedure. When the UE transmits messages, data, signaling, etc. to the gNB, the UE satisfies the Tx RF performance requirements described in the first embodiment of this specification. When the UE receives messages, data, signaling, etc. from the gNB, the UE satisfies the Rx RF performance requirements described in the first embodiment of this specification.

[0132] To connect the UE to the 5G network, the UE and the 5G network must synchronize in the uplink and downlink. Downlink synchronization is performed when the UE successfully decodes the SSB transmitted by the gNB. To establish the uplink synchronization and RRC connection, the UE shall perform the RACH random access procedure.

[0133] Two types of random access procedures are supported. The two types of random access procedures include a four-stage Random Access (RA) type using MSG1 and a two-stage RA type using MSGA.

[0134] The two types of RA procedures can support Contention Based Random Access (CBRA) and Contention Free Random Access (CFRA), as shown in FIG. 5a through FIG. 5e below, respectively. The UE may select the random access type at the beginning of the random access procedure, depending on the network configuration.

[0135] Referring to FIG. 5a and FIG. 5c, a four-stage RA type using MSG1 is illustrated.

[0136] Step 4 The MSG1 of RA type contains the preamble of the PRACH. The UE transmits the MSG1. After the UE sends the MSG1, the UE monitors the network for a response within the set window.

[0137] For CBRA according to the example of FIG. 5a, when the UE receives a random access response (MSG2) from the gNB, the UE may transmit MSG3 using the UL grant scheduled by the response message. The UE may then monitor the contention resolution. If contention resolution is not successful after the MSG3 (re)transmission, the UE shall perform the MSG1 transmission again.

[0138] For CFRA according to the example in FIG. 5c, a dedicated preamble for MSG1 transmission is allocated by the network. The gNB sends the RA preamble assignment to the UE. The UE transmits an MSG1 containing the random access preamble to the gNB. Upon receiving the random access response from the network, the UE terminates the random access procedure.

[0139] Referring to FIGS. 5b, 5d, and 5e, a two-stage RA type is described. The MSGA of the two-stage RA type includes a random access preamble on the PRACH and a PUSCH payload. After the UE transmits the MSGA, the UE monitors the response from the network within a set window.

[0140] For CBRA according to the example of FIG. 5b, after the UE receives the network response (e.g., MSGB), if the contention resolution is successful, the UE terminates the random access procedure. If the fallback indication is received within the MSGB, the UE performs the MSG3 transmission using the UL grant scheduled in the fallback indication and monitors the contention resolution, as shown in FIG. 5e. If contention resolution is not successful after the MSG3 (re)transmission, the UE shall perform the MSGA transmission again.

[0141] In the case of CFRA according to the example of FIG. 5d, the UE may receive RA preamble allocation and PUSCH allocation from the gNB. Dedicated preamble and PUSCH resources may then be set up for MSGA transmission. The UE transmits the MSGA. When the UE receives a network response, the UE terminates the random access procedure.

[0142] If the random access procedure of the two-stage RA type is not completed after several MSGA transmissions, the UE may be set to switch to the CBRA of the four-stage RA type.

[0143] In the present disclosure, a UE may be a robot. Multiple robots may perform communication between robots and with network.

[0144] As an example, online cooperative high-resolution 3D map building may be explained.

[0145] This use case considers a low-energy (or energy-efficient) cooperation scenario to collaboratively build a 3D map among a group of multiple robots. This use case may aim at usage for unstructured settings, such as enterprise building cleaning, preparation for disinfection of large-scale building, and automation for agriculture. With cooperation among multiple robots gathering measurement data, it would be possible to either save energy or build a better quality outcome, or to attain both.

[0146] For example, some aspects related to "automation for agriculture" can also be studied with a combined scenario of ground mobility and aerial mobility.

[0147] For example, the meaning of "map" in this use case is not necessarily limited to geographic appearance but it may also include still life objects that are useful or essential for robots working in an irregular and / or unstructured setting.

[0148] A group of service robots that are equipped with capabilities of multi-dimensional ambient sensing, computing (standalone and / or via compute fabric), federation in learning and model building, and 3GPP subscription-based communication, are in cooperation for a single joint project.

[0149] The availability of communication service to / from edge (or cloud) may be threefold: not available, temporarily unavailable, or available (for certain period of time; positive interpretation although the term "available" does not mean "permanently available").

[0150] For example, this use case may be focused on ProSe-based operation (also, referred to as "ProSe-based") with partial or intermittent connection to NG-RAN (or to edge server via NG-RAN).

[0151] The edge (e.g., a server), if available for one or more of these service robots, will assist them to alleviate their computational burdens (that are or are not within the scope of 3GPP), giving rise to a demand of accessing service-specific network slice(s) or other forms of network resources with certain performance requirements.

[0152] An operator of robotic applications starts operating a group of service robots which are UEs.

[0153] These service robots discover each other and share their capabilities.

[0154] For example, for each service robot (i.e., UE), capabilities include certain characteristics such as types of supported RATs (e.g., NR, E-UTRA, or non-3GPP access technology) and information that are not within the scope of communications layer, such as remaining battery life.

[0155] All or some of these service robots form a working group (with one or more leader robots) and starts communicating.

[0156] Member robots send measurement data to a leader robot so that the leader robot can perform the next step to build a 3D map.

[0157] NOTE 5: The roles of leader robot(s) include coordination required for the operation of the working group of service robots, such as acting as sync master for other robots (sync devices) within the working clock domain.

[0158] Robots may scan environmental parameters, including 3GPP service availability, and collaboratively decide which operational scenario they should choose (i.e., Uu-based or ProSe-based, also referred to as ProSe-based).

[0159] Each service robot in the working group walks in coordination with each other, forming a gregarious cluster (i.e., distance between any pair is not unnecessarily far, degrading the performance of map building outcome).

[0160] Each robot is exposed to uneven surface along its trajectory (e.g., signal angle measurement is not static, unpredicted loss of measurement accuracy level is likely to happen).

[0161] Depending on the accuracy level of 3D map at certain spot of the job site and decision made by the leader robot(s), the application layer of the leader robot requests to adjust the clock synchronization target value within the clock synchronization budget.

[0162] While moving along, one member robot, say robot A, faces some issue, resulting an unexpected drop in the moving speed.

[0163] Member robot A has already predicted this issue beforehand: its follow-up actions include reporting this information to a leader robot and marking time stamp on the measurement data with this outlier situation.

[0164] It is up to member robot A whether or not, to send the measurement data including outlier indication to a leader robot.

[0165] It is up to the leader robot whether or not, to use the received data with outlier indication, if received from member robot A, for 3D map building.

[0166] Later, member robot A gets a little bit away from the gregarious cluster, leading to a temporary loss of connection to a relay UE robot (or to gNB in Uu-based scenario). Member robot A may promptly resume a connection.

[0167] The following drawings are intended to illustrate specific embodiments of the present disclosure. The designations of specific devices or the designations of specific signals / messages / fields shown in the drawings are for illustrative purposes only, and the technical features of the present specification are not limited to the specific designations used in the drawings below.

[0168] FIGS. 6a and 6b illustrate an example of operations of a robot according to an embodiment of the present disclosure.

[0169] FIGS. 6a and 6b show examples of inter-robot operation and intra-robot operations of a robot. In FIGS. 6a and 6b, inter-robot operation example when a network of service robots that have ambient intelligence (e.g., intra-robot operation) may be performed.

[0170] The working group of robots (e.g., service robots) may build up 3D map with only necessary level of accuracy so that they do not have to consume computing and communication resources to build up a 3D map of an area that is overly accurate.

[0171] FIG. 6a shows an example of inter-robot operation. As shown in FIG. 6a, robot performs inter-robot operations based on multi-radio interface with other robots. Robots may share intent and environmental data. The robot may be accessible to network fabric via 3GPP system. At least one of base stations(e.g., gNB) may be connected to edge (e.g., server).

[0172] FIG. 6b shows an example of intra-robot operation. A robot may be input data for state estimation and sensing / localization. The robot may perform policy update and / or phase-based optimal control based on state estimation data and sensing / localization data. The robot may be controlled by state-feedback control which is based on state estimation, policy update, and phase-based optimal control.

[0173] For an important area, robots may adjust the level of accuracy.

[0174] Robots may prevent potential noise factors that could have negatively contributed to the quality of 3D map with the help of prediction-based indication.

[0175] A robot that has instantaneously lost a connection can resume a connection very promptly and send time-critical information to other member(s).

[0176] According to the prior arts, challenges and potential gaps exist.

[0177] It is required that 5G system is expected to be able to provide a means to ensure a very high accuracy level of clock synchronization to support that a group of service robots can build up 3D map collaboratively (i.e., synchronization among service robots within a collaborating group and synchronization among the multiple sources related to the respective service robots) in which the accuracy level is required by the applications layer.

[0178] It is required that 5G system is expected to be able to ensure the integrity and validity of clock synchronization for a designated length of time when a group of service robots are in ProSe-based operation outside the coverage area served by NG-RAN.

[0179] The time length may be dependent upon the type of project and is required by a service robot's application.

[0180] If the integrity and validity of clock synchronization cannot be ensured for a designated length of time, the 5G system is expected to notify the application.

[0181] It is required that 5G system is expected to be able to provide a means for UE(s) to adjust the accuracy level of clock synchronization.

[0182] It is required that 5G system is expected to be able to provide a means to share the accuracy level and integrity-related information of clock synchronization with the cloud (in Uu-based scenario) or with the leader robot (in ProSe-based scenario).

[0183] It is needed that a network be able to provide a means to resume the connection when an ongoing connection is disrupted (e.g., due to radio link failure b / w a robot and the communicating counterpart) within a very short period of time, required by the applications layer. For example, according to examples of the present disclosure, resuming the connection when an ongoing connection is disrupted (e.g., due to radio link failure b / w a robot and the communicating counterpart) within a very short period of time, required by the applications layer may be supported.

[0184] For example, in prior arts, the current time period for securely reconnecting is required to be less than 1s. However, robotic applications that perform critical roles may require much shorter time period, such as less than 100ms for critical, less than 10ms for highly critical.

[0185] Prior arts did not cover scenarios where the service robot experiencing more severe levels of disruptions, such as 3GPP registration state changes.

[0186] It is needed that a 5G system is expected to be able to provide a means to allow a member robot that has predicted communication disruption or measurement failure to disseminate necessary information, which is required by the applications layer, to one or more destinations within a very short period of time required by the applications layer.

[0187] For example, in prior arts, the required time period is application dependent (e.g. <100ms for moderate level of disruption, <10ms for critical level of disruption). The above Challenge and Potential Gap (CPG) is intended for both Radio Resource Control (RRC) Connected mode and RRC-Inactive mode. It is not intended that the above CPG is applicable to RRC Idle mode.

[0188] Based on the request from the application (e.g., from an application of the leader robot in a robot group, or from an application in the cloud server), 5G system is expected to adjust the accuracy level of clock synchronization.

[0189] Possible scenarios regarding the referred robot group may include a group of "automated robots", a group of "fully autonomous robots", a group of "tele-operated robots", and a group that consists of a suitable combination of those kinds of robots.

[0190] In the present disclosure, the following problem may be solved:

[0191] It is needed that a network be able to provide a means to resume the connection when an ongoing connection is disrupted (e.g., due to radio link failure between a robot and the communicating counterpart) within a very short period of time, required by the applications layer.

[0192] For example, in prior arts, the current time period for securely reconnecting is required to be less than 1s. However, robotic applications in a UE (e.g., a robot) that perform critical roles may require much shorter time period, such as less than 100ms for critical, less than 10ms for highly critical.

[0193] It is not intended to cover scenarios where the service robot experiencing more severe levels of disruptions, such as 3GPP registration state changes.

[0194] For example, according to examples of the present disclosure, resuming the connection when an ongoing connection is disrupted (e.g., due to radio link failure b / w a robot and the communicating counterpart) within a very short period of time, required by the applications layer may be supported.

[0195] Examples of the present disclosure are explained. A robot and a UE are used as a term with a same meaning in the present disclosure.

[0196] A group of Robots (UEs) may attempt to form a Group Communication group. For example the group communication group may be Group Communication System Enablers (GCSE) group. In order to distribute the downlink media within a Group, the UE and the network may use eMBMS bears or to use unicast bearers or to use Protocol Data Unit (PDU) session.

[0197] The following drawings are intended to illustrate specific embodiments of the present disclosure. The designations of specific devices or the designations of specific signals / messages / fields shown in the drawings are for illustrative purposes only, and the technical features of the present specification are not limited to the specific designations used in the drawings below.

[0198] FIG. 7 illustrates an example of CBRA with 4-step RA type. FIG. 8 illustrates an example of CBRA with 2-step RA type.

[0199] When a Robot (UE 1) attempts to perform Random Access (RA) procedure. The type of RA may be CBRA with 4-step RA type according to FIG. 7 or CBRA with 2-step RA type according to FIG. 8.

[0200] The UE may perform RA procedure based on FIG. 8. MSGA may mean message A which corresponds to random access preamble and PUSCH payload. The term "MsgA" is part of a procedure aimed at reducing latency and control-signaling overhead by minimizing the number of messages transmitted during the access phase. This process involves a preamble sent via the physical random access channel (PRACH) and additional data through the physical uplink shared channel (PUSCH). If the random access procedure with 2-step RA type is not completed after a number of MSGA transmissions by the UE, the UE can be configured to switch to CBRA with 4-step RA type. Then, the UE performs RA procedure based on FIG. 7.

[0201] This may cause the problem that a network and a UE cannot resume the connection when an ongoing connection is disrupted (e.g., due to radio link failure b / w a robot and the communicating counterpart) within a very short period of time, required by the applications layer.

[0202] Hereinafter, a first example of the present disclosure and a second example of the present disclosure are explained.

[0203] The first example of the present disclosure includes operations based on working with Robot server and gNB.

[0204] A Robot (say, Robot 1 / UE 1) completes Random Access procedure. Once the robot completes the random access procedure, the robot may perform operations based on a certain task.

[0205] If the Robot works on certain task that requires time-sensitive networking, the Robot shall transmit a request message to a server so that the Robot can be arranged by the server to receive a higher priority from gNB (or base station) to recover the connection from communication disruption if it happens. For example, the robot may transmit a request message for a fast recovery to a robot server so that the robot server takes actions to RAN (e.g., gNB or AMF in Core Network) to provide a higher priority to this UE (or this Robot) when the Robot needs to attempt for reconnection or recovery of the lost or disrupted connection. The request message may be a fast_recovery_ra_request message.

[0206] For example, the request message may include the gNB id information (e.g., cell ID in RA-Report) for the Robot server. RA-Report may mean a RA report message. Based on the request message, the robot server can be aware of which gNB to contact when necessary. For reference, the robot server is an example of a server that the UE can communicate with. The scope of the present disclosure is not limited to the term "robot server".

[0207] If a server (e.g., Robot server) receives the request message, the server request the indicated gNB to assign a preamble dedicated to the Robot (Robot 1) for a designated time period (e.g., T1). If the time period is not specified, the time period may be unlimited or be equal to a predetermined value.

[0208] If the gNB is available to assign a dedicated preamble to the Robot, the gNB may assign the dedicated preamble to the robot. The gNB transmit a information including the dedicated preamble and the designated time period info (if there is no designated time period, the field can be empty when sending out to the Robot) to the robot.

[0209] The first example of the present disclosure may be performed based on the example of FIGS. 9a and 9b.

[0210] The following drawings are intended to illustrate specific embodiments of the present disclosure. The designations of specific devices or the designations of specific signals / messages / fields shown in the drawings are for illustrative purposes only, and the technical features of the present specification are not limited to the specific designations used in the drawings below.

[0211] FIGS. 9a and 9b illustrates an example of operations for the first example of the present disclosure.

[0212] Before step S901, UE 1 has performed random access procedure. For example, UE 1 may have performed the random access procedure based on FIGS. 5a to 5e.

[0213] In S901, gNB transmits contention resolution message or random access response message of the RA procedure to UE 1. For example, the message may be any message informs the UE that the random access is completed. The message may include threshold 1 value. For example, threshold 1 value may be a time sensitive application criterion. Threshold 1 value may be used for comparing the required disruption time of an application of UE1 with threshold1.

[0214] In S902, communication layer of UE 1 transmits threshold1 value to application of UE 1. For reference, S902 may be skipped because communication layer and applications are all included in a processor in the UE. S902 may be a logical step of transmitting data within UE1.

[0215] In S903, the UE determines whether a required disruption time of the current application is less than threshold 1 value or not. If the required disruption time is less than threshold 1 value, the UE performs step S904. If the required disruption time is equal to or less than threshold 1 value, the UE does not perform step S904.

[0216] In S904, UE 1 transmits request message to server via gNB. The request message may be fast_recovery_ra_request.

[0217] In S905, the server transmits response message including time value, which is time length T1. The response message may be fast_recovery_allow_request message. The response message may mean that a RA for fat recovery is allowed for UE 1.

[0218] In S906, gNB may determine whether dedicated resource is available for UE 1 or not. If the dedicated resource is not available, the gNB transmits information related to that the request is rejected to UE 1 and the server. If the dedicated resource is available, the gNB performs step S907.

[0219] In S907, the gNB may transmit information related to the fact that the request is accepted to the server.

[0220] The gNB may transmit information related to that dedicated resource is assigned for UE1 to UE1. The information may include dedicated preamble information for UE1.

[0221] In S908, if T1 expires, the UE 1 perform step S904. If T1 does not expire, UE1 may perform S909.

[0222] In S909, disruption may happen for the current applications. Due to disruption, UE 1 buffers Uplink (UL) traffic.

[0223] In S910, the gNB buffers downlink (DL) traffic.

[0224] In S911, UE1 performs random access procedure based on the assigned dedicated resources (e.g., dedicated preamble). UE 1 can use contention-free random access for securely reconnecting to the gNB.

[0225] The second example of the present disclosure includes operations based on working with gNB.

[0226] A Robot (say, Robot 1 / UE 1) completes Random Access procedure. Once the robot completes the random access procedure, the robot may perform operations based on a certain task.

[0227] If the Robot works on certain task that requires time-sensitive networking, the Robot shall transmit a request message to a server. For example, the robot may transmit a request message for a fast recovery to a gNB. The request message may be a fast_recovery_ra_request message.

[0228] If the gNB receives the request message, the gNB may check whether it's available to assign a dedicated preamble to the Robot (Robot 1) for a designated time period (e.g., T1). If the time period is not specified, the time period may be unlimited or be equal to a predetermined value.

[0229] If the gNB is available to assign a dedicated preamble to the Robot, the gNB may assign the dedicated preamble to the robot. The gNB transmits a message including information on the dedicated preamble and the designated time period (if there is no designated time period, the field can be empty when sending out to the Robot) to the robot.

[0230] The second example of the present disclosure may be performed based on the example of FIG. 10.

[0231] The following drawings are intended to illustrate specific embodiments of the present disclosure. The designations of specific devices or the designations of specific signals / messages / fields shown in the drawings are for illustrative purposes only, and the technical features of the present specification are not limited to the specific designations used in the drawings below.

[0232] FIG. 10 illustrates an example of operations for the second example of the present disclosure.

[0233] Before step S1001, UE 1 has performed random access procedure. For example, UE 1 may have performed the random access procedure based on FIGS. 5a to 5e.

[0234] In S1001, gNB transmits contention resolution message or random access response message of the RA procedure to UE 1. For example, the message may be any message informs the UE that the random access is completed. The message may include threshold 1 value. For example, threshold 1 value may be a time sensitive application criterion. Threshold 1 value may be used for comparing the required disruption time of an application of UE1 with threshold1.

[0235] In S1002, communication layer of UE 1 transmits threshold1 value to application of UE 1. For reference, S1002 may be skipped because communication layer and applications are all included in a processor in the UE. S1002 may be a logical step of transmitting data within UE1.

[0236] In S1003, the UE determines whether a required disruption time of the current application is less than threshold 1 value or not. If the required disruption time is less than threshold 1 value, the UE performs step S1004. If the required disruption time is equal to or less than threshold 1 value, the UE does not perform step S1004.

[0237] In S1004, UE 1 transmits request message to a gNB. The request message may be fast_recovery_ra_request.

[0238] In S1005, gNB may determine whether dedicated resource is available for UE 1 or not. If the dedicated resource is not available, the gNB transmits information related to that the request is rejected to UE 1. If the dedicated resource is available, the gNB performs step S1006.

[0239] In S1006, the gNB may transmit information related to that dedicated resource is assigned for UE1 to UE1. The information may include dedicated preamble information for UE1.

[0240] In S1007, if T1 expires, the UE 1 perform step S1004. If T1 does not expire, UE1 may perform S1008.

[0241] In S1008, disruption may happen for the current applications. Due to disruption, UE 1 buffers Uplink (UL) traffic.

[0242] In S1009, the gNB buffers downlink (DL) traffic.

[0243] In S1010, UE1 performs random access procedure based on the assigned dedicated resources (e.g., dedicated preamble). UE 1 can use contention-free random access for securely reconnecting to the gNB.

[0244] Based on the first example and / or the second example of the present disclosure, the detailed procedure for a gNB to assign a dedicated preamble for the Robot is supported. So that the Robot can perform a CFRA to the same gNB, based on the dedicated preamble, when disruption has happened. For example, in the first example of the present disclosure, the UE (Robot) shall send a fast_recovery_ra_request message to Robot server. For example, in the second example of the present disclosure, the UE (Robot) shall send a fast_recovery_ra_request message to gNB.

[0245] As explained above, according the first example of the present disclosure, the Robot server requests the gNB to check if it's possible for the gNB to assign a dedicated preamble to the Robot. The gNB may check and assign one, if available. This can allow the Robot to perform a CFRA and to be able to recover the connectivity status (e.g., connection that has just been lost) as fast as possible.

[0246] As explained above, according the second example of the present disclosure, the gNB check if it's possible to assign a dedicated preamble to the Robot. If possible, the gNB assign a dedicated preamble so that the Robot (UE) can be aware of and can use the dedicated preamble when certain disruption happens. This can allow the Robot to perform a CFRA and to be able to recover the connectivity status (e.g., connection that has just been lost) as fast as possible.

[0247] According the first example and / or the second example of the present disclosure,"fast_recovery_ra_request message" can include the following:

[0248] Application ID (if defined);

[0249] UE ID (e.g., UICC, IMSI, etc.); and / or

[0250] Disruption time limit (if defined).

[0251] According the first example and / or the second example of the present disclosure, "fast_recovery_allow_request message" can include the following:

[0252] Server ID;

[0253] Application ID (if defined); and / or

[0254] UE ID (e.g., UICC, IMSI, etc.).

[0255] The following drawings are intended to illustrate specific embodiments of the present disclosure. The designations of specific devices or the designations of specific signals / messages / fields shown in the drawings are for illustrative purposes only, and the technical features of the present specification are not limited to the specific designations used in the drawings below.

[0256] FIG. 11 illustrates an example of operations according to an embodiment of the present disclosure.

[0257] In addition, operations of a UE and a base station shown in the example of FIG. 11 is only an example. The operations of the UE and the base station are not limited by the example of FIG. 11, and the UE and the base station may perform the operations described in various examples of the present specification. The base station may be the gNB in the various examples in the present disclosure.

[0258] In step S1101, the UE may transmit random access preamble to the base station.

[0259] In step S1102, the base station may transmit response message to the UE. For example, the response message includes threshold value related to a criterion for a time sensitive application.

[0260] Based on step S1102, random access procedure between the UE and the base station is completed.

[0261] The UE may determine whether required disruption time related to the application is less than the threshold value or not.

[0262] When the required disruption time related to the application is less than a threshold value related to a criterion for a time sensitive application, step S1103 is performed.

[0263] In step S1103, the UE may transmit a request message to the base station.

[0264] For example, the request message is related to fast connection recovery time-sensitive networking to the base station, based on an application of the UE. The request message may be fast_recovery_ra_request message in the present disclosure.

[0265] For example, the base station may communicate with a server(e.g., a robot server). In this case, the base station may transmit the request message to the server. The base station may receive a response message including threshold value related to a criterion for a time sensitive application from the server.

[0266] The base station may determine whether a resource for the dedicated preamble is available or not. When the resource for the dedicated preamble is available, the information in step S1104 is related to a dedicated preamble.

[0267] In step S1104, the base station may transmit information to the UE. The information is related to dedicated preamble.

[0268] For example, the information may be a message related to assigning dedicated resource(e.g., preamble) in the present disclosure.

[0269] When the the resource for the dedicated preamble is not available, the information in the information is reject message. If the base station communicates with the server, the base station transmits the reject message to the server.

[0270] Disruption may occur for the application. Then the UE may buffer UL traffic. The UE may transmit the dedicated preamble to the base station. The UE may perform contention-free random access procedure based on the dedicated preamble.

[0271] In order for a critical robotic application of a UE that requires a very stringent interruption tolerance time period (such as "less than 10 ms", "less than 100 ms") to be able to re-gain the capability to send or receive data traffic (i.e., re-establish a connection that has been lost due to some interruption), the robot UE shall be allowed to utilize a contention-free method for Random Access. Various examples are proposed in the present disclosure.

[0272] If a robot is associated with a role-critical application that is sensitive to communication disruption, the robot may transmit a request message to the gNB or the robot server. So that the robot can get an authorization to use a dedicated RA opportunity (i.e., dedicated preamble) in order to save time by performing contention-free random access.

[0273] The present specification may have various effects.

[0274] For example, when a disruption to the UE occurs, RA(e.g., contention-free RA) can be performed quickly based on a dedicated preamble.

[0275] In prior arts, if the currently available Random Access methods are used, the robot that has lost a connection or has faced communication disruption should go through a contention-based random access. However, based on the examples of the present disclosure, the following is supported. Based on a mechanism that allows a robot UE handling role-critical applications to be able to use a dedicated RA resources (e.g., dedicated preamble), the robot UE can get back to a communication mode (i.e., RRC connected mode) to be able to quickly resume their communication (i.e., transmitting or receiving data).

[0276] The effects that may be obtained from the specific examples of this disclosure are not limited to those listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art may understand or infer from this disclosure. Accordingly, the specific effects of the present disclosure are not limited to those expressly set forth herein, but may include a variety of effects that may be understood or inferred from the technical features of the present disclosure.

[0277] For reference, the operation of the terminal (e.g., UE, robot, robot UE) described in the present specification may be implemented by the apparatus of FIGS. 1 to 4 described above. For example, the terminal may be the first device 100 or the second device 200 of FIG. 2. For example, an operation of a terminal described herein may be processed by one or more processors 102 or 202 . The operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors 102 or 202 . One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 105 or 206, and may perform the operation of the terminal described herein by executing instructions / programs stored in one or more memories 104 or 204.

[0278] In addition, instructions for performing an operation of a terminal (e.g., UE) described in the present disclosure of the present specification may be stored in a non-volatile computer-readable storage medium in which it is recorded. The storage medium may be included in one or more memories 104 or 204 . And, the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operation of the terminal (e.g., UE) described in the present disclosure of the present specification.

[0279] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, UDM, server, robot server etc.) or base station (e.g., NG-RAN, gNB, eNB, RAN, E-UTRAN etc.) described herein may be implemented by the apparatus of FIGS. 1 to 3 to be described below. For example, a network node or a base station may be the first device 100 of FIG.2 or the second device 200 of FIG.2. For example, the operation of a network node or base station described herein may be processed by one or more processors 102 or 202. The operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors 102 or 202. One or more processors 102 or 202 may perform the operation of a network node or a base station described herein, by controlling one or more memories 104 or 204 and one or more transceivers 106 or 206 and executing instructions / programs stored in one or more memories 104 or 204.

[0280] In addition, instructions for performing the operation of the network node or base station described in the present disclosure of the present specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium. The storage medium may be included in one or more memories 104 or 204. And, the instructions recorded in the storage medium are executed by one or more processors 102 or 202, so that the operations of a network node or base station are performed.

[0281] In the above, preferred embodiments have been exemplarily described, but the present disclosure of the present specification is not limited to such specific embodiments, and thus, modifications, changes, or may be improved.

[0282] In the exemplary system described above, the methods are described on the basis of a flowchart as a series of steps or blocks, but are not limited to the order of the steps described, some steps may occur in a different order or concurrent with other steps as described above. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and that other steps may be included or that one or more steps of the flowchart may be deleted without affecting the scope of rights.

[0283] The claims described herein may be combined in various ways. For example, the technical features of the method claims of the present specification may be combined and implemented as an apparatus, and the technical features of the apparatus claims of the present specification may be combined and implemented as a method. In addition, the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined to be implemented as an apparatus, and the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined and implemented as a method.

Claims

1.A method for performing communication, the method performed by a User Equipment (UE) and comprising:transmitting random access preamble to a base station;receiving response message in response to the random access preamble from the base station;transmitting request message related to fast connection recovery time-sensitive networking to the base station, based on an application of the UE; andreceiving information related to dedicated preamble from the base station.2.The method of claim 1,wherein the response message includes threshold value related to a criterion for a time sensitive application.3.The method of claim 2, further comprising:determining whether required disruption time related to the application is less than the threshold value or not.4.The method of any one of preceding claims,wherein the request message is transmitted, based on that required disruption time related to the application is less than a threshold value related to a criterion for a time sensitive application.5.The method of any one of preceding claims, further comprising:performing random access procedure based on transmitting the dedicated preamble, based on a disruption occurs for the application.6.A user equipment (UE) configured to operate in a wireless communication system, the UE comprising:at least one transceiver;at least one processor; andat least one memory that stores instructions and is operably electrically connectable with the at least one processor,wherein operations performed based on the instructions being executed by the at least one processor include method of claims 1 to 5.7.An apparatus performing communication, comprising:at least one processor; andat least one memory storing instructions, operatively electrically coupled to the at least one processor, wherein the instructions are executed by the at least one processor to perform operations comprising method of claims 1 to 5.8.A non-transitory computer readable storage medium recording instructions,wherein the instructions, when executed by one or more processors, causing the one or more processors to perform operations comprising method of claims 1 to 5.9.A method for performing communication, the method performed by a base station and comprising:receiving random access preamble from a User Equipment (UE);transmitting response message in response to the random access preamble to the UE;receiving request message related to fast connection recovery time-sensitive networking from the UE; andtransmitting information related to dedicated preamble to the UE.10.The method of claim 9,wherein the response message includes threshold value related to a criterion for a time sensitive application.11.The method of claim 9 or claim 10, further comprising:transmitting the request message to a server related to communication with a robot; andreceiving a response message including threshold value related to a criterion for a time sensitive application from the server.12.The method of any one among claims 9 to 11,determining whether a resource for the dedicated preamble is available or not.13.The method of any one among claims 9 to 12,wherein the information related to dedicated preamble is transmitted, based on that the resource for the dedicated preamble is available.14.The method of any one among claims 9 to 13,receiving the dedicated preamble form the UE.15.A base station configured to operate in a wireless communication system, the base station comprising:at least one transceiver;at least one processor; andat least one memory that stores instructions and is operably electrically connectable with the at least one processor,wherein operations performed based on the instructions being executed by the at least one processor include method of claim 9 to claim 14.

Images