Description:The present application relates to a communication method and device. Disclosed herein are methods performed by a wireless device and base stations, and the wireless device and base stations, as well as systems comprising such devices.

Figure 1 is a schematic diagram of a system 200. The system 200 comprises a radio access network (RAN) 210, a core network 220, a data network 230, and wireless devices 21a/b.

As in Figure 1, the RAN 210 may communicate with Wireless devices (WD or UE) 21a/b via radio communication (e.g. an air interface), and the Wireless Devices 21a/b may communicate with the Core Network 220 via the RAN 210.

The RAN 210 may be referred to as NG-RAN (next generation RAN) and may correspond to a RAN for use in a 5G network. That is, the network 200 may correspond to a 5G network. The network 200 may correspond instead to a 4G/LTE/LTE-A network, for example any network defined by the 3rd Generation Partnership Project (3GPP) specification.

The network 200 comprises a plurality of base stations 31a-f in the RAN 210, denoted eNB or gNB in Figure 1. The RAN 210 may have multiple nodes (base stations 31a-f) acting as primary and secondary nodes. Where the network 200 corresponds to a 5G network, a primary node may be referred to as an M-NG-RAN node and a secondary node as an S-NG-RAN node. Each RAN node in 5G may be a gNodeB (gNB) or an eNodeB (eNB), or an ng-eNB, among other base station types, for example.

Each gNodeB may be deployed with a different architecture (single unit or distributed units – i.e. central unit and at least one distributed unit in the case of a distributed-unit architecture). Each gNB comprises one or more antennas for communicating with Wireless Devices (UEs). One or more gNBs may have multiple sets of antennas to respectively control one or more cells (sectors).
Each Cell provides radio coverage to one or more wireless devices (UEs) over a physical geographical area. That is, the geographical areas served by one or more base stations are generally referred to as cells, and typically many base stations are provided in appropriate locations so as to form a network covering a wide geographical area more or less seamlessly with adjacent and/or overlapping cells. Each base station may support one or more cells and in each cell, the base station divides its available bandwidth, i.e. frequency and time resources, into individual resource allocations for the wireless devices which it serves. The wireless devices (or terminals) may be mobile and therefore may move among the cells, prompting a need for handovers between the base stations of adjacent cells. A terminal may be in range of (i.e. able to detect signals from and/or communicate with) several cells at the same time. In the simplest case it communicates with one “serving” cell, but may be served by multiple cells in a multi-connectivity/multi-connection relationship as described later below.

Two gNBs can communicate with each other using direct physical connection and/or over a transport network. This interface between gNBs may be referred to as the XnAP/X2 Interface as defined in 3GPP 38.423/36.423 specification. Each gNB may be connected to one or more Core Networks, e.g. core network 220, and the interface used for communication between the RAN 210 and core network 220 may be referred to as NG interface as per the 3GPP specification, e.g. 38.413.

The wireless devices (WDs) 21a/b may be referred to as terminals or user equipments (UEs). The UEs 21a/b may be smart phones (e.g. hand held mobile computing device with touch screen), or modems, Customer Premise Equipment (CPE), drones, IoT devices, any other computing device with wire or wireless communication interface to connect to networks.

Each base station 31a-f may be referred to as a Network Node or RAN network node. As indicated above already, in the RAN 210 a gNB may play the role of M-NG-RAN node (may be referred to as M-node) or S-NG-RAN node in the case of a multi-connectivity relationship. The gNB to where the UE primarily gets connected will act as M-NG-RAN node. When the M-Node detects the need to add another node to provide higher capacity of resources to the UE, it can add another node as S-Node and make UE connected to two nodes as multi-connected or “NR-Dual Cell” connected. The M-Node will be the primary node and will be responsible for controlling the signaling with UE, S-Node is used to provide additional capacity.

Core Network (CN) 220: The core Network 220 may correspond to a 5G network core (5GC) and includes an Access and Mobility function (AMF) 221 and User plane functions (UPF) 222, and may include other functions. AMF 221 and UPF 222 may be connected with a gNB using NG-C and NG-U interfaces (control plane and user plane, respectively). The AMF 221 provides access control and mobility services to the UEs 21a/b. Further, the UPF 222 may provide connections to the Data Network 230. The Data Network 230 may include operator services, 3rd party data services, internet access, etc.

According to an embodiment of a first aspect there is disclosed herein a method comprising: by a first base station: receiving deprioritization information indicating deprioritization of (resources of) a second base station for a deprioritization time period; assigning the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assigning the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

Receiving the deprioritization information may comprise receiving the deprioritization information from a wireless device.

The method may comprise, by the first base station, receiving from a/the wireless device a connection request, the connection request including the deprioritization information (as a deprioritization information element).

Receiving the deprioritization information may comprise receiving the deprioritization information from the second base station.

The method may comprise, by the first base station: transmitting to the second base station a multi-connectivity request (in respect of a/the wireless device connected to the first base station); and receiving from the second base station a rejection of the multi-connectivity request, the rejection of the multi-connectivity request including the deprioritization information (as a deprioritization information element).

The multi-connectivity request may comprise a request to add the second base station as an S-node with the first base station as an M-node.

The method may comprise, by the first base station, receiving from the second base station a multi-connectivity disconnection message (with respect to a multi-connectivity relationship (in respect of a/the wireless device) with the first base station as an M-node and the second base station as an S-node), the multi-connectivity disconnection message including the deprioritization information (as a deprioritization information element).

The method may comprise, by the first base station: receiving further deprioritization information indicating deprioritization of (resources of) a third base station for another deprioritization time period; assigning the third base station a third priority (based on the deprioritization of the third base station); and upon expiry of the other deprioritization time period, assigning the third base station a fourth priority, wherein the third priority is lower than the fourth priority, wherein the third priority and the fourth priority are for use by the first base station in determining whether the third base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

The method may comprise, by the second base station, transmitting to the first base station the deprioritization information.

The method may comprise, by the second base station, transmitting to the wireless device the deprioritization information, and by the wireless device: receiving, from the second base station, the deprioritization information; and when transmitting a connection request to the first base station before the deprioritization time period has expired, transmitting to the first base station the deprioritization information, wherein receiving, by the first base station, the deprioritization information comprises receiving from the wireless device the connection request including the deprioritization information.

The method may comprise, by the first base station, transmitting to the second base station a request to add the second base station as an S-node in a multi-connectivity relationship with a/the wireless device and with the first base station as an M-node, and by the second base station: receiving from the first base station the request; determining to reject the request; and transmitting to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including the deprioritization information, wherein receiving, by the first base station, the deprioritization information comprises receiving from the second base station the multi-connectivity rejection message including the deprioritization information.

The method may comprise, by the second base station which is (wirelessly) connected as an S-node in a multi-connectivity relationship with the first base station as an M-node and with a/the wireless device: determining to disconnect from the multi-connectivity relationship; and transmitting to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including the deprioritization information, wherein receiving, by the first base station, the deprioritization information comprises receiving from the second base station the multi-connectivity disconnection message including the deprioritization information.

According to an embodiment of a second aspect there is disclosed herein a method comprising: by a wireless device/terminal: receiving, from a second base station, deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period; and when transmitting/sending a connection request to a first base station before the deprioritization time period has expired, transmitting/sending to the first base station the deprioritization information.

The method may comprise, by the wireless device, receiving from the second base station a connection rejection message, the connection rejection message including the deprioritization information (as a deprioritization information element).

