Base station and communication method

By implementing a control unit in the base station to set MMSIDs for QoS flows, the challenge of managing multi-modal services in wireless communication systems is addressed, allowing for effective scheduling and delivery of interrelated data flows.

JP2025157158APending Publication Date: 2025-10-15NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025046082
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-03-19
Publication Date
2025-10-15

AI Technical Summary

Technical Problem

Existing wireless communication systems struggle to effectively manage and schedule multi-modal services, which consist of multiple interrelated data flows, due to the lack of a unified identification mechanism for data flows in the Radio Access Network (RAN) nodes.

Method used

A base station is equipped with a control unit that sets a Multi-modal Service ID (MMSID) for Quality of Service (QoS) flows, ensuring that RAN nodes, specifically the Central Unit (CU) and Distributed Unit (DU), recognize the relationship between data flows and schedule them accordingly.

Benefits of technology

This approach enables the recognition and scheduling of interrelated data flows within multi-modal services, enhancing the management and delivery of such services in wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025157158000001_ABST
    Figure 2025157158000001_ABST
Patent Text Reader

Abstract

To provide a multi-modal service in a wireless communication system.SOLUTION: A base station 10 includes a CU (Central Unit), a control unit 140 that sets multiple QoS (Quality of Service) flows between the CU and a DU (Distributed Unit), and a communication unit 110 that transmits a message to the DU, the message including an MMSID (Multi-modal service ID) that is set for each QoS flow, and the control unit 140 sets the same MMSID in the message for QoS flows associated with the same service.SELECTED DRAWING: Figure 14
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a base station and a communication method in a wireless communication system. [Background technology]

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, this wireless communication system will be referred to as "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less (for example, Non-Patent Document 1).

[0003] Additionally, 3GPP is considering supporting XR (Extended Reality) applications. XR involves data with a short tolerance for delay (hereinafter referred to as delay-critical data), and 3GPP is currently discussing the need to prioritize scheduling of delay-critical data (e.g., Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V18.4.0 (2024-12) [Non-patent document 2] "Report of 3GPP TSG RAN WG2 meeting #126", 3GPP TSG-RAN WG 2, 3GPP, May 2024 Summary of the Invention [Problem to be solved by the invention]

[0005] Strengthening of policies related to multi-modal services is being considered. A multi-modal service is a communication service consisting of multiple interrelated data flows, enabling application collaboration. 5G Core (5GC) must transmit a multi-modal service ID (MMSID) to the Radio Access Network (RAN) node to identify which service a data flow is associated with, and schedule multi-modal services in the radio access layer.

[0006] The present invention has been made in view of the above points, and has an object to provide a multi-modal service in a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technology, a base station is provided that includes a CU (Central Unit), a control unit that sets multiple QoS (Quality of Service) flows between the CU (Central Unit) and a DU (Distributed Unit), and a communication unit that transmits a message to the DU that includes an MMSID (Multi-modal service ID) that is set for each of the QoS flows, and the control unit sets the same MMSID for the QoS flows associated with the same service in the message. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to provide a multi-modal service in a wireless communication system. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a wireless communication system. [Figure 2] FIG. 1 is a diagram showing an example (1) of a service according to an embodiment of the present invention. [Figure 3] FIG. 10 is a diagram showing an example (2) of a service according to an embodiment of the present invention. [Figure 4] FIG. 10 is a diagram showing an example (3) of a service according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing an example (4) of a service according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example (5) of a service according to an embodiment of the present invention. [Figure 7] FIG. 10 is a diagram showing an example (6) of a service according to an embodiment of the present invention. [Figure 8] FIG. 10 is a sequence diagram showing an example (1) of an MMSID notification according to an embodiment of the present invention. [Figure 9] FIG. 10 is a sequence diagram showing an example (2) of an MMSID notification according to the embodiment of the present invention. [Figure 10] FIG. 10 is a sequence diagram showing an example (3) of an MMSID notification according to an embodiment of the present invention. [Figure 11] FIG. 10 is a sequence diagram showing an example (4) of an MMSID notification according to an embodiment of the present invention. [Figure 12] FIG. 10 is a sequence diagram showing an example (5) of an MMSID notification according to an embodiment of the present invention. [Figure 13] FIG. 10 is a sequence diagram showing an example (6) of an MMSID notification according to an embodiment of the present invention. [Figure 14] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 16] 1 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 17] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0015] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in the downlink (DL) and receives control signals or data from the terminal 20 in the uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0018] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0019] Strengthening of policies related to multi-modal services is being considered. A multi-modal service is a communication service consisting of multiple interrelated data flows, enabling application collaboration. 5G Core (5GC) must transmit a multi-modal service ID (MMSID) to the Radio Access Network (RAN) node to identify which service a data flow is associated with, and schedule multi-modal services in the radio access layer.

[0020] As mentioned above, 5GC is considering transmitting MMSID (Multi-modal service ID) to RAN nodes. When a RAN node is separated into a central unit (CU) and a distributed unit (DU), both the CU and the DU need to be aware of the MMSID. It is necessary to map the protocol data unit (PDU) session or quality of service (QoS) flow on the CU side to each data radio bearer (DRB) within the DU. Within the DU, different data flows, such as voice, video, location information, and haptic data, may be transmitted and received using different DRBs or multicast radio bearers (MRBs). By knowing the MMSID of the DRB or MRB, the DU can recognize the relationship between data flows between multiple DRBs or MRBs and enable scheduling that takes this relationship into account.

[0021] In a UE context setup request sent from a CU to a DU via an F1-AP, the MMSID may be added to the QoS information of each DRB in the DRB information in the DRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to DRB item.

[0022] In a UE context modification request sent from the CU to the DU via the F1-AP, the MMSID may be added to the QoS information of each DRB in the DRB information in the DRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to DRB item.

[0023] In a broadcast context setup request sent from a CU to a DU via an F1-AP, the MMSID may be added to the QoS information of each MRB in the MRB information in the broadcast MRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to MRB item.

[0024] In a broadcast context modification request sent from a CU to a DU via an F1-AP, the MMSID may be added to the QoS information of each MRB in the MRB information in the broadcast MRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to MRB item.

[0025] In a multicast context setup request sent from a CU to a DU via an F1-AP, the MMSID may be added to the QoS information of each MRB in the MRB information in the broadcast MRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to MRB item.

[0026] In a multicast context modification request sent from a CU to a DU via an F1-AP, an MMSID (multi-modal service ID) may be added to the QoS information of each MRB in the MRB information in the broadcast MRB to be setup list, or the MMSID may be added to the QoS Flow Level QoS Parameters in the flows mapped to MRB item.

[0027] Fig. 2 is a diagram showing an example (1) of a service according to an embodiment of the present invention. As shown in Fig. 2, when QoS flow #1 and QoS flow #2 use DRB=1 and QoS flow #3 and QoS flow #4 use DRB=2, by setting MMSID=1 to all QoS flows, the four QoS flows have the same MMSID, and the DU-side scheduler can recognize that the four QoS flows are closely related and belong to the same service.

[0028] Fig. 3 is a diagram showing an example (2) of a service according to an embodiment of the present invention. As shown in Fig. 3, when QoS flow #1, QoS flow #2, QoS flow #3, and QoS flow #4 use DRB=1, by setting MMSID=1 for all QoS flows, the four QoS flows have the same MMSID, and the DU-side scheduler can recognize that the four QoS flows are closely related and belong to the same service.

[0029] Fig. 4 is a diagram showing an example (3) of a service according to an embodiment of the present invention. As shown in Fig. 4, when QoS flow #1 and QoS flow #2 use MRB=1 and QoS flow #3 and QoS flow #4 use MRB=2, by setting MMSID=1 to all QoS flows, the four QoS flows have the same MMSID, and the DU-side scheduler can recognize that the four QoS flows are closely related and belong to the same service.

[0030] Fig. 5 is a diagram showing an example of a service (4) according to an embodiment of the present invention. As shown in Fig. 5, when QoS flow #1, QoS flow #2, QoS flow #3, and QoS flow #4 use MRB=1, by setting MMSID=1 for all QoS flows, the four QoS flows have the same MMSID, and the DU-side scheduler can recognize that the four QoS flows are closely related and belong to the same service.

[0031] For example, when sending MMSID from 5GC to a RAN node, there are two ways: sending it individually to each UE, or sending it in a broadcast manner to multiple UEs (broadcast or multicast services may support XR services).

[0032] The C-plane solution is explained below.

[0033] In an initial context setup request message sent from an AMF (Access and Mobility Management Function) to a RAN node, in a PDU session resource setup request transfer, in a QoS Flow Setup Request List, MMSID may be added to the QoS flow level QoS parameters of each QoS flow.

[0034] In a PDU session resource setup request message sent from the AMF to the RAN node, the MMSID may be added in the PDU Session Resource Setup Request List, in each PDU session resource setup request item, in the PDU session resource setup request transfer, and in the QoS flow level QoS parameters of each QoS flow in the QoS Flow Setup Request List.

[0035] In a PDU session resource modify message sent from the AMF to the RAN node, the MMSID may be added in the PDU Session Resource Modify Request List, in each PDU session resource modify request item, in the PDU session resource modify request transfer, in the QoS Flow Add or Modify Request List, and in the QoS flow level QoS parameters of each QoS flow.

[0036] The MMSID may be added to a broadcast session setup request (BROADCAST SESSION SETUP REQUEST) or a multicast session setup request (MULTICAST SESSION SETUP REQUEST) sent from the AMF to a RAN node, to an MBS Session Setup Request Transfer, to an MBS QoS Flows To Be Setup or Modified List, to an MBS Session Setup Request List, to each MBS QoS flow, and to MBS QoS Flow Level QoS Parameters.

[0037] In a broadcast session modification request (BROADCAST SESSION MODIFICATION REQUEST) or multicast session modification request (MULTICAST SESSION SETUP REQUEST) sent from the AMF to a RAN node, the MMSID may be added in the MBS Session modification Request Transfer, the MBS QoS Flows To Be Setup or Modified List, the MBS Session Setup Request List, each MBS QoS flow, and the MBS QoS Flow Level QoS Parameters.

[0038] The U-plane solution is explained below.

[0039] The MMSID may be added in the DL PDU SET INFORMATION (PDU Type 0).

[0040] Fig. 6 is a diagram showing a service example (5) according to an embodiment of the present invention. As shown in Fig. 6, when QoS flow #1 and QoS flow #2 use PDU session = 1 and QoS flow #3 and QoS flow #4 use PDU session = 2, by setting MMSID = 1 for QoS flow #1 and QoS flow #2, the two QoS flows have the same MMSID, and it is possible to recognize that the two QoS flows on the RAN node side are closely related and belong to the same service. Furthermore, by setting MMSID = 2 for QoS flow #3 and QoS flow #4, the two QoS flows have the same MMSID, and it is possible to recognize that the two QoS flows on the RAN node side are closely related and belong to the same service.

[0041] Fig. 7 is a diagram showing a service example (6) according to an embodiment of the present invention. As shown in Fig. 7, when QoS flow #1 and QoS flow #2 use DRB=1 and QoS flow #3 and QoS flow #4 use DRB=2, by setting MMSID=1 for QoS flow #1 and QoS flow #2, the two QoS flows have the same MMSID, and it is possible to recognize that the two QoS flows on the UE side are closely related and belong to the same service. Furthermore, by setting MMSID=2 for QoS flow #3 and QoS flow #4, the two QoS flows have the same MMSID, and it is possible to recognize that the two QoS flows on the UE side are closely related and belong to the same service.

[0042] 8 is a sequence diagram showing an example (1) of MMSID notification according to an embodiment of the present invention. In step S101, a UPF (User Plane Function) or an NG-RAN node transmits DL PDU set information to an NG-RAN node. Table 1 shows an example of DL PDU set information.

[0043] [Table 1]

[0044] As shown in Table 1, the DL PDU set information may include the MMSID.

[0045] 9 is a sequence diagram showing an example (2) of MMSID notification according to an embodiment of the present invention. In step S201, the UPF or NG-RAN node transmits DL PDU session information to the NG-RAN node. Table 2 shows an example of DL PDU session information.

[0046] [Table 2]

[0047] As shown in Table 2, the DL PDU session information may include the MMSID.

[0048] 10 is a sequence diagram showing an example (3) of MMSID notification according to an embodiment of the present invention. In step S301, the NG-RAN node transmits UL-PDU session information to the UPF. Table 3 shows an example of the UL PDU session information.

