DEVICES AND/OR SERVICES

TECHNICAL FIELD

[001] Disclosed are embodiments related to access control for mission critical (MC) communication devices and/or services.

BACKGROUND

[002] Before a user equipment (UE) (i.e., a communication device capable of communicating wirelessly with an access point (e.g., a base station)) can properly communicate within another communication device (e.g., a server), the UE must perform what is known as “cell search” to find, identify, and synchronize with a cell served by an access point. Then, the UE must acquire basic system information, and perform an access barring check to determine whether or not the UE is allowed to use the cell for network connectivity. If the access is allowed, the UE will then perform what is known as a “random access” (RA) procedure to establish a connection (e.g., a Radio Resource Control (RRC) connection) with the access point. Examples of UEs include: smartphones, sensors, appliances, meters, computers, servers, etc.

[003] 1. New Radio (NR) cell search and System Information Acquisition

[004] In NR, the combination of a synchronization signal (SS) and a physical broadcast channel (PBCH) is referred to as a SS/PBCH block (SSB). Similar to LTE, a pair of synchronization signals (i.e., a primary synchronization signal (PSS) and secondary synchronization signal (SSS)), is periodically transmitted on downlink from each cell to allow a UE to initially access to the network. By detecting a SS, a UE can obtain the physical cell identity, achieve downlink synchronization in both time and frequency, and acquire the timing for the PBCH.

[005] The PBCH carries a master information block (MIB), which contains system information from which the UE can know if the cell is barred and the info on how to acquire system information block 1 (SIBl). This SIB1 carries the additional system information that is needed for a UE to be able to perform access barring control and the subsequent random access procedure if the access request can be sent. [006] 2. NR Unified Access Control

[007] Before sending any connection request to base station (e.g., gNB), a UE shall evaluate the cell reservation and access restriction related information contained in SIB1 to check whether a connection request for the access attempt should be barred or not. This is done by the Unified Access Control (UAC) mechanism specified in 5G.

[008] The UE maps its access attempt to an access category and one or more access identities. The access identities and access categories are defined in Table 1 (copied from Table 4.5.2.1 in 3 GPP TS 24.501 vl6.3.0 ) and Table 2 (copied form Table 4.5.2.2 in TS 24.501 vl6.3.0), respectively. The information on cell access restrictions associated with access categories and access identities is broadcast in SIB1. Based on this information received from SIB1, the UE determines whether an access attempt is authorized for the selected Public Land Mobile Network (PLMN), and the associated access category and access identity(ies) for the access attempt.

[009] This UAC mechanism can effectively reduce the amount of traffic accessing the network shortly after SIBl broadcasting. It also avoids an increase in network processing load because connection requests are barred, meaning that no connection request will be sent from the UE to the gNB.

TABLE 1

TABLE 2

[0010] 3. NR Random Access (RA) Procedure [0011] If an access attempt is permitted, the UE performs an RA procedure (e.g., the 4- step RA procedure) to establish an RRC connection to the gNB. During the RA procedure the UE will transmit an RRCSetupRequest message. The information elements (IEs) included in the RRCSetupRequest message are defined in 3GPP TS 38.331 and shown below in Table 3.

TABLE 3: RRCSetupRequest message

[0012] The establishmentCause IE contained in this RRCSetupRequest message indicates the reason for the connection establishment request, e.g., “emergency” for emergency calls, “mps-Priority Access” for multimedia-priority UEs and “mcs-PriorityAccess” for Mission Critical UEs, etc.

[0013] A UE sets the establishmentCause based on the configured access identities/access categories. The mapping between access categories/access identities and RRC establishment causes are shown in Table 4 below (copied from Table 4.5.6.1 of 3GPP TS 24.501 vl6.3.0). A gNB identifies the type of connection request from a UE by decoding the establishmentCause, based on which, the gNB decides whether to accept the RRC connection request or to reject the request with RRCConectionReject. For instance, in a mission critical situation where the network is highly loaded, to guarantee the QoS for MC UEs (i.e., UEs configured for MC services) a gNB can prioritize the connection establishment for MC UEs and reject the requests from non-MC UEs.