The method may comprise, by the wireless device: transmitting to the second base station a connection request; and receiving from the second base station a connection rejection message (in response to the connection request), the connection rejection message including the deprioritization information (as a deprioritization information element).

The method may comprise, by the wireless device, receiving from the second base station a connection release message, the connection release message including the deprioritization information (as a deprioritization information element).

The method may comprise, by the second base station, transmitting to the wireless device the deprioritization information, and by the first base station: receiving from the wireless device the deprioritization information; assigning the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assigning the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of the wireless device (connected to the first base station)).

According to an embodiment of a third aspect there is disclosed herein a method comprising: by a second base station: receiving from a first base station a request (a multi-connectivity request) to add the second base station as an S-node in a multi-connectivity relationship with a wireless device and with the first base station as an M-node; determining to reject the (muti-connectivity) request; and transmitting to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

The method may comprise, by the first base station: transmitting to the second base station the request; receiving from the second base station the multi-connectivity rejection message including the deprioritization information; assigning the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assigning the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

According to an embodiment of a fourth aspect there is disclosed herein a method comprising: by a second base station (wirelessly) connected as an S-node in a multi-connectivity relationship with a first base station as an M-node and with a wireless device: determining to disconnect from the multi-connectivity relationship; and transmitting to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

The method may comprise, by the first base station: receiving from the second base station the multi-connectivity disconnection message including the deprioritization information; assigning the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assigning the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

Considering the methods of the first to fourth aspects, further optional features are set out below:

The deprioritization information may indicate the deprioritization of the second base station by specifying resources of the second base station.

The deprioritization information may indicate the deprioritization of the second base station by specifying a frequency range and/or a radio access technology (RAT) (corresponding to the second base station or which is specific to the second base station in a communication network comprising the first and second base stations).

The deprioritization information may indicate that the second base station’s communication load is above a communication threshold.

The deprioritization information may indicate that the second base station is overloaded.

The deprioritization information may indicate deprioritization of the second base station in respect of a frequency range and/or a radio access technology (RAT).

The deprioritization information may indicate a deprioritization timer which defines the deprioritization time period.

Assigning the second base station the first priority may comprise storing an identification of the second base station in association with the first priority (in a memory of the first base station).

Assigning the second base station the first priority may comprise, if the first base station has previously assigned a priority to the second base station, adjusting/lowering the previously assigned priority (to the first priority).

Assigning the second base station the first priority may comprise, if the first base station has previously stored an identification of the second base station in association with a priority, adjusting/lowering the priority stored in association with the identification of the second base station.

The method may comprise, by the first base station: starting a deprioritization timer having a length corresponding to the deprioritization time period, and determining the deprioritization time period has expired when the deprioritization timer expires.

The second priority may correspond to (or be the same as) a priority which was assigned to the second base station before the assigning of the first priority.

The method may comprise, by the first base station, selecting at least one candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device) from among a plurality of base stations including the second base station, the selection based on respective priorities assigned to the base stations, the assigned priorities including the (first or second) priority assigned to the second base station.

The method may comprise: by the first base station, when selecting at least one candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device) from among a plurality of base stations including the second base station before expiry of the deprioritization time period, selecting the at least one candidate based on respective priorities assigned to the base stations, the assigned priorities including the first priority assigned to the second base station; and/or by the first base station, when selecting at least one candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device) from among a plurality of base stations including the second base station after (or upon) expiry of the deprioritization time period, selecting the at least one candidate based on respective priorities assigned to the base stations, the assigned priorities including the second priority assigned to the second base station.

The method may comprise, by the first base station, instructing a/the wireless device connected to the first base station to perform at least one measurement with respect to the at least one candidate.

The method may comprise, by the first base station, in response to receiving the deprioritization information, if the first base station has transmitted at least one instruction to at least one wireless device to perform at least one measurement in respect of the second base station, instructing the at least one wireless device to disregard the at least one instruction.

The first and second priorities may be for use by the first base station in determining whether to configure/instruct at least one wireless device to perform at least one measurement with respect to the second base station.

The first and second priorities may be for use by the first base station in determining in respect of which base station among a/the plurality of base stations (including the second base station) to configure/instruct at least one wireless device to perform at least one measurement.

The at least one measurement may comprise at least one of a signal strength, a signal quality, and an interference/noise measurement.

The at least one measurement may comprise at least one of a reference signal received power (RSRP), a reference signal received quality (RSRQ), and a signal to interference and noise ratio (SINR).

The deprioritization information may comprise an/the identification of the second base station.

The connection request may be a radio resource control (RRC) connection request.

The connection release message may be a radio resource control (RRC) release message.

The connection request may include the deprioritization information as a deprioritization information element.

The multi-connectivity rejection message may include the deprioritization information as a deprioritization information element.

The multi-connectivity disconnection message may include the deprioritization information as a deprioritization information element.

The multi-connectivity rejection message may comprise a multi-connectivity release message.

The multi-connectivity rejection message may comprise a multi-connectivity change-required message.

According to an embodiment of a fifth aspect there is disclosed herein a base station, wherein the base station is a first base station and is configured to: receive deprioritization information indicating deprioritization of (resources of) a second base station for a deprioritization time period; assign the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

According to an embodiment of a sixth aspect there is disclosed herein a wireless device/terminal configured to: receive, from a second base station, deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period; and when transmitting/sending a connection request to a first base station before the deprioritization time period has expired, transmit/send to the first base station the deprioritization information.

According to an embodiment of a seventh aspect there is disclosed herein a base station, wherein the base station is a second base station and is configured to: receive from a first base station a request (a multi-connectivity request) to add the second base station as an S-node in a multi-connectivity relationship with a wireless device and with the first base station as an M-node; determine to reject the (muti-connectivity) request; and transmit to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

According to an embodiment of an eighth aspect there is disclosed herein a base station, wherein the base station is a second base station (wirelessly) connected as an S-node in a multi-connectivity relationship with a first base station as an M-node and with a wireless device, the second base station configured to: determine to disconnect from the multi-connectivity relationship; and transmit to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

According to an embodiment of a ninth aspect there is disclosed herein a system comprising a first base station and a second base station, wherein the second base station is configured to transmit to the first base station deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period, and the first base station is configured to: receive the deprioritization information; assign the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

According to an embodiment of a tenth aspect there is disclosed herein a system comprising a first base station and a second base station, wherein the second base station is configured to transmit to the first base station deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period, and wherein the first base station is a base station according to the fifth aspect.

According to an embodiment of an eleventh aspect there is disclosed herein a system comprising a first base station, a second base station, and a wireless device/terminal, wherein the second base station is configured to transmit to the wireless device deprioritization information indicating deprioritization of (resources of) the second base station, the wireless device is configured to: receive, from the second base station, the deprioritization information; and when transmitting/sending a connection request to the first base station before the deprioritization time period has expired, transmit/send to the first base station the deprioritization information, and the first base station is configured to: receive from the wireless device the deprioritization information; assign the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of the wireless device (connected to the first base station)).

According to an embodiment of a twelfth aspect there is disclosed herein a system comprising a wireless device according to the sixth aspect, a first base station, and a second base station, wherein the first base station is a base station according to the fifth aspect.

According to an embodiment of a thirteenth aspect there is disclosed herein a system comprising a first base station, a second base station, and a wireless device, wherein the first base station is configured to transmit to the second base station a request to add the second base station as an S-node in a multi-connectivity relationship with the wireless device and with the first base station as an M-node, the second base station is configured to: receive from the first base station the request; determine to reject the request; and transmit to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period, and the first base station is further configured to: receive from the second base station the deprioritization information; assign the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

According to an embodiment of a fourteenth aspect there is disclosed herein a system comprising a first base station, a second base station, and a wireless device, wherein the first base station is a base station according to the fifth aspect and the second base station is a base station according to the seventh aspect (wherein the first base station is configured to transmit to the second base station the request).

According to an embodiment of a fifteenth aspect there is disclosed herein a system comprising a first base station, a second base station, and a wireless device connected together in a multi-connectivity relationship with the first base station as an M-node and with the second base station as an S-node, wherein the second base station is configured to: determine to disconnect from the multi-connectivity relationship; and transmit to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period, and the first base station is configured to: receive from the second base station the deprioritization information; assign the second base station a first priority (based on the deprioritization of the second base station); and upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority, wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity (in respect of a wireless device (connected to the first base station)).

According to an embodiment of a sixteenth aspect there is disclosed herein a system comprising a first base station, a second base station, and a wireless device, wherein the first base station is a base station according to the fifth and the second base station is a base station according to the eighth aspect.

Features relating to any aspect/embodiment may be applied to any other aspect/embodiment.

Reference will now be made, by way of example, to the accompanying drawings, in which:

Figure 1 is a diagram illustrating a system;
Figure 2 is a timing diagram illustrating a first comparative method;
Figure 3 is a timing diagram illustrating a second comparative method;
Figure 4 is a timing diagram illustrating a first implementation;
Figure 5 is a timing diagram illustrating a second implementation;
Figure 6 is a timing diagram illustrating a third implementation;
Figure 7 is a timing diagram illustrating a fourth implementation;
Figure 8 is a timing diagram illustrating further steps;
Figure 9 is a table;
Figure 10 is a flowchart illustrating a method;
Figure 11 is a flowchart illustrating a method;
Figure 12 is a flowchart illustrating a method;
Figure 13 is a flowchart illustrating a method;
Figure 14 is a diagram illustrating a system;
Figure 15 is a diagram illustrating a wireless device;
Figure 16 is a diagram illustrating a base station;
Figure 17 illustrates an information element;
Figure 18 illustrates an information element;
Figure 19 illustrates an information element;
Figure 20 illustrates an information element; and
Figure 21 is a diagram illustrating an apparatus.

Considering, for example, the network 200 in Figure 1 described above, in NR (new radio, i.e. 5G), when a NetWork node (gNB) gets overloaded or congested or resources are not available or for any other valid reasons, it can reject or release a UE from the frequency and/or RAT (radio access technology – e.g. GSM (Global System for Mobile Communications or 2G, second-generation), UMTS (Universal Mobile Telecommunications Service or 3G, third-generation), LTE (long-term evolution) or 5G NR), it is camped on and indicates to the UE to deprioritize selection of these frequencies and/or RAT again for a specified period. The UE stores this information for the specified period (while the information is valid). And the UE may receive such rejection messages from multiple nodes, for example when nearby cells/nodes are congested.

However when the UE goes to new node and camps, the new node which admits the UE does not have any information of what nodes and/or in respect of what Frequencies and/or RAT the UE has been asked to deprioritize. So, the new node may still configure the UE to perform measurements on these frequencies and/or RAT and/or in respect of the previous node to look for a better coverage/Hand Over candidate node, redirection candidate node, and/or a candidate node for providing multi-connectivity to UE for better throughput.

If the UE is sent to the previous node before expiry of the time period of deprioritization of that node then there is a chance that the UE may get rejected by that node which is undesirable, for example due to wasted signaling and resources in performing the measurements, etc. This scenario is described in more detail below with respect to Figure 2.

Figure 2 is a timing diagram/message sequence diagram according to a first comparative method. The UE and nodes 1-3 (NG-Node1, NG-Node2, NG-Node3) may correspond to the UE 21 and any of nodes 31 in network 200 in Figure 1. The network 200 may correspond to any future networks. Nodes 1-3 are configured to serve UEs on frequencies Freq1-3, respectively, and give rise to cells 1-3 as indicated in Figure 2.

The User Equipment (UE) registers to NetWork (NW) using the RRC connection procedure (e.g. defined in 3gpp spec 38.331) and applies a cell selection (or reselection criteria) to choose a suitable cell to camp on. While selecting the suitable cell, among the cells it has stored, the UE may consider the priority assigned to each cell. If any of the cells needs to be deprioritized as per the NW node instructions it shall lower the priority of that cell and prioritize other cells for the duration indicated by the NW node.

The node 1 admits the UE and may be referred to as M-NG-Node (M-Node), and allocates resources to UE for the operations requested by the UE. However as the NW node 1 admits many UEs and needs to cater for different requests of the UE there is a possibility that the node 1 might run out of resources – such a state may be logically declared as “congestion”. When the node 1 experiences congestion, it may just block new UEs coming in to it or it may release one or more UEs or redirect them to other cells/Frequencies/RAT in order to recover from congestion.

In the case of Figure 2, the UE is connected (or “registered” – these terms may be used herein interchangeably) to node 1 which detects overload (congestion) and at step S21 releases the UE. That is, the node 1 transmits to the UE the message “RRC CONNECTION RELEASE” and provides an information element (IE) “deprioritisationReq” to the UE (e.g. as defined in the 3gpp spec 38.311). The information element may be referred to as deprioritization information and indicates deprioritization of the node 1. The deprioritization information may for example specify a frequency range and/or RAT corresponding to the node 1. The deprioritization information also specifies a deprioritization time period, e.g. defined by a deprioritization timer “deprioritisationTimer” in Figure 2 (which may be referred to as T325 timer as defined in the 3gpp spec 38.331). The UE stores this deprioritization information locally and starts the T325 timer with value sent in “deprioritisationTimer” and deprioritizes the node 1 in respect of those resources. That is, the UE deprioritizes going back to node 1 on the Frequency and/or RAT specified in “deprioritisationReq” IE until “T325” expires.

The UE will also hold these entries and behavior even after it successfully reselects or hands over to a new node/cell/RAT whilst T325 is running. The UE may store multiple of such information if it receives from different Network Nodes – that is, the UE may store deprioritization information in respect of multiple network nodes. However, the UE may still be configured by a new network node to perform measurements in respect of a “deprioritized” node.

That is, after step S21 the UE connects/registers to a new node 2. At step S22 the node 2, unaware that the node 1 is deprioritized for the UE, configures the UE to perform measurements in respect of the node 1, e.g. because the node 2 is considering the node 1 as a candidate for handover or redirection or multi-connectivity. The measurements may include signal strength and/or quality measurements. The measurements may include RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality) or SINR (Signal to Interference & Noise Ratio) or combinations of them (i.e. RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR).

In step S23, after detecting overload, the node 2 releases the UE by transmitting an RRC release message including deprioritization information. The UE stores this deprioritization information and deprioritizes the node 2. However, after the UE is connected to the node 3, at step S24 the node 3 configures the UE to perform measurements in respect of the node 1 and the node 2 even though the deprioritization timers associated therewith are still running.

The measurements configured in steps S22 and S24 may be considered a waste of resources because the UE is likely to be rejected by the nodes 1 and 2 because the nodes 1 and 2 have instructed the UE to deprioritize the node 1 and the node 2.

In case of NR multi-connectivity for the UE, when an M-Node tries to add another node as an S-Node, there is a possibility that the other node may reject the UE addition because of various reasons (overload, HW failure, Resources not available etc.). Currently, handling of such situations is purely left to implementation of the vendor of the Network Node (gNB). With ORAN (Open Radio Access Network) gaining prominence, and if M-Node and S-Node are delivered from two different NW node vendors, they may have different behaviors (Implementation) and may lead to unexpected results. In some implementations, M-node can come back and select the same node again as S-Node with lowered configurations, modified configurations, reconfigurations or trigger other signals towards S-Node. This can create more rejection or failures in the Network as S-Node is already congested. This scenario is described in more detail below with reference to Figure 3.

Figure 3 is a timing diagram/message sequence diagram according to a second comparative method. The UE and nodes 1 and 2 (M-NG-Node, S-NG-Node) may correspond to the UE 21 and any of nodes 31 in network 200 in Figure 1.

At the start of the second comparative method the UE is registered to node 1. After node 1 detects to add another node as an S-node for multi-connectivity, at step S31 node 1 transmits an S-node addition request to node 2. At step S32 node 2 transmits to node 1 an S-node addition request rejection message because, for example, node 2 is overloaded. After disconnection of the UE from node 1, at step S33 the UE re-establishes connection with node 1.

Node 1 again detects to add another node as an S-node for multi-connectivity, and at step S34 node 1 transmits an S-node addition request to node 2. Again, at step S35 node 2 transmits to node 1 an S-node addition request rejection message because, for example, node 2 is still overloaded. The second S-node addition request at step S34 may be considered a waste of resources because node 2 is still overloaded at this point.

Such an undesirable scenario may occur even without the disconnection and reconnection of the UE, but it is noted that the disconnection and reconnection of the UE may make such scenarios more likely because, for example, the node 1 may “forget” information such as when and to what node an S-node addition request was transmitted in respect of the UE upon disconnection of the UE.

In the following description, deprioritization information in respect of a node (i.e. indicating deprioritization of the node) may comprise a frequency range and/or RAT (radio access technology) corresponding to the node. For example, in a network/system comprising the node and other nodes each node may operate on a specific frequency range and/or RAT so that specification of frequency range and/or RAT indicates a particular one of the nodes. For instance, the deprioritization information indicating deprioritization of a node X may specify the frequency range and/or RAT utilized by the node X in the network/system and by virtue of specifying this frequency range and/or RAT may indicate the node X. Alternatively and/or additionally, the deprioritization information may include an identification of the node X. The deprioritization information also includes indication of a deprioritization time period. Furthermore, when a node Y deprioritizes another node X, this may be effected by node Y deprioritizing the node X specifically and/or by node Y deprioritizing the frequency range and/or RAT corresponding to node X which is considered deprioritization of the node X (for example, where the frequency range and/or RAT is specific (unique) to node X).

First Implementation

Figure 4 is a timing diagram/message sequence diagram according to a first implementation disclosed herein.

The UE and nodes 1-3 (NG-Node1, NG-Node2, NG-Node3) may correspond to those involved in the first comparative method and corresponding description may apply with regards to network 200, for example.

The UE initially registers to Node 1 (referred to herein as gNB1) and then moves to Node 2 (referred to herein as gNB2) and then camps on Node 3 (referred to herein as gNB3) after getting released by gNB1 and gNB2 due to congestion. That is, at step S41 node 1 releases the UE via an RRC release message after detecting overload. The RRC release message includes deprioritization information. The deprioritization information may comprise a frequency range and/or RAT corresponding to the node 1 and in a specific example of the first implementation, specifies both a frequency range and an RAT.

At step S42 the UE stores the deprioritization information. The UE then registers to node 2, but at step S43 node 3 releases the UE via an RRC release message after detecting overload. The RRC release message includes deprioritization information in respect of the node 2. At step S44 the UE stores the deprioritization information. This may comprise adding the deprioritization information related to node 2 to an already existing table, or adding this information to information already stored with regards to node 1.

After step S44 the UE has deprioritization information of both gNB1 and gNB2, and a timer T325 is running for each. According to the first comparative method, if the UE were to connect to gNB3 then gNB3, not having knowledge of the UE getting released by gNB1 and gNB2 and instructed to deprioritize them, may see both gNB1 and gNB2 as candidates for HO/redirection/multi-connectivity, and may configure UE to measure these cells for inter frequency or intra frequency HO or possible redirection, or multi-connectivity. As the T325 timers are still running for these frequencies, even if UE tries to reach or camp on them there is a possibility that the UE may get released or rejected soon.

According to the first implementation, at step S45 the UE transmits the deprioritization information relating to gNB1 and gNB2 to gNB3. For example, as illustrated in Figure 4, the UE transmits an RRC connection request including the deprioritization information. The RRC connection request may be referred to herein as an RRC setup request – the terms may be used herein interchangeably. The deprioritization time period indicated in respect of a particular node indicates the time remaining. That is, the indication of the deprioritization time period is such that when gNB3 starts the timer, it will run with the time remaining on the timer and thus expire at the same time as the timer started by the UE. In this way, the deprioritization indicates the same deprioritization time period as stored/monitored by the UE.

To this end, disclosed herein is a new Information Element to be included in the RRC SETUP REQUEST Message according to a specific example of the first implementation so that the UE is able to send all the deprioritization Information that is still valid and stored at the time of sending this message. A modified RRC SETUP REQUEST message according to a specific example (and adapted from the RRC SETUP REQUEST Message defined in a 3GPP specification (38.331) is defined in Figure 17, for example. The additional content is in bold and underlined. Also shown in Figure 17 (at the bottom) is the definition of the “DeprioritisationReq” as already defined in the 3GPP specification 38.331.

According to Figure 4, gNB3 receives the RRC SETUP REQUEST message with deprioritisationReq IE and stores the deprioritization information and assigns gNB1 and gNB2 a priority based on the deprioritization information – i.e. a relatively low priority. The assigned priority is for determining whether the node concerned should be a candidate for handover and/or redirection and/or multi-connectivity, i.e. which node(s) should be candidate(s). gNB3 starts a timer T325 for the duration provided in the deprioritisationTimer in respect of each of node (1 and 2). Once the timer in respect of a node 1 or 2 expires, gNB3 will assign a new priority to the node concerned which is higher than the priority assigned to it whilst the deprioritization timer was running.

That is, whilst T325 is running in respect of a node, gNB3 shall deprioritize configuration of measurements required for redirection or Hand Over or multi connection to those frequencies and/or RAT for that UE (and e.g. for any other UEs as well).

This will help the UE (and e.g. other UEs) not to spend the time on measurements, in turn improving user experience, and providing better performance. Once a said T325 timer expires, gNB3 shall remove these entries from its stored deprioritization list and consider them for all activity as required – i.e. will assign the node concerned new priority taking into consideration that it is no longer deprioritized.

A modified definition of the T325 timer is also disclosed herein according to a specific example of the first implementation, as shown in Figure 9. The first row is what is already defined in the 3GPP specification 38.311 and the second row is the modification. According to the modification, the timer is started by a base station upon reception by the base station of an RRCSetupRequest message (may be referred to herein as an RRC connection request or RRC setup request) with the timer, and upon expiry, the base station is to stop deprioritization of frequencies or RAT (NR) signaled by the RRCSetupRequest, i.e. the nodes indicated by the deprioritization information.

According to a specific example of the first implementation, node 3, upon receiving the RRC connection request (also referred to as RRC setup request) follows a “Procedure A”. Procedure A comprises the following steps:
• Store all the DeprioritisationInfo: {Freq and/or RAT, deprioritisationTime} sent by UE
• Check if any instances of DeprioritisationInfo (Freq and/or RAT) sent by UE corresponds to a neighbor (a neighboring node) for node 1 according to local ANR (automatic neighbor relation) table. If any instance of DeprioritisationInfo entry does not correspond to a neighbor, remove the corresponding stored entries.
• For any instances of DeprioritisationInfo corresponding to a neighboring node, start the corresponding “T325” timer in respect of each said neighboring node.
• Whilst “T325” is valid for a given node, deprioritize (e.g. avoid) configuration of inter frequency, inter RAT measurements and any other measurements which are required for relocating the UE to the frequency range and RAT corresponding to the node.
• Whilst “T325” is valid for a given node, deprioritize “redirection”, “Hand Over”, or multi connection of the UE (and e.g. other UEs) to the said node, i.e. to the Frequency range and RAT corresponding to that node.
• Once “T325” expires for a given node, remove the corresponding “DeprioritisationInfo” entry from the list stored and stop deprioritization of that node and associated measurements.

Determining if a node is a neighbor comprises, for example, checking an ANR table and determining that a node indicated by deprioritization information is a neighbor if the ANR table includes an entry for that node. The node concerned may be identified by its frequency range and/or RAT (in the deprioritization information – as has been described above – and in the ANR table).

Disclosed herein in the first implementation is the UE sending to a first base station deprioritization information indicating deprioritization of a second base station.

Second Implementation

Figure 5 is a timing diagram/message sequence diagram according to a second implementation disclosed herein.

The UE, node 1 (M-NG-Node), and node 2 (S-NG-Node) may correspond to those involved in the second comparative method (Figure 3) and corresponding description may apply with regards to network 200, for example.

The network node, node 1, which admits the UE, is called M-NG-Node (M-Node, or M-NG-RAN node), and will allocate resources to UE for the operations requested by the UE. However the NW node 1 may admit many UEs and if it is not able to serve the resources to UE, it will check if the UE can be connected to multiple cells. If the UE is multi-Connectivity capable, node 1 shall consider to add another cell to the UE, i.e. to establish a multi connectivity or Dual Connectivity relationship/connection.

In order to do that, M-Node sends the “S-Node Addition Request” message at step S51 to request the S-Node (may be referred to as S-NG-RAN node) to allocate resources for dual connectivity operation for a specific UE. The M-node may use, in a 5G scenario, the X2AP interface to send the message at step S51 (and in a 4G/LTE scenario, the XnAP), but this is not essential.

If the S-node were to accept the request, the S-NG-RAN node would report to the M-NG-RAN node, in an S-NODE ADDITION REQUEST ACKNOWLEDGE message, the result for all the requested PDU (protocol data unit) session resources. However if the S-Node is not able to allocate the resources for various reasons, e.g. due to experiencing congestion, it will send an S-NODE ADDITION REQUEST REJECT Message in step S52. As described with respect to the second comparative method, the M-node may try again to add the S-node for multi-connectivity and will be rejected again, leading to wasted resources.

According to the second implementation, the S-node transmits to the M-node deprioritization information indicating deprioritization of the S-node together with the S-node addition request reject message. That is, in step S52 the node 2 transmits to the M-node the S-node addition request reject message including deprioritization information. The deprioritization information here is in the form of an information element “NodeDeprioritisationTime” which indicates a deprioritization time period, i.e. the duration for which it will be deprioritized. That is, the S-Node will identify the amount of time it requires to come out of congestion (this is left to the implementation of the network node and may be determined in a number of ways) and indicates the same to the M-Node.

The NodeDeprioritisationTime IE value can be defined as an enum (data structure for defining the time) of 5min, 10min, 15min and 30min, for example. S-Node shall identify the appropriate value among the given enum values and indicate to M-Node to deprioritize the selection of node 2 as an S-Node. NodeDeprioritisationTime IE is an optional IE to be used only when the S-Node needs to indicate the duration of deprioritization to another Node.

A specific example of the S-node addition request reject message according to the second implementation is shown in Figure 18.

At step S53 the M-Node, which receives S-NODE ADDITION REQUEST REJECT message, stores the deprioritization information. For example the M-node stores the Network node id (of node 2), and the deprioritization time and the frequency range and/or RAT associated with the node 2 (the M-Node may identify the frequency range and/or RAT corresponding to the S-Node which sent the S-NODE ADDITION REQUEST REJECT message from its database (previous knowledge)). The M-node may also store in association therewith an ID of the UE as given by the S-node, NG-RANnodeUEXnAPID, which may be included in the deprioritization information - this is an optional element to store and may be useful for other things in the M-Node later.

At step S54 the M-node starts a timer defining the deprioritization time period (which may be referred to as “TXnNodeDeprioritisation”) and deprioritizes selection of node 2 as an S-node for the duration of the timer. That is, the M-node assigns a first priority to node 2 for the duration of the timer. Upon expiry the M-node assigns a second priority which is higher than the first priority. M-Node shall try to select another node as S-Node for the current UE which needs multi connectivity. The deprioritization of node 2 effected by the M-node is preferably in respect of any UE and not just the UE for which muti-connectivity was attempted.

Furthermore, whilst TXnNodeDeprioritisation timer is running, M-Node releases any measurements with respect to the node 2 if already configured. In other words, the M-node releases any neighbor cell measurements configured in respect of S-node (node 2) in UE, and deprioritizes configuring any further such measurements whilst the timer is running. That is, if the M-node has already configured/instructed a UE to perform measurements with respect to the node 2, the M-node instructs that UE to abandon performing the measurements. The measurements referred to here include those required for taking decisions for mobility management, including all kinds of Handover, cell redirection and cell reselection and multi-connectivity. Furthermore, the M-node shall deprioritize any new such measurements (shall not configure such measurements).

M-node shall perform the same procedure to each S-NODE ADDITION REQUEST REJECT Message received from different nodes that it is connected with.

Disclosed herein in the second implementation is a second base station transmitting to a first base station deprioritization information indicating deprioritization of a second base station.

Third Implementation

Figure 6 is a timing diagram/message sequence diagram according to a third implementation disclosed herein.

The UE, node 1 (M-NG-Node), and node 2 (S-NG-Node) may correspond to those involved in the second comparative method (Figure 3) and corresponding description may apply with regards to network 200, for example.

An S-Node can also experience congestion when a UE is already connected to it, and in such case it can request NW to release it as S-node and indicate to M-Node to deprioritize any further selection of it as S-Node. In such case the S-Node can send an “S-NODE RELEASE REQUIRED” message to M-Node including the NodeDeprioritisationTime IE with valid value. The third implementation is described in more detail below.

The third implementation is similar to the second implementation and concerns the node 2 transmitting to the node 1 deprioritization information. Whilst in the second implementation the node 2 rejected an S-node addition request and included in the rejection the deprioritization information, in the third implementation the node 2 accepts the S-node addition request but then transmits to node 1 an S-node release message including the deprioritization information.

That is, step S61 is the same as step S51 in the second implementation. In step S62 node 2 transmits an “S-node addition request acknowledge” message to the M-node, accepting the S-node addition request. In step S63, after detecting that release is required (e.g. due to overload) and that the node 2 should be deprioritized as an S-node, node 2 transmits an “S-node release required” message to the M-node. The S-node release message includes deprioritization information.

Steps S64 and S65 correspond to the steps S53 and S54 in the second implementation and duplicate description is omitted. The deprioritization information is the same as the deprioritization information described in the second implementation.

At step S66 the M-node transmits to node 2 an “S-node addition release confirm” message.

A specific example of the S-node release required message according to the third implementation is shown in Figure 19.

Disclosed herein in the second implementation is a second base station transmitting to a first base station deprioritization information indicating deprioritization of a second base station.

Fourth Implementation

Figure 7 is a timing diagram/message sequence diagram according to a fourth implementation disclosed herein.

The UE, node 1 (M-NG-Node), and node 2 (S-NG-Node) may correspond to those involved in the second comparative method (Figure 3) and corresponding description may apply with regards to network 200, for example.

An S-Node can also send the NodeDeprioritisationTime IE to the M-Node when it wants to change the S-NODE to any other node using the “S-NODE CHANGE REQUIRED” message.

The fourth implementation (comprising steps S71, S72, S73, S74, S75, and S76) is the same as the third implementation except that instead of an “S-node release required” message, the S-node transmits to the M-node in step S73 an “S-node change required” message which includes the deprioritization information. Furthermore, rather than transmitting an “S-node addition release confirm” message the M-node transmits in step S76 an n “S-node change confirm” message.

A specific example of the S-node change required message according to the fourth implementation is shown in Figure 20.

Disclosed herein in the second implementation is a second base station transmitting to a first base station deprioritization information indicating deprioritization of a second base station.

In the third and fourth implementations, the “S-node release required” message and the “S-node change required” message may be considered examples of multi-connectivity disconnection messages notifying/requesting disconnection from the multi-connectivity relationship of the node transmitting the message.

The first to fourth implementation may be utilized in communication networks corresponding to 5G, 4G, LTE, LTE-A, according to 3GPP definitions, for example, or other communication networks. The network nodes may be referred to as base stations and the UEs may be referred to as wireless devices/terminals. Although the above implementations have been described using terms like “RRC connection request”, “S-node addition request reject” message, “S-node release required” message and the “S-node change required” message, these are not essential and may be replaced with any connection request message, rejection message, or disconnection message, for example. Furthermore, the information elements described in the first to fourth implementations are specific to particular examples of the above implementations and are not essential in including deprioritization information in a message/notification to a base station.

Figure 8 is a timing diagram/message sequence diagram illustrating a possible procedure of an M-node after any of the second to fourth implementations before expiry of the deprioritization time period. In step S81 the M-node determines to add another node as S-node for the UE, and in step S82 detects that the node 2 is congested. That is, in step S82 the M-node acknowledges that the node 2 is deprioritized and, in step S83, determines to not configure measurements in respect of node 2. In step S83, the M-node configures measurements in respect of node 3. In step S84 the M-node selects (or “chooses” – these terms may be used herein interchangeably) node 3 as the best S-node candidate and in step S85 transmits to the node 3 an S-node addition request. In step S86 the node 3 transmits to the M-node an S-node addition request acknowledge message and the node 3 is thus successfully added as an S-node. It is noted that whilst step S82 comprises the M-node detecting that node 2 is congested, this may be considered a specific example of avoiding the node 2 as a candidate for S-node addition because of its low priority (which was assigned based on deprioritization of the node 2).

A number of methods disclosed herein are described below, which may be considered to correspond to the first to fourth implementations as specified below.

Figure 10 is a flowchart illustrating a method. The method comprises steps S101-S103 performed by a first base station.

Step S101 comprises receiving deprioritization information (which may be referred to as DI herein) in respect of a second base station. That is, step S101 comprises receiving deprioritization information indicating deprioritization of (resources of) a second base station for a deprioritization time period.

Step S102 comprises assigning the second base station a first priority (based on the deprioritization of the second base station).

Step S103 comprises, upon expiry of the deprioritization time period, assigning the second base station a second priority. The first priority is lower than the second priority. The first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for handover and/or redirection and/or multi-connectivity (in respect of a wireless device connected to the first base station).

The DI may be received from a wireless device, or from the second base station, for example as part of a multi-connectivity rejection or disconnection message. The DI may be received as a deprioritization information element.

In a specific implementation the method further comprises, by the first base station, receiving further DI indicating deprioritization of (resources of) a third base station for another deprioritization time period, assigning the third base station a third priority, and upon expiry of the other deprioritization time period, assigning the third base station a fourth priority, wherein the third priority is lower than the fourth priority, and wherein the third priority and the fourth priority are for use by the first base station in determining whether the third base station is a candidate for handover and/or redirection and/or multi-connectivity (in respect of the wireless device connected to the first base station). These further steps of this specific implementation are the same as steps S101-S103 except that the DI is received from a third base station rather than a second base station, , a further deprioritization time period is indicated rather than a deprioritization time period, and third and fourth priorities are assigned rather than first and second priorities, respectively.

The Figure 10 method may be considered to correspond to the operations of node 3 in the first implementation and the M-node in any of the second to fourth implementations, and any description therein may apply here, and vice versa.

Figure 11 is a flowchart illustrating a method. The method comprises steps S201 and S202 performed by a wireless device/terminal.

Step S201 comprises receiving DI in respect of a second base station. That is, step S201 comprises receiving, from a second base station, deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

Step S202 comprises transmitting to a first base station the DI. That is, step S202 comprises, when transmitting a connection request to a first base station before the deprioritization time period has expired, transmitting to the first base station the deprioritization information.

The DI may be received as part of a connection rejection or release notification/message, and the DI may be included therein as an information element.

The Figure 11 method may be considered to correspond to the operations of the UE in the first implementation and any description therein may apply here, and vice versa.

Figure 12 is a flowchart illustrating a method. The method comprises steps S301-S302 performed by a second base station.

Step S301 comprises receiving a multi-connectivity request. That is, step S301 comprises receiving from a first base station a request (multi-connectivity request) to add the second base station as an S-node in a multi-connectivity relationship with a wireless device and with the first base station as an M-node.

Step S302 comprises determining to reject the request. Step S303 comprises transmitting to the first base station a rejection including DI indicating deprioritization of the second base station. That is, step S303 comprises transmitting to the first base station a multi-connectivity rejection notification/message, the multi-connectivity rejection notification/message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

The Figure 12 method may be considered to correspond to the operations of node 2 in the second implementation and any description therein may apply here, and vice versa.

Figure 13 is a flowchart illustrating a method. The method comprises steps S401 and S402 performed by a second base station.

Step S401 comprises determining to disconnect from a multi-connectivity relationship. That is, step S401 comprises, by the second base station which is (wirelessly) connected as an S-node in a multi-connectivity relationship with a first base station as an M-node and with a wireless device, determining to disconnect from the multi-connectivity relationship.

Step S402 comprises transmitting to the first base station a disconnection message including DI indicating deprioritization of the second base station. That is, step S402 comprises transmitting to the first base station a multi-connectivity disconnection notification/message, the multi-connectivity disconnection notification/message including deprioritization information indicating deprioritization of (resources of) the second base station for a deprioritization time period.

The Figure 13 method may be considered to correspond to the operations of node 2 in the third and fourth implementations and any description therein may apply here, and vice versa.

There are also disclosed herein methods comprising combinations of the methods in Figures 10-13. That is, there is disclosed herein a method (referred to as Figure 10/11 method) comprising the Figure 11 method followed by the Figure 10 method, optionally with a preceding step of the second base station rejecting or releasing the wireless terminal and transmitting to the wireless device the DI. Such a method may be carried out by a system comprising the wireless device and the first and second base stations and may be considered to correspond to the first implementation and any description therein may apply here, and vice versa. There is also disclosed herein a method (referred to as Figure 10/12 method) comprising the Figure 12 method followed by the Figure 10 method, optionally with a preceding step of the first base station transmitting to the second base station the multi-connectivity request. Such a method may be carried out by a system comprising the first and second base stations (and optionally the wireless device) and may be considered to correspond to the second implementation and any description therein may apply here, and vice versa. There is also disclosed herein a method (referred to as Figure 10/13 method) comprising the Figure 13 method followed by the Figure 10 method. Such a method may be carried out by a system comprising the first and second base stations (and optionally the wireless device) and may be considered to correspond to the third and fourth implementations and any description therein may apply here, and vice versa.

In general, considering the above methods, for example, the DI may indicate the deprioritization of the second base station by specifying resources of the second base station, e.g. a frequency range and/or RAT (corresponding to the second base station or which is specific to the second base station in a communication network comprising the first and second base stations). The DI may indicate deprioritization of the second base station in respect of a frequency range and/or a RAT. The DI may indicate a deprioritization timer which defines the deprioritization time period.

In the first base station, assigning the second base station the first/second priority may comprise storing an identification of the second base station in association with the first/second priority or updating a record already stored therein.

The first base station may start a deprioritization timer having a length corresponding to the deprioritization time period.

The priority assigned to the second base station may be used by the first base station in any of the above methods as follows: selecting at least one candidate for handover and/or redirection and/or multi-connectivity (in respect of the wireless device) from among a plurality of base stations including the second base station, the selection based on respective priorities assigned to the base stations, the assigned priorities including the priority assigned to the second base station.

In more detail, this may involve, by the first base station, when selecting at least one candidate for handover and/or redirection and/or multi-connectivity from among the plurality of base stations before expiry of the deprioritization time period, selecting the at least one candidate based on respective priorities assigned to the base stations, the assigned priorities including the first priority assigned to the second base station, and/or when selecting at least one candidate for handover and/or redirection and/or multi-connectivity from among the plurality of base stations after or upon expiry of the deprioritization time period, selecting the at least one candidate based on respective priorities assigned to the base stations, the assigned priorities including the second priority assigned to the second base station.

In any of the above methods involving steps performed by the first base station, the first base station may in response to receiving the DI, if the first base station has transmitted at least one instruction to at least one wireless device to perform at least one measurement in respect of the second base station, instruct the at least one wireless device to disregard the at least one instruction.

Figure 14 is a schematic diagram illustrating a system 100. System 100 comprises a wireless device 20, a first base station 30, and a second base station 40. The system 100 may be configured to carry out any of the Figure 10/11, Figure 10/12, and Figure 10/13 methods described above, and in such cases the system may comprise only the elements carrying out method steps thereof (e.g. only the first base station 30 and wireless device 20 or only the first and second base stations 30, 40). The system 100 may be partly or wholly configured according to the system 200 and description therein may apply here. For example, the system 100 may correspond to 5G, 4G, LTE, LTE-A, according to 3GPP definitions, for example, or other communication networks.

Figure 15 is a schematic diagram illustrating the wireless device 20. The wireless device 20 may be configured to carry out the method steps described above with respect to Figure 11. Wireless device 20 comprises an antenna 22 for transmitting and receiving signals/information, a memory 24 for storing information/data, and a processor 26 for carrying out method steps/operations that the wireless device performs. The processor 26 may execute instructions stored as a computer program in the memory 24 to carry out operations/method steps. The wireless device 20 may be considered to correspond to the UE in any of the first to fourth implementations.

Figure 16 is a schematic diagram illustrating a base station 50. The base station 50 may correspond to the first base station 30 and/or the second base station 40 and may be configured to carry out the method steps described above with respect to Figures 10, 12, and/or 13 accordingly. Base station 50 comprises an antenna 52 for transmitting and receiving signals/information, a memory 54 for storing information/data, and a processor 56 for carrying out method steps/operations that the base station 50 performs. The processor 56 may execute instructions stored as a computer program in the memory 54 to carry out operations/method steps. The base station 50 may be considered to correspond to any of nodes 1-3 in the first implementation and/or node 1 and/or 2 in the second to fourth implementations. The first and/or second base station 30, 40 may correspond to a eNB, gNB, M-NG-RAN node, S-NG-RAN node, NG-eNB, etc.

Figure 21 is a block diagram of an information processing apparatus 10 or a computing device 10, such as a data storage server, which embodies the present invention, and which may be used to implement some or all of the operations of a method embodying the present invention, and perform some or all of the tasks of apparatus of an embodiment. The computing device 10 may be used to implement any of the method steps described above, e.g. any of steps S101-103, S201-S202, S301-S303, and S401-402, and/or any operations of the UE or any nodes in the first to fourth implementations.

The computing device 10 comprises a processor 993 and memory 994. Optionally, the computing device also includes a network interface 997 for communication with other such computing devices, for example with other computing devices of invention embodiments. Optionally, the computing device also includes one or more input mechanisms such as keyboard and mouse 996, and a display unit such as one or more monitors 995. These elements may facilitate user interaction. The components are connectable to one another via a bus 992.

The memory 994 may include a computer readable medium, which term may refer to a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) configured to carry computer-executable instructions. Computer-executable instructions may include, for example, instructions and data accessible by and causing a computer (e.g., one or more processors) to perform one or more functions or operations. For example, the computer-executable instructions may include those instructions for implementing a method disclosed herein, or any method steps disclosed herein, for example any of steps S101-103, S201-S202, S301-S303, and S401-402, and/or any operations of the UE or any nodes in the first to fourth implementations. Thus, the term “computer-readable storage medium” may also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the method steps of the present disclosure. The term “computer-readable storage medium” may accordingly be taken to include, but not be limited to, solid-state memories, optical media and magnetic media. By way of example, and not limitation, such computer-readable media may include non-transitory computer-readable storage media, including Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory devices (e.g., solid state memory devices).

