Method and apparatus for configuring orthogonal cover codes in a wireless communication system

OCCs for RACH-less handovers in UE improve communication efficiency and reliability in non-terrestrial networks by configuring OCCs through RRC messages, addressing inefficiencies in traditional RACH procedures.

WO2026235347A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005861
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-04-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently managing handovers, particularly in non-terrestrial networks, where traditional random access channel (RACH) procedures can lead to inefficiencies and failures, especially with the increasing demand for higher data rates and connectivity in 5G and beyond.

Method used

Implementing orthogonal cover codes (OCC) for RACH-less handovers in user equipment (UE), configured through messages like RRCReconfiguration, to enhance transmission efficiency and reliability, with fallback mechanisms for failed attempts.

Benefits of technology

Enhances communication efficiency and reliability in handover processes by optimizing transmissions in non-terrestrial networks, reducing the need for traditional RACH procedures and improving overall system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005861_12112026_PF_FP_ABST
    Figure KR2026005861_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The method includes receiving, from a base station, configuration information on a configured grant for a random access channel-less (RACH-less) handover, and identifying information associated with an orthogonal cover code(OCC) based on the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR CONFIGURING ORTHOGONAL COVER CODES IN A WIRELESS COMMUNICATION SYSTEM

[0001] Certain examples of the present disclosure relate to methods, apparatus and / or systems for using orthogonal cover codes (OCC) in various scenarios and circumstances. In various examples, a UE applies OCC in a handover procedure. For example, the UE may apply OCC to a transmission to a target cell during handover. In various examples, a UE applies OCC during an initial access procedure. For example, the UE may apply OCC for a PRACH or PUSCH transmission, and / or for Msg4 ACK / NACK. Various examples describe configuring OCC information for a UE, such as OCC length and / or OCC index. Other scenarios are provided for in further examples.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] This disclosure relates to wireless communication networks, and more particularly to a terminal and a communication method thereof in a wireless communication system.

[0009] In accordance with an aspect of the disclosure, a first aspect of the disclosure, there is provided a user equipment (UE) configured to: receive, from an entity, a message to perform a random access channel (RACH)-less handover; and apply an orthogonal cover code (OCC) for a transmission relating to the RACH-less handover, based on information configuring the OCC for the UE included in the message.

[0010] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

[0011] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0012] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which:

[0013] Figure 1a shows a schematic representation of an example of a NTN transparent architecture, and Figure 1b shows a schematic representation of an example of a NTN regenerative architecture.

[0014] Figure 2 is a call flow diagram showing an initial / random access procedure according to various examples.

[0015] Figure 3 is a call flow diagram showing a handover procedure according to various examples.

[0016] Figures 4a and 4b are call flow diagrams showing types of RACH-less handover according to various examples.

[0017] Figure 5 is a call flow diagram showing a method for applying OCC during handover according to various examples of the present disclosure.

[0018] Figures 6a and 6b are call flow diagrams showing methods for applying OCC for Msg3 according to various examples of the present disclosure.

[0019] Figure 7 is a block diagram illustrating an example structure of a network entity according to various examples of the present disclosure.

[0020] Figure 8 is a flow diagram illustrating a method of a UE according to an example of the disclosure.

[0021] Figure 9 is a block diagram of a terminal or user equipment (UE) 900 according to an embodiment of the disclosure.

[0022] Figure 10 is a block diagram of a base station (BS) 1000 according to an embodiment of the disclosure.

[0023] Figure 11 is a block diagram of a network entity 1100 according to an embodiment of the disclosure.

[0024] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.

[0025] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal and a communication method thereof in a wireless communication system.

[0026] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0027] According to a first aspect of the disclosure, there is provided a user equipment (UE) configured to: receive, from an entity, a message to perform a random access channel (RACH)-less handover; and apply an orthogonal cover code (OCC) for a transmission relating to the RACH-less handover, based on information configuring the OCC for the UE included in the message.

[0028] According to an example, the information configuring the OCC is determined from: a Configured Grant configuration included in the message, or a RACH-less configuration in the Configured Grant configuration.

[0029] According to an example, the information configuring the OCC comprises information relating to an OCC index and / or information relating to an OCC length.

[0030] According to an example, UE is configured to: determine an OCC index and / or OCC length based on the message, wherein the information configuring the OCC includes the OCC index and / or OCC length.

[0031] According to an example, the UE is configured to: upon failure of the RACH-less handover with the OCC applied to the at least one transmission, fallback to performing the RACH-less handover without applying OCC.

[0032] According to an example, the UE is configured to: record information regarding the application of OCC in the RACH-less handover for a result of the procedure.

[0033] According to an example, the RACH-less handover with the OCC applied is determined to fail if a number of attempts at performing the RACH-less handover with the OCC applied reaches or exceeds a predetermined number.

[0034] According to an example, the RACH-less handover is a non-terrestrial network (NTN) handover.

[0035] According to an example, the transmission includes an RRCReconfigurationComplete message; and / or the message is a RRCReconfiguration message.

[0036] According to an example, the UE, the entity and a target of the RACH-less handover are in a NTN.

[0037] According to an example,the UE is configured to indicate one or more of: support of OCCs for a specific scenario, and / or an OCC length supported by the UE.

[0038] According to an example, the specific scenario is a handover or a RACH-less handover; and / or the OCC length supported by the UE is associated with a specific frequency range.

[0039] According to a second aspect, there is provided a method of a user equipment (UE), the method comprising: receiving, from an entity, a message to perform a random access channel (RACH)-less handover; and applying an orthogonal cover code (OCC) for a transmission relating to the RACH-less handover, based on information configuring the OCC for the UE included in the message.

[0040] According to an example, the information configuring the OCC is determined from: a Configured Grant configuration included in the message, or a RACH-less configuration in the Configured Grant configuration.

[0041] According to an example, the information configuring the OCC comprises information relating to an OCC index and / or information relating to an OCC length.

[0042] According to an example, the method comprises: determining an OCC index and / or OCC length based on the message, wherein the information configuring the OCC includes the OCC index and / or OCC length.

[0043] According to an example, the method comprises: upon failure of the RACH-less handover with the OCC applied to the at least one transmission, falling back to performing the RACH-less handover without applying OCC.

[0044] According to an example, the method comprises: recording information regarding the application of OCC in the RACH-less handover for a result of the procedure.

[0045] According to an example, the RACH-less handover with the OCC applied is determined to fail if a number of attempts at performing the RACH-less handover with the OCC applied reaches or exceeds a predetermined number.

[0046] According to an example, the RACH-less handover is a non-terrestrial network (NTN) handover.

[0047] According to an example, the transmission includes an RRCReconfigurationComplete message; and / or the message is a RRCReconfiguration message.

[0048] According to an example, the UE, the entity and a target of the RACH-less handover are in a NTN.

[0049] According to an example, the method comprises indicating one or more of: support of OCCs for a specific scenario, and / or an OCC length supported by the UE.

[0050] According to an example, the specific scenario is a handover or a RACH-less handover; and / or the OCC length supported by the UE is associated with a specific frequency range.

[0051] According to a third aspect, there is provided a computer-readable storage medium configured to store instructions which, when executed by at least one processor of a user equipment (UE), cause the UE to perform the method of any one of claims 13 to 24.

[0052] According to another aspect of the present disclosure, there is provided a user equipment (UE) comprising: a transmitter; a receiver; and at least one processor configured to: identify a trigger to perform a procedure, the procedure being an initial access procedure or a reconfiguration procedure to establish the UE with an entity; during performance of the procedure, apply an orthogonal cover code (OCC) for at least one transmission relating to the procedure, based on information configuring the OCC for the UE; and send the at least one transmission to the entity.

[0053] According to various examples, the at least one transmission includes: a physical random access channel (PRACH) or Msg1; and / or a physical uplink shared channel (PUSCH) or Msg3.

[0054] According to various examples, identifying the trigger comprises receiving a message to perform one of a handover, a random access channel (RACH)-less handover, or a cell reconfiguration.

[0055] According to various examples, the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on the message.

[0056] According to various examples, the information configuring the OCC is determined from a Configured Grant configuration, a RACH-less configuration in the Configured Grant configuration, in a RACH skip configuration, or in a configuration for RACH-less handover for the UE.

[0057] According to various examples, the message comprises information relating to an OCC index and / or information relating to an OCC length.

[0058] According to various examples, the OCC index is configured based on a configuration for the RACH-less handover, and / or the OCC length is configured based on a default length, a Configured Grant configuration or a cell configuration.

[0059] According to various examples, the message indicates to obtain the information configuring the OCC from a random access response (RAR) or Msg2 receiving by the UE.

[0060] According to various examples, the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on a message received from the entity during the procedure.

[0061] According to various examples, the message received from the entity is a random access response (RAR) or Msg2.

[0062] According to various examples, the message includes an indication of whether or not to apply the OCC for the at least one transmission.

[0063] According to various examples, the UE is configured by broadcast instructions to apply OCC for the PUSCH or Msg3, prior to the procedure; and wherein, based on the indication in the message, the at least one processor is configured to: apply the OCC to the at least one transmission, or override the broadcast instructions to refrain from applying the OCC to the at least one transmission.

[0064] According to various examples, the at least one processor is configured to: transmit an indication of support of OCC during performance of the procedure, prior to applying the OCC.

[0065] According to various examples, the at least one processor is configured to: determine an OCC index and / or OCC length based on the message, wherein the information configuring the OCC includes the determined OCC index and / or OCC length.

[0066] According to various examples, the OCC index is determined based on an Radio Network Temporary Identifier (RNTI) included in the message; and / or wherein the OCC length to be applied for the PUSCH or Msg3 is configured by a broadcast received by the UE.

