CN112314048B

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

Info

Publication number: CN112314048B
Application number: CN201980018075.3A
Authority: CN
Inventors: 卡罗琳·加科特
Original assignee: JRD Communication Shenzhen Ltd
Current assignee: JRD Communication Shenzhen Ltd
Priority date: 2018-04-05
Filing date: 2019-03-21
Publication date: 2023-09-19
Anticipated expiration: 2039-03-21
Also published as: GB2572754B; GB2572754A; CN112314048A; WO2019192329A1; GB201805667D0

Abstract

An access method for radio access network service, and user equipment, base station equipment and storage device for implementing the method. A first network entity provides an indicator to a second network entity, the indicator describing the network communication protocol used by the first network entity. The second network entity communicates 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 service, user equipment, base station device, and non-transitory computer-readable medium

Technical Field

The present invention relates to wireless communication systems, and more particularly to apparatus 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), and in particular, but not limited to, integrated access backhaul (Integrated Access Backhaul; IAB).

Background

Wireless communication systems, such as third generation mobile communication standards (3G) and technologies are known to the world. These 3G standards and technologies were developed by the third generation partnership project (3 GPP) agency. The development of third generation wireless communication is generally intended to support Macro-cell (Macro-cell) mobile phone communication. 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 (eNodeB or eNB). More recently, LTE has evolved 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.

Access technologies relating to IABs are described in TR 38.84, NR creates an opportunity to deploy IAB links to provide UE access to services in order to obtain more available bandwidth in the deployment of existing massive multiple-input multiple-output (MIMO) or multi-beam systems. Fig. 1 shows a network schematic example with IAB links, in which relay nodes may be multiplexed switch ACCESS (ACCESS) and BACKHAUL (BACKHAUL) links in time domain, frequency domain or space (e.g. beam operation).

The relay base system must be designed for NR. A Relay Node (RN) requires low cost and low power designs to be deployed quickly and easily when needed. Such nodes may be deployed in many contexts: the coverage is expanded in the rural area, urban hot spots with increased capacity in order to cope with high-density users, indoor hot spots with high data traffic, and the like. The relay base system may also provide wireless backhaul for the core network.

Various existing radio relay technologies based on advanced long term evolution (LTE-a) third layer relay standards are shown in fig. 2. Such relays may improve throughput by canceling inter-cell interference and noise generated by first layer only relays. In the downlink case, the third layer relays demodulate and decode the received frequency modulated (RF) signal, followed by data processing (e.g., encryption and user data concatenation/segmentation/reassembly) to further encode/modulate over a radio interface before transmitting the user data again to the mobile station (UE). These functions are similar to those of a base station.

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

In the NR system, the description of the corresponding PHY layer, MAC/RLC/PDCP sub-layer is located in the TS 38.300 file.

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

Another possible way of linking LTE user equipment to an IAB system is also a deployment scenario that is attractive to NR mobile operators. By connecting an NR relay node to a Donor base station (Donor eNB; deNB) as in the E-UTRAN relay established by TS 36.300, backhaul for LTE access can be achieved. The DeNB will have access to the core network.

Technical problem

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

However, when an LTE UE connects to an NR relay node, in the uplink, for example, when receiving a PDCP data packet from the UE, the NR relay node definitely treats the packet as an NR base instead of an LTE base, so that it cannot recognize that the SDAP header does not actually exist. The SDAP protocol is not originally present in LTE. Nevertheless, the packet is passed through the SDAP protocol handler such that the portion of the SDAP header that is expected to be removed. As a result, the first byte of the PDCP packet including the sequence number is removed, so that the NR relay node cannot sequentially transmit the uplink PDCP packet to the core network.

Similar behavior is also expected to occur in the downlink. When a PDCP data packet is received from the NR relay node, the UE is defined as an LTE base instead of an NR base, so the fact that the SDAP header exists cannot be recognized. Since the SDAP protocol is not originally present in LTE. Nevertheless, the packet is passed through a PDCP protocol handler, where the portion of the SDAP header (consisting of rdi+rqi+qfi) is expected to be interpreted. Of course the interpreted result must be erroneous. As a result, the UE cannot sequentially transmit the downlink PDCP packets to higher layers of the IP protocol.

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

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

Disclosure of Invention

This abstract 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 of accessing Radio Access Network (RAN) services, enabling a radio communication device to access services provided by a RAN. Wherein a first network entity and a second network entity are not aware of each other's network communication protocols in advance. Providing an indicator to the second network entity by the first network entity, wherein the indicator records a network communication protocol used by the first network entity; and

the second network entity obtains 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 a layered structure based on the different network communication protocols.

Preferably, the indicator is based on a layer structure difference signaled to the second network entity.

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

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

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

Preferably, upon receipt of 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 air interface/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, comprising a processor, a storage unit and a communication interface, wherein the processor, storage unit and communication interface are arranged to perform the above-described 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 a RAN service access method as described above. The non-transitory computer readable medium may include at least one of the group of: hard disks, CD-ROMs, 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 disclosure provide an indicator that avoids misinterpretation of data exchanges for communications between network entities.

Drawings

Further details, aspects and embodiments of the present description will be illustrated with reference to the drawings, which are given by way of example only. The components in the figures are presented only in a simple manner and are not true to scale. For example, corresponding reference numerals have been added to the drawings for ease of understanding only.

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

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

Fig. 3 is a communication protocol stack of a third layer relay.

Fig. 4 is a simplified flow chart 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 the embodiment of the present invention.

Fig. 6 is a simplified flow diagram of LTE user equipment accessing NR according to an embodiment of the present description.

Fig. 7 is a diagram of an architecture for exchanging permission information between network nodes when an LTE user equipment of an embodiment of the present description accesses an NR.

Fig. 8 is a simplified flow chart of a non-NR PDU indication of 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 of some embodiments and that they may be practiced in a variety of different configuration.

The present description relates to enabling a mobile device to access a RAN according to the so-called 3GPP new air interface (NR) technology, such as the general description defined by TS 38.300NR and the next generation RAN (NG-RAN) and the architectural description of the TS 38.401 NG-RAN.

More precisely, the present description relates to an access method of an IAB described in the TR 38.874 document. In order to be able to obtain a larger available bandwidth in the deployment of existing massive MIMO or multi-beam systems, NR creates an opportunity to deploy IAB links to provide UE access to services.

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

The control method is performed according to whether the LTE user equipment is allowed to be accessed. Broadly, the following are used to address this problem in several ways: 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 employing the NR relay node scheme, the use of the SDAP protocol in the LTE user equipment is avoided, e.g., the NR relay node is caused to define the SDAP configuration in the LTE user equipment as lacking an uplink/downlink SDAP header.

In another proposal, further in accordance with the NR deployment approach, an indicator is provided to indicate whether a legacy UE is allowed to connect to the NR relay node. This means that there is an indicator that the LTE user equipment is allowed to transmit.

In a user layer based solution, an adaptation layer may be included in a UE and in the NR relay node and an indicator is 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. A more detailed description is as follows.

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

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

Solution 2: when deploying the NR relay node, the SDAP protocol is avoided from being used in the LTE user equipment, for example, the NR relay node is caused to define 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 signaling in the system, but may add additional content to the existing signaling.

Solution 3: in NR non-standalone (NSA) deployments, NR and other non-NR cells, e.g. LTE cells, are associated together, which may transmit an indicator to an LTE user equipment, allowing it to transmit LTE packets on a 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 separate deployments, such an indicator should be part of NR broadcast or proprietary signaling.

A deployment that withstands future challenges should allow any UE connection. The deployment of NR relay nodes therefore first tends to consider employing an indicator to reject connections of non-NR user equipment. The advantage of this solution is that LTE data can be transmitted to an NR network for the UE, which is not done in the conventional way. While this solution may prevent unnecessary access from the UE when the NR backhaul does not actually support relay of LTE data. The UE may reselect to a cell to access an LTE relay node while avoiding the possibility of access being denied by the NR relay node.

Solution 4 is to add an indicator to an adaptation layer in the UE and the NR relay node indicating whether the packet is based on NR. This solution avoids interaction with the control layer. So that it has advantages over the control layer, LTE data can be transmitted whenever LTE user equipment is connected to the NR relay node without changing the configuration of the UE in advance. Since the scheme does not need configuration/parameters and there is no mechanism to prevent the LTE ue from connecting to the NR relay node, it cannot be guaranteed that the packets are transmitted sequentially.

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

Fig. 4 shows an embodiment of solution 1, wherein the SDAP configuration of the LTE user equipment is set to have no uplink/downlink SDAP header.

In step 1, before data transmission with UE, for example, when the UE connects to the relay node RN, the relay node RN configures the UE to have no SDAP header for uplink/downlink data transmission. Step 2 shows the configuration setup. According to this configuration, the UE is still informed of the permission to LTE transmissions in the NR relay node RN. In step 3, according to the configuration of step 2, the UE does not include any SDAP header when transmitting data in step 3 a. The relay node RN decodes the LTE header in the LTE data and forwards 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 be assumed that no SDAP header is present in the received LTE PDU.

