Terminal device, communication method, and base station device

Abstract

To provide a technique related to a terminal device and a communication method which can reduce complexity of protocol processing and efficiently perform communication.SOLUTION: A terminal device according to one embodiment of the present invention receives an RRC re-setting message including DRB setting, performs the first determination for determining that all of conditions that a DRB identifier included in the DRB setting does not exist in the current setting of the terminal device, SDAP setting is included in the DRB setting and an SDAP entity corresponding to a PDU session indicated by a PDU session information element included in the SDAP setting does not exist are satisfied when processing an RRC message, establishes the SDAP entity on the basis of the first determination, and notifies that a user-place resource to the PDU session information element is established in the upper layer on the basis of the second determination for determining that the first determination and the SDAP entity do not exist before receiving the RRC re-setting message.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a communication method, and a base station device. [Background technology]

[0002] A radio access method and radio network for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)"), and a core network (hereinafter referred to as "Evolved Packet Core (EPC)") are being considered by the 3rd Generation Partnership Project (3GPP).

[0003] Furthermore, 3GPP (registered trademark) is conducting technical studies and formulating standards for LTE-Advanced Pro, an extension of LTE, and NR (New Radio technology), a new radio access technology, as radio access methods and radio network technologies for fifth-generation cellular systems (Non-Patent Document 1). 5GC (5th Generation Core Network), a core network for fifth-generation cellular systems, is also being studied (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP RP-170855, “Work Item on New Radio (NR) Access Technology” [Non-patent document 2] 3GPP TS 23.501, “System Architecture for the 5G System; Stage 2” [Non-patent document 3] 3GPP TS 36.300, “Evolved Universal Terestrial Radio Access (E-UTRA) and Evolved Universal Terestrial Radio Access Network (E-UTRAN);Overall description; Stage 2”

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

Non-licensed Document 7

Non-licensed Document 8

Non-licensed literature 9

Non-Patent Document 10

Non-Patent Document 11

Non-Patent Document 12

Non-Patent Document 13

Non-Patent Document 14

Non-Patent Document 15

Non-Patent Document 16

Non-Patent Document 17

Summary of the Invention

[0005] As part of the technical studies for NR, a radio access layer protocol is being considered that will manage Quality of Service (QoS) between the IP (Internet Protocol) layer and higher layers and the NR radio access layer.

[0006] However, if QoS management is not performed correctly between the upper layer and the radio access layer, there is a problem that communication between the base station apparatus and the terminal apparatus cannot be performed efficiently.

[0007] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and one of its objects is to provide a terminal device, a communication method, and a base station device that can efficiently communicate with a base station device. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, one aspect of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC (Radio Resource Control) reconfiguration message including a DRB (Data Radio Bearer) setting from the base station device; and a processing unit, wherein, when processing the RRC reconfiguration message received by the receiving unit, the processing unit (a) determines that a DRB identifier included in the DRB setting does not exist in the current setting of the terminal device, (b) determines that the DRB setting includes an SDAP (Service Data Adaptation Protocol) setting, and (c) determines that an SDAP entity corresponding to a PDU session indicated by a PDU (Protocol Data Unit) session information element included in the SDAP setting does not exist, and if it determines that (a), (b), and (c) are satisfied, establishes an SDAP entity, and further, if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, notifies a higher layer that user-plane resources for the PDU session information element have been established.

[0009] One aspect of the present invention is a communication method for a terminal device communicating with a base station device, which receives an RRC (Radio Resource Control) reconfiguration message including a DRB (Data Radio Bearer) setting from the base station device, and when processing the received RRC reconfiguration message, (a) determines that a DRB identifier included in the DRB setting does not exist in the current setting of the terminal device, (b) determines that the DRB setting includes an SDAP (Service Data Adaptation Protocol) setting, and (c) determines that an SDAP entity corresponding to a PDU session indicated by a PDU (Protocol Data Unit) session information element included in the SDAP setting does not exist, and if it is determined that (a), (b), and (c) are satisfied, establishes an SDAP entity, and further, if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, notifies a higher layer that user-plane resources for the PDU session information element have been established.

[0010] One aspect of the present invention is a base station device that communicates with a terminal device, the base station device comprising: a transmitter that transmits an RRC (Radio Resource Control) reconfiguration message including a DRB (Data Radio Bearer) configuration to the terminal device; and a processor that causes the terminal device to perform processing by including the DRB configuration in the RRC reconfiguration message, the processor including the DRB configuration in the RRC reconfiguration message, the processor including the DRB configuration in the RRC reconfiguration message, the processor including the processing ... a base station device including a process for determining that an SDAP entity corresponding to a PDU session indicated by an SDAP session information element does not exist, and if it is determined that (a), (b), and (c) are satisfied, establishing an SDAP entity; and if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, notifying a higher layer that user-plane resources for the PDU session information element have been established.

[0011] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

[0012] According to one aspect of the present invention, a terminal device can reduce the complexity of protocol processing and perform communication efficiently. [Brief explanation of the drawings]

[0013] [Figure 1]1 is a schematic diagram of a communication system according to each embodiment of the present invention. [Figure 2] 3A and 3B are protocol stack diagrams of UP and CP of a terminal device and a base station device in E-UTRA in each embodiment of the present invention. [Figure 3] A protocol stack diagram of the UP and CP of a terminal device and a base station device in NR in each embodiment of the present invention. [Figure 4] FIG. 2 is a diagram showing an example of a flow of an RRC reconfiguration procedure in each embodiment of the present invention. [Figure 5] FIG. 2 is a block diagram showing the configuration of a terminal device according to each embodiment of the present invention. [Figure 6] FIG. 2 is a block diagram showing the configuration of a base station device according to each embodiment of the present invention. [Figure 7] 1A and 1B are diagrams showing examples of information related to radio bearer configuration and ASN.1 (Abstract Syntax Notation One) description of the information in each embodiment of the present invention. [Figure 8] 1 shows an example of a processing method according to an embodiment of the present invention. [Figure 9] 10 shows another example of a processing method according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0015] LTE (and LTE-A Pro) and NR may be defined as different RATs. NR may also be defined as a technology included in LTE. LTE may also be defined as a technology included in NR. LTE, which is connectable to NR via Multi RAT Dual connectivity (MR-DC), as described in Non-Patent Document 7, may be distinguished from conventional LTE. This embodiment may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR are used, but the present embodiment may also be applied to other technologies using other terms. The term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

