TECHNICAL FIELD

Embodiments herein relate to a user equipment (UE) and method performed therein for communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, especially handling an emergency service, for the UE in a wireless communication network. BACKGROUND

In a typical wireless communication network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (STA) and/or wireless device, communicate via a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a “NodeB” (NB) or “eNodeB” (eNB),

“gNodeB” (gNB). A service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the UE within range of the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High Speed Packet Access (HSPA) for UEs. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for third generation networks, and investigate enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. This type of connection is sometimes referred to as a backhaul connection. The RNCs and BSCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3 ^rd Generation Partnership Project (3GPP) and also a 5 ^th generation network and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (6G) network. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E- UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs. In general, in E-UTRAN/LTE the functions of an RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that, the E- UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface. EPS is the Evolved 3GPP Packet Switched Domain. New radio (NR) is the new radio access technology being standardized in 3GPP.

In NR there is a feature for providing Public Warning System (PWS)-indications to UEs which can be used to provide warning-messages to users. For example, if there is an earthquake the network can indicate this to the UEs by broadcasting PWS-messages in system information (SI).

For example, the PWS-messages of the type Earthquake and Tsunami Warning System (ETWS) are broadcasted in the system information such as system information block six (SIB6) together with SIB7, and PWS-messages of the type Commercial Mobile Alert Service (CMAS) are broadcasted in SIB8. These system information block (SIB) types are defined in the NR radio resource control (RRC) specification, 3GPP TS 38.331 v.15.2.0.

In NR, a UE in IDLE/INACTIVE mode classifies cells into different categories. These categories are defined as below, which is an excerpt from 3GPP TS 38.304 v 15.6.0.

A UE may consider a cell to be an "acceptable cell" in case the UE may obtain limited service in this cell, where limited service comprises emergency calls and to receive ETWS and CMAS notifications. Cell Categories

The cells are categorized according to which services they offer: acceptable cell:

An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and receive ETWS and CMAS notifications). Such a cell fulfils the following requirements, which is a minimum set of requirements to initiate an emergency call and to receive ETWS and CMAS notification in an NR network:

The cell is not barred, see clause 5.3.1 ;

The cell selection criteria are fulfilled, see clause 5.2.3.2. suitable cell:

A cell is considered as suitable if the following conditions are fulfilled:

The cell is part of either the selected public land mobile network (PLMN) or the registered PLMN or PLMN of the Equivalent PLMN list;

The cell selection criteria are fulfilled, see clause 5.2.3.2.

According to the latest information provided by non-access stratum (NAS):

The cell is not barred, see clause 5.3.1;

The cell is part of at least one tracking area (TA) that is not part of the list of "Forbidden Tracking Areas" (TS 22.261 [12]), which belongs to a PLMN that fulfils the first bullet above. barred cell:

A cell is barred if it is so indicated in the system information, as specified in TS 38.331 [3] reserved cell:

A cell is reserved if it is so indicated in system information, as specified in TS 38.331 [3] Following exception to these definitions are applicable for UEs: if a UE has an ongoing emergency call, all acceptable cells of that PLMN are treated as suitable for the duration of the emergency call. camped on a cell that belongs to a registration area that is forbidden for regional provision of service; a cell that belongs to a registration area that is forbidden for regional provision service (TS 23.122 [9], TS 24.501 [14]) is suitable but provides only limited service. “

In release (Rel)-16 of NR a feature called Non-Public Networks (NPN) is added which allows, for example, non-Public Land Mobile Networks (PLMN) to deploy NR- networks. One type of NPN is a Standalone NPN (SNPN), which is intended to not have any necessary relation to a PLMN network. This is in contrast to a Public Network Integrated Non-Public Network (PNI NPN), that is realized by associating, e.g., a specific network slice as an NPN. The SNPN uses as identification a Network ID, consisting of the same portions as the ID for a PLMN, i.e. the mobile country code (MCC) and a Mobile Network Code (MNC). In addition to the MCC and the MNC, the SNPN also has a Network ID (NID).

In many aspects the SNPN functions in a similar way as the PLMN. A UE need to have credentials and be authorized to use it, in a similar way as for a PLMN, although an SNPN is usually intended for a more specific use than the PLMN. It may also be geographically less distributed than the PLMN and has fewer UE’s that can access the network. Examples of places where an SNPN can be deployed are, e.g., as a company network, in a factory, in a port, in a shopping mall, at a race track, in exhibition centers or stadium.

The specifications for SNPN’s, in its first versions do not provide full support of all functionalities that are currently present in a PLMN. For example, the SNPNs are not required to support ETWS and CMAS indications, nor emergency calls. There are most likely going to be SNPN deployments where both these warning messages as well as emergency calls will be supported, but in some situations it may not be.

