CN114080003B - Method and device for accessing network - Google Patents

Method and device for accessing network Download PDF

Info

Publication number
CN114080003B
CN114080003B CN202010853169.7A CN202010853169A CN114080003B CN 114080003 B CN114080003 B CN 114080003B CN 202010853169 A CN202010853169 A CN 202010853169A CN 114080003 B CN114080003 B CN 114080003B
Authority
CN
China
Prior art keywords
relay node
npn
node
supported
relay
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010853169.7A
Other languages
Chinese (zh)
Other versions
CN114080003A (en
Inventor
杨晨晨
朱元萍
马川
晋英豪
谭巍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202010853169.7A priority Critical patent/CN114080003B/en
Publication of CN114080003A publication Critical patent/CN114080003A/en
Application granted granted Critical
Publication of CN114080003B publication Critical patent/CN114080003B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service

Abstract

The application relates to the technical field of communication and discloses a method and a device for accessing a network. The method is applied to a first relay node, and comprises the following steps: receiving a first message from a higher node of the first relay node, wherein the first message is used for indicating one or more non-public network NPNs; and determining a target NPN to be accessed according to the pre-configured NPN supported by the first relay node and the first message. Through configuring an NPN network which can be accessed by the relay node, the normal communication among the nodes is ensured, and the network service provided by the relay node is not influenced.

Description

Method and device for accessing network
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a method and a device for accessing a network.
Background
The multi-hop network architecture comprises two types of nodes, namely a relay node and a host node, wherein the host node is directly connected to a core network, the relay node is connected to the host node through one or more hops, and the relay node provides corresponding network services for terminal equipment or other relay nodes.
At present, different NPN are supported by each node in a multi-hop non-public network (NPN), and how to set NPN accessed by each relay node of the multi-hop NPN ensures normal communication between nodes, and provides network service without influence becomes a technical problem to be solved.
Disclosure of Invention
The embodiment of the application provides a method and a device for accessing a network, which are used for ensuring normal communication between nodes by configuring an NPN network which can be accessed by a relay node, and do not influence network services provided by the nodes.
In a first aspect, an embodiment of the present application provides a method for accessing a network, which is applied to a first relay node, and includes: receiving a first message from a higher node of the first relay node, wherein the first message is used for indicating one or more non-public network NPNs; and determining a target NPN to be accessed according to the pre-configured NPN supported by the first relay node and the first message. The relay node determines a target NPN to be accessed according to the NPN indicated by the upper node and the NPN supported by the relay node, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN.
In an alternative implementation, the upper node is a home node of the first relay node, and the one or more NPN are NPN supported by the home node.
In an optional implementation manner, the upper node is an upper relay node of the first relay node; the one or more nps are nps supported by both the upper relay node and a home node of the first relay node.
In an alternative implementation manner, the determining the target NPN to be accessed includes: determining the target NPN to be accessed in a first NPN type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
In an alternative implementation, the method further includes: and sending a second message, wherein the second message is used for indicating the first NPN type.
In an optional implementation manner, the first relay node is an upper node of the second relay node, and the method further includes: and sending a switching request message to a target relay node switched by the second relay node, wherein the switching request message carries information for indicating NPN supported by the second relay node.
In an alternative implementation manner, the first relay node is a master node in at least one upper relay node of the second relay node, and the method further includes: and when a first secondary node in at least one upper-level relay node of the second relay node needs to be deleted, sending a secondary node release request message to the first secondary node, wherein the secondary node release request message carries information for indicating NPN supported by the second relay node.
In an optional implementation manner, the first relay node is a first secondary node in at least one upper-level relay node of the second relay node, and the method further includes: and sending a secondary node change demand message to a primary node in at least one superior relay node of the second relay node, wherein the secondary node change demand message carries information for indicating NPN supported by the second relay node.
In a second aspect, an embodiment of the present application provides a method for accessing a network, applied to a host node, including: receiving first information from a first relay node, wherein the first information is used for indicating a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node; and sending second information to the first relay node according to the first information and the NPNs supported by the host node, wherein the second information is used for indicating a first NPN which can be accessed by the first relay node, and the first NPN comprises NPNs supported by the first relay node and the host node.
In an alternative implementation, the method further includes: receiving third information from a second relay node, wherein the third information is used for indicating NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node; and according to the third information and the first NPN, sending fourth information to the second relay node, wherein the fourth information is used for indicating a second NPN which can be accessed by the second relay node, and the second NPN comprises NPNs supported by the second relay node in the first NPN.
In the embodiment of the present application, the relay node reports the NPN supported by the relay node to the host node, and the host node determines the NPN that the relay node can access according to the NPN supported by the relay node in combination with the NPN supported by the relay node and/or the NPN supported by the upper node of the relay node, so that an intersection exists between the NPN that can be accessed by each node, and normal network service is ensured to be provided by the multihop NPN.
In a third aspect, an embodiment of the present application provides a method for accessing a network, applied to a host node, including: receiving a first request message from a first relay node, wherein the first request message is used for requesting to access a non-public network NPN supported by the host node; wherein the first relay node communicates directly with the home node; receiving a message sent by core network equipment and used for indicating a first NPN which can be accessed by the first relay node, wherein the first NPN is supported by the first relay node and the host node; and sending a first indication message to the first relay node according to the first NPN indicated by the core network equipment, wherein the first indication message is used for indicating a target NPN accessed by the first relay node.
In the embodiment of the application, the host node and the core network equipment interact, and the relay node and the NPN supported by the upper level of the relay node are combined, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN. The method can be applied to a scene that the relay node is not configured with the NPN supported by the relay node.
In a fourth aspect, an embodiment of the present application provides an apparatus for accessing a network, which is applied to a first relay node, including: a communication module, configured to receive a first message from a higher node of the first relay node, where the first message is used to indicate one or more non-public networks NPN; and the processing module is used for determining a target NPN to be accessed according to the NPN supported by the preconfigured first relay node and the first message. The relay node determines a target NPN to be accessed according to the NPN indicated by the upper node and the NPN supported by the relay node, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN.
In an alternative implementation, the upper node is a home node of the first relay node, and the one or more NPN are NPN supported by the home node.
In an optional implementation manner, the upper node is an upper relay node of the first relay node; the one or more nps are nps supported by both the upper relay node and a home node of the first relay node.
In an alternative implementation, the processing module is specifically configured to: determining the target NPN to be accessed in a first NPN type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
In an alternative implementation, the communication module is further configured to send a second message, where the second message is used to indicate the first NPN.
In an optional implementation manner, the first relay node is an upper node of the second relay node, and the communication module is further configured to send a handover request message to a target relay node that is switched by the second relay node, where the handover request message carries information for indicating NPN supported by the second relay node.
In an optional implementation manner, the first relay node is a primary node in at least one upper relay node of the second relay node, and the processing module is further configured to, when determining that a first secondary node in the at least one upper relay node of the second relay node needs to be deleted, control the communication module to send a secondary node release request message to the first secondary node, where the secondary node release request message carries information for indicating NPN supported by the second relay node.
In an optional implementation manner, the first relay node is a first secondary node in at least one upper relay node of the second relay node, and the communication module is further configured to send a secondary node change requirement message to a primary node in at least one upper relay node of the second relay node, where the secondary node change requirement message carries information for indicating NPN supported by the second relay node.
In a fifth aspect, an embodiment of the present application provides an apparatus for accessing a network, applied to a home node, including: a communication module, configured to receive first information from a first relay node, where the first information is used to indicate a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node; the processing module is configured to control, according to the first information and the NPN supported by the host node, the communication module to send second information to the first relay node, where the second information is used to indicate a first NPN that the first relay node can access, and the first NPN includes NPN supported by both the first relay node and the host node.
In an alternative implementation manner, the communication module is further configured to receive third information from the second relay node, where the third information is used to indicate NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node; the processing module is further configured to control, according to the third information and the first NPN, the communication module to send fourth information to the second relay node, where the fourth information is used to indicate a second NPN that the second relay node can access, and the second NPN includes an NPN supported by the second relay node in the first NPN.
In the embodiment of the present application, the relay node reports the NPN supported by the relay node to the host node, and the host node determines the NPN that the relay node can access according to the NPN supported by the relay node in combination with the NPN supported by the relay node and/or the NPN supported by the upper node of the relay node, so that an intersection exists between the NPN that can be accessed by each node, and normal network service is ensured to be provided by the multihop NPN.
In a sixth aspect, an embodiment of the present application provides an apparatus for accessing a network, applied to a host node, including: a communication module, configured to receive a first request message from a first relay node, where the first request message is used to request access to a non-public network NPN supported by the host node; wherein the first relay node communicates directly with the home node; the communication module is further configured to receive a message sent by the core network device and used for indicating a first NPN that can be accessed by the first relay node, where the first NPN is an NPN supported by both the first relay node and the host node; the processing module is used for controlling the communication module to send a first indication message to the first relay node according to the first NPN indicated by the core network equipment, wherein the first indication message is used for indicating a target NPN accessed by the first relay node.
In the embodiment of the application, the host node and the core network equipment interact, and the relay node and the NPN supported by the upper level of the relay node are combined, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN. The method can be applied to a scene that the relay node is not configured with the NPN supported by the relay node.
In a seventh aspect, embodiments of the present application provide a communication apparatus, including: a processor and a memory;
the memory is used for storing a computer program;
the processor is configured to execute the computer program stored in the memory, so that the method in any optional implementation manner of any of the first to third aspects is performed.
In an eighth aspect, a communication apparatus includes: a processor and interface circuit;
the interface circuit is used for receiving code instructions and transmitting the code instructions to the processor;
the processor is configured to execute the code instructions to cause the method of any of the optional embodiments of any of the first to third aspects described above to be performed.
A ninth aspect, a computer readable storage medium storing instructions that, when executed, cause a method in any of the optional implementations of any of the first to third aspects described above to be performed.
In a tenth aspect, embodiments of the present application provide a computer program product comprising: computer program code which, when run, causes the method of any of the alternative embodiments of any of the first to third aspects described above to be performed.
The technical effects achieved by the seventh to tenth aspects are described with reference to the corresponding technical solutions of the first to third aspects, and the detailed description is not repeated here.
Drawings
Fig. 1a is a schematic diagram of a multi-hop network architecture according to an embodiment of the present application;
fig. 1b is a schematic diagram of another multi-hop network architecture according to an embodiment of the present application;
fig. 2 is a schematic diagram of an IAB network structure provided in an embodiment of the present application;
fig. 3 is a schematic flow chart of a method for accessing a network according to an embodiment of the present application;
fig. 4 is a second flowchart of a method for accessing a network according to an embodiment of the present application;
fig. 5 is a third schematic flowchart of a method for accessing a network according to an embodiment of the present application;
fig. 6 is a schematic diagram of a method for accessing a network according to an embodiment of the present application;
fig. 7 is a fifth flowchart of a method for accessing a network according to an embodiment of the present application;
Fig. 8 is a schematic flow chart of a method for switching a node according to an embodiment of the present application;
FIG. 9 is a schematic flow chart of SN modification according to an embodiment of the present disclosure;
FIG. 10 is a flowchart illustrating another SN change provided in an embodiment of the present application;
fig. 11 is a block diagram of a device for accessing a network according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 13 is a second schematic structural diagram of a communication device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the accompanying drawings.
The following explains some of the terms provided in this application, facilitating understanding by those skilled in the art:
(1) Non-public network (NPN)
A non-public network, also called private network (private network), refers to a network used for non-public purposes, such as an internal network built in a factory, school, business district. The non-public network NPN can be divided into two types: independent NPN (SNPN) and public network integrated NPN (public network integrated NPN, PNI-NPN). SNPN does not depend on the function of the public network, while PNI-NPN depends on the function of the public network.
Wherein each SNPN has an identity, i.e., SNPN ID. The SNPN ID consists of a public network identity (Public Land Mobile Network Identity, PLMN ID) and a network identity (Network Identifier, NID). The SNPN cell will broadcast its own supported SNPN IDs. If the terminal device signs up for an SNPN, the terminal device is configured with a corresponding subscriber permanent identity (Subscription Permanent Identifier, SUPI) and subscription information, which is stored in the terminal device and Core Network (CN). In the cell selection/reselection process, terminal equipment (SNPN UE) subscribed with SNPN can select accessible SNPN according to own subscription information, and CN authenticates the terminal equipment according to the subscription information of the terminal equipment.
PNI-NPN provides services through public land mobile networks (public land mobile network, PLMN), whose objects of service are divided by closed access groups (closed access group, CAG), one CAG representing a group of users having access to a certain CAG cell. One PNI-NPN is determined by PLMN ID and CAG ID. The PNI-NPN cell (or CAG cell) will broadcast its own supported PNI-NPN IDs. If the terminal device signs a PNI-NPN, the UE is configured with corresponding SUPI and subscription information, where the subscription information includes PNI-NPN IDs that the UE is allowed to access, and the above information is stored in the UE and a Core Network (CN). In the cell selection/reselection process, CAG UE (or PNI-NPN UE) selects accessible PNI-NPN according to own subscription information, and CN authenticates the UE according to the subscription information of the UE.
(2) Multi-hop network architecture
A multi-hop network, also called a relay network, refers to a cellular network with relay nodes. The multi-hop network architecture includes two types of nodes: a donor node (donor node) and a relay node (relay node). The host node is directly connected to the core network; the relay node is not directly connected to the core network, but is connected to the host node through one or more hops, and is then transmitted back to the core network by the host node. The relay node can provide access service for the terminal equipment and can also provide relay service for other relay nodes. A multi-hop network architecture as shown in fig. 1a, illustrating a home node, a relay node 1, a relay node 2, and a terminal device; wherein the relay node 1 communicates directly (or is directly connected) with the host node; the relay node 2 is indirectly communicated with (or indirectly connected with) the host node through the relay node 1, and the relay node 1 serves as an upper node (or called parent node) of the relay node 2 to provide access service for the relay node 2; the terminal device communicates directly with the relay node 2, and the relay node 2 provides access service for the terminal device. In addition, one relay node in the multi-hop network may be connected to one or more upper nodes, as in another multi-hop network architecture shown in fig. 1b, and a relay node 4 is further illustrated on the basis of fig. 1a, where the relay node 4 also directly communicates with a host node, and the relay node 4 serves as an upper node of the relay node 2 to provide access service for the relay node 2.
The multi-hop network architecture described in the embodiments of the present application also includes an access backhaul integrated (integrated access and backhaul, IAB) network, as shown in fig. 2, in which a host node, also called IAB gateway, is composed of two parts, namely a Centralized Unit (CU) and a Distributed Unit (DU); the relay node, also called IAB node, consists of two parts, mobile terminal (mobile termination, MT) and DU: wherein, the function of MT is equivalent to terminal equipment, the relay node is connected with its superior node through MT, the relay node is connected with terminal equipment or child node through DU. With the connection relationship of the core network, the hosting node, the relay node 1, the relay node 2 and the terminal device shown in fig. 1a, fig. 2 further illustrates that an F1 interface (physical interface) exists between the CU of the hosting node and the DU of the hosting node. An F1 interface (logical interface) exists between the CU of the host node and the DU of the relay node. Uu interfaces exist between the host node and the relay node 1, between the relay node 1 and the relay node 2, and between the relay node 2 and the terminal equipment.
(3) Terminal equipment
A terminal device, also called a terminal, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user, e.g., a handheld device, an in-vehicle device, etc., with a wireless connection function. Currently, some examples of terminals are: a mobile phone), a tablet, a notebook, a palm, a mobile internet device (mobile internet device, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (self driving), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like.
(4) The term "plurality of" as used herein means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used in describing various data in embodiments of the present invention, these data should not be limited to these terms. These terms are only used to distinguish one data element from another.
The embodiment of the application provides a method and a device for accessing a network, which can be applied to a scene that a multi-hop network is a multi-hop NPN, and can determine the NPN which can be accessed by any relay node in the multi-hop NPN according to the NPN supported by the relay node and the NPN supported by an upper node of the relay node, so that the problem that the multi-hop NPN cannot normally provide NPN service due to no intersection of NPNs supported by all nodes in the multi-hop network, and the experience of a user of terminal equipment is affected is avoided.
The method for accessing the network provided by the embodiment of the application is described in detail below.
As shown in fig. 3, the embodiment of the present application provides a first method for accessing a network, which is applied to a first relay node, and the first relay node is preconfigured with NPN supported by the first relay node. The method comprises the following steps.
S301, receiving a first message from a superordinate node of the first relay node, where the first message is used to indicate one or more non-public network NPN.
The first message may carry information for indicating one or more nps, for example, the first message carries an identifier (NPN ID) of each NPN, where the NPN may be classified into an SNPN and a PNI-NPN, and the identifier of each NPN may be an SNPN ID or a PNI-NPN ID. The one or more NPNs are part or all of NPNs supported by the upper node.
In one case, the upper node is a host node of the first relay node, that is, the first relay node directly communicates with its host node, and the one or more NPN are NPN supported by the host node. By way of example, the first relay node in this one case may be the relay node 1 shown in fig. 1 a/1 b.
In another case, the upper node is an upper relay node of the first relay node, the upper relay node communicates directly with the host node, and the one or more NPN are NPN supported by both the upper relay node and the host node of the first relay node. Illustratively, the first relay node in this other case may be the relay node 2 as in fig. 1a, and the upper relay node may be the relay node 1 in fig. 1 a; alternatively, the first relay node may be the relay node 2 in fig. 1b, and the upper relay node may be one of the relay nodes 1 and 4 in fig. 1 b.
Specifically, for example, when both the relay node 1 and the relay node 4 have access to the network, the relay node 1 sends a portion or a weighing portion that is common to the NPN indicated by the first message and the NPN supported by the first relay node, and then the upper relay node may be the relay node 1; or, the NPN indicated by the first message sent by the relay node 1 and the NPN supported by the first relay node have a common part or a weighted part, the NPN indicated by the first message sent by the relay node 2 and the NPN supported by the first relay node also have a common part or a weighted part, and the overlapping part corresponding to the relay node 1 is greater than the overlapping part corresponding to the relay node 2, so that the upper relay node may be the relay node 1.
S302, determining a target NPN to be accessed according to the pre-configured NPN supported by the first relay node and the first message.
Optionally, the first relay node is preconfigured with an identity (NPN IDs) of the NPN supported by the first relay node to indicate the NPN supported by the first relay node. In an alternative embodiment, the target NPN to be accessed may be determined from among NPN of the first type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
In the embodiment of the application, the relay node determines the target NPN to be accessed according to the NPN indicated by the upper node and the NPN supported by the relay node, so that an intersection exists among the NPNs which can be accessed by each node, and normal network service is ensured to be provided by the multi-hop NPN.
Further, S303 is further included, where the first relay node sends a second message after accessing the target NPN, where the second message is used to indicate the first NPN. And the subordinate node of the first relay node receives the second message, and determines a target network to be accessed by the subordinate node according to the NPN of the first class and the NPN supported by the subordinate node. The lower node may be a lower relay node or a terminal device of the first relay node.
Optionally, the second message may be further configured to indicate a second type of NPN that is supported by the first relay node but not included in the one or more NPN indicated by the first message. When the first type NPN and the second NPN are indicated, the second message can carry indication information for distinguishing the first type NPN from the second type NPN.
Illustratively, taking the multi-hop network architecture shown in fig. 1a as an example, the relay node 1 and the relay node 2 are preconfigured with the identities of a plurality of PNI-NPN supported by each (hereinafter referred to as PNI-NPN IDs). Referring to fig. 4, the flow of the relay node 1 and the relay node 2 accessing the network is specifically illustrated as follows:
S401, the host node broadcasts PNI-NPN IDs supported by itself.
S402a, the relay node 1 reads the broadcast message of the host node, acquires PNI-NPN IDs supported by the host node, and selects a PNI-NPN access corresponding to the PNI-NPN ID in the overlapping portion when determining that the PNI-NPN IDs supported by the relay node 1 overlap with the PNI-NPN IDs supported by the host node. Optionally, the relay node 1 may further include the identification information of the PNI-NPN selected by the relay node to the host node, for example, the PNI-NPN ID, the PLMN ID in the PNI-NPN ID, and the index (index) of the PLMN corresponding to the PNI-NPN in S1B 1.
S402b, the relay node 1 classifies the PNI-NPN IDs supported by itself into two categories, referred to as a class PNI-NPN IDs and a class PNI-NPN IDs. The PNI-NPN IDs are the parts of the PNI-NPN IDs supported by the relay node 1, which are overlapped with the PNI-NPN IDs broadcast by the host node, and the PNI-NPN IDs are the parts of the PNI-NPN IDs supported by the relay node 1, which are not overlapped with the PNI-NPN IDs broadcast by the host node.
S402c, the relay node 1 reports its own PNI-NPN IDs to the host node for the host node to design a routing table, etc. Optionally, the relay node 1 may also report its own class-two PNI-NPN IDs to the host node, as illustrated in S402c of fig. 4, where the relay node 1 reports its class-two PNI-NPN IDs and class-two PNI-NPN IDs to the host node. In addition, the S402c process may be omitted, i.e., S402b may be performed followed by S402d without skipping S402 c.
S402d, the relay node 1 broadcasts its own PNI-NPN IDs. Optionally, as shown in fig. 4, the relay node 1 may also broadcast its own PNI-NPN IDs. In practice, if one type of PNI-NPN IDs and two types of PNI-NPN IDs are broadcasted. The two types can be distinguished in a dominant way or in an implicit way. The dominant mode can be as follows: information indicating that the PNI-NPN IDs belong to the first type is set for the PNI-NPN IDs, such as a first flag, and information indicating that the PNI-NPN IDs belong to the second type is set for the PNI-NPN IDs. And broadcasting the first mark corresponding to each PNI-NPN ID belonging to the class, and broadcasting the second mark corresponding to each PNI-NPN ID belonging to the class. The implicit approach may be as follows: the PNI-NPN IDs of one type and the PNI-NPN IDs of two types are broadcast in two lists, for example, a list located forward (or backward) in the broadcast message is set as one type of PNI-NPN IDs.
S403a, the relay node 2 reads the broadcast message of the relay node 1, acquires PNI-NPN IDs supported by the relay node 1, and selects a PNI-NPN access corresponding to the PNI-NPN ID from the overlapping portion when determining that the PNI-NPN IDs supported by the relay node 2 overlap with the PNI-NPN IDs supported by the relay node 1. Optionally, the relay node 2 may further include the identification information of the PNI-NPN selected by the relay node to the host node, for example, the PNI-NPN ID, the PLMN ID in the PNI-NPN ID, and the index (index) of the PLMN corresponding to the PNI-NPN in S1B 1.
S403b, the relay node 2 classifies the PNI-NPN IDs supported by itself into two categories, referred to as a class PNI-NPN IDs and a class PNI-NPN IDs. The PNI-NPN IDs of the first type are the parts of PNI-NPN IDs supported by the relay node 2 that overlap with the PNI-NPN IDs of the first type broadcast by the relay node 1, and the PNI-NPN IDs of the second type are the parts of PNI-NPN IDs supported by the relay node 2 that do not overlap with the PNI-NPN IDs of the first type broadcast by the relay node 1.
S403c, the relay node 2 reports a PNI-NPN IDs of the own type to the host node for the host node to design a routing table and the like. Optionally, the relay node 2 may also report its own class-two PNI-NPN IDs to the host node, as illustrated in S403c of fig. 4, where the relay node 2 reports its class-two PNI-NPN IDs and class-two PNI-NPN IDs to the host node. In addition, the S403c process may be omitted, that is, S403c may be skipped after S403b is performed, and the subsequent S403d may be directly performed.
S403d, the relay node 2 broadcasts its own PNI-NPN IDs. Optionally, as shown in fig. 4, the relay node 2 may also broadcast its own PNI-NPN IDs. In practice, if one type of PNI-NPN IDs and two types of PNI-NPN IDs are broadcasted. The two types can be distinguished in a dominant way or in an implicit way. Specific embodiments may be executed in the manner referred to in S402d, and will not be described in detail.
S404, the terminal equipment reads the broadcast message of the relay node 2 and acquires PNI-NPN IDs of the relay node 2. If the PNI-NPN IDs supported by the terminal equipment and one type of PNI-NPN IDs of the relay node 2 are overlapped, the terminal equipment selects one PNI-NPN access corresponding to the PNI-NPN ID from the overlapped PNI-NPN IDs.
By way of example, assume that its supported PNI-NPN IDs pre-configured by relay node 1 comprise {1,2,3,5}, and that its supported PNI-NPN IDs pre-configured by relay node 2 comprise {2,3,6}. According to the foregoing steps S401 to S404, when the PNI-NPN IDs supported by the host broadcast include {1,2,3,4}, the relay node 1 may select a corresponding PNI-NPN access from the PNI-NPN IDs {1,2,3}, and determine that the PNI-NPN IDs of the type that can be broadcast include: {1,2,3}, the two types of PNI-NPN IDs include: {5}. The relay node 2 may select a corresponding PNI-NPN access from PNI-NPN IDs {2,3}, and determine that a type of PNI-NPN IDs that may be broadcast by itself includes: {2,3}, the two types of PNI-NPN IDs include: {6}. The terminal equipment can select PNI-NPN access corresponding to PNI-NPN IDs of 2 or 3.
Furthermore, it should be noted that the steps described above based on fig. 1a assume that each node is connected to only one upper node. When a certain node is connected to a plurality of upper nodes, as shown in fig. 1b, the relay node 2 is connected to the relay node 1 and the relay node 4, one type of PNI-NPN IDs broadcasted by the node is a set of PNI-NPN IDs which are overlapped with one type of PNI-NPN IDs supported by at least one upper node of the PNI-NPN IDs supported by the node, and the two type of PNI-NPN IDs are a set of PNI-NPN IDs which are not overlapped with all PNI-NPN IDs supported by all upper nodes of the PNI-NPN IDs supported by the node.
If the multi-hop NPN adopts the IAB network structure, as shown in fig. 2, PNI-NPN IDs supported by the host node in S401 refer to PNI-NPN IDs supported by the DU of the host node, specifically PNI-NPN IDs supported by the DU of the host node are broadcast. Then S402a is specifically that the MT of the relay node 1 reads the broadcast message of the DU of the host node, where the relay node 1 is a PNI-NPN corresponding to the PNI-NPN ID selected by the MT, and the MT of the relay node 1 forwards the broadcast message to the DU of the relay node 1 after reading the broadcast message. Similarly, S402b refers to PNI-NPN IDs supported by the DU of the relay node 1, specifically, the DU of the relay node 1 divides the PNI-NPN IDs supported by the DU into two types, and S402d specifically, the DU of the relay node 1 broadcasts one type PNI-NPN IDs and two types PNI-NPN IDs supported by the DU of the relay node 1. Operations of the relay node 2, such as reading the broadcast message and broadcasting the PNI-NPN IDs supported by the relay node, may be performed with reference to the relay node 1, which will not be described in detail.
Further, as shown in fig. 5, an embodiment of the present application provides a method for accessing a network, which is applied to a host node, and the method includes the following procedures.
S501, receiving first information from a first relay node, wherein the first information is used for indicating a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node; the first relay node is preconfigured with its supported NPN. Optionally, the NPN IDs are specifically configured in the first relay node to indicate NPN supported by the first relay node.
S502, according to the first information and NPNs supported by the host node, sending second information to the first relay node, wherein the second information is used for indicating a first NPN which can be accessed by the first relay node, and the first NPN comprises NPNs supported by the first relay node and the host node.
S503, receiving third information from a second relay node, where the third information is used to indicate NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node;
s504, according to the third information and the first NPN, fourth information is sent to the second relay node, wherein the fourth information is used for indicating a second NPN which can be accessed by the second relay node, and the second NPN comprises NPNs supported by the second relay node in the first NPN.
In the embodiment of the present application, the relay node reports the NPN supported by the relay node to the host node, and the host node determines the NPN that the relay node can access according to the NPN supported by the relay node in combination with the NPN supported by the relay node and/or the NPN supported by the upper node of the relay node, so that an intersection exists between the NPN that can be accessed by each node, and normal network service is ensured to be provided by the multihop NPN.
Illustratively, taking the multi-hop network architecture shown in fig. 1a as an example, the relay node 1 and the relay node 2 are preconfigured with the identities of a plurality of PNI-NPN supported by each (hereinafter referred to as PNI-NPN IDs). Referring to fig. 6, the method flows of the relay node 1 and the relay node 2 accessing the network are specifically illustrated as follows:
s601, the host node broadcasts PNI-NPN IDs supported by itself.
S602a, the relay node 1 reads a broadcast message of the host node, acquires PNI-NPN IDs supported by the host node, and selects one PNI-NPN access corresponding to the PNI-NPN ID from the overlapping part when determining that the PNI-NPN IDs supported by the relay node 1 and the PNI-NPN IDs supported by the host node have the overlapping part. Optionally, the relay node 1 may further include the identification information of the PNI-NPN selected by the relay node to the host node, for example, the PNI-NPN ID, the PLMN ID in the PNI-NPN ID, and the index (index) of the PLMN corresponding to the PNI-NPN in S1B 1.
S602b, the relay node 1 reports the PNI-NPN IDs supported by itself to the host node.
S602c, the host node classifies PNI-NPN IDs supported by the relay node 1 into two types, referred to as a type PNI-NPN IDs and a type PNI-NPN IDs. The PNI-NPN IDs are the parts of the PNI-NPN IDs supported by the relay node 1, which are overlapped with the PNI-NPN IDs broadcast by the host node, and the PNI-NPN IDs are the parts of the PNI-NPN IDs supported by the relay node 1, which are not overlapped with the PNI-NPN IDs broadcast by the host node.
And S602d, the host node sends the PNI-NPN IDs of the type generated in the S602c to the relay node 1. Optionally, the host node may also send the second class PNI-NPN IDs generated in S602c to the relay node 1.
S602e, the relay node 1 broadcasts its own PNI-NPN IDs. Optionally, as shown in fig. 6, the relay node 1 may also broadcast its own class-two PNI-NPN IDs. In practice, if one type of PNI-NPN IDs and two types of PNI-NPN IDs are broadcasted. The two types can be distinguished in a dominant way or in an implicit way. The dominant mode can be as follows: information indicating that the PNI-NPN IDs belong to the first type is set for the PNI-NPN IDs, such as a first flag, and information indicating that the PNI-NPN IDs belong to the second type is set for the PNI-NPN IDs. And broadcasting the first mark corresponding to each PNI-NPN ID belonging to the class, and broadcasting the second mark corresponding to each PNI-NPN ID belonging to the class. The implicit approach may be as follows: the PNI-NPN IDs of one type and the PNI-NPN IDs of two types are broadcast in two lists, for example, a list located forward (or backward) in the broadcast message is set as one type of PNI-NPN IDs.
S603a, the relay node 2 reads the broadcast message of the relay node 1, acquires PNI-NPN IDs supported by the relay node 1, and selects a PNI-NPN access corresponding to the PNI-NPN ID from the overlapping portion when determining that the PNI-NPN IDs supported by the relay node 2 overlap with the PNI-NPN IDs supported by the relay node 1. Optionally, the relay node 2 may further include the identification information of the PNI-NPN selected by the relay node to the host node, for example, the PNI-NPN ID, the PLMN ID in the PNI-NPN ID, and the index (index) of the PLMN corresponding to the PNI-NPN in S1B 1.
S603b, the relay node 2 reports the PNI-NPN IDs supported by itself to the host node.
S603c, the host node divides the PNI-NPN IDs supported by the relay node 2 into two types, namely a type PNI-NPN IDs and a type PNI-NPN IDs, according to the PNI-NPN IDs supported by the relay node 2 and the type PNI-NPN IDs supported by the relay node 1. The PNI-NPN IDs of the first type are the portions of the PNI-NPN IDs supported by the relay node 2 that overlap with the PNI-NPN IDs of the first type supported by the relay node 1, and the PNI-NPN IDs of the second type are the portions of the PNI-NPN IDs supported by the relay node 2 that do not overlap with the PNI-NPN IDs of the first type supported by the relay node 1.
And S603d, the host node sends the PNI-NPN IDs of the type generated in the S603c to the relay node 2. Optionally, the host node may also send the second class PNI-NPN IDs generated in S603c to the relay node 2.
S603e, the relay node 2 broadcasts its own PNI-NPN IDs. Optionally, as shown in fig. 6, the relay node 2 may also broadcast its own PNI-NPN IDs. In practice, if one type of PNI-NPN IDs and two types of PNI-NPN IDs are broadcasted. The two types can be distinguished in a dominant way or in an implicit way. Specific embodiments may be executed in the manner referred to in S602e, and will not be described in detail.
S604, the terminal equipment reads the broadcast message of the relay node 2 and acquires PNI-NPN IDs of the relay node 2. If the PNI-NPN IDs supported by the terminal equipment and one type of PNI-NPN IDs of the relay node 2 are overlapped, the terminal equipment selects one PNI-NPN access corresponding to the PNI-NPN ID from the overlapped PNI-NPN IDs.
Further, as shown in fig. 7, an embodiment of the present application provides a method for accessing a network, which includes the following procedure.
S701, the host node sends a message for indicating NPN supported by the host node, specifically, as shown in fig. 7, the host node broadcasts NPN IDs supported by the host node.
S702, the host node receives a first request message from a first relay node, where the first request message is used to request to access a non-public network NPN supported by the host node; wherein the first relay node communicates directly with the hosting node.
Optionally, the first relay node is a first request message sent when receiving a message sent by the host node and used for indicating NPN supported by the host node. The first request message may specifically be an RRC setup complete (RRC setup complete) message or an F1 interface setup request (F1 setup request) message, etc. The first request message may carry an identifier of a first relay node, for example, the first relay node is a RAN-node, and the identifier of the first relay node is a RAN UE NAGP ID; the first request message may further carry indication information for indicating that the first relay node requests to access the network as the relay node, and further optionally, the first request message may further carry an NPN ID that the first relay node desires to access.
S703, the host node informs the core network device (for example, AMF) that the first relay node requests access according to the first request message.
Specifically, the home node may send an initial UE message (Initial UE message) to the core network device, where the initial UE message may carry an identifier of a first relay node, for example, the first relay node is a RAN-node, and the identifier of the first relay node is a RAN UE NAGP ID; the initial UE message may further carry indication information for indicating that the first relay node requests to access the network as a relay node, and further optionally, the initial UE message may further carry an NPN ID that the first relay node desires to access.
After receiving the notification, the core network device may determine which NPN IDs the first relay node can access/broadcast according to factors such as NPN supported (signed) by the first relay node, NPN supported by the host node, and the like. For example, it is determined that the first relay node is able to access the NPN supported by both the first relay node and the home node, i.e. the aforementioned first NPN.
S705, the host node receives a message sent by the core network device and used for indicating a first NPN that can be accessed by the first relay node, where the first NPN is an NPN supported by both the first relay node and the host node.
Optionally, the message may be an initial context establishment request (initial context setup request) message, where the message carries an identifier of the first relay node, for example, when the first relay node is an RN-node, an AMF UE NGAP ID and a RAN UE NGAP ID of the RN-node; in addition, the message may also carry NPN IDs supported by the first relay node or NPN IDs that the first relay node can access/broadcast.
S706, determining a target NPN which can be accessed by a first relay node according to a first NPN indicated by core network equipment, and sending a first indication message to the first relay node, wherein the first indication message is used for indicating the target NPN accessed by the first relay node, and the target NPN can be the first NPN indicated by the first message.
Optionally, the foregoing first indication message may be specifically an infinite resource control reconfiguration (radio resource control reconfiguration) message, where the message may carry NPN IDs supported by the first relay node and/or NPN IDs that the first relay node may access.
S707, the first relay node may also notify its subordinate node of the target NPN to which it is connected, e.g., in a broadcast manner. In addition, the home node may also decide the NPN accessible/broadcasted by the first relay node at the discretion of the core network device.
In the embodiment of the application, the host node and the core network equipment interact, and the relay node and the NPN supported by the upper level of the relay node are combined, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN. The method can be applied to a scene that the relay node is not configured with the NPN supported by the relay node.
Further, in an alternative embodiment, when the relay node of the multihop network prepares to access the network, if a plurality of upper relay nodes are detected, one of the upper relay nodes may be selected to be accessed, and then the upper relay node to which the relay node is accessed may be requested to switch to another upper relay node.
Taking the previous upper-lower relationship between the first relay node and the second relay node as an example, assuming that the first relay node is an upper node to which the second relay node selects to access, the first relay node may send a handover request message to a target relay node to which the second relay node is handed over. Optionally, the handover request message carries information for indicating NPN supported by the second relay node, so as to indicate that the first relay node requests to handover the second relay node to the target relay node based on consideration of NPN supported by the second relay node. The NPNs supported by the nodes after switching are still overlapped, so that the normal network service can be provided by the multi-hop NPNs. Illustratively, the handover request message carries a cause value, where the cause value includes one or more of NPN (NPN support for relay node) supported by the relay node, relay node setup (relay node setup), network supported by the IAB (NPN support for IAB), and IAB setup (IAB setup). It should be noted that, the inclusion of the "relay node" and the "IAB" in the above cause values generally refer to that, when the foregoing cause values are specifically applied to indicating a specific relay node, such as the foregoing second relay node, a corresponding name "second relay node" may also be adopted, which is not limited in this embodiment of the present application.
Referring to a schematic flow chart of a method for switching nodes shown in fig. 8, the switching flow includes the following steps.
S801, the second relay node sends, to the first relay node that selects access, a message for indicating configuration information of the second relay node, where the message may be an RRC reconfiguration (RRC Reconfiguration) message or the like, and the message includes NPN IDs supported (subscribed) by the second relay node.
S802, the first relay node determines that the second relay node is to be switched to the target relay node according to NPN IDs supported by the second relay node.
The reason for determining to switch the second relay node to the target relay node may be to switch to the target relay node, so that the number of accessible networks of the second relay node can be increased. For example: the second relay node supports SNPN A and B, the first relay node supports SNPN A, and the target relay node supports SNPN A and B. If the second relay node is accessed to the first relay node, the second relay node can only access SNPN A; and if the second relay node accesses the target relay node, the second relay node can selectively access SNPN A or SNPNB. Thus, the first relay node may switch the second relay node to the target relay node, so that the number of networks that the second relay node can selectively access increases.
S803, the first relay node sends a Handover Request (Handover Request) message to the target relay node to Request Handover of the second relay node to the target relay node. Optionally, as described above, the cause value may be included in the handover request message: NPN supported by the second relay node.
S804, the target relay node performs access control, and determines whether to accept the handover request message.
S805, when it is determined to accept, the target relay node sends a handover request confirm (Handover request ack) message to the first relay node.
S806, the first relay node sends an RRC reconfiguration (RRC Reconfiguration) message to the second relay node.
S807, the second relay node initiates a random access procedure to the target relay node.
Further, in an alternative embodiment, a relay node of the multi-hop network may access a plurality of upper relay nodes, and a connection manner with these upper relay nodes is called multi-connectivity (MC). One of the plurality of upper relay nodes is a Master Node (MN), and the remaining upper relay nodes are Secondary Nodes (SNs). When the MN finds that a certain SN is not suitable as an upper-level relay node of the relay node, for example, the intersection of the SN and NPN supported by the relay node is too small, and there is another relay node more suitable as an upper-level relay node of the relay node, the MN may initiate an SN change (secondary node change) procedure, take the another relay node as a new SN, and release the original SN.
Taking the above-mentioned upper-lower relationship between the first relay node and the second relay node as an example, it is assumed that the first relay node is a primary node in at least one upper relay node of the second relay node, the second relay node is further connected to a third relay node, and the third relay node is a first secondary node in at least one upper relay node of the second relay node. The first relay node discovers that the fourth relay node is more suitable as a secondary node of the second relay node, and then the first relay node initiates an SN change process to migrate the second relay node from the third relay node to the fourth relay node. Referring to fig. 9, an embodiment of the present application provides a flow chart of SN modification, which specifically includes the following steps.
S901, the first relay node decides to migrate the second relay node from the third relay node to the fourth relay node (i.e., change the secondary node of the second relay node from the third relay node to the fourth relay node).
S902, the first relay node sends a secondary node new request (SN Addition Request) message to the fourth relay node.
S903, the fourth relay node sends a secondary node new request acknowledgement (SN Addition Request Ack) message to the first relay node. Through steps S902 to S903, the first relay node configures the fourth relay node as a secondary node of the second relay node.
S904, when the first relay node determines that the third relay node needs to be deleted, the first relay node sends a secondary node release request (SN Release Request) message to the third relay node.
Wherein the secondary node release request message carries information for indicating NPN supported by the second relay node. The first relay node is based on the consideration of NPN supported by the second relay node, and the third relay node which is originally accessed by the second relay node is released, so that the third relay node is conveniently changed into the fourth relay node in the follow-up process. Illustratively, the secondary node release request message carries a cause value, where the cause value includes one or more of NPN (NPN support for relay node) supported by the relay node, relay node setup (relay node setup), network supported by the IAB (NPN support for IAB), and IAB setup (IAB setup). It should be noted that, the inclusion of the "relay node" and the "IAB" in the above cause values generally refer to that, when the foregoing cause values are specifically applied to indicating a specific relay node, such as the foregoing second relay node, a corresponding name "second relay node" may also be adopted, which is not limited in this embodiment of the present application.
S905, the third relay node transmits a secondary node release request acknowledgement (SN Release Request Ack) message to the first relay node. Through S904 to S905, the first relay node releases the connection between the third relay node and the second relay node.
S906, the first relay node transmits an RRC reconfiguration (RRC Reconfiguration) message to the second relay node.
S907, the second relay node sends an RRC reconfiguration complete (RRC Reconfiguration Complete) message to the first relay node. Through steps S906 to S907, the first relay node completes the reconfiguration of the second relay node, so that the second relay node knows that the second relay node is changed from the third relay node to the fourth relay node).
S908, the first relay node sends a secondary node reconfiguration complete (SN Reconfiguration Complete) message to the fourth relay node informing the fourth relay node that its reconfiguration of the second relay node has been completed.
S909, the second relay node initiates a random access procedure to the fourth relay node.
Further, in an alternative embodiment, a relay Node of the multihop network accesses a plurality of upper relay nodes, one of the plurality of upper relay nodes is a Master Node (MN), and the remaining upper relay nodes are Secondary Nodes (SN). It may also be that when a SN finds itself not suitable as an upper level relay node of the relay node, and there is another relay node more suitable as an upper level relay node of the relay node, the SN initiates an SN change (Secondary Node Change) procedure, so that the MN takes the another relay node as a new SN and releases the original SN.
Taking the previous upper-lower relationship between the first relay node and the second relay node as an example, assuming that the first relay node is a first secondary node in at least one upper-level relay node of the second relay node, if the first relay node finds that the fourth relay node is more suitable as a secondary node of the second relay node, the first relay node initiates an SN changing process, and the second relay node is migrated from the third relay node to the fourth relay node. Referring to fig. 10, another flow chart of SN modification is provided in the embodiment of the present application, which specifically includes the following steps.
S1001, the first relay node finds that the fourth relay node is more suitable as a secondary node of the second relay node.
S1002, the first relay node sends a secondary node change requirement (SN Change Required) message to a primary node in at least one upper relay node of the second relay node.
The secondary node change requirement message carries information for indicating NPN supported by the second relay node. To indicate that the first relay node is based on consideration of NPN supported by the second relay node, the secondary node needs to be changed. Illustratively, the secondary node change requirement message carries a cause value, where the cause value includes one or more information of NPN (NPN support for relay node) supported by the relay node, relay node setup (relay node setup), network supported by the IAB (NPN support for IAB), and IAB setup (IAB setup). It should be noted that, the inclusion of the "relay node" and the "IAB" in the above cause values generally refer to that, when the foregoing cause values are specifically applied to indicating a specific relay node, such as the foregoing second relay node, a corresponding name "second relay node" may also be adopted, which is not limited in this embodiment of the present application.
S1003, the first relay node sends a secondary node new request (SN Addition Request) message to the fourth relay node.
S1004, the fourth relay node sends a secondary node new request acknowledgement (SN Addition Request Ack) message to the first relay node. Through steps S1003 to S1004, the first relay node configures the fourth relay node as a secondary node of the second relay node.
S1005, the first relay node transmits an RRC reconfiguration (RRC Reconfiguration) message to the second relay node.
S1006, the second relay node transmits an RRC reconfiguration complete (RRC Reconfiguration Complete) message to the first relay node. Through steps S1006 to S1007, the first relay node completes the reconfiguration of the second relay node, so that the second relay node knows that the second relay node is changed from the third relay node to the fourth relay node).
S1007, the primary node sends a secondary node change acknowledgement (SN Change Confirm) message to the first relay node.
S1008, the first relay node sends a secondary node reconfiguration complete (SN Reconfiguration Complete) message to the fourth relay node informing the fourth relay node that its reconfiguration of the second relay node has been completed.
S1009, the second relay node initiates a random access procedure to the fourth relay node.
Based on the same concept, referring to fig. 11, an embodiment of the present application provides an apparatus 1100 for accessing a network, where the apparatus 1100 includes a communication module 1101 and a processing module 1102. The apparatus 1100 for accessing a network may be a first relay node, may be an apparatus that is applied to the first relay node and is capable of supporting the first relay node to perform a method for accessing a network, or the apparatus 1100 for accessing a network may be a home node, may be an apparatus that is applied to the home node, and is capable of supporting the home node to perform a method for accessing a network.
An embodiment of the apparatus 1100 applied to the first relay node is described in detail below.
A communication module 1101, configured to receive a first message from a node higher than the first relay node, where the first message is used to indicate one or more non-public networks NPN; a processing module 1102, configured to determine a target NPN to be accessed according to the first message and an NPN supported by the preconfigured first relay node. The relay node determines a target NPN to be accessed according to the NPN indicated by the upper node and the NPN supported by the relay node, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN.
In an alternative embodiment, the upper node is a home node of the first relay node, and the one or more NPN are NPN supported by the home node.
In an alternative embodiment, the upper node is an upper relay node of the first relay node; the one or more nps are nps supported by both the upper relay node and a home node of the first relay node.
In an alternative embodiment, the processing module 1102 is specifically configured to: determining the target NPN to be accessed in a first NPN type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
In an alternative embodiment, the communication module 1101 is further configured to send a second message, where the second message is used to indicate the first NPN.
In an optional implementation manner, the first relay node is an upper node of the second relay node, and the communication module 1101 is further configured to send a handover request message to a target relay node for handover of the second relay node, where the handover request message carries information for indicating NPN supported by the second relay node.
In an optional implementation manner, the first relay node is a primary node in at least one upper relay node of the second relay node, and the processing module 1102 is further configured to, when determining that a first secondary node in at least one upper relay node of the second relay node needs to be deleted, control the communication module 1101 to send a secondary node release request message to the first secondary node, where the secondary node release request message carries information for indicating NPN supported by the second relay node.
In an optional implementation manner, the first relay node is a first secondary node in at least one upper-level relay node of the second relay node, and the communication module 1101 is further configured to send a secondary node change requirement message to a primary node in at least one upper-level relay node of the second relay node, where the secondary node change requirement message carries information for indicating NPN supported by the second relay node.
One embodiment of the application of the apparatus 1100 to a host node is described in detail below.
A communication module 1101, configured to receive first information from a first relay node, where the first information is used to indicate a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node; the processing module 1102 is configured to control, according to the first information and the NPN supported by the host node, the communication module 1101 to send second information to the first relay node, where the second information is used to indicate a first NPN that the first relay node can access, and the first NPN includes NPN supported by both the first relay node and the host node.
The communication module 1101 is further configured to receive third information from a second relay node, where the third information is used to indicate NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node; the processing module 1102 is further configured to control, according to the third information and the first NPN, the communication module 1101 to send fourth information to the second relay node, where the fourth information is used to indicate a second NPN that can be accessed by the second relay node, and the second NPN includes an NPN supported by the second relay node in the first NPN.
In the embodiment of the present application, the relay node reports the NPN supported by the relay node to the host node, and the host node determines the NPN that the relay node can access according to the NPN supported by the relay node in combination with the NPN supported by the relay node and/or the NPN supported by the upper node of the relay node, so that an intersection exists between the NPN that can be accessed by each node, and normal network service is ensured to be provided by the multihop NPN.
Another embodiment of the apparatus 1100 as applied to a host node is described in detail below.
A communication module 1101, configured to receive a first request message from a first relay node, where the first request message is used to request access to a non-public network NPN supported by the home node; wherein the first relay node communicates directly with the home node; the communication module 1101 is further configured to receive a message sent by a core network device and used for indicating a first NPN that can be accessed by the first relay node, where the first NPN is an NPN supported by both the first relay node and the host node; the processing module 1102 is configured to control, according to the first NPN indicated by the core network device, the communication module 1101 to send a first indication message to the first relay node, where the first indication message is used to indicate a target NPN accessed by the first relay node.
In the embodiment of the application, the host node and the core network equipment interact, and the relay node and the NPN supported by the upper level of the relay node are combined, so that intersections exist among the NPNs which can be accessed by the nodes, and normal network service is ensured to be provided by the multi-hop NPN. The method can be applied to a scene that the relay node is not configured with the NPN supported by the relay node.
Based on the same concept, as shown in fig. 12, the present embodiment provides a communication apparatus 1200. The communication device 1200 may be a chip or a system-on-chip, for example. Alternatively, the chip system in the embodiments of the present application may be formed by a chip, and may also include a chip and other discrete devices.
The communications apparatus 1200 can include at least one processor 1210 and the communications apparatus 1200 can also include at least one memory 1220 for storing computer programs, program instructions, and/or data. Memory 1220 is coupled to processor 1210.
The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other forms for information interaction between the devices, units, or modules. Processor 1210 may operate in conjunction with memory 1220. Memory 1220 holds the computer programs, program instructions and/or data necessary to implement any of the embodiments described above; processor 1210 may execute a computer program stored in memory 1220 to perform the method of any of the embodiments described above. Optionally, at least one of the at least one memory 1220 may be included in the processor 1210.
A transceiver 1230 may also be included in the communication apparatus 1200, and the communication apparatus 1200 may interact with other devices via the transceiver 1230. The transceiver 1230 may be a circuit, bus, transceiver, or any other device that may be used to interact with information.
In one possible implementation manner, the communication apparatus 1200 may be applied to the first relay node, and the specific communication apparatus 1200 may be the first relay node, or may be an apparatus capable of supporting the first relay node, and implementing the function of the first relay node in any of the foregoing embodiments. The memory 1220 holds the necessary computer programs, program instructions and/or data to implement the functions of the first relay node in any of the embodiments described above. Processor 1210 may execute a computer program stored in memory 1220 to perform the method performed by the first relay node in any of the embodiments described above.
In another possible implementation manner, the communication apparatus 1200 may be applied to a host node, and the specific communication apparatus 1200 may be a host node, or may be an apparatus capable of supporting a host node to implement the functions of a host node in any of the foregoing embodiments. Memory 1220 holds the necessary computer programs, program instructions and/or data to implement the functions of the host node in any of the embodiments described above. Processor 1210 may execute a computer program stored in memory 1220 to perform the method performed by the host node in any of the embodiments described above.
In yet another possible implementation manner, the communication apparatus 1200 may be applied to a core network device, and the specific communication apparatus 1200 may be a core network device, or may be an apparatus capable of supporting a core network device, and implementing the function of the core network device in any of the foregoing embodiments. Memory 1220 holds the necessary computer programs, program instructions and/or data to implement the functions of the core network device in any of the embodiments described above. Processor 1210 may execute a computer program stored in memory 1220 to perform the method performed by the core network device in any of the embodiments described above.
The specific connection medium between the transceiver 1230, the processor 1210, and the memory 1220 is not limited in the embodiments of the application. In the embodiment of the present application, the memory 1220, the processor 1210 and the transceiver 1230 are connected by a bus, which is shown by a thick line in fig. 12, and the connection manner between other components is only schematically illustrated, which is not limited to the embodiment. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 12, but not only one bus or one type of bus.
In the embodiments of the present application, the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.
In the embodiment of the present application, the memory may be a nonvolatile memory, such as a hard disk (HDD) or a Solid State Drive (SSD), or may be a volatile memory (volatile memory), for example, a random-access memory (RAM). The memory may also be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of implementing a memory function for storing a computer program, program instructions and/or data.
Based on the above embodiments, referring to fig. 13, another communication apparatus 1300 is provided according to an embodiment of the present application, including: interface circuitry 1310 and a processor 1320; interface circuit 1310 for receiving code instructions and transmitting to the processor; a processor 1320, configured to execute code instructions to perform a method performed by the first relay node and a method performed by the host node in any of the foregoing embodiments.
Based on the above embodiments, the present application further provides a computer readable storage medium storing instructions that, when executed, cause a method performed by the first relay node or a method performed by the second relay node in any of the above embodiments to be performed. The computer readable storage medium may include: various media capable of storing program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.
In order to implement the functions of the communication device of fig. 12 to 13, the embodiment of the present application further provides a chip, which includes a processor, and is configured to support the communication device to implement the functions related to the first relay node or the host node in the embodiment of the method. In one possible design, the chip is connected to a memory or the chip comprises a memory for holding the necessary program instructions and data of the communication device.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to encompass such modifications and variations.

Claims (25)

1. A method of accessing a network, applied to a first relay node, comprising:
receiving a first message from a higher node of the first relay node, wherein the first message is used for indicating one or more non-public network NPNs;
and determining a target NPN to be accessed according to the pre-configured NPN supported by the first relay node and the first message.
2. The method of claim 1, wherein the upper node is a home node of the first relay node, and the one or more NPN are NPN supported by the home node.
3. The method of claim 1, wherein the upper node is an upper relay node of the first relay node; the one or more nps are nps supported by both the upper relay node and a home node of the first relay node.
4. A method according to any one of claims 1 to 3, wherein said determining a target NPN to be accessed comprises:
determining the target NPN to be accessed in a first NPN type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
5. The method of claim 4, wherein the method further comprises:
And sending a second message, wherein the second message is used for indicating the first NPN type.
6. The method of claim 1, wherein the first relay node is a superordinate node of a second relay node, the method further comprising:
and sending a switching request message to a target relay node switched by the second relay node, wherein the switching request message carries information for indicating NPN supported by the second relay node.
7. The method of claim 1, wherein the first relay node is a master node in at least one superordinate relay node of a second relay node, the method further comprising:
and when a first secondary node in at least one upper-level relay node of the second relay node needs to be deleted, sending a secondary node release request message to the first secondary node, wherein the secondary node release request message carries information for indicating NPN supported by the second relay node.
8. The method of claim 1, wherein the first relay node is a first secondary node of at least one superordinate relay node of a second relay node, the method further comprising:
and sending a secondary node change demand message to a primary node in at least one superior relay node of the second relay node, wherein the secondary node change demand message carries information for indicating NPN supported by the second relay node.
9. A method of accessing a network, for use in a home node, comprising:
receiving first information from a first relay node, wherein the first information is used for indicating a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node;
and sending second information to the first relay node according to the first information and the NPNs supported by the host node, wherein the second information is used for indicating a first NPN which can be accessed by the first relay node, and the first NPN comprises NPNs supported by the first relay node and the host node.
10. The method of claim 9, wherein the method further comprises:
receiving third information from a second relay node, wherein the third information is used for indicating NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node;
and according to the third information and the first NPN, sending fourth information to the second relay node, wherein the fourth information is used for indicating a second NPN which can be accessed by the second relay node, and the second NPN comprises NPNs supported by the second relay node in the first NPN.
11. A method of accessing a network, for use in a home node, comprising:
receiving a first request message from a first relay node, wherein the first request message is used for requesting to access a non-public network NPN supported by the host node; wherein the first relay node communicates directly with the home node;
receiving a message sent by core network equipment and used for indicating a first NPN which can be accessed by the first relay node, wherein the first NPN is supported by the first relay node and the host node;
and sending a first indication message to the first relay node according to the first NPN indicated by the core network equipment, wherein the first indication message is used for indicating a target NPN accessed by the first relay node.
12. An apparatus for accessing a network, applied to a first relay node, comprising:
a communication module, configured to receive a first message from a higher node of the first relay node, where the first message is used to indicate one or more non-public networks NPN;
and the processing module is used for determining a target NPN to be accessed according to the NPN supported by the preconfigured first relay node and the first message.
13. The apparatus of claim 12, wherein the upper node is a home node of the first relay node, and the one or more NPN are NPN supported by the home node.
14. The apparatus of claim 12, wherein the upper node is an upper relay node of the first relay node; the one or more nps are nps supported by both the upper relay node and a home node of the first relay node.
15. The apparatus according to any of the claims 12 to 14, wherein the processing module is specifically configured to:
determining the target NPN to be accessed in a first NPN type; wherein the first type of NPN includes an NPN supported by the first relay node of the one or more NPN.
16. The apparatus of claim 15, wherein the communication module is further for sending a second message indicating the first type of NPN.
17. The apparatus of claim 12, wherein the first relay node is a superior node to a second relay node, the communication module further configured to send a handover request message to a target relay node for handover of the second relay node, the handover request message carrying information indicating NPN supported by the second relay node.
18. The apparatus of claim 12, wherein the first relay node is a primary node of at least one upper relay node of a second relay node, the processing module further configured to control the communication module to send a secondary node release request message to the first secondary node when it is determined that a first secondary node of the at least one upper relay node of the second relay node needs to be deleted, the secondary node release request message carrying information indicating NPN supported by the second relay node.
19. The apparatus of claim 12, wherein the first relay node is a first secondary node of at least one upper relay node of a second relay node, the communication module further configured to send a secondary node change demand message to a primary node of the at least one upper relay node of the second relay node, the secondary node change demand message carrying information indicating NPN supported by the second relay node.
20. An apparatus for accessing a network, for use in a home node, comprising:
a communication module, configured to receive first information from a first relay node, where the first information is used to indicate a non-public network NPN supported by the first relay node; wherein the first relay node communicates directly with the home node;
The processing module is configured to control, according to the first information and the NPN supported by the host node, the communication module to send second information to the first relay node, where the second information is used to indicate a first NPN that the first relay node can access, and the first NPN includes NPN supported by both the first relay node and the host node.
21. The apparatus of claim 20, wherein the communication module is further for receiving third information from a second relay node, the third information being for indicating NPN supported by the second relay node; wherein the second relay node communicates with the hosting node through the first relay node;
the processing module is further configured to control, according to the third information and the first NPN, the communication module to send fourth information to the second relay node, where the fourth information is used to indicate a second NPN that the second relay node can access, and the second NPN includes an NPN supported by the second relay node in the first NPN.
22. An apparatus for accessing a network, for use in a home node, comprising:
a communication module, configured to receive a first request message from a first relay node, where the first request message is used to request access to a non-public network NPN supported by the host node; wherein the first relay node communicates directly with the home node;
The communication module is further configured to receive a message sent by the core network device and used for indicating a first NPN that can be accessed by the first relay node, where the first NPN is an NPN supported by both the first relay node and the host node;
the processing module is used for controlling the communication module to send a first indication message to the first relay node according to the first NPN indicated by the core network equipment, wherein the first indication message is used for indicating a target NPN accessed by the first relay node.
23. A communication device, comprising: a processor and a memory;
the memory is used for storing a computer program;
the processor for executing a computer program stored in the memory such that the method of any one of claims 1 to 8 is performed and the method of any one of claims 9 to 11 is performed.
24. A communication device, comprising: a processor and interface circuit;
the interface circuit is used for receiving code instructions and transmitting the code instructions to the processor;
the processor is configured to execute the code instructions such that the method of any one of claims 1 to 8 is performed and the method of any one of claims 9 to 11 is performed.
25. A computer readable storage medium storing instructions that, when executed, cause the method of any one of claims 1 to 8 to be implemented, the method of any one of claims 9 to 11 to be implemented.
CN202010853169.7A 2020-08-22 2020-08-22 Method and device for accessing network Active CN114080003B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010853169.7A CN114080003B (en) 2020-08-22 2020-08-22 Method and device for accessing network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010853169.7A CN114080003B (en) 2020-08-22 2020-08-22 Method and device for accessing network

Publications (2)

Publication Number Publication Date
CN114080003A CN114080003A (en) 2022-02-22
CN114080003B true CN114080003B (en) 2023-06-16

Family

ID=80282715

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010853169.7A Active CN114080003B (en) 2020-08-22 2020-08-22 Method and device for accessing network

Country Status (1)

Country Link
CN (1) CN114080003B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240015713A1 (en) * 2022-07-07 2024-01-11 Dish Wireless L.L.C. Private network

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213808A (en) * 2019-05-06 2019-09-06 腾讯科技(深圳)有限公司 Access control method, device, computer-readable medium and electronic equipment
WO2020102292A1 (en) * 2018-11-14 2020-05-22 Apple Inc. Network selection and service continuity in non-public networks
CN111194095A (en) * 2018-11-09 2020-05-22 维沃移动通信有限公司 Method and device for access control
CN111447675A (en) * 2019-01-17 2020-07-24 华为技术有限公司 Communication method and related product
CN111465011A (en) * 2019-01-18 2020-07-28 华为技术有限公司 Cross-network access method, device, storage medium and communication system
CN111510923A (en) * 2019-01-31 2020-08-07 华为技术有限公司 Communication method, device and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10708015B2 (en) * 2014-02-10 2020-07-07 Lg Electronics Inc. Signal transmitting method for device-to-device (D2D) communication in wireless communication system and device therefor

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111194095A (en) * 2018-11-09 2020-05-22 维沃移动通信有限公司 Method and device for access control
WO2020102292A1 (en) * 2018-11-14 2020-05-22 Apple Inc. Network selection and service continuity in non-public networks
CN111447675A (en) * 2019-01-17 2020-07-24 华为技术有限公司 Communication method and related product
CN111465011A (en) * 2019-01-18 2020-07-28 华为技术有限公司 Cross-network access method, device, storage medium and communication system
CN111510923A (en) * 2019-01-31 2020-08-07 华为技术有限公司 Communication method, device and system
CN110213808A (en) * 2019-05-06 2019-09-06 腾讯科技(深圳)有限公司 Access control method, device, computer-readable medium and electronic equipment

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
R2-2003346 "IAB support in NPN deployment";Kyocera;《3GPP tsg_ran\wg2_rl2》;20200410;全文 *
R2-2004876 "Remaining issues of IAB in NPN";CATT;《3GPP tsg_ran\wg2_rl2》;20200522;全文 *
R3-203837 "IAB support in NPN";Huawei;《3GPP tsg_ran\wg3_iu》;20200522;全文 *

Also Published As

Publication number Publication date
CN114080003A (en) 2022-02-22

Similar Documents

Publication Publication Date Title
JP6988004B2 (en) Communication methods and devices in centralized and distributed unit architectures
CN108605259B (en) Network switching method and related equipment
CN108702692B (en) Function selection in a mobile network
CN110278096B (en) Communication method and device based on network slice
CN108353351B (en) Method for selecting service network, network equipment and management equipment
JP2021185690A (en) Session management method, system and terminal
EP3908020A1 (en) Method and apparatus for selecting an access and mobility management function in a mobile communication system
WO2021027817A1 (en) Parent node selection method and apparatus, device and medium
WO2020164507A1 (en) Method and device for selecting cag cell, communication control method and device for cag cell, network element, terminal, and storage medium
JP7389225B2 (en) Method and apparatus for determining security protection mode
CN111586770B (en) Session management method and device
CN107302788A (en) The system of selection of core net, apparatus and system
CN114080003B (en) Method and device for accessing network
CN115484587A (en) Network element equipment selection method and device and storage medium
CN103079245A (en) Method and equipment for switching non-speaking-right users in LTE (long-term evolution) trunking system
CN111093285A (en) Session creation method, network element and computer readable storage medium
CN109246767B (en) Data transfer method, device, network function entity and SMF entity
CN101541062A (en) Roaming network access method and equipment
CN113259924A (en) Private network subscription information updating method and device
WO2023280581A1 (en) Method, apparatus and computer program
CN114071801B (en) State indication method of terminal equipment and communication device
WO2021115464A1 (en) Network slice selection method and related device
WO2021139464A1 (en) Dual-connection handover method, handover device and storage medium
CN112654068B (en) Reselection control method of mobile terminal and base station
CN114915958A (en) Disaster roaming method, device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant