WO2020031934A1 - 端末装置、基地局装置、および方法 - Google Patents
端末装置、基地局装置、および方法 Download PDFInfo
- Publication number
- WO2020031934A1 WO2020031934A1 PCT/JP2019/030632 JP2019030632W WO2020031934A1 WO 2020031934 A1 WO2020031934 A1 WO 2020031934A1 JP 2019030632 W JP2019030632 W JP 2019030632W WO 2020031934 A1 WO2020031934 A1 WO 2020031934A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information element
- radio bearer
- pdu session
- terminal device
- sdap
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
Definitions
- the present invention relates to a terminal device, a base station device, and a method.
- Wireless access method and wireless network of cellular mobile communication (hereinafter referred to as “Long Term Evolution (LTE: registered trademark)” or “Evolved Universal Terrestrial Radio Access: EUTRA”) and core network (hereinafter “Evolved”).
- Packet @ Core: EPC ”) is being considered in the third generation partnership project (3rd Generation
- Non-Patent Document 1 As a wireless access method and a wireless network technology for a fifth generation cellular system, a technical study of LTE-Advanced Advanced, which is an extension of LTE, and NR (New Radio Technology), a new wireless access technology. And standards are being formulated (Non-Patent Document 1). Also, 5GC (5 Generation Core Network), which is a core network for the fifth generation cellular system, is being studied (Non-Patent Document 2).
- 3GPP RP-170855 “Work Item on New Radio (NR) Access Technology” 3GPP TS 23.501 v15.2.0, "System Architecture for the 5G System; Stage 2” 3GPP TS 36.300 v14.7.0, “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network Evaluation Network- 3GPP TS 36.331 v15.2.2, “Evolved UniversalstTerrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocolsspecifications” 3GPP TS 36.323 v15.0.0, "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specialization” 3GPP TS 36.322 v15.1.0, “Evolved Universal Terrestrial Radio Access” (E-UTRA); Radio Link Control (RLC) protocol specification 3GPP TS 36.321 v15.2.0, "Evolved Universal Terrestrial Radio Access (E
- a protocol of a wireless access layer which performs QoS (Quality of Service) management between an upper layer above an IP (Internet Protocol) layer and a wireless access layer of the NR is studied. ing.
- An aspect of the present invention has been made in view of the above circumstances, and a terminal device, a base station device, a method used for the terminal device, and a base station capable of efficiently performing communication with a base station device
- An object is to provide a method used in an apparatus.
- one embodiment of the present invention employs the following means. That is, a terminal device that communicates with a base station device, a receiving unit that receives a RRC (Radio Resource Control) reconfiguration message including a radio bearer configuration information element from the base station device, and a radio bearer configuration information element.
- RRC Radio Resource Control
- the radio bearer identifier to be configured does not exist in the setting of the terminal device
- the radio bearer setting information element includes a Service Data Adaptation Protocol (SDAP) setting information element, and the PDU (Protocol Data Unit) included in the SDAP setting information element If the session information element is not present in the settings of the terminal device, a process of notifying an upper layer that a user plane resource for a PDU session corresponding to the value of the PDU session information element has been set, And, with a.
- SDAP Service Data Adaptation Protocol
- Another aspect of the present invention is a base station apparatus that communicates with a terminal apparatus, wherein the transmitting section transmits an RRC (Radio Resource Control) reconfiguration message to the terminal apparatus, and a radio bearer setting is included in the RRC reconfiguration message.
- RRC Radio Resource Control
- the radio bearer identifier included in the radio bearer setting information element does not exist in the setting of the terminal device
- the radio bearer setting information element includes a Service Data Adaptation Protocol (SDAP) setting information element
- a PDU (Protocol Data Unit) session information element included in the SDAP setting information element does not exist in the setting of the terminal device
- the PDU session The user plane resource is set for PDU session corresponding to the value of the distribution element includes a process of notifying the upper layer.
- Another aspect of the present invention is a method of a terminal device performing communication with a base station device, the method comprising receiving an RRC (Radio Resource Control) reconfiguration message including a radio bearer configuration information element from the base station device,
- the radio bearer identifier included in the bearer setting information element is not present in the setting of the terminal device, the radio bearer setting information element includes an SDAP setting information element, and the PDU session information element included in the SDAP setting information element is If it does not exist in the setting of the terminal device, it notifies the upper layer that the user plane resource for the PDU session corresponding to the value of the PDU session information element has been set.
- RRC Radio Resource Control
- Another aspect of the present invention is a method of a base station apparatus performing communication with a terminal apparatus, comprising: transmitting an RRC reconfiguration message to the terminal apparatus; and including a radio bearer configuration information element in the RRC reconfiguration message.
- the terminal device performs a process, the process includes a radio bearer identifier included in the radio bearer configuration information element is not present in the configuration of the terminal device, the radio bearer configuration information element includes an SDAP configuration information element If the PDU session information element included in the SDAP setting information element is not present in the setting of the terminal device, it is determined that the user plane resource for the PDU session corresponding to the value of the PDU session information element has been set. Including processing to notify the layer.
- FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.
- FIG. 3 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in E-UTRA according to each embodiment of the present invention.
- FIG. 6 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in NR in each embodiment of the present invention. The figure which shows an example of the flow of the RRC connection resetting procedure in each Embodiment of this invention.
- FIG. 2 is a block diagram illustrating a configuration of a terminal device according to each embodiment of the present invention.
- FIG. 2 is a block diagram illustrating a configuration of a base station device according to each embodiment of the present invention.
- ASN. 1 is a diagram showing an example of an (Abstract ⁇ Syntax ⁇ Notation ⁇ One) description.
- 3 shows an example of a processing method according to Embodiment 1 of the present invention.
- 9 shows another example of the processing method according to the first embodiment of the present invention.
- 3 shows an example of a processing method according to Embodiment 1 of the present invention.
- 9 shows another example of the processing method according to the first embodiment of the present invention.
- LTE (and LTE-A Pro) and NR may be defined as different RATs.
- NR may be defined as a technology included in LTE.
- LTE may be defined as a technology included in NR.
- LTE connectable with NR and Multi ⁇ RAT ⁇ Dual ⁇ connectivity may be distinguished from conventional LTE.
- This embodiment may be applied to NR, LTE and other RATs. The following description will be made using terms related to LTE and NR, but may be applied in other technologies using other terms.
- E-UTRA in the present embodiment may be replaced with the term LTE
- LTE may be replaced with the term E-UTRA.
- FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.
- E-UTRA100 is a radio access technology described in Non-Patent Document 3 and the like, and is composed of a cell group (CellCGroup: CG) composed of one or a plurality of frequency bands.
- the eNB (E-UTRAN ⁇ Node ⁇ B) 102 is an E-UTRA base station apparatus.
- 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.
- the interface 112 is an interface between the eNB 102 and the EPC 104, and includes a control plane (Control @ Plane: CP) through which control signals pass and a user plane (User @ Plane: UP) through which the user data passes.
- Control @ Plane: CP Control @ Plane: CP
- User @ Plane: UP user plane
- the NR 106 is a radio access technology described in Non-Patent Document 9 and the like, and includes a cell group (Cell (Group: CG) configured with one or a plurality of frequency bands.
- Cell Group: CG
- gNB g Node B
- the 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 be used as an E-UTRA core network having a function of connecting to 5CG.
- E-UTRA may include E-UTRA having a function of connecting to 5CG.
- An interface 114 is an interface between the eNB 102 and the 5GC 110, an interface 116 is an interface between the gNB 108 and the 5GC 110, an interface 118 is an interface between the gNB 108 and the EPC 104, an interface 120 is an interface between the eNB 102 and the gNB 108, and an interface 124 is an EPC 104 and the 5GC 110 Interface between the two.
- the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 are interfaces that pass only the CP, only the UP, or both the CP and the UP.
- the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by the communication carrier.
- the UE 122 is a terminal device that supports NR or that supports both E-UTRA and NR.
- FIG. 2 is a diagram showing a protocol stack (Protocol @ Stack) of the UP and CP of the terminal device and the base station device in the E-UTRA radio access layer in each embodiment of the present invention.
- Protocol stack Protocol @ Stack
- FIG. 2A is a UP protocol stack diagram used when the UE 122 communicates with the eNB 102.
- PHY (Physical @ layer) 200 is a wireless physical layer (wireless physical layer), and provides a transmission service to an upper layer (upper layer) using a physical channel (Physical @ Channel).
- the PHY 200 is connected to a higher-order MAC (Medium Access Control layer) 202 described later via a transport channel (Transport Channel). Data moves between the MAC 202 and the PHY 200 via the transport channel. Data transmission and reception are performed between the PHY of the UE 122 and the PHY of the eNB 102 via the radio physical channel.
- MAC Medium Access Control layer
- the $ MAC 202 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels.
- the MAC 202 is connected to a higher-order RLC (Radio Link Control layer) 204 described later by a logical channel.
- Logical channels are roughly classified according to the type of information to be transmitted, and are divided into control channels for transmitting control information and traffic channels for transmitting user information.
- the MAC 202 has a function of controlling the PHY 200 to perform intermittent transmission (DRX / DTX), a function of executing a random access (Random @ Access) procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. (Non-Patent Document 7).
- the RLC 204 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer (lower layer) can appropriately transmit data.
- PDCP Packet Data Convergence Protocol Protocol
- Wireless link control layer wireless link control layer.
- the RLC 200 also has a function to guarantee the QoS (Quality of service) required by each data. That is, the RLC 204 has functions such as data retransmission control (Non-Patent Document 6).
- $ PDCP 206 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section.
- the PDCP 206 may have a header compression function for compressing unnecessary control information.
- the PDCP 206 may also have a data encryption function (Non-Patent Document 5).
- the data processed in the MAC 202, the RLC 204, and the PDCP 206 are referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, and a PDCP PDU, respectively.
- Data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206 or data passed to the upper layer is called MAC @ SDU (Service @ Data @ Unit), RLC @ SDU, and PDCP @ SDU, respectively.
- FIG. 2B is a protocol stack diagram of a CP used when the UE 122 communicates with the eNB 102.
- the $ CP protocol stack includes an RRC (Radio Resource Control layer) 208 in addition to the PHY 200, the MAC 202, the RLC 204, and the PDCP 206.
- the RRC 208 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (Radio Bearer: RB) and controls a logical channel, a transport channel, and a physical channel.
- the RB may be divided into a signaling radio bearer (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may. DRB may be used as a route for transmitting user data.
- Each RB may be set between the eNB 102 and the RRC 208 of the UE 122 (Non-Patent Document 4).
- the above-described function classification of the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 is an example, and some or all of the functions may not be implemented. In addition, some or all of the functions of each layer may be included in another layer.
- the IP layer, the Transmission Control Protocol (TCP) layer above the IP layer, the User Datagram Protocol (UDP) layer, the application layer, and the like are layers higher than the PDCP layer (not shown).
- An RRC layer and a NAS (non Access String) layer are also upper layers of the SDAP layer (not shown).
- the PDCP layer is an RRC layer, a NAS layer, an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and a lower layer of an application layer.
- FIG. 3 is a diagram illustrating a protocol stack (Protocol @ Stack) of UP and CP of the terminal device and the base station device in the NR radio access layer in each embodiment of the present invention.
- Protocol stack Protocol @ Stack
- FIG. 3A is a UP protocol stack diagram used when the UE 122 communicates with the gNB 108.
- PHY (Physical @ layer) 300 is a wireless physical layer (wireless physical layer) of NR, and may provide a transmission service to an upper layer using a physical channel (Physical @ Channel).
- the PHY 300 may be connected to a higher-order MAC (Medium Access Control layer) 302 described later via a transport channel (Transport Channel). Data may move between MAC 302 and PHY 300 via a transport channel. Data transmission and reception may be performed between the UE 122 and the PHY of the gNB 108 via the radio physical channel.
- the $ MAC 302 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels.
- the MAC 302 may be connected to a higher-level RLC (Radio Link Control layer) 304 described later by a logical channel.
- Logical channels are largely classified according to the type of information to be transmitted, and may be divided into control channels for transmitting control information and traffic channels for transmitting user information.
- the MAC 302 has a function of controlling the PHY 300 to perform intermittent transmission (DRX / DTX), a function of executing a random access (Random @ Access) procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. You may have it (Non-Patent Document 13).
- the RLC 304 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer can appropriately transmit the data.
- Layer radio link control layer
- the RLC 304 may have a function for guaranteeing the QoS (Quality of service) required by each data. That is, the RLC 304 may have a function such as data retransmission control (Non-Patent Document 12).
- the $ PDCP 306 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section.
- the PDCP 306 may have a header compression function for compressing unnecessary control information.
- the PDCP 306 may also have a data encryption function (Non-Patent Document 11).
- An SDAP (Service Data Adaptation Protocol) 310 associates a downlink QoS flow sent from a core network to a terminal device via a base station device with a DRB (mapping), and transmits the downlink QoS flow from the terminal device to the base station device.
- a service data adaptation protocol layer (service data adaptation protocol layer) having a function of mapping an uplink QoS flow sent to a core network to a DRB and storing mapping rule information (Non-Patent Document 16) ).
- the terminal device receives the SDAP @ SDU together with the QoS flow information from the upper layer, the terminal device allocates the SDAP @ SDU to the corresponding DRB based on the mapping rule between the stored QoS flow and the DRB.
- the SDAP @ SDU may be assigned to the default radio bearer (default DRB).
- a QoS flow is composed of one or more service data flows (Service ⁇ Data ⁇ Flow: SDF) that are processed according to the same QoS policy (Non-Patent Document 2).
- the SDAP may have a reflective QoS (Reflective QoS) function of mapping the uplink QoS flow and the DRB based on the information of the downlink QoS flow.
- the end marker PDU is an SDAP control PDU described in Non-Patent Document 16, in which the SDAP entity of the UE determines the QoS flow corresponding to the QoS flow identifier included in the QoS flow identifier field of the end marker PDU, and the end marker PDU. Is used to notify that the mapping with the transmitted radio bearer is finished.
- the IP layer, the Transmission Control Protocol (TCP) layer above the IP layer, the User Datagram Protocol (UDP) layer, and the application layer are upper layers of the SDAP layer (not shown).
- An RRC layer and a NAS (non Access String) layer are also upper layers of the SDAP layer (not shown).
- association between the service data flow and the QoS flow is performed.
- the SDAP layer is an RRC layer, a NAS layer, an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and a lower layer of the application layer.
- the data processed in the MAC 302, the RLC 304, the PDCP 306, and the SDAP 310 may be referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, a PDCP PDU, and a SDAP PDU, respectively.
- MAC PDU Protocol Data Unit
- RLC PDU Radio Link Control
- PDCP PDU Packet Control Protocol
- SDAP PDU Secure Access Protocol
- the data passed from the upper layer to the MAC 202, the RLC 204, and the PDCP 206 or the data passed to the upper layer may be called MAC @ SDU (Service @ Data @ Unit), RLC @ SDU, PDCP @ SDU, and SDAP @ SDU, respectively.
- FIG. 3B is a protocol stack diagram of the CP used when the UE 122 communicates with the gNB 108.
- the $ CP protocol stack includes an RRC (Radio Resource Control layer) 308 in addition to the PHY 300, the MAC 302, the RLC 304, and the PDCP 306.
- the RRC 308 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (Radio Bearer: RB) and controls a logical channel, a transport channel, and a physical channel.
- the RB may be divided into a signaling radio bearer (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may.
- DRB may be used as a route for transmitting user data.
- Each RB may be set between the gNB 108 and the RRC 308 of the UE 122. Further, a portion of the RB configured by the RLC 304 and the MAC 302 may be called an RLC bearer (Non-Patent Document 10).
- each layer may be included in another layer (layer).
- the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 are respectively referred to as an E-UTRA MAC or an LTE MAC, an E-UTRA RLC or LTE RLC, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
- the MAC 302, the RLC 304, the PDCP 306, and the RRC 308 may be referred to as an NR MAC, an NR RLC, an NR RLC, and an NR RRC, respectively.
- the space may be described using a space such as E-UTRA @ PDCP, LTE @ PDCP, or NR @ PDCP.
- the eNB 102, the gNB 108, the EPC 104, and the 5GC 110 may be connected via an interface 112, an interface 116, an interface 118, an interface 120, and an interface 114. Therefore, in order to support various communication systems, the RRC 208 of FIG. 2 may be replaced with the RRC 308 of FIG. Further, the PDCP 206 in FIG. 2 may be replaced with the PDCP 306 in FIG. Further, the RRC 308 in FIG. 3 may include the function of the RRC 208 in FIG. Further, the PDCP 306 in FIG. 3 may be the PDCP 206 in FIG.
- FIG. 4 is a diagram showing an example of a flow of an RRC resetting procedure in each embodiment of the present invention.
- the RRC reset procedure may be an RRC connection reset procedure.
- the RRC reconfiguration procedure (RRC @ Reconfiguration) performs establishment, change, and release of RB in NR and change, release, and the like of a secondary cell described in Non-Patent Document 10, and handover (reconfiguration with synchronization). And a procedure used for Measurement and the like.
- the RRC connection re-establishment procedure (RRC Connection Reconfiguration) performs establishment, change, and release of RB in LTE and change, release of a secondary cell, and the like, as well as handover and measurement (Measurement) described in Non-Patent Document 4. )).
- the RRC connection reset procedure is an EN-DC (E-UTRA-NR), which is an MR-DC in the MR-DC, particularly when the core network is the EPC 104 and the master node is the eNB 102 (also referred to as an extended eNB 102).
- E-UTRA-NR EN-DC
- NGEN-DC NG-RAN @ E-UTRA-NR @ Dual @ Connectivity
- the network is also connected to the core network 5GC.
- the RRC connection re-establishment procedure includes the establishment, change, and release of the RB in the NR and the change, release, and the like of the NR described in Non-Patent Document 10 in addition to LTE. And handover Also used to perform a portion of such fine measurement (Measurement).
- the description will be made using the name of RRC reconfiguration procedure, and the description will be made using gNB 108 as the base station apparatus.
- the UE 122 receives an RRC reconfiguration message (RRCReconfiguration) from the gNB 108 (step S400), and performs various settings according to the information included in the RRC reconfiguration message, for example, processing such as radio bearer setting and SDAP setting. Is performed (step S402).
- the UE 122 may send an RRC reconfiguration completion message (RRCReconfigurationComplete) or the like to the gNB 108 (not shown).
- the RRC reconfiguration message may be rephrased as RRC reconfiguration
- the RRC reconfiguration complete message may be rephrased as RRC reconfiguration complete.
- FIG. 5 is a block diagram illustrating a configuration of a terminal device (UE 122) according to each embodiment of the present invention. In order to avoid a complicated description, FIG. 5 shows only main components closely related to the present invention.
- the UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC reconfiguration message and the like from the gNB 108, and a processing unit 502 that performs processing according to various information elements (IE: Information @ Element) and various conditions included in the received message. .
- IE Information @ Element
- FIG. 6 is a block diagram showing a configuration of the base station apparatus (gNB 108) according to each embodiment of the present invention. In order to avoid a complicated description, FIG. 6 shows only main components closely related to the present invention.
- the gNB 108 illustrated in FIG. 6 generates a transmission unit 600 that transmits an RRC reconfiguration message and the like to the UE 122 and an RRC reconfiguration message including various information elements (IE: Information @ Element), and transmits the generated RRC reconfiguration message to the UE 122.
- the processing unit 602 causes the processing unit 502 to perform processing. Note that the configuration illustrated in FIG. 6 may be applied to the eNB 102. When applied to the eNB 102, the message transmitted from the transmitting unit 600 to the UE 122 may be an RRC connection reconfiguration message.
- FIG. 7 is a diagram showing an ASN.1 representing an information element included in the RRC reconfiguration message in FIG. 4 according to the first embodiment of the present invention.
- 1 (Abstract ⁇ Syntax ⁇ Notation ⁇ One) description.
- specifications related to RRC (Non-patent Document 4 and Non-Patent Document 10) include messages related to RRC, information elements (Information @ Element: IE), and the like as ASN. This is described using 1.
- ⁇ abbreviation> and ⁇ omission> are ASN. It is not part of the notation of 1 but indicates that other information is omitted.
- the information element may be omitted.
- the ASN. 1 is ASN. It does not follow the one notation method correctly, but is an example of RRC reset parameters in the present invention, and other names or other notations may be used. Also, the ASN. The first example shows only an example relating to main information closely related to the present invention in order to avoid a complicated description.
- 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 the embodiment of the present invention, the radio bearer setting information Element or data radio bearer information element.
- the information element represented by DRB-Identity in the radio bearer setting information element is information on a DRB identifier of a DRB to be added or changed, and in the embodiment of the present invention, a radio bearer identifier information element or a data radio bearer. It may be rephrased as an identifier information element. In the example of FIG. 7, an integer value of 1 to 32 is used, but another value may be used. For DC, the DRB identifier is unique within the scope of UE 122.
- the information element represented by cnAssociation in the radio bearer setting information element may be an information element indicating whether to use the EPC 104 or the 5GC 110 for the core network. It may be rephrased as an association information element. That is, when the UE 122 connects to the EPC, the DRB is associated with the EPS bearer identifier information element (eps-BearerIdentity) during cnAssociation or the EPS bearer identifier that is the value of the EPS bearer identifier information element, and the UE 122 connects to the 5GC 110.
- the EPS bearer identifier information element eps-BearerIdentity
- the DRB is a SDAP entity set according to a later-described SDAP setting information element (sdap-Config) or a PDU session information element or a PDU session information element value included in the SDAP setting information element. It may be associated with a certain PDU session identifier. That is, the information represented by cnAssociation includes an EPS bearer identifier information element (eps-BearerIdentity) when the EPC 104 is used for the core network, and an information element (sdap-Config) indicating the SDAP setting when the core network 5GC110 is used. ) May be included.
- EPS bearer identifier information element eps-BearerIdentity
- sdap-Config an information element (sdap-Config) indicating the SDAP setting when the core network 5GC110 is used. ) May be included.
- the information element represented by sdap-Config may be information on setting or resetting of an SDAP entity that determines a method of mapping a QoS flow and a DRB when the core network is 5GC110, In the embodiment of the present invention, it may be rephrased as an SDAP setting information element.
- the information element indicated by pdu-session or PDU-Session ID included in the SDAP setting information element is a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
- the identifier of the PDU session described in Non-Patent Document 2 to which the QoS flow assigned to (map) belongs may be referred to. In the embodiment of the present invention, it may be rephrased as a PDU session information element.
- the value of the PDU session information element may be a non-negative integer.
- the information element indicated by mappedQoS-FlowsToAdd included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element (map ), Or information indicating a list of QoS flow identifier (QFI: QoS @ Flow @ Identity) information elements of a QoS flow to be added (mapped), which will be added in the embodiment of the present invention. It may be paraphrased as a QoS flow information element.
- the above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
- the information element indicated by mappedQoS-FlowsToRelease included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
- the information may be information indicating a list of QoS flow identifiers (QFI: QoS @ Flow @ Identity) information elements of the QoS flows for which the correspondence is released among the (mapped) QoS flows, according to an embodiment of the present invention. In the embodiment, it may be paraphrased as a QoS flow information element to be released.
- the above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
- the information element indicated by QFI may be a QoS flow identifier that uniquely identifies a QoS flow described in Non-Patent Document 2, and may be rephrased as a QoS flow identifier information element in the embodiment of the present invention.
- the value of the QoS flow identifier information element may be a non-negative integer. Also, the value of the QoS flow identifier information element may be unique for the PDU session.
- an uplink header information element indicating that an uplink header is present a downlink header information element indicating that a downlink header is present, a default radio bearer (default DRB) May be included.
- the information element represented by pdcp-Config or PDCP-Config may be information related to the setting of the NR @ PDCP entity for establishing or changing the PDCP 306 for SRB or DRB. Often, in the embodiment of the present invention, it may be referred to as a PDCP setting information element.
- the information related to the setting of the NR @ PDCP entity includes information indicating the size of the uplink sequence number, information indicating the size of the downlink sequence number, information indicating the profile of header compression (RoHC: Robust @ Header @ Compression), and reordering (RoHC: Robust @ Header @ Compression). re-ordering) timer information and the like may be included.
- the information element represented by DRB-ToReleaseList may be list information of a DRB identifier of a DRB to be released, and in the embodiment of the present invention, a radio bearer information element to be released, Or, it may be paraphrased as a data radio bearer information element to be released.
- Some or all of the information elements shown in FIG. 7 may be optional. That is, the information elements shown in FIG. 7 may be included in the RRC reset message as needed.
- 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 RRC reconfiguration message from the transmission unit 600 to the UE 122 (not shown).
- the receiving unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (Step S800). Note that the UE 122 may receive an RRC message including the above-described radio bearer setting information element from the eNB 102, and the RRC message in this case may be referred to as an RRC connection re-establishment message.
- the processing unit 502 of the UE 122 confirms that the value of the radio bearer identifier information element included in the above-described radio bearer setting information element is not present in the current setting of the UE 122. Further, it is confirmed that the above-mentioned radio bearer setting information element includes the SDAP setting information element (step S802).
- the value of the radio bearer identifier information element included in the above-described radio bearer configuration information element is not present in the current setting of the UE 122, and the above-mentioned radio bearer configuration information element includes the SDAP configuration information element. If confirmed, the processing unit 502 of the UE 122 then confirms whether the value of the PDU session information element or the PDU session information element included in the above-described SDAP setting information element is present in the current setting of the UE 122 or not. However, if there is no such entity, it is determined that the SDAP entity for the PDU session indicated by the PDU session information element has not been established, and the SDAP entity is established (step S804).
- the LDAP entity for the PDU session indicated by the above PDU session information element has already been established, and the No entity is established.
- the processing unit 502 of the UE 122 sets the SDAP entity corresponding to the above-mentioned PDU session information element according to the above-mentioned SDAP setting information element, and further sets the radio bearer established according to the above-mentioned radio bearer setting element to the above-mentioned SDAP entity. (Step S806).
- the processing unit 502 of the UE 122 includes, in the above-mentioned SDAP setting information element, a QoS flow information element to be added, which corresponds to the above-mentioned radio bearer, that is, the radio bearer corresponding to the value of the above-mentioned radio bearer identifier information element. Check if it is. In the case where it is included, the value of the QoS flow identifier information element that is not present in the current setting of the UE 122 or the value of the QoS flow identifier information element is included in the QoS identifier information element included in the above-described added QoS flow information element.
- the upper layer is notified that “user plane resources (user-plane @ resources) for the PDU session corresponding to the above-mentioned PDU session information element have been established”.
- “The user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established” means “the above-mentioned QoS flow identifier information element that does not exist in the current setting of the UE 122 or the value of the QoS flow identifier information element. That the corresponding rule between the corresponding QoS flow and the radio bearer has been stored.
- To notify that "a user plane resource for a PDU session corresponding to the above-mentioned PDU session information element has been established" means, for example, notifying the above-mentioned PDU session identifier information element or the value of the PDU session identifier information element to an upper layer. It may be a thing. At this time, the new QoS flow identifier information element or the value of the new information element may be notified to the upper layer at the same time, or the value of the PDU session identifier information element or the value of the PDU session identifier information element Instead of notifying the upper layer, the new QoS flow identifier information element or the value of the new information element may be notified to the upper layer (step S808).
- the above-mentioned SDAP setting information element does not include the QoS flow information element to be added, the information indicating that “the user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established” is sent to the upper layer. No notification is given.
- the above-mentioned SDAP setting information element includes a QoS flow information element to be added, all the QoS identifier information elements included in the above-described QoS flow information element or the values of all the QoS identifier information elements are If the QoS setting information element does not include the QoS flow information element to be added when the current setting of the UE 122 is present, the "PDU session corresponding to the PDU session information element described above" is sent to the upper layer. Notification that the user plane resource has been established for.
- the QoS identifier information element included in the above-described QoS flow information element includes a QoS flow identifier information element that does not exist in the current setting of the UE 122 or a value of the QoS flow identifier information element.
- the case may be paraphrased as "when the QoS identifier information element included in the above-described QoS flow information element includes a new QoS flow identifier information element or a value of a new QoS flow identifier information element.” good.
- 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 RRC reconfiguration message from the transmission unit 600 to the UE 122 (not shown).
- the receiving unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (Step S900). Note that the UE 122 may receive an RRC message including the above-described radio bearer setting information element from the eNB 102, and the RRC message in this case may be referred to as an RRC connection re-establishment message.
- the processing unit 502 of the UE 122 confirms that the value of the radio bearer identifier information element included in the above-described radio bearer setting information element is in the current setting of the UE 122. Further, it is confirmed that the above-mentioned radio bearer setting information element includes the SDAP setting information element (step S902).
- the value of the radio bearer identifier information element included in the above-described radio bearer configuration information element is present in the current setting of the UE 122, and the above-mentioned radio bearer configuration information element includes the SDAP configuration information element. If confirmed, then the processing unit 502 of the UE 122 sets or resets the SDAP entity corresponding to the PDU session information element included in the above-mentioned SDAP setting information element according to the above-mentioned SDAP setting information element ( Step S904).
- the processing unit 502 of the UE 122 includes, in the above-mentioned SDAP setting information element, a QoS flow information element to be added, which corresponds to the above-mentioned radio bearer, that is, the radio bearer corresponding to the value of the above-mentioned radio bearer identifier information element. Check if it is. In the case where it is included, the value of the QoS flow identifier information element that does not exist in the current setting of the UE 122 or the value of the QoS flow identifier information element is included in the QoS identifier information element included in the above-described additional QoS flow information element.
- the upper layer is notified that "user plane resources (user-plane @ resources) for the PDU session corresponding to the above-mentioned PDU session information element have been established".
- “The user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established” means “the above-mentioned QoS flow identifier information element that does not exist in the current setting of the UE 122 or the value of the QoS flow identifier information element. That the corresponding rule between the corresponding QoS flow and the radio bearer has been stored.
- To notify that "a user plane resource for a PDU session corresponding to the above-mentioned PDU session information element has been established" means, for example, notifying the above-mentioned PDU session identifier information element or the value of the PDU session identifier information element to an upper layer. It may be a thing. At this time, the new QoS flow identifier information element or the value of the new information element may be notified to the upper layer at the same time, or the value of the PDU session identifier information element or the value of the PDU session identifier information element Instead of notifying the upper layer, the above-described new QoS flow identifier information element or the value of the new information element may be notified to the upper layer (step S906).
- the above-mentioned SDAP setting information element does not include the QoS flow information element to be added, the information indicating that “the user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established” is sent to the upper layer. No notification is given.
- the values of all the QoS identifier information elements or the values of all the QoS identifier information elements included in the above-mentioned added QoS flow information element Is present in the current setting of the UE 122, if the above-mentioned SDAP setting information element does not include the QoS flow information element to be added, the upper layer is referred to as “corresponding to the above-mentioned PDU session information element”. Notification that the user plane resource for the PDU session has been established "is not performed.
- the QoS identifier information element included in the above-described QoS flow information element includes a QoS flow identifier information element that does not exist in the current setting of the UE 122 or a value of the QoS flow identifier information element.
- the case may be paraphrased as "when the QoS identifier information element included in the above-described QoS flow information element includes a new QoS flow identifier information element or a value of a new QoS flow identifier information element.” good.
- step S808 or step S906 may be performed by the RRC 308 or RRC 208, or may be performed by the SDAP 310.
- the upper layer may be a NAS layer.
- the notification to the upper layer in the processing of step S808 or step S906 is performed in the SDAP 310 by the QoS flow identifier information element or the QoS flow identifier information included in the above-mentioned radio bearer configuration information element and not present in the current configuration of the UE 122.
- the fact that the association rule between the QoS flow corresponding to the value of the element and the radio bearer is stored may be confirmed by the RRC 308 or the RRC 208 and then performed.
- the above-described method of confirming that the association rule has been stored may be a notification from the SDAP 310 to the RRC 308 or RRC 208 indicating that the association rule has been stored.
- the terminal device when a QoS flow that is not presently set by the UE 122 is associated with the DRB, by notifying the upper layer, the user plane resources for the PDU session in the upper layer are reduced in the lower layer. It is possible to detect the establishment and to transmit the user data at the optimal timing. That is, the terminal device can reduce the complexity of the protocol processing and can communicate efficiently.
- Embodiment 2 Second Embodiment A second embodiment of the present invention will be described with reference to FIGS. 1 to 7 and FIGS.
- the upper layer is notified of the establishment of the user plane resource for the PDU session.
- the determination based on the QoS flow identifier information element included in the added QoS flow information element may or may not be performed.
- FIG. 4 is a diagram showing an example of a flow of an RRC resetting procedure in each embodiment of the present invention.
- the RRC reset procedure may be an RRC connection reset procedure.
- the RRC reconfiguration procedure (RRC @ Reconfiguration) performs establishment, change, and release of RB in NR and change, release, and the like of a secondary cell described in Non-Patent Document 10, and handover (reconfiguration with synchronization). And a procedure used for Measurement and the like.
- the RRC connection re-establishment procedure (RRC Connection Reconfiguration) performs establishment, change, and release of RB in LTE and change, release of a secondary cell, and the like, as well as handover and measurement (Measurement) described in Non-Patent Document 4. )).
- the RRC connection resetting procedure is performed in the MR-DC, particularly in the 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).
- the EN-DC E-UTRA-NR NGEN-DC (NG-RAN @ E-UTRA-NR @ Dual @ Connectivity), which is an MR-DC when the core network is 5GC110 and the master node is the eNB102, and the extended eNB102 is a core network 5GC.
- the RRC connection re-establishment procedure includes not only LTE but also a part of the establishment, change, and release of RB in NR and the change, release, and the like of the secondary cell described in Non-Patent Document 10.
- Perform handover and measurement (Mea Also used to perform some of Urement) or the like.
- the description will be made using the name of RRC reconfiguration procedure, and the description will be made using gNB 108 as the base station apparatus.
- the UE 122 receives an RRC reconfiguration message (RRCReconfiguration) from the gNB 108 (step S400), and performs various settings according to the information included in the RRC reconfiguration message, for example, processing such as radio bearer setting and SDAP setting. Is performed (step S402).
- the UE 122 may send an RRC reconfiguration completion message (RRCReconfigurationComplete) or the like to the gNB 108 (not shown).
- the RRC reconfiguration message may be rephrased as RRC reconfiguration
- the RRC reconfiguration complete message may be rephrased as RRC reconfiguration complete.
- FIG. 5 is a block diagram illustrating a configuration of a terminal device (UE 122) according to each embodiment of the present invention. In order to avoid a complicated description, FIG. 5 shows only main components closely related to the present invention.
- the UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC reconfiguration message and the like from the gNB 108, and a processing unit 502 that performs processing according to various information elements (IE: Information @ Element) and various conditions included in the received message. .
- IE Information @ Element
- FIG. 6 is a block diagram showing a configuration of the base station apparatus (gNB 108) according to each embodiment of the present invention. In order to avoid a complicated description, FIG. 6 shows only main components closely related to the present invention.
- the gNB 108 illustrated in FIG. 6 generates a transmission unit 600 that transmits an RRC reconfiguration message and the like to the UE 122 and an RRC reconfiguration message including various information elements (IE: Information @ Element), and transmits the generated RRC reconfiguration message to the UE 122.
- the processing unit 602 causes the processing unit 502 to perform processing. Note that the configuration illustrated in FIG. 6 may be applied to the eNB 102. When applied to the eNB 102, the message transmitted from the transmitting unit 600 to the UE 122 may be an RRC connection reconfiguration message.
- FIG. 7 shows ASN.1 representing an information element included in the RRC reconfiguration message in FIG. 4 according to Embodiment 1 of the present invention.
- 1 (Abstract ⁇ Syntax ⁇ Notation ⁇ One) description.
- specifications related to RRC (Non-patent Document 4 and Non-Patent Document 10) include messages related to RRC, information elements (Information @ Element: IE), and the like as ASN. This is described using 1.
- ⁇ abbreviation> and ⁇ omission> are ASN. It is not part of the notation of 1 but indicates that other information is omitted.
- the information element may be omitted.
- the ASN. 1 is ASN. It does not follow the one notation method correctly, but is an example of RRC reset parameters in the present invention, and other names or other notations may be used. Also, the ASN. The first example shows only an example relating to main information closely related to the present invention in order to avoid a complicated description.
- 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 the embodiment of the present invention, the radio bearer setting information Element or data radio bearer information element.
- the information element represented by DRB-Identity in the radio bearer setting information element is information on a DRB identifier of a DRB to be added or changed, and in the embodiment of the present invention, a radio bearer identifier information element or a data radio bearer. It may be rephrased as an identifier information element. In the example of FIG. 7, an integer value of 1 to 32 is used, but another value may be used. For DC, the DRB identifier is unique within the scope of UE 122.
- the information element represented by cnAssociation in the radio bearer setting information element may be an information element indicating whether to use the EPC 104 or the 5GC 110 for the core network. It may be rephrased as an association information element. That is, when the UE 122 connects to the EPC, the DRB is associated with the EPS bearer identifier information element (eps-BearerIdentity) during cnAssociation or the EPS bearer identifier that is the value of the EPS bearer identifier information element, and the UE 122 connects to the 5GC 110.
- the EPS bearer identifier information element eps-BearerIdentity
- the DRB is a SDAP entity set according to a later-described SDAP setting information element (sdap-Config) or a PDU session information element or a PDU session information element value included in the SDAP setting information element. It may be associated with a certain PDU session identifier. That is, the information represented by the cnAssociation includes an EPS bearer identifier information element (eps-BearerIdentity) when the EPC 104 is used for the core network such as when the EN-DC is used, and when the core network 5GC110 is used, When the EN-DC is not used, an information element (sdap-Config) indicating the SDAP setting may be included.
- EPS bearer identifier information element eps-BearerIdentity
- the information element represented by sdap-Config may be information on setting or resetting of an SDAP entity that determines a method of mapping a QoS flow and a DRB when the core network is 5GC110, In the embodiment of the present invention, it may be rephrased as an SDAP setting information element.
- the information element indicated by pdu-session or PDU-Session ID included in the SDAP setting information element is a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
- the identifier of the PDU session described in Non-Patent Document 2 to which the QoS flow assigned to (map) belongs may be referred to. In the embodiment of the present invention, it may be rephrased as a PDU session information element.
- the value of the PDU session information element may be a non-negative integer.
- the information element indicated by mappedQoS-FlowsToAdd included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element (map ), Or information indicating a list of QoS flow identifier (QFI: QoS @ Flow @ Identity) information elements of a QoS flow to be added (mapped), which will be added in the embodiment of the present invention. It may be paraphrased as a QoS flow information element.
- the above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
- the information element indicated by mappedQoS-FlowsToRelease included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
- the information may be information indicating a list of QoS flow identifiers (QFI: QoS @ Flow @ Identity) information elements of the QoS flows for which the correspondence is released among the (mapped) QoS flows, according to an embodiment of the present invention. In the embodiment, it may be paraphrased as a QoS flow information element to be released.
- the above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
- the information element indicated by QFI may be a QoS flow identifier that uniquely identifies a QoS flow described in Non-Patent Document 2, and may be rephrased as a QoS flow identifier information element in the embodiment of the present invention.
- the value of the QoS flow identifier information element may be a non-negative integer. Also, the value of the QoS flow identifier information element may be unique for the PDU session.
- an uplink header information element indicating that an uplink header is present a downlink header information element indicating that a downlink header is present, a default radio bearer (default DRB) May be included.
- the information element represented by pdcp-Config or PDCP-Config may be information related to the setting of the NR @ PDCP entity for establishing or changing the PDCP 306 for SRB or DRB. Often, in the embodiment of the present invention, it may be referred to as a PDCP setting information element.
- the information related to the setting of the NR @ PDCP entity includes information indicating the size of the uplink sequence number, information indicating the size of the downlink sequence number, information indicating the profile of header compression (RoHC: Robust @ Header @ Compression), and reordering (RoHC: Robust @ Header @ Compression). re-ordering) timer information and the like may be included.
- the information element represented by DRB-ToReleaseList may be list information of a DRB identifier of a DRB to be released, and in the embodiment of the present invention, a radio bearer information element to be released, Or, it may be paraphrased as a data radio bearer information element to be released.
- Some or all of the information elements shown in FIG. 7 may be optional. That is, the information elements shown in FIG. 7 may be included in the RRC reset message as needed.
- 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 RRC reconfiguration message from the transmission unit 600 to the UE 122 (not shown).
- the receiving unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (Step S1000). Note that the UE 122 may receive an RRC message including the above-described radio bearer setting information element from the eNB 102, and the RRC message in this case may be referred to as an RRC connection re-establishment message.
- the processing unit 502 of the UE 122 confirms that the value of the radio bearer identifier information element included in the above-described radio bearer setting information element is not present in the current setting of the UE 122. Further, it is confirmed that the above-mentioned radio bearer setting information element includes the SDAP setting information element (step S1002).
- step S1002 the value of the radio bearer identifier information element included in the above-described radio bearer configuration information element is not present in the current setting of the UE 122, and the above-mentioned radio bearer configuration information element includes the SDAP configuration information element.
- the processing unit 502 of the UE 122 checks whether the PDU session information element included in the above-described SDAP setting information element or the value of the PDU session information element is present in the current setting of the UE 122 (step S1004). ).
- the processing unit 502 of the UE 122 sets the SDAP entity according to the above-described SDAP setting information element, and associates the radio bearer established according to the above-described radio bearer setting element with the above-described SDAP entity.
- the processing unit 502 of the UE 122 notifies the upper layer that “user plane resources (user-plane resources) for the PDU session corresponding to the above-mentioned PDU session information element have been established or set”.
- “The user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established or has been established” means “the QoS flow identifier information included in the added QoS flow information element included in the above-described SDAP setting information element”. Element or the corresponding rule between the QoS flow and the radio bearer corresponding to the value of the QoS flow identifier information element.
- Notifying that "a user plane resource for a PDU session corresponding to the above PDU session information element has been established or set" means, for example, that the value of the above PDU session identifier information element or the value of the PDU session identifier information element is May be notified.
- the value of the above-mentioned QoS flow identifier information element or the value of the QoS flow identifier information element may be simultaneously notified to an upper layer, or the value of the above-mentioned PDU session identifier information element or the above-mentioned PDU session identifier information element May be notified to the upper layer instead of notifying the upper layer of the QoS flow identifier information element or the value of the QoS identifier information element described above (step S1006).
- step S1004 it is checked whether or not the PDU session information element included in the above-mentioned SDAP setting information element or the value of the PDU session information element is present in the current setting of the UE 122. , The establishment of the SDAP entity may not be performed. Also, in this case, the existing SDAP entity is established or re-established according to the above-mentioned SDAP setting information element, and the radio bearer established according to the above-mentioned radio bearer setting element is associated with the above-mentioned SDAP entity (step S1008).
- 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 RRC reconfiguration message from the transmission unit 600 to the UE 122 (not shown).
- the receiving unit 500 of the UE 122 receives the RRC reconfiguration message from the gNB 108 (Step S1100). Note that the UE 122 may receive an RRC message including the above-described radio bearer setting information element from the eNB 102, and the RRC message in this case may be referred to as an RRC connection re-establishment message.
- the processing unit 502 of the UE 122 confirms that the value of the radio bearer identifier information element included in the above-described radio bearer setting information element is not present in the current setting of the UE 122. Further, it is confirmed that the above-mentioned radio bearer setting information element includes the SDAP setting information element (step S1102).
- step S1102 the value of the radio bearer identifier information element included in the above-described radio bearer configuration information element is not present in the current setting of the UE 122, and the SDAP configuration information element is included in the above-described radio bearer configuration information element.
- the processing unit 502 of the UE 122 checks whether the PDU session information element included in the above-described SDAP setting information element or the value of the PDU session information element is present in the current setting of the UE 122 (step S1104). ).
- the PDU session information element indicated by the above-mentioned PDU session information element It is determined that the SDAP entity for is not established, and the SDAP entity is established. If the current setting of the UE 122 exists, it is determined that there is an SDAP entity for the PDU session indicated by the PDU session information element based on the presence of the UE 122, and the SDAP entity does not need to be established (step S1106).
- the processing unit 502 of the UE 122 sets or resets the existing SDAP entity corresponding to the established or the PDU session information element according to the above-described SDAP setting information element, and according to the above-described radio bearer setting element.
- the existing SDAP entity corresponding to the above-mentioned PDU session information element A radio bearer that has been configured or reconfigured and established according to the radio bearer configuration element described above may be associated with the SDAP entity described above. Further, the processing unit 502 of the UE 122 notifies the upper layer that “user plane resources (user-plane resources) for the PDU session corresponding to the above-mentioned PDU session information element have been established or set”.
- the user plane resource for the PDU session corresponding to the above-mentioned PDU session information element has been established or has been established means “the QoS flow identifier information included in the added QoS flow information element included in the above-described SDAP setting information element”. Element or the corresponding rule between the QoS flow and the radio bearer corresponding to the value of the QoS flow identifier information element.
- Notifying that "a user plane resource for a PDU session corresponding to the above PDU session information element has been established or set" means, for example, that the value of the above PDU session identifier information element or the value of the PDU session identifier information element is May be notified.
- the value of the above-mentioned QoS flow identifier information element or the value of the QoS flow identifier information element may be simultaneously notified to an upper layer, or the value of the above-mentioned PDU session identifier information element or the above-mentioned PDU session identifier information element May be notified to the upper layer instead of notifying the upper layer of the QoS flow identifier information element or the value of the QoS identifier information element described above (step S1108).
- the process of notifying the upper layer that “user plane resources (user-plane @ resources) for the PDU session corresponding to the above PDU session information element have been established or set” is , RRC 308 or RRC 208 or SDAP 310.
- the upper layer that notifies that “user plane resources (user-plane @ resources) for the PDU session corresponding to the above-mentioned PDU session information element have been established or set” may be the NAS layer.
- the notification to the upper layer that “user plane resources (user-plane @ resources) for the PDU session corresponding to the above-mentioned PDU session information element has been established or set” is sent to the SDAP 310 in the above-mentioned radio bearer setting information.
- the RRC 308 indicates that the association rule between the QoS flow identifier information element included in the added QoS flow information element or the QoS flow corresponding to the value of the QoS flow identifier information element and the association rule with the radio bearer is stored. Alternatively, it may be performed after confirming with the RRC 208.
- the above-described method of confirming that the association rule has been stored may be a notification from the SDAP 310 to the RRC 308 or RRC 208 indicating that the association rule has been stored.
- the user plane resource for the PDU session is transmitted to the lower layer in the upper layer. It is possible to detect the establishment and to transmit the user data at the optimal timing. That is, the terminal device can reduce the complexity of the protocol processing and can communicate efficiently.
- the radio bearer setting 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 (RRC @ Establishment) procedure or the RRC re-establishment (RRC @ Re-Estimation) procedure.
- the radio bearer in each embodiment of the present invention may be a DRB or an SRB.
- the “information element” in each embodiment of the present invention may be called a “field”.
- the fact that the user plane resource for the PDU session corresponding to the PDU session information element has been established” and / or “the user plane resource (user The notification to the upper layer that “plane @ resources has been established or set” is not limited to the paraphrased example in each embodiment of the present invention, except that the user plane resource for the PDU session corresponding to the PDU session information element is Any other information may be used as long as the information indicates "established” and / or "established or set user plane resources (user-plane @ resources) for the PDU session corresponding to the PDU session information element.”
- the radio bearer setting information element includes the SDAP setting information element
- EN-DC is not used, that is, EN-DC is used. It may mean that the opposite is true. This is because, as described in Non-Patent Document 8 and Non-Patent Document 9, in NR (New Radio Technology), EPC is used as a core network only in the case of EN-DC.
- the program that operates on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like so that the computer functions so as to realize the functions of the above-described embodiment according to the present invention.
- the program or information handled by the program is temporarily read into a volatile memory such as a Random Access Memory (RAM) during processing, or is stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD). In response, reading, correction and writing are performed by the CPU.
- a volatile memory such as a Random Access Memory (RAM) during processing
- a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD).
- HDD Hard Disk Drive
- a part of the device in the above-described embodiment may be realized by a computer.
- a program for realizing this control function is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read by a computer system and executed to realize the control function.
- the "computer system” is a computer system built in the apparatus, and includes hardware such as an operating system and peripheral devices.
- the "computer-readable recording medium” may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
- a "computer-readable recording medium” means that a program is dynamically held for a short time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line.
- a program that holds a program for a certain period of time such as a volatile memory in a computer system serving as a server or a client in that case, may be included.
- the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system. .
- each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, that is, typically, an integrated circuit or a plurality of integrated circuits.
- An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
- a general purpose processor may be a microprocessor, or, in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine.
- the general-purpose processor or each of the above-described circuits may be configured by a digital circuit, or may be configured by an analog circuit. Further, in the case where a technology for forming an integrated circuit that substitutes for a current integrated circuit appears due to the progress of semiconductor technology, an integrated circuit based on the technology can be used.
- the present invention is not limited to the above embodiment.
- an example of the device is described.
- the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.
- One embodiment of the present invention is used in, for example, a communication system, a communication device (eg, a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (eg, a communication chip), a program, or the like. be able to.
- a communication device eg, a mobile phone device, a base station device, a wireless LAN device, or a sensor device
- an integrated circuit eg, a communication chip
- program e.g, a program, or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
本願は、2018年8月6日に日本に出願された特願2018-147659号について優先権を主張し、その内容をここに援用する。
図1から図9を用いて、本発明の実施の形態を説明する。
図1から図7、及び図10、図11を用いて、本発明の実施の形態2を説明する。本発明の実施の形態2では、確立された無線ベアラとSDAPエンティティの関連付けが行われた事に基づいて、該当PDUセッションに対するユーザプレーンリソースが確立された事を上位レイヤに通知する。実施の形態1と異なり、追加するQoSフロー情報要素に含まれるQoSフロー識別子情報要素に基づく判断はしても良いし、しなくても良い。
Claims (6)
- 基地局装置と通信を行う端末装置であって、
前記基地局装置から無線ベアラ設定情報要素を含むRRC(Radio Resource Control)再設定メッセージを受信する受信部と、
前記無線ベアラ設定情報要素に含まれる無線ベアラ識別子が前記端末装置の設定に存在せず、前記無線ベアラ設定情報要素にSDAP(Service Data Adaptation Protocol)設定情報要素が含まれ、前記SDAP設定情報要素に含まれるPDU(Protocol Data Unit)セッション情報要素が前記端末装置の設定に存在しない場合には、前記PDUセッション情報要素の値に対応するPDUセッションに対するユーザプレーンリソースが設定されたことを上位レイヤに通知する、処理部と、
を有する、端末装置。 - 前記ユーザプレーンリソースの設定は、無線ベアラに関する設定を含む、
請求項1に記載の端末装置。 - 端末装置と通信を行う基地局装置であって、
前記端末装置へRRC(Radio Resource Control)再設定メッセージを送信する送信部と、
前記RRC再設定メッセージに無線ベアラ設定情報要素を含めることにより、前記端末装置に処理を行わせる処理部とを有し、
前記処理は、
前記無線ベアラ設定情報要素に含まれる無線ベアラ識別子が、前記端末装置の設定に存在せず、前記無線ベアラ設定情報要素にSDAP(Service Data Adaptation Protocol)設定情報要素が含まれ、前記SDAP設定情報要素に含まれるPDU(Protocol Data Unit)セッション情報要素が前記端末装置の設定に存在しない場合には、前記PDUセッション情報要素の値に対応するPDUセッションに対するユーザプレーンリソースが設定された事を上位レイヤに通知する処理を含む、
基地局装置。 - 前記ユーザプレーンリソースの設定は、無線ベアラに関する設定を含む、
請求項3に記載の基地局装置。 - 基地局装置と通信を行う端末装置の方法であって、
前記基地局装置から無線ベアラ設定情報要素を含むRRC(Radio Resource Control)再設定メッセージを受信し、
前記無線ベアラ設定情報要素に含まれる無線ベアラ識別子が前記端末装置の設定に存在せず、前記無線ベアラ設定情報要素にSDAP設定情報要素が含まれ、前記SDAP設定情報要素に含まれるPDUセッション情報要素が前記端末装置の設定に存在しない場合には、前記PDUセッション情報要素の値に対応するPDUセッションに対するユーザプレーンリソースが設定されたことを上位レイヤに通知する、
方法。 - 端末装置と通信を行う基地局装置の方法であって、
前記端末装置へRRC再設定メッセージを送信し、
前記RRC再設定メッセージに無線ベアラ設定情報要素を含めることにより、前記端末装置に処理を行わせ、
前記処理は、
前記無線ベアラ設定情報要素に含まれる無線ベアラ識別子が前記端末装置の設定に存在せず、前記無線ベアラ設定情報要素にSDAP設定情報要素が含まれ、前記SDAP設定情報要素に含まれるPDUセッション情報要素が前記端末装置の設定に存在しない場合には、前記PDUセッション情報要素の値に対応するPDUセッションに対するユーザプレーンリソースが設定されたことを上位レイヤに通知する処理を含む、
方法。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201980049907.8A CN112470544A (zh) | 2018-08-06 | 2019-08-05 | 终端装置、基站装置以及方法 |
BR112021001197A BR112021001197A8 (pt) | 2018-08-06 | 2019-08-05 | Aparelho terminal, aparelho de estação-base e método |
EP19847035.3A EP3836725A4 (en) | 2018-08-06 | 2019-08-05 | TERMINAL DEVICE, BASE STATION DEVICE, AND METHOD |
US17/263,614 US11627614B2 (en) | 2018-08-06 | 2019-08-05 | Terminal apparatus, base station apparatus, and method |
PH12021550181A PH12021550181A1 (en) | 2018-08-06 | 2021-01-25 | Terminal device, base station device, and method |
IL280481A IL280481A (en) | 2018-08-06 | 2021-01-28 | Terminal device, base station device, and method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018147659A JP7262941B2 (ja) | 2018-08-06 | 2018-08-06 | 端末装置、基地局装置、および方法 |
JP2018-147659 | 2018-08-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020031934A1 true WO2020031934A1 (ja) | 2020-02-13 |
Family
ID=69413818
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2019/030632 WO2020031934A1 (ja) | 2018-08-06 | 2019-08-05 | 端末装置、基地局装置、および方法 |
Country Status (8)
Country | Link |
---|---|
US (1) | US11627614B2 (ja) |
EP (1) | EP3836725A4 (ja) |
JP (1) | JP7262941B2 (ja) |
CN (1) | CN112470544A (ja) |
BR (1) | BR112021001197A8 (ja) |
IL (1) | IL280481A (ja) |
PH (1) | PH12021550181A1 (ja) |
WO (1) | WO2020031934A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020072374A (ja) * | 2018-10-31 | 2020-05-07 | シャープ株式会社 | 端末装置、基地局装置、方法、および、集積回路 |
JP2020077928A (ja) * | 2018-11-06 | 2020-05-21 | シャープ株式会社 | 端末装置、基地局装置、方法、および、集積回路 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018147659A (ja) | 2017-03-03 | 2018-09-20 | 松本油脂製薬株式会社 | 二次電池スラリー組成物及びその利用 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101586550B1 (ko) * | 2007-09-28 | 2016-01-20 | 라쿠텐 인코포레이티드 | 업링크 프로토콜 변경을 지원하기 위한 방법 및 장치 |
CN104244347A (zh) * | 2008-08-08 | 2014-12-24 | 交互数字专利控股公司 | 用于服务高速下行链路共享信道小区改变的方法和wtru |
US9113450B2 (en) * | 2012-08-23 | 2015-08-18 | Interdigital Patent Holdings, Inc. | Operating with multiple schedulers in a wireless system |
CN107579807B (zh) * | 2016-06-30 | 2020-11-27 | 电信科学技术研究院 | 数据传输的方法及装置 |
CN108282817B (zh) * | 2017-01-05 | 2021-08-20 | 华为技术有限公司 | 信息传输的方法和装置 |
WO2019030981A1 (ja) * | 2017-08-09 | 2019-02-14 | 日本電気株式会社 | 無線アクセスネットワークノード、コアネットワークノード、及び無線端末並びにこれらの方法 |
US10292078B1 (en) * | 2017-11-08 | 2019-05-14 | Htc Corporation | Device and method of handling an evolved packet system bearer context |
JP6922997B2 (ja) * | 2017-11-13 | 2021-08-18 | 日本電気株式会社 | 無線端末およびその方法 |
CN110691424B (zh) * | 2018-01-12 | 2020-09-18 | 华为技术有限公司 | 一种cu-du架构下重复模式的通信处理方法和设备 |
US20190313311A1 (en) * | 2018-04-09 | 2019-10-10 | Mediatek Inc. | Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover |
-
2018
- 2018-08-06 JP JP2018147659A patent/JP7262941B2/ja active Active
-
2019
- 2019-08-05 EP EP19847035.3A patent/EP3836725A4/en not_active Ceased
- 2019-08-05 CN CN201980049907.8A patent/CN112470544A/zh active Pending
- 2019-08-05 BR BR112021001197A patent/BR112021001197A8/pt unknown
- 2019-08-05 WO PCT/JP2019/030632 patent/WO2020031934A1/ja active Application Filing
- 2019-08-05 US US17/263,614 patent/US11627614B2/en active Active
-
2021
- 2021-01-25 PH PH12021550181A patent/PH12021550181A1/en unknown
- 2021-01-28 IL IL280481A patent/IL280481A/en unknown
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018147659A (ja) | 2017-03-03 | 2018-09-20 | 松本油脂製薬株式会社 | 二次電池スラリー組成物及びその利用 |
Non-Patent Citations (19)
Also Published As
Publication number | Publication date |
---|---|
EP3836725A4 (en) | 2022-05-11 |
US11627614B2 (en) | 2023-04-11 |
CN112470544A (zh) | 2021-03-09 |
BR112021001197A8 (pt) | 2022-06-28 |
BR112021001197A2 (pt) | 2021-04-27 |
JP2020025159A (ja) | 2020-02-13 |
JP7262941B2 (ja) | 2023-04-24 |
EP3836725A1 (en) | 2021-06-16 |
IL280481A (en) | 2021-03-25 |
US20210298097A1 (en) | 2021-09-23 |
PH12021550181A1 (en) | 2022-02-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019131345A1 (ja) | 端末装置、方法、および、集積回路 | |
JP7145603B2 (ja) | 端末装置、基地局装置および方法 | |
JP7142426B2 (ja) | 端末装置および方法 | |
WO2019131851A1 (ja) | 端末装置、方法、および、集積回路 | |
KR102694443B1 (ko) | 단말 장치, 기지국 장치, 및 방법 | |
WO2019131320A1 (ja) | 端末装置、方法、および、集積回路 | |
WO2019131847A1 (ja) | 端末装置、方法、および、集積回路 | |
WO2020031934A1 (ja) | 端末装置、基地局装置、および方法 | |
JP2023176001A (ja) | 端末装置、通信方法、および基地局装置 | |
WO2020059720A1 (ja) | 端末装置、基地局装置、および、方法 | |
JP7390149B2 (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
WO2020013029A1 (ja) | 端末装置、基地局装置、および、方法 | |
WO2020031664A1 (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
JP7518306B2 (ja) | 端末装置、基地局装置、および方法 | |
JP7271766B2 (ja) | 端末装置、基地局装置、通信方法、および、集積回路 | |
WO2020095838A1 (ja) | 端末装置、基地局装置、および、方法 | |
WO2019244615A1 (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
WO2019098266A1 (ja) | 端末装置および方法 | |
JP2022118227A (ja) | 端末装置、基地局装置、および方法 | |
JP2022185122A (ja) | 端末装置、基地局装置、および方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19847035 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 280481 Country of ref document: IL |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112021001197 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019847035 Country of ref document: EP Effective date: 20210309 |
|
ENP | Entry into the national phase |
Ref document number: 112021001197 Country of ref document: BR Kind code of ref document: A2 Effective date: 20210122 |