WO2024025395A1 - Method and apparatus for entity in a wireless communication system - Google Patents

Method and apparatus for entity in a wireless communication system Download PDF

Info

Publication number
WO2024025395A1
WO2024025395A1 PCT/KR2023/011081 KR2023011081W WO2024025395A1 WO 2024025395 A1 WO2024025395 A1 WO 2024025395A1 KR 2023011081 W KR2023011081 W KR 2023011081W WO 2024025395 A1 WO2024025395 A1 WO 2024025395A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
sdt
rach
random access
entity
Prior art date
Application number
PCT/KR2023/011081
Other languages
English (en)
French (fr)
Inventor
Yanru Wang
Lixiang Xu
Hong Wang
Weiwei Wang
Original Assignee
Samsung Electronics Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2024025395A1 publication Critical patent/WO2024025395A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network

Definitions

  • the present disclosure relates to a technical field of wireless communication, and more specifically, the present disclosure relates to method and apparatus for an entity in a wireless communication system.
  • 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.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • THz terahertz
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • 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.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • the present disclosure relates to a technical field of wireless communication, and more specifically, the present disclosure relates to method and apparatus for an entity in a wireless communication system.
  • Embodiments of the present disclosure provide a method performed by a first entity in a wireless communication system, including: transmitting, to a second entity, at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information, wherein the at least one piece of information is associated with at least one of the first entity and other entities except the first entity.
  • SDT small data transmission
  • RACH random access channel
  • Embodiments of the present disclosure provide a method performed by a second entity in a wireless communication system, including: receiving, from a first entity, at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information, wherein the at least one piece of information is associated with at least one of the first entity and other entities except the first entity.
  • SDT small data transmission
  • RACH random access channel
  • Embodiments of the present disclosure provide a first entity device in a wireless communication system, including a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods performed by the first entity in the wireless communication system according to embodiments of the present disclosure.
  • Embodiments of the present disclosure provide a second entity device in a wireless communication system, including a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods performed by the second entity in the wireless communication system according to embodiments of the present disclosure.
  • Embodiments of the present disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when performed by a processor, are used to implement the methods performed by the first entity and/or the second entity in the wireless communication system according to embodiments of the present disclosure.
  • the methods performed by the first entity and/or the second entity in the wireless communication system provided by the present disclosure enable self-optimizing decision-making or configuration updating at the network side by exchanging information related to random access and/or the like between entities.
  • FIG. 1 illustrates an example of system architecture of system architecture evolution (SAE) according to various embodiments of the present disclosure
  • FIG. 2 illustrates an example of system architecture according to various embodiments of the present disclosure
  • FIG. 3 illustrates a flowchart of a method performed by a first entity in a wireless communication system according to various embodiments of the present disclosure
  • FIG. 4 illustrates a flowchart of a method performed by a second entity in a wireless communication system according to various embodiments of the present disclosure
  • FIG. 5 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 6 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 7 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 8 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 9 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 10 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 11 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 12 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 13 illustrates a schematic diagram of a method for supporting network self-optimization according to various embodiments of the present disclosure
  • FIG. 14 illustrates a schematic diagram of a first entity according to various embodiments of the present disclosure
  • FIG. 15 illustrates a schematic diagram of a second entity according to various embodiments of the present disclosure
  • FIG. 16 illustrates a block diagram of a terminal (or a user equipment (UE), according to embodiments of the present disclosure.
  • FIG. 17 illustrates a block diagram of a base station, according to embodiments of the present disclosure.
  • the 5G or pre-5G communication system is also called “beyond 4G network” or “post LTE system”.
  • Wireless communication is one of the most successful innovations in modern history. Recently, a number of subscribers of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, a demand for wireless data services is growing rapidly. In order to meet rapid growth of mobile data services and support new applications and deployments, it is very important to improve efficiency and coverage of wireless interfaces.
  • small data may be transmitted in a Message A (MSGA) or a Message 3 (MSG3).
  • MSGA Message A
  • MSG3 Message 3
  • Random access resources may be partitioned according to different features (for example, Reduced Capability (RedCap), slice, small data transmission, coverage enhancement, etc.).
  • RedCap Reduced Capability
  • slice small data transmission
  • coverage enhancement etc.
  • the term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components.
  • the terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
  • a or B may include A, may include B, or may include both A and B.
  • Embodiments of the present disclosure provide a method performed by a first entity in a wireless communication system, including: transmitting, to a second entity, at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information, wherein the at least one piece of information is associated with at least one of the first entity and other entities except the first entity.
  • SDT small data transmission
  • RACH random access channel
  • the method performed by the first entity in the wireless communication system further includes: receiving, from the second entity, fourth information including a request for the SDT information and/or the RACH partition random access information, wherein the first information and/or the second information are transmitted by the first entity to the second entity based on the fourth information.
  • the method performed by the first entity in the wireless communication system further includes: transmitting, to the second entity, third information indicating that the SDT information is available and/or the RACH partition random access information is available, wherein the fourth information is transmitted by the first entity to the second entity based on the third information.
  • the method performed by the first entity in the wireless communication system further includes: receiving, from the second entity, SDT configuration information and/or RACH partition configuration information associated with the second entity, wherein at least part of the SDT configuration information and/or RACH partition configuration information associated with the second entity is determined by the second entity based on the fifth information.
  • the at least one piece of information is used for at least one of the first entity and the second entity to make a network self-optimization decision, wherein the network self-optimization decision includes at least one of network energy saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration updating.
  • the first information includes one or more of: user equipment identification, node identification, cell identification, indication that a random access is for a purpose of SDT, SDT configuration information for a random access, a time from a random access to information reporting, a time from an SDT start to information reporting, a time from an SDT radio link failure to information reporting, a time from an SDT interruption to information reporting, a time from an SDT failure to information reporting, a signal quality at a time of SDT failure, a remaining data volume after SDT failure, a signal quality at a time of random access, a data volume at a time of random access, data volume when SDT starts, data volume related information in a SDT transmission process, a data volume transmitted via SDT, a remaining data volume after SDT transmission, a time from an SDT start to an SDT end, a time from an SDT start to a radio link failure, an SDT timer status at a time of SDT end, an SDT timer status at a time of SDT end, an SDT
  • the data volume related information in a SDT transmission process includes one or more of: an arrived data volume in a SDT transmission process, a maximum data volume in a SDT transmission process, a minimum data volume in a SDT transmission process and an average data volume in a SDT transmission process.
  • the second information includes one or more of: user equipment identification, node identification, cell identification, a feature priority, a RACH partition configuration, a time from a random access to information reporting, available resources at a time of random access, a time of a random access, a time from a random access failure to information reporting, a time of a random access failure, a feature corresponding to available resources at a time of random access, a signal quality corresponding to a synchronization signal and physical broadcast channel block (SSB), a signal quality corresponding to a MSG3, and information for attempting a random access.
  • SSB physical broadcast channel block
  • the fifth information includes one or more of: node identification, cell identification, SDT configuration information for a random access, an acceptable value and/or a range of the acceptable value of the SDT configuration information for a random access, a RACH partition configuration, an acceptable value and/or a range of the acceptable value of the RACH partition configuration.
  • the fourth information includes one or more of: a request for SDT information, a request for an SDT report, a request for RACH partition random access information, and a request for a RACH partition report.
  • the third information includes one or more of: SDT information available, SDT report available, RACH partition random access information available, and RACH partition report available.
  • Embodiments of the present disclosure provide a method performed by a second entity in a wireless communication system, including: receiving, from a first entity, at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information, wherein the at least one piece of information is associated with at least one of the first entity and other entities except the first entity.
  • SDT small data transmission
  • RACH random access channel
  • the method performed by the second entity in the wireless communication system further includes: transmitting, to the first entity, fourth information including a request for the SDT information and/or the RACH partition random access information, wherein the first information and/or the second information are transmitted by the first entity to the second entity based on the fourth information.
  • the method performed by the second entity in the wireless communication system further includes: receiving, from the first entity, third information indicating that the SDT information is available and/or the RACH partition random access information is available, wherein the fourth information is transmitted by the first entity to the second entity based on the third information.
  • the method performed by a second entity in the wireless communication system further includes: transmitting, to the first entity, SDT configuration information and/or RACH partition configuration information associated with the second entity, wherein at least part of the SDT configuration information and/or RACH partition configuration information associated with the second entity is determined by the second entity based on the fifth information.
  • the at least one piece of information is used for at least one of the first entity and the second entity to make a network self-optimization decision, wherein the network self-optimization decision includes at least one of network energy saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration updating.
  • the first information includes one or more of: user equipment identification, node identification, cell identification, indication that a random access is for a purpose of SDT, SDT configuration information for a random access, a time from a random access to information reporting, a time from an SDT start to information reporting, a time from an SDT radio link failure to information reporting, a time from an SDT interruption to information reporting, a time from an SDT failure to information reporting, a signal quality at a time of SDT failure, a remaining data volume after SDT failure, a signal quality at a time of random access, a data volume at a time of random access, data volume when SDT starts, data volume related information in a SDT transmission process, a data volume transmitted via SDT, a remaining data volume after SDT transmission, a time from an SDT start to an SDT end, a time from an SDT start to a radio link failure, an SDT timer status at a time of SDT end, an SDT timer status at a time of SDT end, an SDT
  • the data volume related information in a SDT transmission process includes one or more of: an arrived data volume in a SDT transmission process, a maximum data volume in a SDT transmission process, a minimum data volume in a SDT transmission process and an average data volume in a SDT transmission process.
  • the second information includes one or more of: user equipment identification, node identification, cell identification, a feature priority, a RACH partition configuration, a time from a random access to information reporting, available resources at a time of random access, a time of a random access, a time from a random access failure to information reporting, a time of a random access failure, a feature corresponding to available resources at a time of random access, a signal quality corresponding to a synchronization signal and physical broadcast channel block (SSB), a signal quality corresponding to a MSG3, and information for attempting a random access.
  • SSB physical broadcast channel block
  • the fifth information includes one or more of: node identification, cell identification, SDT configuration information for a random access, an acceptable value and/or a range of the acceptable value of the SDT configuration information for a random access, a RACH partition configuration, an acceptable value and/or a range of the acceptable value of the RACH partition configuration.
  • the fourth information includes one or more of: a request for SDT information, a request for an SDT report, a request for RACH partition random access information, and a request for a RACH partition report.
  • the third information includes one or more of: SDT information available, SDT report available, RACH partition random access information available, and RACH partition report available.
  • Embodiments of the present disclosure provide a first entity device in a wireless communication system, including a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods performed by the first entity in the wireless communication system according to embodiments of the present disclosure.
  • Embodiments of the present disclosure provide a second entity device in a wireless communication system, including a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods performed by the second entity in the wireless communication system according to embodiments of the present disclosure.
  • Embodiments of the present disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when performed by a processor, are used to implement the methods performed by the first entity and/or the second entity in the wireless communication system according to embodiments of the present disclosure.
  • the methods performed by the first entity and/or the second entity in the wireless communication system provided by the present disclosure enable self-optimizing decision-making or configuration updating at the network side by exchanging information related to random access and/or the like between entities.
  • FIGs. 1 to 17 discussed below and various embodiments for describing the principles of the present disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.
  • FIG. 1 illustrates an exemplary system architecture 100 of system architecture evolution (SAE).
  • UE User equipment
  • E-UTRAN evolved universal terrestrial radio access network
  • E-UTRAN is a radio access network, which includes a macro base station (eNodeB/NodeB) that provides UE with interfaces to access the radio network.
  • a mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE.
  • MME mobility management entity
  • SGW serving gateway
  • a packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104.
  • a policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria.
  • a general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS).
  • UMTS universal mobile telecommunications system
  • a home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.
  • FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.
  • User equipment (UE) 201 is a terminal device for receiving data.
  • a next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network.
  • An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE.
  • a user plane function entity (UPF) 204 mainly provides functions of user plane.
  • a session management function entity SMF 205 is responsible for session management.
  • a data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.
  • Entities and/or nodes mentioned in the present disclosure may include gNB, gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), gNB-CU-Control Plane (gNB CU-CP), gNB-CU-User Plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, Access and Mobility Management Function (AMF), Session Management Function (SMF), Mobility Management Entity (MME) and other network entities or network logic units.
  • gNB gNB Central Unit
  • gNB-DU gNB Distributed Unit
  • gNB CU-CP gNB-CU-Control Plane
  • gNB CU-User Plane gNB CU-UP
  • en-gNB eNB
  • ng-eNB ng-eNB
  • UE Access and Mobility Management Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • MME Mobility Management Entity
  • the signal strength and/or signal quality mentioned in the present disclosure may be a Received Signal Strength Indicator (RSSI), Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), etc.
  • RSSI Received Signal Strength Indicator
  • RSRP Reference Signal Receiving Power
  • RSSQ Reference Signal Receiving Quality
  • SINR Signal to Interference plus Noise Ratio
  • the features described in the present disclosure may include one or more of: RedCap, SDT (or smallData), slice (or slice group), Coverage Enhancement, and/or the like.
  • the present disclosure solves the problem that the related configuration of SDT and/or RACH partition cannot be optimized because the related information of SDT and RACH partition cannot be provided for network self-optimization in the prior art.
  • FIG. 3 illustrates a flowchart of a method 300 performed by a first entity in a wireless communication system according to embodiments of the present disclosure.
  • the method 300 performed by the first entity in the wireless communication system may include that the first entity transmits to a second entity at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information.
  • the at least one piece of information may be associated with at least one of the first entity and any other entity except the first entity.
  • the SDT configuration information and/or RACH partition configuration information included in the fifth information transmitted by the first entity to the second entity may be SDT configuration information and/or RACH partition configuration information of the first entity itself, or SDT configuration information and/or RACH partition configuration information of any other entity collected or acquired by the first entity in any way.
  • the other information mentioned above has the same meaning, and will not be repeated here.
  • the first entity, the second entity and any other entity mentioned herein may be any of the above-mentioned example entities or entities newly introduced in the future, and there is no restriction herein.
  • the method 300 may further include that the first entity receives fourth information including a request for the SDT information and/or the RACH partition random access information from the second entity.
  • the first information and/or the second information described above may be transmitted by the first entity to the second entity autonomously or based on the fourth information.
  • the method 300 may further include that the first entity transmits third information indicating that the SDT information is available and/or the RACH partition random access information is available to the second entity.
  • the fourth information may be transmitted by the first entity to the second entity autonomously or based on the received third information.
  • the method 300 may further include that the first entity receives SDT configuration information and/or RACH partition configuration information associated with the second entity from the second entity.
  • some or all of the SDT configuration information and/or RACH partition configuration information associated with the second entity may be determined by the second entity based at least in part on the fifth information received from the first entity.
  • the second entity may determine part or all of the SDT configuration information and/or RACH partition configuration information associated with the second entity based on its own situation (e.g., its own capabilities and/or its own existing configuration) and/or SDT configuration information and/or RACH partition configuration information associated with the first entity and/or any other entity included in the fifth information received from the first entity.
  • FIG. 4 illustrates a flowchart of a method 400 performed by a second entity in a wireless communication system according to embodiments of the present disclosure.
  • the method 400 performed by the second entity in the wireless communication system may include that the second entity receives from the first entity at least one piece of information of first information including small data transmission (SDT) information for SDT based on SDT configuration information, second information including random access channel (RACH) partition random access information for random access based on RACH partition configuration information, and fifth information including the SDT configuration information and/or the RACH partition configuration information.
  • the at least one piece of information may be associated with at least one of the first entity and any other entity except the first entity.
  • the SDT configuration information and/or RACH partition configuration information included in the fifth information transmitted by the first entity to the second entity may be SDT configuration information and/or RACH partition configuration information of the first entity itself, or SDT configuration information and/or RACH partition configuration information of any other entity collected or acquired by the first entity in any way.
  • the other information mentioned above has the same meaning, and will not be repeated here.
  • the first entity, the second entity and any other entity mentioned herein may be any of the above-mentioned example entities or entities newly introduced in the future, and there is no restriction herein.
  • the method 400 may further include that the second entity transmits fourth information including a request for the SDT information and/or the RACH partition random access information to the first entity.
  • the first information and/or the second information described above may be transmitted by the first entity to the second entity autonomously or based on the fourth information.
  • the method 400 may further include that the second entity receives third information indicating that the SDT information is available and/or the RACH partition random access information is available from the first entity.
  • the fourth information may be transmitted by the first entity to the second entity autonomously or based on the received third information.
  • the method 400 may further include that the second entity transmits SDT configuration information and/or RACH partition configuration information associated with the second entity to the first entity.
  • the SDT configuration information and/or RACH partition configuration information associated with the second entity may be determined by the second entity based at least in part on the fifth information received from the first entity.
  • the second entity may determine the SDT configuration information and/or RACH partition configuration information associated with the second entity based on its own situation (e.g., its own capabilities and/or its own existing configuration) and/or SDT configuration information and/or RACH partition configuration information associated with the first entity and/or any other entity included in the fifth information received from the first entity.
  • a method performed by the first entity and/or the second entity in the wireless communication system according to embodiments of the present disclosure may also be called a method for supporting network self-optimization.
  • One embodiment of the present disclosure proposes a method for supporting network self-optimization, which may include that a first entity transmits first information including Small Data Transmission (SDT) information for SDT based on SDT configuration information to a second entity for the second entity to determine whether the SDT configuration is suitable and/or update a parameter configuration for SDT based on the received information, and/or the second entity forwards the received information to other entities for the other entities to determine whether the SDT configuration is suitable and/or update a configuration related to the SDT, so as to prevent link interruption in an SDT process and improve the robustness and effectiveness of SDT.
  • the SDT here may be Random Access-SDT (RA-SDT) or Configured Grant-SDT (CG-SDT).
  • the first information may be included in one or more of: a user information response (UEInformationResponse), secondary cell group failure information (SCGFailureInformation), master cell group failure information (MCGFailureInformation) of Radio Resource Control (RRC); a FAILURE INDICATION message, a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, an S-NODE MODIFICATION REQUEST message, an SgNB MODIFICATION REQUEST message, an SCG FAILURE INFORMATION REPORT message, a RRC TRANSFER message of Xn; an ACCESS AND MOBILITY INDICATION message of F1; an UPLINK RAN CONFIGURATION TRANSFER message and a DOWNLINK RAN CONFIGURATION TRANSFER message of NG; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.
  • UEInformationResponse a user information response
  • the first information may be included in a report, where the report may be a Connection Establishment Failure (CEF) report, a Random Access report, a Successful Handover report, a Radio Link Failure (RLF) report, a measurement report, or other reports related to wireless connection.
  • the report may also be a new report, for example, a random access SDT report (RA-SDTReport) and/or random access SDT information (RA-SDTInfo) and/or SDT report (SDTReport) and/or SDT information (SDTInfo).
  • the first information may include one or more of the following fields or related information:
  • ⁇ UE identification it is used to identify a UE performing the random access and/or SDT.
  • Node identification it is used to identify a node corresponding to the random access and/or SDT by the UE.
  • ⁇ Cell identification it is used to identify a cell corresponding to the random access and/or SDT by the UE.
  • ⁇ Indication that a random access is for a purpose of SDT it is used to identify that the purpose of the random access is for SDT. This field may be included in a random access purpose (raPurpose).
  • ⁇ SDT configuration information for a random access it is used to indicate the SDT configuration information applied in the random access.
  • the information may include one or more of: a RSRP threshold corresponding to the SDT (sdt-RSRP-Threshold), a logical channel state reporting delay timer corresponding to the SDT (sdt-LogicalChannelSR-DelayTimer), a data volume threshold corresponding to the SDT (sdt-DataVolumeThreshold), and an SDT timer value (for example, T319a).
  • a time from a random access to information reporting it is used to indicate the time from the random access to the reporting of the first information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from an SDT start to information reporting it is used to indicate the time from the SDT start to the reporting of the first information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from an SDT radio link failure to information reporting it is used to indicate the time from the SDT radio link failure to the reporting of the first information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from an SDT interruption to information reporting it is used to indicate the time from the SDT interruption to the information reporting.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from an SDT failure to information reporting it is used to indicate the time from the SDT failure to the information reporting.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a signal quality at a time of SDT failure it is used to indicate the signal quality at a time of SDT failure.
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • the SDT failure may be a radio link failure.
  • a remaining data volume after SDT failure it is used to indicate the remaining untransmitted data volume after the SDT failure.
  • the SDT failure may be a radio link failure.
  • a signal quality at a time of random access it is used to indicate the signal quality at a time of random access.
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • a data volume at a time of random access it is used to indicate the data volume when random access SDT is triggered.
  • a data volume when SDT starts it is used to indicate the data volume when SDT is triggered.
  • Data volume related information in a SDT transmission process it is used to indicate data volume related information in a SDT transmission process.
  • the information may help a receiving node of the information to determine whether the configuration of SDT is suitable and/or how to perform adjustments (e.g., increase, decrease, etc.), for example, data volume threshold, SDT timer value (e.g., T319a), etc.
  • the related information may include one or more of the following:
  • An arrived data volume in a SDT transmission process it is used to indicate the arrived data volume in a SDT transmission process.
  • a maximum data volume in a SDT transmission process it is used to indicate the buffered maximum data volume in a SDT transmission process.
  • a minimum data volume in a SDT transmission process it is used to indicate the buffered minimum data volume in a SDT transmission process.
  • An average data volume in a SDT transmission process it is used to indicate the buffered average data volume in a SDT transmission process.
  • a data volume transmitted via SDT it is used to indicate the data volume transmitted via SDT.
  • the information may help a receiving node of the information to determine whether the configuration of SDT is suitable and/or how to perform adjustments (e.g., increase, decrease, etc.), for example, data volume threshold, SDT timer value (e.g., T319a), etc.
  • a remaining data volume after SDT transmission it is used to indicate the remaining untransmitted data volume after the SDT.
  • the information may help a receiving node of the information to determine whether the configuration of SDT is suitable and/or how to perform adjustments (e.g., increase, decrease, etc.), for example, data volume threshold, SDT timer value (e.g., T319a), etc.
  • a time from an SDT start to an SDT end it may also be a time from a T319a timer start to the SDT end.
  • the time may be used for a node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • it may be used for updating a timer (e.g., it may be T319a) in order to set a more suitable timer.
  • a time from an SDT start to a radio link failure it may also be the time from the T319a timer start to the radio link failure.
  • the time may be used for a node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • it may be used for updating a timer (e.g., it may be T319a) in order to set a more suitable timer.
  • An SDT timer status at a time of SDT end it indicates a status of an SDT timer at a time of SDT end. It may include running, stop, etc.
  • the SDT timer may be the T319a.
  • the status may be used for a node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • it may be used for updating a timer (e.g., it may be T319a) in order to set a more suitable timer.
  • it may be used for updating a data volume threshold corresponding to the configured SDT. For example, there may be a case that the SDT is terminated due to the stop of a timer, while the remaining data volume is small.
  • An SDT timer status at a time of radio link failure it indicates a status of the SDT timer at a time of radio link failure. It may include running, stop, etc.
  • the SDT timer may be the T319a.
  • An SDT end cause it indicates a reason why the SDT ends. It may include one or more of: the stop of a SDT timer (for example, the stop of T319a), the reception of a RRC message (for example, it may be a RRC release message, a RRC resume message, a RRC setup message, a RRC reject message), radio link failure, the completion of the transmission, RRC connection resume failure, etc.
  • An SDT failure cause it indicates a reason why the SDT fails. It may include one or more of: the stop of a SDT timer (for example, the stop of T319a), the reception of a RRC message (for example, it may be a RRC release message, a RRC resume message, a RRC setup message, a RRC reject message), radio link failure, the completion of the transmission, RRC connection resume failure, etc.
  • One embodiment of the present disclosure proposes a method for supporting network self-optimization, which may include that a first entity transmits second information including Random Access Channel (RACH) partition random access information for random access based on RACH partition configuration information to a second entity for the second entity to determine whether a configuration of random access is suitable and/or update a parameter configuration of random access based on the received information, and/or the second entity forwards the received information to other entities for the other entities to determine whether a configuration of random access is suitable and/or update a configuration related to random access, so as to prevent random access failure caused by an unreasonable random access configuration and improve the robustness and effectiveness of random access.
  • RACH Random Access Channel
  • the second information may be included in one or more of: a user information response (UEInformationResponse), secondary cell group failure information (SCGFailureInformation), master cell group failure information (MCGFailureInformation) of RRC; a FAILURE INDICATION message, a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, an S-NODE MODIFICATION REQUEST message, an SgNB MODIFICATION REQUEST message, an SCG FAILURE INFORMATION REPORT message, a RRC TRANSFER message of Xn; an ACCESS AND MOBILITY INDICATION message of F1; an UPLINK RAN CONFIGURATION TRANSFER message and a DOWNLINK RAN CONFIGURATION TRANSFER message of NG; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.
  • the second information may be included in a report, where the report may be a Connection Establishment Failure (CEF) report, a Random Access report, a Successful Handover report, a Radio Link Failure (RLF) report, a measurement report, or other reports related to wireless connection.
  • the report may also be a new report, for example, RACH Partition Random Access Report (RA-RACHPatitionRepor) and/or RACH Partition Random Access Information Report (RA-RACHPatitionReportInfo).
  • the second information may include one or more of the following fields or related information:
  • ⁇ UE identification it is used to identify a UE performing the random access.
  • Node identification it is used to identify a node corresponding to the random access by the UE.
  • ⁇ Cell identification it is used to identify a cell corresponding to the random access by the UE.
  • a feature priority it is used to indicate a priority of a feature and/or a priority list of a group of features.
  • a RACH partition configuration it is used to indicate the RACH partition configuration applied when performing the random access.
  • the configuration may include one or more of:
  • a feature combination it is used to indicate features the configuration is applicable to.
  • the features may include one or more of: RedCap, SDT (or smallData), slice (or slice group), Coverage Enhancement, etc.
  • startPreambleForThisPartition A start preamble for this partition (startPreambleForThisPartition)
  • the uplink resource may be a Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • Feature-specific parameters it includes one or more of: a signal quality threshold corresponding to a Synchronization Signal and PBCH (physical broadcast channel) block (SSB) (for example, it may be rsrp-ThresholdSSB), a signal quality threshold corresponding to a MSG3 (for example, it may be rsrp-ThresholdMsg3), a message power offset corresponding to GroupB (for example, it may be messagePowerOffsetGroupB), a size of random access GroupA (for example, it may be ra-SizeGroupA), and a preamble delta (deltaPreamble).
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • a time from a random access to information reporting it is used to indicate the time from the random access to the reporting of the second information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from a random access failure to information reporting it is used to indicate the time from a random access failure to the reporting of the second information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • ⁇ A time of a random access failure may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a signal quality corresponding to an SSB the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • a signal quality corresponding to a MSG3 the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • Information for attempting a random access information and/or information list for each attempt in a random access process, it includes one or more of:
  • the number of attempts it is used to indicate the number of attempts. It indicates how many times this attempt is.
  • the total number of attempts it is used to indicate the total number of attempts.
  • - UE identification it is used to identify a UE performing the random access.
  • Node identification it is used to identify a node corresponding to the random access by the UE.
  • - Cell identification it is used to identify a cell corresponding to the random access by the UE.
  • a time from a random access to information reporting it is used to indicate the time from the random access to the reporting of the second information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • a time from a random access failure to information reporting it is used to indicate the time from the random access failure to the reporting of the second information.
  • the time may be used for the node and/or entity to find related configuration, and for the node and/or entity to perform self-optimization such as configuration update on the related configuration.
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • the features may include one or more of: RedCap, SDT (or smallData), slice (or slice group), Coverage Enhancement, etc.
  • the uplink resource may be a Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • Feature-specific parameters it includes one or more of: a signal quality threshold corresponding to a Synchronization Signal and PBCH (physical broadcast channel) block (SSB) (for example, it may be rsrp-ThresholdSSB), a signal quality corresponding to a Synchronization Signal and PBCH (physical broadcast channel) block (SSB), a signal quality threshold corresponding to a MSG3 (for example, it may be rsrp-ThresholdMsg3), a signal quality corresponding to a MSG3, a message power offset corresponding to GroupB (for example, it may be messagePowerOffsetGroupB), a size of random access GroupA (for example, it may be ra-SizeGroupA), and a preamble delta (deltaPreamble).
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • One embodiment of the present disclosure proposes a method for supporting network self-optimization, which may include that a first entity transmits third information indicating that SDT information is available and/or RACH partition random access information is available to a second entity, so as to inform the second entity that the first entity has the SDT information and/or the RACH partition random access information, so that the second entity may choose whether to acquire the information.
  • the third information may be included in one or more of: UE-Measurements Available (UE-MeasurementsAvailable), RRC Setup Complete (RRCSetupComplete), RRC Reestablishment Complete (RRCReestablishmentComplete), RRC Reconfiguration Complete (RRCReconfigurationComplete), or RRC Resume Complete (RRCResumeComplete) of RRC; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.
  • UE-Measurements Available UE-MeasurementsAvailable
  • RRCSetupComplete RRC Reestablishment Complete
  • RRCReconfigurationComplete RRC Reconfiguration Complete
  • RRCResumeComplete RRC Resume Complete
  • the third information may include one or more of the following fields or related information:
  • SDT information available it is used to indicate that the SDT information is available, which represents that there is stored SDT information available.
  • This field may be represented by a single bit, for example, when this bit is 1, it means that the SDT information is available, and when this bit is 0, it means that the SDT information is not available; alternatively, when this bit is 0, it means that the SDT information is available, and when this bit is 1, it means that the SDT information is not available.
  • SDT report available it is used to indicate that the SDT report is available, which represents that there is stored SDT report available.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that the SDT report is available, and when this bit is 0, it means that the SDT report is not available; alternatively, when this bit is 0, it means that the SDT report is available, and when this bit is 1, it means that the SDT report is not available.
  • RACH partition random access information available it is used to indicate that the RACH partition random access information is available, which represents that there is stored RACH partition random access information available.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that the RACH partition random access information is available, and when this bit is 0, it means that the RACH partition random access information is not available; alternatively, when this bit is 0, it means that the RACH partition random access information is available, and when this bit is 1, it means that the RACH partition random access information is not available.
  • RACH partition report available it is used to indicate that the RACH partition report is available, which represents that there is stored RACH partition report available.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that the RACH partition report is available, and when this bit is 0, it means that the RACH partition report is not available; alternatively, when this bit is 0, it means that the RACH partition report is available, and when this bit is 1, it means that the RACH partition report is not available.
  • the second entity may transmit fourth information including a request for SDT information and/or RACH partition random access information to the first entity according to its own situation and/or according to the received information indicating that the SDT information is available and/or the RACH partition random access information is available, so as to request the first entity to transmit and/or report the SDT information and/or the RACH partition random access information, so that the second entity may obtain the SDT information and/or the RACH partition random access information and make a self-optimization decision, and/or the second entity forwards the received information to other entities for the other entities to make a self-optimization decision.
  • the fourth information may be included in one or more of: UEInformationRequest of RRC, or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.
  • the fourth information may include one or more of the following fields or related information:
  • a request for SDT information it is used to request the SDT information and/or indicate whether it is required to report the SDT information.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that SDT information is requested and/or needs to be reported, and when this bit is 0, it means that SDT information is not requested and/or needs not to be reported; alternatively, when this bit is 0, it means that SDT information is requested and/or needs to be reported, and when this bit is 1, it means that SDT information is not requested and/or needs not to be reported.
  • a request for an SDT Report it is used to request the SDT report and/or indicate whether it is required to report the SDT report.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that SDT report is requested and/or needs to be reported, and when this bit is 0, it means that SDT report is not requested and/or needs not to be reported; alternatively, when this bit is 0, it means that SDT report is requested and/or needs to be reported, and when this bit is 1, it means that SDT report is not requested and/or needs not to be reported.
  • a request for RACH partition random access information it is used to request RACH partition random access information and/or indicate whether it is required to report the RACH partition random access information.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that the RACH partition random access information is requested and/or needs to be reported, and when this bit is 0, it means that the RACH partition random access information is not requested and/or needs not to be reported; alternatively, when this bit is 0, it means that the RACH partition random access information is requested and/or needs to be reported, and when this bit is 1, it means that the RACH partition random access information is not requested and/or needs not to be reported.
  • a request for a RACH partition report it is used to request a RACH partition report and/or indicate whether it is required to report the RACH partition report.
  • This field may be represented by a single bit. For example, when this bit is 1, it means that the RACH partition report is requested and/or needs to be reported; and when this bit is 0, it means that the RACH partition report is not requested and/or needs not to be reported; alternatively, when this bit is 0, it means that the RACH partition report is requested and/or needs to be reported, and when this bit is 1, it means that the RACH partition report is not requested and/or needs not to be reported.
  • One embodiment of the present disclosure proposes a method for supporting network self-optimization, which may include that a first entity transmits fifth information including SDT configuration information and/or RACH partition configuration information to a second entity to provide reference information for the second entity to perform SDT and/or RACH partition configuration to avoid resource configuration collision, etc., or the second entity may transmit the received SDT configuration information and/or RACH partition configuration information to other entities to provide reference information for the other entities to perform SDT and/or RACH partition configuration to avoid resource configuration collision, etc.
  • the fifth information may be included in one or more of: an XN SETUP REQUEST message or an XN SETUP RESPONSE message of Xn; an ENB CONFIGURATION UPDATE message or an ENB CONFIGURATION UPDATE ACKNOWLEDGE message or an EN-DC CONFIGURATION UPDATE message or an EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message of X2; an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message of Xn; a RESET REQUEST message of X2 or Xn; a MOBILITY CHANGE REQUEST message of X2; a F1 SETUP REQUEST message or F1 SETUP RESPONSE message or GNB-DU CONFIGURATION UPDATE message or GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or GNB-CU CONFIG
  • the fifth information may include one or more of the following fields or related information:
  • Node identification it is used to identify a node corresponding to the configuration information.
  • ⁇ Cell identification it is used to identify a cell corresponding to the configuration information.
  • SDT configuration information for a random access it is used to indicate SDT configuration information for a random access.
  • This information may include one or more of:
  • An acceptable value and/or a range of the acceptable value of the SDT configuration information for a random access it is used to indicate an acceptable value and/or a range of the acceptable value of the SDT configuration information for a random access.
  • the range of the acceptable value may include, for example, a maximum value and/or a minimum value.
  • This field may be an acceptable value and/or a range of the acceptable value of one or more of the following information:
  • a RACH partition configuration it is used to indicate the RACH partition configuration applied when performing the random access.
  • the configuration may include one or more of:
  • a feature combination it is used to indicate features the configuration is applicable to.
  • the features may include one or more of: RedCap, SDT (or smallData), slice (or slice group), Coverage Enhancement, etc.
  • startPreambleForThisPartition A start preamble for this partition (startPreambleForThisPartition)
  • the uplink resource may be a Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • Feature-specific parameters it includes one or more of: a signal quality threshold corresponding to a Synchronization Signal and PBCH (physical broadcast channel) block (SSB) (for example, it may be rsrp-ThresholdSSB), a signal quality threshold corresponding to a MSG3 (for example, it may be rsrp-ThresholdMsg3), a message power offset corresponding to GroupB (for example, it may be messagePowerOffsetGroupB), a size of random access GroupA (for example, it may be ra-SizeGroupA), and a preamble delta (deltaPreamble).
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • An acceptable value and/or a range of the acceptable value of a RACH partition configuration it is used to indicate the acceptable value and/or the range of the acceptable value of the RACH partition configuration information.
  • the range of the acceptable value may include, for example, a maximum value and/or a minimum value.
  • This field may be an acceptable value and/or a range of the acceptable value of one or more of the following information:
  • a feature combination it is used to indicate features the configuration is applicable to.
  • the features may include one or more of: RedCap, SDT (or smallData), slice (or slice group), Coverage Enhancement, etc.
  • startPreambleForThisPartition A start preamble for this partition (startPreambleForThisPartition)
  • the uplink resource may be a Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • Feature-specific parameters a signal quality threshold corresponding to a Synchronization Signal and PBCH (physical broadcast channel) block (SSB) (for example, it may be rsrp-ThresholdSSB), a signal quality threshold corresponding to a MSG3 (for example, it may be rsrp-ThresholdMsg3), a message power offset corresponding to GroupB (for example, it may be messagePowerOffsetGroupB), a size of random access GroupA (for example, it may be ra-SizeGroupA), and a preamble delta (deltaPreamble).
  • the signal quality may be RSRP, RSRQ, SINR, RSSI, etc.
  • the second entity may transmit fifth information of the second entity (for example, including SDT configuration information and/or RACH partition configuration information associated with the second entity) to the first entity according to its own situation, in order to provide reference information for the configuration of SDT and/or RACH partition of the first entity, or the first entity may transmit the received SDT configuration information and/or RACH partition configuration information to other entities to provide reference information for the configuration of SDT and/or RACH partition of other entities.
  • fifth information of the second entity for example, including SDT configuration information and/or RACH partition configuration information associated with the second entity
  • the first entity may transmit the received SDT configuration information and/or RACH partition configuration information to other entities to provide reference information for the configuration of SDT and/or RACH partition of other entities.
  • the methods performed by the first entity and/or the second entity in the wireless communication system according to embodiments of the present disclosure may be used for network self-optimization decision.
  • the network self-optimization decision mentioned in the present disclosure may include one or more of network energy saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration updating, etc.
  • results and reports in the present disclosure may refer to each other.
  • FIG. 5 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 5 shows a process of exchanging SDT information and/or RACH partition random access information between two entities, so that a second entity may obtain SDT information and/or RACH partition random access information and make a self-optimization decision and/or update configurations, etc.
  • the first entity may be a UE
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the first entity may be an AMF or SMF or MME
  • the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB
  • the second entity may be an AMF or SMF or MME.
  • Operation 501 the first entity reports SDT information and/or RACH partition random access information to the second entity.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • Operation 502 the second entity makes a self-optimization decision and/or updates configurations and the like based on the received SDT information and/or RACH partition random access information.
  • FIG. 6 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 6 shows a process of exchanging SDT information and/or RACH partition random access information between two entities, so that a second entity may obtain SDT information and/or RACH partition random access information and make a self-optimization decision and/or update configurations, etc.
  • the first entity may be a UE
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the first entity may be an AMF or SMF or MME
  • the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB
  • the second entity may be an AMF or SMF or MME.
  • Operation 601 the second entity transmits a request for SDT information and/or RACH partition random access information to the first entity.
  • the request for the SDT information and/or the RACH partition random access information may be the aforementioned fourth information.
  • Operation 602 the first entity reports SDT information and/or RACH partition random access information to the second entity.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • Operation 603 the second entity makes a self-optimization decision and/or updates configurations and the like based on the received SDT information and/or RACH partition random access information.
  • FIG. 7 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 7 shows a process of exchanging SDT information and/or RACH partition random access information between two entities, so that a second entity may obtain SDT information and/or RACH partition random access information and make a self-optimization decision and/or update configurations, etc.
  • the first entity may be a UE
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the first entity may be an AMF or SMF or MME
  • the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB
  • the second entity may be an AMF or SMF or MME.
  • Operation 701 the first entity transmits information indicating that SDT information is available and/or RACH partition random access information is available to a second entity, so as to inform the second entity that the first entity has the SDT information and/or the RACH partition random access information.
  • the information indicating that the SDT information is available and/or the RACH partition random access information is available may be the aforementioned third information.
  • Operation 702 the second entity transmits a request for SDT information and/or RACH partition random access information to the first entity.
  • the request for the SDT information and/or the RACH partition random access information may be the aforementioned fourth information.
  • Operation 703 the first entity reports SDT information and/or RACH partition random access information to the second entity.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • Operation 704 the second entity makes a self-optimization decision and/or updates configurations and the like based on the received SDT information and/or RACH partition random access information.
  • FIG. 8 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 8 shows a process of exchanging SDT information and/or RACH partition random access information among a user, a node and a last serving node, so that the last serving node may obtain SDT information and/or RACH partition random access information, and may make configuration adjustment and make a self-optimization decision.
  • a node may be a base station, which may include a central unit (CU) and a distributed unit (DU), and the CU may further include a user plane (UP) and a control plane (CP).
  • CU central unit
  • DU distributed unit
  • CP control plane
  • Operation 801 the UE performs a random access process with the last serving node (which may also be the CU of the last serving node and/or the DU of the last serving node).
  • the last serving node which may also be the CU of the last serving node and/or the DU of the last serving node.
  • Operation 802 the UE performs a RRC setup process and/or RRC re-establishment process with the node (or the CU of the node).
  • Operation 803 the UE transmits information indicating that SDT information is available and/or RACH partition random access information is available to the node (which may also be the CU of the node), so as to inform the node (which may also be the CU of the node) that SDT information and/or RACH partition random access information are available at the UE.
  • the information indicating that the SDT information is available and/or the RACH partition random access information is available may be the aforementioned third information.
  • the information indicating that the SDT information is available and/or the RACH partition random access information is available may be transmitted through a RRC Setup Complete (RRCSetupComplete) message.
  • RRCSetupComplete RRC Setup Complete
  • Operation 804 the node (which may also be the CU of the node) transmits a request for SDT information and/or RACH partition random access information to the UE to request the UE to report the SDT information and/or the RACH partition random access information.
  • the request for the SDT information and/or the RACH partition random access information may be the aforementioned fourth information.
  • the request for the SDT information and/or the RACH partition random access information may be transmitted through a UE Information Request (UEInformationRequest) message.
  • UEInformationRequest UE Information Request
  • Operation 805 the UE transmits SDT information and/or RACH partition random access information to the node (or the CU of the node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may be transmitted through a UE Information Response (UEInformationResponse) message.
  • UEInformationResponse UE Information Response
  • Operation 806 the node (which may also be the CU of the node) transmits SDT information and/or RACH partition random access information to the last serving node (which may also be the CU of the last serving node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in operation 805.
  • the SDT information and/or the RACH partition random access information may be transmitted through a Failure Indication and/or a Handover Report and/or an Access And Mobility Indication message.
  • Operation 807 the CU of the last serving node transmits SDT information and/or RACH partition random access information to the DU of the last serving node.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in operation 806.
  • the SDT information and/or the RACH partition random access information may be transmitted through an Access And Mobility Indication message.
  • the last serving node (which may also be the CU of the last serving node or the DU of the last serving node) may make a self-optimizing decision and/or update configurations based on the received SDT information and/or RACH partition random access information.
  • FIG. 9 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 9 shows a process of exchanging SDT information and/or RACH partition random access information among a UE, a master node and a secondary node in a case of dual-connectivity in which the UE performs a random access with the secondary node, so that the secondary node may obtain SDT information and/or RACH partition random access information, in order for the secondary node to make configuration adjustment and make a self-optimization decision.
  • Operation 901 the UE performs a random access process with a secondary node (which may also be the CU of the secondary node and/or the DU of the secondary node).
  • a secondary node which may also be the CU of the secondary node and/or the DU of the secondary node.
  • Operation 902 the UE transmits SDT information and/or RACH partition random access information to the master node (which may also be the CU of the master node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may be transmitted through an SCG Failure Information (SCGFailureInformation) message.
  • SCGFailureInformation SCG Failure Information
  • the master node (which may also be the CU of the master node) transmits SDT information and/or RACH partition random access information to the secondary node (which may also be the CU of the secondary node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in step 902.
  • the SDT information and/or RACH partition random access information may be transmitted through a SgNB Modification Request and/or an SCG Failure Information Report message.
  • Operation 904 the CU of the secondary node transmits SDT information and/or RACH partition random access information to the DU of the secondary node.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in step 903.
  • the SDT information and/or the RACH partition random access information may be transmitted through an Access And Mobility Indication message.
  • the master node (which may also be the CU of the master node) and the secondary node (which may also be the CU of the secondary node or the DU of the secondary node) may make a self-optimization decision and/or update configurations based on the received SDT information and/or RACH partition random access information.
  • FIG. 10 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure.
  • FIG. 10 shows a process of exchanging SDT information and/or RACH partition random access information among a UE, a master node and a secondary node in a case of dual-connectivity in which the UE performs a random access with the master node, so that the master node may obtain SDT information and/or RACH partition random access information, in order for the master node to make configuration adjustment and make a self-optimization decision.
  • Operation 1001 the UE performs a random access process with the master node (which may also be the CU of the master node and/or the DU of the master node).
  • the master node which may also be the CU of the master node and/or the DU of the master node.
  • Operation 1002 the UE transmits SDT information and/or RACH partition random access information to the secondary node (which may also be the CU of the secondary node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may be transmitted through a Master Cell Group Failure Information (MCGFailureInformation) message.
  • MCGFailureInformation Master Cell Group Failure Information
  • the secondary node (which may also be the CU of the secondary node) transmits SDT information and/or RACH partition random access information to the master node (which may also be the CU of the master node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in step 1002.
  • the SDT information and/or the RACH partition random access information may be transmitted through a RRC Transfer message.
  • Operation 1004 the CU of the master node transmits SDT information and/or RACH partition random access information to the DU of the master node.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in operation 1003.
  • the SDT information and/or the RACH partition random access information may be transmitted through an Access And Mobility Indication message.
  • the master node (which may be the CU of the master node or the DU of the master node) may make a self-optimization decision and/or update configurations based on the received SDT information and/or RACH partition random access information.
  • FIG. 11 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 11 shows a process of exchanging SDT information and/or RACH partition random access information among a user, a node, a last serving node and an AMF, so that the last serving node may obtain SDT information and/or RACH partition random access information, and make configuration adjustment and make a self-optimization decision.
  • Operation 1101 the UE performs a random access process with the last serving node (which may also be the CU of the last serving node and/or the DU of the last serving node).
  • the last serving node which may also be the CU of the last serving node and/or the DU of the last serving node.
  • Operation 1102 the UE performs a RRC setup process and/or RRC re-establishment process with the node (or the CU of the node).
  • Operation 1103 the UE transmits information indicating that SDT information is available and/or RACH partition random access information is available to the node (which may also be the CU of the node), so as to inform the node (which may also be the CU of the node) that the SDT information and/or the RACH partition random access information are available at the UE.
  • the information indicating that the SDT information is available and/or the RACH partition random access information is available may be the aforementioned third information.
  • the information indicating that the SDT information and/or the RACH partition random access information are available may be transmitted through a RRC Setup Complete (RRCSetupComplete) message.
  • RRCSetupComplete RRC Setup Complete
  • Operation 1104 the node (which may also be the CU of the node) transmits a request for SDT information and/or RACH partition random access information to the UE to request the UE to report the SDT information and/or the RACH partition random access information.
  • the request for the SDT information and/or the RACH partition random access information may be the aforementioned fourth information.
  • the request for the SDT information and/or the RACH partition random access information may be transmitted through a UE Information Request (UEInformationRequest) message.
  • UEInformationRequest UE Information Request
  • Operation 1105 the UE transmits SDT information and/or RACH partition random access information to the node (or the CU of the node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may be transmitted through a UE Information Response (UEInformationResponse) message.
  • UEInformationResponse UE Information Response
  • Operation 1106 the node (or the CU of the node) transmits SDT information and/or RACH partition random access information to the AMF.
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in step 1105.
  • the SDT information and/or the RACH partition random access information may be transmitted through an Uplink RAN Configuration Transfer message.
  • Operation 1107 the AMF transmits SDT information and/or RACH partition random access information to the last serving node (or the CU of the last serving node).
  • the SDT information may be the aforementioned first information.
  • the RACH partition random access information may be the aforementioned second information.
  • the SDT information and/or the RACH partition random access information may include all information and/or part of information in operation 1106.
  • the SDT information and/or the RACH partition random access information may be transmitted through a Downlink RAN Configuration Transfer message.
  • the CU of the last serving node may also transmit all and/or part of the received SDT information and/or RACH partition random access information to the DU of the last serving node.
  • the last serving node (which may also be the CU of the secondary node or the DU of the secondary node) may make a self-optimization decision and/or update configurations based on the received SDT information and/or RACH partition random access information.
  • FIG. 12 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 12 shows a process of exchanging SDT configuration information and/or RACH partition random access configuration information (that is, the above-mentioned SDT configuration information and/or RACH partition configuration information) between two entities, so that a second entity may obtain the SDT configuration information and/or the RACH partition random access configuration information to update configurations, etc.
  • SDT configuration information and/or RACH partition random access configuration information that is, the above-mentioned SDT configuration information and/or RACH partition configuration information
  • the first entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the first entity may be an AMF or SMF or MME
  • the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB
  • the second entity may be an AMF or SMF or MME.
  • Operation 1201 the first entity transmits SDT configuration information and/or RACH partition random access configuration information to the second entity.
  • the SDT configuration information and/or the RACH partition random access configuration information may be the aforementioned fifth information.
  • Operation 1202 the second entity updates configurations and the like based on the received SDT configuration information and/or RACH partition random access configuration information.
  • FIG. 13 illustrates a schematic diagram of a method for supporting network self-optimization according to embodiments of the present disclosure. Specifically, FIG. 13 shows a process of exchanging SDT configuration information and/or RACH partition random access configuration information between two entities, so that the first entity may negotiate the SDT configuration information and/or the RACH partition random access configuration information with the second entity, and the first entity may update configurations, etc.
  • the first entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the second entity may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB
  • the first entity may be an AMF or SMF or MME
  • the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB.
  • the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB
  • the second entity may be an AMF or SMF or MME.
  • Operation 1301 the first entity transmits SDT configuration information and/or RACH partition random access configuration information to the second entity.
  • the SDT configuration information and/or the RACH partition random access configuration information may be the aforementioned fifth information.
  • Operation 1302 the second entity transmits SDT configuration information and/or RACH partition random access configuration information associated with the second entity to the first entity.
  • the SDT configuration information and/or the RACH partition random access configuration information may also be the aforementioned fifth information.
  • Operation 1303 the first entity updates configurations and the like based on the SDT configuration information and/or the RACH partition random access configuration information negotiated in operation 1301 and/or operation 1302.
  • FIG. 14 illustrates a schematic diagram of a first entity 1400 according to embodiments of the present disclosure.
  • the first entity (or a first entity device) 1400 may include a transceiver 1410 and a processor 1420.
  • the transceiver 1410 may be configured to transmit and receive signals.
  • the processor 1420 may be coupled to the transceiver 1410 and may be configured to (e.g., control the transceiver 1410 to) perform methods performed by a first entity according to embodiments of the present disclosure.
  • FIG. 15 illustrates a schematic diagram of a second entity 1500 according to embodiments of the present disclosure.
  • the second entity (or a second entity device) 1500 may include a transceiver 1510 and a processor 1520.
  • the transceiver 1510 may be configured to transmit and receive signals.
  • the processor 1520 may be coupled to the transceiver 1510 and may be configured to (e.g., control the transceiver 1510 to) perform methods performed by a second entity according to embodiments of the present disclosure.
  • a processor may also be called a controller.
  • FIG. 16 illustrates a block diagram of a terminal (or a user equipment (UE)), according to embodiments of the present disclosure.
  • FIG. 16 corresponds to the example of the UE of FIG. 101.
  • the UE may include a transceiver 1610, a memory 1620, and a processor 1630.
  • the transceiver 1610, the memory 1620, and the processor 1630 of the UE may operate according to a communication method of the UE described above.
  • the components of the UE are not limited thereto.
  • the UE may include more or fewer components than those described above.
  • the processor 1630, the transceiver 1610, and the memory 1620 may be implemented as a single chip.
  • the processor 1630 may include at least one processor.
  • the transceiver 1610 collectively refers to a UE receiver and a UE transmitter, and may transmit/receive a signal to/from a base station or a network entity.
  • the signal transmitted or received to or from the base station or a network entity may include control information and data.
  • the transceiver 1610 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal.
  • the transceiver 1610 may receive and output, to the processor 1630, a signal through a wireless channel, and transmit a signal output from the processor 1630 through the wireless channel.
  • the memory 1620 may store a program and data required for operations of the UE. Also, the memory 1620 may store control information or data included in a signal obtained by the UE.
  • the memory 1620 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.
  • the processor 1630 may control a series of processes such that the UE operates as described above.
  • the transceiver 1610 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 1630 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.
  • FIG. 17 illustrates a block diagram of a base station, according to embodiments of the present disclosure.
  • FIG. 17 corresponds to the example of the gNB of FIG. 1.
  • the base station may include a transceiver 1710, a memory 1720, and a processor 1730.
  • the transceiver 1710, the memory 1720, and the processor 1730 of the base station may operate according to a communication method of the base station described above.
  • the components of the base station are not limited thereto.
  • the base station may include more or fewer components than those described above.
  • the processor 1730, the transceiver 1710, and the memory 1720 may be implemented as a single chip.
  • the processor 1730 may include at least one processor.
  • the transceiver 1710 collectively refers to a base station receiver and a base station transmitter, and may transmit/receive a signal to/from a terminal or a network entity.
  • the signal transmitted or received to or from the terminal or a network entity may include control information and data.
  • the transceiver 1710 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal.
  • the transceiver 1710 may receive and output, to the processor V30, a signal through a wireless channel, and transmit a signal output from the processor 1730 through the wireless channel.
  • the memory 1720 may store a program and data required for operations of the base station. Also, the memory 1720 may store control information or data included in a signal obtained by the base station.
  • the memory 1720 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.
  • the processor 1730 may control a series of processes such that the base station operates as described above.
  • the transceiver 1710 may receive a data signal including a control signal transmitted by the terminal, and the processor 1730 may determine a result of receiving the control signal and the data signal transmitted by the terminal.
  • Embodiments of the present disclosure also provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, implement any method according to embodiments of the present disclosure.
  • a computer-readable recording medium is any data storage device that can store data readable by a computer system.
  • Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disk read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), etc.
  • Computer-readable recording media can be distributed by computer systems connected via a network, and thus computer-readable codes can be stored and executed in a distributed manner.
  • functional programs, codes and code segments for implementing various embodiments of the present disclosure can be easily explained by those skilled in the art to which the embodiments of the present disclosure are applied.
  • Non-transitory computer-readable recording media include magnetic storage media (such as ROM, floppy disk, hard disk, etc.) and optical recording media (such as CD-ROM, digital video disk (DVD), etc.).
  • Non-transitory computer-readable recording media may also be distributed on computer systems coupled to a network, so that computer-readable codes are stored and executed in a distributed manner. The medium can be read by a computer, stored in a memory, and executed by a processor.
  • Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transitory computer-readable recording medium suitable for storing program (s) with instructions for implementing embodiments of the present disclosure.
  • the present disclosure may be realized by a program with code for concretely implementing the apparatus and method described in the claims, which is stored in a machine (or computer)-readable storage medium.
  • the program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the present disclosure suitably includes its equivalents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2023/011081 2022-07-29 2023-07-28 Method and apparatus for entity in a wireless communication system WO2024025395A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210907688.6 2022-07-29
CN202210907688 2022-07-29
CN202310787780.8 2023-06-29
CN202310787780.8A CN117479339A (zh) 2022-07-29 2023-06-29 无线通信系统中的实体及其执行的方法

Publications (1)

Publication Number Publication Date
WO2024025395A1 true WO2024025395A1 (en) 2024-02-01

Family

ID=89622728

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/011081 WO2024025395A1 (en) 2022-07-29 2023-07-28 Method and apparatus for entity in a wireless communication system

Country Status (3)

Country Link
KR (1) KR20240016935A (ko)
CN (1) CN117479339A (ko)
WO (1) WO2024025395A1 (ko)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200112996A1 (en) * 2018-10-08 2020-04-09 Idac Holdings, Inc. Prach enhancement methods in nr-u
US20200236704A1 (en) * 2019-01-17 2020-07-23 Qualcomm Incorporated Random access channel (rach) message partitioning for beam correspondence indication
WO2022036339A2 (en) * 2020-12-07 2022-02-17 Futurewei Technologies, Inc. Method and apparatus for identification of redcap ues

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200112996A1 (en) * 2018-10-08 2020-04-09 Idac Holdings, Inc. Prach enhancement methods in nr-u
US20200236704A1 (en) * 2019-01-17 2020-07-23 Qualcomm Incorporated Random access channel (rach) message partitioning for beam correspondence indication
WO2022036339A2 (en) * 2020-12-07 2022-02-17 Futurewei Technologies, Inc. Method and apparatus for identification of redcap ues

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.321, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V17.1.0, 20 July 2022 (2022-07-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 241, XP052183760 *
LG ELECTRONICS: "Discussion on RO sharing cases for common RACH configuration", 3GPP DRAFT; R2-2203063, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20220221 - 20220303, 14 February 2022 (2022-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052110897 *

Also Published As

Publication number Publication date
CN117479339A (zh) 2024-01-30
KR20240016935A (ko) 2024-02-06

Similar Documents

Publication Publication Date Title
WO2023191478A1 (en) Method and device for supporting movement of unmanned aerial vehicle
WO2023003438A1 (en) Method and apparatus for providing configuration information related to paging in wireless communication system
WO2022225315A1 (en) Method and device for notifying mbs state
WO2024025395A1 (en) Method and apparatus for entity in a wireless communication system
WO2022103137A1 (en) Method and apparatus for random access in wireless communication system
WO2024025359A1 (en) Method and apparatus for minimization of drive tests measurement enhancement
WO2023140701A1 (en) Method performed by communication node and communication node in communication system
WO2024029985A1 (en) Method and device for information transmission
WO2024096635A1 (en) Scheme of mobility and method and apparatus for the same
WO2024096634A1 (en) Method and apparatus supporting self-configuration and self-optimization
WO2024029892A1 (en) Method and apparatus for supporting self-configuration and self-optimization
WO2024071768A1 (en) Node, user equipment in wireless communication system and method performed by the same
WO2024029932A1 (en) Method and device for handover optimization
WO2024030005A1 (en) Method and apparatus for data transmission
WO2024025349A1 (en) Method and apparatus for supporting self-configuration and self-optimization
WO2024029749A1 (en) Communication method in a communication system
WO2023140521A1 (en) Method and apparatus for node movement and corresponding node
WO2023146210A1 (en) A method for adding nodes
WO2024014787A1 (en) Method and apparatus for conditional handover in wireless communication system
WO2024096601A1 (en) Device and method performed by the device in a wireless communication
WO2023146374A1 (en) Method and apparatus for mobility enhancement in a wireless communication system
WO2024096620A1 (en) Methods performed by network node and node, and node device
WO2024025282A1 (en) Apparatus and method for supporting communication service continuity in wireless communication system
WO2023177028A1 (en) Methods and systems for handling trp and beam change mechanism
WO2024029884A1 (en) Method and apparatus for confirming f1 termination donor node

Legal Events

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

Ref document number: 23847051

Country of ref document: EP

Kind code of ref document: A1