Node devices in wireless communication systems and the methods they perform

Abstract

This disclosure provides a method and apparatus for execution in a wireless communication system. In one embodiment, a method is provided for execution by a first node in a wireless communication network, the method comprising: receiving third information from a second node, the third information including information of a first timer associated with cascading and information of a cascading maximum value; and, while the first timer is running, performing a cascading-related operation on a received service data unit based on the information of the cascading maximum value.

Description

Technical Field

[0001] This application relates to wireless communication technology, and more particularly to an interactive method and apparatus. Background Technology

[0002] Given the successive generations of wireless communication development, these technologies have primarily been developed for human-oriented services such as voice calls, multimedia services, and data services. With the commercialization of 5th-generation (5G) communication systems, the number of connected devices is expected to grow exponentially. These will increasingly connect to communication networks. Examples of the Internet of Things (IoT) can include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve in various forms, such as augmented reality glasses, virtual reality headsets, and holographic devices. Efforts are underway to develop improved 6G communication systems to provide a wide range of services by connecting hundreds of billions of devices and things in the 6th-generation (6G) era.

[0003] The 6G communication system, expected to be commercially available around 2030, will offer significant improvements in all aspects compared to existing 5G systems. Its peak speed will reach at least 50 Gbit / s, user experience speed will reach at least 300 Mbit / s, air interface latency will be less than 1 ms, and air interface reliability will reach [missing information]. In addition to the basic communication indicators mentioned above, 6G communication systems will also have sensing capabilities, AI-related capabilities, and better security, interoperability, and sustainability.

[0004] To achieve the aforementioned performance indicators in 6G communication systems, more advanced air interface and network technologies are needed. Currently, the evolution of extreme multiple input multiple output (MIMO) is being considered, including the use of very large-scale antenna arrays, the development and evolution of distributed antenna systems, and the design of MIMO air interface algorithms assisted by artificial intelligence (AI). This technology can achieve higher spectral efficiency, greater coverage, and more precise positioning and sensing capabilities. Furthermore, technologies that contribute to improving high-frequency coverage, such as metamaterial-based lenses and antennas, novel antenna architectures, and reconfigurable intelligence surfaces (RIS), also require further evolution and development.

[0005] To meet the new functions added to the 6G communication system, it is necessary to develop new technologies in areas such as network energy saving, air interface security, and network security, and at the same time, it is necessary to study the feasibility of integrated technologies such as communication and sensing integration.

[0006] In addition, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology to enable uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies that utilize satellites, high-altitude platform stations (HAPS), etc., in a comprehensive manner; improved network architecture to support mobile base stations, etc., and to enable network operation optimization and automation; dynamic spectrum sharing technology based on spectrum usage prediction and conflict avoidance; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by utilizing AI from the design phase of 6G development and internalizing end-to-end AI support functions; and next-generation distributed computing technologies that overcome the computing power limitations of user equipment (UE) by leveraging ultra-high-performance communication and computing resources available on the network, such as mobile edge computing (MEC), cloud, etc. Furthermore, efforts are continuing to enhance connectivity between devices, optimize networks, promote the software-defined networking of network entities, and increase the openness of wireless communications by designing new protocols to be used in 6G communication systems, developing mechanisms for achieving hardware-based secure environments and secure data use, and developing technologies for maintaining privacy.

[0007] The research and development of 6G communication systems, encompassing both person-to-machine (P2M) and machine-to-machine (M2M) hyper-connectivity, is expected to deliver the next wave of hyper-connected experiences. Specifically, services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas are anticipated to be provided through 6G communication systems. Furthermore, services such as remote surgery for enhanced safety and reliability, industrial automation, and emergency response will be available via 6G communication systems, enabling the technology to be applied across a wide range of sectors including industry, healthcare, automotive, and home appliances. Summary of the Invention

[0008] According to one aspect of this disclosure, a method is provided performed by a first node in a wireless communication network, the method comprising: receiving third information from a second node, the third information including information of a first timer associated with cascading and information of a cascading maximum value; and, while the first timer is running, performing a cascading-related operation on a received service data unit based on the information of the cascading maximum value.

[0009] In a further embodiment, the method further includes: receiving second information from a second node, wherein the second information includes at least one of the following: first value-related information, used to indicate threshold value-related information of small service data units that can be cascaded; and related information for activating or deactivating cascading.

[0010] In a further embodiment, the method further includes: maintaining state variables, the state variables including at least one of the following: a first quantity, used to record the number of service data units being cascaded; and a first duration, used to record the duration of the first timer.

[0011] In a further embodiment, at least one of the following is also included: when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is associated with the service data unit; when the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded; when the first timer times out, the cascaded service data units are combined into a grouped data unit and sent to the lower layer.

[0012] In a further embodiment, it further includes at least one of the following: when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, the first timer being associated with the service data unit, and then the first quantity is set to 0 or 1; while the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded, and then the first quantity is incremented by 1; if the updated first quantity is greater than the cascaded maximum value related information, the first timer is stopped and reset, and the cascaded multiple service data units are combined into a grouped data unit and sent to the lower layer; when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is set to 0 or 1; The first timer is associated with the service data unit, and then the first duration is set to the value configured by the relevant configuration information of the first timer. When the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded. Then, the first duration is subtracted from the value configured by the relevant step size information of the first timer. If the updated first duration is less than the running time of the first timer, the first timer is stopped and reset. The cascaded service data units are combined into a group data unit and sent to the lower layer. The relevant step size information of the first timer is included in the third information. When the first timer times out, the cascaded service data units are combined into a group data unit and sent to the lower layer.

[0013] In a further embodiment, at least one of the following is also included: when a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is associated with the service data unit; when the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are cascaded; when the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer; when the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a packet data unit and sent to the lower layer, then the service data units with a length greater than the first value are combined into another packet data unit and sent to the lower layer, and then the first timer is stopped and reset; when the first timer times out, the multiple cascaded service data units are combined into a packet data unit and sent to the lower layer.

[0014] In a further embodiment, at least one of the following is also included: when a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, the first timer is associated with the service data unit, and then the first quantity is set to 0 or 1; when the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are concatenated, and then the first quantity is incremented by 1; if the updated first quantity is greater than the concatenation maximum value related information, the first timer is stopped and reset, and the multiple concatenated service data units are combined into a group data unit and sent to the lower layer; When the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer. When the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a packet data unit and sent to the lower layer, then the service data units with a length greater than the first value are combined into another packet data unit and sent to the lower layer, and then the first timer is stopped and reset. When a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, associated with the service data unit, and then the first duration is set to the value configured in the relevant configuration information of the first timer. When the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are cascaded, and then the... The first duration is subtracted from the value configured by the first timer's related step size information. If the updated first duration is less than the running time of the first timer, the first timer is stopped and reset, and the cascaded service data units are combined into a single data packet and sent to the lower layer. The first timer's related step size information is included in the third information. During the first timer's operation, if other service data units with a length greater than the first value are received from the upper layer, these service data units are directly combined into a single data packet and sent to the lower layer. If, during the first timer's operation, other service data units with a length greater than the first value are received from the upper layer, the already cascaded service data units are first combined into a single data packet and sent to the lower layer, then the service data units with a length greater than the first value are combined into another single data packet and sent to the lower layer, and then the first timer is stopped and reset. When the first timer times out, the cascaded service data units are combined into a single data packet and sent to the lower layer.

[0015] In a further embodiment, it further includes at least one of the following: if concatenation is activated and if the length of the service data unit is less than the first value, then consider concatenating the service data unit; if concatenation is activated and if more than one service data unit has a length less than the first value, then concatenate the service data units; if concatenation is activated, concatenate service data units with a length less than the first value.

[0016] In a further embodiment, at least one of the following is included: if the relevant information for activating the cascade is indicated, then the cascade is activated; if the relevant information for deactivating the cascade is indicated, then the cascade is deactivated.