Table 4: Mapping table for access identities/access categories and RRC establishment cause

SUMMARY

[0014] Certain challenges presently exist. For instance, in some mission critical (MC) situations, not all MC UEs and/or MC services should be treated equally. For example, an access request from a UE that is being used by a commander in charge of coordinating several different groups of first responders may need higher priority than an access request transmitted by a UE being used by one of the first responders. That is, for example, the access requests from different MC UEs need to be treated with different priorities based on their operation roles, the importance of the data or services to be transmitted over the network, etc. According to the NR Rel-16 standard, all MC UEs are configured with access identity 2, which means that during initial access, the establishmentCause for all MC UEs will be set to mcs-Priority Access. This implies that a network node can’t differentiate between different MC UEs (e.g., can’t differentiate between a first MC UE that is attempting to invoke a first MC service and a second MC UE attempting to invoked a second MC service that has a lower priority than the first MC service). Thus, the network node (e.g., gNB) cannot perform differentiated access control during initial access phase.

[0015] Accordingly, in one aspect there is provided a method performed by a network node for configuring UEs. The method includes assigning a first access identity number to a first mission critical (MC) UE. The method also includes assigning a second access identity number to a second MC UE. The first access identity number is different than the second access identity number.

[0016] In another aspect, there is provided a method performed by a network node for configuring a UE. The method includes configuring the UE with an access identity number reserved for UEs configured for mission critical services (MCSs). The method also includes configuring the UE with a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first RRC establishment cause value. The method also includes configuring the UE with a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value. The second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0017] In another aspect there is provided a method performed by a UE. The method includes the UE storing an access identity number, wherein the access identity number is reserved for UEs configured for an MCS. The method also includes the UE storing a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first Radio Resource Control, RRC, establishment cause value. The method also includes the UE storing a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value. The second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0018] In another aspect there is provided a computer program comprising instructions which when executed by processing circuitry of a network node causes the network node to perform any one of the network node methods disclosed herein. In another aspect there is provided a carrier containing the computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium. In another aspect there is provided a network node, where the network node is configured to perform any one of the network node methods disclosed herein. In some embodiments, the network node includes processing circuitry and a memory containing instructions executable by the processing circuitry, whereby the network node is configured to perform any one of the network methods disclosed herein.

[0019] In another aspect there is provided a computer program comprising instructions which when executed by processing circuitry of a UE causes the UE to perform any one of the UE methods disclosed herein. In another aspect there is provided a carrier containing the computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium. In another aspect there is provided a UE, where the UE is configured to perform any one of the UE methods disclosed herein. In some embodiments, the UE includes processing circuitry and a memory containing instructions executable by the processing circuitry, whereby the UE is configured to perform any one of the network methods disclosed herein.

[0020] The aspects and embodiments disclosed herein are advantageous in that they enable that different MC UEs can use different establishment causes when attempting to establish an RRC connection. By enabling a differentiation among different MC UEs and/or MC services in establishment causes, this allows the network node to apply a different admission control at an early stage. Therefore, in an extreme network load situation, a network node can, for example, prioritize the more important MC services to access to the network first. In addition, the network node can utilize the information to predict the network load and the demanded additional resources, so that it can make better decisions on the load balancing, traffic management and queuing mechanism after an RRC connection has been established.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0022] FIG. 1 illustrates a RA procedure according to an embodiment.

[0023] FIG. 2 is a flowchart illustrating a process according to some embodiments.

[0024] FIG. 3 is a flowchart illustrating a process according to some embodiments.

[0025] FIG. 4 is a flowchart illustrating a process according to some embodiments.

[0026] FIG. 5 illustrates a network node according to some embodiments.

[0027] FIG. 6 illustrates a UE according to some embodiments.

DETAILED DESCRIPTION

[0028] FIG. 1 illustrates a random access (RA) procedure being performed by a UE 102.

That RA procedure is used by UEs to establish a connection (e.g., a Radio Resource Control (RRC) connection) with a network node 104 (e.g., an access point, which is also known as a base station). The RA procedure shown in FIG. 1 is the 4-step RA procedure, also referred to as the Type-1 random access procedure in 3GPP TS 38.213, but other RA procedures exist (e.g., the 2- step RA procedure). In a first step, UE 102 initiates the RA procedure by transmitting a random- access preamble (RAP) (a.k.a., “Message 1” or “Msg 1”) on the Physical Random Access Channel (PRACH). After detecting the Msgl, the network node 104 (e.g., a 5G base station (gNB)) responds by transmitting to the UE on the Physical Downlink Control Channel (PDCCH) Downlink Control Information (DCI) (e.g., DCI format 1 0) to prepare the UE to receive a random-access response (RAR) (a.k.a., “Message 2” or “Msg2”) and then sends the RAR on the Physical Downlink Shared Channel (PDSCH). In the third step, after successfully decoding Msg2, the UE 102 continues the procedure by transmitting a message (a.k.a., “Message 3” or “Msg3”) on the Physical Uplink Shared Channel (PUSCH). Msg3 is or contains an RRC connection establishment request. In the last step of the procedure, the gNB transmits a message (a.k.a., “Message 4” or “Msg4”) on the Physical Downlink Shared Channel (PDSCH) for contention resolution. Msg3 includes a rrcSetupRequest message, which contains the establishmentCause Information Element (IE) which contains a value indicating the reason that caused the UE 102 to initiate the connection establishment, e.g., emergency call, mission critical services, multimedia priority services, etc. The network node 104 identifies the type of connection request being requested by UE 102 by decoding the establishmentCause IE received in msg3, based on which, the network node 104 decides whether this request shall be admitted or rejected, based on the network traffic load situation and available resource in the network.

[0029] In many mission critical (MC) situations, the access requests from different MC

UEs need to be treated with different priorities based on their operation roles, the importance of the data or services to be transmitted over the network, etc. For example, a central commander who coordinates the mission critical actions of a first responder group needs to be configured with a relatively higher priority, the first responders can be configured with a relatively lower priority. As another example, one MC UE group operating in a life-threatening situation needs to be configured with a higher priority, and the other MC UE groups can be configured with a relatively lower priority, even if they are all using the same service. Yet another example, an MC UE (e.g., a MC drone fleet leader or a MC rely device) that has a centralized decision or coordination role for the other MC devices may need to be configured with a relatively higher priority.

[0030] Accordingly, more than one RRC establishment cause is defined for MC UEs and/or MC services so that the network can distinguish between different MC UEs and/or MC services. Different methods of defining a more than one RRC establishment causes for MC UE/services are defined. Note that the examples focus on MC services, but the same methodology can be applied to other services, e.g., multimedia priority services.

[0031] 1. Using Existing Access Identities

[0032] In this embodiment, existing establishment causes and access identities specified in 3GPP standard are utilized. This can be achieved by, for example, configuring one group of MC UEs (e.g., higher priority MC UEs) with Access Identity 2, and the configuring another group of MC UEs (e.g., lower priority MC UEs) with Access Identity 11, 12, 13, 14, or 15. That is, for example, when configuring an MC UE, a network operator can select an access identity for the MC UE from a set of two or more access identities (e.g., a set comprising the following access identities: 2, 11, 12, 13, 14, and 15), whereas today the network operator has no choice but to select the same access identity for all MC UEs (i.e., access identity 2).

[0033] Based on Table 4, the access attempts from higher priority MC UEs will be mapped to the establishment cause “mcs-Priority Access,” and the access attempts from lower priority MC UEs will be mapped to the establishment cause “highPriority Access.” A network node can prioritize between MC UEs mapped to “mcs-Priority Access” and MC UEs mapped to “highPrioirty Access,” depending on the current network load situation and the resource utilization status. That is, for example, an MC UE that uses “mcs-Priority Access” as the establishment cause can be given more resources than an MC UE that uses “highPriority Access” as the establishment cause.

[0034] In one embodiment, all MC UEs are provisioned with access identities from the value set (11, 12, 13, 14, 15} on their SIM/USIM card, and the core network can assign access identity 2 to UEs configured with higher priority mission critical services before these UEs apply access control.

[0035] This alternative utilizes the existing standardized differentiation indicators, and it can support differentiation between MC UEs base on, for example, their operation roles. A drawback of this method is that it is not possible for a network to acquire service type information of MC UEs, so prioritization for a certain type of MC service cannot be supported during initial access phase. Another drawback of this method is that the operator needs to make sure that the access identities from the value set { 11, 12, 13, 14, 15} are not configured for non-MC UEs, otherwise the network node will not be able to distinguish between these non- MC UEs and the MC UEs whose access requests are mapped to “highPri ority Access ” Yet another drawback of this method is that the network can have only up to two levels of priorities used between MC UEs, one mapped to “highPri ority Access”, and the other one mapped to “mcs-Priority Access.”

[0036] 2. New Establishment Cause(s) [0037] In another embodiment one or more new establishment causes are defined. For example, in one embodiment, at least one new establishment cause is defined to provide more than one RRC establishment causes sent by different MC UEs. The additional establishment cause can be defined by using one of the six spared parameters that have not been defined for the establishmentCause field.

TABLE 5

[0038] As a UE sets the establishmentCause based on the configured access identities/access categories, new mapping rules need to be added in the mapping table for access identities/access categories and RRC establishment cause to support a newly added establishment cause in the rrcSetupRequest message.

[0039] 2.1 Define a new access identity value for MC UEs

[0040] In one embodiment at least one new access identity value (e.g., 3) is defined for certain MC UEs. MC UEs configured with access identity 2 and MC UEs configured with the new access identity value (e.g., 3) may have different access priorities.

[0041] In one embodiment, the new access identity value is any value in the set of values 3-10 that are currently reserved for future use.

[0042] Table 6 and Table 7 give an example on the way of adding an additional establishment cause for differentiating MC UEs by defining a new access identity for MC UEs and modifying the mapping table for access identities/access categories and RRC establishment cause accordingly.

Table 6 Modified Access Identities

Table 7 Modified mapping table for access identities/access categories and RRC establishment cause (new access identities) [0043] As can be seen by comparing Table 6 with Table 1, a new UE configuration and corresponding access identity (i.e., 3) has been added to the table provide an access identity for lower priority MC UEs, and as can be seen by comparing Table 7 with Table 4, a new rule (i.e., Rule 6) has been added to the table for MC UEs having an access identity of 3.

[0044] Because a dedicated access identity is standardized for MC UEs, the network can utilize one or more additional access identities (e.g., 3-10) together with the already specified access identity (i.e., 2) to differentiate between MC UEs configured with different priority MC services, without preventing using access identities 11-15 for other users with “hi ghPriority Access”.

[0045] 2.2: Define new standardized access categories for MC Services

[0046] In an embodiment, at least a new access category is standardized for differentiating different MC services during the initial access phase, and at least a new rule is defined for mapping the type of access attempt for the new access category.

[0047] In an embodiment, a new standardized access category in combination with the legacy access identity (i.e., access identity 2) is mapped to a new RRC establishment cause.

[0048] Table 8 and Table 9 give an example of additional establishment causes for differentiating MC Services by defining at least a few new access categories for MC Services and modifying the mapping table for access identities/access categories and RRC establishment cause accordingly. For example, as shown in Table 8, new access categories 10- 13 are introduced.

[0049] In the example shown in Table 9, access identity 2 is used in combination with a set of new standardized access categories (i.e., 10-13 in this example) to obtain a set of new RRC establishment causes. Note that the legacy Rel-15/16 MC UEs will follow the legacy mapping table (Table 4), as the new release MC UEs and legacy MC UEs will have different RRC establishment cause values, the network node can distinguish the legacy MC UEs and new release MC UEs, therefore, no impact on legacy MC UE operations.

Table 8 Part of modified Mapping Table for access categories

Table 9 Modified mapping table for access identities/access categories and RRC establishment cause (new access categories)

[0050] In an embodiment, a new standardized access category in combination with a new access identity (i.e., different from access identity 2) is mapped to a new RRC establishment cause.

[0051] In another example as shown in Table 10, a new access identity (access identity

3) is used together with a set of new access categories (e.g., 10-13) to define a set of new RRC establishment causes. Note that the legacy Rel-15/16 MC UEs will follow the legacy mapping table (Table 4), as the new release MC UEs and legacy MC UEs will have different RRC establishment cause values, the network node can distinguish the legacy MC UEs and new release MC UEs, therefore, no impact on legacy MC UE operations.

Table 10 Modified mapping table for access identities/access categories and RRC establishment cause (new access identities and new access categories)

[0052] In an embodiment, a new standardized access category in combination with the legacy access identity is mapped to one new RRC establishment cause, the new standardized access category in combination with a new access identity is mapped to a different new RRC establishment cause. [0053] In an example as shown in Table 11, a new access identity (access identity 3) is used together with a set of new access categories (10, 11, 12, and 13) to define a set of new RRC establishment causes; the legacy access identity (access identity 2) is also used together with the same set of new access categories (10, 11, 12, and 13) to define a different set of new RRC establishment causes. These two different sets of new RRC establishment causes are mapped to different priorities. For instance, the set of new RRC establishment causes associated to the access identity 2 is mapped to higher priority MC UEs/services, and the set of new RRC establishment causes associated to access identity 3 are mapped to lower priority MC UEs/Services.

[0054] Note that the legacy Rel- 15/16 MC UEs will follow the legacy mapping table

(Table 4), as the new release MC UEs and legacy MC UEs will have different RRC establishment cause values, the network node can distinguish the legacy MC UEs and new release MC UEs, therefore, no impact on legacy MC UE operations.

Table 11

Modified mapping table for access identities/access categories and RRC establishment cause (legacy access identity with new access categories, and new access identities with new access categories)

[0055] 2.3: Define different operator-defined access categories for MC Services [0056] In an embodiment, at least an operator-defined access category is defined for differentiating different MC services. In the case where a UE has already attached and received a Non-Access Stratum (NAS) message (e.g., a message originating from an Access and Mobility Function (AMF)) before entering RRC Idle state, an operator-defined access categories can be defined for differentiation between different MC Services.

[0057] FIG. 2 is a flowchart illustrating a process 200, according to an embodiment, for configuring UEs. Process 200 may begin in step s202. Step s202 comprises assigning a first access identity number to a first UE (e.g., UE 102). Step s204 comprises assigning a second access identity number to a second MC UE, where the first access identity number is different than the second access identity number. In some embodiments, the first access identity is 2. In some embodiments, the second access identity number is an integer greater than 2 and less than 16. In some embodiments, the second access identity number is an integer greater than 10 and less than 16. In some embodiments, the second access identity number is an integer greater than 2 and less than 11. In some embodiments, the process further comprises configuring the first MC UE with a first rule that maps a first tuple comprising the first access identity number to a first Radio Resource Control (RRC) establishment cause value (e.g., mcs-Priority Access or mcs-Pri ority Access-1 evell); and configuring the second MC UE with a second rule that maps a second tuple comprising the second access identity number to a second RRC establishment cause value (e.g., mcs-Priority Access-level2), where the second RRC establishment cause value is different than the first RRC establishment cause value. In some embodiments, the second tuple further comprises a first access category identifier (e.g., Category 10). In some embodiments, the process further includes configuring the second MC UE with a third rule that maps a third tuple comprising the second access identity number and a second access category identifier (e.g., Category 11) to a third RRC establishment cause value (e.g., mcs-Priority Access-Data). In some embodiments, the second access category identifier is 8 or an integer greater than 9 and less than 32.

[0058] FIG. 3 is a flowchart illustrating a process 300, according to an embodiment, for configuring a UE (e.g., UE 102). Process 300 may begin in step s302. Step s302 comprises configuring the UE with an access identity number reserved for UEs configured for mission critical services (MCSs). Step s304 comprises configuring the UE with a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first RRC establishment cause value. Step s306 comprises configuring the UE with a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value. The second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0059] FIG. 4 is a flowchart illustrating a process 400 according to an embodiment.

Process 400 may be performed by UE 102 and may begin in step s402. Step s402 comprises the UE storing an access identity number, wherein the access identity number is reserved for UEs configured for an MCS. Step s404 comprises the UE storing a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first Radio Resource Control, RRC, establishment cause value. Step s406 comprises the UE storing a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value. The second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0060] In some embodiments, the access identity number is an integer greater than 1 and less than 11 (i.e., between and including 2-10). In some embodiments, the access identity number is 2. In some embodiments, the access identity number is greater than 2 and less than 11 (e.g., 3). In some embodiments, the first access category identifier is 8 or an integer greater than 9 and less than 32, and the second access category identifier is 8 or an integer greater than 9 and less than 32.

[0061] FIG. 5 is a block diagram of network node 104, according to some embodiments, for performing network node methods disclosed herein. As shown in FIG. 5, network node 104 may comprise: processing circuitry (PC) 502, which may include one or more processors (P) 555 (e.g., one or more general purpose microprocessors and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., network node 104 may be a distributed computing apparatus); at least one network interface 568 comprising a transmitter (Tx) 565 and a receiver (Rx) 567 for enabling network node 104 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 568 is connected; communication circuitry 548, which is coupled to an antenna arrangement 549 comprising one or more antennas and which comprises a transmitter (Tx) 545 and a receiver (Rx) 547 for enabling network node 104 to transmit data and receive data (e.g., wirelessly transmit/receive data); and a local storage unit (a.k.a., “data storage system”) 508, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. In embodiments where PC 502 includes a programmable processor, a computer program product (CPP) 541 may be provided. CPP 541 includes a computer readable medium (CRM) 542 storing a computer program (CP) 543 comprising computer readable instructions (CRI) 544. CRM 542 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 544 of computer program 543 is configured such that when executed by PC 502, the CRI causes network node 104 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, network node 104 may be configured to perform steps described herein without the need for code. That is, for example, PC 502 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

[0062] FIG. 6 is a block diagram of UE 102, according to some embodiments. As shown in FIG. 6, UE 102 may comprise: processing circuitry (PC) 602, which may include one or more processors (P) 655 (e.g., one or more general purpose microprocessors and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); communication circuitry 648, which is coupled to an antenna arrangement 649 comprising one or more antennas and which comprises a transmitter (Tx) 645 and a receiver (Rx) 647 for enabling UE 102 to transmit data and receive data (e.g., wirelessly transmit/receive data); and a local storage unit (a.k.a., “data storage system”) 608, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. In embodiments where PC 602 includes a programmable processor, a computer program product (CPP) 641 may be provided. CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644. CRM 642 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 644 of computer program 643 is configured such that when executed by PC 602, the CRI causes UE 102 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, UE 102 may be configured to perform steps described herein without the need for code. That is, for example, PC 602 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

[0063] Summary of Various Embodiments

[0064] Al. A method for configuring user equipments, UEs, the method comprising: assigning a first access identity number to a first mission critical, MC, UE; and assigning a second access identity number to a second MC UE, wherein the first access identity number is different than the second access identity number.

[0065] A2. The method of embodiment Al, wherein the first access identity is 2.

[0066] A3. The method of embodiment Al or A2, wherein the second access identity number is an integer greater than 2 and less than 16.

[0067] A4. The method of embodiment A3, wherein the second access identity number is an integer greater than 10 and less than 16.

[0068] A5. The method of embodiment A3, wherein the second access identity number is an integer greater than 2 and less than 11.

[0069] A6. The method of embodiment A5, further comprising: configuring the first

MC UE with a first rule that maps a first tuple comprising the first access identity number to a first Radio Resource Control, RRC, establishment cause value (e.g., mcs-Priority Access or mcs-Pri ority Access-level 1); and configuring the second MC UE with a second rule that maps a second tuple comprising the second access identity number to a second RRC establishment cause value (e.g., mcs-Priority Access-level2), wherein the second RRC establishment cause value is different than the first RRC establishment cause value. [0070] A7. The method of embodiment A6, wherein the second tuple further comprises a first access category identifier (e.g., Category 10).

[0071] A8. The method of embodiment A7, further comprising: configuring the second

MC UE with a third rule that maps a third tuple comprising the second access identity number and a second access category identifier (e.g., Category 11) to a third RRC establishment cause value (e.g., mcs-Priority Access-Data).

[0072] A9. The method of embodiment A7 or A8, wherein the second access category identifier is 8 or an integer greater than 9 and less than 32.

[0073] Bl. A method for configuring a user equipment, UE, the method comprising: configuring the UE with an access identity number reserved for UEs configured for mission critical services, MCSs; configuring the UE with a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first Radio Resource Control, RRC, establishment cause value; and configuring the UE with a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value, wherein the second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0074] B2. A method performed by a user equipment, UE, the method comprising: the

UE storing an access identity number, wherein the access identity number is reserved for UEs configured for mission critical services, MCSs; the UE storing a first rule that maps a first tuple comprising the access identity number and a first access category identifier to a first Radio Resource Control, RRC, establishment cause value; and the UE storing a second rule that maps a second tuple comprising the access identity number and a second access category identifier to a second RRC establishment cause value, wherein the second access category identifier is different than the first access category identifier, and the second RRC establishment cause value is different than the first RRC establishment cause value.

[0075] B3. The method of embodiment Bl or B2, wherein the access identity number is an integer greater than 1 and less than 11 (i.e., between and including 2-10). [0076] B4. The method of embodiment B1 or B2, wherein the access identity number is

2

[0077] B5. The method of embodiment B3, wherein the access identity number is greater than 2 and less than 11 (e.g., 3).

[0078] B6. The method of any one of embodiments B1-B5, wherein the first access category identifier is 8 or an integer greater than 9 and less than 32, and the second access category identifier is 8 or an integer greater than 9 and less than 32.

[0079] Cl . A computer program comprising instructions which when executed by processing circuitry of a network node causes the network node to perform the method of any one embodiments A1-A9, Bl, or B3-B6.

[0080] C2. A computer program comprising instructions which when executed by processing circuitry of a user equipment, UE, causes the UE to perform the method of any one embodiments B2-B6.

[0081] C3. A carrier containing the computer program of embodiment Cl or C2, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (542, 642).

[0082] D1. A network node, the network node being adapted to perform the method of any one of embodiments A1-A9, Bl, or B3-B6.

[0083] El. A network node, the network node comprising: processing circuitry; and a memory, the memory containing instructions executable by the processing circuitry, whereby the network node is operative to perform the method of any one of the embodiments A1-A9, Bl, or B3-B6.

[0084] F 1. A user equipment, EE, the UE being adapted to perform the method of any one of embodiments B2-B6.

[0085] Gl. A user equipment, UE, the UE comprising: processing circuitry; and a memory, the memory containing instructions executable by the processing circuitry, whereby the UE is operative to perform the method of any one of the embodiments B2-B6. [0086] While various embodiments are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0087] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.