WO2016175634A1 - 무선 통신 시스템에서 재난 안전망 용 베어러를 형성하는 방법 및 장치 - Google Patents
무선 통신 시스템에서 재난 안전망 용 베어러를 형성하는 방법 및 장치 Download PDFInfo
- Publication number
- WO2016175634A1 WO2016175634A1 PCT/KR2016/004606 KR2016004606W WO2016175634A1 WO 2016175634 A1 WO2016175634 A1 WO 2016175634A1 KR 2016004606 W KR2016004606 W KR 2016004606W WO 2016175634 A1 WO2016175634 A1 WO 2016175634A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mcptt
- bearer
- service
- terminal
- mme
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/02—Arrangements for increasing efficiency of notification or paging channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
Definitions
- the present invention relates to a wireless communication system, and more particularly, to a method and apparatus for forming a bearer for easily using a disaster safety net service.
- a 5G communication system or a pre-5G communication system is called a Beyond 4G network communication system or a post LTE system.
- 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
- mmWave ultra-high frequency
- FD-MIMO massive array multiple input / output
- FD-MIMO massive array multiple input / output
- Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
- 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation
- cloud RAN cloud radio access network
- ultra-dense network ultra-dense network
- D2D Device to Device communication
- wireless backhaul moving network
- cooperative communication Coordinated Multi-Points (CoMP), and interference cancellation
- Hybrid FSK and QAM Modulation FQAM
- SWSC Slide Window Superposition Coding
- ACM Advanced Coding Modulation
- FBMC Fan Bank Multi Carrier
- NOMA non orthogonal multiple access
- SCMA sparse code multiple access
- PS-LTE public safely LTE
- the present invention provides a method and an apparatus in which a terminal has a high priority in using a disaster safety net service, and the terminal can be allocated resources according to the high priority.
- receiving a first message including information about public safety and based on the received message may include forming a bearer having a higher priority than a preset bearer.
- MME mobility management entity
- a control unit for forming a bearer having a higher priority than the set bearer may include a control unit for forming a bearer having a higher priority than the set bearer.
- the terminal when a terminal uses a disaster safety net service, the terminal has a high priority, and the terminal can be allocated a resource according to the high priority.
- FIG. 1 is a sequence diagram illustrating a method for a UE to use a disaster safety net transmitting a service request to an MME and changing a bearer context for use of the disaster safety net according to an embodiment of the present invention.
- FIG. 2 is a sequence diagram illustrating a method in which a terminal intending to use a disaster safety net transmits a disaster safety net service request to an MME, and activates a second bearer context by the MME to use the disaster safety net according to an embodiment of the present invention.
- FIG. 3 is a sequence illustrating a method for a terminal to use a disaster safety net receiving a paging signal for disaster safety net service and forming a bearer for the terminal where the MME receives the paging signal according to an embodiment of the present invention.
- FIG. 4 is a diagram illustrating an example of forming a bearer for using the disaster safety net by the PGW receiving the information on the disaster safety net, according to an embodiment of the present invention.
- FIG. 5 is a sequence diagram illustrating a method of forming a bearer for using the disaster safety net when the terminal intending to use the disaster safety net transmits an access request message according to an embodiment of the present invention.
- FIG. 6 is a block diagram illustrating components of an MME according to an embodiment of the present invention.
- the Public Safety LTE uses Mission Critical Push To Talk over LTE (MCPTT) technology to provide users with services to communicate for public safety.
- MCPTT is one of the technologies defined by 3GPP and provides features including group communication between users, one-to-one communication, emergency calls, disaster notifications, and listening to ambient sounds.
- the MCPTT service consists of a UE, an Evolved Packet System (EPS), a Session Initiation Protocol (SIP) Core, and an MCPTT Application Server.
- EPS may refer to LTE network
- SIP Core refers to a network composed of core devices using Session Initiation Protocol.
- IMS Internet Multimedia Subsystem.
- the MCPTT service may be deployed in various structures. MCPTT operators can operate EPS, SIP Core, and even MCPTT Application Server.
- the MCPTT service provider can operate the SIP Core and MCPTT Application Server and provide services in conjunction with the EPS of other providers.
- MCPTT service provider can operate only MCPTT Application Server and provide services by interworking with EPS and SIP Core of other service providers.
- the MCPTT service can be divided into group call, one-to-one call, and emergency alert.
- the group call provides a general call for public safety, an emergency call that provides communication with the highest priority in case of an emergency / emergency situation, and prepares for an impending emergency / emergency with lower priority than an emergency call. It can support Imminent Peril Call which enables group communication.
- One-to-one calls support regular calls, emergency calls, and the Ambient Listening feature, which allows you to listen to the other party's surroundings.
- the emergency notification refers to a function that can transmit its emergency / emergency situation to the MCPTT system or other MCPTT user as a notification, it may be called an emergency alert.
- the emergency call provided by the MCPTT may support group communication functions unlike the existing emergency call. Therefore, the terminal should be able to receive as well as send an emergency call. Emergency call, its next priority, Imminent Peril call, and Emergency Alert can all be processed in priority over general communication in EPS, SIP Core and MCPTT Application Server. Therefore, there is a requirement that a call requiring a high priority as above should be able to establish a connection and send and receive data faster than other calls.
- the present invention provides a method for establishing a connection so that the MCPTT terminal can be allocated resources preferentially in the EPS and preferentially transmit data by giving a high priority to a terminal using a disaster safety net (hereinafter referred to as MCPTT).
- MCPTT disaster safety net
- the emergency call control present in the EPS currently considers only the Mobile Originated situation in which the terminal attempts to make an emergency call by establishing a connection, and the MCPTT service is not separately controlled.
- MCPTTs may have a higher priority than general services for disaster safety net services and should be applicable to EPS.
- MCPTT can transmit / receive group call or one-to-one call, it should be able to support not only Mobile Originated situation but also Mobile Terminated situation that must answer MCPTT call coming to MCPTT terminal.
- the present invention proposes a method in which the MCPTT terminal may have a high priority in using the MCPTT system, a method of allocating radio resources according to the method, and a method of notifying that the MCPTT terminal is an MCPTT terminal when the MCPTT terminal accesses the MCPTT system.
- MCPTT represents one of the disaster safety net services, and is a concept including a service having a different name supporting group communication between terminals and one-to-one communication, or emergency / emergency communication.
- Embodiments of the present invention may be similarly used in wireless communication, such as WLAN and Bluetooth, in addition to the described communication system.
- the priority of the overall MCPTT service handled in the present invention may be a priority of a part of the MCPTT service, for example, an emergency call having the highest priority or an imminent peril call having a second priority.
- the Mobile Originated scenario in which the MCPTT terminal initiates priority connection to the EPS network as a method for providing priority to the MCPTT terminal the Mobile Terminated scenario in which the MCPTT terminal receives priority from the EPS network and makes a priority connection
- MCPTT The terminal will inform the EPS network that it is a MCPTT-enabled terminal and will explain how to access the terminal.
- MCPTT Normal Call which means MCPTT Basic Call operation, Emergency Call having the highest priority, Imminent Peril Call, which is the next priority call, Ambient Listening, which is the ambient sound listening function, and Emergency Alert.
- Different MCPTT services may provide different priorities.
- EPS means Evolved Packet System or LTE network.
- the EPS consists of an E-UTRAN between the UE and the eNB and an Evolved Packet Core (EPC), which is a core network of the LTE system.
- EPC is composed of MME, S-GW, P-GW, PCRF and the like.
- EPS is connected to a SIP Core in order to be connected to an MCPTT service, and the SIP Core may mean a network of core devices using a Session Initiation Protocol (SIP) and may refer to an Internet Multimedia Subsystem (IMS). Therefore, an IMS device such as P-CSCF referred to herein means a SIP Core device for MCPTT.
- MCPTT Application Server means a network device for exchanging information of the Application layer for providing the MCPTT service, the meaning is not limited to the name of the Application Server various logical / physical devices required to configure the MCPTT service It may mean.
- FIG. 1 is a sequence diagram illustrating a method for a UE to use a disaster safety net transmitting a service request to an MME and changing a bearer context for use of the disaster safety net by an embodiment of the present invention.
- the MCPTT terminal 100 transmits an extended service request to the MME 300 to establish an MCPTT connection to the EPS network, thereby receiving a bearer having a priority corresponding to the MCPTT.
- Radio resources can be used by allocation.
- FIG. 1 is a diagram illustrating a method and procedure for a MCPTT terminal 100 to transmit a service request for MCPTT to an MME 300 and to receive a bearer applying QoS suitable for MCPTT.
- the MCPTT terminal 100 needs to activate a bearer of the EPS network to use the MCPTT service, and initiates this request by sending an extended service request to the MME 300.
- the MCPTT terminal 100 may transmit a service request message including at least one of information about a type of MCPTT and MCPTT capability to the MME 300.
- the Extended Service Request message includes a service type field, and the MCPTT terminal 100 may set and transmit an MCPTT service type in this field.
- the MCPTT service type may be set to MCPTT which refers to the MCPTT service as a whole, or a value may be set to classify the MCPTT service into emergency-related services among the MCPTT services.
- the MCPTT service type may be set to a value indicating a specific MCPTT service such as an MCPTT Group Call, an MCPTT Emergency Call, or an MCPTT Imminent Peril Call, an MCPTT Emergency Alert, an Ambient Listening, or a Private Call. .
- the MCPTT Emergency Call may be divided into an MCPTT Emergency Group Call, which represents an emergency group call, or an MCPTT Emergency Private Call, which represents an emergency one-to-one call.
- the MCPTT terminal 100 may specify that the MCPTT using terminal in the Device Property field of the Extended Service Request.
- Device property may indicate information on the capability of the MCPTT service, and comprehensively indicate that the UE is using MCPTT, or indicate that the UE uses an emergency related service among MCPTT services by dividing it into MCPTT Emergency. Value can be set. Or, more specifically, it may indicate information on the capability (Capability) to use a specific MCPTT service, such as MCPTT Emergency Call, MCPTT Imminent Peril Call, MCPTT Ambient Listening, MCPTT Private call.
- MCPTT Emergency service When distinguishable values for MCPTT Emergency service are set in the Service Type or Device Property, detailed services that can be provided for MCPTT Emergency are set differently for each EPS network provider or MCPTT service provider. Can be.
- the MCPTT terminal 100 When the MCPTT terminal 100 wants to use a service which is MCPTT Emergency, the MCPTT terminal 100 may use an extended service request, and a general MCPTT service may request a resource from the EPS network using the service request.
- the MME 300 may determine the type of the MCPTT service.
- the MME 300 that receives the Extended Service Request looks at the Service Type or Device Property included in the Extended Service Request, or both, and the MCPTT terminal 100. You can figure out which MCPTT service to use.
- the MME 300 may determine that the MCPTT terminal 100 uses the MCPTT Emergency service and apply a specific QoS for the service related to the emergency.
- the MME 300 may obtain QoS information for forming a bearer for a disaster safety net from a home subscriber server (HSS) 500.
- the QoS information that can be provided to the terminal 100 in order to use a specific MCPTT service by negotiating with the HSS 500, the MME 300 that the MCPTT terminal 100 determines which MCPTT service to use. Can be obtained.
- the QoS information may include a QCI value for identifying a QoS priority and an ARP value for indicating whether a resource can be preempted first.
- the MME 300 stores the obtained information as an internal setting value or stores the information in MME Emergency Configuration Data and proceeds with the rest of the process.
- the procedure between the MME 300 and the HSS 500 may be omitted, and in this case, the QoS value may be determined according to an internal setting value stored in the MME.
- the internal setting value stored in the MME 300 may be a value stored in the MME Emergency Configuration Data.
- the MME 300 may change the context for the default bearer based on the QoS information received from the HSS 500.
- the MME 300 determines what QoS to provide for the Extended Service Request sent by the MCPTT terminal 100, and then modifies the Context for the Default Bearer of the terminal sending the request to have a QoS value suitable for the MCPTT service. . For example, if the MME 300 determines that the MCPTT emergency service should be provided to the MCPTT terminal 100 that has sent the Extended Service Request, the existing default bearer context with a QCI or ARP value corresponding to the service. Change
- the MME 300 may transmit an initial context setup request to an evolved Node B (eNB) 200.
- eNB evolved Node B
- the MME 300 changes the default bearer context for the MCPTT terminal 100 according to the MCPTT service, the emergency service, or the detailed MCPTT service, and then initializes the initial context setup request to the eNB 200. Send a request to establish a bearer connection with the terminal 100 according to the changed Bearer Context.
- step S125 the eNB 200 may reset the RRC connection with the MCPTT terminal 100.
- the eNB 200 receiving the Initial Context Setup Request from the MME 300 prepares for generating a bearer according to Bearer Context, that is, QoS information contained in the Initial Context Setup Request, and sends an RRC Connection Reconfiguration to the MCPTT terminal 100 to the terminal. Establish a bearer connection between the 100 and the eNB 200 (step S130).
- the eNB 200 that has completed establishing the bearer connection with the MCPTT terminal 100 may transmit an initial context setup response to the MME 300. Specifically, the eNB 200 sends an Initial Context Setup Response to the MME 300 in response to an Initial Context Setup Request to inform that a Bearer having QoS set by the MME 300 is set to a Bearer ID.
- step S140 the MME 300 receives a Initial Context Setup Response and then sends a bearer modification request to the eNB 200 and the S-GW / P-GW 400. / P-GW 400 may be transmitted.
- step S145 a bearer connection is established between the eNB 200 and the S-GW / P-GW 400.
- the bearer connection established from the terminal 100 to the eNB 200 and the S-GW / P-GW 400 is a connection having a QoS value set by the MME 300 according to the MCPTT type in the above procedure, and the other bearer Can handle data delivery with higher priority.
- the P-GW (400) that the bearer connection establishment is complete may modify the IPF-CAN session with the PCRF (600).
- the P-GW 400 may transmit a newly established bearer and terminal information to a policy and charging rule function (PCRF) 600 to update the PCC rule and utilize it for charging or providing a service.
- PCRF policy and charging rule function
- the S-GW / P-GW 400 may transmit a bearer modification response to the MME 300.
- FIG. 2 is a diagram illustrating a method for a UE to use a disaster safety net transmitting a disaster safety net service request to an MME and activating a second bearer context for use of the disaster safety net according to an embodiment of the present invention. Sequence diagram.
- the MCPTT terminal 100 transmits an extended service request to the MME 300 to establish an MCPTT connection to the EPS network, thereby transmitting a priority corresponding to the MCPTT.
- Branches can be assigned a bearer to use radio resources.
- the name Emergency is used in the figure, it is obvious that the overall MCPTT service, the MCPTT Emergency, or the detailed MCPTT service may be represented.
- the MCPTT terminal 100 must activate the bearer of the EPS network to use the MCPTT service and sends the Extended Service Request to the MME 300 to initiate this request.
- the Extended Service Request message includes a service type field, and the MCPTT terminal 100 may set and transmit an MCPTT service type in this field.
- the MCPTT service type may be set to MCPTT which refers to the MCPTT service as a whole, or a value may be set to classify the MCPTT service into emergency-related services among the MCPTT services.
- the MCPTT service type may be set to a value indicating a specific MCPTT service such as an MCPTT Group Call, an MCPTT Emergency Call, an MCPTT Imminent Peril Call, an MCPTT Emergency Alert, an Ambient Listening, or a Private Call.
- the MCPTT Emergency Call may be divided into an MCPTT Emergency Group Call, which represents an emergency group call, or an MCPTT Emergency Private Call, which represents an emergency one-to-one call.
- the MCPTT terminal 100 may specify that the MCPTT using terminal in the Device Property field of the Extended Service Request.
- Device property may indicate information on the capability of the MCPTT service, and comprehensively indicate that the UE is using MCPTT, or indicate that the UE uses an emergency related service among MCPTT services by dividing it into MCPTT Emergency. Value can be set. Or, more specifically, it may indicate information on the capability (Capability) to use a specific MCPTT service, such as MCPTT Emergency Call, MCPTT Imminent Peril Call, MCPTT Ambient Listening, MCPTT Private call.
- MCPTT Emergency service When distinguishable values for MCPTT Emergency service are set in the Service Type or Device Property, detailed services that can be provided for MCPTT Emergency are set differently for each EPS network provider or MCPTT service provider. Can be.
- the MCPTT terminal 100 When the MCPTT terminal 100 wants to use a service which is MCPTT Emergency, the MCPTT terminal 100 may use an extended service request, and a general MCPTT service may request a resource from the EPS network using the service request.
- the MME 300 may determine the type of the MCPTT service.
- the MME 300 that receives the Extended Service Request looks at the Service Type or Device Property included in the Extended Service Request, or both, and the MCPTT terminal 100. You can figure out which MCPTT service to use.
- the service is used for the overall MCPTT, the emergency call among the MCPTT services, the Imminent Peril Call, the Ambient Listening, the Private Call, or the Emergency Alert. .
- the MME 300 determines that the MCPTT Emergency service is used, and may apply a specific QoS to the service related to the emergency.
- the difference from the first embodiment as shown in FIG. 1 is that the MME 300 knows in advance whether the terminal 100 can use the MCPTT service or not, and requests the MCPTT service. Secondary Default Bearer Context for MCPTT is stored in order to allocate Bearer suitable for QoS. Whether the terminal is a terminal that can use the MCPTT service will be addressed in another embodiment of the present invention.
- the MME 300 is setting a secondary default bearer context having a QoS value for the MCPTT in preparation for requesting the MCPTT service.
- the secondary default bearer context may be the context for the overall MCPTT, the context for the MCPTT Emergency service, or may have separate contexts for Emergency Call, Imminent Peril Call, Ambient Listening, Private Call, and Emergency Alert.
- Secondary Default Bearer Context is composed of the corresponding QCI or ARP value.
- the MME 300 may activate a second default bearer for the disaster safety net service.
- the MME 300 receiving the Extended Service Request transmitted from the MCPTT terminal 100 may check the MCPTT type and determine whether the terminal can use the service. After that, the bearer context corresponding to the MCPTT type requested by the terminal 100 among the bearer contexts stored in the MME 300 is selected as the secondary default bearer context, and the bearer connection establishment is started according to the QoS included in the context.
- step S215 the MME 300 transmits an initial context setup request to the eNB 200 using a bearer context in a secondary default bearer context.
- the eNB 200 may reset the RRC connection in step S220.
- the eNB 200 prepares a bearer generation according to a bearer context, that is, QoS information contained in an initial context setup request, and sends an RRC connection reconfiguration to the MCPTT terminal 100 to connect a bearer between the terminal 100 and the eNB 200. Establish. (Step S225)
- step S230 the eNB 200 has completed establishing the bearer connection with the terminal 100 sends an initial context setup response (Initial Context Setup Response) to the MME 300 in response to the Initial Context Setup Request to the MME to any Bearer ID. Notifies that the bearer having the QoS set by the 300 is set.
- an initial context setup response (Initial Context Setup Response) to the MME 300 in response to the Initial Context Setup Request to the MME to any Bearer ID.
- step S235 after receiving the Initial Context Setup Response, the MME 300 issues a S-GW / Modify Bearer Request for a connection between the eNB 200 and the S-GW / P-GW 400. May transmit to the P-GW 400.
- a bearer connection is established between the eNB 200 and the S-GW / P-GW 400.
- the bearer connection established from the terminal 100 to the eNB 200 and the S-GW / P-GW 400 is a connection having a QoS value set by the MME 300 according to the MCPTT type in the above procedure, and the other bearer Can handle data delivery with higher priority.
- the bearer connection establishment is complete P-GW (400) may modify the IP-CAN session with the PCRF (600).
- the P-GW 400 may transmit a newly established bearer and terminal information to a policy and charging rule function (PCR) 600 to update the PCC rule and utilize it for charging or providing a service.
- PCR policy and charging rule function
- the S-GW / P-GW 400 may transmit a bearer modification response to the MME 300.
- FIG. 3 illustrates a method in which a terminal intending to use a disaster safety net receives a paging signal for disaster safety net service, and forms a bearer for the terminal where the MME receives the paging signal according to an embodiment of the present invention. It is a sequence diagram to show.
- FIG. 3 is an embodiment according to the present invention.
- the MCPTT terminal 100 receives data having a high priority from the MCPTT service, a procedure for receiving paging by applying priority and a result according to paging are shown.
- the name Emergency is used in FIG. 3, it is apparent that the overall MCPTT service may be represented, or the MCPTT Emergency may be represented or the detailed MCPTT service may be represented.
- step S300 data on the MCPTT service usage from the MCPTT service is transferred from the MCPTT application server (800) to the P-CSCF (700).
- the P-CSCF 700 may determine whether signaling arriving from the MCPTT Application Server 800 should be processed with priority.
- Overall priority can be given to MCPTT services, or high priority can be given to MCPTT Emergency services, or detailed MCPTT services such as Emergency Call, Imminent Peril Call, Ambient Listening, Private Call, Emergency Alert, etc. Services can be classified and given priority.
- the P-CSCF 700 may transmit a signal including an indicator for the disaster safety net to the P-GW 400.
- the P-CSCF forwards to the P-GW 400 including an indication that Signaling arrived from the MCPTT application server has priority.
- the P-CSCF 700 may request the PCRF 600 to give high priority to data from the IP address of the MCPTT Application Server 800.
- the PCRF 600 may reflect this and inform the P-GW 400 to the PCC Rule to reflect the high priority for the data arriving from the IP of the MCPTT Application Server 800 or update the policy.
- the P-GW 400 may transmit a downlink data notification including an indicator for the disaster safety net to the MME 300.
- the P-GW 400 which has learned that signaling having a high priority has arrived through the above procedure, transmits a downlink notification message to the MME 300 for paging to the terminal 100.
- the P-GW 400 may add an identifier to the downlink notification message indicating that the downlink notification is for MCPTT, MCPTT Emergency, or detailed MCPTT service.
- the identifier is included in the downlink notification message by adding the identifier for the MCPTT service or MCPTT emergency or MCPTT detailed service to the indication flag of the downlink notification message, or corresponding to the emergency or the MCPTT service in the ARP setting value of the downlink notification message.
- a corresponding value may be set, MCPTT information may be set in Paging and Service Information of Downlink Notification message, MCPTT Emergency information may be set, or detailed MCPTT service information may be set.
- the MME 300 may determine the type of downlink data.
- the MME 300 may determine that the data type transmitted to the downlink is for MCPTT, MCPTT Emergency or detailed MCPTT service.
- the MME 300 may transmit a paging signal including an indicator for the disaster safety net to the eNB 200. Specifically, the MME 300 sends a paging message to the eNB 200, which includes an indication that this paging should be processed with high priority for MCPTT or MCPTT Emergency or for detailed MCPTT service. . To this end, the MME 300 may set the paging priority of the paging message according to the MCPTT service, the MCPTT Emergency or the detailed MCPTT service.
- the eNB 200 may determine that the paging should be processed first, and may process it before other paging requests.
- step S325 the eNB 200 may transmit a paging signal to the MCPTT terminal 100.
- step S330 the eNB 200 may reset the RRC connection with the MCPTT terminal 100.
- step S335 the eNB 200 may transmit an initial terminal message to the MME 300.
- the MCPTT terminal 100 receives the paging and responds to the eNB 200, and the eNB 200 receiving the response of the MCPTT terminal 100 transmits an Initial UE message to the MME 300 to the MCPTT terminal. Request for (100) to establish a bearer connection.
- the MME 300 may receive an Initial UE message, and may determine that the terminal 100 receiving the paging having the priority requests the bearer connection.
- the MME 300 may determine the bearer context for the disaster safety net service. For example, the MME 300 determines the context of a bearer to be allocated to the MCPTT terminal 100, and sets a QoS value according to an MCPTT service or an MCPTT Emergency or a detailed MCPTT service.
- step S345 the MCP 300 that the MCPTT terminal 100 determines which MCPTT service to use and authenticates may be provided to the terminal 100 to negotiate with the HSS 500 to use the specific MCPTT service. Information can be obtained.
- the QoS information may include a QCI value for identifying a QoS priority and an ARP value for indicating whether a resource can be preempted first.
- the MME 300 stores the obtained information as an internal setting value or stores the information in MME Emergency Configuration Data and proceeds with the rest of the process.
- the procedure between the MME 300 and the HSS 500 may be omitted, and in this case, the QoS value is determined according to an internal setting value stored in the MME 300.
- the internal setting value stored in the MME 300 may be a value stored in the MME Emergency Configuration Data.
- the MME 300 determines which QoS to provide for the bearer to be allocated to the MCPTT terminal 100, and then modifies the context of the default bearer of the terminal 100 which has sent the request to have a QoS value suitable for the MCPTT service. . For example, if the MME 300 determines that the MCPTT emergency service should be provided to the MCPTT terminal 100 that has sent the Extended Service Request, the MME 300 changes the existing default bearer context to a corresponding QCI or ARP value. Alternatively, as in another embodiment of the present invention, the secondary default bearer context stored for MCPTT is activated.
- the MME 300 may transmit an initial context setup request to the eNB 200. Specifically, the MME 300 sends an Initial Context Setup Request to the eNB 200 and requests to establish a bearer connection with the terminal 100 according to the set Bearer Context.
- the eNB 200 may reset the RRC connection with the terminal 100. Specifically, the eNB 200 receiving the Initial Context Setup Request from the MME 300 prepares for generating a bearer according to Bearer Context, that is, QoS information contained in the Initial Context Setup Request, and sends an RRC Connection Reconfiguration to the MCPTT terminal 100 to the terminal. Establish a bearer connection between the 100 and the eNB 200. (Step S360)
- step S365 the eNB 200 has completed the establishment of the bearer connection with the terminal 100 sends an initial context setup response (Initial Context Setup Response) to the MME 300 in response to the Initial Context Setup Request to the MME to any Bearer ID. Informs that the bearer with the QoS set by the user is configured.
- an initial context setup response (Initial Context Setup Response) to the MME 300 in response to the Initial Context Setup Request to the MME to any Bearer ID. Informs that the bearer with the QoS set by the user is configured.
- step S370 after receiving the Initial Context Setup Response, the MME 300 makes a S-GW / Modify Bearer Request for a connection between the eNB 200 and the S-GW / P-GW 400.
- the bearer connection is established between the eNB 200 and the S-GW / P-GW 400 as a result.
- Step S375 From the terminal 100 to the eNB 200, the bearer connection established up to the S-GW / P-GW 400 is a connection having the QoS value set by the MME 300 according to the MCPTT Type in the above procedure, and may handle data transmission at a higher priority than other bearers. Can be.
- the P-GW 40 is completed Bearer connection establishment can modify the IP-CAN session with the PCRF 600.
- the P-GW 400 may transmit a newly established bearer and terminal information to a policy and charging rule function (PCRF) 600 to update the PCC rule and utilize it for charging or providing a service.
- PCRF policy and charging rule function
- the S-GW / P-GW 400 may transmit a bearer modification response to the MME 300.
- the MCPTT terminal 100 may use the MCPTT service with a high priority in response to a request from the MCPTT service.
- Figure 4 is, according to an embodiment of the present invention, when the information for forming a bearer for using the disaster safety net by the PGW receiving the information on the disaster safety net is determined, the MME for using the disaster safety net It is a sequence diagram which shows a method of forming a bearer.
- the P-GW 400 receives MCPTT signaling from the P-CSCF 700 is the same as the embodiment according to FIG. 3.
- step S400 data on MCPTT service usage from the MCPTT service is transferred from the MCPTT application server 800 to the P-CSCF 700.
- the P-CSCF 700 may determine whether signaling arriving from the MCPTT Application Server 800 should be processed with priority. Overall priority can be given to MCPTT services, or high priority can be given to MCPTT Emergency services, or detailed MCPTT services such as Emergency Call, Imminent Peril Call, Ambient Listening, Private Call, Emergency Alert, etc. Services can be classified and given priority.
- the P-CSCF 700 may transmit a signal including an indicator for the disaster safety net to the P-GW 400.
- the P-GW 400 may transmit a paging signal to the MME 300.
- the MME 300 may transmit a paging signal to the eNB 200.
- the eNB 200 may transmit a paging signal to the terminal 100.
- the eNB 200 may form an RRC connection with the MCPTT terminal 100.
- the eNB 200 may transmit an initial UE message to the MME 300.
- the P-GW 400 may determine the QoS for the disaster safety net service.
- QoS is merely an example, and the P-GW 400 may determine a bearer context to form a bearer for disaster safety net service.
- the P-GW 400 that receives the high priority signaling from the P-CSCF 700 sends a paging message to the MME 300 and then establishes a bearer connection with a priority suitable for the high priority.
- the P-GW 400 that receives the high priority signaling from the P-CSCF 700 sends a paging message to the MME 300 and then establishes a bearer connection with a priority suitable for the high priority.
- the P-GW 400 that determines the QoS may transmit a bearer update request including the QoS determined to the MME 300 via the S-GW.
- the P-GW 400 transmits an Update Bearer Request to the MME 300, and sets and transmits a QoS value having a high priority determined in the procedure in this message.
- the MME 300 may determine a bearer context for the disaster safety net service. For example, upon receiving the message, the MME 300 determines a bearer context to be allocated to the MCPTT terminal 100 based on the information contained in the bearer update request message.
- step S450 the MME 300 that the MCPTT terminal 100 determines which MCPTT service to use and authenticates is provided to the terminal 100 to negotiate with the HSS 500 to use a specific MCPTT service.
- QoS information that can be obtained can be obtained.
- the QoS information may include a QCI value for identifying a QoS priority and an ARP value for indicating whether a resource can be preempted first.
- the MME 300 stores the obtained information as an internal setting value or stores the information in MME Emergency Configuration Data and proceeds with the rest of the process.
- the procedure between the MME 300 and the HSS 500 may be omitted, and in this case, the QoS value is determined according to an internal setting value stored in the MME 300.
- the internal setting value stored in the MME 300 may be a value stored in the MME Emergency Configuration Data.
- the MME 300 determines which QoS to provide for the bearer to be allocated to the MCPTT terminal 100, and then modifies the context of the default bearer of the terminal 100 which has sent the request to have a QoS value suitable for the MCPTT service. . For example, if the MME 300 determines that the MCPTT emergency service should be provided to the MCPTT terminal 100 that has sent the Extended Service Request, the MME 300 changes the existing default bearer context to a corresponding QCI or ARP value. Alternatively, as in another embodiment of the present invention, the secondary default bearer context stored for MCPTT is activated.
- the MME 300 may transmit an initial context setup request to the eNB 200. Specifically, the MME 300 sends an Initial Context Setup Request to the eNB 200 and requests to establish a bearer connection with the terminal 100 according to the set Bearer Context.
- the eNB 200 may reset the RRC connection with the terminal 100. Specifically, the eNB 200 receiving the Initial Context Setup Request from the MME 300 prepares for generating a bearer according to Bearer Context, that is, QoS information contained in the Initial Context Setup Request, and sends an RRC Connection Reconfiguration to the MCPTT terminal 100 to the terminal. Establish a bearer connection between the 100 and the eNB 200. (Step S465)
- step S470 the eNB 200 that has completed the establishment of the bearer connection with the terminal 100 sends an initial context setup response to the MME 300 in response to the initial context setup request to the MME 300 with a bearer ID. Informs that the bearer with the QoS set by the user is configured.
- step S475 after receiving the Initial Context Setup Response, the MME 300 sends a S-GW / Modify Bearer Request to the eNB 200 and the S-GW / P-GW 400 for connection.
- the bearer connection is established between the eNB 200 and the S-GW / P-GW 400 as a result.
- Step S480 The terminal 100 to the eNB 200 are transmitted to the P-GW 400.
- the bearer connection established up to the S-GW / P-GW 400 is a connection having the QoS value set by the MME 300 according to the MCPTT Type in the above procedure, and may handle data transmission at a higher priority than other bearers. Can be.
- the bearer connection establishment completes the P-GW 40 may modify the IPF-CAN session with the PCRF 600.
- the P-GW 400 may transmit a newly established bearer and terminal information to a policy and charging rule function (PCRF) 600 to update the PCC rule and utilize it for charging or providing a service.
- PCRF policy and charging rule function
- the MCPTT terminal 100 may use the MCPTT service with a high priority in response to a request from the MCPTT service.
- the MME 300 may modify the existing context of the default bearer to establish a bearer connection having a high priority, in this case, may follow the first embodiment shown in Figure 1 of the present invention.
- the Bearer connection may be established by activating the previously stored Secondary Default Bearer Context, in which case, the second embodiment shown in FIG. 2 will be described.
- the MME 300 may perform establishment of dedicated bearer connection suitable for high priority. In this case, both the Default Bearer connection and the Dedicated Bearer connection are established, and the MCPTT terminal 100 uses the MCPTT service through the dedicated bearer. Alternatively, the MME 300 may establish a new bearer connection. In this case, all existing bearer contexts are deactivated and a new bearer according to the newly determined bearer context is created by the MME 300.
- FIG. 5 is a sequence diagram illustrating a method of forming a bearer for using the disaster safety net when the terminal intending to use the disaster safety net transmits an access request message according to an embodiment of the present invention.
- FIG. 5 illustrates a method for notifying that an MCPTT terminal can use MCPTT when attaching to an EPS network and a method for notifying the MME to use an MCPTT service through attachment, and a method and procedure for establishing a bearer connection accordingly The figure which shows.
- the MCPTT terminal 100 may receive an attach request message including at least one of information on the type of MCPTT and MCPTT capability.
- the MCPTT terminal 100 performs an attach procedure to access the EPS network.
- the MPCTT terminal 100 may notify the MME 300 that it is a terminal using MCPTT in the following method in the Attach Request message.
- the MCPTT terminal 100 may indicate that it is an MCPTT in the Type Field of the Attach Request message or may indicate that it is an MCPTT Emergency.
- the MCPTT terminal 100 may inform that it will access the MCPTT service by setting the MCPTT APN in the APN field of the Attach Request message.
- the MCPTT terminal 100 may set a value corresponding to MCPTT Capability in the UE network capability of the Attach Request, and may indicate that the MCPTT terminal is a Device Property.
- the MCPTT terminal 100 may inform that it is an MCPTT terminal by performing at least one or more of the above methods, and a bearer connection for MCPTT should be established as a result of attaching using a type of an access request and an APN field. May be indicated.
- the operation of setting UE network capability information or device property may indicate that the corresponding terminal 100 is a terminal capable of using MCPTT.
- step S505 the MCPTT terminal 100 transmits an RRC connection setup complete message to the eNB 200, and in step S510, the eNB 200 includes an initial terminal including an indicator for a disaster safety net. A message may be transmitted.
- the MME 300 receiving the attach request may configure a secondary bearer context for the MCPPT service in advance with respect to the corresponding terminal 100.
- the MCPTT terminal 100 transmits the Attach Request message configured as described above to the eNB 200 by including the RRC connection setup complete message during the RRC connection procedure. It may include an indication that the priority should be processed for the purpose.
- the eNB 200 that receives the RRC Connection Setup Complete message containing the Attach Request message together with the indication from the MCPTT terminal 100 may follow the indication of other terminals.
- the request of the terminal may be processed before the request.
- the eNB 200 includes an Attach Request message in an Initial UE message, and delivers to the MME an Indication that it should be processed at a high priority.
- the MME 300 may process the request before the request arrives from another eNB according to an indication that priority processing included in the message is required.
- step S515 the MME 300 may determine a bearer context for the disaster safety net service.
- the MME 300 that receives the Attach Request message contained in the Initial UE Message according to the value set when the MCPTT terminal 100 configures the Attach Request message, the context of the bearer required for the MCPTT terminal 100 Can be determined. For example, if the type of the Attach Request message is Emergency and the APN indicates the MCPTT APN, the MME 300 may determine that the UE requesting the Attach needs an Emergency Bearer for the MCPTT. Similarly, if the type of the Attach message indicates the MCPTT Emergency, it can determine the bearer context for the MCPTT Emergency to the terminal.
- the MCPTT in case of using the MCPTT service.
- Bearer context suitable for service priority can be determined and saved as Secondary Default Bearer Context.
- the MME 300 having determined the bearer context by the same process as described above may obtain and request QoS information from the HSS 500 in step S520, and the terminal 100 requesting the attachment has a high QoS. You can also perform an authentication procedure.
- the above process may be omitted, and if omitted, the stored value may be used by the MME Emergency Configuration data or another method in the MME 300.
- the MME 300 may transmit a session creation request including an indicator for the disaster safety net service to the S-GW / P-GW 400.
- the MME 300 transmits a Create Session Request to the S-GW / P-GW 400 to provide a bearer connection to the terminal 100 requesting the attachment, in which case the S-GW / P-GW
- an Indication Flag or Signaling Priority Indication of the Create Session Request message or a QoS value of the Bearer Context may be included and transmitted.
- the S-GW / P-GW 400 receiving the message may process the message more preferentially than a request from another terminal or MME by checking an Indication flag or Signaling Priority Indication, or a QoS value contained in Bearer information. If it has a high priority QCI or ARP value corresponding to Emergency, it may be determined that the request should be processed first.
- the P-GW 400 may establish an IP-CAN session with the PCRF 600.
- the P-GW 400 may transmit a session creation response including the second bearer information to the MME 300.
- the P-GW 400 may accept the Create Session Request and negotiate with the PCRF 600 to update the PCC rule. Thereafter, the P-GW 400 may respond to the Create Session Request with Create Session Response, and the Create Session Response message may be activated when the MCPTT terminal 100 wants to use the MCPTT service. Secondary Default Bearer (Secondary Default Bearer) information is included, or the current MCPTT terminal 100 including the Default Bearer information to be activated and transmits.
- Secondary Default Bearer Secondary Default Bearer
- the MME 300 may transmit an access permission message to the MCPTT terminal 100.
- the MME 300 may transmit an initial context setup request to the eNB 200.
- the MME may transmit an initial context setup request including an attach accept message and bearer context information.
- the eNB 200 transmits an access allowance with an RRC connection reconfiguration message, and the UE as a bearer context in an initial context setup request. Bearer connection is established between the 100 and the eNB 200.
- step S560 the eNB 200 may transmit an initial context setup response to the MME 300 to inform the bearer setup.
- the eNB 200 may notify the MME 300 that the Bearer is set by sending an Initial context Setup response.
- the terminal 100 may transmit an attach complete message to the MME 300.
- the MME 300 may transmit a bearer modification request to the S-GW / P-GW 400. If a bearer modification response is sent from the S-GW / P-GW 400 in step S575, in step S580 a bearer is formed between the eNB 200 and the S-GW / P-GW 400.
- the MME 300 sends a Modify Bearer Request to the S-GW / P-GW 400 to establish a bearer connection between the eNB 200 and the S-GW / P-GW and the terminal 100. Terminates the Attach procedure by sending an Attach Accept message to the MME 300.
- the MME 6000 may include a transceiver 6100 and a controller 6200.
- the transceiver 6100 may transmit and receive a signal.
- the MME 6000 may transmit / receive a signal to a base station or a P-GW through a transceiver 6100.
- the controller 6200 may overall control the MME 6000. As described above, the controller 6200 may control the transceiver 6100 to receive a first message including information on public safety. The controller 6200 may control to form a bearer having a higher priority than the preset bearer based on the received message.
- the service for the disaster safety net may include a mission critical push to talk over LTE (MCPTT).
- MCPTT mission critical push to talk over LTE
- the information on the disaster safety net may include at least one of information on the type of MCPTT and the MCPTT capability from the terminal.
- the first message may be a service request message.
- the controller 6200 determines the type of the MCPTT service to be used by the terminal based on the information included in the service request message, and based on the determined type of the MCPTT service, the home subscriber server (home)
- a subscriber server (HSS) may request QoS information for using the MCPTT service.
- the control unit When the QoS information is received from the HSS through the transceiver 6100, the control unit changes the context of a first default bearer for the terminal based on the received QoS information. Can be.
- the controller 6200 may store a second default bearer context for the MCPTT service before receiving the service request message from the terminal.
- the controller 6200 may determine the type of the MCPTT service based on the information included in the service request message.
- the controller 6200 may determine a bearer context based on the determined type of the MCPTT service in the stored second default bearer context, and activate the second default bearer based on the determined bearer context.
- the first message may be an attach request message including at least one of information on a type of MCPTT and MCPTT capability from a terminal.
- the controller 6200 may determine a bearer context based on the information included in the access request message, and form the bearer according to the determined bearer context.
- the controller 6200 may receive a second message including information on the disaster safety net from a packet data network gateway (PGW).
- PGW packet data network gateway
- the second message may be a downlink data notification (DDN) message.
- DDN downlink data notification
- the controller 6200 transmits a paging signal including a identifier for the disaster safety net to a base station, and the terminal receiving the paging signal is connected to the paging signal.
- a message including the bearer establishment request may be received from the base station.
- the controller 6200 may form a bearer by determining a bearer context according to the received request.
- the second message includes an update bearer request message including a quality of service (QoS) value for forming a bearer for the disaster safety net determined in the PGW by signaling transmitted from an application server.
- QoS quality of service
- the controller 6200 may form the bearer based on the QoS value included in the bearer request message.
- the controller 6200 may further include components such as the determination unit 6210 and the forming unit 6220.
- the determination unit 6210 may determine whether the message has been received from the disaster safety net terminal or the need to form a disaster safety net bearer through the information included in the received message.
- the determination unit 6210 may determine a bearer context in order to form a bearer for a disaster safety net.
- the forming unit 6220 may form a bearer according to the determination result of the determination unit 6210.
- the forming unit 6220 may form a bearer by modifying a default bearer context based on the determination result.
- components of the controller 6200 may be implemented in software.
- the controller 6200 may further include a flash memory or other nonvolatile memory.
- the nonvolatile memory may store a program for performing the roles of each of the determination unit 6210 and the formation unit 6220.
- controller 6200 may be implemented in a form including a CPU and a random access memory (RAM). After copying the programs stored in the nonvolatile memory to RAM, the copied programs can be executed to perform the scheduling as described above.
- RAM random access memory
- the controller 6200 may be used interchangeably with the same meaning as a central processing unit, a microprocessor, a controller, a processor, an operating system, and the like.
- the control unit 6200 of the MME 6000 is implemented as a single chip system (System-on-a-chip or System on chip, SOC, SoC) together with other functional units such as a transceiver unit included in the MME 6000. Can be.
- a bearer having a higher priority than a preset bearer is formed, so that the terminal can easily use the disaster safety net service.
- the bearer formation method of the MME may be coded in software and stored in a non-transitory readable medium.
- Such non-transitory readable media can be mounted and used in a variety of devices.
- the non-transitory readable medium refers to a medium that stores data semi-permanently and is readable by a device, not a medium storing data for a short time such as a register, a cache, a memory, and the like. Specifically, it may be a CD, a DVD, a hard disk, a Blu-ray disk, a USB, a memory card, a ROM, or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (15)
- 이동성 관리 엔티티(mobility management entity: MME)의 베어러 형성 방법에 있어서,재난 안전망(public safety)에 대한 정보를 포함하는 제1 메시지를 수신하는 단계; 및수신된 메시지에 기반하여, 기설정된 베어러보다 높은 우선순위를 가지는 베어러를 형성하는 단계; 를 포함하는 방법.
- 제1항에 있어서,상기 재난 안전망에 대한 서비스는,MCPTT(mission critical push to talk over LTE)를 포함하고,상기 재난 안전망에 대한 정보는,단말로부터 MCPTT의 타입 및 MCPTT 능력에 대한 정보 중 적어도 하나를 포함하는 것을 특징으로 하는 방법.
- 제3항에 있어서,상기 형성하는 단계는,상기 서비스 요청 메시지에 포함된 정보에 기반하여, 상기 단말이 이용할 상기 MCPTT 서비스에 대한 종류를 판단하는 단계;상기 판단된 MCPTT 서비스에 대한 종류에 기반하여, 홈 가입자 서버(home subscriber server: HSS)에 상기 MCPTT 서비스를 이용하기 위한 QoS 정보를 요청하는 단계; 및상기 HSS로부터 상기 QoS 정보가 수신되면, 상기 수신된 QoS 정보에 기반하여, 상기 단말에 대한 제1 디폴트 베어러(default bearer)에 대한 컨텍스트 (context)를 변경하는 단계; 를 더 포함하는 것을 특징으로 하는 방법.
- 제3항에 있어서,상기 형성하는 단계는,상기 단말로부터 상기 서비스 요청 메시지를 수신하기 전에, 상기 MCPTT 서비스를 위한 제2 디폴트 베어러 컨텍스트를 저장하는 단계;상기 서비스 요청 메시지가 수신된 경우, 상기 서비스 요청 메시지에 포함된 정보에 기반하여 상기 MCPTT 서비스에 대한 종류를 판단하는 단계;상기 저장된 제2 디폴트 베어러 컨텍스트에서, 상기 판단된 MCPTT 서비스에 대한 종류에 기반한 베어러 컨텍스트를 결정하는 단계; 및상기 결정된 베어러 컨텍스트에 기반하여 상기 제2 디폴트 베어러를 활성화는 단계; 를 더 포함하는 것을 특징으로 하는 방법.
- 제1항에 있어서,상기 수신하는 단계는,상기 재난 안전망에 대한 정보를 포함하는 제2 메시지를 패킷 데이터 네트워크 게이트웨이(packet data network gateway: PGW)로부터 수신하는 단계인 것을 특징으로 하는 방법.
- 제5에 있어서,상기 제2 메시지는,다운링크 데이터 통지(downlink data notification, DDN) 메시지이고,상기 형성하는 단계는,상기 재난 안전망에 대한 식별자를 포함하는 페이징 신호(paging signal)을 기지국으로 전송하는 단계;상기 페이징 신호를 수신한 단말이 상기 페이징 신호에 따른 응답을 상기 기지국으로 전송하면, 상기 기지국으로부터 상기 베어러 형성 요청을 포함하는 메시지를 수신하는 단계; 및상기 수신된 요청에 따라, 베어러 컨텍스트를 결정하여 상기 베어러를 형성하는 단계; 를 더 포함하고,상기 제2 메시지는,어플리케이션 서버로부터 전송된 시그널링에 의해, 상기 PGW에서 결정된 상기 재난 안전망에 대한 베어러를 형성하기 위한 QoS(quality of service) 값을 포함하는 업데이트 베어러 요청(update bearer request) 메시지이고,상기 형성하는 단계는,상기 베어러 요청 메시지에 포함된 상기 QoS 값에 기반하여, 상기 베어러를 형성하는 단계인 것을 특징으로 하는 방법.
- 1항에 있어서,상기 제1 메시지는,단말로부터 상기 MCPTT의 타입 및 MCPTT 능력에 대한 정보 중 적어도 하나를 포함하는 접속 요청(attach request) 메시지이고,상기 형성하는 단계는,상기 접속 요청 메시지에 포함된 정보에 기반하여, 베어러 컨텍스트를 결정하는 단계; 및상기 결정된 베어러 컨텍스트에 따라, 상기 베어러를 형성하는 단계; 를 더 포함하는 것을 특징으로 하는 방법.
- 이동성 관리 엔티티(mobility management entity: MME) 에 있어서,신호를 송수신하는 송수신부; 및재난 안전망(public safety)에 대한 정보를 포함하는 제1 메시지를 상기 송수신부를 통해 수신하도록 제어하고, 수신된 메시지에 기반하여, 기설정된 베어러보다 높은 우선순위를 가지는 베어러를 형성하는 제어부; 를 포함하는 MME.
- 제8에 있어서,상기 재난 안전망에 대한 서비스는,MCPTT(mission critical push to talk over LTE)를 포함하는 것을 특징으로 하고, 또는,상기 재난 안전망에 대한 정보는,단말로부터 MCPTT의 타입 및 MCPTT 능력에 대한 정보 중 적어도 하나를 포함하는 것을 특징으로 하는 MME.
- 제9항에 있어서,상기 제어부는,상기 서비스 요청 메시지에 포함된 정보에 기반하여, 상기 단말이 이용할 상기 MCPTT 서비스에 대한 종류를 판단하고, 상기 판단된 MCPTT 서비스에 대한 종류에 기반하여, 홈 가입자 서버(home subscriber server: HSS)에 상기 MCPTT 서비스를 이용하기 위한 QoS 정보를 요청하며, 상기 HSS로부터 상기 QoS 정보가 수신되면, 상기 수신된 QoS 정보에 기반하여, 상기 단말에 대한 제1 디폴트 베어러(default bearer)에 대한 컨텍스트 (context)를 변경하는 것을 특징으로 하는 MME.
- 제9에 있어서,상기 제어부는,상기 단말로부터 상기 서비스 요청 메시지를 수신하기 전에, 상기 MCPTT 서비스를 위한 제2 디폴트 베어러 컨텍스트를 저장하고, 상기 서비스 요청 메시지가 수신된 경우, 상기 서비스 요청 메시지에 포함된 정보에 기반하여 상기 MCPTT 서비스에 대한 종류를 판단하며, 상기 저장된 제2 디폴트 베어러 컨텍스트에서, 상기 판단된 MCPTT 서비스에 대한 종류에 기반한 베어러 컨텍스트를 결정하고, 상기 결정된 베어러 컨텍스트에 기반하여 상기 제2 디폴트 베어러를 활성화는 것을 특징으로 하는 MME.
- 제8에 있어서,상기 제어부는,상기 재난 안전망에 대한 정보를 포함하는 제2 메시지를 패킷 데이터 네트워크 게이트웨이(packet data network gateway: PGW)로부터 수신하는 것을 특징으로 하는 MME.
- 제12항에 있어서,상기 제2 메시지는,다운링크 데이터 통지(downlink data notification, DDN) 메시지이고,상기 제어부는,상기 재난 안전망에 대한 식별자를 포함하는 페이징 신호(paging signal)을 기지국으로 전송하고, 상기 페이징 신호를 수신한 단말이 상기 페이징 신호에 따른 응답을 상기 기지국으로 전송하면, 상기 기지국으로부터 상기 베어러 형성 요청을 포함하는 메시지를 수신 하도록 상기 송수신부를 제어하고, 상기 수신된 요청에 따라, 베어러 컨텍스트를 결정하여 상기 베어러를 형성하는 것을 특징으로 하는 MME.
- 제12항에 있어서,상기 제2 메시지는,어플리케이션 서버로부터 전송된 시그널링에 의해, 상기 PGW에서 결정된 상기 재난 안전망에 대한 베어러를 형성하기 위한 QoS(quality of service) 값을 포함하는 업데이트 베어러 요청(update bearer request) 메시지이고,상기 제어부는,상기 베어러 요청 메시지에 포함된 상기 QoS 값에 기반하여, 상기 베어러를 형성하는 것을 특징으로 하는 MME.
- 제8항에 있어서,상기 제1 메시지는,단말로부터 상기 MCPTT의 타입 및 MCPTT 능력에 대한 정보 중 적어도 하나를 포함하는 접속 요청(attach request) 메시지이고,상기 제어부는,상기 접속 요청 메시지에 포함된 정보에 기반하여, 베어러 컨텍스트를 결정하고, 상기 결정된 베어러 컨텍스트에 따라, 상기 베어러를 형성하는 것을 특징으로 하는 MME.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020177032113A KR20170140256A (ko) | 2015-04-30 | 2016-05-02 | 무선 통신 시스템에서 재난 안전망 용 베어러를 형성하는 방법 및 장치 |
CN201680024939.9A CN108541398B (zh) | 2015-04-30 | 2016-05-02 | 用于在无线通信系统中形成用于公共安全的承载的方法及其设备 |
US15/567,364 US10368263B2 (en) | 2015-04-30 | 2016-05-02 | Method for forming bearer for public safety in wireless communication system and device therefor |
EP16786820.7A EP3291625B1 (en) | 2015-04-30 | 2016-05-02 | Method for forming bearer for public safety in wireless communication system and device therefor |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562155169P | 2015-04-30 | 2015-04-30 | |
US62/155,169 | 2015-04-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016175634A1 true WO2016175634A1 (ko) | 2016-11-03 |
Family
ID=57198609
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/004606 WO2016175634A1 (ko) | 2015-04-30 | 2016-05-02 | 무선 통신 시스템에서 재난 안전망 용 베어러를 형성하는 방법 및 장치 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10368263B2 (ko) |
EP (1) | EP3291625B1 (ko) |
KR (1) | KR20170140256A (ko) |
CN (1) | CN108541398B (ko) |
WO (1) | WO2016175634A1 (ko) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018517361A (ja) * | 2015-05-29 | 2018-06-28 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ベアラセットアップ方法および装置 |
TWI715823B (zh) * | 2018-02-07 | 2021-01-11 | 淡江大學 | 災難緊急救助系統及其控制方法 |
US10701539B2 (en) | 2018-07-02 | 2020-06-30 | Qualcomm Incorporated | Enhanced public warning system |
WO2020022840A1 (en) * | 2018-07-26 | 2020-01-30 | Samsung Electronics Co., Ltd. | Method and apparatus for prioritizing mission critical push to talk traffic during an emergency |
US11483886B2 (en) * | 2018-12-21 | 2022-10-25 | T-Mobile Usa, Inc. | Staggered IMS bearer activation and radio bearer activation in 5G non-standalone networks |
EP4106368A4 (en) * | 2020-02-10 | 2024-06-05 | Mitsubishi Electric Corporation | COMMUNICATION SYSTEM, COMMUNICATION TERMINAL AND NETWORK |
KR102434818B1 (ko) * | 2020-11-06 | 2022-08-22 | 주식회사 케이티 | 재난 현장을 커버하는 재난안전통신망 기지국, 통신 방법 및 컴퓨터 프로그램 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013116476A2 (en) * | 2012-02-02 | 2013-08-08 | Motorola Solutions, Inc. | Method and apparatus for admitting a request for allocation of wireless connection resources in a communication system |
US20130287012A1 (en) * | 2012-04-27 | 2013-10-31 | Interdigital Patent Holdings, Inc. | Method and apparatus for optimizing proximity data path setup |
US20130329559A1 (en) * | 2012-06-08 | 2013-12-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Communication network congestion control using allocation and retention priority |
US20140101303A1 (en) * | 2012-10-08 | 2014-04-10 | Cisco Technology, Inc. | System and method for throttling downlink data notifications in a network environment |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101009698A (zh) * | 2006-01-26 | 2007-08-01 | 华为技术有限公司 | Ims网络中保障会话发起质量的方法及网络单元和系统 |
CN101500213B (zh) * | 2008-02-03 | 2011-04-20 | 华为技术有限公司 | 一种用户设备紧急接入的方法、设备和系统 |
CN101540979B (zh) * | 2008-03-20 | 2011-07-27 | 大唐移动通信设备有限公司 | 用于紧急呼叫业务的紧急承载建立方法与通信系统 |
WO2010120689A2 (en) | 2009-04-14 | 2010-10-21 | Interdigital Patent Holdings, Inc. | Method and apparatus for processing emergency calls |
KR101528496B1 (ko) | 2009-04-17 | 2015-06-15 | 삼성전자주식회사 | 이동 통신 시스템에서 비계층 프로토콜을 이용하여 응급 콜 서비스를 지원하는 방법 및 시스템 |
US8655305B2 (en) | 2011-03-21 | 2014-02-18 | Htc Corporation | Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same |
JP5912926B2 (ja) * | 2012-06-29 | 2016-04-27 | 株式会社Nttドコモ | 移動通信システム、サービングゲートウェイ装置及び移動通信方法 |
WO2016039579A1 (ko) * | 2014-09-11 | 2016-03-17 | 엘지전자 주식회사 | 무선 통신 시스템에서 mcptt 그룹 콜 설정 방법 및 이를 위한 장치 |
CN112118217B9 (zh) | 2015-01-16 | 2023-05-09 | 三星电子株式会社 | 无线通信系统中的控制信息传输方法和装置 |
US9955321B2 (en) * | 2015-04-08 | 2018-04-24 | Blackberry Limited | Regrouping push-to-talk groups |
-
2016
- 2016-05-02 WO PCT/KR2016/004606 patent/WO2016175634A1/ko active Application Filing
- 2016-05-02 EP EP16786820.7A patent/EP3291625B1/en active Active
- 2016-05-02 KR KR1020177032113A patent/KR20170140256A/ko not_active Application Discontinuation
- 2016-05-02 US US15/567,364 patent/US10368263B2/en active Active
- 2016-05-02 CN CN201680024939.9A patent/CN108541398B/zh active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013116476A2 (en) * | 2012-02-02 | 2013-08-08 | Motorola Solutions, Inc. | Method and apparatus for admitting a request for allocation of wireless connection resources in a communication system |
US20130287012A1 (en) * | 2012-04-27 | 2013-10-31 | Interdigital Patent Holdings, Inc. | Method and apparatus for optimizing proximity data path setup |
US20130329559A1 (en) * | 2012-06-08 | 2013-12-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Communication network congestion control using allocation and retention priority |
US20140101303A1 (en) * | 2012-10-08 | 2014-04-10 | Cisco Technology, Inc. | System and method for throttling downlink data notifications in a network environment |
Non-Patent Citations (2)
Title |
---|
HALLAHAN, RYAN ET AL.: "Policies for Public Safety Use of Commercial Wireless Networks", 38TH TELECOMMUNICATIONS POLICY RESEARCH CONFERENCE, 23 January 2012 (2012-01-23), XP055326962, Retrieved from the Internet <URL:http://papers.ssm.com/sol3/papers.cfm?abstract_id=1989600> * |
See also references of EP3291625A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN108541398A (zh) | 2018-09-14 |
EP3291625A1 (en) | 2018-03-07 |
US20180109972A1 (en) | 2018-04-19 |
US10368263B2 (en) | 2019-07-30 |
EP3291625A4 (en) | 2018-04-25 |
CN108541398B (zh) | 2022-02-01 |
KR20170140256A (ko) | 2017-12-20 |
EP3291625B1 (en) | 2021-09-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016175634A1 (ko) | 무선 통신 시스템에서 재난 안전망 용 베어러를 형성하는 방법 및 장치 | |
WO2020209641A1 (en) | Method and system of ue for switching between plurality of sim networks | |
WO2021029649A1 (en) | Method and apparatus for handling conditional handover (cho) in a wireless communication network | |
US10455489B2 (en) | Method for supporting PDN GW selection | |
US9554406B2 (en) | Method for device to device communication and control node using the same | |
US9450667B2 (en) | Method for device to device communication and base station and user equipment using the same | |
JP5132815B2 (ja) | アイドルモードにおけるシグナリング節約機能の活性化判断方法及びシステム | |
WO2016133344A1 (en) | Method for triggering transmission of user equipment (ue)-to-network relay indication | |
WO2017086720A1 (ko) | 무선 통신 시스템에서 단말의 v2x 신호의 전송 방법 및 상기 방법을 이용하는 단말 | |
CN113475109A (zh) | 随着rrc恢复完成之类的消息的早期测量报告 | |
KR102484223B1 (ko) | Pdu 세션 활성화 방법, 페이징 방법 및 그의 장치 | |
WO2017034324A1 (ko) | 무선 통신 시스템에서 단말의 v2x 신호의 송수신 방법 및 상기 방법을 이용하는 단말 | |
KR20090033088A (ko) | 에이치 앤 비 억세스 시스템을 통한 직접 통신을 수행하는 사용자 기기를 위한 방법 | |
WO2018027995A1 (zh) | 一种寻呼方法和寻呼设备 | |
WO2017074100A1 (ko) | 이동 통신 시스템에서 페이징 메시지를 송수신하는 방법 및 장치 | |
WO2013048100A1 (en) | Method for processing data associated with location area update in a wireless communication system | |
WO2021047454A1 (zh) | 位置信息获取、位置服务配置方法和通信设备 | |
WO2015182991A1 (en) | Method and apparatus for transmitting and receiving voice call in communication system | |
AU2020384842A1 (en) | Method and apparatus for improving network slice control accuracy in wireless communication system | |
WO2022067575A1 (zh) | 测量报告上报方法及装置 | |
WO2014106396A1 (zh) | 集群登记的方法及装置 | |
WO2012171394A1 (zh) | 一种基于x2接口的csg小区切换方法及其装置 | |
WO2010015170A1 (zh) | 移动性管理处理方法、系统和设备 | |
WO2015105397A1 (en) | Apparatus and method for paging in wireless communication system | |
JP7367186B2 (ja) | ページング方法と機器 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16786820 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2016786820 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15567364 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20177032113 Country of ref document: KR Kind code of ref document: A |