[0016] FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.

[0017] E-UTRA 100 is a radio access technology described in Non-Patent Document 3 and the like, and is composed of cell groups (CGs) consisting of one or more frequency bands. eNB (E-UTRAN Node B) 102 is an E-UTRA base station device. EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14 and the like, and is designed as a core network for E-UTRA. Interface 112 is an interface between eNB 102 and EPC 104, and includes a control plane (CP) through which control signals pass and a user plane (UP) through which user data passes.

[0018] NR 106 is a radio access technology described in Non-Patent Document 9 and the like, and is composed of cell groups (CGs) consisting of one or more frequency bands. gNB (g Node B) 108 is an NR base station device. 5GC 110 is a core network described in Non-Patent Document 2 and the like, and is designed as an NR core network, but may also be used as an E-UTRA core network with the function of connecting to 5CG. Hereinafter, E-UTRA may include E-UTRA with the function of connecting to 5CG.

[0019] Interface 114 is an interface between eNB102 and 5GC110, interface 116 is an interface between gNB108 and 5GC110, interface 118 is an interface between gNB108 and EPC104, interface 120 is an interface between eNB102 and gNB108, and interface 124 is an interface between EPC104 and 5GC110. Interfaces 114, 116, 118, 120, and 124 are interfaces that pass only CP, only UP, or both CP and UP. Furthermore, interfaces 114, 116, 118, 120, and 124 may not exist depending on the communication system provided by the communication carrier.

[0020] The UE 122 is a terminal device that supports NR or supports both E-UTRA and NR.

[0021] FIG. 2 is a diagram showing protocol stacks of UP and CP of a terminal device and a base station device in the E-UTRA radio access layer in each embodiment of the present invention.

[0022] FIG. 2A is a diagram of a protocol stack of the UP used when the UE 122 communicates with the eNB 102 in the E-UTRA 100.

[0023] The PHY (Physical layer) 200 is a wireless physical layer that provides transmission services to an upper layer using a physical channel. The PHY 200 is connected to a higher layer, a Medium Access Control (MAC) layer 202 (described later), via a transport channel. Data moves between the MAC 202 and the PHY 200 via the transport channel. Data is transmitted and received between the PHYs of the UE 122 and the eNB 102 via the wireless physical channel.

[0024] The MAC 202 is a medium access control layer that maps various logical channels to various transport channels. The MAC 202 is connected to the higher-level RLC (Radio Link Control layer) 204 (described later) via a logical channel. Logical channels are broadly categorized according to the type of information transmitted, into control channels that transmit control information and traffic channels that transmit user information. The MAC 202 has functions such as controlling the PHY 200 to perform discontinuous transmission / reception (DRX / DTX), executing random access procedures, reporting transmission power information, and performing HARQ control (Non-Patent Document 7).

[0025] The RLC 204 is a radio link control layer that segments data received from the later-described upper PDCP (Packet Data Convergence Protocol Layer) 206 and adjusts the data size so that the lower layer can transmit the data appropriately. The RLC 200 also has a function to guarantee the QoS (Quality of Service) required by each data. That is, the RLC 204 has a function such as data retransmission control (Non-Patent Document 6).

[0026] The PDCP 206 is a packet data convergence protocol layer for efficiently transmitting IP packets, which are user data, over wireless sections. The PDCP 206 may have a header compression function for compressing unnecessary control information. The PDCP 206 may also have a data encryption function (see Non-Patent Document 5).

[0027] The data processed by the MAC 202, RLC 204, and PDCP 206 are called MAC PDUs (Protocol Data Units), RLC PDUs, and PDCP PDUs, respectively. Data passed from higher layers to the MAC 202, RLC 204, and PDCP 206, or data passed to higher layers, are called MAC SDUs (Service Data Units), RLC SDUs, and PDCP SDUs, respectively.

[0028] FIG. 2B is a diagram of a protocol stack of a CP used when a UE 122 communicates with an eNB 102 in E-UTRA 100.

[0029] The CP protocol stack includes a PHY 200, a MAC 202, an RLC 204, a PDCP 206, and an RRC (Radio Resource Control) layer 208. The RRC 208 is a radio link control layer that configures and reconfigures radio bearers (RBs) and controls logical channels, transport channels, and physical channels. The RBs may be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs), and the SRBs may be used as paths for transmitting RRC messages, which are control information. The DRBs may be used as paths for transmitting user data. Configuration of each RB may be performed between the eNB 102 and the RRC 208 of the UE 122 (see Non-Patent Document 4).

[0030] The above-described classification of functions into MAC 202, RLC 204, PDCP 206, and RRC 208 is an example, and some or all of the functions may not be implemented. Also, some or all of the functions of each layer may be included in another layer.

[0031] The IP layer, and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, and application layer above the IP layer are upper layers of the PDCP layer (not shown). The RRC layer and NAS (non-access strat) layer are also upper layers of the SDAP layer (not shown). In other words, the PDCP layer is a lower layer than the RRC layer, NAS layer, IP layer, and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, and application layer above the IP layer.

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

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

[0034] The PHY (Physical layer) 300 is a radio physical layer of NR and may provide transmission services to higher layers using a physical channel. The PHY 300 may be connected to a higher-level MAC (Medium Access Control layer) 302 (described later) via a transport channel. Data may be transferred between the MAC 302 and the PHY 300 via the transport channel. Data may be transmitted and received between the PHYs of the UE 122 and the gNB 108 via a radio physical channel.

[0035] The MAC 302 is a medium access control layer that maps various logical channels to various transport channels. The MAC 302 may be connected to a higher-level RLC (Radio Link Control) layer 304 (described later) via a logical channel. Logical channels are broadly classified according to the type of information transmitted, and may be divided into control channels that transmit control information and traffic channels that transmit user information. The MAC 302 may have functions such as controlling the PHY 300 to perform discontinuous transmission / reception (DRX / DTX), executing a random access procedure, reporting transmission power information, and performing HARQ control (Non-Patent Document 13).

[0036] The RLC 304 is a radio link control layer that segments data received from the later-described upper PDCP (Packet Data Convergence Protocol Layer) 206 and adjusts the data size so that the lower layer can transmit the data appropriately. The RLC 304 may also have a function to guarantee the QoS (Quality of Service) required by each data. In other words, the RLC 304 may have a function such as data retransmission control (Non-Patent Document 12).

[0037] PDCP 306 is a packet data convergence protocol layer that efficiently transmits IP packets, which are user data, over wireless sections. PDCP 306 may have a header compression function that compresses unnecessary control information. PDCP 306 may also have a data encryption function (Non-Patent Document 11).

[0038] The SDAP (Service Data Adaptation Protocol) 310 is a service data adaptation protocol layer (SDAP) that maps downlink QoS flows sent from the core network via a base station to a terminal device to a DRB, and maps uplink QoS flows sent from the terminal device to a core network via a base station to a DRB, and stores mapping rule information (see Non-Patent Document 16). When the terminal device receives an SDAP SDU along with QoS flow information from a higher layer, it assigns the SDAP SDU to the corresponding DRB based on the stored QoS flow-to-DRB mapping rule. If no QoS flow-to-DRB mapping rule is stored, the SDAP SDU may be assigned to a default radio bearer (default DRB). A QoS flow consists of one or more service data flows (SDFs) that are processed according to the same QoS policy (see Non-Patent Document 2). The SDAP may also have a reflective QoS function that maps uplink QoS flows to DRBs based on downlink QoS flow information. Furthermore, if the rules for associating QoS flows with DRBs are changed, an End Marker DPU may be created and sent to the previous DRB to ensure in-sequence delivery of SDAP SDUs (see Non-Patent Document 2 and Non-Patent Document 16).

[0039] The end marker PDU is an SDAP control PDU described in Non-Patent Document 16, which is used by the SDAP entity of the UE to notify that the mapping between the QoS flow corresponding to the QoS flow identifier contained in the QoS flow identifier field of this end marker PDU and the radio bearer on which this end marker PDU was transmitted has ended.

[0040] The IP layer, and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, and application layer above the IP layer are upper layers of the SDAP layer (not shown). The RRC layer and NAS (Non Access Stratum) layer are also upper layers of the SDAP layer (not shown). The NAS layer associates service data flows with QoS flows. In other words, the SDAP layer is a lower layer than the RRC layer, NAS layer, IP layer, and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, and application layer above the IP layer.

[0041] The data processed in MAC 302, RLC 304, PDCP 306, and SDAP 310 may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, data passed from an upper layer to MAC 302, RLC 204, and PDCP 206, or data passed to an upper layer, may be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.

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

[0043] The CP protocol stack includes a PHY 300, a MAC 302, an RLC 304, a PDCP 306, and an RRC (Radio Resource Control layer) 308. The RRC 308 is a radio link control layer that configures and reconfigures radio bearers (RBs) and controls logical channels, transport channels, and physical channels. RBs may be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs), and the SRBs may be used as paths for transmitting RRC messages, which are control information. The DRBs may be used as paths for transmitting user data. RBs may be configured between the gNB 108 and the RRC 308 of the UE 122. The portion of the RBs consisting of the RLC 304 and the MAC 302 may be referred to as an RLC bearer (Non-Patent Document 10).

[0044] The functional classification of MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308 described above is an example, and some or all of the functions may not be implemented. Furthermore, some or all of the functions of each layer may be included in another layer.

[0045] In each embodiment of the present invention, in order to distinguish between E-UTRA protocols and NR protocols, MAC 202, RLC 204, PDCP 206, and RRC 208 may 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. MAC 302, RLC 304, PDCP 306, and RRC 308 may be referred to as NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Alternatively, they may be written with spaces, such as E-UTRA PDCP or LTE PDCP, or NR PDCP.

