[go: up one dir, main page]

WO2017026444A1 - Terminal sans fil et station de base - Google Patents

Terminal sans fil et station de base Download PDF

Info

Publication number
WO2017026444A1
WO2017026444A1 PCT/JP2016/073298 JP2016073298W WO2017026444A1 WO 2017026444 A1 WO2017026444 A1 WO 2017026444A1 JP 2016073298 W JP2016073298 W JP 2016073298W WO 2017026444 A1 WO2017026444 A1 WO 2017026444A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
information
pdcp packet
recording process
base station
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2016/073298
Other languages
English (en)
Japanese (ja)
Inventor
憲由 福田
真人 藤代
裕之 安達
優志 長坂
ヘンリー チャン
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyocera Corp
Original Assignee
Kyocera Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kyocera Corp filed Critical Kyocera Corp
Publication of WO2017026444A1 publication Critical patent/WO2017026444A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • the present invention relates to a radio terminal and a base station in a mobile communication system.
  • MDT Minimization of the technology
  • Drive Tests Driving Tests
  • a wireless terminal includes a control unit that performs processing of transmitting a PDCP (Packet Data Convergence Protocol) packet to a base station.
  • the control unit performs a recording process of recording transmission time information of the PDCP packet together with identification information of the PDCP packet.
  • PDCP Packet Data Convergence Protocol
  • FIG. 10 is a sequence diagram showing an operation pattern 2-2 of the third embodiment.
  • the wireless terminal includes a control unit that performs a process of transmitting a packet data convergence protocol (PDCP) packet to a base station.
  • the control unit performs a recording process of recording transmission time information of the PDCP packet together with identification information of the PDCP packet.
  • PDCP packet data convergence protocol
  • the transmission time information may indicate a time when the PDCP packet arrives at the PDCP layer from an upper layer of the PDCP layer.
  • the identification information may be a sequence number in the PDCP packet.
  • the control unit may receive setting information for uplink latency measurement from the base station, and perform the recording process based on the setting information.
  • the setting information may include network absolute time information, and the transmission time information may be based on the absolute time information.
  • the setting information may include a sequence number of a specific PDCP packet where the recording process is to be started.
  • the setting information may include at least one of a sequence number of a specific PDCP packet for which the recording process is to be completed, the number of PDCP packets for which the recording process is to be performed, and a period for which the recording process is to be performed. .
  • the control unit may add information indicating that the recording process is performed to each PDCP packet related to the recording process.
  • the control unit adds information indicating the start of the recording process to the first PDCP packet related to the start of the recording process, and applies the recording process to the second PDCP packet related to the end of the recording process. Information indicating the end of the process may be added.
  • the control unit may add a tag number for identifying each PDCP packet to each PDCP packet related to the recording process, and record the tag number as the identification information.
  • the control unit confirms that reception processing of the PDCP packet by the base station is completed based on a confirmation response to the PDCP packet transmitted from the base station, and transmits time information related to the confirmation completion to the transmission It may be recorded in association with time information.
  • the control unit performs processing for transmitting the PDCP packet to one of the master base station and the secondary base station, and determines whether the one base station is the master base station or the secondary base station.
  • Information to be shown may be associated with the transmission time information and the identification information.
  • the base station includes a control unit that performs processing of receiving a PDCP (Packet Data Convergence Protocol) packet from a wireless terminal.
  • the control unit performs a recording process of recording the reception time information of the PDCP packet together with the identification information of the PDCP packet.
  • PDCP Packet Data Convergence Protocol
  • the reception time information may indicate a time when the PDCP packet arrives at the PDCP layer from a lower layer of the PDCP layer or a time when the PDCP packet is delivered from the PDCP layer to an upper layer of the PDCP layer.
  • the identification information may be a sequence number in the PDCP packet or a tag number added by the wireless terminal to the PDCP packet.
  • the control unit transmits uplink latency measurement setting information to the wireless terminal, and the setting information includes network absolute time information, a sequence number of a specific PDCP packet to start the recording process, and the recording process. May include at least one of a sequence number of a specific PDCP packet to be terminated, the number of PDCP packets to be subjected to the recording process, and a period for which the recording process is to be performed.
  • the control unit may receive recording information including the transmission time information of the PDCP packet and the identification information from the wireless terminal, and associate the transmission time information with the reception time information based on the identification information. .
  • the control unit performs a process of directly receiving the PDCP packet from the wireless terminal or receiving from the wireless terminal via a secondary base station, and information indicating whether the PDCP packet is via the secondary base station You may link with the said reception time information and the said identification information.
  • FIG. 1 is a diagram illustrating a configuration of an LTE system.
  • LTE Long Term Evolution
  • UE User Equipment
  • E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
  • EPC Evolved Paque
  • the UE 100 corresponds to a wireless terminal.
  • the UE 100 is a mobile communication device, and performs radio communication with a cell (serving cell).
  • the configuration of the UE 100 will be described later.
  • the E-UTRAN 10 corresponds to a radio access network.
  • the E-UTRAN 10 includes an eNB 200 (evolved Node-B).
  • the eNB 200 corresponds to a base station.
  • the eNB 200 is connected to each other via the X2 interface. The configuration of the eNB 200 will be described later.
  • the eNB 200 manages one or a plurality of cells and performs radio communication with the UE 100 that has established a connection with the own cell.
  • the eNB 200 has a radio resource management (RRM) function, a routing function of user data (hereinafter simply referred to as “data”), a measurement control function for mobility control / scheduling, and the like.
  • RRM radio resource management
  • Cell is used as a term indicating a minimum unit of a radio communication area, and is also used as a term indicating a function of performing radio communication with the UE 100.
  • the EPC 20 corresponds to a core network.
  • the EPC 20 includes an MME (Mobility Management Entity) / S-GW (Serving-Gateway) 300.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • MME performs various mobility control etc. with respect to UE100.
  • the S-GW performs data transfer control.
  • the MME / S-GW 300 is connected to the eNB 200 via the S1 interface.
  • the E-UTRAN 10 and the EPC 20 constitute a network.
  • FIG. 2 is a protocol stack diagram of a radio interface in the LTE system.
  • the radio interface protocol is divided into the first to third layers of the OSI reference model, and the first layer is a physical (PHY) layer.
  • the second layer includes a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer.
  • the third layer includes an RRC (Radio Resource Control) layer.
  • the physical layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping.
  • Data and control signals are transmitted between the physical layer of the UE 100 and the physical layer of the eNB 200 via a physical channel.
  • the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control signals are transmitted between the MAC layer of the UE 100 and the MAC layer of the eNB 200 via a transport channel.
  • the MAC layer of the eNB 200 includes a scheduler that determines an uplink / downlink transport format (transport block size, modulation / coding scheme (MCS)) and an allocation resource block to the UE 100.
  • MCS modulation / coding scheme
  • the RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and the physical layer. Data and control signals are transmitted between the RLC layer of the UE 100 and the RLC layer of the eNB 200 via a logical channel.
  • the PDCP layer performs header compression / decompression and encryption / decryption.
  • the RRC layer is defined only in the control plane that handles control signals. Messages for various settings (RRC messages) are transmitted between the RRC layer of the UE 100 and the RRC layer of the eNB 200.
  • the RRC layer controls the logical channel, the transport channel, and the physical channel according to establishment, re-establishment, and release of the radio bearer.
  • RRC connection When there is a connection (RRC connection) between the RRC of the UE 100 and the RRC of the eNB 200, the UE 100 is in the RRC connected mode (connected mode), and otherwise, the UE 100 is in the RRC idle mode (idle mode).
  • the NAS (Non-Access Stratum) layer located above the RRC layer performs session management and mobility management.
  • FIG. 3 is a block diagram of the UE 100 (wireless terminal). As illustrated in FIG. 3, the UE 100 includes a reception unit 110, a transmission unit 120, and a control unit 130.
  • the receiving unit 110 performs various types of reception under the control of the control unit 130.
  • the receiving unit 110 includes an antenna and a receiver.
  • the receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.
  • the transmission unit 120 performs various transmissions under the control of the control unit 130.
  • the transmission unit 120 includes an antenna and a transmitter.
  • the transmitter converts the baseband signal (transmission signal) output from the control unit 130 into a radio signal and transmits it from the antenna.
  • the control unit 130 performs various controls in the UE 100.
  • the control unit 130 includes a processor and a memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor includes a baseband processor that performs modulation / demodulation and encoding / decoding of the baseband signal, and a CPU (Central Processing Unit) that executes various processes by executing programs stored in the memory.
  • the processor may include a codec that performs encoding / decoding of an audio / video signal.
  • the processor executes various communication protocols described above and various processes described later.
  • the UE 100 may further include a GNSS (Global Navigation Satellite System) receiver for obtaining location information indicating the geographical location of the UE 100 itself.
  • GNSS Global Navigation Satellite System
  • FIG. 4 is a block diagram of the eNB 200 (base station). As illustrated in FIG. 4, the eNB 200 includes a transmission unit 210, a reception unit 220, a control unit 230, and a backhaul communication unit 240.
  • the transmission unit 210 performs various transmissions under the control of the control unit 230.
  • the transmission unit 210 includes an antenna and a transmitter.
  • the transmitter converts the baseband signal (transmission signal) output from the control unit 230 into a radio signal and transmits it from the antenna.
  • the receiving unit 220 performs various types of reception under the control of the control unit 230.
  • the receiving unit 220 includes an antenna and a receiver.
  • the receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.
  • the control unit 230 performs various controls in the eNB 200.
  • the control unit 230 includes a processor and a memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor includes a baseband processor that performs modulation / demodulation and encoding / decoding of the baseband signal, and a CPU (Central Processing Unit) that executes various processes by executing programs stored in the memory.
  • the processor executes various communication protocols described above and various processes described later.
  • the backhaul communication unit 240 is connected to the adjacent eNB via the X2 interface and is connected to the MME / S-GW 300 via the S1 interface.
  • the backhaul communication unit 240 is used for communication performed on the X2 interface, communication performed on the S1 interface, and the like.
  • Uplink latency measurement according to the first embodiment Hereinafter, uplink latency measurement according to the first embodiment will be described.
  • FIG. 5 is a diagram illustrating a basic operation of uplink latency measurement according to the first embodiment. Prior to this operation, the eNB 200 performs settings for uplink latency measurement on the UE 100. Details of such setting processing will be described later.
  • the UE 100 performs a process of transmitting a PDCP packet (Packet) to the eNB 200 in the connected mode.
  • the PDCP packet is a PDCP SDU (Service Data Unit) that arrives at the PDCP layer from an upper layer (for example, an application layer) of the PDCP layer.
  • the PDCP packet may be a PDCP PDU (Protocol Data Unit) delivered from the PDCP layer to a lower layer (RLC layer) of the PDCP layer.
  • the UE 100 in the connected mode performs a recording process (logging) for recording the PDCP packet transmission time information (Time Stamp start) together with the identification information of the PDCP packet.
  • the transmission time information (Time Stamp start) is information indicating the time when a PDCP packet arrives at the PDCP layer from the upper layer of the PDCP layer.
  • the identification information is a sequence number (PDCP SN) in the PDCP packet.
  • the UE 100 records the time stamp start indicating the time together with the PDCP SN.
  • FIG. 5 shows an example in which the UE 100 records PDCP SN and Time Stamp start for each PDCP SDU of sequence numbers (SN) 1 to X and holds it as record information (log).
  • ENB200 performs the process which receives a PDCP packet (Packet) from UE100.
  • the eNB 200 performs a recording process of recording the PDCP packet reception time information (Time Stamp end) together with the identification information of the PDCP packet.
  • the reception time information (Time Stamp end) is the time when the PDCP packet (PDCP PDU) arrives at the PDCP layer from the lower layer (RLC layer) of the PDCP layer, or the PDCP packet (PDCP SDU) from the PDCP layer to the upper layer of the PDCP layer Is information indicating the time at which was delivered.
  • FIG. 5 shows an example in which the eNB 200 records PDCP SN and Time Stamp end) for each PDCP SDU of sequence numbers (SN) 1 to X and holds it as record information (log).
  • UE100 performs the reporting process which transmits the record information (log) which it hold
  • eNB200 receives recording information from UE100.
  • the eNB 200 associates the record information received from the UE 100 with the record information held by the own eNB 200.
  • the recording information received from the UE 100 includes a plurality of combinations of PDCP SN and Time Stamp start.
  • the record information held by the own eNB 200 includes a plurality of combinations of PDCP SN and Time Stamp end.
  • the eNB 200 associates Time Stamp start and Time Stamp end with each PDCP SN.
  • FIG. 5 illustrates an example in which the eNB 200 associates the Time Stamp start and the Time Stamp end with respect to each PDCP SDU having the sequence numbers (SN) 1 to X.
  • the recorded information associated in this way or the uplink latency calculated based on the information may be referred to as an uplink latency measurement result.
  • Time Stamp start and Time Stamp end indicates the delay time (ie, uplink latency) required for the PDCP packet to be transmitted from the PDCP layer of UE 100 to the PDCP layer of eNB 200. Therefore, it is possible to grasp the uplink latency for each PDCP packet.
  • the UE 100 and the eNB 200 perform the recording process, the information for uplink latency measurement is not transmitted / received. Therefore, uplink latency measurement with reduced overhead can be realized.
  • an apparatus other than the eNB 200 may perform the association.
  • An apparatus other than the eNB 200 is, for example, a TCE (Trace Collection Entity).
  • the eNB 200 transmits the recording information of the UE 100 and the recording information of the own eNB 200 to the TCE.
  • the TCE associates the recording information of the UE 100 with the recording information of the eNB 200.
  • ENB200 transmits the setting information (configuration) of uplink latency measurement to UE100.
  • the eNB 200 transmits the setting information by dedicated RRC signaling addressed to the UE 100.
  • the setting information includes network absolute time information (Network absolute time stamp).
  • the absolute time information is information indicating a set time (absolute time) managed by the network.
  • the transmission time information (Time Stamp start) recorded by the UE 100 is based on the absolute time indicated by the absolute time information.
  • the transmission time information may be an absolute time calculated based on the absolute time, or a relative value (relative time) from the absolute time. In the case of relative time, the UE 100 needs to include the absolute time in the recording information (log). Therefore, it is possible to obtain accurate transmission time information (Time Stamp start) by including the absolute time information of the network in the setting information.
  • the setting information includes a sequence number (PDCP SN) of a specific PDCP packet for which recording processing (logging) is to be started.
  • the UE 100 starts the recording process from a specific PDCP packet having the PDCP SN specified by the setting information. Thereby, UE100 can start a recording process appropriately.
  • the setting information may include a sequence number (PDCP SN) of a specific PDCP packet for which the recording process is to be terminated.
  • the UE 100 continues the recording process up to a specific PDCP packet having the PDCP SN specified by the setting information.
  • the setting information may include the number of PDCP packets to be recorded.
  • the UE 100 continues the recording process for the number of PDCP packets specified by the setting information.
  • the setting information may include a period during which the recording process is to be performed.
  • the UE 100 continues the recording process for the period specified by the setting information. Therefore, the UE 100 can appropriately continue the recording process and end.
  • setting information may further include information indicating a report processing condition (trigger). Such information will be described later.
  • FIG. 6 is a diagram for explaining the operation of the UE 100 related to the designation of the PDCP SN.
  • the eNB 200 gives the UE 100 the sequence number (SN start) of the specific PDCP packet for which the recording process is to be started and the sequence number (SN end) of the specific PDCP packet for which the recording process is to be ended.
  • SN start sequence number of the specific PDCP packet for which the recording process is to be started
  • SN end sequence number of the specific PDCP packet for which the recording process is to be ended.
  • An example of setting is assumed.
  • PDCP SN has a bit length of 5 bits and can take a value from “00000” to “11111”. When the PDCP SN reaches “11111”, the next PDCP SN returns to “00000”. That is, PDCP SN is used cyclically.
  • the eNB 200 designates “01000” as the SN start and “10011” as the SN end.
  • the PDCP SNs from “01000” to “11111” and the PDCP SNs from “00000” to “10011” are specified as the targets of the recording process.
  • the eNB 200 designates the PDCP SN that has made one rotation with respect to the SNCP PDCP SN as SN end.
  • the UE 100 cannot grasp the intention of the eNB 200. Specifically, it is unknown whether or not the designated SN end is the one after the SN start. Therefore, if the operation of the UE 100 in such a case is not specified, an unexpected error may occur.
  • the UE 100 considers that SN start and SN end are specified within a range in which PDCP SN does not rotate once. Therefore, the UE 100 understands that the PDCP SN from “01000” to “10011” is the target of the recording process within a range in which the PDCP SN does not rotate once. As a result, an unexpected error can be prevented.
  • the UE 100 may include location information and radio environment information in the recording information (log).
  • the position information is detailed position information obtained using, for example, a GNSS receiver.
  • the radio environment information is, for example, reference signal received power (RSRP) and reference signal received quality (RSRQ). This makes it possible to achieve more appropriate network optimization.
  • RSRP reference signal received power
  • RSSQ reference signal received quality
  • the eNB 200 may be configured to report location information and radio environment information to the UE 100 that sets uplink latency measurement using Immediate MDT. Specifically, the eNB 200 instructs the UE 100 to include location information in a measurement report (Measurement Report) of radio environment information. The UE 100 includes the position information in the measurement report (Measurement Report) and transmits it to the eNB 200. The position information and wireless environment information obtained in this way may be referred to as Immediate MDT results. The network (eNB 200 or TCE) associates the uplink latency measurement result with the Immediate MDT result.
  • Option 1 The UE 100 immediately transmits the record information to the network.
  • Option 2 The UE 100 transmits recording information at a predetermined time interval (for example, 1 minute).
  • Option 3 The UE 100 transmits the record information at a time interval specified by the setting information for uplink latency measurement.
  • Option 4 The UE 100 transmits the record information when the measurement end condition specified in the setting information for uplink latency measurement is satisfied.
  • Measurement end condition is satisfied means that, for example, when a specific PDCP SN to be ended is specified, the measurement of the specific PDCP SN is completed, and the PDCP packet to be recorded is to be processed.
  • the number it means that the measurement of the number of PDCP packets is completed.
  • Option 5 When the measurement event designated by the setting information for uplink latency measurement is completed, the UE 100 transmits an indicator (log available indicator) indicating that the record information is retained.
  • an indicator log available indicator
  • the UE 100 holds record information and transmits log availability when a predetermined RRC event (RRC connection setup, RRC connection re-establishment, RRC connection re-configuration) occurs.
  • a predetermined RRC event RRC connection setup, RRC connection re-establishment, RRC connection re-configuration
  • the UE 100 records the record information when a predetermined RRC event occurs. You may transmit the indicator (log available indicator) of having hold
  • eNB200 which received log available indicator requests
  • UE100 transmits recording information to eNB200 according to the request
  • FIG. 7 is a diagram illustrating a first modification example of the uplink latency measurement according to the first embodiment.
  • the UE 100 adds information (Tag) indicating that the recording process is performed to each PDCP packet on which the recording process (logging) is performed.
  • Tag is 1-bit flag information.
  • the UE 100 transmits the PDCP packet to which the Tag is added to the eNB 200.
  • the eNB 200 can grasp the PDCP packet that the UE 100 is performing the recording process based on the Tag.
  • the configuration information (configuration) for uplink latency measurement includes the sequence number (PDCP SN) of a specific PDCP packet for which the recording process is to be started or a specific end condition for which the recording process is to be ended. Or both.
  • FIG. 8 is a diagram illustrating a second modification example of the uplink latency measurement according to the first embodiment.
  • the UE 100 adds information (Tag start) indicating the start of the recording process to the PDCP packet P1 related to the start of the recording process. Also, the UE 100 adds information (Tag end) indicating the end of the recording process to the PDCP packet P2 related to the end of the recording process.
  • the PDCP packet P1 related to the start of the recording process is a PDCP packet for which the recording process has been started.
  • the PDCP packet P2 related to the end of the recording process may be a PDCP packet immediately after the end of the recording process, or may be a PDCP packet immediately before the end of the recording process (last).
  • UE 100 transmits PDCP packet P1 to which Tag start is added to eNB 200, and transmits PDCP packet P2 to which Tag end is added to eNB 200. Based on Tag start and Tag end, the eNB 200 can grasp the PDCP packet in which the UE 100 is performing the recording process.
  • the configuration information (configuration) for uplink latency measurement includes the sequence number (PDCP SN) of a specific PDCP packet for which the recording process is to be started or a specific end condition for which the recording process is to be ended. Or both.
  • FIG. 9 is a diagram illustrating a third modification example of the uplink latency measurement according to the first embodiment.
  • the UE 100 adds tag numbers (Tag 1 to Tag X) for identifying the PDCP packets to each PDCP packet to be recorded.
  • the UE 100 records the tag number added by the own UE 100 as the identification information of the PDCP packet instead of the PDCP SN.
  • the eNB 200 records the tag number added by the UE 100 as the identification information of the PDCP packet instead of the PDCP SN.
  • this modification for example, by making the bit length of the tag number longer than the bit length of the PDCP SN, more PDCP packets can be uniquely identified by the tag number.
  • FIG. 10 is a diagram illustrating a fourth modification example of the uplink latency measurement according to the first embodiment.
  • the UE 100 confirms that the PDCP packet reception process is completed based on the ACK response transmitted from the eNB 200, and sets the time related to the confirmation to the reception time information (Time Record as Stamp end). Specifically, UE100 confirms that eNB200 received the said PDCP packet correctly by monitoring the ACK response which the MAC layer or RLC layer of self-UE100 receives from eNB200 for every PDCP packet. The time when the confirmation is completed is recorded as reception time information (Time Stamp end). And UE100 records the identification information of a PDCP packet, the transmission time information (Time Stamp start) of the said PDCP packet, and reception time information (Time Stamp end) for every PDCP packet.
  • the UE 100 when the UE 100 transmits the PDCP packet P having PDCP SN1 to the eNB 200, the UE 100 records PDCP SN1 and corresponding transmission time information (Time Stamp start). When the UE 100 receives one or more ACK responses corresponding to the PDCP packet P, the UE 100 further records reception time information (Time Stamp end) corresponding to PDCP SN1. The UE 100 performs the same process for each PDCP packet of PDCP SN2 to PDCP SNX. Then, UE100 transmits record information (log) to eNB200.
  • Time Stamp start transmission time information
  • the UE 100 receives one or more ACK responses corresponding to the PDCP packet P
  • the UE 100 further records reception time information (Time Stamp end) corresponding to PDCP SN1.
  • the UE 100 performs the same process for each PDCP packet of PDCP SN2 to PDCP SNX. Then, UE100 transmits record information (log) to eNB200
  • the fourth modification it is possible to realize uplink latency measurement only by the recording process on the UE 100 side without performing the recording process on the eNB 200 side.
  • the second embodiment is an embodiment in which the operation according to the first embodiment or a modification thereof is applied to double connection communication (Dual Connectivity).
  • FIG. 11 is a diagram illustrating uplink double connection communication according to the second embodiment.
  • FIG. 11 illustrates a user plane protocol stack. Also, in FIG. 11, the physical layer entities are not shown.
  • the double connection communication is a communication mode in which a master cell group (MCG) and a secondary cell group (SCG) are set in the UE 100 in the RRC connected mode.
  • MCG is a serving cell group managed by MeNB200M (master base station).
  • SCG is a serving cell group managed by SeNB200S (secondary base station).
  • UE100 connects to MeNB200M and SeNB200S, and receives resource allocation from each of the scheduler of MeNB200M and the scheduler of SeNB200S.
  • MeNB200M has RRC connection with UE100, and can transmit / receive an RRC message with UE100.
  • SeNB200S does not have the RRC connection with UE100, and cannot transmit / receive an RRC message with UE100.
  • MeNB200M may be a macro cell base station, and SeNB200M may be a small cell base station.
  • MeNB200M and SeNB200S are mutually connected via X2 interface.
  • Each of the MeNB 200M and the SeNB 200S is connected to the S-GW via the S1 interface (S1-U interface).
  • MeNB200M is connected with MME via S1 interface (S1-MME interface).
  • MCG bearer is a bearer in which a corresponding radio protocol exists only in the MeNB 200M and uses only the resources of the MeNB 200M.
  • SCG bearer is a bearer in which a corresponding radio protocol exists only in the SeNB 200S and uses only resources of the SeNB 200S.
  • the split bearer is a bearer in which a corresponding radio protocol exists in both the MeNB 200M and the SeNB 200S and uses both resources of the MeNB 200M and the SeNB 200S.
  • the data of the MCG bearer is processed in the order of the PDCP entity 11, the RLC entity 21, and the MAC entity 31 of the UE 100 and transmitted to the MeNB 200M.
  • the data of the MCG bearer is processed in the order of the MAC entity 41, the RLC entity 51, and the PDCP entity 61 of the MeNB 200M and transferred to the S-GW.
  • the data of the SCG bearer is processed in the order of the PDCP entity 13 of the UE 100, the RLC entity 24, and the MAC entity 32 and transmitted to the SeNB 200S.
  • the data of the SCG bearer is processed in the order of the MAC entity 42, the RLC entity 54, and the PDCP entity 63 of the SeNB 200S and transferred to the S-GW.
  • the split bearer data is distributed to the RLC entity 22 for the MeNB 200M (MCG) and the RLC entity 23 for the SeNB 200S (SCG) in the PDCP entity 12 of the UE 100.
  • the PDCP entity 12 converts PDCP SDU (Service Data Unit) into PDCP PDU (Protocol Data Unit) and distributes each PDCP PDU to either the RLC entity 22 or the RLC entity 23 (routing).
  • the PDCP entity 12 transmits the split bearer data to the MeNB 200M via a first transmission path (hereinafter referred to as “MCG path”) and a second transmission path (hereinafter referred to as “MCG path”).
  • MCG path first transmission path
  • MCG path second transmission path
  • the RLC entity 22 receives the PDCP PDU distributed by the PDCP entity 12 as an RLC SDU, converts the RLC SDU into an RLC PDU, and outputs the RLC SDU to the MAC entity 31.
  • the MAC entity 31 receives the RLC PDU output from the RLC entity 22 as a MAC SDU, converts the MAC SDU into a MAC PDU, and transmits it to the MeNB 200M via a physical layer entity (not shown).
  • the RLC entity 23 receives the PDCP PDU distributed by the PDCP entity 12 as an RLC SDU, converts the RLC SDU into an RLC PDU, and outputs the RLC SDU to the MAC entity 32.
  • the MAC entity 32 receives the RLC PDU output from the RLC entity 23 as a MAC SDU, converts the MAC SDU into a MAC PDU, and transmits it to the SeNB 200S via a physical layer entity (not shown).
  • the MAC entity 42 of the SeNB 200S receives a MAC PDU via a physical layer entity (not shown), converts the MAC PDU into a MAC SDU, and outputs the MAC PDU to the RLC entity 53.
  • the RLC entity 53 receives the MAC SDU output from the MAC entity 42 as an RLC PDU, converts the RLC PDU into an RLC SDU, and outputs the RLC PDU to the PDCP entity 62 of the MeNB 200M via the X2 interface.
  • the MAC entity 42 of the MeNB 200M receives the MAC PDU via a physical layer entity (not shown), converts the MAC PDU into a MAC SDU, and outputs the MAC PDU to the RLC entity 52.
  • the RLC entity 52 receives the MAC SDU output from the MAC entity 41 as an RLC PDU, converts the RLC PDU into an RLC SDU, and outputs the RLC PDU to the PDCP entity 62.
  • the PDCP entity 62 receives the RLC SDU output from the RLC entity 52 of the MeNB 200M as a PDCP PDU (MCG path), and receives the RLC SDU output from the RLC entity 53 of the SeNB 200S as a PDCP PDU (SCG path).
  • the PDCP entity 62 converts PDCP PDUs into PDCP SDUs while performing rearrangement processing (so-called PDCP reordering) of PDCP PDUs (MCG paths) and PDCP PDUs (SCG paths).
  • MeNB200M receives a PDCP packet directly from UE100 (MCG path), or receives from UE100 via SeNB200S (SCG path). MeNB200M associates the information which shows whether a PDCP packet is via SeNB200S with reception time information (Time Stamp end) and identification information (PDCP SN). Thereby, it is possible to perform uplink latency measurement individually for the MCG path and the SCG path.
  • the MeNB 200M may perform the recording process by dividing the PDCP packet received via the SeNB 200S from the PDCP packet directly received from the UE 100. Or MeNB200M does not need to perform a recording process about the PDCP packet received via SeNB200S.
  • the UE 100 transmits the PDCP packet to one of the MeNB 200M and the SeNB 200S.
  • the UE 100 may associate information indicating whether the one eNB is the MeNB 200M or the SeNB 200S with the transmission time information (Time Stamp start) and the identification information (PDCP SN).
  • the UE 100 records the identifier of the MCG path / SCG path together with transmission time information (Time Stamp start) and identification information (PDCP SN).
  • UE100 may perform a recording process separately about a MCG path
  • the third embodiment is an embodiment that considers the handover of the UE 100.
  • the UE 100 discards the configuration information (configuration) related to the uplink latency measurement and does not continue the recording process (logging) at the time of handover.
  • the UE 100 discards the setting information, the UE 100 discards the record information (log).
  • the UE 100 may discard the setting information or hold the recording information. In this case, the UE 100 may transmit the recording information to the target eNB after the handover. Moreover, UE100 may transmit log available indicator to the target eNB, and may transmit recording information to the target eNB in response to a request from the target eNB.
  • the source eNB may notify the target eNB that the uplink latency measurement is applied to the UE 100 using the UE context information.
  • the target eNB may request the UE 100 to cancel the recording process as necessary, and sends new configuration information (configuration) for uplink latency measurement to the UE 100. May be sent to.
  • the UE 100 may discard the stored recording information (log), or store the stored recording information. You may transmit to the target eNB.
  • the target eNB retains the retained recording before requesting the UE 100 to stop the recording process or before transmitting new setting information for uplink latency measurement to the UE 100.
  • the UE 100 may be requested to transmit information.
  • the target eNB may request the UE 100 to continue the recording process as necessary.
  • FIG. 12 is a sequence diagram showing an operation pattern 2-2 of the third embodiment. In the initial state of this sequence, the UE 100 performs recording processing (logging) based on the setting information from the source eNB 200-1.
  • the source eNB 200-1 determines the handover of the UE 100 to the target eNB 200-2 based on the measurement result (Measurement Report) (S301 to S303).
  • the source eNB 200-1 transmits a handover request to the target eNB 200-2 (S304).
  • the handover request includes UE context information (Handover Preparation) including setting information (configuration) set in the UE 100 by the source eNB 200-1.
  • the target eNB 200-2 generates an RRC container including new configuration information (configuration) for uplink latency measurement (S305). Further, the target eNB 200-2 transmits a handover request ACK response including the RRC container (Handover Command) to the source eNB 200-1 (S306). The source eNB 200-1 transmits a handover instruction including the RRC container (Handover Command) to the UE 100 (S307, S308). Thus, the target eNB 200-2 notifies the UE 100 of new setting information for uplink latency measurement via the source eNB 200-1 before the handover.
  • the UE 100 performs a process of switching the connection destination to the target eNB 200-2 (S309).
  • the source eNB 200-1 performs a forwarding process for transferring untransmitted data (PDCP packet) addressed to the UE 100 to the target eNB 200-2 (S310 to S312).
  • the target eNB 200-2 records the PDCP SN for each PDCP packet transferred (forwarded) from the source eNB 200-1. Note that the recording information before the handover may be sent from the target eNB 200-2 to the source eNB 200-1.
  • the target eNB 200-2 performs a recording process on the PDCP packet received from the UE 100 after the handover, and records the PDCP SN.
  • the UE 100 transmits recording information (log) obtained by performing the recording process for each of the source eNB 200-1 and the target eNB 200-2 to the target eNB 200-2 (S313).
  • the target eNB 200-2 distinguishes between the pre-handover and post-handover based on the PDCP SN for the recording information received from the UE 100 (S314).
  • the target eNB 200-2 identifies recording information in which each PDCP packet transferred from the source eNB 200-1 matches the PDCP SN as recording information before handover.
  • MDT provides the ability for the NW to collect information such as radio measurements and QoS measurements, along with location information that can assist operators in optimizing their networks.
  • information such as radio measurements and QoS measurements, along with location information that can assist operators in optimizing their networks.
  • one of the main subjects is to determine the goal of network optimization. It was understood that the goal for network optimization should be to maintain not only jitter, but also average latency within appropriate limits. This is because GBR type traffic is particularly sensitive to delay related jitter. Therefore, it should be determined whether the NW needs to know if jitter is a problem or if only problems related to queue delay are sufficient. This should consider which measurements are needed, ie UL delay or just queue delay. If the root cause of the problem is not due to a schedule, it should be borne in mind that queue delay measurement alone may not be sufficient. If jitter needs to be evaluated, one of two options should be considered.
  • Option 1 UE measures queue delay while NW evaluates HARQ delay based on BLER.
  • Option 2 The UE and / or NW measures the entire UL latency including both queue delay and HARQ delay.
  • Proposal 1 It should be determined whether the NW needs to know whether jitter is an issue or whether the queue delay measurement is sufficient.
  • Option 1-1 The UE logs a queue delay measurement along with a time stamp and other support information and reports it later.
  • Option 2-1 Both the UE and / or NW log the time stamp associated with each PDCP SDU and report it later.
  • the UE may also log other assistance information.
  • Option 2-1 An example of how Option 2-1 is realized is illustrated in FIG.
  • both the UE and the eNB record time stamps with PDCP SN on each other in the log report.
  • the actual PDCP SDU does not need to be logged.
  • either the eNB or the TCE can calculate the UL latency based on logs from both the UE and the eNB.
  • option 1-1 only the UE will log the measurement associated with the queue delay with a type stamp. However, as previously explained, further log acquisition on the eNB side may be required if HARQ delay information is also required based on the decision in Proposition 1.
  • option 1 and option 2 in section 2.1 have advantages and disadvantages. For example, if option 1 is applied, NW complexity is increased because the NW needs to combine measurements tracked by different entities to obtain jitter information. On the other hand, if the eNB is also associated with UL latency measurement, Option 2 may increase the complexity of the eNB. In any case, further research is needed for both options, and details should be defined in the WI phase.
  • Proposal 2 RAN2 does not require real-time processing for UL latency measurement, and as one possible solution for UL latency measurement, post-processing procedure is acquired in TR during SI phase You should agree that it should.
  • Proposal 1 RAN2 should determine whether the NW needs to know whether jitter is an issue or whether the queue delay measurement is sufficient.
  • Proposal 2 RAN2 is one of the possible solutions for UL latency measurement that real-time processing is not necessary for UL latency measurement and that the post-processing procedure is in TR during the SI phase. It should be agreed that it should not be acquired as.
  • the eNB sets M1 and / or M2 and / or performs M3.
  • -TCE calculates the average delay of the measurement results and the delay jitter for each packet.
  • the TCE has determined whether the UL latency measurement is an abnormal value, but the TCE sees any problem with the M2 and M3 measurement results corrected at the same timing using the UL latency. Rather, TCE understands that the scheduling algorithm has several problems.
  • the eNB performs a per-packet HARQ BLER measurement using the time stamp.
  • the UE provides the UL latency measurement result with the location information to the TCE via the eNB, and the eNB provides the HARQ BLER measurement result with the target UE ID to the TCE.
  • TCE combines these based on the time stamp of each measurement result.
  • -TCE calculates UL delay jitter information.
  • the eNB should be allowed to trigger an “early congestion warning” for vocoder rate adaptation based on the UL delay information exceeding a threshold. It is. The eNB should be allowed to trigger an “early congestion warning” in cases where the M2 and M3 measurement results exceed the threshold or the HARQ BLER measurement results exceed the threshold.
  • the present invention is useful in the field of wireless communication.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un terminal sans fil, selon un mode de réalisation de la présente invention, est pourvu d'une unité de commande qui effectue un procédé de transmission d'un paquet de protocole de convergence de données par paquets (PDCP) vers une station de base. L'unité de commande réalise un procédé d'enregistrement consistant à enregistrer des informations de temps de transmission pour le paquet PDCP conjointement avec des informations d'identification pour le paquet PDCP.
PCT/JP2016/073298 2015-08-11 2016-08-08 Terminal sans fil et station de base Ceased WO2017026444A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562203611P 2015-08-11 2015-08-11
US62/203,611 2015-08-11

Publications (1)

Publication Number Publication Date
WO2017026444A1 true WO2017026444A1 (fr) 2017-02-16

Family

ID=57984522

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/073298 Ceased WO2017026444A1 (fr) 2015-08-11 2016-08-08 Terminal sans fil et station de base

Country Status (1)

Country Link
WO (1) WO2017026444A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020530691A (ja) * 2017-08-10 2020-10-22 コンヴィーダ ワイヤレス， エルエルシー 新無線におけるコネクテッドモードのモビリティ
WO2023100981A1 (fr) * 2021-12-01 2023-06-08 シャープ株式会社 Dispositif terminal, procédé et circuit intégré

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100296449A1 (en) * 2007-12-20 2010-11-25 Ntt Docomo, Inc. Mobile station, radio base station, communication control method, and mobile communication system
WO2014084499A1 (fr) * 2012-11-29 2014-06-05 Lg Electronics Inc. Procédé de mesure de latence et appareil associé
US20150208235A1 (en) * 2014-01-17 2015-07-23 Samsung Electronics Co., Ltd. Dual connectivity mode of operation of a user equipment in a wireless communication network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100296449A1 (en) * 2007-12-20 2010-11-25 Ntt Docomo, Inc. Mobile station, radio base station, communication control method, and mobile communication system
WO2014084499A1 (fr) * 2012-11-29 2014-06-05 Lg Electronics Inc. Procédé de mesure de latence et appareil associé
US20150208235A1 (en) * 2014-01-17 2015-07-23 Samsung Electronics Co., Ltd. Dual connectivity mode of operation of a user equipment in a wireless communication network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "UL latency measurement in MDT", 3GPP TSG-RAN WG2 MEETING #90 R2-152296, 25 May 2015 (2015-05-25), XP050971406 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020530691A (ja) * 2017-08-10 2020-10-22 コンヴィーダ ワイヤレス， エルエルシー 新無線におけるコネクテッドモードのモビリティ
JP7319962B2 (ja) 2017-08-10 2023-08-02 アイピーエルエー ホールディングス インコーポレイテッド 新無線におけるコネクテッドモードのモビリティ
US11765626B2 (en) 2017-08-10 2023-09-19 Ipla Holdings Inc. Connected mode mobility in new radio
US12127045B2 (en) 2017-08-10 2024-10-22 Ipla Holdings Inc. Connected mode mobility in new radio
WO2023100981A1 (fr) * 2021-12-01 2023-06-08 シャープ株式会社 Dispositif terminal, procédé et circuit intégré

