Terminal device, method, and integrated circuit

Abstract

A terminal device includes a reception unit that receives an RRC message including MBS configuration information from a base station device, and a processing unit that establishes an MBS radio bearer based on the terminal device starting reception of an MBS session, and notifies a part or all of the MBS session information to an upper layer.

Description

TECHNICAL FIELD

[0001] The present application relates to a terminal device, a method, and an integrated circuit.

[0002] This application claims priority to Japanese Patent Application No. 2020-79034 filed on April 28, 2020 in Japan, the content of which is incorporated herein by reference. BACKGROUND

[0003] In the 3rd Generation Partnership Project (3GPP) which is a standardization project of cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems including radio access, core network, service, and the like are conducted.

[0004] For example, in the 3GPP, technical studies and standardization of E-UTRA (Evolved Universal Terrestrial Radio Access) as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th and 4th generations are started. Technical studies and standardization of an extension technology of E-UTRA are also currently conducted in the 3GPP. Note that E-UTRA is also referred to as Long Term Evolution (LTE: a registered trademark), and the extension technology is also referred to as LTE-Advanced (LTE-A), LTE-Advanced Pro (LTE-A Pro).

[0005] Further, in the 3GPP, technical studies and standardization of NR (New Radio or NR Radio access) as a radio access technology (RAT) for cellular mobile communication systems for the 5th generation (5G) are started. Technical studies and standardization of an extension technology of NR are also currently conducted in the 3GPP.

[0006] Prior Art Documents

[0007] Non-Patent Literature

[0008] Non-Patent Literature 1: 3GPP RP-193248, “New Work Item on NR Multicast and Broadcast Services”

[0009] Non-Patent Literature 2: 3GPP TS 23.501 v15.3.0, "System Architecture for the 5G System; Stage 2"

[0010] Non-Patent Literature 3: 3GPP TS 36.300 v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA) and Evolved Universal Terestrial Radio Access Network (E-UTRAN); Overall description; Stage 2"

[0011] Non-Patent Literature 4: 3GPP TS 36.331 v15.4.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications"

[0012] Non-Patent Literature 5: 3GPP TS 36.323 v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification"

[0013] Non-Patent Literature 6: 3GPP TS 36.322 v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification"

[0014] Non-Patent Literature 7: 3GPP TS 36.321 v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification"

[0015] Non-Patent Literature 8: 3GPP TS 37.340 v 15.8.0, "Evolved Universal Terestrial Radio Access (E-UTRA) and NR; Multi-Connectivity; Stage 2"

[0016] Non-Patent Literature 9: 3GPP TS 38.300 v 15.3.0, "NR; NR and NG-RAN Overall description; Stage 2"

[0017] Non-Patent Literature 10: 3GPP TS 38.331 v15.4.0, "NR; Radio Resource Control (RRC); Protocol specifications"

[0018] Non-Patent Literature 11: 3GPP TS 38.323 v15.3.0, "NR; Packet Data Convergence Protocol (PDCP) specification"

[0019] Non-Patent Literature 12: 3GPP TS 38.322 v15.3.0, "NR; Radio Link Control (RLC) protocol specification"

[0020] Non-Patent Literature 13: 3GPP TS 38.321 v15.3.0, "NR; Medium Access Control (MAC) protocol specification"

[0021] Non-Patent Literature 14: 3GPP TS 23.401 v15.0.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terestrial Radio Access Network (E-UTRAN) access"

[0022] Non-Patent Literature 15: 3GPP TS 26.346 v16.3.0, "Multimedia Broadcast / Multicast Service (MBMS); Protocols and codecs"

[0023] Non-Patent Literature 16: 3GPP TS 37.324 v15.1.0, "NR; Service Data Adaptation Protocol (SDAP) specification" SUMMARY

[0024] PROBLEMS TO BE SOLVED BY THE INVENTION

[0025] As one of the extension technologies of E-UTRA, the MBMS (Multimedia Broadcast Multicast Service) transmission technology was standardized in order to provide a multicast / broadcast service. In the MBMS transmission, transmission using MBSFN (Multicast Broadcast Single Frequency Network) or SC-PTM (Single Cell Point-To-Multipoint) is used.

[0026] In the transmission using MBSFN, in units of an MBSFN (Multicast-Broadcast Single-Frequency Network) area constituted by a plurality of cells, PMCH (Physical Multicast Channel) is used to perform transmission of multicast / broadcast data. In contrast, in the transmission using SC-PTM, in units of a cell, PDSCH (Physical Downlink Shared Channel) is used to perform transmission of multicast data.

[0027] On the other hand, the multicast / broadcast service (MBS) as an extension technology of NR is under study. (Non-Patent Literature 1) In the case of MBS via NR, it is necessary to consider NR-specific technologies different from E-UTRA, a core network standardized for 5G, and the like. However, detailed operations for efficiently receiving MBS using NR have not been studied.

[0028] One aspect of the present application is achieved in view of the above problems, and an object thereof is to provide a terminal device, a method, and an integrated circuit that can efficiently receive MBS using NR.

[0029] TECHNICAL SOLUTION

[0030] To achieve the above objectives, one aspect of the present invention adopts the following approach. Specifically, one aspect of the present invention is a terminal device that communicates with a base station device. This terminal device includes: a receiving unit that receives an RRC message from the base station device, including multicast / broadcast service (MBS) configuration information; and a processing unit, wherein the MBS configuration information includes MBS session information, the MBS session information includes PDU session information, and the processing unit performs the following processing: based on the terminal device initiating the reception of the MBS session, establishing an MBS radio bearer, and notifying an upper layer of part or all of the MBS session information.

[0031] Furthermore, one aspect of the present invention is a method for a terminal device to communicate with a base station device, wherein the terminal device receives an RRC message including multicast / broadcast service (MBS) configuration information from the base station device, the MBS configuration information including MBS session information, the MBS session information including PDU session information, the terminal device initiates reception of the MBS session, establishes an MBS wireless bearer, and notifies an upper layer of some or all of the MBS session information.

[0032] It should be noted that these specific solutions can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0033] Beneficial effects

[0034] According to one aspect of the present invention, the terminal device can efficiently receive MBS using NR. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of the communication system according to various embodiments of the present invention.

[0036] Figure 2 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the E-UTRA of various embodiments of the present invention.

[0037] Figure 3 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR of various embodiments of the present invention.

[0038] Figure 4 This is a diagram illustrating an example of the flow of various settings in RRC208 and / or RRC308 according to various embodiments of the present invention.

[0039] Figure 5 This is a block diagram illustrating the configuration of the terminal device according to various embodiments of the present invention.

[0040] Figure 6 is a block diagram showing the configuration of a base station device of each embodiment of the present application.

[0041] Figure 7 is one example of an ASN.1 description included in a message related to reestablishment of an RRC connection in NR of an embodiment of the present application.

[0042] Figure 8 is one example of an ASN.1 description included in a message related to reestablishment of an RRC connection in E-UTRA of an embodiment of the present application.

[0043] Figure 9 is a diagram showing a flow of a procedure for setting of MBMS reception using SC-PTM.

[0044] Figure 10 is a diagram showing one example of an ASN.1 description representing a field and / or information element included in SIB20 (System Information Block Type 20).

[0045] Figure 11 is a diagram showing one example of an ASN.1 description representing a field and / or information element included in an SC-PTM setting message (SCPTM Configuration).

[0046] Figure 12 is a diagram showing one example of the configuration of an SDAP sublayer of an embodiment of the present application.

[0047] Figure 13 is a diagram showing one example of a flow of a procedure for setting of MBS reception in NR of an embodiment of the present application. DETAILED DESCRIPTION

[0048] Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0049] LTE (and LTE-A, LTE-A Pro) and NR can be defined as different radio access technologies (RATs). Further, NR can be defined as a technology included in LTE. LTE can be defined as a technology included in NR. Further, LTE that can be connected to NR through multi radio dual connectivity can be distinguished from the existing LTE. Further, LTE of which core network is 5GC can be distinguished from the existing LTE of which core network is EPC. The present embodiment can be applied to NR, LTE, and other RATs. In the following description, explanation is made using terms associated with LTE and NR, but the present embodiment can also be applied to other technologies using other terms. Further, in the present embodiment, the term called E-UTRA can be replaced with the term called LTE, and the term called LTE can be replaced with the term called E-UTRA.

[0050] Figure 1 is a schematic diagram of a communication system of each embodiment of the present application.

[0051] E-UTRA 100 is a radio access technology described in Non-Patent Literature 3 and the like, and includes a cell group (CG) configured of one or a plurality of frequency bands. An eNB (E-UTRAN Node B) 102 is a base station device of the E-UTRA 100. An EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Literature 14 and the like, and is designed as a core network for the E-UTRA 100. An interface 112 is an interface between the eNB 102 and the EPC 104, and there are a control plane (CP) through which control signals pass and a user plane (UP) through which user data passes.

[0052] NR 106 is a radio access technology described in Non-Patent Literature 9 and the like, and includes a cell group (CG) configured of one or a plurality of frequency bands. A gNB (g Node B) 108 is a base station device of the NR 106. A 5GC 110 is a core network described in Non-Patent Literature 2 and the like, and is designed as a core network for the NR 106, but can also be used as a core network for the E-UTRA 100 having a function of connecting to the 5GC 110. Hereinafter, the E-UTRA 100 can include the E-UTRA 100 having a function of connecting to the 5GC 110.

[0053] The interface 114 is an interface between the eNB 102 and the 5GC 110, the interface 116 is an interface between the gNB 108 and the 5GC 110, the interface 118 is an interface between the gNB 108 and the EPC 104, the interface 120 is an interface between the eNB 102 and the gNB 108, and the interface 124 is an interface between the EPC 104 and the 5GC 110. The interfaces 114, 116, 118, 120, and 124 can be interfaces through only the CP or only the UP, or through both the CP and the UP. Further, the interfaces 114, 116, 118, 120, and 124 can not exist depending on the communication system provided by the communication carrier.

[0054] The UE 122 is a terminal device corresponding to any one or both of the E-UTRA 100 and the NR 106. As described in any one or both of Non Patent Literature 3 and Non Patent Literature 9, when the UE 122 is connected with the core network via any one or both of the E-UTRA 100 and the NR 106, a logical path called a radio bearer (RB) is established between the UE 122 and any one or both of the E-UTRA 100 and the NR 106. A radio bearer for the CP is called a signaling radio bearer (SRB), and a radio bearer for the UP is called a data radio bearer (DRB). Each RB is identified as unique by being assigned an RB identifier (RB Identity or RB ID). An SRB is identified as unique by being assigned an SRB identifier (SRB Identity or SRB ID), and a DRB is identified as unique by being assigned a DRB identifier (DRB Identity or DRB ID).

[0055] As described in Non Patent Literature 3, in a case where the connection destination core network of the UE 122 is the EPC 104, each DRB established between the UE 122 and any one or both of the E-UTRA 100 and the NR 106 is further uniquely associated with each EPS (Evolved Packet System) bearer within the EPC 104. Each EPS bearer is identified as unique by being assigned an EPS bearer identifier (Identity or ID). Further, the same QoS is guaranteed for data passing through the same EPS bearer.

[0056] As described in Non-Patent Literature 9, in a case where the connection destination core network of the UE 122 is the 5GC 110, one or a plurality of DRBs that have been established between the UE 122 and either or both of the E-UTRA 100 and the NR 106 are further associated with one of PDU (Packet Data Unit) sessions to be established within the 5GC 110. There are one or a plurality of QoS (Quality of Service) flows in each PDU session. Each DRB can or can not be mapped to one or a plurality of QoS flows existing within the associated PDU session. Each PDU session is identified by a PDU session identifier (Identity or ID). Further, each QoS flow is identified by a QoS flow identifier. Further, the same QoS is guaranteed for data through the same QoS flow.

