WO2016104311A1 - Wireless communication terminal, communication control method, and network device - Google Patents

Wireless communication terminal, communication control method, and network device Download PDF

Info

Publication number
WO2016104311A1
WO2016104311A1 PCT/JP2015/085317 JP2015085317W WO2016104311A1 WO 2016104311 A1 WO2016104311 A1 WO 2016104311A1 JP 2015085317 W JP2015085317 W JP 2015085317W WO 2016104311 A1 WO2016104311 A1 WO 2016104311A1
Authority
WO
WIPO (PCT)
Prior art keywords
data communication
emergency data
wireless communication
emergency
communication terminal
Prior art date
Application number
PCT/JP2015/085317
Other languages
French (fr)
Japanese (ja)
Inventor
慎吾 片桐
和也 金野
裕二 井口
Original Assignee
京セラ株式会社
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 京セラ株式会社 filed Critical 京セラ株式会社
Publication of WO2016104311A1 publication Critical patent/WO2016104311A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present invention relates to a wireless communication terminal, a communication control method, and a network device, and more particularly, wireless communication that realizes QoS sufficient for data communication when urgency and / or real-time performance is required, such as emergency use.
  • the present invention relates to a terminal, a communication control method, and a network device.
  • LTE Long Term Evolution
  • the LTE system includes a UE (User Equipment) that is a radio communication terminal, an eNB (evolved Node B) that is a radio communication base station, and an EPC (Evolved Packet Core) that is an IP (Internet Protocol) -based core network.
  • UE User Equipment
  • eNB evolved Node B
  • EPC Evolved Packet Core
  • IP Internet Protocol
  • VoLTE Voice over LTE
  • IP Internet protocol
  • a procedure for handling high priority emergency calls with the highest priority is defined.
  • the voice at the time of VoLTE is recognized as an application that is difficult to be cut off, and the priority 1 that is the highest priority in QCI (Quality of service class identifier) is assigned.
  • QCI Quality of service class identifier
  • data communication for example, a TCP-based service / application defined in 3GPP TS23.203 rel.12.
  • a lower priority for example, VoIP, VoLTE
  • QCI QoS
  • GRR Guaranteed bit rate
  • QCI QoS
  • QoS QoS
  • it is normal data communication (thing which does not require real-time property or urgency, for example, web browsing), there is no problem even with QoS corresponding to the QCI.
  • the present invention has been made to solve the above-described problems, and realizes QoS sufficient for data communication in data communication when urgency and / or real-time performance is required, such as emergency use. With the goal.
  • One aspect of a wireless communication terminal requests a network device to perform emergency data communication, and a service quality class corresponding to the emergency data communication transmitted from the network device in response to the request
  • a control unit is provided that receives an identifier (QCI) and performs a process of performing the emergency data communication via the network device based on the service quality class identifier.
  • QCI an identifier
  • the service quality class identifier corresponding to the emergency data communication is a service quality class identifier dedicated to the emergency data communication.
  • One aspect of the wireless communication terminal includes a service quality class identifier dedicated to the emergency data communication, wherein the service quality class identifier dedicated to the emergency data communication is stored in a memory of the network device. Assigned based on the QCI characteristic table.
  • the service quality class identifier corresponding to the emergency data communication is a service quality class identifier shared with other applications.
  • the service quality class identifier also used as the other application is stored in a memory of the network device, and the other application And the QCI characteristic table including the emergency data communication.
  • At least a higher priority than normal data communication is assigned to the service quality class identifier corresponding to the emergency data communication.
  • control unit performs a process of requesting execution of emergency data communication to the network device when an emergency call is transmitted.
  • the control unit when the control unit requests the network device to execute the emergency data communication, the PDN Connectivity Request corresponding to the emergency data communication is transmitted to the network device. Performs transmission processing to the device.
  • the PDN Connectivity Request corresponding to the emergency data communication is a PDN Connectivity Request including a specific access point name (APN) corresponding to the emergency data communication.
  • APN access point name
  • the control unit transmits a PDN Connectivity Request corresponding to the emergency call when an emergency call is made, and then the PDN Connectivity corresponding to the emergency data communication. Processing to send a Request is performed.
  • One aspect of the wireless communication terminal according to the present invention is a process in which the control unit transmits a PDN Connectivity Request corresponding to the emergency call and corresponding to the emergency data communication when an emergency call is made. Do.
  • the network device when executing emergency data communication, the network device is requested to execute another application corresponding to the emergency data communication, and in response to the request Control that receives a quality of service class identifier (QCI) corresponding to the other application transmitted from the network device, and performs a process of communicating the emergency data via the network device based on the service quality class identifier A part.
  • QCI quality of service class identifier
  • the wireless communication terminal requests the network device to execute emergency data communication (a), and the network device corresponds to the emergency data communication. (B) transmitting a quality of service class identifier (QCI) to the wireless communication terminal; and when the wireless communication terminal receives the quality of service class identifier (QCI), based on the quality of service class identifier, the network And (c) performing the emergency data communication through a device.
  • QCI quality of service class identifier
  • the wireless communication terminal corresponding to the emergency data communication responds to the request by the emergency communication
  • a control unit is provided for performing a process of transmitting a quality of service class identifier (QCI) to be used for data communication to the wireless communication terminal.
  • QCI quality of service class identifier
  • FIG. 10 is a diagram illustrating a control procedure when emergency data is transmitted from a UE in the LTE system according to the first embodiment.
  • 3 is a diagram illustrating a QCI characteristic table used in the LTE system according to Embodiment 1.
  • FIG. 6 is a diagram showing a QCI characteristic table used in the LTE system according to the first modification of the first embodiment.
  • FIG. 10 is a diagram illustrating a control procedure when emergency data is transmitted from the UE in the LTE system according to the second modification of the first embodiment.
  • FIG. 10 is a diagram illustrating a control procedure when an emergency call is transmitted from a UE in the LTE system according to the second embodiment.
  • FIG. 10 is a diagram illustrating a control procedure when an emergency call is transmitted from a UE in an LTE system according to a modification of the second embodiment.
  • FIG. 1 is a configuration diagram of an LTE system.
  • the LTE system includes a UE 100, an E-UTRAN (Evolved-UMTS Terrestria 1 Radio Access Network) 10, and an EPC 20.
  • the E-UTRAN 10 corresponds to a radio access network
  • the EPC 20 corresponds to a core network.
  • the E-UTRAN 10 and the EPC 20 constitute an LTE system network.
  • the UE 100 is a mobile radio communication terminal and performs radio communication with a connection destination cell (serving cell).
  • UE100 is corresponded to a user terminal.
  • the E-UTRAN 10 includes a plurality of eNBs 200 (200-1, 200-2, 200-3).
  • the eNB 200 manages one or a plurality of cells, and performs radio communication with the UE 100 that establishes a connection with a cell managed by the eNB 200.
  • “cell” is used as a term indicating a minimum unit of a radio communication area, and also as a term indicating a function of performing radio communication with the UE 100.
  • the eNB 200 has, for example, a radio resource management (RRM) function, a user data routing function, and a measurement control function for mobility control and scheduling.
  • RRM radio resource management
  • the EPC 20 includes a plurality of MME (Mobility Management Entity) / S-GW (Serving-Gateway) 300 (300-1, 300-2).
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • the MME is a network node that performs various types of mobility control for the UE 100, and corresponds to a control station.
  • the S-GW is a network node that performs transfer control of user data, and corresponds to an exchange.
  • the eNB 200 is connected to each other via the interface X2.
  • the eNB 200 is connected to the MME / S-GW 300 via the interface S1.
  • FIG. 2 is a block diagram showing the configuration of the UE 100.
  • the UE 100 includes a plurality of antennas 101, a radio transceiver 110, a user interface 120, a GNSS (Global Navigation Satellite System) receiver 130, a battery 140, a memory 150, and a processor 160.
  • GNSS Global Navigation Satellite System
  • the UE 100 may not have the GNSS receiver 130.
  • the memory 150 may be integrated with the processor 160, and this set (that is, a chip set) may be used as the processor 160 ′.
  • the plurality of antennas 101 and the wireless transceiver 110 are used for transmitting and receiving wireless signals.
  • the radio transceiver 110 includes a transmission unit 111 that converts a baseband signal (transmission signal) output from the processor 160 into a radio signal and transmits the radio signal from a plurality of antennas 101.
  • the radio transceiver 110 includes a receiving unit 112 that converts radio signals received by the plurality of antennas 101 into baseband signals (received signals) and outputs the baseband signals to the processor 160.
  • the user interface 120 is an interface with a user who owns the UE 100, and includes, for example, a display, a microphone, a speaker, and various buttons.
  • the user interface 120 receives an operation from the user and outputs a signal indicating the content of the operation to the processor 160.
  • the GNSS receiver 130 receives a GNSS signal and outputs the received signal to the processor 160 in order to obtain position information indicating the geographical position of the UE 100.
  • the battery 140 stores power to be supplied to each block of the UE 100.
  • the memory 150 stores a program executed by the processor 160 and information used for processing by the processor 160.
  • the processor 160 includes a signal processing unit 161 that performs signal processing such as modulation / demodulation and encoding / decoding of a baseband signal, and a control unit 162 that executes various programs by executing programs stored in the memory 150. Contains.
  • the control unit 162 performs a process for making an emergency call based on an operation through the user interface 120, which will be described later, and performs an emergency data communication under the control of the MME / S-GW. Control.
  • FIG. 3 is a block diagram showing the configuration of the MME / S-GW 300.
  • the MME / S-GW 300 includes a network interface 220, a memory 230, and a processor 240.
  • the network interface 220 is connected to the eNB 200 via the interface S1 (FIG. 1).
  • the memory 230 stores a program executed by the processor 240 and information used for processing by the processor 240.
  • the processor 240 includes a control unit 241 that receives an emergency call transmitted from the UE and performs a control operation for controlling the UE, and executes various controls for the UE described later.
  • the eNB and the MME / S-GW are collectively described as a network device (NW).
  • the UE and the eNB execute RRC Connection establishment processing S1.
  • the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • the RRC Connection establishment process S1 includes a procedure in which the eNB that has received the RRC Connection Request transmits the RRC Connection Setup to the UE, and the UE transmits the RRC Connection Setup Complete to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer (communication path) via the eNB with the MME / S-GW is executed subsequent to the RRC connection, illustration is omitted.
  • the PDN connection request process S2 is executed.
  • the UE transmits a PDN Connectivity Request with Req_type as Emergency to the MME / S-GW via the eNB.
  • the MME / S-GW Upon receiving the PDN Connectivity Request, the MME / S-GW executes a Default Bearer establishment process S3 for establishing a bearer for IMS signaling related to an emergency call (control signal related to call control), and Activate Default EPS BearerCerterCaster
  • the QCI value is included in the Request message and transmitted to the UE.
  • QCI 5 corresponding to IMS signaling for managing voice communication is assigned.
  • the MME / S-GW transmits an E-RAB Setup Request to the eNB, and the eNB transmits an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
  • the MME / S-GW executes a dedicated bearer establishment process S4 for establishing a bearer for voice data related to an emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Request Request message to the UE. Send.
  • QCI 1 corresponding to VoIP (Voice over IP) is assigned.
  • the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
  • FIG. 5 shows a basic (standard) QCI characteristic table.
  • bit rate is guaranteed (GBR, Non-GBR), priority (Priority (Level), packet delay budget (Packet Delay Budget), packet error loss rate (PELR) associated with the QCI value : Packet Error Loss Rate) and application (service) are shown.
  • VoIP VoiceLTE
  • VoIP is assigned the second priority level 2.
  • the transmission speed is also guaranteed and can be used stably.
  • FIG. 6 is a diagram illustrating a control procedure when the UE transmits emergency data in the LTE system according to the first embodiment.
  • eNB and MME / S-GW are collectively described as a network device (NW).
  • NW network device
  • an operation for emergency data transmission (emergency data communication start) is performed via the user interface 120 (FIG. 3) or an emergency
  • the UE and the eNB execute an RRC connection establishment process S11.
  • the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • the specific event that triggers the emergency data transmission is, for example, an emergency application.
  • the emergency application here is, for example, an in-vehicle camera device that has a communication function mounted on a vehicle and has an acceleration sensor or the like. This is an application that detects this with an acceleration sensor and transmits the image data before and after receiving an impact as emergency data to an external server or the like via a network device.
  • the emergency data transmission executed by this application is performed from the necessity of urgently transmitting the image data to an external server because there is a possibility that the in-vehicle camera device may be subsequently damaged in the case of a car accident.
  • the present invention is not limited to this, and the UE may be a communication module that transmits data received from the vehicle-mounted camera device via wire or wirelessly.
  • the acceleration sensor may not be provided in the in-vehicle camera device, but may be provided outside and configured to transmit the detection result to the in-vehicle camera device.
  • RRC Connection establishment process S11 there is also transmission of RRC Connection Setup from the eNB to the UE and transmission of RRC Connection Setup Complete from the UE to the eNB, but illustration is omitted.
  • a specific access point name (APN: Access Point Name) is included in the PDN Connectivity Request and transmitted.
  • the APN included in the PDN Connectivity Request is specified for emergency data communication by a network operator (communication carrier) or the like.
  • the MME / S-GW determines whether the APN included in the PDN Connectivity Request is compatible with emergency data communication. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If the MME / S-GW determines that the APN supports emergency data communication, for example, based on the QCI characteristic table shown in FIG. 7, a dedicated bearer is established to allocate a bearer for emergency data communication. Process S13 is performed and the bearer (QCI) matched with the emergency data communication (application) is allocated.
  • QCI bearer
  • FIG. 6 it is assumed that the UE is in an idle state. However, the present invention is not limited to this, and the UE may be in a null state or a connected state, and the UE is in a connected state. In this case, the transmission of the RRC Connection Request by the UE
  • the QCI has a value of 1 to 10 and the priority has a value of 1 to 10 due to the addition of the TCP protocol (emergency data communication) as an application.
  • TCP protocol electronic mail protocol
  • the present invention is not limited to this, and may be simply emergency data communication, and the emergency data communication may include the UDP protocol.
  • the packet delay budget is 150 ms, and the packet error loss rate is 10 ⁇ 3 . Needless to say, these values are only examples and may be changed to other values.
  • Modification 1 when the UE performs emergency data communication, the MME / S-GW has shown the configuration in which the QCI assignment is performed using the QCI characteristic table shown in FIG. Instead of setting a dedicated QCI and priority for emergency data communication, a QCI characteristic table including other applications and emergency data communication may be used as an application to which a specific QCI is applied.
  • FIG. 9 is a diagram illustrating a control procedure when the UE performs emergency data communication (emergency data transmission) in the LTE system according to the first modification of the first embodiment.
  • emergency data communication emergency data transmission
  • FIG. 9 in a UE in an idle state, for example, an operation for transmitting emergency data is performed via the user interface 120 (FIG. 3), or a trigger that triggers emergency data transmission
  • the UE and the eNB execute the RRC connection establishment process S11.
  • the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • the UE when the UE performs emergency data communication (emergency data is transmitted), in the PDN connection request processing S12, the UE performs PDN Connectivity Request with Req_type as Emergency, via the eNB, MME / S- When transmitting to the GW, the specific APN is included in the PDN Connectivity Request and transmitted.
  • the APN included in the PDN Connectivity Request is specified for real-time game use and emergency data communication by a network operator (communication carrier) or the like.
  • the MME / S-GW determines whether the APN included in the PDN Connectivity Request is compatible with emergency data communication. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If it is determined that the APN corresponds to emergency data communication or the like, for example, the QCI shown in FIG. In order to assign a bearer for emergency data communication or the like based on the characteristic table, the Dedicated Bearer establishment process S131 is executed, and the MME / S-GW is associated with the emergency data communication (application) (QCI). ).
  • application application
  • the emergency data communication is added to another existing application to which the QCI is assigned, instead of setting a dedicated QCI and priority for the emergency data communication. Therefore, the standardized QCI characteristic table can be handled without greatly changing, and the modification to the LTE system can be reduced.
  • the MME / S-GW has shown the configuration in which the QCI is assigned using the QCI characteristic table shown in FIG. Instead of setting a dedicated QCI and priority for emergency data communication, it may be configured to camouflage to an application to which a high-priority QCI is assigned when executing emergency data communication.
  • FIG. 10 is a diagram illustrating a control procedure when the UE transmits emergency data in the LTE system according to the second modification of the first embodiment.
  • the UE and the eNB perform RRC connection establishment processing. S11 is executed.
  • the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • the UE when the UE performs emergency data communication (emergency data is transmitted), in the PDN connection request processing S12, the UE performs PDN Connectivity Request with Req_type as Emergency, via the eNB through the MME / S. -When transmitting to the GW, include the specific APN in the PDN Connectivity Request.
  • the APN transmitted here is specified for a real-time game by a network operator or the like.
  • the MME / S-GW determines whether or not the APN included in the PDN Connectivity Request corresponds to the real-time game. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If it is determined that the APN corresponds to the real-time game, for example, the QCI characteristic table shown in FIG. Based on the above, a Dedicated Bearer establishment process S132 for establishing a bearer for a real-time game is executed, and the MME / S-GW assigns a bearer (QCI) associated with the real-time game (application).
  • QCI bearer
  • the MME / S-GW is based on the QCI characteristic table shown in FIG. 5 in the Activate Dedicated EPS Bearer Context Request message.
  • emergency data communication is standardized because it does not set a dedicated QCI or priority for emergency data communication, but camouflages the application to which a high-priority QCI is assigned.
  • QCI characteristic tables can be used, and fewer modifications are made to the LTE system.
  • Embodiment 2 In Embodiment 1 demonstrated above, the case where emergency data transmission was transmitted from UE in the LTE system was demonstrated. However, since the emergency data transmission is frequently used, there is a possibility that the speed of the truly urgent data communication may be delayed. Therefore, the execution of the emergency data communication may be limited. .
  • Embodiment 2 a configuration in which execution of emergency data communication is restricted will be described.
  • FIG. 11 is a diagram illustrating a control procedure when the UE transmits an emergency call in the LTE system according to the second embodiment.
  • the eNB and the MME / S-GW are collectively described as a network device (NW).
  • the UE and the eNB perform RRC Connection establishment process S21. Execute. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • RRC connection establishment process S21 there is an RRC connection setup transmission from the eNB to the UE and an RRC connection setup complete transmission from the UE to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer is executed following RRC Connection, illustration is omitted.
  • the UE After the default bearer establishment process for establishing a voice bearer enables data exchange between the UE and the MME / S-GW, the UE sets Req_type to Emergency in the first PDN connection request process S22. PDN Connectivity Request is transmitted to MME / S-GW via eNB.
  • the MME / S-GW Upon receiving the PDN Connectivity Request, the MME / S-GW executes a Default Bearer establishment process S23 for establishing a bearer for IMS signaling (control signal) related to an emergency call, and sends an Activate Default EPS Bearer Quest Request Queue Request Quest Request Queue Request Queue Request Message Include value and send to UE.
  • a Default Bearer establishment process S23 for establishing a bearer for IMS signaling (control signal) related to an emergency call, and sends an Activate Default EPS Bearer Quest Request Queue Request Quest Request Queue Request Queue Request Message Include value and send to UE.
  • QCI 5 corresponding to IMS signaling for managing voice communication is assigned.
  • the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
  • the MME / S-GW executes a dedicated bearer establishment process S24 for establishing a bearer for voice data related to the emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Request Request message to the UE.
  • QCI 1 corresponding to VoIP is assigned based on the standardized QCI characteristic table shown in FIG.
  • the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
  • the UE when calling the police, if the UE needs to execute emergency data communication (emergency data transmission), for example, when a traffic accident occurs, call the police.
  • emergency data communication emergency data transmission
  • the UE sends a PDN Connectivity Request with Req_type as Emergency in the second PDN connection request processing S25 via the eNB via the MME / S-GW.
  • a specific APN is included in the PDN Connectivity Request and transmitted.
  • the UE may determine that it is necessary to execute the emergency data communication described above (transmission of emergency data) when making a call to the police, that is, call the police.
  • emergency data communication emergency data transmission
  • the APN included in the PDN Connectivity Request is, for example, the APN specified for emergency data communication by the network operator or the like described in the first embodiment, or the first modification of the first embodiment.
  • the APN specified for the real-time game and emergency data communication for example, by the network operator described in the above, or the APN specified for the real-time game, for example, by the network operator described in the second modification of the first embodiment It is.
  • the MME / S-GW executes the Dedicated Bearer establishment process S26 for establishing the bearer for emergency data communication
  • the MME / S-GW displays the Activate Dedicated EPS Bearer Context Request message in FIG. 5, FIG. 7 and FIG.
  • the QCI value (X) determined based on any of the shown QCI characteristic tables and transmitting it to the UE, at least emergency data communication can be performed with higher priority than normal data communication.
  • GBR is also set, so that the transmission speed is guaranteed and it can be used stably.
  • the second PDN connection request process for establishing the bearer for emergency data communication is performed.
  • a configuration has been shown in which emergency data communication can be performed with a high QoS such as a high priority.
  • an emergency data communication is also requested so that a single PDN connection request process is performed. You may enable it to perform emergency data communication.
  • FIG. 12 is a diagram illustrating a control procedure when an emergency call is transmitted from the UE in the LTE system according to the modification of the second embodiment.
  • the UE and the eNB perform RRC Connection establishment processing S31. Execute. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
  • the RRC connection establishment process S31 there is a transmission of the RRC connection setup from the eNB to the UE and a transmission of the RRC connection setup complete from the UE to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer is executed following RRC Connection, illustration is omitted.
  • the PDN connection request process S32 causes the UE to use the PDN Connectivity Request with Req_type as Emergency. Is transmitted to the MME / S-GW via the eNB, the specific APN is included in the PDN Connectivity Request and transmitted. This APN is the APN described in the first embodiment or the first modification or the second modification thereof, and a duplicate description is omitted.
  • the MME / S-GW Upon receiving the PDN Connectivity Request, the MME / S-GW executes the Default Bearer establishment process S33 for establishing the bearer for IMS signaling related to the emergency call, and includes the Activate Default EPS Bearer Context Request message value in the Request Queue Request Quest message value. To the UE.
  • QCI 5 corresponding to IMS signaling for managing voice communication is assigned.
  • the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
  • the MME / S-GW executes a dedicated bearer establishment process S34 for establishing a bearer for voice data related to an emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Context Request message to the UE. Send.
  • QCI 1 corresponding to VoIP is assigned based on the QCI characteristic table shown in FIG.
  • the MME / S-GW transmits an E-RAB Setup Request to the eNB, and the eNB transmits an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
  • the MME / S-GW executes the Dedicated Bearer establishment process S35 for establishing the bearer for emergency data communication
  • the MME / S-GW adds the Activate Dedicated EPS Bearer Context Request message to FIG. 5, FIG. 7 and FIG.
  • the QCI value (X) determined based on any of the shown QCI characteristic tables and transmitting it to the UE
  • at least emergency data communication can be performed with higher priority than normal data communication.
  • GBR is also set, so that the transmission speed is guaranteed and it can be used stably.
  • emergency data communication is requested together with a call to the police.
  • a UE is a radio communication terminal
  • a traffic accident occurs

