Communication device, control method, and program

Abstract

This technology provides the ability to appropriately modify the mapping between LCH (Logical Channel) and LCG (Logical Channel Group). [Solution] A communication device according to one aspect of the present disclosure is a communication device operating as a terminal, and includes a transmission means for transmitting information to a communication device operating as a base station, notifying that two or more types of LCHs (Logical Channels), each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a communication apparatus, a control method, and a program. BACKGROUND ART

[0002] Cellular communication standards are being formulated in The 3rd Generation Partnership Project (3GPP (registered trademark)). In 3GPP, studies are being conducted to support various applications as application targets of cellular communication standards (hereinafter referred to as "3GPP standards"), and as one of such studies, investigations toward application to XR (eXtended Reality) are underway. Here, XR refers to technologies that provide new experiences integrating real space and virtual space, such as VR (Virtual Reality), AR (Augmented Reality), and MR (Mixed Reality).

[0003] The 3GPP standard envisions an XR system that connects a high-definition CG rendering function provided by an XR server (such as a cloud server) with a high-performance XR device (such as an HMD) via 5G (NR (New Radio)) cellular communication. CG is an abbreviation for Computer Graphics, and HMD is an abbreviation for Head Mounted Display. In such an XR system, 5G cellular communication is required to provide high-quality, low-latency, and stable real-time video transmission. Furthermore, application data transmitted between the XR server and the high-performance XR device (for example, in an XR application) must satisfy mutual delay requirements between multiple different data types (e.g., video, audio, haptic information, etc.). Mutual delay requirements refer to requirements (constraints) regarding the delay between one data type and another, such as video not being delayed by more than 15ms relative to haptic information. Constraint information such as 15ms may also be called a synchronization threshold. Hereafter, multiple different data types or data of multiple different data types (multiple different kinds of data) will be referred to as multimodality. Furthermore, satisfying mutual delay requirements between multiple different data types will be referred to as satisfying intermodal delay requirements. This delay requirement is one of the multimodal requirements.

[0004] In relation to multimodality, a multimodal service (or multimodality service) refers to a communication service consisting of multiple interrelated data flows coordinated by an application (e.g., an XR application). These data flows can transmit data of multiple different data types (e.g., video, audio, haptic information, etc.).

[0005] On the other hand, in the 3GPP standard, each application data transmitted between an XR server and a high-performance XR device is treated as a QoS (Quality of Service) flow according to the QoS requirements. In a 5G cellular communication network, base stations (hereinafter also referred to as gNBs (gNodeBs)) transmit each QoS flow by assigning it to a logical channel (LCH) that can satisfy its respective QoS requirements. Furthermore, for efficiency, LCHs with equivalent QoS requirements are managed together in the same logical channel group (LCG), and bandwidth is allocated according to the BSR transmitted from the UE. In addition, if delay-critical data occurs in the UE, a mechanism has been introduced to encourage preferential bandwidth allocation by sending the remaining validity time of the data to the gNB via a DSR. BSR is an abbreviation for Buffer Status Report, DSR is an abbreviation for Delay Status Report, and UE is an abbreviation for User Equipment. UE may also be called a terminal or user terminal, and includes, for example, an XR device capable of 5G cellular communication.

[0006] Thus, in uplink (UL) communication within a RAN (Radio Access Network), the management system is based on LCG (Loop Controller Group) units. When delay requirements are met between LCHs in a multimodal relationship, it is desirable that they be the same LCG. In other words, if LCHs in the same multimodal relationship are assigned to different LCGs, the processing becomes more complex for the UE and gNB in ​​terms of BSR, DSR, and bandwidth allocation, so management by the same LCG is required. Here, "(the same) multimodal relationship A (e.g., LCH)" refers to A (e.g., LCH) belonging to (associated with) the same multimodal service.

[0007] In the 5G standardization process by 3GPP, the RAN2 working group, which develops wireless communication protocols, is discussing how to meet the latency requirements between multiple modalities.

[0008] Non-patent document 1 proposes extending UAI to meet multimodal requirements, enabling the UE to provide RAN with support information regarding delay requirements between multiple QoS flows that have multimodal relationships in the UL. This support information includes MMSID (Multi-Modal Service ID), which explicitly indicates that a data flow is related to a multimodal service. UAI is an abbreviation for UE Assistance Information and is a special RRC (Radio Resource Control) message.

[0009] Furthermore, Non-Patent Document 2 proposes that a base station can enable scheduling that takes into account the delay requirements between each QoS flow by assigning relevant LCHs to the same LCG based on the delay requirements between multiple modalities. [Prior art documents] [Non-patent literature]

[0010] [Non-Patent Document 1] “Views on Support of Multi-Modality Services in Rel-19 XR”,R2-2406676,3GPP TSG-RAN WG2 Meeting #127,August 2024 [Non-Patent Document 2] “Discussion on Multi-modality for XR”,R2-2406370,3GPP TSG-RAN WG2 Meeting #127,August 2024 [Overview of the project] [Problems that the invention aims to solve]

[0011] In UL (Urban Link) configurations, to meet the intermodal latency requirements demanded by UE (Urban User), it is desirable that LCHs belonging to the same multimodal service be mapped (assigned) to the same LCG (Landing Chain Group) at the base station. However, under current specifications, LCHs belonging to the same multimodal service may be mapped to different LCGs.

[0012] One aspect of this disclosure aims, in view of the above, to provide a technique that enables appropriate modification of the mapping between the LCH and LCG. [Means for solving the problem]

[0013] A communication device according to one aspect of this disclosure is a communication device operating as a terminal, and includes a transmission means for transmitting information to a communication device operating as a base station, notifying that two or more types of LCHs (Logical Channels), each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group). [Effects of the Invention]

[0014] According to one aspect of this disclosure, it is possible to appropriately modify the mapping between the LCH and LCG. [Brief explanation of the drawing]

[0015] [Figure 1] This is a diagram showing an example configuration of a wireless communication system according to Embodiment 1. [Figure 2] This is a block diagram showing an example of the hardware configuration of a terminal according to Embodiment 1. [Figure 3] This is a block diagram showing an example of the functional configuration of a terminal according to Embodiment 1. [Figure 4] This is a block diagram showing an example of the hardware configuration of a base station according to Embodiment 1. [Figure 5] This is a block diagram showing an example of the functional configuration of a base station according to Embodiment 1. [Figure 6]1 is a sequence diagram illustrating an operation example of a wireless communication system according to Embodiment 1. [Figure 7] 3 is a diagram illustrating an example of a UAI message format according to Embodiment 1. [Figure 8] 6 is a flowchart illustrating an operation example of a terminal according to Embodiment 1. [Figure 9] 9 is a flowchart illustrating an operation example of a base station according to Embodiment 1. [Figure 10] 12 is a sequence diagram illustrating an operation example of a wireless communication system according to Embodiment 2. [Figure 11] 15 is a diagram illustrating an example of an RRC Reestablishment Request message format according to Embodiment 2. [Modes for Carrying Out the Invention]

[0016] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the subject matter recited in the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are necessarily essential to the present disclosure, and the plurality of features may be arbitrarily combined. Furthermore, in the accompanying drawings, the same or similar configurations are denoted by the same reference numerals, and redundant descriptions may be omitted.

[0017] (Embodiment 1) <Wireless Communication System> Figure 1 shows an example configuration of a wireless communication system according to this embodiment. The wireless communication system 100 shown in Figure 1 supports XR. While embodiments are described below with respect to a 5G system, this disclosure is not intended to be limited to 5G systems. For example, this disclosure may be applied to next-generation mobile communication systems such as 6G, LTE (Long Term Evolution), LTE-A (LTE-Advanced), and combinations thereof. For example, the base station 110 described below may be a base station supporting LTE, 6G, or a 6G or later generation. The base station 110 may be, for example, an eNB, or a NB supporting 6G or a 6G or later. It should be understood that this disclosure is applicable to any wireless communication system supporting XR or similar services.

[0018] The wireless communication system 100 (also called the wireless communication network 100) includes a base station (gNB) 110, a terminal (UE) 111, and a core network (CN) 120.

[0019] The gNB110 allocates downlink (DL) and uplink (UL) wireless resources to the UE111.

[0020] gNB110 is a network node that provides access points to the CN, which includes CN120, of the UE, which includes UE111. gNB110 is part of the RAN. Hereafter, the terms RAN node, base station, and gNB are used interchangeably.

[0021] The gNB110 controls one or more cells. A cell is a geographical area of ​​a radio network defined by the frequency used to transmit data, and can be uniquely identified by a terminal from an identifier (identification information, ID) broadcast across the geographical area. The gNB110 can service several UEs. The base station to which a terminal is connected by establishing an RRC (Radio Resource Control) connection with the base station is called the terminal's serving base station. A cell controlled by a serving base station and containing terminals is called a serving cell.

[0022] The gNB110 communicates with the UE111 wirelessly. The gNB110 receives UL signals transmitted from the UE111. The gNB110 transmits DL signals to the UE111. The DL signals include, for example, DL data (signals) and control information. The DL control information includes, for example, Downlink Control Information (DCI) which includes information indicating the scheduling of signal transmission by the UE111 (e.g., UL Grant). For example, the DL signals may also include upper-layer control information (e.g., RRC control information), reference signals, etc.

[0023] The channels used to transmit DL signals include, for example, a data channel and a control channel. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, gNB110 may transmit control information to UE101 using the PDCCH and data signals using the PDSCH.

[0024] UE111 may be an XR device such as an augmented reality wearable, such as a virtual reality helmet or goggles. UE may generally be a device capable of wirelessly communicating with one or more CNs (including CN120) via one or more RANs. Such a device may be any wireless device, such as a wireless communication device or terminal, an IoT device, a machine-type communication (MTC) device, a device-to-device (D2D) terminal, or a user device. IoT is an abbreviation for Internet of Things. User devices may be, for example, smartphones, desktop computers, mobile phones, tablets, cameras, game consoles, wearable devices, etc.

[0025] UE111 communicates wirelessly with gNB110. UE111 receives DL signals transmitted from gNB110. UE111 transmits UL signals to gNB110. UL signals include, for example, UL data (signals) and control information (e.g., Uplink Control Information (UCI) including SR (Scheduling Request)). UL signals may also include, for example, information regarding UE111's processing capabilities (capability information; e.g., UE capability), reference signals, etc.

[0026] The channels used to transmit UL signals include, for example, a data channel and a control channel. For example, the data channel may include PUSCH (Physical Uplink Shared Channel), and the control channel may include PUCCH (Physical Uplink Control Channel). For example, UE111 may transmit control information to gNB110 using PUCCH and data signals using PUSCH.

[0027] In the example shown in Figure 1, UE111 has completed the RRC connection process with gNB110 and is in a state where it can communicate with gNB110. That is, the internal state of UE111 is RRC_CONNECTED.

[0028] Furthermore, in the example shown in Figure 1, UE111 is connected to the internet line 113 via IP (Internet Protocol) through gNB110 and CN120, and is in a state where it can communicate via IP with the server device 114, which is an XR server.

[0029] CN120 includes a User Plane Function (UPF) 121, which is a network function (NF) that handles user plane communication (e.g., forwarding data packets). CN120 also includes an Access and Mobility Management Function (AMF) 122, which is an NF that manages access and mobility. CN120 also includes a Session Management Function (SMF) 123, which is an NF that manages sessions and QoS.

[0030] It goes without saying that the number of UEs, gNBs, and / or CNs present in the wireless communication system 100 is not limited to the numbers shown in Figure 1.

[0031] In UE111, the XR application client (hereinafter simply referred to as the XR client) is launched. The XR client connects to the XR application server (hereinafter simply referred to as the XR app server) running in server device 114, and the XR application is executed in UE111 (and server device 114). The XR client running in UE111 compresses and encodes the video (hereinafter referred to as real video) and surrounding audio captured by the camera mounted on its station using a codec. The XR client then transmits the compressed and encoded data to the XR app server running in server device 114 according to RTP (Real-time Transport Protocol).

[0032] At this time, the XR client (UE111) transmits inertial information such as 6DOF (Six Degrees of Freedom), haptic information, and operation information from the controller to the server device 114 (XR application server). This communication is conducted according to UDP (User Datagram Protocol).

[0033] The XR application server operating in server device 114 estimates the position and orientation of the XR device UE111 based on received real-world video and 6DOF information. The XR application server renders a 2D video frame (hereinafter referred to as CG video) from the viewpoint of UE111 relative to a 3D CG model, according to the estimated position and orientation of UE111. CG is an abbreviation for Computer Graphics. Server device 114 (XR application server) compresses and encodes the rendered CG video using a codec and transmits the compressed and encoded data to UE111 according to RTP.

[0034] The XR application server accurately detects user input to the CG based on haptic information received from the UE111 (XR client), and can reproduce changes in the shape of CG objects and controls applied to the CG objects themselves under conditions close to reality. The XR application server can also transmit the sensation of touching the CG to the UE111 (XR client) for reproduction. The UE111 displays a composite image (hereinafter referred to as the XR image) on the HMD, which is a composite of the CG image received by the XR client and real-world footage captured in real time. Here, in order to composite the images, alpha information and other information associated with the CG image may be communicated in accordance with RTP in addition to the CG image. Since this technology is well known, its details are omitted.