[0057] None of the PDU session and the QoS flow exists in the EPC 104, and none of the EPS bearer exists in the 5GC 110. At the time of connection of the UE 122 with the EPC 104, the UE 122 has information of the EPS bearer but does not have information of any one or all of the PDU session and the QoS flow. At the time of connection of the UE 122 with the 5GC 110, the UE 122 has information of any one or all of the PDU session and the QoS flow but does not have information of the EPS bearer.

[0058] Note that, in the following description, the eNB 102 and / or the gNB 108 will be simply referred to as a base station device, and the UE 122 will be simply referred to as a terminal device.

[0059] Figure 2 is a protocol stack diagram of the UP and the CP of the terminal device and the base station device of the E-UTRA Radio Access Layer of each embodiment of the present application.

[0060] Figure 2 (A) of is a protocol stack diagram of the UP used at the time of communication of the UE 122 with the eNB 102 in the E-UTRA 100.

[0061] The PHY (Physical layer) 200 is a radio physical layer that provides a transmission service to an upper layer using a physical channel. The PHY 200 is connected to a higher MAC (Medium Access Control layer) 202 described later through a transport channel. Data moves between the MAC 202 and the PHY 200 via the transport channel. Between the PHYs of the UE 122 and the eNB 102, data is transmitted and received via a radio physical channel. In the PHY 200, various control information is identified using an RNTI (Radio Network Temporary Identifire).

[0062] The MAC 202 is a medium access control layer that maps a plurality of logical channels to a plurality of transport channels. The MAC 202 is connected to a higher RLC (Radio Link Control layer) 204 described later through a logical channel. The logical channels are roughly classified into a control channel that transmits control information and a traffic channel that transmits user information according to the kind of information transmitted. The MAC 202 has a function of controlling the PHY 200 for performing DRX (Discontinuous Reception) and / or (and / or) DTX (Discontinuous Transmission), a function of performing a random access procedure, a function of notifying information of a transmission power, a function of performing HARQ control, and the like (Non-Patent Literature 7).

[0063] The uplink (UL) and / or downlink (DL) logical channels used in the E-UTRA are described.

[0064] The BCCH (Broadcast Control Channel) can be a downlink logical channel for broadcasting control information such as system information (SI).

[0065] The PCCH (Paging Control Channel) can be a downlink logical channel for carrying a paging message. Further, the PCCH can also be used for notifying a change in system information.

[0066] The CCCH (Common Control Channel) can be a logical channel for transmitting control information between the UE 122 and the eNB 102. The CCCH can also be used in a case where the UE 122 does not have an RRC (Radio Resource Control) connection described later. Further, the CCCH can also be used between a base station device and a plurality of terminal devices.

[0067] The DCCH (Dedicated Control Channel) can be a logical channel for bi-directionally transmitting dedicated control information between the UE 122 and the eNB 102 on a point-to-point basis. The dedicated control information can be control information dedicated to each terminal device. The DCCH can also be used in a case where the UE 122 has an RRC (Radio Resource Control) connection described later with the eNB 102.

[0068] The DTCH (Dedicated Traffic Channel) can be a logical channel for transmitting user data between the UE 122 and the eNB 102 on a point-to-point basis.

[0069] The MTCH (Multicast Traffic Channel) can be a point-to-multipoint downlink channel for transmitting data from the eNB 102 to the UE 122. The SC-MTCH can be used by the UE 122 only in a case where the UE 122 receives an MBMS.

[0070] The MCCH (Multicast Control Channel) can be a point-to-multipoint downlink channel for transmitting MBMS control information for one or a plurality of MTCHs from the eNB 102 to the UE 122. The MCCH can also be used by the UE 122 only in a case where the UE 122 receives an MBMS or the UE 122 is interested in receiving an MBMS.

[0071] SC-MTCH (Single Cell Multicast Traffic Channel) can be a point-to-multipoint downlink channel for transmitting data from the eNB 102 to the UE 122 using SC-PTM. The SC-MTCH can also be used by the UE 122 only if the UE 122 receives MBMS using SC-PTM.

[0072] SC-MCCH (Single Cell Multicast Control Channel) can be a point-to-multipoint downlink channel for transmitting MBMS control information for one or more SC-MTCHs from the eNB 102 to the UE 122. The SC-MCCH can also be used by the UE 122 only if the UE 122 receives MBMS using SC-PTM or the UE 122 has interest in receiving MBMS using SC-PTM.

[0073] Mapping of logical channels to transport channels for uplink in E-UTRA is described.

[0074] The CCCH can be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0075] The DCCH can also be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0076] The DTCH can also be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0077] Mapping of logical channels to transport channels for downlink in E-UTRA is described.

[0078] The BCCH can be mapped to the BCH (Broadcast Channel) and / or the DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0079] The PCCH can be mapped to the PCH (Paging Channel) as a downlink transport channel.

[0080] The CCCH can be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0081] The DCCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0082] The DTCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0083] The MTCH can be mapped to a MCH (Multicast Channel) as a downlink transport channel.

[0084] The MCCH can also be mapped to a MCH (Multicast Channel) as a downlink transport channel.

[0085] The SC-MTCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0086] The SC-MTCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0087] The RLC 204 segments data received from a higher layer PDCP (Packet Data Convergence Protocol layer) 206 described later, adjusts the data size so that the lower layer can appropriately perform data transmission. The RLC 204 has three modes of TM (Transparent Mode), UM (Unacknowledged Mode), and AM (Acknowledged Mode). In the TM, segmentation of data received from the upper layer is not performed, and addition of an RLC header is not performed. In the UM, segmentation of data received from the upper layer and addition of an RLC header are performed, but retransmission control of data is not performed. In the AM, segmentation of data received from the upper layer, addition of an RLC header, and retransmission control of data are performed. The retransmission control function can be a function for guaranteeing QoS (Quality of Service) requested for each data. In the retransmission control of data, information of undelivered data transmitted from the reception side of the RLC to the transmission side is called a status report. Further, an instruction for urging a status report transmitted from the transmission side of the RLC to the reception side is called a poll. Note that data transmitted to the lower layer in the TM is sometimes called a TM D PDU, data transmitted to the lower layer in the UM is sometimes called a UM D PDU, and data transmitted to the lower layer in the AM is sometimes called an AM D PDU. (Non-Patent Literature 6)

[0088] The PDCP 206 is a packet data convergence protocol layer for efficiently transmitting user data such as IP packets over a wireless region. The PDCP 206 can have a header compression function of compressing unnecessary control information. Further, the PDCP 206 can have a data encryption function. Further, the PDCP 206 can have a re-ordering function (Non-Patent Literature 5).

[0089] Note that data processed in the MAC 202, RLC 204, PDCP 206 is referred to as a MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, respectively. Further, data transferred from an upper layer to the MAC 202, RLC 204, PDCP 206 or data transferred to an upper layer is referred to as a MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, respectively. Further, a segmented RLC SDU is referred to as an RLC SDU segment.

[0090] Further, in order to distinguish between data and control, the PDCP PDU can also be referred to as a PDCP DATA PDU, PDCP CONTROL PDU, respectively. Further, in order to distinguish between data and control, the RLC PDU can also be referred to as a RLC DATA PDU, RLC CONTROL PDU, respectively.

[0091] Figure 2 (B) is a protocol stack diagram of a CP used when the UE 122 communicates with the eNB 102 and an MME (Mobility Management Entity) that is a logical node that provides functions such as authentication, mobility management, and the like in the E-UTRA 100.

[0092] In the protocol stack of the CP, in addition to the PHY 200, the MAC 202, the RLC 204, and the PDCP 206, there are the RRC (Radio Resource Control layer) 208 and the NAS (non Access Strarum) 210. The RRC 208 is a radio link control layer that performs, in addition to processes such as establishment, re-establishment, suspension, and resumption of an RRC connection, reconfiguration of the RRC connection, such as establishment, change, and release of a radio bearer (RB) and a cell group, and setting of logical channels, transport channels, and physical channels, and setting of handover and measurement. The RB can be classified into a signaling radio bearer (SRB) and a data radio bearer (DRB), and the SRB can be used as a path for transmitting an RRC message that is control information. The DRB can be used as a path for transmitting user data. The setting of each RB can be performed between the RRC 208 of the eNB 102 and the UE 122. Furthermore, a part of the RB that is composed of the RLC 204 and a logical channel can be referred to as an RLC bearer (non-patent literature 4). Furthermore, the NAS layer that transports signals between the MME and the UE 122 can be an AS (Access Strarum) layer that is composed of a part or all of the layers of the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 that transport signals and data between the UE 122 and the eNB 102.

[0093] Furthermore, the SRB can be defined as SRB0 to SRB2, and SRBs other than these can be defined. The SRB0 can be an SRB for an RRC message of a CCCH (Common Control Channel) using a logical channel. The SRB1 can be an SRB for an RRC message (possibly including a piggybacked NAS message) and for a NAS message before establishment of the SRB2, and can use a DCCH (Dedicated Control CHannel) using a logical channel. The SRB2 can be an SRB for a NAS message, and can use a DCCH using a logical channel. Furthermore, the SRB2 can have a lower priority than the SRB1.

[0094] Further, the RRC message can be transmitted using the BCCH of the logical channel, can be transmitted using the PCCH of the logical channel, and can be transmitted using the MCCH of the logical channel. The RRC message transmitted using the BCCH can include, for example, a Master Information Block described in Non-Patent Literature 4, can include each type of System Information Block, and can include other RRC messages. The RRC message transmitted using the BCCH can include, for example, a paging message described in Non-Patent Literature 4, and can include other RRC messages. The RRC message transmitted using the MCCH can include, for example, an MBSFN (Multicast Broadcast Single Frequency Network) Area Configuration described in Non-Patent Literature 4, can include an MBMS Continuing Request, and can include other RRC messages.

[0095] The classification of the functions of the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 described above is an example, and a part or all of each function can not be implemented. Further, a part or all of the functions of each layer can be included in another layer.

[0096] Note that the IP layer and a TCP (Transmission Control Protocol) layer, a UDP (User Datagram Protocol) layer, an application layer, and the like that are layers above the IP layer are upper layers (not illustrated) of the PDCP layer. Further, an RRC layer and a NAS (non Access Strarum) layer are also upper layers (not illustrated) of the PDCP layer. In other words, the PDCP layer is a lower layer of the RRC layer, the NAS layer, the IP layer, and a TCP (Transmission Control Protocol) layer, a UDP (User Datagram Protocol) layer, an application layer that are layers above the IP layer.

[0097] Figure 3 is a protocol stack diagram of the UP and the CP of the terminal device and the base station device in the NR radio access layer of each embodiment of the present application.

[0098] Figure 3 (A) of is a protocol stack diagram of the UP used when the UE 122 communicates with the gNB 108 in the NR 106.

[0099] The PHY (Physical layer) 300 is a Radio Physical layer of NR, and can provide a transmission service to an upper layer using a physical channel. The PHY 300 can be connected with the MAC (Medium Access Control layer) 302 described later, which is an upper layer, through a transport channel. Data can move between the MAC 302 and the PHY 300 via the transport channel. Transmission and reception of data can be performed between the PHYs of the UE 122 and the gNB 108 via a radio physical channel. An RNTI (Radio Network Temporary Identifire) can be used in the PHY 200 to identify various control information.

[0100] Here, a physical channel is described.

[0101] The following physical channels can be used in wireless communication between the terminal device and the base station device.

[0102] PBCH (Physical Broadcast CHannel)

[0103] PDCCH (Physical Downlink Control CHannel)

[0104] PDSCH (Physical Downlink Shared CHannel)

[0105] PUCCH (Physical Uplink Control CHannel)

[0106] PUSCH (Physical Uplink Shared CHannel)

[0107] PRACH (Physical Random Access CHannel)

[0108] The PBCH is used to broadcast system information required by the terminal device.

[0109] Further, in NR, the PBCH can be used to broadcast a time index (SSB-Index) within a period of a block of synchronization signals (also referred to as an SS / PBCH block).

[0110] The PDCCH is used to transmit (or carry) downlink control information (DCI) in wireless communication of the downlink (wireless communication from the base station device 3 to the terminal device). Here, the transmission of the downlink control information defines one or plural DCIs (may also be referred to as DCI formats). That is, fields for the downlink control information are defined as the DCI and mapped to information bits. The PDCCH is transmitted in a PDCCH candidate. The terminal device monitors a set of PDCCH candidates in a serving cell. The monitoring is to mean that the decoding of the PDCCH is attempted according to a certain DCI format. The certain DCI format can be used for scheduling of the PUSCH in the serving cell. The PUSCH can be used for transmission of user data, transmission of an RRC message, and the like.

[0111] The PUCCH can be used to transmit uplink control information (UCI) in wireless communication of the uplink (wireless communication from the terminal device to the base station device). Here, the uplink control information can include channel state information (CSI) indicating a state of a channel of the downlink. Further, the uplink control information can include a scheduling request (SR) for requesting a UL-SCH resource. Further, the uplink control information can include a HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).

[0112] The PDSCH can be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Further, in the case of the downlink, also used to transmit system information (SI), a random access response (RAR), and the like.

[0113] PUSCH can be used to transmit HARQ-ACK and / or CSI along with uplink data (UL-SCH: Uplink Shared Channel) or uplink data from the MAC layer. Additionally, PUSCH can be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH can also be used to transmit only UCI. Furthermore, PDSCH or PUSCH can be used to transmit RRC signaling (also known as RRC messages) and MAC control elements. Here, in PDSCH, the RRC signaling transmitted from the base station device can be signaling shared by multiple terminal devices within the cell. Furthermore, the RRC signaling transmitted from the base station device can also be signaling dedicated to a specific terminal device (also known as dedicated signaling). That is, dedicated signaling can be used to transmit terminal device-specific (UE-specific) information to a specific terminal device. Additionally, PUSCH can be used to transmit UE capabilities in the uplink.

[0114] PRACH can be used to send random access preambles. PRACH can be used to indicate the initial connection establishment process, the handover procedure, the connection re-establishment process, synchronization (timing adjustment) sent for the uplink, and requests for PUSCH (UL-SCH) resources.

[0115] MAC302 is a medium access control layer that maps multiple logical channels to multiple transmission channels. MAC302 can connect to the higher-level RLC (Radio Link Control layer) 304 (described later) via logical channels. Logical channels can be broadly classified according to the type of information transmitted, into control channels transmitting control information and service channels transmitting user information. MAC302 may have functions such as controlling PHY300 for intermittent transmit / receive (DRX / DTX), executing random access procedures, notifying transmit power information, and performing HARQ control (Non-Patent Document 13).

[0116] The uplink (UL) and / or downlink (DL) used in NR are described using logical channels.

[0117] The BCCH (Broadcast Control Channel) can be a downlink logical channel for broadcasting control information such as system information (SI).

[0118] The PCCH (Paging Control Channel) can be a downlink logical channel for carrying a paging message.

[0119] The CCCH (Common Control Channel) can be a logical channel for transmitting control information between the UE 122 and the gNB 108. The CCCH can also be used in a case where the UE 122 does not have an RRC connection. Furthermore, the CCCH can also be used between a base station device and a plurality of terminal devices.

[0120] The DCCH (Dedicated Control Channel) can be a logical channel for transmitting dedicated control information between the UE 122 and the gNB 108 in a point-to-point bi-directional manner. The dedicated control information can refer to control information dedicated to each terminal device. The DCCH can also be used in a case where the UE 122 has an RRC connection.

[0121] The DTCH (Dedicated Traffic Channel) can be a logical channel for transmitting user data between the UE 122 and the gNB 108 in a point-to-point manner. The DTCH can exist in both the uplink and the downlink.

[0122] The mapping of the logical channels and the transport channels for the uplink in NR is described.

[0123] The CCCH can be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0124] The DCCH can also be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0125] The DTCH can also be mapped to the UL-SCH (Uplink Shared Channel) as an uplink transport channel.

[0126] The mapping of the logical channels and the transport channels for the downlink in NR is described.

[0127] The BCCH can be mapped to a BCH (Broadcast Channel) and / or a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0128] The PCCH can be mapped to a PCH (Paging Channel) as a downlink transport channel.

[0129] The CCCH can be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0130] The DCCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0131] The DTCH can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0132] The RLC 304 is a radio link control layer that segments data received from a PDCP (Packet Data Convergence Protocol Layer) 306 described later, adjusts the data size so that the lower layer can appropriately perform data transmission. The RLC 304 has three modes of a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). In the TM, segmentation of data received from the upper layer is not performed, and addition of an RLC header is not performed. In the UM, segmentation of data received from the upper layer and addition of an RLC header are performed, but retransmission control of data is not performed. In the AM, segmentation of data received from the upper layer, addition of an RLC header, and retransmission control of data are performed. The retransmission control function can be a function for guaranteeing a QoS (Quality of Service) requested for each data. In the retransmission control of data, information of non-delivered data transmitted from the reception side of the RLC to the transmission side is called a status report. Further, an instruction to urge a status report transmitted from the transmission side of the RLC to the reception side is called a poll. Note that data transmitted to the lower layer in the TM is sometimes called a TM D PDU, data transmitted to the lower layer in the UM is sometimes called a UM D PDU, and data transmitted to the lower layer in the AM is sometimes called an AM D PDU.(Non-Patent Literature 12)

[0133] The PDCP 306 is a packet data convergence protocol layer for efficiently transmitting user data such as IP packets over a wireless section. The PDCP 306 can have a header compression function of compressing unnecessary control information. In addition, the PDCP 306 can also have a function of encrypting data, and protecting the integrity of data. Furthermore, the PDCP 306 can also have a function of re-ordering (non-patent literature 11).

[0134] The SDAP 310 is a service data adaptation protocol layer having a function of establishing (mapping) a correspondence between a QoS flow of a downlink transmitted from the 5GC 110 to the terminal device via the base station device and a DRB, and a correspondence between a QoS flow of an uplink transmitted from the terminal device to the 5GC 110 via the base station device and a DRB, and storing mapping rule information (non-patent literature 16).

[0135] Note that data processed in the MAC 302, the RLC 304, the PDCP 306, and the SDAP 310 is referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, a PDCP PDU, and an SDAP PDU, respectively. In addition, data transferred from an upper layer to the MAC 302, the RLC 304, the PDCP 306, and the SDAP 310, or data transferred to the upper layer is referred to as a MAC SDU (Service Data Unit), an RLC SDU, a PDCP SDU, and an SDAP SDU, respectively. Furthermore, a divided RLC SDU is referred to as an RLC SDU segment.

[0136] Further, in order to distinguish between data and control, the SDAP PDU can also be referred to as SDAP DATA PDU, SDAP data PDU, SDAP CONTROL PDU, SDAP control PDU, SDAP control PDU, respectively. Further, in order to distinguish between data and control, the PDCP PDU can also be referred to as PDCP DATA PDU, PDCP data PDU, PDCP CONTROL PDU, PDCP control PDU, PDCP control PDU, respectively. Further, in order to distinguish between data and control, the RLC PDU can also be referred to as RLC DATA PDU, RLC data PDU, RLC CONTROL PDU, RLC control PDU, RLC control PDU, respectively.

[0137] Figure 3 (B) is a protocol stack diagram of a CP used when the UE 122 communicates with the gNB 108 and an AMF (Access and Mobility Management function) that is a logical node that provides authentication, mobility management, etc. in the NR 106.

[0138] In the CP protocol stack, besides PHY300, MAC302, RLC304, and PDCP306, there are also RRC (Radio Resource Control layer) 308 and NAS (non-access strawrum) 312. RRC308 is a radio link control layer that handles RRC connection establishment, re-establishment, suspending, and resuming; RRC connection reconfiguration, such as establishing, changing, and releasing radio bearers (RBs) and cell groups; control of logical channels, transport channels, and physical channels; and handover and measurement settings. RBs can be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs). SRBs can be used as paths for sending RRC messages as control information. DRBs can be used as paths for sending user data. The configuration of each RB can be performed between the gNB108 and UE122's RRC308. Furthermore, the portion of the RB consisting of RLC304 and the logical channel can also be referred to as the RLC bearer (Non-Patent Document 10). Additionally, relative to the NAS layer that transmits signals between the AMF and UE122, some or all of the layers among PHY300, MAC302, RLC304, PDCP306, RRC308, and SDAP310 that transmit signals and data between UE122 and gNB108 can be referred to as the AS (Access Strarum) layer.

[0139] Further, the SRB can be defined with SRB0 to SRB3 as follows, and can be defined with SRBs other than these. SRB0 can be an SRB for an RRC message of a CCCH (Common Control Channel) using a logical channel. SRB1 can be an SRB for an RRC message (possibly including a piggybacked NAS message) and for a NAS message before establishment of SRB2, and can use a DCCH (Dedicated Control CHannel) using a logical channel in its entirety. SRB2 can be an SRB for a NAS message, and can use a DCCH using a logical channel in its entirety. Further, SRB2 can be lower in priority than SRB1. SRB3 can be an SRB for a specific RRC message at the time when the UE 122 is configured with EN-DC, NGEN-DC, NR-DC, and the like described later, and can use a DCCH using a logical channel in its entirety. Further, other SRBs can be prepared for other uses.

[0140] Further, the RRC message can be transmitted using a BCCH of a logical channel, and can be transmitted using a PCCH of a logical channel. The RRC message transmitted using the BCCH can include, for example, a Master Information Block (MIB) described in Non-Patent Literature 10, can include each type of System Information Block (SIB), and can include other RRC messages. The RRC message transmitted using the BCCH can include, for example, a paging message described in Non-Patent Literature 10, and can include other RRC messages.

[0141] The functional classification of the MAC 302, the RLC 304, the PDCP 306, the SDAP 310, and the RRC 308 described above is one example, and a part or all of each function can not be implemented. Further, a part or all of the function of each layer can be included in another layer.

[0142] Note that, as described in Non Patent Literature 2, an upper layer (not illustrated) of the AS layer can also be referred to as a PDU layer. Any one or all of an IP layer and a TCP (Transmission Control Protocol) layer, a UDP (User Datagram Protocol) layer, other layers, which are upper layers of the IP layer, can be included in the PDU layer. The application layer can be an upper layer of the PDU layer, or can be included in the PDU layer. Note that the PDU layer can be an upper layer of the AS layer with respect to the user plane. Further, the RRC layer, the NAS (non Access Stratum) layer can also be an upper layer (not illustrated) of any one or all of the SDAP layer and the PDCP layer. In other words, any one or all of the SDAP layer and the PDCP layer are lower layers of any one or all of the RRC layer, the NAS layer, the IP layer, and a TCP (Transmission Control Protocol) layer, a UDP (User Datagram Protocol) layer, an application layer, which are upper layers of the IP layer.

[0143] Note that, in each embodiment of the present application, as one of the service networks standardized in 3GPP, SIP (Session Initiation Protocol) used in IMS (IP Multimedia Subsystem), SDP (Session Description Protocol), and the like used in IMS, and any one or all of RTP (Real-time Transport Protocol), RTCP (Real-time Transport Control Protocol), HTTP (HyperText Transfer Protocol), and the like for media communication or media communication control, and various codecs of media, and the like can belong to the application layer.