Abstract

The present invention relates to a wireless communication terminal, and is provided with a control unit, which requests a network device to execute emergency data communication, receives a service quality class identifier (QCI) transmitted from the network device corresponding to the request, said service quality class identifier corresponding to the emergency data communication, and performs emergency data communication processing via the network device on the basis of the service quality class identifier.

Description

無線通信端末、通信制御方法およびネットワーク装置Wireless communication terminal, communication control method, and network device
 本発明は、無線通信端末、通信制御方法よびネットワーク装置に関し、特に、緊急用途等、緊急性及び/又はリアルタイム性が求められる時のデータ通信において、当該データ通信に十分なQoSを実現する無線通信端末、通信制御方法およびネットワーク装置に関する。 The present invention relates to a wireless communication terminal, a communication control method, and a network device, and more particularly, wireless communication that realizes QoS sufficient for data communication when urgency and / or real-time performance is required, such as emergency use. The present invention relates to a terminal, a communication control method, and a network device.
 次世代の無線通信方式として、LTE(Long Term Evolution)システムが3GPP(3rd Generation Partnership Project)で標準化されている。LTEシステムは、無線通信端末であるUE(User Equipment)と、無線通信基地局であるeNB(evolved Node B)と、IP(Internet Protocol)ベースのコアネットワークであるEPC(Evolved Packet Core)とによって構成されている。なお、本明細書において、無線通信基地局は「基地局」と略記し、無線通信端末は「端末」と略記する。 As a next generation wireless communication system, LTE (Long Term Evolution) system has been standardized by 3GPP (3rd Generation Partnership Project). The LTE system includes a UE (User Equipment) that is a radio communication terminal, an eNB (evolved Node B) that is a radio communication base station, and an EPC (Evolved Packet Core) that is an IP (Internet Protocol) -based core network. Has been. In this specification, a radio communication base station is abbreviated as “base station”, and a radio communication terminal is abbreviated as “terminal”.
 LTEシステムでは、インターネットプロトコル(IP)をベースとしたネットワークを経由して音声通信呼の接続を実現するVoLTE(Voice over LTE)が規定されており、VoLTEでは、警察や消防への発信など、緊急性の高い緊急呼を最優先で処理するための手順が規定されている。そして、VoLTE時の音声は切れては困るアプリケーションという認識が持たれており、QCI(Quality of service Class Identifier:サービス品質クラス識別子)において最優先である優先度1が割り当てられている。この結果、送信速度も保証され、安定して利用することが可能である。なお、VoLTEにおける緊急呼の処理手順については特許文献1に開示されている。一方、データ通信(例えば、3GPP TS23.203 rel.12で規定されているTCPベースのサービス/アプリケーション)は、他のアプリケーション(例えば、VoIP、VoLTE)に比べて、優先度(Priority Level)が低く(優先度6、8及び9)、なお且つ保証ビット・レート(GBR:Guaranteed bitrate)のないQCI(QoS)が割り当てられている。 In the LTE system, VoLTE (Voice over LTE) that realizes connection of voice communication calls via a network based on the Internet protocol (IP) is regulated. A procedure for handling high priority emergency calls with the highest priority is defined. The voice at the time of VoLTE is recognized as an application that is difficult to be cut off, and the priority 1 that is the highest priority in QCI (Quality of service class identifier) is assigned. As a result, the transmission speed is also guaranteed and can be used stably. Note that the emergency call processing procedure in VoLTE is disclosed in Patent Document 1. On the other hand, data communication (for example, a TCP-based service / application defined in 3GPP TS23.203 rel.12.) Has a lower priority (Priority Level) than other applications (for example, VoIP, VoLTE). QCI (QoS) without priority bits (GBR: Guaranteed bit rate) is assigned ( priorities 6, 8, and 9).
