Apparatus and method for managing congestion and burst status in wireless communication system

Abstract

The present disclosure relates to a 5th-Generation (5G) or 6th-Generation (6G) communication system for supporting higher data transmission rates. An apparatus and method are provided. The method includes identifying a start of a congestion state or a burst state, the congestion state based on insufficient resources for uplink data, the burst state relating to an increase in uplink data; determining whether to perform a drop operation on a protocol data unit (PDU) of uplink data or a PDU set including at least one PDU based on the identification of the start of the congestion state or the burst state; performing a drop operation on the PDU or the set of PDUs based on the identification according to a priority of a configuration based on the importance of the PDU or the set of PDUs; and stopping performing the discard operation based on an end of the congestion state or the burst state.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly to a device and method for identifying and managing congestion or emergency status in a wireless communication system. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be realized not only in the "Sub 6 Gigahertz (GHz)" frequency band (such as 3.5GHz) but also in the "above 6GHz" frequency band (including 28GHz and 39GHz) known as mmWave. In addition, in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth lower than 5G mobile communication technology, the implementation of the sixth generation (6G) mobile communication technology (called a super 5G system) in the terahertz (THz) band (such as the 95GHz to 3THz band) is considered.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet the performance requirements of enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC), the following technologies have been continuously standardized: beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance; support for parameter sets (e.g., operating multiple subcarrier spacings) for efficient use of millimeter wave resources and dynamic operation of time slot formats; initial access technology to support multi-beam transmission and broadband; definition and operation of bandwidth parts (BWPs); new channel coding methods, such as low-density parity-check (LDPC) codes for large amounts of data transmission and polarization codes for highly reliable transmission of control information; L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Discussions are underway on improvements and performance enhancements to initial 5G mobile communications technologies for the services they will support, and physical layer standardization has been carried out for related technologies: for example, vehicle-to-everything (V2X) technology, which assists autonomous vehicles in driving decisions and improves user convenience based on information transmitted by vehicles about their location and status; New Radio Unlicensed (NR-U) technology, which aims to make system operations compliant with various regulatory requirements for unlicensed frequency bands; NR user equipment (UE) energy-saving technology; non-terrestrial network (NTN) technology, which is user equipment-satellite direct communication technology, used to provide coverage in areas where communication with terrestrial networks is not possible; and positioning technology.

[0005] In addition, standardization of air interface architecture / protocols is ongoing for technologies such as: Industrial Internet of Things (IIoT) to support new services through interworking and convergence with other industries; Integrated Access and Backhaul (IAB) to provide nodes for network service area extension by supporting integration of wireless backhaul links and access links; Mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover; and two-step random access (two-step random access channel (RACH) for NR) to simplify random access procedures. Standardization is also ongoing in system architecture / services for technologies such as: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies; and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponentially growing number of networked devices will be connected to the communication network, so the functions and performance of 5G mobile communication systems are expected to be enhanced, and the integrated operation of networked devices will also be essential. To this end, new research is planned related to the following technologies: extended reality (XR) for effective support of augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvement and complexity reduction using artificial intelligence (AI) and machine learning (ML); AI service support; metaverse services; and drone communications.

[0007] In addition, the development of 5G mobile communication systems adopts new waveforms, full-dimensional MIMO (FD-MIMO) and array antennas to ensure the coverage of 6G mobile communication technology in the terahertz band. The following technologies can become the basis: multi-antenna transmission technology such as massive antennas; metamaterial-based lenses and antennas for improving the coverage of terahertz band signals; high-dimensional spatial multiplexing technology using orbital angular momentum (OAM); reconfigurable smart surface (RIS) technology; full-duplex technology for improving the frequency efficiency and system network of 6G mobile communication technology; satellites; AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and end-to-end development to achieve system optimization by internalizing AI-supported functions; and next-generation distributed computing technology that uses ultra-high-performance communication and computing resources to realize complex services beyond the computing power limit of terminals.

[0008] As mentioned above, with the development of wireless systems, open source tools and hacker techniques have emerged that can easily create fake base stations and mobile communication terminals. With the development of these technologies, it is easy for attackers to use fake base stations to launch denial of service (DoS) attacks on users and communication service providers. Therefore, a method is needed to prevent DoS attacks initiated by fake base stations.

[0009] The above information is provided as background information only to assist in understanding the present disclosure. No determination has been made and no assertion has been made as to whether any of the above may be used as prior art related to the present disclosure. Summary of the invention

[0010]

Technical solution

[0011] Various aspects of the present disclosure are intended to solve at least the above-mentioned problems and / or disadvantages and provide at least the following advantages. Therefore, one aspect of the present disclosure is to provide a device and method for identifying and managing congestion and burst states in a wireless communication system that do not meet the requirements of high speed and low latency of applications or XR services, so as to effectively provide services.

[0012] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0013] According to one aspect of the present disclosure, a method performed by a terminal in a wireless communication system is provided, the method comprising: identifying the beginning of a congestion state or a burst state, the congestion state being based on insufficient resources for uplink data, the burst state being associated with an increase in uplink data; based on the identification of the beginning of the congestion state or the burst state, identifying whether to perform a discard operation on a protocol data unit PDU of the uplink data or a PDU set including at least one PDU; based on the identification, performing a discard operation on the PDU or the PDU set according to a priority configured based on the importance of the PDU or the PDU set; and performing a discard operation based on the end of the congestion state or the burst state.

[0014] According to one embodiment of the present disclosure, in the method, identifying the start of a congestion state or a burst state further includes: receiving a message indicating the start of a congestion state or a burst state from a base station, and the start of the congestion state or the burst state is identified based on the message.

[0015] According to another embodiment of the present disclosure, in the method, a message indicating the start of a congestion state or a burst state is received in the following situations: the terminal sends a buffer status report BSR for uplink data transmission to the base station, and the base station does not allocate resources for the uplink data within a predetermined time from the time point when the base station receives the BSR; the terminal is configured to report the uplink data rate to the base station and the terminal reports the uplink data rate to the base station, and from the time point before the preconfigured time to the predetermined time point, the uplink data rate through which the terminal sends the resources allocated from the base station is lower than the reported uplink data rate; the terminal sends a BSR for uplink data transmission for sending data amount, and the amount of data that can be sent through the resources allocated by the base station within the preconfigured time from the time point when the base station receives the BSR is less than the amount of data sent through the BSR; the uplink data rate related to the uplink data of the terminal is higher than the preconfigured data rate; the uplink data rate related to the uplink data of the terminal is higher than the recommended data rate configured by the base station; or the base station receives a report on a congestion state or a burst state from the terminal.

[0016] According to another embodiment of the present disclosure, in the method, the beginning of a congestion state or a burst state is identified in the following circumstances: within a preconfigured time from a time point when a packet data convergence protocol PDCP or a terminal configured to identify a congestion state receives a PDCP service data unit SDU from a higher layer of the terminal, the base station does not allocate resources for uplink data; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number or rate of PDUs or PDU sets discarded by a timer for a discard operation exceeds a reference value; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets discarded by a timer for a discard operation sequentially exceeds a reference value; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets discarded by a timer for a discard operation sequentially exceeds a reference value; Among the received PDUs or PDU sets, the number or rate of discarded PDUs or PDU sets determined by the PDCP sequence number SN exceeds a reference value; the terminal is configured to report the uplink data rate to the base station and the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time point to a predetermined time point, the uplink data rate that can be sent through the resources allocated from the base station to the terminal is lower than the reported uplink data rate; the terminal sends a BSR for sending data to the base station and for sending data volume, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the terminal sends the BSR is less than the amount of data sent through the BSR; the uplink data rate related to the uplink data of the terminal is higher than the preconfigured data rate; the uplink data rate related to the uplink data of the terminal is higher than the recommended data rate configured by the base station; an indication of a congestion state or a burst state is received from a high layer of the terminal, or the terminal receives an indication of a congestion state or a burst state from the base station.

[0017] According to another embodiment of the present disclosure, the method further includes sending information related to whether the terminal supports a function of identifying a congestion state or a sudden state of the terminal to the base station.

[0018] According to another embodiment of the present disclosure, in a method, according to the method of claim 5, wherein the information related to whether the terminal supports the terminal's identification function of a congestion state or a burst state includes at least one of the following: information related to whether the congestion state identification function is supported, information related to the type of supported congestion state identification conditions, information related to whether the burst state identification function is supported, information related to the type of supported burst state identification conditions, information related to the type of information that can be received and used by a higher layer, or information related to instructions or reports that can be sent / received to / from a higher layer.

[0019] According to another embodiment of the present disclosure, the method further includes sending information indicating the end of the burst state to the base station.

[0020] According to another embodiment of the present disclosure, the method further includes: based on the identification related to the start of the congestion state or the burst state, sending a report related to the congestion state or the burst state to the base station.

[0021] According to another embodiment of the present disclosure, determining whether to perform the discard operation corresponds to determining whether to perform the discard operation by further considering a message indicating that the discard operation is applied based on a priority.

[0022] According to another embodiment of the present disclosure, in the method, the priority is configured by the base station or a core network connected to the base station.

[0023] According to another aspect of the present disclosure, a terminal in a wireless communication system is provided, the terminal comprising: a transceiver configured to send or receive a signal; and at least one processor connected to the transceiver, wherein the at least one processor is configured to: identify the beginning of a congestion state or a burst state, the congestion state is based on insufficient resources for uplink data, and the burst state is related to an increase in uplink data; based on the identification of the beginning of the congestion state or the burst state, identify whether to perform a discard operation on a protocol data unit PDU of the uplink data or a PDU set including at least one PDU; based on the identification, perform a discard operation on the PDU or the PDU set according to a priority configured based on the importance of the PDU or the PDU set; and stop performing the discard operation based on the end of the congestion state or the burst state.

[0024] According to one embodiment of the present disclosure, in order to identify the beginning of a congestion state or a burst state, at least one processor is also configured to: receive a message indicating the beginning of a congestion state or a burst state from a base station, and the beginning of the congestion state or the burst state is identified based on the message.

[0025] According to another embodiment of the present disclosure, in a terminal, a message indicating the start of a congestion state or a burst state is received in the following situations: the terminal sends a buffer status report BSR for uplink data transmission to the base station, and the base station does not allocate resources for uplink data within a predetermined time from the time point when the base station receives the BSR; the terminal is configured to report the uplink data rate to the base station and the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time to a predetermined time point, the uplink data rate through which the terminal sends resources allocated from the base station is lower than the reported uplink data rate; the terminal sends a BSR for uplink data transmission for sending data amount, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the base station receives the BSR is less than the amount of data sent through the BSR; the uplink data rate related to the uplink data of the terminal is higher than the preconfigured data rate; the uplink data rate related to the uplink data of the terminal is higher than the recommended data rate configured by the base station; or the base station receives a report on a congestion state or a burst state from the terminal.

[0026] According to one embodiment of the present disclosure, in the terminal, the beginning of a congestion state or a burst state is identified in the following circumstances: within a preconfigured time from a time point when a packet data convergence protocol PDCP or a terminal configured to identify a congestion state receives a PDCP service data unit SDU from a higher layer of the terminal, the base station does not allocate resources for uplink data; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number or rate of PDUs or PDU sets discarded by a timer for a discard operation exceeds a reference value; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets discarded by a timer for a discard operation sequentially exceeds a reference value; from a time point before the preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets discarded by a timer for a discard operation sequentially exceeds a reference value; Among the received PDUs or PDU sets, the number or rate of discarded PDUs or PDU sets determined by the PDCP sequence number SN exceeds a reference value; the terminal is configured to report the uplink data rate to the base station and the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time point to a predetermined time point, the uplink data rate that can be sent through the resources allocated from the base station to the terminal is lower than the reported uplink data rate; the terminal sends a BSR for sending data to the base station and for sending a data amount, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the terminal sends the BSR is less than the amount of data sent through the BSR; the uplink data rate related to the uplink data of the terminal is higher than the preconfigured data rate; the uplink data rate related to the uplink data of the terminal is higher than the recommended data rate configured by the base station; an indication of a congestion state or a burst state is received from a high layer of the terminal; or the terminal receives an indication of a congestion state or a burst state from the base station.

[0027] According to another embodiment of the present disclosure, in the terminal, at least one processor is further configured to send, to the base station, information related to whether the terminal supports a function of identifying a congestion state or a sudden state of the terminal.

[0028] According to another embodiment of the present disclosure, in the terminal, the information about whether the terminal supports the terminal identification function for a congestion state or a burst state includes at least one of the following: information about whether the congestion state identification function is supported, information about the types of supported congestion state identification conditions, information about whether the burst state identification function is supported, information about the types of supported burst state identification conditions, information about the types of information that can be received and used by a high layer, or information about indications or reports that can be sent / received to / from a high layer.

[0029] According to another embodiment of the present disclosure, the at least one processor is further configured to send information indicating that the burst state ends to the base station.

[0030] According to another embodiment of the present disclosure, the at least one processor is further configured to send a report of the congestion state or the burst state to the base station based on the identification of the start of the congestion state or the burst state.

[0031] According to another embodiment of the present disclosure, in order to determine whether to perform a discard operation, at least one processor is further configured to further consider a message from a base station indicating that the discard operation is applied based on priority when determining whether to perform the discard operation.

[0032] According to another embodiment of the present disclosure, in the terminal, the priority is configured by the base station or a core network connected to the base station.

[0033] One embodiment of the present disclosure provides an apparatus and method for identifying and managing congestion and burst states in a wireless communication system.

[0034] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and other aspects, features and advantages of some embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which: Figure 1 The structure of an extended reality XR service in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 2 The signal flow for configuring a congestion or burst recognition reference in a terminal or a base station according to an embodiment of the present disclosure is shown; Figure 3 The signal flow for providing a congestion or burst management reference in a terminal or a base station according to one embodiment of the present disclosure is shown; Figure 4 shows a signal flow for reporting or indicating congestion or burst according to one embodiment of the present disclosure; Figure 5 A method of discarding a PDU set or a PDU from a PDCP of a terminal according to an embodiment of the present disclosure is shown; Figure 6 is a view showing a structure of a base station according to an embodiment of the present disclosure; and Figure 7 is a view showing a structure of a terminal according to an embodiment of the present disclosure.

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

[0037] The following description in conjunction with the accompanying drawings is intended to assist in a comprehensive understanding of the various embodiments of the present disclosure, which are defined by the claims and their equivalents. It includes various specific details that are helpful for understanding, but these are only considered as examples. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0038] The terms and expressions used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable the present disclosure to be clearly and consistently understood. Therefore, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is for illustrative purposes only and is not intended to limit the present disclosure, which is defined by the appended claims and their equivalents.

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

[0040] For the same reason, in the accompanying drawings, some components are exaggerated, omitted or shown in the form of schematic diagrams. In addition, the size of each component does not fully reflect its actual size. In each figure, the same reference numeral is given to the same or corresponding components.

[0041] With reference to the following embodiments and drawings, the advantages, features and methods for achieving these advantages and features of the present disclosure will become clear. However, the present disclosure is not limited to the following embodiments, and can be implemented in various forms, but these embodiments make the disclosure of the present disclosure complete and provide common knowledge in the technical field to which the present disclosure belongs, so as to fully inform the technical personnel of the scope of protection of the present disclosure, and the present disclosure is only limited by the scope of protection of the claims. Throughout the disclosure, the same reference numerals refer to the same elements. In addition, when describing the present disclosure, if it is determined that a detailed description of the relevant functions or configurations may unnecessarily obscure the subject matter of the present disclosure, the detailed description will be omitted. In addition, the terms to be described later are terms based on functional definitions in the present disclosure, which may vary according to the intentions or habits of the user or operator. Therefore, it should be defined according to the content of the full text of this specification.

[0042] When describing the embodiments of the present disclosure, the main target is the New Radio (NR), a wireless access network on the 5G mobile communication standard specified by the mobile communication standardization organization 3rd Generation Partnership Project (3GPP), and a packet core 5G system or 5G core network or next generation core (NG Core), but with only slight modifications, the gist of the present disclosure is also applicable to other communication systems with similar technical backgrounds without significantly deviating from the scope of the present disclosure. This is possible, and those skilled in the art are able to achieve this based on their judgment.

[0043] In the following, for the convenience of description, some terms and names defined in 3GPP standards (5G, NR, Long Term Evolution (LTE) or similar system standards) may be used. However, the present disclosure is not limited to the terms and names and may be equally applicable to systems conforming to other standards.

[0044] The following are terms used in the description to identify access nodes, network entity terms, message terms, interface terms between network entities, and various types of identification information. For ease of explanation, the terms, etc. are explained. Therefore, the present disclosure is not limited to the terms used herein, and other terms referring to objects with equivalent technical meanings may also be used.

[0045] Hereinafter, a base station is a subject that performs resource allocation of a terminal, and may be at least one of a gNodeB, an eNodeB, a NodeB, a base station (BS), a wireless access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path for sending signals from a base station to a terminal, and an uplink (UL) refers to a wireless transmission path for sending signals from a terminal to a base station.

[0046] At this point, it is understood that each block in the flowchart and the combination of flowcharts can be executed by computer program instructions. These computer program instructions can be embodied in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device are described in the flowchart block. It creates a device for performing functions. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can be executed in a specific manner by a computer or other programmable data processing device to achieve the function, so that the instructions stored in the computer-usable or computer-readable memory can also manufacture a product containing an instruction device for performing the function described in the flowchart block. The computer program instructions can also be loaded onto a computer or other programmable data processing device, so as to perform a series of operation steps on the computer or other programmable data processing device to create a process executed by a computer to generate a computer or other programmable data processing device. The instructions for executing the processing device can also provide steps for performing the functions described in the flowchart block.

[0047] In addition, each block may represent a module, segment or portion of code that includes one or more executable instructions for performing a specific logical function. It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur in an unordered manner. For example, in fact, two blocks shown in succession may be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order according to their functions.

[0048] At this time, the term "~ unit" used in this embodiment refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the "~ unit" performs certain functions. However, the "~ part" is not limited to software or hardware. "~" can be configured to be in an addressable storage medium, and can be configured to replicate one or more processors. Therefore, for example, "~ unit" refers to a component, such as a software component, an object-oriented software component, a class component, a task component, a process, a function, a property, a process, a subroutine, a program code segment, a driver, a firmware, a microcode, a circuit, data, a database, a data structure, a table, an array, and a variable. The functions provided in the components and "~ units" can be combined into a smaller number of components and "~ units", or further separated into additional components and "~ units". In addition, these components and "~ units" can be implemented to reproduce one or more central processing units (CPUs) in a device or a secure multimedia card. In addition, in one embodiment of the present disclosure, the "~ unit" can include one or more processors.

[0049] 5G mobile communication technology defines a wide frequency band to achieve fast transmission speeds and new services. It can also be implemented in ultra-high frequency bands ("above 6GHz") called Wave. In addition, in 6G mobile communication technology, which is called the post-5G communication system (super 5G), in order to achieve a transmission speed 50 times faster than 5G mobile communication technology and ultra-low latency reduced to one-tenth, terahertz bands (for example, the 3 terahertz (3THz) band at 95 GHz) are being considered for terahertz-scale implementation.

[0050] In the early days of 5G mobile communication technology, enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) are needed. Beamforming and massive MIMO technologies are used to alleviate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves to meet service support and performance requirements and achieve efficient use of ultra-high frequency resources. The following technologies have made progress: support for multiple parameter sets (multiple subcarrier spacing operations, etc.) and dynamic operation time slot formats; initial access technology that supports multi-beam transmission and broadband; bandwidth part (BWP) definition and operation; large-capacity new channel coding methods, such as low-density parity check (LDPC) codes for data transmission and polarization codes for reliable transmission of control information; L2 preprocessing; and dedicated services for specific services. The standardization of network slicing for providing networks has also made progress.

[0051] Currently, discussions are underway to improve and enhance the performance of initial 5G mobile communication technologies based on the services they are intended to support. Physical layer standardization of the following technologies is ongoing: New Radio Unlicensed Bands (NR-U) (aimed at systems operating to meet various regulatory requirements for unlicensed bands); NR terminal low power consumption technology (UE energy saving); Non-terrestrial Networks (NTN), where terminals communicate directly with satellites to ensure coverage in areas where communication with terrestrial networks is not possible; positioning, etc.

[0052] In addition, the following technologies are also underway: Industrial Internet of Things (IIoT) integrated access and backhaul (IAB) that provides nodes for expanding the network service area by integrating and supporting wireless backhaul links and access links to support new services through links and integration with other industries; Mobility enhancement technology, including conditional switching and dual active protocol stack (DAPS) switching; and 2-step random access that simplifies the random access procedure (2-step RACH standardized in the air interface architecture / protocol field for technologies such as NR), and the following technologies are also underway: 5G baseline for grafting network function virtualization (NFV) and software defined networking (SDN) for architecture (e.g., service-based architecture, service-based interface) technology standardization (in the system architecture / service field); and mobile edge computing (MEC) that provides services based on terminal location, etc.

[0053] In addition, the development of 5G mobile communication systems adopts new waveforms, full-dimensional MIMO (FD-MIMO) and array antennas to ensure the coverage of 6G mobile communication technology in the terahertz band. From the design stage, multi-antenna transmission technology (such as massive antennas, lenses and antennas based on metamaterials to improve the coverage of terahertz band signals), high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), reconfigurable smart surface (RIS) technology, and full-duplex technology, satellites and artificial intelligence (AI) are used to improve the frequency efficiency and system network of 6G mobile communication technology, which can serve as the basis for the development of AI-based communication technology, which achieves system optimization by internalizing end-to-end AI support functions and next-generation distributed computing technology (which uses ultra-high performance communication and computing resources to realize complex services that exceed the computing power limit of terminals).

[0054] Hereinafter, the present disclosure relates to a method and apparatus for recognizing / identifying / determining and managing congestion and emergency states in a wireless communication system. Specifically, the present disclosure provides a technology that can effectively provide services based on XR service requirements by recognizing / identifying, determining and managing congestion caused by insufficient resources or emergency situations caused by increased XR business volume when providing services for XR services that include high speed and low latency as service requirements in a wireless communication system.

[0055] The present disclosure relates to a wireless communication system, and more particularly, to an apparatus and method for identifying and managing a congestion or emergency state in a wireless communication system.

[0056] Figure 1 The structure of an XR service in a wireless communication system according to an embodiment of the present disclosure is shown.

[0057] Reference Figure 1 , Extended Reality (XR) services may include various types of services for one service. Services that provide Extended Reality (XR) services (such as Virtual Reality (VR), Cloud Gaming (CG), and Augmented Reality (AR)) may include one or more of video, audio, data, field of view (FOV), omnidirectional view, gesture / control, see 3GPP Radio Access Network (RAN) Working Group (WG) 1 Technical Report (TR) 38.838 for details. In addition to the above examples, more types of services may be included.

[0058] In addition, according to one embodiment of the present disclosure, various types of XR services may be divided into information (or data) units that can be distinguished at the application level. For example, an XR service may correspond to a photo or picture, a frame of video, or an audio unit. XR service data may be segmented into units of a protocol data unit (PDU) set 110 or 120, and may be segmented into one or more PDUs 111, 112, 113, 121, and 122 based on the size of the PDU set 110 or 120 and transmitted.

[0059] Reference Figure 1 When transmitting compressed video, the PDU set may include two types: intra-coded (I) frames 130 or predicted (P) frames 140. An I frame is an independent frame that can represent a complete photo or image 131, regardless of whether there are other frames. A P frame 140 is a frame that represents change information of the previous I frame 130, and if the I frame 130 is not received normally, the photo or image 141 to be expressed using the P frame 140 may not be expressed normally.

[0060] According to one embodiment of the present disclosure, the I frame 130 may be more important than the P frame 140, and the P frame 140 may be dependent on the I frame 130. Depending on the application configuration or policy, characteristics such as importance or dependency that may differ between different PDU sets or PDUs may be utilized to determine the priority or packet processing policy.

[0061] According to an embodiment of the present disclosure, the priority and the packet processing policy may be associated with the PDU set 150 (151 and 152), or associated with all PDUs 160 and 170 included in the PDU set (161, 162, 171, and 172). In addition, the priorities 161 and 171 and the packet processing policies 162 and 172 between different PDU sets or different PDUs 160 and 170 of the same PDU set 150 may be different.

[0062] According to one embodiment of the present disclosure, the priority may be information representing a policy associated with at least one of the following: importance, dependency, packet processing strategy, delay budget, and error rate, and the information may be different in numerical or textual form for each different PDU set or PDU.

[0063] The packet processing strategy may be configured separately from the priority, and may include at least one of the following processing operations. The present disclosure is not limited to the following examples.

[0064] Operation 1: The PDU set or PDU may not be discarded.

[0065] Action 2: The PDU set or PDUs may not be discarded, but under certain conditions including congestion, the PDU set or PDUs may be discarded.

[0066] Action 3: The PDU set or PDU may be discarded.

[0067] Operation 4: If a PDU included in a PDU set is discarded, all other PDUs or part of the PDUs included in the same PDU set may also be discarded.

[0068] Operation 5: In the case where one or more PDUs included in the PDU set are not received, the corresponding PDU set may be discarded.

[0069] For example, in a case where only one of an I frame 130 and a P frame 140 can be sent or received, sending or receiving the I frame 130 can help provide efficient service, and therefore, the application can be configured to have the following packet processing policy: the PDU set used to transmit the I frame 130 or the PDU included in the PDU set has a higher priority or is not discarded.