[0049] [Table 3]

[0050] As shown in Table 3, the UL PDU session information may include the MMSID.

[0051] 11 is a sequence diagram showing an example (4) of MMSID notification according to an embodiment of the present invention. In step S401, the gNB-CU transmits DL-PDU set information to the gNB-DU. The DL PDU set information may be as shown in Table 1 and may include the MMSID.

[0052] For example, during NG handover, the MMSID information of each PDU session between the source gNB and the core network may be handed over to the target gNB.

[0053] In the handover request message sent from the AMF to the target gNB, in the PDU Session Resource Setup Request, in the TransferQoS Flow Setup Request List, the MMSID may be added to the QoS flow level QoS parameters of each QoS flow.

[0054] In addition, in a handover required message sent from the source gNB to the AMF, the MMSID may be added to each QoS flow info in the PDU Session Resource Information List in the Source to Target Transparent Container.In a handover request message sent from the AMF to the target gNB, the MMSID may be added to each QoS flow info in the PDU Session Resource Information List in the Source to Target Transparent Container.

[0055] FIG. 12 is a sequence diagram showing an example (5) of MMSID notification according to an embodiment of the present invention. In step S501, the UE transmits a measurement result (Measurement Report) to the source gNB. In step S502, the source gNB transmits a handover request message (Handover required) to the AMF. In step S503, the AMF transmits a handover request (PDU Session Resource Setup Request Transfer (MMSID (multi-modal service ID) is added to the QoS flow level QoS parameters of each QoS flow in the QoS Flow Setup Request List)) to the target gNB. In step S503, the target gNB is notified of the MMSID to be set for each QoS flow.

[0056] In step S504, the target gNB sends a handover request ACK to the AMF. In step S505, the AMF sends a handover command to the source gNB. In step S506, the source gNB sends a handover command (RRCReconfiguration) to the UE.

[0057] 13 is a sequence diagram showing an example (6) of MMSID notification according to an embodiment of the present invention. In step S601, the UE transmits a measurement result (Measurement Report) to the source gNB. In step S602, the source gNB transmits a handover request message (Handover required (Source to Target Transparent Container (MMSID added to each QoS flow info in the PDU Session Resource Information List))) to the AMF. In step S602, the MMSID set for each QoS flow is notified to the AMF.

[0058] In step S603, the AMF sends a handover request (Source to Target Transparent Container (MMSID added to each QoS flow info in the PDU Session Resource Information List)) to the target gNB. Step S603 notifies the target gNB of the MMSID set for each QoS flow.

[0059] In step S6504, the target gNB sends a handover request ACK to the AMF. In step S605, the AMF sends a handover command to the source gNB. In step S606, the source gNB sends a handover command (RRCReconfiguration) to the UE.

[0060] As described above, when a RAN node is separated into a CU and a DU, the CU notifies the DU of the MMSID, and the DU knows the MMSID of the DRB or MRB, thereby recognizing the relationship between data flows between multiple DRBs or MRBs and enabling scheduling that takes that relationship into consideration. Furthermore, when sending the MMSID from 5GC to the RAN node, it is possible to select a transmission method for each UE and a transmission method for multiple UEs, and during NG handover, it is possible to transfer the MMSID information of each PDU session between the source gNB and the core network to the target gNB, thereby enabling, for example, XR to be realized favorably.

[0061] That is, a multi-modal service can be provided in a wireless communication system.

[0062] (Device configuration) Next, a description will be given of examples of functional configurations of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0063] <Base Station 10 and Network Node 30> FIG. 16 is a diagram showing an example of the functional configuration of the base station 10. As shown in FIG. 16, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in FIG. 16 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0064] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal.

[0065] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out from the storage device as needed. The contents of the setting information include, for example, settings related to the operations described in the embodiments.

[0066] As described in the embodiments, the control unit 140 performs processing related to the operations described in the embodiments. The control unit 140 also performs processing related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0067] <Terminal 20> Fig. 15 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 15, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 15 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0068] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0069] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to the operations described in the embodiments.