国際公開第2014/050345号International Publication No. 2014/050345
 以上説明したように、LTEシステムにおいて、データ通信は、優先度が低く、なお且つ保証ビット・レートのないQCI(QoS)が割り当てられている。通常のデータ通信(リアルタイム性や緊急性を要しないもの、例えばウェブブラウジング)であれば、上記QCIに対応するQoSであっても問題はない。 As described above, in the LTE system, QCI (QoS) with low priority and no guaranteed bit rate is assigned to data communication. If it is normal data communication (thing which does not require real-time property or urgency, for example, web browsing), there is no problem even with QoS corresponding to the QCI.
 しかし、通常のデータ通信とは異なり、例えば緊急用途等、緊急性及び/又はリアルタイム性が求められるデータ通信(例えば、事故状況に関する動画の送信)を実行する場合においても、上記通常のデータ通信と同様の上記QCIに対応するQoSでは十分ではない可能性がある。 However, unlike normal data communication, even when performing data communication that requires urgency and / or real-time characteristics, such as emergency use (for example, transmission of a video about an accident situation), A similar QoS corresponding to the above QCI may not be sufficient.
 本発明は上記のような課題を解決するためになされたものであり、緊急用途等、緊急性及び/又はリアルタイム性が求められる時のデータ通信において、当該データ通信に十分なQoSを実現することを目的とする。 The present invention has been made to solve the above-described problems, and realizes QoS sufficient for data communication in data communication when urgency and / or real-time performance is required, such as emergency use. With the goal.
 本発明に係る無線通信端末の一態様は、ネットワーク装置に対して緊急用データ通信の実行を要求し、当該要求に応じて前記ネットワーク装置から送信された前記緊急用データ通信に対応したサービス品質クラス識別子(QCI)を受信し、該サービス品質クラス識別子に基づいて前記ネットワーク装置を介して前記緊急用データ通信する処理を行う制御部を備えている。 One aspect of a wireless communication terminal according to the present invention requests a network device to perform emergency data communication, and a service quality class corresponding to the emergency data communication transmitted from the network device in response to the request A control unit is provided that receives an identifier (QCI) and performs a process of performing the emergency data communication via the network device based on the service quality class identifier.
 本発明に係る無線通信端末の一態様は、前記緊急用データ通信に対応したサービス品質クラス識別子が、前記緊急用データ通信に専用のサービス品質クラス識別子である。 In one aspect of the wireless communication terminal according to the present invention, the service quality class identifier corresponding to the emergency data communication is a service quality class identifier dedicated to the emergency data communication.
 本発明に係る無線通信端末の一態様は、前記緊急用データ通信に専用のサービス品質クラス識別子が、前記ネットワーク装置のメモリに記憶された、前記緊急用データ通信に専用のサービス品質クラス識別子を含むQCI特性表に基づいて割り当てられる。 One aspect of the wireless communication terminal according to the present invention includes a service quality class identifier dedicated to the emergency data communication, wherein the service quality class identifier dedicated to the emergency data communication is stored in a memory of the network device. Assigned based on the QCI characteristic table.
 本発明に係る無線通信端末の一態様は、前記緊急用データ通信に対応したサービス品質クラス識別子が、他のアプリケーションと兼用のサービス品質クラス識別子である。 In one aspect of the wireless communication terminal according to the present invention, the service quality class identifier corresponding to the emergency data communication is a service quality class identifier shared with other applications.
 本発明に係る無線通信端末の一態様は、前記他のアプリケーションと兼用のサービス品質クラス識別子が、前記ネットワーク装置のメモリに記憶された、前記サービス品質クラス識別子の適用対象のアプリケーションに前記他のアプリケーション及び前記緊急用データ通信を含むQCI特性表に基づいて割り当てられる。 In one aspect of the wireless communication terminal according to the present invention, the service quality class identifier also used as the other application is stored in a memory of the network device, and the other application And the QCI characteristic table including the emergency data communication.
 本発明に係る無線通信端末の一態様は、前記緊急用データ通信に対応したサービス品質クラス識別子には、少なくとも通常のデータ通信よりも高い優先度が割り当てられる。 In one aspect of the wireless communication terminal according to the present invention, at least a higher priority than normal data communication is assigned to the service quality class identifier corresponding to the emergency data communication.
 本発明に係る無線通信端末の一態様は、前記制御部が、緊急呼の発信を契機として前記ネットワーク装置に対する緊急用データ通信の実行を要求する処理を行う。 In one aspect of the wireless communication terminal according to the present invention, the control unit performs a process of requesting execution of emergency data communication to the network device when an emergency call is transmitted.
 本発明に係る無線通信端末の一態様は、前記制御部が、前記ネットワーク装置に対して前記緊急用データ通信の実行を要求する際に、前記緊急用データ通信に対応するPDN Connectivity Requestを前記ネットワーク装置に対して送信する処理を行う。 In one aspect of the wireless communication terminal according to the present invention, when the control unit requests the network device to execute the emergency data communication, the PDN Connectivity Request corresponding to the emergency data communication is transmitted to the network device. Performs transmission processing to the device.
 本発明に係る無線通信端末の一態様は、前記緊急用データ通信に対応するPDN Connectivity Requestは、前記緊急用データ通信に対応する特定のアクセスポイント名(APN)を含むPDN Connectivity Requestである。 In one aspect of the wireless communication terminal according to the present invention, the PDN Connectivity Request corresponding to the emergency data communication is a PDN Connectivity Request including a specific access point name (APN) corresponding to the emergency data communication.
 本発明に係る無線通信端末の一態様は、前記制御部が、緊急呼の発信の際に、当該緊急呼に対応するPDN Connectivity Requestを送信し、その後に前記緊急用データ通信に対応するPDN Connectivity Requestを送信する処理を行う。 In one aspect of the wireless communication terminal according to the present invention, the control unit transmits a PDN Connectivity Request corresponding to the emergency call when an emergency call is made, and then the PDN Connectivity corresponding to the emergency data communication. Processing to send a Request is performed.
 本発明に係る無線通信端末の一態様は、前記制御部が、緊急呼の発信の際に、当該緊急呼に対応し、なお且つ前記緊急用データ通信に対応するPDN Connectivity Requestを送信する処理を行う。 One aspect of the wireless communication terminal according to the present invention is a process in which the control unit transmits a PDN Connectivity Request corresponding to the emergency call and corresponding to the emergency data communication when an emergency call is made. Do.
 本発明に係る無線通信端末の一態様は、緊急用データ通信の実行をする際に、当該緊急用データ通信に対応する他のアプリケーションの実行をネットワーク装置に対して要求し、当該要求に応じて前記ネットワーク装置から送信された前記他のアプリケーションに対応するサービス品質クラス識別子(QCI)を受信し、該サービス品質クラス識別子に基づいて、前記ネットワーク装置を介して前記緊急用データ通信する処理を行う制御部を備える。 In one aspect of the wireless communication terminal according to the present invention, when executing emergency data communication, the network device is requested to execute another application corresponding to the emergency data communication, and in response to the request Control that receives a quality of service class identifier (QCI) corresponding to the other application transmitted from the network device, and performs a process of communicating the emergency data via the network device based on the service quality class identifier A part.
 本発明に係る通信制御方法の一態様は、無線通信端末が、ネットワーク装置に対して緊急用データ通信の実行を要求するステップ(a)と、前記ネットワーク装置が、前記緊急用データ通信に対応したサービス品質クラス識別子(QCI)を前記無線通信端末に送信するステップ(b)と、前記無線通信端末が、前記サービス品質クラス識別子(QCI)を受信すると、該サービス品質クラス識別子に基づいて、前記ネットワーク装置を介して前記緊急用データ通信を行うステップ(c)と、を備えている。 In one aspect of the communication control method according to the present invention, the wireless communication terminal requests the network device to execute emergency data communication (a), and the network device corresponds to the emergency data communication. (B) transmitting a quality of service class identifier (QCI) to the wireless communication terminal; and when the wireless communication terminal receives the quality of service class identifier (QCI), based on the quality of service class identifier, the network And (c) performing the emergency data communication through a device.
 本発明に係るネットワーク装置の一態様は、無線通信端末から緊急用データ通信の実行の要求を受けると、当該要求に応じて、前記緊急用データ通信に対応した、前記無線通信端末が前記緊急用データ通信を行う際に用いるサービス品質クラス識別子(QCI)を、前記無線通信端末に送信する処理を行う制御部を備えている。 In one aspect of the network device according to the present invention, when a request for execution of emergency data communication is received from a wireless communication terminal, the wireless communication terminal corresponding to the emergency data communication responds to the request by the emergency communication A control unit is provided for performing a process of transmitting a quality of service class identifier (QCI) to be used for data communication to the wireless communication terminal.
 本発明によれば、緊急用途等、緊急性及び/又はリアルタイム性が求められる時のデータ通信において、当該データ通信に十分なQoSを実現することができる。 According to the present invention, in data communication when urgency and / or real-time property is required, such as emergency use, QoS sufficient for the data communication can be realized.
LTEシステムの構成を説明する図である。It is a figure explaining the structure of a LTE system. LTEシステムにおけるUEのブロック図である。It is a block diagram of UE in an LTE system. LTEシステムにおけるMME/S-GWのブロック図である。It is a block diagram of MME / S-GW in an LTE system. UEから緊急呼が発信された場合の一般的な制御手順を説明する図である。It is a figure explaining the general control procedure when an emergency call is transmitted from UE. 基本のQCI特性表を示す図である。It is a figure which shows a basic QCI characteristic table. 実施の形態1のLTEシステムにおいてUEから緊急用データが発信された場合の制御手順を示す図である。FIG. 10 is a diagram illustrating a control procedure when emergency data is transmitted from a UE in the LTE system according to the first embodiment. 実施の形態1のLTEシステムにおいて使用されるQCI特性表を示す図である。3 is a diagram illustrating a QCI characteristic table used in the LTE system according to Embodiment 1. FIG. 実施の形態1の変形例1のLTEシステムにおいて使用されるQCI特性表を示す図である。6 is a diagram showing a QCI characteristic table used in the LTE system according to the first modification of the first embodiment. FIG. 実施の形態1の変形例1のLTEシステムにおいて、UEから緊急用データが発信された場合の制御手順を示す図である。In the LTE system of the modification 1 of Embodiment 1, it is a figure which shows the control procedure when emergency data are transmitted from UE. 図10は実施の形態1の変形例2に係るLTEシステムにおいて、UEから緊急用データが発信された場合の制御手順を示す図である。FIG. 10 is a diagram illustrating a control procedure when emergency data is transmitted from the UE in the LTE system according to the second modification of the first embodiment. 実施の形態2のLTEシステムにおいてUEから緊急呼が発信された場合の制御手順を示す図である。FIG. 10 is a diagram illustrating a control procedure when an emergency call is transmitted from a UE in the LTE system according to the second embodiment. 実施の形態2の変形例のLTEシステムにおいてUEから緊急呼が発信された場合の制御手順を示す図である。FIG. 10 is a diagram illustrating a control procedure when an emergency call is transmitted from a UE in an LTE system according to a modification of the second embodiment.
 (はじめに)
 実施の形態の説明に先だって、LTEシステムについて説明する。図1は、LTEシステムの構成図である。図1に示すように、LTEシステムは、UE100と、E-UTRAN(Evolved-UMTS Terrestria1 Radio Access Network)10と、EPC20と、を含んでいる。E-UTRAN10は無線アクセスネットワークに相当し、EPC20はコアネットワークに相当する。E-UTRAN10およびEPC20は、LTEシステムのネットワークを構成する。
(Introduction)
Prior to the description of the embodiments, the LTE system will be described. FIG. 1 is a configuration diagram of an LTE system. As shown in FIG. 1, the LTE system includes a UE 100, an E-UTRAN (Evolved-UMTS Terrestria 1 Radio Access Network) 10, and an EPC 20. The E-UTRAN 10 corresponds to a radio access network, and the EPC 20 corresponds to a core network. The E-UTRAN 10 and the EPC 20 constitute an LTE system network.
 UE100は、移動型の無線通信端末であり、接続先のセル(サービングセル)との無線通信を行う。UE100はユーザ端末に相当する。 The UE 100 is a mobile radio communication terminal and performs radio communication with a connection destination cell (serving cell). UE100 is corresponded to a user terminal.
 E-UTRAN10は、複数のeNB200(200-1、200-2、200-3)を含んでいる。eNB200は、1または複数のセルを管理しており、自らが管理するセルとの接続を確立したUE100との無線通信を行う。なお、「セル」は、無線通信エリアの最小単位を示す用語として使用される他にUE100との無線通信を行う機能を示す用語としても使用される。 The E-UTRAN 10 includes a plurality of eNBs 200 (200-1, 200-2, 200-3). The eNB 200 manages one or a plurality of cells, and performs radio communication with the UE 100 that establishes a connection with a cell managed by the eNB 200. Note that “cell” is used as a term indicating a minimum unit of a radio communication area, and also as a term indicating a function of performing radio communication with the UE 100.
 eNB200は、例えば、無線リソース管理(RRM)機能と、ユーザデータのルーティング機能と、モビリティ制御およびスケジューリングのための測定制御機能と、を有している。 The eNB 200 has, for example, a radio resource management (RRM) function, a user data routing function, and a measurement control function for mobility control and scheduling.
 EPC20は、複数のMME(Mobility Management Entity)/S-GW(Serving―Gateway)300(300-1、300-2)を含んでいる。 The EPC 20 includes a plurality of MME (Mobility Management Entity) / S-GW (Serving-Gateway) 300 (300-1, 300-2).
 MMEは、UE100に対する各種モビリティ制御等を行うネットワークノードであり、制御局に相当する。S-GWは、ユーザデータの転送制御を行うネットワークノードであり、交換局に相当する。 The MME is a network node that performs various types of mobility control for the UE 100, and corresponds to a control station. The S-GW is a network node that performs transfer control of user data, and corresponds to an exchange.
 eNB200は、インターフェイスX2を介して相互に接続される。また、eNB200は、インターフェイスS1を介してMME/S-GW300と接続される。 The eNB 200 is connected to each other via the interface X2. The eNB 200 is connected to the MME / S-GW 300 via the interface S1.
 図2は、UE100の構成を示すブロック図である。図2に示すようにUE100は、複数のアンテナ101と、無線送受信機110と、ユーザインターフェイス120と、GNSS(Global Navigation Satellite System)受信機130と、バッテリ140と、メモリ150と、プロセッサ160とを有している。なお、UE100は、GNSS受信機130を有していなくても良い。また、メモリ150をプロセッサ160と一体化し、このセット(すなわち、チップセット)をプロセッサ160'としても良い。 FIG. 2 is a block diagram showing the configuration of the UE 100. As shown in FIG. 2, the UE 100 includes a plurality of antennas 101, a radio transceiver 110, a user interface 120, a GNSS (Global Navigation Satellite System) receiver 130, a battery 140, a memory 150, and a processor 160. Have. Note that the UE 100 may not have the GNSS receiver 130. Further, the memory 150 may be integrated with the processor 160, and this set (that is, a chip set) may be used as the processor 160 ′.
 複数のアンテナ101および無線送受信機110は、無線信号の送受信に用いられる。無線送受信機110は、プロセッサ160が出力するベースバンド信号(送信信号)を無線信号に変換して複数のアンテナ101から送信する送信部111を含んでいる。また、無線送受信機110は、複数のアンテナ101が受信する無線信号をベースバンド信号(受信信号)に変換してプロセッサ160に出力する受信部112を含んでいる。 The plurality of antennas 101 and the wireless transceiver 110 are used for transmitting and receiving wireless signals. The radio transceiver 110 includes a transmission unit 111 that converts a baseband signal (transmission signal) output from the processor 160 into a radio signal and transmits the radio signal from a plurality of antennas 101. The radio transceiver 110 includes a receiving unit 112 that converts radio signals received by the plurality of antennas 101 into baseband signals (received signals) and outputs the baseband signals to the processor 160.
 ユーザインターフェイス120は、UE100を所持するユーザとのインターフェイスであり、例えば、ディスプレイ、マイク、スピーカ、および各種ボタンなどを含んでいる。ユーザインターフェイス120は、ユーザからの操作を受け付けて、該操作の内容を示す信号をプロセッサ160に出力する。 The user interface 120 is an interface with a user who owns the UE 100, and includes, for example, a display, a microphone, a speaker, and various buttons. The user interface 120 receives an operation from the user and outputs a signal indicating the content of the operation to the processor 160.
 GNSS受信機130は、UE100の地理的な位置を示す位置情報を得るために、GNSS信号を受信して、受信した信号をプロセッサ160に出力する。バッテリ140は、UE100の各ブロックに供給すべき電力を蓄える。 The GNSS receiver 130 receives a GNSS signal and outputs the received signal to the processor 160 in order to obtain position information indicating the geographical position of the UE 100. The battery 140 stores power to be supplied to each block of the UE 100.
 メモリ150は、プロセッサ160によって実行されるプログラムと、プロセッサ160による処理に使用される情報と、を記憶する。プロセッサ160は、ベースバンド信号の変調・復調および符号化・復号などの信号処理を行う信号処理部161と、メモリ150に記憶されるプログラムを実行して各種の制御を行う制御部162と、を含んでいる。 The memory 150 stores a program executed by the processor 160 and information used for processing by the processor 160. The processor 160 includes a signal processing unit 161 that performs signal processing such as modulation / demodulation and encoding / decoding of a baseband signal, and a control unit 162 that executes various programs by executing programs stored in the memory 150. Contains.
 なお、制御部162は、後述する、ユーザインターフェイス120を介しての操作に基づいて緊急呼の発信のための処理を行うと共に、MME/S-GWからの制御を受けて緊急用データ通信のための制御を行う。 The control unit 162 performs a process for making an emergency call based on an operation through the user interface 120, which will be described later, and performs an emergency data communication under the control of the MME / S-GW. Control.
 図3は、MME/S-GW300の構成を示すブロック図である。図3に示すようにMME/S-GW300は、ネットワークインターフェイス220と、メモリ230と、プロセッサ240と、を有している。 FIG. 3 is a block diagram showing the configuration of the MME / S-GW 300. As shown in FIG. 3, the MME / S-GW 300 includes a network interface 220, a memory 230, and a processor 240.
 ネットワークインターフェイス220は、インターフェイスS1(図1)を介してeNB200と接続される。 The network interface 220 is connected to the eNB 200 via the interface S1 (FIG. 1).
 メモリ230は、プロセッサ240によって実行されるプログラムと、プロセッサ240による処理に使用される情報と、を記憶する。プロセッサ240は、UEから発信された緊急呼を受信して、UEを制御する制御動作を行う制御部241を有しており、後述するUEに対する各種の制御を実行する。 The memory 230 stores a program executed by the processor 240 and information used for processing by the processor 240. The processor 240 includes a control unit 241 that receives an emergency call transmitted from the UE and performs a control operation for controlling the UE, and executes various controls for the UE described later.
 次に、上述したLTEシステムにおいてUEから緊急呼が発信された場合の制御手順について図4を用いて説明する。なお、図4においては、eNBおよびMME/S-GWをまとめてネットワーク装置(NW)として記載している。 Next, a control procedure when an emergency call is transmitted from the UE in the above-described LTE system will be described with reference to FIG. In FIG. 4, the eNB and the MME / S-GW are collectively described as a network device (NW).
 図4に示すように、アイドル(Idle)状態にあるUEにおいて、例えば警察への発信操作により緊急呼が発信されると、UEとeNBは、RRC Connection確立処理S1を実行する。RRC Connection確立処理S1では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 As shown in FIG. 4, when an emergency call is made in a UE in an idle state, for example, by a call origination operation to the police, the UE and the eNB execute RRC Connection establishment processing S1. In the RRC connection establishment process S1, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 なお、RRC Connection確立処理S1には、RRC Connection Requestを受信したeNBが、UEにRRC Connection Setupを送信し、UEがeNBにRRC Connection Setup Completeを送信する手順も含まれるが、図示は省略する。また、RRC Connectionに続いてMME/S-GWとの間でeNBを介した音声用のベアラ(通信経路)を確立するためのデフォルトベアラ確立処理が実行されるが、図示は省略する。 The RRC Connection establishment process S1 includes a procedure in which the eNB that has received the RRC Connection Request transmits the RRC Connection Setup to the UE, and the UE transmits the RRC Connection Setup Complete to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer (communication path) via the eNB with the MME / S-GW is executed subsequent to the RRC connection, illustration is omitted.
 音声用のベアラを確立するためのデフォルトベアラ確立処理により、UEとMME/S-GWとがデータ交換可能となった後、PDN接続要求処理S2が実行される。PDN接続要求処理S2では、UEが、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する。 After the default bearer establishment process for establishing the voice bearer enables the UE and the MME / S-GW to exchange data, the PDN connection request process S2 is executed. In the PDN connection request process S2, the UE transmits a PDN Connectivity Request with Req_type as Emergency to the MME / S-GW via the eNB.
 PDN Connectivity Requestを受信したMME/S-GWは、緊急呼に係るIMSシグナリング(呼の制御に係る制御信号)用のベアラを確立するためのDeafault Bearer確立処理S3を実行し、Activate Default EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、音声通信を管理するためのIMSシグナリングに対応するQCI=5を割り当てる。 Upon receiving the PDN Connectivity Request, the MME / S-GW executes a Default Bearer establishment process S3 for establishing a bearer for IMS signaling related to an emergency call (control signal related to call control), and Activate Default EPS BearerCerterCaster The QCI value is included in the Request message and transmitted to the UE. Here, QCI = 5 corresponding to IMS signaling for managing voice communication is assigned.
 なお、緊急呼に係るIMSシグナリング用のベアラを確立するためのDeafault Bearer確立処理S3では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMME/S-GWにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。 In the default bearer establishment process S3 for establishing a bearer for IMS signaling related to an emergency call, the MME / S-GW transmits an E-RAB Setup Request to the eNB, and the eNB transmits an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
 次に、MME/S-GWは、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S4を実行し、Activate Dedicated EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、VoIP(Voice over IP)に対応するQCI=1を割り当てる。 Next, the MME / S-GW executes a dedicated bearer establishment process S4 for establishing a bearer for voice data related to an emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Request Request message to the UE. Send. Here, QCI = 1 corresponding to VoIP (Voice over IP) is assigned.
 なお、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S4では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMMEにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。以上のような手順を経てVoLTEによる音声通信が開始される。 In the Dedicated Bearer establishment process S4 for establishing a bearer for voice data related to an emergency call, the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
 図5には、基本の(基準となる)QCI特性表を示す。図5においては、QCI値に対応付けられた、ビット・レートの保証の有無(GBR、Non-GBR)、優先度(Priority Level)、パケット遅延バジェット(Packet Delay Budget)、パケットエラーロス率(PELR:Packet Error Loss Rate)およびアプリケーション(サービス)が示されている。 FIG. 5 shows a basic (standard) QCI characteristic table. In FIG. 5, whether bit rate is guaranteed (GBR, Non-GBR), priority (Priority (Level), packet delay budget (Packet Delay Budget), packet error loss rate (PELR) associated with the QCI value : Packet Error Loss Rate) and application (service) are shown.
 図5に示されるように、VoIP(VoLTE)には2番目である優先度2が割り当てられている。この結果、送信速度も保証され、安定して利用することが可能である。 As shown in FIG. 5, VoIP (VoLTE) is assigned the second priority level 2. As a result, the transmission speed is also guaranteed and can be used stably.
 (実施の形態1)
 以下、図6~図10を用いて、実施の形態1のLTEシステムについて説明する。図6は実施の形態1のLTEシステムにおいてUEが緊急用データの発信をする場合の制御手順を示す図である。なお、図6においては、eNBおよびMME/S-GWをまとめてネットワーク装置(NW)として記載している。