[0017] In a further embodiment, the information related to the activation or deactivation cascade is included in the transmission of the media access control layer control unit.

[0018] In a further embodiment, at least one of the following is also included: if the media access control layer entity receives an instruction from the control unit to activate cascading, the media access control layer entity will indicate cascading activation information to the upper layer; if the media access control layer entity receives an instruction from the control unit to deactivate cascading, the media access control layer entity will indicate cascading deactivation information to the upper layer.

[0019] In a further embodiment, it further includes at least one of the following: if the length of a service data unit is less than the first value, then consider cascading the service data units; if more than one service data unit has a length less than the first value, then cascade the service data units; cascade service data units with a length less than the first value.

[0020] In a further embodiment, the method further includes: sending first information to a second node, the first information being used by the second node to recover a packet data unit into multiple service data units; wherein the first information includes at least one first length information, the first length information indicating the byte length of the corresponding service data unit in the related packet data unit.

[0021] In a further embodiment, the length of the first length information is 7 bits or less.

[0022] According to another aspect of this disclosure, a method is provided performed by a second node in a wireless communication network, the method comprising: initiating a process for modifying a radio resource control connection; and sending third information to a first node, wherein the third information includes information about a first timer associated with cascading and information about a cascading maximum value; wherein the cascading-related operation of the first node is performed while the first timer is running and based on the information about the cascading maximum value.

[0023] In a further embodiment, the method further includes: sending second information to the first node, wherein the second information includes at least one of the following: first value-related information, used to indicate threshold value-related information of small service data units that can be cascaded; and related information for activating or deactivating cascading.

[0024] In a further embodiment, the method further includes: receiving first information from a first node, the first information being used by the second node to recover a packet data unit into multiple service data units; wherein the first information includes at least one first length information, the first length information indicating the byte length of the corresponding service data unit in the associated packet data unit.

[0025] In a further embodiment, the length of the first length information is 7 bits or less. Attached Figure Description

[0026] Figure 1 Here is an example of a wireless network; Figure 2 Here is an example of a base station structure; Figure 3 Example of a user device; Figures 4A to 4G Various example embodiments for data transmission; Figure 5 A block diagram of the fifth node according to the present invention; Figure 6 This is a block diagram of network nodes in a network according to this disclosure. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0028] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout the patent literature. The term “connection” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are physically in contact with each other. The terms “transmit,” “receive,” and “transmit,” and their derivatives encompass both direct and indirect communication. The terms “comprise” and “include,” and their derivatives mean inclusion without limitation. The term “or” is concurrent, meaning both and / or. The phrase “associated with,” and its derivatives mean including, being included in, interconnected with, containing, being contained within, connected to or connected with, coupled to or coupled with, able to communicate with, cooperate with, intertwine, juxtapose, proximate, bound to or bound with, having, possessing attributes, having a relationship with, or having a relationship with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functionality associated with any particular controller, whether local or remote, can be centralized or distributed. The phrase "at least one" when used to list items means that different combinations of one or more of the listed items can be used, and it is possible that only one item in the list is needed. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C; A and B; A and C; B and C; and only A, only B, and only C. Similarly, the term "set" means one or more. Therefore, a set of items can be a single item or a set of two or more items.

[0029] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each function being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media such as rewritable optical discs or erasable memory devices in which data can be stored and later rewritten.

[0030] Definitions for certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many, if not the most, instances, such definitions apply to both prior and future use of the words and phrases defined in this way.

[0031] The figures and various embodiments included herein, used to illustrate the principles of this disclosure, are merely illustrative and should not be construed in any way as limiting the scope of this disclosure. Furthermore, those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system.

[0032] The following Figures 1 to 3 Various embodiments of this disclosure implemented in wireless communication systems are described. Figures 1 to 3 The description does not imply any physical or architectural limitations on the ways in which different embodiments can be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0033] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0034] like Figure 1As shown, the wireless network includes a base station (next generation nodeB, gNB or gNodeB) 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 such as the Internet, a proprietary Internet Protocol (IP) network, or other data networks.

[0035] gNB 102 provides wireless broadband access to network 130 to multiple first user equipments (UEs) within coverage area 120 of gNB 102. The multiple first UEs include UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R1); UE 115, which may be located in a second residence (R2); and UE 116, which may be a mobile device (M) such as a cellular phone, wireless laptop, or wireless personal digital assistant (PDA). gNB 103 provides wireless broadband access to network 130 to multiple second UEs within coverage area 125 of gNB 103. The multiple second UEs include UE 115 and UE 116, and subscriber stations (SS, such as UEs) 117, 118, and 119. In some embodiments, one or more of the gNBs 101103 may communicate with each other and with the UE 111116 using existing wireless communication technologies, and one or more of the UEs 111119 may communicate directly with each other (e.g., UE 117119) using other existing or proposed wireless communication technologies.

[0036] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), enhanced (or "evolved") base station (eNodeB or eNB), 5G base station (gNB), macro cell, femtocell, wireless fidelity (WiFi) access point (AP), or other wirelessly capable device. A base station can provide wireless access according to one or more wireless communication protocols, such as 3GPP 5G new radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTEA), high-speed packet access (HSPA), WiFi 802.11a / b / g / n / ac, etc. For convenience, various names for base station type devices and functions may be used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "User Equipment" (UE) can refer to any component such as a mobile station (MS), user station (SS), remote terminal, wireless terminal, receiving point, or user device. For convenience, various names for user equipment type devices and functions may be used interchangeably in this patent document to refer to remote wireless devices that wirelessly access the BS regardless of whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0037] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as roughly circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas such as 120 and 125 associated with the gNB can have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the wireless environment associated with natural and man-made obstacles.

[0038] As described in more detail below, one or more of UE 111119 include circuitry, programming, or a combination thereof. In some embodiments, one or more of gNB 101103 include circuitry, programming, or a combination thereof.

[0039] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1Various modifications can be made. For example, wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102 or 103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0040] Figure 2 An example base station according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs come in a variety of configurations, and Figure 2 This disclosure is not intended to limit the scope to any particular implementation of gNB.

[0041] like Figure 2 As shown, gNB 102 includes multiple antennas 200a and 200n, multiple radio frequency (RF) transceivers 201a and 201n, transmit (TX) processing circuitry 203, and receive (RX) processing circuitry 204. gNB 102 also includes a controller / processor 205, a memory 206, and a backhaul or network interface (IF) 207.

[0042] RF transceivers 201a and 201n receive incoming RF signals from antennas 200a and 200n, such as signals transmitted by the UE in network 100. RF transceivers 201a and 201n down-convert the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signal is sent to RX processing circuitry 204, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 204 sends the processed baseband signal to controller / processor 205 for further processing.

[0043] TX processing circuit 203 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 205. TX processing circuit 203 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 201a and 201n receive the processed baseband or IF signal from TX processing circuit 203 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 201a and 201n.

[0044] The controller / processor 205 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 205 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 201a and 201n, the RX processing circuit 204, and the TX processing circuit 203, according to known principles. The controller / processor 205 may also support additional functions, such as more advanced wireless communication functions.

[0045] For example, the controller / processor 205 can support beamforming or directional routing operations, where signals emitted from multiple antennas 200a and 200n are weighted differently to effectively redirect the emitted signals in the desired direction. Any of a variety of other functions can be supported in the gNB 102 via the controller / processor 205.

[0046] The controller / processor 205 is also capable of executing programs and other processes located in memory 206, such as the operating system (OS). The controller / processor 205 can move data into or out of memory 206 as needed by the executing process.

[0047] The controller / processor 205 is also connected to a backhaul or network interface 207. The backhaul or network interface 207 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 207 can support communication via any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G, LTE, or LTE-A), interface 207 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 207 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). Interface 207 includes any suitable structure that supports communication via wired or wireless connections such as Ethernet or RF transceivers.