3GPP has specified that to be able to access an SNPN, a UE may need to enter or be configured to a specific “access mode” referred to as SNPN access mode. In this SNPN access mode, the UE will not look for or be able to select a PLMN, but it will only search for SNPNs and make an SNPN selection.

The definition is from TS 23.501 version 16.0.0: “SNPN access mode: A UE operating in SNPN access mode only selects stand-alone Non-Public Networks over Uu.” Uu is the air interface. While this is the definition of SNPN access mode there has not been any earlier need for or definition of PLMN access mode, and no such definition is added in current specifications either. In the below description however, the term “PLMN access mode” will be used for a UE that is not in SNPN access mode.

If the UE has credentials to register to an SNPN the UE may access the SNPN services. A UE which supports SNPNs may be in an SNPN Access Mode wherein it aims to use SNPN-cells. Alternatively, the UE may be in an PLMN Access Mode wherein the UE aims to use PLMN-cells. The UE is either in the SNPN Access Mode or the PLMN Access Mode. SUMMARY

A UE which is in an SNPN Access Mode may end up selecting an SNPN cell where it is not allowed to register, i.e., the UE will end up in a limited service state.

For example, the UE may have access to an SNPN1 , but does currently not find any cell associated with SNPN1 , and the UE may then select a cell which is associated with an SNPN2 in which the UE is not allowed to register. The UE would in that case consider the cell associated with the SNPN2 to be an "acceptable cell". An acceptable cell in a PLMN is usually a cell in which you would be able to camp in limited service state, hear warnings and make emergency calls. The SNPN2 cell may however not offer such broadcast and may not allow emergency calls. This would result in that the UE, staying in an acceptable cell cannot basically get any service at all, not even emergency and warning service. There is currently in the specifications no particular trigger or description for how a UE should be programmed to act or behave in such a scenario.

An object of embodiments herein is to provide a mechanism for improving, in an efficient manner, performance of the wireless communication network e.g. enabling the UE to receive messages related to an emergency.

According to an aspect the object is achieved by providing a method performed by a UE for handling communication in a wireless communication network. The UE determines that one or more conditions are fulfilled when being in a first type of access mode, wherein the one or more conditions are related to support of providing an emergency service or not. Upon fulfillment of the one or more conditions, the UE performs a cell selection in a second type of access mode, and/or camps on a cell providing the emergency service , wherein type of access mode is defined based on a privacy structure. Thus, the UE determines that one or more conditions are fulfilled when being in a first type of access mode, for example, SNPN access mode, and upon the one or more conditions being fulfilled the UE performs a cell selection in a second type of access mode, for example, PLMN access mode. As stated, the types of access modes are defined based on privacy policy, for example, whether allowed to access a public network or a non-public network. The one or more conditions are related to an emergency service e.g. supporting PWS indication or emergency messages such as ETWS and CMAS notifications.

According to yet another aspect the object is achieved by providing a UE configured to perform the methods herein. Thus, embodiments herein provide a UE, for handling communication in a wireless communication network. The UE is configured to determine that one or more conditions are fulfilled when being in a first type of access mode, wherein the one or more conditions are related to support of providing an emergency service or not. The UE is configured, upon fulfillment of the one or more conditions, to perform a cell selection in a second type of access mode, and/or camp on a cell providing the emergency service , wherein type of access mode is defined based on a privacy structure.

It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods above, as performed by the UE. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the methods above, as performed by the UE.

According to one aspect, when a UE is in the first type of access mode and cannot find any networks for which registration is possible, a UE is programmed to switch to the second type of access mode and make a network selection in the second type of access mode instead. The UE may leave the first type of access mode as soon as it would leave coverage of any network for which it is allowed registration. Once in the second type of access mode, the UE can start camping on a cell that broadcast support for a second type of network and that has set indications such that emergency calls are allowed also for UE’s that are not registered in the second type of network.

Once the UE has left the first type of access mode and entered the second type of access mode, the UE would thus stop looking for cells or signals of cells of the first type of access mode such as SNPNs.

According to another aspect the UE that has left the first type of access mode and entered the second type of access mode, for example triggered by that the UE does not find any SNPN for which it is allowed to register, shall, also in the second type of access mode, continue to monitor for SNPNs, such that, when the UE moves into coverage of an SNPN that the UE is allowed to register to, shall move to that SNPN instead of camping in a cell that belongs to a PLMN the UE is not allowed to register in, but where it can make emergency calls.

Thus, the UE changes access mode from the first type of access mode to the second type of access mode if the UE would end up in a cell of a first type which is acceptable but wherein the UE cannot receive PWS or initiate emergency calls, i.e. a cell not supporting an emergency service. Embodiments herein thus lead to that the UE can receive warning messages such as PWS and set up emergency calls instead of the UE ending up selecting a cell which is acceptable but does not provide PWS or emergency call service. Further, the UE may be programmed to, even in the second type of access mode, if it is an first type capable UE, continue to search for first type of cells when it is camping in an acceptable cell in a second type of cell.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

Fig. 1 is a schematic overview depicting a wireless communications network according to embodiments herein;

Fig. 2A is a is a combined signalling scheme and flowchart according to some embodiments herein;

Fig. 2B is a schematic flowchart depicting a method performed by a UE according to embodiments herein;

Fig. 2C is a schematic overview depicting a wireless communications network according to embodiments herein;

Fig. 2D are schematic flowcharts depicting methods performed by a UE node according to embodiments herein;

Fig. 3 is a block diagram depicting UEs according to embodiments herein;

Fig. 4 is a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

Fig. 5 is a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

Fig. 6 is methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

Fig. 7 is methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

Fig. 8 is methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

Fig. 9 is methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments. DETAILED DESCRIPTION

Embodiments herein are described within the context of 3GPP NR radio technology, e.g. 3GPP TS 38.300 v.16.0.0. It is understood, that the embodiments herein are equally applicable to wireless access networks and UEs implementing other access technologies and standards. NR is used as an example technology in the embodiments herein, and using NR in the description therefore is particularly useful for understanding the problem and solutions solving the problem. In particular, the embodiments herein are applicable also to 3GPP LTE, or 3GPP LTE and NR integration, also denoted as non- standalone NR.

Embodiments herein relate to wireless communication networks in general. Fig. 1 is a schematic overview depicting a wireless communication network 1. The wireless communication network 1 comprises one or more communication networks comprising one or more RANs e.g. a first RAN (RAN1), connected to one or more CNs. The wireless communication network 1 may use one or more technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, Wdeband Code Division Multiple Access (WCDMA), Global System for Mobile communications/Enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are applicable also in further development of the existing communication systems such as e.g. 3G and LTE.

In the wireless communication network 1, one or more wireless devices, for example a UE 10 such as a mobile station, a non-access point (non-AP) station (STA), a STA, and/or a wireless terminal, are connected via the one or more RANs, to e.g. the one or more CNs. It should be understood by those skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communication terminal, communication equipment, Machine Type Communication (MTC) device, internet of things (loT) capable device, Device to Device (D2D) terminal, or wireless device e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or any device communicating within a cell or service area.

The wireless communication network 1 comprises a radio network node 12. The radio network node 12 is exemplified herein as a first radio network node or a first RAN node providing radio coverage over a geographical area, a first service area 11 , of a first radio access technology (RAT), such as NR, LTE, UMTS, W-Fi or similar. The radio first network node 12 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, a gNodeB, an evolved Node B (eNB, eNodeB), a base transceiver station, Access Point Base Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a UE 10 within the service area served by the first radio network node 12 depending e.g. on the radio access technology and terminology used and may be denoted as a primary radio network node. The first radio network node 12 may alternatively be denoted as a serving radio network node providing a cell of a second access mode for the UE 10. The first cell 11 may be a PLMN cell.

The wireless communication network 1 comprises a second radio network node 13. The second radio network node 13 is exemplified herein as a second RAN node providing radio coverage over a geographical area, a second service area 14 or cell, of a second RAT, such as NR, LTE, UMTS, Wi-Fi or similar. The second radio network node 13 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, a gNodeB, an evolved Node B (eNB, eNodeB), a base transceiver station, Access Point Base Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a UE 10 within the service area served by the second radio network node 13 depending e.g. on the radio access technology and terminology used. The radio network node 13 may alternatively be denoted as a serving radio network node providing a second cell of a first access mode e.g. restricted access for UEs. The second cell may be a SNPN cell. It should herein be noted that a same radio network node may provide both the first and second cell. It should further be noted that a service area or cell may be denoted as beam, beam group or similar to define an area of radio coverage. The first RAT may the same or different RAT as the second RAT but cells and/or RAT may differ in the access rights i.e. differs whether being a public or a non-public cell.

It will herein be discussed how the UE 10 switches access modes between a first type of access mode such as a first access mode, for example, an SNPN access mode, and a second type of access mode such as a second access mode, for example, PLMN access mode. If the UE 10 selects or changes from, for example, SNPN access mode to, for example, PLMN access mode, the PLMN access mode may be referred to as a target access mode, and SNPN access mode may be referred to as a source access mode. Fig. 2A is a schematic combined signaling scheme and flowchart depicting embodiments herein.

Action 201. The UE 10 may monitor for a cell in the first type of access mode e.g. the first access mode, for e.g. an SNPN cell, or the UE 10 may be connected to a cell in the first access mode.

Action 202. The UE 10 determines that one or more conditions are fulfilled when being in the first type of access mode. The one or more conditions may comprise one or more of the following: a current connected cell does not support or has not enabled an emergency service; a target cell does support or has enabled an emergency service; and/or the UE 10 is capable, enabled and/or supports an emergency service. The UE 10 may determine this, for example, by reading indications of such support in broadcast information such as SIBs and/or within the UE 10. For example, the UE 10 may determine that no cell of the first access mode is present or may provide support for emergency service, i.e. no cell supporting emergency service is present but a target cell of a second type is present supporting the emergency service.

Action 203. The UE 10, upon fulfillment of the one or more conditions, performs a cell selection or camps on a cell in the second type of access mode. Thus, the UE 10 may change access mode, for example, switches to the second type of access mode when being in the first type of access mode and the one or more conditions are fulfilled. The type of access mode is defined based on privacy structure e.g. whether allowed to access a public network or a non-public network. The one or more conditions are related to emergency service e.g. capability of the cell to provide the emergency service learned through detection of signals and/or cells. The UE 10 thus determines that one or more conditions are fulfilled and the UE 10 performs a cell selection in the second type of access mode. Thus, the UE supports the emergency service which means the UE 10 is able to receive PWS or emergency messages, for example, receive warning messages.

Action 204. The UE 10 may further keep on monitoring cell/s in the first type pf access mode in case another cell with e.g. another emergency capability is detected.

The method actions performed by the UE 10 for handling communication in the wireless communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 2B. Optional actions are marked with dashed boxes and the order of performing the actions may be in any suitable order. Action 205. The UE 10 may monitor for a cell in the first type of access mode, and/or the UE 10 is connected to a first cell in the first access mode.

Action 206. The UE 10 determines that one or more conditions are fulfilled when being in the first type of access mode, wherein the one or more conditions are related to support of providing an emergency service or not. The one or more conditions may comprise one or more of the following: that a current connected cell does not support or has not enabled an emergency service; that a target cell does support or has enabled an emergency service; and/or that the UE is capable, enabled and/or supports emergency service. The UE 10 may read indications in broadcast information and/or within the UE and based on the read indications determine that the one or more conditions are fulfilled. Thus, the UE 10 may determine that the one or more conditions are fulfilled by reading indications in broadcast information and/or from within the UE.

Action 207. Upon fulfillment of the one or more conditions, the UE 10 performs a cell selection in the second type of access mode, and/or camps on a cell providing the emergency service, such as a cell of the second type, wherein type of access mode (and type of cell) is defined based on a privacy structure. For example, the first type of access mode allows access to a non-public network and the second type of access mode (or cell) allows access to a public network. Thus, the privacy structure may be defined as whether to allow access to a public network or a non-public network. According to embodiments herein, the UE 10 may switch to the second type of access mode when being in the first type of access mode and the one or more conditions are fulfilled. As another example the UE 10 may camp on the cell providing the emergency service but remaining in the first type of access mode.

Action 208. The UE 10 may keep on monitoring cell or cells in the first type of access mode in case another cell with an emergency capability is detected.

The following is the definition of and description wherein the UE 10 is an SNPN enabled UE and how the UE 10 would behave in the SNPN access mode: (Copy from TS 23.501 v.16.0.0)

5.30.2.3 UE configuration and subscription aspects

An SNPN-enabled UE is configured with a subscriber identifier such as a Subscription Permanent identifier (SUPI) and credentials for each subscribed SNPN identified by the combination of a PLMN ID and a NID.

A subscriber of an SNPN is either: identified by a SUPI containing a network-specific identifier that takes the form of a Network Access Identifier (NAI) using the NAI RFC 7542 [20] based user identification as defined in TS 23.003 [19] clause 28.7.2. The realm part of the NAI may include the NID of the SNPN; or identified by a SUPI containing an international mobile subscriber identity

(I MSI).

An SNPN enabled UE supports the SNPN access mode. When the UE is set to operate in the SNPN access mode the UE only selects and registers with SNPNs over Uu interface as described in clause 5.30.2.4.

Emergency services are not supported in SNPN access mode.

NOTE 1: Voice support with emergency services in SNPN access mode is not specified in this release.

If a UE is not set to operate in the SNPN access mode, even if it is SNPN-enabled, the UE does not select and register with SNPNs. A UE not set to operate in the SNPN access mode performs PLMN selection procedures as defined in clause 4.4 of TS 23.122 [17] For a UE capable of simultaneously connecting to an SNPN and a PLMN, the setting for operation in the SNPN access mode is applied only to the Uu interface for connection to the SNPN. Annex D.4 provides more details.

NOTE 2: Details of activation and deactivation of SNPN access mode are up to UE implementation.

For network selection, TS 23.122 v.16.0.0 specifies:

“If there were one or more SNPNs which were available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the mobile equipment (ME), i.e. a mobile station without a Subscriber Identity Module (SIM), but an location registration (LR) failure made registration on those SNPNs unsuccessful, the mobile station (MS), i.e. UE, selects one of those SNPNs again and enters a limited service state.”

The description of limited service state is:

3.5 No suitable cell (limited service state)

There are a number of situations in which the UE (also referred to as MS) is unable to obtain normal service from a PLMN or SNPN. These include: a) Failure to find a suitable cell of the selected PLMN or of the selected

SNPN; b) No SIM in the MS or the "list of subscriber data" with no valid entry; c) A "PLMN not allowed" response in case of PLMN or a "Temporarily not authorized for this SNPN" or "Permanently not authorized for this SNPN" response in case of SNPN when an LR is received; d) An "illegal MS" or "illegal ME" response when an LR is received (Any SIM or the corresponding entry of the "list of subscriber data" in the ME is then considered "invalid"); e) An "IMSI unknown in home location register (HLR)" response when an LR is received (Any SIM in the ME is then considered "invalid" for non-GPRS services); f) A "GPRS services not allowed" response when an LR of a GPRS MS attached to GPRS services only is received, the cell selection state of GPRS MSs attached to GPRS and non-GPRS depends on the outcome of the location updating), or an "EPS services not allowed" response is received when an EPS attach, tracking area update or service request is performed, or a "5GS services not allowed" response is received when a registration or service request is performed; g) Power saving mode (PSM) is activated (see 3GPP TS 23.682 [27A]); or h) Mobile initiated connection only (MICO) mode is activated (see 3GPP TS 23.501 [62] and 3GPP TS 23.502 [63]). i) MS supporting closed access group (CAG) is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and none of the CAG-ID(s) of the CAG cell are present in the "Allowed CAG list" associated with that PLMN in the "CAG information list"; and j) MS supporting CAG is camped on a non-CAG cell belonging to a PLMN, the non-CAG cell is not manually selected by the user and the UE is configured with "indication that the MS is only allowed to access 5GS via CAG cells" for that PLMN in the "CAG information list".

Editor's note: For further study (FFS) whether there is any requirement for MS not supporting CAG, but supporting this release of the specification can camp on a CAG cell when no other non-CAG cells are available and the CAG cell is available for emergency services. Details of camping on such a CAG cell and availability of the CAG-cell for emergency services is subject to RAN2 agreement. In automatic PLMN selection mode, items a, c and f would normally cause a new PLMN selection, but even in this case, the situation may arise when no PLMNs are available and allowable for use.

In automatic SNPN selection mode, items a, c, d, and f would normally cause a new SNPN selection if there are two or more entries in the "list of subscriber data", but even in this case, the situation may arise when no SNPNs are available and allowable for use.

For the items a to f, if the MS does not operate in SNPN access mode, the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls or access to Restricted local operator services (RLOS) can be made if necessary, with the exception that an MS operating in narrowband (NB)-S1 mode, shall never attempt to make emergency calls or to access RLOS. When in the limited service state with a valid SIM, the MS shall search for available and allowable PLMNs in the manner described in subclause 4.4.3.1 and when indicated in the SIM also as described in subclause 4.4.3.4. For an MS that is not in eCall only mode, with the exception of performing GPRS attach or EPS attach for emergency bearer services, performing registration for emergency services, or performing EPS attach for access to RLOS, no LR requests are made until a valid SIM is present and either a suitable cell is found or a manual network reselection is performed. For an MS in eCall only mode, no LR requests are made except for performing EPS attach for emergency bearer services or registration for emergency services. When performing GPRS attach or EPS attach for emergency bearer services, registration for emergency services, or performing EPS attach for access to RLOS, the PLMN of the current serving cell is considered as the selected PLMN for the duration the MS is attached for emergency bearer services, registered for emergency services, or attached for access to RLOS. In the limited service state the presence of the MS need not be known to the PLMN on whose cell it has camped.

For the items a, c, d and f, if the MS operates in SNPN access mode and the UE has a valid entry in the "list of subscriber data", the MS shall search for available and allowable SNPNs in the manner described in subclause 4.9.3.1. For the item b, if the MS operates in SNPN access mode, the MS attempts to camp on an acceptable cell. When in the limited service state, no LR requests are made until a valid entry of the "list of subscriber data" is present and either a suitable cell is found or a manual network reselection is performed. In the limited service state the presence of the MS need not be known to the SNPN on whose cell it has camped. There are also other conditions under which only emergency calls or access to RLOS may be made. These are shown in table 2 in clause 5. Proximity services (ProSe) direct communication and ProSe direct discovery for public safety use can be initiated if necessary (see 3GPP TS 24.334 [51]) when in the limited service state due to items a) or c) or f). Vehicle to everything (V2X) communication over PC5 interface can be initiated if necessary, see 3GPP TS 24.386 [59], when in the limited service state due to items a) or c) or f).

According to embodiments herein the UE 10, which is in the first type of access mode, for example, an SNPN access mode, and selects, or is about to select, a cell which would be considered as an "acceptable cell" may switch access mode from the SNPN access mode to the PLMN access mode. This would allow the UE 10 to select a cell of a PLMN, where PWS and emergency calls are expected to be supported.

Thus, the UE 10 may when it has switched access mode to PLMN access mode, select a PLMN cell.

If the UE 10 is SNPN capable/enabled and the UE 10 currently is in PLMN access mode, for example since it has earlier changed access mode as above, and if the UE 10 detects that there is an SNPN cell available which the UE has access to, and hence could consider to be a suitable cell, the UE 10 may switch back the access mode to SNPN access mode thus, switching from PLMN access mode to SNPN access mode.

The UE 10 may when it has switched back to SNPN access mode select an SNPN cell and hence be able to select a cell which for that UE would be considered suitable.

However, if the UE 10, when in the PLMN access mode detects an SNPN cell which the UE 10 does not have access to, for example, a third SNPN which the UE also does not have access to, the UE 10 may refrain from switching to SNPN access mode.

The UE 10 may in the PLMN access mode search for SNPNs that it is allowed to register on. This can be made conditional such that the UE 10 in the PLMN access mode that is registered to a PLMN to receive normal service, may not look for an SNPN that it is allowed to register on, whereas the UE 10 in the PLMN access mode that is not registered to the PLMN for normal service, but it is only allowed for limited services (emergency calls, listen to PWS) may include in a search for a network to register for normal services, a search for SNPNs.

Referring to Fig. 2C illustrating four different cells, wherein cells 1 and 2 denoted as 110 and 111 belongs to a respective PLMN in which the UE 10 can listen to PWS and be able to make emergency calls. The UE 10 is SNPN capable and can access for normal services in cell 105, for SNPN1. When the UE 10 leaves cell 105, it may enter the area covered by cell 106, belonging to SNPN2, wherein the UE 10 is not allowed to register for normal services. Cell 106 for SNPN2 is not broadcasting or supporting PWS or emergency calls.

Two positions are marked in the Fig. 2B, a first position 120 in the coverage of PLMN1 and SNPN1 and position 140 in the coverage of PLMN1 and SNPN2, but outside the coverage of SNPN 1.

According to embodiments herein, when the UE 10 is in the first position 120 in the SNPN access mode, it may select SNPN1 if it can get normal service from this SNPN. If the UE 10 is in the second position 120 in the PLMN access mode, the UE 10 selects PLMN1.

When the UE 10 is in the second position 140 in the SNPN access mode, the UE 10 may select PLMN1 to camp on a PLMN cell to be able to receive PWS and make emergency calls. There are two alternative solutions on how to reach the above results.

The UE 10 may in the SNPN access mode switch access mode to the PLMN access mode when the UE 10 detects that there are no services in an SNPN it is camping on in limited service state (see below).

The UE 10 may remain in SNPN access mode, but may, instead of camping only in SNPNs, if there is no SNPN for which the UE 10 could register and get normal service, instead, in the SNPN access mode, camp on a PLMN in a limited service state.

The result of these two different embodiments would be that the UE 10, once the UE cannot register to an SNPN, would enter a limited service state and camp on a PLMN. The alternatives provide different functionality in the different access modes however. Embodiments herein may solve the problem by allowing the UE 10 to remain in the SNPN access mode. Embodiments herein may further solve the problem by allowing the UE to search for SNPNs when being in the PLMN access mode.

Two flow-charts in Fig. 2D are comparable:

On the left side of Fig. 2D, the UE 10 leaves SNPN access mode i.e. the first type of access mode. In action 210, the UE 10, e.g., due to mobility, or otherwise decreasing signal strength, may leave coverage of registered SNPN in SNPN access mode. In action 215, the UE 10 detects or determines that there is no other SNPN that allows certain services from camping in a limited service state, i.e., PWS and/or emergency is not supported or no other SNPN provides PWS and/or emergency service. In action 220 the UE 10 is then configured to search for other cells i.e. also PLMN cells and read information about if such service is supported. Thus, the UE 10 may find a PLMN cell that supports PWS and/or emergency calls. In action 225, when the UE 10 finds a PLMN cell that supports, e.g., PWS, the UE 10 may enter PLMN access mode (or actually, leave SNPN access mode) and camp on a PLMN cell in limited service state. The UE 10 may anyway continue to look for SNPN’s, since its selected/main service may be the SNPN service, i.e. the UE 10 may continue to search for SNPNs. In action 230, the UE 10 may, when returning to coverage, make a new network selection to the desired SNPN service, for example, select SNPN and register for normal service.

On the right side of Fig. 2D, the UE 10 remains in SNPN access mode. In action 250, the UE 10, e.g., due to mobility, or otherwise decreasing signal strength, may leave coverage of registered SNPN in SNPN access mode. In action 255, the UE 10 detects or determines that there is no other SNPN that allows certain services from camping in a limited service state, i.e., PWS and/or emergency is not supported or no other SNPN provides PWS and/or emergency service. In action 260 the UE 10 is then configured to search for other cells i.e. also PLMN cells and read information about if such service is supported. Thus, the UE 10 may find a PLMN cell that supports PWS and/or emergency calls. In action 265, when the UE 10 finds a PLMN cell that supports, e.g., PWS, the UE 10 may remain in the SNPN state, but that this state allows camping in limited service state also on cells that are not SNPN cells such as PLMNs and camp on a PLMN cell in the limited service state. In action 270, the UE 10 may, when returning to coverage, make a new network selection to the desired SNPN service, for example, select SNPN and register for normal service.

Even though the above mentions that the UE 10 may find a PLMN cell that supports, e.g., PWS or emergency (see actions 220 and 260), prior to switching to, or remaining in the referred access states (see actions 225 and 265), it should be recognized that it is equally possible that the switching of states happens prior to that UE 10 detects that certain cells are found, i.e., the order of the flow diagram above may be different and action 260 may come after action 265 (and action 220 may come after action 225).

In the following, it is herein addressed the solution that is based on that, when moving out of coverage from an SNPN where UE can register to an SNPN where UE cannot register for normal service, that this trigger a switch to no longer remain in SNPN access mode. In the above it has been described methods for how to switch access mode between SNPN access more and PLMN access mode depending on whether or not the cell that the UE selects, or is about to select, an SNPN cell which would be considered as acceptable.

Below it will be described further conditions which the UE 10 may apply when determine whether to switch access mode to an access mode that is not restricted e.g. allowed to receive warning messages.

The UE 10 may determine whether the UE 10 is PWS capable and/or enabled or interested in PWS when determining whether to change access mode as described above. If the UE 10 is not capable of, not enabled, or not interested in PWS, the UE 10 may not be meaningful to change access mode to allow to select a PLMN cell which anyway would (only) be considered as acceptable, since on acceptable cells the UE 10 is only able to receive PWS and perform emergency calls and since the UE 10 is not capable/enabled/interested of/in PWS, it may not be meaningful to select a PLMN cell instead of an SNPN cell.

If the UE 10 is not PWS capable it will not be able to, or it may not be meaningful to, receive PWS messages. Such examples can be if, e.g., a UE is a sensor device for example, or the UE is implemented as part of anything that is not able to neither display nor interpret such warning messages.

The UE 10 may determine whether the cell in the source access mode has PWS enabled or is supported. If the UE 10 determines that PWS is enabled or the cell is capable of PWS, it may refrain from changing access mode, while if the cell does not have PWS enabled or the cell is not capable of PWS, the UE 10 may perform the access mode change. This ensures that the UE 10 does not change access mode unless it would be meaningful from a PWS availability point of view. An example of this is /7SNPN2 in Fig. 2C above, do support PWS, the UE 10 is in position 140 and is mainly interested in PWS, then there is no need to switch to PLMN access mode, or attempt to camp on a PLMN in limited service state

The UE 10 may determine whether the cell in the target access mode has PWS enabled or is supported. If the UE 10 determines that PWS is not enabled or the cell is not capable of PWS, it may refrain from changing access mode, while if the cell has PWS enabled or the cell is capable of PWS the UE 10 may perform the access mode change. This ensures that the UE 10 does not change access mode unless it would be meaningful from a PWS availability point of view. The UE 10 may re-evaluate whether to change access mode when the target access mode has a new candidate cell available. For example, if the UE 10 moves, a new cell may be the cell which the UE 10 would select if it changes access mode, and in this case the UE may re-evaluate whether access mode should be changed.

In the above it has been described how the UE 10 determines whether the UE 10 and/or the cells are capable of PWS when determining whether to change access mode. The UE 10 may apply the same behavior as described here but when determining whether the UE 10 and/or the cells are capable of emergency service.

The UE 10 may determine whether to change access mode based on whether there is a cell available in that other access mode. For example, if the UE 10 determines that the UE 10 selects, or is about to select, an SNPN cell which is only going to be considered to be "acceptable", and based on the above the UE 10 should change access mode to PLMN access mode, but if there is no cell available in PLMN access mode, the UE 10 may refrain from changing access mode. While if there indeed is a PLMN cell available, the UE 10 may change access mode.

In an alternative embodiment, the UE 10 remains in the same SNPN access mode, but in this access mode, camping on PLMN cells in limited service state is still possible.

Fig. 3 is a block diagram depicting the UE 10, in two embodiments, for handling communication in the wireless communication network 1 according to embodiments herein.

The UE 10 may comprise processing circuitry 301, e.g. one or more processors, configured to perform the methods herein.

The UE 10 may comprise a determining unit 302. The UE 10, the processing circuitry 301 and/or the determining unit 302 is configured to determine that one or more conditions are fulfilled when being in the first type of access mode. The one or more conditions are related to support of providing an emergency service or not. The one or more conditions may comprise one or more of the following: fulfilled in case of the current connected cell does not support or has not enabled an emergency service; fulfilled in case the target cell does support or has enabled an emergency service; and/or fulfilled in case the UE is capable, enabled and/or supports emergency service. Thus, the one or more conditions may comprise one or more of the following: that a current connected cell does not support or has not enabled an emergency service; that a target cell does support or has enabled an emergency service; and/or that the UE is capable, enabled and/or supports emergency service. The UE 10, the processing circuitry 301 and/or the determining unit 302 may determine this for example by reading indications of such support in the broadcast information and/or within the UE. Thus, the UE 10, the processing circuitry 301 and/or the determining unit 302 may be configured to determine that the one or more conditions are fulfilled by reading indications in broadcast information and/or within the UE. The UE may be connected to a first cell in the first access mode when determining that the one or more conditions are fulfilled.

The UE 10 may comprise a changing unit 303. The UE 10, the processing circuitry 301 and/or the changing unit 303 is configured to upon fulfillment of the one or more conditions, perform the cell selection in the second type of access mode, and/or camp on the cell providing the emergency service, wherein type of access mode is defined based on a privacy structure. For example, perform the cell selection or to camp on the cell in the second type of access mode, e.g. second access mode. The UE 10, the processing circuitry 301 and/or the changing unit 303 may be configured to switch to the second type of access mode when being in the first type of access mode and the one or more conditions are fulfilled. The UE 10, the processing circuitry 301 and/or the changing unit 303 may be configured to camp on the cell providing the emergency service by remaining in the first type of access mode. As stated, the type of access mode is defined based on the privacy structure e.g. whether allowed to access a public network or a non public network. Thus, the privacy structure may be defined as whether to allow access to a public network or a non-public network. The one or more condition are related to emergency service e.g. capability of the cell to provide the emergency service learned through detection of signals and/or cells

The UE 10 may comprise a receiving unit 304, e.g. a receiver or transceiver. The UE 10, the processing circuitry 301 and/or the receiving unit 304 may be configured to receive one or more emergency messages and/or warning messages. The UE 10, the processing circuitry 301 and/or the receiving unit 304 may be configured to monitor for a cell in the first type of access mode e.g. the first access mode, for e.g. an SNPN cell, or a cell in the second type of access mode. The UE 10, the processing circuitry 301 and/or the receiving unit 304 may be configured to keep on monitoring cell/s in the first type pf access mode in case another cell with e.g. an or another emergency capability is detected.

The UE 10 further comprises a memory 305. The memory comprises one or more units to be used to store data on, such as indications, access modes, emergency messages, cell capability, UE capability, applications to perform the methods disclosed herein when being executed, and similar. Thus, the UE 10 may comprise the processing circuitry and the memory, said memory comprising instructions executable by said processing circuitry whereby said UE 10 is operative to perform the methods herein. The UE may comprise a communication interface 308 comprising e.g. a transmitter, a receiver, a transceiver and/or one or more antennas.

The methods according to the embodiments described herein for the UE 10 are respectively implemented by means of e.g. a computer program 306 or a computer program product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. The computer program product 306 may be stored on a computer-readable storage medium 307, e.g. a disc, universal serial bus (USB) stick or similar. The computer-readable storage medium 307, having stored thereon the computer program product 306, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. In some embodiments, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and non-volatile memory. Other hardware, conventional and/or custom, may also be included. Designers of radio network nodes will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices. With reference to Fig. 4, in accordance with an embodiment, a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network nodes herein, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) 3291, being an example of the wireless device 10, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).

The communication system of Fig. 4 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Fig. 5. In a communication system 3300, a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Fig.5) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or it may pass through a core network (not shown in Fig.5) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331 , which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides.

It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Fig.5 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Fig. 4, respectively. This is to say, the inner workings of these entities may be as shown in Fig.5 and independently, the surrounding network topology may be that of Fig.4.

In Fig.5, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the performance since the emergency messages may be received and thereby provide benefits such as better reachability.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.

Fig. 6 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 4 and 5. For simplicity of the present disclosure, only drawing references to Figure 6 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional substep 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

Fig. 7 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 4 and 5. For simplicity of the present disclosure, only drawing references to Figure 7 will be included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

Fig. 8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 4 and 5. For simplicity of the present disclosure, only drawing references to Figure 8 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional substep 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional substep 3611 of the first step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer. In a fourth step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Fig. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 4 and 5. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section. In an optional first step 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.