[0070] The control unit 240 performs control to realize the operations described in the embodiments. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0071] (Hardware configuration) The block diagrams (FIGS. 14 and 15) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0072] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0073] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 16 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0074] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0075] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0076] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0077] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 14 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 15 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0078] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0079] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0080] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0081] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0082] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0083] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic A-IoT device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0084] Fig. 17 shows an example configuration of a vehicle 2001. As shown in Fig. 17, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0085] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0086] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0087] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0088] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0089] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0090] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0091] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0092] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0093] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0094] (Summary of the embodiment) The terminal or base station of this embodiment may be configured as a communication device, terminal, or base station shown in the following items. Also, the following communication method may be implemented.

[0095] (Section 1) A base station including a CU (Central Unit), a control unit that sets multiple QoS (Quality of Service) flows between the control unit and a DU (Distributed Unit); a communication unit that transmits a message including an MMSID (Multi-modal service ID) set for each of the QoS flows to the DU; The control unit is a base station that sets the same MMSID to the QoS flows associated with the same service in the message. (Section 2) The base station according to claim 1, wherein the control unit processes the message as a UE context setup request or a UE context modification request. (Section 3) 2. The base station according to claim 1, wherein the control unit processes the message as a multicast context setup request or a broadcast context setup request. (Section 4) 2. The base station according to claim 1, wherein the communication unit receives a message including the MMSID from an Access and Mobility Management Function (AMF). (Section 5) The base station according to claim 1, wherein the communication unit, when being a source base station during handover, transmits a handover request message including an MMSID set for each of the QoS flows to an AMF (Access and Mobility Management Function). (Section 6) A communication method executed by a base station including a CU (Central Unit), A procedure for setting up multiple QoS (Quality of Service) flows between DUs (Distributed Units), a step of transmitting a message including an MMSID (Multi-modal service ID) set for each of the QoS flows to the DU; and a procedure of setting the same MMSID to the QoS flows associated with the same service in the message.

[0096] Any of the above configurations can provide multi-modal services in a wireless communication system. According to paragraphs 2 to 5, when a RAN node is separated into a CU and DU, the CU notifies the DU of the MMSID, and the DU learns the MMSID of the DRB or MRB. This allows the DU to recognize the relationship between data flows between multiple DRBs or MRBs and perform scheduling that takes this relationship into consideration. Furthermore, when sending the MMSID from 5GC to the RAN node, a transmission method for each UE and a transmission method for multiple UEs are available. During NG handover, the MMSID information of each PDU session between the source gNB and the core network can be handed over to the target gNB, making it possible to realize, for example, XR.

[0097] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0098] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0099] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0100] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0101] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0102] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0103] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0104] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0105] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0106] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0107] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0108] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0109] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0110] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0111] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0112] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0113] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0114] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0115] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0116] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0117] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0118] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (A-IoT Device-to-A-IoT Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0119] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0120] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0121] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0122] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0123] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0124] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0125] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0126] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0127] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0128] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0129] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0130] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0131] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0132] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0133] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0134] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0135] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0136] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0137] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0138] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0139] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0140] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0141] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0142] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0143] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0144] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0145] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0146] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0147] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0148] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0149] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0150] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 30 network nodes 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A base station including a CU (Central Unit), a control unit that sets up multiple QoS (Quality of Service) flows between the control unit and a DU (Distributed Unit); a communication unit that transmits a message including a multi-modal service ID (MMSID) set for each of the QoS flows to the DU; The base station, wherein the control unit sets the same MMSID to the QoS flows associated with the same service in the message.

2. The base station according to claim 1 , wherein the control unit processes the message as a UE context setup request or a UE context modification request.

3. The base station according to claim 1 , wherein the control unit processes the message as a multicast context setup request or a broadcast context setup request.

4. The base station according to claim 1 , wherein the communication unit receives a message including the MMSID from an Access and Mobility Management Function (AMF).

5. The base station according to claim 1, wherein, when the communication unit is a source base station during handover, the communication unit transmits a handover request message including an MMSID set for each of the QoS flows to an AMF (Access and Mobility Management Function).

6. A communication method executed by a base station including a CU (Central Unit), A procedure for setting up multiple QoS (Quality of Service) flows between a DU (Distributed Unit); a step of transmitting a message including a multi-modal service ID (MMSID) set for each of the QoS flows to the DU; and setting the same MMSID in the message to the QoS flows associated with the same service.