(Embodiment 1)
Hereinafter, the LTE system according to the first embodiment will be described with reference to FIGS. FIG. 6 is a diagram illustrating a control procedure when the UE transmits emergency data in the LTE system according to the first embodiment. In FIG. 6, eNB and MME / S-GW are collectively described as a network device (NW).
 図6に示すように、アイドル(Idle)状態にあるUEにおいて、例えばユーザインターフェイス120(図3)を介して緊急用データ発信(緊急用データ通信開始)のための操作がなされるか若しくは緊急用データ発信の契機となる特定のイベントが発生した場合、UEとeNBは、RRC Connection確立処理S11を実行する。RRC Connection確立処理S11では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 As shown in FIG. 6, in a UE in an idle state, an operation for emergency data transmission (emergency data communication start) is performed via the user interface 120 (FIG. 3) or an emergency When a specific event that triggers data transmission occurs, the UE and the eNB execute an RRC connection establishment process S11. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 ここで、緊急用データ発信の契機となる特定のイベントとは、例えば、緊急用アプリケーションによるものである。ここでいう緊急用アプリケーションとは、例えば、UEが車両に搭載された通信機能を有する車載カメラ装置であって、内部に加速度センサーなどを有する場合、自車両が所定の閾値以上の衝撃を受けるとそれを加速度センサーで検知し、衝撃を受けた前後の画像データを緊急用データとしてネットワーク装置を介して外部のサーバー等に送信するアプリケーションである。このアプリケーションによって実行される緊急用データ発信は、自動車事故であれば、その後に車載カメラ装置が破損する可能性が考えられるので、画像データを至急に外部のサーバーに送信する必要性から行われる。 Here, the specific event that triggers the emergency data transmission is, for example, an emergency application. The emergency application here is, for example, an in-vehicle camera device that has a communication function mounted on a vehicle and has an acceleration sensor or the like. This is an application that detects this with an acceleration sensor and transmits the image data before and after receiving an impact as emergency data to an external server or the like via a network device. The emergency data transmission executed by this application is performed from the necessity of urgently transmitting the image data to an external server because there is a possibility that the in-vehicle camera device may be subsequently damaged in the case of a car accident.
 なお、ここでは、UEを車載カメラ装置としているが、これに限られず、UEは、車載カメラ装置から有線若しくは無線を介して受信したデータを外部に送信する通信モジュールであっても良い。また、加速度センサーは、車載カメラ装置に設けられていなくとも良く、外部に設けられ、検出結果を車載カメラ装置に送信する構成であっても良い。 In addition, although UE is used as the vehicle-mounted camera device here, the present invention is not limited to this, and the UE may be a communication module that transmits data received from the vehicle-mounted camera device via wire or wirelessly. Further, the acceleration sensor may not be provided in the in-vehicle camera device, but may be provided outside and configured to transmit the detection result to the in-vehicle camera device.
 なお、RRC Connection確立処理S11では、eNBからUEへのRRC Connection Setupの送信および、UEからeNBへのRRC Connection Setup Completeの送信もあるが、図示は省略する。 In addition, in RRC Connection establishment process S11, there is also transmission of RRC Connection Setup from the eNB to the UE and transmission of RRC Connection Setup Complete from the UE to the eNB, but illustration is omitted.
 UEが、緊急用データ通信を実行する(緊急用データを送信する)場合、例えば交通事故発生時に、事故現場の写真や動画を送信する場合、PDN接続要求処理S12において、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する際に、特定のアクセスポイント名(APN:Access Point Name)をPDN Connectivity Requestに含めて送信する。 When the UE performs emergency data communication (transmits emergency data), for example, when a traffic accident occurs, a photo or video of the accident site is transmitted, in the PDN connection request processing S12, PDN with Req_type as Emergency When transmitting the Connectivity Request to the MME / S-GW via the eNB, a specific access point name (APN: Access Point Name) is included in the PDN Connectivity Request and transmitted.
 ここで、PDN Connectivity Requestに含めて送信されるAPNは、ネットワークオペレータ(通信事業者)等によって緊急用データ通信用に特定されている。MME/S-GWは、PDN Connectivity Requestに含まれるAPNが、緊急用データ通信に対応するか否かを判定する。この判定は、MME/S-GWが、例えばメモリ230(図3)に記憶するテーブル等を用いて行う。MME/S-GWが、当該APNが緊急用データ通信に対応すると判定した場合は、例えば図7に示すQCI特性表に基づいて、緊急用データ通信のためのベアラを割り当てるために、Dedicated Bearer確立処理S13を実行し、緊急用データ通信(アプリケーション)に対応付けられたベアラ(QCI)の割り当てを行う。なお、図6においては、UEがアイドル状態であることを前提としているが、これに限られず、UEがヌル(null)状態若しくはコネクティッド(connected)状態であっても良く、UEがコネクティッド状態である場合には、UEによるRRC Connection Requestの送信を省略しても良い。 Here, the APN included in the PDN Connectivity Request is specified for emergency data communication by a network operator (communication carrier) or the like. The MME / S-GW determines whether the APN included in the PDN Connectivity Request is compatible with emergency data communication. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If the MME / S-GW determines that the APN supports emergency data communication, for example, based on the QCI characteristic table shown in FIG. 7, a dedicated bearer is established to allocate a bearer for emergency data communication. Process S13 is performed and the bearer (QCI) matched with the emergency data communication (application) is allocated. In FIG. 6, it is assumed that the UE is in an idle state. However, the present invention is not limited to this, and the UE may be in a null state or a connected state, and the UE is in a connected state. In this case, the transmission of the RRC Connection Request by the UE may be omitted.
 図7に示すQCI特性表においては、アプリケーションとしてTCPプロトコル(緊急用データ通信)が加わったことにより、QCIは1から10の値を有し、優先度も1から10の値を有している。なお、TCPプロトコル(緊急用データ通信)と記載されているが、これに限られず、単に、緊急用データ通信であっても良く、この緊急用データ通信はUDPプロトコルによるものも含むようにしても良い。 In the QCI characteristic table shown in FIG. 7, the QCI has a value of 1 to 10 and the priority has a value of 1 to 10 due to the addition of the TCP protocol (emergency data communication) as an application. . Although described as TCP protocol (emergency data communication), the present invention is not limited to this, and may be simply emergency data communication, and the emergency data communication may include the UDP protocol.
 すなわち、QCI=5に緊急用データ通信がビット・レートの保証有り(GBR)として割り付けられ、その優先度は、VoIP(VoLTE)よりも低く、リアルタイムゲームよりも高い優先度3に設定されている。また、パケット遅延バジェットは150ms、パケットエラーロス率は10-3となっている。なお、これらの値は一例であり、他の値に変えて良いことは言うまでもない。また、緊急用データ通信がQCI=5に割り付けられたので、図5におけるQCI=5以上の値が1つずつ増加し、図5における優先度3以上の値が1つずつ増加したこと以外は図5と同じである。 In other words, the emergency data communication is assigned as a bit rate guaranteed (GBR) when QCI = 5, and the priority thereof is set lower than that of VoIP (VoLTE) and higher than that of the real-time game. . The packet delay budget is 150 ms, and the packet error loss rate is 10 −3 . Needless to say, these values are only examples and may be changed to other values. Further, since the emergency data communication is assigned to QCI = 5, the value of QCI = 5 or more in FIG. 5 is increased by one, and the value of priority 3 or more in FIG. 5 is increased by one. This is the same as FIG.
 このようなQCI特性表を用いて、MME/S-GWは、緊急用データ通信用のベアラを確立するためのDedicated Bearer確立処理S13を実行する際に、Activate Dedicated EPS Bearer Context Requestメッセージに、図7に示すQCI特性表に基づいて決定したQCI=5の値を含ませてUEに送信する。 Using such a QCI characteristic table, when executing the Dedicated Bearer establishment process S13 for establishing the bearer for emergency data communication, the MME / S-GW displays the figure in the Activate Dedicated EPS Bearer Context Request message. 7 including the value of QCI = 5 determined based on the QCI characteristic table shown in FIG.
 QCI=5では優先度が3であるので、リアルタイムゲームや通常のデータ通信よりも優先的に緊急用データ通信を行うことができ、GBRも設定されているので送信速度も保証され、安定して利用することが可能となる。 When QCI = 5, the priority is 3, so emergency data communication can be performed with priority over real-time games and normal data communication, and the GBR is also set, so the transmission speed is guaranteed and stable. It can be used.
  (変形例1)
 以上説明した実施の形態1では、UEが、緊急用データ通信を実行する場合に、MME/S-GWが、図7に示すQCI特性表を用いてQCIの割り当てを行う構成を示したが、緊急用データ通信のための専用のQCIや優先度を設定するのではなく、特定のQCIの適用対象のアプリケーションに、他のアプリケーション及び緊急用データ通信を含むQCI特性表を用いる構成としても良い。
(Modification 1)
In Embodiment 1 described above, when the UE performs emergency data communication, the MME / S-GW has shown the configuration in which the QCI assignment is performed using the QCI characteristic table shown in FIG. Instead of setting a dedicated QCI and priority for emergency data communication, a QCI characteristic table including other applications and emergency data communication may be used as an application to which a specific QCI is applied.
 例えば、QCI特性表におけるQCI=4の適用対象のアプリケーションとして、リアルタイムゲームだけでなく、緊急用データ通信も加えるによって、QCIを複数のアプリケーションで兼用する構成とすることで、緊急用データ通信に際しては優先度3が割り当てられるようになり、UEが通常のデータ通信よりも優先的に緊急用データ通信を行うことができる。 For example, as an application subject to application of QCI = 4 in the QCI characteristic table, not only a real-time game but also emergency data communication is added so that QCI can be used by a plurality of applications. Priority 3 is assigned, and the UE can perform emergency data communication with priority over normal data communication.
 図8には、QCI=5の適用対象のアプリケーションとして、リアルタイムゲームと緊急用データ通信を含むQCI特性表を示す。 FIG. 8 shows a QCI characteristic table including real-time games and emergency data communication as applications to which QCI = 5 is applied.
 図9は実施の形態1の変形例1に係るLTEシステムにおいて、UEが緊急用データ通信を実行する(緊急用データ発信をする)場合の制御手順を示す図である。図9に示すように、アイドル(Idle)状態にあるUEにおいて、例えばユーザインターフェイス120(図3)を介して緊急用データ発信のための操作がなされるか若しくは緊急用データ発信の契機となる特定のイベントが発生した場合、UEとeNBは、RRC Connection確立処理S11を実行する。RRC Connection確立処理S11では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 FIG. 9 is a diagram illustrating a control procedure when the UE performs emergency data communication (emergency data transmission) in the LTE system according to the first modification of the first embodiment. As shown in FIG. 9, in a UE in an idle state, for example, an operation for transmitting emergency data is performed via the user interface 120 (FIG. 3), or a trigger that triggers emergency data transmission When this event occurs, the UE and the eNB execute the RRC connection establishment process S11. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 また、UEが、緊急用データ通信を実行する(緊急用データを発信する)場合、PDN接続要求処理S12において、UEがReq_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する際に、特定のAPNをPDN Connectivity Requestに含めて送信する。 Further, when the UE performs emergency data communication (emergency data is transmitted), in the PDN connection request processing S12, the UE performs PDN Connectivity Request with Req_type as Emergency, via the eNB, MME / S- When transmitting to the GW, the specific APN is included in the PDN Connectivity Request and transmitted.
 ここで、PDN Connectivity Requestに含めて送信されるAPNは、ネットワークオペレータ(通信事業者)等によってリアルタイムゲーム用と緊急用データ通信用に特定されている。MME/S-GWは、PDN Connectivity Requestに含まれるAPNが、緊急用データ通信に対応するか否かを判定する。この判定は、MME/S-GWが、例えばメモリ230(図3)に記憶するテーブル等を用いて行い、当該APNが緊急用データ通信等に対応すると判定した場合は、例えば図8に示すQCI特性表に基づいて、緊急用データ通信等のためのベアラを割り当てるために、Dedicated Bearer確立処理S131を実行し、MME/S-GWが緊急用データ通信(アプリケーション)に対応付けられたベアラ(QCI)の割り当てを行う。 Here, the APN included in the PDN Connectivity Request is specified for real-time game use and emergency data communication by a network operator (communication carrier) or the like. The MME / S-GW determines whether the APN included in the PDN Connectivity Request is compatible with emergency data communication. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If it is determined that the APN corresponds to emergency data communication or the like, for example, the QCI shown in FIG. In order to assign a bearer for emergency data communication or the like based on the characteristic table, the Dedicated Bearer establishment process S131 is executed, and the MME / S-GW is associated with the emergency data communication (application) (QCI). ).
 すなわち、MME/S-GWは、緊急用データ通信等用のベアラを確立するためのDedicated Bearer確立処理S131を実行する際に、Activate Dedicated EPS Bearer Context Requestメッセージに、図8に示すQCI特性表に基づいて決定したQCI=4の値を含ませてUEに送信する。 That is, when the MME / S-GW executes the Dedicated Bearer establishment process S131 for establishing a bearer for emergency data communication or the like, the MCI / S-GW displays the QCI characteristic table shown in FIG. 8 in the Activate Dedicated EPS Bearer Request Request message. A value of QCI = 4 determined based on this is included and transmitted to the UE.
 QCI=4では優先度が3であるので、通常のデータ通信よりも優先的に緊急用データ通信を行うことができ、GBRも設定されているので送信速度も保証され、安定して利用することが可能となる。 When QCI = 4, the priority is 3, so emergency data communication can be performed with priority over normal data communication, and the GBR is also set, so the transmission speed is guaranteed and the data can be used stably. Is possible.
 以上説明したように、緊急用データ通信に際しては、緊急用データ通信のための専用のQCIや優先度を設定するのではなく、QCIが割り当てられた既設の他のアプリケーションに緊急用データ通信を加えるので、標準化されたQCI特性表を大きく変更することなく対応でき、LTEシステムに加える改変が少なくて済む。 As described above, in the emergency data communication, the emergency data communication is added to another existing application to which the QCI is assigned, instead of setting a dedicated QCI and priority for the emergency data communication. Therefore, the standardized QCI characteristic table can be handled without greatly changing, and the modification to the LTE system can be reduced.
  (変形例2)
 以上説明した実施の形態1では、UEが、緊急用データ通信を実行する場合には、MME/S-GWでは、図7に示すQCI特性表を用いてQCIの割り当てを行う構成を示したが、緊急用データ通信のための専用のQCIや優先度を設定するのではなく、緊急用データ通信の実行に際しては、高優先度のQCIが割り当てられたアプリケーションにカモフラージュする構成としても良い。
(Modification 2)
In Embodiment 1 described above, when the UE performs emergency data communication, the MME / S-GW has shown the configuration in which the QCI is assigned using the QCI characteristic table shown in FIG. Instead of setting a dedicated QCI and priority for emergency data communication, it may be configured to camouflage to an application to which a high-priority QCI is assigned when executing emergency data communication.
 例えば、UEとMME/S-GWとの間で、QCI=2のビデオコール用のベアラを設定するための手順や、QCI=4のリアルタイムゲーム用のベアラを設定するための手順が確立されている場合、緊急用データ通信においてもそれらの手順を使用してQCI=2またはQCI=4が割り当てられるようにしても良い。 For example, a procedure for setting up a bearer for a video call with QCI = 2 and a bearer for a real-time game with QCI = 4 is established between the UE and the MME / S-GW. In the case of the emergency data communication, QCI = 2 or QCI = 4 may be assigned even in the emergency data communication.
 この動作の一例を、図10を用いて説明する。図10は実施の形態1の変形例2に係るLTEシステムにおいて、UEが緊急用データを発信する際の制御手順を示す図である。図10に示すように、アイドル(Idle)状態にあるUEにおいて、例えばユーザインターフェイス120(図3)を介して緊急用データ発信のための操作がなされると、UEとeNBは、RRC Connection確立処理S11を実行する。RRC Connection確立処理S11では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 An example of this operation will be described with reference to FIG. FIG. 10 is a diagram illustrating a control procedure when the UE transmits emergency data in the LTE system according to the second modification of the first embodiment. As shown in FIG. 10, in the UE in the idle state, when an operation for emergency data transmission is performed through the user interface 120 (FIG. 3), for example, the UE and the eNB perform RRC connection establishment processing. S11 is executed. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 また、UEにおいて、緊急用データ通信を実行する(緊急用データを発信する)場合、PDN接続要求処理S12において、UEが、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する際に、特定のAPNをPDN Connectivity Requestに含めて送信する。 Further, when the UE performs emergency data communication (emergency data is transmitted), in the PDN connection request processing S12, the UE performs PDN Connectivity Request with Req_type as Emergency, via the eNB through the MME / S. -When transmitting to the GW, include the specific APN in the PDN Connectivity Request.
 ここで送信するAPNは、ネットワークオペレータ等によってリアルタイムゲーム用に特定されている。MME/S-GWは、PDN Connectivity Requestに含まれるAPNが、リアルタイムゲームに対応するか否かを判定する。この判定は、MME/S-GWが、例えばメモリ230(図3)に記憶するテーブル等を用いて行い、当該APNがリアルタイムゲームに対応すると判定した場合は、例えば図5に示したQCI特性表に基づいて、リアルタイムゲーム用のベアラを確立するめのDedicated Bearer確立処理S132を実行し、MME/S-GWがリアルタイムゲーム(アプリケーション)に対応付けられたベアラ(QCI)の割り当てを行う。 The APN transmitted here is specified for a real-time game by a network operator or the like. The MME / S-GW determines whether or not the APN included in the PDN Connectivity Request corresponds to the real-time game. This determination is performed by the MME / S-GW using, for example, a table stored in the memory 230 (FIG. 3). If it is determined that the APN corresponds to the real-time game, for example, the QCI characteristic table shown in FIG. Based on the above, a Dedicated Bearer establishment process S132 for establishing a bearer for a real-time game is executed, and the MME / S-GW assigns a bearer (QCI) associated with the real-time game (application).
 すなわち、MME/S-GWは、リアルタイムゲーム用のベアラを確立するためのDedicated Bearer確立処理S132を実行する際に、Activate Dedicated EPS Bearer Context Requestメッセージに、図5に示したQCI特性表に基づいて決定したQCI=4の値を含ませてUEに送信する。 That is, when executing the Dedicated Bearer establishment process S132 for establishing a bearer for a real-time game, the MME / S-GW is based on the QCI characteristic table shown in FIG. 5 in the Activate Dedicated EPS Bearer Context Request message. The determined value of QCI = 4 is included and transmitted to the UE.
 QCI=4では優先度が3であるので、通常のデータ通信よりも優先的に緊急用データ通信を行うことができ、GBRも設定されているので送信速度も保証され、安定して利用することが可能となる。 When QCI = 4, the priority is 3, so emergency data communication can be performed with priority over normal data communication, and the GBR is also set, so the transmission speed is guaranteed and the data can be used stably. Is possible.
 以上説明したように、緊急用データ通信に際しては、緊急用データ通信のための専用のQCIや優先度を設定するのではなく、高優先度のQCIが割り当てられたアプリケーションにカモフラージュするので、標準化されたQCI特性表を使用することができ、LTEシステムに加える改変が少なくて済む。 As described above, emergency data communication is standardized because it does not set a dedicated QCI or priority for emergency data communication, but camouflages the application to which a high-priority QCI is assigned. QCI characteristic tables can be used, and fewer modifications are made to the LTE system.
 なお、以上説明した実施の形態1およびその変形例1および2では、VoLTEへの適用を前提として説明したが、実施の形態1およびその変形例1および変形例2は、VoLTEへの適用に限定されず、LTEシステムであれば適用可能である。 In the first embodiment and its modifications 1 and 2 described above, the description has been made on the assumption that they are applied to VoLTE. However, the first embodiment and its modifications 1 and 2 are limited to application to VoLTE. However, the present invention is applicable to any LTE system.
 (実施の形態2)
 以上説明した実施の形態1においては、LTEシステムにおいてUEから緊急用データ発信をする場合について説明した。しかし、緊急用データ発信が多用されることで、本当に緊急性のあるデータ通信の速度が遅延するという弊害が起きる可能性もあるので、緊急用データ通信の実行に制限をかけるようにしても良い。以下、実施の形態2として、緊急用データ通信の実行に制限をかけた構成について説明する。
(Embodiment 2)
In Embodiment 1 demonstrated above, the case where emergency data transmission was transmitted from UE in the LTE system was demonstrated. However, since the emergency data transmission is frequently used, there is a possibility that the speed of the truly urgent data communication may be delayed. Therefore, the execution of the emergency data communication may be limited. . Hereinafter, as Embodiment 2, a configuration in which execution of emergency data communication is restricted will be described.
 図11は実施の形態2のLTEシステムにおいてUEが緊急呼を発信した場合の制御手順を示す図である。なお、図11においては、eNBおよびMME/S-GWをまとめてネットワーク装置(NW)として記載している。 FIG. 11 is a diagram illustrating a control procedure when the UE transmits an emergency call in the LTE system according to the second embodiment. In FIG. 11, the eNB and the MME / S-GW are collectively described as a network device (NW).
 図11に示すように、アイドル(Idle)状態にあるUEにおいて、例えばユーザインターフェイス120(図3)を介して緊急呼発信のための操作がなされると、UEとeNBは、RRC Connection確立処理S21を実行する。RRC Connection確立処理S11では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 As shown in FIG. 11, in the UE in the idle state, when an operation for emergency call transmission is performed via the user interface 120 (FIG. 3), for example, the UE and the eNB perform RRC Connection establishment process S21. Execute. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 なお、RRC Connection確立処理S21では、eNBからUEへのRRC Connection Setupの送信および、UEからeNBへのRRC Connection Setup Completeの送信もあるが、図示は省略する。また、RRC Connectionに続いて音声用のベアラを確立するためのデフォルトベアラ確立処理が実行されるが、図示は省略する。 In the RRC connection establishment process S21, there is an RRC connection setup transmission from the eNB to the UE and an RRC connection setup complete transmission from the UE to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer is executed following RRC Connection, illustration is omitted.
 音声用のベアラを確立するためのデフォルトベアラ確立処理により、UEとMME/S-GWとがデータ交換可能となった後、第1のPDN接続要求処理S22において、UEが、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する。 After the default bearer establishment process for establishing a voice bearer enables data exchange between the UE and the MME / S-GW, the UE sets Req_type to Emergency in the first PDN connection request process S22. PDN Connectivity Request is transmitted to MME / S-GW via eNB.
 PDN Connectivity Requestを受信したMME/S-GWは、緊急呼に係るIMSシグナリング(制御信号)用のベアラを確立するためのDeafault Bearer確立処理S23を実行し、Activate Default EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、図5に示した標準化されたQCI特性表に基づいて、音声通信を管理するためのIMSシグナリングに対応するQCI=5を割り当てる。 Upon receiving the PDN Connectivity Request, the MME / S-GW executes a Default Bearer establishment process S23 for establishing a bearer for IMS signaling (control signal) related to an emergency call, and sends an Activate Default EPS Bearer Quest Request Queue Request Quest Request Queue Request Queue Request Message Include value and send to UE. Here, based on the standardized QCI characteristic table shown in FIG. 5, QCI = 5 corresponding to IMS signaling for managing voice communication is assigned.
 なお、緊急呼に係るIMSシグナリング用のベアラを確立するためのDeafault Bearer確立処理S23では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMME/S-GWにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。 In the default bearer establishment process S23 for establishing a bearer for IMS signaling related to an emergency call, the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
 次に、MME/S-GWは、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S24を実行し、Activate Dedicated EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、図5に示した標準化されたQCI特性表に基づいて、VoIPに対応するQCI=1を割り当てる。 Next, the MME / S-GW executes a dedicated bearer establishment process S24 for establishing a bearer for voice data related to the emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Request Request message to the UE. Send. Here, QCI = 1 corresponding to VoIP is assigned based on the standardized QCI characteristic table shown in FIG.
 なお、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S24では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMMEにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。以上のような手順を経てVoLTEによる音声通信が開始される。 In the Dedicated Bearer establishment process S24 for establishing a bearer for voice data related to an emergency call, the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
 上述したように、例えば警察への電話をかけた際に、UEにおいて、緊急用データ通信の実行(緊急用データの送信)が必要となった場合、例えば交通事故発生時に、警察への電話をすると共に事故現場の写真や動画を送信する必要が生じた場合、第2のPDN接続要求処理S25において、UEが、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する際に、特定のAPNをPDN Connectivity Requestに含めて送信する。なお、UEは、警察への電話をかけた場合をもって、上述した緊急用データ通信の実行(緊急用データの送信)が必要となった場合と判断しても良く、つまり、警察への電話をかけた際に、自動的に、緊急用データ通信の実行(緊急用データの送信)が必要と判断しても良い。 As described above, for example, when calling the police, if the UE needs to execute emergency data communication (emergency data transmission), for example, when a traffic accident occurs, call the police. In the second PDN connection request processing S25, the UE sends a PDN Connectivity Request with Req_type as Emergency in the second PDN connection request processing S25 via the eNB via the MME / S-GW. When transmitting to the PDN, a specific APN is included in the PDN Connectivity Request and transmitted. Note that the UE may determine that it is necessary to execute the emergency data communication described above (transmission of emergency data) when making a call to the police, that is, call the police. When making a call, it may be automatically determined that emergency data communication (emergency data transmission) is necessary.
 ここで、PDN Connectivity Requestに含めて送信されたAPNは、例えば、実施の形態1において説明した、ネットワークオペレータ等によって緊急用データ通信用に特定されたAPN、または、実施の形態1の変形例1において説明した、ネットワークオペレータ等によって例えばリアルタイムゲーム用と緊急用データ通信用に特定されたAPN、または実施の形態1の変形例2において説明した、ネットワークオペレータ等によって例えばリアルタイムゲーム用に特定されたAPNである。 Here, the APN included in the PDN Connectivity Request is, for example, the APN specified for emergency data communication by the network operator or the like described in the first embodiment, or the first modification of the first embodiment. The APN specified for the real-time game and emergency data communication, for example, by the network operator described in the above, or the APN specified for the real-time game, for example, by the network operator described in the second modification of the first embodiment It is.
 その後、MME/S-GWは、緊急用データ通信用のベアラを確立するためのDedicated Bearer確立処理S26を実行する際に、Activate Dedicated EPS Bearer Context Requestメッセージに、図5、図7および図8に示した何れかのQCI特性表に基づいて決定したQCIの値(X)を含ませてUEに送信することで、少なくとも通常のデータ通信よりも高い優先度で緊急用データ通信を行うことができ、GBRも設定されているので送信速度も保証され、安定して利用することが可能となる。 After that, when the MME / S-GW executes the Dedicated Bearer establishment process S26 for establishing the bearer for emergency data communication, the MME / S-GW displays the Activate Dedicated EPS Bearer Context Request message in FIG. 5, FIG. 7 and FIG. By including the QCI value (X) determined based on any of the shown QCI characteristic tables and transmitting it to the UE, at least emergency data communication can be performed with higher priority than normal data communication. , GBR is also set, so that the transmission speed is guaranteed and it can be used stably.
 以上説明したように、実施の形態2のLTEシステムにおいては、例えば警察への電話などの第1のPDN接続要求処理を行った後でなければ、高い優先度での緊急用データ通信を行うことができないので、緊急呼が多用されることによる弊害を抑制することができる。 As described above, in the LTE system according to the second embodiment, emergency data communication with high priority is performed unless the first PDN connection request processing such as a telephone call to the police is performed. Therefore, harmful effects caused by frequent use of emergency calls can be suppressed.
  (変形例)
 以上説明した実施の形態2においては、緊急呼用のベアラ確立のために第1のPDN接続要求処理を行った後に、緊急用データ通信用のベアラ確立のために第2のPDN接続要求処理を行うことで、高い優先度等の高いQoSで緊急用データ通信を行える構成を示したが、緊急呼を発信する際に、緊急用データ通信も要求することで、1回のPDN接続要求処理で緊急用データ通信を実行できるようにしても良い。
(Modification)
In the second embodiment described above, after performing the first PDN connection request process for establishing the bearer for emergency call, the second PDN connection request process for establishing the bearer for emergency data communication is performed. By doing so, a configuration has been shown in which emergency data communication can be performed with a high QoS such as a high priority. However, when an emergency call is made, an emergency data communication is also requested so that a single PDN connection request process is performed. You may enable it to perform emergency data communication.
 図12は実施の形態2の変形例のLTEシステムにおいてUEから緊急呼が発信された場合の制御手順を示す図である。 FIG. 12 is a diagram illustrating a control procedure when an emergency call is transmitted from the UE in the LTE system according to the modification of the second embodiment.
 図12に示すように、アイドル(Idle)状態にあるUEにおいて、例えばユーザインターフェイス120(図3)を介して緊急呼発信のための操作がなされると、UEとeNBは、RRC Connection確立処理S31を実行する。RRC Connection確立処理S11では、UEがeNBに対してcauseをEmergencyとしたRRC Connection Requestを送信する。 As shown in FIG. 12, in the UE in the idle state, for example, when an operation for emergency call transmission is performed via the user interface 120 (FIG. 3), the UE and the eNB perform RRC Connection establishment processing S31. Execute. In the RRC connection establishment process S11, the UE transmits an RRC connection request with the cause being “Emergency” to the eNB.
 なお、RRC Connection確立処理S31では、eNBからUEへのRRC Connection Setupの送信および、UEからeNBへのRRC Connection Setup Completeの送信もあるが、図示は省略する。また、RRC Connectionに続いて音声用のベアラを確立するためのデフォルトベアラ確立処理が実行されるが、図示は省略する。 In the RRC connection establishment process S31, there is a transmission of the RRC connection setup from the eNB to the UE and a transmission of the RRC connection setup complete from the UE to the eNB, but the illustration is omitted. Further, although a default bearer establishment process for establishing a voice bearer is executed following RRC Connection, illustration is omitted.
 音声用のベアラを確立するためのデフォルトベアラ確立処理により、UEとMME/S-GWとがデータ交換可能となった後、PDN接続要求処理S32において、UEが、Req_typeをEmergencyとしたPDN Connectivity Requestを、eNBを経由してMME/S-GWに送信する際に、特定のAPNをPDN Connectivity Requestに含めて送信する。このAPNは、実施の形態1または、その変形例1または変形例2において説明したAPNであり、重複する説明は省略する。 After data exchange between the UE and the MME / S-GW is enabled by the default bearer establishment process for establishing a voice bearer, the PDN connection request process S32 causes the UE to use the PDN Connectivity Request with Req_type as Emergency. Is transmitted to the MME / S-GW via the eNB, the specific APN is included in the PDN Connectivity Request and transmitted. This APN is the APN described in the first embodiment or the first modification or the second modification thereof, and a duplicate description is omitted.
 PDN Connectivity Requestを受信したMME/S-GWは、緊急呼に係るIMSシグナリング用のベアラを確立するためのDeafault Bearer確立処理S33を実行し、Activate Default EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、図5に示した標準化されたQCI特性表に基づいて、音声通信を管理するためのIMSシグナリングに対応するQCI=5を割り当てる。 Upon receiving the PDN Connectivity Request, the MME / S-GW executes the Default Bearer establishment process S33 for establishing the bearer for IMS signaling related to the emergency call, and includes the Activate Default EPS Bearer Context Request message value in the Request Queue Request Quest message value. To the UE. Here, based on the standardized QCI characteristic table shown in FIG. 5, QCI = 5 corresponding to IMS signaling for managing voice communication is assigned.
 なお、緊急呼に係るIMSシグナリング用のベアラを確立するためのDeafault Bearer確立処理S33では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMME/S-GWにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。 In the default bearer establishment process S33 for establishing a bearer for IMS signaling related to an emergency call, the MME / S-GW sends an E-RAB Setup Request to the eNB, and the eNB sends an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME / S-GW, but illustration is omitted.
 次に、MME/S-GWは、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S34を実行し、Activate Dedicated EPS Bearer Context RequestメッセージにQCIの値を含ませてUEに送信する。ここでは、図5に示したQCI特性表に基づいて、VoIPに対応するQCI=1を割り当てる。 Next, the MME / S-GW executes a dedicated bearer establishment process S34 for establishing a bearer for voice data related to an emergency call, and includes the QCI value in the Activate Dedicated EPS Bearer Context Request message to the UE. Send. Here, QCI = 1 corresponding to VoIP is assigned based on the QCI characteristic table shown in FIG.
 なお、緊急呼に係る音声データ用のベアラを確立するためのDedicated Bearer確立処理S34では、MME/S-GWがeNBにE-RAB Setup Requestを送信し、eNBがUEにRRC Connection Reconfigurationを送信し、UEがeNBにRRC Connection Reconfiguration Completeを送信し、eNBがMMEにE-RAB Setup Responseを送信する手順も含まれるが、図示は省略する。以上のような手順を経てVoLTEによる音声通信が開始される。 In the Dedicated Bearer establishment process S34 for establishing a bearer for voice data related to an emergency call, the MME / S-GW transmits an E-RAB Setup Request to the eNB, and the eNB transmits an RRC Connection Reconfiguration to the UE. Also included is a procedure in which the UE transmits an RRC Connection Reconfiguration Complete to the eNB, and the eNB transmits an E-RAB Setup Response to the MME, which is not shown. Voice communication by VoLTE is started through the above procedure.
 その後、MME/S-GWは、緊急用データ通信用のベアラを確立するためのDedicated Bearer確立処理S35を実行する際に、Activate Dedicated EPS Bearer Context Requestメッセージに、図5、図7および図8に示した何れかのQCI特性表に基づいて決定したQCIの値(X)を含ませてUEに送信することで、少なくとも通常のデータ通信よりも高い優先度で緊急用データ通信を行うことができ、GBRも設定されているので送信速度も保証され、安定して利用することが可能となる。 After that, when the MME / S-GW executes the Dedicated Bearer establishment process S35 for establishing the bearer for emergency data communication, the MME / S-GW adds the Activate Dedicated EPS Bearer Context Request message to FIG. 5, FIG. 7 and FIG. By including the QCI value (X) determined based on any of the shown QCI characteristic tables and transmitting it to the UE, at least emergency data communication can be performed with higher priority than normal data communication. , GBR is also set, so that the transmission speed is guaranteed and it can be used stably.
 以上説明したように、実施の形態2の変形例のLTEシステムにおいては、例えば警察への電話と共に、緊急用データ通信も要求するので、例えば、UEが無線通信端末である場合、交通事故発生時に、警察に電話するだけでなく、無線通信端末で撮影した事故現場の写真や動画を送信したい場合に、1回のPDN接続要求処理で緊急用データ通信も実行できれば、ユーザにとってより利便性の高いシステムとなる。 As described above, in the LTE system according to the modification of the second embodiment, for example, emergency data communication is requested together with a call to the police. For example, when a UE is a radio communication terminal, when a traffic accident occurs , It is more convenient for users if not only to call the police, but also to send emergency site data and data in a single PDN connection request process when they want to send pictures and videos of accidents taken with wireless communication terminals. System.
 なお、本発明は、その発明の範囲内において、各実施の形態を自由に組み合わせたり、各実施の形態を適宜、変形、省略することが可能である。 It should be noted that the present invention can be freely combined with each other within the scope of the invention, and each embodiment can be appropriately modified or omitted.

Claims (14)

  1.  ネットワーク装置に対して緊急用データ通信の実行を要求し、当該要求に応じて前記ネットワーク装置から送信された前記緊急用データ通信に対応したサービス品質クラス識別子(QCI)を受信し、該サービス品質クラス識別子に基づいて前記ネットワーク装置を介して前記緊急用データ通信する処理を行う制御部を備える、無線通信端末。 A network device is requested to execute emergency data communication, and a quality of service class identifier (QCI) corresponding to the emergency data communication transmitted from the network device in response to the request is received. A wireless communication terminal comprising a control unit that performs a process of performing the emergency data communication via the network device based on an identifier.
  2.  前記緊急用データ通信に対応したサービス品質クラス識別子は、
     前記緊急用データ通信に専用のサービス品質クラス識別子である、請求項1記載の無線通信端末。
    The service quality class identifier corresponding to the emergency data communication is:
    The wireless communication terminal according to claim 1, wherein the wireless communication terminal is a service quality class identifier dedicated to the emergency data communication.
  3.  前記緊急用データ通信に専用のサービス品質クラス識別子は、
     前記ネットワーク装置のメモリに記憶された、前記緊急用データ通信に専用のサービス品質クラス識別子を含むQCI特性表に基づいて割り当てられる、請求項2記載の無線通信端末。
    The quality of service class identifier dedicated to the emergency data communication is:
    The wireless communication terminal according to claim 2, wherein the wireless communication terminal is assigned based on a QCI characteristic table including a quality of service class identifier dedicated to the emergency data communication stored in a memory of the network device.
  4.  前記緊急用データ通信に対応したサービス品質クラス識別子は、
     他のアプリケーションと兼用のサービス品質クラス識別子である、請求項1記載の無線通信端末。
    The service quality class identifier corresponding to the emergency data communication is:
    The wireless communication terminal according to claim 1, wherein the wireless communication terminal is a service quality class identifier shared with another application.
  5.  前記他のアプリケーションと兼用のサービス品質クラス識別子は、
     前記ネットワーク装置のメモリに記憶された、前記サービス品質クラス識別子の適用対象のアプリケーションに前記他のアプリケーション及び前記緊急用データ通信を含むQCI特性表に基づいて割り当てられる、請求項4記載の無線通信端末。
    The service quality class identifier that is also used for the other application is:
    The wireless communication terminal according to claim 4, wherein the wireless communication terminal is assigned to an application to which the service quality class identifier is applied, based on a QCI characteristic table including the other application and the emergency data communication, which is stored in a memory of the network device. .
  6.  前記緊急用データ通信に対応したサービス品質クラス識別子には、少なくとも通常のデータ通信よりも高い優先度が割り当てられる、請求項1記載の無線通信端末。 The wireless communication terminal according to claim 1, wherein at least a higher priority than normal data communication is assigned to the service quality class identifier corresponding to the emergency data communication.
  7.  前記制御部は、
     緊急呼の発信を契機として前記ネットワーク装置に対する緊急用データ通信の実行を要求する処理を行う、請求項1記載の無線通信端末。
    The controller is
    The wireless communication terminal according to claim 1, wherein processing for requesting execution of emergency data communication with respect to the network device is performed when an emergency call is transmitted.
  8.  前記制御部は、
     前記ネットワーク装置に対して前記緊急用データ通信の実行を要求する際に、前記緊急用データ通信に対応するPDN Connectivity Requestを前記ネットワーク装置に対して送信する処理を行う、請求項1記載の無線通信端末。
    The controller is
    2. The wireless communication according to claim 1, wherein when the network device is requested to execute the emergency data communication, a process of transmitting a PDN Connectivity Request corresponding to the emergency data communication to the network device is performed. Terminal.
  9.  前記緊急用データ通信に対応するPDN Connectivity Requestは、前記緊急用データ通信に対応する特定のアクセスポイント名(APN)を含むPDN Connectivity Requestである、請求項8記載の無線通信端末。 The wireless communication terminal according to claim 8, wherein the PDN connectivity request corresponding to the emergency data communication is a PDN connectivity request including a specific access point name (APN) corresponding to the emergency data communication.
  10.  前記制御部は、
     緊急呼の発信の際に、当該緊急呼に対応するPDN Connectivity Requestを送信し、その後に前記緊急用データ通信に対応するPDN Connectivity Requestを送信する処理を行う、請求項7記載の無線通信端末。
    The controller is
    The wireless communication terminal according to claim 7, wherein when an emergency call is transmitted, a process of transmitting a PDN Connectivity Request corresponding to the emergency call and thereafter transmitting a PDN Connectivity Request corresponding to the emergency data communication is performed.
  11.  前記制御部は、
     緊急呼の発信の際に、当該緊急呼に対応し、なお且つ前記緊急用データ通信に対応するPDN Connectivity Requestを送信する処理を行う、請求項7記載の無線通信端末。
    The controller is
    The wireless communication terminal according to claim 7, wherein when an emergency call is transmitted, a process of transmitting a PDN Connectivity Request corresponding to the emergency call and corresponding to the emergency data communication is performed.
  12.  緊急用データ通信の実行をする際に、当該緊急用データ通信に対応する他のアプリケーションの実行をネットワーク装置に対して要求し、当該要求に応じて前記ネットワーク装置から送信された前記他のアプリケーションに対応するサービス品質クラス識別子(QCI)を受信し、該サービス品質クラス識別子に基づいて、前記ネットワーク装置を介して前記緊急用データ通信する処理を行う制御部を備える、無線通信端末。 When executing emergency data communication, the network device is requested to execute another application corresponding to the emergency data communication, and the other application transmitted from the network device in response to the request is sent to the network device. A wireless communication terminal comprising a control unit that receives a corresponding service quality class identifier (QCI) and performs processing for performing the emergency data communication via the network device based on the service quality class identifier.
  13.  (a)無線通信端末が、ネットワーク装置に対して緊急用データ通信の実行を要求するステップと、
     (b)前記ネットワーク装置が、前記緊急用データ通信に対応したサービス品質クラス識別子(QCI)を前記無線通信端末に送信するステップと、
     (c)前記無線通信端末が、前記サービス品質クラス識別子(QCI)を受信すると、該サービス品質クラス識別子に基づいて、前記ネットワーク装置を介して前記緊急用データ通信を行うステップと、を備える、通信制御方法。
    (A) a step in which the wireless communication terminal requests the network device to perform emergency data communication;
    (B) the network device transmitting a quality of service class identifier (QCI) corresponding to the emergency data communication to the wireless communication terminal;
    (C) when the wireless communication terminal receives the quality of service class identifier (QCI), performs the emergency data communication via the network device based on the quality of service class identifier. Control method.
  14.  無線通信端末から緊急用データ通信の実行の要求を受けると、当該要求に応じて、前記緊急用データ通信に対応した、前記無線通信端末が前記緊急用データ通信を行う際に用いるサービス品質クラス識別子(QCI)を、前記無線通信端末に送信する処理を行う制御部を備える、ネットワーク装置。 Upon receiving a request for execution of emergency data communication from a wireless communication terminal, a service quality class identifier used when the wireless communication terminal performs the emergency data communication corresponding to the emergency data communication in response to the request A network apparatus provided with the control part which performs the process which transmits (QCI) to the said radio | wireless communication terminal.
PCT/JP2015/085317 2014-12-25 2015-12-17 Wireless communication terminal, communication control method, and network device WO2016104311A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014-262492 2014-12-25
JP2014262492 2014-12-25

Publications (1)

Publication Number Publication Date
WO2016104311A1 true WO2016104311A1 (en) 2016-06-30

Family

ID=56150332

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/085317 WO2016104311A1 (en) 2014-12-25 2015-12-17 Wireless communication terminal, communication control method, and network device

Country Status (1)

Country Link
WO (1) WO2016104311A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013053376A1 (en) * 2011-10-10 2013-04-18 Telefonaktiebolaget L M Ericsson (Publ) A method of and apparatus for establishing bearer attributes

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013053376A1 (en) * 2011-10-10 2013-04-18 Telefonaktiebolaget L M Ericsson (Publ) A method of and apparatus for establishing bearer attributes

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.401 V12.7.0, 17 December 2014 (2014-12-17), pages 73 - 75 , 236-242 *

Similar Documents

Publication Publication Date Title
US20220132603A1 (en) Apparatus, system, method, and computer-readable medium for connection-oriented vehicle-to-x (vtx) communication in 5g
US10952094B2 (en) AT commands for 5G QoS management
CN111182540B (en) Data transmission guaranteeing method and communication equipment
CN108323245B (en) Registration and session establishment method, terminal and AMF entity
JP2023120188A (en) Method of managing connection to local area data network (ladn) in 5g network
US20220022089A1 (en) Service instance indication for resource creation
CN108141867B (en) Method for improved priority handling of data stream transmissions in a communication system
KR20130019024A (en) Paging method, core network device, wireless access network device, and gateway device
US20190124563A1 (en) Communication method and device
JP2017511981A (en) Data rate control in UE (UE-R) that relays traffic to and from relayed UEs
CN108024284B (en) Wireless communication method, user equipment access network equipment and core network equipment
KR20120093491A (en) Method and apparatus for providing an emergency communication in a wireless communication system
WO2018170747A1 (en) Communication method and apparatus
US20230189054A1 (en) Relay communication method, and communication apparatus
CN113950851A (en) Wireless communication method and apparatus
WO2022161148A1 (en) Quality of service control method and apparatus
CN114173368A (en) Method for monitoring QoS
WO2022068687A1 (en) Edge computing method and apparatus
KR102084038B1 (en) Method and Apparatus for Priority Processing Important Data Packet
CN114586405B (en) Method and device for reporting measurement report
CN117156457A (en) Quality of service QoS adjustment method and device
WO2016104311A1 (en) Wireless communication terminal, communication control method, and network device
KR101830224B1 (en) Method for controlling packet traffic and apparatus therefor
WO2023185608A1 (en) Data transmission method and communication apparatus
CN113906783A (en) Communication method, device and system

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

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP