Method for controlling usage of radio cells

Abstract

Method for Controlling Usage of Radio Cells According to various embodiments, a method for controlling usage of radio cells is described, comprising receiving, by a component of a 5G mobile radio communication system, a specification of a group of radio cells forbidden for a mobile terminal in form of three octets, checking, by the component of the 5G mobile radio communication system, whether the octet has a predefined value at a predefined position of the three octets, in response to the octet at the predefined position of the three octets having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 4G radio cells of a 4G mobile radio communication network from the other two octets of the three octets and prevent usage of the determined group of 4G radio cells by the mobile terminal and, in response to the octet at the predefined position of the three octets not having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 5G radio cells from the three octets and prevent usage of the determined group of 5G radio cells by the mobile terminal.

Description

[0001] Description

[0002] Device and Method for Distributing a Warning Message to Mobile Terminals Served by a Mobile Communication Network

[0003] The present disclosure relates to devices and methods for distributing a warning Message to mobile terminals served by a mobile communication network.

[0004] Public Warning Systems (PWS) and Earthquake and Tsunami Warning Systems (ETWS) are critical components of modem emergency communication infrastructures. These systems are designed to disseminate urgent alerts to the public in the event of natural disasters, such as earthquakes and tsunamis, as well as other emergencies. The primary goal of PWS and ETWS is to provide timely and accurate information to help mitigate the impact of such events on human lives and property.

[0005] PWS and ETWS typically utilize mobile radio cell broadcast technology to deliver messages to a large number of mobile devices within a specific geographic area. This method ensures that alerts are received quickly and efficiently, even when traditional communication networks are congested or compromised.

[0006] Non-Terrestrial Networks (NTNs) which include satellite and high-altitude platform systems, offer the potential to extend the reach of PWS and ETWS to remote and underserved areas. However, utilizing an NTN for PWS or ETWS leads to specific challenges. In particular, a radio access network node aboard a geostationary equatorial orbit (GEO) satellite has typically a coverage area that covers large parts outside the impacted area, i.e. the area where the warning message should be distributed. Thus, users may be unnecessarily alerted which may have various undesired effects, such as panic in a region that is not in danger and finally loss of trust in the warning system.

[0007] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Accordingly, approaches which allow a reliable implementation of a PWS or ETWS in a mobile communication system comprising an NTN architecture are desirable.

[0008] According to various embodiments, a method for distributing a warning message to mobile terminals served by a mobile communication network is provided, comprising:

[0009] • receiving, by a network component of the mobile communication network, a request message indicating that a warning message is to be distributed to a set of mobile terminals, wherein the request message includes information allowing the network component to determine a set of radio access network nodes of the mobile communication network which should distribute the warning message to reach the mobile terminals of the set of mobile terminals

[0010] • determining, by the network component, the set of radio access network nodes and determining whether the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite

[0011] • in reaction to a determination that the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite, determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users and removing the radio access network node onboard the geostationary equatorial orbit satellite from the set of radio access network nodes in reaction to the warning message lacking information allowing the mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users; and

[0012] • requesting the radio access network nodes of the set of radio access network nodes to distribute the warning message.

[0013] In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following

[0014] SHEET INCORPORATED BY REFERENCE (RULE 20.6)description, various aspects are described with reference to the following drawings, in which:

[0015] Figure 1 shows a mobile radio communication system.

[0016] Figure 2 illustrates a scenario where the functionality of one or more base stations is provided by one or more satellites.

[0017] Figure 3 illustrates the coverage of a GEO satellite.

[0018] Figure 4 illustrates a warning delivery procedure.

[0019] Figure 5 shows a flow diagram illustrating a method for distributing a warning message to mobile terminals served by a mobile communication network according to an embodiment.

[0020] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects of this disclosure in which the invention may be practiced. Other aspects may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the invention. The various aspects of this disclosure are not necessarily mutually exclusive, as some aspects of this disclosure can be combined with one or more other aspects of this disclosure to form new aspects.

[0021] Various examples corresponding to aspects of this disclosure are described below:

[0022] Example 1 is a method for distributing a warning message to mobile terminals served by a mobile communication network, comprising:

[0023] • receiving, by a network component of the mobile communication network, a request message indicating that a warning message is to be distributed to a set of

[0024] SHEET INCORPORATED BY REFERENCE (RULE 20.6)mobile terminals, wherein the request message includes information allowing the network component to determine a set of radio access network nodes of the mobile communication network which should distribute the warning message to reach the mobile terminals of the set of mobile terminals;

[0025] • determining, by the network component, the set of radio access network nodes and determining whether the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite;

[0026] • in reaction to a determination that the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite, determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users and removing the radio access network node onboard the geostationary equatorial orbit satellite from the set of radio access network nodes in reaction to the warning message lacking information allowing the mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users; and

[0027] • requesting the radio access network nodes of the set of radio access network nodes to distribute the warning message.

[0028] Example 2 is the method of example 1, wherein the information allowing the network component to determine the set of radio access network nodes includes a specification of one or more geographical regions which the warning message should be distributed (i.e. the warning message should be distributed to the mobile terminals served by the mobile communication network which are located in the one or more geographical regions).

[0029] Example 3 is the method of example 1 or 2, wherein the information allowing the network component to determine the set of radio access network nodes is a list of tracking areas to which the warning message should be distributed.

[0030] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Example 4 is the method of any one of examples 1 to 3, wherein the information allowing the mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users includes a specification of one or more geographical areas within a coverage area of the radio access network node onboard the geostationary equatorial orbit satellite where users should be alerted.

[0031] Example 5 is the method of example 4, wherein the specification of the one or more geographical areas within a coverage area of the radio access network node onboard the geostationary equatorial orbit satellite comprises warning area coordinates.

[0032] Example 6 is the method of any one of examples 1 to 5, comprising determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users by checking content of the warning message.

[0033] Example 7 is the method of any one of examples 1 to 5, comprising determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users by checking an indicator included in the warning request message which indicates whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users.

[0034] Example 8 is the method of any one of examples 1 to 7, comprising receiving the request message from a Cell Broadcast Centre Function or from a Public Warning System -Interworking Function.

[0035] Example 9 is the method of any one of examples 1 to 8, wherein the network component is a mobility management component.

[0036] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Example 10 is the method of any one of examples 1 to 9, wherein the network component is a network function of a core network of the mobile communication network.

[0037] Example 11 is the method of any one of examples 1 to 10, wherein the network component is an Access and Mobility Management Function or a Mobility Management Entity.

[0038] Example 12 is a network component of a mobile communication network, configured to perform the method of any one of examples 1 to 11.

[0039] It should be noted that one or more of the features of any of the examples above may be combined with any one of the other examples. In particular, the Examples described in context of the device are analogously valid for the method.

[0040] According to further embodiments, a computer program and a computer readable medium comprising instructions, which, when executed by a computer, make the computer perform the method of any one of the above Examples are provided.

[0041] In the following, various examples will be described in more detail.

[0042] Figure 1 shows a mobile radio communication system 100, for example configured according to 5G (Fifth Generation) as specified by 3GPP (Third Generation Partnership Project).

[0043] The mobile radio communication system 100 includes a mobile radio terminal device 102 such as a UE (user equipment), and the like. The mobile radio terminal device 102, also referred to as subscriber terminal, forms the terminal side while the other components of the mobile radio communication system 100 described in the following are part of the

[0044] SHEET INCORPORATED BY REFERENCE (RULE 20.6)mobile communication network side, i.e. part of a mobile communication network (e.g. a Public Land Mobile Network PLMN).

[0045] Furthermore, the mobile radio communication system 100 includes a Radio Access Network (RAN) 103, which may include a plurality of radio access network nodes, i.e. base stations configured to provide radio access in accordance with a 5G (Fifth Generation) radio access technology (5G New Radio). It should be noted that the mobile radio communication system 100 may also be configured in accordance with LTE (Long Term Evolution) or 6G or another mobile radio communication standard (e.g. non-3GPP accesses like Wi-Fi) but 5G is herein used as an example. Each radio access network node may provide a radio communication with the mobile radio terminal device 102 over an air interface. It should be noted that the radio access network 103 may include any number of radio access network nodes.

[0046] The mobile radio communication system 100 further includes a core network (5GC) 119 including an Access and Mobility Management Function (AMF) 101 connected to the RAN 103, a Unified Data Management (UDM) 104 and a Network Slice Selection Function (NSSF) 105. Here and in the following examples, the UDM may further consist of the actual UE’s subscription database, which is known as, for example, the UDR (Unified Data Repository) 121. The core network 119 further includes an AUSF (Authentication Server Function) 114, a PCF (Policy Control Function) 115 and an AF (application function) 120.

[0047] The core network 119 may have multiple core network slices 106, 107 and for each core network slice 106, 107, the operator (also referred to MNO for Mobile Network Operator) may create multiple core network slice instances 108, 109. For example, the core network 119 includes a first core network slice 106 with three core network slice instances (C-NSIs) 108 for providing Enhanced Mobile Broadband (eMBB) and a second core network slice 107 with three core network slice instances (NSIs) 109 for providing Vehicle-to-Everything (V2X).

[0048] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Specifically, in the shown example, each instance 108 of the first core network slice 106 includes a first Session Management Function (SMF) 110 and a first User Plane Function (UPF) 111 and each instance 109 of the second core network slice 107 includes a second Session Management Function (SMF) 112 and a second User Plane Function (UPF) 113. The SMFs 110, 112 are for handling PDU (Protocol Data Unit) sessions, i.e. for creating, updating and removing PDU sessions and managing session context with the User Plane Function (UPF).

[0049] The RAN 103 and the core network 119 form the network side of the mobile radio communication system, or, in other words, form the mobile radio communication network. The mobile radio communication network and the mobile terminals accessing the mobile radio communication network form, together, the mobile radio communication system.

[0050] Like the core network 119, the RAN 103 may also be sliced, i.e. include multiple RAN slices. A RAN slice and a core network slice 106, 107 may be grouped to form a network slice. In the following, “network slice” (or just “slice”) generally refers to a core network slice but may also include a RAN slice or even a transport network slice.

[0051] The mobile radio communication system 100 may further include an OAM (Operation, Administration and Maintenance) function (or entity) 116, e.g. implemented by one or more OAM servers which is connected to the RAN 103 and the core network 119 (connections are not shown for simplicity). The OAM 116 may include an MDAS (Management Data Analytics Service). The MDAS may for example provide an analytics report regarding network slice instance load. Various factors may impact the network slice instance load, e.g. number ofUEs accessing the network, number of QoS flows, the resource utilizations of different NFs which are related with the network slice instance.

[0052] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Further, the core network 118 includes an NRF (Network Repository Function). The core network 119 may further include a Network Exposure Function (NEF) 117.

[0053] Some base stations (i.e. radio access network nodes) may be implemented by satellites. This means that communication between UEs under the coverage of one or more serving satellites can be supported, using regenerative (or regenerative payload)-based satellite access (onboard gNBs). Such a scenario is illustrated in figure 2.

[0054] Figure 2 illustrates a scenario where the functionality of one or more base stations 201, 202 is provided by one or more satellites 203, 204.

[0055] In the example of figure 1, a first satellite 203 provides a first base station (gNB) 201 and a second satellite 204 provides a second base station 202. The two satellites 203, 204 form a satellite constellation 205 (which may have one or more satellites).

[0056] Each satellite 203, 204 is connected via a respective satellite antenna 206, 207 to a ground network 208 which includes a core network of the mobile communication network to the RAN of which the base stations 201 , 202 belong.

[0057] The ground network 208 in particular includes a ground UPF 209, 210 for each satellite 203, 204 (which may also be the same ground UPF for each satellite 203, 204).

[0058] In the example of figure 2, the first base station 201 serves a first UE 211 and the second base station 202 serves a second UE 212, i.e. the first base station 201 operates a radio cell in which the first UE 211 is located and the second base station 202 operates a radio cell in which the second UE 212 is located. In other words, the first satellite 203 is the serving satellite for the first UE 211 and the second satellite 204 is the serving satellite for the second UE 212.

[0059] SHEET INCORPORATED BY REFERENCE (RULE 20.6)An example of an application function (AF) 120 is a Cell Broadcast Centre Function (CBCF). This is a component in the 5G network architecture responsible for managing and delivering cell broadcast messages. These messages are typically used for public warning systems (PWS), emergency alerts, and other broadcast services. The CBCF interfaces with the Access and Mobility Management Function (AMF) 101 in the 5G core network 119 to ensure that broadcast messages are efficiently delivered to the appropriate cells and user equipment (UE) within a specified area.

[0060] The content of a warning message may be delivered by a Cell Broadcast Entity (CBE) which is a component responsible for creating and managing the content of warning messages. The CBE interfaces with the Cell Broadcast Centre (CBC) to ensure that these messages are formatted correctly and delivered to the appropriate network elements for broadcast to users.

[0061] Since there may not be complete 5G coverage, a Public Warning System - Interworking Function (PWS-fWF) may act as an intermediary between the legacy LTE-based Cell Broadcast Centre (CBC) and the new 5G core network components, ft ensures compatibility and smooth operation of public warning systems as networks transition from LTE to 5G. The PWS-fWF facilitates the communication between the CBC and the AMF 101, enabling the delivery of emergency alerts and public warnings over the 5G network.

[0062] In a 5G network, the CBCF and PWS-fWF work together to ensure the seamless delivery of public warning messages. The CBCF is responsible for generating and managing the broadcast messages, while the PWS-fWF ensures these messages are compatible with the 5G network infrastructure.

[0063] An example for a PWS is an Earthquake and Tsunami Warning System (ETWS).

[0064] SHEET INCORPORATED BY REFERENCE (RULE 20.6)It is desirable that a PWS works also in an NTN (non-terrestrial network) scenario where (at least some) mobile terminals are served by base stations onboard of satellites, as illustrated in figure 2, in particular by base stations on board of geostationary equatorial orbit (GEO) satellites. A GEO satellite may be understood as a satellite in a circular geosynchronous orbit (approximately) 35786 km in altitude above Earth's equator and following the direction of Earth's rotation.

[0065] NTN scenarios cause challenges for PWS. Specifically, in case of GEO satellites, because of the higher altitude deployment (the altitude is typically 35786 Km), the coverage area is very large compared to a LEO (low-earth orbit) satellite or HAP (High-altitude platform station). Hence, using a traditional PWS procedure may lead to unnecessary warning messages being distributed to users outside the “impacted area”, see figure 3.

[0066] Figure 3 illustrates the coverage of a GEO satellite 301.

[0067] It should be noted that if herein coverage of a satellite is mentioned, then this is meant to refer of the coverage of RAN node (i.e. base station) onboard the satellite. In this example, the coverage of the GEO satellite 301 spans four geographical zones, e.g. tracking areas 302, 303, while only one of them is the “impacted area” 303 i.e. is the tracking area 303 where a warning should be distributed (i.e. the area presumably affected by a disaster (earthquake, tsunami, etc.)). This is only a simple example and the impacted area 303 may also cover multiple tracking areas, possibly a large number of tracking areas.

[0068] It is not desirable to distribute the warning to other tracking areas 302 (which are not impacted by the respective danger like earthquake or tsunami) since this might cause unnecessary panic, confusion and evacuation procedures for non-impacted regions. Moreover, distributing (broadcasting) warning messages to possibly thousands of mobile terminals that do not need them is a waste of energy.

[0069] SHEET INCORPORATED BY REFERENCE (RULE 20.6)In view of the above, according to various embodiments, a GEO satellite is used for PWS (i.e. warning message distribution) only when it is possibly to restrict (i.e. limit) the area of distribution (i.e. typically) broadcast or at least the output of a warning to user to an “impacted area” 303.

[0070] Figure 4 illustrates a warning delivery procedure.

[0071] A CBE 401, a CBCF or PWS-IWF 402, an AMF 403, a RAN node (i.e. a base station, e.g. an eNB or a NG(next generation)-RAN node) 404 and a mobile terminal 405 are involved in the procedure. It should be noted that the approaches and procedures described herein may apply to both E-UTRAN (evolved UTMS Terrestrial Radio Access Network, i.e. LTE radio access network) and NG-RAN (i.e. 5G radio access network. Specifically, in the LTE (long-term evolution) case, the AMF 403 may instead by an MME 403.

[0072] In 406, the CBE 401 includes an emergency broadcast request to the CBCF / PWS-IWF 402.

[0073] In 407, the CBCF / PWS-IWF 402 sends a request (e.g. a Write-Replace Warning Request message NG-RAN) to send a warning message according to the emergency broadcast request to the AMF 403 (e.g. to each of multiple AMFs).

[0074] The Write-Replace Warning Request message NG-RAN includes information to which geographical areas the warning message should be delivered. This is typically a list of NG-RAN TAIs (next generation radio access network tracking area identifications). Based on this list, the AMF 403, in 408, selects the appropriate RAN nodes for distribution of the warning message.

[0075] SHEET INCORPORATED BY REFERENCE (RULE 20.6)In 409, the AMF 403 confirms to the CBCF / PWS-IWF 402 and in 410, the CBCF / PWS-IWF 402 response to the CBE 401 accordingly.

[0076] In 411, the AMF 403 sends a request (e.g. a Write-Replace Warning Request) to each RAN node it is determined for distribution of the warning message to distribute the warning message in the coverage area it serves, including the RAN node 404 in the present example.

[0077] Accordingly, in 412, the RAN node 404 broadcasts the warning message to all mobile terminals in its coverage area, including the mobile terminal 405 in the present example. The mobile terminal 405 then alerts its user according to the warning message (i.e. display the warning message and / or outputs an audio alarm) in 413.

[0078] In 414, the RAN node responds (acknowledges) to the AMF 403 and the AMF 403 in 415 informs the CBCF / PWS-IWF 402 about the warning message distribution and may record success and failure of warning message delivery in a trace required in 416.

[0079] The Write-Replace Warning Request (or Indication) message and the Write-Replace Warning Request NG-RAN Request (or Indication) message may include Warning Area Coordinates which may be used to restrict the area in which mobile terminals output (e.g. visually display, typically along with an audio alarm signal) warning (e.g. PWS such as ETWS) messages, in particular to the “impacted area”.

[0080] Namely, the Warning Area Coordinates information element indicates alert area coordinates of a warning message. The RAN node 404 (eNB or NG-RAN node) passes this information to the mobile terminal 404. The mobile terminal 405 uses this information to conditionally display the warning message contents. Specifically, if a mobile terminal receives a warning message which includes Warning Area Coordinates and the mobile terminal determines that it is not located at those coordinates, it does not alert its user (visually and / or via audio).

[0081] SHEET INCORPORATED BY REFERENCE (RULE 20.6)However, the conventional warning delivery procedure contains the Warning Area Coordinates as an optional attribute in the Write-Replace Warning Request message and the Write-Replace Warning Request NG-RAN Request message. Accordingly, in case the RAN node 403 is a GEO satellite as in the scenario of figure 3, a mobile terminal located in a tracking area 302 may receive a warning message, may be unable to determine that it is not in the impacted area 302 (because the warning message does not include the Warning Area Coordinates) and alerts its user although that is unnecessary.

[0082] To address this issue, according to various embodiments, a logic is introduced into the AMF 403 (or MME 403) such that, in 408, after it has received the Write-Replace Warning Request NG-RAN message from the CBCF / PWS-fWF 402 and it has determined the RAN nodes (in particular NR-RAN nodes) which should distribute the warning message, it checks if there is a node with RAT (radio access technology) type “NR(GEO)” in the determined list of RAN nodes. In other words, it determines whether one of the RAN nodes is onboard a GEO satellite.

[0083] If there is, the AMF 403 follows up with a check to see if Warning Area Coordinates (i.e. the Warning Area Coordinates IE) are included in the (e.g. Write-Replace Warning Request NG-RAN) message from the CBCF / PWS-fWF 402. If yes, only then it sends the Write-Replace Warning Message Request to the RAN node onboard the GEO satellite. Else, the AMF 403 (or MME 403) ignores that RAN node from the list of RAN nodes it has determined (when sending Write-Replace Warning Message Requests).

[0084] Alternatively, instead of the AMF 403 (or MME 403) checking whether the Warning Area Coordinates are included in the Write-Replace Warning Request NG-RAN message, an indicator can be introduced as part of the delivery attributes of the Write Replace Warning Request NG-RAN message from the CBCF / PWS-IWF 402, e.g. denoted as called as WAC Indicator. This indicator indicates to the AMF 403 (or MME 403) if the Warning Area Coordinates are available at the CBCF / PWS-fWF and included

[0085] SHEET INCORPORATED BY REFERENCE (RULE 20.6)in the warning messages to be distributed to mobile terminals. In this case, the AMF 403 (or MME 403) only needs to check the indicator’s value to decide whether to send the Write-Replace Warning Message Request to the RAN node onboard the GEO satellite (without having to check the content of the warning message).

[0086] For example, the AMF 404 (or MME 403) proceeds as follows:

[0087] • Based on the list of NG-RAN TAIs received from the CBCF / PWS-IWF, it determines (selects) the appropriate NG RAN nodes for distribution.

[0088] • If a node with RAT type “NR(GEO)” is among the determined radio access network nodes:

[0089] o Check if “Warning Area Coordinates” is present.

[0090] o If present: continue the usual procedure and distribute Warning message also to RAN node onboard GEO.

[0091] o If NOT present: remove the NR(GEO) type RAN node from the list (of RAN nodes for warning message distribution) and continue procedure. o If no node with RAT type “NR(GEO)” is among the selected nodes:

[0092] continue normal procedure.

[0093] For the alternative, where a WAC indicator is used as part of the warning request message from the CBCF / PWS IWF 402 (which is “True / 1” if the warning request message includes “Warning Area Coordinates” and “False / 0” otherwise) , the AMF 404 (or MME 403) proceeds as follows:

[0094] • Based on the list of NG-RAN TAIs received from the CBCF / PWS-IWF, it determines (selects) the appropriate NG RAN nodes for distribution.

[0095] • If a node with RAT type “NR(GEO)” is among the selected nodes:

[0096] o Check “WAC Indicator” in the message:

[0097] ■ if “True / 1”: continue the usual procedure and distribute Warning message also to RAN node onboard GEO satellite.

[0098] ■ If “False / 0”: remove the NR(GEO) type RAN node from list of

[0099] SHEET INCORPORATED BY REFERENCE (RULE 20.6)RAN nodes for distribution and continue procedure.

[0100] • If no node with RAT type “NR(GEO)” is among the selected nodes: continue normal procedure

[0101] In summary, according to various embodiments, a method is provided as illustrated in figure 5.

[0102] Figure 5 shows a flow diagram 500 illustrating a method for distributing a warning message to mobile terminals served by a mobile communication network.

[0103] In 501, a request message indicating that a warning message is to be distributed to a set of mobile terminals is received by a network component of the mobile communication network (e.g. AMF in 5G or MME in LTE). The request message includes information allowing the network component to determine a set of radio access network nodes of the mobile communication network which should distribute the warning message to reach the mobile terminals of the set of mobile terminals.

[0104] In 502 the network component determines the set of radio access network nodes and determines whether the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite.

[0105] In 503, in reaction to a determination that the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite, the network component determines whether the warning message includes (e.g. geographical) information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users (i.e. display a warning and / or output an audio signal according to the warning message) and removes the radio access network node onboard the geostationary equatorial orbit satellite from the set of radio access network nodes in reaction to the warning message lacking (i.e. not including) information allowing the mobile terminals served by the radio

[0106] SHEET INCORPORATED BY REFERENCE (RULE 20.6)access network node onboard the geostationary equatorial orbit satellite whether to alert their users (e.g. depending on location, i.e. depending on (i.e. based on) where the mobile terminals are located: each mobile terminal may from this information and from its own location determine whether to alert its user).

[0107] In 504, the network component requests the radio access network nodes of the set of radio access network nodes to distribute the warning message (wherein possibly, RAN nodes aboard GEO satellites have been removed and thus are not requested to distribute the warning message, i.e. this refers to the remaining radio access network nodes).

[0108] According to various embodiments, in other words, a network component (e.g. AMF or MME) checks if a warning message can be forwarded (or not) to a RAN onboard a GEO Satellite without causing unnecessary alerts (i.e. alerting of users which are not located in the impacted area). For this, an extension of an ETWS / PWS procedure to a regenerative payload-based NTN architecture is provided. This provides a capability of restricting the area of distribution to only the ‘impacted area” as per warning message attributes (in particular whether warning message includes information allowing mobile terminals to determine whether they are in the impacted area).

[0109] The method is for example performed by one or more circuits (e.g. of a network component, which may also be realized by multiple devices). A "circuit" may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof. Thus a "circuit" may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, e.g. a microprocessor. A "circuit" may also be a processor executing software, e.g. any kind of computer program. Any other kind of implementation of the respective functions described above may also be understood as a "circuit". According to an embodiment, a communication system is provided which comprises the mobile terminal and which is particular configured (i.e.

[0110] SHEET INCORPORATED BY REFERENCE (RULE 20.6)comprises one or more components configured) to provision the secure element with the sensing profile.

[0111] While specific aspects have been described, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the aspects of this disclosure as defined by the appended claims. The scope is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced.

[0112] SHEET INCORPORATED BY REFERENCE (RULE 20.6)Description

[0113] Method for Controlling Usage of Radio Cells

[0114] The present disclosure relates to methods for controlling usage of radio cells.

[0115] In mobile radio communication systems, it may be desirable to restrict radio cells that can be used by a mobile terminal. This may for example be the case when radio cells are reserved for users of a certain company or are private cells, etc. Both 4G and 5G communication networks typically provide such a functionality by allowing the definition and signalling of Tracking Area Codes (TACs) which allow defining forbidden tracking areas and thus, groups of radio cells. However, 4G networks typically have TACs consisting of two octets while 5G networks typically have TACs consisting of three octets, leading to challenges in interworking scenarios like in scenario where a 4G network is used as a fallback for a 5G network. Accordingly approaches which allow reliable control of the usage of radio cells in such interworking scenarios are desirable.

[0116] According to various embodiments, a method for controlling usage of radio cells is provided, comprising:

[0117] • Receiving, by a component of a 5G mobile radio communication system, a specification of a group of radio cells forbidden for a mobile terminal in form of three octets,

[0118] • Checking, by the component of the 5G mobile radio communication system, whether the octet has a predefined value at a predefined position of the three octets;

[0119] • In response to the octet at the predefined position of the three octets having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 4G radio cells of a 4G mobile radio

[0120] ERRONEOUSLY FILED (RULE 20.5bis)communication network from the other two octets of the three octets and prevent usage of the determined group of 4G radio cells by the mobile terminal and • In response to the octet at the predefined position of the three octets not having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 5G radio cells from the three octets and prevent usage of the determined group of 5G radio cells by the mobile terminal.

[0121] In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various aspects are described with reference to the following drawings, in which:

[0122] Figure 1 shows a mobile radio communication system.

[0123] Figure 2 illustrates a scenario where NR (New Radio) cells and LTE (Long Term Evolution) cells are neighbouring each other and a Forbidden Area and Non-Forbidden Areas are neighbouring each other.

[0124] Figure 3 shows a flow diagram illustrating a method for controlling usage of radio cells.

[0125] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects of this disclosure in which the invention may be practiced. Other aspects may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the invention. The various aspects of this disclosure are not necessarily mutually exclusive, as some aspects of this disclosure can be combined with one or more other aspects of this disclosure to form new aspects.

[0126] ERRONEOUSLY FILED (RULE 20.5bis)Various examples corresponding to aspects of this disclosure are described below:

[0127] Example 1 is a method for controlling usage of radio cells, comprising receiving, by a component of a 5G mobile radio communication system, a specification of a group of radio cells forbidden for a mobile terminal in form of three octets, checking, by the component of the 5G mobile radio communication system, whether the octet has a predefined value at a predefined position of the three octets, in response to the octet at the predefined position of the three octets having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 4G radio cells of a 4G mobile radio communication network from the other two octets of the three octets and prevent usage of the determined group of 4G radio cells by the mobile terminal and in response to the octet at the predefined position of the three octets not having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 5G radio cells from the three octets and prevent usage of the determined group of 5G radio cells by the mobile terminal.

[0128] Example 2 is the method of example 1, wherein determining the group of 4G radio cells from the other two octets of the three octets comprises interpreting the two octets as 4G Tracking Area Code.

[0129] Example 3 is the method of example 1 or 2, wherein determining the group of 5G radio cells from the three octets comprises interpreting the three octets as 5G Tracking Area Code.

[0130] Example 4 is the method of any one of examples 1 to 3, wherein the component of the 5G mobile radio communication system is an Access and Mobility Management Function, a base station or the mobile terminal.

[0131] Example 5 is the method of any one of examples 1 to 4, wherein the octet at the predefined position is the first octet of the three octets.

[0132] ERRONEOUSLY FILED (RULE 20.5bis)Example 6 is the method of any one of examples 1 to 5, comprising generating, by another component of the 5G mobile radio communication system, the three octets by padding a 4G Tracking Area Code with an octet having the predefined value at the predefined position.

[0133] Example 7 is the method of any one of examples 1 to 6, comprising transmitting the three octets from the other component of the 5G mobile radio communication system to the component of the 5G mobile radio communication system as 5G Tracking Area Code.

[0134] Example 8 is the method of any one of examples 1 to 7, wherein the group of radio cells are radio cells of a tracking area, the group of 4G radio cells are radio cells of a 4G tracking area and the group of 5G radio cells are radio cells of a 5G tracking area.

[0135] Example 9 is the method of any one of examples 1 to 8, wherein the mobile terminal is a subscriber terminal of the 5G mobile radio communication system and is configured for fallback to the 4G mobile radio communication network.

[0136] Example 10 is the method of any one of examples 1 to 9, wherein preventing usage of the determined group of 4G radio cells by the mobile terminal comprises excluding the determined group of 4G radio cells from a set of cells to which the mobile terminal may fall back from the 5G mobile radio communication system.

[0137] Example 11 is the method of any one of examples 1 to 10, wherein preventing usage of the determined group of 5G radio cells by the mobile terminal comprises excluding the determined group of 5G radio cells from a set of target cells for a handover by the mobile terminal.

[0138] Example 12 is a mobile radio communication system, configured to perform a method of any one of examples 1 to 11.

[0139] ERRONEOUSLY FILED (RULE 20.5bis)It should be noted that one or more of the features of any of the examples above may be combined with any one of the other examples. In particular, the Examples described in context of the device are analogously valid for the method.

[0140] According to further embodiments, a computer program and a computer readable medium comprising instructions, which, when executed by a computer, make the computer perform the method of any one of the above Examples are provided.

[0141] In the following, various examples will be described in more detail.

[0142] Figure 1 shows a mobile radio communication system 100 including a 4G part (i.e. a 4G mobile radio communication system) and a 5G part (i.e. a 5G mobile radio communication system).

[0143] The terms 4G and 5G (and the other terms used in the following in this context like EPC, E-UTRAN, LTE, NR etc.) may be understood according to 3 GPP (Third Generation Partnership Project).

[0144] The mobile radio communication system 100 includes a mobile radio terminal device 102 such as a UE (user equipment), and the like. The mobile radio terminal device 102, also referred to as subscriber terminal, forms the terminal side while the other components of the mobile radio communication system 100 described in the following are part of the mobile communication network side, i.e. part of a mobile communication network (e.g. a Public Land Mobile Network PLMN).

[0145] In the 5G part, the mobile radio communication system 100 includes a 5G Radio Access Network (RAN) 103, which may include a plurality of radio access network nodes, i.e. 5G base stations (gNBs) configured to provide radio access in accordance with a 5G (Fifth Generation) radio access technology (5G New Radio). Each 5G radio

[0146] ERRONEOUSLY FILED (RULE 20.5bis)access network node may provide a radio communication with the mobile radio terminal device 102 over an air interface. It should be noted that the 5G radio access network 103 may include any number of radio access network nodes.

[0147] Further, in the 5G part, the mobile radio communication system 100 includes a 5G core network (5GC) 101 including an Access and Mobility Management Function (AMF) 104 connected to the 5G RAN 103 and a Network Slice Selection Function (NSSF) 105. Typically, there is also a Unified Data Management (UDM, not shown in figure 1) which may further consist of the actual UE’s subscription database, which is known as, for example, the UDR (Unified Data Repository). The 5G core network further includes an AUSF (Authentication Server Function) 106, a PCF (Policy Control Function) 107, an AF (application function) 108, a Network Exposure Function (NEF) 109 and a Session Management Function (SMF) 110.

[0148] Further, the 5G RAN 103 is connected to a data network (DN) 112 via a User Plane Function (UPF) 111. The SMF 110 is for handling PDU (Protocol Data Unit) sessions, i.e. for creating, updating and removing PDU sessions and managing session context with the User Plane Function (UPF) 111.

[0149] In the 4G part, the communication system 100 includes a 4G Radio Access Network 113, i.e. an E-UTRAN, which may include a plurality of radio access network nodes, i.e. 4G base stations (eNBs) configured to provide radio access in accordance with a 4G (Fourth Generation) radio access technology, i.e. LTE (Long Term Evolution). Again, it should be noted that each 4G radio access network node may provide a radio communication with the mobile radio terminal device 102 over an air interface and that the 4G radio access network 103 may include any number of 4G radio access network nodes.

[0150] Further, in the 4G part, the mobile radio communication system 100 includes a 4G core network (4GS) 114 which includes a Serving Gateway (S-GW) 115, a PDN (Packet Data

[0151] ERRONEOUSLY FILED (RULE 20.5bis)Network) Gateway (P-GW) 116, a Policy und Charging Rules Function (PCRF) 117 and a Mobility Management Entity (MME) 118.

[0152] The 5GRAN 103 and the 5Gcore network 101 and / or the 4G RAN 113 and the 4G core network 114 form the network side of the mobile radio communication system, or, in other words, form the 5G and / or 4G mobile radio communication network(s). The mobile radio communication network(s) and the mobile terminals accessing the mobile radio communication network(s), in particular the UE 102, form, together, the mobile radio communication system.

[0153] The 5G RAN 103 comprises 5G base stations (gNBs) operating NR (new radio) cells 120 and the 4G RAN 113 comprises 4G (i.e. LTE) base stations (eNBs) operating LTE cells 119.

[0154] The UE 102 may use a NR cell 120 or an LTE cell 119 as its serving radio cell depending on where it is located or choose among them in case it is located in both an NR cell 120 and an LTE cell 119.

[0155] Groups of cells 119, 120 form a tracking area, identified by a tracking area code (TAC). So, the Tracking Area Code (TAC) is a numerical identifier used in cellular networks, including 5G, to uniquely identify a tracking area within the respective cellular network. A tracking area is a geographical region served by a group of radio cells, and the TAC helps determine which tracking area a UE 102 belongs to.

[0156] The TAC can also be used to specify forbidden cells, i.e. cells that a UE 102 may not use as serving cell (i.e. may not register in and thus may not use for communication). This means that a TAC may be a Forbidden TAC within Forbidden Area Information for a UE 102, meaning that the group of radio cells it identifies are forbidden cells for the UE 102. For example, the access of the UE 102 to restricted areas / zones like for example, an MPN

[0157] ERRONEOUSLY FILED (RULE 20.5bis)(Mobile Private Network), military zones, sensitive areas, or enterprise specific areas is forbidden.

[0158] In 5G, Forbidden TACs to which the UE is prohibited to access defines TACs for NR as three octets, i.e. a Forbidden TAC in 5G (i.e. a group of 5G cells 120) is specified in form of three octets (i.e. three times eight bit). In 4G, however, TACs consisting of two octets are used to define Forbidden TACs in E-UTRAN. This causes an interworking issue, since the NGAP (Next Generation Application Protocol) does not support configuring two octets as a forbidden TAC. Nevertheless, it may be desirable to include LIE cells (i.e. parts of an E-UTRAN serving area) as a forbidden area in restriction information (e.g. provided by AMF 104) for the UE to gNB in case of NR to LTE fallback. For example, it may be desirable to restrict mobility from a NR cell to specific EPS (Evolved Packet System) TACs, i.e. groups of LTE cells identified by two-octet LTE TACs, e.g. based on user subscription information. Examples where this may be of interest include in particular HAP (high-altitude platform) and NTN (non-terrestrial network) deployments since because of the moving coverage areas (e.g. due to satellite movement), LTE fallback may occur relatively often and it may not be desirable that a UE 102 falling back from NR to LTE can use any LTE cell.

[0159] UE behaviour in 5GS regarding mobility restriction is specified in 3GPP TS 24.501, where the specification of a Forbidden Area can include three-octet NR TACs. However, this is not limiting from a UE perspective: the UE can for example simultaneously register with an EPS and can directly receive information related to mobility restriction to EPS TAC from the EPC (in the form of a two-octet TAC). However, based on information exchanged in “Mobility Restriction LIST IE” in NGAP, according to the current 3 GPP standard, the gNB cannot receive mobility restriction for EPS TAC from EPS. This may also lead to misalignment in UE and AMF with regard to mobility restriction.

[0160] ERRONEOUSLY FILED (RULE 20.5bis)Figure 2 illustrates a scenario where NR cells (i.e. 5G cells) 201 (of a deployed 5GRAN) and LTE cells (i.e. 4G cells) 202 (of a deployed LTE RAN) are neighbouring each other and a Forbidden Area (i.e. forbidden cells, shown without hatching) and Non-Forbidden Areas (i.e. non-forbidden cells, shown with hatching) are neighbouring each other.

[0161] It is desirable that a 5G core network (5GC, e.g. AMF 104) is enabled to determine and / or specify forbidden LTE cells since otherwise (i.e. without the 5GC being able configure mobility restriction to LTE cells) a handover from the non-forbidden area to the forbidden area may occur (when a UE leaves the 5G coverage and a fallback occurs). If it were only NR deployment or only LTE deployment, such handover could be avoided by the mobility restriction function in 5GC and EPC respectively (using three-octet TACs and two-octet TACs, respectively.

[0162] To address this, according to various embodiments, a padding (left or right) is used to allow a three-octet Forbidden TAC in 5GC to also convey a Forbidden EPS TAC of two octets. For example, a padding at the beginning (or end) of a 5GC three-octet string is introduced (with a length of one octet). Logic at an AMF 104, a gNB, and / or a UE 102 detects the first (or last) octet of a received TAC and determines from that whether the TAC is for EPS or 5GC, i.e. specifies a forbidden 5G or LTE tracking area and avoids, if applicable, access to cells of forbidden tracking areas (and possibly determine an alternative serving cell, if any).

[0163] For example, a two-octet EPC Forbidden TAC

[0164] TAC = [TAC_High][TAC_low]

[0165] is padded to a three-octet 5GC Forbidden TAC

[0166] TAC = [0x00] [TAC High] [TAC Jow],

[0167] Here, the octet (padding) [0x00] serves as indicator that the TAC is for EPS. It is a predefined (and reserved) value.

[0168] ERRONEOUSLY FILED (RULE 20.5bis)The padding is performed by a component of the mobile radio communication system which provides information about Forbidden 4G TACs. This component is for example a policy source, in particular the forbidden TACs which is for example a storage component for subscription data (of subscriber terminals). For example, the policy source for forbidden TACs is the UDM and, for example, the AMF retrieves policies (including forbitten TACs) from the UDM and applies them. In such a case, the UDM (or another source (e.g. policy storage) of the forbidden TACs) performs the padding.

[0169] The 5G network side (e.g. AMF 104 and / or gNB)

[0170] • If 4G Forbidden TAC

[0171] o recognizes the 1st octet (0x00) as indicative to EPS Forbidden Area TAC. o extracts the last two octets [TAC_High][TAC_low] as the EPS Forbidden TAC.

[0172] • if 5G Forbidden TAC EPS

[0173] o recognises the first octet as not an EPS indicative octet (since it has a value other than 0x00).

[0174] o reads the three octets as they are to derive the 5GC Forbidden TAC.

[0175] The mobile terminal side (i.e. the UE 102) may operate in the same manner, if needed. It may for example not be needed if the UE 102 has already registered with the EPS and is informed about forbidden 4G TACs by the EPS

[0176] It should be noted that the padding at the beginning (left padding) is only an example and the padding can also be done at the end (right padding) or even in the middle (i.e. an octet may be inserted between the first and the second octet of the two-octet TAC). However, padding at the end (or in the middle) might be risky since the full three-octets could be interpreted as a different value. It should be noted that the padding value [0x00] is also only an example and other values may be defined to indicate 4G Forbidden TACs. It is also possible that more than one value is defined to indicated 4G Forbidden TACs, i.e.

[0177] ERRONEOUSLY FILED (RULE 20.5bis)either of multiple values at the predefined position of the TAC may indicate that the TAC is a 4G Forbidden TAC.

[0178] In summary, according to various embodiments, a method is provided as illustrated in figure 3.

[0179] Figure 3 shows a flow diagram 300 illustrating a method for controlling usage (by a mobile terminal) of radio cells.

[0180] In 301, a component of a 5G mobile radio communication system receives a specification of a group of radio cells forbidden for a mobile terminal in form of three octets.

[0181] In 302, the component of the 5G mobile radio communication system checks whether the octet has a predefined value at a predefined position of the three octets.

[0182] In 303, in response to the octet at the predefined position of the three octets having the predefined value, the component of the 5G mobile radio communication system determines a group of 4G radio cells of a 4G mobile radio communication network from the other two octets of the three octets (other than the one at the predefined position) and prevents (e.g. avoids) usage of the determined group of 4G radio cells by the mobile terminal.

[0183] In 304, in response to the octet at the predefined position of the three octets not having the predefined value (i.e., “otherwise” or “else”), the component of the 5G mobile radio communication system determines a group of 5G radio cells from the three octets and prevent (e.g. avoids) usage of the determined group of 5G radio cells by the mobile terminal. This may be done under the condition that (i.e. and in response to that), if multiple such predefined values have been defined, the octet at the predefined position does not have one of the other predefined values either. The predefined value may be considered as the last of multiple predefined values for which it is checked whether the

[0184] ERRONEOUSLY FILED (RULE 20.5bis)octet at the predefined position has it so the condition may be assumed to be fulfilled (because the first reaction according to 303 would have already been entered for one of the other predefined values otherwise).

[0185] According to various embodiments, in other words, a component like an AMF, gNB, and / or UE checks whether a Forbidden TAC is for EPS or 5GC and has the capability to interpret received TAC differently for EPS and 5GC.

[0186] The approach of figure 3 enables an inclusion of E-UTRAN tracking areas as a forbidden area in restriction information for the UE (e.g. provided or checked by an AMF) in case of NR to LTE Fallback. So, the mobile terminal (i.e. UE) can for example be prevented from accessing a Forbidden area when falling back from NR to LTE.

[0187] Thus, the approach of figure 3 allows restricting a UE from accessing restricted forbidden areas such as military zones etc. specifically in scenarios of NR to LTE fallback, like for example in HAPs / NTN deployments. Further, it allows backward compatibility (from 4G to 5G).

[0188] The method of figure 3 is carried out by one or more components of a mobile radio communication system, i.e. one or more components of a mobile radio communication system may be configured to perform 301 to 303. The components of the mobile radio communication system may for example be implemented by one or more circuits. A "circuit" may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof. Thus a "circuit" may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, e.g. a microprocessor. A "circuit" may also be a processor executing software, e.g. any kind of computer program. Any other kind of implementation of the respective functions described above may also be understood as a "circuit".

[0189] ERRONEOUSLY FILED (RULE 20.5bis)While specific aspects have been described, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the aspects of this disclosure as defined by the appended claims. The scope is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced.

[0190] ERRONEOUSLY FILED (RULE 20.5bis)

Claims

1. A method for distributing a warning message to mobile terminals served by a mobile communication network, comprising:receiving, by a network component of the mobile communication network, a request message indicating that a warning message is to be distributed to a set of mobile terminals, wherein the request message includes information allowing the network component to determine a set of radio access network nodes of the mobile communication network which should distribute the warning message to reach the mobile terminals of the set of mobile terminals;determining, by the network component, the set of radio access network nodes and determining whether the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite;in reaction to a determination that the set of radio access network nodes includes a radio access network node onboard a geostationary equatorial orbit satellite, determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users and removing the radio access network node onboard the geostationary equatorial orbit satellite from the set of radio access network nodes in reaction to the warning message lacking information allowing the mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users; andrequesting the radio access network nodes of the set of radio access network nodes to distribute the warning message.

2. The method of claim 1 , wherein the information allowing the network component to determine the set of radio access network nodes includes a specification of one or more geographical regions which the warning message should be distributed.SHEET INCORPORATED BY REFERENCE (RULE 20.6)3. The method of claim 1 or 2, wherein the information allowing the network component to determine the set of radio access network nodes is a list of tracking areas to which the warning message should be distributed.

4. The method of any one of claims 1 to 3, wherein the information allowing the mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users includes a specification of one or more geographical areas within a coverage area of the radio access network node onboard the geostationary equatorial orbit satellite where users should be alerted.

5. The method of claim 4, wherein the specification of the one or more geographical areas within a coverage area of the radio access network node onboard the geostationary equatorial orbit satellite comprises warning area coordinates.

6. The method of any one of claims 1 to 5, comprising determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users by checking content of the warning message.

7. The method of any one of claims 1 to 5, comprising determining whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users by checking an indicator included in the warning request message which indicates whether the warning message includes information allowing mobile terminals served by the radio access network node onboard the geostationary equatorial orbit satellite whether to alert their users.SHEET INCORPORATED BY REFERENCE (RULE 20.6)8. The method of any one of claims 1 to 7, comprising receiving the request message from a Cell Broadcast Centre Function or from a Public Warning System - Interworking Function.

9. The method of any one of claims 1 to 8, wherein the network component is a mobility management component.

10. The method of any one of claims 1 to 9, wherein the network component is a network function of a core network of the mobile communication network.

11. The method of any one of claims 1 to 10, wherein the network component is an Access and Mobility Management Function or a Mobility Management Entity.

12. A network component of a mobile communication network, configured to perform the method of any one of claims 1 to 11.SHEET INCORPORATED BY REFERENCE (RULE 20.6)Claims1. A method for controlling usage of radio cells, comprising:Receiving, by a component of a 5G mobile radio communication system, a specification of a group of radio cells forbidden for a mobile terminal in form of three octets;Checking, by the component of the 5G mobile radio communication system, whether the octet of the three octets at a predefined position of the three octets has a predefined value;In response to the octet at the predefined position of the three octets having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 4G radio cells of a 4G mobile radio communication network from the other two octets of the three octets and prevent usage of the determined group of 4G radio cells by the mobile terminal;In response to the octet at the predefined position of the three octets not having the predefined value, determining, by the component of the 5G mobile radio communication system, a group of 5G radio cells from the three octets and prevent usage of the determined group of 5G radio cells by the mobile terminal.

2. The method of claim 1 , wherein determining the group of 4G radio cells from the other two octets of the three octets comprises interpreting the two octets as 4G Tracking Area Code.

3. The method of claim 1 or 2, wherein determining the group of 5G radio cells from the three octets comprises interpreting the three octets as 5G Tracking Area Code.

4. The method of any one of claims 1 to 3, wherein the component of the 5G mobile radio communication system is an Access and Mobility Management Function, a base station or the mobile terminal.ERRONEOUSLY FILED (RULE 20.5bis)5. The method of any one of claims 1 to 4, wherein the octet at the predefined position is the first octet of the three octets.

6. The method of any one of claims 1 to 5, comprising generating, by another component of the 5 G mobile radio communication system, the three octets by padding a 4G Tracking Area Code with an octet having the predefined value at the predefined position.

7. The method of claim 6, comprising transmitting the three octets from the other component of the 5 G mobile radio communication system to the component of the 5G mobile radio communication system as 5G Tracking Area Code.

8. The method of any one of claims 1 to 7, wherein the group of radio cells are radio cells of a tracking area, the group of 4G radio cells are radio cells of a 4G tracking area and the group of 5G radio cells are radio cells of a 5G tracking area.

9. The method of any one of claims 1 to 8, wherein the mobile terminal is a subscriber terminal of the 5G mobile radio communication system and is configured for fallback to the 4G mobile radio communication network.

10. The method of any one of claims 1 to 9, wherein preventing usage of the determined group of 4G radio cells by the mobile terminal comprises excluding the determined group of 4G radio cells from a set of cells to which the mobile terminal may fall back from the 5G mobile radio communication system.

11. The method of any one of claims 1 to 10, wherein preventing usage of the determined group of 5G radio cells by the mobile terminal comprises excluding the determined group of 5G radio cells from a set of target cells for a handover by the mobile terminal.ERRONEOUSLY FILED (RULE 20.5bis)12. A mobile radio communication system, configured to perform a method of any one of claims 1 to 11.ERRONEOUSLY FILED (RULE 20.5bis)

Images