CN112314048A - Access method for radio access network traffic, user equipment, base station equipment, and non-transitory computer-readable medium - Google Patents

Abstract

A method for accessing radio access network service, and user equipment, base station equipment and storage device for implementing the method are provided. A first network entity provides an indicator to a second network entity, wherein the indicator records a network communication protocol used by the first network entity. The second network entity communicating with the first network entity according to the indicator; wherein the first network entity and the second network entity are not aware of each other's network communication protocol in advance.

Description

Access method for radio access network traffic, user equipment, base station equipment, and non-transitory computer-readable medium

Technical Field

The present invention relates to wireless communication systems, and more particularly, to an apparatus and method for enabling a wireless communication device, such as a User Equipment (UE) or a mobile device to Access a Radio Access Technology (RAT) or a Radio Access Network (RAN), and more particularly, but not exclusively, to Integrated Access Backhaul (IAB).

Background

Wireless communication systems, such as the third generation mobile communications standard (3G) and technology, are known in the art. These 3G standards and technologies were developed by the third generation partnership project (3GPP) organization. The third generation of wireless communications has evolved to generally support Macro-cell (Macro-cell) mobile phone communications. Both communication systems and networks have evolved towards broadband and mobile systems.

The third generation partnership project has developed the so-called long term evolution system (LTE), an evolved universal terrestrial radio access network (E-UTRAN), for a mobile access network in which one or more macro cells are supported by a base station called an evolved node b (eNodeB or eNB). More recently, LTE has evolved further into a so-called fifth generation (5G) or New Radio (NR) system, in which one or more cells are supported by a base station called a gNB.

IAB related access techniques are described in TR 38.84, NR creates an opportunity to deploy IAB links to provide UE access services in order to obtain more available bandwidth in an existing deployment of massive multiple-input multiple-output (MIMO) or multi-beam systems. Fig. 1 shows a schematic example of a network with IAB links, in which relay nodes can switch ACCESS (ACCESS) and BACKHAUL (BACKHAUL) links in time, frequency or space (e.g. beam steering) in a multitasking manner.

The relay base system must be designed for NR. A Relay Node (RN) requires a low cost and low power design to be quickly and easily deployed when needed. Such nodes may be deployed in many scenarios: coverage is expanded in rural areas, urban hotspots with enhanced capacity to cope with high density of users, indoor hotspots with high data traffic, etc. The relay-based system may also provide wireless backhaul connectivity to the core network.

Various existing radio relay technologies based on the advanced long term evolution (LTE-a) layer three relay standard are shown in fig. 2. Such relays may improve throughput by eliminating inter-cell interference and noise generated by first layer only relays. In the downlink case, the third layer relays demodulating and decoding the received frequency modulated (RF) signal, followed by data processing (e.g., encryption and user data concatenation/segmentation/reassembly) to retransmit the user data to the mobile station (user equipment UE) after further encoding/modulation on a radio interface. These functions are similar to the base station.

Fig. 3 shows a communication protocol stack for implementing LTE-a layer three relay technology in a radio network architecture. The functions performed by the physical layer (PHY), the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) sublayer are all found in the LTE system standard TS 36.300.

In the NR system, the specification of the MAC/RLC/PDCP sublayer corresponding to the PHY layer is in the TS 38.300 file.

A Service Data Adaptation Protocol (SDAP) sublayer is also added to support quality of service (QOS) in mapping data packets of Protocol Data Unit (PDU) sessions to the correct radio bearers based on service specific quality flow identifiers supported by the proprietary SDAP defined by TS 37.324.

Another possible way to link LTE user equipment to the IAB system is also a deployment scenario that is attractive to NR mobile operators. Backhaul for LTE access is achieved by connecting an NR relay node to a Donor base station (DeNB) via E-UTRAN relaying as specified in TS 36.300. The DeNB will have access to the core network.

Technical problem

When designing a relay node for NR, when an NR ue is connected to an NR relay node, relaying at the third layer is not problematic. Both SDAP parties have the ability to process the removed SDAP headers, properly recover and transmit Internet Protocol (IP) packets without the need for additional headers.

However, when an LTE UE is connected to an NR relay node, in the uplink, for example, when a PDCP data packet is received from the UE, the NR relay node is supposed to regard the packet as the NR base rather than the LTE base, so it cannot be identified that the SDAP header does not actually exist. There is originally no SDAP protocol in LTE. The packet is nevertheless processed by the SDAP protocol handler so that the portion of the packet where the SDAP header is expected is removed. As a result, the first byte of the PDCP packet containing the sequence number is removed, so that the NR relay node cannot transmit the uplink PDCP packet to the core network in sequence.

Similar behavior is expected to occur in the downlink. When a PDCP data packet is received from the NR relay node, the UE is determined to consider the packet as an LTE base rather than an NR base, so that the fact that an SDAP header exists cannot be recognized. Since there is originally no SDAP protocol in LTE. Nevertheless, the packet is passed through a PDCP protocol handler to cause the portion of the SDAP header (consisting of RDI + RQI + QFI) expected to be interpreted. The interpreted result must of course be erroneous. As a result, the UE cannot deliver the downlink PDCP packets to the higher layers of the IP protocol in sequence.

In view of the above, the problem can be summarized as when an LTE ue is connected to an NR relay node, IP packets cannot be guaranteed to be transmitted sequentially because of protocol stack mismatch.

This specification seeks to address at least some of the above issues.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This abstract 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 accessing a Radio Access Network (RAN) service, so that a radio communication device can access an access service provided by a RAN. Wherein a first network entity and a second network entity are not aware of each other's network communication protocol in advance. Providing an indicator to a second network entity by a first network entity, wherein the indicator records a network communication protocol used by the first network entity; and

the second network entity knows the network communication protocol of the first network entity according to the indicator so as to communicate with the first network entity.

Preferably, the first network entity and the second network entity use different network communication protocols, and the indicator is based on a hierarchy of the different network communication protocols.

Preferably, the indicator is based on a hierarchy difference suggested to the second network entity.

Preferably, the indicator includes a header indicating whether a network protocol of one of the network entities exists or lacks a layer structure.

Preferably, the indicator indication includes system information indicating a nature of a network communication protocol of the first network entity.

Preferably, the indicator is a packet type indicator indicating a network communication protocol of a packet.

Preferably, upon receiving the indicator, the second network entity reselects the other first network entity if the indicator indicates that the first network entity does not support one of the network communication protocols.

Preferably, one of the network communication protocols is LTE

Preferably, one of the network communication protocols is NR

Preferably, wherein the network communication protocol of the second network entity is WLAN

Preferably, the indicator prevents misinterpretation of data exchanges for communication between network entities.

Preferably, the RAN is a new radio/5G network.

According to a second aspect of the present invention, there is provided an apparatus, which may be a user equipment or a base station device, including a processor, a storage unit and a communication interface, wherein the processor, the storage unit and the communication interface are configured to perform the RAN service access method.

According to a third aspect of the present invention, there is provided a non-transitory computer readable medium comprising computer readable instructions for causing a processor to perform the RAN service access method as described above. The non-transitory computer readable medium may comprise at least one of the group of: hard disk, CD-ROM, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, an electrically erasable programmable read-only memory, and flash memory.

Advantageous effects

Embodiments of the present description provide an indicator that prevents misinterpretation of data exchanges for communications between network entities.

Drawings

Further details, aspects and embodiments of the present description will be described, purely by way of example, with reference to the accompanying drawings. The components in the figures are shown by way of illustration only and not in true scale. For example, the corresponding reference numerals have been added to the illustrations for ease of understanding only.

Fig. 1 is an architecture diagram of an IAB link.

Fig. 2 is an architecture diagram of a third layer relay.

Fig. 3 is a communication protocol stack for a layer three relay.

Fig. 4 is a simplified flow diagram of SDAP header setting in an embodiment of the present description.

Fig. 5 is a simplified flowchart illustrating the internal operation of the relay node RN according to an embodiment of the present disclosure.

Fig. 6 is a simplified flowchart of an LTE ue accessing NR according to an embodiment of the present disclosure.

Fig. 7 is an architecture diagram of the network nodes exchanging permission information when the LTE user equipment accesses the NR according to the embodiment of the present disclosure.

Fig. 8 is a simplified flow diagram of non-NR PDU indication for an embodiment of the present description.

Detailed Description

Those skilled in the art will understand and appreciate that the examples provided herein are merely exemplary embodiments and that they may be implemented in a variety of different configurations.

This specification relates to enabling a mobile device to access a RAN according to the so-called 3GPP New Radio (NR) technology, as defined by TS 38.300 NR and next generation RAN (NG-RAN) in general and TS 38.401 NG-RAN in architectural descriptions.

More specifically, the present description relates to the access method of the IAB described in the TR 38.874 document. To enable more available bandwidth in deployments with already large numbers of MIMO or multi-beam systems, NR creates an opportunity to deploy IAB links to provide UE access services.

The present specification is directed to a method and system to control access procedures from a mobile device to an NR integrated network, also considering that the UE may have radio capabilities other than NR, such as LTE.

The control method is performed depending on whether the LTE user equipment is allowed to be accessed. Broadly speaking, the following are several solutions to address this problem: in a control layer based solution, the LTE ue may be attached with an SDAP configuration that lacks an uplink/downlink SDAP header.

In another proposal, when the NR relay node scheme is adopted, the use of the SDAP protocol in the LTE user equipment is avoided, for example, the NR relay node is configured to consider the SDAP configuration in the LTE user equipment as lacking an uplink/downlink SDAP header.

In another further proposal according to NR deployment, an indicator is provided to indicate whether a legacy UE is allowed to attach to the NR relay node. This means that there is an indicator to allow the LTE user equipment to transmit.

In a user layer based solution, an adaptation layer may be included in a UE and NR relay node and an indicator may be added to indicate whether the transmitted packet is the NR base. Thereby opening a user layer transport mechanism.

These solutions and technical effects are not mutually exclusive and can be used in combination with each other. A more detailed description is as follows.

The above technical problems and solutions are numbered for ease of reference only and for no other purpose.

Solution 1: an LTE ue is set to an SDAP configuration without an uplink/downlink SDAP profile header.

Solution 2: when the NR relay node is deployed, the use of the SDAP protocol in the LTE user equipment is avoided, for example, the NR relay node is determined to consider the SDAP configuration in the LTE user equipment as lacking an uplink/downlink SDAP header.

Solutions 1 and 2 do not imply the use of new signalling in the system, but may add extra content to the existing signalling.

Solution 3: in NR non-standalone (NSA) deployments, NR is associated with other non-NR cells, such as LTE cells, which may transmit an indicator to an LTE user equipment allowing transmission of LTE packets on an NG-Uu (radio interface between BS and UE). Such an indicator may be part of an LTE broadcast (system information or proprietary signaling in NSA deployments). In contrast, in NR-only deployments, such indicators should be part of the NR broadcast or proprietary signaling.

A deployment that withstands future trials should allow any UE to connect. The deployment of NR relay nodes therefore tends to consider first the use of an indicator to reject connections for non-NR user equipment. The advantage of this solution is that for the UE it is possible to transmit LTE data to an NR network, which is not done conventionally. While this solution may prevent unnecessary access from the UE when the NR backhaul does not in fact support relaying of LTE data. The UE may reselect cells to access an LTE relay node, avoiding the possibility of access being denied by an NR relay node.

Solution 4 is to add an indicator at an adaptation layer in the UE and the NR relay node to indicate whether the packet is based on NR. This solution avoids interaction with the control layer. Therefore, the LTE relay node has the advantages over the control layer, and LTE data can be transmitted without changing the configuration of the UE in advance as long as the LTE user equipment is connected to the NR relay node at any time. Since the present solution does not require configuration/parameters and there is no mechanism to prevent LTE ues from connecting to the NR relay node, there is no guarantee that packets are transmitted sequentially.

The above-mentioned several solutions will again be discussed in more detail. The Core Network referred to herein is a functional representation and may in fact be understood as a Network entity from the Core Network (a so-called access and mobility management function (AMF)), a 5G Core User Plane (UPF) as defined in TS 38.300, or an entity allowing access to the Core Network (CN) (a donor eNB accessible to E-UTRAN as described in TS 36.300). The "LTE data" represents an LTE packet transfer procedure that can handle both data and signaling.

Figure 4 shows an embodiment of solution 1 where the SDAP configuration of the LTE user equipment is configured without uplink/downlink SDAP header.

In step 1, before data transmission with the UE, for example, when the UE is connected to the relay node RN, the relay node RN configures the UE without an SDAP header for uplink/downlink data transmission. Step 2 shows the configuration setting. According to this configuration, the UE is still informed of the permission of LTE transmission in the NR relay node RN. In step 3, the UE does not include any SDAP header when transmitting data in step 3a, according to the configuration of step 2. The relay node RN decodes the LTE header in the LTE data and transfers the IP data therein to the CN in step 3 b. The downlink data transmission from the relay node RN is not shown in this figure, however, when the UE receives an LTE transmission from the relay node RN, it will also assume that there is no SDAP header in the received LTE PDU.

Fig. 5 shows an embodiment of solution 2, which avoids using the SDAP protocol in the LTE ue when deploying the NR relay node RN, for example, making the NR relay node RN default to the SDAP configuration in the LTE ue as lacking an uplink/downlink SDAP header.

In step 1, the UE performs LTE transmission to the NR relay node RN. The UE knows that this transmission is possible through some means, such as the embodiment of solution 3. The NR relay node RN, upon receiving this transmission, may detect whether the transmitted packet is based on the LTE protocol (e.g. according to the embodiment of solution 4). In step 1a, the NR relay node RN recognizes that the SDAP header does not exist for the transmission of step 1a, directly decodes the LTE protocol header in step 1b, and transmits the IP data to the CN in step 1 c.

In step 2, the relay node RN wraps the IP data according to the LTE protocol and forwards the IP data to the UE without adding any SDAP header, and then packet forwarding is performed in step 2 b.

Fig. 6 shows an embodiment of solution 3 where the UE receives a unique indicator indicating that LTE access through NR is allowed. In step 1, the UE receives an indicator from the NR or an LTE cell indicating that LTE access through NR is allowed. The UE may also receive an indicator indicating which relay node RN entity (in the form of a physical cell identity) supports such access. Upon receiving the indicator, the UE determines that LTE transmissions are allowed at the RN entity for the relay node. In step 2, the UE performs LTE transmission. When receiving the LTE transmission, the relay node RN performs step 2b to unwrap the LTE protocol header, and transmits the IP data to the CN in step 2 c.

Fig. 7 shows another embodiment of solution 3, where information allowing access to LTE through NR is exchanged in the network node. NR uses a donor node (DgNB) to modify the NG-Nu radio interface, referred to as NG-Uu¹Wirelessly connected to a gNB to support relay functionality. This is NR relay node RN case 1 in fig. 7. To support backhaul for LTE access, the NR relay node RN connects to a donor ng-ENB (Dnb-ENB) that connects wirelessly to the ng-ENB to terminate user and control layer protocols provided to the UE. This is NR relay node RN case 2 in fig. 7.

An NR relay node RN may be connected to both a DgNB and an Dng-eNB, thereby providing EN-DC (E-UTRA NR dual connectivity) or NE-DC (NR E-UTRA dual connectivity) configurations to UEs. This is case 1 and case 2 hosted by the same relay node RN in fig. 7. The donor nodes provide NG and Xn proxy functions between the relay node RN and other network nodes (eNB, nb-eNB, CN entity), the proxy functions being included in NG¹And Xn¹Transferring UE specific NG and Xn signalling information and GPRS channel protocol GTP number over the interfaceAnd (7) packaging according to the packet. So-called NG¹And Xn¹I.e. a modification of the NG and Xn interfaces.

In a NR relay node RN start-up procedure, the relay node RN first attaches a relay node RN pre-configuration, and then attaches the relay node RN to operate according to a donor node list in the relay node RN pre-configuration. Whether the donor node supports LTE backhaul in the donor node list is based on an indicator indicating whether the donor node is a DgNB connected to the gNB or a Dnb-eNB connected to the ng-eNB. According to the indicator, during the operation of the additional relay node RN, the NR relay node RN may select a donor node that supports and/or does not support LTE backhaul according to whether the NR relay node RN allows the LTE ue to connect.

In case at least one or none of the donor nodes support LTE backhaul, the NR relay node RN may indicate in step 1 in the manner discussed in scheme 3 whether LTE access is supported or not. According to an indicator, the LTE user equipment reselects other relay nodes RN supporting LTE access as much as possible. Therefore, unnecessary online can be avoided, and the relay node RN which does not support LTE is accessed and rejected.

Fig. 8 shows an embodiment of solution 3, where an indicator of the transmission type is carried by the transmitted packet. In step 1, in LTE transmission, the UE provides an indicator. Various types of LTE transmissions may be made by the UE transmitting an NR PDU, wrapping an LTE PDU, and providing an "LTE base data indicator" message in the NR PDU header, informing that the LTE PDU is embedded. From such information, the relay node RN judges that not the NR PDU but the LTE PDU is transmitted. The header of the LTE protocol is then unpacked in step 1b and the IP data is transmitted to the CN in step 1 c.

In LTE transmissions from the relay node RN to the UE, this type of indicator may not be necessary because the UE knows that it can receive the transmission from the relay node RN (e.g., step 2/2a/2b of solution 2). The present specification provides a range of possible solutions, individually or in combination, to prevent protocol mismatch, enabling successful exchange of IP packets between different types of networks, such as between an LTE user equipment and an NR relay node RN.

It is understood that the present description is also applicable to other similar situations, such as enabling a WLAN user equipment to access an IAB through an NR relay node.

Although details of components forming the network device or apparatus are not disclosed in detail, such as a processor, a storage unit, and a communication interface configured to perform the various methods disclosed herein, further options and options are described below. The signaling processing functions described in the embodiments of the present specification, particularly the gNB and the UE, may be implemented by computing systems or architectures known to those skilled in the art. The computing system may be a desktop, laptop, handheld device (PDA, cell phone, palm device, etc.), mainframe, server, client, or any other type of general purpose computing device capable of performing a particular application or environment, and should be understood to be within the scope of the appropriate application. The computing system may include one or more processors implemented by a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.

The computing system may also include a main memory, such as a Random Access Memory (RAM) or other volatile storage for storing information and instructions to be executed by the processor. Such main memory may also be used for storing temporary variables or other intermediate information during execution of instructions by the processor. Computing systems may likewise include a Read Only Memory (ROM) or other static storage device for storing static information and commands for the processor.

The computing system may also include an information storage system that 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 disk drive (CD) or Digital Video Drive (DVD) read-write drive (R or RW), or other removable or fixed media drive. The 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 a media drive. The storage media may include a computer-readable storage medium having stored therein particular computer software or data.

In alternative embodiments, the 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, removable storage units and interfaces such as program cartridges and cartridge interfaces, removable storage (e.g., flash memory or other removable memory modules) and memory slots, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computing system.

The computing system may also include a communication interface. Such a communication interface may be used to allow software and data to be transferred between the computing system and external devices. Examples of a communication interface may include a modem, a network interface (e.g., an ethernet or other NIC card), a communication port (e.g., a Universal Serial Bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via the communications interface are in the form of electronic signals, electromagnetic, optical, or other signals capable of being received by the 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 memory, storage devices, or storage units. These and other forms of computer-readable media may store one or more instructions for use by a processor comprising a computer system, to cause the processor to perform specified operations. These instructions, when executed, are generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), enable the computing system to perform functions of embodiments of the present invention. Note that the code may directly cause the processor to perform specified operations, be compiled to perform the specified operations, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to perform the specified operations.

The non-transitory computer readable medium may comprise at least one of the group of: hard disk, CD-ROM, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, an electrically erasable programmable read-only memory, and flash memory.

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

Furthermore, the inventive concept is applicable to any circuit that performs a signal processing function within a network component. It is further contemplated that a semiconductor manufacturer may use the inventive concept in the design of a stand-alone device such as a microcontroller or Application Specific Integrated Circuit (ASIC) of a Digital Signal Processor (DSP) and/or any other subsystem component, for example.

It will be appreciated that the above description, for clarity, describes embodiments of the invention with reference to a single processing logic. The inventive concept may, however, be equally implemented by a plurality of different functional units and processors to provide the signal processing functions. Hence, 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 organization.

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 modular components such as FPGA devices. Thus, the components and elements 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 invention is limited only by the attached 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 e.g. a single unit or processor. Furthermore, although individual features may be included in different claims, these may possibly advantageously be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Furthermore, 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. Furthermore, 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 invention is limited only by the attached 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" or "comprises" does not exclude the presence of other elements.

Claims (13)

1. An access method of a Radio Access Network (RAN) service, comprising:

providing an indicator to a second network entity by a first network entity, wherein the indicator records a network communication protocol used by the first network entity; and

the second network entity communicates with the first network entity according to the indicator, wherein the first network entity and the second network entity have no prior knowledge of each other's network communication protocol.

2. The RAN service access method of claim 1, wherein:

the first network entity and the second network entity use different network communication protocols; and

the indicator is based on a layered structure of different network communication protocols.

3. The RAN service access method of claim 1 or 2, wherein:

the indicator is based on the difference in the layer structure suggested to the second network entity.

4. The RAN service access method of any preceding claim, wherein:

the indicator includes a header to indicate whether a network communication protocol of one of the network entities has a presence or absence of a layer structure.

5. The RAN service access method of any preceding claim, wherein:

the indicator indication includes system information indicating a nature of a network communication protocol of the first network entity.

6. The RAN service access method of any preceding claim, wherein:

the indicator is a packet type indicator indicating a network communication protocol of a packet.

7. The RAN service access method of any preceding claim, wherein:

upon receiving the indicator, the second network entity reselects the other first network entity if the indicator indicates that the first network entity does not support one of the network communication protocols.

8. The RAN service access method of any preceding claim, wherein one of the network communication protocols is LTE.

9. A RAN service access method according to any preceding claim, wherein one of the network communication protocols is NR.

10. The RAN service access method of claim 9, wherein the network communication protocol of the second network entity is WLAN.

11. A user equipment comprising a processor, a memory unit, and a communication interface, wherein the processor, the memory unit, and the communication interface are configured to perform the RAN service access method of claims 1-10.

12. A base station device comprising a processor, a memory unit, and a communication interface, wherein the processor, the memory unit, and the communication interface are configured to perform the RAN service access method of claims 1-10.

13. A non-transitory computer readable medium comprising computer readable instructions for causing a processor to perform the RAN service access method of claims 1-10.

Images