CN117479339A

CN117479339A - Entities in wireless communication systems and methods for their execution

Info

Publication number: CN117479339A
Application number: CN202310787780.8A
Authority: CN
Inventors: 王妍茹; 许丽香; 王弘; 汪巍崴
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-07-29
Filing date: 2023-06-29
Publication date: 2024-01-30
Also published as: EP4548698A1; WO2024025395A1; EP4548698A4; KR20240016935A

Abstract

The present disclosure provides an entity in a wireless communication system and a method for executing the same. A method performed by a first entity in a wireless communication system according to an embodiment of the present disclosure may include: sending to the second entity first information including SDT information based on small data packet transmission SDT configuration information, including SDT information based on random transmission. At least one of the second information of the RACH split random access information of the access channel RACH split configuration for random access, and the fifth information including SDT configuration information and/or RACH split configuration information, wherein the at least one Information is associated with at least one of the first entity and an entity other than the first entity. The method provided by the present disclosure and executed by the first entity and/or the second entity in the wireless communication system enables self-optimization decisions or configuration updates to be made on the network side by exchanging information related to random access and the like between the entities. .

Description

Entity in wireless communication system and method for performing the same

Technical Field

The present disclosure relates to the field of wireless communication technology, and more particularly, to entities in a wireless communication system and methods performed thereby.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeds 50 billion and continues to grow rapidly. As smartphones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) become increasingly popular among consumers and businesses, the demand for wireless data services is rapidly growing. To meet the high-speed growth of mobile data services and support new applications and deployments, it is important to improve the efficiency and coverage of the wireless interface.

In the random access procedure, a small packet may be carried in message a (MSGA) or message 3 (MSG 3) for transmission.

The random access resources may be partitioned according to different characteristics (e.g., reduced capability (Reduced Capability, redCap), slicing, small packet transmissions, coverage enhancement, etc.).

Disclosure of Invention

Embodiments of the present disclosure provide a method performed by a first entity in a wireless communication system, comprising: transmitting, to a second entity, at least one of first information including SDT information for SDT based on small packet transfer SDT configuration information, second information including RACH segmentation random access information for random access based on a random access channel RACH segmentation configuration, and fifth information including SDT configuration information and/or RACH segmentation configuration information, wherein the at least one information is associated with at least one of the first entity and other entities than the first entity.

Embodiments of the present disclosure provide a method performed by a second entity in a wireless communication system, comprising: at least one of first information including SDT information for SDT based on small packet transfer SDT configuration information, second information including RACH segmentation random access information for random access based on a random access channel RACH segmentation configuration, and fifth information including SDT configuration information and/or RACH segmentation configuration information is received from a first entity, wherein the at least one information is associated with at least one of the first entity and other entities than the first entity.

Embodiments of the present disclosure provide a first entity apparatus in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled with the transceiver and configured to perform a method performed by a first entity in a wireless communication system according to an embodiment of the disclosure.

Embodiments of the present disclosure provide a second entity apparatus in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled with the transceiver and configured to perform a method performed by a second entity in a wireless communication system according to an embodiment of the disclosure.

Embodiments of the present disclosure provide a computer readable medium having stored thereon computer readable instructions which, when executed by a processor, are for implementing a method performed by a first entity and/or a second entity in a wireless communication system according to embodiments of the present disclosure.

The method performed by the first entity and/or the second entity in the wireless communication system enables the self-optimization decision making or configuration updating at the network side by interacting information related to random access and the like between the entities.

Drawings

The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

FIG. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE);

FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

fig. 3 illustrates a flow chart of a method 300 performed by a first entity in a wireless communication system in accordance with an embodiment of the present disclosure;

fig. 4 illustrates a flow chart of a method 400 performed by a second entity in a wireless communication system in accordance with an embodiment of the present disclosure;

FIG. 5 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 6 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 7 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 8 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 9 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 10 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 11 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 12 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 13 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 14 shows a schematic diagram of a first entity 1400 in accordance with an embodiment of the present disclosure; and is also provided with

Fig. 15 shows a schematic diagram of a second entity 1500 according to embodiments of the present disclosure.

Detailed Description

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The description includes various specific details to facilitate understanding but should be considered exemplary only. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and phrases used in the following specification and claims are not limited to their dictionary meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more such surfaces.

The terms "comprises" or "comprising" may refer to the presence of a corresponding disclosed function, operation or component that may be used in various embodiments of the present disclosure, rather than to the presence of one or more additional functions, operations or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the existence of one or more other features, numbers, steps, operations, constituent elements, components, or combinations thereof.

The term "or" as used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "a or B" may include a, may include B, or may include both a and B.

Unless defined differently, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure pertains. The general terms as defined in the dictionary are to be construed to have meanings consistent with the context in the relevant technical field, and should not be interpreted in an idealized or overly formal manner unless expressly so defined in the present disclosure.

According to an embodiment of the present disclosure, the method performed by the first entity in the wireless communication system further comprises: fourth information including a request for the SDT information and/or the RACH split random access information is received from the second entity, wherein the first information and/or the second information is transmitted by the first entity to the second entity based on the fourth information.

According to an embodiment of the present disclosure, the method performed by the first entity in the wireless communication system further comprises: and transmitting third information for indicating that the SDT information is available and/or the RACH segmentation random access information is available to the second entity, wherein the fourth information is transmitted to the second entity by the first entity based on the third information.

According to an embodiment of the present disclosure, the method performed by the first entity in the wireless communication system further comprises: and receiving SDT configuration information and/or RACH segmentation configuration information associated with the second entity from the second entity, wherein at least a portion of the SDT configuration information and/or RACH segmentation configuration information associated with the second entity is determined by the second entity based on the fifth information.

According to an embodiment of the present disclosure, the at least one 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 comprises at least one of network energy saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration update.

According to an embodiment of the present disclosure, the first information includes one or more of the following: the user equipment identifier, the node identifier, the cell identifier, the random access purpose is an indication of the SDT, random access SDT configuration information, random access to information reporting time, SDT starting to information reporting time, SDT radio link failure to information reporting time, SDT interruption to information reporting time, SDT failure to information reporting time, signal quality at the time of SDT failure, residual data quantity after SDT failure, signal quality at the time of random access, data quantity at the time of SDT starting, data quantity related information in the SDT transmission process, data quantity sent by the SDT, residual data quantity after SDT transmission, time from the start of the SDT to the end of the SDT, time from the start of the SDT to the wireless link failure, SDT timer state at the end of the SDT, SDT timer state at the time of the wireless link failure, SDT end reason and SDT failure reason.

According to an embodiment of the present disclosure, the data volume related information in the SDT transmission process includes one or more of the following: the data amount reached in the SDT transmission process, the maximum data amount in the SDT transmission process, the minimum data amount in the SDT transmission process and the average data amount in the SDT transmission process.

According to an embodiment of the present disclosure, the second information includes one or more of the following: user equipment identification, node identification, cell identification, feature priority, RACH segmentation configuration, time of random access to information reporting, available resources at random access, time of random access failure to information reporting, time of random access failure, features corresponding to available resources at random access, signal quality corresponding to a synchronizing signal and a physical broadcast channel block SSB, signal quality corresponding to an MSG3, and information of attempting random access.