[0144] Note that the physical layer, the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer of the terminal device can be any one or all of establishment, setting, and control by the RRC layer of the terminal device. Further, the RRC layer of the terminal device can establish and / or set the physical layer, the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer in accordance with a message of RRC transmitted from the RRC layer of the base station device. Further, the MAC layer (MAC layer), the RLC layer (RLC layer), the PDCP layer (PDCP layer), the SDAP layer (SDAP layer) can also be referred to as a MAC sublayer (MAC sublayer), an RLC sublayer (RLC sublayer), a PDCP sublayer (PDCP sublayer), an SDAP sublayer (SDAP sublayer), respectively.

[0145] Note that each layer or the function of each layer belonging to the AS layer set in any one or all of the terminal device and the base station device can also be referred to as an entity. That is, the physical layer (PHY layer), the MAC layer, the RLC layer, the PDCP layer, the SDAP layer, and the RRC layer or the function of each layer can also be referred to as a physical entity (PHY entity), a MAC entity, an RLC entity, a PDCP entity, an SDAP entity, and an RRC entity, respectively, which are any one or all of establishment, setting, and control in any one or all of the terminal device and the base station device. Further, one or a plurality of entities of each layer can be included in each layer. Further, the PDCP entity and the RLC entity can be any one or all of establishment, setting, and control per radio bearer. Further, the MAC entity can be any one or all of establishment, setting, and control per cell group. Further, the SDAP entity can be any one or all of establishment, setting, and control per PDU session.

[0146] Note that in the PDCP layer or the PDCP entity, a COUNT value can be used when processing encryption or integrity protection is performed. The COUNT value can be constituted by an HFN (Hyper Frame Number) and a sequence number (SN) added to the header of a PDCP PDU. The sequence number can be incremented by 1 each time a PDCP DATA PDU is generated in the PDCP layer or the PDCP entity on the transmission side. The HFN can be incremented by 1 each time the sequence number reaches the maximum value. Further, any one or all of the following (A) to (F) can be used as state variables for managing the COUNT value on the transmission side and the reception side.

[0147] (A) is a state variable indicating the COUNT value of the PDCP SDU to be transmitted next. It can also be a state variable of the name TX_NEXT described in Non-Patent Literature 11.

[0148] (B) is a state variable indicating the sequence number of the PDCP SDU to be transmitted next in the present PDCP entity. It can also be a state variable of the name Next_PDCP_TX_SN described in Non-Patent Literature 5.

[0149] (C) is a state variable indicating the HFN value of the COUNT value used for generating a PDCP PDU in the present PDCP entity. It can also be a state variable of the name TX_HFN described in Non-Patent Literature 5.

[0150] (D) is a state variable indicating the COUNT value of the PDCP SDU expected to be received next on the receiving side of the PDCP entity. It can also be a state variable of the name RX_NEXT described in Non-Patent Literature 11.

[0151] (E) is a state variable indicating the sequence number of the PDCP SDU expected to be received next on the receiving side of the present PDCP entity. It can also be a state variable of the name Next_PDCP_RX_SN described in Non-Patent Literature 5.

[0152] (F) is a state variable indicating the HFN value of the COUNT value used for generating a PDCP PDU in the present PDCP entity. It can also be a state variable of the name RX_HFN described in Non-Patent Literature 5.

[0153] Further, in the PDCP layer or PDCP entity, re-ordering can mean processing for storing PDCP SDUs in a reception buffer and delivering the PDCP SDUs to an upper layer in order of COUNT values obtained from header information of PDCP DATA PDUs. Further, re-ordering can also include processing for delivering the stored PDCP SDUs to the upper layer in order of COUNT values in a case where a COUNT value of a received PDCP DATA PDU is a COUNT value of a first PDCP SDU which has not been delivered to the upper layer. That is, it can be processing in which, in re-ordering, in a case where a PDCP DATA PDU having a COUNT value smaller than a COUNT value of a received PDCP DATA PDU cannot be received (PDCP DATA PDU loss), the received PDCP DATA PDU is converted into a PDCP SDU and stored in a re-ordering buffer, and after all of the lost PDCP DATA PDUs are received and converted into PDCP SDUs, the PDCP SDUs are delivered to the upper layer. A re-ordering timer (a timer of the name t-Reordering described in Non-Patent Literature 11 or Non-Patent Literature 5) can also be used in re-ordering for detecting loss of PDCP DATA PDUs. Further, re-ordering can be performed using some or all of the following (A) to (F) state variables.

[0154] (A) is a state variable indicating a COUNT value of a PDCP SDU expected to be next received on a reception side of the PDCP entity. It can be a state variable of the name RX_NEXT described in Non-Patent Literature 11.

[0155] (B) is a state variable indicating a sequence number of a PDCP SDU expected to be next received on a reception side of the PDCP entity. It can be a state variable of the name Next_PDCP_RX_SN described in Non-Patent Literature 5.

[0156] (C) is a state variable indicating a HFN value used for generating a COUNT value for a received PDCP PDU in the PDCP entity. It can be a state variable of the name RX_HFN described in Non-Patent Literature 5.

[0157] (D) is a state variable indicating a COUNT value of a first PDCP PDU among PDCP SDUs which are waiting for reception on a reception side of the PDCP entity without being delivered to an upper layer. It can be a state variable of the name RX_DELIV described in Non-Patent Literature 11.

[0158] (E) represents a state variable indicating the sequence number of the PDCP PDU that was last transmitted to the upper-layer PDCP SDU on the receiving side of this PDCP entity. It can also be a state variable with the name Last_Submitted_PDCP_RX_SN, as described in Patent Document 5.

[0159] (F) represents the state variable for the next COUNT value of the PDCP PDU that triggers the reordering timer on the receiving side of the PDCP entity. It can also be a state variable named RX_REORD as described in Non-Patent Document 11 or a state variable named Reordering_PDCP_RX_COUNT as described in Non-Patent Document 5.

[0160] It should be noted that, in the various embodiments of the present invention, to distinguish between the E-UTRA protocol and the NR protocol, MAC202, RLC204, PDCP206, and RRC208 will be referred to as E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Furthermore, MAC302, RLC304, PDCP306, and RRC308 will be referred to as NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Alternatively, spaces may be used to denote terms such as E-UTRA PDCP or LTE PDCP, NR PDCP, etc.

[0161] In addition, such as Figure 1 As shown, eNB102, gNB108, EPC104, and 5GC110 can be connected via interfaces 112, 116, 118, 120, and 114. Therefore, to accommodate various communication systems, Figure 2 RRC208 can be replaced with Figure 3 RRC308. In addition, Figure 2 PDCP206 can also be replaced with Figure 3 PDCP306. In addition... Figure 3 The RRC308 may include Figure 2 The functions of RRC208. In addition. Figure 3 PDCP306 can be Figure 2 PDCP206. Furthermore, in E-UTRA100, even when UE122 is communicating with eNB102, NR PDCP can be used as the PDCP.

[0162] Next, state transitions of the UE 122 in LTE and NR are described. When an RRC connection has been established, the UE 122 connected with the EPC or the 5GC can be in an RRC CONNECTED state. The state in which the RRC connection has been established can include a state in which the UE 122 holds a part or all of a UE context described later. Further, the state in which the RRC connection has been established can also include a state in which the UE 122 can transmit and / or receive unicast data. Further, the UE 122 can be in an RRC INACTIVE state when the RRC connection is suspended (if the UE 122 is connected with the 5GC). If not, the UE 122 can be in an RRC IDLE state.

[0163] Note that the UE 122 connected to the EPC does not have the RRC INACTIVE state, but can start suspension of the RRC connection through the E-UTRAN. In this case, when the RRC connection is suspended, the UE 122 holds the UE's AS context and a resumeIdentity for resumption and transitions to the RRC IDLE state. When the UE 122 holds the UE's AS context and the resumption of the RRC connection is permitted through the E-UTRAN, and the UE 122 needs to transition from the RRC IDLE state to the RRC CONNECTED state, resumption of the suspended RRC connection can be started through an upper layer (e.g., the NAS layer).

[0164] That is, among the UE 122 connected to the EPC and the UE 122 connected to the 5GC, the definition of suspension can be different. Further, under the condition that the UE 122 is connected to the EPC (suspended in the RRC IDLE state) and the condition that the UE 122 is connected to the 5GC (suspended in the RRC INACTIVE state), all or a part of the procedure for the UE 122 to resume from suspension can be different.

[0165] Note that the RRC CONNECTED state, the RRC INACTIVE state, the RRC IDLE state can be referred to as a connected mode, an inactive mode, an idle mode, respectively, or can be referred to as an RRC connected mode, an RRC inactive mode, an RRC idle mode, respectively.

[0166] The UE's AS context held by the UE 122 can be information including all or a part of the current RRC configuration, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the PCell of the connection source, the cell identifier (cellIdentity), the physical cell identifier of the PCell of the connection source. Note that the UE's AS context held by any one or both of the eNB 102 and the gNB 108 can include the same information as the UE's AS context held by the UE 122 or different information from the information included in the UE's AS context held by the UE 122.

[0167] The security context can refer to information including all or a part of the encryption key in the AS level, the NH (Next Hop parameter), the NCC (Next Hop Chaining Counter parameter) for access key derivation of the next hop, the identifier of the selected encryption algorithm in the AS level, and the counter for replay protection.

[0168] Next, handover in LTE and NR is described. The handover can refer to a process in which the UE 122 in the RRC connected state changes the serving cell. The handover can be performed when the UE 122 receives an RRC message indicating the handover from the eNB 102 and / or the gNB 108. The RRC message indicating the handover can refer to a message related to reconfiguration of the RRC connection including a parameter indicating the handover (for example, an information element of the name MobilityControlInfo described in Non-Patent Literature 4 or an information element of the name ReconfigurationWithSync described in Non-Patent Literature 10), and can refer to a message indicating movement to a cell of another RAT (for example, MobilityFromEUTRACommand described in Non-Patent Literature 4 or MobilityFromNRCommand described in Non-Patent Literature 10). Further, the conditions in which the UE 122 can perform the handover can include when the AS security is activated, when the SRB2 is established, and when at least a part or all of the DRBs are established.

[0169] Figure 4is a diagram showing one example of a procedure for various settings in the RRC 208 and / or the RRC 308 according to each embodiment of the present application. Figure 4 is one example of a procedure in a case where an RRC message is transmitted from a base station device (eNB 102 and / or gNB 108) to a terminal device (UE 122).

[0170] In Figure 4 , the base station device generates an RRC message (step S400). The generation of the RRC message in the base station device can be performed when the base station device transmits broadcast information (System Information: SI), paging information, or can be performed when it is determined that the base station device needs to perform processing for a specific terminal device, for example, a setting related to security, re-setting of an RRC connection (processing of a radio bearer (establishment, change, release, and the like), processing of a cell group (establishment, addition, change, release, and the like), measurement setting, handover setting, and the like), release of an RRC connection state, and the like. Further, the RRC message can be used for a handover command to a different RAT. Information (parameters) for various information notification, setting are included in the RRC message. In the standards related to RRC such as Non-Patent Literature 4 or Non-Patent Literature 10, these parameters can also be referred to as fields and / or information elements, and are described using ASN.1 (Abstract Syntax Notation One).

[0171] In Figure 4 , next, the base station device transmits the generated RRC message to the terminal device (step S402). Next, the terminal device performs processing in a case where setting and the like need to be performed, based on the received RRC message (step S404).

[0172] Note that the generation of the RRC message is not limited to the above example, and can be performed for other purposes as described in Non-Patent Literature 4, Non-Patent Literature 10, and the like.

[0173] For example, the RRC message can be used for a setting related to Dual Connectivity (DC), Multi-Radio Dual Connectivity (MR-DC) described in Non-Patent Literature 8.

[0174] Dual Connectivity (DC) can refer to a technique of performing data communication using radio resources of both a master cell group (MCG) constituted by a master node (MN) and a second cell group (SCG) constituted by a second node (SN) which are cell groups constituted by two base station devices (nodes). Further, the master node and the second node can be the same node (the same base station device). Further, MR-DC can refer to a technique of performing data communication using radio resources of both the MCG and the SCG by grouping cells of both E-UTRA and NR per RAT and allocating to a UE as described in Non-Patent Literature 8, and can refer to dual connectivity (DC) using a RAT of NR. In the MR-DC, the master node can refer to a base station having a main RRC function of the MR-DC, such as addition of a second node, establishment, change, and release of an RB, addition, change, release, and handover of the MCG, and the like, and the second node can refer to a base station having a part of the RRC function, such as change and release of the SCG, and the like.

[0175] In the MR-DC described in Non-Patent Literature 8, the RRC of the RAT on the master node side can be used to perform setting of both the MCG and the SCG. For example, in EN-DC (E-UTRA-NR Dual Connectivity) of the MR-DC in a case where the core network is the EPC 104 and the master node is the eNB 102 (also referred to as an extended eNB 102), and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) of the MR-DC in a case where the core network is the 5GC 110 and the master node is the eNB 102, the RRC message of E-UTRA described in Non-Patent Literature 4 can be transmitted and received between the eNB 102 and the UE 122. In this case, the RRC message can include not only the setting information of LTE (E-UTRA) but also the setting information of NR described in Non-Patent Literature 10. Further, the RRC message transmitted from the eNB 102 to the UE 122 can be transmitted from the eNB 102 to the UE 122 via the gNB 108. Further, the configuration of the present RRC message can be used for the E-UTRA / 5GC in which the eNB 102 (extended eNB) uses the 5GC as the core network.

[0176] Further, in the MR-DC described in Non-Patent Literature 8, in NE-DC (NR-E-UTRA Dual Connectivity) of the MR-DC in the case where the core network is the 5GC 110 and the master node is the gNB 108, the RRC message of the NR described in Non-Patent Literature 10 can be transmitted and received between the gNB 108 and the UE 122. In this case, in the RRC message, not only the configuration information of the NR but also the configuration information of the LTE (E-UTRA) described in Non-Patent Literature 4 can be included. Further, the RRC message transmitted from the gNB 108 to the UE 122 can also be transmitted from the gNB 108 to the UE 122 via the eNB 102.

[0177] Note that, not limited to the case of the MR-DC, the RRC message of the NR can be included in the RRC message of the E-UTRA transmitted from the eNB 102 to the UE 122, and the RRC message of the E-UTRA can be included in the RRC message of the NR transmitted from the gNB 108 to the UE 122.

[0178] Further, the network configuration in which the master node is the eNB 102 and the EPC 104 is the core network can also be referred to as E-UTRA / EPC. Further, the network configuration in which the master node is the eNB 102 and the 5GC 110 is the core network can also be referred to as E-UTRA / 5GC. Further, the network configuration in which the master node is the gNB 108 and the 5GC 110 is the core network can also be referred to as NR or NR / 5GC. Further, the designation can not be limited to the case where the DC is configured. In the case where the DC is not configured, the master node described above can mean a base station device that communicates with the terminal device.

[0179] Figure 7 is one example of an ASN.1 description of a field and / or an information element related to the radio bearer configuration included in the message related to the reconfiguration of the RRC connection in the NR in Figure 4 . Further, Figure 8 is one example of an ASN.1 description of a field and / or an information element related to the radio bearer configuration included in the message related to the reconfiguration of the RRC connection in the E-UTRA in Figure 4 . Not limited to Figure 7 , Figure 8In the example of the ASN.1 of the embodiment of the present application, <omitted> and <middle omitted> indicate omission of other information, rather than omission of a part of the expression of the ASN.1. Note that, in a case where such a notation of <omitted> or <middle omitted> is not described, the information element can also be omitted. Note that, in the embodiment of the present application, the example of the ASN.1 does not correctly follow the expression method of the ASN.1, but expresses one example of the parameters of the message related to the RRC connection reconfiguration of the embodiment of the present application, and other names or other expressions can also be used. Further, in order to avoid complication of the description, the example of the ASN.1 expresses only an example of the main information closely related to one embodiment of the present application. Note that, sometimes, the parameters described by the ASN.1 are not distinguished from the fields, information elements, and the like, but are all referred to as information elements. Further, in the embodiment of the present application, sometimes, the fields, information elements, and the like described by the ASN.1 included in the RRC message are referred to as information. Note that, the message related to the RRC connection reconfiguration can be the RRC reconfiguration message in the NR, or the RRC connection reconfiguration message in the E-UTRA.

[0180] In Figure 7 The information element represented by RadioBearerConfig is an information element related to the configuration of the radio bearer such as the SRB, the DRB, and the like, and includes the PDCP configuration information element, the SDAP configuration information element described later. The information element represented by SRB-ToAddMod included in the information element represented by RadioBearerConfig can be information indicating the configuration of the SRB (signaling radio bearer), and is sometimes also referred to as an SRB configuration information element or a signaling radio bearer configuration information element. Further, the information element represented by SRB-ToAddModList can be a list of information indicating the configuration of the SRB. The information element represented by DRB-ToAddMod included in the information element represented by RadioBearerConfig can be information indicating the configuration of the DRB (data radio bearer), and is sometimes also referred to as a DRB configuration information element or a data radio bearer configuration information element. The information element represented by DRB-ToAddModList can be a list of information indicating the configuration of the DRB. Note that, sometimes, either or both of the SRB configuration and the DRB configuration are also referred to as a radio bearer configuration.

[0181] The information element represented by SRB-Identity in the SRB setting information element is information of an SRB identifier (SRB Identity) of an SRB to be added or changed, and can also be an identifier that uniquely identifies an SRB in each terminal device. The information element represented by SRB-Identity in the SRB setting information element is sometimes also referred to as an SRB identifier information element or a radio bearer identifier information element or a signaling radio bearer identifier information element.

[0182] The information element represented by DRB-Identity in the DRB setting information element is information of a DRB identifier (DRB Identity) of a DRB to be added or changed, and can also be an identifier that uniquely identifies a DRB in each terminal device. The information element represented by DRB-Identity in the DRB setting information element is sometimes also referred to as a DRB identifier information element or a radio bearer identifier information element or a data radio bearer identifier information element. Figure 7 In the example of Table 1, the value of the DRB identifier is set to an integer value of 1 to 32, but can also take other values. In the case of DC, the DRB identifier is unique within the range of the UE 122.

[0183] The information element represented by cnAssociation in the DRB setting information element can be an information element indicating whether EPC 104 or 5GC 110 is used in the core network, and is sometimes also referred to as a core network establishment association information element. That is, it can also be that, when the UE 122 is connected with the EPC, the DRB is associated with an EPS bearer identifier information element (eps-BearerIdentity) in the cnAssociation or an EPS bearer identifier (EPS bearer identity) that is a value of the EPS bearer identifier information element, and when the UE 122 is connected with the 5GC 110, the DRB is associated with an SDAP entity set in accordance with a later-described SDAP setting information element (sdap-Config), or a later-described PDU session information element included in the SDAP setting information element, or a PDU session identifier that is a value of the PDU session information element, or a PDU session indicated by the PDU session information element. That is, in the information represented by cnAssociation, in the case of using EPC 104 in the core network in the case of using EN-DC or the like, the EPS bearer identifier information element (eps-BearerIdentity) is included, and in the case of using the core network 5GC 110, that is, in the case of not using EN-DC or the like, an information element (sdap-Config) indicating the SDAP setting is included.

[0184] In a case where the core network is the 5GC 110, an information element represented by sdap-Config can be information related to setting or re-setting of an SDAP entity that determines a mapping method of a QoS flow to a DRB, and is also sometimes referred to as an SDAP setting information element.

[0185] A field or information element represented by pdu-session or PDU-SessionID included in the SDAP setting information element can be a PDU session identifier of a PDU session described in Non-Patent Literature 2 to which a QoS flow corresponding to a value of a radio bearer identifier information element is mapped, and is also sometimes referred to as a PDU session identifier information element. A value of the PDU session identifier information element can be a non-negative integer. Furthermore, in each terminal device, one PDU session identifier can correspond to a plurality of DRB identifiers.

[0186] An information element represented by mappedQoS-FlowsToAdd included in the SDAP setting information element can be information of a list of QoS flow identifier (QFI: QoS Flow Identity) information elements representing QoS flows corresponding to or additionally corresponding to a value of a radio bearer identifier information element included in a DRB setting information element including the present SDAP setting information element, and is also sometimes referred to as an additional QoS flow information element. The above-described QoS flow can be a QoS flow of a PDU session indicated by a PDU session information element included in the present SDAP setting information element.

[0187] Furthermore, an information element represented by mappedQoS-FlowsToRelease included in the SDAP setting information element can be information of a list of QoS flow identifier (QFI: QoS Flow Identity) information elements representing QoS flows in which a correspondence relationship is released, among QoS flows corresponding to a value of a radio bearer identifier information element included in a DRB setting information element including the present SDAP setting information element, and is also sometimes referred to as a released QoS flow information element. The above-described QoS flow can be a QoS flow of a PDU session indicated by a PDU session information element included in the present SDAP setting information element.

[0188] The information element represented by the QFI can be a QoS flow identifier that uniquely identifies a QoS flow described in Non-Patent Literature 2, and is also sometimes referred to as a QoS flow identifier information element. The value of the QoS flow identifier information element can be a non-negative integer. Furthermore, the value of the QoS flow identifier information element can be unique to a PDU session.

[0189] Furthermore, in the SDAP configuration information element, in addition to this, an uplink header information element indicating whether or not there is an SDAP header for uplink in uplink data transmitted via a configured DRB, a downlink header information element indicating whether or not there is an SDAP header for downlink in downlink data received via a configured DRB, a default bearer information element indicating whether or not a configured DRB is a default radio bearer (default DRB), and the like can be included.

[0190] Furthermore, the information element represented by pdcp-Config or PDCP-Config in the SRB configuration information element and the DRB configuration information element can be an information element related to the configuration of an NR PDCP entity for performing establishment and change of the PDCP 306 for the SRB and / or for the DRB, and is also sometimes referred to as a PDCP configuration information element. The information element related to the configuration of the NR PDCP entity can include an information element indicating the size of a sequence number for uplink, an information element indicating the size of a sequence number for downlink, an information element indicating the profile of header compression (RoHC: RObust Header Compression), a re-ordering timer information element, and the like.

[0191] The information element represented by DRB-ToReleaseList included in the information element represented by RadioBearerConfig can include information indicating one or more DRB identifiers to be released.

[0192] In Figure 8The information element represented by RadioResourceConfigDedicated can also be an information element for setting, changing, releasing, and the like of a radio bearer. The information element represented by SRB-ToAddMod included in the information element represented by RadioResourceConfigDedicated can be information representing SRB (Signaling Radio Bearer) setting, and is also sometimes referred to as SRB setting information element or signaling radio bearer setting information element. The information element represented by SRB-ToAddModList can be a list of information representing SRB setting. The information element represented by DRB-ToAddMod included in the information element represented by RadioResourceConfigDedicated can be information representing DRB (Data Radio Bearer) setting, and is also sometimes referred to as DRB setting information element or data radio bearer setting information element. The information element represented by DRB-ToAddModList can be a list of information representing DRB setting. Note that, either or both of the SRB setting and the DRB setting are also sometimes referred to as radio bearer setting.

[0193] The information element represented by SRB-Identity in the SRB setting information element is information of an SRB identifier (SRB Identity) of an SRB to be added or changed, and can also be an identifier uniquely identifying the SRB in each terminal device. The information element represented by SRB-Identity in the SRB setting information element is also sometimes referred to as SRB identifier information element or radio bearer identifier information element or signaling radio bearer identifier information element. Figure 8 The information element represented by SRB-Identity in the SRB setting information element can also be an information element having the same role as Figure 7 The information element represented by SRB-Identity in the SRB setting information element can also be an information element having the same role as

[0194] The information element represented by DRB-Identity in the DRB setting is information of a DRB identifier (DRB Identity) of a DRB to be added or changed, and can also be an identifier uniquely identifying the DRB in each terminal device. The information element represented by DRB-Identity in the DRB setting is also sometimes referred to as DRB identifier information element or radio bearer identifier information element or data radio bearer identifier information element. In the example of Figure 8 The value of the DRB identifier is set to an integer value of 1 to 32 in the example of Figure 8 The information element represented by DRB-Identity in the DRB setting information element can also be an information element having the same role as Figure 7 The information element represented by DRB-Identity in the DRB setting information element can also be an information element having the same role as

[0195] The information element represented by eps-BearerIdentity in the DRB setup information element can be an EPS bearer identifier that uniquely identifies an EPS bearer in each terminal device. The information element represented by eps-BearerIdentity is also sometimes referred to as an EPS bearer identifier information element. In Figure 8 In an example, the value of the EPS bearer identifier is set to an integer value of 1 to 15, but can also take other values. Figure 8 The information element represented by eps-BearerIdentity in the DRB setup information element can also be an information element having the same role as the Figure 7 The information element represented by eps-BearerIdentity in the DRB setup information element has the same role as the information element. Furthermore, the EPS bearer identifier and the DRB identifier can correspond one-to-one in each terminal device.

[0196] Furthermore, the information element represented by pdcp-Config or PDCP-Config in the SRB setup information element and the DRB setup information element can be an information element related to the setup of the PDCP 206 for the SRB and / or for the DRB, and is sometimes also referred to as a PDCP setup information element. In the information element related to the setup of the E-UTRA PDCP entity, an information element representing the size of the sequence number, an information element representing the profile of the header compression (RoHC: RObust Header Compression), a re-ordering timer information element, and the like can be included.

[0197] Furthermore, Figure 7 or Figure 8 Some or all of the information elements shown in the SRB setup information element and the DRB setup information element can be optional. That is, Figure 7 or Figure 8 The information elements shown in the SRB setup information element and the DRB setup information element can be included in the message related to the re-setup of the RRC connection as needed, on a condition. Furthermore, in the message related to the re-setup of the RRC connection, an information element meaning that the full setup is applied can be included in addition to the information element related to the setup of the radio bearer. The information element meaning that the full setup is applied can be represented by an information element name such as fullConfig, and can also be represented by true (true), enable (enable), and the like to indicate the application of the full setup.

[0198] The information element represented by DRB-ToReleaseList included in the information element represented by RadioResourceConfigDedicated can include information representing one or more DRB identifiers to be released.

[0199] During the establishment, re-establishment, or handover of an RRC connection, a serving cell provides NAS mobility information. During the re-establishment or handover of an RRC connection, a serving cell provides security input. This serving cell can be referenced as the primary cell (PCell). Furthermore, depending on the capabilities of the terminal device, one or more serving cells (secondary cells, SCells) can be added and configured along with the primary cell.

[0200] Furthermore, a set of serving cells consisting of two subsets can be configured for the terminal device. These two subsets can consist of: a cell group (primary cell group) comprising one or more serving cells including a primary cell (PCell) and one or more cell groups (secondary cell group) comprising one or more serving cells including a primary secondary cell (PSCell) but not a primary cell. The primary and secondary cells can be cells configured with PUCCH resources. It should be noted that PCell and / or PSCell can also be referred to as a special cell (SpCell).

[0201] Based on the above description, various embodiments of the present invention will be described. It should be noted that the processes described above can be applied to the processes omitted in the following description.

[0202] Figure 5 This is a block diagram illustrating the configuration of the terminal device (UE122) according to various embodiments of the present invention. It should be noted that, to avoid unnecessary detail, in... Figure 5 Only the main components closely related to one embodiment of the invention are shown.

[0203] Figure 5 The UE122 shown comprises a receiving unit 500 that receives RRC messages from a base station device, a processing unit 502 that processes configuration information based on any or all of the various information elements (IEs), fields, and conditions included in the received messages, and a transmitting unit 504 that sends RRC messages to the base station device. The base station device mentioned above sometimes refers to eNB102 and sometimes to gNB108. Furthermore, the processing unit 502 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer). That is, the processing unit 502 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, RRC layer processing unit, and NAS layer processing unit.

[0204] Figure 6 This is a block diagram illustrating the configuration of a base station apparatus according to various embodiments of the present invention. It should be noted that, to avoid unnecessary detail, in... Figure 6Only the main components closely related to one embodiment of the present application are shown in the figure. The base station device described above is sometimes referred to as eNB 102 and sometimes as gNB 108.

[0205] Figure 6 The base station device shown in the figure is configured to include a transmission section 600 that transmits an RRC message or the like to the UE 122, a processing section 602 that creates an RRC message including any one or all of various information elements (IEs), various fields, and various conditions and the like, and causes the processing section 502 of the UE 122 to perform processing by transmitting to the UE 122, and a reception section 604 that receives an RRC message or the like from the UE 122. Further, the processing section 602 can include some or all of the functions of various layers (for example, a physical layer, a MAC layer, an RLC layer, a PDCP layer, an RRC layer, and a NAS layer). That is, the processing section 602 can include some or all of a physical layer processing section, a MAC layer processing section, an RLC layer processing section, a PDCP layer processing section, an RRC layer processing section, and a NAS layer processing section.

[0206] Using Figures 9-11 An outline of the action of MBMS transmission / reception using SC-PTM will be described. Note that the MBMS, MBMS service, and MBMS session, which are terms used in the following description, can be terms having the same meaning and can be used interchangeably.

[0207] Figure 9 is a diagram showing a flow of a procedure for setting for MBMS reception using SC-PTM. Figure 10 is a diagram showing Figure 9 in Figure 11 is a diagram showing one example of an ASN.1 description representing a field and / or an information element included in a SIB20 (System Information Block Type 20) in Figure 9

[0208] As shown in Figure 9 , the processing section 602 of the eNB 102 generates a SIB20 (System Information Block type 20) as an RRC message, and transmits it to the UE 122 via the BCCH from the transmission section 600. The reception section 500 of the UE 122 receives the SIB20. (Step S900)

[0209] ​As described in Non-Patent Literature 4, the SIB20 includes information required to acquire control information (specifically, SC-MCCH) related to transmission of MBMS using SC-PTM. For example, the SIB20 includes some or all of fields and / or information elements such as a field represented by sc-mcch-ModificationPeriod indicating a period in which the contents of the SC-MCCH can be changed, a field represented by sc-mcch-RepetitionPeriod indicating a transmission (retransmission) time interval of the SC-MCCH by the number of radio frames, a field represented by sc-mcch-Offset indicating an offset of a radio frame in which the SC-MCCH is scheduled, a field represented by sc-mcch-FirstSubframe indicating a subframe in which the SC-MCCH is scheduled, a field represented by sc-mcch-duration indicating a duration of a subframe in which the SC-MCCH is scheduled, and the like.

[0210] Next, the processing section of the eNB 102 generates an SC-PTM configuration message (SCPTMConfiguration) as an RRC message, and transmits it from the transmission section 600 via the SC-MCCH. The reception section 500 of the UE 122 receives the SC-PTM configuration information based on the configuration of the SIB20. In the physical layer, the SC-RNTI (Single Cell RNTI) is used in the transmission of the SC-MCCH.

[0211] (Step S902).

[0212] As described in Non-Patent Literature 4, the SC-PTM configuration information includes control information applicable to MBMS reception. For example, the SC-PTM configuration information includes some or all of fields and / or information elements such as a field represented by sc-mtch-InfoList including the configuration of each SC-MTCH in a cell transmitting the information, and a field represented by scptm-NeighbourCellList as a list of adjacent cells providing MBMS, and the like.

[0213] The sc-mtch-InfoList includes information elements represented by one or more SC-MTCH-Info. Each SC-MTCH-Info includes some or all of a field represented by mbmsSessionInfo that is information of an MBMS session, a field represented by g-RNTI that is an RNTI (Radio Network Temporary Identifier) identifying a multicast group (specifically, an SC-MTCH destined for a certain group), a field represented by sc-mtch-schedulingInfo that is DRX information for the SC-MTCH, a field represented by sc-mtch-neighbourCell that is information of a neighbor cell capable of receiving the MBMS session using the SC-MTCH, and the like. The mbmsSessionInfo includes some or all of a field represented by tmgi that is an identifier, TMGI (Temporary Mobile Group Identity), identifying an MBMS bearer service described in Non-Patent Literature 15 and the like, and a field represented by sessionId that is an identifier of the MBMS session described in Non-Patent Literature 15 and the like.

[0214] The processing section 502 of the UE 122 can perform SC-MRB (Single Cell MBMS Point to Multipoint Radio Bearer) setup processing as wireless bearer for reception of an MBMS session using SC-PTM, for starting reception of an MBMS session of interest (step S904). The SC-MRB setup processing can be initiated, for example, at the start of the MBMS session, when the UE 122 enters a cell providing an MBMS service of interest via SC-MRB, when interested in the MBMS service, when the restriction of the UE capability that suppresses reception of the MBMS service is removed, and the like. The SC-MRB setup processing can also be performed when the UE 122 is in the RRC_IDLE state, and can also be performed when the UE 122 is in the RRC_CONNECTED state. The processing section 502 of the UE 122 can also perform some or all of the following (A) to (D) when performing the SC-MRB setup processing.

[0215] (A) Establishes an RLC entity in accordance with the default setting of the SC-MCCH and the SC-MTCH.

[0216] (B) Configure the SC-MTCH logical channel applied to the SC-MRB to be established, and instruct the MAC entity to receive the MBMS session according to the SC-PTM configuration message for the cell that receives the above-mentioned SC-PTM configuration message.

[0217] (C) For the SC-MRB to be established, set the physical layer based on the above sc-mtch-InfoList.

[0218] (D) The establishment of the SC-MRB is notified to the upper layer by notifying the tmgi and sessionId corresponding to the established SC-MRB.

[0219] The processing unit 502 of UE122 receives the MBMS session via the established SC-MRB according to the SC-PTM setting message described above (step S906). Alternatively, before receiving the MBMS session, the processing unit 502 of UE122 generates an MBMS Interest Indication message to notify eNB102 of its interest in receiving MBMS service via SC-MRB or its interest in receiving MBMS service, and sends it from the sending unit 504 to eNB102 (not shown). The MBMS Interest Indication message may also include information on whether MBMS service reception takes precedence over unicast reception. Furthermore, the MBMS Interest Indication message may be sent after receiving SIB20 and transitioning to the RRC_CONNECTED state, or after transitioning to the RRC_CONNECTED state. Additionally, the MBMS Interest Indication message may be sent if SIB20 is received during handover, or if SIB20 is received during the re-establishment of the RRC connection.