Similar Documents

Publication Publication Date Title
US11825338B2 (en) Dynamic link selection
US10492110B2 (en) Long term evolution radio access network
EP3944670A1 (fr) Procédé et appareil de traitement de services côté scg dans un scénario de connectivité double
JP7249780B2 (ja) 端末機及び端末機の通信方法
US20160338074A1 (en) Method and Apparatus of Latency Measurement for LTE-WLAN Aggregation
US9055505B2 (en) Method and apparatus in which a terminal transmits a channel estimation result in a mobile communication system
US8738001B2 (en) Handover procedure in a coordinated multipoint (CoMP) transmission network
US20170013650A1 (en) Secondary base station, mobile station, communication control method, and master base station
US20100189075A1 (en) Base station and method for mobile communication system
WO2016185946A1 (fr) Dispositif réseau et station de base
WO2016185986A1 (fr) Terminal d'utilisateur
US20160323762A1 (en) Measurement control method
JP6741966B2 (ja) 通信装置
JP7058716B2 (ja) ユーザ装置
US20220386196A1 (en) Method and device for handing over terminal in wireless communication system using artificial intelligence
KR20160131065A (ko) 파라미터 측정 장치, 기지국 및 통신 시스템
CN104247550B (zh) 一种数据的传输方法、通信设备和通信系统
WO2017026444A1 (fr) Terminal sans fil et station de base
US12432616B2 (en) Radio network node, network node, and methods performed in a wireless communication network
WO2016163475A1 (fr) Terminal d'utilisateur et station de base

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: 16835141

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16835141

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP