Method for integrating network nodes

Abstract

A method, apparatus and computer program product are provided for wireless communication, the method including: performing, by a wireless communication node together with a network node, an initial access process; and identifying, by the wireless communication node, the network node according to a message from the network node during or after the initial access process, where the network node is employed to amplify a signal between the wireless communication node and a user equipment.

Description

[Technical field]

[0001] This document relates to wireless communications in general, and fifth generation (5G) in particular. th This applies to communications using the IEEE 802.11n standard. [Background technology]

[0002] As new radio (NR) systems move to higher frequencies (approximately 4 GHz for FR1 deployments and above 24 GHz for FR2), propagation conditions deteriorate compared to lower frequencies, exacerbating coverage challenges. As a result, further densification of cells may be required. Although a standard full-stack cell deployment would be preferred, it may not always be possible (e.g., not backhaul availability) or an economically viable option. RF repeaters with full-duplex amplify-and-forward operation have been used in 2G, 3G, and 4G systems to provide blanket coverage in cellular network deployments at a relatively low cost. However, the main problem posed by RF repeaters is that they amplify both the signal and noise, increasing interference within the system.

[0003] Another common property of NR systems is the use of multi-beam operation with associated beam management in the higher frequency bands defined for TDD. Multi-antenna techniques consisting of massive MIMO for FR1 and analog beamforming for FR2 help address the challenging propagation conditions of these higher frequency bands. RF repeaters without beam management capabilities cannot provide beamforming gain in their signal transfer.

[0004] This document relates to a method for network node integration for a cellular network with a smartnode, an apparatus thereof, and a system thereof.

[0005] RF repeaters have been used in 2G, 3G, and 4G deployments to supplement the coverage provided by standard full-stack cells with various transmission power characteristics. They constitute the simplest and most cost-effective measure to improve network coverage. The main advantages of RF repeaters are their low cost, their ease of deployment, and the fact that they do not increase latency. The main disadvantage is that they amplify signals and noise and therefore may contribute to increased interference (pollution) in the system. Within RF repeaters, there are different categories depending on the power characteristics and the amount of spectrum they are configured to amplify (e.g., single band, multi-band, etc.). RF repeaters are non-regenerative relay nodes, they simply amplify and forward everything they receive. RF repeaters are typically full-duplex nodes, and they do not distinguish between UL and DL from a transmission or reception standpoint. Summary of the Invention [Means for solving the problem]

[0006] One aspect of the present disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: performing, by a wireless communication node together with a network node, an initial access process; and identifying, by the wireless communication node, the network node according to a message from the network node during or after the initial access process, where the network node is employed to amplify a signal between the wireless communication node and a user equipment.

[0007] Another aspect of the present disclosure relates to a wireless communication method, in an embodiment, the wireless communication method includes transmitting a message by a network node to a wireless communication node during or after an initial access process to enable the wireless communication node to identify the network node according to the message, the network node being employed to amplify a signal between the wireless communication node and a user equipment.

[0008] Another aspect of the present disclosure relates to a wireless communication method, in an embodiment, the wireless communication method includes receiving, by a wireless communication node, from a network node, an identity report message including an identity of the network node, and performing, by the wireless communication node, authentication of the network node according to the identity of the network node, where the network node is employed to amplify a signal between the wireless communication node and a user equipment.

[0009] Another aspect of the present disclosure relates to a wireless communication method, in an embodiment, the wireless communication method includes transmitting an identity report message by a network node to a wireless communication node, the identity report message including an identity of the network node, to enable the wireless communication node to perform authentication of the network node according to the identity of the network node, the network node being employed to amplify a signal between the wireless communication node and a user equipment.

[0010] Another aspect of the present disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. In an embodiment, the processor is configured to perform an initial access process together with a network node and to identify the network node according to a message from the network node during or after the initial access process, and the network node is employed to amplify a signal between the wireless communication node and a user equipment.

[0011] Another aspect of the present disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. In an embodiment, the processor is configured to: transmit a message to the wireless communication node during or after an initial access process to enable the wireless communication node to identify a network node according to the message, the network node being employed to amplify a signal between the wireless communication node and a user equipment.

[0012] Another aspect of the present disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. In an embodiment, the processor is configured to receive an identity report message from a network node, the identity of the network node including the identity of the network node, and to perform authentication of the network node according to the identity of the network node, the network node being employed to amplify a signal between the wireless communication node and a user equipment.

[0013] Another aspect of the present disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. In an embodiment, the processor is configured to: transmit an identity report message to the wireless communication node, the identity report message including an identity of the network node, to enable the wireless communication node to perform authentication of the network node according to the identity of the network node, the network node being employed to amplify a signal between the wireless communication node and a user equipment.

[0014] Various embodiments may preferably implement the following features. Preferably, the network nodes are identified based on a Random Access Channel Occasion (RO) and a Physical Random Access Channel (PRACH) preamble.

[0015] Preferably, a network node is identified when the wireless communication node detects a PRACH preamble having a contention-free PRACH preamble index corresponding to the network node during the RO.

[0016] Preferably, the network node is identified based on a contention-based Physical Random Access Channel (PRACH) preamble and a Random Access Radio Network Temporary Identifier (RA-RNTI).

[0017] Preferably, the network node is identified when the wireless communication node receives a reply to a Random Access Response (RAR) scrambled with an RA-RNTI corresponding to the network node.

[0018] Preferably, a network node is identified when the wireless communication node receives a reply to an RAR scrambled with an RA-RNTI having an offset corresponding to the network node.

[0019] Preferably, the network nodes are identified based on the content of the message of the scheduled transmission.

[0020] Preferably, the scheduled transmission is a scheduled transmission after a successful initial access process or a data payload sent together with a preamble.

[0021] Preferably, a network node is identified when the wireless communications node receives an indication corresponding to the network node in an identity field or an establishment cause field in the content of the message.

[0022] Preferably, the network node is identified based on an indication corresponding to the network node in a higher layer message received from the network node.

[0023] Preferably, the higher layer message is a registration request and the connection between the network node and the wireless communication node is released when the wireless communication node receives a registration rejection from the core network.

[0024] Preferably, the method further comprises transmitting, by the wireless communications node, an indication to the network node indicating that the network node is supported by the wireless communications node.

[0025] Preferably, the method further comprises receiving, by the network node, an indication from the wireless communication node indicating that the network node is supported by the wireless communication node.

[0026] Preferably, the method further comprises sending, by the wireless communications node, a request to the network node for an identity of the network node.

[0027] Preferably, the method further comprises transmitting, by the wireless communications node to the network node, an access reject in response to authentication of the network node failing.

[0028] Preferably, the identity report message is identified based on a Medium Access Control (MAC) subheader.

[0029] Preferably, the method further comprises receiving, by the network node from the wireless communications node, a request for an identity of the network node.

[0030] Preferably, the method further comprises receiving, by the network node, an access denial from the wireless communications node in response to authentication of the network node failing.

[0031] Preferably, the identity report message is identified based on a Medium Access Control (MAC) subheader.

[0032] The present disclosure relates to a computer program product comprising computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to realize a wireless communication method as detailed in any one of the preceding methods.

[0033] To address undesirable interference, a smart node (SN) can be considered, which leverages control information from the BS to enable intelligent amplify-and-forward operation. The SN is placed in a location where it can receive signals from the BS via wireless communication. Once the SN boots up, a network integration procedure is required. Through this network integration procedure, the BS identifies the SN as a network node and configures the SN for its subsequent amplify-and-forward operation.

[0034] Exemplary embodiments disclosed herein are directed to providing features that will become readily apparent by reference to the following description when considered in conjunction with the accompanying drawings. Consistent with various embodiments, exemplary systems, methods, apparatus, and computer program products are disclosed herein. It will be understood, however, that these embodiments are presented by way of example and not limitation, and that various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0035] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps of a disclosed method or process can be rearranged while remaining within the scope of the present disclosure. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented, unless otherwise stated.

[0036] These and other aspects and their implementations are described in more detail in the drawings, description, and claims. [Brief description of the drawings]

[0037] [Figure 1] FIG. 2 is a schematic diagram of the operational steps of a SN according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a schematic diagram of a communication link and a transfer link according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 is a tree diagram illustrating some of the methods and corresponding cases according to embodiments of the present disclosure. [Figure 4] 1 is an example schematic diagram of a wireless terminal according to an embodiment of the present disclosure. [Diagram 5] 1 is an example schematic diagram of a wireless network node according to an embodiment of the present disclosure. [Figure 6] FIG. 2 illustrates a four-step RACH and a two-step RACH according to an embodiment of the present disclosure. [Figure 7] FIG. 2 illustrates an upper layer message flow according to an embodiment of the present disclosure. [Figure 8] FIG. 2 illustrates a flowchart of a method according to an embodiment of the present disclosure. [Figure 9] FIG. 2 illustrates a flowchart of a method according to an embodiment of the present disclosure. [Figure 10] FIG. 2 illustrates a flowchart of a method according to an embodiment of the present disclosure. [Figure 11] FIG. 2 illustrates a flowchart of a method according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] In an embodiment, referring to Fig. 1 showing the operation steps of an SN, the SN is placed in a position where it can receive signals from the BS via wireless communication. When the SN powers up, a network integration procedure is performed. Through this network integration procedure, the SN (1) is identified by the BS as a network node and (2) is configured for its amplify-and-forward operation as follows:

[0039] After the integration is complete, the SN performs amplify-and-forward operations for the UEs within its coverage using the control information received from the BS.

[0040] The SN consists of two functional parts, one is a communication unit (CU) and the other is a forwarding unit (FU). The CU includes, but is not limited to, a mobile terminal or a device having a UE function part. The FU includes, but is not limited to, a radio unit of a BS or a Reconfigurable Intelligent Surfaces (RIS).

[0041] Figure 2 illustrates a link according to an embodiment of the present disclosure. As shown in Figure 2, the links between the BS, the SN, and the UE are defined as follows:

[0042] In this disclosure, the communication link is the link between the BS and the SN-CU. Indexes 1 and 2 indicate the DL and UL directions, respectively. Using the communication link, the SN-CU acts like a UE to perform initial access, measurements, and receiving control information. Control information for the SN-FU is also received by the SN-CU from the BS via the communication link.

[0043] In this disclosure, the forwarding links are those used between the BS and the SN-FU and between the SN-FU and the UE. Similarly, the indexes 1-4 are used to indicate the direction. The SN-FU uses the control information received by the SN-CU from the BS to perform intelligent amplify-and-forward operations.

[0044] 3 shows a tree diagram illustrating various methods and corresponding cases according to an embodiment of the present disclosure, each of which will be described in detail in the following disclosure with reference to FIG.

[0045] FIG. 4 relates to a schematic diagram of a wireless terminal 40 according to an embodiment of the present disclosure. The wireless terminal 40 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, and is not limited herein. The wireless terminal 40 may include a processor 400, such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device that stores a program code 412 that is accessed and executed by the processor 400. The embodiments of the storage unit 412 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random-access memory (RAM), a hard disk, and an optical data storage device. The communication unit 420 may be a transceiver, and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 400. In an embodiment, the communication unit 420 transmits and receives signals via at least one antenna 422 shown in FIG.

[0046] In an embodiment, the storage unit 410 and the program code 412 may be omitted and the processor 400 may include a storage unit having the program code stored therein.

[0047] The processor 400 may, for example, by executing program code 412, implement any one of the steps in the illustrated embodiments on the wireless terminal 40.

[0048] The communication unit 420 may be a transceiver. Alternatively or additionally, the communication unit 420 may combine a transmitting unit and a receiving unit configured to transmit and receive signals, respectively, to and from a wireless network node (e.g., a base station).

[0049] 5 relates to a schematic diagram of a wireless network node 50 according to an embodiment of the present disclosure. The wireless network node 50 may be, but is not limited to, a satellite, a base station (BS), a smart node, a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a radio network controller (RNC) as defined herein. In addition, the wireless network node 50 may comprise (implement) at least one network function, such as, for example, an access and mobility management function (AMF), a session management function (SMF), a user place function (UPF), a policy control function (PCF), an application function (AF), etc. The wireless network node 50 may include a processor 500, such as a microprocessor or ASIC, a storage unit 510, and a communication unit 520. The storage unit 510 may be any data storage device that stores program code 512 that is accessed and executed by the processor 500. Examples of the storage unit 512 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device.The communication unit 520 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 600. In an example, the communication unit 520 transmits and receives signals via at least one antenna 522 shown in FIG.

[0050] In an embodiment, the memory unit 510 and the program code 512 may be omitted. The processor 500 may include a memory unit having the program code stored therein.

[0051] The processor 500, for example through execution of the program code 512, may perform on the wireless network node 50 any of the steps described in the illustrative embodiments.

[0052] The communication unit 520 may be a transceiver. The communication unit 520 may alternatively or additionally combine a transmitting unit and a receiving unit configured to transmit and receive, respectively, signals to and from a wireless terminal (e.g., user equipment or another wireless network node).

[0053] SN Support Instructions in SI Case 0 (C0) In an embodiment, if SN deployment is an optional feature, an indication (e.g., named "sn-support") may be added to the system information, e.g., in SIB1. When the SN powers up, it performs cell search, system information acquisition as the UE. The SN then checks the indication sn-support in the system information to determine whether the cell is accessible.

[0054] For a normal UE, a cell barring indication is included in the system information, e.g., MIB, to prevent the UE from accessing the cell (e.g., the cell is overloaded). This indication can be ignored by the SN. That is, when the SN receives system information with a cell barring indication corresponding to a cell, the SN can still access the cell.

[0055] SN Identification Procedure Since the SN communicates with the BS via a wireless channel like the UE, the integration can be performed similarly to the initial access procedure of the UE. The SN performs its initial access using communication links 1 and 2.

[0056] The initial access message flow is shown in Figure 6. Figure 6 shows possible points for SN identification according to an embodiment of the present disclosure. Both "4-step RACH" and "2-step RACH" procedures can be used by the SN if the BS supports the corresponding RACH procedure. Figure 6 also shows messages Msg1, Msg2, Msg3, Msg4 in the 4-step RACH procedure, and messages MsgA and MsgB in the 2-step RACH procedure. SN identification can be accomplished by the BS at different points 1-5 (shown as circles in Figure 6). The identification at points 1, 2, and 4 preferably has less impact on the CN core network (CN), since the SN may transparently forward the received signal from the BS / UE to the UE / BS.

[0057] In an embodiment, in the "4-step RACH" procedure (see FIG. 6), the SN is identified by the BS at point 1, i.e. after the BS receives the PRACH preamble. In this scenario, the following cases may be considered:

[0058] RO Period Configuration and Dedicated PRACH Preamble Index - Case 1 (C1) For the RO period configuration for SN, since the deployment of SN does not change frequently, the RO period for SN can be longer than that of normal UE. There are the following options: 1) SN can use a predefined RO period (e.g., 640 ms), and 2) the RO period can be configured by OAM in the deployment of SN.

[0059] For the dedicated PRACH preamble index, the BS needs to reserve a dedicated preamble resource for the SN in order to identify the SN from the received PRACH preamble. In the current NR specification, the PRACH preamble is divided into contention based (CB) and contention free (CF).

[0060] A dedicated CF PRACH preamble index may be used to provide an initial access opportunity for a SN. For example, the first or last CF PRACH preamble index may be reserved for an initial access of a SN in a corresponding RO. The BS may ensure that the dedicated CF PRACH preamble index is not assigned to any UE using CF PRACH in a corresponding RO. If the BS detects a PRACH preamble with a dedicated CF PRACH preamble index in a corresponding RO, the BS may identify the preamble sent by the SN.

[0061] The technical advantages of this method include: (1) reducing the impact on CF PRACH capacity in a sparser RO configuration; and (2) reducing the BS workload for SN detection.

[0062] In an embodiment, in a "four-step RACH" procedure (see Figures 3 and 6), the SN is identified by the BS at point 2, i.e., after it receives the first scheduled transmission (i.e., Msg3 in the LTE / NR specifications). In this scenario, the following cases may be considered:

[0063] Dedicated CB PRACH preamble index and RA-RNTI-SN-Case 2a (C2a) A dedicated CB PRACH preamble index with a dedicated RNTI can be used to identify the initial access of the SN. For example, the first or last CB PRACH preamble index can be reserved for the initial access of the SN in the corresponding RO. Since the initial access of the SN is expected to be less frequent, the dedicated RA-RNTI-SN can be predefined, e.g., 0xFFFD. If the BS detects a PRACH preamble with a dedicated CB PRACH preamble index in the corresponding RO, the BS sends a scrambled RAR with RA-RNTI-SN. The SN detects the RAR with RA-RNTI-SN. If the SN correctly receives the RAR for it and replies with Msg3. The BS can identify that the preamble is the one sent by the SN.

[0064] Technical advantages of this method include that the BS can send two RARs with RA-RNTI-SN and RA-RNTI, respectively. If there is a normal UE that collides with an SN that uses a dedicated CB PRACH preamble index, the UE can receive the RAR with RA-RNTI and the SN can receive the RAR with RA-RNTI-SN.

[0065] Dedicated CB PRACH preamble index and RA-RNTI + predefined offset - Case 2b (C2b) The offset of RA-RNTI can be predefined or configured by OAM. A dedicated CB PRACH preamble index with RA-RNTI offset can be used to identify the initial access of the SN. For example, the first or last CB PRACH preamble index can be reserved for the initial access of the SN in the corresponding RO. If the BS detects a PRACH preamble with a dedicated CB PRACH preamble index in the corresponding RO, the BS sends a RAR scrambled with RA-RNTI with an offset (also presented as RA-RNTI+offset). The SN detects the RAR with RA-RNTI+offset. If the SN receives the RAR correctly for it and replies with Msg3. The BS can identify that the preamble is the one sent by the SN.

[0066] Technical advantages of this method include that the BS can send two RARs with RA-RNTI+offset and RA-RNTI, respectively. If there is a normal UE that collides with an SN that uses a dedicated CB PRACH preamble index, the UE can receive the RAR with RA-RNTI and the SN can receive the RAR with RA-RNTI+offset.

[0067] New Content in Msg3 for SN Initial Access - Case 2c (C2c) For the purpose of identifying the SN from the first scheduled transmission (i.e., Msg3), new content in Msg3 can be considered. In some approaches, Msg3 contains an RRCSetupRequest message. In an example, the content of the RRCSetupRequest message is as follows: --ASN1START --TAG-RRCSETUPREQUEST-START RRCSetupRequest::=SEQUENCE { rrcSetupRequest RRCSetupRequest-IES } RRCSetupRequest-IEs::=SEQUENCE { ue-Identity InitialUE-Identity, establishmentCause EstablishmentCause, spare BIT STRING(SIZE(1)) } InitialUE-Identity::=CHOICE{ ng-5G-S-TMSI-Part1 BIT STRING(SIZE(39)), randomValue BIT STRING(SIZE(39)) } EstablishmentCause::=ENUMERATED{ emergency,highPriorityAccess,mt-Access,mo-Signalling, mo-Data,mo-VoiceCall,mo-SMS,mps-PriorityAcces,mcs-PriorityAccess, spare 6,spare 5,spare 4,spare 3,spare 2,spare 1} --TAG-RRCSETUPREQUEST-STOP --ANS1STOP To identify the SN in the RRCSetupRequest message, the following options can be considered, in which the second option is preferred due to the fact that it has no impact on the initial access of normal UEs.

[0068] As a first option, a predefined UE-Identity can be used. Since ng-5G-S-TMSI-part1 is assigned by the CN, it is not suitable for identifying the SN in point 2. Therefore, a field randomValue with a predefined value can be used to identify the SN. For example, the value 0 or the value 239-1 can be considered as predefined values. In this case, the predefined values ​​cannot be used by normal UEs in their initial access. Otherwise, the BS cannot convey the SN from normal UEs by the UE-Identity field.

[0069] As a second, more preferred option, a dedicated EstablishmentCause can be used. In the EstablishmentCause field, a new value can be defined for the initial access of the SN. For example, spare6 can be redefined as "sn-Access" for the identification of the SN.

[0070] In an embodiment, in the "four-step RACH" procedure (see Figures 3 and 6), the SN is identified by the BS at point 3, i.e. after the SN successfully completes its initial access. In this scenario, the following cases may be considered:

[0071] New Identification Fields Defined in Upper Layer Messages - Case 3 (C3) After successful initial access, the SN sends an RRCSetupComplete message to the BS to register with the CN like a UE. To support identification on the BS side, a new indication field (e.g., named "smart-NodeIndication") can be added to the RRCSetupComplete message. This field is optional and has an enumerated value range {true, false}.

[0072] In addition, this method can be used together with RAN-based SN identification to improve network access security.

[0073] The CN judges whether to accept the registration request according to the reported smart-NodeIndication. If the smart-NodeIndication is invalid, the CN responds with a registration rejection to the BS. The BS forwards the registration rejection and releases the connection with the SN accordingly.

[0074] Figure 7 is an illustration of a higher layer message flow consistent with an embodiment of the present disclosure. As shown in Figure 7, the SN first sends an RRCSetupRequest, S71, to the BS and receives an RRCSetup, S72, in response. The SN sends an RRCSetupComplete message, S73, to the BS. The BS sends a registration request, S74, to the CN. The CN sends a registration accept message, S75, to the BS. The BS sends a message to the SN, S76, including DL information transmission. The UE sends a message to the BS, S77, including UL information transmission. Finally, the BS sends a registration complete message, S78, to the CN.

[0075] In an embodiment, in a two-step RACH procedure (see Figures 3 and 6), the SN is identified by the BS at point 4, i.e. after the BS receives the random access preamble + data. In this scenario, the following cases may be considered:

[0076] RO Period Configuration and Dedicated PRACH Preamble Index - Case 4a (C4a) The same method can be reused as in Case 1. The benefits of this method include: (1) reduced impact on CF PRACH capacity due to sparser RO configuration, (2) reduced BS workload for SN detection.

[0077] New Content in MsgA PUSCH for SN Initial Access - Case 4b (C4b) The MsgA PUSCH contains the RRCSetupRequest message. In this case, the method in case 2c can be reused to identify the SN.

[0078] If only MsgA PRACH is successfully detected, the BS sends MsgB to ask the SN to fall back to 4-step RACH like a normal UE.

[0079] In an embodiment, in a two-step RACH procedure (see Figures 3 and 6), the SN is identified by the BS at point 5, i.e. after the SN successfully completes its initial access with data. In this scenario, the following cases may be considered:

[0080] New Identification Fields Defined in Upper Layer Messages - Case 5 (C5) The upper layer message flow is the same as in the 4-step RACH. In this case, the method described above for case 3 can be reused by the BS to identify the SN.

[0081] In addition, this method can be used together with RAN-based SN identification to improve network access security.

[0082] RAN-based authentication procedure for SN The SN can be authenticated by the RAN after its successful initial access. Using this procedure, authentication can be accomplished by the RAN, which reduces the impact on the CN.

[0083] In various embodiments, the following cases may be considered: New MAC CE-Case 6a (C6a) for SN ID acquisition The BS sends a SN ID request MAC CE to the SN-CU, and the SN-CU responds with a SN ID report MAC CE to the BS.

[0084] The SN ID request MAC CE is identified by a MAC subheader with a predefined LCID. For example, the value 46 can be used for current NR systems. It has a fixed size of 0 bits.

[0085] The SN ID reporting MAC CE is identified by a MAC subheader with a predefined LCID. For example, the value 44 can be used for current NR systems. It has a predefined size and consists of a single field containing the SN ID. The SN ID is the network node identity assigned by the network node manufacturer or configured by the OAM. The validity of the SN ID is recognizable by the BS.

[0086] Authentication Rejected - Case 6b (C6b) The BS checks the received SN ID report MAC CE and determines whether the SN is a valid network node for the current cell. If the BS determines that the SN is invalid, it sends a SN Access Reject MAC CE to the SN-CU. The SN Access Reject MAC CE is identified by a MAC subheader with a predefined LCID. For example, the value 45 can be used in the current NR system. It has a fixed size of 0 bits.

[0087] 8 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 8 may be used in a BS, and includes:

[0088] Step 801: Conducting an initial access process by a wireless communication node (eg, BS) together with a network node (eg, SN).

[0089] Step 802: Identifying, by the wireless communication node, a network node according to a message from the network node during or after the initial access process.

[0090] In this embodiment, the network node is employed to amplify signals between the wireless communication node and the user equipment.

[0091] In an embodiment, the network node is identified based on a random access channel opportunity (RO) and a physical random access channel (PRACH) preamble.

[0092] In an embodiment, a network node is identified when the wireless communication node detects a PRACH preamble having a contention-free PRACH preamble index corresponding to the network node during an RO.

[0093] In an embodiment, the network node is identified based on a contention-based physical random access channel (PRACH) preamble and a random access radio network temporary identifier (RA-RNTI).

[0094] In an embodiment, a network node is identified when the wireless communication node receives a reply to a Random Access Response (RAR) scrambled with a RA-RNTI corresponding to the network node.

[0095] In an embodiment, a network node is identified when the wireless communication node receives a reply to an RAR scrambled with an RA-RNTI having an offset corresponding to the network node.

[0096] In an embodiment, the network node is identified based on the content of the message of the scheduled transmission.

[0097] In an embodiment, the scheduled transmission is a scheduled transmission after a successful initial access process or a data payload sent along with a preamble.

[0098] In an embodiment, a network node is identified when the wireless communications node receives an indication corresponding to the network node in an identity field or an establishment cause field in the content of the message.

[0099] In an embodiment, the network node is identified based on an indication corresponding to the network node in a higher layer message received from the network node.

[0100] In an embodiment, the higher layer message is a registration request and the connection between the network node and the wireless communication node is released when the wireless communication node receives a registration rejection from the core network.

[0101] In an embodiment, the method further includes transmitting, by the wireless communications node, an indication to the network node indicating that the network node is supported by the wireless communications node.

[0102] 9 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 9 may be used in an SN and includes:

[0103] Step 901: Sending a message by a network node to a wireless communication node during or after an initial access process, to enable the wireless communication node to identify the network node according to the message.

[0104] In this embodiment, the network node is employed to amplify signals between the wireless communication node and the user equipment.

[0105] In an embodiment, the network node is identified based on a random access channel opportunity (RO) and a physical random access channel (PRACH) preamble.

[0106] In an embodiment, a network node is identified when the wireless communication node detects a PRACH preamble having a contention-free PRACH preamble index corresponding to the network node during an RO.

[0107] In an embodiment, the network node is identified based on a contention-based physical random access channel (PRACH) preamble and a random access radio network temporary identifier (RA-RNTI).

[0108] In an embodiment, a network node is identified when the wireless communication node receives a reply to a Random Access Response (RAR) scrambled with a RA-RNTI corresponding to the network node.

[0109] In an embodiment, a network node is identified when the wireless communication node receives a reply to an RAR scrambled with an RA-RNTI having an offset corresponding to the network node.

[0110] In an embodiment, the network node is identified based on the content of the message of the scheduled transmission.

[0111] In an embodiment, the scheduled transmission is a scheduled transmission after a successful initial access process or a data payload sent along with a preamble.

[0112] In an embodiment, a network node is identified when the wireless communications node receives an indication corresponding to the network node in an identity field or an establishment cause field in the content of the message.

[0113] In an embodiment, the network node is identified based on an indication corresponding to the network node in a higher layer message received from the network node.

[0114] In an embodiment, the higher layer message is a registration request and the connection between the network node and the wireless communication node is released when the wireless communication node receives a registration rejection from the core network.

[0115] In an embodiment, the method further includes receiving, by the network node, an indication from the wireless communication node indicating that the network node is supported by the wireless communication node.

[0116] 10 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 10 may be used in a BS, and includes:

[0117] Step 1001: Receiving, by a wireless communication node (eg, a BS), from a network node, an identity report message (eg, an SN ID Report MAC CE) including an identity of the network node.

[0118] Step 1002: Performing, by the wireless communication node, authentication of the network node according to the identity of the network node.

[0119] In this embodiment, the network node is employed to amplify signals between the wireless communication node and the user equipment.

[0120] In an embodiment, the method further includes transmitting, by the wireless communication node, a request (eg, SN ID Report MAC CE) to the network node for an identity of the network node.

[0121] In an embodiment, the method further includes transmitting, by the wireless communication node to the network node, an access reject (eg, SN Access Reject MAC CE) in response to failing authentication of the network node.

[0122] In an embodiment, the identity report message is identified based on a Medium Access Control (MAC) subheader.

[0123] 11 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 11 may be used in an SN and includes:

[0124] Step 1101: Sending an identity report message including an identity of the network node by the network node to a wireless communication node, to enable the wireless communication node to perform authentication of the network node according to the identity of the network node.

[0125] In this embodiment, the network node is employed to amplify signals between the wireless communication node and the user equipment.

[0126] In an embodiment, the method further comprises receiving, by the network node from the wireless communications node, a request for an identity of the network node.

[0127] In an embodiment, the method further includes receiving, by the network node, an access denial from the wireless communication node in response to authentication of the network node failing.

[0128] In an embodiment, the identity report message is identified based on a Medium Access Control (MAC) subheader.

[0129] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example and not limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable one of ordinary skill in the art to appreciate example features and functions of the present disclosure. However, it will be appreciated that the present disclosure is not limited to the depicted example architectures or configurations, but may be implemented using various alternative architectures and configurations. Furthermore, as will be appreciated by one of ordinary skill in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any one of the above-described example embodiments.

[0130] It is also understood that when designations such as "first," "second," etc. are used herein to refer to elements, they are not intended to generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, the phrases "first and second element" do not imply that only two elements may be employed or that the first element must precede the second element in some manner.

[0131] Additionally, those skilled in the art will appreciate that information and signals may be represented using any one of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0132] Those skilled in the art will further recognize that any one of the various illustrative logical blocks, units, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which may be referred to herein for convenience as "software" or "software units"), or any combination of these technologies.

[0133] To clearly illustrate this interchangeability of hardware, firmware, and software, various example components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. Consistent with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. may be configured to perform one or more of the functions described herein. The term "configured to" or "configured for" as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0134] Moreover, those skilled in the art will appreciate that the various exemplary logical blocks, units, devices, components, and circuits described herein may be implemented in or performed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logical blocks, units, and circuits may further include an antenna and / or a transceiver for communicating with various components in the network or device. The general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.

[0135] Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transmit a computer program or code from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0136] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Additionally, for purposes of discussion, various units are described as separate units. However, as would be apparent to one skilled in the art, two or more units may be combined to form a single unit that performs the relevant functions according to embodiments of the present disclosure.

[0137] Additionally, embodiments of the present disclosure may employ memory or other storage, as well as communication components. It will be appreciated that for the sake of clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or regions may be used without detracting from the disclosure. For example, functionality illustrated to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not refer to a strict logical or physical structure or organization, but merely to suitable means for providing the described functionality.

[0138] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the scope of the claims. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as detailed in the following claims.

Claims

1. conducting an initial access process by the wireless communication node together with the network node; identifying, by the wireless communications node, the network node according to a message from the network node during or after the initial access process; Including, 20. A wireless communication method, wherein the network node is employed to amplify signals between the wireless communication node and user equipment.

2. 2. The wireless communication method of claim 1, wherein the network nodes are identified based on a random access channel opportunity (RO) and a physical random access channel (PRACH) preamble.

3. 3. The wireless communication method of claim 2, wherein the network node is identified when the wireless communication node detects the PRACH preamble having a contention-free PRACH preamble index corresponding to the network node during the RO.

4. The wireless communication method according to any of claims 1 to 2, wherein the network node is identified based on a contention-based Physical Random Access Channel (PRACH) preamble and a Random Access Radio Network Temporary Identifier (RA-RNTI).

5. 5. The wireless communication method of claim 4, wherein the network node is identified when the wireless communication node receives a reply to a Random Access Response (RAR) scrambled with a RA-RNTI corresponding to the network node.

6. The wireless communication method of claim 4, wherein the network node is identified when the wireless communication node receives a reply to an RAR scrambled with the RA-RNTI having an offset corresponding to the network node.

7. A wireless communication method according to any preceding claim, wherein the network nodes are identified based on the content of a message of a scheduled transmission.

8. 8. The wireless communication method of claim 7, wherein the scheduled transmission is a scheduled transmission after a successful initial access process or a data payload sent together with a preamble.

9. 9. The wireless communication method of claim 7 or 8, wherein the network node is identified when the wireless communication node receives an indication corresponding to the network node in an identity field or an establishment cause field in the content of the message.

10. A wireless communication method according to any preceding claim, wherein the network node is identified based on an indication corresponding to the network node in a higher layer message received from the network node.

11. 11. The wireless communication method of claim 10, wherein the higher layer message is a registration request and a connection between the network node and the wireless communication node is released when the wireless communication node receives a registration rejection from a core network.

12. The wireless communication method of any of claims 1 to 11, further comprising transmitting, by the wireless communication node, an indication to the network node indicating that the network node is supported by the wireless communication node.

13. transmitting said message by said network node to said wireless communication node during or after an initial access process to enable said wireless communication node to identify the network node according to said message; the network node is adapted to amplify signals between the wireless communication node and user equipment; Wireless communication method.

14. 14. The wireless communication method of claim 13, wherein the network node is identified based on a random access channel opportunity (RO) and a physical random access channel (PRACH) preamble.

15. 15. The wireless communication method of claim 14, wherein the network node is identified when the wireless communication node detects the PRACH preamble having a contention-free PRACH preamble index corresponding to the network node during the RO.

16. The wireless communication method according to any of claims 13 to 14, wherein the network node is identified based on a contention-based Physical Random Access Channel (PRACH) preamble and a Random Access Radio Network Temporary Identifier (RA-RNTI).

17. 17. The wireless communication method of claim 16, wherein the network node is identified when the wireless communication node receives a reply to a Random Access Response (RAR) scrambled with a RA-RNTI corresponding to the network node.

18. The wireless communication method of claim 16, wherein the network node is identified when the wireless communication node receives a reply to an RAR scrambled with the RA-RNTI having an offset corresponding to the network node.

19. A wireless communication method according to any of claims 13 to 18, wherein the network node is identified based on the content of a message of a scheduled transmission.

20. 20. The wireless communication method of claim 19, wherein the scheduled transmission is a scheduled transmission after a successful initial access process or a data payload sent together with a preamble.

21. 21. The wireless communication method of claim 19 or 20, wherein the network node is identified when the wireless communication node receives an indication corresponding to the network node in an identity field or an establishment cause field in the content of the message.

22. A wireless communication method according to any of claims 13 to 21, wherein the network node is identified based on an indication corresponding to the network node in a higher layer message received from the network node.

23. 23. The wireless communication method of claim 22, wherein the higher layer message is a registration request and a connection between the network node and the wireless communication node is released when the wireless communication node receives a registration rejection from a core network.

24. 23. The wireless communication method of any of claims 13 to 22, further comprising receiving, by the network node, an indication from the wireless communication node indicating that the network node is supported by the wireless communication node.

25. receiving, by the wireless communications node, an identity report message from a network node, the identity of the network node; performing, by the wireless communication node, an authentication of the network node according to the identity of the network node; the network node is adapted to amplify signals between the wireless communication node and user equipment; Wireless communication method.

26. 26. The wireless communications method of claim 25, further comprising sending, by the wireless communications node to the network node, a request for the identity of the network node.

27. 27. The wireless communications method of claim 25 or 26, further comprising transmitting, by the wireless communications node to the network node, an access reject in response to the authentication of the network node failing.

28. The wireless communication method of any of claims 25 to 27, wherein the identity report message is identified based on a Medium Access Control (MAC) subheader.

29. transmitting, by the network node to the wireless communication node, an identity report message including the identity of the network node, to enable the wireless communication node to perform authentication of the network node according to the identity of the network node; the network node is adapted to amplify signals between the wireless communication node and user equipment; Wireless communication method.

30. 30. The wireless communications method of claim 29, further comprising receiving, by the network node from the wireless communications node, a request for the identity of the network node.

31. 31. The wireless communications method of claim 29 or 30, further comprising receiving, by the network node from the wireless communications node, an access refusal in response to the authentication of the network node failing.

32. The wireless communication method of any of claims 29 to 31, wherein the identity report message is identified based on a Medium Access Control (MAC) subheader.

33. A communication unit; a processor configured to: perform, together with a network node, an initial access process; and identify the network node according to a message from the network node during or after the initial access process, the network node being employed to amplify signals between the wireless communication node and a user equipment; A wireless communication node comprising:

34. The wireless communication node of claim 33, wherein the processor is further configured to perform a wireless communication method according to any of claims 2 to 12.

35. A communication unit; a processor configured to transmit the message to a wireless communication node during or after an initial access process to enable the wireless communication node to identify a network node according to the message, the network node being employed to amplify a signal between the wireless communication node and a user equipment; A wireless communication node comprising:

36. The wireless communication node of claim 35, wherein the processor is further configured to perform a wireless communication method according to any of claims 14 to 24.

37. A communication unit; a processor configured to receive, from a network node, an identity report message including an identity of the network node, and to perform authentication of the network node according to the identity of the network node, the network node being employed to amplify a signal between the wireless communication node and a user equipment; A wireless communication node comprising:

38. The wireless communication node of claim 37, wherein the processor is further configured to perform a wireless communication method according to any of claims 26 to 28.

39. A communication unit; a processor configured to: transmit to a wireless communication node an identity report message including an identity of the network node, to enable the wireless communication node to perform authentication of the network node according to the identity of the network node, the network node being employed to amplify a signal between the wireless communication node and a user equipment; A wireless communication node comprising:

40. The wireless communication node of claim 39, wherein the processor is further configured to perform a wireless communication method according to any of claims 30 to 32.

41. A computer program product comprising computer readable program medium code stored on said computer program product, said code, when executed by a processor, causing said processor to implement a wireless communication method as detailed in any of claims 1 to 32.

Images