Method and apparatus for transferring modality traffic information

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to operations of a terminal and a base station in a wireless communication system, wherein the base station may receive, from the terminal, a terminal capability message including information on multi-modality. The base station may transmit an RRC configuration message including multi-modality configuration information to the terminal on the basis of the information on the multi-modality. The base station may receive, from the terminal, a multi-modality report message including multi-modality data information on the basis of the multi-modality configuration information.

Description

Method and device for transmitting modality traffic information

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for transmitting multi-modality traffic information and a device capable of doing so.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The disclosed embodiment seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0009] A method of operating a base station according to one embodiment of the present disclosure may include receiving a terminal capability message including information regarding multi-modality from a terminal. The method may include transmitting an RRC (Radio Resource Control) configuration message including multi-modality configuration information to the terminal based on the information regarding multi-modality. The method may include receiving a multi-modality report message including multi-modality data information from the terminal based on the multi-modality configuration information.

[0010] A method of operating a terminal according to one embodiment of the present disclosure may include a step of transmitting a terminal capability message including information regarding multi-modality to a base station. The method may include a step of receiving an RRC configuration message including multi-modality configuration information from the base station based on the information regarding multi-modality. The method may include a step of transmitting a multi-modality report message including multi-modality data information to the base station based on the multi-modality configuration information.

[0011] In a wireless communication system according to one embodiment of the present disclosure, a base station performing communication may include a transceiver and at least one processor connected to the transceiver. The at least one processor may receive a terminal capability message including information regarding multi-modality from a terminal. The at least one processor may transmit an RRC (Radio Resource Control) configuration message including multi-modality configuration information to the terminal based on the information regarding multi-modality. The at least one processor may receive a multi-modality report message including multi-modality data information from the terminal based on the multi-modality configuration information.

[0012] FIG. 1 is a diagram illustrating the characteristics of multi-modal data processed in a mobile communication system according to one embodiment of the present disclosure.

[0013] FIG. 2 is a diagram illustrating a procedure for performing multi-modality reporting of a terminal in a mobile communication system according to one embodiment of the present disclosure.

[0014] FIG. 3 is a diagram illustrating a format of a multi-modality report for one PDU session according to one embodiment of the present disclosure.

[0015] FIG. 4 is a diagram illustrating a format of a multi-modality report for multiple PDU sessions according to one embodiment of the present disclosure.

[0016] FIG. 5 is a diagram illustrating an example in which a plurality of multi-modal data are processed by one QoS Flow according to one embodiment of the present disclosure.

[0017] FIG. 6 is a diagram illustrating a procedure for performing multi-flow reporting of a terminal in a mobile communication system according to one embodiment of the present disclosure.

[0018] FIG. 7 is a diagram illustrating the structure of a base station according to one embodiment of the present invention.

[0019] Figure 8 is a diagram illustrating the structure of a terminal according to one embodiment of the present invention.

[0020] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0021] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0022] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0023] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the specification.

[0024] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, the downlink (DL) refers to a wireless transmission path of a signal transmitted from the base station to the terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from the terminal to the base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0025] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0026] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0027] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0028] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0029] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a user equipment (UE) or mobile station (MS) transmits data or control signals to a base station (eNode B or Base Station, BS), and the downlink refers to a wireless link in which a base station transmits data or control signals to a user equipment (UE). The above multiple access method typically allocates and operates the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality, thereby distinguishing the data or control information of each user.

[0030] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers, and thus support services that simultaneously satisfy these requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0031] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0032] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0033] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of 10-5 or lower. Therefore, for URLLC-enabled services, 5G systems must provide shorter Transmit Time Intervals (TTIs) than other services, while simultaneously allocating extensive resources in the frequency band to ensure communication link reliability.

[0034] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0035] Hereinafter, a / b can be understood as at least one of a or b.

[0036] FIG. 1 is a diagram illustrating the characteristics of multi-modal data processed in a mobile communication system according to one embodiment of the present disclosure. Multi-modal data refers to data generated by various types of devices or destined for various destinations, but may refer to data related to applications or tasks with the same purpose. Such multi-modal data may be composed of multiple modal data or multiple modalities, and there may be strong interdependencies between each modal data. For example, if data of one modality is transmitted at a specific time, there may be data of another modality that must be transmitted and processed together. Conversely, if one of the data of one modality is not transmitted, the transmission of data of the other modality may become unnecessary. An example of such multi-modal data is video data accompanied by sound, where each modality may correspond to voice and video. At this point, video data at a specific point in time may have audio data that must be transmitted at a similar time, indicating a dependency between video and audio. Therefore, when transmitting such multimodal data over a communications network, scheduling that takes intermodal dependencies into account can improve transmission efficiency.

[0037] The embodiment of Fig. 1 shows an example of multi-modal data having two modal data (modalities), a first modality (110) and a second modality (120). In the embodiment of Fig. 1, each modal data is illustrated as being periodic traffic, but it is not necessarily required to have periodicity, and even if it has periodicity, it may have different periods. There may be dependencies between each modal data, and there may be dependencies between the periods of each modal data. The embodiment of Fig. 1 shows an example in which the first modality data is transmitted four times (111, 112, 113, 114) while the second modality data is generated eight times (121, 122, 123, 124), and two data are generated per period. In addition, the first modality data transmitted in step 111 and the second modality data transmitted in step 121 are shown to have mutual dependencies. This may mean that although the first modality data and the second modality data are different modal data, they must be transmitted at similar times because they perform the same purpose of application or task, or that they have dependencies, such as the non-transmission of one modal data making the transmission of the other modal data unnecessary. In addition, it was shown that the first modality data transmitted in step 112 and the second modality data transmitted in step 122 have interdependencies. In addition, it was shown that the first modality data transmitted in step 113 and the second modality data transmitted in step 123 have interdependencies, and the first modality data transmitted in step 114 and the second modality data transmitted in step 124 have interdependencies.

[0038] FIG. 2 is a diagram illustrating a procedure for performing multi-modality reporting of a terminal in a mobile communication system according to one embodiment of the present disclosure.

[0039] When transmitting multimodal data described in FIG. 1 over a mobile communication network between a terminal and a base station, it may be necessary to perform scheduling that reflects the characteristics of the multimodal data. Such scheduling may involve transmitting data with interdependencies simultaneously or at similar times. In other embodiments, a transmission failure or packet discard of one modality's data may also trigger packet deletion of other modality's data with different interdependencies. However, scheduling that reflects the characteristics of such multimodal data may be performed based on recognition by the base station or mobile communication core network device, or based on settings by the base station or mobile communication core network device. Since the device where the actual multimodal data application runs may be the terminal, it is necessary for the terminal (210) to transmit information about the multimodal traffic that the terminal is attempting to process or is currently processing to the base station (220) and the core network device (250). To this end, the terminal may transmit a UE Capability message (230) to the base station, indicating that the terminal has the capability to recognize and report to the base station that it processes multi-modal data. This message may include whether the terminal can transmit information on multi-modal data it wishes to process to the base station or whether the terminal supports at least one scheduling method that takes into account the characteristics of multi-modal data. This information may be referred to as multi-modal awareness information because it is based on the terminal's awareness of multi-modal data. The transmission of this multi-modal awareness information to the base station that the terminal supports may be triggered at a higher layer, such as the application layer.

[0040] Based on this, the base station can set up to indicate to the terminal information about the multi-modal data that the terminal is trying to process (try to transmit or receive) or is processing (transmitting or receiving). (235) Such a message can be transmitted as one of the RRC (Radio Resource Control) messages. In another embodiment, the corresponding content can be set in the MAC CE (Medium Access Control - Control Element) or the DCI (Downlink Control Information) message of the PDCCH (Physical Downlink Control Channel) or other separate messages. Thereafter, the terminal can transmit the multi-modality data information of the terminal to the base station. (240) This transmission of the multi-modality data information by the terminal to the base station can be referred to as a multi-modality report. The multi-modality report message can include an identifier of the multi-modality data and an identifier of each modality. In one embodiment, the identifier of the multi-modality data can be a multi-modal service ID used by the PCF, which is one of the core network devices. The identifier of each individual modality that constitutes multi-modality data can be a QoS Flow ID (QFI). If a modality is transmitted on a single Data Radio Bearer (DRB), it can also be the DRB ID. If multi-modal data spans multiple protocol data unit (PDU) sessions, each modality can be represented by a combination of the PDU session ID and the individual modality identifier. In addition, when there is an interdependency between each modality, the specific type of dependency can be indicated.Such dependencies may include transmissions at similar times, and may include at least one of the allowable transmission timing differences or commonly required delay requirements. Furthermore, they may also include values ​​of modalities that do not need to be transmitted when data from other modalities is discarded. In one embodiment, information regarding which scheduling method is required may be included in consideration of the dependencies. This multi-modality report message may be transmitted as an RRC message transmitted by the terminal to the base station. In one embodiment, it may be transmitted in a UE Assistance Information message. In this case, an indicator indicating which scheduling method is preferred may be included in consideration of the characteristics of the multi-modality data. In one embodiment, the preference may be indicated for each scheduling method. In one embodiment, the message may be transmitted in a MAC CE or a NAS (Non-access Stratum) message. The information included in the multi-modality report message transmitted in step 240 may include the contents described below in FIGS. 3 and 4.

[0041] When the base station (220) receives a multi-modality report message (240) from a terminal, it can transmit all or part of the information included therein to a core network device (250). (255) This core network device can be at least one of a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF). The message of step 255 can be a message in another format that reprocesses only the necessary information from the message of step 240. Based on this, the core network device (250) can transmit a message such as a policy update (260) to the terminal. The policy update message of step 260 can include an instruction to activate or enable a scheduling method that considers multi-modal data in a mobile communication network, or to transmit or update a QoS (Quality of Service) profile for multi-modal data or each modality. Based on this, the base station can instruct the terminal to perform scheduling considering the characteristics of multi-modal data through an RRC Reconfiguration message. (265) Afterwards, the terminal can transmit an RRC Reconfiguration Complete message to the base station indicating that it has applied the received RRC Reconfiguration message. (270)

[0042] FIG. 3 is a diagram illustrating a format of a multi-modality report for one PDU session according to one embodiment of the present disclosure.

[0043] The multi-modality report message described in step 240 of FIG. 2 may include information about multi-modal data that the terminal is attempting to process (send or receive) or is processing (send or receive). This multi-modality report message may be transmitted as one of the RRC (Radio Resource Control) messages. In one embodiment, the content may be included in a MAC CE (Medium Access Control - Control Element) or UCI (Downlink Control Information) message or another separate message. The multi-modality report message may include an identifier of the multi-modality data and an identifier of each modality. In one embodiment, the identifier of the multi-modality data may be a multi-modal service ID used by a PCF, which is one of the core network devices. In this case, the identifier of each individual modality that constitutes the multi-modality data may be a QoS Flow ID (QFI). That is, each individual modality may correspond to a QoS Flow. In the embodiment of FIG. 3, an example is shown in which one PDU session (310) is processed within a terminal, and the terminal has a total of four QoS Flows, namely, a first QoS Flow (311), a second QoS Flow (312), a third QoS Flow (313), and a fourth QoS Flow (314). Here, QoS Flows belonging to the same PDU session do not need to constitute a single multi-modal data. In the embodiment of FIG. 3, the first QoS Flow (311) and the third QoS Flow (313) are multi-modal data having a single multi-modality. In addition, it is shown that the first QoS Flow and the third QoS Flow have an interdependency. The multi-modality report message can indicate that these QoS Flows have an interdependency.To this end, a list of QoS Flow IDs that have interdependencies in a single multi-modality data may be indicated. When interdependencies exist between multiple modalities, the specific type of dependency may be indicated. This dependency may mean that data is transmitted at the same or similar time points, and may include at least one of an allowable transmission time difference or a commonly required delay time requirement. Furthermore, the value of a modality that does not need to be transmitted when data from another modality is discarded may also be included. In one embodiment, information regarding the required scheduling method considering the dependencies may be included. In addition, priority information according to importance may be included among QoS Flows belonging to a single multi-modal data. For example, each QoS Flow may have its own priority value. However, in some embodiments, only the relative priorities between QoS Flows may be included, indicating which QoS Flow should be processed with higher priority. This can assist the base station in determining the scheduling policy for the QoS Flow. Such multimodal data often needs to be transmitted at similar times, which may necessitate processing multiple QoS Flows within a single DRB and performing reordering and in-sequence delivery functions at the Packet Data Convergence Protocol (PDCP) layer. To this end, the multimodality reporting message may include whether the multimodal data requires reordering and in-sequence delivery. In one embodiment, this may be transmitted within a UE Assistance Information message. In this case, an indicator indicating a preference for scheduling that takes into account the characteristics of the multimodality data may be included.In one embodiment, preferences may be indicated for each scheduling method. While the embodiment of FIG. 3 illustrates the transmission of information about multimodal data with interdependencies, multimodality reports may also be transmitted for base station scheduling purposes even when interdependencies between QoS Flows are not required.

[0044] FIG. 4 is a diagram illustrating a format of a multi-modality report for multiple PDU sessions according to one embodiment of the present disclosure.

[0045] The multi-modality report message described in step 240 of FIG. 2 may include information about multi-modal data that the terminal is attempting to process (send or receive) or is processing (send or receive). This multi-modality report message may be transmitted as one of the RRC (Radio Resource Control) messages. In one embodiment, the content may be included in a MAC CE (Medium Access Control - Control Element) or UCI (Downlink Control Information) message or another separate message. The multi-modality report message may include an identifier of the multi-modality data and an identifier of each modality. In one embodiment, the identifier of the multi-modality data may be a multi-modal service ID used by a PCF, which is one of the core network devices. In this case, the identifier of each individual modality that constitutes the multi-modality data may be a QoS Flow ID (QFI). That is, each individual modality may correspond to a QoS Flow. In the embodiment of FIG. 4, two PDU sessions, a first PDU session (410) and a second PDU session (420), are processed within a terminal, and the terminal has a total of three QoS Flows, namely, a first QoS Flow (411), a second QoS Flow (412), and a third QoS Flow (413) in the first PDU session, and an example of a total of two QoS Flows, namely, a fourth QoS Flow (424) and a fifth QoS Flow (425) in the second PDU session is shown. Here, QoS Flows belonging to the same PDU session do not need to constitute one multi-modal data, and QoS Flows belonging to different PDU sessions can constitute one multi-modal data.In the embodiment of FIG. 4, the first QoS Flow (411) belonging to the first PDU session and the fourth QoS Flow (424) belonging to the second PDU session are multi-modal data having one multi-modality. In addition, it is indicated that there is interdependency between the first QoS Flow and the fourth QoS Flow. The multi-modality report message can indicate that these QoS Flows have interdependency. For this purpose, a list of (QoS Flow ID, PDU Session ID) pairs that have interdependency between one multi-modality data can be indicated. When there is interdependency between multiple modalities, it can also indicate which dependency they have specifically. This dependency can mean that they are transmitted at the same time or a similar time, and can include at least one of an allowable transmission time difference or a commonly required delay time requirement. In addition, the value of a modality that does not need to be transmitted when data of another modality is discarded can also be included. In one embodiment, information regarding the required scheduling method considering dependencies may be included. Furthermore, priority information based on importance among QoS Flows within a single multi-modal data set may be included. For example, each QoS Flow may have its own priority value. However, in some embodiments, only the relative priorities among QoS Flows may be included, indicating which QoS Flow should be processed with higher priority. This can assist the base station in determining the scheduling policy for the QoS Flows.Such multimodal data often needs to be transmitted at similar times, which may require multiple QoS Flows to be processed in a single DRB and reordering and in-sequence delivery functions performed at the Packet Data Convergence Protocol (PDCP) layer. To this end, the multimodality report message may include whether the multimodal data requires reordering and in-sequence delivery. In one embodiment, this may be transmitted in a UE Assistance Information message. In this case, an indicator indicating a preference for scheduling that takes into account the characteristics of the multimodality data may be included. In one embodiment, preferences may be indicated for each scheduling method.

[0046] Although the embodiment of FIG. 4 illustrates an example of transmitting information about multi-modal data having interdependence, multi-modality reports may also be transmitted for scheduling purposes at a base station even when interdependence between QoS Flows is not required.

[0047] FIG. 5 is a diagram illustrating an example in which multiple multi-modal data are processed by a single QoS Flow according to an embodiment of the present disclosure. A terminal (500) that transmits and receives multi-modal data may have multiple child devices through a technology such as tethering. The embodiment of FIG. 5 illustrates an example in which a terminal is connected to two child devices, a first child device (510) and a second child device (520). In this case, if data having similar QoS requirements are generated in each child device, these data may be mapped to the same QoS Flow and processed in the AS (Access Stratum) responsible for connecting the terminal and the base station. The embodiment of FIG. 5 illustrates an example in which a first data flow (515) generated in the first child device and a second data flow (525) generated in the second child device are mapped to the first QoS Flow (531) and processed in the terminal. For example, if some sensor data from a first child device corresponds to a first data flow, and similar sensor data from a second child device corresponds to a second data flow, these data flows may have similar QoS requirements and may be transmitted corresponding to the same QoS Flow. In this case, from the perspective of the AS between the base station and the terminal, it may be considered that a single data is transmitted in a single QoS Flow, but in reality, it may correspond to an independent QoS Flow as an independent data flow and require separate QoS Handling. In one embodiment, even if multiple data flows are mapped to a single QoS Flow, the scheduling policy of the corresponding QoS Flow may need to be updated so as to satisfy all requirements of each data flow.To this end, if there are multiple data flows that require separate QoS Handling in a single QoS Flow, or if a scheduling policy that satisfies all QoS requirements of multiple data flows is required, the terminal needs to report this to the base station. In one embodiment, the terminal also needs to notify the base station of the fact that multiple data flows are processed in a single QoS Flow. FIG. 6 describes the procedures related to the multi-flow report message that notifies the base station that multiple data flows are processed in a single QoS Flow.

[0048] FIG. 6 is a diagram illustrating a procedure for performing multi-flow reporting by a terminal in a mobile communication system according to one embodiment of the present disclosure. In a scenario such as tethering described in FIG. 5, when a terminal processes multiple actual data flows generated from multiple terminals in addition to the QoS flows it processes, the base station may need to perform scheduling that reflects this. One possible method for performing such scheduling is to map each data flow to a different QoS flow. This scheduling can be performed based on recognition by the base station or mobile communication core network device, or based on settings by the base station or mobile communication core network device. Since information such as whether the terminal is actually performing an operation with a child device, such as tethering, or processing multiple actual data flows is information that the terminal (610) needs to transmit information about the data flows that the terminal is attempting to process to the base station (620) and the core network device (650). To this end, the terminal may transmit a UE Capability message (630) to the base station, indicating that the terminal has the ability to recognize and report to the base station that it processes such multi-flow data. This message may include whether the terminal can transmit to the base station information on multiple data flows (multi-flow information) that it wishes to process. Since this information is based on the terminal's awareness of multi-flow data, it may also be referred to as multi-flow awareness information. The transmission of such multi-flow awareness information to the base station by the terminal may be triggered at a higher layer, such as the application layer.

[0049] Based on this, the base station can set up an instruction for the terminal to report information on multi-flow data that the terminal is trying to process (try to transmit or receive) or is processing (transmitting or receiving) to the base station. (635) Such a message can be transmitted as one of the RRC (Radio Resource Control) messages. In one embodiment, the corresponding content can be set up in a MAC CE (Medium Access Control - Control Element) or a PDCCH (Physical Downlink Control Channel) DCI (Downlink Control Information) message or other separate message. Thereafter, the terminal can transmit its multi-flow data information to the base station. (640) This transmission of multi-flow data information by the terminal to the base station can be referred to as a multi-flow report. The multi-flow report message can include the QoS Flow ID of the QoS Flow through which multiple data flows are being transmitted. And, the QoS requirements required by each data flow can be included. This may additionally include the required data rate, packet delay, and packet delivery ratio (1 minus the probability of non-delivery). If this data flow belongs to multi-modality data, the multi-modal service ID used by PCF, one of the core network devices, and the QoS Flow ID of other QoF Flows with interdependence may also be included and transmitted. Furthermore, the corresponding contents may be included and transmitted in the multi-modality report message described in FIGS. 2, 3, and 4.If multiple data flows included in a QoS Flow have similar or identical QoS requirements, the number of data flows processed in the corresponding QoS Flow may be reported in a multi-flow report message. The base station receiving the multi-flow report message may perform an operation to separately process each data flow based on the multi-flow report message. The multi-flow report message may be transmitted as an RRC message transmitted from the terminal to the base station. In one embodiment, it may be transmitted in a UE Assistance Information message. In this case, an indicator indicating that the multi-flow prefers separate scheduling may be included. However, in another embodiment, the message may be transmitted in a MAC CE or NAS (Non-access Stratum) message.

[0050] When the base station (620) receives a multi-flow report message (640) from a terminal, it can transmit all or part of the information included therein to a core network device (650). (655) This core network device can be at least one of a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF). The message of step 655 can be a message in another format that reprocesses only the necessary information from the message of step 640. Based on this, the core network device (650) can transmit a message such as a policy update (660) to the terminal. The policy update message of step 660 can include an instruction to activate or enable a scheduling method that takes multi-flow data into account in a mobile communication network, or to transmit or update a QoS (Quality of Service) profile for multi-flow data or each data flow. At this time, each data flow can also be remapped to a different QoS Flow.

[0051] Based on this, the base station can instruct the terminal to perform scheduling considering the characteristics of multi-flow data by an RRC Reconfiguration message. (665) This may be accompanied by QoS Flow remapping for each data flow used by the terminal in the AS. In one embodiment, QoS Flow remapping may be instructed by setting the RDI and RQI fields of the SDAP (Service Data Adaptation Protocol) header instead of the RRC Reconfiguration message. Thereafter, the terminal can transmit an RRC Reconfiguration Complete message to the base station indicating that it has applied the received RRC Reconfiguration message. (670)

[0052] FIG. 7 is a diagram illustrating the structure of a base station according to one embodiment of the present invention. Referring to FIG. 7, the base station may include a transceiver (710), a control unit (720), and a storage unit (730). In the present invention, the control unit (720) may be defined as a circuit, an application-specific integrated circuit, or at least one processor. The transceiver (710), the control unit (720), and the storage unit (730) of the base station may operate according to the communication method of the base station described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the control unit, and the storage unit may be implemented in the form of a single chip.

[0053] The transceiver (710) can transmit and receive signals with other network entities. For example, the transceiver (710) can transmit system information to a terminal, and can transmit a synchronization signal or a reference signal. Here, the signal can include control information and data. To this end, the transceiver can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0054] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0055] The control unit (720) can control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the control unit (720) can control the signal flow between each block so that operations according to the flowchart described above are performed. There may be multiple control units (720), and the control units (720) can perform component control operations of the base station by executing a program stored in the storage unit (730).

[0056] The storage unit (730) can store at least one of the information transmitted and received through the transceiver unit (710) and the information generated through the control unit (720). The storage unit (730) can store programs and data necessary for the operation of the base station. In addition, the storage unit (730) can store control information or data included in signals transmitted and received by the base station. The storage unit (730) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of storage units (830).

[0057] FIG. 8 is a diagram illustrating the structure of a terminal according to an embodiment of the present invention. Referring to FIG. 8, the terminal may include a transceiver (810), a control unit (820), and a storage unit (830). In the present invention, the control unit may be defined as a circuit, an application-specific integrated circuit, or at least one processor. The transceiver (810), the control unit (820), and the storage unit (830) of the terminal may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver, the control unit, and the storage unit may be implemented in the form of a single chip.

[0058] The transceiver (810) can transmit and receive signals with other network entities. For example, the transceiver (810) can receive system information from a base station, and can receive synchronization signals or reference signals. Here, the signals can include control information and data. To this end, the transceiver can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0059] The control unit (820) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (820) can control the signal flow between each block so that operations according to the flowchart described above are performed. There may be multiple control units (820), and the control units (820) can perform component control operations of the terminal by executing a program stored in the storage unit (830).

[0060] The storage unit (830) can store at least one of the information transmitted and received through the transmission and reception unit (810) and the information generated through the control unit (820). The storage unit (830) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of storage units (830).

[0061] A method of operating a base station according to one embodiment of the present disclosure may include receiving a terminal capability message including information regarding multi-modality from a terminal. The method may include transmitting an RRC (Radio Resource Control) configuration message including multi-modality configuration information to the terminal based on the information regarding multi-modality. The method may include receiving a multi-modality report message including multi-modality data information from the terminal based on the multi-modality configuration information.

[0062] In one embodiment, the method may include transmitting multi-modality data information to a core network entity. The method may include receiving a message regarding an updated QoS policy from the core network entity based on the multi-modality data information. The method may include transmitting an RRC reconfiguration message including scheduling information based on the message regarding the updated QoS policy to the terminal.

[0063] In one embodiment, the terminal capability message may include information regarding whether the terminal is capable of transmitting multi-modality data or whether the terminal supports a scheduling method for multi-modality data.

[0064] In one embodiment, the terminal capability message may include information regarding whether multi-flow data can be transmitted to multiple child devices connected via tethering.

[0065] In one embodiment, the multi-modality report message may include at least one multi-modality identifier or identifier of multi-modality data for identifying the multi-modality service.

[0066] In one embodiment, the multi-modality data information may include information regarding interdependencies between multiple modality data.

[0067] In one embodiment, the multi-modality reporting message may be received via at least one of a UE Assistance Information (UAI), a terminal capability message, an RRC message, a Medium Access Control Control Element (MAC CE), or a Non-Access Stratum (NAS) message.

[0068] A method of operating a terminal according to one embodiment of the present disclosure may include a step of transmitting a terminal capability message including information regarding multi-modality to a base station. The method may include a step of receiving an RRC configuration message including multi-modality configuration information from the base station based on the information regarding multi-modality. The method may include a step of transmitting a multi-modality report message including multi-modality data information to the base station based on the multi-modality configuration information.

[0069] In a wireless communication system according to one embodiment of the present disclosure, a base station performing communication may include a transceiver and at least one processor connected to the transceiver. The at least one processor may receive a terminal capability message including information regarding multi-modality from a terminal. The at least one processor may transmit an RRC (Radio Resource Control) configuration message including multi-modality configuration information to the terminal based on the information regarding multi-modality. The at least one processor may receive a multi-modality report message including multi-modality data information from the terminal based on the multi-modality configuration information.

[0070] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0071] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

Claims

1. In a method for a base station to perform communication in a wireless communication system, A step of receiving a terminal capability message including information about multi-modality from a terminal; A step of transmitting an RRC (Radio Resource Control) configuration message including multi-modality configuration information to the terminal based on the information about the multi-modality; and A method comprising: receiving a multi-modality report message including multi-modality data information from the terminal based on the multi-modality setting information; 2. In the first paragraph, the method, A step of transmitting the multi-modality data information to a core network entity; A step of receiving a message regarding an updated QoS (Quality of Service) policy from the core network entity based on the multi-modality data information; and A method further comprising: transmitting an RRC reset message including scheduling information based on a message regarding the updated QoS policy to the terminal; 3. In paragraph 1, A method wherein the terminal capability message includes information regarding whether the terminal can transmit multi-modality data or whether the terminal supports a scheduling method for the multi-modality data.

4. In paragraph 1, A method wherein the terminal capability message includes information regarding whether multi-flow data can be transmitted to multiple child devices connected via tethering.

5. In paragraph 1, A method wherein the multi-modality report message includes at least one multi-modality identifier or an identifier of multi-modality data for identifying a multi-modality service.

6. In paragraph 1, A method wherein the multi-modality reporting message includes information regarding interdependencies between multiple modality data.

7. In paragraph 1, A method wherein the multi-modality reporting message is received via at least one of a UAI (UE Assistance Information), a terminal capability message, an RRC message, a MAC CE (Medium Access Control Control Element), or a NAS (Non-Access Stratum) message.

8. In a method for a terminal to perform communication in a wireless communication system, A step of transmitting a terminal capability message including information about multi-modality to a base station; A step of receiving an RRC (Radio Resource Control) configuration message including multi-modality configuration information from the base station based on the information about the multi-modality; and A method comprising: a step of transmitting a multi-modality report message including multi-modality data information to the base station based on the multi-modality setting information; 9. In the 8th paragraph, the method, A step of receiving an RRC reset message from the base station including scheduling information based on a message regarding an updated Quality of Service (QoS) policy; further comprising: A method wherein the above QoS policy is updated by a core network entity based on the multi-modality data information.

10. In paragraph 8, A method wherein the terminal capability message includes information regarding whether the terminal can transmit multi-modality data or whether the terminal supports a scheduling method for the multi-modality data.

11. In paragraph 8, A method wherein the terminal capability message includes information regarding whether multi-flow data can be transmitted to multiple child devices connected via tethering.

12. In paragraph 8, A method wherein the multi-modality report message includes at least one multi-modality identifier or an identifier of multi-modality data for identifying a multi-modality service.

13. In paragraph 8, A method wherein the multi-modality reporting message includes information regarding interdependencies between multiple modality data.

14. In paragraph 8, A method wherein the above multi-modality reporting message is transmitted via at least one of a UAI (UE Assistance Information), a terminal capability message, an RRC message, a MAC CE (Medium Access Control Control Element), or a NAS (Non-Access Stratum) message.

15. In a base station performing communication in a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, wherein the at least one processor comprises: Receive a terminal capability message containing information about multi-modality from the terminal, Based on the information about the multi-modality, an RRC (Radio Resource Control) configuration message including multi-modality configuration information is transmitted to the terminal, A base station that receives a multi-modality report message including multi-modality data information from the terminal based on the multi-modality setting information.

Images