[0220] The processing unit 502 of UE122 can perform SC-MRB release processing to stop the reception of the MBMS session (step S908). SC-MRB release processing can be initiated, for example, when stopping a currently receiving MBMS session, when leaving a cell where SC-MRB has been established, when losing interest in MBMS service, or when MBMS service reception is suppressed due to limitations in UE capabilities. SC-MRB release processing can also be performed when UE122 is in the RRC_IDLE state, or when UE122 is in the RRC_CONNECTED state. When performing SC-MRB release processing, the processing unit 502 of UE122 can also perform some or all of the following processes (A) to (B).

[0221] (A) Release the RLC entity of the SC-MRB to be released and the associated MAC and physical layer settings.

[0222] (B) The release of the SC-MRB is notified by notifying the tmgi and the sessionId corresponding to the released SC-MRB to the upper layer.

[0223] The above describes an outline of the operation regarding the setting of the MBMS reception using the SC-PTM. As described in Non-Patent Literature 4 and the like, in addition to the MBMS transmission from the base station device using the SC-PTM and the MBMS reception in the terminal device (hereinafter described as MBMS transmission / reception), the MBMS transmission / reception using the MBSFN is also standardized. However, in the MBMS transmission / reception using the SC-PTM described in Non-Patent Literature 4 and the MBMS transmission / reception using the MBSFN, E-UTRA is used as the RAT. The multicast / broadcast service (MBS: Multicast Broadcast Service) transmission / reception using NR as the RAT has not been standardized.

[0224] Using Figures 12-13 One example of the operation regarding the setting of the MBS reception in the embodiment of the present application is described. Note that the MBS, the MBS service, and the MBS session, which are terms used in the embodiment of the present application, can also be terms having the same meaning and can be interchangeable. Further, the MBS, the MBS service, and the MBS session, which are terms used in the embodiment of the present application, can also be terms having the same meaning as the MBMS, the MBMS service, and the MBMS session described in Non-Patent Literature 4 and the like. Further, in the embodiment of the present application, the MRB can also refer to a radio bearer established in the UE 122 for the MBS reception. Further, the MRB can also refer to a radio bearer established in the gNB 108 for the MBS transmission.

[0225] Figure 12 is a diagram illustrating one example of a configuration of an SDAP sublayer representing the embodiment of the present application. Figure 12 (A) of is an example in which an RLC-SAP (RLC-Service Access Point: RLC service access point) exists between the SDAP sublayer and the RLC sublayer. In Figure 12 In the example of (A) of, the data of the MBS session received in the UE 122 via the MRB can be delivered to the SDAP entity as an RLC SDU in the RLC entity of the MRB described above. Further, in Figure 12In the example of (A) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In the example of (A) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU.

[0226] Figure 12 (B) of FIG. 10 is an example in which the PDCP-SAP (PDCP-Service Access Point) exists between the SDAP sublayer and the PDCP sublayer. In (B) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In (B) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU. Figure 12 In the example of (B) of FIG. 10, the data of the MBS session received via the MRB in the UE 122 can be delivered to the PDCP entity of the MRB as a RLC SDU in the RLC entity of the MRB. The PDCP entity to which the RLC SDU is delivered can not perform any processing on the delivered RLC SDU, i.e., a PDCP PDU, and deliver it to the SDAP entity as a PDCP SDU as it is. Further, in the example of (B) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In the example of (B) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU. Figure 12 In the example of (B) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In the example of (B) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU. Figure 12 In the example of (B) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In the example of (B) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU. Figure 12 In the example of (B) of FIG. 10, the PDCP entity of the MRB can not perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU as it is. In the example of (B) of FIG. 10, the PDCP entity of the MRB can perform any processing on the PDCP SDU delivered thereto, and deliver the PDCP SDU to the RLC entity of the MRB as a PDCP PDU.

[0227] Note that the association can also be referred to as bundle, and can also be referred to as other similar terms. Further, the establishing correspondence can also be referred to as map, and can also be referred to as other similar terms.

[0228] Here, the relationship of the MRB, the SDAP entity, and the PDU session of the embodiment of the present application is explained. One or more DRBs can be associated with the SDAP entity associated with the MRB. That is, the SDAP entity can be established and / or configured commonly for the MBS service and the unicast service. Further, one PDU session can correspond to the MBS service and the unicast service, provide the MBS service and / or the unicast service. Further, one SDAP entity common to the MBS service and the unicast service can also be established and / or configured for one PDU session. Further, the SDAP entity associated with the MRB can also not be associated with the DRB for the MBS service and the unicast service. Further, one SDAP entity for the MBS service (for the MRB) and one SDAP entity for the unicast service (for the DRB) can also be established and / or configured for one PDU session, respectively. Further, the PDU session for the MBS service can also exist separately from the PDU session for the unicast service. Further, one SDAP entity for the MBS service can also be established and / or configured for the PDU session for the MBS service. Further, the SDAP entity can also not be established and / or configured in the PDU session for the MBS service. Further, at least one MRB and / or at least one DRB can also be established in the PDU session. Further, the establishment and / or configuration of the SDAP entity associated with the MRB can be when the UE 122 transitions from the RRC_IDLE state and / or the RRC_INACTIVE state to the RRC_CONNECTED state. Further, the establishment and / or configuration of the SDAP entity associated with the MRB can also be when the UE 122 is in the RRC_INACTIVE state and / or the RRC_CONNECTED state.

[0229] Figure 13 is a diagram representing one example of a flow of a procedure for the configuration of the MBS reception in NR of the embodiment of the present application. Note that, in the present embodiment, the parameters can refer to the fields and / or information elements in ASN.1.

[0230] As Figure 13As illustrated, the processing section 602 of the gNB 108 can also generate a SIB (System Information Block) as one of the RRC messages, for broadcasting information required for acquisition of control information related to the MBS transmission, and transmit to the UE 122 via the transmitting section 600. The receiving section 500 of the UE 122 receives the above-described SIB. (Step S900) Note that the above-described SIB can also be transmitted via a BCCH logical channel. Further, the information required for acquisition of control information related to the above-described MBS transmission can also refer to information related to a MCCH (Multicast Control Channel) logical channel. The above-described MCCH can refer to a point-to-multipoint downlink channel for transmitting, from the gNB 108 to the UE 122, MBS control information for one or a plurality of MTCH (Multicast Traffic Channel) logical channels. Further, the above-described MTCH can refer to a point-to-multipoint downlink channel for transmitting, from the gNB 108 to the UE 122, data of the MBS. The above-described MTCH can also be used only by the UE 122 in a case where the UE 122 receives the MBMS. Note that the above-described MCCH can also be referred to as an MBS-MCCH, an NR-MCCH, or other names. Further, the above-described MTCH can also be referred to as an MBS-MTCH, an NR-MTCH, or other names. Further, the MBS transmission can also be performed via an MRB. Further, the above-described MCCH can also be mapped to a MCH (Multicast Channel) as a downlink transport channel, and can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel. Further, the above-described MTCH can also be mapped to a MCH (Multicast Channel) as a downlink transport channel, and can also be mapped to a DL-SCH (Downlink Shared Channel) as a downlink transport channel.

[0231] The above-described SIB can include, for example, some or all of a parameter indicating a period in which the content of the MCCH can be changed, a parameter related to a transmission (retransmission) time interval of the MCCH, a parameter indicating an offset of a radio frame in which the MCCH is scheduled, a parameter indicating a subframe in which the MCCH is scheduled, a parameter indicating a period of the subframe in which the MCCH is scheduled, and the like. Note that the above-described parameter related to the transmission (retransmission) time interval of the MCCH can also be expressed by a number of radio frames.

[0232] Next, the processing section of the gNB 108 can generate the RRC message transmitted in the MCCH described above, and transmit it through the transmitting section 600. The receiving section 500 of the UE 122 can receive the RRC message transmitted in the MCCH described above, based on the setting of the SIB described above. A dedicated RNTI (Radio Network Temporary Identifier) for identifying the transmission of the MCCH described above can be used in the transmission of the MCCH described above. (Step S1302) In the embodiment of the present application, the RRC message transmitted in the MCCH described above is described using the message name "MBS-ConfigInfo-Message", but it can be another message name.

[0233] The MBS configuration information described above can include control information applicable to MBS reception. For example, the MBS configuration information can include some or all of the fields such as a parameter related to information of an MBS session, a parameter indicating an RNTI identifying a multicast group (MTCH destined for a specific group), a parameter related to DRX information for an MTCH, a parameter indicating a list of neighboring cells providing the same MBS, and the like. The parameter related to information of an MBS session described above can include some or all of the parameters such as a parameter indicating a TMGI (Temporary Mobile Group Identity) described in Non-Patent Literature 15 as an identifier identifying an MBS (or MBMS) bearer service, a parameter indicating a Session ID described in Non-Patent Literature 15 or the like as an identifier of an MBS (or MBMS) session, a parameter indicating a PDU session to which the MBS (or MBMS) bearer service described above and / or the MBS session described above belong, a parameter indicating a QoS flow for the MBS (or MBMS) bearer service described above and / or the MBS session described above, and the like.

[0234] Note that some or all of the parameters included in the MBS configuration information described above can be included in the form of a list. The parameters included in the form of a list described above can exist with respect to each MTCH (or each MBS service) in the cell to which the transmitted MCCH belongs. In addition, the parameter indicating a list of neighboring cells providing the same MBS described above can include a parameter indicating a list of neighboring cells providing the same MBS via an MTCH and / or an MRB, and can include a parameter indicating a list of neighboring cells providing the same MBS via unicast and / or a DTCH and / or a DRB. In addition, the parameter indicating a PDU session described above can refer to a PDU session ID described in Non-Patent Literature 2 or the like. In addition, the parameter indicating a PDU session described above and / or the parameter indicating a QoS flow can be included in a parameter indicating an SDAP configuration.

[0235] The processing section 502 of the UE 122 can perform MRB establishment processing for starting reception of an MBS session of interest (step S1304). The MRB establishment processing can be initiated, for example, at the start of the MBS session, when the UE 122 enters a cell that provides an MBS service of interest via an MRB, when the UE 122 has an interest in the MBS service, when the restriction of the UE capability that suppresses reception of the MBS service is removed, or the like. The MRB establishment processing can be performed when the UE 122 is in the RRC_IDLE state, or can be performed when the UE 122 is in the RRC_INACTIVE state, or can be performed when the UE 122 is in the RRC_CONNECTED state. The processing section 502 of the UE 122 can also perform some or all of the following (A) to (G) when performing the MRB establishment processing. Note that the (A) processing can be performed when the UE 122 is in the RRC_CONNECTED state and / or the RRC_INACTIVE state. Note that the (F) processing can be performed when the UE 122 is in the RRC_CONNECTED state, or can be performed when the UE 122 is in the RRC_CONNECTED state and / or the RRC_INACTIVE state. Further, the (F) processing can also be performed when the UE 122 transitions from the RRC_IDLE state and / or the RRC_INACTIVE state to the RRC_CONNECTED state.

[0236] (A) In a case where there is no SDAP entity in a PDU session corresponding to a parameter indicating a PDU session included in the MBS configuration, an SDAP entity is established and / or configured.

[0237] (B) A PDCP entity is established in accordance with a default configuration related to MRB establishment.

[0238] (C) An RLC entity is established in accordance with a default configuration related to MRB establishment.

[0239] (D) A MTCH logical channel to be applied to the MRB to be established is configured, and a MAC entity is instructed so as to be able to receive the MBS session intended to be received.

[0240] (E) A physical layer is configured for the MRB to be established, based on the MBS configuration received above.

[0241] (F) An SDAP entity is associated with the established MRB.

[0242] (G) Establishment of the MRB is notified by notifying the upper layer of information including some or all of a TMGI, a session ID, a PDU session ID, a QoS flow corresponding to the established MRB.

