Multimedia priority services (MPS) and / or mission critical services (MCS) user devices

Abstract

Various example embodiments relate generally to user devices configured for at least one of multimedia priority services (MPS) or mission critical services (MCS). In some examples, a method of a first apparatus comprises transmitting, to a second apparatus, a resume request, receiving, from the second apparatus, a radio resource control, RRC, reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time, and ignoring the wait time.

Description

[0001] Multimedia Priority Services (MPS) and / or Mission Critical Services (MCS) User Devices

[0002] Technical Field

[0003] Various example embodiments relate generally to user devices configured for at least one of multimedia priority services (MPS) or mission critical services (MCS).

[0004] Background

[0005] Multimedia priority services (MPS) and mission critical services (MCS) are 3GPP features for enabling subscribers associated with national security (NS) or emergency preparedness (EP) to make priority calls or data sessions on a service provider's network, for example in times of network congestion. These services may be used by emergency responders, law enforcement agencies, hospitals and / or other infrastructure organizations to ensure they can communicate effectively during emergencies or times of crisis.

[0006] Summary

[0007] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. The embodiments that do not fall under the scope of the claims are to be interpreted as examples useful for understanding the disclosure.

[0008] According to a first aspect, there is provided a first apparatus, configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, the first apparatus comprising: means for transmitting, to a second apparatus, a resume request; means for receiving, from the second apparatus, a radio resource control, R.R.C, reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and means for ignoring the wait time.

[0009] In some examples, the at least one of MPS or MCS that the first apparatus is configured for is indicated by an upper layer of the first apparatus.

[0010] In some examples, the wait time is a T302 time period.

[0011] In some examples, the means for ignoring the wait time is configured based at least in part on: a pre-configuration of the first apparatus; or an indication or allowance from the second apparatus.In some examples, the means for ignoring the wait time is configured to ignore the wait time for at least one of: any resume requests; predetermined type(s) of resume requests; any access requests; or any establishment requests.

[0012] In some examples, the predetermined type(s) of resume requests comprise at least one of: resume requests for RIMA update procedure; resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated, MO, or mobile terminated, MT, access.

[0013] In some examples, the means for ignoring the wait time is configured to ignore the wait time for initiating a resume procedure with the second apparatus.

[0014] In some examples, the means for ignoring the wait time is configured to ignore the wait time based on the first apparatus being configured for at least one of MPS or MCS.

[0015] According to a second aspect, there is provided a method of a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, the method comprising: transmitting, to a second apparatus, a resume request; receiving, from the second apparatus, a radio resource control, RRC, reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and ignoring the wait time.

[0016] In some embodiments, the second aspect may comprise any feature described in relation to the first aspect.

[0017] According to a third aspect, there is provided a computer program product comprising program instructions which, when the program instructions are executed by a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to carry out a method of: transmitting, to a second apparatus, a resume request; receiving, from the second apparatus, a radio resource control, RRC, reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and ignoring the wait time.

[0018] In some embodiments, the third aspect may comprise any feature described in relation to the first aspect.According to a fourth aspect, there is provided a computer program product embodied on a non-transitory distribution medium readable by a computer and comprising program instructions which, when the program instructions are executed by a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to: transmit, to a second apparatus, a resume request; receive, from the second apparatus, a radio resource control, R.R.C, reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and ignore the wait time.

[0019] In some embodiments, the fourth aspect may comprise any feature described in relation to the first aspect.

[0020] According to a fifth aspect, there is provided a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to: transmit, to a second apparatus, a resume request; receive, from the second apparatus, a radio resource control, R.R.C, reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and ignore the wait time.

[0021] In some embodiments, the fifth aspect may comprise any feature described in relation to the first aspect.

[0022] According to a sixth aspect, there is provided a first apparatus, configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, the first apparatus comprising: means for receiving, from a second apparatus, an indication to ignore a wait time included with a radio resource control, R.R.C, reject or R.R.C release with suspend configuration; means for transmitting, to a second apparatus, a resume request; means for receiving, from the second apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and means for ignoring, based on the indication and the first apparatus being configured for at least one of MPS or MCS, the wait time.

[0023] In some examples, the indication comprises at least one of: a configuration for ignoring the wait time; or an indication that the wait time is allowed to be ignored.In some examples, the indication is received in broadcast signaling from the second apparatus. In some examples, the indication is comprised within system information. In some examples, the indication is comprised within a system information block, SIB.

[0024] In some examples, the indication is received in dedicated radio resource control, RRC, signaling from the second apparatus. In some examples, the indication is received in an RRC release message.

[0025] In some examples, the at least one of MPS or MCS that the first apparatus is configured for is indicated by an upper layer of the first apparatus. In some examples, the wait time is a T302 time period. In some examples, the means for ignoring the wait time is configured based at least in part on: a pre-configuration of the first apparatus; or an indication or allowance from the second apparatus. In some examples, the means for ignoring the wait time is configured to ignore the wait time for at least one of: any resume requests; predetermined type(s) of resume requests; any access requests; or any establishment requests. In some examples, the predetermined type(s) of resume requests comprise at least one of: resume requests for RNA update procedure; resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated, MO, or mobile terminated, MT, access. In some examples, the means for ignoring the wait time is configured to ignore the wait time for initiating a resume procedure with the second apparatus.

[0026] According to a seventh aspect, there is provided a method of a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, the method comprising: receiving, from a second apparatus, an indication to ignore a wait time included with a radio resource control, RRC, reject or RRC release with suspend configuration; transmitting, to a second apparatus, a resume request; receiving, from the second apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and ignoring, based on the indication and on the first apparatus being configured for at least one of MPS or MCS, the wait time.

[0027] In some embodiments, the seventh aspect may comprise any feature described in relation to the sixth aspect.

[0028] According to an eighth aspect, there is provided a computer program product comprising program instructions which, when the program instructions are executed by a firstapparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to carry out a method of: receiving, from a second apparatus, an indication to ignore a wait time included with a radio resource control, R.R.C, reject or R.R.C release with suspend configuration; transmitting, to a second apparatus, a resume request; receiving, from the second apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and ignoring, based on the indication and on the first apparatus being configured for at least one of MPS or MCS, the wait time.

[0029] In some embodiments, the eighth aspect may comprise any feature described in relation to the sixth aspect.

[0030] According to a ninth aspect, there is provided a computer program product embodied on a non-transitory distribution medium readable by a computer and comprising program instructions which, when the program instructions are executed by a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to: receive, from a second apparatus, an indication to ignore a wait time included with a radio resource control, R.R.C, reject or R.R.C release with suspend configuration; transmit, to a second apparatus, a resume request; receive, from the second apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and ignore, based on the indication and on the first apparatus being configured for at least one of MPS or MCS, the wait time.

[0031] In some embodiments, the ninth aspect may comprise any feature described in relation to the sixth aspect.

[0032] According to a tenth aspect, there is provided a first apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to: receive, from a second apparatus, an indication to ignore a wait time included with a radio resource control, R.R.C, reject or R.R.C release with suspend configuration; transmit, to a second apparatus, a resume request; receive, from the second apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and ignore, based on the indication and on the first apparatus being configured for at least one of MPS or MCS, the wait time.In some embodiments, the tenth aspect may comprise any feature described in relation to the sixth aspect.

[0033] According to an eleventh aspect, there is provided a second apparatus comprising: means for transmitting, to a first apparatus configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, an indication to ignore a wait time associated with a radio resource control, RRC, reject or RRC release with suspend configuration; means for receiving, from the first apparatus, a resume request; means for transmitting, to the first apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and means for receiving, from the first apparatus, initiation of a resume procedure.

[0034] In some examples, the indication comprises at least one of: a configuration associated with the wait time; or an indication that the wait time is allowed to be ignored.

[0035] In some examples, the indication is transmitted in broadcast signaling to the first apparatus. In some examples, the indication is comprised within system information. In some examples, the indication is comprised within a system information block, SIB.

[0036] In some examples, the indication is transmitted in dedicated radio resource control, RRC, signaling to the first apparatus. In some examples, the indication is transmitted in an RRC release message.

[0037] In some examples, the wait time is a T302 time period. In some examples, the indication to ignore the wait time is for: any resume requests; or predetermined type(s) of resume requests; any access requests; or any establishment requests. In some examples, the predetermined type(s) of resume requests comprise at least one of: resume requests for RNA update procedure; resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated, MO, or mobile terminated, MT, access.

[0038] According to a twelfth aspect, there is provided a method of a second apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, the method comprising: transmitting, to a first apparatus configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, an indication to ignore a wait time associated with a radio resource control, RRC, reject or RRC release withsuspend configuration; receiving, from the first apparatus, a resume request; transmitting, to the first apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and receiving, from the first apparatus, initiation of a resume procedure.

[0039] In some embodiments, the twelfth aspect may comprise any feature described in relation to the eleventh aspect.

[0040] According to a thirteenth aspect, there is provided a computer program product comprising program instructions which, when the program instructions are executed by a second apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to carry out a method of: transmitting, to a first apparatus configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, an indication to ignore a wait time associated with a radio resource control, RRC, reject or RRC release with suspend configuration; receiving, from the first apparatus, a resume request; transmitting, to the first apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and receiving, from the first apparatus, initiation of a resume procedure.

[0041] In some embodiments, the thirteenth aspect may comprise any feature described in relation to the eleventh aspect.

[0042] According to a fourteenth aspect, there is provided a computer program product embodied on a non-transitory distribution medium readable by a computer and comprising program instructions which, when the program instructions are executed by a second apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, cause the first apparatus to: transmit, to a first apparatus configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, an indication to ignore a wait time associated with a radio resource control, RRC, reject or RRC release with suspend configuration; receive, from the first apparatus, a resume request; transmit, to the first apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time; and receive, from the first apparatus, initiation of a resume procedure.

[0043] In some embodiments, the fourteenth aspect may comprise any feature described in relation to the eleventh aspect.According to a fifteenth aspect, there is provided a second apparatus configured for at least one of multimedia priority services, MPS, or mission critical services, MCS, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to: transmit, to a first apparatus configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, an indication to ignore a wait time associated with a radio resource control, R.R.C, reject or R.R.C release with suspend configuration; receive, from the first apparatus, a resume request; transmit, to the first apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; and receive, from the first apparatus, initiation of a resume procedure.

[0044] In some embodiments, the fifteenth aspect may comprise any feature described in relation to the eleventh aspect.

[0045] Drawings

[0046] In the following, example embodiments will be described in greater detail with reference to the embodiments and the accompanying drawings, in which:

[0047] FIG. 1 illustrates an example communication network;

[0048] FIG. 2 is a signalling diagram illustrating a UE-triggered RIMA update procedure;

[0049] FIG. 3 is a flow diagram of first apparatus operations according to an example embodiment;

[0050] FIG. 4 is a signal flow diagram according to an example embodiment;

[0051] FIG. 5 is a flow diagram of first apparatus operations according to another example embodiment;

[0052] FIG. 6 is a flow diagram of second apparatus operations according to another example embodiment; and

[0053] FIG. 7 illustrates an example apparatus.

[0054] Detailed Description

[0055] Various example embodiments relate generally to user devices configured for at least one of multimedia priority services (MPS) or mission critical services (MCS). Example embodiments may relate to the handling, by such user devices, of reject or release with suspend messages when received from a network node.

[0056] The following embodiments are exemplary. Although the specification may refer to "an", "one", or "some" embodiment(s) in several locations of the text, this does not necessarilymean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms "first," "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0057] For the purposes of the present disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0058] Embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (L.TE), L.TE-Advanced, and enhanced L.TE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0059] As used herein, the term "network device" or "network node" refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a non-terrestrial network (NTN) or non-ground network device such as a satellitenetwork device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0060] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralised unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, the DUs may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0061] The term "terminal device" refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0062] A term "resource", as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term "transmission" and / or "reception" may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.FIG. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network or a cellular communication network may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0063] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0064] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0065] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0066] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprisee.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example. A UE may be configured for MPS and / or MCS by one or more upper layers (for example a NAS layer) of the UE. For example, the one or more upper layers may configure the UE for MPS and / or MCS by indicating access identity "1" and / or "2" in accordance with unified access control (UAC) standards.

[0067] A radio access network notification area (RNA) is an area assigned to UEs by the RAN. When a UE moves out of the RNA, it may report its location change to the RAN using an RNA update (RNAU) procedure.

[0068] FIG. 2 illustrates an UE-triggered RNAU procedure involving context retrieval over an Xn interface. FIG. 2 indicates signalling between a UE 200, a gNB 202, a last serving gNB 204 and an AMF 206.

[0069] The RNAU procedure may be triggered when the UE 200 moves out of a configured RNA, or the RNAU procedure may be triggered periodically.

[0070] In a first operation 2.1, the UE resumes from an RRC_Inactive state and provides to the gNB 204 an RNAU message. The RNAU message includes an inactive radio network temporary identifier (I-RNTI) allocated by the last serving gNB 204 and at least one appropriate cause value. A cause value indicates a cause (reason) for the RNAU. In a second operation 2.2, the gNB 204, if able to resolve the gNB identity contained in the I-RNTI, transmits a retrieve UE context request to the last serving gNB 206, including the at least one cause value. In a third operation 2.3, the last serving gNB 206 may responsively transmit to the gNB 202 the UE context for the UE 200. In a fourth operation 2.4, the gNB 202 may move the UE 200 to the RRC_Connected state, the RRC_Idle state or RRC_Inactive state. We assume the latter case in the following. In a fifth (optional) operation 2.5, the gNB 202 may transmit to the last serving gNB 204 a forwarding address indication if loss of downlink user data buffered in the last serving gNB is to be prevented. In a sixth operation 2.6, the gNB 202 may transmit a path switch request to the AMF 206. In a seventh operation 2.7, the AMF 206 may responsively transmit a path switch request response to the gNB 202. In an eighth operation 2.8, the gNB 202 may keep the UE 200in the RRC_Inactive state by sending an RRCRelease with suspend configuration to the UE. In a ninth operation 2.9, the gNB 202 may trigger the release of the UE resources at the last serving gNB 204. Further details of the above process may be found with reference to 3GPP TS 38.300.

[0071] A RAN may also provide overload and access control functionality such as RACH back off, RRC connection Reject, RRC connection release and UE-based access barring mechanisms.

[0072] 3GPP TS 22.261 specifies an example UAC framework which may apply to all 5G NR states of RRC_Idle, RRC_Inactive and RRC_Connected. The RAN may broadcast barring control information associated with access categories and / or access identities; in the case of network sharing, the barring control information can be set individually for each public land mobile network (PLMN). A UE may determine whether an access attempt is authorized based on the barring control information for the selected PLMN, and the selected access category and access identity or identities for the access attempt. For non-access stratum (NAS) triggered requests, the NAS determines the access category and access identity or identities. For access stratum (AS) triggered requests, RRC determines the access category and NAS determines the access identity or identities. The gNB handles access attempts with establishment cause(s) or resume cause(s); where the establishment or resume causes indicate "emergency", "mps-PriorityAccess" and "mcs-PriorityAccess" for, respectively, emergency calls or session, MPS subscribers and MCS subscribers, the gNB handles with high priority and will respond with an RRCReject message only in extreme network load conditions that may threaten gNB stability.

[0073] For the RNAU procedure, however, the resume cause assigned to MPS subscribed UEs is "rna-Update" and not "mps-PriorityAccess". As such, the RNAU message, or resume request, sent by MPS subscribed UEs during the RNAU procedure may not be prioritized, for example when the gNB is congested. Furthermore, if the gNB responsively transmits an RRCReject message to the UE, the UE will start a timer (e.g., timer T302) associated with a wait time of between 1 and 16 seconds and is barred until the timer expires. Only access categories 0 and 2 (respectively associated with paging response and emergency access categories) are exempt from UAC while the timer is running. However, access category 8 (mobile originated signalling on RRC level resulting from other than paging) is used during RNAU. Therefore, all resume procedures in the RRC_Inactive state are blocked, except for paging response and emergency, including mobile origination and MPS resumes, at least until the timer (e.g., timer T302) expires.

[0074] Example embodiments enable UEs configured for at least one of MPS or MCS to handle at least one of a reject (e.g., RRCReject) message or release message with suspendconfiguration (RRCRelease with Suspend), wherein the reject or release with suspend configuration is includes a wait time, e.g., timer T302.

[0075] FIG. 3 is a flow diagram showing operations 200 that may be performed by one or more example embodiments. The operations 300 may be performed by hardware, software, firmware or a combination thereof. The operations 300 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories.

[0076] The operations 300 may, for example, be performed by a first apparatus, for example a UE. The first apparatus may be configured for at least one of MPS or MCS. The UE may be any of the UEs 120, 122 illustrated in FIG. 1 or the UE 200 illustrated in FIG. 2. The order of operations 300 is not necessarily indicative of their order of processing or performance.

[0077] A first operation 310 may comprise transmitting, to a second apparatus, a resume request.

[0078] A second operation 320 may comprise receiving, from the second apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time.

[0079] A third operation 330 may comprise ignoring (e.g., disregarding) the wait time for initiating a resume procedure with the second apparatus. The ignoring may be based, at least in part, on the first apparatus being configured for at least one of MPS or MCS.

[0080] The second apparatus may be a network node, e.g., gNB.

[0081] Ignoring the wait time may comprise not running a timer associated with the wait time (e.g., a T302 timer) or running the timer but ignoring or disregarding it.

[0082] In some examples, the at least one of the MPS or MCS that the first apparatus is configured for is indicated by an upper layer (e.g., NAS layer) of the first apparatus.

[0083] In some examples, the wait time is the T302 time period.

[0084] In some examples, the second operation 320 is based at least in part on: a preconfiguration of the first apparatus (for example, a configuration of the first apparatusthat specified in which circumstances the UE ignores the wait time, examples of which are explained herein); or an indication or allowance from the second apparatus.

[0085] In some examples, the second operation 320 is performed for at least one of: any resume requests, predetermined type(s) of resume requests, any access requests; or any establishment requests.

[0086] For example, the second operation 320 is performed for predetermined type(s) of resume requests that may comprise at least one of: resume requests for an R.NAU procedure; resume requests for procedures other than an R.NAU procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated (MO) or mobile terminated (MT) access.

[0087] In some examples, the second operation 320 may involve ignoring the wait time for initiating a resume procedure (e.g., associated with RNAU or other procedure) with the second apparatus.

[0088] The first apparatus may therefore attempt or initiate a resume procedure after receiving a reject or release with suspend configuration without having to wait for expiry of an associated wait time, such as the T302 time period. The first apparatus may perform the second operation 320 based the first apparatus being configured for at least one of MPS or MCS.

[0089] FIG. 4 illustrates a signal flow diagram according to an example embodiment with reference to a system comprising a UE 402 (as an example of a first apparatus) and a gNB 404 (as an example of a second apparatus).

[0090] A first operation 4.1 may comprise the UE 402 being configured for at least one of MPS and / or MCS, e.g., by being configured by at least one upper layer (e.g., the NAS layer) with access identity "1" and / or "2".

[0091] A second (optional) operation 4.2 may comprise the gNB 404 transmitting an indication to ignore a wait time included with an R.R.C reject or R.R.C release with suspend configuration. The indication may comprise at least one of a configuration for ignoring the wait time or an indication that the wait time is allowed to be ignored by the UE 402. The indication may be received in broadcast signaling from the gNB 404, wherein the indication may be comprised within system information, e.g., within a system information block (SIB).Alternatively, the indication may be received in RRC signaling from the gNB 404, e.g., in a RRC release message.

[0092] The UE 402 may receive the indication from the gNB 404.

[0093] A third operation 4.3 may comprise the UE 402 detecting a trigger condition associated with an RNA update (RNAU). In some examples, detecting the trigger condition comprises at least one of: detecting expiry of a wait time; detecting that the first apparatus is outside a configured RNA; or detecting that barring applicable to an RNA update procedure is alleviated and there is a pending RNA update procedure.

[0094] A fourth operation 4.4 may comprise the UE 402 transmitting to the gNB 404 an RRC Resume Request. The RRC Resume Request may include at least one resume cause.

[0095] A fifth operation 4.5 may comprise the gNB 404 performing admission control to determine whether to accept or reject the RRC Resume Request. This may comprise, for example, taking current network load into account.

[0096] A sixth operation 4.6 may comprise the gNB 404 transmitting to the UE 402 a network response, for example an RRC Reject or RRC Release with suspend configuration with wait time, depending on the admission control procedure of the fifth operation 4.5.

[0097] A seventh operation 4.7 may comprise the UE 402 ignoring the wait time in accordance with the indication in the second operation 4.2 (or alternatively based on a preconfiguration of the UE 402). As indicated above, the UE 402 may ignore the wait time for any resume requests, predetermined type(s) of resume requests, such as those other than RNAU procedures, any access requests; or any establishment requests.

[0098] An eighth operation 4.8 may comprise the UE 402 triggering an RRC Resume procedure whilst ignoring the wait time. This may be triggered based on uplink data arrival and because the wait time is not running, or is running but is ignored, the RRC Resume procedure is initiated.

[0099] A ninth operation 4.9 may comprise the UE 402 and gNB 404 performing the RRC Resume procedure.

[0100] Further examples will now be described with reference to FIGs. 5 and 6.FIG. 5 is a flow diagram showing operations 500 that may be performed by one or more example embodiments. The operations 500 may be performed by hardware, software, firmware or a combination thereof. The operations 500 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories.

[0101] The operations 500 may, for example, be performed by a first apparatus, for example a UE. The first apparatus may be configured for at least one of MPS or MCS. The UE may be any of the UEs 120, 122 illustrated in FIG. 1 or the UE 402 illustrated in FIG. 4. The order of operations 500 is not necessarily indicative of their order of processing or performance.

[0102] A first operation 510 may comprise receiving, from a second apparatus, an indication to ignore a wait time included with an R.R.C reject or R.R.C release with suspend configuration.

[0103] A second operation 520 may comprise transmitting, to the second apparatus, a resume request.

[0104] A third operation 530 may comprise receiving, from the second apparatus, an R.R.C reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time.

[0105] A fourth operation 540 may comprise ignoring, based on the indication and on the first apparatus being configured for at least one of MPS or MCS, the wait time.

[0106] In some examples, the indication comprises at least one of: a configuration for ignoring the wait time; or an indication that the wait time is allowed to be ignored.

[0107] In some examples, the indication is received in broadcast signaling from the second apparatus. In some examples, the indication is comprised within system information, for example within a system information block, SIB.

[0108] In some examples, the indication is received in dedicated radio resource control, R.R.C, signaling from the second apparatus, for example, in an R.R.C release message.

[0109] In some examples, the at least one of MPS or MCS that the_first apparatus is configured for is indicated by an upper layer of the first apparatus, e.g., the NAS layer.In some examples, the wait time is a T302 time period.

[0110] In some examples, the wait time is ignored for: any resume requests; predetermined type(s) of resume requests; any access requests; or any establishment requests.

[0111] In some examples, the predetermined type(s) of resume requests comprise at least one of: resume requests for RIMA update procedure; resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated, MO, or mobile terminated, MT, access.

[0112] In some examples, the wait time is ignored for initiating a resume procedure with the second apparatus.

[0113] FIG. 6 is a flow diagram showing operations 600 that may be performed by one or more example embodiments. The operations 600 may be performed by hardware, software, firmware or a combination thereof. The operations 600 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories.

[0114] The operations 600 may, for example, be performed by a second apparatus, for example a network node. The network node may be any of the network nodes 110, 112 illustrated in FIG. 1, the gNB 202 illustrated in FIG. 2, or the gNB 404 illustrated in FIG. 4. The order of operations 600 is not necessarily indicative of their order of processing or performance.

[0115] A first operation 610 may comprise transmitting to a first apparatus configured for at least one of MPS or MCS, an indication to ignore a wait time associated with an RRC reject or RRC release with suspend configuration.

[0116] A second operation 620 may comprise receiving, from the first apparatus, a resume request.

[0117] A third operation 630 may comprise transmitting, to the first apparatus, an RRC reject or RRC release with suspend configuration, wherein the RRC reject or RRC release with suspend configuration includes a wait time.A fourth operation 640 may comprise receiving, from the first apparatus, initiation of a resume procedure.

[0118] In some examples, the indication comprises at least one of: a configuration associated with the wait time; or an indication that the wait time is allowed to be ignored.

[0119] In some examples, the indication is transmitted in broadcast signaling to the first apparatus. For example, the indication may be comprised within system information, e.g., within a system information block, SIB.

[0120] In some examples, the indication is transmitted in dedicated radio resource control, RRC, signaling to the first apparatus, e.g., in an RRC release message.

[0121] In some examples, the wait time is a T302 time period.

[0122] In some examples, the indication to ignore the wait time is for: any resume requests; predetermined type(s) of resume requests; any access requests; or any establishment requests.

[0123] In some examples, the predetermined type(s) of resume requests comprise at least one of: resume requests for RNA update procedure; resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access; resume requests for MCS priority access; resume requests for an emergency; or resume requests for mobile originated, MO, or mobile terminated, MT, access.

[0124] Example embodiments enable MPS and / or MCS -configured UEs to initiate resume procedures without the need to follow wait times.

[0125]

[0126] Fig. 7 shows, by way of example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and any of the embodiments thereof. In an example, the at least one memory and the instructions (e.g. a computer program code, software), are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and any of the embodiments thereof.A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used in this application, the term "circuitry" may refer to one or more or all of the following : (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0127] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[0128] The instructions 15 may be comprised in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random access memory, RAM, vs. read only memory, ROM).

[0129] For example, the apparatus 10 is a terminal device, such as the UE of earlier figures. As another example, the apparatus is comprised in such a terminal device, e.g. as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform at least the method of FIGs. 3 or 5 and / or any one or more of the embodiments described.

[0130] As another example, the apparatus 10 is a network node, such as a gNB of earlier figures. In another embodiment, the apparatus is comprised in such a network node, e.g. as achipset configured to control the network node. The apparatus 10 may be caused or configured to perform at least the method of FIG. 6 and / or any one or more of the embodiments described.

[0131] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity.

[0132] The apparatus 10 comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmitter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[0133] The apparatus 10 may comprise a user interface 18 comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 may be used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[0134] In an embodiment, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Means for performing method steps as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the embodiments thereof. As used herein the term "means" is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology "means for [performing A, B, C]", is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology "means for performing A, means for performing B, means for performing C" is to be interpreted to cover an apparatus in which there is only one meansfor performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

Claims

Claims1. A first apparatus, configured for at least one of Multimedia Priority Services, MPS, or Mission Critical Services, MCS, the first apparatus comprising:means for transmitting, to a second apparatus, a resume request;means for receiving, from the second apparatus, a radio resource control, R.R.C, reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; andmeans for ignoring the wait time.

2. The first apparatus of claim 1, whereinthe at least one of MPS or MCS that the first apparatus is configured for is indicated by an upper layer of the first apparatus.

3. The first apparatus of claim 1 or claim 2, whereinthe wait time is a T302 time period.

4. The first apparatus of any preceding claim, whereinthe means for ignoring the wait time is configured based at least in part on:a preconfiguration of the first apparatus; oran indication or allowance from the second apparatus.

5. The first apparatus of any preceding claim, whereinthe means for ignoring the wait time is configured to ignore the wait time for at least one of:any resume requests;predetermined type(s) of resume requests;any access requests; orany establishment requests.

6. The first apparatus of claim 5, whereinthe predetermined type(s) of resume requests comprise at least one of:resume requests for RIMA update procedure;resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access;resume requests for MCS priority access;resume requests for an emergency; orresume requests for mobile originated, MO, or mobile terminated, MT, access.

7. The first apparatus of any preceding claim, whereinthe means for ignoring the wait time is configured to ignore the wait time for initiating a resume procedure with the second apparatus.

8. The apparatus of any preceding claim, whereinthe means for ignoring the wait time is configured to ignore the wait time based on the first apparatus being configured for at least one of MPS or MCS.

9. A method of a first apparatus, comprising:transmitting, to a second apparatus, a resume request;receiving, from the second apparatus, a radio resource control, R.R.C, reject or R.R.C release with suspend configuration, wherein the R.R.C reject or R.R.C release with suspend configuration includes a wait time; andignoring the wait time.

10. The method of claim 9, whereinthe at least one of MPS or MCS that the first apparatus is configured for is indicated by an upper layer of the first apparatus.

11. The method of claim 9 or claim 10, whereinthe wait time is a T302 time period.

12. The method of any of claims 9 to 11, whereinignoring the wait time is based at least in part on:a preconfiguration of the first apparatus; oran indication or allowance from the second apparatus.

13. The method of any of claims 9 to 12, whereinthe wait time is ignored for at least one of:any resume requests;predetermined type(s) of resume requests;any access requests; orany establishment requests.

14. The method of claim 13, whereinthe predetermined type(s) of resume requests comprise at least one of: resume requests for RIMA update procedure;resume requests for procedures other than an RNA update procedure; resume requests for MPS priority access;resume requests for MCS priority access;resume requests for an emergency; orresume requests for mobile originated, MO, or mobile terminated, MT, access.

15. The method of any of claims 9 to 14, whereinthe wait time is ignored for initiating a resume procedure with the second apparatus.

Images