[0067] According to various examples, the at least one transmission further includes the PRACH or Msg1; and wherein one of: the OCC applied for the PUSCH or Msg3 is the same as the OCC applied for the PRACH or Msg1; or if an OCC length for the PRACH or Msg1 is different to an OCC length for the PUSCH or Msg3, determine an OCC index for the PUSCH or Msg3 based on an OCC index for the PRACH or Msg1.

[0068] According to various examples, the at least one transmission includes a Msg4 acknowledgment(ACK) / negative ACK (NACK), ACK / NACK; and wherein the information configuring the OCC is configured by a Msg4 received by the UE.

[0069] According to various examples, the at least one processor is configured to: transmit, in response to the Msg4, information indicating support for applying the OCC to the Msg4 ACK / NACK.

[0070] According to various examples, the information is included in a medium access control (MAC) layer indication or in an radio resource control (RRC) message, and / or wherein the information includes a OCC length supported by the UE.

[0071] According to various examples, the at least one transmission further includes a PUSCH or Msg3, and the OCC applied for the Msg4 ACK / NACK is the same as the OCC applied for the PUSCH or Msg3; or the at least one transmission further includes a PRACH or Msg1, and the OCC applied for the Msg4 ACK / NACK is the same as the OCC applied for the PRACH or Msg1.

[0072] According to various examples, the information configuring the OCC includes a OCC length and / or OCC index determined based on a random access preamble selected by the UE for the PRACH or Msg1.

[0073] According to various examples, the at least one processor is configured to: upon failure of the procedure with the OCC applied to the at least one transmission, fallback to performing the procedure without applying OCC.

[0074] According to various examples, the at least one processor is configured to: record information regarding the application of OCC in the procedure for a result of the procedure.

[0075] According to various examples, when the procedure is a RACH-less handover, the information configuring the OCC is different depending on the RACH-less handover being Dynamic Grant RACH-less handover (or a first type of RACH-less handover) or Configured Grant RACH-less handover (or a second type of RACH-less handover).

[0076] According to various examples, a first OCC index and / or a first OCC length is configured for the UE for the Dynamic Grant RACH-less handover, and / or a second OCC index and / or a second OCC length is configured for the UE for the Configured Grant RACH-less handover. The first OCC index may be different to the second OCC index and / or the first OCC length may be different to the second OCC length.

[0077] According to another aspect of the present disclosure, there is provided a method of a user equipment (UE), the method comprising: identifying a trigger to perform a procedure, the procedure being an initial access procedure or a reconfiguration procedure to establish the UE with an entity; during performance of the procedure, apply an orthogonal cover code (OCC) for at least one transmission relating to the procedure, based on information configuring the OCC for the UE; and sending the at least one transmission to the entity.

[0078] According to various examples, the at least one transmission includes: a physical random access channel (PRACH) or Msg1; and / or a physical uplink shared channel (PUSCH) or Msg3.

[0079] According to various examples, identifying the trigger comprises receiving a message to perform one of a handover, a random access channel (RACH)-less handover, or a cell reconfiguration.

[0080] According to various examples, the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on the message.

[0081] According to various examples, the information configuring the OCC is determined from a Configured Grant configuration, a RACH-less configuration in the Configured Grant configuration, in a RACH skip configuration, or in a configuration for RACH-less handover for the UE.

[0082] According to various examples, the message comprises information relating to an OCC index and / or information relating to an OCC length.

[0083] According to various examples, the OCC index is configured based on a configuration for the RACH-less handover, and / or the OCC length is configured based on a default length, a Configured Grant configuration or a cell configuration.

[0084] According to various examples, the message indicates to obtain the information configuring the OCC from a random access response (RAR) or Msg2 receiving by the UE.

[0085] According to various examples, the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on a message received from the entity during the procedure.

[0086] According to various examples, the message received from the entity is a random access response (RAR) or Msg2.

[0087] According to various examples, the message includes an indication of whether or not to apply the OCC for the at least one transmission.

[0088] According to various examples, the UE is configured by broadcast instructions to apply OCC for the PUSCH or Msg3, prior to the procedure; and the method comprises: based on the indication in the message, applying the OCC to the at least one transmission, or overriding the broadcast instructions to refrain from applying the OCC to the at least one transmission.

[0089] According to various examples, the method comprises: transmitting an indication of support of OCC during performance of the procedure, prior to applying the OCC.

[0090] According to various examples, the method comprises: determining an OCC index and / or OCC length based on the message, wherein the information configuring the OCC includes the determined OCC index and / or OCC length.

[0091] According to various examples, the OCC index is determined based on an Radio Network Temporary Identifier (RNTI) included in the message; and / or wherein the OCC length to be applied for the PUSCH or Msg3 is configured by a broadcast received by the UE.

[0092] According to various examples, the at least one transmission further includes the PRACH or Msg1; and wherein one of: the OCC applied for the PUSCH or Msg3 is the same as the OCC applied for the PRACH or Msg1; or if an OCC length for the PRACH or Msg1 is different to an OCC length for the PUSCH or Msg3, determine an OCC index for the PUSCH or Msg3 based on an OCC index for the PRACH or Msg1.

[0093] According to various examples, the at least one transmission includes a Msg4 acknowledgment(ACK) / negative ACK (NACK), ACK / NACK; and wherein the information configuring the OCC is configured by a Msg4 received by the UE.

[0094] According to various examples, the method comprises: transmitting, in response to the Msg4, information indicating support for applying the OCC to the Msg4 ACK / NACK.

[0095] According to various examples, the information is included in a medium access control (MAC) layer indication or in an radio resource control (RRC) message, and / or wherein the information includes a OCC length supported by the UE.

[0096] According to various examples, the at least one transmission further includes a PUSCH or Msg3, and the OCC applied for the Msg4 ACK / NACK is the same as the OCC applied for the PUSCH or Msg3; or the at least one transmission further includes a PRACH or Msg1, and the OCC applied for the Msg4 ACK / NACK is the same as the OCC applied for the PRACH or Msg1.

[0097] According to various examples, the information configuring the OCC includes a OCC length and / or OCC index determined based on a random access preamble selected by the UE for the PRACH or Msg1.

[0098] According to various examples, the method comprises: upon failure of the procedure with the OCC applied to the at least one transmission, falling back to performing the procedure without applying OCC.

[0099] According to various examples, the method comprises: recording information regarding the application of OCC in the procedure for a result of the procedure.

[0100] According to various examples, when the procedure is a RACH-less handover, the information configuring the OCC is different depending on the RACH-less handover being Dynamic Grant RACH-less handover (or a first type of RACH-less handover) or Configured Grant RACH-less handover (or a second type of RACH-less handover).

[0101] According to various examples, a first OCC index and / or a first OCC length is configured for the UE for the Dynamic Grant RACH-less handover, and / or a second OCC index and / or a second OCC length is configured for the UE for the Configured Grant RACH-less handover. The first OCC index may be different to the second OCC index and / or the first OCC length may be different to the second OCC length.

[0102] According to another aspect of the present disclosure, there is provided a computer-readable storage medium comprising instructions which, when executed by at least one processor of an electronic device (e.g. a UE), causes the electronic device to perform a method according to any of the above examples or aspect.

[0103] According to another aspect of the present disclosure, there is provided a network or system comprising a user equipment according to any of the above examples or aspect.

[0104] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings.

[0105] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0106] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0107] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0108] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0109] Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0110] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0111] As used in embodiments of the disclosure, a “~unit / module” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit / module” may include one or more processors.

[0112] The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0113] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0114] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0115] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0116] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0117] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0118] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0119] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0120] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0121] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0122] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0123] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0124] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0125] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0126] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0127] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0128] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0129] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0130] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0131] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0132] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0133] In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0134] The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0135] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0136] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0137] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0138] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0139] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0140] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0141] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0142] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0143] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0144] Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0145] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0146] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0147] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0148] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0149] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0150] The content of the following documents is referred to below and / or their content provides background information that the following disclosure should be considered in the context of:

[0151] [1]3GPP RP-202689 - MediaTek Inc., “New Study WID on NB-IoT / eTMC support for NTN”; 3GPP TSG RAN Meeting #90; Electronic Meeting, December 7 - 11, 2020.

[0152] [2]3GPP RP-211557 - Thales, “Solutions for NR to support non-terrestrial networks (NTN)”; 3GPP TSG RAN meeting #91-e; e-meeting, March 22 - 26th, 2021.

[0153] [3]3GPP RP-220953 - Thales, “NR NTN (Non-Terrestrial Networks) enhancements”; 3GPP TSG RAN Meeting #95e; Electronic Meeting, March 17 - 23, 2022.

[0154] [4]3GPP RP-223519 - MediaTek Inc., “Revised WID on IoT NTN enhancements”; 3GPP TSG RAN Meeting #98e; Electronic, 12-16 December 2022.

[0155] [5]3GPP RP-234077 - Deutsche Telekom (moderator, RAN VC), “New WID: Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3”; 3GPP TSG RAN Meeting #102; Edinburgh, Scotland, December 11-15, 2023.

[0156] [6]3GPP RP-243300 - Thales, CATT, “Revised WID: Non-Terrestrial Networks (NTN) for NR Phase 3; 3GPP TSG RAN Meeting #106; Madrid, Spain; 9-12 December 2024.

[0157] [7]3GPP RP-243278 - MediaTek Inc., “Revised WID on Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3; 3GPP TSG RAN Meeting #106; Madrid, Spain; 9-12 December 2024.

[0158] Note: indicated version numbers are provided for illustrative purposes, other (including future) versions of these documents are considered also.