[0243] The processing section 502 of the UE 122 receives the MBS session via the established MRB in accordance with the PTM configuration message described above (step S1306). Also, before receiving the MBS session, the processing section 502 of the UE 122 can generate an RRC message for notifying the gNB 108 of the reception of the MBS service via the MRB or the interest in the reception of the MBS service and transmit the RRC message to the eNB 102 (not shown) via the transmitting section 504. Note that, in the embodiment of the present application, the RRC message for notifying the gNB 108 of the reception of the MBS service via the MRB or the interest in the reception of the MBS service is described using the message name "MBS Interest Indication", but another message name can be used. The MBS Interest Indication message can also include information on whether the reception of the MBS service is prioritized over other unicast reception. Further, the MBS Interest Indication message can include information on whether the same MBS service is received via the DTCH and / or the DRB in the case where the UE 122 moves to a cell capable of receiving the same MBS service via the DTCH and / or the DRB, although the MBS service cannot be received via the MTCH and / or the MRB in the cell capable of receiving the MBS service via the MTCH and / or the MRB. Further, the MBS Interest Indication message can be transmitted when the UE 122 transitions to the RRC_CONNECTED state after receiving the SIB described in step S1300 or after the transition to the RRC_CONNECTED state. Further, the MBS Interest Indication message can be transmitted in the case where the SIB described in step S1300 is received at the time of handover, in the case where the SIB described in step S1300 is received at the time of reestablishment of the RRC connection, and in the case where the SIB described in step S1300 is received at the time of transition from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0244] The processing section 502 of the UE 122 can also perform MRB release processing to stop reception of the MBMS session (step S1308). The MRB release processing can be initiated, for example, when the MBS session being received is stopped, when leaving a cell in which the MRB is established, when leaving a cell in which the MBS service can be received using the MRB, when losing interest in the MBS service, when reception of the MBS service is suppressed due to a limitation of the UE capability, and so on. The MRB release processing can be performed when the UE 122 is in the RRC_IDLE state, can be performed when the UE 122 is in the RRC_INACTIVE state, and can be performed when the UE 122 is in the RRC_CONNECTED state. The processing section 502 of the UE 122 can also perform some or all of the following (A) to (D) when performing the MRB release processing. Note that the following (D) processing can be performed only when the UE 122 is in the RRC_CONNECTED state and / or the RRC_INACTIVE state.

[0245] (A) Release the PDCP entity of the MRB to be released.

[0246] (B) Release the RLC entity and the associated MAC and physical layer settings of the MRB to be released.

[0247] (C) Notify the release of the MRB by notifying the upper layer of information including some or all of the TMGI, the session ID, the PDU session ID, and the QoS flow corresponding to the released MRB.

[0248] (D) Release the SDAP entity that does not have the SDAP entity associated with the MRB and / or the DRB established, with respect to the SDAP entity.

[0249] Note that, in the embodiment of the present application, when the UE 122 receives the message relating to the reconfiguration of the RRC connection and establishes the DRB, that is, in the case where the DRB identifier included in the message relating to the reconfiguration of the RRC connection described above is not present in the configuration of the UE 122, the processing section 502 of the UE 122 notifies the upper layer that the user plane resource for the PDU session corresponding to the field indicated by the pdu-session described above is established, on the basis of the presence of the SDAP entity for the PDU session corresponding to the field indicated by the pdu-session described above, and the DRB established or to be established is the first DRB for the SDAP entity described above and / or the PDU session described above. Note that the case of "the presence of the SDAP entity for the PDU session corresponding to the field indicated by the pdu-session described above, and the DRB established or to be established is the first DRB for the SDAP entity described above and / or the PDU session described above" described above can mean the case where the SDAP entity described above is the SDAP entity established at the time of establishment of the MRB, and the first DRB for the SDAP entity described above and / or the PDU session described above is to be established or has been established.

[0250] Further, in the embodiment of the present application, it can also be the case that, after the UE 122 receives the message relating to the reconfiguration of the RRC connection and performs the processing relating to the configuration of the radio bearer, the user plane resource for the SDAP entity described above that does not have the associated DRB established is released on the basis of the presence of the SDAP entity described above that does not have the associated DRB established in the SDAP entity. Further, in the embodiment of the present application, it can also be the case that, after the UE 122 receives the message relating to the reconfiguration of the RRC connection and performs the processing relating to the configuration of the radio bearer, the SDAP entity described above that does not have the associated DRB and / or MRB established is released on the basis of the presence of the SDAP entity described above that does not have the associated DRB and / or MRB established in the SDAP entity.

[0251] Thus, in the embodiment of the present application, the UE 122 can efficiently receive the MBS using NR.

[0252] The radio bearers described above can each be the DRB, the SRB, or the DRB and the SRB.

[0253] Further, in the above description, the expressions "associated with", "corresponding to", "associated with", and the like can be replaced with each other.

[0254] Moreover, in the example of each process or the example of the flow of each process in the above description, one part or all of the steps can not be performed. Furthermore, in the example of each process or the example of the flow of each process in the above description, the order of the steps can be different. Furthermore, in the example of each process or the example of the flow of each process in the above description, one part or all of the processes in each step can not be performed. Furthermore, in the example of each process or the example of the flow of each process in the above description, the order of the processes in each step can be different. Furthermore, in the above description, “performing B on the basis of A” can be changed to “performing B”. That is, “performing B” can be performed independently of “A”.

[0255] Note that, in the above description, “A can be changed to B” includes the meaning that B is changed to A in addition to A being changed to B. Furthermore, in the above description, in a case where “C can be D” and “C can be E” are described, a case where “D can be E” can be included. Furthermore, in the above description, in a case where “F can be G” and “G can be H” are described, a case where “F can be H” can be included.

[0256] Furthermore, in the above description, in a case where a condition of “A” and a condition of “B” are opposite conditions, the condition of “B” can be expressed as an “other” condition of the condition of “A”.

[0257] Hereinafter, various schemes of a terminal device of an embodiment of the present application will be described.

[0258] (1) One embodiment of the present application is a terminal device that performs communication with a base station device, the terminal device including: a reception section that receives, from the base station device, an RRC message including configuration information of a multicast / broadcast service (MBS); and a processing section, the configuration information of the MBS including MBS session information, the MBS session information including PDU session information, the processing section performing processing of establishing a radio bearer for MBS, notifying one part or all of the MBS session information to an upper layer, based on the terminal device starting reception of the MBS session.

[0259] (2) The terminal device according to (1), wherein the processing section further performs processing of establishing an SDAP entity for the PDU session, based on the terminal device starting reception of the MBS session, in a case where the SDAP entity does not exist.

[0260] (3) The terminal device according to (1) or (2), wherein the establishment of the radio bearer for MBS includes one part or all of establishment of a PDCP entity, establishment of an RLC entity, configuration of a logical channel, and configuration of a physical layer.

[0261] (4) One embodiment of the present application is a method of a terminal device that communicates with a base station device, in which an RRC message including multicast / broadcast service (MBS) configuration information is received from the base station device, the MBS configuration information includes MBS session information, the MBS session information includes PDU session information, an MBS radio bearer is established based on the terminal device starting reception of the MBS session, and some or all of the MBS session information is notified to an upper layer.

[0262] (5) The method according to (4), in which, in the method of the terminal device, an SDAP entity is further established based on the terminal device starting reception of the MBS session, in the absence of the SDAP entity for the PDU session.

[0263] (6) The method according to (4) or (5), in which the establishment of the MBS radio bearer includes some or all of establishment of a PDCP entity, establishment of an RLC entity, configuration of a logical channel, and configuration of a physical layer.

[0264] A program working in the device of one aspect of the present application can be a program that controls a Central Processing Unit (CPU: Central Processing Unit) or the like so as to realize the functions of the above-described embodiments of one aspect of the present application to cause a computer to function. The program or information processed by the program is temporarily read into a volatile memory such as a Random Access Memory (RAM: Random Access Memory) or stored in a non-volatile memory such as a Flash Memory, a Hard Disk Drive (HDD: Hard Disk Drive), and read out, modified / written by a CPU as necessary while processing is performed.

[0265] Note that a part of the device in the above-described embodiments can be realized by a computer. In this case, a program for realizing the control function can be recorded in a computer-readable recording medium, and realized by reading the program recorded in the recording medium into a computer system and executing. The "computer system" herein refers to a computer system built into the device, and is configured to include an operating system, hardware such as peripherals. Further, the "computer-readable recording medium" can be any one of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

[0266] Moreover, the "computer-readable recording medium" can include a medium that temporarily stores the program dynamically for a short time like a communication line in the case where the program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that stores the program for a fixed period of time like a volatile memory inside a computer system that functions as a server or a client in this case. Furthermore, the program can be a program for realizing a part of the functions described above, and can also be a program that realizes the functions described above by being combined with a program already recorded in the computer system.

[0267] Furthermore, each functional block or each characteristic of the device used in the above-described embodiments can be realized or implemented by a circuit, typically by an integrated circuit or a plurality of integrated circuits. A circuit designed in such a manner as to execute the functions described in this specification can include a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, a discrete hardware component, or a combination thereof. The general-purpose processor can be a microprocessor, and alternatively a processor can be a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described above can be configured of a digital circuit or can be configured of an analog circuit. Furthermore, in the case where a technology replacing the integrated circuit appears as a result of advancement of semiconductor technology, an integrated circuit based on this technology can also be used.

[0268] Note that the present application is not limited to the above-described embodiments. In the embodiments, one example of the device is described, but the present application is not limited to this, and can be applied to a fixed or non-portable electronic device, such as a terminal device or a communication device, provided indoors or outdoors, such as an AV device, a kitchen device, a cleaning / washing device, an air conditioning device, an office device, a vending machine, and other living devices.

[0269] The embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiments, and design changes and the like within a range not deviating from the gist of the present application are included. Furthermore, one aspect of the present application can be changed in various ways within the range shown in the technical means, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present application. Furthermore, a configuration obtained by replacing elements that have the same effects as the elements described in the above-described embodiments with each other is also included.

[0270] Industrial Applicability

[0271] One aspect of the present application can be used in a communication system, a communication device (for example, a portable telephone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (for example, a communication chip), a program, or the like, for example.

[0272] Reference Signs

[0273] 100 E-UTRA

[0274] 102 eNB

[0275] 104 EPC

[0276] 106 NR

[0277] 108 gNB

[0278] 110 5GC

[0279] 112, 114, 116, 118, 120, 124 Interface

[0280] 122 UE

[0281] 200, 300 PHY

[0282] 202, 302 MAC

[0283] 204, 304 RLC

[0284] 206, 306 PDCP

[0285] 208, 308 RRC

[0286] 310 SDAP

[0287] 210, 312 NAS

[0288] 500, 604 Receiving Section

[0289] 502, 602 Processing Section

[0290] 504, 600 Transmitting Section

Claims

1. A terminal device for communicating with a base station device, the terminal device comprising: The receiving unit receives an RRC message including setting information for the Multicast Broadcast Service (MBS) from the base station device; and the processing unit, wherein... The MBS configuration information includes MBS session information. The processing unit establishes an MRB to receive the MBS session, and When the MRB is established, the processing unit establishes a PDCP entity for the MRB, and If the SDAP entity used for the MBS session does not exist, the SDAP entity is created.

2. A method for a terminal device to communicate with a base station device, wherein, The method of receiving an RRC message including configuration information of Multicast Broadcast Service (MBS) from the base station device includes: The MBS configuration information includes MBS session information, and Establish an MRB to receive the MBS session, wherein When the MRB is established, the terminal device establishes a PDCP entity for the MRB, and If the SDAP entity used for the MBS session does not exist, the SDAP entity is created.

Images