WO2018086451A1

WO2018086451A1 - Network access method and device utilized by terminal, and downlink data delivery method and device

Info

Publication number: WO2018086451A1
Application number: PCT/CN2017/106978
Authority: WO
Inventors: 李志军; 黄梅青
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-11-14
Filing date: 2017-10-20
Publication date: 2018-05-17
Also published as: CN108377564A; CN108377564B

Abstract

A network access method and device utilized by a terminal, and a downlink data delivery method and device. The network access method utilized by a terminal comprises: remote user equipment (UE) transmits, via relay UE, and to a core network control plane function (CN-CP), a non-access stratum (NAS) layer access request; and the remote UE receives a NAS access response responded by the CN-CP and via the relay UE, and obtains, according to the NAS access response, bearer information of the remote UE. In the embodiment, the remote UE can realize, by using the relay UE relaying data, interaction with the CN-CP, completing an access process or a relay UE reselection process.

Description

Method and device for terminal accessing network, downlink data delivery method and device

Technical field

The present disclosure relates to the field of communications, and in particular, to a method and apparatus for a terminal accessing a network, and a downlink data delivery method and apparatus.

Background technique

With the development of wireless communication networks, especially the construction of high-speed and high-bandwidth Long Term Evolution (LTE)/Evolved Packet System (EPS) systems, various multimedia applications have been stimulated. Business development. Many businesses, such as social networking, close-range data sharing, and local advertising, are placing increasing demands on near-field communications. In short-range communication, special emphasis is placed on communication between devices and devices, that is, device-to-device (D2D) communication.

In response to the demand for D2D communication, the 3rd Generation Partnership Project (3GPP) established a special research project, Proximity Service (ProSeimity Service, referred to as ProSe) to support D2D communication. In D2D communication, there is a typical service requirement, which enables a remote terminal (Remote UE) to access the network through a relay terminal (Relay UE) without network coverage.

FIG. 1 is a schematic diagram of a structure in which a remote terminal (Remote UE) accesses an LTE/EPS system through a relay terminal (Relay UE) in the related art.

The architecture shown in Figure 1 mainly includes the following parts: (1) LTE part of the wireless subsystem, namely Evolved Universal Terrestrial Radio Access Network (E-UTRAN); (2) EPS The core network subsystem part, also known as the Evolved Packet Core (EPC); (3) the short-range communication service part, namely the ProSe architecture function.

The E-UTRAN radio access network includes an enhanced NodeB node (Evolved NodeB, eNodeB for short), that is, a base station portion of LTE.

The EPC packet core network includes a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a packet data network. A gateway (PDN Gateway, P-GW for short), a Serving GPRS Support Node (SGSN), and a Policy and Charging Enforcement Function (PCRF), where:

HSS (Home Subscriber Server): a home subscriber data server, which is a permanent storage location for user subscription data, and is located in the home network to which the user subscribes;

MME (Mobility Management Entity): The mobility management unit is the location where the user subscription data is stored in the current network. It is responsible for the non-access stratum (Non-Access Stratum, NAS) signaling management of the terminal to the network, and the user idle mode. Tracking and paging management functions and bearer management;

S-GW (Serving Gateway): A gateway that is a core network to a wireless system. It is responsible for user plane bearer from the terminal to the core network, data buffering in the idle mode of the terminal, function of initiating service requests on the network side, legal eavesdropping and grouping. Data routing and forwarding functions;

P-GW (PDN Gateway): A packet data network gateway, which is an evolved packet domain system (EPS) and a gateway of the external network of the system, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy application of the terminal.

Policy and Charging Enforcement Function (PCRF): The policy and charging rule function entity is responsible for providing policy control and charging rules to the PCEF.

ProSe architecture functions, including ProSe Function (PF), ProSe Application Server (PAS), Relay UE, and Remote UE.

PF (ProSe Function): Authorizes the short-range communication of the terminal, provides inter-terminal discovery assistance, and the like.

PAS (ProSe Application Server): Provides specific near-field communication service support.

Relay UE: Provides relay access support for remote terminals.

Remote UE: accesses the network through a relay terminal (Relay UE) to obtain an IP service.

2 is a schematic diagram of a process in which a remote terminal accesses a network to obtain an IP service through a relay terminal based on the architecture shown in FIG. 1, and the process includes the following steps:

S201. The Relay UE is attached to the network to establish a PDN connection.

S202, the Remote UE discovers the Relay UE;

In this step, in the process of discovering the Relay UE, the APN supported by the Relay UE will serve as an important reference information;

S203. On the PC5 interface, the Remote UE requests the Relay UE to establish one-to-one (One-2-One) communication;

In this step, the Remote UE carries user information (User Info) in the request, including a specific APN.

S204, the Relay UE uses the specific APN carried in the request by the Remote UE in S203, and requests the network to establish a corresponding PDN connection, which is used to provide relay communication for the Remote UE.

S205. The Relay UE allocates an IP address to the Remote UE, where the address is either a private IPv4 address or an IPv6 prefix.

S206. The Relay UE sends a remote terminal access report to the MME, and carries the identifier of the remote terminal, a Remote UE ID, and an IP address.

S207, the MME sends a remote terminal access report to the PGW, and carries the information of the Remote UE, including the identifier of the remote terminal, the Remote UE ID, and the IP address.

The PGW stores the information of the Remote UE locally. Using this information, the PGW can gate the uplink and downlink data of the Remote UE, that is, whether to allow uplink and downlink data transmission.

S208. The Remote UE sends the uplink IP data, or receives the downlink IP data, and the IP data is relayed by the Relay UE, and the IP data is carried in the PDN connection established by the Relay UE for the relay.

According to the flow described in FIG. 2, the remote terminal (Remote UE) can access the network through the relay terminal (Relay UE) to obtain the IP service when there is no network information coverage. However, use In this access mode, the network has no control over the remote terminal (Remote UE). For example, there is no control over the access of the remote terminal, and there is no control over the reselection of the remote terminal by the remote terminal. In addition, the network cannot effectively implement remote access. The terminal performs downlink data delivery. Due to these shortcomings, some services that rely on terminal perception are difficult to implement.

Summary of the invention

The embodiments of the present disclosure provide a method and an apparatus for a terminal to access a network, and a downlink data delivery method and apparatus, so as to at least solve the related art, the network has no control to the remote terminal (Remote UE), or the network cannot effectively implement downlink data to the remote terminal. The problem of delivery.

According to an embodiment of the present disclosure, a method for a terminal to access a network is provided, including:

The remote terminal sends a non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal;

The remote terminal receives the NAS access response returned by the CN-CP through the relay terminal, and obtains the bearer information of the remote terminal according to the NAS access response.

Optionally, the remote terminal sends the NAS access request to the CN-CP by using the relay terminal, where the remote terminal sends the NAS access request to the relay terminal by using the PC5 signaling message or the PC5 data packet, where the NAS access request is passed. Following the terminal forwarding to the CN-CP;

Receiving, by the remote terminal, the NAS access response returned by the CN-CP through the relay terminal includes: the remote terminal receiving the NAS access response sent by the relay terminal to the relay terminal by using the PC5 signaling message or the PC5 data packet, wherein the NAS access response It is sent by the CN-CP to the remote terminal through the relay terminal.

Optionally, the NAS access request includes one or a combination of the following information:

The network identity of the remote terminal, the PDN connection establishment request, or the PDN connection update request.

Optionally, the NAS access request includes: a neighbor communication identifier of the remote terminal.

Optionally, the NAS access response includes:

The bearer information of the remote terminal, where the bearer information of the remote terminal includes: an IP address allocated to the remote terminal and a core network bearer.

Optionally, the NAS access response further includes:

The temporary identifier assigned by the CN-CP to the remote terminal.

Optionally, in the case that the remote terminal initially accesses the network, the relay terminal is a relay terminal selected when the remote terminal initially accesses the network.

Optionally, the NAS access request includes an attach request Attach Request; and the NAS access response includes an attach response Attach Response.

Alternatively, in the case where the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal.

Optionally, the NAS access request includes a PDN connection update request; the NAS access response includes a PDN connection update response.

Optionally, the NAS access request further includes the following information: an IP address of the remote terminal.

According to another embodiment of the present disclosure, a method for a terminal to access a network is provided, including:

The relay terminal receives a non-access stratum NAS access request from the remote terminal;

The relay terminal forwards the NAS access request to the core network control plane function CN-CP;

The relay terminal receives the NAS access response returned by the CN-CP;

The relay terminal forwards the NAS access response to the remote terminal.

Optionally, the receiving, by the relay terminal, the NAS access request from the remote terminal includes: the relay terminal receiving the NAS access request sent by the remote terminal by using the PC5 signaling message or the PC5 data packet;

The relay terminal forwarding the NAS access response to the remote terminal includes: the relay terminal forwards the NAS access response to the remote terminal by using the PC5 signaling message or the PC5 data packet.

Optionally, the method further includes:

The relay terminal sends the relay access information to the CN-CP, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and a relay terminal identifier Relay UE ID.

Optionally, the method further includes:

The relay terminal receives the identifier of the remote terminal transmitted by the CN-CP, the Remote UE ID.

Optionally, the forwarding, by the relay terminal, the NAS access response to the remote terminal includes:

The relay terminal forwards the NAS access response to the remote terminal according to the remote terminal identifier of the remote terminal.

Optionally, the method further includes:

The relay terminal receives the relay wireless data bearer sent by the CN-CP, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID.

Optionally, after the relay terminal receives the relay wireless data bearer sent by the CN-CP, the method further includes:

The relay terminal stores the relay wireless data bearer in the context; and/or

The relay terminal binds the PC5 interface of the remote terminal to the relay wireless data bearer serving the remote terminal.

Optionally, the information sent by the CN-CP to the relay terminal is carried in an access layer AS access response sent by the wireless node RAN to the relay terminal.

According to still another embodiment of the present disclosure, a method for a terminal to access a network is provided, including:

The wireless node RAN receives the non-access stratum NAS access request from the remote terminal forwarded by the relay terminal;

The RAN sends a NAS access request to the core network control plane function CN-CP;

The RAN receives the NAS access response returned by the CN-CP;

The RAN sends a NAS access response to the remote terminal through the relay terminal.

Optionally, the method further includes:

The RAN receives the relay wireless data bearer returned by the CN-CP and the remote UE ID of the remote terminal, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID. .

Optionally, after the RAN receives the relay wireless data bearer returned by the CN-CP, the method further includes:

The RAN stores the relay wireless data bearer in the context of the relay terminal.

Optionally, the sending, by the RAN, the NAS access response to the remote terminal by using the relay terminal includes:

The RAN sends an access layer AS access response to the relay terminal, where the AS access response includes: a NAS access response, an identifier of the remote terminal, a Remote UE ID, and a relay wireless data bearer.

The core network control plane function CN-CP receives the non-access stratum NAS access request sent by the remote terminal through the relay terminal;

The CN-CP establishes or updates a PDN connection and bearer for the remote terminal in response to the NAS access request;

The CN-CP returns a NAS access response to the remote terminal through the relay terminal.

Optionally, the method further includes:

The CN-CP receives the relay access information, where the relay access information includes one or a combination of the following information: an identifier of the relay terminal, a Relay UE ID, and a relay access indication, a Relay Indicator.

Optionally, the NAS access request includes a neighbor communication identifier of the remote terminal.

Optionally, the CN-CP establishes a PDN connection and a bearer for the remote terminal in response to the NAS access request, and includes: CN-CP to the core network user plane function CN-UP if the NAS access request includes the PDN connection establishment request Sending a bearer setup request, where the bearer setup request is used to request the CN-UP to establish a PDN connection and bearer for the remote terminal; or

The CN-CP updates the PDN connection and the bearer for the remote terminal in response to the NAS access request, and includes: when the NAS access request includes the PDN connection update request, the CN-CP sends a bearer update request to the core network user plane function CN-UP. The bearer update request is used to request the CN-UP to update the PDN connection and bearer for the remote terminal.

Optionally, after the CN-CP establishes or updates the PDN connection and the bearer for the remote terminal in response to the NAS access request, the method further includes:

The CN-CP stores context information of the remote terminal, wherein the context information of the remote terminal includes one or a combination of the following information:

Remote terminal ID of the remote terminal;

The bearer information of the remote terminal, including the IP address assigned to the remote terminal and the core network bearer;

The relay access information of the remote terminal, where the relay access information includes: an identifier of the relay terminal, a Relay UE ID.

Optionally, the context information of the remote terminal further includes:

Neighbor communication identifier of the remote terminal.

The CN-CP stores context information of the relay terminal, where the context information of the relay terminal includes:

The information of the remote terminal accessed by the relay terminal, wherein the information of the remote terminal accessed by the relay terminal includes one or a combination of the following information: the identifier of the remote terminal accessed through the relay terminal, the Remote UE ID, and the The IP address of the remote terminal accessed by the terminal.

The CN-CP binds the core network of the remote terminal to the relay wireless data bearer serving the remote terminal according to the relay access information of the remote terminal, where the attribute of the relay wireless data bearer is marked with bearer binding information. The bearer binding information includes an identifier of the remote terminal, a Remote UE ID.

Optionally, the method further includes:

The CN-CP returns the identifier of the remote terminal and the relay radio data bearer, wherein the attribute of the relay radio data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID.

Optionally, the NAS access response includes bearer information of the remote terminal, where the bearer information of the remote terminal includes: an IP address allocated to the remote terminal and a core network bearer.

Optionally, the NAS access response includes a temporary identifier assigned by the CN-CP to the remote terminal.

Optionally, in the case that the remote terminal initially accesses the network, the relay terminal is a relay terminal selected when the remote terminal initially accesses the network, the NAS access request includes an attach request Attach Request, and the NAS access response includes an attach response. Attach Response.

Optionally, in the case that the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal, the NAS access request includes the PDN connection update request, and the NAS access response includes the PDN connection update. response.

Optionally, the NAS access request includes the following information: an IP address assigned to the remote terminal when the remote terminal initially accesses the network.

Optionally, after the CN-CP receives the NAS access request sent by the remote terminal through the relay terminal, the method further includes:

The CN-CP determines the change of the relay terminal selected by the remote terminal according to the NAS access request and the relay access information and/or the IP address assigned to the remote terminal when the remote terminal continues to use the initial access network.

According to still another embodiment of the present disclosure, a downlink data delivery method is provided, including:

The core network control plane function CN-CP receives downlink data sent to the remote terminal;

The CN-CP transmits downlink data to the remote terminal through the relay terminal.

Optionally, before the CN-CP receives the downlink data sent to the remote terminal, the method further includes:

The CN-CP stores context information of the remote terminal, where the context information of the remote terminal includes:

Remote terminal ID of the remote terminal;

Authentication parameters of the remote terminal;

Bearer information of the remote terminal, where the bearer information includes an IP address allocated to the remote terminal and a core network bearer;

The relay access information of the remote terminal, wherein the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and a relay terminal identifier Relay UE ID.

Optionally, before the remote terminal is in an idle state, before the CN-CP sends the downlink data to the remote terminal by using the relay terminal, the method further includes:

The CN-CP initiates a paging request, where the paging request carries the identifier Relay UE ID of the relay terminal and the identifier Remote UE ID of the remote terminal.

Optionally, before the CN-CP initiates the paging request, the method further includes:

In the case that the downlink data is the short message service SMS information, the CN-CP determines that the SMS information is sent to the remote terminal according to the terminal identity UE ID carried in the SMS delivery request message;

In the case that the downlink data is the downlink IP data, the CN-CP determines that the downlink IP data is sent to the remote terminal according to the bearer information carried in the downlink data notification request message from the core network user plane function CN-UP, and according to the remote terminal. The context determines the identity of the remote terminal, the Remote UE ID, and the identity of the relay terminal, the Relay UE ID.

According to still another embodiment of the present disclosure, an apparatus for a terminal to access a network is provided, which is applied to a remote terminal, and the apparatus includes:

The first sending module is configured to send a non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal;

The first receiving module is configured to receive a NAS access response returned by the CN-CP through the relay terminal, and obtain bearer information of the remote terminal according to the NAS access response.

Optionally, the NAS access response includes:

Optionally, in a case that the remote terminal initially accesses the network, the first sending module is configured to send a NAS access request including a PDN connection establishment request;

In the case where the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal, and the first transmission module is configured to transmit the NAS including the PDN connection update request. Access request.

According to still another embodiment of the present disclosure, an apparatus for a terminal to access a network is provided, which should be configured as a relay terminal, and the apparatus includes:

a second receiving module, configured to receive a non-access stratum NAS access request from the remote terminal;

The first forwarding module is configured to forward the NAS access request to the core network control plane function CN-CP;

a third receiving module, configured to receive a NAS access response returned by the CN-CP;

The second forwarding module is configured to forward the NAS access response to the remote terminal.

Optionally, the first forwarding module is further configured to send the relay access information to the CN-CP, where the relay access information includes one or a combination of the following information: a relay access indication, a relay indicator, and an identifier of the relay terminal. Relay UE ID.

Optionally, the third receiving module is further configured to receive the identifier Remote UE ID of the remote terminal sent by the CN-CP.

Optionally, the second forwarding module is further configured to forward the NAS access response to the remote terminal according to the identifier of the remote terminal, the Remote UE ID.

Optionally, the third receiving module is further configured to receive the relay wireless data bearer sent by the CN-CP, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal. UE ID.

Optionally, the device further includes:

a first storage module configured to store a relay wireless data bearer in a context; and/or

The first bearer binding module is configured to bind the PC5 interface of the remote terminal and the relay wireless data bearer serving the remote terminal.

According to still another embodiment of the present disclosure, an apparatus for a terminal to access a network is provided, which is applied to a wireless node RAN, and the apparatus includes:

a fourth receiving module, configured to receive a non-access stratum NAS access request from the remote terminal forwarded by the relay terminal;

The second sending module is configured to send a NAS access request to the core network control plane function CN-CP;

a fifth receiving module, configured to receive a NAS access response returned by the CN-CP;

The third sending module is configured to send the NAS access response to the remote terminal through the relay terminal.

Optionally, the fifth receiving module is further configured to receive the relay wireless data bearer returned by the CN-CP and the identifier remote UE ID of the remote terminal, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer is bound The information includes the identity of the remote terminal, the Remote UE ID.

Optionally, the device further includes:

The second storage module is configured to store the relay wireless data bearer in the context of the relay terminal.

According to still another embodiment of the present disclosure, an apparatus for a terminal to access a network is provided, which is applied to a core network control plane function CN-CP, including:

a sixth receiving module, configured to receive a non-access stratum NAS access request sent by the remote terminal through the relay terminal;

Establishing or updating a module, configured to establish or update a PDN connection and bearer for the remote terminal in response to the NAS access request;

The fourth sending module is configured to return a NAS access response to the remote terminal through the relay terminal.

Optionally, the device further includes:

a second storage module, configured to store context information of the remote terminal after the establishing or updating module responds to the NAS access request to establish or update the PDN connection and the bearer for the remote terminal, where the context information of the remote terminal includes one of the following information: Or combination:

Remote terminal ID of the remote terminal;

Optionally, the fourth sending module is further configured to return the identifier of the remote terminal, the Remote UE ID. And a relay wireless data bearer, wherein the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes an identifier of the remote terminal, a Remote UE ID.

Optionally, the device further includes:

a determining module, configured to determine, according to the NAS access request and the relay access information, a change of the relay terminal selected by the remote terminal and/or the remote terminal continues to use the initial access if the NAS access request includes the PDN connection update request The IP address assigned to the remote terminal at the time of the network.

According to still another embodiment of the present disclosure, a downlink data delivery device is provided, which is applied to a core network control plane function CN-CP, and the device includes:

a seventh receiving module, configured to receive downlink data sent to the remote terminal;

The fifth sending module is configured to send downlink data to the remote terminal by using the relay terminal.

According to still another embodiment of the present disclosure, a storage medium is also provided. The storage medium is arranged to store program code arranged to perform any of the above methods.

Embodiments of the present invention also provide a processor for running a program, wherein the program is executed to perform the steps of any of the above methods.

Through the solution of some embodiments of the present disclosure, the remote terminal can implement interaction with the control plane of the core network through the relay of the relay terminal, complete the access process or the reselection process of the relay terminal, and the control plane of the core network is implemented by the relay terminal. The interaction with the remote terminal can implement the bearer creation of the remote terminal and the bearer update when the relay reselection is implemented, and can also initiate the downlink data delivery to the remote terminal. Through the solution of the above embodiments, information or data transmission between the network side and the remote terminal is implemented, and the network side can implement effective control on the terminal access or relay reselection process, and the remote terminal is relayed. When the terminal accesses the network, the network can sense or control the remote terminal.

DRAWINGS

The drawings described herein are intended to provide a In the drawing:

1 is a schematic diagram of a structure in which a remote terminal accesses LTE/EPS through a relay terminal in the related art;

2 is a schematic diagram of a process in which a remote terminal accesses an LTE/EPS network through a relay terminal in the related art;

3 is a flowchart of a method for a terminal connected to a network on a remote terminal side according to an embodiment of the present disclosure;

4 is a flowchart of a method for a terminal connected to a network on a relay terminal side according to a first embodiment of the present disclosure;

5 is a flowchart of a method for a terminal connected to a network on a wireless node side according to a first embodiment of the present disclosure;

6 is a flowchart of a method for a terminal accessing a network applied to a function side of a core network control plane according to Embodiment 1 of the present disclosure;

7 is a flowchart of a downlink data delivery method applied to a function side of a control plane of a core network according to Embodiment 2 of the present disclosure;

8 is a structural block diagram of an apparatus for a terminal applied to a remote terminal to access a network according to Embodiment 3 of the present disclosure;

9 is a structural block diagram of an apparatus for a terminal applied to a relay terminal to access a network according to Embodiment 3 of the present disclosure;

10 is a structural block diagram of an apparatus for a terminal of a wireless node to access a network according to Embodiment 3 of the present disclosure;

11 is a structural block diagram of an apparatus for a terminal accessing a network applied to a core network control plane function according to Embodiment 3 of the present disclosure;

12 is a structural block diagram of a downlink data delivery device applied to a core network control plane function according to Embodiment 4 of the present disclosure;

FIG. 13 is a schematic diagram of an architecture according to Embodiment 5 of the present disclosure.

14A is a first schematic diagram of a control plane protocol stack architecture according to Embodiment 5 of the present disclosure;

14B is a second schematic diagram of a control plane protocol stack architecture according to Embodiment 5 of the present disclosure;

14C is a schematic diagram of a user plane protocol stack according to Embodiment 5 of the present disclosure;

15 is a schematic flowchart of a remote terminal accessing a network through a relay terminal according to Embodiment 6 of the present disclosure;

16 is a schematic flowchart of a remote terminal accessing a network through a relay terminal according to Embodiment 7 of the present disclosure;

17 is a schematic flowchart of a core network control plane function after placing a remote terminal into an idle state after the relay terminal enters an idle state according to Embodiment 8 of the present disclosure;

18 is a schematic flowchart of an application server sending a downlink SMS message to a remote terminal according to Embodiment 9 of the present disclosure;

19 is a schematic flowchart of sending downlink IP data to a remote terminal after the relay terminal and the remote terminal enter an idle state according to Embodiment 10 of the present disclosure;

FIG. 20 is a schematic flowchart of re-activating a PDN connection after a remote terminal reselects a relay terminal according to Embodiment 11 of the present disclosure.

detailed description

The present disclosure will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second", and the like in the specification and claims of the present disclosure are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Embodiment 1

According to a first embodiment of the present disclosure, a method for a terminal to access a network is provided, which is applied to a remote terminal side, and FIG. 3 is a flowchart of a method for a terminal applied to a remote terminal side to access a network according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps:

Step S302, the remote terminal controls the function of the core network through the relay terminal (Core Network-Control Plane (referred to as CN-CP) sends a NAS access request;

Step S304: The remote terminal receives the NAS access response returned by the CN-CP through the relay terminal, and obtains the bearer information of the remote terminal according to the NAS access response.

Through the method, the remote terminal can realize the interaction with the control plane of the core network through the relay of the relay terminal, complete the access process or the reselection process of the relay terminal, and the control plane of the core network realizes the interaction with the remote terminal through the relay terminal. The bearer creation of the remote terminal and the bearer update when the relay reselection are implemented can be implemented. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To achieve the purpose of the network to sense or control the remote terminal.

Optionally, the information exchange between the remote terminal and the relay terminal may be implemented by using a PC5 interface. For example, in step S302, the remote terminal may send a NAS access request to the relay terminal by using a PC5 signaling message or a PC5 data packet. The NAS access request is forwarded to the CN-CP through the relay terminal. In step S304, the remote terminal can receive the NAS access response sent by the relay terminal to the relay terminal by using the PC5 signaling message or the PC5 data packet. The NAS access response is sent by the CN-CP to the remote terminal through the relay terminal.

In order to facilitate the CN-CP to authenticate the remote terminal, the NAS access request sent by the remote terminal may include one or a combination of the following information: a network identity of the remote terminal, a PDN connection establishment request, or a PDN connection update request.

Optionally, the NAS access request may include: a neighbor communication identifier of the remote terminal. By carrying the neighbor communication identifier of the remote terminal in the NAS access request, the CN-CP can simultaneously mark the neighbor communication identifier of the remote terminal when returning the NAS access response, so that the relay terminal forwards the NAS access response to the correct one. Remote terminal.

The NAS access response may include bearer information of the remote terminal, where the bearer information of the remote terminal includes: an IP address allocated to the remote terminal and a core network bearer. The remote terminal can obtain the bearer information of the remote terminal by using the above information carried in the NAS access response.

Optionally, the NAS access response may further include: a temporary allocation of the CN-CP to the remote terminal. Logo.

In the case that the remote terminal initially accesses the network, the relay terminal described above is the relay terminal selected when the remote terminal initially accesses the network. Optionally, the NAS access request includes an attach request Attach Request; and the NAS access response includes an attach response Attach Response.

In the case where the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal described above is the target relay terminal. Optionally, the NAS access request includes a PDN connection update request; the NAS access response includes a PDN connection update response.

Optionally, the NAS access request may further include the following information: an IP address of the remote terminal. For example, the IP address assigned by the CN-CP to the remote terminal when the remote terminal first accesses the network. By carrying the IP address, the CN-CP can identify the remote terminal and confirm that the current relay access information changes according to the context of the remote terminal, thereby performing PDN connection and bearer update for the remote terminal.

According to the first embodiment of the present disclosure, a method for a terminal to access a network is further provided, which is applied to a relay terminal side. FIG. 4 is a flowchart of a method for a terminal connected to a network on a relay terminal side according to a first embodiment of the present disclosure. As shown in FIG. 4, the process includes the following steps:

Step S402, the relay terminal receives a NAS access request from the remote terminal;

Step S404, the relay terminal forwards the NAS access request to the CN-CP;

Step S406: The relay terminal receives the NAS access response returned by the CN-CP.

Step S408, the relay terminal forwards the NAS access response to the remote terminal.

Through the method, the relay terminal can implement the relay between the remote terminal and the CN-CP, assist the remote terminal to complete the access process or the request process of the relay terminal reselection, and simultaneously assist the core network control plane to implement the bearer to the remote terminal. Create and implement bearer updates when relay reselection. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To achieve the purpose of the network to sense or control the remote terminal.

Optionally, the information interaction between the remote terminal and the relay terminal can be implemented through the PC5 interface. For example, in S402, the relay terminal may receive the NAS access request sent by the remote terminal using the PC5 signaling message or the PC5 data packet; in S404, the relay terminal may forward the packet to the remote terminal by using the PC5 signaling message or the PC5 data packet. NAS access response.

In a preferred embodiment, the relay terminal may send the relay access information to the CN-CP, where the relay access information includes one or a combination of the following information: the relay access indication relay indicator, the relay terminal Identifies the Relay UE ID. Through this method, the CN-CP can learn the relay access information of the remote terminal, thereby facilitating maintaining the context of the remote terminal and the context of the relay terminal in the core network.

In order to facilitate the relay terminal to forward the NAS access response to the correct remote terminal, the relay terminal may receive the remote UE ID of the remote terminal sent by the CN-CP, and the information may be that the relay terminal receives the NAS connection from the CN-CP. Receiving the response from the CN-CP, as a preferred implementation manner, the identifier of the remote terminal, the Remote UE ID, may be encapsulated outside the NAS access response, and after the relay terminal resolves the identifier of the remote terminal, the Remote UE ID. And transmitting the NAS access response to the remote terminal according to the identifier of the remote terminal, the Remote UE ID.

Preferably, the relay terminal further receives the relay wireless data bearer sent by the CN-CP, wherein the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID. After the relay terminal receives the relay wireless data bearer sent by the CN-CP, the method further includes: the relay terminal stores the relay wireless data bearer in the context; and/or the relay terminal connects the remote terminal's PC5 interface and serves the remote The relay wireless data bearer binding of the terminal.

Preferably, the information sent by the CN-CP to the relay terminal (eg, the NAS access response, the relay wireless data bearer, and the remote terminal ID of the remote terminal) may be sent to the relay terminal through the RAN, for example, the above information may be It is carried in the access layer AS access response sent by the RAN to the relay terminal.

According to a first embodiment of the present disclosure, a method for a terminal to access a network is provided. FIG. 5 is a flowchart of a method for a terminal connected to a network on a wireless node side according to a first embodiment of the present disclosure, as shown in FIG. The process includes the following steps:

Step S502, the RAN receives a non-access stratum NAS access request from a remote terminal forwarded by the relay terminal;

Step S504, the RAN sends a NAS access request to the CN-CP.

Step S506, the RAN receives the NAS access response returned by the CN-CP.

Step S508, the RAN sends a NAS access response to the remote terminal through the relay terminal.

Through the method, the RAN serves as a serving node of the relay terminal, and can support the remote terminal to assist the remote terminal in completing the access process or the request process of the relay terminal reselection through the interaction between the relay terminal and the CN-CP, and assists The core network control plane implements bearer creation for remote terminals and bearer updates when relay reselection is implemented. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To achieve the purpose of the network to sense or control the remote terminal.

The RAN may receive the relay radio data bearer returned by the CN-CP and the identifier of the remote terminal, the remote UE ID, where the attribute of the relay radio data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal. ID.

After receiving the relay wireless data bearer returned by the CN-CP, the method further includes:

Optionally, the RAN sends the NAS access response to the remote terminal by using the relay terminal, where the RAN sends the access layer AS access response to the relay terminal, where the AS access response includes: the NAS access response, the identifier of the remote terminal. Remote UE ID and relay wireless data bearer.

According to the first embodiment of the present disclosure, a method for a terminal to access a network is provided, which is applied to a control function of a core network, and FIG. 6 is a terminal access applied to a function side of a control plane of a core network according to Embodiment 1 of the present disclosure. A flow chart of the method of the network, as shown in FIG. 6, the process includes the following steps:

Step S602, the CN-CP receives a NAS access request sent by the remote terminal through the relay terminal.

Step S604, the CN-CP establishes or updates a PDN connection and a bearer for the remote terminal in response to the NAS access request.

Step S606, the CN-CP returns a NAS access response to the remote terminal through the relay terminal.

With this method, the control plane of the core network can implement the interaction with the remote terminal through the relay of the relay terminal, thereby realizing the bearer creation of the remote terminal and the bearer update when the relay reselection is implemented. Through the above solution, information or data transmission between the network side and the remote terminal is realized, and the network side can effectively control the access or relay reselection process of the terminal, and the remote terminal accesses through the relay terminal. When the network is connected, the network can sense or control the remote terminal.

In a preferred embodiment, the CN-CP may receive relay access information from the relay terminal, where the relay access information includes one or a combination of the following information: the relay terminal ID of the relay terminal, and the relay Access indication Relay Indicator. Through this method, the CN-CP can learn the relay access information of the remote terminal, thereby facilitating maintaining the context of the remote terminal and the context of the relay terminal in the core network.

The NAS access request may include one or a combination of the following information:

Optionally, the NAS access request may further include a neighbor communication identifier of the remote terminal.

In response to the NAS access request, the CN-CP may implement establishment or update of the PDN connection and the bearer, as follows:

The CN-CP establishes a PDN connection and bearer for the remote terminal in response to the NAS access request, and includes: when the NAS access request includes the PDN connection establishment request, the CN-CP sends a bearer setup request to the core network user plane function CN-UP. The bearer setup request is used to request the CN-UP to establish a PDN connection and bearer for the remote terminal;

After obtaining the relevant information of the remote terminal, the CN-CP can locally maintain the context of the remote terminal, thereby facilitating the transmission of uplink and downlink data of the remote terminal, the control of the remote terminal, and the like. Preferably, the CN-CP establishes or updates a PDN connection and a remote terminal for the remote terminal in response to the NAS access request. After the bearer, the method further includes:

Remote terminal ID of the remote terminal;

Optionally, the context information of the remote terminal further includes:

Neighbor communication identifier of the remote terminal.

After obtaining the relay access information, the CN-CP can maintain the context of the relay terminal locally, thereby facilitating the state maintenance of the relay terminal and the remote terminal accessing the network through it, and the like. Preferably, after the CN-CP establishes or updates the PDN connection and the bearer for the remote terminal in response to the NAS access request, the method further includes:

In order to facilitate the transmission control of the uplink and downlink data of the remote terminal, after the CN-CP establishes or updates the PDN connection and the bearer for the remote terminal in response to the NAS access request, the method may further include:

In order to facilitate the relay terminal to deliver the NAS access response to the correct remote terminal, and in order to notify the relay terminal of the relay wireless data bearer, the CN-CP may return the remote terminal's identity Remote UE ID and the relay wireless data bearer. Among them, the attribute of the relay wireless data bearer is awarded The bearer binding information is recorded, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID. The information sent by the CN-CP to the relay terminal in the whole process, for example, the NAS access response, the remote terminal identifier Remote UE ID, and the relay wireless data bearer can be sent to the relay terminal through the RAN, for example, CN-CP The above information may be returned to the RAN through an initialization response, and then sent by the RAN to the relay terminal through the AS access response.

The NAS access response may include the bearer information of the remote terminal, where the bearer information of the remote terminal includes: an IP address allocated to the remote terminal and a core network bearer.

Optionally, the NAS access response may further include a temporary identifier assigned by the CN-CP to the remote terminal.

Optionally, in the case that the remote terminal initially accesses the network, the foregoing relay terminal is a relay terminal selected when the remote terminal initially accesses the network, and the NAS access request includes an attach request Attach Request; the NAS access response Includes Attach Response Attach Response.

Optionally, in the case that the remote terminal reselects from the original relay terminal to the target relay terminal, the foregoing relay terminal is a target relay terminal, and the NAS access request includes a PDN connection update request; the NAS access response includes PDN connection update response.

For the case where the remote terminal performs relay reselection, the remote terminal may carry the following information in the NAS access request: the IP address assigned to the remote terminal when the remote terminal initially accesses the network.

Optionally, after the CN-CP receives the NAS access request sent by the remote terminal by using the relay terminal, the method further includes: determining, by the CN-CP, the relay terminal selected by the remote terminal according to the NAS access request and the relay access information. The change and/or remote terminal continues to use the IP address assigned to the remote terminal when initially accessing the network. As a preferred implementation manner, the CN-CP determines that the NAS access request is a PDN connection update request, and/or the CN-CP determines that the relay access information changes through the relay access information, and the CN-CP may determine The relay terminal selected by the remote terminal changes, and the remote terminal continues to use the IP address assigned to the remote terminal when initially accessing the network. In addition, the CN-CP may also determine that the remote terminal is assigned to the remote terminal when the remote terminal continues to use the initial access network, when the remote terminal carried by the NAS access request initially accesses the network and is assigned to the remote terminal. IP address.

Embodiment 2

According to the second embodiment of the present disclosure, a downlink data delivery method is provided, which is applied to a core network control plane function, and FIG. 7 is a flowchart of a downlink data delivery method applied to a function side of a core network control plane according to Embodiment 2 of the present disclosure. Figure, as shown in Figure 7, the process includes the following steps:

Step S702, the CN-CP receives downlink data sent to the remote terminal.

Step S704, the CN-CP sends downlink data to the remote terminal through the relay terminal.

Through the method, the core network control plane implements interaction with the remote terminal through the relay terminal, and can implement downlink data delivery to the remote terminal. Through the above solution, data transmission between the network side and the remote terminal is realized, and when the remote terminal accesses the network through the relay terminal, the network can sense or control the remote terminal.

Remote terminal ID of the remote terminal;

Authentication parameters of the remote terminal;

Embodiment 3

In the embodiment, the apparatus for respectively accessing the network, which is applied to the remote terminal, the relay terminal, the wireless node, and the control function of the core network, is provided, and the devices are configured to implement the first embodiment and the preferred embodiment, and have been performed. The description will not be repeated. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

According to a third embodiment of the present disclosure, a device for accessing a network of a terminal is applied to a remote terminal, and FIG. 8 is a structural block diagram of an apparatus for accessing a network by a terminal applied to a remote terminal according to Embodiment 3 of the present disclosure, such as As shown in Figure 8, the device includes:

The first sending module 82 is configured to send a non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal;

The first receiving module 84 is coupled to the first sending module 82, configured to receive the NAS access response returned by the CN-CP through the relay terminal, and obtain bearer information of the remote terminal according to the NAS access response.

Through the device, the remote terminal can realize the interaction with the control plane of the core network through the relay of the relay terminal, complete the access process or the reselection process of the relay terminal, and the control interface of the core network realizes the interaction with the remote terminal through the relay terminal. The bearer creation of the remote terminal and the bearer update when the relay reselection are implemented can be implemented. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To reach the network to sense or control the remote terminal the goal of.

Optionally, the NAS access response may include:

In the case that the remote terminal initially accesses the network, the first sending module 82 is configured to send a NAS access request including a PDN connection establishment request; in the case where the remote terminal reselects from the original relay terminal to the target relay terminal, Following the terminal being the target relay terminal, the first transmitting module 82 is arranged to transmit a NAS access request including a PDN connection update request.

According to the third embodiment of the present disclosure, an apparatus for accessing a network of a terminal is applied to a relay terminal, and FIG. 9 is a structure of an apparatus for accessing a network by a terminal applied to a relay terminal according to Embodiment 3 of the present disclosure. The block diagram, as shown in Figure 9, includes:

The second receiving module 92 is configured to receive a non-access stratum NAS access request from the remote terminal;

The first forwarding module 94 is coupled to the second receiving module 92, and configured to forward the NAS access request to the core network control plane function CN-CP;

The third receiving module 96 is coupled to the first forwarding module 94, and configured to receive the NAS access response returned by the CN-CP;

The second forwarding module 98 is coupled to the third receiving module 96 and configured to forward the NAS access response to the remote terminal.

Through the device, the relay terminal can implement the relay between the remote terminal and the CN-CP, assist the remote terminal to complete the access process or the request process of the relay terminal reselection, and simultaneously assist the core network control plane to implement the bearer to the remote terminal. Create and implement bearer updates when relay reselection. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To achieve the purpose of the network to sense or control the remote terminal.

Optionally, the first forwarding module 94 is further configured to send relay access information to the CN-CP, where The relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and a relay terminal identifier Relay UE ID.

Optionally, the third receiving module 96 is further configured to receive an identifier of the remote terminal sent by the CN-CP.

Optionally, the second forwarding module 98 is further configured to forward the NAS access response to the remote terminal according to the identifier of the remote terminal, the Remote UE ID.

Optionally, the third receiving module 96 is further configured to receive the relay wireless data bearer sent by the CN-CP, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier of the remote terminal. Remote UE ID.

Optionally, the device further includes:

a first storage module coupled to the third receiving module 96, configured to store the relay wireless data bearer in the context; and/or

The first bearer binding module is coupled to the third receiving module 96 and configured to bind the PC5 interface of the remote terminal to the relay wireless data bearer serving the remote terminal.

According to a third embodiment of the present disclosure, a device for accessing a network of a terminal is applied to a wireless node RAN, and FIG. 10 is a structural block diagram of an apparatus for accessing a network by a terminal of a wireless node according to Embodiment 3 of the present disclosure. As shown in Figure 10, the device includes:

The fourth receiving module 1002 is configured to receive a non-access stratum NAS access request from the remote terminal forwarded by the relay terminal;

The second sending module 1004 is coupled to the fourth receiving module 1002, and configured to send a NAS access request to the core network control plane function CN-CP;

The fifth receiving module 1006 is coupled to the second sending module 1004, and configured to receive the NAS access response returned by the CN-CP;

The third sending module 1008 is coupled to the fifth receiving module 1006 and configured to send a NAS access response to the remote terminal through the relay terminal.

Through the device, the RAN acts as a service node of the relay terminal and can support remote terminal communication. The interaction between the relay terminal and the CN-CP assists the remote terminal in completing the access process or the request process of the relay terminal reselection, and simultaneously assists the core network control plane to implement bearer creation for the remote terminal and implements relaying Bearer updates for timing. Through the above solution, information transmission between the network side and the remote terminal is realized, and the network side can implement effective control on the terminal access or relay reselection process, when the remote terminal accesses the network through the relay terminal. To achieve the purpose of the network to sense or control the remote terminal.

Optionally, the fifth receiving module 1006 is further configured to receive the relay wireless data bearer returned by the CN-CP and the identifier Remote UE ID of the remote terminal, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer The binding information includes the identity of the remote terminal, the Remote UE ID.

Optionally, the device further includes:

A second storage module, coupled to the fifth receiving module 1006, is configured to store the relay wireless data bearer in the context of the relay terminal.

According to the third embodiment of the present disclosure, an apparatus for accessing a network of a terminal is applied to a CN-CP, and FIG. 11 is a device for accessing a network by a terminal applied to a control function of a core network according to Embodiment 3 of the present disclosure. The structural block diagram, as shown in FIG. 11, includes:

The sixth receiving module 1102 is configured to receive a non-access stratum NAS access request sent by the remote terminal through the relay terminal;

A setup or update module 1104, coupled to the sixth receive module 1102, configured to establish or update a PDN connection and bearer for the remote terminal in response to the NAS access request;

The fourth sending module 1106 is coupled to the setup or update module 1104 and is configured to return a NAS access response to the remote terminal through the relay terminal.

Through the device, the control plane of the core network can implement the interaction with the remote terminal through the relay of the relay terminal, thereby realizing the bearer creation of the remote terminal and the bearer update when the relay reselection is implemented. Through the above solution, information or data transmission between the network side and the remote terminal is realized, and the network side can effectively control the access or relay reselection process of the terminal, and the remote terminal accesses through the relay terminal. When the network is connected, the network can sense or control the remote terminal.

Optionally, the device further includes:

a second storage module, coupled to the setup or update module 1104, configured to store context information of the remote terminal after the setup or update module 1104 establishes or updates the PDN connection and bearer for the remote terminal in response to the NAS access request, wherein the remote location The context information of the terminal includes one or a combination of the following information:

Remote terminal ID of the remote terminal;

Optionally, the fourth sending module 1106 is further configured to return the identifier of the remote terminal, the Remote UE ID, and the relay wireless data bearer, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the remote The identifier of the terminal is the Remote UE ID.

Optionally, the device further includes:

a determining module, coupled to the sixth receiving module 1102, configured to determine, according to the NAS access request and the relay access information, a change of the relay terminal selected by the remote terminal and/or if the NAS access request includes the PDN connection update request Or the remote terminal continues to use the IP address assigned to the remote terminal when initially accessing the network.

Embodiment 4

In the embodiment, a downlink data delivery device is also provided, which is applied to the CN-CP. The device is configured to implement the foregoing second embodiment and the preferred embodiment, and the description has been omitted. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 12 is a structural block diagram of a downlink data delivery device applied to a core network control plane function according to Embodiment 4 of the present disclosure. As shown in FIG. 12, the device includes:

The seventh receiving module 1202 is configured to receive downlink data sent to the remote terminal.

The fifth sending module 1204 is configured to send downlink data to the remote terminal through the relay terminal.

Through the device, the core network control plane realizes interaction with the remote terminal through the relay terminal, and can implement downlink data delivery to the remote terminal. Through the above solution, data transmission between the network side and the remote terminal is realized, and when the remote terminal accesses the network through the relay terminal, the network can sense or control the remote terminal.

Embodiment 5

FIG. 13 is a schematic diagram of an architecture according to Embodiment 5 of the present disclosure, including:

-Remote UE: The remote terminal can only access through the Relay UE if there is no network coverage;

-Relay UE: a relay terminal that provides relay access for the Remote UE;

-RAN: a wireless node that provides wireless access to the Relay UE;

-CN-CP: The control function of the core network provides process control functions such as authentication, bearer resource management, and mobility management for Relay UE and Remote UE.

-CN-UP: The core network user plane function, providing IP address allocation and IP data routing for Relay UE and Remote UE;

-CN-SD: the core network subscription database, providing subscription data access functions for Relay UE and Remote UE;

- NG-Uu interface: an interface between the Relay UE and the RAN, for transmitting AS (Access Stratum, access layer) signaling;

- NG1 interface: an interface between the Relay UE and the CN-CP for transmitting NAS (Non-Access Stratum) signaling;

- NG2 interface: an interface between the RAN and the CN-CP, transmitting control plane signaling;

- NG3 interface: an interface between the RAN and the CN-UP, transmitting user plane data;

- NG4 interface: an interface between the CN-CP and the CN-UP, transmitting bearer control signaling;

In the architecture shown in Figure 13, the Relay UE acts as a NAS relay for the Remote UE, that is, receives the NAS message sent by the Remote UE on the PC5 interface, and forwards it to the CN-CP on the NG1 interface. Or receiving a NAS message sent by the CN-CP to the Remote UE on the NG1 interface, Forwarded to the Remote UE on the PC5 interface. That is, there is no physical NG1 interface between the Remote UE and the CN-CP, and the NAS message between the Remote UE and the CN-CP is encapsulated in the NG1 interface message between the Relay UE and the CN-CP.

When the architecture shown in Figure 13 is applied in LTE/EPS, it has the following correspondence:

-RAN: eNodeB;

-CN-CP: MME;

-CN-UP: SGW, PGW;

-CN-SD: HSS;

-NG-Uu: LTE-Uu interface;

-NG2: the S1-AP interface;

-NG3: the S1-U interface;

-NG4: that is, the S11 interface;

14A and FIG. 14B are schematic diagrams of a control plane protocol stack according to Embodiment 5 of the present disclosure, wherein:

- On the Relay UE, there is a NAS Relay protocol layer, which receives the NAS signaling sent by the Remote UE from the PC5 interface, and forwards the NAS signaling of the Remote UE to the CN-CP on the NG1 interface. On the other hand, the NAS signaling sent by the CN-CP to the Remote UE is received on the NG1 interface and forwarded to the Remote UE on the PC5 interface.

- On the PC5 interface, the Remote UE can send and receive NAS signaling in two ways:

-1) As shown in FIG. 14A, the Remote UE transmits NAS signaling to the Relay UE and NAS signaling from the Relay UE through the PC5 signaling plane (PC5-C). To this end, in the PC5 signaling plane, it is necessary to add a corresponding PC5 message, such as a NAS signaling relay request, a NAS signaling relay response, and the like.

-2) As shown in FIG. 14B, the Remote UE transmits NAS signaling to the Relay UE and NAS signaling from the Relay UE through the PC5 user plane (PC5-U). In order to distinguish the sending and receiving of the conventional IP data on the PC5-U, the following manner can be implemented: a special port is designated, and the port is only used for the transmission of the NAS signaling;

It can be seen from the protocol stack architecture shown in FIG. 14A and FIG. 14B that the architecture only affects the Remote UE, the Relay UE, and the CN-CP, and has little impact on the RAN.

14C is a schematic diagram of a user plane protocol stack according to Embodiment 5 of the present disclosure, where:

The -Relay UE provides mapping and conversion of the IP data transmission from the PC5 interface data to the Relay UE for the Remote UE. The uplink data of the remote UE on the PC5 interface is mapped by the Relay UE to the bearer of the PDN connection for relaying, and is sent to the core network. On the other hand, the downlink data sent by the core network to the Remote UE is taken out by the Relay UE from the bearer of the PDN connection for relaying, and is sent to the Remote UE through the PC5 interface.

Embodiment 6

15 is a schematic flowchart of a remote terminal accessing a network through a relay terminal according to Embodiment 6 of the present disclosure. In this embodiment, the Remote UE and the Relay UE receive and transmit NAS signaling on the PC5 signaling plane.

Figure 15 has the following steps:

S1501: The Relay UE is attached to the network to establish a PDN connection.

S1502, the Remote UE discovers the Relay UE;

In this step, the Relay UE selects a suitable Relay according to the capabilities broadcast by the Remote UE. In this solution, the Relay UE broadcasts the following capabilities: supported APN, whether to support NAS relay function.

S1503, on the PC5 interface, the Remote UE requests the Relay UE to establish one-to-one (One-2-One) communication;

In this step, the Relay UE allocates an IP address to the Remote UE, and the address is either a private IPv4 address or an IPv6 prefix, and the IP address is used only for communication between the Remote UE and the Relay UE on the PC5 interface.

S1504, on the PC5 interface, using a PC5 signaling message, and the Remote UE sends a NAS access request to the Relay UE;

In this step, the PC5 signaling message may be: a NAS relay request.

In this step, since the Remote UE is initially connected to the network in this embodiment, the NAS access request carried by the Remote UE is an Attach Request. In the attach request, a PDN setup request is included. The Remote UE can request a corresponding PDN connection and bearer using a specific APN requesting network. If no APN is specified, the CN-CP creates a PDN connection for the Remote UE using the default APN.

In this step, the Remote UE may further carry a ProSe UE ID in the NAS access request. The neighbor communication identifier is an identifier used by the Remote UE on the PC5 interface, for example, a layer 2 identifier (Layer 2 ID) of the Remote UE.

S1505: The Relay UE forwards the NAS access request of the Remote UE to the RAN, and sends the relay access information.

In this step, the relay UE sends the relay access information, where the relay access information includes one or a combination of the following information: a relay indication (Relay indication), and a relay terminal identifier (Relay UE ID).

S1506: The RAN sends an initialization request to the CN-CP.

In this step, the RAN carries the following information: a NAS access request of the Remote UE, and relay access information provided by the Relay UE.

S1507: The CN-CP acquires user subscription data of the Remote UE from the CP-SD.

S1508: The CN-CP authenticates the Remote UE.

S1509: The CN-CP sends a bearer setup request to the CN-UP according to the request of the Remote UE and the subscription data of the Remote UE, and establishes a corresponding PDN connection and bearer for the Remote UE.

The CN-CP selects the CN-UP for the Remote UE according to the APN requested by the Remote UE or the default APN set in the subscription data, and requests the CN-UP to create a corresponding bearer.

S1510: The CN-UP returns a bearer setup response to the CN-CP, and returns the created bearer.

In this step, the CN-UP allocates an IP address to the Remote UE and creates the requested bearer.

S1511: The CN-CP stores the context of the Remote UE and is in the context of the Remote UE. Recording relay access information;

In this step, the CN-CP stores the following information in the context of the Remote UE:

-Remote UE's network identity, such as IMSI;

-Remote UE bearer information, such as IP address and core network bearer;

-Remote UE relay access information, such as the relay terminal ID (Relay UE ID);

The information stored by the CN-CP in the context of the Remote UE may also include the neighbor communication identifier of the Remote UE.

In this step, the CN-CP stores the following information in the context of the Relay UE:

- information of all Remote UEs accessed through the Relay UE, such as the identifier of the remote terminal, the Remote UE ID, the IP address, and the like.

S1512: The CN-CP returns an initialization response to the RAN.

In this step, the CN-CP sends the following information through the initialization response:

- NAS access response: In this embodiment, the NAS access response is an Attach Response, and is forwarded by the Relay UE to the Remote UE;

- Remote UE ID: According to the remote terminal ID of the remote terminal, the Relay UE sends the NAS access response to the correct Remote UE. The identifier of the remote terminal, the remote UE ID, may be a network identity of the remote terminal (such as an IMSI), a neighboring communication identifier of the remote terminal, or a combination of the two.

- Relay wireless data bearer: The wireless data bearer is allocated to the Relay UE, and the Remote UE is provided with relay transmission of uplink and downlink data. The attributes of the wireless data bearer include bearer binding information. The bearer binding information includes an identifier of the remote terminal, a Remote UE ID;

In this step, the CN-CP matches the core network bearer of the Remote UE to the relay radio data bearer of the Relay UE according to the bearer binding information of the Remote UE. Then, all downlink data on the core network bearer of the Remote UE will be sent to the relay wireless data bearer of the Relay UE. On the other hand, all uplink data on the relay radio data bearer of the Relay UE will be sent to the core network of the Remote UE.

S1513. The RAN stores a context of the Relay UE.

In this step, the RAN records in the context of the Relay UE: the relay radio data bearer.

S1514. The RAN sends an AS access response to the Relay UE.

In this step, the RAN carries the information sent by the CN-CP in the foregoing step in the AS access response, that is, the NAS access response (the attachment response in this embodiment), the remote terminal identifier (Remote UE ID), Relay wireless data bearer.

S1515: The Relay UE receives the AS access response of the RAN, and stores its own context information.

In this step, the Relay UE records in its own context: the relay wireless data bearer.

The relay UE determines, according to the bearer binding information in the radio data bearer attribute, that the bearer is a relay transmission for providing uplink and downlink data for a remote UE. When the Relay UE receives the uplink data of the Remote UE on the PC5 interface, the Relay UE sends the received uplink data on the relay radio data bearer corresponding to the Remote UE. When the relay UE receives the downlink data on the relay radio data bearer, the relay UE sends the downlink data to the corresponding Remote UE on the PC5 interface according to the bearer binding information of the relay radio bearer. That is, the Relay UE binds the PC5 interface of the Remote UE and the relay radio data bearer serving the Remote UE on the Relay UE one by one to implement relay transmission of uplink and downlink data of the Remote UE.

S1516, on the PC5 interface, using the PC5 signaling message, the Relay UE sends a PC5 message to the Remote UE, and carries the NAS access response, in this embodiment, an Attach Response;

The attach response includes an IP address and a bearer allocated by the core network to the UE. Using the IP address and the bearer, the Remote UE may send uplink IP data or receive downlink IP data, and the uplink and downlink IP data are transmitted through the relay wireless data bearer of the Relay UE.

It should be noted that in the flow shown in FIG. 15, steps S1504 to S1516 may occur before step S1503.

Example 7

16 is a schematic flowchart of a remote terminal accessing a network through a relay terminal according to Embodiment 7 of the present disclosure. In this embodiment, the Remote UE and the Relay UE receive and transmit NAS signaling on the PC5 user plane.

Compared with the flow shown in Figure 15, the flow shown in Figure 16 has the following differences:

- on the PC5 interface, in steps S1604, S1608, S1616, using the PC5 user plane (ie PC5 data packet) between the Remote UE and the Relay UE to transmit the NAS signaling of the Remote UE;

- step S1603 must be performed before steps S1604 to S1616;

Example eight

FIG. 17 is a schematic flowchart of a core network control plane function placing an remote terminal in an idle state after the relay terminal enters an idle state according to Embodiment 8 of the present disclosure.

Figure 17 has the following steps:

S1701, the Relay UE is attached to the network;

S1702, as shown in Figure 16, the Remote UE discovers the Relay UE and accesses the network through the Relay UE.

S1703, the Relay UE enters an idle state;

S1704: The wireless node RAN sends a connection release request to the core network control plane function CN-CP.

S1705: The CN-CP sends an access bearer release request to the CN-UP.

After receiving the access bearer release request, the CN-UP releases the access bearer between the RAN and the CN-UP.

S1706: The CN-UP returns an access bearer release response to the CP-CN.

S1707: The CN-CP puts the Relay UE into an idle state, and puts the Remote UE accessed through the Relay UE into an idle state.

In this step, the CN-CP searches for the Remote accessed through the Relay UE by the following method. UE:

- look up the Remote UE information in the context of the Relay UE; or,

- In the context of the Remote UE, look up the Relay UE information, and according to the Relay UE information, determine whether the Remote UE is accessed via the Relay UE.

S1708, the CN-CP returns a connection release response to the RAN.

Example nine

FIG. 18 is a schematic flowchart of an application server transmitting a downlink SMS message to a remote terminal according to Embodiment 9 of the present disclosure.

Figure 18 has the following steps:

S1801. The application server AS wants to send an SMS message to the Remote UE. The AS initiates an SMS delivery request to the short message center SM-SC;

S1802: The SM-SC acquires a CN-CP currently attached by the Remote UE, and initiates an SMS delivery request to the CN-CP.

S1803: If the Remote UE is currently in an idle state, the CN-CP initiates a paging process.

In this step, the CN-CP determines that the paging needs to be initiated to the Remote UE according to the SMS delivery request message, and determines that the Remote UE is accessed by the relay terminal Relay UE according to the context of the Remote UE, and the CN-CP initiates the paging request. And carrying the identifier of the relay terminal, the Relay UE ID, and the identifier of the remote terminal, the Remote UE ID. The identifier of the remote terminal, the remote UE ID, may be one of the following: a network identity of the Remote UE (IMSI), and a neighboring communication identifier of the Remote UE (eg, Layer 2 ID of the Remote UE on the PC5 interface).

S1804: The CN-CP sends a paging request to the RAN, and carries the identifier of the relay terminal, the Relay UE ID.

In this step, according to the decision of the CN-CP in S1803, the paging request further carries the identifier of the remote terminal, the Remote UE ID.

S1805: The RAN sends a paging request to the Relay UE, and carries the identifier of the relay terminal, the Relay UE ID, and the identifier of the remote terminal, the Remote UE ID.

S1806: After receiving the paging request, the Relay UE detects, on the PC5 interface, whether the Remote UE is reachable;

In this step, if the Relay UE determines that the paging request only carries the identifier Relay UE ID of the relay terminal, the Relay UE itself responds to the paging. If the relay UE determines that the paging request carries the remote UE ID of the remote terminal, it detects whether the Remote UE is reachable on the PC5 interface according to the identifier of the remote terminal, the Remote UE ID. If the Relay UE determines that the PC5 connection with the Remote UE has been released, that is, the Remote UE is inaccessible, the Relay UE may not respond to the paging request.

S1807: The Relay UE initiates a service request process to the CN-CP in response to the paging, and restores the radio bearer, the access network bearer, and the core network bearer.

S1808. Since the Remote UE accesses the network through the Relay UE, the CN-CP determines that the SMS delivery should be initiated to the Relay UE.

S1809: The CN-CP sends a downlink NAS request to the Relay UE, and carries the SMS data to be sent to the Remote UE.

In this step, the CN-CP may send the SMS data to the Relay UE by one of the following methods:

Downlink Generic NAS Transport message, and set the type of the message to: relay SMS delivery;

Newly introduced relay SMS delivery message.

In the downlink general NAS transmission message or the relay SMS delivery message, the CN-CP carries the remote terminal ID (Remote UE ID), according to the Remote UE ID, the Relay UE can determine which correct Remote should be delivered to the SMS data. UE. The identifier of the remote terminal, the Remote UE ID, may be one of the following: a network identity of the Remote UE (IMSI), and a neighboring communication identifier of the Remote UE (such as a layer 2 identifier Layer 2 ID of the Remote UE on the PC5 interface).

S1810, on the PC5 interface, the Relay UE forwards the SMS delivery request to the Remote UE, and carries the SMS data.

S1811: On the PC5 interface, the Remote UE returns an SMS delivery response to the Relay UE.

S1812: The Relay UE sends a downlink NAS response to the CN-CP, and carries an SMS delivery response.

S1813: The CN-CP returns an SMS delivery response to the SM-SC.

S1814. The SM-SC returns an SMS delivery response to the AS.

Example ten

FIG. 19 is a schematic flowchart of transmitting downlink IP data to a remote terminal after the relay terminal and the remote terminal enter an idle state according to Embodiment 10 of the present disclosure.

Figure 19 has the following steps:

S1901, the Relay UE is attached to the network;

S1902, as shown in Figure 15, the Remote UE discovers the Relay UE and accesses the network through the Relay UE.

S1903, as shown in Figure 17, the Relay UE and the Remote UE enter an idle state;

S1904: The application service sends downlink data to the Remote UE, that is, sends downlink IP data to the IP address of the Remote UE.

S1905: The CN-UP sends a downlink data notification request to the CN-CP.

After receiving the downlink IP data, the CN-UP determines that the access bearer between the CN-UP and the RAN has been released, and sends a downlink data notification request to the CN-CP.

S1906: The CN-CP returns a downlink data notification response to the CN-UP.

S1907: The CN-CP determines that paging should be initiated to the Relay UE/Remote UE.

In this step, the CN-CP determines that the Remote UE should be paged according to the downlink data notification request. For example, if the CN-CP determines that the Remote UE is accessed via the relay terminal Relay UE, it is determined that the Relay UE and the Remote UE should be paged. Therefore, the CN-CP carries the identifier Relay UE ID of the relay terminal and the identifier Remote UE ID of the remote terminal in the paging request. The identifier of the remote terminal, the remote UE ID, may be one of the following: a network identity of the Remote UE (IMSI), and a neighboring communication identifier of the Remote UE (such as a layer 2 identifier of the Remote UE on the PC5 interface). 2ID).

S1908, the CN-CP sends a paging request to the RAN, and carries the identifier of the relay terminal, the Relay UE ID;

In this step, according to the decision of the CN-CP in S1907, the paging request further carries the identifier of the remote terminal, the Remote UE ID.

S1909, the RAN sends a paging request to the Relay UE, and carries the identifier of the relay terminal, the Relay UE ID, and the identifier of the remote terminal, the Remote UE ID.

S1910: After receiving the paging request, the Relay UE detects, on the PC5 interface, whether the Remote UE is reachable;

In this step, if the Relay UE determines that the paging request only carries the identifier Relay UE ID of the relay terminal, the Relay UE itself responds to the paging. If the relay UE determines that the paging request carries the remote UE ID of the remote terminal, it detects whether the Remote UE is reachable on the PC5 interface. If the Relay UE determines that the PC5 connection with the Remote UE has been released, that is, the Remote UE is inaccessible, the Relay UE may not respond to the paging request.

S1911: The Relay UE initiates a service request process to the CN-CP, and restores the radio bearer, the access network bearer, and the core network bearer.

S1912 to S1913, after the bearer is restored, the UP-GW sends downlink IP data, and the Relay UE forwards the downlink IP data to the Remote UE on the PC5 interface.

Embodiment 11

Figure 20 has the following steps:

S2001~S2004, the Remote UE is attached to the network through the Relay UE1, and establishes a PDN connection;

S2005~S2006, the Remote UE moves, reselects the Relay UE2, and establishes one-to-one communication with the Relay UE2;

S2007, on the PC5 interface, the Remote UE sends a NAS access request to the Relay UE2. The NAS access request is a PDN connection update request.

In this step, the Remote UE may carry the IP address assigned by the network to the Remote UE in the foregoing process.

S2008, the Relay UE2 forwards the NAS access request of the Remote UE to the RAN, and sends the relay access information;

S2009, the RAN sends an initialization request to the CN-CP, where the NAS carries the NAS access request of the Remote UE, and carries the relay access information;

S2010: After receiving the PDN connection update request of the Remote UE, the CN-CP determines that the PDN connection and the bearer update are performed.

In this step, the CN-CP determines that the selected relay terminal (Relay) of the Remote UE changes according to the request of the Remote UE and the Relay information of the Remote UE, needs to update the PDN connection, and should keep the previous assignment to the Remote UE. IP address.

S2011: The CN-CP sends a bearer update request to the CN-UP.

In this step, the CN-CP sends a bearer update request to the CN-UP as needed. For example, when the RAN node changes, the RAN tunnel port needs to be updated.

S2012: The CN-UP returns a bearer update response to the CN-CP, and returns the updated bearer.

S2013, the CN-CP stores the context of the Remote UE, and records new relay access information in the context of the Remote UE;

S2014, the CN-CP returns an initialization response to the RAN, and carries a NAS access response (in the present embodiment, a PDN connection update response), a remote terminal identifier Remote UE ID, a relay wireless data bearer, and the like;

S2015, the RAN stores a context of the Relay UE, and records information of the relay wireless data bearer in a context of the Relay UE;

S2016, the RAN sends an AS access response to the Relay UE, and carries information such as a PDN connection update response, a remote terminal identifier Remote UE ID, a relay wireless data bearer, and the like;

S2017, the Relay UE stores its own context, and stores information of the relay wireless data bearer in the context;

S2018: On the PC5 interface, the Relay UE sends a PC5 message to the Remote UE. In the PC5 message, carrying a NAS access response (in this embodiment, a PDN connection update response (PDN Response));

After the process is completed, the Remote UE may continue to use the IP address allocated by the network to the Remote UE when the UE is previously accessed by the Relay UE1, send uplink IP data, or receive downlink IP data, and the IP data is relayed by the Relay UE2. That is, through the process shown in this embodiment, the Remote UE can keep the IP address assigned by the network to the Remote UE unchanged when the Relay UE is switched, thereby implementing service continuity.

Through the solution provided by the embodiment of the present disclosure, the remote terminal can implement interaction with the control plane of the core network through the relay of the relay terminal, complete the access process or the reselection process of the relay terminal, and the control plane of the core network is implemented by the relay terminal. The interaction with the remote terminal can implement the bearer creation of the remote terminal and the bearer update when the relay reselection is implemented, and can also initiate the downlink data delivery to the remote terminal. Through the above solution, information or data transmission between the network side and the remote terminal is realized, and the network side can effectively control the access or relay reselection process of the terminal, and the remote terminal accesses through the relay terminal. When the network is connected, the network can sense or control the remote terminal.

It will be apparent to those skilled in the art that the various modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure, and is not intended to limit the disclosure, Various changes and modifications of the present disclosure are possible to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the present disclosure are intended to be included within the scope of the present disclosure.

Industrial applicability

Claims

A method for a terminal to access a network includes:

The remote terminal sends a non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal;

Receiving, by the remote terminal, the NAS access response returned by the CN-CP through the relay terminal, and obtaining bearer information of the remote terminal according to the NAS access response.
The method of claim 1 wherein

Sending, by the remote terminal, the NAS access request to the CN-CP by using the relay terminal, the remote terminal sending the NAS access to the relay terminal by using a PC5 signaling message or a PC5 data packet a request, wherein the NAS access request is forwarded to the CN-CP through the relay terminal;

Receiving, by the remote terminal, the NAS access response returned by the CN-CP through the relay terminal, the remote terminal receiving, by the remote terminal, the PC5 signaling message or the PC5 data packet to the relay The NAS access response sent by the terminal, wherein the NAS access response is sent by the CN-CP to the remote terminal through the relay terminal.
The method of claim 1 or 2, wherein the NAS access request comprises one or a combination of the following information:

The network identity of the remote terminal, a PDN connection establishment request, or a PDN connection update request.
The method of claim 1 or 2 or 3, wherein the NAS access request comprises: a neighbor communication identifier of the remote terminal.
The method of claim 1 or 2, wherein the NAS access response comprises:

The bearer information of the remote terminal, where the bearer information of the remote terminal includes: The IP address and core network bearer assigned to the remote terminal.
The method of claim 5, wherein the NAS access response further comprises:

The CN-CP is a temporary identifier assigned to the remote terminal.
The method according to any one of claims 1 to 6, wherein, in the case that the remote terminal initially accesses a network, the relay terminal is a relay terminal selected when the remote terminal initially accesses a network .
The method of claim 7, wherein the NAS access request comprises an attach request Attach Request; the NAS access response comprises an attach response Attach Response.
The method according to any one of claims 1 to 6, wherein, in the case where the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal.
The method of claim 9, wherein the NAS access request comprises a PDN connection update request; the NAS access response comprises a PDN connection update response.
The method of claim 9 or 10, wherein the NAS access request further comprises information of an IP address of the remote terminal.
A method for a terminal to access a network includes:

The relay terminal receives a non-access stratum NAS access request from the remote terminal;

The relay terminal forwards the NAS access request to a core network control plane function CN-CP;

Receiving, by the relay terminal, a NAS access response returned by the CN-CP;

The relay terminal forwards the NAS access response to the remote terminal.
The method of claim 12, wherein

Receiving, by the relay terminal, the NAS access request from the remote terminal, the relay terminal receiving the NAS access request sent by the remote terminal by using a PC5 signaling message or a PC5 data packet;

The forwarding, by the relay terminal, the NAS access response to the remote terminal includes: the relay terminal forwarding the NAS access response to the remote terminal by using a PC5 signaling message or a PC5 data packet.
The method of claim 12 or 13, further comprising:

The relay terminal sends relay access information to the CN-CP, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, an identifier of the relay terminal Relay UE ID.
The method of claim 12 further comprising:

The relay terminal receives an identifier of the remote terminal that is sent by the CN-CP, a Remote UE ID.
The method of claim 15, wherein the relaying the terminal to the remote terminal to forward the NAS access response comprises:

The relay terminal forwards the NAS access response to the remote terminal according to the identifier Remote UE ID of the remote terminal.
The method of claim 12 or 15, further comprising:

The relay terminal receives the relay wireless data bearer sent by the CN-CP, where the attribute of the relay wireless data bearer is marked with bearer binding information, where the bearer binding information includes the remote terminal Identifies the Remote UE ID.
The method of claim 17, wherein after the relay terminal receives the relay wireless data bearer sent by the CN-CP, the method further includes:

The relay terminal stores the relay wireless data bearer in context; and/or

The relay terminal binds the PC5 interface of the remote terminal to the relay wireless data bearer serving the remote terminal.
The method according to any one of claims 12, 15 to 18, wherein the information sent by the CN-CP to the relay terminal is carried in an access layer AS sent by the wireless node RAN to the relay terminal. Into the response.
A method for a terminal to access a network includes:

The wireless node RAN receives the non-access stratum NAS access request from the remote terminal forwarded by the relay terminal;

Sending, by the RAN, the NAS access request to a core network control plane function CN-CP;

Receiving, by the RAN, a NAS access response returned by the CN-CP;

The RAN sends the NAS access response to the remote terminal through the relay terminal.
The method of claim 20 further comprising:

Receiving, by the RAN, the relay radio data bearer returned by the CN-CP and the identifier of the remote terminal, the remote UE ID, where the attribute of the relay radio data bearer is marked with bearer binding information, and the bearer is bound The information includes an identifier of the remote terminal, a Remote UE ID.
The method of claim 21, wherein after the RAN receives the relay wireless data bearer returned by the CN-CP, the method further includes:

The RAN stores the relay wireless data bearer in the context of the relay terminal.
The method according to claim 21 or 22, wherein the transmitting, by the RAN, the NAS access response to the remote terminal by the relay terminal comprises:

The RAN sends an access layer AS access response to the relay terminal, where the AS access response includes: the NAS access response, the identifier of the remote terminal, a Remote UE ID, and the relay wireless Data bearer.
A method for a terminal to access a network includes:

The core network control plane function CN-CP receives the non-access stratum NAS access request sent by the remote terminal through the relay terminal;

The CN-CP establishes or updates a PDN connection and bearer for the remote terminal in response to the NAS access request;

The CN-CP returns a NAS access response to the remote terminal through the relay terminal.
The method of claim 24 further comprising:

The CN-CP receives the relay access information, where the relay access information includes one or a combination of the following: an identifier of the relay terminal, a Relay UE ID, and a relay access indication, a Relay Indicator.
The method of claim 24 or 25, wherein the NAS access request comprises one or a combination of the following information:

The network identity of the remote terminal, a PDN connection establishment request, or a PDN connection update request.
The method of claim 24 or 25 or 26, wherein the NAS access request comprises a neighbor communication identifier of the remote terminal.
A method according to any one of claims 24 to 27, wherein

Establishing, by the CN-CP, the PDN connection and the bearer for the remote terminal, in response to the NAS access request, the CN-CP to the core network if the NAS access request includes a PDN connection establishment request User plane function CN-UP send bearer setup The request, wherein the bearer setup request is used to request the CN-UP to establish a PDN connection and bearer for the remote terminal; or

Updating, by the CN-CP, the PDN connection and the bearer for the remote terminal, in response to the NAS access request, the CN-CP to the core network if the NAS access request includes a PDN connection update request The user plane function CN-UP sends a bearer update request, where the bearer update request is used to request the CN-UP to update the PDN connection and bearer for the remote terminal.
The method according to any one of claims 24 to 28, wherein after the CN-CP establishes or updates a PDN connection and a bearer for the remote terminal in response to the NAS access request, the method further includes:

The CN-CP stores context information of the remote terminal, where the context information of the remote terminal includes one or a combination of the following information:

The remote terminal identifier of the remote terminal;

The bearer information of the remote terminal includes an IP address allocated to the remote terminal and a core network bearer;

The relay access information of the remote terminal, where the relay access information includes: an identifier Relay UE ID of the relay terminal.
The method of claim 29, wherein the context information of the remote terminal further comprises:

Neighbor communication identifier of the remote terminal.
The method according to any one of claims 24 to 30, wherein after the CN-CP establishes or updates a PDN connection and a bearer for the remote terminal in response to the NAS access request, the method further includes:

The CN-CP stores context information of the relay terminal, where the context information of the relay terminal includes:

The information of the remote terminal accessed by the relay terminal, wherein the information of the remote terminal accessed by the relay terminal includes one or a combination of the following information: an identifier of the remote terminal accessed by the relay terminal Remote UE ID, the IP address of the remote terminal accessed through the relay terminal.
The method according to any one of claims 24 to 31, wherein after the CN-CP establishes or updates a PDN connection and a bearer for the remote terminal in response to the NAS access request, the method further includes:

The CN-CP binds a core network bearer of the remote terminal and a relay wireless data bearer serving the remote terminal according to the relay access information of the remote terminal, where the relay wireless data is The bearer attribute is marked with bearer binding information, and the bearer binding information includes an identifier of the remote terminal, a Remote UE ID.
The method of claims 24 to 32, further comprising:

Returning, by the CN-CP, an identifier of the remote terminal, a remote UE ID, and a relay radio data bearer, where the attribute of the relay radio data bearer is marked with bearer binding information, where the bearer binding information includes the The remote terminal's identity is the Remote UE ID.
The method according to any one of claims 24 to 33, wherein the NAS access response comprises bearer information of the remote terminal, wherein the bearer information of the remote terminal comprises: an IP assigned to the remote terminal Address and core network bearer.
The method of any of claims 24 to 34, wherein the NAS access response comprises a temporary identity assigned by the CN-CP to a remote terminal.
The method according to any one of claims 24 to 35, wherein, in the case that the remote terminal initially accesses a network, the relay terminal is a relay terminal selected when the remote terminal initially accesses a network The NAS access request includes an attach request Attach Request; the NAS access response includes an attach response Attach Response.
The method according to any one of claims 24 to 35, wherein at the far In the case where the terminal is reselected from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal, and the NAS access request includes a PDN connection update request; the NAS access response includes PDN connection update response.
The method according to any one of claims 24 to 26, 37, wherein the NAS access request comprises information: an IP address assigned to the remote terminal when the remote terminal initially accesses the network.
The method according to claim 25 or 26 or 38, wherein after the CN-CP receives the NAS access request sent by the remote terminal by the relay terminal, the method further includes:

Determining, by the CN-CP, the relay terminal selected by the remote terminal according to the NAS access request and the relay access information, and/or assigning the remote terminal to the remote terminal when the remote terminal continues to use the initial access network IP address.
A downlink data delivery method includes:

The core network control plane function CN-CP receives downlink data sent to the remote terminal;

The CN-CP sends the downlink data to the remote terminal through a relay terminal.
The method according to claim 40, wherein before the CN-CP receives the downlink data sent to the remote terminal, the method further includes:

The CN-CP stores context information of the remote terminal, where the context information of the remote terminal includes:

The remote terminal identifier of the remote terminal;

The authentication parameter of the remote terminal;

The bearer information of the remote terminal, where the bearer information includes an IP address allocated to the remote terminal and a core network bearer;

The relay access information of the remote terminal, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and a label of the relay terminal Know the Relay UE ID.
The method according to claim 40 or 41, wherein, before the remote terminal is in an idle state, before the CN-CP transmits the downlink data to the remote terminal through the relay terminal, include:

The CN-CP initiates a paging request, where the paging request carries an identifier Relay UE ID of the relay terminal and an identifier of the remote terminal, a Remote UE ID.
The method according to claim 42, wherein before the CN-CP initiates the paging request, the method further includes:

In the case that the downlink data is the short message service SMS information, the CN-CP determines that the SMS information is sent to the remote terminal according to the terminal identity UE ID carried in the SMS delivery request message;

In the case that the downlink data is the downlink IP data, the CN-CP determines, according to the bearer information carried in the downlink data notification request message from the core network user plane function CN-UP, that the downlink IP data is sent to the a remote terminal, and determining an identifier of the remote terminal, a Remote UE ID, and an identifier of the relay terminal, a Relay UE ID, according to a context of the remote terminal.
A device for accessing a network by a terminal is applied to a remote terminal, and the device includes:

The first sending module is configured to send a non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal;

The first receiving module is configured to receive a NAS access response returned by the CN-CP through the relay terminal, and obtain bearer information of the remote terminal according to the NAS access response.
The apparatus of claim 44, wherein the NAS access response comprises:

The bearer information of the remote terminal, where the bearer information of the remote terminal includes: The IP address and core network bearer assigned to the remote terminal.
The device according to claim 44 or 45, wherein

In a case that the remote terminal initially accesses the network, the first sending module is configured to send the NAS access request including a PDN connection establishment request;

In a case where the remote terminal reselects from the original relay terminal to the target relay terminal, the relay terminal is the target relay terminal, and the first sending module is configured to send a location including a PDN connection update request. Said NAS access request.
A device for accessing a network by a terminal is applied to a relay terminal, and the device includes:

a second receiving module, configured to receive a non-access stratum NAS access request from the remote terminal;

The first forwarding module is configured to forward the NAS access request to the core network control plane function CN-CP;

a third receiving module, configured to receive a NAS access response returned by the CN-CP;

The second forwarding module is configured to forward the NAS access response to the remote terminal.
The apparatus according to claim 47, wherein the first forwarding module is further configured to send relay access information to the CN-CP, wherein the relay access information comprises one or a combination of the following information: The relay access indication Relay Indicator, the relay terminal ID of the relay terminal.
The apparatus of claim 47, wherein the third receiving module is further configured to receive an identifier Remote UE ID of the remote terminal transmitted by the CN-CP.
The apparatus of claim 49, wherein the second forwarding module is further configured to forward the NAS access response to the remote terminal based on an identifier Remote UE ID of the remote terminal.
The apparatus according to claim 47 or 49, wherein said third receiving mode The block is further configured to receive the relay radio data bearer sent by the CN-CP, where the attribute of the relay radio data bearer is marked with bearer binding information, where the bearer binding information includes an identifier of the remote terminal. Remote UE ID.
The apparatus of claim 51 further comprising:

a first storage module configured to store the relay wireless data bearer in a context; and/or

The first bearer binding module is configured to bind the PC5 interface of the remote terminal and the relay wireless data bearer serving the remote terminal.
A device for accessing a network by a terminal is applied to a wireless node RAN, and the device includes:

a fourth receiving module, configured to receive a non-access stratum NAS access request from the remote terminal forwarded by the relay terminal;

a second sending module, configured to send the NAS access request to a core network control plane function CN-CP;

a fifth receiving module, configured to receive a NAS access response returned by the CN-CP;

And a third sending module, configured to send the NAS access response to the remote terminal by using the relay terminal.
The apparatus according to claim 53, wherein the fifth receiving module is further configured to receive a relay wireless data bearer returned by the CN-CP and an identifier Remote UE ID of the remote terminal, wherein the relay The bearer binding information is marked in the attribute of the wireless data bearer, and the bearer binding information includes the identifier of the remote terminal, the Remote UE ID.
The apparatus of claim 54 further comprising:

And a second storage module configured to store the relay wireless data bearer in a context of the relay terminal.
A device for accessing a network by a terminal is applied to a core network control plane function CN-CP, and the device includes:

a sixth receiving module, configured to receive a non-access stratum NAS access request sent by the remote terminal by using the relay terminal;

Establishing or updating a module, configured to establish or update a PDN connection and bearer for the remote terminal in response to the NAS access request;

The fourth sending module is configured to return a NAS access response to the remote terminal by using the relay terminal.
The apparatus of claim 56, further comprising:

a second storage module, configured to store context information of the remote terminal after the establishing or updating module establishes or updates a PDN connection and a bearer for the remote terminal in response to the NAS access request, where The context information of the remote terminal includes one or a combination of the following information:

The remote terminal identifier of the remote terminal;

The bearer information of the remote terminal includes an IP address allocated to the remote terminal and a core network bearer;

The relay access information of the remote terminal, where the relay access information includes: an identifier Relay UE ID of the relay terminal.
The apparatus according to claim 56 or 57, wherein the fourth transmitting module is further configured to return an identifier of the remote terminal, a Remote UE ID, and a relay wireless data bearer, wherein the attribute of the relay wireless data bearer The bearer binding information is marked in the middle, and the bearer binding information includes an identifier of the remote terminal, a Remote UE ID.
The apparatus of claim 56, further comprising:

a determining module, configured to determine, according to the NAS access request and the relay access information, the remote terminal if the NAS access request includes a PDN connection update request The selected relay terminal changes and/or the remote terminal continues to use the IP address assigned to the remote terminal when initially accessing the network.
A downlink data delivery device is applied to a core network control plane function CN-CP, and the device includes:

a seventh receiving module, configured to receive downlink data sent to the remote terminal;

The fifth sending module is configured to send the downlink data to the remote terminal by using a relay terminal.