MASTER NODE, SECONDARY NODE, AND METHOD IMPLEMENTED IN A WIRELESS COMMUNICATION NETWORK - Patent application

Abstract

Embodiments herein relate to a method, for example implemented by a master node (12) for handling communications in a wireless communication network (1). The master node obtains a UHI associated with a PCell of a user equipment (UE) (10) and further obtains an additional UHI associated with a connected PSCell of the UE (10) from a secondary node (13). The master node then correlates the obtained UHI and the obtained additional UHI with a list of associated PCells and PSCells.

Description

[Technical Field]

[0001]

[0001] The present disclosure relates to a master node (MN), a secondary node (SN), and methods implemented therein for wireless communication. Additionally, a computer program product and a computer-readable storage medium are also provided herein. In particular, the present disclosure relates to handling or enabling communications, such as handling of user equipment history information (UHI), from a user equipment (UE) to a radio network node in a wireless communication network. [Background technology]

[0002] In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, or stations (STAs) and / or wireless devices, communicate through a radio access network (RAN) to one or more core networks (CNs). The RAN covers a geographical region that is divided into service areas or cell areas, and each service area or cell area is served by a radio network node, such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some wireless networks may also be referred to as a Node B, Evolved Node B, or gNode B. A service area or cell area is a geographical area where radio coverage is provided by a radio network node. The radio network node operates on radio frequencies to communicate over the air interface with wireless devices within range of the access node. The radio network node communicates with wireless devices over a downlink (DL), and the wireless devices communicate with the access node over an uplink (UL).

[0003] The Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) telecommunications network that evolved from the second-generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA) for communication with UEs. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree on standards for current and future generation networks, exploring improvements in data rates and radio capacity. In some RANs, as in the case of UMTS, several radio network nodes may be connected, for example, by landlines or microwaves, to a controller node, such as a radio network controller (RNC) or base station controller (BSC), which monitors and coordinates the various activities of multiple radio network nodes connected to the controller node. The RNC is typically connected to one or more core networks.

[0004] The Evolved Packet System (EPS) specification has been completed within the 3rd Generation Partnership Project (3GPP), and this work will continue in future 3GPP releases, such as 4G and 5G networks. The EPS includes the Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology in which radio network nodes are directly connected to the EPC core network. Therefore, the EPS radio access network (RAN) has an essentially "flat" architecture, with radio network nodes directly connected to one or more core networks.

[0005] In the emerging 5G technology, also known as New Radio (NR), the use of a large number of transmit and receive antenna elements may be of great interest because it allows for the use of beamforming, such as transmit and receive beamforming. Transmit beamforming means that the transmitter can amplify the transmitted signal in one or more selected directions while suppressing the transmitted signal in other directions. Similarly, on the receive side, the receiver can amplify the signal from one or more selected directions while suppressing undesired signals from other directions.

[0006] Beamforming allows for stronger signals for individual connections. On the transmitting side, this can be achieved by concentrating the transmit power in the desired direction, and on the receiving side, it can be achieved by increasing the receiver sensitivity in the desired direction. This beamforming improves the throughput and coverage of the connection. It also makes it possible to reduce interference from undesired signals, thereby enabling several simultaneous transmissions via multiple individual connections using the same resources in the time-frequency grid, the so-called multi-user multiple-input multiple-output (MIMO).

[0007] User Equipment History Information (UHI) was introduced in LTE and is adopted in NR. The source radio network node collects and stores UHI while the UE is connected and camped in one of its cells.

[0008] The UHI collected by the radio network node differs depending on whether it is NR or LTE, but they share similarities. The UHI may include the cell identifier of the serving primary cell (PCell), the time the UE has stayed in the cell, and the handover (HO) cause. The maximum number of cells in the UHI is capped at 16 entries.

[0009] The procedural text for the accumulation of UHI by the involved NG-RAN nodes can be found in TS 38.300 v16.0.0, section 15.5.4, and the corresponding ASN.1 can be found in TS 38.413 v16.0.0, section 9.3.1.95, IE UE Historical Information. The Abstract Syntax Notation (ASN, ASN1, ASN.1) used herein, e.g., as code snippets, describes what information is / can be communicated in each scenario referenced.

[0010] The procedural text related to the accumulation of UHI by the involved eNBs can be found in section 16.2.2.1 of TS 36.300, and the corresponding ASN.1 can be found in section 9.2.1.42 of TS 36.413 v16.0.0, information element (IE) UE history information.

[0011] It should be noted that the UHI is different from Mobility History Information (MHI): the MHI is collected by the UE and then forwarded to the network, whereas the UHI is collected by the relevant radio network nodes.

[0012] Multi-Radio Dual Connectivity (MR-DC), as described in TS 37.340 v16.0.0, describes a scenario in which a UE that can connect to multiple radio network nodes utilizes multiple resources to improve throughput. It is a generalization of intra-E-UTRA Dual Connectivity (DC), as described in TS 36.300 v16.0.0.

[0013] When a UE is in DC mode, one radio network node acts as a Master Node (MN) and the other radio network node acts as a Secondary Node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. More information about MR-DC can be found in TS 38.401 v.16.0.0. The primary cell in the MN is known as the Primary Cell (PCell) and the primary cell in the SN is known as the Primary Secondary Cell (PSCell).

[0014] In the ongoing RAN3 discussion, the MN can collect UHI associated with the PCell. Similarly, the SN can collect UHI associated with the PSCell. Also in the discussion, the SN UHI is forwarded to the MN and then correlated at the MN. The correlated complete UHI consists of a nested structure where the SN UHI is listed under the associated MN UHI. Thus, the complete UHI structure for the UE consists of a list of PCell information, and the associated PSCell information is listed under the associated PCell.

[0015] The UE historical information present at the MN consists of both PCell and PSCell information. The MN collects PCell information and compiles this information in a correlated UHI. Similarly, the SN only collects PSCell information, which is maintained independently and forwarded to the MN.

[0016] Since the list is modified independently by the radio network nodes, the list can be correlated at the MN and achieved by the IE "Time the UE has stayed in the cell" or "Time the UE has stayed in the cell extension granularity".

[0017] The element "UE Stayed in Cell" has a range of (0-4095) seconds, and the element "UE Stayed in Cell Extended Granularity" has a range of (0-40950) tenths of seconds. Beyond this limit, a maximum value is set. This makes correlation between PSCell and PCell impossible in certain situations, as explained below. Further information on the IEs can be found in sections 9.3.1.95-97 of TS 38.413 v16.0.0. Summary of the Invention

[0018] Having complex or less accurate correlations may affect the mobility of the UEs, and thus the performance of the wireless communication network may be limited or slowed down.

[0019] An object of the embodiments herein is to provide a mechanism for improving performance in wireless communication networks.

[0020] According to one aspect, the object is achieved by providing a method implemented by a mobile node (MN) for handling communications, such as handling a user-defined information (UHI), in a wireless communication network. The MN obtains a user-defined information (UHI) associated with a PCell of the UE and obtains, from a secondary node, a further user-defined information (UHI) associated with a PSCell to which the UE is connected. The MN then correlates the obtained UHI and the obtained further user-defined information (UHI) with a list of associated PCells and PSCells.

[0021] According to embodiments herein, MN is based on correlation to: timestamps within the two UHIs, An optional timestamp that is used only if the "UE time spent in the cell" exceeds a given range; Repeated entries when the "UE stays in cell" range is exceeded, An optional timestamp that is used only if the "UE stayed in cell" time exceeds a given range and SN release time; New "Time UE stayed in extended cell" IE with extended range.

[0022] According to another aspect, the present object is achieved by providing a method implemented by an SN for handling communications, such as handling a UHI, in a wireless communication network. The SN obtains a UHI associated with a PSCell to which a UE is connected and provides the obtained UHI for the UE to an MN. The SN can add one or more of the following to the UHI: -Timestamps in UHI and An optional timestamp that is used only if the "UE time spent in the cell" exceeds a given range; Repeated entries when the "UE stays in cell" range is exceeded, An optional timestamp that is used only if the "UE stayed in cell" time exceeds a given range and SN release time; New "Time UE stayed in extended cell" IE with extended range.

[0023] According to yet another aspect, this object is achieved by providing a MN and a SN configured to carry out the methods herein.

[0024]

[0010] Accordingly, provided herein is an MN for handling communications in a wireless communication network. The MN is configured to obtain a UHI associated with a PCell of a UE and to obtain, from a secondary node, a further UHI associated with a connected PSCell of the UE. The MN is then further configured to correlate the obtained UHI and the obtained further UHI with a list of associated PCells and PSCells.

[0025] Further provided herein is an SN for handling communications in a wireless communication network, configured to obtain a UHI associated with a PSCell to which a UE is connected and to provide the obtained UHI for the UE to an MN.

[0026] Further provided herein is a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods herein, as performed by the MN or SN, respectively. Further provided herein is a computer-readable storage medium having stored thereon a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods herein, as performed by the MN or SN, respectively.

[0027] The proposed solution enables correlation of PCell and PSCell information at the MN, for example, by using timestamps, the time the UE has stayed in the cell, and / or both. Currently, no strategy exists for correlation of PCell and PSCell information at the MN. One option would also enable correlation of PCell and PSCell information without requiring synchronization between two network nodes. Thus, embodiments herein may provide a mechanism for improving performance in wireless communication networks.

[0028] Embodiments will now be described in more detail with reference to the accompanying drawings. [Brief explanation of the drawings]

[0029] [Figure 1] 1 is a schematic diagram illustrating a wireless communication network according to an embodiment herein; [Figure 2] 1 is a combined signaling scheme and flow chart according to an embodiment herein; [Figure 3] 1 is a combined flowchart according to an embodiment of the present disclosure. [Figure 4] 1 is a flowchart illustrating a method performed by a MN according to an embodiment herein. [Figure 5] 1 is a flowchart illustrating a method performed by an SN, according to an embodiment herein. [Figure 6] FIG. 2 is a block diagram illustrating a MN according to an embodiment of the present specification. [Figure 7] FIG. 2 is a block diagram illustrating a SN according to an embodiment herein. [Figure 8] 1 illustrates a schematic representation of a telecommunications network connected to a host computer via an intermediate network. [Figure 9] FIG. 1 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection. [Figure 10] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 11] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 12] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 13] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. DETAILED DESCRIPTION OF THE INVENTION

[0030] The embodiments herein are described within the context of 3GPP NR radio technology (3GPP TS 38.300 V15.2.0(2018-06)). It is understood that the problems and solutions described herein are equally applicable to radio access networks and user equipment (UE) implementing other access technologies and standards. NR is used as an exemplary technology for which the embodiments are preferred, and therefore, using NR in the description is particularly useful for understanding the problems and solutions that solve them. In particular, the embodiments are also applicable to 3GPP LTE, also referred to as non-standalone NR, or the integration of 3GPP LTE and NR.

[0031]

[0003] Embodiments herein generally relate to wireless communication networks. Figure 1 is a schematic diagram illustrating a wireless communication network 1. The wireless communication network 1 comprises one or more RANs and one or more CNs. The wireless communication network 1 may use one or several different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE Advanced, Fifth Generation (5G), Wideband Code Division Multiple Access (WCDMA), Pan European System for Mobile Communications / Enhanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name a few possible implementations. Although embodiments herein relate to recent technology trends of particular interest in the 5G context, the embodiments are also applicable in further evolutions of existing wireless communication systems, such as WCDMA and LTE.

[0032] In the wireless communication network 1, wireless devices such as mobile stations, non-access point (non-AP) STAs, STAs, user equipment, and / or wireless terminals, e.g., UEs 10, communicate with one or more core networks (CNs) via one or more access networks (ANs), e.g., RANs. It should be understood by those skilled in the art that "UE" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, machine-type communication (MTC) device, device-to-device (D2D) terminal, or node, e.g., a smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even small base station, capable of communicating using wireless communication with a network node within an area served by the network node.