Fig. 5 shows an embodiment of solution 2, avoiding the use of the SDAP protocol in the LTE user equipment when deploying the NR relay node RN, e.g. having the NR relay node RN define the SDAP configuration in the LTE user equipment as lacking an uplink/downlink SDAP header.

In step 1, the UE performs LTE transmission on the NR relay node RN. It is possible that the UE knows this transmission through some means, e.g. the embodiment of solution 3. Upon receiving this transmission, the NR relay node RN 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 in the transmission in 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 packages the IP data according to the LTE protocol and forwards the data to the UE without adding any SDAP header, and then the packet forwarding is performed in step 2 b.

Fig. 6 shows an embodiment of solution 3, wherein the UE receives a unique indicator indicating that LTE is allowed to be accessed through NR. In step 1, the UE receives an indicator from the NR or an LTE cell indicating that access to LTE through NR is allowed. The UE may also receive an indicator indicating which relay node RN entity (in the form of physical cell identity) supports such access. Upon receipt of the indicator, the UE decides that LTE transmissions are allowed for the relay node RN entity. In step 2, the UE performs LTE transmission. When the relay node RN receives the LTE transmission, it proceeds to step 2b, unwraps the LTE protocol header, and transmits 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 a network node. NR uses a donor node (DgNB) to modify the NG-Nu radio interface, called NG-Uu ¹ Wirelessly connects 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 is wirelessly connected to the ng-ENB to terminate user layer 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 a Dng-eNB, thereby providing an EN-DC (E-UTRA NR dual connectivity) or NE-DC (NR E-UTRA dual connectivity) configuration to the UE. This is case 1 and case 2, which are 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 the NG ¹ And Xn ¹ UE-specific NG and Xn signaling information and GPRS channel protocol GTP data packets are transmitted over the interface. So-called NG ¹ And Xn ¹ I.e. a modification of the NG and Xn interfaces.

In an NR relay node RN start-up procedure, the relay node RN first appends a relay node RN pre-configuration and then appends a relay node RN operation according to a donor node list pre-configured by the relay node RN. In the donor node list, whether the donor node supports LTE backhaul depends on an indicator indicating whether the donor node is a DgNB connected to a gNB or a Dnb-eNB connected to a ng-eNB. According to the indicator, during operation of the additional relay node RN, the NR relay node RN may select a donor node supporting and/or not supporting LTE backhaul according to whether the NR relay node RN allows the LTE ue to connect.

In case at least one or no donor node supports LTE backhaul, the NR relay node RN may indicate in step 1 whether LTE access is supported in the manner discussed in scheme 3. According to an indicator, the LTE user equipment will reselect as much as possible to other relay nodes RN supporting LTE access. This avoids unnecessary connections, and access to a relay node RN that does not support LTE is denied.

Fig. 8 shows an embodiment of solution 3, in which the transmitted packet carries an indicator of the transmission type. In step 1, in LTE transmissions, the UE provides an indicator. Various types of LTE transmissions may be a UE transmitting an NR PDU, wrapping an LTE PDU, and providing an "LTE base data indicator" message in the NR PDU header informing of the embedded LTE PDU. Based on such information, the relay node RN determines that the transmission is not an NR PDU but an LTE PDU. Next, in step 1b, the header of the LTE protocol is released, and in step 1c, the IP data is transmitted to the CN.

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

It will be appreciated that the description is also applicable in other similar situations, for example, where a WLAN user equipment accesses the IAB via an NR relay node.

Although details of the 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 description, and in particular 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, notebook, handheld (PDA, cell phone, palm top, etc.), mainframe, server, client, or any other type of general purpose computing device capable of performing a particular application or environment, as may be understood as a reasonable application scope. The computing system may include one or more processors implemented by a general-purpose or special-purpose processing engine, such as a microprocessor, microcontroller, or other control module.

The computing system may also include a main memory, such as Random Access Memory (RAM) or other volatile memory, for storing information and instructions for execution 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, 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 disk drive (CD) or a Digital Video Drive (DVD) read-write drive (R or RW), or other removable or fixed media drive. The storage medium 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 medium may include a computer-readable storage medium having stored therein specific 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 cartridge and cassette interfaces, removable memory (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 units 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 communication interfaces may include modems, network interfaces (e.g., ethernet or other NIC cards), communication ports (e.g., universal Serial Bus (USB) ports), PCMCIA slots and cards, etc. Software and data transferred via the communications interface are in the form of electronic signals, electromagnetic signals, optical signals, 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 to generally 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. When executed, these instructions, commonly 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 the 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 include at least one of the group of: hard disks, CD-ROMs, 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 a computing system using, for example, a removable storage drive. The control module (in this example, software instructions or executable computer program code) when executed by a processor in a computer system causes the processor to perform the functions of the invention described herein.

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

It should be appreciated that for clarity, the above description describes embodiments of the invention with reference to a single processing logic. However, the inventive concept may equally be implemented by a number of different functional units and processors to provide 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 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 module components such as FPGA devices. Thus, the components and assemblies of embodiments of the invention can 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 appended claims. In addition, while 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 be advantageously 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 claim category 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 that order. Rather, the steps may be performed in any suitable order. Furthermore, singular references do not exclude a plurality. Thus, references to "a," "an," "the first," "the second," etc. do not exclude 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 appended claims. In addition, while 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

1. An access method for 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, the first network entity is a New Radio (NR) relay node of an integrated access backhaul (Integrated Access Backhaul, IAB), the indicator indicates that the NR relay node allows access to a transmission of a long term evolution (Long Term Evolution, LTE) protocol through a New Radio (NR) system, and the second network entity is a user equipment;

the second network entity communicates 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;

when the NR relay node receives the uplink LTE transmission of the user equipment, detecting whether a packet transmitted in the uplink LTE transmission is based on an LTE protocol or not;

when the packet transmitted in the uplink LTE transmission is based on the LTE protocol, the NR relay node recognizes that the uplink LTE transmission does not have a service data adaptation protocol (service data adaption protocol, SDAP) header, directly decodes the LTE protocol header in the uplink LTE transmission, and transmits internet protocol (Internet Protocol, IP) data in the uplink LTE transmission to a Core Network (CN); a kind of electronic device with high-pressure air-conditioning system

When the NR relay node receives downlink IP data to be sent to the user equipment from the core network, SDAP (software defined access point) file header is not added to the downlink IP data, and the IP data is packaged according to an LTE (long term evolution) protocol and then is sent to the user equipment.

2. The access method of radio access network, RAN, traffic of claim 1, wherein:

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

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

3. The access method of radio access network, RAN, traffic of claim 1, wherein:

the indicator is based on a layer structure difference hinted to the second network entity.

4. The access method of radio access network, RAN, traffic of claim 1, wherein:

the indicator includes a header to indicate whether a network communication protocol of one of the network entities exists or lacks a layered structure.

5. The access method of radio access network, RAN, traffic of claim 1, wherein:

the indicator indication comprises system information to indicate a nature of a network communication protocol of the first network entity.

6. The access method of radio access network, RAN, traffic of claim 1, wherein:

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

7. The access method of radio access network, RAN, traffic of claim 1, 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 access method for radio access network RAN traffic of claim 1, wherein one of the network communication protocols is LTE.

9. The access method for radio access network RAN traffic of claim 8, wherein one of the network communication protocols is NR.

10. The method for accessing radio access network, RAN, traffic of claim 9, wherein the network communication protocol of the second network entity is WLAN.

11. A user equipment comprising a processor, a storage unit and a communication interface, wherein the processor, the storage unit and the communication interface are arranged to perform an access method for radio access network, RAN, services, the access method comprising a first network entity providing an indicator to a second network entity, the indicator recording therein a network communication protocol used by the first network entity; and 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;

wherein the first network entity is a New Radio, NR, relay node of an integrated access backhaul (Integrated Access Backhaul, IAB) and the indicator indicates that the NR relay node allows transmission of an access long term evolution (Long Term Evolution, LTE) protocol over a New Radio, NR system among a plurality of relay nodes, wherein the second network entity is the user equipment;

the user equipment selects the NR relay node; and

the user equipment does not include any service data adaptation protocol (service data adaption protocol, SDAP) header when transmitting uplink LTE data to the NR relay node in uplink (Long Term Evolution, LTE) transmission;

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 arranged to perform an access method for radio access network, RAN, services, the access method comprising a first network entity providing an indicator to a second network entity, the indicator recording therein a network communication protocol used by the first network entity; and 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;

wherein the base station device is the first network entity, the first network entity is a New Radio, NR, relay node of an integrated access backhaul (Integrated Access Backhaul, IAB), and the indicator indicates that the NR relay node allows transmission of an access long term evolution (Long Term Evolution, LTE) protocol through a New Radio, NR system, wherein the second network entity is a user equipment;

13. A non-transitory computer readable medium comprising computer readable instructions for causing a processor to perform an access method for radio access network, RAN, services, the access method comprising a first network entity providing an indicator to a second network entity, the indicator recording therein a network communication protocol used by the first network entity; and 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;

wherein the first network entity is a New air-interface (NR) relay node of an integrated access backhaul (Integrated Access Backhaul, IAB), and the indicator indicates that the NR relay node allows transmission of an access long term evolution (Long Term Evolution, LTE) protocol through a New air-interface (NR) system, wherein the second network entity is a user equipment;