[0046] Also, as shown in FIG. 1, the eNB 102, the gNB 108, the EPC 104, and the 5GC 110 may be connected via interface 112, interface 116, interface 118, interface 120, and interface 114. Therefore, in order to support various communication systems, the RRC 208 in FIG. 2 may be replaced with the RRC 308 in FIG. 3. The PDCP 206 in FIG. 2 may be replaced with the PDCP 306 in FIG. 3. The RRC 308 in FIG. 3 may include the functions of the RRC 208 in FIG. 2. The PDCP 306 in FIG. 3 may be the PDCP 206 in FIG. 2. In E-UTRA 100, even when the UE 122 communicates with the eNB 102, NR PDCP may be used as the PDCP.

[0047] (Embodiment) An embodiment of the present invention will be described using Figures 1 to 9. In this embodiment of the present invention, when an SDAP entity is established, it notifies upper layers when a new PDU session is established that user plane resources for the PDU session have been established or configured.

[0048] 4 is a diagram showing an example of a flow of an RRC reconfiguration procedure in each embodiment of the present invention. Note that the RRC reconfiguration procedure may be an RRC connection reconfiguration procedure.

[0049] The RRC connection reconfiguration procedure is a procedure described in Non-Patent Document 4 that is used to establish, change, and release Radio Bearers (RBs) in LTE, change and release secondary cells, and perform other configurations, as well as to configure handovers and measurements. On the other hand, the RRC reconfiguration procedure is a procedure described in Non-Patent Document 10 that is used to establish, change, and release RBs in NR, change and release secondary cells, and perform other configurations, as well as to configure handovers (reconfiguration involving synchronization) and measurements. In the embodiments of the present invention, information included in each message in the RRC connection reconfiguration procedure for performing the above-mentioned configurations, such as the establishment, change, and release of RBs, change and release of secondary cells, handovers, and measurements, is referred to as configuration information. In addition, the configuration information is not limited to the above-mentioned configurations, and may be other configurations, and may be included in each message in another procedure, not limited to the RRC connection reconfiguration procedure.

[0050] Furthermore, the RRC connection reconfiguration procedure may be used in MR-DC (Multi-RAT Dual Connectivity) described in Non-Patent Document 8, particularly in EN-DC (E-UTRA-NR Dual Connectivity) (options 3 and 3a described in Non-Patent Document 17), which is MR-DC when the core network is EPC104 and the master node is eNB102 (also referred to as enhanced eNB102), NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) (options 7 and 7a described in Non-Patent Document 17), which is MR-DC when the core network is 5GC110 and the master node is eNB102, and E-UTRA / 5GC (option 5 described in Non-Patent Document 17), in which eNB102 (enhanced eNB) uses 5GC as the core network. In this case, the RRC connection reconfiguration procedure may include not only LTE (E-UTRA) configuration information but also NR configuration information described in Non-Patent Document 10. In this case, the RRC connection reconfiguration message may be transmitted from the eNB 102 to the UE 122 via the gNB 108.

[0051] Furthermore, the RRC reconfiguration procedure may be used in MR-DC, particularly in NE-DC (NR-E-UTRA Dual Connectivity) (Option 4 and Option 4a described in Non-Patent Document 17), which is MR-DC when the core network is 5GC 110 and the master node is gNB 108. In this case, the RRC reconfiguration procedure may include not only NR configuration information but also LTE (E-UTRA) configuration information described in Non-Patent Document 10. In this case, the RRC reconfiguration message may be transmitted from the gNB 108 to the UE 122 via the eNB 102.

[0052] In each embodiment of the present invention, in order to avoid complicating the explanation, the explanation will be given using the name of RRC reconfiguration procedure, and the explanation will be given using a gNB 108 as the base station device. Note that the names of architectures such as EN-DC, NGEN-DC, E-UTRA / 5GC, and NE-DC may be other names instead of the above.

[0053] In the RRC reconfiguration procedure, the UE 122 receives an RRC reconfiguration message (RRCReconfiguration) from the gNB 108 (step S400) and performs various configuration processes, such as radio bearer configuration and SDAP configuration, in accordance with the information included in the RRC reconfiguration message (step S402). After step S402, the UE 122 may send an RRC reconfiguration complete message (RRCReconfigurationComplete) or the like to the gNB 108 (not shown). Note that the RRC reconfiguration message may be rephrased as RRC reconfiguration, and the RRC reconfiguration complete message may be rephrased as RRC reconfiguration complete.

[0054] Fig. 5 is a block diagram showing the configuration of a terminal device (UE 122) in each embodiment of the present invention. To avoid complicating the explanation, Fig. 5 shows only the main components closely related to the present invention.

[0055] The UE 122 shown in Figure 5 comprises a receiving unit 500 that receives an RRC reconfiguration message, etc. from the gNB 108, and a processing unit 502 that performs processing according to configuration information, such as various information elements (IEs) and / or various fields and / or various conditions, contained in the received message.

[0056] Fig. 6 is a block diagram showing the configuration of a base station device (gNB 108) in each embodiment of the present invention. Note that, to avoid complicating the explanation, Fig. 6 shows only the main components closely related to the present invention.

[0057] The gNB 108 shown in Fig. 6 includes a transmitter 600 that transmits an RRC reconfiguration message or the like to the UE 122, and a processor 602 that creates an RRC reconfiguration message including configuration information such as various information elements (IEs), various fields, and / or various conditions, and transmits the message to the UE 122, thereby causing the processor 502 of the UE 122 to perform processing. Note that the configuration shown in Fig. 6 may also be applied to the eNB 102. When applied to the eNB 102, the message transmitted from the transmitter 600 to the UE 122 may be an RRC connection reconfiguration message.

[0058] FIG. 7 shows an example of an ASN.1 (Abstract Syntax Notation One) description representing information elements included in the RRC reconfiguration message shown in FIG. 4 in the first embodiment of the present invention. In 3GPP (registered trademark), RRC-related specifications (Non-Patent Document 4, Non-Patent Document 10) use ASN.1 to describe RRC-related messages and information elements (IEs). In the ASN.1 example shown in FIG. 7, "omitted" and "omitted" are not part of the ASN.1 notation and indicate that other information has been omitted. Note that information elements may be omitted even when "omitted" or "omitted" is not written. Note that the ASN.1 example shown in FIG. 7 does not strictly follow the ASN.1 notation method, but merely describes an example of parameters for RRC reconfiguration in the present invention, and other names and notations may be used. To avoid complication of explanation, the ASN.1 example shown in FIG. 7 only shows an example of main information closely related to the present invention.

[0059] In Figure 7, the information element represented by DRB-ToAddModList or DRBToAddMod may be a list of information indicating the setting of a DRB (data radio bearer) to be added or changed, and in embodiments of the present invention, it may be referred to as a radio bearer setting information element or a data radio bearer information element.

[0060] The information element represented by DRB-Identity in the radio bearer configuration information element is information on the DRB identifier of the DRB to be added or changed, and in the embodiment of the present invention, it may be referred to as a radio bearer identifier information element or a data radio bearer identifier information element. In the example of Figure 7, it is an integer value from 1 to 32, but it may also take another value. In the case of DC, the DRB identifier is unique within the scope of the UE 122.

[0061] The information element represented by cnAssociation among the radio bearer configuration information elements may be an information element indicating whether the EPC 104 or the 5GC 110 is used as the core network, and may be referred to as a core network association information element in the embodiment of the present invention. That is, when the UE 122 connects to the EPC, the DRB may be associated with the EPS bearer identifier information element (eps-BearerIdentity) in the cnAssociation or the EPS bearer identifier that is the value of the EPS bearer identifier information element, and when the UE 122 connects to the 5GC 110, the DRB may be associated with an SDAP entity configured according to a later-described SDAP configuration information element (sdap-Config), or with a later-described PDU session information element included in the SDAP configuration information element, or with a PDU session identifier that is the value of the PDU session information element, or with a PDU session indicated by the PDU session information element. That is, the information represented by cnAssociation may include an EPS bearer identifier information element (eps-BearerIdentity) when EPC104 is used in the core network, such as when EN-DC is used, and may also include an information element (sdap-Config) indicating SDAP configuration when core network 5GC110 is used, i.e., when EN-DC is not used.

[0062] The information element represented by sdap-Config may be information regarding the configuration or reconfiguration of an SDAP entity that determines how QoS flows and DRBs are mapped when the core network is 5GC110, and in embodiments of the present invention, it may be referred to as an SDAP configuration information element.

[0063] The field or information element indicated by pdu-session or PDU-SessionID included in the SDAP configuration information element may be the identifier of the PDU session described in Non-Patent Document 2 to which the QoS flow that is mapped to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer configuration information element that includes this SDAP configuration information element belongs, and may be referred to as the PDU session information element in some embodiments of the present invention. The value of the PDU session information element may be a non-negative integer.

[0064] The information element indicated by mappedQoS-FlowsToAdd included in the SDAP configuration information element may be information indicating a list of QoS flow identity (QFI) information elements (to be described later) of QoS flows that are to be mapped to or additionally mapped to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer configuration information element including this SDAP configuration information element, and may be referred to as an additional QoS flow information element in the embodiments of the present invention. The above-mentioned QoS flow may be the QoS flow of the PDU session indicated by the PDU session information element included in this SDAP configuration information element.

[0065] Furthermore, the information element indicated by mappedQoS-FlowsToRelease included in the SDAP configuration information element may be information indicating a list of QoS flow identity (QFI) information elements (to be described later) of QoS flows to be released from among the QoS flows that map to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer configuration information element that includes this SDAP configuration information element, and in the embodiments of the present invention, this may be rephrased as the QoS flow information element to be released. The above-mentioned QoS flow may be the QoS flow of the PDU session indicated by the PDU session information element included in this SDAP configuration information element.

[0066] The information element indicated by QFI may be a QoS flow identifier that uniquely identifies a QoS flow, as described in Non-Patent Document 2, and may be referred to as a QoS flow identifier information element in the embodiments of the present invention. The value of the QoS flow identifier information element may be a non-negative integer. The value of the QoS flow identifier information element may also be unique for a PDU session.

[0067] In addition, the SDAP setting information element may also include an uplink header information element indicating whether an uplink SDAP header is present in the uplink data transmitted via the DRB being set, a downlink header information element indicating whether a downlink SDAP header is present in the downlink data received via the DRB being set, and a default bearer information element indicating whether the DRB being set is a default radio bearer (default DRB).

[0068] Furthermore, the information element represented by pdcp-Config or PDCP-Config in the radio bearer configuration information element may be information related to the configuration of the NR PDCP entity for establishing or changing the PDCP 306 for an SRB or DRB, and may be referred to as a PDCP configuration information element in the embodiments of the present invention. The information related to the configuration of the NR PDCP entity may include information indicating the size of the uplink sequence number, information indicating the size of the downlink sequence number, information indicating a profile of ROHC (Robust Header Compression), reordering timer information, etc.

[0069] In addition, the information element represented by DRB-ToReleaseList among the radio bearer setting information elements may be list information of DRB identifiers of the DRBs to be released, and in embodiments of the present invention, it may be referred to as the radio bearer information element to be released or the data radio bearer information element to be released.

[0070] Also, some or all of the information elements shown in Fig. 7 may be optional, i.e., the information elements shown in Fig. 7 may be included in the RRC reconfiguration message according to necessity or conditions.

[0071] An example of a processing method of the UE 122 according to the embodiment of the present invention will be described with reference to FIG.

[0072] The processing unit 602 of the gNB 108 creates an RRC reconfiguration message including a radio bearer configuration information element for causing the UE 122 to perform processing, and transmits the message to the UE 122 from the transmission unit 600 (not shown). The reception unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (step S800). Note that the UE 122 may also receive an RRC message including the above-mentioned radio bearer configuration information element from the eNB 102.

[0073] Next, the processing unit 502 of the UE 122 determines whether the value of the radio bearer identifier information element included in the above-mentioned radio bearer setting information element is set in the UE 122 and whether the above-mentioned radio bearer setting information element includes an SDAP setting information element, and performs processing of step S804 described below based on whether the value of the radio bearer identifier information element included in the above-mentioned radio bearer setting information element is not set in the UE 122 and / or whether the above-mentioned radio bearer setting information element includes an SDAP setting information element (step S802).

[0074] The processing unit 502 of UE 122 determines whether or not an SDAP entity corresponding to the PDU session indicated by the PDU session information element included in the above-mentioned SDAP setting information element exists, and performs processing of step S806 and / or step S808 based on the fact that an SDAP entity corresponding to the PDU session indicated by the PDU session information element included in the above-mentioned SDAP setting information element does not exist (step S804).

[0075] Processing unit 502 of UE 122 establishes an SDAP entity (step S806). Note that before establishing the above-mentioned SDAP entity, a DRB corresponding to the value of the above-mentioned Radio Bearer Identifier information element may be established by establishing a PDCP entity or the like. Note that after establishing the above-mentioned SDAP entity, an SDAP entity may be further configured or reconfigured. Furthermore, when an SDAP entity is configured or reconfigured, the above-mentioned established DRB may be associated with the above-mentioned SDAP entity.

[0076] The processing unit 502 of the UE 122 determines whether an SDAP entity corresponding to the PDU session existed before receiving the RRC reconfiguration message, and notifies the upper layer that "user-plane resources for the PDU session have been established" based on the fact that an SDAP entity corresponding to the PDU session did not exist before receiving the RRC reconfiguration message (step S808). Note that "user-plane resources for the PDU session have been established" may be expressed in other ways, such as "user-plane resources for the PDU session have been configured."

[0077] "User plane resources for the above-mentioned PDU session have been established" can also be rephrased as "the QoS flow identifier information element included in the QoS flow information element to be added included in the above-mentioned SDAP configuration information element, or the correspondence rule between the QoS flow and the radio bearer corresponding to the value of the QoS flow identifier information element, has been stored."

[0078] The notification of "the establishment of user plane resources for the above-mentioned PDU session" may be, for example, notification of the above-mentioned PDU session identifier information element or the value of the PDU session identifier information element to the upper layer. In this case, the above-mentioned QoS flow identifier information element or the value of the QoS flow identifier information element may be notified to the upper layer at the same time, or instead of notifying the above-mentioned PDU session identifier information element or the value of the above-mentioned PDU session identifier information element to the upper layer, the value of the above-mentioned QoS flow identifier information element or the QoS identifier information element may be notified to the upper layer.

[0079] Furthermore, "determine whether an SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC Reconfiguration message" may be rephrased or supplemented as "determine whether the establishment of the above-mentioned SDAP entity (in step S806) is the result of full configuration." Furthermore, "based on the fact that an SDAP entity corresponding to the above-mentioned PDU session did not exist before receiving the above-mentioned RRC Reconfiguration message" may be rephrased or supplemented as "based on the fact that the establishment of the above-mentioned SDAP entity (in step S806) is not the result of full configuration."

[0080] In step S808, "before receiving the RRC reconfiguration message, an SDAP entity corresponding to the PDU session did not exist" may be rephrased as another condition (else) of "before receiving the RRC reconfiguration message, an SDAP entity corresponding to the PDU session existed." In addition, "the establishment of the SDAP entity (in step S806) is not the result of full configuration" may be rephrased as another condition (else) of "the establishment of the SDAP entity (in step S806) is the result of full configuration."

[0081] Next, another example of the processing method of the UE 122 according to the embodiment of the present invention will be described with reference to FIG.

[0082] The processing unit 602 of the gNB 108 creates an RRC reconfiguration message including a radio bearer configuration information element for causing the UE 122 to perform processing, and transmits the message to the UE 122 from the transmission unit 600 (not shown). The reception unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (step S900). Note that the UE 122 may also receive an RRC message including the above-mentioned radio bearer configuration information element from the eNB 102.

[0083] Next, the processing unit 502 of the UE 122 determines whether the value of the radio bearer identifier information element included in the above-mentioned radio bearer setting information element is set in the UE 122 and whether the above-mentioned radio bearer setting information element includes an SDAP setting information element, and performs processing of step S904 described below based on whether the value of the radio bearer identifier information element included in the above-mentioned radio bearer setting information element is not set in the UE 122 and / or whether the above-mentioned radio bearer setting information element includes an SDAP setting information element (step S902).

[0084] The processing unit 502 of the UE 122 determines whether or not an SDAP entity corresponding to the PDU session indicated by the PDU session information element included in the above-mentioned SDAP configuration information element exists, and performs processing of step S906 (described later) and / or step S908 (described later) based on the determination that an SDAP entity corresponding to the PDU session indicated by the PDU session information element included in the above-mentioned SDAP configuration information element does not exist (step S904).

[0085] Processing unit 502 of UE 122 establishes an SDAP entity (step S806). Note that before establishing the above-mentioned SDAP entity, a DRB corresponding to the value of the above-mentioned Radio Bearer Identifier information element may be established by establishing a PDCP entity or the like. Note that after establishing the above-mentioned SDAP entity, an SDAP entity may be further configured or reconfigured. Furthermore, when an SDAP entity is configured or reconfigured, the above-mentioned established DRB may be associated with the above-mentioned SDAP entity.

[0086] The processing unit 502 of the UE 122 determines whether an SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC reconfiguration message, and, based on the fact that an SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC reconfiguration message, associates the above-mentioned SDAP entity established (in step S906) with the above-mentioned PDU session (step S908).

[0087] Furthermore, "determine whether an SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC Reconfiguration message" may be rephrased or supplemented as "determine whether the establishment of the above-mentioned SDAP entity (in step S906) is the result of full configuration." Furthermore, "based on the fact that an SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC Reconfiguration message" may be rephrased or supplemented as "based on the fact that the establishment of the above-mentioned SDAP entity (in step S906) is the result of full configuration."

[0088] In step S908, "the SDAP entity corresponding to the above-mentioned PDU session existed before receiving the above-mentioned RRC reconfiguration message" may be rephrased as another condition (else) of "the SDAP entity corresponding to the above-mentioned PDU session did not exist before receiving the above-mentioned RRC reconfiguration message." In addition, "the establishment of the above-mentioned SDAP entity (in step S906) is the result of full configuration" may be rephrased as another condition (else) of "the establishment of the above-mentioned SDAP entity (in step S806) is not the result of full configuration."

[0089] In the embodiment of the present invention, the process of notifying the upper layer that "user-plane resources for the PDU session corresponding to the above-mentioned PDU session information element have been established or configured" may be performed by RRC308 or RRC208, or may be performed by SDAP310. The upper layer that notifies the upper layer that "user-plane resources for the PDU session corresponding to the above-mentioned PDU session information element have been established or configured" may be the NAS layer. The notification of the upper layer that "user-plane resources for the PDU session corresponding to the above-mentioned PDU session information element have been established or configured" may be performed after RRC308 or RRC208 confirms in SDAP310 that the QoS flow identifier information element included in the QoS flow information element to be added, or the QoS flow corresponding to the value of the QoS flow identifier information element, and the radio bearer have been stored. The method of confirming that the above-mentioned association rule has been stored may be a notification from the SDAP 310 to the RRC 308 or 208 indicating that the association rule has been stored.

[0090] In this manner, in the embodiment of the present invention, when an SDAP entity is established, the fact that user plane resources for a PDU session have been established or configured is notified to the upper layer when the PDU session is newly established. This allows the upper layer to detect that user plane resources for the PDU session have been established in the lower layer, and enables user data to be transmitted at the optimal timing. In other words, the terminal device can reduce the complexity of protocol processing and perform communication efficiently.

[0091] Note that the radio bearer setup in each embodiment of the present invention may be included not only in the RRC connection re-establishment procedure but also in the RRC establishment procedure or the RRC re-establishment procedure. Furthermore, the radio bearer in each embodiment of the present invention may be a DRB or an SRB.

[0092] It should be noted that the "information elements" in each embodiment of the present invention may also be called "fields."

[0093] Furthermore, in each embodiment of the present invention, the notification to the upper layer that "user plane resources for the PDU session corresponding to the PDU session information element have been established" and / or "user plane resources for the PDU session corresponding to the PDU session information element have been established or configured" may be other information other than the rephrased examples in each embodiment of the present invention, as long as it indicates that "user plane resources for the PDU session corresponding to the PDU session information element have been established" and / or "user plane resources for the PDU session corresponding to the PDU session information element have been established or configured."

[0094] Furthermore, in each embodiment of the present invention, "the radio bearer configuration information element includes an SDAP configuration information element" may mean that an EN-DC is not used, that is, the opposite of using an EN-DC. This is because, as explained in Non-Patent Document 8 and Non-Patent Document 9, in NR (New Radio technology), an EPC is used as a core network only in the case of an EN-DC.

[0095] Furthermore, the processes and methods of the terminal device and base station device described in each embodiment of the present invention can be summarized, for example, as follows.

[0096] That is, the terminal device communicates with a base station device and includes: a receiving unit that receives an RRC reconfiguration message including a radio bearer configuration information element from the base station device; and a processing unit that, if an SDAP entity for a PDU session information element included in the SDAP configuration information element does not exist based on the fact that the value of a radio bearer identifier information element included in the radio bearer configuration information element does not exist in the configuration of the terminal device and that an SDAP configuration information element is included in the radio bearer configuration information element, establishes an SDAP entity; further, determines whether an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message; notifies a higher layer that user plane resources for a PDU session corresponding to the value of the PDU session information element have been configured based on the fact that an SDAP entity for the PDU session information element did not exist before receiving the RRC reconfiguration message; and associates the established SDAP entity with the PDU session based on the fact that an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message.

[0097] Also, a base station device that communicates with a terminal device includes a transmitting unit that transmits an RRC reconfiguration message including a radio bearer configuration information element to the terminal device, and a processing unit that includes the radio bearer configuration information element in the RRC reconfiguration message and causes the terminal device to perform processing, wherein the processing is to establish an SDAP entity if an SDAP entity for a PDU session information element included in the SDAP configuration information element does not exist based on the fact that the value of a radio bearer identifier information element included in the radio bearer configuration information element does not exist in the configuration of the terminal device and that an SDAP configuration information element is included in the radio bearer configuration information element, and further notify a higher layer that user plane resources for a PDU session corresponding to the value of the PDU session information element have been configured based on the fact that an SDAP entity for the PDU session information element did not exist before receiving the RRC reconfiguration message, and associate the established SDAP entity with the PDU session based on the fact that an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message.