[0033] The wireless communication network 1 comprises a first radio network node 12 providing radio coverage over a first service area 11 of a radio access technology (RAT), such as LTE, Wi-Fi, or the like, which is a geographical region. The radio network node 12 may be a transmitting and receiving point, e.g., a radio network node such as a wireless local area network (WLAN) access point or access point station (AP STA), an access node, an access controller, a base station, a radio base station such as a Node B, an evolved Node B (eNB, eNodeB), a gNode B (gNB), a base transceiver station, a radio remote unit, an access point base station, a base station router, a radio base station transmission arrangement, a standalone access point, or any other network unit or node capable of communicating with UEs in the area served by the first network node 12, e.g., depending on the radio access technology and terminology used. The radio network node 12 may alternatively or additionally be a controller node or a packet processing node, such as a radio controller node or the like. The first radio network node 12 may be referred to as a serving network node or master node (MN) 12, the first cell may be referred to as a serving cell or primary cell (PCell), and the serving network node communicates with the UE 10 in the form of DL transmissions to the UE 10 and UL transmissions from the UE 10.

[0034] The wireless communication network 1 comprises a second radio network node 13 providing radio coverage over a second service area 14 of a radio access technology (RAT), such as LTE, Wi-Fi, or the like, which is a geographical region. The radio network node 13 may be a transmitting and receiving point, e.g., a radio network access node such as a wireless local area network (WLAN) access point or access point station (AP STA), an access node, an access controller, a base station, e.g., a radio base station such as a Node B, an evolved Node B (eNB), a gNode B (gNB), a base transceiver station, a radio remote unit, an access point base station, a base station router, a radio base station transmission arrangement, a standalone access point, or any other network unit or node capable of communicating with UEs in the area served by the second radio network node 13, e.g., depending on the radio access technology and terminology used. The second radio network node 13 may alternatively or additionally be a controller node or a packet processing node, such as a radio controller node or the like. The second radio network node 13 may be referred to as a secondary node (SN) 13 or a secondary serving network node, and the second service area may be referred to as a secondary serving cell or primary secondary cell (PSCell), and the SN communicates with the UE 10 in the form of DL transmissions to the UE 10 and UL transmissions from the UE 10 in the DC.

[0035] It should be noted that the service area may be expressed as a cell, beam, beam group, or the like to define an area of ​​wireless coverage.

[0036] The new IE "Timestamp" in the SN UHI can be useful for correlation. However, the above problem exists without the timestamp in the MN UHI. Also, using the timestamp instead of the legacy "UE stayed in cell time" requires time synchronization between the MN and the SN when the MN needs to perform correlation between the PCell list and the PSCell list. The embodiments herein enable the MN to select the correct PCell entry under which the acquired PSCell entry is to be entered.

[0037] This can be achieved through five different options. Option A: Timestamps within two UHIs Option B: Optional timestamp used only if the "UE time spent in cell" exceeds a given range Option C: Repeated entries when the "UE stayed in cell" range is exceeded Repeated entries in the UHI means multiple consecutive PSCell entries with the same PSCell ID under the same PCell entry. The first PSCell entry with the "UE stayed in cell" parameter is set to the maximum value. The last entry with the "UE stayed in cell" parameter is set to the remaining time the UE has stayed in this PSCell. Option D: Optional timestamp used only if the "UE time spent in cell" exceeds a given range and SN release time · Option E: New "Time UE stayed in extended cell" IE with extended range.

[0038] The proposed solution enables correlation of PCell and PSCell information at the MN, for example, by using timestamps, the time the UE has stayed in the cell, and / or both. Currently, no strategy exists for correlation of PCell and PSCell information at the MN. One option would also enable correlation of PCell and PSCell information without requiring synchronization between two network nodes. Thus, embodiments herein may provide a mechanism for improving performance in wireless communication networks.

[0039] 2 is a combined flowchart and signaling scheme according to an embodiment of the present disclosure. Actions may be performed in any suitable order.

[0040] Action 201. The MN 12 obtains the UHI of one or more cells.

[0041] Action 202.SN13 obtains the UHI of one or more cells.

[0042] Action 203. The SN 13 then provides the obtained UHI to the MN 12 periodically or on demand.

[0043] Action 204. The MN 12 correlates the obtained UHI with a correlation list of UHIs of different cells for the UE 10. According to some embodiments herein, a timestamp, an optional timestamp, a repeated entry, and an extended IE can be used for correlation.

[0044] Action 205. The MN 12 may then use the correlation list to improve mobility. For example, it may select a preferred combination of PCell and PSCell for good coverage and / or find problems with some cell combinations. The MN 12 may decide whether to implement dual connectivity for the UE 10 based on the correlation list. The MN 12 may provide the correlation list to another network node to handle the mobility of the UE 10.

[0045] 3 is a combined flowchart and signaling scheme according to an exemplary embodiment of the present disclosure. Actions may be performed in any suitable order.

[0046] Action 101a: The master node 12 collects PCell information for each UE and stores it in a list. This list may consist of previously obtained PSCell information listed under the appropriate PCell information. Each entry for the PCell caps the IE "Time spent by UE in cell" at a value of X seconds, beyond which it is set to X.

[0047] Action 101b: The secondary node 13 collects and stores the PSCell information of each UE as a list. This list may contain old entries sent by the PCell during SN addition. The SN modifies this list with information obtained during dual connectivity operation. Similar to the PCell entries, each PSCell entry has the IE "Time spent by UE in cell" capped at a value Y seconds, beyond which it is set to Y. This list is then sent to the MN 12 for correlation with the PCell entries.

[0048] Action 102: When the MN 12 receives the PSCell list from the SN 13, it must separate the PSCell entries and properly insert them into the PCell entries corresponding to the time when both were active, i.e., the MN 12 correlates the UHI. This can be done by different solutions.

[0049] Option A: Timestamps in both MN UHI and SN UHI Action 103a: The MN 12 compares the timestamp in the PCell list with the timestamp in the received PSCell list, evaluates to which PCell and PSCell the UE 10 is simultaneously connected, and inserts one or more PSCell entries under the appropriate one or more PCell entries. This is applicable to different scenarios: All PSCell entries with timestamps between the old and new PCell timestamps are inserted into the old PCell entry. If all PSCell entries have a newer timestamp than the latest PCell entry, then all PSCell entries are inserted into the last / latest PCell entry; If all PSCell entries have an older timestamp than the oldest PCell entry, the newest PSCell entry is inserted into all PCell entries, which may lead to the remaining PSCell entries being discarded.

[0050] Option B: Optional timestamp used only if the "UE time spent in cell" exceeds a given range Action 103b: The MN 12 and SN 13 insert an optional timestamp into the PCell / PSCell entry, respectively. This is done independently by the MN 12 if the UE has stayed in the PCell for longer than a predetermined range X (time the UE has stayed in the cell).

[0051] Similarly, the SN 13 inserts an optional timestamp into the PSCell information if the UE 10 has stayed in the PSCell for longer than a predetermined range Y "time the UE has stayed in the cell".

[0052] Then, once the MN 12 acquires the SN UHI, it performs the following for UHI correlation. · The MN 12 uses the combination of the "time the UE stayed in the cell" and the timestamp to obtain the actual time spent by the UE in the cell. The MN 12 then performs the action performed in action 103a to correlate the PCell and PSCell information.

[0053] Option C: Repeated entry when "UE stay time in cell" exceeds X / Y range Action 103c: If the range IE "Time spent by the UE in the cell" or "Time spent by the UE in the cell extension granularity" in either the MN 12 or the SN 13 is exceeded, the appropriate entry is repeated with a new "Time spent by the UE in the cell". This information is then used to:

[0054] Option D: Optional timestamp used only if the "UE stayed in cell time" exceeds a predetermined range and SN release time. Action 103d: The MN 12 and SN 13 each insert an optional timestamp into the PCell / PSCell entry. This is done independently by the MN 12 if the UE 10 has stayed in the PCell for longer than a predetermined range X (time the UE has stayed in the cell). The timestamp corresponds to the time when the connection was successfully established.

[0055] Similarly, the SN 13 inserts an optional timestamp into the PSCell information if the UE 10 has stayed in the PSCell for longer than a predefined range Y (time the UE has stayed in the cell) and a PSCell change has occurred. The timestamp corresponds to the time of the PSCell connection.

[0056] The MN 12 may then independently calculate the actual time spent in each cell without requiring synchronization between the two nodes.

[0057] Option E: A new "UE stayed in extended cell" IE with extended range. Action 103e: The UHI has a new IE with an extended range compared to the legacy to allow for a longer duration. This new IE is inserted only if the UE 10 has stayed in the PSCell for longer than a predefined range Y (time the UE has stayed in the cell).

[0058] Therefore, the embodiments herein assume a dual connection scenario with the UE 10 connected to the MN 12 and the SN 13. When the UE 10 is connected to different PCells and PSCells, the MN 12 and the SN 13 independently collect related information. After a certain period of time, the MN 12 has a list with PCell information, and the SN 13 has a list with PSCell information. The following list shows examples of combinations where the UE 10 stays for a short time and a long time, and the time that exceeds the "UE stays in cell" limit. Cells that have exceeded the time limit are indicated with * for better understanding.

[0059] The UE 10 connects to a set of PCell entries for the following times: PCell A: Time 10:00:00 to 10:50:00 PCell B: Time 10:50:00 to 12:00:00 PCell C: Time 12:00:00 to 12:40:00 Pcell B: From 12:40:00 to the correlation time (12:50:00)

[0060] At the same time, the UE 10 is connected to the following PSCells: PSCell A: Time 10:00:00 to 10:02:00 PSCell B time 10:02:00 to 10:42:00 PSCell C: Time 10:42:00 to 12:10:00 PSCell A: From 12:10:00 to SN release at 12:40:00

[0061] MN and SN list cell information independently as shown below. TIFF0007739598000001.tif31170

[0062] The above list is then correlated using various options as described in Section 3.

[0063] Option A: The MN 12 and SN 13 can insert a timestamp into each entry indicating the time of the successful cell connection, which can then be used for correlation. TIFF0007739598000002.tif31170TIFF0007739598000003.tif31170

[0064] When the SN 13 transmits PSCell information, the MN 12 constructs a correlated PCell PSCell list as follows: TIFF0007739598000004.tif66170

[0065] Option B: The SN 13 inserts a timestamp into the entry that exceeds the time that the UE has stayed. TIFF0007739598000005.tif31170

[0066] The MN 12 may correlate the UHIs of the PCell and the PSCell by using an optional timestamp and time in the MN 12 to construct a correlated UHI. TIFF0007739598000006.tif66170

[0067] Option C: MN12 and SN13 can repeat the entry if the IE exceeds the 4095 limit. TIFF0007739598000007.tif36170

[0068] The MN 12 can correlate the UHI of the PCell and the PSCell by using the time stayed by the UE 10 as follows. TIFF0007739598000008.tif81170

[0069] Option D: The SN 13 may insert a timestamp into the entry that exceeds the time the UE stayed. The timestamp corresponds to the time of the successful time. The SN 13 also inserts a timestamp of the SN release. This does not require clock synchronization between the two nodes. TIFF0007739598000009.tif74170

[0070] The SN 13 sends the SN release time to the MN 12, which the MN 12 can use to obtain the actual time spent in each cell for correlation with the following equation:

[0071] For entries in the PCell list: Actual time in cell = correlation time at MN - optional timestamp - time to stay in all future cells.

[0072] For entries in the PSCell list: actual time in cell = SN release time - optional timestamp - time to stay in all future cells. TIFF0007739598000010.tif31170TIFF0007739598000011.tif31170

[0073] The MN 12 may then use the information to construct a correlated UHI similar to option B.

[0074] Possible implementations of different options for correlation Option B: Possible implementations Below is a possible implementation of the method described for Option B, bold text: In this example, the Last Visited NG-RAN Cell Information IE found in TS 38.413 is extended with an optional timestamp.

[0075] 9.3.1.97 Last visited NG-RAN cell information This IE contains information about the cell. For an NR cell, this IE contains information about a set of NR cells that have the same NR Absolute Radio Frequency Channel Number (ARFCN) relative to reference point A, and the Global Cell ID IE identifies one of the NR cells in the set. This information should be used for radio resource management (RRM) purposes. TIFF0007739598000012.tif139170

[0076] In another possible implementation, this additional timestamp may be added to the new Last Visited NG-RAN PSCell Information IE.

[0077] Option D: Possible implementations Below is a possible implementation of the method described for option D, bold text. In this example, the UE History Information IE found in TS 38.413 is extended with an optional SN release timestamp. Similarly, the Last Visited NG-RAN Cell Information IE found in TS 38.413 is extended with an optional cell change timestamp.

[0078] 9.3.1.97 Last visited NG-RAN cell information This IE contains information about the cell. For an NR cell, this IE contains information about the set of NR cells that have the same NR ARFCN for reference point A, and the Global Cell ID IE identifies one of the NR cells in the set. This information should be used for RRM purposes. TIFF0007739598000013.tif132170

[0079] In another possible implementation, this additional PSCell change timestamp may be added to the new last visited NG-RAN PSCell Information IE.

[0080] 9.3.1.95 UE History Information This IE contains information about the cell in which the UE was actively served before the target cell. TIFF0007739598000014.tif64170

[0081] In another possible implementation, an additional release timestamp can be added to a new Last Visited NG-RAN PSCell Information IE, or to the SN UE History Information. The additional timestamp may also be added to the Last Visited Cell Information IE found in TS 38.413.

[0082] Option E Possible Implementations Below is a possible implementation of the method described for option C, bold text: In this example, the Last Visited NG-RAN Cell Information IE found in TS 38.413 is extended with an optional time IE that the UE has stayed in the extended cell.

[0083] 9.3.1.97 Last visited NG-RAN cell information This IE contains information about the cell. For an NR cell, this IE contains information about the set of NR cells that have the same NR ARFCN for reference point A, and the Global Cell ID IE identifies one of the NR cells in the set. This information should be used for RRM purposes. TIFF0007739598000015.tif143170

[0084] In another possible implementation, this additional PSCell change timestamp may be added to the new last visited NG-RAN PSCell Information IE.

[0085] 4, the actions of a method performed by the MN 12 for handling communications or UHI in the wireless communication network 1 according to an embodiment will now be described. The actions do not have to be performed in the order set out below, but may be performed in any suitable order. Actions performed in some embodiments are marked with dotted boxes.

[0086] Action 400. The MN 12 acquires the UHI associated with the PCell of the UE 10. The MN 12 may acquire the UHI of the PCell information and / or the PSCell information.

[0087] Action 401. The MN12 may add a timestamp in the UHI, an optional timestamp that is used only if the time the UE stayed in the cell-IE exceeds a predetermined range, a repeat entry when the range of the time the UE stayed in the cell-IE is exceeded, an optional timestamp that is used only if the time the UE stayed in the cell-IE exceeds a predetermined range and the SN release time, and / or an extended time the UE stayed in the cell-IE with an extended range.

[0088] Action 402: The MN 12 acquires a further UHI related to the connected PSCell of the UE 10 from the SN 13. The MN 12 may acquire the UHI of the PSCell information and / or the PCell information. The acquired further UHI may include a timestamp in the further UHI, an optional timestamp used only when the time the UE has stayed in the cell-IE exceeds a predetermined range, a repeated entry when the range of the time the UE has stayed in the cell-IE exceeds a predetermined range and an SN release time, and / or an extended time the UE has stayed in the cell-IE with an extended range.

[0089] Action 403. The MN 12 then correlates the acquired UHI and the acquired further UHI with a list of associated (or connected) PCells and PSCells. Thus, the MN 12 can correlate the PCell list with the PSCells such that the PSCells that are served to the UE 10 at the same time as the PCell are together in the correlation list.

[0090] According to embodiments herein, MN12 may be based on a correlation to: Timestamps within the UHI. Timestamps within two UHIs. "Time the UE stayed in the cell" - an optional timestamp that is used only if the IE exceeds a given range, Repeated entries when the range of the "UE stayed in cell" IE is exceeded, "Time the UE stayed in the cell" - an optional timestamp that is used only if the IE exceeds the given range and SN release time, "Time the UE has stayed in the extended cell" IE with extended range.

[0091] Therefore, depending on whether the MN 12 and / or SN can add these timestamps, optional timestamps, repeat entries, and / or new IEs when collecting the UHI (shown by dashed boxes in actions 401 and 402), the obtained UHI may include the timestamps, optional timestamps, repeat entries, and / or new IEs.

[0092] Action 404. The MN 12 may then use the correlation list to handle communications such as mobility, DC, or the like for the UE 10. The MN 12 may use the correlation list to improve mobility for the UE 10 or other UEs. For example, the MN 12 may select a preferred combination of PCell and PSCell for good coverage and / or find problems with some cell combinations. The MN may decide whether to implement dual connectivity for the UE 10 based on the correlation list.

[0093] Action 405. The MN 12 may provide the correlation list to another network node to handle the mobility of the UE 10.

[0094] The actions of a method performed by the SN 13 for handling communications or UHI in the wireless communication network 1 according to an embodiment will now be described with reference to the flowchart shown in Figure 5. The actions do not have to be performed in the order set out below and may be performed in any suitable order. Actions that are performed in some embodiments are marked with dotted boxes.

[0095] Action 501: The SN 13 obtains further UHI related to the connected PSCell of the UE 10. For example, the SN 13 may obtain UHI of the connected PCell and PSCell for one or more UEs.

[0096] Action 502.SN13 can add the following to the UHI: -Timestamps in UHI, "Time the UE stayed in the cell" - an optional timestamp that is used only if the IE exceeds a given range, Repeated entries when the range of the "UE stayed in cell" IE is exceeded, "Time the UE stayed in the cell" - an optional timestamp that is used only if the IE exceeds the given range and SN release time, "Time the UE has stayed in the extended cell with extended range - IE.

[0097] Action 503. The SN 13 then provides the MN 12 with the UHI obtained for the UE, also referred to as further UHI. The SN 13 may provide a UHI for one or more UEs, including a timestamp, an optional timestamp, a repeat entry, and / or a new IE. The UHI may include: The timestamp in UHI and an optional timestamp that is used only if the UE's time spent in the cell - information element (IE) exceeds a predetermined range; and Repeated entries when the UE stays in the cell - IE range is exceeded, the time the UE has stayed in the cell - an optional timestamp that is used only if the IE exceeds a predetermined range and SN release time; and and the time the UE has stayed in the extended cell—IE, which has an extended range.

[0098] FIG. 6 is a block diagram illustrating a mobile node 12 in two embodiments for handling communications, for example, UHI, in a wireless communication network 1 according to an embodiment of the present specification.

[0099] The MN 12 may comprise processing circuitry 601, eg, one or more processors, configured to perform the methods herein.

[0100] The MN 12 may include an acquiring unit 602, such as a receiver, a collector, or a transceiver. The MN 12, the processing circuit 601, and / or the acquiring unit 602 are configured to acquire a UHI associated with a PCell of the UE 10. The MN 12, the processing circuit 601, and / or the acquiring unit 602 are further configured to acquire a further UHI associated with a connected PSCell of the UE 10 from the SN 13. For example, the MN 12, the processing circuit 601, and / or the acquiring unit 602 may be configured to acquire a UHI of PCell information and / or PSCell information of the MN 12, and acquire a UHI of PSCell information and / or PCell information of the SN 13 from the SN 13.

[0101] The MN 12 may comprise a correlation unit 603. The MN 12, the processing circuit 601, and / or the correlation unit 603 are configured to correlate the obtained UHI and the obtained further UHI with a list of associated (or connected) PCells and PSCells. The MN 12, the processing circuit 601, and / or the correlation unit 603 may be configured to correlate the UHI with a list of connected PCells and PSCells.

[0102] The MH 12, the processing circuit 601, and / or the correlation unit 603 may: The timestamp in UHI and an optional timestamp that is used only if the UE's time spent in the cell - information element (IE) exceeds a predetermined range; and Repeated entries when the UE's time spent in the cell exceeds the range of the IE; the time the UE has stayed in the cell - an optional timestamp that is used only if the IE exceeds a predetermined range and SN release time; and The acquired UHI may be configured to correlate the acquired further UHI based on one or more of the following: the time the UE has stayed in the extended cell—IE, which has an extended range; and

[0103] The MN 12 may be configured to add in the UHI a timestamp, an optional timestamp that is used only if the time the UE stayed in the cell-IE exceeds a predetermined range, a repeat entry when the range of the time the UE stayed in the cell-IE is exceeded, an optional timestamp that is used only if the time the UE stayed in the cell-IE exceeds a predetermined range and the SN release time, and / or an extended time the UE stayed in the cell-IE with an extended range.

[0104] Therefore, depending on which MN 12 may be configured to add these timestamps, optional timestamps, repeat entries, and / or new IEs when collecting the UHI (indicated by dashed boxes in actions 401 and 402). The obtained further UHI may include the timestamps in the further UHI, the optional timestamps used only when the time the UE stayed in the cell-IE exceeds a predetermined range, the repeat entries when the time the UE stayed in the cell-IE exceeds a range, the optional timestamps used only when the time the UE stayed in the cell-IE exceeds a predetermined range and the SN release time, and / or the time the UE stayed in the extended cell-IE with an extended range. Thus, the obtained UHI may include the timestamps, optional timestamps, repeat entries, and / or new IEs.

[0105] The MN 12 may include an implementing unit 604, such as a scheduler, a transmitter, or a transceiver. The MN 12, the processing circuit 601, and / or the implementing unit 604 may be configured to use the correlation list to handle communications of the UE 10. The MN 12, the processing circuit 601, and / or the implementing unit 604 may be configured to use the correlation list by determining whether to implement dual connectivity for the UE 10 based on the correlation list. The MN 12, the processing circuit 601, and / or the implementing unit 604 may be configured to provide the correlation list to another network node to handle mobility of the UE 10.

[0106] The MN 12, the processing circuit 601, and / or the implementation unit 604 may be configured to use or provide correlation lists for handling communications, such as mobility, DC, or the like, to one or more UEs.

[0107] The MN 12 further comprises a memory 607. The memory comprises one or more units used to store data such as instructions, timestamps, correlation lists, priorities, RSs, strengths or qualities, UL grants, instructions, requests, commands, timers, applications that, when executed, perform the methods disclosed herein, and the like. Thus, the MN may comprise a processing circuit and a memory, the memory including instructions executable by the processing circuit, whereby the MN operates to perform the methods disclosed herein. The MN 12 comprises a communication interface 608, which comprises a transmitter, a receiver, a transceiver, and / or one or more antennas.

[0108] The methods according to the embodiments described herein for the MN 12 are implemented, for example, by a computer program product 605 or computer program including instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be performed by the MN 12. The computer program product 605 may be stored on a computer-readable storage medium 606, for example, a Universal Serial Bus (USB) stick, a disk, or the like. The computer-readable storage medium 606 having the computer program product stored thereon may comprise instructions that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be performed by the MN 12. In some embodiments, the computer-readable storage medium may be a non-transitory or a transitory computer-readable storage medium.

[0109] FIG. 7 is a block diagram illustrating two embodiments of an SN 13 for handling communications, for example for handling UHI, in a wireless communication network 1 according to embodiments herein.

[0110] The SN 13 may comprise processing circuitry 701, eg, one or more processors, configured to perform the methods herein.

[0111] The SN 13 may comprise an acquisition unit 702, such as a receiver or transceiver, for example. The SN 13, the processing circuit 701, and / or the receiving unit 702 are configured to acquire UHI associated with connected PSCells of the UE 10. Thus, the SN 13, the processing circuit 701, and / or the acquiring unit 702 may be configured to acquire UHI of connected PCells and PSCells for one or more UEs.

[0112] The SN13 may be configured to add a timestamp in the UHI, an optional timestamp that is used only if the time the UE has stayed in the cell-IE exceeds a predetermined range, a repeat entry when the time the UE has stayed in the cell-IE range is exceeded, an optional timestamp that is used only if the time the UE has stayed in the cell-IE exceeds a predetermined range and the SN release time, and / or an extended time the UE has stayed in the cell-IE with an extended range.

[0113] The SN 13 may comprise a transmitting unit 703, e.g., a transmitter or transceiver. The SN 13, the processing circuit 701, and / or the transmitting unit 703 are configured to provide the UHI obtained for the UE 10 to the MN 12. The SN 13, the processing circuit 701, and / or the transmitting unit 703 may be configured to transmit / provide the UHI for one or more UEs, including a timestamp, an optional timestamp, a repeat entry, and / or a new IE. The UHI may be The timestamp in UHI and an optional timestamp that is used only if the time the UE has stayed in the cell—information element (IE)—exceeds a predetermined range; and Repeated entries when the UE's time spent in the cell exceeds the range of the IE; the time the UE has stayed in the cell - an optional timestamp that is used only if the IE exceeds a predetermined range and SN release time; and and the time the UE has stayed in the extended cell—IE, which has an extended range.

[0114] The SN 13 further comprises a memory 705. The memory comprises one or more units used to store data such as instructions, timestamps, UHI, strength or quality, grants, scheduling information, timers, applications that when executed perform the methods disclosed herein, and the like. Thus, an SN may comprise processing circuitry and memory, the memory including instructions executable by the processing circuitry whereby the SN operates to perform the methods disclosed herein.

[0115] The SN 13 comprises a communication interface 708 that comprises a transmitter, a receiver, a transceiver and / or one or more antennas.

[0116] Methods according to embodiments described herein for SN 13 are implemented, for example, by a computer program product 706 or computer program including instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be performed by SN 13. The computer program product 706 can be stored on a computer-readable storage medium 707, such as a USB stick, a disk, or the like. The computer-readable storage medium 707 having the computer program product stored thereon may comprise instructions that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be performed by SN 13. In some embodiments, the computer-readable storage medium may be a non-transitory or a transitory computer-readable storage medium.

[0117] In some embodiments, the more general term "radio network node" is used, which can correspond to any type of radio network node or any network node that communicates with wireless devices and / or other network nodes. Examples of network nodes include Node B, master eNB, secondary eNB, network nodes belonging to a master cell group (MCG) or a secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio nodes such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), access point (AP), transmission point, transmitting node, remote radio unit (RRU), remote radio head (RRH), node in a distributed antenna system (DAS), core network nodes such as mobility switching center (MSC), mobile management entity (MME), operation and maintenance (O&M), operation support system (OSS), self-organizing network (SON), positioning node such as evolved serving mobile location center (SMLC), drive minimization test (MDT), etc.

[0118] In some embodiments, the non-limiting terms wireless device or user equipment (UE) are used to refer to any type of wireless device that communicates with network nodes and / or other UEs in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, proximity-enabled UEs (also known as ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communications, PDAs, PADs, tablets, mobile terminals, smartphones, laptop embedded equipment (LEEs), laptop mounted equipment (LMEs), USB dongles, etc.

[0119] The embodiments are described for 5G. However, the embodiments are applicable to any RAT or multi-RAT system in which a UE receives and / or transmits signals (e.g., data), such as, for example, LTE, LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi-Fi, WLAN, CDMA2000, etc.

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

[0121] Alternatively, some of the functional elements of the described processing means may be provided through the use of dedicated hardware, while others comprise hardware for executing software in association with appropriate software or firmware. Thus, the terms "processor" or "controller" as used herein do not refer exclusively to hardware capable of executing software, but may implicitly include, but are not limited to, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will understand the cost, performance, and maintenance tradeoffs inherent in these design choices.

[0122] 8, according to one embodiment, a communication system includes a telecommunications network 3210, such as a 3GPP-type cellular network, comprising an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs, or other types of wireless access points, which are examples of radio network nodes 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c can be connected to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) 3291, an example of a UE 10, located in the coverage area 3213c is configured to wirelessly connect to or be paged by the corresponding base station 3212c. A second UE 3292 within the coverage area 3213a can wirelessly connect with the corresponding base station 3212a. While multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or is connected to the corresponding base station 3212.

[0123] The telecommunications network 3210 is itself connected to a host computer 3230, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connection 3221, 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may proceed via an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them; if present, the intermediate network 3220 may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more subnetworks (not shown).

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

[0125] An exemplary implementation of the UE, base station, and host computer described in the previous paragraph, according to one embodiment, will now be described with reference to FIG. 9. In the communication system 3300, the host computer 3310 comprises hardware 3315, including a communication interface 3316 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311, which is stored on or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330, connecting via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data that is transmitted using the OTT connection 3350.

[0126] The communications system 3300 further includes a base station 3320 provided in the telecommunications system, the base station 3320 comprising hardware 3325 that enables the base station 3320 to communicate with the host computer 3310 and the UE 3330. The hardware 3325 may include a communications interface 3326 for setting up and maintaining wired or wireless connections with interfaces of different communications devices of the communications system 3300, as well as a wireless interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in FIG. 9 ) served by the base station 3320. The communications interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct, or alternatively, the connection 3360 may pass through a core network of the telecommunications system (not shown in FIG. 9 ) and / or one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

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

[0128] It should be noted that the host computer 3310, base station 3320, and UE 3330 illustrated in Figure 9 may be equivalent to the host computer 3230, one of the base stations 3212a, 3212b, and 3212c, and one of the UEs 3291 and 3292, respectively, of Figure 8. That is, the internal workings of these entities may be as shown in Figure 9, and separately, the surrounding network topology may be that of Figure 8.

[0129] 9, the OTT connection 3350 is depicted abstractly to show communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to intermediary devices and the precise routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to be hidden from the UE 3330, the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0130] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments can improve performance because mobility can be handled more efficiently, which can provide benefits such as reduced user latency and better responsiveness.

[0131] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 3350 may be implemented in software 3311 of the host computer 3310 or in software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 3350 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above or other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 3350 can include message formats, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the base station 3320, and the reconfiguration may be unknown or unrecognizable to the base station 3320. Such procedures and functions may be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling that facilitates the host computer 3310 measurements of throughput, propagation time, latency, and the like. Measurements may be implemented in causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 3350 while software 3311, 3331 monitors propagation times, errors, etc.

[0132] FIG. 10 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 8 and 9. To simplify this disclosure, only a drawing reference to FIG. 10 is included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits the user data carried in the host computer-initiated transmission to the UE, according to the teachings of embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0133] FIG. 11 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 8 and 9. To simplify this disclosure, only a drawing reference to FIG. 11 is included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may be via a base station in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0134] FIG. 12 is a flowchart illustrating a method implemented in a communications system, according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be those described with reference to FIGS. 8 and 9. To simplify this disclosure, only drawing references to FIG. 12 are included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In optional sub-step 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes the client application, which provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in optional third sub-step 3630. In a fourth step 3640 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0135] 13 is a flowchart illustrating a method implemented in a communications system, according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 8 and 9. To simplify this disclosure, only drawing references to FIG. 13 are included in this section. In an optional first step 3710 of the method, the base station receives user data from the UE, in accordance with the teachings of embodiments described throughout this disclosure. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in a transmission initiated by the base station.

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

Claims

1. A method implemented by a master node (12) for handling communications in a wireless communication network (1), comprising: Obtaining (400) user equipment historical information (UHI) associated with a primary cell (PCell) of a user equipment (UE) (10); Obtaining (402) from a secondary node (13) a further UHI associated with a connected primary secondary cell PSCell of said UE (10); Correlating the obtained UHI and the obtained further UHI with a list of associated PCells and PSCells (403); Including, The correlating comprises: The time that the UE has stayed in the cell - an optional timestamp that is used only if the information element (IE) exceeds a predetermined range; Repeated entries when the UE stays in the cell for longer than the IE range; an optional timestamp that is used only if the UE's time spent in a cell—IE exceeds the predetermined range and SN release time; and the time the UE has stayed in the extended cell-IE, which has an extended range.

2. Adding the optional timestamp to be used only when the Time UE Stayed in Cell-IE exceeds the predetermined range, the repeating entry when the range of the Time UE Stayed in Cell-IE is exceeded, the optional timestamp to be used only when the Time UE Stayed in Cell-IE exceeds the predetermined range and SN release time, and / or the Time UE Stayed in an extended cell-IE with the extended range (401). The method of claim 1 further comprising:

3. 2. The method of claim 1, wherein the obtained further UHI comprises the optional timestamp used only when the UE has stayed in a cell—time IE exceeds the predetermined range, the repeated entries when the UE has stayed in a cell—time IE exceeds the predetermined range and SN release time, and / or the optional timestamp used only when the UE has stayed in an extended cell—IE with the extended range.

4. using the correlation list to handle communications of the UE (10) (404); The method of claim 1 further comprising:

5. 5. The method of claim 4, wherein said using (404) comprises determining whether to implement dual connectivity for said UE (10) based on said correlation list.

6. providing (405) the correlation list to another network node for handling the mobility of said UE (10); The method of claim 1 further comprising:

7. A method implemented by a secondary node (13) for handling communications in a wireless communication network (1), comprising: Obtaining (501) User Equipment Historical Information (UHI) associated with a connected Primary Secondary Cell (PSCell) of a User Equipment (UE) (10); providing (503) the obtained UHI for the UE to a master node (12); Including, The UHI is The time that the UE has stayed in the cell - an optional timestamp that is used only if the information element (IE) exceeds a predetermined range; Repeated entries when the UE stays in the cell for longer than the IE range; an optional timestamp that is used only if the UE's time spent in a cell—IE exceeds the predetermined range and SN release time; and a time that the UE has stayed in the extended cell-IE, the time having the extended range.

8. adding the optional timestamp used only when the UE's time spent in a cell—IE exceeds the predetermined range, the repeated entries when the UE's time spent in a cell—IE exceeds the range, the optional timestamp used only when the UE's time spent in a cell—IE exceeds the predetermined range and SN release time, and / or the UE's time spent in an extended cell—IE with the extended range (502); The method of claim 7 further comprising:

9. A master node (12) for handling communications in a wireless communication network (1), the master node (12) being configured to perform the method according to any one of claims 1 to 6.

10. A secondary node (13) for handling communications in a wireless communication network (1), the secondary node (13) being configured to perform a method according to claim 7 or 8.

11. 7. A computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 6, implemented by the master node.

12. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to claim 7 or 8, performed by the secondary node.

13. 7. A computer-readable storage medium having stored thereon a computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 6 as implemented by the master node.

14. A computer-readable storage medium storing a computer program including instructions that, when executed on at least one processor, cause the at least one processor to execute a method according to claim 7 or 8, which is performed by the secondary node.

Images