GB2572754A

GB2572754A - Access to Integrated Access Backhaul

Info

Publication number: GB2572754A
Application number: GB1805667.1A
Authority: GB
Inventors: Jactat Caroline
Original assignee: TCL Communication Ltd
Current assignee: TCL Communication Ltd
Priority date: 2018-04-05
Filing date: 2018-04-05
Publication date: 2019-10-16
Anticipated expiration: 2038-04-05
Also published as: WO2019192329A1; GB2572754B; GB201805667D0; CN112314048A; CN112314048B

Abstract

A network protocol of a transmitting entity and a receiving entity of a Radio Access Network (RAN) are initially unknown to one another. A first entity of the transmitting entity or the receiving entity provides an indicator to the other entity indicative of the network protocol of the first entity. The other entity is enabled to recognise the network protocol of the first entity from the indicator and then operates in accordance with the indicated network protocol when in communication with the first entity. The indicator may be based on a layer structure of the different protocols and the indicator may be based on a layer structure difference which is indicated to the other entity. For instance this difference may be indicating that one entity supports the Service Data Adaption Protocol (SDAP) layer. The indicator may be in the form of a header which specifies whether a later structure is absent or present in the protocol of one of the entities. One protocol may be LTE © or New Radio (NR).

Description

Technical Field

Embodiments of the present invention generally relate to wireless communication systems and in particular to devices and methods for enabling a wireless communication device, such as a User Equipment (UE) or mobile device to access a Radio Access Technology (RAT) or Radio Access Network (RAN), particularly but nor exclusively to integrated access backhaul.

Background

Wireless communication systems, such as the third-generation (3G) of mobile telephone standards and technology are well known. Such 3G standards and technology have been developed by the Third Generation Partnership Project (3GPP). The 3^rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications. Communication systems and networks have developed towards a broadband and mobile system.

The 3rd Generation Partnership Project has developed the so-called Long Term Evolution (LTE ™) system, namely, an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, (E-UTRAN), for a mobile access network where one or more macro-cells are supported by a base station known as an eNodeB or eNB (evolved NodeB). More recently, LTE is evolving further towards the so-called 5G or NR (new radio) systems where one or more cells are supported by a base station known as a gNB.

Access to Integrated Access Backhaul is described in TR 38.874 where due to expected larger bandwidth availability along with native deployment of massive Multiple Input Multiple Output (ΜΙΜΟ) or multi-beam systems, NR creates an opportunity to deploy integrated access and backhaul links for providing access to UEs. An illustration example of a network with such integrated access and backhauls links is shown in Figure 1, where relay nodes can multiplex access and backhaul links in time, frequency, or space (e.g. beam-based operation).

Relay based systems are to be designed for NR. A relay node is designed to be low cost and lower power so that it can be easily and quickly deployed when needed. Such nodes can be deployed in several scenarios: in rural areas to enhance the coverage, urban hotspots to enhance the capacity in order to cope with the high user density, indoor hotspots to achieve high data throughput, etc. Relay based systems also provide wireless backhaul connection to the Core Network.

Various radio relay technologies exist among which Relay technology in LTEAdvanced is based on a Layer 3 relay as depicted by Figure 2. Such a relay can improve throughput by eliminating inter-cell interference and noise caused by a Layer 1 only relay. Thus, in the downlink case, the Layer 3 relay performs demodulation and decoding of Radio Frequency (RF) signals received, and then goes on to perform processing (such as ciphering and user-data concatenation/segmentation/reassembly) for retransmitting user data on a radio interface and further performs encoding/modulation and transmission to the Mobile Station (UE). Such functions are similar to that of the base station.

In terms of Protocol stack, the radio network architecture for achieving Layer 3 relay technology in LTE Advanced is shown in Figure 3. The functions performed by the physical layer, Medium Access Control (MAC)/ Radio Link Control (RLC)/ Packet Data Convergence Protocol (PDCP) sublayers can be found in TS 36.300 for LTE system.

For NR system, the counterparts of the physical layer, MAC/RLC/PDCP sublayers are described in TS 38.300.

In addition, a Service Data Adaptation Protocol (SDAP) sublayer is added above PDCP to support Quality of Service (QoS) in mapping the data packets of a protocol data unit (PDU) session onto the right radio bearer based on dedicated QoS Flow identifier information supported by dedicated SDAP protocol as defined in TS 37.324.

There is also the possibility for an LTE UE to connect to the Integrated Access and Backhaul (IAB) system, which is an attractive deployment use case for a NR mobile operator. Support of backhauling of LTE access can be achieved by having an NR relay node (RN) connected to a Donor eNB (DeNB) as used in relaying for E-UTRAN as per TS 36.300. The DeNB would give access to the Core Network.

Upon designing an RN for NR, when an NR UE connects to NR RN, there is no issue in Layer 3 relaying. SDAP by either side would handle SDAP header removal so IP packets can be properly recovered and transmitted without the additional header.

However, when an LTE UE is connected to NR RN, in the uplink i.e. upon receipt of a PDCP data packet from the UE, the NR RN considering the packet is NR based and not LTE based, would not be aware that SDAP header is actually not present. There is actually no such SDAP protocol in LTE. Nevertheless, the packet would go through the SDAP protocol in which the presumed SDAP header would be removed. As a result, the first byte including part of the sequence number of the PDCP packet would be removed. Consequently, the NR RN would not be able to deliver the uplink PDCP packets in-sequence towards the Core Network.

A similar behaviour can be expected for the downlink. Upon receipt of a PDCP data packet from the NR RN, the UE considering the packet is LTE based and not NR based, would not be aware that SDAP header is actually present. There is actually no such SDAP protocol in LTE. Nevertheless, the packet would go through PDCP protocol wherein the presumed SDAP header (made up of RDI+RQI+QFI) would be interpreted as PDCP header. This is of course incorrect behaviour. As a result, the UE would not be able to deliver the downlink PDCP packets in-sequence towards the IP upper layers.

Based on the above, the problem can be formulated as: due to protocol stack mismatch, in-sequence delivery of IP packets is not ensured when LTE UE connects to a NR RN.

The present invention is seeking to solve at least some of the outstanding problems in this domain.

Summary

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

According to a first aspect of the present invention there is provided a method for enabling a wireless communication device to access services provided by a Radio

Access Network, in which a network protocol of a transmitting entity and a receiving entity are initially unknown to one another, the method comprising: a first entity of the transmitting entity or the receiving entity providing an indicator to the other entity indicative of the network protocol of the first entity such that the other entity is enabled to recognise the network protocol of the first entity from the indicator and to operate in accordance therewith when in communication with the first entity.

Preferably, the transmitting entity and the receiving entity are operating on different network protocols and wherein the indicator is based on a layer structure of the different protocols.

Preferably, the indicator is based on a layer structure difference which is indicated to the other entity.

Preferably, the indicator comprises a header indicating a layer structure is absent or present in the protocol of one of the entities.

Preferably, the indicator includes system information for indicating the nature of the protocol of the first entity.

Preferably, the indicator is a packet type indicator that indicates the protocol of the packet.

Preferably, upon receipt of the indicator, the receiving entity can reselect to another transmitting entity if the indicator indicates some network protocol is not supported by the transmitting entity.

Preferably, one protocol is LTE.

Preferably, one protocol is NR.

Preferably, the protocol of the other entity is WLAN.

Preferably, the indicator avoids misinterpretation of data exchanged in the communication between the entities.

Preferably, the Radio Access Network is a New Radio/5G network.

According to a second aspect of the present invention there is provided an equipment, such as a BS or UE, comprising a processor, a storage unit and a communications interface, wherein the processor unit, storage unit, and communications interface are configured to perform the method of another aspect.

According to a third aspect of the present invention there is provided a non-transitory computer readable medium having computer readable instructions stored thereon for execution by a processor to perform the method of another aspect of the present invention.

The non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.

Brief description of the drawings

Further details, aspects and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. Like reference numerals have been included in the respective drawings to ease understanding.

Figure 1 is a simplified diagram showing integrated access and backhaul links.

Figure 2 is a simplified diagram showing a layer 3 relay.

Figure 3 is a simplified diagram showing a protocol stack from a layer 3 relay

Figure 4 is a simplified diagram showing an SDAP header configuration, according to an embodiment of the present invention.

Figure 5 is a simplified diagram showing an RN internal implementation, according to an embodiment of the present invention.

Figure 6 is a simplified diagram showing an LTE access via NR, according to an embodiment of the present invention.

Figure 7 is a simplified diagram showing an LTE access via NR in which allowed information is exchanged between network nodes, according to an embodiment of the present invention.

Figure 8 is a simplified diagram showing a non NR PDU indication, according to an embodiment of the present invention.

Detailed description of the preferred embodiments

Those skilled in the art will recognise and appreciate that the specifics of the examples described are merely illustrative of some embodiments and that the teachings set forth herein are applicable in a variety of alternative settings.

The present invention relates to access from a mobile device to a radio access network based on so called 3GPP NR (New Radio) technology, a defined in TS 38.300 NR and the Next Generation Radio Access Network (NG-RAN) overall description and TS 38.401 NG-RAN architecture description.

Specifically, the present invention relates to access to Integrated Access Backhaul described in TR 38.874 where due to expected larger bandwidth availability along with native deployment of massive ΜΙΜΟ or multi-beam systems, NR creates an opportunity to deploy integrated access and backhaul links for providing access to UEs.

The invention is intended to provide a method and system to control access from the mobile device to the NR integrated network, also considering the UE can have other radio capability than NR (e.g. LTE).

Such control is performed according to whether access to the LTE UE is allowed. In broad terms the following possible solutions can be used to address the problem: a control plane based solutions can configure the LTE UE with an SDAP configuration including SDAP-Header-Down Link (DL)/Uplink (UL) is absent. In an alternative proposal: NR RN implementation is adopted to avoid using SDAP protocol for an LTE UE i.e. NR RN internally considers the SDAP configuration for the LTE UE to include SDAP-Header-DL/UL is absent. A further proposal depends on NR deployment schemes, an indication of whether legacy UE is allowed to connect to NR RN or not. This means that there is an indication that the LTE UE is allowed to transmit LTE data 6 on a NR network. A user plane based solutions can include an adaptation layer in the UE and NR RN in which an indication is added based on whether or not the packet is NR based. This enables a user plane transmission mechanism.

These solutions and technical effects are not intended to be exclusive and can be used in combination to complement each other as will be described below in greater detail.

For ease of reference and for no other reason the possible solutions to the above described technical problems are numbered as follows.

Solution 1: configure the LTE UE with an SDAP configuration including SDPA-HeaderDL/UL is absent.

Solution 2: NR RN implementation to avoid using SDAP protocol for an LTE UE i.e. NR RN internally considers the SDAP configuration for the LTE UE to include SDAPHeader-DL/UL is absent. Solution 1 and 2 do not imply additional new signalling to the system however may rely on existing signalling with potential additional overheads.

Solution 3: In NR Non Standalone deployments where NR is associated with another non NR cell e.g. LTE cell, the LTE cell would indicate to LTE UE that it is allowed to transmit LTE packets over NG-Uu (the radio interface between BS and UE). Such indication as part of LTE broadcast (e.g. System Information (SI)) or dedicated signalling in a Non-standalone (NSA) deployment.

Conversely, in NR Standalone deployments, such indication should to be part of NR broadcast (e.g. SI) or dedicated signalling.

A future proof deployment could be to allow any UE to connect. Hence the first NR RN deployments would rather consider an indication to disallow non NR UE to connect. This solution has the advantage for the UE to know that LTE data can be transmitted onto an NR network, which basically should not have been the case. Also such solution avoids unnecessary access from the UE if NR backhaul does not actually support relaying of LTE data. The UE could then make a cell reselection to an (LTE) relay node instead of accessing such NR Relay Node and potentially be rejected from such access.

Solution 4: is an adaptation layer in the UE and NR RN which adds an indication of whether or not the packet is based on NR. This solution avoids interaction with control plane. This has advantage over control plane solutions above that LTE data can be transmitted whenever the LTE UE is connected to NR RN which does not need to configure the UE beforehand.

Without the proposed configuration/parameter, an LTE UE would connect to NR RN because there is no means preventing the UE to do so. As a consequence, insequence delivery would be no more be ensured.

The above-mentioned solutions will now be discussed in greater detail. Where a Core Network (CN) is represented, it will be appreciated that it can be functionally: an entity from a Core Network (a so called Access and Mobility Management Function (AMF)); a User Plane Function (UPF) for 5G Core as defined in TS 38.300; or an entity (similar to Donor eNB for E-UTRAN access as per TS 36.300) allowing access to a CN. “LTE data” represents an LTE packet transmission which can deal with data or signalling.

Figure 4 illustrates an embodiment for so called Solution 1, where the LTE UE is configured with SDAP-Header-DL/UL absence within the SDAP configuration.

At step 1, ahead of data transmission with a UE e.g., when the UE connects to the RN, the RN configures the UE to apply no SDAP header for uplink and downlink data transmission, which configuration is provided at step 2. Based on this configuration, the UE is also informed that LTE transmission is allowed on the NR RN. At step 3, based on the configuration at step 2, the UE does not include any SDAP header upon transmitting data based on LTE protocol at step 3a. The RN extracts the LTE protocol headers at step 3b to forward the IP data to CN. Downlink data transmission from the RN is not shown in this Figure however when the UE receives LTE transmission from the RN, the UE should consider that no SDAP header is present in the received LTE PDU.

Figure 5 illustrates the embodiment of so called Solution 2 where the NR RN implementation avoids using SDAP protocol for an LTE UE i.e. NR RN internally considers the SDAP configuration for the LTE UE to include SDAP-Header-DL/UL is absent.

At step 1, the UE performs LTE transmission to the NR RN. The UE is aware by some means (e.g. based on the embodiment of Solution 3) that such a transmission is possible. Upon receipt of the transmission, the NR RN is able to detect that the transmitted packet is based on LTE protocol (e.g. based on the embodiment of Solution 4). The NR RN then considers there is no SDAP header at step 1a and extracts the LTE protocol headers at step 1 b to forward the IP data to CN at step 1 c.

At step 2, IP data is transmitted to the UE via the RN which encapsulates the IP data based on LTE protocol and does not add any SDAP header ahead of forwarding the LTE transmission to the UE at step 2b.

Figure 6 illustrates the embodiment of so called Solution 3 where the UE receives an explicit indication that LTE access via NR is allowed. At step 1, the UE receives an indication from the NR or an LTE cell that LTE access via NR is allowed. The UE can be also receive an indication as to which RN entity (in the form of e.g. a Physical Cell Identity) supports such access. Upon receipt of the indication, the UE considers LTE transmission is allowed and potentially onto which RN entity. At step 2, the UE performs LTE transmission. Upon receipt of such transmission, RN extracts the LTE protocol headers at step 2b to forward the IP data to CN at step 2c.

Figure 7 illustrates another embodiment of Solution 3 where the LTE access via NR allowed information is exchanged between network nodes. NR supports relaying in having a Donor gNB (DgNB) may be wirelessly connected to the gNB via a modification of the NG-Uu radio interface called NG-Uu’. This is NR RN Case 1 in the Figure 7. To support backhauling of LTE access, the NR RN connects to a Donor ng-eNB (DngeNB) wirelessly connected to the ng-eNB providing E-UTRA user plane and control plane protocol terminations towards the UE. This is NR RN Case 2 in the Figure.

A given NR RN can be simultaneously connected to a DgNB and a Dng-eNB, thus providing ΕΝ-DC (E-UTRA NR dual connectivity) or NE-DC (NR E-UTRA dual connectivity) configuration to a UE. This is both NR RN Case 1 and Case 2 in the Figure hosted by the same RN. The Donors provide NG and Xn proxy functionality between the RN and other network nodes (gNBs, ng-eNBs, Core Network (CN) entities), such proxy functionality includes passing UE-dedicated NG and Xn signalling messages and GPRS Tunnelling Protocol GTP data packets along with the NG’ and

ΧιΤ interfaces, NG’ and Xn’ being modifications based on NG and Xn interfaces respectively.

During an NR RN start-up procedure, the RN firstly attaches for RN pre-configuration and then attaches for RN operation based on Donors list provided at pre-configuration. Within the Donors list, whether the Donor supports LTE backhauling would be indicated depending on whether the Donor is a DgNB connected to gNB or a Dng-eNB connected to ng-eNB. Based on the indication, during the attach for RN operation, the NR RN can select a Donor supporting LTE backhauling and/or a Donor not supporting LTE backhauling depending on whether the NR RN allows the LTE LIE to connect.

Where at least one or none of the Donors supports LTE backhauling, then NR RN can indicate whether LTE access is supported or not as discussed above with reference to Solution 3, step 1. Based on the indication, the LTE UE would reselect to another RN supporting LTE access if possible. This has an advantage of avoiding a connection to an RN not supporting LTE access and rejection by such RN.

Figure 8 illustrates the embodiment of so called Solution 4 where an indication of transmission type is provided along with the transmitted packet. At step 1, upon LTE transmission, the UE provides an indication thereof. A variant of the LTE transmission can be that the UE transmits an NR PDU encapsulating an LTE PDU and provides in the NR PDU header the “LTE based data indicator” information that an LTE PDU is embedded. Based on such information, the RN infers that an RN PDU is not transmitted but an LTE PDU is. Then the RN extracts the LTE protocol headers at step 1 b to forward the IP data to CN at step 1c.

This type of indication may not be necessary for LTE transmission from the RN by the UE where the UE knows it can receive such transmission from the RN (e.g. based on Solution 2, steps 2/2a/2b).The present invention provides a number of possible solutions either alone or in combination which prevents protocol stack mismatching and enables the successful delivery of IP packets between different types of network, for example between an LTE UE and an NR RN.

It will be appreciated that the present invention may apply to other similar situations, such as for example: WLAN UE accessing the IAB via NR RN.

Although not shown in detail any of the devices or apparatus that form part of the network may include at least a processor, a storage unit and a communications interface, wherein the processor unit, storage unit, and communications interface are configured to perform the method of any aspect of the present invention. Further options and choices are described below.

The signal processing functionality of the embodiments of the invention especially the gNB and the UE may be achieved using computing systems or architectures known to those who are skilled in the relevant art. Computing systems such as, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment can be used. The computing system can include one or more processors which can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.

The computing system can also include a main memory, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by a processor. Such a main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor. The computing system may likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for a processor.

The computing system may also include an information storage system which may include, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive. Storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive. The storage media may include a computer-readable storage medium having particular computer software or data stored therein.

In alternative embodiments, an information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. Such components may include, for example, a removable storage unit and an interface , such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to computing system.

The computing system can also include a communications interface. Such a communications interface can be used to allow software and data to be transferred between a computing system and external devices. Examples of communications interfaces can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via a communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface medium.

In this document, the terms ‘computer program product’, ‘computer-readable medium’ and the like may be used generally to refer to tangible media such as, for example, a memory, storage device, or storage unit. These and other forms of computer-readable media may store one or more instructions for use by the processor comprising the computer system to cause the processor to perform specified operations. Such instructions, generally referred to as ‘computer program code’ (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system to perform functions of embodiments of the present invention. Note that the code may directly cause a processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

The non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system using, for example, removable storage drive. A control module (in this example, software instructions or executable computer program code), when executed by the processor in the computer system, causes a processor to perform the functions of the invention as described herein.

Furthermore, the inventive concept can be applied to any circuit for performing signal processing functionality within a network element. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP), or application-specific integrated circuit (ASIC) and/or any other sub-system element.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to a single processing logic. However, the inventive concept may equally be implemented by way of a plurality of different functional units and processors to provide the signal processing functionality. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organisation.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as FPGA devices. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to ‘a’, ‘an’, ‘first’, ‘second’, etc. do not preclude a plurality.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognise that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ or “including” does not exclude the presence of other elements.

Claims

1. A method for enabling a wireless communication device to access services provided by a Radio Access Network, in which a network protocol of a transmitting entity and a receiving entity are initially unknown to one another, the method comprising: a first entity of the transmitting entity or the receiving entity providing a indicator to the other entity indicative of the network protocol of the first entity such that the other entity is enabled to recognise the network protocol of the first entity from the indicator and to operate in accordance therewith when in communication with the first entity.

2. The method of claim 1, wherein the transmitting entity and the receiving entity are operating on different network protocols and wherein the indicator is based on a layer structure of the different protocols.

3. The method of claim 1 or claim 2, wherein the indicator is based on a layer structure difference which is indicated to the other entity..

4. The method of any preceding claim, wherein the indicator comprises a header indicating a layer structure is absent or present in the protocol of one of the entities.

5. The method of any preceding claims, wherein the indicator includes system information for indicating the nature of the protocol of the first entity.

6. The method of any preceding claim, wherein the indicator is a packet type indicator that indicates the protocol of the packet.

7. is. The method of any preceding claim, wherein upon receipt of the indicator, the receiving entity can reselect to another transmitting entity if the indicator indicates some network protocol is not supported by the transmitting entity.

8. The method of any preceding claim, wherein one protocol is LTE.

9. The method of any preceding claim wherein one protocol is NR.

10. The method of claim 9 wherein the protocol of the other entity is WLAN.

11. A user equipment, UE, apparatus comprising a processor, a storage unit and a communications interface, wherein the processor unit, storage unit, and communications interface are configured to perform the method as claimed in any one of claims 1-10.

5

12. A base station, BS, apparatus comprising a processor, a storage unit and a communications interface, wherein the processor unit, storage unit, and communications interface are configured to perform the method as claimed in any one of claims 1-10

13. A non-transitory computer readable medium having computer readable 10 instructions stored thereon for execution by a processor to perform the method according to any of claims 1 -10.