Radio resource allocation for emergency vehicular communications
In one embodiment, a method is performed. A device may receive a registration request from a user equipment (UE) device associated with a category. The device may receive a registration response from an access and mobility function (AMF). The registration response may comprise a group identifier associated with the category. The device may select resources from a resource pool based on the group identifier. The resource pool may be dedicated for use for emergency communications. The device may allocate the selected resources to the UE device.
1. A method comprising:
receiving, from a user equipment (UE) device, a registration request that indicates a category, wherein the category comprises at least one of an emergency vehicle category or a roadside unit (RSU) category;
receiving a registration response from an access and mobility function (AMF), the registration response comprising a group identifier that indicates the category, wherein the group identifier is based on a subscription profile from a unified data management (UDM) module;
selecting resources from a resource pool based on the group identifier, the resource pool dedicated for use for emergency communications; and
allocating the selected resources to the UE device.
2. The method of claim 1 , wherein the registration request indicates whether the UE device supports a PC5 interface.
3. The method of claim 1 , wherein the selected resources comprise a plurality of resource blocks (Rbs).
4. The method of claim 1 , wherein the UE device is associated with an identifier that is unique to the UE device.
5. The method of claim 2 , wherein the selected resources are allocated for vehicle to everything (V2X) communication using the PC5 interface.
6. The method of claim 4 , wherein the identifier comprises an international mobile subscriber identity (IMSI).
7. A system comprising:
a network interface in communication with a network;
a processor configured to execute computer readable instructions included on a non-transitory memory; and
a non-transitory memory including processor-readable instructions, that performs an operation when executed by the processor, the operation comprising:
receiving, from a user equipment (UE) device, a registration request that indicates a category, wherein the category comprises at least one of an emergency vehicle category or a roadside unit (RSU) category;
receiving a registration response from an access and mobility function (AMF), the registration response comprising a group identifier that indicates the category, wherein the group identifier is based on a subscription profile from a unified data management (UDM) module;
selecting resources from a resource pool based on the group identifier, the resource pool dedicated for use for emergency communications; and
allocating the selected resources to the UE device.
8. The system of claim 7 , wherein the registration request indicates whether the UE device supports a PC5 interface.
9. The system of claim 7 , wherein the selected resources comprise a plurality of resource blocks (Rbs).
10. The system of claim 7 , wherein the UE device is associated with an identifier that is unique to the UE device.
11. The system of claim 7 , wherein the system comprises an eNodeB device.
12. The system of claim 10 , wherein the identifier comprises an international mobile subscriber identity (IMSI).
13. A system comprising:
a network interface in communication with a network;
a processor configured to execute computer readable instructions included on a non-transitory memory; and
a non-transitory memory including processor-readable instructions, that performs an operation when executed by the processor, the operation comprising:
receiving, from a user equipment (UE) device, a registration request that indicates a category, wherein the category comprises at least one of an emergency vehicle category or a roadside unit (RSU) category;
receiving a subscription profile from a unified data management (UDM) module, the subscription profile comprising a group identifier that indicates the category; and
sending the group identifier to an eNodeB device, wherein the group identifier is associated with a resource pool dedicated for use for emergency communications.
14. The system of claim 13 , wherein the registration request indicates whether the UE device supports a PC5 interface.
15. The system of claim 13 , wherein the subscription profile comprises a quality of service (QoS) parameter.