[0070] According to one embodiment of the present disclosure, a base station or a core network may configure a priority or packet processing policy associated with a protocol data unit (PDU) set or a single PDU sent or received on one or more slices, quality of service (QoS) flows, data radio bearers (DRBs), or logical channels (LCHs) to a terminal in the form of one-to-one or many-to-one mapping information, so as to support the priority or packet processing policy of the PDU set or the single PDU. The higher layers of the terminal may use implicit or explicit communication or pre-configured policies, etc. to configure or notify the access layer of the priority or packet processing policy mapped to one or more slices, QoS flows, PDU sets, and PDUs. In addition, the higher layers of the terminal or base station may determine the priority or packet processing policy based on service characteristics or service requirements, and configure it to the terminal if the policy is not received.

[0071] Figure 2 A signal flow for configuring a congestion or burst awareness / recognition reference in a terminal or a base station according to an embodiment of the present disclosure is shown.

[0072] Reference Figure 2 , in the event that it is determined that one or more PDU sets or PDUs meet the service requirements and may not be sent or received, the configuration can be performed by sending data with higher priority first Figure 1 The priority or packet processing policy described in the method can be used to minimize the degradation of user experience, and the conditions for applying the priority or packet processing policy can be configured based on congestion or burst.

[0073] According to an embodiment of the present disclosure, the terminal 210 or the base station 220 may implicitly or explicitly recognize / identify congestion or burst, and a recognition / identification reference may be configured in the terminal 210 or the base station 220 to recognize / identify congestion or burst of the wireless communication network.

[0074] According to one embodiment of the present disclosure, the terminal 210 may report to the base station 220 whether the congestion or burst recognition / identification function is supported through the radio resource control (RRC) UECapabilityInformation 213. The terminal may report to the base station 220 whether the congestion or burst recognition / identification function is supported through another message other than UECapabilityInformation 213. The terminal 210 may report one or more of the following information individually or in combination. The present disclosure is not limited to the following examples.

[0075] Information 1: Whether the congestion recognition / identification function is supported

[0076] Information 2: Types of congestion awareness / recognition conditions supported

[0077] Information 3: Whether the congestion recognition / identification function is supported

[0078] Information 4: Types of supported emergency recognition / identification conditions

[0079] Information 5: Types of information that higher-level managers can receive and use

[0080] Information 6: Types of reports or instructions that can be sent / received by higher layers

[0081] According to one embodiment of the present disclosure, when the access stratum (AS) layer 212 of the terminal 210 receives a request from the high layer 211 to configure a congestion or burst identification / identification reference in operation 214 or to update an existing configuration, or to determine the same, the AS layer 212 may request information about the congestion or burst identification / identification reference configuration from the high layer 211 or the base station 220 in operations 215 and 216.

[0082] According to one embodiment of the present disclosure, when the terminal 210 requests a congestion or burst recognition / identification reference in operation 216, it is determined that the core network 230 needs to update the congestion or burst recognition / identification reference, or it is determined that the congestion or burst recognition / identification reference needs to be configured by the base station policy, and the base station 220 may provide the congestion or burst recognition / identification reference to the terminal 210 by using an RRCReconfiguration message 221 based on whether the terminal 210 supports the congestion or burst recognition / identification function in operation 213. Without being limited to the above example, the base station 220 may provide the congestion or burst recognition / identification reference to the terminal 210 through another message other than the RRCReconfiguration message 221.

[0083] According to one embodiment of the present disclosure, the base station 220 may select the congestion or burst recognition / identification reference to be configured in the terminal 210 based on the service requirement, or use the congestion or burst recognition / identification reference configured by the core network 230 to the base station 220 in operation 231. The core network 230 may select the congestion or burst recognition / identification reference to be transmitted to the base station based on the service requirement, or use the congestion or burst recognition / identification reference configured by the application server 240 to the core network 230 in operation 241.

[0084] According to one embodiment of the present disclosure, when a request for a congestion or burst awareness / identification reference is received from the AS layer 212 in operation 215, or when it is determined that a congestion or burst awareness / identification reference needs to be configured, the high layer 211 of the terminal 210 may configure the congestion or burst awareness / identification reference in operation 218.

[0085] According to one embodiment of the present disclosure, the high layer 211 of the terminal 210 may select the congestion or burst recognition / identification reference to be configured in the AS layer 212 based on the service demand, or may use the congestion or burst recognition / identification reference configured to the high layer 211 by the application server 240 in operation 242. When it is determined that the congestion or burst recognition reference needs to be configured by the application server 240, the high layer 211 of the terminal 210 may request the application server 240 to configure the congestion or burst recognition / identification reference in operation 217, and when receiving the request to configure the congestion or burst recognition / identification reference in operation 217 or determining that configuration is required, the application server 240 may configure the congestion or burst recognition / identification reference to the high layer 211 in operation 242.

[0086] According to an embodiment of the present disclosure, when the upper layer 211 or the base station 220 may not configure a congestion or burst recognition / identification reference, the AS layer 212 of the terminal 210 may configure a congestion or burst recognition / determination reference based on service requirements in operation 219 .

[0087] According to an embodiment of the present disclosure, when configuring a congestion or burst recognition / identification reference, the terminal 210 may be configured to recognize / identify the beginning of congestion or burst when one or more of the following conditions are simultaneously met. The present disclosure is not limited to the following examples.

[0088] Condition 1: From the time when a Packet Data Convergence Protocol (PDCP) configured to recognize / identify a congestion state receives a PDCP Service Data Unit (SDU) from a higher layer, the base station does not allocate resources within a preconfigured time.

[0089] Condition 2: From a time point before a preconfigured time to a current time point, the number or rate of PDU sets or PDUs discarded due to discardTimer among PDU sets or PDUs received from higher layers by a PDCP configured to recognize / identify congestion status exceeds a reference value.

[0090] Condition 3: From a time point before a preconfigured time to the current time point or regardless of time, the number of PDU sets or PDUs received from higher layers by the PDCP configured to recognize / identify the congestion state that are continuously discarded by the discardTimer exceeds a reference value.

[0091] Condition 4: From a time point before a preconfigured time to a current time point, the number or rate of PDU sets or PDUs received from lower layers by a PDCP configured to recognize / identify a congestion state, which are determined to be lost by the PDCP SN, exceeds a reference value.

[0092] Condition 5: The data rate of the uplink or downlink XR service is configured to be reported to the base station through RRCUEAssistnaceInformation, and when reporting, the uplink or downlink data rate that can be transmitted through the resources allocated by the base station from the time point before the preconfigured time to the current time point is lower than the data rate of the uplink or downlink XR service reported through RRCUEAssistnaceInformation.

[0093] Condition 6: In the case where the amount of data of the logical channel group (LCG) associated with at least one slice, QoS flow, DRB or LCH configured to transmit uplink XR services is transmitted via a buffer status report (BSR), the amount of data that can be transmitted via the resources allocated by the base station for a preconfigured time starting from the time point when the BSR is transmitted is less than the reported amount of data.

[0094] Condition 7: The uplink or downlink data rate of the XR service is higher than the uplink or downlink data rate of the pre-configured XR service.

[0095] Condition 8: The uplink or downlink data rate of the XR service is higher than the uplink or downlink recommended bit rate transmitted by the base station.

[0096] Condition 9: Congestion or burst indication is received from higher layers.

[0097] Condition 10: A congestion or burst indication is received from the base station.

[0098] According to an embodiment of the present disclosure, even when a reference for recognizing / identifying the start of congestion is configured and the reference for recognizing / identifying the start of congestion is met, the terminal 210 predicts that the service will soon return to normal. More specifically, when at least one of switching, redirection and reconstruction is in progress, the terminal 210 can be configured not to recognize / determine congestion within a predetermined time from the corresponding time point.

[0099] According to an embodiment of the present disclosure, when one or more of the following conditions are simultaneously satisfied, the terminal 210 may be configured to recognize / identify the beginning of congestion or burst. The present disclosure is not limited to the following examples.

[0100] Condition 1: One or all of the conditions included in the reference for determining the start of congestion or burst are no longer met within a preconfigured time period, or are no longer met regardless of the time.

[0101] Condition 2: A preconfigured time has passed from the moment when congestion or burst starts to be recognized.

[0102] Condition 3: An indication is received from a higher layer indicating the end of congestion or burst.

[0103] Condition 4: An indication is received from a higher layer indicating that the data rate of the XR service has changed.

[0104] Condition 5: A congestion or burst indication is received from the base station.

[0105] Condition 6: The terminal is configured not to use the slice, QoS flow, DRB or LCH associated with the start of congestion or burst, or is configured to no longer recognize / identify congestion or burst.

[0106] According to one embodiment of the present disclosure, the base station 220 may select and configure a congestion or burst awareness / identification reference based on service requirements in operation 222, or use a reference configured for the base station 220 by the core network 230 in operation 231. The core network 230 may select a reference configured for the base station 220 based on service requirements, or use a reference transmitted to the core network 230 by the application server 240 in operation 241.

[0107] According to an embodiment of the present disclosure, when configuring a congestion or burst recognition / identification reference, the base station 220 may be configured to recognize / identify the beginning of congestion or burst when one or more of the following conditions are simultaneously met. The present disclosure is not limited to the following examples.

[0108] Condition 1: When the terminal transmits a BSR to the base station for sending the data volume of the LCG associated with at least one slice, QoS flow, DRB or LCH (these slices, QoS flows, DRB or LCH are configured to transmit uplink XR services), starting from the time point of receiving the BSR, the base station does not allocate resources within a preconfigured time.

[0109] Condition 2: From a time point before a preconfigured time to a current time point, among PDU sets or PDUs received from the core network, the number or rate of PDU sets or PDUs that are not transmitted to the terminal and are discarded exceeds a reference value.

[0110] Condition 3: From a time point before a preconfigured time to the current time point or regardless of time, the number of PDU sets or PDUs received from the core network that are not transmitted to the terminal and are continuously discarded exceeds a reference value.

[0111] Condition 4: The terminal is configured to report the data rate of the uplink or downlink XR service to the base station through RRCUEAssistnaceInformation, and when reporting, from the time point before the preconfigured time to the current time point, the uplink or downlink data rate that can be transmitted through the resources allocated by the base station is lower than the data rate of the uplink or downlink XR service reported through RRCUEAssistnaceInformation.

[0112] Condition 5: In the case where the terminal transmits a buffer status report (BSR) to send the base station the amount of data of the LCG associated with at least one slice, QoS flow, DRB or LCH (these slices, QoS flows, DRB or LCH are configured to transmit uplink XR services), for a preconfigured time from the time point when the BSR is received, the amount of data that can be transmitted through the resources allocated by the base station is less than the amount of data reported by the terminal.

[0113] Condition 6: The uplink data rate of the terminal or the downlink XR service data rate of the base station is higher than the preconfigured data rate.

[0114] Condition 7: The uplink data rate of the terminal or the downlink XR service data rate of the base station is higher than the recommended bit rate configured by the base station.

[0115] Condition 8: The base station receives a congestion or burst report from the core network.

[0116] Condition 9: The base station receives a congestion or burst report from the terminal.

[0117] According to one embodiment of the present disclosure, even in a case where a reference for identifying / determining the start of congestion is configured and the reference for identifying / determining the start of congestion is met, more specifically, in a case where at least one of switching, redirection and re-establishment is in progress, the base station 220 predicts that the service of the terminal 210 will soon return to normal, the base station 220 can be configured not to recognize / identify the congestion of the terminal 210 for a preconfigured time from the corresponding time point.

[0118] According to one embodiment of the present disclosure, when one or more of the following conditions are simultaneously satisfied, the base station 220 may be configured to recognize / identify the beginning of congestion or burst with respect to the terminal 210. The present disclosure is not limited to the following examples.

[0119] Condition 1: One or all of the conditions included in the reference for determining the start of congestion or burst are no longer met within a preconfigured time period, or are no longer met regardless of the time.

[0120] Condition 2: A preconfigured time has passed since the time when congestion or burst is recognized / identified.

[0121] Condition 3: An indication indicating congestion or the end of a burst is received from the core network.

[0122] Condition 4: An indication indicating the end of congestion or burst is received from the terminal.

[0123] Condition 5: The terminal is configured not to use the slice, QoS flow, DRB or LCH associated with the start of congestion or burst, or is configured to no longer recognize congestion or burst.

[0124] According to an embodiment of the present disclosure, the "PDCP configured to recognize / identify congestion status" available in the above conditions may be a PDCP related to the following situation: at least one slice, QoS flow, DRB or LCH configured from a high layer, base station or core network for transmitting uplink XR services is configured to recognize / identify congestion status.

[0125] According to an embodiment of the present disclosure, the "preconfigured time" may include a default averaging window or a PDB mapped to a QoS flow transmitted using a PDCP configured to recognize / identify a congestion state, a value configured by a base station, a value configured by a core network, or a value configured by an application server.

[0126] According to one embodiment of the present disclosure, the "number or rate used as a reference" may include a maximum packet loss rate, a packet error rate, a value configured by a base station, a value configured by a core network, or a value configured by an application server.

[0127] According to one embodiment of the present disclosure, the "data rate of XR service" may correspond to the sum of data rates provided from a high layer for one or more XR applications, or may correspond to the sum of data rates measured for at least one slice, QoS flow, DRB or LCH configured from a high layer for transmitting XR service and the measured value of the service data rate for a preconfigured time.

[0128] According to an embodiment of the present disclosure, the "preconfigured data rate" may include a guaranteed stream bit rate (GFBR0), a maximum stream bit rate (MFBR0), a maximum data burst volume (MDBV), a session aggregation maximum bit rate (session-AMBR), UE-AMBR, UE-Slice-MBR, a value configured by a base station, a value configured by a core network, or a value configured by an application server.

[0129] Figure 3 A signal flow for providing a congestion or burst management reference in a terminal or a base station according to an embodiment of the present disclosure is shown.

[0130] like Figure 2 As described above, the terminal 210 or the base station 220 may be configured to recognize / identify the beginning or end of a congestion or burst state by referring to one or more conditions.

[0131] Reference Figure 3 , the terminal 310 or the base station 320 may be provided with a reference to a management operation, and when the beginning or end of congestion or a burst is recognized / identified, the management operation may be executed or stopped.

[0132] According to an embodiment of the present disclosure, the terminal 310 may report to the base station 320 whether the congestion or burst management function is supported through UECapabilityInformation 301. The terminal may report to the base station 320 whether the congestion or burst identification function is supported through another message other than UECapabilityInformation 301. The terminal may report one or more of the following information separately or in combination. The present disclosure is not limited to the following examples.

[0133] Information 1: Whether the congestion recognition / identification function is supported

[0134] Information 2: Types of congestion awareness / recognition conditions supported

[0135] Information 3: Whether the congestion reporting function is supported

[0136] Information 4: Whether the congestion recognition / identification function is supported

[0137] Information 5: Types of supported emergency recognition / identification conditions

[0138] Information 6: Whether the emergency reporting function is supported

[0139] Information 7: Types of information that higher-level managers can receive and use

[0140] Information 8: Types of reports or indications that can be sent / received in higher layers

[0141] Information 9: Whether the PDU aggregation or PDU discard function is supported

[0142] According to one embodiment of the present disclosure, when the access stratum (AS) layer 312 of the terminal 310 receives a request from the high layer 311 in operation 314 to configure a congestion or burst management reference or to update an existing configuration, or when making the above determination, the AS layer 312 may request information about the congestion or burst management reference configuration from the high layer 311 or the base station 320 in operations 315 and 316.

[0143] According to an embodiment of the present disclosure, when the terminal 310 requests a congestion or burst management reference in operation 316, it is determined that the congestion or burst management reference needs to be updated by the core network 330, or it is determined that the congestion or burst management reference needs to be configured by the policy of the base station, and the base station 320 can provide the congestion or burst management reference to the terminal 310 by using an RRCReconfiguration message 321 based on whether the terminal 310 supports a congestion or burst recognition / identification function in operation 313. Without being limited to the above example, the base station 320 can provide the congestion or burst recognition / identification reference to the terminal 310 through another message other than the RRCReconfiguration message 321.

[0144] According to an embodiment of the present disclosure, the base station 320 may select the congestion or burst management reference to be configured in the terminal 310 based on the service demand, or may use the congestion or burst management reference configured by the core network 330 to the base station 320 in operation 331. The core network 330 may select the congestion or burst management reference based on the service demand of the congestion or burst management reference to be transmitted to the base station, or may use the congestion or burst management reference configured by the application server 340 for the core network 330 in operation 341.

[0145] According to an embodiment of the present disclosure, when a request for a congestion or burst management reference is received from the AS layer 312 in operation 315, or when it is determined that the congestion or burst management reference needs to be configured, the high layer 311 of the terminal 310 may configure the congestion or burst management reference in operation 319. The high layer 311 of the terminal 310 may select the congestion or burst management reference to be configured in the AS layer 312 based on the service requirements, or may use the congestion or burst management reference configured to the high layer 311 by the application server 340 in operation 342. When it is determined that the application server 340 needs to configure the congestion or burst management reference, the high layer 311 of the terminal 310 may request the application server 340 to configure the congestion or burst management reference in operation 317, and when a request for configuring the congestion or burst management reference is received in operation 317 or it is determined that configuration is required, the application server 340 may configure the congestion or burst management reference for the high layer 311 in operation 342.

[0146] According to an embodiment of the present disclosure, when the upper layer 311 or the base station 320 cannot configure the congestion or burst management reference, the AS layer 312 of the terminal 310 can configure the congestion or burst management reference based on service requirements in operation 318 .

[0147] According to one embodiment of the present disclosure, Figure 2 In the case of the reference configuration for recognizing / identifying / determining the start or end of congestion or a burst described in , or in the case of the reference for recognizing / identifying / determining the start or end of congestion or a burst configured by a method not disclosed in the present disclosure, the terminal 310 may configure at least one reference to perform or stop the following at least one management operation when at least one configured reference is satisfied. The present disclosure is not limited to the following examples.

[0148] Action 1: Congestion or burst may be reported to higher layers.

[0149] Operation 2: Congestion or emergency situation may be reported to the base station.

[0150] Operation 3: A PDU set or a PDU may be discarded. This operation may implicitly or explicitly include at least one of the following references.

[0151] Reference 1: Whether the base station or application uses data rate

[0152] Reference 2: A PDU set or at least one slice of a PDU, QoS flow, DRB or LCH identifier may be discarded

[0153] Reference 3: A higher level priority associated with a PDU set or PDUs that can be discarded

[0154] Reference 4: AS layer priority associated with a slice, QoS flow, DRB or LCH that can discard a PDU set or PDU

[0155] Reference 5: Whether to discard other PDUs configured with the same PDU set

[0156] Operation 4: The base station may send a recommended bit rate query.

[0157] According to one embodiment of the present disclosure, the base station 320 may select and configure a congestion or burst management reference based on service requirements in operation 322, or use the congestion or burst management reference configured for the base station 320 by the core network 330 in operation 331. The core network 330 may select the congestion or burst management reference configured for the base station 320 based on service requirements, or may use the congestion or burst management reference transmitted to the core network 330 by the application server 340 in operation 341.

[0158] According to one embodiment of the present disclosure, Figure 2 In the case where the reference for recognizing / identifying / determining the start or end of congestion or burst is configured, or in the case where the reference for recognizing / identifying / determining the start or end of congestion or burst is configured by a method not disclosed in the present disclosure, the base station 320 may configure at least one reference so that when at least one of the configured references is satisfied at the same time, at least one of the following management operations is performed or stopped. The present disclosure is not limited to the following examples.

[0159] Action 1: Congestion or burst may be reported to the core network.

[0160] Operation 2: Congestion or emergency situations can be reported to the terminal.

[0161] Action 3: The PDU set or PDU may be discarded.

[0162] Operation 4: A recommended bit rate query may be sent to the terminal.

[0163] Figure 4 A signal flow for reporting or indicating congestion or burst according to one embodiment of the present disclosure is shown.

[0164] Reference Figure 4 According to one embodiment of the present disclosure, Figure 2 The reference for recognizing / identifying / determining the start and end of congestion or burst described in the present disclosure is configured, or the reference for recognizing / identifying / determining the start and end of congestion or burst is configured by a method not disclosed in the present disclosure, and when the congestion or burst end is recognized in operation 450, the AS layer 412 of the terminal 410 can refer to the operation 413 and 414. Figure 3The described congestion or burst management operation performs congestion or burst reporting to the upper layer 411 or the base station 420 .

[0165] According to one embodiment of the present disclosure, the congestion or burst report may include any form that can report one or more information about the start, end, or notification of congestion or burst. The congestion or burst report 414 sent to the base station 420 can be transmitted via RRC or medium access control (MAC) control element (CE). The present disclosure is not limited to the above examples.

[0166] According to an embodiment of the present disclosure, when executed by MAC CE, a congestion or burst report may be distinguished by a logical channel ID (LCID) or an extended LCID (eLCID) and transmitted with a size of 0 bits, or may include other information with a size greater than 0 bits. The congestion or burst report 413 or 414 may implicitly or explicitly include at least one of the following information. The present disclosure is not limited to the following examples.

[0167] Information 1: Classification of congestion or burst

[0168] Information 2: The start or end of congestion or burst

[0169] Information 3: Traffic direction (uplink or downlink) where congestion or burst occurs

[0170] Information 4: One or more slices, QoS flows, DRBs or LCHs associated with congestion or bursts

[0171] Information 5: Expected duration of congestion or burst

[0172] Information 6: Burst required uplink data rate

[0173] Message 7: Request for uplink data rate that can be provided by the base station

[0174] Information 8: One or more references to determine congestion or burst

[0175] According to an embodiment of the present disclosure, when the upper layer 411 of the terminal 410 receives a congestion or burst report 413 or detects congestion at the application layer, the terminal 410 (or the upper layer 411 of the terminal 410 ) may send a congestion or burst report to the application server 440 .

[0176] According to an embodiment of the present disclosure, when a congestion or burst report 415 is received from a high layer 411 of a terminal 410 or congestion is detected at an application layer, an application server 440 may send a congestion or burst report management request 441 to a core network 430 .

[0177] According to an embodiment of the present disclosure, when a congestion or burst report management request 441 is received or congestion or burst is detected according to an operation policy, the core network 430 may send a congestion or burst report management request 431 to the base station 420 .

[0178] According to one embodiment of the present disclosure, Figure 2 The reference for recognizing / identifying / determining the beginning or end of congestion or a burst described in the present disclosure may be configured, or the reference for recognizing / identifying / determining the beginning or end of congestion or a burst may be configured by a method not disclosed in the present disclosure, and in the case where the beginning of the end of the congestion or a burst is identified in operation 460, or in the case where the congestion or burst indication information needs to be updated, the base station 420 may send a congestion or burst indication 421 to the terminal 410. The congestion or burst indication 421 may include information indicating one or more of the following information: the beginning, end or notification of congestion, or the beginning, end or notification of a burst. According to one embodiment of the present disclosure, the congestion or burst indication 421 may be transmitted via RRC or MAC CE. The present disclosure is not limited to the above examples.

[0179] According to one embodiment of the present disclosure, when executed by MAC CE, the congestion or burst indication 421 can be distinguished by LCID or eLCID and transmitted with a size of 0 bits, or can include other information with a size greater than 0 bits. The congestion or burst indication 421 can implicitly or explicitly include at least one of the following information. The present disclosure is not limited to the following examples.

[0180] Information 1: Classification of congestion or burst

[0181] Information 2: The start or end of congestion or burst

[0182] Information 3: Traffic direction (uplink or downlink) where congestion or burst occurs

[0183] Information 4: One or more slices, QoS flows, DRBs or LCHs associated with congestion or bursts

[0184] Information 5: Expected duration of congestion or burst

[0185] Information 6: Whether the uplink data rate required for the burst reported by the terminal via the congestion or burst report 414 is supported

[0186] Information 7: Uplink data rate that can be provided by the base station during congestion

[0187] Information 8: Burst required downlink data rate

[0188] Information 9: At least one reference or condition for determining congestion or burst

[0189] According to one embodiment of the present disclosure, in the case of recognizing / identifying the congestion or burst state 460, if it is necessary to configure or update the congestion or burst management reference for the terminal 410, or it is intended to transmit the information that can be included in the congestion or burst indication 421 together with the management reference configuration, the base station 420 may send a congestion or burst management indication 422 to the terminal. The congestion or burst management indication 422 may include information indicating one or more of the following information: the start, end or notification of congestion, or the start, end or notification of a burst. The congestion or burst management indication 422 may be transmitted via RRC or MAC CE. The present disclosure is not limited to the above examples.

[0190] According to an embodiment of the present disclosure, when executed by MAC CE, the congestion or burst management indication 422 can be distinguished by LCID or eLCID and transmitted with a size of 0 bits, or can include other information with a size greater than 0 bits. The congestion or burst management indication 422 can implicitly or explicitly include at least one of the following information. The present disclosure is not limited to the following examples.

[0191] Information 1: Classification of congestion or burst

[0192] Information 2: The start or end of congestion or burst

[0193] Information 3: Traffic direction (uplink or downlink) where congestion or burst occurs

[0194] Information 4: One or more slices, QoS flows, DRBs or LCHs associated with congestion or bursts

[0195] Information 5: Expected duration of congestion or burst

[0196] Information 6: Whether the uplink data rate required for the burst reported by the terminal via the congestion or burst report 414 is supported

[0197] Information 7: Uplink data rate that can be provided by the base station during congestion

[0198] Information 8: Burst required downlink data rate

[0199] Information 9: At least one reference or condition for determining congestion or burst

[0200] Message 10: Configuration for reporting congestion or burst operation to higher layers

[0201] Message 11: Discarding PDU set or PDU configuration

[0202] Information 12: Recommended bit rate query operation configuration

[0203] According to one embodiment of the present disclosure, a terminal 410 that receives a congestion or burst management indication 422 may perform or stop an operation according to a preconfigured congestion or burst management reference or a reference contained in a previously received congestion or burst management indication 422, or may perform or stop a management operation according to a reference received through a newly received congestion or burst management indication 422.

[0204] Figure 5 A method for discarding a PDU set or a PDU from a PDCP of a terminal according to an embodiment of the present disclosure is shown.

[0205] According to one embodiment of the present disclosure, the PDCP of the terminal may discard the PDU set or PDU to support Figure 1 The priority and group handling strategies described in Figure 3 management operations in , or Figure 4 Management instructions in the operation.

[0206] refer to Figure 5 In operation 510, when the PDCP receives the PDCP SDU at the higher layer, the terminal may identify the mapping to Figure 1 The slice, QoS flow, priority or packet processing strategy of the DRB or LCH described in the , and information related to whether the PDU set or PDU is configured to be discarded by a management operation, and whether the reference conditions for performing the PDU discard operation are met, such as Figure 3 described.

[0207] If the discarded PDU set or PDU is not configured, or the reference condition for performing the PDU discard operation is not met, the PDCP SDU is processed normally in operation 580. Figure 3 When the data packet processing strategy or configuration described in satisfies at least one of the following conditions, the PDCP SDU may be discarded in operation 590, provided that a discarded PDU set or PDU has been configured, or a reference condition for performing a PDU discard operation is met. The present disclosure is not limited to the following examples.

[0208] Condition 1: In operation 530, the data rate of the uplink XR service is higher than the data rate indicated by the base station using the congestion or burst indication 421, the congestion or burst management indication 422, or the recommended bit rate.

[0209] Condition 2, in 540, the higher layer, base station or core network is configured to discard one or more slices of the PDU set or PDU, QoS flow, DRB or LCH identifier related to PDCP.

[0210] Condition 3, in operation 550, one or more slices, QoS flows, DRBs or LCH identifiers configured by the base station or the core network are associated with PDCP, and the priority associated with the corresponding slice, QoS flow, DRB or LCH is lower than the configured reference value.

[0211] Condition 4: In operation 560, the PDCP SDUs received at the higher layer constitute a PDU set, and the priority of the corresponding PDU set is configured in the higher layer, and the priority is lower than the configured reference.

[0212] Condition 5: In operation 560, the PDCP SDU received at the higher layer is associated with the PDU, the priority of the corresponding PDU is configured in the higher layer, and the priority is lower than the configured reference.

[0213] Condition 6: In operation 570, the PDCP SDUs received at the higher layer constitute a PDU set, and the higher layer is configured to be able to discard the corresponding PDU set.

[0214] Condition 7: In operation 570, the PDCP SDU received by the higher layer is related to the PDU, and the higher layer is configured to discard the corresponding PDU.

[0215] Figure 6 The structure of a base station according to an embodiment of the present disclosure is shown.

[0216] like Figure 6 As shown, the base station may include a transceiver 610, a controller 620, and a storage unit 630. The transceiver 610, the controller 620, and the storage unit 630 may operate according to the communication method of the above-mentioned base station. The network device may also correspond to the structure of the base station. However, the components of the base station are not limited to the above examples. For example, the base station may include more or less components than described above. For example, the base station may include a transceiver 610 and a controller 620. In addition, the transceiver 610, the controller 620, and the storage unit 630 may be implemented in the form of a single chip.

[0217] According to one embodiment of the present disclosure, the transceiver 610 is collectively referred to as a receiver of a base station and a transmitter of a base station, and can send and receive signals with a terminal, other base stations, or other network devices. At this time, the signal to be sent and received may include control information and data. For example, the transceiver 610 can send system information to the terminal, and can send a synchronization signal or a reference signal. To this end, the transceiver 610 may include: an RF transmitter for up-converting and amplifying the transmitted signal; and an RF receiver for low-noise amplifying the received signal and down-converting it. However, this is only one embodiment of the transceiver 610, and the components of the transceiver 610 are not limited to the RF transmitter and the RF receiver. The transceiver 610 may include a wired / wireless transceiver, and may include various configurations for sending and receiving signals. In addition, the transceiver 610 may receive a signal through a communication channel (e.g., a wireless channel), output the signal to the controller 620, and send a signal output from the controller 620 through the communication channel. In addition, the transceiver 610 may receive a communication signal and output it to the processor, and may transmit the signal output by the processor to a terminal, another base station, or another entity through a wired or wireless network.

[0218] According to one embodiment of the present disclosure, the storage unit 630 may store programs and data required for the base station operation. In addition, the storage unit 630 may store control information or data contained in the signal obtained from the base station. The storage unit 630 may include a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disk (CD)-ROM, and a digital versatile disk (DVD), or a combination of storage media. In addition, the storage unit 630 may store at least one of the information sent and received by the transceiver 610 and the information generated by the controller 620.

[0219] According to one embodiment of the present disclosure, in the present disclosure, the controller 620 may be defined as a circuit or a dedicated integrated circuit or at least one processor. The processor may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling an upper layer (e.g., an application). According to the embodiment proposed in the present disclosure, the controller 620 may control the overall operation of the base station. For example, the controller 620 may control the signal flow between the modules to perform operations according to the flowchart described above.

[0220] Figure 7 The structure of a terminal according to an embodiment of the present disclosure is shown.

[0221] Reference Figure 7, the terminal may include a transceiver 710, a controller 720, and a storage unit 730. The transceiver unit 710, the controller 720, and the storage unit 730 may operate according to the communication method of the above-mentioned terminal. However, the components of the terminal are not limited to the above-mentioned examples. For example, the terminal may include more or less components than the aforementioned components. For example, the terminal may include a transceiver 710 and a controller 720. In addition, the transceiver 710, the controller 720, and the storage unit 730 may be implemented as a single chip.

[0222] According to one embodiment of the present disclosure, the transceiver unit 710 is a general term for a receiving unit of a terminal and a transmitting unit of a terminal, and can send signals to / receive signals from a base station, other terminals or a network entity. The signals sent and received with the base station may include control information and data. For example, the transceiver 710 may receive system information from a base station, and may receive a synchronization signal or a reference signal. To this end, the transceiver 710 may include a radio frequency transmitter that up-converts and amplifies the transmitted signal, and a radio frequency receiver that amplifies the received signal with low noise and down-converts it. However, this is only one embodiment of the transceiver 710, and the components of the transceiver 710 are not limited to the RF transmitter and the RF receiver. In addition, the transceiver 710 may include a wired / wireless transceiver, and may include various components for sending and receiving signals. In addition, the transceiver 710 may receive a signal through a wireless channel, output the signal to the controller 720, and send a signal output from the controller 720 through a wireless channel. In addition, the transceiver 710 may receive a communication signal and output it to the processor, and may transmit the signal output by the processor to a network entity through a wired or wireless network.

[0223] According to one embodiment of the present disclosure, the storage unit 730 may store programs and data required for terminal operation. In addition, the storage unit 730 may store control information or data contained in a signal obtained from the terminal. The storage unit 730 may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of these storage media.

[0224] According to one embodiment of the present disclosure, in the present disclosure, the controller 720 may be defined as a circuit or an application specific integrated circuit or at least one processor. The processor may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling an upper layer (e.g., an application). According to one embodiment proposed in the present disclosure, the controller 720 may control the overall operation of the terminal. For example, the controller 720 may control the signal flow between the blocks to perform operations according to the flowchart described above.

[0225] The methods according to various embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0226] When implemented as software, a computer-readable storage medium may be provided, which stores one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to perform the method according to the embodiments described in the claims or specification of the present disclosure.

[0227] Such a program (software module, software) may be stored in a random access memory, a non-volatile memory including flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk read-only memory (CD-ROM), a digital versatile disk (DVD) or other forms of optical storage devices, a magnetic tape, etc. Alternatively, it may be stored in a memory composed of a combination of some or all of the above storage media. In addition, there may be multiple configuration memories of each type.

[0228] In addition, the program can be executed through a communication network (such as the Internet, an intranet, a local area network (LAN), a wireless local area network (WLAN) or a storage area network (SAN), or a communication network composed of these networks). It can be stored on an accessible attachable storage device. Such a storage device can be connected to the device executing the embodiments of the present disclosure through an external port. In addition, a separate storage device on the communication network can be connected to the device executing the embodiments of the present disclosure.

[0229] In the above-mentioned specific embodiments of the present disclosure, the components included in the present disclosure are expressed in singular or plural form according to the specific embodiments presented. However, for the convenience of description, singular or plural expression is appropriately selected according to the presented situation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural can be composed of a single component, and even the expressed components can be composed of multiple components.

[0230] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit of the present disclosure and the scope defined by the following claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: identifying the onset of a congestion state or a burst state, the congestion state being based on insufficient resources for uplink data, the burst state being associated with an increase in the uplink data; Based on the identification of the start of the congestion state or the burst state, identifying whether to perform a discard operation on a protocol data unit PDU of uplink data or a PDU set including at least one PDU; Based on the identification, performing the discard operation on the PDU or the PDU set according to a priority configured based on the importance of the PDU or the PDU set; as well as The discarding operation is stopped based on the end of the congestion state or the burst state.

2. The method according to claim 1, in, Identifying the start of the congestion state or the burst state includes: receiving a message from a base station indicating the beginning of the congestion state or the burst state, and The beginning of the congestion state or the burst state is identified based on the message.

3. The method according to claim 2, in, The message indicating the start of the congestion state or the burst state is received in the following situation: the terminal sends a buffer status report BSR for uplink data transmission to the base station, and the base station does not allocate resources for the uplink data within a predetermined time from the time point when the base station receives the BSR, The terminal is configured to report an uplink data rate to the base station, the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time to a predetermined time point, an uplink data rate at which the terminal can send resources allocated from the base station is lower than the reported uplink data rate, The terminal sends a BSR for uplink data transmission for sending a data amount, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the base station receives the BSR is less than the amount of data sent through the BSR, wherein the uplink data rate associated with the uplink data of the terminal is higher than a preconfigured data rate, wherein the uplink data rate associated with the uplink data of the terminal is higher than a recommended data rate configured by the base station, or The base station receives a report on the congestion state or the sudden state from the terminal.

4. The method according to claim 1, in, The start of the congestion state or the burst state is identified in the following situation: within a preconfigured time from a time point when a terminal or a packet data convergence protocol PDCP configured to identify the congestion state receives a PDCP service data unit SDU from a higher layer of the terminal, the base station does not allocate resources for the uplink data, wherein, from a time point before a preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number or rate of the PDUs or PDU sets discarded by the timer for a discard operation exceeds a reference value, wherein, from a time point before a preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets sequentially discarded by the timer for the discard operation exceeds a reference value, wherein, from a time point before a preconfigured time point to a predetermined time point, in a PDU or a PDU set received by a PDCP of a terminal configured to identify the congestion state from a higher layer of the terminal, the number or rate of discarded PDUs or PDU sets determined by a PDCP sequence number SN exceeds a reference value, The terminal is configured to report an uplink data rate to the base station, the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time point to a predetermined time point, an uplink data rate that can be sent through resources allocated from the base station to the terminal is lower than the reported uplink data rate, The terminal sends a BSR for data transmission and for sending a data amount to the base station, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the terminal sends the BSR is less than the amount of data sent through the BSR, wherein the uplink data rate associated with the uplink data of the terminal is higher than a preconfigured data rate, wherein the uplink data rate associated with the uplink data of the terminal is higher than a recommended data rate configured by the base station, wherein an indication of the congestion state or the burst state is received from a higher layer of the terminal, or The terminal receives an indication of the congestion state or the sudden state from the base station.

5. The method according to claim 1, further comprising: Information related to whether the terminal supports a function of the terminal to identify the congestion state or the sudden state is sent to the base station.

6. The method according to claim 5, wherein: The information related to whether the terminal supports the terminal's identification function of the congestion state or the sudden state includes at least one of the following: information related to whether the congestion state identification function is supported, information related to the type of supported congestion state identification conditions, information related to whether the sudden state identification function is supported, information related to the type of supported sudden state identification conditions, information related to the type of information that can be received and used by the upper layer, or information related to instructions or reports that can be sent / received to / from the upper layer.

7. The method according to claim 1, further comprising: Information indicating the end of the burst state is sent to the base station.

8. The method according to claim 1, further comprising: Based on the identification related to the start of the congestion state or the burst state, a report related to the congestion state or the burst state is sent to the base station.

9. The method according to claim 1, wherein: Identifying whether to perform the discard operation corresponds to identifying whether to perform the discard operation by further considering a message indicating that the discard operation is applied based on the priority.

10. The method according to claim 9, wherein: The priority is configured by the base station or a core network connected to the base station.

11. A terminal in a wireless communication system, the terminal comprising: a transceiver configured to transmit or receive a signal; as well as at least one processor, connected to the transceiver, Wherein, the at least one processor is configured to: identifying the onset of a congestion state or a burst state, the congestion state being based on insufficient resources for uplink data, the burst state being associated with an increase in the uplink data; Based on the identification of the start of the congestion state or the burst state, identifying whether to perform a discard operation on a protocol data unit PDU of uplink data or a PDU set including at least one PDU; Based on the identification, performing the discard operation on the PDU or the PDU set according to a priority configured based on the importance of the PDU or the PDU set; and The discarding operation is stopped based on the end of the congestion state or the burst state.

12. The terminal according to claim 11, in, In order to identify the beginning of the congestion state or the burst state, the at least one processor is further configured to: receiving a message from a base station indicating the beginning of the congestion state or the burst state, and The beginning of the congestion state or the burst state is identified based on the message.

13. The terminal according to claim 12, in, The message indicating the start of the congestion state or the burst state is received in the following circumstances: The terminal sends a buffer status report BSR for uplink data transmission to the base station, and the base station does not allocate resources for the uplink data within a predetermined time from a time point when the base station receives the BSR, The terminal is configured to report an uplink data rate to the base station, the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time to a predetermined time point, an uplink data rate at which the terminal can send resources allocated from the base station is lower than the reported uplink data rate, The terminal sends a BSR for uplink data transmission for sending a data amount, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the base station receives the BSR is less than the amount of data sent through the BSR, wherein the uplink data rate associated with the uplink data of the terminal is higher than a preconfigured data rate, wherein the uplink data rate associated with the uplink data of the terminal is higher than a recommended data rate configured by the base station, or The base station receives a report on the congestion state or the sudden state from the terminal.

14. The terminal according to claim 11, in, The start of the congestion state or the burst state is identified in the following situation: within a preconfigured time from a time point when a terminal or a packet data convergence protocol PDCP configured to identify the congestion state receives a PDCP service data unit SDU from a higher layer of the terminal, the base station does not allocate resources for the uplink data, wherein, from a time point before a preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number or rate of the PDUs or PDU sets discarded by the timer for the discarding operation exceeds a reference value, wherein, from a time point before a preconfigured time point to a predetermined time point, among the PDUs or PDU sets received by the PDCP of the terminal configured to identify the congestion state from the higher layer of the terminal, the number of PDUs or PDU sets sequentially discarded by the timer for the discard operation exceeds a reference value, wherein, from a time point before a preconfigured time point to a predetermined time point, in a PDU or a PDU set received by a PDCP of a terminal configured to identify the congestion state from a higher layer of the terminal, the number or rate of discarded PDUs or PDU sets determined by a PDCP sequence number SN exceeds a reference value, The terminal is configured to report an uplink data rate to the base station, the terminal reports the uplink data rate to the base station, and from a time point before a preconfigured time point to a predetermined time point, an uplink data rate that can be sent through resources allocated from the base station to the terminal is lower than the reported uplink data rate, The terminal sends a BSR for data transmission and for sending a data amount to the base station, and the amount of data that can be sent through the resources allocated by the base station within a preconfigured time from the time point when the terminal sends the BSR is less than the amount of data sent through the BSR, wherein the uplink data rate associated with the uplink data of the terminal is higher than a preconfigured data rate, wherein the uplink data rate associated with the uplink data of the terminal is higher than a recommended data rate configured by the base station, wherein an indication of the congestion state or the burst state is received from a higher layer of the terminal, or The terminal receives an indication of the congestion state or the sudden state from the base station.

15. The terminal according to claim 11, wherein: The at least one processor is further configured to send, to the base station, information related to whether the terminal supports a function of the terminal identifying the congestion state or the sudden state.

Images