[0098] Also, a method for a terminal device communicating with a base station device, comprising: receiving an RRC reconfiguration message including a radio bearer configuration information element from the base station device; and, if an SDAP entity for a PDU session information element included in the SDAP configuration information element does not exist based on the fact that the value of a radio bearer identifier information element included in the radio bearer configuration information element does not exist in the configuration of the terminal device and that the radio bearer configuration information element includes an SDAP configuration information element, establishing an SDAP entity; further, determining whether an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message; notifying a higher layer that user plane resources for a PDU session corresponding to the value of the PDU session information element have been configured based on the fact that an SDAP entity for the PDU session information element did not exist before receiving the RRC reconfiguration message; and associating the established SDAP entity with the PDU session based on the fact that an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message.

[0099] Also, a method of a base station device communicating with a terminal device includes transmitting an RRC reconfiguration message including a radio bearer configuration information element to the terminal device, including the radio bearer configuration information element in the RRC reconfiguration message, causing the terminal device to perform processing, the processing including establishing an SDAP entity if an SDAP entity for a PDU session information element included in the SDAP configuration information element does not exist based on the fact that a value of a radio bearer identifier information element included in the radio bearer configuration information element does not exist in the configuration of the terminal device and the fact that the radio bearer configuration information element includes an SDAP configuration information element, and further including This process determines whether an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message, notifies the upper layer that user plane resources have been configured for the PDU session corresponding to the value of the PDU session information element based on the fact that an SDAP entity for the PDU session information element did not exist before receiving the RRC reconfiguration message, and associates the established SDAP entity with the PDU session based on the fact that an SDAP entity for the PDU session information element existed before receiving the RRC reconfiguration message.

[0100] The program running on the device according to the present invention may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of the above-described embodiments according to the present invention. The program or the information handled by the program is temporarily loaded into a volatile memory such as a random access memory (RAM) during processing, or stored in a nonvolatile memory such as a flash memory or a hard disk drive (HDD), and is read, modified, or written by the CPU as needed.

[0101] Note that a part of the device in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by a computer system and executed to realize the control function. The "computer system" here refers to a computer system built into the device, including hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0102] Furthermore, the term "computer-readable recording medium" may also include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such cases. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0103] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, typically an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may 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 gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology result in the emergence of integrated circuit technologies that can replace current integrated circuits, integrated circuits based on that technology may also be used.

[0104] The present invention is not limited to the above-described embodiment. Although an example of a device has been described in the embodiment, the present invention is not limited to this and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0105] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the gist of the present invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0106] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interface 122UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 500 Receiver 502, 602 Processing section 600 Transmitter

Claims

1. A terminal device that communicates with a base station device, a receiving unit that receives a Radio Resource Control (RRC) reconfiguration message including a Data Radio Bearer (DRB) configuration from the base station device; a processing unit, When processing the RRC reconfiguration message received by the receiving unit, the processing unit: (a) determines that a DRB identifier included in the DRB configuration does not exist in the current configuration of the terminal device; (b) determines that the DRB configuration includes a Service Data Adaptation Protocol (SDAP) configuration; and (c) determines that an SDAP entity corresponding to a PDU session indicated by a Protocol Data Unit (PDU) session information element included in the SDAP configuration does not exist. establishing an SDAP entity if it determines that (a), (b), and (c) are satisfied; Furthermore, if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, the terminal device notifies the upper layer that user plane resources for the PDU session information element have been established.

2. A communication method for a terminal device communicating with a base station device, comprising: receiving a Radio Resource Control (RRC) reconfiguration message including a Data Radio Bearer (DRB) configuration from the base station device; When processing the received RRC reconfiguration message, (a) determine that the DRB identifier included in the DRB configuration does not exist in the current configuration of the terminal device, (b) determine that the DRB configuration includes a Service Data Adaptation Protocol (SDAP) configuration, and (c) determine that there is no SDAP entity corresponding to the PDU session indicated by the Protocol Data Unit (PDU) session information element included in the SDAP configuration; establishing an SDAP entity if it is determined that (a), (b), and (c) are satisfied; and, if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, notifying an upper layer that user plane resources for the PDU session information element have been established.

3. A base station device that communicates with a terminal device, a transmitter that transmits a radio resource control (RRC) reconfiguration message including a data radio bearer (DRB) configuration to the terminal device; A processing unit that causes the terminal device to perform processing by including the DRB configuration in the RRC reconfiguration message, The process comprises: When the terminal device processes the received RRC reconfiguration message, (a) it determines that the DRB identifier included in the DRB configuration does not exist in the current configuration of the terminal device, (b) it determines that the DRB configuration includes a Service Data Adaptation Protocol (SDAP) configuration, and (c) it determines that there is no SDAP entity corresponding to the PDU session indicated by the Protocol Data Unit (PDU) session information element included in the SDAP configuration; establishing an SDAP entity if it is determined that (a), (b), and (c) are satisfied; Further, if the SDAP entity corresponding to the PDU session indicated by the PDU session information element did not exist before receiving the RRC reconfiguration message, notifying an upper layer that user plane resources for the PDU session information element have been established. Base station equipment.

Images