Method and apparatus for prioritizing mission critical push to talk traffic during an emergency
地域：
Gyeonggi-do
摘要
Provided are methods and apparatuses for prioritizing Mission Critical Push to Talk Traffic during an emergency, related to wireless communication networks, and more particularly to mission critical services in Long Term Evolution (LTE) communication networks. A channel sensitive MCPTT prioritization scheduling method and system are provided to increase the download/upload. speeds for MCPTT users during the emergency situations. Also provided are methods and systems for prioritizing traffic for connected User Equipments (UEs) over idle UEs.
說明書
This application is a Continuation of U.S. patent application Ser. No. 17/044,699, filed with the U.S. Patent and Trademark Office on Oct. 1, 2020, which is a National Phase Entry of PCT International Application No. PCT/KR2019/009343, which was filed on Jul. 26, 2019, and claims priority to Indian Patent Application No. 201841028218 (PS), which was filed on Jul. 26, 2018, and Indian Patent Application No. 201841028218 (CS), which was filed on Jul. 22, 2019, the entire content of each of which is incorporated herein by reference.
The present disclosure relates to wireless communication networks, and more particularly to mission critical services in Long Term Evolution (LTE) communication networks.
In the event of a natural disaster, or a man-made disaster, mission critical services are to be provided with highest priority for those who are affected. For example, a civilian with a User Equipment (UE), such as a cell phone, stuck in an earthquake may require emergency assistance. In such situations, the service priority has to be updated in real time so as to allocate more radio resources to mission critical services.
權(quán)利要求
What is claimed:1. A method for access prioritization by a device in a mission critical push to talk (MCPTT) network, comprising:detecting an occurrence of an emergency in a location of a mission critical service (MCX) group; identifying a distance of each of one or more devices from the location of the detected emergency; and prioritizing in the location of the detected emergency, an access to the MCPTT network for at least one first device among the one or more devices based on the identified distance, wherein the at least one first device includes at least one user equipment (UE). 2. The method of claim 1 , wherein identifying the distance of each of the one or more devices from the location of the detected emergency comprises:detecting presence of at least one second device among the one or more devices in a close proximity from the location of the detected emergency; and calculating a distance of the at least one second device from the location of the detected emergency and time required for the at least one second device to reach the location of the detected emergency. 3. The method of claim 2 , wherein prioritizing in the location of the detected emergency, the access to the MCPTT network for the at least one first device among the one or more devices based on the identified distance comprises:prioritizing in the location of the detected emergency, the access to the MCPTT network for the at least one first device, if the at least one second device is at a distance more than a pre-determined distance from the location of the detected emergency. 4. The method of claim 1 , wherein the method further comprises prioritizing the at least one first device based on one or more of a channel quality detector (CQI) value, a packet delay budget, a quality of service class identifier (QCJ) value, a buffer occupancy, and a token priority, if the at least one LE is in a connected mode. 5. The method of claim 1 , wherein the method further comprises, on detecting the emergency, sending a request to change a MCPTT user priority to a mobility management entity (MME), if the at least one first device is in an idle mode. 6. The method of claim 1 , wherein the method further comprises receiving, from the at least one second device, a radio resource control (RRC) connection request message with a logical channel ID (LCID) value and an establishment cause value. 7. A device for access prioritization in a mission critical push to talk (MCPTT) network, comprising:at least one processor configured to:detect an occurrence of an emergency in a location of a mission critical service (MCX) group; identify a distance of each of one or more devices from the location of the detected emergency; and prioritize in the location of the detected emergency, an access to the MCPTT network for at least one first device among the one or more devices based on the identified distance, wherein the at least one first device includes at least one user equipment (UE). 8. The device of claim 7 , wherein the at least one processor is configured to:detect presence of at least one second device among the one or more devices in a close proximity from the location of the detected emergency; and calculate a distance of the at least one second device from the location of the detected emergency and time required for the at least one second device to reach the location of the detected emergency. 9. The device of claim 8 , wherein the at least one processor is further configured to prioritize in the location of the detected emergency, the access to the MCPTT network for the at least one first device, if the at least one second device is at a distance more than a pre-determined distance from the location of the detected emergency. 10. The device of claim 7 , wherein the at least one processor is further configured to prioritize the at least one first device based on one or more of a channel quality detector (COI) value, a packet delay budget, a quality of service class identifier (QCI) value, a buffer occupancy, and a token priority, if the at least one UE is in a connected mode. 11. The device of claim 7 , wherein the at least one processor is further configured to, on detecting the emergency, send a request to change a MCPTT user priority to a mobility management entity (MME), if the at least one first device is in an idle mode. 12. The device of claim 11 , wherein the at least one processor is further configured to receive, from the at least one second device, a radio resource control (RRC) connection request message with a logical channel ID (LCID) value and an establishment cause value.
意見反饋
使用該功能遇到問題