[0048] Memory 206 is connected to controller / processor 205. A portion of memory 206 may include random access memory (RAM), and another portion of memory 206 may include flash memory or other read-only memory (ROM).

[0049] although Figure 2 An example of gNB 102 is shown, but it is possible to see more. Figure 2 Various changes can be made. For example, gNB 102 can include any number of Figure 2 Each component is shown in the diagram. As a specific example, an access point may include multiple interfaces 207, and the controller / processor 205 may support routing functionality to route data between different network addresses. As another specific example, although shown as a single instance of TX processing circuitry 203 and a single instance of RX processing circuitry 204, gNB102 may include multiple instances of each (such as one per RF transceiver). For example, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0050] Figure 3 An example user equipment according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111115 and 117119 can have the same or similar configurations. However, UEs appear in multiple configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0051] like Figure 3 As shown, UE 116 includes an antenna 301, a radio frequency (RF) transceiver 302, a TX processing circuit 303, a microphone 304, and a receive (RX) processing circuit 305. UE 116 also includes a speaker 306, a controller or processor 307, an input / output (I / O) interface (IF) 308, an input device 309, a touchscreen display 310, and memory 311. Memory 311 includes an OS 312 and one or more applications 313.

[0052] RF transceiver 302 receives incoming RF signals transmitted by gNB of network 100 from antenna 301. RF transceiver 302 down-converts the incoming RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 305, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 305 sends the processed baseband signal to speaker 306 (e.g., for voice data) or processor 307 for further processing (e.g., for web browsing data).

[0053] TX processing circuit 303 receives analog or digital voice data from microphone 304 or other outgoing baseband data (such as web data, email, or interactive video game data) from processor 307. TX processing circuit 303 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 302 receives the processed baseband or IF signal from TX processing circuit 303 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 301.

[0054] Processor 307 may include one or more processors or other processing devices and executes OS 312 stored in memory 311 to control the overall operation of UE 116. For example, processor 307 may control the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 302, RX processing circuitry 305, and TX processing circuitry 303 according to known principles. In some embodiments, processor 307 includes at least one microprocessor or microcontroller.

[0055] Processor 307 is also capable of executing other processes and programs located in memory 311, such as processes for CSI (Channel State Information) reporting on the uplink channel. Processor 307 can move data into or out of memory 311 as needed for executing processes. In some embodiments, processor 307 is configured to execute application 313 based on OS 312 or in response to signals received from gNB or operator. Processor 307 is also coupled to I / O interface 308, which provides UE 116 with the ability to connect to other devices such as laptops and laptops. I / O interface 308 is the communication path between these accessories and processor 307.

[0056] The processor 307 is also connected to the touchscreen display 310. The user of the UE 116 can use the touchscreen display 310 to input data into the UE 116. The touchscreen display 310 can be a liquid crystal display, a light-emitting diode display, or other display capable of rendering text and / or at least limited graphics such as those from a website.

[0057] Memory 311 is connected to processor 307. A portion of memory 311 may include RAM, and another portion of memory 311 may include flash memory or other ROM.

[0058] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 307 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Moreover, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0059] Exemplary embodiments of this disclosure are further described below with reference to the accompanying drawings.

[0060] The text and accompanying drawings are provided by way of example only to aid in understanding this disclosure. They should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes may be made to the illustrated embodiments and examples without departing from the scope of this disclosure.

[0061] Before proceeding with the specific details, the following are some assumptions and definitions of this disclosure.

[0062] The message names in this disclosure are just examples; other message names may also be used.

[0063] The use of terms such as "first" and "second" in the message names disclosed herein is merely an example of a message and does not represent the order of execution.

[0064] Detailed descriptions of steps that are not related to this disclosure have been omitted from this disclosure.

[0065] In this disclosure, the steps in each process can be executed in combination or individually. The execution steps of each process are merely examples, and other possible execution orders are not excluded.

[0066] In this disclosure, the base station can be a 5G base station (such as a gNB, ng-eNB), a 4G base station (such as an eNB), a 6G base station, or other types of access nodes.

[0067] In this disclosure, data transmission refers to the receipt or sending of data.

[0068] The nodes involved in this disclosure are: First node: User Equipment (UE) Second node: Base station, or centralized unit of base station, or control plane portion of centralized unit of base station. This disclosure provides a transmission method that saves on data transmission header overhead compared to traditional methods.

[0069] It should be noted that transmission can occur from the first node to the second node, or vice versa. When the first node is the sender or sending entity (hereinafter referred to as the "sending entity" for simplicity), the second node is the receiver or receiving entity (hereinafter referred to as the "receiving entity" for simplicity). When the second node is the sending entity, the first node is the receiving entity. The behavior of the nodes will be described below using the behaviors of the sending entity and the receiving entity.

[0070] Figure 4A An example method of transmission according to this disclosure is shown. Figure 4A As shown, The first node sends first information to the second node, or the second node sends first information to the first node. The first information is used for the receiving entity to restore a Packet Data Unit (PDU) into multiple Service Data Units (SDUs), and / or for the sending entity to instruct the sending entity to merge or concatenate multiple Service Data Units into a single Packet Data Unit.

[0071] The first information includes at least one first length information.

[0072] The first length information may be named L, LI, Length, etc. (hereinafter, "L" will be used to describe it).

[0073] Wherein the first length information: In one implementation, the byte length of the corresponding data field unit in the relevant packet data unit is indicated.

[0074] In another implementation: the byte length of the corresponding data field unit in the associated packet data unit minus N. Here, N can be 1 or any other integer.

[0075] In another implementation: the byte length of the corresponding data field unit in the relevant packet data unit plus N. N can be 1 or any other integer.

[0076] In another implementation, the byte length of the associated service data unit is indicated.

[0077] In another implementation, the byte length of the associated service data unit is indicated by minus N. N can be 1 or any other integer.

[0078] In another implementation, the byte length of the associated service data unit is indicated by N. N can be 1 or any other integer.

[0079] The first information may be included in a Service Data Adaptation Protocol (SDAP) packet data unit or in a Packet Data Convergence Protocol (PDCP) packet data unit.

[0080] If the first information is contained in an SDAP packet data unit, one possible implementation is as follows: Figure 4B As shown, The D / C field, with a length of 1 bit, is used to indicate whether a packet data unit is a data packet data unit or a control packet data unit. In one possible implementation, a value of 0 represents a control packet data unit, and a value of 1 represents a data packet data unit.

[0081] The QFI field, which is 6 bits long, is used to indicate the identifier of the Quality of Service (QoS) flow to which the packet data unit belongs.

[0082] The E field, with a length of 1 bit, indicates whether it is followed by a data field or a set of L and E fields. For the E field in the fixed portion of the header, in one possible implementation, a value of 0 indicates that the fixed portion of the header is followed by a data field, and a value of 1 indicates that the fixed portion of the header is followed by a set of L and E fields. For the E field in the extended portion of the header, in one possible implementation, a value of 0 indicates that this E field and / or the corresponding L field is followed by a data field, and a value of 1 indicates that this E field and / or the corresponding L field is followed by a set of L and E fields.

[0083] A Data domain contains at least one Service Data Unit or at least one Data Domain Unit. Data Domain Units are mapped into Data Domains in the order they arrive at the SDAP entity.

[0084] The L field, with a length of 7 bits, represents the first length information. In one possible implementation, the first occurrence of the first length information in the packet header corresponds to the first data field unit in the data field, the second occurrence of the first length information corresponds to the second data field unit, and so on. In another possible implementation, the first occurrence of the first length information in the packet header corresponds to the second data field unit, the second occurrence of the first length information corresponds to the third data field unit, and so on.

[0085] It should be noted that, in one possible implementation, the last data field unit does not need to indicate the corresponding set of L and E fields in the packet header. In another possible implementation, the first data field unit does not need to indicate the corresponding set of L and E fields in the packet header.

[0086] It should be noted that the order of an L-field and an E-field can be either 7 bits of L-field followed by 1 bit of E-field, or 1 bit of E-field followed by 7 bits of L-field.

[0087] If the first information is contained in a PDCP packet data unit, one possible implementation is as follows: Figure 4C As shown, The D / C field, with a length of 1 bit, is used to indicate whether a packet data unit is a data packet data unit or a control packet data unit. In one possible implementation, a value of 0 represents a control packet data unit, and a value of 1 represents a data packet data unit.

[0088] The SN field, which is 12 bits long, is used to indicate the sequence number of the data packet.

[0089] The E field, with a length of 1 bit, indicates whether it is followed by a data field or a set of L and E fields. For the E field in the fixed portion of the header, in one possible implementation, a value of 0 indicates that the fixed portion of the header is followed by a data field, and a value of 1 indicates that the fixed portion of the header is followed by a set of L and E fields. For the E field in the extended portion of the header, in one possible implementation, a value of 0 indicates that this E field and / or the corresponding L field is followed by a data field, and a value of 1 indicates that this E field and / or the corresponding L field is followed by a set of L and E fields.

[0090] A Data domain contains at least one Service Data Unit or at least one Data Domain Unit. Data Domain Units are mapped into the Data Domain in the order they arrive at the PDCP entity.

[0091] The L field, with a length of 7 bits, represents the first length information. In one possible implementation, the first occurrence of the first length information in the packet header corresponds to the first data field unit in the data field, the second occurrence of the first length information corresponds to the second data field unit in the data field, and so on. In another possible implementation, the first occurrence of the first length information in the packet header corresponds to the second data field unit in the data field, the second occurrence of the first length information corresponds to the third data field unit in the data field, and so on.

[0092] It should be noted that, in one possible implementation, the last data field unit does not need to indicate the corresponding set of L and E fields in the packet header. In another possible implementation, the first data field unit does not need to indicate the corresponding set of L and E fields in the packet header.

[0093] It should be noted that the order of an L-field and an E-field can be either 7 bits of L-field followed by 1 bit of E-field, or 1 bit of E-field followed by 7 bits of L-field.

[0094] The MAC-I field is used to carry the message verification code.

[0095] The sending entity concatenates only small service data units. These small service data units can be service data units with a length less than a first value. The first value can be a fixed value specified by the standard or a network-configurable value. In one possible implementation, the sending entity only concatenates service data units with a length less than 127 or 128 bytes; correspondingly, the length of the L field can be set to no more than 7 bits. The advantage of this design is that by controlling the length of a set of L and E fields to one byte or less, it ensures that each concatenated service data unit only adds one byte of header overhead, saving header overhead compared to schemes that do not limit the length of the L field. In another possible implementation, if the length of a service data unit is less than the first value, the sending entity considers concatenating the service data unit. In another possible implementation, if more than one service data unit has a length less than the first value, the sending entity concatenates the service data units. In yet another possible implementation, when the sending entity constructs packet data units based on service data units, the sending entity concatenates service data units with a length less than the first value.

[0096] It is worth mentioning that, in one possible implementation, the small service data units are concatenated by the SDAP or PDCP transmitting entity. The advantage of this design is that PDCP integrity protection can be performed after multiple small service data units have been concatenated, and since a PDCP packet data unit can contain a MAC-I field, multiple concatenated small SDAP or PDCP service data units only require one MAC-I field. Compared to the method of concatenating small service data units at the RadioLink Control (RLC) transmitting entity (where integrity protection is already performed at the PDCP layer, so each RLC service data unit's corresponding PDCP packet data unit already contains a MAC-I field), this significantly reduces the overhead of the MAC-I field.

[0097] When a sending entity concatenates service data units, it sets the E field in the fixed portion of the header to indicate that a set of L and E fields follows the fixed portion of the header, and sets the first L field appearing in the extended portion of the header to the length of the first data field unit (or service data unit) to be concatenated. If there is a third service data unit to be concatenated, the sending entity sets the first E field appearing in the extended portion of the header to indicate that a set of L and E fields follows this E field and / or the first L field, and sets the second L field appearing in the extended portion of the header to the length of the second data field unit (or service data unit) to be concatenated; if there is no third service data unit to be concatenated, the sending entity sets the first E field appearing in the extended portion of the header to indicate that a data field follows this E field and / or the corresponding L field; and so on.

[0098] In one implementation, the last service data unit of a sending entity concatenated to a packet data unit has no length limit, or the length does not need to be less than a first value.

[0099] When a receiving entity receives a packet data unit, if the E field in the fixed portion of the received header is set to indicate that a set of L and E fields follows the fixed portion of the header, then it is confirmed that the packet data unit is cascaded with multiple service data units. The receiving entity determines the length of the first cascaded service data unit based on the first L field appearing in the extended portion of the received header; it then determines whether a set of L and E fields follows the first E field and / or the first L field, based on the first E field appearing in the extended portion of the received header; and so on. Based on the above information, the receiving node reconstructs the packet data unit into multiple service data units and delivers these multiple service data units to the upper layer.

[0100] In one implementation, when the receiving entity recovers the service data unit based on the packet header of the packet data unit and finds that the length of the last data field unit is greater than the first value, the receiving entity considers that the packet data unit and / or the multiple service data units contained therein have not been correctly received.

[0101] Figure 4D An example method of transmission according to this disclosure is shown. Figure 4D As shown, The second node sends a second message to the first node, the second message being used to provide information related to cascading.

[0102] The second piece of information includes at least one of the following: - First-value related information is used to provide information about service data units that can be cascaded, or to provide threshold information about small service data units that can be cascaded. Possible names for this information include concatenationThreshold, concatenationValue, smallDataThreshold, smallDataValue, smallSDUThreshold, smallSDUValue, SDUThreshold, SDUValue, etc. The beneficial effects of this information are: the network can control the length limit of service data units that can be cascaded; or the network can change the length of service data units that can be cascaded based on conditions (such as channel quality, resource load, etc.). It should be noted that the first-value related information can be configured based on each user equipment, radio bearer, or quality of service stream.

[0103] - Concatenation-related information, used to provide information on activating or deactivating, enabling or disabling, or allowing or disabling concatenation (hereinafter referred to as "activation" or "deactivation"). Possible names for this information include concatenationAllowed, concatenationStatus, concatenationActivationStatus, concatenationActivated, and concatenationEnabled. The beneficial effects of this information are: the network can control whether to activate the concatenation function; the network can decide whether to enable the concatenation function based on conditions (such as channel quality, resource load, etc.). It should be noted that the concatenation-related information can be configured based on each user equipment, radio bearer, or quality of service flow.

[0104] The second information can be included in Radio Resource Control (RRC) messages, with message names such as RRC reconfiguration message, system message, system message block, etc.; or it can be included in Media Access Control (MAC) Element, with information names such as ConcatenationInformation, Concatenation Status, Concatenation Activation / Deactivation, etc.

[0105] In one possible implementation, the cascading-related information is contained in the ConcatenationActivation / Deactivation MAC CE, such as... Figure 4E As shown, the MAC CE contains an 8-bit C field. The Ci field indicates the concatenation activation / deactivation status of radio bearer i or quality of service flow i. Here, i is either an ascending or descending order of radio bearer or quality of service flow identifiers in the configured concatenated radio bearers or quality of service flows, or i is simply the ascending or descending order of radio bearer or quality of service flow identifiers. When the Ci field is set to 1 (or 0), it indicates that the concatenation of radio bearer i or quality of service flow i is activated. When the Ci field is set to 0 (or 1), it indicates that the concatenation of radio bearer i or quality of service flow i is deactivated. It should be noted that the 8-bit C field is only an example; the C field may also be of other lengths such as 32 bits, 64 bits, etc.

[0106] In another possible implementation, the concatenation-related information is contained in the MAC CE, and when the first node receives the MAC CE, it activates / deactivates the concatenation of all radio bearers or quality of service flows.

[0107] The first node identifies or confirms the length limit of the service data unit that can be cascaded based on the first value-related information. In one possible implementation, if the first value-related information indicates 7 bits, the first node confirms that the length of the service data unit that can be cascaded is limited to 127 bytes or 128 bytes, or confirms that the length of the service data unit that can be cascaded does not exceed 127 bytes or 128 bytes. In another possible implementation, if the first value-related information indicates 128 bytes or 64 bytes, the first node confirms that the length of the service data unit that can be cascaded does not exceed or is less than 128 bytes or 64 bytes.

[0108] The first node identifies or confirms whether to activate or deactivate the cascading based on the cascading-related information. When the cascading is activated, the uplink data transmission sent by the first node can cascade multiple small service data units. When the cascading is deactivated, the uplink data transmission sent by the first node cannot cascade multiple service data units.

[0109] In one possible implementation, if concatenation-related information is configured or concatenation is activated, and if the service data unit length is less than the first value, the sending entity considers concatenating the service data units. In another possible implementation, if concatenation-related information is configured or concatenation is activated, and if more than one service data unit has a length less than the first value, the sending entity concatenates the service data units. In yet another possible implementation, when the sending entity constructs packet data units based on service data units, if concatenation-related information is configured or concatenation is activated, the sending entity concatenates service data units with a length less than the first value.

[0110] In one possible implementation, if the MAC entity of the first node receives a MAC CE that activates concatenation of a radio bearer or a quality of service flow, the MAC entity will indicate the concatenation activation information of the radio bearer or quality of service flow to the upper layer; if the MAC entity of the first node receives a MAC CE that deactivates concatenation of a radio bearer or a quality of service flow, the MAC entity will indicate the deactivation information of the concatenation deactivation of the radio bearer or quality of service flow to the upper layer.

[0111] In another possible implementation, if the MAC entity of the first node receives a MAC CE to activate concatenation, the MAC entity will indicate the concatenation activation information to the upper layer; if the MAC entity of the first node receives a MAC CE to deactivate concatenation, the MAC entity will indicate the deactivation information to the upper layer.

[0112] In one possible implementation, if information related to the concatenation activation of a radio bearer or quality of service flow is indicated to the sending entity (such as a PDCP entity or SDAP entity) of the first node, the sending entity activates the concatenation of the radio bearer or quality of service flow; if information related to the deactivation of the concatenation of a radio bearer or quality of service flow is indicated to the sending entity of the first node, the sending entity deactivates the concatenation of the radio bearer or quality of service flow.

[0113] In another possible implementation, if the relevant information for cascading activation is indicated to the sending entity of the first node, the sending entity activates the cascading; if the relevant information for cascading deactivation is indicated to the sending entity of the first node, the sending entity deactivates the cascading.

[0114] Figure 4FAn example method of transmission according to this disclosure is shown. Figure 4F As shown, The second node sends a third message to the first node, the third message being used to provide information related to cascading.

[0115] The third information mentioned above includes at least one of the following: - Configuration information for the first timer, used by the sending entity to perform cascading operations. This information may be named concatenationTimer, transmittingTimer, etc. (hereinafter referred to as "concatenationTimer"). The beneficial effect of the first timer is that the sending entity can decide how to perform cascading operations based on the timer's running status, thereby achieving more reasonable cascading of service data units.

[0116] - Concatenation maximum value information is used to provide the sending entity with the maximum number of service data units that can be concatenated to a single packet data unit, or to limit the maximum number of service data units that can be concatenated to a single packet data unit. This information may be named maxConcatenationNumber, maxConcatenateThreshold, maxConcatNumber, maxConcatThreshold, etc. (hereinafter, "maxConcatenationNumber" will be used consistently). The beneficial effect of this concatenation maximum value information is that the sending entity can limit the maximum number of service data units that can be concatenated to a single packet data unit, reducing the need for subsequent segmentation of the packet data unit due to excessively large packet data units, thereby achieving more reasonable concatenation of service data units.

[0117] - The first timer-related step size information is used by the sending entity to perform cascading operations, or to perform related operations when the sending entity runs the first timer and receives a qualified service data unit. This information may be named timerDecreaseStep, timerReduceStep, timeIncreaseDelta, timeAddDelta, etc. (hereinafter, it will be consistently described as "timerReduceStep"). The beneficial effect of the first timer-related step size information is that when the sending entity runs the first timer and receives a qualified service data unit, it can speed up the timeout of the first timer, thereby reducing the number of service data units cascaded to a single data packet. This reduces the need for subsequent segmentation of the data packet due to its large size, thus achieving more reasonable cascading of service data units.

[0118] It should be noted that the configuration information for the first timer can be configured based on each user equipment, radio bearer, or quality of service stream. In one possible implementation, the concatenationTimer configures the duration of the first timer. In another possible implementation, the concatenationTimer configures the duration of the first timer for a radio bearer. In yet another possible implementation, the concatenationTimer configures the duration of the first timer for a quality of service stream.

[0119] It should be noted that the concatenation maximum value information can be configured based on each user equipment, radio bearer, or quality of service stream. In one possible implementation, `maxConcatenationNumber` configures the maximum number of service data units that can be concatenated to a packet data unit. In another possible implementation, `maxConcatenationNumber` configures the maximum number of service data units that can be concatenated to a packet data unit for a radio bearer. In yet another possible implementation, `maxConcatenationNumber` configures the maximum number of service data units that can be concatenated to a packet data unit for a quality of service stream.

[0120] It should be noted that the step size information related to the first timer can be configured based on each user equipment, radio bearer, or quality of service flow. In one possible implementation, the timerReduceStep configures the duration reduction step size of the first timer. In another possible implementation, the timerReduceStep configures the duration reduction step size of the first timer for a radio bearer. In yet another possible implementation, the timerReduceStep configures the duration reduction step size of the first timer for a quality of service flow.

[0121] The third information can be included in Radio Resource Control (RRC) messages, with message names such as RRC reconfiguration message, system message, system message block, etc.

[0122] The third information is configured to the sending entity of the first node. The sending entity of the first node needs to maintain the first timer.

[0123] In one possible implementation, if the value of concatenationTimer is configured to 0, it indicates that concatenation is not configured, or that the duration of the first timer is infinite.

[0124] In one possible implementation, when a sending entity receives a service data unit from an upper layer, if a first timer is not running, the first timer, which is associated with the service data unit, is started. If the sending entity receives other service data units from the upper layer before or during the first timer's execution, the received service data units can be concatenated. When the first timer expires, the sending entity combines the concatenated service data units into a single packet data unit and sends it to the lower layer.

[0125] In another possible implementation, when the sending entity receives a service data unit (Data Unit) with a length less than the first value from the upper layer, if the first timer is not running, the first timer is started, and the first timer is associated with the service data unit. Before or during the execution of the first timer, if the sending entity receives other service data units with a length less than the first value from the upper layer, the received multiple service data units can be concatenated. When the first timer expires, the sending entity combines the concatenated service data units into a single data packet and sends it to the lower layer. Before or during the execution of the first timer, if the sending entity receives other service data units with a length greater than the first value from the upper layer, the service data units with a length greater than the first value are directly combined into a single data packet and sent to the lower layer.

[0126] In another possible implementation, when the sending entity receives a service data unit (FMU) with a length less than the first value from the upper layer, if the first timer is not running, the first timer is started and associated with the FMU. Before or during the first timer's expiration, if the sending entity receives other FMUs with a length less than the first value from the upper layer, the received FMUs can be concatenated. When the first timer expires, the sending entity groups the concatenated FMUs into a single data packet and sends it to the lower layer. Before or during the first timer's expiration, if the sending entity receives other FMUs with a length greater than the first value from the upper layer, it first groups the already concatenated FMUs into a single data packet and sends it to the lower layer, then groups the FMUs with a length greater than the first value into another data packet and sends it to the lower layer. Afterward, the sending entity stops and resets the first timer.

[0127] In another possible implementation, the sending entity maintains a state variable: a first quantity, used to record the number of service data units being cascaded. When the sending entity receives a service data unit from the upper layer, if the first timer is not running, it starts the first timer, which is associated with the service data unit, and then sets the first quantity to 0 or 1. Before or during the first timer's expiration, if the sending entity receives other service data units from the upper layer, it can perform cascading on the received service data units, then increment the first quantity by 1, and then determine whether the updated first quantity is greater than the cascading maximum value information: if it is greater, the sending entity stops and resets the first timer, combines the cascaded service data units into a single data packet, and sends it to the lower layer; otherwise, it continues to run the first timer. When the first timer expires, the sending entity combines the cascaded service data units into a single data packet and sends it to the lower layer.

[0128] In another possible implementation, the sending entity maintains a state variable: a first quantity, used to record the number of service data units being cascaded. When the sending entity receives a service data unit with a length less than the first value from the upper layer, if the first timer is not running, it starts the first timer, which is associated with the service data unit, and then sets the first quantity to 0 or 1. Before or during the first timer's expiration, if the sending entity receives other service data units with a length less than the first value from the upper layer, it can cascade the received service data units, then increment the first quantity by 1, and then determine whether the updated first quantity is greater than the cascade maximum value information: if it is, the sending entity stops and resets the first timer, combines the cascaded service data units into a single data packet, and sends it to the lower layer; otherwise, it continues to run the first timer. When the first timer expires, the sending entity combines the cascaded service data units into a single data packet and sends it to the lower layer. Before or during the first timer's expiration, if the sending entity receives other service data units with a length greater than the first value from the upper layer, it directly combines the service data units with a length greater than the first value into a single data packet and sends it to the lower layer.

[0129] In another possible implementation, the sending entity maintains a state variable: a first quantity, used to record the number of service data units being cascaded. When the sending entity receives a service data unit with a length less than the first value from the upper layer, if the first timer is not running, the first timer is started and associated with the service data unit, and then the first quantity is set to 0 or 1. Before or during the first timer's expiration, if the sending entity receives other service data units with a length less than the first value from the upper layer, the received service data units can be cascaded, and then the first quantity is incremented by 1. The updated first quantity is then checked against the cascaded maximum value information: if it is, the sending entity stops and resets the first timer, combines the cascaded service data units into a single data packet, and sends it to the lower layer; otherwise, the first timer continues to run. When the first timer expires, the sending entity combines the cascaded service data units into a single data packet and sends it to the lower layer. If, before or during the expiration of the first timer, the sending entity receives other service data units with a length greater than the first value from the upper layer, it first combines the multiple cascaded service data units into a single packet data unit and sends it to the lower layer. Then, it combines the service data units with a length greater than the first value into another packet data unit and sends it to the lower layer. After that, the sending entity stops and resets the first timer.

[0130] In another possible implementation, the sending entity maintains a state variable: a first duration, used to record the duration of the first timer. When the sending entity receives a service data unit from the upper layer, if the first timer is not running, it starts the first timer, which is associated with the service data unit, and then sets the first duration to the value configured by `concatenationTimer`. Before or during the first timer's timeout, if the sending entity receives other service data units from the upper layer, it can perform concatenation on the received service data units. Then, it subtracts `timerReduceStep` from the first duration (note: the updated first duration is used by the sending entity to determine if the running first timer has timed out, i.e., whether the first timer's running time exceeds the updated first duration), and then determines whether the updated first duration is less than the first timer's running time: if it is less, the sending entity stops and resets the first timer, combines the concatenated service data units into a single data packet, and sends it to the lower layer; otherwise, it continues running the first timer. When the first timer times out, the sending entity combines the concatenated service data units into a single data packet and sends it to the lower layer.

[0131] In another possible implementation, the sending entity maintains a state variable: a first duration, used to record the duration of the first timer. When the sending entity receives a service data unit with a length less than the first value from the upper layer, if the first timer is not running, it starts the first timer, which is associated with the service data unit, and then sets the first duration to the value configured by `concatenationTimer`. Before or during the first timer's timeout, if the sending entity receives other service data units with a length less than the first value from the upper layer, it can perform concatenation on the received service data units. Then, it subtracts `timerReduceStep` from the first duration (Note: the updated first duration is used by the sending entity to determine whether the running first timer has timed out, i.e., whether the running time of the first timer exceeds the updated first duration), and then determines whether the updated first duration is less than the running time of the first timer: if it is less, the sending entity stops and resets the first timer, combines the concatenated service data units into a single data packet, and sends it to the lower layer; otherwise, it continues to run the first timer. When the first timer times out, the sending entity combines the concatenated service data units into a single data packet and sends it to the lower layer. If, before or during the first timer expires, the sending entity receives other service data units with a length greater than the first value from the upper layer, it directly forms a packet data unit from the service data units with a length greater than the first value and sends it to the lower layer.

[0132] In another possible implementation, the sending entity maintains a state variable: a first duration, used to record the duration of the first timer. When the sending entity receives a service data unit with a length less than the first value from the upper layer, if the first timer is not running, it starts the first timer, which is associated with the service data unit, and then sets the first duration to the value configured by `concatenationTimer`. Before or during the first timer's timeout, if the sending entity receives other service data units with a length less than the first value from the upper layer, it can perform concatenation on the received service data units. Then, it subtracts `timerReduceStep` from the first duration (Note: the updated first duration is used by the sending entity to determine whether the running first timer has timed out, i.e., whether the running time of the first timer exceeds the updated first duration), and then determines whether the updated first duration is less than the running time of the first timer: if it is less, the sending entity stops and resets the first timer, combines the concatenated service data units into a single data packet, and sends it to the lower layer; otherwise, it continues to run the first timer. When the first timer times out, the sending entity combines the concatenated service data units into a single data packet and sends it to the lower layer. If, before or during the expiration of the first timer, the sending entity receives other service data units with a length greater than the first value from the upper layer, it first combines the multiple cascaded service data units into a single packet data unit and sends it to the lower layer. Then, it combines the service data units with a length greater than the first value into another packet data unit and sends it to the lower layer. After that, the sending entity stops and resets the first timer.

[0133] It should be noted that the above-described various implementation methods can also be used in combination.

[0134] Figure 4G An example method of transmission according to this disclosure is shown. Figure 4G As shown, Step 1: The second node sends the second information and / or the third information to the first node, which is used by the first node to configure cascading-related information.

[0135] Step 2: The sending entity of the first node performs concatenation based on the content of the second information and / or the third information, including the first information in the packet data unit (packet header) and transmitting the packet data unit to the second node.

[0136] Figure 5 This is a block diagram of the fifth node according to the present invention.

[0137] refer to Figure 5According to this disclosure, the fourth node may be a user equipment, which may include a transceiver 410 and a processor 420, wherein the transceiver 410 is coupled to the processor 420. Optionally, the network node may also include a memory 430. The transceiver 410, processor 420, and memory 430 are configured to perform the operations of the methods and / or embodiments of the present invention. Although the transceiver 410, processor 420, and memory 430 are shown as separate entities, they may be implemented as a single entity, such as a single chip. The transceiver 410, processor 420, and memory 430 may be electrically connected or coupled to each other. The transceiver 410 may transmit signals to and receive signals from other network nodes, such as other UEs, base stations, or core network equipment (e.g., AMF). The processor 420 may include one or more processing units and may control the UE to perform operations and / or functions according to one of the above embodiments. The memory 430 may store instructions for implementing the operations and / or functions of one of the above embodiments.

[0138] According to one aspect of this disclosure, a method is provided performed by a first node in a wireless communication network, the method comprising: receiving third information from a second node, the third information including information of a first timer associated with cascading and information of a cascading maximum value; and, while the first timer is running, performing a cascading-related operation on a received service data unit based on the information of the cascading maximum value.

[0139] In a further embodiment, the method further includes: receiving second information from a second node, wherein the second information includes at least one of the following: first value-related information, used to indicate threshold value-related information of small service data units that can be cascaded; and related information for activating or deactivating cascading.

[0140] In a further embodiment, the method further includes: maintaining state variables, the state variables including at least one of the following: a first quantity, used to record the number of service data units being cascaded; and a first duration, used to record the duration of the first timer.

[0141] In a further embodiment, at least one of the following is also included: when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is associated with the service data unit; when the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded; when the first timer times out, the cascaded service data units are combined into a grouped data unit and sent to the lower layer.

[0142] In a further embodiment, it further includes at least one of the following: when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, the first timer being associated with the service data unit, and then the first quantity is set to 0 or 1; while the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded, and then the first quantity is incremented by 1; if the updated first quantity is greater than the cascaded maximum value related information, the first timer is stopped and reset, and the cascaded multiple service data units are combined into a grouped data unit and sent to the lower layer; when a service data unit is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is set to 0 or 1; The first timer is associated with the service data unit, and then the first duration is set to the value configured by the relevant configuration information of the first timer. When the first timer is running, if other service data units are received from the upper layer, the received service data units are cascaded. Then, the first duration is subtracted from the value configured by the relevant step size information of the first timer. If the updated first duration is less than the running time of the first timer, the first timer is stopped and reset. The cascaded service data units are combined into a group data unit and sent to the lower layer. The relevant step size information of the first timer is included in the third information. When the first timer times out, the cascaded service data units are combined into a group data unit and sent to the lower layer.

[0143] In a further embodiment, at least one of the following is also included: when a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, and the first timer is associated with the service data unit; when the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are cascaded; when the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer; when the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a packet data unit and sent to the lower layer, then the service data units with a length greater than the first value are combined into another packet data unit and sent to the lower layer, and then the first timer is stopped and reset; when the first timer times out, the multiple cascaded service data units are combined into a packet data unit and sent to the lower layer.

[0144] In a further embodiment, at least one of the following is also included: when a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, the first timer is associated with the service data unit, and then the first quantity is set to 0 or 1; when the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are concatenated, and then the first quantity is incremented by 1; if the updated first quantity is greater than the concatenation maximum value related information, the first timer is stopped and reset, and the multiple concatenated service data units are combined into a group data unit and sent to the lower layer; When the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer. When the first timer is running, if other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a packet data unit and sent to the lower layer, then the service data units with a length greater than the first value are combined into another packet data unit and sent to the lower layer, and then the first timer is stopped and reset. When a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started, associated with the service data unit, and then the first duration is set to the value configured in the relevant configuration information of the first timer. When the first timer is running, if other service data units with a length less than the first value are received from the upper layer, the received service data units are cascaded, and then the... The first duration is subtracted from the value configured by the first timer's related step size information. If the updated first duration is less than the running time of the first timer, the first timer is stopped and reset, and the cascaded service data units are combined into a single data packet and sent to the lower layer. The first timer's related step size information is included in the third information. During the first timer's operation, if other service data units with a length greater than the first value are received from the upper layer, these service data units are directly combined into a single data packet and sent to the lower layer. If, during the first timer's operation, other service data units with a length greater than the first value are received from the upper layer, the already cascaded service data units are first combined into a single data packet and sent to the lower layer, then the service data units with a length greater than the first value are combined into another single data packet and sent to the lower layer, and then the first timer is stopped and reset. When the first timer times out, the cascaded service data units are combined into a single data packet and sent to the lower layer.

[0145] In a further embodiment, it further includes at least one of the following: if concatenation is activated and if the length of the service data unit is less than the first value, then consider concatenating the service data unit; if concatenation is activated and if more than one service data unit has a length less than the first value, then concatenate the service data units; if concatenation is activated, concatenate service data units with a length less than the first value.

[0146] In a further embodiment, at least one of the following is included: if the relevant information for activating the cascade is indicated, then the cascade is activated; if the relevant information for deactivating the cascade is indicated, then the cascade is deactivated.

[0147] In a further embodiment, the information related to the activation or deactivation cascade is included in the transmission of the media access control layer control unit.

[0148] In a further embodiment, at least one of the following is also included: if the media access control layer entity receives an instruction from the control unit to activate cascading, the media access control layer entity will indicate cascading activation information to the upper layer; if the media access control layer entity receives an instruction from the control unit to deactivate cascading, the media access control layer entity will indicate cascading deactivation information to the upper layer.

[0149] In a further embodiment, it further includes at least one of the following: if the length of a service data unit is less than the first value, then consider cascading the service data units; if more than one service data unit has a length less than the first value, then cascade the service data units; cascade service data units with a length less than the first value.

[0150] In a further embodiment, the method further includes: sending first information to a second node, the first information being used by the second node to recover a packet data unit into multiple service data units; wherein the first information includes at least one first length information, the first length information indicating the byte length of the corresponding service data unit in the related packet data unit.

[0151] In a further embodiment, the length of the first length information is 7 bits or less.

[0152] Figure 6 This is a block diagram of network nodes in a network according to this disclosure.

[0153] Network nodes in the network can be used to implement the first node, second node, or third node, etc., in this invention. (See reference) Figure 6The network node according to this disclosure includes a transceiver 510 and a processor 520, wherein the transceiver 510 is coupled to the processor 520. Optionally, the network node may also include a memory 530. The transceiver 510, processor 520, and memory 530 are configured to perform the operations of the methods and / or embodiments of the present invention. Although the transceiver 510, processor 520, and memory 530 are shown as separate entities, they can be implemented as a single entity, such as a single chip. The transceiver 510, processor 520, and memory 530 may be electrically connected or coupled to each other. The transceiver 510 can transmit signals to and receive signals from other network nodes, such as UEs, other base stations, parts of base stations, or core network equipment (e.g., AMF). The processor 520 may include one or more processing units and can control the network node to perform operations and / or functions according to one of the above embodiments. The memory 530 may store instructions for implementing the operations and / or functions of one of the above embodiments.

[0154] According to another aspect of this disclosure, a method is provided performed by a second node in a wireless communication network, the method comprising: initiating a process for modifying a radio resource control connection; and sending third information to a first node, wherein the third information includes information about a first timer associated with cascading and information about a cascading maximum value; wherein the cascading-related operation of the first node is performed while the first timer is running and based on the information about the cascading maximum value.

[0155] In a further embodiment, the method further includes: sending second information to the first node, wherein the second information includes at least one of the following: first value-related information, used to indicate threshold value-related information of small service data units that can be cascaded; and related information for activating or deactivating cascading.

[0156] In a further embodiment, the method further includes: receiving first information from a first node, the first information being used by the second node to recover a packet data unit into multiple service data units; wherein the first information includes at least one first length information, the first length information indicating the byte length of the corresponding service data unit in the associated packet data unit.

[0157] In a further embodiment, the length of the first length information is 7 bits or less.

[0158] According to embodiments of this disclosure, a computer-readable storage medium storing instructions may also be provided, wherein when the instructions are executed by at least one processor, they cause the at least one processor to perform any one of the methods described above according to exemplary embodiments of this disclosure. Examples of computer-readable storage media herein include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disc storage, hard disk drive (HDD), solid-state drive (SSD), card storage (such as multimedia cards, secure digital (SD) cards, or ultra-fast digital (XD) cards), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid-state drive, and any other device configured to store a computer program and any associated data, data files, and data structures in a non-transitory manner and to provide the computer program and any associated data, data files, and data structures to a processor or computer so that the processor or computer can execute the computer program. The instructions or computer program in the aforementioned computer-readable storage medium can run in an environment deployed in computer devices such as clients, hosts, agent devices, servers, etc. Furthermore, in one example, the computer program and any associated data, data files, and data structures are distributed across a networked computer system, such that the computer program and any associated data, data files, and data structures are stored, accessed, and executed in a distributed manner through one or more processors or computers.

[0159] Those skilled in the art will understand that the illustrative embodiments described above are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein can be combined in any combination. Furthermore, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that aspects of the invention disclosed herein, as generally described herein and illustrated in the accompanying drawings, can be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are contemplated herein.

[0160] Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and steps described herein can be implemented in hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in the form of sets of functions. Whether such sets of functions are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described sets of functions in different ways for each specific application, but such design decisions should not be construed as departing from the scope of this application.

[0161] The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0162] The steps of the methods or algorithms described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read and write information to / from the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0163] In one or more exemplary designs, the functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or lines of code on or transmitted via a computer-readable medium. Computer-readable media includes both computer storage media and communication media, the latter including any medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0164] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application. The scope of protection of this application is determined by the appended claims.

Claims

1. A method performed by a first node in a wireless communication network, the method comprising: Receive third information from the second node, the third information including information about the first timer associated with the cascade and information about the cascade maximum value; as well as During the execution of the first timer, cascading related operations are performed on the received service data units based on the information of the cascading maximum value.

2. The method according to claim 1, further comprising: Receive second information from the second node, wherein the second information includes at least one of the following: The first value-related information is used to indicate the threshold value-related information of small service data units that can be cascaded; Information related to activating or deactivating cascades.

3. The method according to claim 1, further comprising: Maintain state variables, which include at least one of the following: The first quantity is used to record the number of service data units that are cascaded. The first duration is used to record the duration of the first timer.

4. The method of claim 1, further comprising at least one of the following: When a service data unit is received from the upper layer, if the first timer is not running, the first timer is started and associated with the service data unit. If other service data units are received from the upper layer during the operation of the first timer, then the received service data units are cascaded. When the first timer expires, the cascaded service data units are combined into a single data packet and sent to the lower layer.

5. The method according to claims 1 and 3, further comprising at least one of the following: When a service data unit is received from the upper layer, if the first timer is not running, the first timer is started and associated with the service data unit, and then the first quantity is set to 0 or 1. If other service data units are received from the upper layer during the operation of the first timer, the received service data units are concatenated, and then the first quantity is incremented by 1. If the updated first quantity is greater than the relevant information of the concatenation maximum value, the first timer is stopped and reset, and the multiple concatenated service data units are combined into a group data unit and sent to the lower layer. When a service data unit is received from the upper layer, if the first timer is not running, the first timer is started. The first timer is associated with the service data unit, and then the first duration is set to the value configured by the relevant configuration information of the first timer. During the execution of the first timer, if other service data units are received from the upper layer, the received service data units are concatenated. Then, the first duration is subtracted from the value configured by the step size information of the first timer. If the updated first duration is less than the running time of the first timer, the first timer is stopped and reset. The concatenated service data units are then grouped into a single data unit and sent to the lower layer. The step size information related to the first timer is included in the third information; When the first timer expires, the cascaded service data units are combined into a single data packet and sent to the lower layer.

6. The method of claim 2, further comprising at least one of the following: When a service data unit with a length smaller than the first value is received from the upper layer, if the first timer is not running, the first timer is started and associated with the service data unit. If, during the operation of the first timer, other service data units with a length shorter than the first value are received from the upper layer, then the received service data units are cascaded. If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer. If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a single data packet and sent to the lower layer. Then, the service data units with a length greater than the first value are combined into another data packet and sent to the lower layer. After that, the first timer is stopped and reset. When the first timer expires, the cascaded service data units are combined into a single data packet and sent to the lower layer.

7. The method according to claims 2 and 3, further comprising at least one of the following: When a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started and associated with the service data unit, and then the first quantity is set to 0 or 1. If, during the operation of the first timer, other service data units with lengths shorter than the first value are received from the upper layer, the received service data units are concatenated, and then the first quantity is incremented by 1. If the updated first quantity is greater than the relevant information of the concatenated maximum value, the first timer is stopped and reset, and the multiple concatenated service data units are combined into a grouped data unit and sent to the lower layer. If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer. If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a single data packet and sent to the lower layer. Then, the service data units with a length greater than the first value are combined into another data packet and sent to the lower layer. After that, the first timer is stopped and reset. When a service data unit with a length less than the first value is received from the upper layer, if the first timer is not running, the first timer is started. The first timer is associated with the service data unit, and then the first duration is set to the value configured by the relevant configuration information of the first timer. During the execution of the first timer, if other service data units with a length shorter than the first value are received from the upper layer, the received service data units are concatenated. Then, the first duration is subtracted from the value configured in the first timer's step size information. If the updated first duration is less than the execution time of the first timer, the first timer is stopped and reset. The concatenated service data units are then grouped into a single data packet and sent to the lower layer. The step size information related to the first timer is included in the third information; If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the service data units with a length greater than the first value are directly combined into a packet data unit and sent to the lower layer. If, during the operation of the first timer, other service data units with a length greater than the first value are received from the upper layer, the multiple cascaded service data units are first combined into a single data packet and sent to the lower layer. Then, the service data units with a length greater than the first value are combined into another data packet and sent to the lower layer. After that, the first timer is stopped and reset. When the first timer expires, the cascaded service data units are combined into a single data packet and sent to the lower layer.

8. The method of claim 2, further comprising at least one of the following: If cascading is activated, and if the length of the service data unit is less than the first value, then consider cascading the service data unit. If cascading is activated, and if more than one service data unit has a length less than the first value, then cascading service data units; If cascading is activated, the cascading length is less than the first value of the service data unit.

9. The method of claim 2, further comprising at least one of the following: If the relevant information for activating the cascade is indicated, then the cascade is activated; If the relevant information for deactivating the cascade is indicated, then the cascade is deactivated.

10. The method of claim 2, wherein the information related to the activation or deactivation cascade is included in the transmission of the media access control layer control unit.

11. The method of claim 10, further comprising at least one of the following: If the media access control layer entity receives an instruction from the control unit to activate cascading, the media access control layer entity will instruct the upper layer with cascading activation information. If the media access control layer entity receives an instruction from the control unit to deactivate the cascading, the media access control layer entity will instruct the upper layer to deactivate the cascading information.

12. The method of claim 2, further comprising at least one of the following: If the length of the service data unit is less than the first value, then consider cascading the service data units; If more than one service data unit has a length less than the first value, then cascade the service data units; Service data units with a cascade length less than the first value.

13. The method according to claim 1 or 12, further comprising: Send first information to the second node, the first information being used by the second node to restore a packet data unit into multiple service data units; The first information includes at least one first length information, which indicates the byte length of the corresponding service data unit in the related packet data unit.

14. The method according to claim 13, wherein, The length of the first length information is 7 bits or less.

15. A method performed by a second node in a wireless communication network, the method comprising: Initiate the process of modifying the wireless resource control connection; as well as Send third information to the first node, wherein the third information includes information about a first timer associated with the cascading and information about the cascading maximum value; wherein the cascading-related operation of the first node is performed while the first timer is running and based on the information about the cascading maximum value.

16. The method of claim 15, further comprising: Send a second message to the first node, wherein the second message includes at least one of the following: The first value-related information is used to indicate the threshold value-related information of small service data units that can be cascaded; Information related to activating or deactivating cascades.

17. The method according to claim 15 or 16, further comprising: The first node receives first information, which is used by the second node to restore a packet data unit into multiple service data units; The first information includes at least one first length information, which indicates the byte length of the corresponding service data unit in the related packet data unit.

18. The method according to claim 17, wherein, The length of the first length information is 7 bits or less.

19. A first node device in a wireless communication network, the device comprising: A transceiver is configured to send and receive signals; and A processor, coupled to the transceiver and configured to perform the method as described in any one of claims 1 to 14.

20. A second node device in a wireless communication network, the device comprising: A transceiver, configured to transmit and receive signals; and A processor, coupled to the transceiver and configured to perform the method as described in any one of claims 15 to 18.

Images