CN108377564B

CN108377564B - Method and device for accessing terminal to network and method and device for delivering downlink data

Info

Publication number: CN108377564B
Application number: CN201611009327.0A
Authority: CN
Inventors: 李志军; 黄梅青
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-11-14
Filing date: 2016-11-14
Publication date: 2023-05-30
Anticipated expiration: 2036-11-14
Also published as: WO2018086451A1; CN108377564A

Abstract

The invention provides a method and a device for accessing a terminal to a network, and a method and a device for delivering downlink data, wherein the method for accessing the terminal to the network comprises the following steps: the remote terminal sends a non-access stratum NAS access request to a core network control plane function CN-CP through a relay terminal; and the remote terminal receives the NAS access response returned by the CN-CP through the relay terminal, and obtains the bearing information of the remote terminal according to the NAS access response. Through the invention, the remote terminal can realize the interaction with the control surface of the core network through the relay of the relay terminal, and complete the access process or the relay terminal reselection process.

Description

Method and device for accessing terminal to network and method and device for delivering downlink data

Technical Field

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

Background

With the development of wireless communication networks, especially the construction of a high-rate and high-bandwidth long term evolution (Long Term Evolution, abbreviated as LTE)/evolved packet domain system (Evolved Packet System, abbreviated as EPS) system, the development of various multimedia services is stimulated. Many businesses, such as social networking, close-range data sharing, local advertising, and the like, are increasingly placing strong demands on close-range communications. In short-range communication, particular emphasis is given to Device-to-Device (D2D) communication, which is a communication between devices.

For the requirement of D2D communication, the third generation partnership project (the 3rd Generation Partnership Project, abbreviated as 3 GPP) has established a specialized research project, short range communication service (Proximity Service, abbreviated as ProSe), to support D2D communication. In D2D communication, there is a typical service requirement to enable a Remote terminal (Remote UE) to access a network through a Relay terminal (Relay UE) without network coverage.

Fig. 1 is a schematic diagram of an architecture of a related art in which a Remote terminal (Remote UE) accesses an LTE/EPS system through a Relay terminal (Relay UE).

The architecture shown in fig. 1 mainly comprises the following parts: (1) The LTE part of the radio subsystem, the evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, abbreviated E-UTRAN); (2) The EPS core network subsystem portion, also referred to as evolved packet core network (Evolved Packet Core, EPC for short); (3) short-range communication service part, namely ProSe architecture function.

In the E-UTRAN radio access network, enhanced NodeB (eNodeB for short), i.e. the base station part of LTE, is included.

An EPC packet core network comprising a home subscriber data server (Home Subscriber Server, abbreviated HSS), a mobility management unit (Mobility Management Entity, abbreviated MME), a Serving Gateway (S-GW), a packet data network Gateway (PDN Gateway, abbreviated P-GW), a Serving GPRS support node (Serving GPRS Support Node, abbreviated SGSN), and a policy and charging rules function entity (Policy and Charging Enforcement Function, abbreviated PCRF), wherein:

HSS (Home Subscriber Server): the home subscriber data server is a permanent storage place of subscriber subscription data and is positioned in a home network subscribed by the subscriber;

MME (Mobility Management Entity): the mobile management unit is a storage place of user subscription data in a current network and is responsible for Non-Access Stratum (NAS) signaling management of a terminal to the network, tracking and paging management functions and bearer management in a user idle mode;

S-GW (Serving Gateway): the service gateway is a gateway from the core network to the wireless system and is responsible for user plane bearing from the terminal to the core network, data caching in a terminal idle mode, a function of initiating a service request by a network side, a legal interception and packet data routing and forwarding function;

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

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

ProSe architecture functions, including a near field communication service Function (PF), a near field communication application server (ProSe Application Server, PAS), a Relay terminal (Relay UE), and a Remote terminal (Remote UE).

PF (ProSe Function): authorizing near field communication of terminals, providing discovery assistance between terminals, and the like.

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

Relay UE: relay access support is provided for Remote terminals (Remote UEs).

Remote UE: the IP service is obtained by accessing the network through a Relay terminal (Relay UE).

Fig. 2 is a schematic flow chart of obtaining IP services by a remote terminal accessing a network through a relay terminal based on the architecture shown in fig. 1, the flow chart including the steps of:

s201, a Relay UE is attached to a network, and PDN connection is established;

s202, the Remote UE discovers a Relay UE;

in the step, in the process of discovering the Relay UE, the APN supported by the Relay UE is used as important reference information;

s203, on the PC5 interface, the Remote UE requests to 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 by the Remote UE in the request in S203 to establish a corresponding PDN connection to the network request, and is used for providing Relay communication for the Remote UE;

s205, the Relay UE allocates an IP address for the Remote UE, wherein 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 the Remote terminal access report carries the identification Remote UE ID and the IP address of the Remote terminal;

s207, the MME sends a Remote terminal access report to the PGW, and the report carries information of Remote UE, including the identification Remote UE ID and IP address of the Remote terminal;

the PGW locally stores information of the Remote UE, and using this information, the PGW may gate uplink and downlink data of the Remote UE, i.e. whether to allow transmission of the uplink and downlink data.

S208, the Remote UE transmits uplink IP data or receives downlink IP data, the IP data is relayed by the Relay UE, and the IP data is born in a PDN connection established by the Relay UE for the Remote UE.

According to the flow described in fig. 2, a Remote terminal (Remote UE) may access the network through a Relay terminal (Relay UE) to obtain IP services without network information coverage. However, with this access scheme, the network has substantially no control over the Remote terminal (Remote UE), e.g., no control over the access of the Remote terminal, no control over the reselection of the relay terminal by the Remote terminal; in addition, the network cannot effectively deliver downlink data to the remote terminal. Due to these drawbacks, certain services that rely on terminal awareness are difficult to implement.

Disclosure of Invention

The embodiment of the invention provides a method and a device for accessing a terminal to a network and a method and a device for delivering downlink data, which at least solve the problems that the network basically has no control on a Remote terminal (Remote UE) or the network cannot effectively deliver the downlink data to the Remote terminal in the related technology.

According to one embodiment of the present invention, there is provided a method for a terminal to access a network, including:

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

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

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

the remote terminal receiving the NAS access response returned by the CN-CP through the relay terminal comprises the following steps: the remote terminal receives a 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 is sent to the remote terminal by the CN-CP through the relay terminal.

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

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

Optionally, the NAS access request includes: and the neighbor communication identification of the remote terminal.

Optionally, the NAS access response includes:

the load bearing information of the remote terminal, wherein the load bearing information of the remote terminal comprises: an IP address assigned for the remote terminal and a core network bearer.

Optionally, the NAS access response further includes:

the CN-CP assigns a temporary identity for the remote terminal.

Alternatively, in the case where 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; the NAS access Response includes an 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: the IP address of the remote terminal.

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

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

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

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

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

Optionally, the relay terminal receiving the NAS access request from the remote terminal includes: the relay terminal receives an NAS access request sent by a remote terminal by using a PC5 signaling message or a 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 using a PC5 signaling message or a PC5 data packet.

Optionally, the method further comprises:

the relay terminal sends relay access information to the CN-CP, wherein the relay access information comprises one or a combination of the following information: the Relay access indicates a Relay Indicator and an identification Relay UE ID of the Relay terminal.

Optionally, the method further comprises:

the relay terminal receives an identification Remote UE ID of the Remote terminal transmitted by the CN-CP.

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

And the relay terminal forwards the NAS access response to the Remote terminal according to the Remote terminal identification Remote UE ID.

Optionally, the method further comprises:

the relay terminal receives a relay wireless data carrier sent by the CN-CP, wherein the attribute of the relay wireless data carrier is marked with bearing binding information, and the bearing binding information comprises an identification Remote UE ID of the Remote terminal.

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

the relay terminal storing relay wireless data bearers in context; and/or

The relay terminal binds the PC5 interface of the remote terminal with the relay radio data bearer serving the remote terminal.

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

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

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

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

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

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