[0035] Here, for example, regarding the application data transmitted by UE111, video, audio, and haptic information are in a multimodal relationship, and there are mutual delay requirements between these data (data types). Before the XR application starts generating XR video, UE111 establishes a PDU session with CN120 that satisfies the QoS requirements for each application data. UE111 requests AMF122 to establish the PDU session, including the QoS requirements for each application data. Then, the PDU session is established by SMF123 via AMF122. When establishing the PDU session, SMF123 defines a QoS flow for each application data according to QoS parameters such as resource type, priority, throughput, delay, and packet loss rate as defined by 5QI. 5QI is an abbreviation for 5G QoS Identifier. SMF123 also assigns a QFI (QoS Flow Identifier) ​​to each QoS flow and manages the QFI (QoS flow) together with the PDU session. Here, for example, "67," "65," and "69" are assigned as QFI or 5QI IDs to video, audio, and haptic information, respectively. The mapping information between application data and QFI or 5QI (hereinafter referred to as QoS flow configuration information) is notified to the gNB110 via the AMF122 by the SMF123. The QoS flow configuration information is also notified from the gNB110 to the UE111 using the SDAP-Config information of the RRC Reconfiguration message. SDAP is an abbreviation for Service Data Adaptation Protocol, and Config is an abbreviation for Configuration. Here, the QoS flow configuration information may also be notified from the gNB110 to the UE111 via the AMF122.

[0036] Furthermore, SMF123 configures a tunnel to transmit QoS flows based on PDU sessions to UPF121. UE111 then uses this tunnel configured in UPF121 to send application data to CN120 via gNB110.

[0037] On the other hand, in RAN130, gNB110 assigns LCHs to each type of application data according to the requirements of the QoS flow. Furthermore, gNB110 maps LCHs with equivalent QoS requirements to the same LCG.

[0038] For example, as a QoS requirement, video and audio resources are of the GBR (Guaranteed Bit Rate) type, while haptic information resources are of the Non-GBR type. Because these resource types are different, video and audio and haptic information are assigned to separate LCGs. However, since video and audio have equivalent resource types, priorities, latency, and packet loss rates, they are assigned to the same LCG. Specifically, QFI "67" is associated with LCH0, QFI "65" is associated with LCH1, and LCH0 and LCH1 are assigned to LCG0. Also, QFI "69" is associated with LCH2, and LCH2 is assigned to LCG1. In this way, LCHs (QFIs) are managed using different LCGs depending on the QoS requirements.

[0039] The gNB110 includes the assignment of LCHs in each LCG, and the relationship between LCHs and QFIs, as logical channel configuration information in an RRC message and sends it to the UE111. The UE111 can recognize the correspondence between application data and LCHs and LCGs from the received logical channel configuration information and the QoS flow configuration information received from the AMF122 when the PDU session is established. From these correspondences, the UE111 determines whether the LCHs corresponding to application data in a multimodal relationship are assigned to the same LCG. If these LCHs are assigned to different LCGs, the UE111 includes information indicating the combination of LCHs and LCGs that satisfy the multimodal relationship (hereinafter referred to as multimodal LCG information or multimodal information) in an RRC message (including UAI) and sends it to the gNB110. gNB110 receives multimodal LCG information from UE111 and reassigns LCGs based on the received multimodal LCG information. Here, the multimodal LCG information may include information indicating the relationship between LCHs and MMSIDs instead of information indicating the combination of LCHs and LCGs, or it may include both. Multimodal LCG information is an example of information that (explicitly or implicitly) notifies that two or more LCHs, each containing two or more types of data in a multimodal relationship (such as video, audio, and haptic information), are not assigned to the same LCG. Multimodal LCG information may also be called information that (explicitly or implicitly) notifies that two or more types of data in a multimodal relationship are not properly assigned to an LCG. Note that LCHs satisfying a multimodal relationship being assigned to the same LCG is one of the multimodal requirements.

[0040] In this way, the gNB110 can manage application data with multimodal relationships required by the XR application executed by the UE111 using the same LCG. This allows for the construction of an RRC link that is suitable for meeting multimodal requirements. In other words, by managing application data with multimodal relationships using the same LCG, the LCP-based priority control and DSR-based delay guarantee in the UE111 become effective in meeting multimodal requirements. LCP stands for Logical Channel Prioritization.

[0041] Here, the XR server (server device 114) to which UE111 is connected is assumed to be a cloud server, but it may also be a MEC (Multi-access Edge Computing) server operating on the wireless communication network 100. Alternatively, the XR server (server device 114) may be a server operating in an on-premises environment, in which case a local communication network may be used instead of the wireless communication network 100.

[0042] In addition to RTP, other video transmission protocols such as SRT, RTMP, HLS, and MPEG-DASH may be used between UE111 and server device 114. SRT is an abbreviation for Secure Reliable Transport, RTMP is an abbreviation for Real-Time Messaging Protocol, and HLS is an abbreviation for HTTP Live Streaming. MPEG-DASH is an abbreviation for MPEG Dynamic Adaptive Streaming over HTTP. HTTP is an abbreviation for Hyper Text Transfer Protocol, and MPEG is an abbreviation for Moving Picture Experts Group.

[0043] In this embodiment, UE111 is assumed to be an XR device, but it may also be other shooting devices such as video cameras or network cameras, or mobile terminals such as smartphones, tablets, or notebook PCs (Personal Computers).

[0044] <Device Configuration> Figure 2 is a block diagram showing an example of the hardware configuration of a terminal according to this embodiment. As an example of its hardware configuration, UE111 includes a control unit 201, a storage unit 202, a wireless communication unit 203, an antenna control unit 204, an antenna 205, a codec 206, and a camera imaging unit 207. UE111 also includes, as an example of its hardware configuration, an image synthesis unit 208, a panel display unit 209, an inertial measurement unit 210, a tactile measurement unit 211, an audio acquisition unit 212, an audio playback unit 213, and an operation information acquisition unit 214.

[0045] The control unit 201 includes one or more processors such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). The control unit 201 may also include an FPGA (Field Programmable Gate Array), a DSP (Digital Signal Processor), or an ASIC (Application-Specific Integrated Circuit). The control unit 201 controls the entire device. The control unit 201 controls the entire device, for example, by executing a control program stored in the storage unit 202.

[0046] The storage unit 202 includes one or more storage devices (memories), such as RAM (Random Access Memory), ROM (Read-Only Memory), HDD (Hard Disk Drive), and SSD (Solid State Drive). The storage unit 202 is configured to store various programs executed by the control unit 201 (e.g., control programs), various information used in processing by the control unit 201, and various application data. The various information includes, for example, logical channel configuration information, QoS flow setting information, and multimodal LCG information. The various application data includes 6DOF information, real-world images, CG images, XR images, audio, and haptic information. The storage unit 202 is also configured to function as a transmission and reception buffer for packets (data, information, etc.) transmitted and received by the wireless communication unit 203.

[0047] Multimodal LCG information may be transmitted to gNB110 by UE111 using RRC messages (including UAI), etc. Alternatively, multimodal LCG information may be transmitted to gNB110 by UE111 using a new MAC CE (Control Element).

[0048] Furthermore, UE111 may transmit multimodal LCG information by explicitly indicating its relationship with QoS flow and application data by including MMSID in the multimodal LCG information.

[0049] The wireless communication unit 203 performs processing related to wireless communication (cellular communication) compliant with 3GPP standards such as LTE and 5G. The wireless communication unit 203 includes communication processing circuits such as a baseband chip and an RF (radio frequency) chip. The wireless communication unit 203 also operates according to the wireless resource allocation scheme determined by the gNB110.

[0050] The antenna control unit 204 controls the antenna 205 used for wireless communication performed by the wireless communication unit 203 based on instruction signals from the control unit 201, etc. For example, the antenna control unit 204 controls the antenna 205 to switch its directional direction.

[0051] Antenna 205 consists of one or more antennas. When Antenna 205 consists of multiple antennas, it is configured to provide beamforming capability.

[0052] The codec 206 compresses and encodes the real-world video acquired (captured, imaged) by the camera imaging unit 207 to a size that can be transmitted to the server device 114, and stores the compressed real-world video (data) in the storage unit 202. The codec 206 also decompresses the compressed CG video received from the server device 114 and outputs the decompressed CG video (data) to the video synthesis unit 208.

[0053] The camera imaging unit 207 acquires real-world images by capturing and RAW processing them to be combined with CG images received from the server device 114 in order to generate XR images, and stores the processed (acquired) real-world images (data) in the storage unit 202. The acquired real-world images are then transmitted to the server device 114 according to the RTP in order for the XR application server running on the server device 114 to estimate the position and orientation of the UE 111. The camera imaging unit 207 is configured to acquire stereo images from multiple cameras, and multiple real-world images with different fields of view may be acquired depending on the application.

[0054] The video synthesis unit 208 combines the CG image input from the codec 206 with the real-world image acquired by the camera imaging unit 207 to generate stereo XR image (data). The video synthesis unit 208 outputs the generated XR image to the panel display unit 209.

[0055] The panel display unit 209 displays the XR image, which is a stereo image generated by the image synthesis unit 208, on multiple panels. The panels are composed of LCDs (Liquid Crystal Displays), micro-LEDs (Light Emitting Diodes), micro-OLEDs (Organic LEDs), etc.

[0056] The inertial measurement unit 210 acquires 6DOF information, which is the attitude information of the UE111, and stores the acquired 6DOF information in the storage unit 202. The 6DOF information acquired by the inertial measurement unit 210 is transmitted by the XR client to the server device 114, for example, via UDP, and is used to estimate the position and attitude of the UE111 in the XR application server.

[0057] The tactile measurement unit 211 acquires tactile information from the UE 111 and stores the acquired tactile information in the storage unit 202. The tactile information acquired by the tactile measurement unit 211 is transmitted by the XR client to the server device 114, for example via UDP, and is used by the XR application server to estimate the UE 111's interaction with the CG.

[0058] The audio acquisition unit 212 acquires sounds from the surrounding environment of the UE 111, user voices, etc., and stores the acquired audio in the storage unit 202. The audio acquired by the audio acquisition unit 212 is compressed and encoded by the codec 206 and transmitted by the XR client to the server device 114, for example, according to RTP. In the server device 114, the XR application server synthesizes the audio with sound effects, etc., in the XR application, and the synthesized audio is transmitted to the UE 111 and played back by the audio playback unit 213 via a speaker, etc. The synthesized audio may also be transmitted to other users (or their terminals) using the same application.

[0059] The audio playback unit 213 decodes and plays back sound effects from the XR application and the voices of other users using the application, which are transmitted to the UE 111 by the server device 114, using the codec 206.

[0060] The operation information acquisition unit 214 acquires operation information input from the UE111 controller and stores the acquired operation information in the storage unit 202. The acquired operation information is transmitted by the XR client to the server device 114, for example, via UDP, and is used by the XR application server for CG operation, XR application UI (User Interface) operation, etc.

[0061] Figure 3 is a block diagram showing an example of the functional configuration of a terminal according to this embodiment. As an example of its functional configuration, the UE111 includes a signal transmission unit 301, a signal reception unit 302, a data storage control unit 303, a connection control unit 304, an XR function control unit 305, a video transmission control unit 306, and a multimodal determination unit 307. The functions of each functional block shown in Figure 3 may be realized, for example, as software functions, by the control unit 201 executing a control program stored in the storage unit 202.

[0062] The signal transmitting unit 301 and the signal receiving unit 302 control the wireless communication unit 203 to transmit and receive wireless signals with the gNB110. The signal transmitting unit 301 and the signal receiving unit 302 transmit and receive wireless signals in accordance with 3GPP standards such as LTE and 5G standards. The signal transmitting unit 301 and / or the signal receiving unit 302 are examples of transmitting means or transmitting unit, receiving means or receiving unit, transmitting and receiving means or transmitting and receiving unit, communication means or communication unit, etc.

[0063] The data storage control unit 303 stores various programs and various data (various information) in the storage unit 202.

[0064] The connection control unit 304 performs processing related to connection control in the wireless communication network 100, such as sending and receiving RRC messages with the gNB 110 for wireless resource control. The connection control unit 304 further performs processing related to connection control with the CN 120, the internet line 113, and the server device 114.

[0065] Here, the signal transmission unit 301, the signal reception unit 302, and / or the connection control unit 304 perform data communication to satisfy QoS requirements using functions such as LCP, according to the QoS flow setting information notified from the AMF122 of the gNB110 and CN120. In addition, the signal transmission unit 301, the signal reception unit 302, and / or the connection control unit 304 transmit BSR and DSR to the gNB110 according to the logical channel configuration information, and perform data communication according to the bandwidth allocated by the gNB110.

[0066] The XR function control unit 305 controls the camera imaging unit 207, panel display unit 209, image synthesis unit 208, inertial measurement unit 210, tactile measurement unit 211, audio acquisition unit 212, audio playback unit 213, and operation information acquisition unit 214 via their respective drivers. This enables the XR function control unit 305 to generate XR images. The XR function control unit 305 also controls the exchange of real-world images, CG images, 6DOF information, tactile information, audio, operation information, etc., between the video transmission control unit 306 and the data storage control unit 303.

[0067] The video transmission control unit 306 generates wireless communication packets according to RTP from the real-world video compressed and encoded by the codec 206, and controls the signal transmission unit 301 to transmit the generated wireless communication packets. The video transmission control unit 306 also controls the signal reception unit 302 to output the CG video received from the server device 114 to the XR function control unit 305. This causes the XR function control unit 305 to decompress the CG video using the codec 206. The video transmission control unit 306 also transmits and receives audio according to RTP in a similar manner.

[0068] The multimodal determination unit 307 determines whether LCHs in a multimodal relationship are assigned to the same LCG. The multimodal determination unit 307 makes this determination based on logical channel configuration information, QoS flow setting information, etc., acquired by the signal receiving unit 302, connection control unit 304, etc. If the multimodal relationship is not met, the multimodal determination unit 307 controls the connection control unit 304 and the signal transmission unit 301 to transmit the multimodal LCG information in an RRC message (including UAI), etc. Note that in the above and below, "LCHs in a multimodal relationship," "application data in a multimodal relationship," and "data flow or QoS flow in a multimodal relationship" may be read interchangeably. The multimodal determination unit 307 is an example of a determination means or determination unit, etc.

[0069] Figure 4 is a block diagram showing an example of the hardware configuration of a base station according to this embodiment. The gNB110 includes, as an example of its hardware configuration, a control unit 401, a storage unit 402, a wireless communication unit 403, an antenna control unit 404, an antenna 405, and a wired communication unit 406.

[0070] The control unit 401 includes one or more processors such as a CPU or MPU. The control unit 401 may also include an FPGA, DSP, or ASIC. The control unit 401 controls the entire device. The control unit 401 controls the entire device, for example, by executing a control program stored in the memory unit 402. The control unit 401 generates (determines) logical channel configuration information based on QoS flow setting information from CN120. The control unit 401 also performs (determines) bandwidth allocation. The control unit 401 also performs (determines) LCG reassignment based on multimodal LCG information from UE111. The control unit 401 also determines bandwidth allocation to satisfy the multimodal requirements associated with MMSID.

[0071] The storage unit 402 includes one or more storage devices (memories), such as RAM, ROM, HDD, or SSD. The storage unit 402 is configured to store various programs executed by the control unit 401 (e.g., control programs), various information used in processing by the control unit 401, and various application data. The various information includes traffic control information from the UE 111 or server device 114, such as logical channel configuration information, QoS flow setting information, and multimodal LCG information. The various application data includes 6DOF information, real-world images, CG images, XR images, audio, and haptic information. The storage unit 202 is also configured to function as a transmission and reception buffer for packets (data, information, etc.) transmitted and received by the wireless communication unit 203 and / or the wired communication unit 406.

[0072] The wireless communication unit 403 performs processing related to wireless communication (cellular communication) compliant with 3GPP standards such as LTE and 5G standards. The wireless communication unit 403 includes communication processing circuits, such as a baseband chip and an RF chip. The wireless communication unit 403 receives QoS flow setting information from CN120 and transmits logical channel configuration information determined (generated) by the control unit 401 based on the QoS flow setting information to UE111. The wireless communication unit 403 also receives BSR and DSR based on the logical channel configuration information from UE111 and performs data communication according to the bandwidth allocation performed by the control unit 401. The wireless communication unit 403 also receives multimodal LCG information from UE111 and performs data communication according to the LCG reallocation performed by the control unit 401. The wireless communication unit 403 also performs data communication according to the bandwidth allocation determined by the control unit 401 to satisfy the multimodal requirements associated with MMSID.

[0073] The antenna control unit 404 controls the antenna 405 used for wireless communication performed by the wireless communication unit 403 based on instruction signals from the control unit 401, etc. For example, the antenna control unit 404 controls the antenna 405 to switch its directional direction.

[0074] Antenna 405 consists of one or more antennas. When Antenna 405 consists of multiple antennas, it is configured to provide beamforming capability.

[0075] The wired communication unit 406 is configured to perform data communication of various information from the UE 111 and server device 114, as well as connection settings for the wireless communication network 100 with the CN 120, via a wired backhaul line consisting of an optical fiber line or the like. The various information from the UE 111 and server device 114 includes, for example, real-world images, CG images, 6DOF information, haptic information, audio, operation information, etc. The wired communication unit 406 also receives QoS flow setting information from the SMF 123 in the CN 120 via the AMF 122. The wired communication unit 406 outputs the received QoS flow setting information to the control unit 401 in order to determine (generate) logical channel configuration information.

[0076] Figure 5 is a block diagram showing an example of the functional configuration of a base station according to this embodiment. As an example of its functional configuration, the gNB110 includes a signal transmission unit 501, a signal reception unit 502, a data storage control unit 503, a connection control unit 504, and a logical channel determination unit 505. The functions of each functional block shown in Figure 5 may be realized, for example, by the control unit 401 executing a control program stored in the storage unit 402 as a software function.

[0077] The signal transmitting unit 501 and the signal receiving unit 502 control the wireless communication unit 403 to transmit and receive wireless signals with the UE 111. The signal transmitting unit 501 and the signal receiving unit 502 transmit and receive wireless signals in accordance with 3GPP standards such as LTE and 5G standards. The signal transmitting unit 301 and / or the signal receiving unit 302 are examples of transmitting means or transmitting unit, receiving means or receiving unit, transmitting and receiving means or transmitting and receiving unit, communication means or communication unit, etc.

[0078] The data storage control unit 503 stores various programs and various data (logical channel configuration information, QoS flow setting information, multimodal LCG information, etc.) in the storage unit 402.

[0079] The connection control unit 504 performs processing related to connection control in the wireless communication network 100, such as sending and receiving RRC messages with the UE 111 for wireless resource control, by the wireless communication unit 403. The connection control unit 304 further performs processing related to connection control (e.g., configuration) of the wireless communication network 100 with the CN 120, by the wired communication unit 406. Based on logical channel information, the connection control unit 504 performs wireless bandwidth allocation according to the BSR and DSR received from the UE 111. The connection control unit 504 may also be called the bandwidth allocation determination unit.

[0080] The logical channel determination unit 505 determines the combination (association) of LCH and LCG in the logical channel configuration information based on the QoS flow setting information received from AMF122 in CN120 when a PDU session is established. The logical channel determination unit 505 assigns LCH to LCG so that the determined combination is achieved. The logical channel determination unit 505 also re-determines the combination of LCH and LCG according to the multimodal LCG information received from UE111. The logical channel determination unit 505 then re-assigns LCH to LCG so that the re-determined combination is achieved. Details of the LCG reassignment determination method will be described later. The logical channel determination unit 505 is an example of a determination means or determination unit, an assignment means or assignment unit, etc.

[0081] <Operation of the wireless communication system> Next, we will describe an example of how a wireless communication system works.

[0082] Figure 6 is a sequence diagram showing an example of operation of a wireless communication system (terminal, base station, and core network) according to this embodiment, and shows an example of LCG reassignment using UAI. Below, an example sequence for gNB110 to perform LCG assignment to satisfy the multimodal requirements of the application data transmitted by UE111 will be described.

[0083] An RRC link has already been established between UE111 and gNB110, and the XR application is being executed on UE111 and server device 114. UE111 is attempting to establish a PDU session to transmit application data to be sent to server device 114 when executing the XR application.

[0084] In S600, UE111 includes the application data type and corresponding QoS information in a PDU Session Establishment Request message and sends it to AMF122 via gNB110 and UPF121. AMF122 passes the received application data type and corresponding QoS information to SMF123, which then establishes the PDU session.

[0085] In S601, AMF122 includes the QoS flow configuration information determined by SMF123 in the PDU SESSION RESOURCE SETUP REQUEST message and sends it to gNB110. Based on the received QoS flow configuration information, gNB110 assigns each QoS flow to a DRB (Data Radio Bearer). gNB110 also assigns each DRB to an LCH and maps the LCH to an LCG based on the QoS requirements.

[0086] In S602, the gNB110 includes logical channel configuration information and QoS flow setting information in the RRC Reconfiguration message and sends it to the UE111.

[0087] In S603, UE111 determines, based on logical channel configuration information and QoS flow setting information, whether application data in a multimodal relationship is mapped to the same LCG. Details of this determination method will be described later.

[0088] If, as a result of the determination in S603, the LCG notified by gNB110 does not satisfy the multimodal relationship, then in S604, UE111 includes the multimodal LCG information in the UAI and sends it to gNB110.

[0089] In S605, gNB110 performs LCG reassignment based on the correspondence between LCH and LCG in the multimodal LCG information. Alternatively, gNB110 may perform LCG reassignment based on the relationship between LCH and MMSID in the multimodal LCG information.

[0090] In S606, gNB110 includes the logical channel configuration information after the reassignment in the RRC Reconfiguration message and sends it to UE111.

[0091] In S607, UE111 verifies the multimodal relationships in the logical channel configuration information after the reassignment and sends an RRC Reconfiguration Complete message to gNB110.

[0092] In S608, gNB110 sends a PDU SESSION RESOURCE SETUP RESPONSE message to AMF122 via UPF121 to notify that resource setup in the PDU session is complete.

[0093] Next, we will describe the UAI transmitted in S604 of Figure 6, as described above. Figure 7 shows an example of the UAI message format according to this embodiment.

[0094] UE111, in UAI700, includes multimodal LCG information in the RRC-MultiModal-UL-Info field 701 and transmits UAI700 to gNB110 (S604 in Figure 6). At this time, UE111 stores the LCH identification information in the "logicalChannelIdentity" field in Figure 7 and the LCG identification information in the "logicalChannelGroup" field in Figure 7. The RRC-MultiModal-UL-Info field 701 allows UE111 to explicitly notify gNB110 of the correspondence when assigning LCHs in a multimodal relationship to the same LCG. Here, MMSID ("mmsid" in Figure 7) for managing the multimodal relationship and each delay requirement between multimodalities (e.g., synchronization threshold, not shown) may be included in the RRC-MultiModal-UL-Info field 701.

[0095] Figure 8 is a flowchart showing an example of terminal operation according to this embodiment, illustrating the processing flow for determining LCG assignment in UE111. Below, the processing by which the multimodal determination unit 307 of UE111 determines LCG assignment based on multimodal relationships, which is executed in S603 of Figure 6 (and the processing in S604 of Figure 6), will be described.

[0096] In S800, UE111 receives an RRC Reconfiguration message from gNB110.

[0097] In S801-S804, UE111 repeatedly executes S802 and S803 for all MMSIDs. This loop may be executed in ascending order of MMSIDs, descending order of MMSIDs, or in any other order. At the beginning of this loop, UE111 sets the value of variable N to 0.

[0098] In S802, UE111 determines whether LCHs indicating a multimodal relationship are assigned to the same LCG in the logical channel configuration information included in the RRC Reconfiguration message. More specifically, UE111 determines whether LCHs associated with an MMSID indicating a multimodal relationship are assigned to the same LCG. LCHs associated with an MMSID indicating a multimodal relationship refer to LCHs with the same MMSID in the logical channel configuration information.

[0099] If the LCH associated with MMSID is not assigned to the same LCG (NO in S802), then in S803, UE111 increments the value of variable N by 1. In this case, after incrementing the value of variable N by 1, UE111 may exit the loop and proceed to S805.

[0100] On the other hand, if the LCH associated with MMSID is assigned to the same LCG (YES in S802), UE111 does not change the value of variable N.

[0101] When the loop processing is complete, in S805, UE111 determines whether the value of variable N is greater than 0.

[0102] If the value of variable N is greater than 0 (YES in S805), UE111 determines that the logical channel configuration information contains an LCG that does not satisfy the multimodal relationship and proceeds to S806. On the other hand, if the value of variable N is not greater than 0 (NO in S805), UE111 proceeds to S807. An LCG that does not satisfy the multimodal relationship refers to a different LCG to which an LCH that satisfies the multimodal relationship is assigned. Similarly, an LCG that does not satisfy the multimodal relationship means that an LCH that satisfies the multimodal relationship is assigned to a different LCG.

[0103] In S806 (corresponding to S604 in Figure 6), UE111 sends a UAI (e.g., UAI700) containing multimodal LCG information to gNB110. Then, UE111 terminates this process.

[0104] In S807, UE111 sends an RRC Reconfiguration Complete message to gNB110 to notify it that the RRC link reconfiguration is complete. Then, UE111 terminates the process.

[0105] Figure 9 is a flowchart showing an example of base station operation according to this embodiment, illustrating the processing flow for determining LCG reassignment in gNB110. Below, the processing for determining LCG reassignment (and the processing in S606 of Figure 6) performed by the logical channel determination unit 505 of UE111 will be described.

[0106] In S900, gNB110 receives UAI (e.g., UAI700) from UE111.

[0107] In S901, gNB110 determines whether the received UAI contains multimodal LCG information (e.g., multimodal LCG information 701).

[0108] If the UAI contains multimodal LCG information (YES in S901), gNB110 proceeds to S902. On the other hand, if the UAI does not contain multimodal LCG information (NO in S901), gNB110 proceeds to S903.

[0109] In S902, gNB110 performs LCG reassignment according to the correspondence between LCH and LCG in the multimodal LCG information. Then, gNB110 proceeds to S903.

[0110] In S903 (corresponding to S606 in Figure 6), gNB110 includes the logical channel configuration information in the RRC Reconfiguration message and sends it to UE111. When proceeding from S902 to S903, gNB110 includes the logical channel configuration information after the reassignment execution in the RRC Reconfiguration message. Then, gNB110 terminates this process.

[0111] According to Embodiment 1 described above, if the LCG does not satisfy the multimodal requirement in the logical channel configuration information notified by gNB110, UE111 can do the following: UE111 can explicitly request a change in LCG assignment by sending multimodal LCG information to gNB110. This makes it possible to appropriately change the mapping between LCH and LCG, and enables gNB110 to map LCHs belonging to the same multimodal service to the same LCG.

[0112] As a modification of Embodiment 1, the multimodal LCG information may be transmitted by UE111 in addition to another RRC message. Examples of such other RRC messages include an RRC Reestablishment Request message and an RRC Reconfiguration Complete message. This modification can also achieve the same effects as described above.

[0113] (Embodiment 2) In Embodiment 1, the UE111 transmits multimodal LCG information to the gNB110 and directly notifies it of the relationship between the LCH and LCG, thereby explicitly requesting the gNB110 to perform LCG reassignment based on the multimodal LCG information.

[0114] In contrast, in this embodiment, if the LCG does not meet the multimodal requirements in the logical channel configuration information transmitted by gNB110, UE111 notifies gNB110 of a failure or error due to multimodal factors. The method for prompting gNB110 to reassign the LCG based on this notification is described below.

[0115] In the following, we will omit descriptions of configurations and operations that are the same as or similar to those in Embodiment 1, and will focus on describing configurations and operations that differ from those in Embodiment 1.

[0116] Figure 10 is a sequence diagram showing an example of the operation of a wireless communication system (terminal, base station, and core network) according to this embodiment, and shows an example of LCG reassignment due to mmsFailure.

[0117] In this embodiment as well, an RRC link has already been established between UE111 and gNB110, and the XR application is executed in UE111 and server device 114. UE111 attempts to establish a PDU session for transmitting application data to be sent to server device 114 when executing the XR application.

[0118] In S1000, UE111 includes the application data type and corresponding QoS information in the PDU Session Establishment Request message and sends it to AMF122 via gNB110 and UPF121. Here, UE111 also includes the MMSID, which indicates the multimodal relationship of the application data, and the delay requirements between the multimodalities in the PDU Session Establishment Request message.

[0119] In S1001, AMF122 includes the QoS flow configuration information determined by SMF123 in a PDU SESSION RESOURCE SETUP REQUEST message and sends it to gNB110. Here, AMF122 also includes the mapping information between QoS flows and MMSIDs, as well as the delay requirements between each multimodality, in the PDU SESSION RESOURCE SETUP REQUEST message and sends it to gNB110. Based on the received QoS flow configuration information, gNB110 assigns each QoS flow to a DRB. Furthermore, gNB110 assigns each DRB to an LCH and maps the LCH to an LCG based on the QoS requirements.

[0120] In S1002, gNB110 includes logical channel configuration information and QoS flow setting information in the RRC Reconfiguration message and sends it to UE111.

[0121] In S1003, UE111 determines from the logical channel configuration information and QoS flow setting information whether application data in a multimodal relationship are mapped to the same LCG. More specifically, UE111 determines whether application data in a multimodal relationship are mapped to the same LCG using S800~S805 as explained with reference to Figure 8.

[0122] If, as a result of the determination in S1003, the LCG notified by gNB110 does not satisfy the multimodal relationship, then in S1004, UE111 will act as follows: UE111 will send an mmsFailure message to gNB110 in the RRC Reestablishment Request message, indicating a failure or error due to a multimodal factor, rather than a UAI. mmsFailure is an abbreviation for multi-modal service failure.

[0123] In S1005, the gNB110 detects a failure or error in LCG allocation from mmsFailure included in the RRC Reestablishment Request message and performs LCG reassignment based on MMSID. In other words, the gNB110 performs LCG reassignment based on MMSID depending on the cause of the failure.

[0124] In S1006, gNB110 sends an RRC Reestablishment message to UE111 to notify it of the success of RRC re-establishment.

[0125] In S1007, gNB110 includes the logical channel configuration information after the reassignment in the RRC Reconfiguration message and sends it to UE111.

[0126] In S1008, UE111 sends an RRC Reestablishment Complete message to gNB110 to notify it that the re-establishment of the RRC connection is complete.

[0127] In S1009, UE111 confirms that the LCG satisfies the multimodal relationship in the logical channel configuration information after the reassignment execution. Then, in the same S1009, UE111 sends an RRC Reconfiguration Complete message to gNB110.

[0128] Furthermore, if the message in S1007 can also serve as the notification of the successful re-establishment of the RRC in S1006, then S1006 may be omitted. Similarly, if the message in S1009 can also serve as the notification of the completion of the re-establishment of the RRC connection in S1008, then S1008 may be omitted.

[0129] In S1010, gNB110 sends a PDU SESSION RESOURCE SETUP RESPONSE message to AMF122 via UPF121 to notify that resource setup in the PDU session is complete.

[0130] Next, we will describe the RRC Reestablishment Request message sent in S1004 of Figure 10 as described above. Figure 11 shows an example of the RRC Reestablishment Request message format according to this embodiment.

[0131] In the RRC Reestablishment Request message 1100, UE111 notifies of LCG assignment failure or error via the ReestablishmentCause field 1101 (S1004 in Figure 10). For example, mmsFailure1102, which indicates LCG assignment failure or error based on multimodal relationships, may be added as a value (Fail reason) stored in the ReestablishmentCause field 1101. Then, UE111 can notify gNB110 of LCG assignment failure or error by specifying mmsFailure1102 in the ReestablishmentCause field 1101. mmsFailure1102 is an example of information that (explicitly or implicitly) notifies that two or more LCHs, each containing two or more types of data (video, audio, haptic information, etc.) in a multimodal relationship, have not been assigned to the same LCG. mmsFailure1102 may be called information that (explicitly or implicitly) indicates that two or more types of data in a multimodal relationship have not been properly assigned to the LCG.

[0132] According to Embodiment 2 described above, if the LCG does not meet the multimodal requirements in the logical channel configuration information notified from gNB110, UE111 can do the following: UE111 can prompt the reassignment of the LCG based on multimodal relationships by notifying gNB110 of the failure or error in LCG assignment. This makes it possible to appropriately change the mapping between LCH and LCG, and enables gNB110 to map LCHs belonging to the same multimodal service to the same LCG.

[0133] As a modification of Embodiment 2, information indicating a failure or error in LCG allocation based on multimodal relationships may be included in other RRC messages (including UAI) and transmitted by UE111. This modification can also achieve the same effects as described above.

[0134] (Other embodiments) Embodiments 1 and 2 describe a method for requesting the allocation of LCGs that satisfy multimodal relationships from UE111 to gNB110 during PDU session construction. However, the allocation of LCGs that satisfy multimodal relationships is not limited to the above timing, and may also be performed when application data is added or QoS settings are changed in UE111, along with updating the PDU session and RRC link. Furthermore, LCG allocation to satisfy multimodal relationships may also be performed similarly when UE111 is reconnected, when the RRC link is re-established, during handover, etc.

[0135] This disclosure can also be implemented by supplying a program that implements one or more of the functions of each of the embodiments described above to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. Furthermore, this disclosure can also be implemented by a circuit (e.g., an ASIC or FPGA) that implements one or more functions.

[0136] Any two or more of the components of UE111 and gNB110 described above may be integrated, or one component may be divided into two or more (sub)components.

[0137] The names of the functional units, messages, parameters, fields, etc., described in the embodiments described above may be changed to other names.

[0138] The order of the processing procedures, sequences, flowcharts, etc., in the embodiments described above may be rearranged as long as they do not contradict each other. For example, the methods described above present various step elements using an exemplary order and are not limited to the specific order presented.

[0139] Furthermore, the classification of items in the above description is not essential to this disclosure, and matters described in two or more items may be used in combination as necessary, and matters described in one item may apply to matters described in another item (as long as they do not contradict each other).

[0140] Furthermore, the following additional information is disclosed regarding the above embodiments.

[0141] [Note 1] A communication device that operates as a terminal, A communication device comprising a transmission means for transmitting information to a communication device operating as a base station, indicating that two or more types of data, each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

[0142] [Note 2] The communication device as described in Appendix 1, wherein the information is information indicating the correspondence between at least two logical channels (LCHs), each containing at least two types of data in a multimodal relationship, and multimodal service identification information or logical channel group (LCG).

[0143] [Note 3] The aforementioned information is information indicating a failure or error in LCG allocation based on multimodal relationships, as described in Appendix 1 of the communication device.

[0144] [Note 4] A receiving means for receiving logical channel configuration information from the base station that shows the correspondence between LCH and LCG, The logical channel configuration information includes a determination means for determining whether the two or more LCHs are assigned to the same LCG, Furthermore, If the two or more LCHs mentioned above are not assigned to the same LCG, the transmitting means transmits the information to the communication device operating as the base station, as described in any of Appendix 1 to 3.

[0145] [Note 5] The transmission means is a communication device as described in Appendix 2, which transmits an RRC (Radio Resource Control) message containing the information to a communication device operating as a base station.

[0146] [Note 6] The aforementioned RRC message is UAI (UE (User Equipment) Assistance Information), as described in Appendix 5 of the communication device.

[0147] [Note 7] The communication device described in Appendix 3, wherein the transmitting means transmits an RRC message containing the information to a communication device operating as a base station.

[0148] [Note 8] The RRC message is an RRC Reestablishment Request message, as described in Appendix 7 of the communication device.

[0149] [Note 9] The aforementioned information is included in the ReestablishmentCause field of the RRC Reestablishment Request message, and is related to the communication device described in Appendix 8.

[0150] [Note 10] A communication device that operates as a base station, A communication device equipped with a receiving means for receiving information from a communication device acting as a terminal that notifies that two or more types of data, each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

[0151] [Note 11] The communication device as described in Appendix 10, wherein the information is information indicating the correspondence between at least two logical channels (LCHs), each containing at least two types of data in a multimodal relationship, and multimodal service identification information or logical channel group (LCG).

[0152] [Note 12] The aforementioned information is information indicating a failure or error in LCG allocation based on multimodal relationships, as described in Appendix 10, for the communication device.

[0153] [Note 13] The communication device according to any one of appendices 10 to 12, further comprising an assignment means for assigning two or more types of LCH to the same LCG in response to the receiving means receiving the information.

[0154] [Note 14] The communication device according to Appendix 13, further comprising a transmission means for transmitting logical channel configuration information indicating the correspondence between LCH and LCG after allocation by the allocation means to a communication device operating as a terminal.

[0155] [Note 15] The receiving means is a communication device according to any one of appendices 10 to 14, which receives an RRC (Radio Resource Control) message containing the information from a communication device operating as the terminal.

[0156] [Note 16] A method for controlling a communication device that operates as a terminal, A control method including a transmission step of transmitting information to a communication device acting as a base station, which notifies that two or more types of data each containing two or more types of data in a multimodal relationship are not assigned to the same LCG (Logical Channel Group).

[0157] [Note 17] A method for controlling a communication device that operates as a base station, A control method that includes a receiving step of receiving information from a communication device acting as a terminal, which notifies that two or more types of data, each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

[0158] [Note 18] A program for causing a computer to perform the control methods described in Appendix 16 or 17. [Explanation of Symbols]

[0159] 100 Wireless Communication Systems 110 gNB 111 UE 114 Server Device 120 CN 121 UPF 122 AMF 123 SMF 301 Signal Transmitter 302 Signal receiving unit 304 Connection Control Unit 307 Multimodal determination unit 501 Signal Transmitter 502 Signal receiving unit 504 Connection Control Unit 505 Logical Channel Determination Unit

Claims

1. A communication device that operates as a terminal, A communication device comprising a transmission means for transmitting information to a communication device operating as a base station, notifying that two or more types of data, each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

2. The communication device according to claim 1, wherein the information is information indicating the correspondence between at least two logical channels (LCHs), each containing at least two types of data in a multimodal relationship, and multimodal service identification information or logical channel group (LCG).

3. The communication device according to claim 1, wherein the information is information indicating a failure or error in LCG assignment based on multimodal relationships.

4. A receiving means for receiving logical channel configuration information from the base station that shows the correspondence between LCH and LCG, The logical channel configuration information includes a determination means for determining whether the two or more LCHs are assigned to the same LCG, Furthermore, If the two or more LCHs mentioned above are not assigned to the same LCG, the transmitting means transmits the information to the communication device operating as the base station, according to claim 1.

5. The communication device according to claim 2, wherein the transmitting means transmits an RRC (Radio Resource Control) message containing the information to a communication device operating as a base station.

6. The communication device according to claim 5, wherein the RRC message is a UAI (UE (User Equipment) Assistance Information).

7. The communication device according to claim 3, wherein the transmitting means transmits an RRC message containing the information to a communication device operating as the base station.

8. The communication device according to claim 7, wherein the RRC message is an RRC Restabilization Request message.

9. The communication device according to claim 8, wherein the information is included in the RestabilitationCause field of the RRC Restabilitation Request message.

10. A communication device that operates as a base station, A communication device equipped with a receiving means for receiving information from a communication device acting as a terminal that notifies that two or more types of data, each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

11. The communication device according to claim 10, wherein the information is information indicating the correspondence between at least two logical channels (LCHs), each containing at least two types of data in a multimodal relationship, and multimodal service identification information or logical channel group (LCG).

12. The communication device according to claim 10, wherein the information is information indicating a failure or error in LCG assignment based on multimodal relationships.

13. The communication device according to claim 10, further comprising an assignment means that assigns the two or more LCHs to the same LCG in response to the receiving means receiving the information.

14. The communication device according to claim 13, further comprising a transmission means for transmitting logical channel configuration information indicating the correspondence between LCH and LCG after allocation by the allocation means to a communication device operating as a terminal.

15. The communication device according to claim 10, wherein the receiving means receives an RRC (Radio Resource Control) message containing the information from a communication device operating as the terminal.

16. A method for controlling a communication device that operates as a terminal, A control method comprising a transmission step of transmitting information to a communication device acting as a base station, indicating that two or more Logical Channels (LCHs), each containing two or more types of data in a multimodal relationship, are not assigned to the same Logical Channel Group (LCG).

17. A method for controlling a communication device that operates as a base station, A control method including a receiving step of receiving information from a communication device acting as a terminal that notifies that two or more types of LCHs (Logical Channels), each containing two or more types of data in a multimodal relationship, are not assigned to the same LCG (Logical Channel Group).

18. A program for causing a computer to execute the control method described in claim 16 or 17.

Images