[0159] Wireless or mobile (cellular) communications networks in which a mobile terminal (e.g., user equipment (UE), such as a mobile handset) communicates via a radio link with a network of base stations, or other wireless access points or nodes, have undergone rapid development through a number of generations. The 3rdGeneration Partnership Project (3GPP) design, specify and standardise technologies for mobile wireless communication networks. Fourth Generation (4G) and Fifth Generation (5G) systems (5GS) are now widely deployed, while beyond 5G (B5G) and 6G systems are being considered.

[0160] 3GPP standards for 4G systems include an Evolved Packet Core (EPC) and an Enhanced-UTRAN (E-UTRAN: an Enhanced Universal Terrestrial Radio Access Network). The E-UTRAN uses Long Term Evolution (LTE) radio technology. LTE is commonly used to refer to the whole system including both the EPC and the E-UTRAN, and LTE is used in this sense in the remainder of this document. LTE should also be taken to include LTE enhancements such as LTE Advanced and LTE Pro, which offer enhanced data rates compared to LTE.

[0161] In 5G systems a new air interface has been developed, which may be referred to as 5G New Radio (5G NR) or simply NR. NR is designed to support the wide variety of services and use case scenarios envisaged for 5G networks, though builds upon established LTE technologies B5G systems, such as 6G, are currently being considered and developed, and are expected to at least partly build on 5G systems.

[0162] New frameworks and architectures are being developed as part of 5G network (and beyond, such as 6G networks) in order to increase the range of functionality and use cases available through 5G networks.

[0163] IoT (Internet of Things) NTN (Non-Terrestrial Network) was a 3GPP study and work item in 3GPP release 17 to provide Non-Terrestrial Network access for E-UTRAN IoT devices (NB-IoT (Narrowband-IoT) and LTE-M / eMTC (Long-Term Evolution Machine Type Communication / enhanced machine-type communication)) (RP-202689 [1]].

[0164] NR NTN was a work item in Rel-17 to specify adaptation to allow NR to function over NTN (RP-211557 [2]). Non-Terrestrial Network access may be through Lower Earth Orbit (LEO), Medium Earth Orbit (MEO) and Geostationary Orbit (GEO), as well as through High-Altitude Platform Systems (HAPS).

[0165] Figure 1a illustrates a transparent architecture for a NTN (e.g. NTN Release 17 transparent architecture), and Figure 1b illustrates a regenerative architecture for a NTN (e.g. NTN Release 19 regenerative architecture).

[0166] In Figure 1a, an NTN is shown to comprise NTN cell 101 and a NTN entity 113 associated with (e.g. controlling or configuring) NTN cell 101. The NTN entity 113 is connected to a gateway 103 via feeder link 115. The gateway 103 is connected to eNB / gNB 105, which communicates with core network 107. It will be appreciated that gateway 103 and eNB / gNB 105 may be co-located or implemented together. A UE 109 is located within NTN cell 101. The UE 109 is connected to NTN entity 113 via access link 111. Accordingly, the UE 109 is connected to core network 107 via the NTN entity 113.

[0167] In Figure 1b, an NTN is shown to comprise NTN cell 121 and a NTN entity 131 associated with (e.g. controlling or configuring) NTN cell 121. The NTN entity 131 is connected to a gateway 123 via feeder link 133. A eNB or gNB is implemented in NTN entity 131, e.g. NTN entity 131 provides eNB / gNB functionality. The gateway 123 is connected to core network 125. A UE 127 is located within NTN cell 121. The UE 127 is connected to NTN entity 131 via access link 129. Accordingly, the UE 127 is connected to core network 125 via the NTN entity 131.

[0168] Following the Work items in Release 17 there were work items to enhance NR NTN (RP-220953 [3]) and IoT NTN (RP-223519 [4]) in Release 18.

[0169] The work item description for IoT NTN Rel-19 is the following (RP-234077 [5]):

[0170] ●Support of Store&Forward (S&F) satellite operation with full eNB as regenerative payload, therefore:

[0171] ○Define the necessary enhancements into E-UTRAN (network & UE) to support S&F operation for delay-tolerant services [RAN3, RAN2]

[0172] ○Specify necessary enhancements for full eNB as regenerative payload e.g. related to S1 protocol, especially to address the feeder link switch over as needed [RAN3]

[0173] Note: Strive to minimise UE impact.

[0174] Note: Coordination with SA2 (Rel-19 SA2 led Sat-Arch ph3 SI) is needed on the detail requirements (e.g. traffic type, or QoS parameters for S&F), network architecture (e.g. whether consider (partial) core network on satellite) etc.; further coordination with CT1 might be required

[0175] ●Support of Capacity enhancements for uplink

[0176] ○Study then specify, if beneficial, enhancements to enable multiplexing of multiple UEs (e.g. up to the min of 4 and the maximum allowed by the existing UL and DL signalling) in a single 3.75 kHz or 15 kHz subcarrier via orthogonal cover codes (OCC) for NPUSCH format 1 and NPRACH [RAN1, RAN2, RAN4]

[0177] ·Multi-tone support for 15 kHz SCS should also be considered

[0178] ·Specify necessary signalling, if needed

[0179] ·Update RF requirements accordingly, if needed

[0180] Note: Impact of impairment shall be taken into account

[0181] ○Study and specify, if beneficial the following enhancements to reduce the necessary uplink and downlink signaling to complete an Early Data Transmission (EDT) transaction [RAN2]:

[0182] ·Msg3 transmission without msg1 / Random Access Response (RAR)

[0183] ·Efficient delivery (reduced overhead) of msg4 / RRCEarlyDataComplete

[0184] ·Study and specify RRM requirement, if identified [RAN4]

[0185] ●Support broadcast of PWS messages for NB-IoT re-using the LTE mechanisms [RAN2]

[0186] Note: The solutions will be developed for NTN but can be applicable to TN (if possible). Specific NB-IoT TN optimizations will not be considered as part of this WI.

[0187] Note: Support for indication of intended service area for ETWS will be considered based on NR NTN discussions / outcome.

[0188] Narrowband Internet of Things and LTE-M

[0189] Narrowband Internet of Things (NB-IoT) is a 3GPP-defined network based on 4G E-UTRAN that supports ultra-low complexity devices with very narrow bandwidth that was introduced in 3GPP Release 13. It supports the massive Machine Type Communication (mMTC) 5G use case for IMT-2020. The use case of NB-IoT is to serve massive IoT application, where requirements for instance are to support enhanced coverage, power-efficient operation and a massive number of devices. Some of the features introduced are:

[0190] - Support for enhanced coverage through low bandwidth and extreme amounts of repetitions.

[0191] - Power efficient operation by allowing the UE to sleep for very long times, relaxed requirements and more efficient signal to establish with a cell.

[0192] LTE-M (or eMTC) is another technology that serves the mMTC 5G use case. Compared to NB-IoT, an LTE-M device is more like a simplified 4G E-UTRAN device with certain simplifications allowing for easier and cheaper implementation. It addressed a slight wider use case compared to NB-IoT, with higher data rates and is not quite as power efficient as NB-IoT. This type of device may also be referred to as a Cat M1 / 2 device or as Bandwidth Limited (BL) UE and UE in enhanced coverage.

[0193] Both LTE-M and NB-IoT are specified with what is known as User plane and Control plane enhancements for reduced signaling. In user plane solution, the UE supports AS security and Data radio bearers.

[0194] In control plane, the UE does not support AS security and instead relies on NAS for security, which means that all data is routed through MME. Control Plane IoT has several impacts on the radio interface. One of these is that the UE may only be configured once when the UE establishes its connection and may not be reconfigured. The configuration is done via RRCConnectionSetup or RRCConnectionResume message, sometimes known as Msg4. Furthermore, DRBs may not be setup. Control plane is mandatory for NB-IoT and optional for LTE-M.

[0195] Initial / random access procedure in IoT NTN

[0196] Figure 2 is a call flow diagram showing an initial / random access procedure according to various examples.

[0197] In operation S210, the UE 210 is in RRC idle mode or RRC inactive mode (or, more generally, not in RRC connected mode).

[0198] In operation S220, the UE 210 determines the timing advance (TA) pre-compensation using the UE position and the satellite position. The UE position is via GNSS, but other methods that do not rely on the network may also potentially be used, such as using inertial navigation system or similar. The satellite position is acquired via SIB19 or SIB31 and the UE also pre-compensates using TA-Common, which is the common timing advance from the satellite to the ground gateway where the base station resides.

[0199] In operation S230, the UE 210 uses the pre-compensation and sends Msg1 which is the RACH (random access channel) preamble. The RACH preamble will represent a number between 1 and 64. The number selected by the UE is random, but there exists several rules to determine the range of preambles, depending on configurations and conditions - sometimes referred to as preamble division.

[0200] In operation S240, if the network (e.g. eNB or gNB 220, CN etc.) is able to detect and determine the RACH preamble, the eNB 220 responds with Msg2 or RAR (random access response). The RAR may be scheduled by PDCCH (physical downlink control channel), which is scrambled based on the resource that the Msg1 was sent in. The RAR includes an uplink grant for the message 3 and the preamble ID that the network is responding to. The uplink grant contains a time and frequency allocation for the Msg3 as well as an temporary RNTI that the UE shall use for Msg3 and potentially Msg4. In some cases in case of successful random access procedures, the temporary RNTI may become the connected mode RNTI (C-RNTI).

[0201] In operations S250 and S260 (note, these may be combined into a single operation of scheduling and sending Msg3), the UE 210 sends Msg3, which is sent using PUSCH (physical uplink shared channel). This message contains the first RRC message, which may be a RRC request. The RRC message depends on the specific reason why the random access procedure was triggered. For example: for initial access it will be RRCSetupRequest; for resuming it is RRCConnectionResumeRequest; for re-establishing RRC it is RRCConnectionReestablishmentRequest; for CP-EDT it is RRCEarlyDataRequest etc. Note that in some cases, the RRC request information will be sent in the first message.

[0202] In operation S270, since it is possible that two UEs select the same RAPID (random access preamble ID), there is a chance of collision. So in Msg4, sent over PDSCH in operation S270, this contention may be resolved using the Contention Resolution MAC CE. Msg4 also contains an RRC message that is a response to Msg3. This can for instance be RRCConnectionSetup, RRCConnectionResume, RRCConnectionReestablishment, RRCReject, RRCEarlyDataComplete etc. Note that in some cases, this RRC message will be sent in the second message. The Msg4 will be acknowledged in order for the network to be notified that the Msg4 was successful. Some of these message may include the UE configuration to use in RRC connected. RRC Connection Setup, for example, configures or establishes SRB1, which can be used for continued configuration.

[0203] In a further operation (not shown in Figure 2), the UE 210 sends Msg5. Msg5 is a further message that is scheduled uplink message which would consist of the reply to the downlink RRC message in Msg4. Msg5 is sometimes not considered a part of the random access procedure, but a part of any access procedures. The RRC message carried in Msg5 may be RRCConnectionSetupComplete, RRCConnectionResumeComplete, RRCConnectionReestablishmentComplete and so on. The Msg5 can for instance contain a NAS message. For RRC setup, this is can be used for initial establishment or to request service, which is forwarded to the MME or AMF. The Msg5 may also contain various indications, such as existence of UE assistance data etc.

[0204] In some cases, the steps S220, S230 and S240 are not shown for RRC procedures as they are part of lower layer procedures. For 2-step random access, steps S230 and S260 may be combined to a MsgA and steps S240 and S270 are combined to MsgB.

[0205] 3.2.3 E-UTRAN and eMTC connected mode mobility

[0206] E-UTRAN connected mode mobility functions similar to other cellular standards and connected mode mobility is also supported for E-UTRAN eMTC. A standard connected mode handover is performed only when triggered by the eNB.

[0207] Figure 3 is a call flow diagram showing a handover procedure according to various examples.

[0208] In operation S310, UE 310 performs neighbour cell measurements, which are configured by the network.

[0209] In operation S320, a measurement report (of a neighbour cell) is triggered and sent to source eNB 320, by the UE 310.

[0210] In operation S340, source eNB 320 ends a handover request (i.e. a message relating to handover) to target eNB 330 after the source eNB 320 having decided, e.g. based on measurement report and / or any other information, whether to initiate an handover in operation S330.

[0211] In operation S350, source eNB 320 receives a handover request acknowledge (i.e. message acknowledging the handover request) from target eNB 330. This may follow the target eNB 330 performing admission control. Admission control is where the target cell determines whether the UE may perform handover to the cell, taking into account eNB resource usage etc.

[0212] In operation S360, source eNB 320 triggers a handover command which is sent to the UE 310. This handover command may include the RRC message RRCConnectionReconfiguration, which may contain the mobilityControlInfo field.

[0213] In operation 370, the UE 310 prepares for handover and performs a handover via a random access procedure.

[0214] If a neighbour cell measurement is configured to be performed in a NTN cell, then as being discussed in Rel-18 IoT NTN, the UE needs to have the ephemeris of the neighbouring NTN cell in order to allow for time-frequency synchronization to measure neighbouring cell. The ephemeris may be provided in a broadcasted fashion using SIB.

[0215] 3.2.4 RACH-less

[0216] RACH-less is a handover method introduced in E-UTRAN Release 14 and NR Release 18. It enables a UE to skip performing random access during a handover. This is to improve (e.g. reduce) the delay of handovers in some certain cases.

[0217] RACH-less can in general be said to be performed in certain cases related to the Timing Advance (TA):

[0218] ● When TA to the target cell is equal to zero.

[0219] ● When TA to the target cell is equal to the TA of the source cell.

[0220] ○ In LTE the source cell may be considered to be based one of the serving cells, which can be a PCell or SCell. The Timing Advance is based on a Timing Advance Group (TAG), which can be either the Primary TAG or Secondary TAG.

[0221] ○ In NR the timing of the source cell is always based on the PCell.

[0222] RACH-less can be said to include two different methods:

[0223] ● In a first method, consecutive Uplink Grants are configured to be used by a UE to send the first message after the handover, which is the RRCReconfigurationComplete and optionally any data. For this case, the UE is configurated with an uplink grant (e.g. ul-Grant), the scheduling interval (e.g. ul-SchedInterval) as well as how many occasions that are configured (e.g. numberOfConfUL-Processes). This may be termed Configured Grant (CG) RACH-less.

[0224] ● In a second method, a UE is scheduled to synchronize with a cell without sending any messages to the target cell. Instead, the UE starts monitoring PDCCH for assignments from the target cell. The assignments may be for downlink PDSCH transmissions or UL grants for the UE to send PUSCH. This may be termed Dynamic Grant (DG) RACH-less.

[0225] Figures 4a and 4b illustrates examples of RACH-less handover procedures. In Figure 4a, an example is illustrated in which a UE is configured with uplink grants. In Figure 4b, an example is illustrated in which a UE is configured to monitor PDCCH of the target cell.

[0226] In Figure 4a, operation S410a shows source eNB 420 making a handover decision, e.g. determining to handover.

[0227] In operation S420a, a handover request is sent by source eNB 420 to target eNB 430, and a handover request acknowledgement is sent by target eNB 430 to source eNB 420.

[0228] In operation S430a, source eNB 420 sends a message to perform handover to UE 410 (e.g. sends RRCConnectionReconfiguration, with RACH less opportunities configured). This message may indicate that RACH-less handover may be performed by UE 410.

[0229] In operation S440a, the UE 410 prepares handover.

[0230] In operation S450a, UE 410 sends a message relating to handover completion (e.g. sends RRCConnectionReconfigurationComplete, using RACH less UL grant) to target eNB 430. Target eNB 430 is or has been monitoring for UL RACH-less transmission(s) from the UE, e.g. following sending the handover request acknowledgement.

[0231] Turning to Figure 4b, operation S410b, shows source eNB 420 making a handover decision, e.g. determining to handover.

[0232] In operation S420b, a handover request is sent by source eNB 420 to target eNB 430, and a handover request acknowledgement is sent by target eNB 430 to source eNB 420.

[0233] In operation S430b, source eNB 420 sends a message to perform handover to UE 410 (e.g. sends RRCConnectionReconfiguration, with PDCCH monitoring). This message may indicate that PDCCH monitoring may be performed by UE 410.

[0234] In operation S440b, the UE 410 prepares handover. Following this, UE 410 monitors PDCCH of target cell (e.g. target eNB 430).

[0235] In operation S450b, UE 410 receives PDCCH(s) from taget eNB 430.

[0236] In operation S460b, UE 410 sends a message relating to handover completion (e.g. sends RRCConnectionReconfigurationComplete.

[0237] In various examples, the following fields are configured with RACH-less for LTE RACH-less:

[0238] ● targetTA,

[0239] ● numberOfConfUL-Processes,

[0240] ● ul-SchedInterval,

[0241] ● ul-StartSubframe,

[0242] ● ul-Grant.

[0243] In various examples, the following fields are configured for NR RACH-less:

[0244] ● targetNTA,

[0245] ● beamIndication,

[0246] ● CG-RRC-Configuration.

[0247] For 5G NR Configured Grant RACH-less, the UE may be configured to select an SSB during the handover. This selection is based on a configured threshold. The SSB selected may determine which of the configured PUSCH occasion that the UE shall select. This means that the UE may select different PUSCH occasions depending on the selected SSB.

[0248] 3.2.5 Orthogonal cover codes (OCC)

[0249] OCC is a way to introduce a orthogonality between one or more devices by utilizing the code domain. This spreads a transmission across codes and, as long as two devices utilize different codes, the users can be distinguished. Each cover codeword is a sequence or matrix that is orthogonal to all of the other codewords. Orthogonal Cover Codes may be employed on reference signals and / or training fields. In both 4G and 5G, cover codes may be employed on PUCCH. One reason for this is that the resources for these channels are typically quite low, compared with any of the channels used for data transmissions.

[0250] 3G technologies often employed Code Division Multiple Access (CDMA) where different codes were employed for multiple access.

[0251] Orthogonal coverage codes for NR NTN

[0252] For NR NTN, what is configured is the OCC length and the OCC sequence. For dynamic grant PUSCH, the OCC configuration may be configured based on signalling in the DCI.

[0253] Orthogonal coverage codes for IoT NTN

[0254] In IoT NTN, orthogonal cover codes are only supported for NB-IoT devices. In this case, the OCC length is fixed and the UE is configured with an OCC sequence.

[0255] Orthogonal cover codes are being discussed as part of 3GPP Rel-19 for NR NTN (RP-243300, [6]):

[0256] 1.Uplink Capacity / Cell Throughput Enhancement for FR1-NTN [RAN1, RAN2, RAN4]

[0257] ● Specify Orthogonal Cover Codes (OCC) for DFT-s-OFDM PUSCH at least for multiplexing 2 or 4 UEs when PUSCH repetitions are used

[0258] ○ Specify necessary signalling

[0259] ○ Update RF requirements accordingly, if needed

[0260] ● Notes for this objective:

[0261] ○ The enhancement is not targeting improvements / impacts of MU-MIMO capability

[0262] ○ The enhancement is not targeted to PUSCH DMRS

[0263] ○ No enhancement for initial access

[0264] ○ Enhancements to PRACH are not in scope.

[0265] ○ This feature may be applicable for UEs operating in terrestrial networks based on a common design

[0266] They are also being discussed for 3GPP Rel-19 IoT NTN (RP-243278, [7]):

[0267] ○ Study then specify, if beneficial, enhancements to enable multiplexing of multiple UEs (e.g. up to the min of 4 and the maximum allowed by the existing UL and DL signalling) in a single 3.75 kHz or 15 kHz subcarrier via orthogonal cover codes (OCC) for NPUSCH format 1 and NPRACH [RAN1, RAN2, RAN4]

[0268] · Multi-tone support for 15 kHz SCS should also be considered

[0269] · Specify necessary signalling, if needed

[0270] · Update RF requirements accordingly, if needed

[0271] However, there are several aspects and special scenarios that have not been discussed. For instance, whether OCC shall be supported for handovers, for Msg3 and for Msg4 ACK / NACK.

[0272] Certain examples of the present disclosure relate to methods, apparatus and / or systems for using orthogonal cover codes (OCC) in various scenarios and circumstances. In various examples, a UE applies OCC in a handover procedure. For example, the UE may apply OCC to a transmission to a target cell during handover. In various examples, a UE applies OCC during an initial access procedure. For example, the UE may apply OCC for a PRACH or PUSCH transmission, and / or for Msg4 ACK / NACK. Various examples describe configuring OCC information for a UE, such as OCC length and / or OCC index. Other scenarios are provided for in further examples..

[0273] The following examples are applicable to, and use terminology associated with, 3GPP 5G. However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 5G, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards. The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 5G NR or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network. In particular, the following disclosure should be considered at least in relation to 6G also, which is expected to use at least part of the 5G architecture, or equivalent, and to which the present disclosure also relates.

[0274] A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0275] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0276] ● The techniques disclosed herein are not limited to 3GPP LTE, LTE-A, 5G, B5G or 6G.

[0277] ● One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations.

[0278] ● One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.

[0279] ● One or more further elements, entities and / or messages may be added to the examples disclosed herein.

[0280] ● One or more non-essential elements, entities and / or messages may be omitted in certain examples.

[0281] ● The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example.

[0282] ● The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example.

[0283] ● Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.

[0284] ● Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.

[0285] ● The order in which operations are performed may be modified, if possible, in alternative examples.

[0286] ● The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0287] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0288] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0289] A network according to one or more of the examples disclosed herein may include one or more of a Network Data Analytics Function (NWDAF) entity, an Access and Mobility Management Function (AMF) entity, a Session Management Function (SMF) entity, a Network Slice Selection Function (NSSF) entity, a Network Repository Function (NRF) entity, Application Function (AF) entity, and an Operation and Maintenance (OAM) entity. The network may include one or more Service Consumers (including one or more of the entities mentioned above and / or one or more other entities) that receive analytics from NWDAF. The skilled person will appreciate that a network may omit one or more of the entities mentioned above and / or may comprise one or more additional entities.

[0290] All proposals, embodiments, and examples disclosed herein may also apply for, but are not limited to, NR NTN, LTE-M / eMTC NTN, E-UTRA NTN or even 6G NTN.

[0291] As described above, there are several aspects and special scenarios that have not been discussed in regards to orthogonal cover codes. Examples include whether OCC shall be supported for handovers, for Msg3 and / or for Msg4 ACK / NACK. Various embodiments of the present disclosure aim to address this issue by providing methods and apparatus for supporting or using OCC in relation to various scenarios, including handovers, initial access, reconfiguration, random access procedure etc. Accordingly, various examples provide methods for configuring a UE to perform one or more transmission using OCC in certain circumstances or scenarios.

[0292] Herein, a feature of configuring the OCC may be interpreted to mean configuring the OCC length and / or OCC index (i.e. a length of an orthogonal cover code and / or an index of an orthogonal cover code). For example, a UE may only be configured with the OCC length (e.g. via RRC configuration), while the OCC index is configured for each transmission or each set of transmissions with a DCI (downlink control information). In an example, if OCC length only has a single length, then the UE may only be configured to apply a default OCC length, which means that the configuration is only a single bit to indicate that OCC is configured. In another example, UE may also only be configured with an OCC index if the OCC length is fixed. The term ‘OCC index’ as used herein may refer to the OCC sequence, i.e. the specific OCC code word in an OCC.

[0293] According to various embodiments of the present disclosure, a UE is configured (e.g. by the network or CN) to perform a handover using OCC. For example, this includes applying or using OCC for at least one transmission, by the UE, in a handover procedure. Specific examples of this will be provided below.

[0294] In various examples, the UE is configured to perform handover using OCC in a handover command or message configuring the UE to perform reconfiguration with sync (e.g. any of the messages of operations S360, S430a, S430b).

[0295] When the UE is configured to perform or apply OCC during a handover procedure, in various examples this includes PRACH (physical random access channel) transmission(s), PUSCH (physical uplink shared channel) transmission(s) or PRACH and PUSCH transmission(s) being performed with OCC. In other words, in various examples, the Msg1, the Msg2 or both the Msg1 and the Msg3 may apply OCC (or may have OCC applied) when performing a handover.

[0296] Figure 5 is a call flow diagram showing a method for applying OCC during handover according to various examples of the present disclosure.

[0297] Operation S510 shows source cell 520 (e.g. source eNB) sending a handover request to target cell 530 (e.g. target eNB).

[0298] Operation S520 shows target cell 530 determining or deciding whether to allow for handover. A separate or combined decision is also made in S520 as to configuring the UE with OCC. For example, this may include deciding how to configure the UE with OCC (e.g. how to apply OCC or parameters for applying OCC), or configuring a OCC length and / or OCC index for the UE 510 to use (and, optionally, how to inform / provide this to the UE), or determining parameters that the UE 510 will use. For example, the target cell 530 determines one or more OCC parameter for the UE 510 or information relating to applying OCC for the UE 510, such as OCC length and / or OCC index. In various examples, source cell 520 may also or instead decide (or determine) this information. In various examples, the result of the decision by target cell 530 (e.g. the determined information) is sent to the source cell 520, e.g. for forwarding to the UE 510 (e.g. in the handover command).

[0299] In operation S530, target cell 530 acknowledges the handover request to source cell 520, e.g. sends a handover request acknowledge message. This may also include a configuration for the UE to use at the target cell as well as handover configuration. For example, the information, e.g. OCC parameter(s), determined / decided in operation S520 may be included in a handover request acknowledgement from the target cell 530 to the source cell 520.

[0300] In operation S540, source cell 520 sends a handover command to UE 510. The handover command, configured by the target cell 530 (e.g. configured based on information provided or determined by the target cell 530), may indicate OCC is configured and, optionally, may provide OCC parameters or information for applying OCC, such as OCC index and / or OCC length. This OCC information / parameter(s) may have been determined by source cell 520 or by target cell 530, as mentioned above.

[0301] In operation S550, UE 510 performs handover with OCC, e.g. implementing a parameter(s) provided by the source cell 520.

[0302] Further features relating to a procedure for performing handover with OCC will now be described. It will be appreciated that these features may combine with those described above in relation to Figure 5 to provide further examples of the present disclosure.

[0303] In various examples, when applying OCC for Msg3, it may be configured in the handover command or it may be configured based on the received Msg2. In a case where the OCC is configured via Msg2, the network (or other entity, e.g. source cell or target cell) may still indicate to the UE how to interpret the Msg2, which can be indicated in the handover command. This may allow the OCC index to be determined based on a received Temporary Cell (TC) Radio Network Temporary Identifier (TC-RNTI). In a case where the OCC is configured in the handover command, the UE may be configured with the OCC index in the handover command, and the OCC length, if not default, may be configured in the common cell configuration. In other examples, the OCC index is included or indicated in the handover command and the OCC length is set according to a default value.

[0304] According to various embodiments, the UE applies OCC for RACH-less handovers. In various examples, the UE applies OCC for the PUSCH transmission when the UE is configured with RACH-less. In other words, the UE applies OCC for the PUSCH transmission in the target cell.

[0305] The OCC configuration may be configured in the handover command as part of the RACH-less configuration. This may, for example, include the UE being configured with OCC in the Configured Grant configuration, for example in the RACH-less configuration (cg-RRC-Configuration) in the Configured Grant configuration. In other examples, this may include the UE being configured with OCC in the RACH skip configuration. Examples of this can be seen in Specification Example #1 and Specification Example #2 found below.

[0306] In various examples, the OCC may also be configured as part of the RACH-less handover configuration (rach-lessHO) in ReconfigurationWithSync information element, which is used when a handover command is sent. The OCC index may be configured as part of (e.g. in, or indicated in / by) the rach-lessHO, while the OCC length may be configured as part of (e.g. in, or indicated in / by) cell configuration or a configured grant configuration. Applying OCC for RACH-less handovers may be particularly useful in a non-terrestrial network (NTN) as there may be a lot of handovers occurring. This may apply for both Configured Grant RACH-less and Dynamic Grant RACH-less. In various examples, if the Dynamic Grant RACH-less is used, then the OCC may be configured based on the received PDCCH.

[0307] Configuring the OCC for RACH-less handovers may be different for Dynamic Grant RACH-less and Configured Grant RACH-less.

[0308] In various examples, for Dynamic Grant RACH-less, the OCC index may be configured via the PDCCH (from target cell) that schedules the RACH-less PUSCH transmission. For example, as a result the OCC length is configured via RRC in the handover message (from source cell), or this may additionally or alternatively be configured by the PDCCH that schedules the RACH-less PUSCH transmission. The OCC index may also (i.e. additionally or alternatively) be configured via the handover command. For example, as a result the network may configure the UE to interpret the PDCCH in a manner where the OCC index can be signalled for the RACH-less PUSCH transmission.

[0309] In various examples, for Configured Grant RACH-less, the OCC index and the OCC length may be configured via the handover command. Alternatively, the OCC index may be determined based on either the PUSCH occasion that is selected, or the SSB that is selected during SSB selection. For example, as a result the same PUSCH occasion may be selected for the same SSB, but with different OCC index. This would mean that the OCC length would be configured by the handover command (e.g. the handover command includes or indicates information for configuring the OCC length). Alternatively, the network may, in addition to configuring the OCC length, either configure the specific OCC index or whether the UE shall select the OCC index based on the selected SSB. For example, the network may configure and indicate the specific OCC index to the UE or may configure (e.g. decide) whether the UE shall select the OCC index based on the selected SSB and indicate this (i.e. a result) to the UE.

[0310] According to various examples, if the UE fails performing a handover applying OCCs, the UE may be configured to fallback and not perform handover applying OCCs. The UE may thus fallback to not apply OCC during the handover. The UE may thus be configured with a maximum number of attempts when applying OCC. That is, in various examples, once a UE has reached or exceeded a predetermined number of attempts to perform handover with OCC applied (e.g. having failed a number of times equal to this predetermined number), the UE is configured to perform handover without applying OCC.

[0311] According to various examples, if the UE fails or completely fails (e.g. failing equal to or more than a maximum number of times) the handover procedure when applying OCC, the UE may be configured to log that OCC was applied during the failure. Similarly, for a successful handover procedure the UE may also be configured to log that OCC was used. The UE may also log the specific OCC index that was used during a success or failure. In various examples, the UE reports the logged information, e.g. to the network or target cell.

[0312] In various embodiments, polarization (either Left Hand Circular Polarization or Right Hand Circular Polarization) and OCC may be employed together during a handover. For example, these may be applied to Msg3.

[0313] In various embodiments of the present disclosure, OCC is applied for Msg3, e.g. during an initial access procedure.

[0314] Configuring OCC as (or to be) applied for Msg3 may be based on whether the UE supports using / applying OCC for MSg3 or not. That is, from the perspective of the network, before configuring or instructing a UE to apply OCC for Msg3, the network may check or determine whether the UE supports this. In various examples, a UE utilizes one or more PRACH opportunities or specific PRACH preambles to indicate support of OCC for Msg3, or general support for OCC (i.e. non-specific for Msg3). Accordingly, the network or cell may receive an indication of support from the UE.

[0315] In various examples, an OCC index for the UE to apply for the Msg3 transmission is indicated to the UE or obtained by the UE. For example, the UE may determine the OCC index based on Msg2, which may be the Random Access Response (RAR). In various examples, this is based on one or more new fields included or indicated in Msg2, where for instance the Msg2 may indicate the OCC length and / or the OCC index. Fields (E.g. existing fields) in Msg2 may also be repurposed or re-interpreted to provide the OCC index and / or OCC length or an indication thereof (i.e. allowing for the derivation of OCC index and / or OCC length). In an example, an RNTI indicated in Msg2, which is used for the RNTI for Msg3, may be used to determine which OCC index to use. This may be termed the Temporary C-RNTI (TC-RNTI). This may be done, for example, by applying a modulus operation based on the number of OCC indices or the length of the OCC, for instance OCC_index = MOD(TC-RNTI, OCC-length). Accordingly, the network can select the OCC using the RNTI, and may communicate the selected OCC to the UE. An example of this is shown in Figure 6a.

[0316] Figure 6a illustrates a procedure, e.g. initial access procedure, in which OCC is applied to Msg3.

[0317] Operation S610a shows UE 610 transmitting Msg1 (RA preamble) to network entity 620 (e.g. eNB, gNB). This may be similar to operation S230 of Figure 2.

[0318] Operation S620a shows network entity 620 sensing Msg2 (RAR) to UE 610. As mentioned above, Msg2 may include or indicate RNTI (or TC-RNTI, following the notation above). Operation S620a may otherwise be similar to operation S240 of Figure 2.

[0319] In operation S630a, UE 610 schedules Msg3, and determines (or computes, identifies, obtains etc) OCC based on Msg2. For example, the UE may identify a configuration or parameter for OCC based on Msg2, such as based on TC-RNTI as described above.

[0320] In operation S640a, UE 610 sends Msg3 (i.e. PUSCH) with OCC to network entity 620. That is, UE 610 applies OCC as determined in operation S630a to Msg3 and sends Msg3 to the network entity 620.

[0321] In operation S650a (which may be omitted, in various examples), network entity 620 responds by sending Msg4 (i.e. PDSCH) to the UE 610, e.g. for contention resolution.

[0322] Accordingly, in various embodiments, the UE determines an OCC configuration based on Msg2, e.g. based on information included in Msg2 such as information relating to OCC or other / existing information such as RNTI.

[0323] In various embodiments of the present invention, the OCC to be applied for Msg3 is decided or determined (or obtained, identified etc.) based on the preamble that the UE selects for the PRACH (e.g. based on Msg1). This may be done by applying a modulus operation based on the number of OCC indices or the length of the OCC, for instance OCC_index = MOD(preambleID, OCC-length). This makes it clear for the UE and the network which OCC index is used. An example of this is shown in Figure 6b.

[0324] Figure 6b illustrates a procedure, e.g. initial access procedure, in which OCC is applied to Msg3.

[0325] Operation S610b shows UE 610 transmitting Msg1 (RA preamble) to network entity 620 (e.g. eNB, gNB). This may be similar to operation S230 of Figure 2.

[0326] Operation S620b shows network entity 620 sensing Msg2 (RAR) to UE 610. As mentioned above, Msg2 may include or indicate RNTI (or TC-RNTI, following the notation above). Operation S620a may otherwise be similar to operation S240 of Figure 2.

[0327] In operation S630b, UE 610 schedules Msg3.

[0328] In operation S640b, UE 610 sends Msg3 (i.e. PUSCH) with OCC to network entity 620. The OCC is based on based on the preamble, e.g. based on preamble ID. For example, the UE may identify a configuration or parameter for OCC based on the preamble, such as described above.

[0329] In operation S650b (which may be omitted, in various examples), network entity 620 responds by sending Msg4 (i.e. PDSCH) to the UE 610, e.g. for contention resolution.

[0330] In various embodiments of the present disclosure, the network may indicate whether OCC is applied or not in Msg2. For example, the network may have configured in a broadcasted manner (e.g. may have previously broadcast information or instructions for configuring) one or more UEs to apply or be prepared to apply OCC for Msg3; but this may be overriden in / by Msg2 which instructs the UE (e.g. a specific UE among the one or more UEs) to not apply OCC for Msg3. This can be used in case there are no collisions or generally no need to apply OCC, which can save resources and UE power. In other words, broadcasting instructions to UEs to use OCC for Msg3 may be useful when collisions are possible, but if there is no or little risk of collision then these instructions may be overridden by using Msg2 to indicate to a UE, e.g. when performing initial access, not to use OCC for Msg3.

[0331] In various embodiments of the present disclosure, OCC length for Msg3 may be broadcasted and applied by all of one or more UEs for OCC. For example, all UEs of a plurality of UEs may be provided with a OCC length to use when applying OCC to Msg3. This may mean that only the OCC index needs to be decided (e.g. dynamically decided( for Msg3. In various examples, if the OCC length is fixed, then only the OCC index need to be configured. This may mean that the network only configures that OCC is applied for Msg3.

[0332] In various embodiments, if a / the UE performs PRACH using OCC (e.g. applies OCC for Msg1), then the UE may apply the same OCC as that for PRACH (e.g. to Msg3). If the OCC length of PRACH and Msg3 is different, then OCC for Msg3 may be determined based on OCC used for PRACH (e.g. OCC length and / or OCC index to be used for Msg3 is determined based on OCC length and / or OCC index used for PRACH). For example, if the OCC length for PRACH is smaller than the OCC length for Msg3, then the UE may use the selected OCC index for PRACH to select the OCC index to reduce the selection space and thus the number of needed bits to signal the OCC index for Msg3.

[0333] In various embodiments of the present disclosure, OCC is used (or applied) for Msg4 ACK / NACK. An example of Msg4 ACK / NACK can be seen in relation to operation S270 of Figure 2 above.

[0334] Msg4 ACK / NACK is sent over PUCCH for 5G NR and LTE, while sent over NPUSCH for NB-IoT. Other, e.g. new, methods of sending Msg4 ACK / NACK are also envisaged and included herein.

[0335] The OCC to apply for Msg4 ACK / NACK may be configured by the Msg4, for example based on content in the PDCCH that schedules the Msg4 transmission. It may also be based on content in the Msg4.

[0336] Further, the OCC for Msg4 ACK / NCAK may be based on an RNTI configured to the UE, for instance the TC-RNTI (e.g. as found or indicated in Msg2), C-RNTI or any other configured RNTI. The TC-RNTI would be signalled in Msg2 and applied for Msg3, while a C-RNTI may applied if the UE performs random access procedure while in RRC connected. The C-RNTI may also be used if the TC-RNTI becomes the C-RNTI.

[0337] In various examples, to configure OCC for Msg4 ACK / NACK, the UE may indicate support for it in a Msg3 (e.g. indicate support for applying OCC for Msg4 ACK / NACK in Msg3, or in an earlier transmission). This may be indicated in a MAC layer indication, or in an RRC message. If indicated in a MAC layer indication, for example, this may be through a new MAC CE, which is included in a Msg3. This can be an empty MAC CE, since the UE may only need to indicate whether it is supported or not. If indicated in an RRC message, for example, this may be sent in an RRC Setup, RRC Resume, RRC Re-establishment message. The indication may include an indication of the OCC length supported and / or whether the UE supports OCC (in various examples, indicating a OCC length is considered an indication of support for OCC by the UE).

[0338] The OCC applied by the Msg4 ACK / NACK may be configured to be the same as that of the Msg3, if OCC is applied for Msg3. If PRACH is performed using OCC, then the OCC applied for the Msg4 ACK / NACK may be the same as that of PRACH. In various examples, OCC applied for Msg4 ACK / NACK may be the same as OCC applied for Msg3 which may also be the same as OCC applied for PRACH.

[0339] In various embodiments of the present disclosure (e.g. separate to or in combination with any of those described above), the UE may perform Configured Grant Small Data Transmission (CG-SDT) using OCC. This can be done by configuring OCC in the CG-SDT configuration. This means that the UE performs the SDT PUSCH transmission using OCC as configured by the CG-SDT configuration. The CG-SDT configuration may be configured in an RRC Release message, e.g. as may be received by a UE.

[0340] In various embodiments of the present disclosure (e.g. separate to or in combination with any of those described above), a UE may perform a 2-step random access using OCC. This may include the UE using OCC for MsgA (MsgA is the Msg1 and Msg3 combined). Either the PRACH or the PUSCH of MsgA can be performed using OCC, or both can be configured to or for transmission using OCC. In various examples, the OCC index applied is the same in the PRACH and PUSCH transmission of MsgA. In 2-step random access, the chosen PRACH preamble may be used to determine the associated PUSCH resource. In various examples, the OCC (e.g. parameters or information for OCC, such as OCC length and / or OCC index) applied for PUSCH of MsgA may be determined based on the preamble selected for the PRACH transmission of the MsgA.

[0341] In various embodiments of the present disclosure (e.g. separate to or in combination with any of those described above), a UE indicates (e.g. is configured to indicate) support of OCC for a specific scenario, such as for one or more of handover, for RACH-less handover, for initial access, for Msg3, for Msg4 ACK / NACK, for CG-SDT and / or for 2-step random access. The UE may, for example, indicate (e.g. to the core network or cell) the OCC length that it supports, which may be specific for each of the specific scenario where the OCC is used (e.g. the UE can indicate an OCC length for each of the one or more specific scenarios that it has indicated support for or supports). In various examples, a specific OCC length may be applicable to different frequencies. For example, for higher frequencies a larger OCC length may be applicable. This means that a UE that supports higher frequencies may need to support a larger OCC length. This can for instance be specific for Frequency Ranges, such as FR1, FR2 or FR3; for example, OCC length, or support of OCC length, may be based on Frequency Range.

[0342] In various examples (e.g. separate to or in combination with any of those described above), OCC (e.g. the application of OCC to a transmission by a UE) may be specific to non-terrestrial network or may be applicable to terrestrial networks.

[0343] Specification Examples

[0344] There are now provided a number of Examples of changes to standards specification (in this case, TS 38.331, TS 36.331) to implement various features disclosed herein, e.g. see references to these Examples (or ‘Specification Examples’) found above. The text shown inboldandunderlinedindicates a change, e.g. addition, to the existing version of the specification. The version number given for the standards specification should not be seen as limiting, as it will be understood how to apply the shown changes to other, including newer, versions.

[0345] Specification Example #1

[0346]

[0347]

[0348]

[0349]

[0350] Specification Example #2

[0351]

[0352]

[0353] Specification Example #3

[0354]

[0355]

[0356] Figure 7 is a block diagram of an exemplary apparatus, or network entity, that may be used in examples of the present disclosure. The skilled person will appreciate said entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0357] The entity 1100 comprises a processor (or controller) 1101, a transmitter 1103 and a receiver 1105. The receiver 1105 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 1103 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 1101 is configured for performing one or more operations, for example according to the operations as described above. It will be appreciated that an entity as described herein may be a virtual or logical entity, which may be implemented using or in an apparatus which comprises a processor, an antenna, a receiver and / or a transmitter etc. but which does not itself have a physical form (i.e. would not be said to comprise a processor, an antenna, a receiver and / or a transmitter etc.).

[0358] Figure 8 illustrates a method of a UE according to an example of the disclosure.

[0359] In step S810, the UE receives, from an entity, a message to perform a RACH-less handover.

[0360] In step S820, the UE applies an OCC for a transmission relating to the RACH-less handover, based on information configuring the OCC included in the message.

[0361] According to an embodiment, there is provided a computer-readable storage medium comprising instructions which, when executed by at least one processor of an electronic device, cause the electronic device to perform a method according to any one or more of the embodiments, examples etc. described herein.

[0362] Various examples of the disclosure are provided by the following numbered clauses:

[0363] Clause 1. A user equipment (UE) comprising: a transmitter; a receiver; and at least one processor configured to: identify a trigger to perform a procedure, the procedure being an initial access procedure or a reconfiguration procedure to establish the UE with an entity; during performance of the procedure, apply an orthogonal cover code (OCC) for at least one transmission relating to the procedure, based on information configuring the OCC for the UE; and send the at least one transmission to the entity.

[0364] Clause 2. The UE of Clause 1, wherein the at least one transmission includes: a physical random access channel (PRACH) or Msg1; and / or a physical uplink shared channel (PUSCH) or Msg3.

[0365] Clause 3. The UE of Clause 2, wherein identifying the trigger comprises receiving a message to perform one of a handover, a random access channel (RACH)-less handover, or a cell reconfiguration.

[0366] Clause 4. The UE of Clause 3, wherein the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on the message.

[0367] Clause 5. The UE of Clause 4, wherein the information configuring the OCC is determined from a Configured Grant configuration, a RACH-less configuration in the Configured Grant configuration, in a RACH skip configuration, or in a configuration for RACH-less handover for the UE.

[0368] Clause 6. The UE of Clause 4 or Clause 5, wherein the message comprises information relating to an OCC index and / or information relating to an OCC length.

[0369] Clause 7. The UE of Clause 6, wherein the OCC index is configured based on a configuration for the RACH-less handover, and / or the OCC length is configured based on a default length, a Configured Grant configuration or a cell configuration.

[0370] Clause 8. The UE of Clause 4, wherein the message indicates to obtain the information configuring the OCC from a random access response (RAR) or Msg2 receiving by the UE.

[0371] Clause 9. The UE of Clause 2 or Clause 3, wherein the at least one transmission includes the PUSCH or Msg3; and wherein the information configuring the OCC is obtained based on a message received from the entity during the procedure.

[0372] Clause 10. The UE of Clause 9, wherein the message received from the entity is a random access response (RAR) or Msg2.

[0373] Clause 11. The UE of Clause 9 or Clause 10, wherein the message includes an indication of whether or not to apply the OCC for the at least one transmission.

[0374] Clause 12. The UE of Clause 11, wherein the UE is configured by broadcast instructions to apply OCC for the PUSCH or Msg3, prior to the procedure; and wherein, based on the indication in the message, the at least one processor is configured to: apply the OCC to the at least one transmission, or override the broadcast instructions to refrain from applying the OCC to the at least one transmission.

[0375] Clause 13. The UE of any one of Clauses 9 to 12, wherein the at least one processor is configured to: transmit an indication of support of OCC during performance of the procedure, prior to applying the OCC.

[0376] Clause 14. The UE of any one of Clauses 3 to 5 or 9 to 13, wherein the at least one processor is configured to: determine an OCC index and / or OCC length based on the message, wherein the information configuring the OCC includes the determined OCC index and / or OCC length.

[0377] Clause 15. The UE of Clause 14, wherein the OCC index is determined based on an Radio Network Temporary Identifier (RNTI) included in the message; and / or wherein the OCC length to be applied for the PUSCH or Msg3 is configured by a broadcast received by the UE.

[0378] Clause 16. The UE of any one of Clauses 4 to 15, wherein the at least one transmission further includes the PRACH or Msg1; and wherein one of: the OCC applied for the PUSCH or Msg3 is the same as the OCC applied for the PRACH or Msg1; or if an OCC length for the PRACH or Msg1 is different to an OCC length for the PUSCH or Msg3, determine an OCC index for the PUSCH or Msg3 based on an OCC index for the PRACH or Msg1.

[0379] Clause 17. The UE of Clause 1, wherein the at least one transmission includes a Msg4 acknowledgment(ACK) / negative ACK (NACK), ACK / NACK; and wherein the information configuring the OCC is configured by a Msg4 received by the UE.

[0380] Clause 18. The UE of Clause 17, wherein the at least one processor is configured to: transmit, in response to the Msg4, information indicating support for applying the OCC to the Msg4 ACK / NACK.

[0381] Clause 19. The UE of Clause 18, wherein the information is included in a medium access control (MAC) layer indication or in an radio resource control (RRC) message, and / or wherein the information includes a OCC length supported by the UE.

[0382] Clause 20. The UE of any one of Clauses 17 to 19, wherein: the at least one transmission further includes a PUSCH or Msg3, and the OCC applied for the Msg4 ACK / NACK is the same as the OCC applied for the PUSCH or Msg3; or the at least one transmission further includes a PRACH or Msg1, and the OCC applied for the Msg4 ACK / NACK is the same as the OC C applied for the PRACH or Msg1.

[0383] Clause 21. The UE of Clause 2, wherein the information configuring the OCC includes a OCC length and / or OCC index determined based on a random access preamble selected by the UE for the PRACH or Msg1.

[0384] Clause 22. The UE of any one of Clauses 1 to 21, wherein the at least one processor is configured to: upon failure of the procedure with the OCC applied to the at least one transmission, fallback to performing the procedure without applying OCC

[0385] Clause 23. The UE of Clause 24, wherein the at least one processor is configured to: record information regarding the application of OCC in the procedure for a result of the procedure

[0386] Clause 24. A method of a user equipment (UE), the method comprising: identifying a trigger to perform a procedure, the procedure being an initial access procedure or a reconfiguration procedure to establish the UE with an entity; during performance of the procedure, apply an orthogonal cover code (OCC) for at least one transmission relating to the procedure, based on information configuring the OCC for the UE; and sending the at least one transmission to the entity.

[0387] Clause 25. A computer-readable storage medium configured to store instructions which, when executed by at least one processor of a user equipment (UE), cause the UE to perform the method of Clause 24.

[0388] It will be appreciated that, in each example / embodiment / aspect etc. described above, one or more features or operations may be omitted, modified or moved (e.g., to change the order of the features or the operations), if desired and appropriate. For example, referring to the method shown by the call flow diagram of any of the figures, it will be understood that one or more of the operations of these methods may be omitted. Additionally, one or more features or operations from any example / embodiment may be combined with features or operations from any other example / embodiment. In particular, regardless of whether or not a pointer towards a combination of features / examples is found herein, the present disclosure should be considered to include all combinations of two or more of the embodiments, examples etc. disclosed herein, and all combinations of two or more of the features disclosed herein.

[0389] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment or example disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0390] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0391] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment and / or aspect disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0392] While the present disclosure has been shown, illustrated and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the disclosure.