Optionally, the method further comprises:

the RAN receives a relay wireless data bearer returned by the CN-CP and an identification Remote UE ID of the Remote terminal, wherein the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information comprises the identification Remote UE ID of the Remote terminal.

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

the RAN stores the relay radio data bearer in the context of the relay terminal.

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

the RAN sends an Access Stratum (AS) access response to the relay terminal, wherein the AS access response comprises the following steps: NAS access response, remote terminal identity Remote UE ID and relay radio data bearer.

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

the CN-CP responds to the NAS access request to establish or update PDN connection and bearing for the remote terminal;

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

Optionally, the method further comprises:

The CN-CP receives relay access information, wherein the relay access information comprises one or a combination of the following information: the identification Relay UE ID of the Relay terminal and the Relay access indication Relay Indicator.

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

Optionally, the CN-CP establishing a PDN connection and bearer for the remote terminal in response to the NAS access request includes: in the case that the NAS access request comprises a PDN connection establishment request, the CN-CP sends a bearer establishment request to a core network user plane function CN-UP, wherein the bearer establishment request is used for requesting the CN-UP to establish PDN connection and bearer for a remote terminal; or alternatively, the first and second heat exchangers may be,

the CN-CP responds to the NAS access request, and updating the PDN connection and the bearer for the remote terminal comprises the following steps: in case the NAS access request comprises a PDN connection update request, the CN-CP sends a bearer update request to a core network user plane function CN-UP, where 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 the context information of the remote terminal, wherein the context information of the remote terminal comprises one or a combination of the following information:

remote terminal identification (Remote UE ID);

the load information of the remote terminal comprises an IP address and a core network load allocated to the remote terminal;

relay access information of a remote terminal, wherein the relay access information includes: identification of Relay terminal Relay UE ID.

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

and the neighbor communication identification of the remote terminal.

the CN-CP stores the context information of the relay terminal, wherein the context information of the relay terminal comprises:

information of the remote terminal accessed through the relay terminal, wherein the information of the remote terminal accessed through the relay terminal comprises one or a combination of the following information: the Remote terminal accessed through the relay terminal has an identification Remote UE ID, and the IP address of the Remote terminal accessed through the relay terminal.

The CN-CP binds a core network load of the Remote terminal with a relay wireless data load serving the Remote terminal according to relay access information of the Remote terminal, wherein the attribute of the relay wireless data load is marked with load binding information, and the load binding information comprises an identification Remote UE ID of the Remote terminal.

Optionally, the method further comprises:

the CN-CP returns an identification Remote UE ID of the Remote terminal and a relay wireless data bearing, wherein the attribute of the relay wireless data bearing is marked with bearing binding information, and the bearing binding information comprises the identification Remote UE ID of the Remote terminal.

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

Optionally, the NAS access response includes a temporary identity assigned by the CN-CP for 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, and the NAS access Request includes an Attach Request; the NAS access Response includes an 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, and 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 includes the following information: 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 through the relay terminal, the method further includes:

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

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

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

the CN-CP transmits the 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 the context information of the remote terminal, wherein the context information of the remote terminal comprises:

remote terminal identification (Remote UE ID);

authentication parameters of the remote terminal;

the method comprises the steps of carrying information of a remote terminal, wherein the carrying information comprises an IP address and a core network carrier distributed for the remote terminal;

relay access information of the remote terminal, wherein the relay access information includes one or a combination of the following information: the Relay access indicates a Relay Indicator and an identification Relay UE ID of the Relay terminal.

Optionally, in the case that the remote terminal is in an idle state, before the CN-CP transmits downlink data to the remote terminal through the relay terminal, the method further includes:

the CN-CP initiates a paging request, wherein the paging request carries an identification Relay UE ID of the Relay terminal and an identification 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 SMS information of short message service, the CN-CP determines that the SMS information is sent to a remote terminal according to a terminal identification (UE ID) carried in the SMS delivery request message;

in the case that the downlink data is 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 CN-UP, and determines, according to the context of the Remote terminal, the Remote terminal ID and the Relay terminal ID.

According to yet another embodiment of the present invention, there is provided an apparatus for a terminal to access a network, for use with a remote terminal, the apparatus comprising:

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

The first receiving module is used for receiving the NAS access response returned by the CN-CP through the relay terminal and obtaining the bearing information of the remote terminal according to the NAS access response.

Optionally, the NAS access response includes:

Optionally, in the 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 that 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 NAS access request including a PDN connection update request.

According to still another embodiment of the present invention, there is provided an apparatus for a terminal to access a network, applied to a relay terminal, the apparatus including:

the second receiving module is used for receiving a non-access stratum (NAS) access request from the remote terminal;

the first forwarding module is used for forwarding 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;

and the second forwarding module is used for forwarding the NAS access response to the remote terminal.

Optionally, the first forwarding module 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: the Relay access indicates a Relay Indicator and an identification Relay UE ID of the Relay terminal.

Optionally, the third receiving module is further configured to receive an 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 Remote terminal's identity Remote UE ID.

Optionally, the third receiving module is further configured to receive a relay radio data bearer sent by the CN-CP, where an attribute of the relay radio 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 apparatus further comprises:

a first storage module for storing relay wireless data bearers in context; and/or

And the first bearing binding module is used for binding the PC5 interface of the remote terminal and the relay wireless data bearing serving the remote terminal.

According to yet another embodiment of the present invention, there is provided an apparatus for a terminal to access a network, applied to a radio node RAN, the apparatus comprising:

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

The second sending module is used for sending 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;

and the third sending module is used for sending the NAS access response to the remote terminal through the relay terminal.

Optionally, 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, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier Remote UE ID of the Remote terminal.

Optionally, the apparatus further comprises:

and a second storage module for storing the relay wireless data bearer in the context of the relay terminal.

According to still another embodiment of the present invention, there is provided an apparatus for a terminal to access a network, 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 a remote terminal through a relay terminal;

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

and the fourth sending module is used for returning the NAS access response to the remote terminal through the relay terminal.

Optionally, the apparatus further comprises:

the second storage module is used for storing the context information of the remote terminal after the establishment or update module responds to the NAS access request to establish or update the PDN connection and the bearer for the remote terminal, wherein the context information of the remote terminal comprises one or a combination of the following information:

remote terminal identification (Remote UE ID);

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

Optionally, the apparatus further comprises:

and the determining module is used for determining the relay terminal change selected by the remote terminal and/or the IP address allocated to the remote terminal when the remote terminal continues to use the initial access network according to the NAS access request and the relay access information in the case that the NAS access request comprises the PDN connection update request.

According to still another embodiment of the present invention, there is provided a downlink data delivery apparatus applied to a core network control plane function CN-CP, the apparatus including:

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

and the fifth sending module is used for sending the downlink data to the remote terminal through the relay terminal.

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

Through the invention, the remote terminal can realize the interaction with the control surface of the core network through the relay of the relay terminal, the access process or the reselection process of the relay terminal is completed, the control surface of the core network can realize the interaction with the remote terminal through the relay terminal, the load creation of the remote terminal and the load update during the relay reselection can be realized, and the initiation of the downlink data delivery to the remote terminal can also be realized. Through the scheme, information or data transfer between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:

fig. 1 is a schematic diagram of an architecture of a related art in which a remote terminal accesses LTE/EPS through a relay terminal;

fig. 2 is a schematic flow chart of a related art method in which a remote terminal accesses to an LTE/EPS network through a relay terminal;

fig. 3 is a flowchart of a method for a terminal on a remote terminal side to access a network according to a first embodiment of the present invention;

fig. 4 is a flowchart of a method for a terminal on a relay terminal side to access a network according to the first embodiment of the present invention;

fig. 5 is a flowchart of a method for a terminal on a wireless node side to access a network according to the first embodiment of the present invention;

fig. 6 is a flowchart of a method for a terminal applied to a control plane function side of a core network to access a network according to a first embodiment of the present invention;

fig. 7 is a flowchart of a downlink data delivery method applied to a control plane function side of a core network according to a second embodiment of the present invention;

fig. 8 is a block diagram of an apparatus for a terminal access network applied to a remote terminal according to a third embodiment of the present invention;

Fig. 9 is a block diagram of an apparatus for a terminal access network applied to a relay terminal according to a third embodiment of the present invention;

fig. 10 is a block diagram of an apparatus for a terminal applied to a wireless node to access a network according to a third embodiment of the present invention;

fig. 11 is a block diagram of an apparatus for a terminal to access a network, which is applied to a control plane function of a core network, according to a third embodiment of the present invention;

fig. 12 is a block diagram of a downlink data delivery device applied to a control plane function of a core network according to a fourth embodiment of the present invention;

FIG. 13 is a schematic diagram of a fifth embodiment of an architecture according to the present invention;

fig. 14A is a schematic diagram of a control plane protocol stack structure according to a fifth embodiment of the present invention;

fig. 14B is a second control plane protocol stack architecture diagram according to a fifth embodiment of the present invention;

fig. 14C is a schematic diagram of a user plane protocol stack according to a fifth embodiment of the present invention;

fig. 15 is a schematic flow chart of a remote terminal accessing to a network through a relay terminal according to a sixth embodiment of the present invention;

fig. 16 is a schematic flow chart of a remote terminal accessing to a network through a relay terminal according to a seventh embodiment of the present invention;

fig. 17 is a schematic flow chart of a procedure after a core network control plane function places a remote terminal into an idle state after a relay terminal enters the idle state according to an eighth embodiment of the present invention;

Fig. 18 is a schematic flow chart of sending a downlink SMS message to a remote terminal by an application server according to a ninth embodiment of the present invention;

fig. 19 is a schematic flow chart of sending downlink IP data to a remote terminal after the relay terminal and the remote terminal enter an idle state according to the tenth embodiment of the present invention;

fig. 20 is a schematic flow chart of a process of reactivating a PDN connection after a remote terminal reselects a relay terminal according to an eleventh embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

Example 1

According to a first embodiment of the present invention, a method for accessing a terminal to a network is provided and applied to a remote terminal side, and fig. 3 is a flowchart of a method for accessing a terminal to a network applied to a remote terminal side according to the first embodiment of the present invention, as shown in fig. 3, the flowchart includes the following steps:

Step S302, a remote terminal sends NAS access request to a Core Network Control Plane (CN-CP) through a relay terminal;

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

By the method, the remote terminal can realize interaction with the control surface of the core network through the relay of the relay terminal, the access process or the relay terminal reselection process is completed, the control surface of the core network realizes interaction with the remote terminal through the relay terminal, and the load creation of the remote terminal and the load update during the relay reselection can be realized. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

Optionally, the information interaction between the remote terminal and the relay terminal may be implemented through a PC5 interface, for example, in step S302, the remote terminal may send a NAS access request to the relay terminal using a PC5 signaling message or a PC5 data packet, where the NAS access request is forwarded to the CN-CP through the relay terminal; in step S304, the remote terminal may receive a NAS access response transmitted by the relay terminal to the relay terminal using the PC5 signaling message or the PC5 data packet, wherein the NAS access response is transmitted by the CN-CP to the remote terminal through the relay terminal.

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

Optionally, the NAS access request may include: and the neighbor communication identification of the remote terminal. By carrying the neighbor communication identifier of the remote terminal in the NAS access request, the CN-CP can mark the neighbor communication identifier of the remote terminal at the same time when the NAS access response is returned, so that the relay terminal can forward the NAS access response to the correct remote terminal.

The NAS access response may include bearer information for the remote terminal, where the bearer information for the remote terminal includes: an IP address assigned for the remote terminal and a core network bearer. Through the above information carried in the NAS access response, the remote terminal can obtain the bearing information of the remote terminal.

Optionally, the NAS access response may further include: the CN-CP assigns a temporary identity for the remote terminal.

In the case where the remote terminal initially accesses the network, the relay terminal described above is a relay terminal selected when the remote terminal initially accesses the network. Optionally, the NAS access Request includes an Attach Request; the NAS access Response includes an 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: the IP address of the remote terminal. For example, the CN-CP may be enabled to assign an IP address to a 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 carrying out PDN connection and bearing update for the remote terminal.

According to a first embodiment of the present invention, a method for accessing a terminal to a network is also provided, which is applied to a relay terminal side. Fig. 4 is a flowchart of a method for a terminal on a relay terminal side to access a network according to a first embodiment of the present invention, as shown in fig. 4, the flowchart includes the steps of:

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

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

step S406, the relay terminal receives the NAS access response returned by the CN-CP;

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

By the method, the relay terminal can realize the relay between the remote terminal and the CN-CP, assist the remote terminal to finish the access process or the request process of the relay terminal reselection, and assist the core network control plane to realize the load creation of the remote terminal and the load update during the relay reselection. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

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

In a preferred embodiment, the relay terminal may transmit relay access information to the CN-CP, wherein the relay access information includes one or a combination of the following information: the Relay access indicates a Relay Indicator and an identification Relay UE ID of the Relay terminal. By the method, the CN-CP can acquire relay access information of the remote terminal, so that the context of the remote terminal and the context of the relay terminal are conveniently maintained in a 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 terminal identifier Remote UE ID sent by the CN-CP, where the information may be received by the relay terminal from the CN-CP while the relay terminal receives the NAS access response from the CN-CP, and as a preferred embodiment, the Remote terminal identifier Remote UE ID may be encapsulated outside the NAS access response, and after the relay terminal parses the Remote terminal identifier Remote UE ID, the relay terminal sends the NAS access response to the Remote terminal according to the Remote terminal identifier Remote UE ID.

Preferably, the relay terminal further receives a relay wireless data bearer sent by the CN-CP, where an attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes an identifier Remote UE ID of the Remote terminal. After the relay terminal receives the relay wireless data bearer sent by the CN-CP, the method further comprises the following steps: the relay terminal storing relay wireless data bearers in context; and/or the relay terminal binds the PC5 interface of the remote terminal with a relay wireless data bearer serving the remote terminal.

Preferably, the information sent by the CN-CP to the relay terminal (e.g., NAS access response, relay radio data bearer, and Remote terminal identity, remote UE ID) may be sent to the relay terminal by the RAN, e.g., the above information may be carried in an access stratum AS access response sent by the RAN to the relay terminal.

According to a first embodiment of the present invention, there is further provided a method for accessing a terminal to a network, and fig. 5 is a flowchart of a method for accessing a terminal to a network applied to a wireless node side according to the first embodiment of the present invention, as shown in fig. 5, where the flowchart includes the following steps:

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

step S504, RAN sends NAS access request to CN-CP;

step S506, the RAN receives NAS access response returned by the CN-CP;

in step S508, the RAN sends the NAS access response to the remote terminal through the relay terminal.

By the method, the RAN is used as a service node of the relay terminal, can support interaction between the remote terminal and the CN-CP through the relay terminal, assist the remote terminal to complete an access process or a relay terminal reselection request process, and assist a core network control plane to realize load creation of the remote terminal and load update during relay reselection. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

The RAN can receive a relay wireless data bearer returned by the CN-CP and an identification Remote UE ID of the Remote terminal, wherein the attribute of the relay wireless data bearer is marked with bearing binding information, and the bearing binding information comprises the identification Remote UE ID of the Remote terminal.

After receiving the relay radio data bearer returned by the CN-CP, the RAN further comprises:

Optionally, the RAN sending the NAS access response to the remote terminal through the relay terminal includes: the RAN sends an Access Stratum (AS) access response to the relay terminal, wherein the AS access response comprises the following steps: NAS access response, remote terminal identity Remote UE ID and relay radio data bearer.

According to a first embodiment of the present invention, there is further provided a method for accessing a network by a terminal, which is applied to a control plane function of a core network, and fig. 6 is a flowchart of a method for accessing a network by a terminal applied to a control plane function side of a core network according to the first embodiment of the present invention, as shown in fig. 6, the flowchart includes the following steps:

step S602, CN-CP receives NAS access request sent by remote terminal through relay terminal;

step S604, the CN-CP responds to the NAS access request to establish or update PDN connection and bearing for the remote terminal;

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

By the method, the core network control plane can realize interaction with the remote terminal through the relay of the relay terminal, thereby realizing the load creation of the remote terminal and the load update during the relay reselection. Through the scheme, information or data transfer between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

In a preferred embodiment, the CN-CP may receive relay access information from the relay terminal, wherein the relay access information includes one or a combination of the following information: the identification Relay UE ID of the Relay terminal and the Relay access indication Relay Indicator. By the method, the CN-CP can acquire relay access information of the remote terminal, so that the context of the remote terminal and the context of the relay terminal are conveniently maintained in a 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 identity of the remote terminal.

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

the CN-CP responds to the NAS access request, and establishes PDN connection and bearing for the remote terminal comprises the following steps: in the case that the NAS access request comprises a PDN connection establishment request, the CN-CP sends a bearer establishment request to a core network user plane function CN-UP, wherein the bearer establishment request is used for requesting the CN-UP to establish PDN connection and bearer for a remote terminal;

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

remote terminal identification (Remote UE ID);

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

and the neighbor communication identification of the remote terminal.

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

In order to facilitate the transmission control of 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 at the same time, in order to notify the relay terminal of the relay radio data bearer, the CN-CP may return an identifier Remote UE ID of the Remote terminal and the relay radio data bearer, where the attribute of the relay radio data bearer is marked with bearer binding information, and the bearer binding information includes the identifier Remote UE ID of the Remote terminal. 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 radio data bearer may all be sent to the relay terminal through the RAN, for example, the CN-CP may return the above information to the RAN through an initialization response, and then send the above information to the relay terminal through the AS access response by the RAN.

In order to facilitate the remote terminal to acquire the bearer information, 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 assigned for the remote terminal and a core network bearer.

Optionally, the NAS access response may also include a temporary identity allocated by the CN-CP for the remote terminal.

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

For the case of relay reselection by the remote terminal, 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 through the relay terminal, the method further includes: the CN-CP determines the relay terminal change selected by the remote terminal and/or the IP address allocated to the remote terminal when the remote terminal continues to use the initial access network according to the NAS access request and the relay access information. As a preferred embodiment, 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 has changed through the relay access information, so that the CN-CP may determine that the relay terminal selected by the remote terminal has changed, and the remote terminal continues to use the IP address allocated to the remote terminal when the initial access network is used. In addition, the CN-CP may also determine the IP address allocated to the remote terminal when the remote terminal continues to use the initial access network by the IP address allocated to the remote terminal when the remote terminal initially accesses the network carried by the NAS access request.

Example two

According to a second embodiment of the present invention, a downlink data delivery method is provided, which is applied to a control plane function of a core network, and fig. 7 is a flowchart of a downlink data delivery method applied to a control plane function side of the core network according to the second embodiment of the present invention, as shown in fig. 7, where the flowchart includes the following steps:

step S702, CN-CP receives downlink data sent to remote terminal;

step S704, the CN-CP transmits the downlink data to the remote terminal through the relay terminal.

By the method, the core network control plane can realize interaction with the remote terminal through the relay terminal, and can initiate downlink data delivery to the remote terminal. Through the scheme, the data transmission between the network side and the remote terminal is realized, and the purpose that the network can sense or control the remote terminal is achieved when the remote terminal is accessed to the network through the relay terminal.

remote terminal identification (Remote UE ID);

authentication parameters of the remote terminal;

Example III

In this embodiment, devices respectively applied to the remote terminal, the relay terminal, the wireless node, and the terminal access network of the core network control plane function are also provided, and these devices are used to implement the first embodiment and the preferred implementation manner, which have already been described and will not be repeated. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

According to a third embodiment of the present invention, there is provided an apparatus for accessing a network by a terminal, which is applied to a remote terminal, and fig. 8 is a block diagram of an apparatus for accessing a network by a terminal, which is applied to a remote terminal according to the third embodiment of the present invention, and as shown in fig. 8, the apparatus includes:

a first sending module 82, configured to send, through the relay terminal, a NAS access request of the non-access stratum to the CN-CP;

the first receiving module 84 is coupled to the first sending module 82, and is configured to receive the NAS access response returned by the CN-CP through the relay terminal, and obtain the 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 surface of the core network through the relay of the relay terminal, the access process or the reselection process of the relay terminal is completed, the control surface of the core network realizes the interaction with the remote terminal through the relay terminal, and the load creation of the remote terminal and the load update during the relay reselection can be realized. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

Optionally, the NAS access response may include:

In case 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 case 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 82 is configured to send a NAS access request including a PDN connection update request.

According to a third embodiment of the present invention, there is further provided an apparatus for accessing a terminal to a network, which is applied to a relay terminal, and fig. 9 is a block diagram of an apparatus for accessing a terminal to a network, which is applied to a relay terminal, according to the third embodiment of the present invention, and as shown in fig. 9, the apparatus includes:

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

a first forwarding module 94 coupled to the second receiving module 92 for forwarding the NAS access request to the core network control plane function CN-CP;

a third receiving module 96, coupled to the first forwarding module 94, for receiving a NAS access response returned by the CN-CP;

A second forwarding module 98 coupled to the third receiving module 96 for forwarding the NAS access response to the remote terminal.

Through the device, the relay terminal can realize the relay between the remote terminal and the CN-CP, assist the remote terminal to finish the access process or the request process of the relay terminal reselection, and assist the core network control plane to realize the load creation of the remote terminal and the load update during the relay reselection. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

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: the Relay access indicates a Relay Indicator and an identification Relay UE ID of the Relay terminal.

Optionally, the third receiving module 96 is further configured to receive an identification Remote UE ID 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 Remote terminal's identity Remote UE ID.

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

Optionally, the apparatus further comprises:

a first storage module coupled to the third receiving module 96 for storing relay wireless data bearers in context; and/or

A first bearer binding module coupled to the third receiving module 96 for binding the PC5 interface of the remote terminal with the relay wireless data bearer serving the remote terminal.

According to a third embodiment of the present invention, there is provided an apparatus for accessing a network by a terminal, which is applied to a radio node RAN, and fig. 10 is a block diagram of an apparatus for accessing a network by a terminal, which is applied to a radio node according to the third embodiment of the present invention, and as shown in fig. 10, the apparatus includes:

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

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

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

A third sending module 1008 is coupled to the fifth receiving module 1006 for sending NAS access responses to the remote terminal through the relay terminal.

Through the device, the RAN is used as a service node of the relay terminal, can support the interaction between the remote terminal and the CN-CP through the relay terminal, assist the remote terminal to complete the access process or the request process of the relay terminal reselection, and assist the control plane of the core network to realize the load creation of the remote terminal and the load update during the relay reselection. Through the scheme, information transmission between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

Optionally, the fifth receiving module 1006 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, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier Remote UE ID of the Remote terminal.

Optionally, the apparatus further comprises:

a second storage module, coupled to the fifth receiving module 1006, for storing relay wireless data bearers in the context of the relay terminal.

According to a third embodiment of the present invention, there is provided an apparatus for accessing a network by a terminal, which is applied to a CN-CP, and fig. 11 is a block diagram of an apparatus for accessing a network by a terminal, which is applied to a control plane function of a core network according to the third embodiment of the present invention, as shown in fig. 11, the apparatus includes:

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

an establishing or updating module 1104, coupled to the sixth receiving module 1102, for establishing or updating PDN connections and bearers for the remote terminal in response to the NAS access request;

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

Through the device, the core network control surface can realize interaction with the remote terminal through the relay of the relay terminal, thereby realizing the load creation of the remote terminal and the load update during the relay reselection. Through the scheme, information or data transfer between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

Optionally, the apparatus further comprises:

a second storage module coupled to the establishment or update module 1104 for storing context information of the remote terminal after the establishment 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 context information of the remote terminal includes one or a combination of the following information:

remote terminal identification (Remote UE ID);

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

Optionally, the apparatus further comprises:

a determining module, coupled to the sixth receiving module 1102, configured to determine, in a case where the NAS access request includes a PDN connection update request, a relay terminal change selected by the remote terminal and/or an IP address allocated to the remote terminal when the remote terminal continues to use the initial access network according to the NAS access request and the relay access information.

Example IV

The embodiment also provides a downlink data delivery device, which is applied to the CN-CP, and the device is used to implement the second embodiment and the preferred implementation manner, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 12 is a block diagram of a downlink data delivery apparatus applied to a control plane function of a core network according to a fourth embodiment of the present invention, and as shown in fig. 12, the apparatus includes:

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

and a fifth sending module 1204, configured to send the downlink data to the remote terminal through the relay terminal.

Through the device, the core network control plane can realize interaction with the remote terminal through the relay terminal, and can realize that downlink data delivery is initiated to the remote terminal. Through the scheme, the data transmission between the network side and the remote terminal is realized, and the purpose that the network can sense or control the remote terminal is achieved when the remote terminal is accessed to the network through the relay terminal.

Example five

Fig. 13 is a schematic diagram of an architecture according to a fifth embodiment of the present invention, including:

remote UE: the remote terminal can only access through the Relay UE under the condition of no network coverage;

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

-RAN: a wireless node provides a wireless access function for a Relay UE;

-CN-CP: a core network control plane function for providing flow control functions such as authentication, bearer resource management, mobility management and the like for a Relay UE and a Remote UE;

-CN-UP: the core network user plane function provides functions such as IP address allocation, IP data routing and the like for the Relay UE and the Remote UE;

-CN-SD: the core network subscription database provides a subscription data access function for the Relay UE and the Remote UE;

NG-Uu interface: an interface between the Relay UE and the RAN for transmitting AS (Access Stratum) 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, and transmitting control plane signaling;

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

NG4 interface: an interface between the CN-CP and the CN-UP transmits a bearing control signaling;

In the architecture shown in fig. 13, the Relay UE acts as a NAS Relay for the Remote UE, i.e. 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 NAS information sent by the CN-CP to the Remote UE on the NG1 interface and forwarding the NAS information 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 NAS messages between the Remote UE and the CN-CP are wrapped in NG1 interface messages between the Relay UE and the CN-CP.

When the architecture shown in fig. 13 is applied in LTE/EPS, there is a correspondence as follows:

-RAN: i.e. eNodeB;

-CN-CP: i.e., MME;

-CN-UP: SGW, PGW;

-CN-SD: namely HSS;

NG-Uu: i.e. the LTE-Uu interface;

NG2: namely an S1-AP interface;

NG3: S1-U interface;

NG4: i.e. the S11 interface;

fig. 14A and 14B are diagrams of a control plane protocol stack according to a fifth embodiment of the present invention, in which:

on the Relay UE there is a NAS Relay protocol layer that receives NAS signaling sent by the Remote UE from the PC5 interface and forwards NAS signaling of the Remote UE to the CN-CP on the NG1 interface. And otherwise, 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 in fig. 14a, remote UE sends NAS signaling to and receives NAS signaling from Relay UE through PC5 signaling plane (PC 5-C). For this reason, on the PC5 signaling plane, corresponding PC5 messages, such as NAS signaling relay request, NAS signaling relay response, and the like, need to be added.

-2) as in fig. 14b, remote UE sends NAS signaling to and receives NAS signaling from Relay UE through PC5 user plane (PC 5-U). In order to distinguish the conventional IP data transceiving on the PC5-U, it can be implemented in the following manner: designating a particular port for transmission of NAS signaling only;

as can be seen from the protocol stack architecture shown in fig. 14A and 14B, the architecture only has an effect on Remote UE, relay UE, CN-CP, and has a small effect on RAN.

Fig. 14C is a schematic diagram of a user plane protocol stack according to a fifth embodiment of the present invention, wherein:

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

Example six

Fig. 15 is a schematic flow chart of a remote terminal accessing to a network through a relay terminal according to a sixth embodiment of the present invention. In this embodiment, remote UE and Relay UE receive and send NAS signaling on the PC5 signaling plane.

Fig. 15 has the following steps:

s1501, a Relay UE is attached to a network to establish a PDN connection;

s1502, remote UE discovers Relay UE;

in this step, the Relay UE selects an appropriate Relay according to the capability broadcasted by the Remote UE. In this scheme, the Relay UE broadcasts the following capabilities: supported APN, whether NAS Relay (NAS Relay) functionality is supported.

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, where the address is either a private IPv4 address or an IPv6 prefix, and the IP address is only used for communication between the Remote UE and the Relay UE on the PC5 interface;

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

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

In this step, since the Remote UE is initially accessed to the network in this embodiment, the NAS access Request carried by the Remote UE is an Attach Request (Attach Request). In the attach request, a PDN establishment request is included. The Remote UE may request the network to create a corresponding PDN connection and bearer using a particular APN. If the APN is not specified, the CN-CP creates a PDN connection for the Remote UE using the default APN.

In this step, further, the Remote UE may also carry a neighbor communication identifier (ProSe UE ID) in the NAS access request. The neighbor communication identifier is an identifier of the Remote UE, which is used 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 Relay access information;

in this step, the Relay UE transmits Relay access information, where the Relay access information includes one or a combination of the following information: relay indication (Relay indication), and an identity of a Relay terminal (Relay UE ID).

S1506, the RAN sends an initialization request to the CN-CP;

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

S1507, the CN-CP acquires user subscription data of Remote UE from the CP-SD;

s1508, CN-CP authenticates the Remote UE;

s1509, according to the request of the Remote UE and the subscription data of the Remote UE, the CN-CP sends a bearer establishment request to the CN-UP, and establishes a corresponding PDN connection and bearer for the Remote UE;

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

S1510, the CN-UP returns a bearer establishment response to the CN-CP and returns the created bearer;

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

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

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

-network identity of Remote UE, such as IMSI;

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

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

further, a neighbor communication identity of the Remote UE may also be included.

Further, 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 identification Remote UE ID, IP address of the Remote terminal, etc.

S1512, the CN-CP returns an initialization response to the RAN;

in this step, the CN-CP transmits the following information through an initialization response:

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

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

-relay radio data bearer: the wireless data bearer is distributed to the Relay UE, and Relay transmission of uplink and downlink data is provided for the Remote UE. The attribute of the radio data bearer includes bearer binding information. The bearer binding information comprises an identification Remote UE ID of the Remote terminal;

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 downstream data on the core network bearer of the Remote UE will be sent on the Relay radio data bearer to the Relay UE. Otherwise, all uplink data on the Relay wireless data bearer of the Relay UE is carried to the core network of the Remote UE.

S1513, the RAN stores the context of the Relay UE;

in this step, the RAN records in the context of the Relay UE: relaying the wireless 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: NAS access response (attach response in this embodiment), identification of Remote terminal (Remote UE ID), relay radio data bearer.

S1515, the Relay UE receives the AS access response of the RAN and stores the self context information;

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

And the Relay UE judges that the bearer is the Relay transmission for providing uplink and downlink data for a certain Remote UE according to the bearer binding information in the wireless data bearer attribute. When the Relay UE receives uplink data of the Remote UE on the PC5 interface, the Relay UE sends the received uplink data on a Relay radio data bearer corresponding to the Remote UE. When the Relay UE receives downlink data on the Relay wireless 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 wireless bearer. Namely, the Relay UE binds the PC5 interface of the Remote UE with the Relay radio data bearer serving the Remote UE on the Relay UE one by one, so as to realize 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, carrying a NAS access Response, in this embodiment an Attach Response (Attach Response);

the Attach Response (Attach Response) includes an IP address and a bearer allocated by the core network to the UE. Using the IP address and bearer, the Remote UE may send uplink IP data or receive downlink IP data, which are all transmitted over the Relay radio data bearer of the Relay UE.

Note that, in the flow shown in fig. 15, steps S1504 to S1516 may occur before step S1503.

Example seven

Fig. 16 is a schematic flow chart of a remote terminal accessing to a network through a relay terminal according to the seventh embodiment of the present invention. In this embodiment, remote UE and Relay UE receive and send NAS signaling at the PC5 user plane.

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

-transmitting NAS signaling of Remote UE using a PC5 user plane (i.e. PC5 data packet) between Remote UE and Relay UE over a PC5 interface as in steps S1604, S1608, S1616;

step S1603 must be performed before steps S1604 to S1616;

example eight

Fig. 17 is a schematic flow chart of a procedure for placing a remote terminal into an idle state by a core network control plane function after a relay terminal enters the idle state according to the eighth embodiment of the present invention.

Fig. 17 has the following steps:

s1701, a Relay UE is attached to a network;

s1702, as shown in the flow of FIG. 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 radio 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;

and after the CN-UP receives the access bearer release request, releasing the access bearer between the RAN and the CN-UP.

S1706, CN-UP returns access bearer release response to CP-CN;

s1707, the CN-CP puts the Relay UE into an idle state, and simultaneously puts the Remote UE accessed through the Relay UE into the idle state;

in this step, the CN-CP looks up Remote UE accessed through Relay UE by:

-looking up Remote UE information in the context of a Relay UE; or alternatively, the first and second heat exchangers may be,

-in the context of the Remote UE, looking up Relay UE information, determining from the Relay UE information 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 flow chart of sending a downlink SMS message to a remote terminal by an application server according to a ninth embodiment of the present invention.

Fig. 18 has the following steps:

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

s1802, SM-SC obtains CN-CP to which Remote UE is currently attached, and initiates an SMS delivery request to the CN-CP;

s1803, if the Remote UE is in an idle state, the CN-CP initiates a paging process;

in the step, the CN-CP determines that paging needs to be initiated to the Remote UE according to the SMS delivery request message, and judges that the Remote UE is accessed through the Relay terminal Relay UE according to the context of the Remote UE, and initiates a paging request carrying the identification Relay UE ID of the Relay terminal and the identification Remote UE ID of the Remote terminal. The Remote terminal identifier, remote UE ID, may be one of the following: network identity (IMSI) of Remote UE, neighbor communication identity of Remote UE (e.g., layer 2 identity Layer 2ID of Remote UE on PC5 interface).

S1804, the CN-CP sends a paging request to the RAN, and the paging request carries an identification Relay UE ID of the Relay terminal;

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

S1805, the RAN sends a paging request to the Relay UE, and the paging request carries an identifier of the Relay UE ID and an identifier of the Remote terminal Remote UE ID;

s1806, after receiving the paging request, the Relay UE detects whether the Remote UE is reachable on the PC5 interface;

in this step, if the Relay UE determines that the paging request only carries the Relay UE ID, which is the identifier of the Relay terminal, the Relay UE itself responds to the paging. If the Relay UE judges that the paging request carries the Remote terminal identification Remote UE ID, detecting whether the Remote UE is reachable on the PC5 interface according to the Remote terminal identification Remote UE ID. If the Relay UE determines that the PC5 connection with the Remote UE has been released, i.e., the Remote UE is not reachable, the Relay UE may not respond to the paging request.

S1807, the Relay UE responds to the paging, initiates a service request process to the CN-CP, and restores the radio bearer, the access network bearer and the core network bearer;

s1808, because the Remote UE accesses to the network via the Relay UE, the CN-CP judges that SMS delivery should be initiated to the Relay UE;

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

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

the downlink generic NAS transport (Downlink Generic NAS Transport) message and sets the type of the message to: relaying SMS delivery;

newly introduced relay SMS deliver messages.

In the downlink generic NAS transport message, or the Relay SMS deliver message, the CN-CP carries the identity of the Remote terminal (Remote UE ID), from which the Relay UE can determine to which correct Remote UE the SMS data should be delivered. The Remote terminal identifier, remote UE ID, may be one of the following: network identity (IMSI) of Remote UE, neighbor communication identity of Remote UE (e.g., layer 2 identity Layer 2ID of Remote UE on PC5 interface).

S1810, on the PC5 interface, the Relay UE forwards an SMS delivery request to the Remote UE, carrying SMS data;

s1811, on a PC5 interface, returning an SMS delivery response to the Relay UE by the Remote UE;

s1812, the Relay UE sends a downlink NAS response to the CN-CP, carrying 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.

Examples ten

Fig. 19 is a schematic flow chart of sending downlink IP data to a remote terminal after the relay terminal and the remote terminal enter an idle state according to the tenth embodiment of the present invention.

Fig. 19 has the following steps:

s1901, relay UE attaches to the network;

s1902, as shown in the flow of FIG. 15, the Remote UE discovers the Relay UE and accesses the network through the Relay UE;

s1903, as shown in the flow of FIG. 17, the Relay UE and the Remote UE enter an idle state;

s1904, the application service sends downlink data to the Remote UE, namely 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 the CN-UP receives the downlink IP data, if the access bearer between the CN-UP and the RAN is judged to be released, a downlink data notification request is sent to the CN-CP.

S1906, the CN-CP returns a downlink data notification response to the CN-UP;

s1907, the CN-CP judges 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. Further, if the CN-CP judges that the Remote UE is accessed through the Relay terminal Relay UE, the Relay UE and the Remote UE are judged to be paged. Thus, the CN-CP carries the identification Relay UE ID of the Relay terminal and the identification Remote UE ID of the Remote terminal in the paging request. The Remote terminal identifier, remote UE ID, may be one of the following: network identity (IMSI) of Remote UE, neighbor communication identity of Remote UE (e.g., layer 2 identity Layer 2ID of Remote UE on PC5 interface).

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

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

S1909, the RAN sends a paging request to the Relay UE, and the paging request carries an identification Relay UE ID of the Relay terminal and an identification Remote UE ID of the Remote terminal;

s1910, after receiving the paging request, the Relay UE detects whether the Remote UE is reachable or not on the PC5 interface;

in this step, if the Relay UE determines that the paging request only carries the Relay UE ID, which is the identifier of the Relay terminal, the Relay UE itself responds to the paging. If the Relay UE judges that the paging request carries the Remote terminal identification Remote UE ID, detecting whether the Remote UE is reachable or not on the PC5 interface. If the Relay UE determines that the PC5 connection with the Remote UE has been released, i.e., the Remote UE is not reachable, the Relay UE may not respond to the paging request.

S1911, a Relay UE initiates a service request process to a CN-CP, and a radio bearer, an access network bearer and a core network bearer are recovered;

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

Example eleven

Fig. 20 has the following steps:

S2001-S2004, the Remote UE is attached to a network through a Relay UE1 to establish PDN connection;

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

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

in this step, the Remote UE may carry the IP address allocated to the Remote UE by the network in the foregoing procedure.

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

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

s2010, after receiving a PDN connection update request of Remote UE, the CN-CP judges that PDN connection and bearing update are required to be executed;

in this step, the CN-CP determines, according to the request of the Remote UE and the Relay information of the Remote UE, that the selected Relay terminal (Relay) of the Remote UE is changed, and needs to update the PDN connection, and should maintain the IP address previously allocated to the Remote UE.

S2011, CN-CP sends a load update request to CN-UP;

in this step, the CN-CP sends a bearer update request to the CN-UP as needed, e.g. 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 an 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 information such as NAS access response (PDN connection update response in the embodiment), remote terminal identification Remote UE ID, relay wireless data bearer and the like;

s2015, the RAN stores the context of the Relay UE and records the information of the Relay radio data bearer in the context of the Relay UE;

s2016, the RAN sends an AS access response to the Relay UE and carries information such AS PDN connection update response, remote terminal identification (Remote UE ID), relay wireless data bearer and the like;

s2017, the Relay UE stores the self context and information of Relay wireless data bearing in the context;

s2018, on the PC5 interface, the Relay UE sends a PC5 message to the Remote UE. In the PC5 message, a NAS access Response (PDN connection update Response (PDN Response) in this embodiment) is carried therein;

After the present procedure is completed, the Remote UE may continue to transmit uplink IP data or receive downlink IP data using an IP address previously allocated to the Remote UE by the network when the network is accessed through the Relay UE1, which is relayed through the Relay UE 2. That is, through the procedure shown in this embodiment, when the Remote UE switches the Relay UE, the IP address allocated by the network to the Remote UE is still kept unchanged, so as to implement service continuity.

Through the scheme provided by the embodiment of the invention, the remote terminal can realize interaction with the core network control surface through the relay of the relay terminal, finish an access process or a relay terminal reselection process, realize interaction with the remote terminal through the relay terminal, realize load creation of the remote terminal, load update during relay reselection, and initiate downlink data delivery to the remote terminal. Through the scheme, information or data transfer between the network side and the remote terminal is realized, the network side can effectively control the access or relay reselection process of the terminal, and the purpose that the network can sense or control the remote terminal when the remote terminal accesses the network through the relay terminal is achieved.

It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for a terminal to access a network, comprising:

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

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

the remote terminal receiving the NAS access response returned by the CN-CP through the relay terminal comprises the following steps: the remote terminal receives the NAS access response sent by the relay terminal to the relay terminal by using a PC5 signaling message or a PC5 data packet, wherein the NAS access response is sent to the remote terminal by the CN-CP through the relay terminal;

wherein the NAS access request includes 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 NAS access request comprises a PDN connection update request; the NAS access response includes a PDN connection update response.

2. The method of claim 1, wherein the NAS access request comprises: and the neighbor communication identifier of the remote terminal.

3. The method of claim 1, wherein the NAS access response comprises:

the carrying information of the remote terminal, wherein the carrying information of the remote terminal comprises: and the IP address and the core network bearer are allocated to the remote terminal.

4. The method of claim 3, wherein the NAS access response further comprises:

the CN-CP allocates a temporary identifier for the remote terminal.

5. The method according to any one of claims 1 to 4, wherein in case of initial access of the remote terminal to the network, the relay terminal is a relay terminal selected when the remote terminal initially accesses the network.

6. The method of claim 5, wherein the NAS access Request comprises an Attach Request; the NAS access Response includes an Attach Response.

7. The method according to any of claims 1 to 4, wherein the relay terminal is a target relay terminal in case the remote terminal reselects from an original relay terminal to the target relay terminal.

8. The method of claim 1, wherein the NAS access request further comprises the following information: the IP address of the remote terminal.

9. A method for a terminal to access a network, comprising:

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

the relay terminal forwards the NAS access response to the remote terminal;

wherein the relay terminal receiving the NAS access request from the remote terminal includes: the relay terminal receives the NAS access request sent by the remote terminal by using a PC5 signaling message or a 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 a PC5 signaling message or a PC5 data packet;

wherein the method further comprises:

the relay terminal sends relay access information to the CN-CP, wherein the relay access information comprises one or a combination of the following information: a Relay access indication Relay Indicator, and an identification Relay UE ID of the Relay terminal;

Wherein the method further comprises:

the relay terminal receives a 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 comprises an identifier Remote UE ID of the Remote terminal;

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

the relay terminal storing the relay radio data bearer in context; and/or

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

10. The method as recited in claim 9, further comprising:

and the relay terminal receives the Remote terminal identification (Remote UE ID) sent by the CN-CP.

11. The method of claim 10, wherein the relay terminal forwarding the NAS access response to the remote terminal comprises:

12. The method according to any of the claims 9 to 11, characterized in that the information sent by the CN-CP to the relay terminal is carried in an access stratum, AS, access response sent by the radio node, RAN, to the relay terminal.

13. A method for a terminal to access a network, comprising:

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

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

the RAN sends the NAS access response to the remote terminal through the relay terminal;

wherein the method further comprises:

the RAN receives a relay wireless data bearer returned by the CN-CP and an identification Remote UE ID of the Remote terminal, wherein the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information comprises the identification Remote UE ID of the Remote terminal;

wherein after the RAN receives the relay radio data bearer returned by the CN-CP, the method further comprises:

the RAN storing the relay radio data bearer in the context of the relay terminal;

wherein the RAN sending the NAS access response to the remote terminal through the relay terminal includes:

the RAN sends an Access Stratum (AS) access response to the relay terminal, wherein the AS access response comprises: the NAS access response, an identification of the Remote terminal, a Remote UE ID, and the relay wireless data bearer.

14. A method for a terminal to access a network, comprising:

the CN-CP returns NAS access response to the remote terminal through the relay terminal;

wherein the CN-CP establishing PDN connection and bearing for the remote terminal in response to the NAS access request comprises: in the case that the NAS access request comprises a PDN connection establishment request, the CN-CP sends a bearer establishment request to a core network user plane function CN-UP, wherein the bearer establishment request is used for requesting the CN-UP to establish PDN connection and bearer for the remote terminal; or alternatively, the first and second heat exchangers may be,

the CN-CP responding to the NAS access request, updating PDN connection and bearing for the remote terminal comprises the following steps: in the case that the NAS access request comprises a PDN connection update request, the CN-CP sends a bearer update request to a core network user plane (CN-UP), wherein the bearer update request is used for requesting the CN-UP to update PDN connection and bearer for the remote terminal;

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, wherein the context information of the remote terminal comprises one or a combination of the following information:

the Remote terminal identification Remote UE ID;

the bearing information of the remote terminal comprises an IP address and a core network bearing distributed to the remote terminal;

the relay access information of the remote terminal, wherein the relay access information includes: the identification Relay UE ID of the Relay terminal;

wherein the context information of the remote terminal further comprises:

neighbor communication identification of the remote terminal;

information of the remote terminal accessed through the relay terminal, wherein the information of the remote terminal accessed through the relay terminal comprises one or a combination of the following information: the Remote terminal accessed through the relay terminal is identified with a Remote UE ID and the IP address of the Remote terminal accessed through the relay terminal.

15. The method as recited in claim 14, further comprising:

the CN-CP receives relay access information, wherein the relay access information comprises one or a combination of the following information: and the identification Relay UE ID of the Relay terminal and the Relay access indication Relay Indicator.

16. The method of claim 15, wherein the NAS access request includes one or a combination of the following information:

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

17. The method of claim 16, wherein the NAS access request includes a neighbor communication identity of the remote terminal.

18. The method of claim 14, wherein the context information of the remote terminal further comprises:

and the neighbor communication identification of the remote terminal.

19. The method of claim 14, wherein after the CN-CP establishes or updates a PDN connection and bearer for the remote terminal in response to the NAS access request, further comprising:

and the CN-CP binds a core network load of the Remote terminal with a relay wireless data load serving the Remote terminal according to relay access information of the Remote terminal, wherein the attribute of the relay wireless data load is marked with load binding information, and the load binding information comprises an identification Remote UE ID of the Remote terminal.

20. The method as recited in claim 14, further comprising:

21. The method of claim 14, wherein the NAS access response includes bearer information for the remote terminal, wherein the bearer information for the remote terminal includes: and the IP address and the core network bearer are allocated to the remote terminal.

22. The method of claim 14, wherein the NAS access response includes a temporary identity assigned by the CN-CP for a remote terminal.

23. The method according to claim 14, wherein in case of initial access of the remote terminal to the network, the relay terminal is a relay terminal selected when the remote terminal initially accesses the network, the NAS access Request comprises an Attach Request; the NAS access Response includes an Attach Response.

24. The method of claim 14, wherein the relay terminal is a target relay terminal if the remote terminal reselects from an original relay terminal to the target relay terminal, the NAS access request comprising a PDN connectivity update request; the NAS access response includes a PDN connection update response.

25. The method of claim 24, wherein the NAS access request includes the following information: the remote terminal initially accesses the network by assigning an IP address to the remote terminal.

26. The method of claim 25, wherein after the CN-CP receives the NAS access request sent by the remote terminal through the relay terminal, further comprising:

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

27. A downstream data delivery method, comprising:

the CN-CP sends the downlink data to the remote terminal through a relay terminal;

wherein before the CN-CP receives the downlink data sent to the remote terminal, the CN-CP further comprises:

the CN-CP stores context information of the remote terminal, wherein the context information of the remote terminal comprises:

the Remote terminal identification Remote UE ID;

Authentication parameters of the remote terminal;

the load bearing information of the remote terminal, wherein the load bearing information comprises an IP address and a core network load bearing allocated to the remote terminal;

the relay access information of the remote terminal, wherein the relay access information comprises one or a combination of the following information: a Relay access indication Relay Indicator, and an identification Relay UE ID of the Relay terminal;

wherein, in a case that the remote terminal is in an idle state, before the CN-CP transmits the downlink data to the remote terminal through the relay terminal, the method further comprises:

28. The method of claim 27, wherein prior to the CN-CP initiating the paging request, further comprising:

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

and under the condition that the downlink data is downlink IP data, the CN-CP determines that the downlink IP data is sent to the Remote terminal according to the bearing information carried in a downlink data notification request message from a core network user plane function CN-UP, and determines an identification Remote UE ID of the Remote terminal and an identification Relay UE ID of the Relay terminal according to the context of the Remote terminal.

29. An apparatus for accessing a network by a terminal, for use in a remote terminal, comprising:

the first sending module is configured to send a non-access stratum NAS access request to a core network control plane function CN-CP through the relay terminal, where sending the non-access stratum NAS access request to the core network control plane function CN-CP through the relay terminal includes: the remote terminal sends the NAS access request to the relay terminal by using a PC5 signaling message or a PC5 data packet, wherein the NAS access request is forwarded to the CN-CP through the relay terminal; wherein the NAS access request includes 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; wherein the NAS access request includes a PDN connection update request; the NAS access response comprises a PDN connection update response;

the first receiving module is configured to receive a NAS access response returned by the CN-CP through the relay terminal, and obtain, according to the NAS access response, bearer information of the remote terminal, where receiving the NAS access response returned by the CN-CP through the relay terminal includes: the remote terminal receives the NAS access response sent by the relay terminal to the relay terminal by using a PC5 signaling message or a PC5 data packet, wherein the NAS access response is sent to the remote terminal by the CN-CP through the relay terminal.

30. The apparatus of claim 29, wherein the NAS access response comprises:

31. The apparatus of claim 29 or 30, wherein the device comprises a plurality of sensors,

the first sending module is used for sending the NAS access request comprising a PDN connection establishment request under the condition that the remote terminal initially accesses a network;

and under the condition that the remote terminal reselects from an original relay terminal to a target relay terminal, the relay terminal is the target relay terminal, and the first sending module is used for sending the NAS access request comprising a PDN connection update request.

32. An apparatus for accessing a terminal to a network, applied to a relay terminal, comprising:

a second receiving module, configured to receive a non-access stratum NAS access request from a remote terminal, where receiving the non-access stratum NAS access request from the remote terminal includes: the relay terminal receives the NAS access request sent by the remote terminal by using a PC5 signaling message or a PC5 data packet;

The first forwarding module is used for forwarding the NAS access request to a core network control plane function CN-CP;

a second forwarding module, configured to forward the NAS access response to the remote terminal, where forwarding the NAS access response to the remote terminal includes: the relay terminal forwards the NAS access response to the remote terminal by using a PC5 signaling message or a PC5 data packet;

the first forwarding module 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 an identification Relay UE ID of the Relay terminal;

the third receiving module is further configured to receive a relay radio data bearer sent by the CN-CP, where an attribute of the relay radio data bearer is marked with bearer binding information, where the bearer binding information includes an identifier Remote UE ID of the Remote terminal;

wherein the apparatus further comprises: a first storage module for storing the relay wireless data bearer in context; and the first bearing binding module is used for binding the PC5 interface of the remote terminal and the relay wireless data bearing serving the remote terminal.

33. The apparatus of claim 32, wherein the third receiving module is further configured to receive an identification Remote UE ID of the Remote terminal sent by the CN-CP.

34. The apparatus of claim 33, wherein the second forwarding module is further configured to forward the NAS access response to the Remote terminal based on an identification Remote UE ID of the Remote terminal.

35. An apparatus for accessing a network by a terminal, applied to a radio node RAN, comprising:

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

a third sending module, configured to send, through the relay terminal, the NAS access response to the remote terminal;

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, where the attribute of the relay wireless data bearer is marked with bearer binding information, and the bearer binding information includes the identifier Remote UE ID of the Remote terminal;

Wherein the apparatus further comprises: a second storage module for storing the relay wireless data bearer in the context of the relay terminal;

the third sending module is further configured to send an access stratum AS access response to the relay terminal, where the AS access response includes: the NAS access response, an identification of the Remote terminal, a Remote UE ID, and the relay wireless data bearer.

36. An apparatus for accessing a terminal to a network, applied to a core network control plane function CN-CP, comprising:

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

a fourth sending module, configured to return, through the relay terminal, a NAS access response to the remote terminal;

the establishing or updating module is further configured to, when the NAS access request includes a PDN connection establishment request, send a bearer establishment request to a CN-UP serving as a user plane of a core network, where the bearer establishment request is used to request the CN-UP to establish a PDN connection and a bearer for the remote terminal; or, in case that the NAS access request includes a PDN connection update request, the CN-CP sends a bearer update request to a core network user plane function CN-UP, where the bearer update request is used to request the CN-UP to update PDN connection and bearer for the remote terminal;

Wherein the apparatus further comprises: a second storage module, configured to store context information of the remote terminal after the establishment or update 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 identification Remote UE ID; the bearing information of the remote terminal comprises an IP address and a core network bearing distributed to the remote terminal; the relay access information of the remote terminal, wherein the relay access information includes: the identification Relay UE ID of the Relay terminal; wherein the context information of the remote terminal further comprises: neighbor communication identification of the remote terminal;

the establishing or updating module is further configured to store context information of the relay terminal, where the context information of the relay terminal includes: information of the remote terminal accessed through the relay terminal, wherein the information of the remote terminal accessed through the relay terminal comprises one or a combination of the following information: the Remote terminal accessed through the relay terminal is identified with a Remote UE ID and the IP address of the Remote terminal accessed through the relay terminal.

37. The apparatus of claim 36, wherein the fourth sending module is further configured to return an identity Remote UE ID of the Remote terminal and a relay radio data bearer, wherein bearer binding information is marked in an attribute of the relay radio data bearer, and wherein the bearer binding information includes the identity Remote UE ID of the Remote terminal.

38. The apparatus as recited in claim 36, further comprising:

and the determining module is used for determining the relay terminal change selected by the remote terminal and/or the IP address allocated to the remote terminal when the remote terminal continues to use an initial access network according to the NAS access request and the relay access information when the NAS access request comprises a PDN connection update request.

39. A downlink data delivery device applied to a core network control plane function CN-CP, comprising:

a fifth sending module, configured to send the downlink data to the remote terminal through a relay terminal;

wherein the seventh receiving module is further configured to store context information of the remote terminal, where the context information of the remote terminal includes: the Remote terminal identification Remote UE ID; authentication parameters of the remote terminal; the load bearing information of the remote terminal, wherein the load bearing information comprises an IP address and a core network load bearing allocated to the remote terminal; the relay access information of the remote terminal, wherein the relay access information comprises one or a combination of the following information: a Relay access indication Relay Indicator, and an identification Relay UE ID of the Relay terminal;

The fifth sending module is further configured to initiate a paging request when the Remote terminal is in an idle state, where the paging request carries an identifier Relay UE ID of the Relay terminal and an identifier Remote UE ID of the Remote terminal.