According to an embodiment of the present disclosure, the fifth information includes one or more of the following: node identification, cell identification, random access SDT configuration information, acceptable values and/or acceptable ranges of values for random access SDT configuration information, RACH segmentation configuration, acceptable values and/or acceptable ranges of values for RACH segmentation configuration.

According to an embodiment of the present disclosure, the fourth information includes one or more of the following: SDT information request, SDT report request, RACH segmentation random access information request, RACH segmentation report request.

According to an embodiment of the present disclosure, the third information includes one or more of the following: SDT information available, SDT reports available, RACH segmentation random access information available, RACH segmentation reports available.

According to an embodiment of the present disclosure, the method performed by the second entity in the wireless communication system further comprises: and transmitting fourth information including a request for the SDT information and/or the RACH split random access information to the first entity, wherein the first information and/or the second information is transmitted to the second entity by the first entity based on the fourth information.

According to an embodiment of the present disclosure, the method performed by the second entity in the wireless communication system further comprises: third information indicating that the SDT information is available and/or the RACH split random access information is available is received from the first entity, wherein the fourth information is transmitted by the first entity to the second entity based on the third information.

According to an embodiment of the present disclosure, the method performed by the second entity in the wireless communication system further comprises: and transmitting SDT configuration information and/or RACH segmentation configuration information associated with the second entity to the first entity, wherein at least a portion of the SDT configuration information and/or RACH segmentation configuration information associated with the second entity is determined by the second entity based on the fifth information.

Figures 1 through 15, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Fig. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE). A User Equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network including macro base stations (enodebs/nodebs) providing an access radio network interface for UEs. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. Serving Gateway (SGW) 104 mainly provides the functions of the user plane, and MME 103 and SGW 104 may be in the same physical entity. The packet data network gateway (PGW) 105 is responsible for charging, lawful interception, etc. functions, and may also be in the same physical entity as the SGW 104. A Policy and Charging Rules Function (PCRF) 106 provides quality of service (QoS) policies and charging criteria. The general packet radio service support node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides a route for the transmission of data. A Home Subscriber Server (HSS) 109 is a home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, 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 this disclosure.

A User Equipment (UE) 201 is a terminal device for receiving data. The next generation radio access network (NG-RAN) 202 is a radio access network including base stations (gnbs or enbs connected to a 5G core network 5GC, also called NG-gnbs) providing access radio network interfaces for UEs. An access control and mobility management function (AMF) 203 is responsible for managing the mobility context of the UE, and security information. The User Plane Function (UPF) 204 mainly provides the functions of the user plane. The session management function entity SMF205 is responsible for session management. The Data Network (DN) 206 contains services such as operators, access to the internet, and third party traffic, among others.

The entities and/or nodes described in this disclosure may include: a gNB, gNB centralized Unit (gNB-CU), gNB distribution Unit (gNB Distributed Unit, gNB-DU), gNB centralized Unit Control Plane (gNB CU-CP), gNB centralized Unit User Plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, access and mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), mobility management entity (Mobility Management Entity, MME) and other network entities or network logic units.

The signal strength and/or signal quality described in this disclosure may be a received signal strength indication (Received Signal Strength Indicator, RSSI), a reference signal received power (Reference Signal Receiving Power, RSRP), a reference signal received quality (Reference Signal Receiving Quality, RSRQ), a signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR), and the like.

Features described in this disclosure may include one or more of the following: redCap, SDT (also small data), slice (also slice group), coverage enhancement (Coverage Enhancement), etc.

The method and the device solve the problems that SDT and RACH segmentation related information cannot be provided for network self-optimization in the prior art, so that SDT and/or RACH segmentation related configuration cannot be optimized.

Next, fig. 3 illustrates a flow chart of a method 300 performed by a first entity in a wireless communication system in accordance with an embodiment of the disclosure.

As shown in fig. 3, in step S301, a method 300 performed by a first entity in a wireless communication system according to an embodiment of the present disclosure may include: the first entity transmits at least one of first information including SDT information for SDT based on small packet transfer SDT configuration information, second information including RACH segmentation random access information for random access based on a random access channel RACH segmentation configuration, and fifth information including SDT configuration information and/or RACH segmentation configuration information to the second entity. In some embodiments, the at least one piece of information may be associated with at least one of the first entity and any other entity other than the first entity. For example, taking the fifth information as an example, SDT configuration information and/or RACH segmentation configuration information included in the fifth information sent by the first entity to the second entity may be SDT configuration information and/or RACH segmentation configuration information of the first entity itself, or SDT configuration information and/or RACH segmentation configuration information of any other entity collected or acquired by the first entity in any manner. The other information mentioned above has the same meaning and is not described here again. Further, the first entity, the second entity, and any other entity described herein may be any of the example entities listed above or newly introduced entities in the future, without limitation.

Additionally or alternatively, the method 300 may further comprise: the first entity receives fourth information comprising a request for SDT information and/or RACH split random access information from the second entity. In some embodiments, the first information and/or the second information described above may be sent to the second entity autonomously by the first entity or based on fourth information.

Additionally or alternatively, the method 300 may further comprise: the first entity sends third information to the second entity indicating that SDT information is available and/or RACH segmentation random access information is available. In some implementations, the fourth information may be sent to the second entity autonomously by the first entity or based on receiving the third information.

Additionally or alternatively, the method 300 may further comprise: the first entity receives SDT configuration information and/or RACH segmentation configuration information associated with the second entity from the second entity. In some implementations, some or all of the SDT configuration information and/or RACH segmentation configuration information associated with the second entity can be determined by the second entity based at least in part on fifth information received from the first entity. For example, the second entity may determine some or all of the SDT configuration information and/or RACH partition configuration information associated with the second entity based on its own conditions (e.g., its own capabilities and/or its existing configuration) and/or SDT configuration information and/or RACH partition configuration information associated with one of the first entity and/or any other entity included in the fifth information received from the first entity.

Fig. 4 illustrates a flow chart of a method 400 performed by a second entity in a wireless communication system in accordance with an embodiment of the present disclosure.

As shown in fig. 4, in step S401, a method 400 performed by a second entity in a wireless communication system according to an embodiment of the present disclosure may include: the second entity receives at least one of first information including SDT information for SDT based on small packet transfer SDT configuration information, second information including RACH segmentation random access information for random access based on a random access channel RACH segmentation configuration, and fifth information including SDT configuration information and/or RACH segmentation configuration information from the first entity. In some embodiments, the at least one piece of information may be associated with at least one of the first entity and any other entity other than the first entity. For example, taking the fifth information as an example, SDT configuration information and/or RACH segmentation configuration information included in the fifth information sent by the first entity to the second entity may be SDT configuration information and/or RACH segmentation configuration information of the first entity itself, or SDT configuration information and/or RACH segmentation configuration information of any other entity collected or acquired by the first entity in any manner. The other information mentioned above has the same meaning and is not described here again. Further, the first entity, the second entity, and any other entity described herein may be any one of the example entities listed above or newly introduced entities in the future, without limitation.

Additionally or alternatively, the method 400 may further comprise: the second entity sends fourth information comprising a request for SDT information and/or RACH split random access information to the first entity. In some embodiments, the first information and/or the second information described above may be sent to the second entity autonomously by the first entity or based on fourth information.

Additionally or alternatively, the method 400 may further comprise: the second entity receives third information from the first entity indicating that SDT information is available and/or RACH segmentation random access information is available. In some implementations, the fourth information may be sent to the second entity autonomously by the first entity or based on receiving the third information.

Additionally or alternatively, the method 400 may further comprise: the second entity sends SDT configuration information and/or RACH segmentation configuration information associated with the second entity to the first entity. In some implementations, the SDT configuration information and/or RACH segmentation configuration information associated with the second entity can be determined by the second entity based at least in part on fifth information received from the first entity. For example, the second entity may determine SDT configuration information and/or RACH partition configuration information associated with the second entity based on SDT configuration information and/or RACH partition configuration information associated with the first entity and/or one of any other entities included in the fifth information received from the first entity and/or a self-case (e.g., self-capabilities and/or an existing configuration of itself).

The various steps or operations included in the methods 300 and 400 according to embodiments of the present disclosure as described above may be performed individually or in any combination, collectively, and may be performed in any order, e.g., concurrently or in reverse order from that listed. In addition, the various steps or operations and various information described above will be further described below in connection with specific examples.

Methods performed by a first entity and/or a second entity in a wireless communication system according to embodiments of the present disclosure will be described in various aspects further in conjunction with specific examples. More generally, a method performed by a first entity and/or a second entity in a wireless communication system according to embodiments of the present disclosure may also be referred to as a method of supporting network self-optimization.

Example one

One aspect of the present disclosure proposes a method of supporting network self-optimization, which may include: the first entity sends first information containing SDT information for SDT based on small data packet transmission (Small Data Transmission, SDT) configuration to the second entity so that the second entity can judge whether the SDT configuration is suitable and/or update parameter configuration of the SDT based on the received information, and/or the second entity forwards the received information to other entities so that the other entities can judge whether the SDT configuration is suitable and/or update SDT related configuration, thereby preventing link interruption in the SDT process and improving the robustness and the effectiveness of the SDT. Here, the SDT may be a Random Access SDT (RA-SDT) or a Configured Grant SDT (CG-SDT).

In some embodiments, the first information may be contained in one or more of: user information response (ueinformation response) for radio resource control (Radio Resource Control, RRC), secondary cell group failure information (SCGFailureInformation), primary cell group failure information (MCGFailureInformation); a failure indication (FAILURE INDICATION) message for Xn, a HANDOVER REPORT (HANDOVER) message, an access and mobility indication (ACCESS AND MOBILITY INDICATION) message, a secondary node modification request (S-NODE MODIFICATION REQUEST) message, a secondary gNB modification request (SgNB MODIFICATION REQUEST) message, a secondary cell group failure information REPORT (SCG FAILURE INFORMATION REPORT) message, an RRC transfer (RRC TRANSFER) message; f1 access and mobility indication (ACCESS AND MOBILITY INDICATION) message; the uplink RAN configuration of NG forwards (UPLINK RAN CONFIGURATION TRANSFER) the message and the downlink RAN configuration forwards (DOWNLINK RAN CONFIGURATION TRANSFER) the message; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message. In some embodiments, the first information may be included in a report, where the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, or other report related to a radio connection. The report may also be a new report, e.g. 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).

In some implementations, the first information may include one or more of the following fields or related information:

UE identity: for identifying UEs for random access and/or SDT.

Node identification: and the node is used for identifying the node corresponding to the random access and/or SDT of the UE.

Cell identity: and the method is used for identifying the cell corresponding to the random access and/or SDT of the UE.

Indication of the purpose of random access as SDT: the purpose for identifying random access is SDT. This field may be included in the random access purpose (rapurpos).

Random access SDT configuration information: for representing SDT configuration information applied when making random access. The information may include one or more of the following: SDT corresponds to an RSRP Threshold (SDT-RSRP-Threshold), SDT corresponds to a logical channel status reporting delay timer (SDT-LogicalchannelSR-DelayTimer), SDT corresponds to a data volume Threshold (SDT-

Datavolemethreshold), SDT timer value (e.g., T319 a).

Time of random access to information reporting: for indicating the time from random access to the first information reporting. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time from start of SDT to reporting of information: for indicating the time from the start of SDT to the reporting of the first information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of SDT radio link failure to information reporting: for indicating the time from the failure of the SDT radio link to the reporting of the first information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of SDT interrupt to information reporting: for indicating the time from the SDT interrupt to the reporting of the information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of SDT failure to information reporting: for indicating time from failure of SDT to reporting of information

And (3) the room(s). In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Signal quality at SDT failure: for indicating the signal quality when SDT fails. The signal quality

The amount may be RSRP, RSRQ, SINR, RSSI, etc. The SDT failure may be a radio link failure.

The amount of data remaining after SDT failure: for indicating the number of unsent residues remaining after SDT failure

And (5) measuring the data. The SDT failure may be a radio link failure.

Signal quality at random access: for indicating the signal quality when random access is performed. The method comprises

The signal quality may be RSRP, RSRQ, SINR, RSSI, etc.

Data amount at random access: for indicating the amount of data when triggering random access SDT.

Data amount at the beginning of SDT: for indicating the amount of data at the time of triggering the SDT.

Data volume related information during SDT transfer: for representing data during SDT transmission

Quantity related information. In one implementation, this information may assist the receiving node of the information in determining whether and/or how the configuration of the SDT is appropriate (e.g., increasing, decreasing, etc.), such as a data amount threshold, an SDT timer value (e.g., T319 a), etc. The related information may include one or more of the following:

data amount reached during the osdt transmission: for representing the amount of data arriving during SDT delivery.

Maximum data volume in the o SDT transmission process: for representing the maximum amount of data buffered during SDT delivery.

The smallest data volume in the osdt transmission process: for representing the minimum amount of data buffered during SDT delivery.

Average data volume during osdt transmission: for representing the average amount of data buffered during SDT delivery.

Data amount sent by SDT: for representing the amount of data sent through the SDT. In one implementation, this information may assist the receiving node of the information in determining whether and/or how the configuration of the SDT is appropriate (e.g., increasing, decreasing, etc.), such as a data amount threshold, an SDT timer value (e.g., T319 a), etc.

Remaining data amount after SDT delivery: for indicating the amount of data remaining unsent after SDT is performed. In one implementation, this information may assist the receiving node of the information in determining whether and/or how the configuration of the SDT is appropriate (e.g., increasing, decreasing, etc.), such as a data amount threshold, an SDT timer value (e.g., T319 a), etc.

Time from the start of SDT to the end of SDT: or may be the time from the start of the T319a timer to the end of the SDT. In one implementation, this time may be used for self-optimization of the node and/or entity for configuration updates, etc. of the relevant configuration. In one implementation, for example, the timer (e.g., may be T319 a) may be updated to set a more appropriate timer.

Time from SDT start to radio link failure: or from the beginning of the T319a timer to

Time of radio link failure. In one implementation, this time may be used for self-optimization of the node and/or entity for configuration updates, etc. of the relevant configuration. In one implementation, for example, the timer (e.g., may be T319 a) may be updated to set a more appropriate timer.

SDT timer state at the end of SDT: indicating the state of the SDT timer at the end of the SDT.

May include running, ending, etc. The SDT timer may be T319a. In one implementation, the state may be used for self-optimization of the node and/or entity for configuration updates, etc. of the relevant configuration. In one implementation, for example, the timer (e.g., may be T319 a) may be updated to set a more appropriate timer. In another implementation, for example, the data volume threshold value corresponding to the configured SDT may be updated. For example, the SDT may expire due to the timer stopping, and the remaining data amount is smaller, and the need to return to the RRC connected state for transmission due to a small amount of remaining data may be avoided by appropriately increasing the data amount threshold corresponding to the SDT and/or appropriately extending the timer.

SDT timer status at radio link failure: indicating SDT radio link failure, SDT meter

State of the timer. May include running, ending, etc. The SDT timer may be T319a.

SDT end reason: indicating the reason for the end of SDT. May include one or more of the following: the SDT timer stops (e.g., may be T319a stopped), receives an RRC message (e.g., may be an RRC release message, an RRC resume message, an RRC setup message, an RRC reject message), a radio link failure, a transmission completion, an RRC connection resume failure, etc.

SDT failure cause: indicating the cause of SDT failure. May include one or more of the following: the SDT timer stops (e.g., may be T319a stopped), receives an RRC message (e.g., may be an RRC release message, an RRC resume message, an RRC setup message, an RRC reject message), a radio link failure, a transmission completion, an RRC connection resume failure, etc.

Example two

One aspect of the present disclosure proposes a method of supporting network self-optimization, which may include: the first entity sends second information containing random access information of random access channel (Random Access Channel, RACH) segmentation configuration to the second entity, so that the second entity can judge whether the random access configuration is suitable and/or update the random access parameter configuration based on the received information, and/or the second entity forwards the received information to other entities, so that the other entities can judge whether the random access configuration is suitable and/or update the random access related configuration, thereby preventing random access failure caused by unreasonable random access configuration and improving the robustness and the effectiveness of the random access.

In some implementations, the second information may be included in one or more of: RRC user information response (ueinformation response), secondary cell group failure information (SCGFailureInformation), primary cell group failure information (MCGFailureInformation); a failure indication (FAILURE INDICATION) message for Xn, a HANDOVER REPORT (HANDOVER) message, an access and mobility indication (ACCESS AND MOBILITY INDICATION) message, a secondary node modification request (S-NODE MODIFICATION REQUEST) message, a secondary gNB modification request (SgNB MODIFICATION REQUEST) message, a secondary cell group failure information REPORT (SCG FAILURE INFORMATION REPORT) message, an RRC transfer (RRC TRANSFER) message; f1 access and mobility indication (ACCESS AND MOBILITY INDICATION) message; the uplink RAN configuration of NG forwards (UPLINK RAN CONFIGURATION TRANSFER) the message and the downlink RAN configuration forwards (DOWNLINK RAN CONFIGURATION TRANSFER) the message; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message. In some embodiments, the second information may be included in a report, where the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, or other report related to a radio connection. The report may also be a new report, e.g. a RACH segment random access report (RA-rachpatiionreport) and/or RACH segment random access information (RA-rachpatiionreportinfo).

In some implementations, the second information may include one or more of the following fields or related information:

UE identity: for identifying the UE for random access.

Node identification: and the node is used for identifying the node corresponding to the random access of the UE.

Cell identity: for identifying the cell to which the UE performs random access.

Feature priority: for representing the priority of a feature and/or a list of priorities of a set of features.

RACH segmentation configuration: for representing RACH segmentation configuration applied when performing random access.

The configuration may include one or more of the following:

o feature combination: for indicating the features for which the configuration is applicable. The features may include one or more of the following: redCap, SDT (also small data), slice (also slice group), coverage enhancement (Coverage Enhancement), etc.

o split Start preamble (startPreambleforThisPartification)

Number of o-divided Preamble sequences codes (Preamble)

(numberOfPreamblesForThisPartition)

o-divided synchronization signal and physical broadcast signal block (Synchronization Signal and

PBCH (physical boardcast channel) Block, SSB) shared RACH occasion

(RACH Occasion, RO) mask index (ssb-SharedRO-MaskIndex)

o number of consecutive Preamble sequences (Preamble) belonging to GroupA (number OfRA-

PreamblesGroupA)

Uplink resource configuration of the o MSGA: the uplink resource may be a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

o characteristic specific parameters: including one or more of the following: synchronization signal and physical broadcast channel block (Synchronization Signal and PBCH (physical boardcast

channel) Block, SSB) corresponding to a signal quality threshold (e.g., rsrp-

ThresholdSSB), a signal quality threshold value corresponding to MSG3 (e.g., may be rsrp-ThresholdMsg 3), a message power interval corresponding to GroupB (e.g., may be messagePowerOffsetGroupB), a size of random access GroupA (e.g., may be ra-SizeGroupA), a Preamble change (deltaPreamble).

The signal quality may be RSRP, RSRQ, SINR, RSSI, etc.

Time of random access to information reporting: for indicating from random access to the second message

Reporting time. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of random access

Time of random access failure to information reporting: for indicating the time from the failure of the random access to the reporting of the second information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of random access failure: in one implementation, this time can be used for nodes and +.

Or the entity finds the relevant configuration, the node and/or the entity can perform self-optimization such as configuration update on the relevant configuration.

Resources available at random access

Features corresponding to available resources at random access

Signal quality corresponding to SSB: the signal quality may be RSRP, RSRQ, SINR,

RSSI, etc.

Signal quality corresponding to MSG 3: the signal quality may be RSRP, RSRQ, SINR,

RSSI, etc.

Information of attempted random access: information for each attempt in a random access procedure

And/or a list of information. Including one or more of the following:

o RACH segmentation configuration

o feature priority

Feature information of user during o random access

o attempt identification: for identifying the attempt.

Number of attempts o: for indicating the number of attempts. Indicating how many attempts the attempt was.

Total number of attempts: for indicating the total number of attempts.

o UE identity: for identifying the UE for random access.

o node identification: and the node is used for identifying the node corresponding to the random access of the UE.

o cell identity: for identifying the cell to which the UE performs random access.

o time of random access to information reporting: for indicating from random access to the first

And reporting time of the two information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of o random access

Time from random access failure to information reporting: for indicating failure from random access to random access

And the time for reporting the second information. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of random access failure

Resources available for o-random access

Features corresponding to available resources during o-random access

Signal quality corresponding to ossb: the signal quality may be RSRP, RSRQ, SINR,

RSSI, etc.

o MSG3 corresponds to signal quality: the signal quality may be the signal quality of RSRP, RSRQ,

SINR, RSSI, etc.

Parameters at random access: may include one or more of the following:

feature combinations: the features may include one or more of the following: redCAP, SDT

(small data (smallData) may be included), slices (slice groups may be included), coverage enhancement (Coverage Enhancement), and the like.

Divided start preamble (startpreamblef orthipartition)

Number of segmented Preamble sequences (Preamble) number (numberofpreambisforthos partitions)

The divided synchronization signal and physical broadcast signal Block (Synchronization Signal and PBCH (physical boardcast channel) Block, SSB) share RACH Occasion (RACH timing, RO) mask index (SSB-SharedRO-

MaskIndex)

Number of consecutive Preamble sequences codes (preambles) belonging to group a

(numberOfRA-PreamblesGroupA)

Uplink resource configuration of MSGA: the uplink resource may be a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

Feature specific parameters: including one or more of the following: a signal quality threshold (e.g., may be rsrp-threshold SSB) corresponding to a synchronization signal and physical broadcast channel Block (Synchronization Signal and PBCH (physical boardcast channel) Block, SSB), a signal quality corresponding to a synchronization signal and physical broadcast channel Block (Synchronization Signal and PBCH (physical boardcast channel) Block, SSB), a signal quality threshold corresponding to MSG3 (e.g., may be rsrp-threshold MSG 3), a signal quality corresponding to MSG3, a message power interval corresponding to GroupB (e.g., may be message poweroffsetgroupb), a size of random access GroupA (e.g., may be ra-SizeGroupA), a Preamble change

(deltaPreamble). The signal quality may be the signal quality of RSRP, RSRQ,

SINR, RSSI, etc.

Example three

One aspect of the present disclosure proposes a method of supporting network self-optimization, which may include: the first entity sends third information for indicating that the SDT information and/or the RACH segmentation random access information are available to the second entity so as to inform the second entity of the SDT information and/or the RACH segmentation random access information stored in the first entity, and the second entity can select whether the information needs to be acquired or not.

In some embodiments, the third information may be included in one or more of: UE measurement available for RRC (UE-MeasurementsAvailable), RRC setup complete (rrcsetup complete), RRC reestablishment complete (RRCReestablishmentComplete), RRC reconfiguration complete (RRCReconfigurationComplete), RRC resume complete (rrcrescendcomple); or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the third information may include one or more of the following fields or related information:

SDT information available: for indicating that SDT information is available, indicating that SDT information is available. This field may be represented by a single bit, e.g., when the bit is 1, it indicates that SDT information is available, and when the bit is 0, it indicates that SDT information is not available; alternatively, when the bit is 0, SDT information may be available, and when the bit is 1, SDT information may be unavailable.

SDT report available: for indicating that an SDT report is available, indicating that there is an SDT report available. This field may be represented by a single bit, e.g., when the bit is 1, it indicates that SDT reports are available, and when the bit is 0, it indicates that SDT reports are not available; or when the bit is 0, it indicates that the SDT report is available, and when the bit is 1, it indicates that the SDT report is not available.

RACH split random access information available: for indicating that RACH segment random access information is available, indicating that RACH segment random access information is available. The field may be represented by a single bit, for example, when the bit is 1, it indicates that RACH segmentation random access information is available, and when the bit is 0, it indicates that RACH segmentation random access information is not available; when the bit is 0, RACH segmentation random access information may be available, and when the bit is 1, RACH segmentation random access information may be unavailable.

RACH segmentation report available: for indicating that RACH segment reports are available, indicating that RACH segment reports are available. This field may be represented by a single bit, e.g., when the bit is 1, it indicates that RACH segmentation report is available, and when the bit is 0, it indicates that RACH segmentation report is not available; when the bit is 0, RACH segmentation report may be available, and when the bit is 1, RACH segmentation report may be unavailable.

In some embodiments, the second entity may send fourth information including the SDT information and/or the RACH segmentation random access information request to the first entity according to the self situation and/or according to the received information indicating that the SDT information is available and/or the RACH segmentation random access information is available, so as to request the first entity to send and/or report the SDT information and/or the RACH segmentation random access information, so that the second entity may acquire the SDT information and/or the RACH segmentation 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.

In some implementations, the fourth information may be included in one or more of: a request for user information (ueinfo request) for 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.

In some implementations, the fourth information may include one or more of the following fields or related information:

SDT information request: for requesting SDT information and/or indicating whether SDT information needs to be reported. The field may be represented by a single bit, e.g., when the bit is 1, it indicates that SDT information is requested and/or that SDT information needs to be reported, and when the bit is 0, it indicates that SDT information is not requested and that

Or no SDT information need to be reported; alternatively, when the bit is 0, it indicates that SDT information is requested and/or SDT information needs to be reported, and when the bit is 1, it indicates that SDT information is not requested and/or SDT information does not need to be reported.

SDT report request: for requesting SDT reports and/or indicating whether reporting of SDT reports is required. This field may be represented by a single bit, e.g., when the bit is 1, it indicates that an SDT report is requested and/or that an SDT report needs to be reported, and when the bit is 0, it indicates that an SDT report is not requested and

or no SDT report need to be reported; alternatively, when the bit is 0, it indicates that the SDT report is requested and/or the SDT report needs to be reported, and when the bit is 1, it indicates that the SDT report is not requested and/or the SDT report does not need to be reported.

RACH split random access information request: for requesting RACH segmentation random access information and/or indicating whether or not RACH segmentation random access information needs to be reported. The field may be represented by a single bit, for example, when the bit is 1, it indicates that RACH segmentation random access information is requested and/or RACH segmentation random access information needs to be reported, and when the bit is 0, it indicates that RACH segmentation random access information is not requested and/or RACH segmentation random access information does not need to be reported; when the bit is 0, it may indicate that RACH segmentation random access information is requested and

And/or RACH segment random access information needs to be reported, and when the bit is 1, the RACH segment random access information is not requested and/or RACH segment random access information does not need to be reported.

RACH segmentation report request: for requesting RACH segmentation reports and/or indicating whether or not RACH segmentation reports need to be reported. The field may be represented by a single bit, e.g., when the bit is 1, it indicates that RACH segment report is requested and/or RACH segment report needs to be reported, and when the bit is 0, it indicates that RACH segment report is not requested and/or RACH segment report does not need to be reported; when the bit is 0, it may indicate that RACH segmentation report is requested and/or RACH segmentation report needs to be reported, and when the bit is 1, it may indicate that RACH segmentation report is not requested and/or RACH segmentation report does not need to be reported.

Example four

One aspect of the present disclosure proposes a method of supporting network self-optimization, which may include: the first entity sends fifth information containing the SDT configuration information and/or RACH segmentation configuration information to the second entity to provide reference information for the configuration of the second entity for SDT and/or RACH segmentation, avoiding resource configuration collision, etc., or the second entity sends the received SDT configuration information and/or RACH segmentation configuration information to other entities to provide reference information for the configuration of the other entities for SDT and/or RACH segmentation, avoiding resource configuration collision, etc.

In some embodiments, the fifth information may be included in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the fifth information may include one or more of the following fields or related information:

node identification: and the node is used for identifying the node corresponding to the configuration information.

Cell identity: for identifying the cell to which the configuration information corresponds.

Random access SDT configuration information: SDT configuration information for representing random access. This information

May comprise one or more of the following:

o SDT corresponds to RSRP Threshold (SDT-RSRP-Threshold)

o SDT corresponding logic channel state reporting time delay timer (SDT-LogicalchannelSR-

DelayTimer)

o SDT corresponds to a data quantity threshold (SDT-DataVolumeThreshold)

o SDT timer value (e.g., T319 a)

Acceptable value and/or acceptable value range of random access SDT configuration information: for representing follow-up

The machine accesses acceptable values and/or acceptable value ranges for the SDT configuration information. Wherein the acceptable value range may comprise, for example, a maximum value and/or a minimum value. The field may be the following information

Acceptable values and/or acceptable value ranges for one or more of the following:

o SDT corresponds to RSRP Threshold (SDT-RSRP-Threshold)

DelayTimer)

o SDT corresponds to a data quantity threshold (SDT-DataVolumeThreshold)

o SDT timer value (e.g., T319 a)

The configuration may include one or more of the following:

o split Start preamble (startPreambleforThisPartification)

Number of o-divided Preamble sequences codes (Preamble)

(numberOfPreamblesForThisPartition)

o-split synchronization signal and physical broadcast channel Block (Synchronization Signal and PBCH (physical boardcast channel) Block, SSB) share RACH Occasion (RACH timing, RO) mask index (SSB-SharedRO-mask index)

PreamblesGroupA)

o characteristic specific parameters: including one or more of the following: the signal quality threshold (e.g., rsrp-

The signal quality may be RSRP, RSRQ, SINR, RSSI, etc.

Acceptable value and/or acceptable value range for RACH segmentation configuration: for representing RACH score

Cutting the acceptable value and/or acceptable value range of the configuration information. Wherein the acceptable value range may comprise, for example, a maximum value and/or a minimum value. The field may be one of the following information

Or a plurality of acceptable values and/or acceptable value ranges:

o split Start preamble (startPreambleforThisPartification)

o number of segmented Preamble sequences (Preamble) number (numberofpreambisforthos partitions)

PreamblesGroupA)

o characteristic specific parameters: the synchronization signal corresponds to a signal quality threshold (e.g., may be rsrp-threshold SSB) for the physical broadcast channel Block (Synchronization Signal and PBCH (physical boardcast channel) Block, a signal quality threshold (e.g., may be rsrp-threshold MSG 3) for MSG3, a message power interval (e.g., may be messagePowerOffsetGroupB) for group pb, a size of random access group pa (e.g., may be ra-SizeGroupA), a Preamble change (deltaPreamble). The signal quality may be RSRP, RSRQ, SINR, RSSI, etc.

In some embodiments, the second entity, upon receiving the fifth information from the first entity, may send the fifth information of the second entity (e.g., including SDT configuration information and/or RACH segmentation configuration information associated with the second entity) to the first entity, as the case may be. The first entity may send the received SDT configuration information and/or RACH segmentation configuration information to other entities to provide reference information for the configuration of the SDT and/or RACH segmentation by the other entities.

Methods performed by a first entity and/or a second entity in a wireless communication system according to embodiments of the present disclosure may be used for network self-optimization decisions. The network self-optimization decisions described in this disclosure may include one or more of network power saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation, and/or network configuration update, etc.

Further, results and reports in this disclosure may refer to each other.

Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

The text and drawings are provided as examples only to aid in the understanding of the present disclosure. They should not be construed as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations can be made to the embodiments and examples shown without departing from the scope of the disclosure.

Fig. 5 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. In particular, fig. 5 illustrates a process of interacting SDT information and/or RACH split random access information between two entities so that a second entity may obtain the SDT information and/or RACH split random access information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first entity may be a UE and 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. In other embodiments, for example, 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 and 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. In further embodiments, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second entity may be an AMF or SMF or MME.

Step 501: the first entity reports the SDT information and/or the RACH segmentation random access information to the second entity. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information.

Step 502: the second entity makes self-optimizing decisions and/or updates configurations, etc., based on the received SDT information and/or RACH split random access information.

Fig. 6 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. In particular, fig. 6 illustrates a process of interacting SDT information and/or RACH split random access information between two entities so that a second entity may obtain the SDT information and/or RACH split random access information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first entity may be a UE and 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. In other embodiments, for example, 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 and 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. In further embodiments, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second entity may be an AMF or SMF or MME.

Step 601: the second entity sends SDT information and/or a RACH segmentation random access information request to the first entity. The SDT information and/or RACH split random access information request may be the fourth information described above.

Step 602: the first entity reports the SDT information and/or the RACH segmentation random access information to the second entity. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information.

Step 603: the second entity makes self-optimizing decisions and/or updates configurations, etc., based on the received SDT information and/or RACH split random access information.

Fig. 7 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. In particular, fig. 7 illustrates a process of interacting SDT information and/or RACH split random access information between two entities so that a second entity may obtain the SDT information and/or RACH split random access information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first entity may be a UE and 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. In other embodiments, for example, 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 and 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. In further embodiments, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second entity may be an AMF or SMF or MME.

Step 701: the first entity sends information indicating that SDT information and/or RACH segmentation random access information is available to the second entity to inform the second entity that the first entity has SDT information and/or RACH segmentation random access information. The information indicating that SDT information is available and/or RACH segmentation random access information is available may be the aforementioned third information.

Step 702: the second entity sends SDT information and/or a RACH segmentation random access information request to the first entity. The SDT information and/or RACH split random access information request may be the fourth information described above.

Step 703: the first entity reports the SDT information and/or the RACH segmentation random access information to the second entity. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information.

Step 704: the second entity makes self-optimizing decisions and/or updates configurations, etc., based on the received SDT information and/or RACH split random access information.

Fig. 8 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 8 illustrates a process of interacting SDT information and/or RACH split random access information among users, nodes, and final service nodes, so that the final service node may obtain the SDT information and/or RACH split random access information, so that the final service node may perform configuration adjustment, make self-optimization decisions, and so on. As described above, the node may be a base station, which may include a Concentration Unit (CU) and a Distribution Unit (DU), and CU may further include a User Plane (UP) and a Control Plane (CP).

Step 801: the UE performs a random access procedure with the last serving node (or may be the CU of the last serving node and/or the DU of the last serving node).

Step 802: the UE performs RRC setup and/or re-establishment procedures with the node (or CU of the node).

Step 803: the UE sends information indicating that SDT information and/or RACH segmentation random access information is available to the node (or CU of the node) to inform the node (or CU of the node) that SDT information and/or RACH segmentation random access information is present at the UE. The information indicating that SDT information is available and/or RACH segmentation random access information is available may be the aforementioned third information. The information indicating that SDT information is available and/or RACH segmentation random access information is available may be transmitted through an RRC setup complete (rrcsetup complete) message.

Step 804: the node (or CU of the node) sends SDT information and/or RACH split random access information requests to the UE to request the UE to report SDT information and/or RACH split random access information. The SDT information and/or RACH split random access information request may be the fourth information described above. The SDT information and/or RACH segmentation random access information request may be transmitted through a UE information request (ueinfo request) message.

Step 805: the UE sends SDT information and/or RACH split random access information to the node (or CU of the node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may be transmitted through a UE information response (ueinfo response) message.

Step 806: the node (or CU of the node) sends SDT information and/or RACH split random access information to the last serving node (or CU of the last serving node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 805. The SDT information and/or RACH split random access information may be sent via a failure indication (Failure Indication) and/or a Handover Report (Handover Report) and/or an access and mobility indication (Access And Mobility Indication) message.

Step 807: the CU of the last service node transmits SDT information and/or RACH split random access information to the DU of the last service node. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 806. The SDT information and/or RACH split random access information may be transmitted via access and mobility indication (Access And Mobility Indication) messages.

The last serving node (or a CU of the last serving node or a DU of the last serving node) may make a self-optimizing decision and/or update configuration based on the received SDT information and/or RACH split random access information.

Fig. 9 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 9 shows a process of performing random access between the UE and the secondary node in the dual-connection case, and exchanging SDT information and/or RACH segmentation random access information between the UE, the primary node, and the secondary node, so that the secondary node may obtain the SDT information and/or RACH segmentation random access information, so that the secondary node may perform configuration adjustment, make a self-optimization decision, and so on.

Step 901: the UE performs a random access procedure with the secondary node (or a CU of the secondary node and/or a DU of the secondary node).

Step 902: the UE sends SDT information and/or RACH split random access information to the master node (or CU of the master node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may be transmitted through an SCG failure information (scgfailurenformation) message.

Step 903: the master node (or a CU of the master node) sends SDT information and/or RACH split random access information to the secondary node (or a CU of the secondary node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 902. The SDT information and/or RACH split random access information may be sent via a secondary node modification request (SgNB Modification Request) and/or SCG failure information report (SCG Failure Information Report) message.

Step 904: the CU of the secondary node sends SDT information and/or RACH segmentation random access information to the DU of the secondary node. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 903. The SDT information and/or RACH split random access information may be transmitted via access and mobility indication (Access And Mobility Indication) messages.

The master node (or a CU of the master node) and the slave node (or a CU of the slave node or a DU of the slave node) may make self-optimizing decisions and/or update configurations based on the received SDT information and/or RACH split random access information.

Fig. 10 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 10 shows a process of performing random access between the UE and the master node in the dual-connection case, and exchanging SDT information and/or RACH segmentation random access information between the UE, the master node, and the slave node, so that the master node may obtain the SDT information and/or RACH segmentation random access information, so that the master node may perform configuration adjustment, make a self-optimization decision, and so on.

Step 1001: the UE performs a random access procedure with the master node (or may be a CU of the master node and/or a DU of the master node).

Step 1002: the UE sends SDT information and/or RACH split random access information to the secondary node (or a CU of the secondary node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH split random access information may be transmitted via a master cell group (Master Cell Group) failure information (MCGFailureInformation) message.

Step 1003: the secondary node (or a CU of the secondary node) sends SDT information and/or RACH split random access information to the primary node (or a CU of the primary node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 1002. The SDT information and/or RACH segmentation random access information may be transmitted through an RRC Transfer (RRC Transfer) message.

Step 1004: the CU of the master node transmits SDT information and/or RACH split random access information to the DU of the master node. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 1003. The SDT information and/or RACH split random access information may be transmitted via access and mobility indication (Access And Mobility Indication) messages.

The master node (either a CU of the master node or a DU of the master node) may make self-optimizing decisions and/or update configurations based on the received SDT information and/or RACH split random access information.

Fig. 11 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 11 illustrates a process of interacting SDT information and/or RACH segmentation random access information among users, nodes, last service nodes, AMFs, so that the last service node may obtain the SDT information and/or RACH segmentation random access information, so that the last service node may perform configuration adjustment, make self-optimization decisions, and so on.

Step 1101: the UE performs a random access procedure with the last serving node (or may be the CU of the last serving node and/or the DU of the last serving node).

Step 1102: the UE performs RRC setup and/or re-establishment procedures with the node (or CU of the node).

Step 1103: the UE sends information indicating that SDT information and/or RACH segmentation random access information is available to the node (or CU of the node) to inform the node (or CU of the node) that SDT information and/or RACH segmentation random access information is present at the UE. The information indicating that SDT information is available and/or RACH segmentation random access information is available may be the aforementioned third information. The information indicating that the SDT information and/or RACH segmentation random access information is available may be transmitted through an RRC setup complete (rrcsetup complete) message.

Step 1104: the node (or CU of the node) sends SDT information and/or RACH split random access information requests to the UE to request the UE to report SDT information and/or RACH split random access information. The SDT information and/or RACH split random access information request may be the fourth information described above. The SDT information and/or RACH segmentation random access information request may be transmitted through a UE information request (ueinfo request) message.

Step 1105: the UE sends SDT information and/or RACH split random access information to the node (or CU of the node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may be transmitted through a UE information response (ueinfo response) message.

Step 1106: the node (or CU of the node) sends SDT information and/or RACH split random access information to the AMF. The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH partition random access information may include all information and/or part of the information in step 1105. The SDT information and/or RACH split random access information may be sent via an uplink RAN configuration forwarding (Uplink RAN Configuration Transfer) message.

Step 1107: the AMF sends SDT information and/or RACH split random access information to the last serving node (or CU of the last serving node). The SDT information may be the aforementioned first information. The RACH split random access information may be the aforementioned second information. The SDT information and/or RACH segmentation random access information may include all information and/or part of the information in step 1106. The SDT information and/or RACH split random access information may be sent via a downlink RAN configuration forwarding (Downlink RAN Configuration Transfer) message.

The CU of the last serving node may also send all and/or part of the received SDT information and/or RACH segmentation random access information to the DU of the last serving node.

Finally, the serving node (or a CU of the secondary node or a DU of the secondary node) may make a self-optimizing decision and/or update a configuration based on the received SDT information and/or RACH split random access information.

Fig. 12 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 12 illustrates a process of interacting SDT configuration information and/or RACH split random access configuration information (i.e., the SDT configuration information and/or RACH split configuration information described above) between two entities so that a second entity may obtain the SDT configuration information and/or RACH split random access configuration information to update a configuration, etc. In some embodiments, for example, 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 and 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. In other embodiments, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second entity may be an AMF or SMF or MME.

Step 1201: the first entity sends the SDT configuration information and/or RACH segmentation random access configuration information to the second entity. The SDT configuration information and/or RACH segmentation random access configuration information may be the fifth information described above.

Step 1202: the second entity updates the configuration, etc., based on the received SDT configuration information and/or RACH split random access configuration information.

Fig. 13 illustrates a schematic diagram of one aspect of a method of supporting network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 13 illustrates a process of interacting SDT configuration information and/or RACH split random access configuration information between two entities, so that a first entity may negotiate SDT configuration information and/or RACH split random access configuration information with a second entity, and the first entity may perform update configuration, etc. In some embodiments, for example, 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 and 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. In other embodiments, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first entity may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second entity may be an AMF or SMF or MME.

Step 1301: the first entity sends the SDT configuration information and/or RACH segmentation random access configuration information to the second entity. The SDT configuration information and/or RACH segmentation random access configuration information may be the fifth information described above.

Step 1302: the second entity sends SDT configuration information and/or RACH segmentation random access configuration information associated with the second entity to the first entity. The SDT configuration information and/or RACH segmentation random access configuration information may also be the fifth information described above.

Step 1303: the first entity performs update configuration, etc., based on the SDT configuration information and/or RACH segmentation random access configuration information negotiated in step 1301 and/or step 1302.

Next, fig. 14 shows a schematic diagram of a first entity 1400 according to an embodiment of the disclosure.

As shown in fig. 14, a first entity (or first entity device) 1400 in accordance with embodiments of the present disclosure 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 (e.g., to control the transceiver 1410) to perform a method performed by a first entity according to embodiments of the present disclosure.

As shown in fig. 15, a second entity (or second entity device) 1500 in accordance with embodiments of the present disclosure 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 with the transceiver 1510 and may be configured (e.g., to control the transceiver 1510) to perform a method performed by a second entity in accordance with embodiments of the present disclosure. The processor may also be referred to as a controller.

Embodiments of the present disclosure also provide a computer readable medium having stored thereon computer readable instructions, which when executed by a processor may be used to implement any method according to embodiments of the present disclosure.

Various embodiments of the present disclosure may be implemented as computer readable code embodied on a computer readable recording medium from a particular perspective. The computer readable recording medium is any data storage device that can store data which can be read by a computer system. Examples of the computer readable recording medium may include a read-only memory (ROM), a random-access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, a carrier wave (e.g., data transmission via the internet), and so forth. The computer-readable recording medium can be distributed by a computer system connected via a network, and thus the computer-readable code can be stored and executed in a distributed manner. Moreover, functional programs, codes, and code segments for accomplishing the various embodiments of the present disclosure may be easily construed by one skilled in the art to which the embodiments of the present disclosure are applied.

It will be understood that embodiments of the present disclosure may be implemented in hardware, software, or a combination of hardware and software. The software may be stored as program instructions or computer readable code executable on a processor on a non-transitory computer readable medium. Examples of the non-transitory computer readable recording medium include magnetic storage media (e.g., ROM, floppy disks, hard disks, etc.) and optical recording media (e.g., CD-ROMs, digital Video Disks (DVDs), etc.). The non-transitory computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. The medium may be readable by a computer, stored in a memory, and executed by a processor. The 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 adapted to store a program(s) having instructions to implement the embodiments of the present disclosure. The present disclosure may be implemented by a program having codes for embodying the apparatus and method described in the claims, the program being stored in a machine (or computer) readable storage medium. The program may be carried electronically on any medium, such as communication signals conveyed via a wired or wireless connection, and the disclosure suitably includes equivalents thereof.

The foregoing is merely a specific embodiment of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art may make various changes or substitutions within the technical scope of the present disclosure, and such changes or substitutions are intended to be included in the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method performed by a first entity in a wireless communication system, comprising:

Send to the second entity first information including SDT information for SDT based on small data packet transmission SDT configuration information, second information including RACH split random access information for random access based on the random access channel RACH split configuration, and at least one of the fifth information including SDT configuration information and/or RACH split configuration information,

Wherein, the at least one piece of information is associated with at least one of the first entity and other entities other than the first entity.

2. The method of claim 1, further comprising:

receiving fourth information including a request for the SDT information and/or the RACH split random access information from the second entity,

Wherein, the first information and/or the second information are sent by the first entity to the second entity based on the fourth information.

3. The method of claim 2, further comprising:

sending third information indicating that the SDT information is available and/or the RACH split random access information is available to the second entity,

Wherein, the fourth information is sent by the first entity to the second entity based on the third information.

4. The method of claim 1, further comprising:

receiving SDT configuration information and/or RACH split configuration information associated with the second entity from the second entity,

Wherein, at least part of the SDT configuration information and/or RACH split configuration information associated with the second entity is determined by the second entity based on the fifth information.

5. The method of claim 1, wherein the at least one 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 update.

6. The method of claim 1, wherein the first information includes one or more of the following:

User equipment identification, node identification, cell identification, indication that the purpose of random access is SDT, random access SDT configuration information, random access to information reporting time, SDT start to information reporting time, SDT wireless link failure to Time for information reporting, time from SDT interruption to information reporting, time from SDT failure to information reporting, signal quality when SDT fails, remaining data amount after SDT failure, signal quality during random access, data during random access amount, the amount of data at the beginning of SDT, information related to the amount of data during SDT transmission, the amount of data sent by SDT, the amount of remaining data after SDT is sent, the time from the beginning of SDT to the end of SDT, the time from the beginning of SDT to the failure of the wireless link Time, SDT timer status when SDT ends, SDT timer status when wireless link fails, SDT end reason, SDT failure reason.

7. The method according to claim 6, wherein the information related to the amount of data in the SDT transmission process includes one or more of the following:

The amount of data arriving during SDT transmission, the maximum amount of data during SDT transmission, the minimum amount of data during SDT transmission, and the average amount of data during SDT transmission.

8. The method of claim 1, wherein the second information includes one or more of the following:

User equipment identification, node identification, cell identification, feature priority, RACH split configuration, time from random access to information reporting, resources available during random access, time of random access, time from random access failure to information reporting , the time when the random access fails, the characteristics corresponding to the available resources during random access, the signal quality corresponding to the synchronization signal and the physical broadcast channel block SSB, the signal quality corresponding to MSG3, and the information of the random access attempt.

9. The method of claim 1, wherein the fifth information includes one or more of the following:

Node identification, cell identification, random access SDT configuration information, acceptable values and/or acceptable value ranges of random access SDT configuration information, RACH split configuration, acceptable values and/or acceptable value ranges of RACH split configuration.

10. The method of claim 2, wherein the fourth information includes one or more of the following:

SDT information request, SDT report request, RACH split random access information request, RACH split report request.

11. The method of claim 3, wherein the third information includes one or more of the following:

SDT information is available, SDT report is available, RACH split random access information is available, and RACH split report is available.

12. A method performed by a second entity in a wireless communication system, comprising:

Receive from the first entity first information including SDT information for SDT based on small data packet transmission SDT configuration information, second information including RACH split random access information for random access based on the random access channel RACH split configuration, and at least one of the fifth information including SDT configuration information and/or RACH split configuration information,

13. A first entity device in a wireless communication system, including:

a transceiver configured to transmit and receive signals; and

A controller coupled to the transceiver and configured to perform the method of any one of claims 1-11.

14. A second entity device in a wireless communication system, including:

a transceiver configured to transmit and receive signals; and

A controller coupled to the transceiver and configured to perform the method of claim 12.

15. A computer-readable medium having computer-readable instructions stored thereon, the instructions, when executed by a processor, are used to implement the method of any one of claims 1-12.