The processor 993 is configured to control the computing device and execute processing operations, for example executing computer program code stored in the memory 994 to implement any of the method steps described herein. The memory 994 stores data being read and written by the processor 993 and may store deprioritization information and/or an ANR tables and/or signaling information/messages, for example, and/or other data, described above, and/or programs for executing any of the method steps described above. As referred to herein, a processor may include one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. The processor may include a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or processors implementing a combination of instruction sets. The processor may also include one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. In one or more embodiments, a processor is configured to execute instructions for performing the operations and operations discussed herein.

The display unit 995 may display a representation of data stored by the computing device, and may also display a cursor and dialog boxes and screens enabling interaction between a user and the programs and data stored on the computing device. The input mechanisms 996 may enable a user to input data and instructions to the computing device.

The network interface (network I/F) 997 may be connected to a network, such as network 100 and/or the Internet, and is connectable to other such computing devices via the network. The network I/F 997 may control data input/output from/to other apparatus via the network.

Other peripheral devices such as microphone, speakers, printer, power supply unit, fan, case, scanner, trackerball etc may be included in the computing device.

Methods embodying the present invention may be carried out on a computing device/apparatus 10 such as that illustrated in Figure 21. Such a computing device need not have every component illustrated in Figure 21, and may be composed of a subset of those components. For example, the apparatus 10 may comprise the processor 993 and the memory 994 connected to the processor 993. Or the apparatus 10 may comprise the processor 993, the memory 994 connected to the processor 993, and the display 995. A method embodying the present invention may be carried out by a single computing device in communication with one or more data storage servers via a network. The computing device may be a data storage itself storing at least a portion of the data.

The computing device 10 may be referred to as an information processing apparatus 10. The information processing apparatus 10 is a specific example of the wireless device 20 and the base station 50, and additionally comprises an antenna.

A method embodying the present invention may be carried out by a plurality of computing devices operating in cooperation with one another. One or more of the plurality of computing devices may be a data storage server storing at least a portion of the data.

The invention may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The invention may be implemented as a computer program or computer program product, i.e., a computer program tangibly embodied in a non-transitory information carrier, e.g., in a machine-readable storage device, or in a propagated signal, for execution by, or to control the operation of, one or more hardware modules.

A computer program may be in the form of a stand-alone program, a computer program portion or more than one computer program and may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a data processing environment. A computer program may be deployed to be executed on one module or on multiple modules at one site or distributed across multiple sites and interconnected by a communication network.

Method steps of the invention may be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Apparatus of the invention may be implemented as programmed hardware or as special purpose logic circuitry, including e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions coupled to one or more memory devices for storing instructions and data.

The above-described embodiments of the present invention may advantageously be used independently of any other of the embodiments or in any feasible combination with one or more others of the embodiments.

Disclosed herein are methodologies for controlling measurements and node selection when a network node needs to be deprioritized. This improves overall experience in User equipment, Network node and saves signaling messages by avoiding failures.

Elements of aspects disclosed herein include:
• A method to report all the deprioritized freq/RAT that are active in UE while connecting to any node
• A method for controlling measurement configurations in UE for deprioritized Nodes
• Method to select appropriate secondary node while providing a multi connectivity for a UE

Objectives of the aspects disclosed herein include (among others):
• To reduce signaling failures and save User Equipment power, and improve user experience.
• To avoid sending the UE to congested (deprioritized) nodes - to avoid UE experiencing rejection in those nodes
• To improve the UE battery life (power) by not configuring measurements on such deprioritized frequencies/RATs (i.e. the nodes corresponding thereto)
• To avoid selection of deprioritized nodes as secondary nodes for UE - So that admission failures/rejection for UE are avoided
• To save UE from performing unnecessary measurements, avoid Hand over failures, redirection failures, avoid secondary node selection failures.

Problems with the first and second comparative methods include the fact that the network will not have information of what Freq/RATs, UE has deprioritized and hence may configure them to be measured by UE blindly. These measurements may take lots of power cycles, involve many signals between UE and network, and if the network redirects UE to such frequencies/RAT, UE attachment to those frequencies/RAT will fail, and then the UE has to perform additional procedures to find another suitable Frequency/RAT.

The problems with the first and second comparative methods make the User experience poor and introduce unnecessary signaling, failure messages, and wastes lot of power of UE.

The aspects disclosed herein solve the above problems because, in the case of the first comparative method, the UE transmits DI to the base station and this new node (current node where UE is camping) knows not to configure such deprioritized frequencies/RATs for measurement by the UE (and other UEs) during the deprioritization time period. This will help UE(s) not to spend time, resources, and energy on those measurements, improving power and performance.

The aspects disclosed herein solve the above problems because, in the case of the second comparative method, the message by S-node of DI indicating deprioritization of the S-node enables the M-node to adjust its algorithm and select any other suitable node as S-Node which are connected to it, and also to avoid configuring measurements in respect of the S-node (i.e. frequencies/RATs corresponding thereto). This avoids unnecessary signaling and failures scenarios. The sending of DI helps the M-Node to select the better node as S-Node for any UE which requires multi connectivity. With the help of information received from the S-Node, which is congested, the M-node will deprioritize selection of same node as S-Node for the period of congestion.
, Claims:1. A method comprising
by a first base station:
receiving deprioritization information indicating deprioritization of a second base station for a deprioritization time period;
assigning the second base station a first priority; and
upon expiry of the deprioritization time period, assigning the second base station a second priority, wherein the first priority is lower than the second priority,
wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity.
2. A base station, wherein the base station is a first base station and is configured to:
receive deprioritization information indicating deprioritization of a second base station for a deprioritization time period;
assign the second base station a first priority; and
upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority,
wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity.
3. A system comprising a first base station and a second base station, wherein
the second base station is configured to transmit to the first base station deprioritization information indicating deprioritization of the second base station for a deprioritization time period, and
the first base station is configured to:
receive the deprioritization information;
assign the second base station a first priority; and
upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority,
wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity.
4. A method comprising
by a wireless device:
receiving, from a second base station, deprioritization information indicating deprioritization of the second base station for a deprioritization time period; and
when transmitting a connection request to a first base station before the deprioritization time period has expired, transmitting to the first base station the deprioritization information.
5. A wireless device configured to:
receive, from a second base station, deprioritization information indicating deprioritization of the second base station for a deprioritization time period; and
when transmitting a connection request to a first base station before the deprioritization time period has expired, transmit to the first base station the deprioritization information.
6. A system comprising a first base station, a second base station, and a wireless device, wherein
the second base station is configured to transmit to the wireless device deprioritization information indicating deprioritization of the second base station,
the wireless device is configured to:
receive, from the second base station, the deprioritization information; and
when transmitting a connection request to the first base station before the deprioritization time period has expired, transmit to the first base station the deprioritization information, and
the first base station is configured to:
receive from the wireless device the deprioritization information;
assign the second base station a first priority; and
upon expiry of the deprioritization time period, assign the second base station a second priority, wherein the first priority is lower than the second priority,
wherein the first priority and the second priority are for use by the first base station in determining whether the second base station is a candidate for any of handover, redirection, and multi-connectivity.
7. A method comprising
by a second base station:
receiving from a first base station a request to add the second base station as an S-node in a multi-connectivity relationship with a wireless device and with the first base station as an M-node;
determining to reject the request; and
transmitting to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including deprioritization information indicating deprioritization of the second base station for a deprioritization time period.
8. A base station, wherein the base station is a second base station and is configured to:
receive from a first base station a request to add the second base station as an S-node in a multi-connectivity relationship with a wireless device and with the first base station as an M-node;
determine to reject the request; and
transmit to the first base station a multi-connectivity rejection message, the multi-connectivity rejection message including deprioritization information indicating deprioritization of the second base station for a deprioritization time period.
9. A method comprising
by a second base station connected as an S-node in a multi-connectivity relationship with a first base station as an M-node and with a wireless device:
determining to disconnect from the multi-connectivity relationship; and
transmitting to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including deprioritization information indicating deprioritization of the second base station for a deprioritization time period.
10. A base station, wherein the base station is a second base station connected as an S-node in a multi-connectivity relationship with a first base station as an M-node and with a wireless device, the second base station configured to:
determine to disconnect from the multi-connectivity relationship; and
transmit to the first base station a multi-connectivity disconnection message, the multi-connectivity disconnection message including deprioritization information indicating deprioritization of the second base station for a deprioritization time period.