[0393] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0394] The following describes the terminal, base station or network entity device that may constitute entity 1100 in Figure 7, as described above.

[0395] Figure 9 is a block diagram of a terminal or user equipment (UE) 900 according to an embodiment of the disclosure.

[0396] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0397] Referring to FIG. 9, the UE 900 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 901, at least one processor (hereinafter, referred to as simply “processor”) 902, and at least one memory (hereinafter, referred to as simply “memory”) 903. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 901, the processor 902, and the memory 903 of the UE 900 may operate. However, components of the UE 900 are not limited to the example components illustrated in FIG. 9. In another embodiment, the UE 900 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 901, the processor 902, or the memory 903 may be integrated in the form of one component.

[0398] The transceiver 901 may be a communication circuit or communication circuitry that enables the UE 900 to perform wireless communication with a node or an entity of a network. For example, the transceiver 901 may enable the UE 900 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 901 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (901) may include all subsequent generations of evolved wireless communications.

[0399] According to an embodiment, the UE 900 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 900 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 900 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 900 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0400] According to an embodiment, the transceiver 901 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 901 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 901 may output a signal received through a wireless channel to the processor 902 and may transmit, through a wireless channel, a signal output from the processor 902.

[0401] The processor 902 may control general operations of the UE 900 according to embodiments of the disclosure. The processor 902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 903, individually, collectively or in any combination thereof. Further, the processor 902 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0402] The processor 902 may be electrically, operatively, and / or communicatively coupled to the transceiver 901 to control the transceiver 901.

[0403] The processor 902 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 902 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 902 may be included in one chip (or IC) and the other part of the processor 902 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 901 or the memory 903.

[0404] The processor 902 may perform or control or cause an operation of the UE 900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 902 may control operations of the UE 900 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 902 may execute a computer program, codes, or instructions stored in the memory 903, so as to control other components of the UE 900 to enable execution of various operations.

[0405] The memory 903 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 903 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0406] The memory 903 may be electrically, operatively, and / or communicatively coupled to the processor 902 and may be accessed by the processor 902.

[0407] The memory 903 may store a computer program, codes, or instructions executable by the processor 902. According to an embodiment, a computer program, codes, or instructions executable by the processor 902 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 903, the processor 902 may perform various functions according to an embodiment of the disclosure.

[0408] According to an embodiment of the disclosure, operations of the UE 900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 903 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0409] Figure 10 is a block diagram of a base station (BS) 1000 according to an embodiment of the disclosure.

[0410] The BS 1000 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1000 through a wireless channel. The BS 1000 may perform communication with a node or an entity of a network through wired or wireless communication.

[0411] Referring to FIG. 10, the BS 1000 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1001, at least one processor (hereinafter, referred to as simply “processor”) 1002, and at least one memory (hereinafter, referred to as simply “memory”) 1003. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1001, the processor 1002, and the memory 1003 of the BS 1000 may operate. However, components of the BS 1000 are not limited to the example components illustrated in FIG. 10. In another embodiment, the BS 1000 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1001, the processor 1002, or the memory 1003 may be integrated in the form of one component.

[0412] The transceiver 1001 may be a communication circuit or communication circuitry that enables the BS 1000 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1001 may enable the BS 1000 to transmit or receive a signal to or from the UE 900 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1001 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1001) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1001 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1001 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1001 may output a signal received through a wireless channel to the processor 1002 and may transmit, through a wireless channel, a signal output from the processor 1002.

[0413] Meanwhile, according to an embodiment of the present disclosure, the BS 1000 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1000 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 10, when the BS 1000 performs wired communication, the BS 1000 may further include a separate network interface for wired communication in addition to the transceiver 1001. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0414] The processor 1002 may control general operations of the BS 1000 according to embodiments of the disclosure. The processor 1002 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1002 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1003, individually, collectively or in any combination thereof. Further, the processor 1002 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0415] The processor 1002 may be electrically, operatively, and / or communicatively coupled to the transceiver 1001 to control the transceiver 1001.

[0416] The processor 1002 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1002 may be included in one chip (or IC) and the other part of the processor 1002 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1001 or the memory 1003.

[0417] The processor 1002 may perform or control or cause an operation of the BS 1000 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1002 may control operations of the BS 1000 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1000 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1002 may execute a computer program, codes, or instructions stored in the memory 1003, so as to control other components of the BS 1000 to enable execution of various operations.

[0418] The memory 1003 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1003 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0419] The memory 1003 may be electrically, operatively, and / or communicatively coupled to the processor 1002 and may be accessed by the processor 1002.

[0420] The memory 1003 may store a computer program, codes, or instructions executable by the processor 1002. According to an embodiment, a computer program, codes, or instructions executable by the processor 1002 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1003, the processor 1002 may perform various functions according to an embodiment of the disclosure.

[0421] According to an embodiment of the disclosure, operations of the BS 1000 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1003 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0422] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0423] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0424] Figure 11 is a block diagram of a network entity 1100 according to an embodiment of the disclosure.

[0425] The network entity 1100 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1100.

[0426] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0427] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0428] Referring to FIG. 11, the network entity 1100 may include at least one network interface 1101, at least one processor 1102 (hereinafter, “processor”), and at least one memory 1103 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1100, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 11. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0429] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1101, the processor 1102, and the memory 1103 of the network entity 1100 may operate. However, components of the network entity 1100 are not limited to the example components illustrated in FIG. 11. In another embodiment, the network entity 1100 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1101, the processor 1102, or the memory 1103 may be integrated in the form of one component.

[0430] The network interface 1101 is a collective term for a transmitter part of the network entity 1100 and a receiver part of the network entity 1100, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1101 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1101 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1101 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0431] The processor 1102 may control general operations of the network entity 1100 according to embodiments of the disclosure. The processor 1102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1103, individually, collectively or in any combination thereof. Further, the processor 1102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0432] According to an embodiment, the processor 1102 may be electrically, operatively, and / or communicatively coupled to the network interface 1101 to control the network interface 1101.

[0433] The processor 1102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1102 may be included in one chip (or IC) and the other part of the processor 1102 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1101 or the memory 1103.

[0434] The processor 1102 may perform or control or cause an operation of the network entity 1100 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1102 may control operations of the network entity 1100 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1102 may execute a computer program, codes, or instructions stored in the memory 1103, so as to control other components of the network entity 1100 to enable execution of various operations.

[0435] The memory 1103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0436] The memory 1103 may be electrically, operatively, and / or communicatively coupled to the processor 1102 and may be accessed by the processor 1102.

[0437] The memory 1103 may store a computer program, codes, or instructions executable by the processor 1102. According to an embodiment, a computer program, codes, or instructions executable by the processor 1102 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1103, the processor 1102 may perform various functions according to an embodiment of the disclosure.

[0438] According to an embodiment of the disclosure, operations of the network entity 1100 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0439] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0440]

[0441]

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station, configuration information on a configured grant for a random access channel-less (RACH-less) handover; andidentifying information associated with an orthogonal cover code (OCC) based on the configuration information.2.The method of claim 1,wherein the information includes information on a length and information on a index.3.The method of claim 1,wherein the configuration information is included in a radio resource control (RRC) reconfiguration message.4.The method of claim 1,wherein the OCC is for the RACH-less handover in a non-terrestrial network (NTN).5.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), configuration information on a configured grant for a random access channel-less (RACH-less) handover,wherein information associated with an orthogonal cover code (OCC) is based on the configuration information.6.The method of claim 5,wherein the information includes information on a length and information on a index.7.The method of claim 5,wherein the configuration information is included in a radio resource control (RRC) reconfiguration message.8.The method of claim 5,wherein the OCC is for the RACH-less handover in a non-terrestrial network (NTN).9.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive, from a base station, configuration information on a configured grant for a random access channel-less (RACH-less) handover, andidentify information associated with an orthogonal cover code (OCC) based on the configuration information.10.The UE of claim 9,wherein the information includes information on a length and information on a index.11.The UE of claim 9,wherein the configuration information is included in a radio resource control (RRC) reconfiguration message.12.The UE of claim 9,wherein the OCC is for the RACH-less handover in a non-terrestrial network (NTN).13.A base station comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the base station to:transmit, to a user equipment (UE), configuration information on a configured grant for a random access channel-less (RACH-less) handover,wherein information associated with an orthogonal cover code (OCC) is based on the configuration information.14.The base station of claim 13,wherein the information includes information on a length and information on a index.15.The base station of claim 13,wherein the configuration information is included in a radio resource control (RRC) reconfiguration message, andwherein the OCC is for the RACH-less handover in a non-terrestrial network (NTN).