WO2018086452A1

WO2018086452A1 - Terminal authentication, terminal state switching, and downlink data delivery methods and devices

Info

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

Abstract

The invention provides terminal authentication, terminal state switching, and downlink data delivery methods and devices. The terminal authentication method comprises: remote user equipment (UE) transmits, to a core network control plane function (CN-CP), by relay UE performing data forwarding, a non-access stratum (NAS) layer authentication request; and the remote UE receives a NAS authentication response responded by the CN-CP and via the relay UE. By employing the method, the remote UE can realize, by the relay UE relaying data, interaction with the CN-CP, and complete an authentication process. As a result, a network side can implement full control over the remote UE, achieving the goal of a network sensing and controlling remote UE when the remote UE accesses the network via the relay UE.

Description

Terminal authentication, terminal state switching, downlink data delivery method and device

Technical field

The present disclosure relates to the field of communications, and in particular, to terminal authentication, terminal state switching, and downlink data delivery method and apparatus.

Background technique

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

Demand for D2D communication, the third generation partnership project ^(the 3 ^rd Generation Partnership Project referred to as 3GPP) set up a special research project - Near Field Communication Services (Proximity Service, referred to as ProSe), to support D2D communications. In D2D communication, there is a typical service requirement, which enables a remote terminal (Remote UE) to access the network through a relay terminal (Relay UE) without network coverage.

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

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

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

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

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

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

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

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

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

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

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

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

Relay UE: Provides relay access support for remote terminals.

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

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

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

S202, the Remote UE discovers the Relay UE;

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

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

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

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

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

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

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

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

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

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

Summary of the invention

The embodiments of the present disclosure provide a terminal authentication, a terminal state switching, a downlink data delivery method, and a device, to at least solve the problem that the network has no control over a remote terminal (Remote UE) in the related art.

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

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

The remote terminal receives a NAS authentication response returned by the CN-CP through the relay terminal.

Optionally, the sending, by the remote terminal, the NAS authentication request to the CN-CP by using the forwarding by the relay terminal includes:

Transmitting, by the remote terminal, the NAS authentication request to the relay terminal by using a PC5 signaling message or a PC5 data packet;

Receiving, by the remote terminal, the NAS authentication response returned by the CN-CP through the relay terminal includes:

The remote terminal receives the NAS authentication response sent by the relay terminal to the relay terminal using a PC5 signaling message or a PC5 data packet.

Optionally, the NAS authentication request sent by the remote terminal includes:

The network identity and authentication parameters of the remote terminal.

The neighbor communication identifier of the remote terminal.

Optionally, the NAS authentication response includes the following information:

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

Optionally, after the remote terminal sends the NAS authentication request to the CN-CP by using the forwarding by the relay terminal, the method further includes:

Receiving, by the remote terminal, an authentication challenge sent by the CN-CP to the remote terminal by using the relay terminal;

The remote terminal calculates an authentication challenge response, and sends the authentication challenge response to the CN-CP by forwarding by the relay terminal.

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

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

Transmitting, by the relay terminal, the NAS authentication request to a core network control plane function CN-CP;

The relay terminal receives a NAS authentication response from the CN-CP;

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

Optionally, the receiving, by the relay terminal, the NAS authentication request from the remote terminal includes:

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

Forwarding, by the relay terminal, the NAS authentication response to the remote terminal includes:

The relay terminal transmits the NAS authentication response to the remote terminal using a PC5 signaling message or a PC5 data packet.

Optionally, the forwarding, by the relay terminal, the NAS authentication request to the CN-CP includes:

The relay terminal sends an uplink general-purpose NAS transmission message to the CN-CP, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates that the service type is a relay NAS authentication service; or,

The relay terminal sends a relay NAS authentication request message to the CN-CP, where the relay NAS authentication request message carries the NAS authentication request.

Optionally, the method further includes:

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

Optionally, the receiving, by the relay terminal, the NAS authentication response from the CN-CP includes:

The relay terminal receives a downlink general NAS transmission message from the CN-CP, where the downlink general NAS transmission message carries the NAS authentication response, and the downlink general NAS transmission message indicates that the service type is medium Following the NAS authentication business;

The relay terminal receives a relay NAS authentication response message from the CN-CP, wherein the relay NAS authentication response message carries the NAS authentication response.

Optionally, the NAS authentication response includes the following information:

Optionally, the method further includes:

The relay terminal receives the identifier Remote UE ID of the remote terminal from the CN-CP, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following: a network identity of the remote terminal, The neighbor communication identifier of the remote terminal.

Optionally, the relaying, by the relay terminal, the NAS authentication response to the remote terminal includes:

The relay terminal forwards the NAS authentication response to the remote terminal according to the identifier Remote UE ID of the remote terminal.

Optionally, after the relay terminal forwards the NAS authentication request to the core network control plane function CN-CP, the method further includes:

Receiving, by the relay terminal, an authentication challenge sent by the CN-CP;

The relay terminal forwards the authentication challenge to the remote terminal;

Receiving, by the relay terminal, an authentication challenge response sent by the remote terminal in response to the authentication challenge;

The relay terminal forwards the authentication challenge response to the CN-CP.

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

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

The CN-CP authenticates the remote terminal to generate a NAS authentication response;

The CN-CP returns the NAS authentication response to the remote terminal by forwarding by the relay terminal.

Optionally, the receiving, by the CN-CP, the NAS authentication request sent by the remote terminal by using the relay terminal includes:

The CN-CP receives an uplink general-purpose NAS transmission message sent by the relay terminal, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates that the service type is medium Following the NAS authentication business; or,

The CN-CP receives a relay NAS authentication request message sent by the relay terminal, where the relay NAS authentication request message carries the NAS authentication request.

Optionally, the NAS authentication request received by the CN-CP includes:

The network identity and authentication parameters of the remote terminal.

Optionally, the NAS authentication request received by the CN-CP includes:

The neighbor communication identifier of the remote terminal.

Optionally, the method further includes:

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

Optionally, after the CN-CP authenticates the remote terminal, the method further includes:

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

Remote terminal information, where the remote terminal information includes one or a combination of the following: an identifier of the remote terminal, a Remote UE ID, and an IP address of the remote terminal;

And relaying the access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID.

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

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

Optionally, the returning, by the CN-CP, the NAS authentication response to the remote terminal by forwarding by the relay terminal includes:

The CN-CP sends a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries the NAS authentication response, and the downlink general NAS transmission message indicates that the service type is a relay NAS authentication service;

The CN-CP sends a relay NAS authentication response message to the relay terminal, where the relay NAS authentication response message carries the NAS authentication response.

Optionally, the NAS authentication response includes the following information:

Optionally, the method further includes:

The CN-CP sends the identifier of the remote terminal to the relay terminal, where the remote UE ID includes at least one of the following information: a network identity of the remote terminal, The neighbor communication identifier of the remote terminal.

Optionally, after the core network control plane function CN-CP receives the non-access stratum NAS authentication request sent by the remote terminal by using the relay terminal, the method further includes:

Sending, by the relay terminal, the authentication challenge to the remote terminal by using the relay terminal;

The CN-CP receives an authentication challenge response returned by the remote terminal through the relay terminal.

Transmitting, by the CN-CP, remote terminal information to a core network user plane function CN-UP, where the remote terminal information includes one or a combination of the following information: an identifier of the remote terminal, a Remote UE ID, and an IP of the remote terminal. The address, the information of whether the remote terminal is authenticated or not.

According to still another embodiment of the present disclosure, a terminal state switching method is provided, including:

The core network control plane function CN-CP receives a connection release request from the wireless node RAN, wherein the connection release request is used to request to release the connection of the relay terminal;

The CN-CP releases the connection of the relay terminal, puts the relay terminal into an idle state, and places the remote terminal accessed through the relay terminal into an idle state.

Optionally, the CN-CP puts the remote terminal accessed by the relay terminal into an idle state, including:

Determining, by the CN-CP, the remote terminal accessed by the relay terminal according to user context information of the relay terminal or user context information of the remote terminal;

The CN-CP places the determined remote terminal into an idle state.

Optionally, the user context information of the relay terminal includes: information of a remote terminal accessed by the relay terminal; and the CN-CP determines, according to user context information of the relay terminal, the relay The remote terminal accessed by the terminal includes: the CN-CP searching for the remote terminal accessed by the relay terminal in user context information of the relay terminal;

and / or,

The user context information of the remote terminal includes: remote terminal information and relay access information; and determining, by the CN-CP, the remote terminal accessed by the relay terminal according to the user context information of the remote terminal includes: Determining, by the CN-CP, whether the remote terminal is connected via the relay terminal according to the relay access information in user context information of the remote terminal In.

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

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

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

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

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

Optionally, before the sending, by the CN-CP, the downlink data to the remote terminal by using the relay terminal, the method further includes:

The CN-CP initiates a paging request, where the paging request carries an identifier Relay UE ID of the relay terminal and an identifier of the remote terminal, a Remote UE ID, where the identifier of the remote terminal is a Remote UE. The ID includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.

Optionally, the sending, by the CN-CP, the downlink data to the remote terminal by using a relay terminal includes:

The CN-CP sends the downlink data sent to the remote terminal to the relay terminal according to the relay access information of the remote terminal.

The CN-CP sends a downlink general NAS transmission message to the relay terminal, where the downlink universal NAS transmission message carries the downlink data, and the downlink universal NAS transmission disappears. In the information, indicate that the service type is relay data delivery; or,

The CN-CP sends a relay data delivery message to the relay terminal corresponding to the remote terminal, where the relay data delivery message carries the downlink data.

Optionally, the downlink universal NAS transmission message or the relay data delivery message carries an identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.

Optionally, the CN-CP determines, by at least one of the following manners, that the downlink data is downlink data that is sent to the remote terminal:

In a case where the downlink data is short message service SMS information, the CN-CP determines, according to an SMS delivery request message, that the SMS information is sent to the remote terminal;

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 a downlink data notification request message from the core network user plane function CN-UP.

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

The relay terminal sends the downlink data to the remote terminal.

Optionally, before the receiving, by the relay terminal, the downlink data that is sent by the CN-CP and sent to the remote terminal that is accessed by the relay terminal, the method further includes:

The relay terminal receives the paging request sent by the CN-CP, where the paging request carries the identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes the following information. At least one of: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal;

The relay terminal initiates a service request procedure to the CN-CP if it is acknowledging that the remote terminal is reachable.

Optionally, the sending, by the relay terminal, the downlink data to the remote terminal includes:

The relay terminal transmits the downlink data to the remote terminal through a PC5 interface with the remote terminal.

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

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

The first receiving module is configured to receive a NAS authentication response returned by the CN-CP through the relay terminal.

Optionally, the NAS authentication request sent by the first sending module includes:

The network identity and authentication parameters of the remote terminal.

The neighbor communication identifier of the remote terminal.

Optionally, the NAS authentication response includes the following information:

According to still another embodiment of the present disclosure, a terminal authentication apparatus is provided, which is applied to a relay terminal, and includes:

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

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

a third receiving module, configured to receive a NAS authentication response from the CN-CP;

And a second forwarding module, configured to forward the NAS authentication 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: a relay access indication Relay Indicator The identifier of the relay terminal is a Relay UE ID.

Optionally, the NAS authentication response includes the following information:

Optionally, the third receiving module is further configured to:

Receiving an identifier of the remote terminal from the CN-CP, the remote UE ID, where the identifier of the remote terminal includes at least one of the following: a network identity of the remote terminal, and a remote terminal Neighboring communication logo.

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

According to still another embodiment of the present disclosure, a terminal authentication apparatus is provided, which is applied to a core network control plane function CN-CP, and includes:

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

An authentication module configured to authenticate the remote terminal to generate a NAS authentication response;

The second sending module is configured to return the NAS authentication response to the remote terminal by forwarding by the relay terminal.

Optionally, the NAS authentication request received by the fourth receiving module includes:

The network identity and authentication parameters of the remote terminal.

The neighbor communication identifier of the remote terminal.

Optionally, the fourth receiving module is further configured to receive relay access information sent by the relay terminal, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, the relay UE ID of the relay terminal.

Optionally, the device further includes a first storage module, configured to store user context information of the remote terminal after the authentication module authenticates the remote terminal, where the user of the remote terminal The context information includes:

Optionally, the first storage module is further configured to: after the remote terminal performs authentication, storing user context information of the relay terminal, where the user context information of the relay terminal includes:

Optionally, the NAS authentication response includes the following information:

The result of the authentication and the temporary identification assigned to the remote terminal.

Optionally, the second sending module is further configured to send, to the relay terminal, an identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.

According to still another embodiment of the present disclosure, a terminal state switching apparatus is provided, which is applied to a core network control plane function CN-CP, and includes:

a fifth receiving module, configured to receive a connection release request from the wireless node RAN, where the connection release request is used to request to release the connection of the relay terminal;

Connecting a release module, configured to release a connection of the relay terminal;

The status setting module is configured to put the relay terminal into an idle state, and place the remote terminal accessed through the relay terminal into an idle state.

Optionally, the status setting module includes:

a determining unit, configured to be based on user context information of the relay terminal or the remote terminal The user context information of the terminal determines the remote terminal accessed through the relay terminal;

a status setting unit configured to put the determined remote terminal into an idle state.

Optionally, the user context information of the relay terminal includes: information of a remote terminal accessed by the relay terminal; the determining unit is configured to search through the user context information of the relay terminal by using the The remote terminal accessed by the relay terminal;

and / or,

The user context information of the remote terminal includes: remote terminal information and relay access information; the determining unit is configured to determine the remote terminal according to the relay access information in the user context information of the remote terminal. Whether to access via the relay terminal.

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

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

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

Optionally, the device further includes a second storage module, configured to store context information of the remote terminal, where the context information of the remote terminal includes:

Optionally, the device further includes a paging module, configured to send, by the third sending module, the downlink data to the remote terminal by using the relay terminal, when the remote terminal is in an idle state. The paging request is initiated, wherein the paging request carries the identifier Relay UE ID of the relay terminal and the identifier of the remote terminal, and the remote UE ID, where the identifier of the remote terminal includes the following At least one of the information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.

Optionally, the third sending module is configured to send the downlink data sent to the remote terminal to the relay terminal according to the relay access information of the remote terminal.

Optionally, the third sending module is configured to:

Sending a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries the downlink data, and the downlink general NAS transmission message indicates that the service type is relay data delivery; or

And transmitting, to the relay terminal corresponding to the remote terminal, a relay data delivery message, where the relay data delivery message carries the downlink data.

According to still another embodiment of the present disclosure, a downlink data delivery device is provided, which is applied to a relay terminal, and includes:

The seventh receiving module is configured to receive downlink data sent by the core network control plane function CN-CP to the remote terminal accessed through the relay terminal;

The fourth sending module is configured to send the downlink data to the remote terminal.

Optionally, the device further includes:

And an eighth receiving module, configured to receive a paging request sent by the CN-CP, where the paging request carries an identifier of the remote terminal, a Remote UE ID, where the identifier of the remote terminal includes: At least one of the following information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal;

The service request module is configured to initiate a service request process to the CN-CP in the case of confirming that the remote terminal is reachable.

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

According to still another embodiment of the present disclosure, there is also provided a processor for running a program, wherein the program is executed to perform the steps of any of the above methods.

Through the solution of some embodiments of the present disclosure, the remote terminal can implement interaction with the core network control plane through the relay of the relay terminal, and complete the authentication process, and the core network control plane implements interaction with the remote terminal through the relay terminal, The authentication of the remote terminal can be implemented, and the downlink data delivery can be initiated to the remote terminal. At the same time, the control plane of the core network can also complete the switching of the state of the remote terminal in real time, and put the remote terminal into an idle state. Through the above solution, the network side implements all-round control on the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

DRAWINGS

The drawings described herein are intended to provide an understanding of the present disclosure, and are intended to be a part of the present disclosure. In the drawing:

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

2 is a schematic flowchart of obtaining an IP service by a remote terminal accessing a network through a relay terminal according to the architecture shown in FIG. 1;

3 is a flowchart of a terminal authentication method applied to a remote terminal side according to Embodiment 1 of the present disclosure;

4 is a flowchart of a terminal authentication method applied to a relay terminal side according to Embodiment 1 of the present disclosure;

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

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

7 is downlink data applied to a functional side of a control plane of a core network according to Embodiment 3 of the present disclosure. Flow chart of the delivery method;

8 is a flowchart of a downlink data delivery method applied to a relay terminal side according to Embodiment 3 of the present disclosure;

9 is a structural block diagram of a terminal authentication apparatus applied to a remote terminal according to Embodiment 4 of the present disclosure;

10 is a structural block diagram of a terminal authentication apparatus applied to a relay terminal according to Embodiment 4 of the present disclosure;

11 is a structural block diagram of a terminal authentication apparatus applied to a core network control plane function according to Embodiment 4 of the present disclosure;

12 is a structural block diagram of a terminal state switching device applied to a core network control plane function according to Embodiment 5 of the present disclosure;

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

14 is a structural block diagram of a downlink data delivery device applied to a relay terminal according to Embodiment 6 of the present disclosure;

15 is a schematic structural diagram of Embodiment 7 of the present disclosure;

16A is a first schematic diagram of a control plane protocol stack according to Embodiment 7 of the present disclosure;

16B is a second schematic diagram of a control plane protocol stack according to Embodiment 7 of the present disclosure;

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

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

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

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

20 is a schematic flowchart of an application server transmitting a downlink SMS message to a remote terminal according to Embodiment 11 of the present disclosure;

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

detailed description

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

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

Embodiment 1

According to the first embodiment of the present disclosure, a terminal authentication method is provided, which is applied to a remote terminal side. FIG. 3 is a flowchart of a terminal authentication method applied to a remote terminal side according to Embodiment 1 of the present disclosure. As shown in FIG. 3, the process includes the following steps:

Step S302: The remote terminal sends a NAS authentication request to the core network control plane function (Core Network-Control Plane, CN-CP for short) through forwarding of the relay terminal;

Step S302: The remote terminal receives the NAS authentication response returned by the CN-CP through the relay terminal.

Through the method, the remote terminal can realize the interaction with the control plane of the core network through the relay of the relay terminal, and complete the authentication process, so that the control plane of the core network can realize the interaction with the remote terminal through the relay terminal, thereby realizing the remote Terminal authentication. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the information interaction between the remote terminal and the relay terminal may be implemented by using a PC5 interface. For example, in step S302, the remote terminal may send a NAS authentication request to the relay terminal by using a PC5 signaling message or a PC5 data packet. In step S304, the remote terminal may receive the NAS authentication response sent by the relay terminal to the relay terminal using the PC5 signaling message or the PC5 data packet.

In order to facilitate the CN-CP to authenticate the remote terminal, the NAS certificate sent at the remote terminal The right request may include a network identity and an authentication parameter of the remote terminal.

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

The NAS authentication response may include the following information: an authentication result and a temporary identifier assigned by the CN-CP to the remote terminal. Through the above information carried in the NAS authentication response, the remote terminal can confirm the authentication result of the core network to itself, and obtain the temporary identifier allocated by the CN-CP for the remote terminal.

In the process of implementing the authentication, in order to improve the accuracy and security of the authentication process, after the remote terminal sends the NAS authentication request to the CN-CP by forwarding the relay terminal, the following steps may be further included: the remote terminal receives the CN - an authentication challenge sent by the CP to the remote terminal through the relay terminal; the remote terminal calculates an authentication challenge response, and transmits an authentication challenge response to the CN-CP through forwarding of the relay terminal.

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

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

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

Step S406, the relay terminal receives the NAS authentication response from the CN-CP;

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

Through the method, the relay terminal can implement the pre-transmission of the message interaction between the control plane of the core network and the remote terminal, thereby cooperating with the implementation of the authentication process. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the information interaction between the remote terminal and the relay terminal may be implemented by using a PC5 interface. For example, in S402, the relay terminal may receive a NAS authentication request sent by the remote terminal by using a PC5 signaling message or a PC5 data packet. In S408, the relay terminal can use PC5 signaling to eliminate The packet or PC5 packet sends a NAS authentication response to the remote terminal.

In order to facilitate the CN-CP to obtain the information of the relay terminal that the remote terminal currently requesting authentication to access when accessing the network, the relay terminal may forward the NAS authentication request to the CN-CP, and the relay terminal may further The CN-CP sends the relay access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID. It should be noted that the relay terminal may send the relay access information in multiple manners. For example, the relay access information may be sent at the same time as the NAS authentication request is sent, specifically in the NAS The relay access information is encapsulated outside the right request.

In the actual application process, the relay terminal can forward the NAS authentication request to the CN-CP in multiple ways, for example:

The relay terminal may send an uplink general-purpose NAS transmission message to the CN-CP, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates that the service type is the relay NAS authentication service; or

The relay terminal may send a relay NAS authentication request message to the CN-CP, where the relay NAS authentication request message carries the NAS authentication request.

Similarly, the relay terminal can also receive the NAS authentication response sent by the CN-CP in multiple ways, for example:

The relay terminal may receive the downlink general NAS transmission message from the CN-CP, where the downlink general NAS transmission message carries the NAS authentication response, and the downlink general NAS transmission message indicates that the service type is the relay NAS authentication service;

The relay terminal may receive a relay NAS authentication response message from the CN-CP, wherein the relay NAS authentication response message carries a NAS authentication response.

The NAS authentication response may include the following information: an authentication result and a temporary identifier assigned by the CN-CP to the remote terminal.

In order to facilitate the relay terminal to forward the NAS authentication response to the correct remote terminal, the CN-CP may simultaneously mark the remote terminal's identity Remote UE ID when returning the NAS authentication response. Therefore, in addition to receiving the NAS authentication response from the CN-CP, the relay terminal can also The remote UE ID of the remote terminal from the CN-CP is received, wherein the remote UE ID of the remote terminal includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal. It should be noted that the relay terminal may receive the identifier of the remote terminal, the Remote UE ID, when receiving the NAS authentication response. For example, the identifier of the received remote terminal, the Remote UE ID, may be encapsulated outside the NAS authentication response.

The relay terminal forwards the NAS authentication response to the remote terminal according to the identifier of the remote terminal, the Remote UE ID. In this way, the relay terminal can forward the received NAS authentication response to the correct remote terminal.

Optionally, in the process of implementing the authentication, in order to improve the accuracy and security of the authentication process, after the relay terminal forwards the NAS authentication request to the core network control plane function CN-CP, the relay terminal may receive the CN- The authentication challenge sent by the CP and forwarding the authentication challenge to the remote terminal; the relay terminal receives the authentication challenge response sent by the remote terminal in response to the authentication challenge, and forwards the authentication challenge response to the CN-CP.

According to the first embodiment of the present disclosure, a terminal authentication method is further provided, which is applied to a CN-CP. FIG. 5 is a flowchart of a terminal authentication method applied to a function side of a control plane of a core network according to Embodiment 1 of the present disclosure. As shown in FIG. 5, the process includes the following steps:

Step S502, the CN-CP receives the NAS authentication request sent by the remote terminal through the relay terminal.

Step S504, the CN-CP authenticates the remote terminal to generate a NAS authentication response.

Step S506, the CN-CP returns a NAS authentication response to the remote terminal by forwarding the relay terminal.

Through this method, the core network control plane can implement interaction with the remote terminal through the relay terminal, thereby realizing authentication of the remote terminal. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

In the actual application process, the CN-CP can receive NAS authentication requests sent by the relay terminal in multiple ways, for example:

The CN-CP receives the uplink general-purpose NAS transmission message sent by the relay terminal, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates The service type is a relay NAS authentication service; or,

The CN-CP receives the relay NAS authentication request message sent by the relay terminal, where the relay NAS authentication request message carries the NAS authentication request.

In order to facilitate the smooth implementation of the authentication, the NAS authentication request received by the CN-CP includes: the network identity of the remote terminal and the authentication parameter.

The NAS authentication request received by the CN-CP may include a neighbor communication identifier of the remote terminal. Through the neighbor communication identifier of the remote terminal carried in the NAS authentication request, the CN-CP can simultaneously mark the neighbor communication identifier of the remote terminal when returning the NAS authentication response, so that the relay terminal forwards the NAS authentication response to the correct one. Remote terminal.

The CN-CP may further receive the relay access information sent by the relay terminal, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID. . Through the information, the CN-CP can acquire information about the relay terminal that the remote terminal currently requesting authentication uses when accessing the network.

In order to facilitate the control of the remote terminal and the subsequent information exchange or data interaction, the CN-CP can store the user context information of the remote terminal after the CN-CP authenticates the remote terminal, wherein the user context information of the remote terminal includes:

Remote terminal information, where the remote terminal information includes one or a combination of the following information: a remote terminal identifier, a remote UE ID, and an IP address of the remote terminal;

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

In order to facilitate the control of the remote terminal and implement subsequent information interaction or data interaction, after the CN-CP authenticates the remote terminal, the CN-CP may store the user context information of the relay terminal, wherein the user context of the relay terminal Information includes:

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

In the actual application process, the CN-CP can send the NAS authentication response to the relay terminal in multiple ways, for example:

The CN-CP may send a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries a NAS authentication response, and the downlink general NAS transmission message indicates that the service type is a relay NAS authentication service;

The CN-CP may send a relay NAS authentication response message to the relay terminal, where the relay NAS authentication response message carries the NAS authentication response.

In order to facilitate the relay terminal to identify which remote terminal the NAS authentication response should be sent to, the CN-CP may send the remote terminal's identifier Remote UE ID to the relay terminal, where the remote terminal's identifier Remote UE ID includes at least one of the following information. : The network identity of the remote terminal and the neighbor communication identifier of the remote terminal. It should be noted that the CN-CP may send the remote UE ID in a plurality of manners when transmitting the remote UE ID of the remote terminal. For example, the remote UE may be sent with the identifier of the remote terminal while transmitting the NAS authentication response. The remote UE ID of the remote terminal is encapsulated in addition to the NAS authentication response.

Optionally, in the process of implementing the authentication, in order to improve the accuracy and security of the authentication process, after the CN-CP receives the non-access stratum NAS authentication request sent by the remote terminal through the relay terminal, the CN-CP may pass The relay terminal sends an authentication challenge to the remote terminal and receives an authentication challenge response returned by the remote terminal through the relay terminal.

In order to enable the core network user plane to obtain the information of the remote terminal, after the CN-CP authenticates the remote terminal, the CN-CP may send the remote terminal information to the core network user plane function (Core Network-User Plane, referred to as CN-UP). The remote terminal information includes one or a combination of the following information: a remote terminal identifier, a remote UE ID, an IP address of the remote terminal, and information about whether the remote terminal authenticates.

Embodiment 2

According to the second embodiment of the present disclosure, a terminal state switching method is provided, which is applied to CN-CP side. FIG. 6 is a flowchart of a terminal state switching method applied to a function side of a control plane of a core network according to Embodiment 2 of the present disclosure. As shown in FIG. 6, the process includes the following steps:

Step S602, the CN-CP receives a connection release request from the wireless node RAN, where the connection release request is used to request to release the connection of the relay terminal;

Step S604, the CN-CP releases the connection of the relay terminal, puts the relay terminal into an idle state, and puts the remote terminal accessed through the relay terminal into an idle state.

Through this method, the core network control plane can complete the switching of the state of the remote terminal in real time, and put the remote terminal into an idle state. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

In an actual application, the CN-CP may determine the remote terminal accessed through the relay terminal according to the user context information of the relay terminal or the user context information of the remote terminal, and place the determined remote terminal into an idle state.

The user context information of the relay terminal may include: information of the remote terminal accessed through the relay terminal; the CN-CP may determine the remote terminal accessed through the relay terminal according to the user context information of the relay terminal in the following manner: CN- The CP searches for the remote terminal accessed by the relay terminal in the user context information of the relay terminal;

and / or,

The user context information of the remote terminal may include: remote terminal information and relay access information; the CN-CP may determine the remote terminal accessed through the relay terminal according to the user context information of the remote terminal in the following manner: CN-CP according to the remote terminal The relay access information in the user context information determines whether the remote terminal is accessed via the relay terminal.

Embodiment 3

According to the third embodiment of the present disclosure, a downlink data delivery method is provided, which is applied to the CN-CP side. 7 is a flowchart of a downlink data delivery method applied to a function side of a control plane of a core network according to Embodiment 3 of the present disclosure. As shown in FIG. 7, the process includes the following steps:

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

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

Through the method, the core network control plane implements interaction with the remote terminal through the relay terminal, and can implement downlink data delivery to the remote terminal. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, before the CN-CP receives the downlink data sent to the remote terminal, the CN-CP may store the context information of the remote terminal, where the context information of the remote terminal includes:

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

The CN-CP initiates a paging request, where the paging request carries the identifier Relay UE ID of the relay terminal and the identifier of the remote terminal, the Remote UE ID, wherein the identifier of the remote terminal, the Remote UE ID, includes at least one of the following information: the remote terminal Network identity, proximity communication identifier of the remote terminal.

In practical applications, the CN-CP may send downlink data to the remote terminal to the relay terminal according to the relay access information of the remote terminal.

Optionally, the CN-CP can send downlink data to the remote terminal through the relay terminal in multiple manners, for example:

The CN-CP may send the downlink general-purpose NAS transmission message to the relay terminal, where the downlink general-purpose NAS transmission message carries the downlink data, and the downlink general-purpose NAS transmission message indicates that the service type is the relay data delivery; or

The CN-CP may send a relay data delivery message to the relay terminal corresponding to the remote terminal, where The relay data delivery message carries downlink data.

Optionally, the downlink general NAS transport message or the relay data delivery message may carry the identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following: a network identity of the remote terminal, and a remote terminal. Neighboring communication logo.

Optionally, the CN-CP may determine, by at least one of the following manners, that the downlink data is downlink data that is sent to the remote terminal:

In the case that the downlink data is the short message service SMS information, the CN-CP determines that the SMS information is sent to the remote terminal according to the 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 downlink data notification request message from the core network user plane function CN-UP.

According to the third embodiment of the present disclosure, a downlink data delivery method is also provided, which is applied to a relay terminal. FIG. 8 is a flowchart of a downlink data delivery method applied to a relay terminal side according to Embodiment 3 of the present disclosure, such as As shown in FIG. 8, the process includes the following steps:

Step S802: The relay terminal receives downlink data sent by the CN-CP and sent to the remote terminal accessed through the relay terminal.

Step S804, the relay terminal sends downlink data to the remote terminal.

Through the method, the relay terminal can implement interaction between the control plane of the core network and the remote terminal, so that the core network control plane can initiate downlink data delivery to the remote terminal. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, before the receiving, by the relay terminal, the downlink data sent by the CN-CP to the remote terminal accessed by the relay terminal, the method further includes:

The relay terminal receives the paging request sent by the CN-CP, where the paging request carries the identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following information: the network identity of the remote terminal , the neighboring communication identifier of the remote terminal;

The relay terminal initiates a service request to the CN-CP if it confirms that the remote terminal is reachable. Cheng.

Optionally, the relay terminal may send downlink data to the remote terminal through a PC5 interface with the remote terminal.

Embodiment 4

According to a fourth embodiment of the present disclosure, a terminal authentication apparatus is provided, which is applied to a remote terminal, and FIG. 9 is a structural block diagram of a terminal authentication apparatus applied to a remote terminal according to Embodiment 4 of the present disclosure, as shown in FIG. , the device includes:

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

The first receiving module 94 is coupled to the first sending module 92 and configured to receive the NAS authentication response returned by the CN-CP through the relay terminal.

Through the device, the remote terminal can realize the interaction with the control plane of the core network through the relay of the relay terminal, and complete the authentication process, so that the control plane of the core network can realize the interaction with the remote terminal through the relay terminal, thereby realizing the remote Terminal authentication. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the NAS authentication request sent by the first sending module 92 may include:

Network identity and authentication parameters of the remote terminal.

Optionally, the NAS authentication request sent by the first sending module 92 includes:

Neighbor communication identifier of the remote terminal.

Optionally, the NAS authentication response may include the following information:

According to Embodiment 4 of the present disclosure, a terminal authentication apparatus is further provided, which is applied to a relay terminal, and FIG. 10 is a structural block diagram of a terminal authentication apparatus applied to a relay terminal according to Embodiment 4 of the present disclosure, as shown in FIG. As shown in Figure 10, the device comprises:

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

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

The third receiving module 1006 is coupled to the first forwarding module 1004 and configured to receive a NAS authentication response from the CN-CP.

The second forwarding module 1008 is coupled to the third receiving module 1006 and configured to forward the NAS authentication response to the remote terminal.

Through the device, the relay terminal can implement the pre-transmission of the message interaction between the control plane of the core network and the remote terminal, thereby cooperating with the implementation of the authentication process. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

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

Optionally, the NAS authentication response may include the following information: an authentication result and a temporary identifier assigned by the CN-CP to the remote terminal.

Optionally, the third receiving module 1006 is further configured to:

Receiving an identifier of the remote terminal from the CN-CP, the Remote UE ID, wherein the identifier of the remote terminal, the Remote UE ID, includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.

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

According to Embodiment 4 of the present disclosure, a terminal authentication apparatus is provided, which is applied to a core network control plane function CN-CP, and FIG. 11 is a terminal authentication apparatus applied to a core network control plane function according to Embodiment 4 of the present disclosure. The structural block diagram, as shown in Figure 11, the device includes:

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

The authentication module 1104 is coupled to the fourth receiving module 1102 and configured to perform the remote terminal Authentication, generating a NAS authentication response;

The second sending module 1106 is coupled to the authentication module 1104 and configured to return a NAS authentication response to the remote terminal by forwarding the relay terminal.

Through the device, the core network control plane can implement interaction with the remote terminal through the relay terminal, thereby realizing authentication of the remote terminal. Through the above solution, when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the NAS authentication request received by the fourth receiving module 1102 may include:

Network identity and authentication parameters of the remote terminal.

Optionally, the NAS authentication request received by the fourth receiving module 1102 may include one or a combination of the following information:

Neighbor communication identifier of the remote terminal;

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

Optionally, the device may further include: a first storage module, configured to: after the authentication module authenticates the remote terminal, store user context information of the remote terminal, where the user context information of the remote terminal includes:

Optionally, the NAS authentication response includes the following information:

The result of the authentication and the temporary identity assigned to the remote terminal.

Optionally, the second sending module 1106 is further configured to send, to the relay terminal, an identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following information: a network identity of the remote terminal, and a remote terminal. Neighboring communication logo.

Embodiment 5

According to the fifth embodiment of the present disclosure, a terminal state switching device is provided, which is applied to a core network control plane function CN-CP, and FIG. 12 is a terminal state switching device applied to a core network control plane function according to Embodiment 5 of the present disclosure. The structural block diagram, as shown in Figure 12, includes:

The fifth receiving module 1202 is configured to receive a connection release request from the wireless node RAN, where the connection release request is used to request to release the connection of the relay terminal;

The connection release module 1204 is coupled to the fifth receiving module 1202 and configured to release the connection of the relay terminal;

The state setting module 1206 is coupled to the connection release module 1204, configured to put the relay terminal into an idle state, and place the remote terminal accessed through the relay terminal into an idle state.

Through the device, the core network control plane can complete the switching of the state of the remote terminal in real time, and put the remote terminal into an idle state. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the state setting module 1206 includes:

a determining unit, configured to determine, according to user context information of the relay terminal or user context information of the remote terminal, a remote terminal accessed through the relay terminal;

Optionally, the user context information of the relay terminal may include: information of the remote terminal accessed by the relay terminal; the determining unit is configured to search for the remote terminal accessed by the relay terminal in the user context information of the relay terminal;

and / or,

The user context information of the remote terminal may include: remote terminal information and relay access information; the determining unit is configured to determine whether the remote terminal is accessed via the relay terminal according to the relay access information in the user context information of the remote terminal.

Embodiment 6

According to the sixth embodiment of the present disclosure, a downlink data delivery device is provided, which is applied to a core network control plane function CN-CP, and FIG. 13 is a downlink data delivery device applied to a core network control plane function according to Embodiment 6 of the present disclosure. The structural block diagram, as shown in Figure 13, the device includes:

The sixth receiving module 1302 is configured to receive downlink data sent to the remote terminal.

The third sending module 1304 is coupled to the sixth receiving module 1302 and configured to send downlink data to the remote terminal by using the relay terminal.

Through the device, the core network control plane realizes interaction with the remote terminal through the relay terminal, and can implement downlink data delivery to the remote terminal. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the device may further include a second storage module, configured to store context information of the remote terminal, where the context information of the remote terminal includes:

Optionally, the device may further include a paging module, configured to initiate a paging request before the third sending module 1304 sends the downlink data to the remote terminal by using the relay terminal, where the remote terminal is in the idle state, where The paging request carries the identifier Relay UE ID of the relay terminal and the identifier of the remote terminal. The remote UE ID includes at least one of the following information: a network identity of the remote terminal, and a neighbor communication of the remote terminal. Logo.

Optionally, the third sending module 1304 may be configured to send downlink data sent to the remote terminal to the relay terminal according to the relay access information of the remote terminal.

Optionally, the third sending module 1304 is configured to:

Sending a downlink general-purpose NAS transmission message to the relay terminal, where the downlink general-purpose NAS transmission message carries the downlink data, and the downlink general-purpose NAS transmission message indicates that the service type is the relay data delivery; or

And transmitting a relay data delivery message to the relay terminal corresponding to the remote terminal, where the relay data delivery message carries the downlink data.

Optionally, the downlink universal NAS transmission message or the relay data delivery message carries the identifier of the remote terminal, and the remote UE ID includes at least one of the following information: a network identity of the remote terminal, and a remote terminal. Neighboring communication logo.

According to the sixth embodiment of the present disclosure, there is also provided a downlink data delivery device, which is applied to a relay terminal, and FIG. 14 is a structural block diagram of a downlink data delivery device applied to the relay terminal according to Embodiment 6 of the present disclosure, as shown in the figure. As shown in Figure 14, the device includes:

The seventh receiving module 1402 is configured to receive downlink data sent by the core network control plane function CN-CP to the remote terminal accessed through the relay terminal;

The fourth sending module 1404 is coupled to the seventh receiving module 1402 and configured to send downlink data to the remote terminal.

Through the device, the relay terminal can implement interaction between the control plane of the core network and the remote terminal, so that the core network control plane can initiate downlink data delivery to the remote terminal. Through the above solution, the network side implements all-round control of the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Optionally, the device further includes:

The eighth receiving module is configured to receive the paging request sent by the CN-CP, where the paging request carries the identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal includes at least one of the following information: the remote terminal Network identity, proximity of remote terminals Neighboring communication identifier;

The service request module is configured to initiate a service request process to the CN-CP in the case that the remote terminal is confirmed to be reachable.

Example 7

15 is a schematic structural diagram of Embodiment 7 of the present disclosure, which includes:

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

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

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

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

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

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

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

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

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

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

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

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

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

-RAN: eNodeB;

-CN-CP: MME;

-CN-UP: SGW, PGW;

-CN-SD: HSS;

-NG-Uu: LTE-Uu interface;

-NG2: the S1-AP interface;

-NG3: the S1-U interface;

-NG4: that is, the S11 interface;

16A and 16B are schematic diagrams of a control plane protocol stack according to Embodiment 7 of the present disclosure, wherein:

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

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

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

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

It can be seen from the protocol stack architecture shown in FIG. 16 that the architecture only affects the Remote UE, the Relay UE, and the CN-CP, and has no effect on the RAN.

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

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

Example eight

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

Figure 17 has the following steps:

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

S1702, the Remote UE discovers the Relay UE;

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

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

In this step, the Remote UE carries the user information (User Info) in the request, including the specific APN. According to the APN, the Relay UE needs to request the network to establish a corresponding PDN connection, and is used to provide relay communication for the Remote UE.

S1704. The Relay UE requests to establish a PDN connection for relaying to the network by using a specific APN.

S1705: The Relay UE allocates an IP address to the Remote UE, and the address is either a private Have an IPv4 address or an IPv6 prefix;

S1706: The Relay UE sends a remote terminal access report to the core network control plane function CN-CP, and carries information of the Remote UE, such as a remote terminal identifier, a Remote UE ID, and an IP address of the remote terminal.

S1707: The core network control plane function CN-CP sends a remote terminal access report to the core network user plane function CN-UP, and carries the information of the Remote UE;

In this solution, by default, the core network user plane function CN-UP obtains the information of the Remote UE, and performs the gate prohibition on the uplink and downlink data of the Remote UE, that is, the Remote UE is initially not allowed to initiate the uplink and downlink data.

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

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

In this step, the NAS authentication request sent by the Remote UE to the core network may be an independent NAS Authentication Request message, or may be an Attach Request message that does not establish a PDN connection.

In this step, the Remote UE may carry the NAS authentication information in the NAS authentication request, and may also carry the neighbor communication identifier.

The NAS authentication information includes the following information:

-Remote UE network identity, such as IMSI, IMEI, etc.;

- authentication parameters, such as authentication algorithms, etc.;

The ProSe UE ID is an identifier used by the Remote UE on the PC5 interface, for example, a Layer 2 ID of the Remote UE, and the like;

S1709: The Relay UE forwards the NAS authentication request of the Remote UE to the core network control plane function CN-CP;

In this step, the Relay UE forwards the NAS authentication request of the Remote UE to the CN-CP by:

An Uplink Generic NAS Transport message carrying a NAS authentication request of the Remote UE. Moreover, the service type of the uplink general-purpose NAS transmission message is set to: relay NAS authentication service. or,

The relay NAS authentication request message is a newly introduced message relative to the related art.

In this step, as a preferred implementation manner, the Relay UE may also send relay access information to the CN-CP, where the relay access information is one or a combination of the following information:

a relay access indication (Relay indication) indicating that the Remote UE is currently accessed through a relay UE (Relay UE);

- the identity of the relay terminal (Relay UE ID);

S1710: The CN-CP obtains the subscription data of the terminal from the core network subscription database CN-SD;

S1711-S1712, the CN-CP sends an authentication challenge to the Remote UE, and the authentication challenge is forwarded to the Remote UE by the Relay UE;

S1713~S1714, the Remote UE calculates an authentication challenge response, and sends an authentication challenge response to the CN-CP, and the authentication challenge response is forwarded to the CN-CP by the Relay UE;

S1715. The core network control plane function CN-CP returns a relay NAS authentication response to the Relay UE.

In this step, the core network control plane function CN-CP sends a NAS authentication response to the Relay UE in the following manner:

Downlink Generic NAS Transport message, and set the type of the message to: relay NAS authentication message. or,

The relay NAS authentication response message is a newly introduced message relative to the related art.

In this step, the NAS authentication response includes the following information: the authentication result, and the temporary identifier assigned by the CN-CP to the Remote UE.

In this step, as a preferred implementation manner, when the core network control plane function CN-CP sends a NAS authentication response to the Relay UE, the following information may also be sent to the Relay UE:

- the identity of the remote terminal, the Remote UE ID, which may comprise at least one of the following: far The network identity of the terminal (such as IMSI), the proximity communication identifier of the remote terminal. Based on the identity of the remote terminal, the Remote UE sends the NAS authentication response to the correct Remote UE.

S1716: After receiving the relay NAS authentication response of the CN-CP, the Relay node returns a NAS authentication response to the Remote UE through the PC5 signaling message on the PC5 interface.

S1717: After the authentication succeeds, the CN-CP stores the user context of the Remote UE.

In this step, the CN-CP stores the user context of the Remote UE, including a combination of the following information:

Remote UE information, such as the network identity of the Remote UE (IMSI, IMEI), the IP address of the Remote UE, etc.

Authentication information, such as an authentication vector, an authentication result, etc.;

The neighbor communication identifier of the remote terminal, for example, the Layer 2 ID of the Remote UE, etc.;

Relay access information, such as a relay access indication (Relay indication), a relay terminal identifier (Relay UE ID, such as IMSI), an IP address of a Relay UE, and the like;

If the relay UE ID is not carried in the NAS authentication request of the Remote UE, the CN-CP obtains the Relay UE ID according to the context of the Relay UE.

As a preferred implementation manner, the CN-CP may store the following information in the context of the Relay UE:

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

S1718: The CN-CP sends a notification message to the CN-UP, and carries the information of the Remote UE.

In this step, the information of the Remote UE carried includes: the ID of the Remote UE, the IP of the Remote UE, and whether the authentication is passed.

After receiving the information of the Remote UE, the CN-UP controls the remote device to control the context data transmission according to whether the Remote UE passes the authentication. For example, only when Remote UE authentication When passing, the uplink and downlink data transmission of the Remote UE is allowed, otherwise the uplink and downlink data transmission of the Remote UE is prohibited.

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

It should be noted that in the flow shown in FIG. 17, steps S1708 to S1717 may occur before steps S1703 to S1707. At this time, since steps S1706 to S1707 are executed, step S1717 is not required.

Example nine

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

Compared with the flow shown in Figure 17, the flow shown in Figure 18 has the following differences:

- on the PC5 interface, in steps S1808, S1812, S1813, S1816, using the PC5 user plane (ie PC5 data packet) between the Remote UE and the Relay UE to transmit the NAS signaling of the Remote UE;

- steps S1803 - S1807 must be performed before steps S1808 - S1818;

- Steps S1806 to S1807 are not essential, and if step S1818 is performed, S1806 and S1807 may be omitted.

Example ten

Figure 19 has the following steps:

S1901, the Relay UE is attached to the network;

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

S1903, the Relay UE enters an idle state;

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

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

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

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

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

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

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

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

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

Embodiment 11

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

Figure 20 has the following steps:

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

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

S2003, if the Remote UE is currently in an idle state, the CN-CP initiates a paging procedure;

In this step, the CN-CP determines that it needs to go to the Remote UE according to the SMS delivery request message. A paging is initiated, and according to the context of the Remote UE, it is determined that the Remote UE is accessed by the Relay UE, and the CN-CP initiates a paging request, carrying the identifier of the Relay UE and the identifier of the Remote UE. The identifier of the Remote UE may be one or a combination of the following: a network identity (IMSI) of the Remote UE, and a neighbor communication identifier of the Remote UE (such as a layer 2 identifier Layer 2 ID of the Remote UE on the PC5 interface).

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

As a preferred embodiment, in this step, according to the decision of the CN-CP in S2003, the paging request further carries the identifier of the Remote UE.

S2005: The RAN sends a paging request to the Relay UE, and carries the identifier of the Relay UE and the identifier of the Remote UE.

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

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

S2007, 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;

S2008, since the Remote UE accesses the network via the Relay UE, the CN-CP determines that the SMS delivery should be initiated to the Relay UE;

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

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

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

Relay SMS delivery messages, which are new incoming messages relative to related technologies.

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

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

S2011, on the PC5 interface, the Remote UE returns an SMS delivery response to the Relay UE.

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

S2013, the CN-CP returns an SMS delivery response to the SM-SC;

S2014, the SM-SC returns an SMS delivery response to the AS.

Example twelve

Figure 21 has the following steps:

S2101, the Relay UE is attached to the network;

S2102, as shown in Figure 17, the Remote UE discovers the Relay UE and accesses the network through the Relay UE.

S2103, as shown in Figure 19, the Relay UE and the Remote UE enter an idle state;

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

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

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

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

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

In this step, the CN-CP determines, according to the information in the downlink data notification request, whether the terminal to be paged is only paging the Relay UE or paging the Relay UE and the Remote UE:

- If it is determined that only the Relay UE is paged according to the information in the downlink data notification, the CN-CP carries only the identifier of the Relay UE in the paging request; or

- If it is determined that the Remote UE needs to be paged according to the information in the downlink data notification request, the CN-CP carries the identifier of the Relay UE and the identifier of the Remote UE in the paging request. The identifier of the Remote UE may be one or a combination of the following: a network identity (IMSI) of the Remote UE, and a neighbor communication identifier of the Remote UE (such as a layer 2 identifier Layer 2 ID of the Remote UE on the PC5 interface).

The CN-CP can notify the terminal in the request by using the downlink data to notify the information in the request, such as the bearer identifier. The bearer identifier can be used to obtain the corresponding bearer, and obtain the IP address corresponding to the bearer, and determine whether the IP address is used by the Relay UE or used by the Remote UE, and the CN-CP can determine the terminal that should be paged, thereby searching for The call request carries the corresponding terminal identifier.

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

As a preferred implementation manner, in this step, according to the decision of the CN-CP in S2107, the paging request further carries the identifier of the Remote UE.

S2109: The RAN sends a paging request to the Relay UE, and carries the identifier of the Relay UE and the identifier of the Remote UE.

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

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

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

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

Through the solution of the embodiment of the present disclosure, the remote terminal can implement interaction with the control plane of the core network through the relay of the relay terminal to complete the authentication process, and the control plane of the core network implements interaction with the remote terminal through the relay terminal, which can be implemented. The authentication of the remote terminal can also initiate downlink data delivery to the remote terminal. At the same time, the control plane of the core network can also complete the switching of the state of the remote terminal in real time, and put the remote terminal into an idle state. Through the above solution, the network side implements all-round control on the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

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

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

Industrial applicability

Through the solution of some embodiments of the present disclosure, the remote terminal can relay through the relay terminal. The interaction with the control plane of the core network is implemented, and the authentication process is completed. The control plane of the core network implements interaction with the remote terminal through the relay terminal, which can implement authentication of the remote terminal, and can also initiate downlink data delivery to the remote terminal. The core network control plane can also complete the switching of the state of the remote terminal in real time, and put the remote terminal into an idle state. Through the above solution, the network side implements all-round control on the remote terminal, and when the remote terminal accesses the network through the relay terminal, the network can sense and control the remote terminal.

Claims

A terminal authentication method includes:

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

The remote terminal receives a NAS authentication response returned by the CN-CP through the relay terminal.
The method of claim 1 wherein

The sending, by the remote terminal, the NAS authentication request to the CN-CP by using the relay terminal, includes:

Transmitting, by the remote terminal, the NAS authentication request to the relay terminal by using a PC5 signaling message or a PC5 data packet;

Receiving, by the remote terminal, the NAS authentication response returned by the CN-CP through the relay terminal includes:

The remote terminal receives the NAS authentication response sent by the relay terminal to the relay terminal using a PC5 signaling message or a PC5 data packet.
The method according to claim 1 or 2, wherein the NAS authentication request sent by the remote terminal comprises:

The network identity and authentication parameters of the remote terminal.
The method according to claim 1 or 3, wherein the NAS authentication request sent by the remote terminal comprises:

The neighbor communication identifier of the remote terminal.
The method of claim 1 or 2, wherein the NAS authentication response comprises:

The authentication result and the temporary identifier assigned by the CN-CP to the remote terminal.
The method according to any one of claims 1 to 5, wherein after the remote terminal sends the NAS authentication request to the CN-CP by forwarding by the relay terminal, the method further includes:

Receiving, by the remote terminal, an authentication challenge request sent by the CN-CP to the remote terminal by using the relay terminal;

The remote terminal calculates an authentication challenge response, and sends the authentication challenge response to the CN-CP by forwarding by the relay terminal.
A terminal authentication method includes:

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

Transmitting, by the relay terminal, the NAS authentication request to a core network control plane function CN-CP;

The relay terminal receives a NAS authentication response from the CN-CP;

The relay terminal forwards the NAS authentication response to the remote terminal.
The method of claim 7 wherein

Receiving, by the relay terminal, the NAS authentication request from the remote terminal includes:

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

Forwarding, by the relay terminal, the NAS authentication response to the remote terminal includes:

The relay terminal transmits the NAS authentication response to the remote terminal using a PC5 signaling message or a PC5 data packet.
The method of claim 7, wherein the relaying the terminal to the CN-CP to forward the NAS authentication request comprises:

The relay terminal sends an uplink general-purpose NAS transmission message to the CN-CP, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates that the service type is a relay NAS authentication service; or,

The relay terminal sends a relay NAS authentication request message to the CN-CP, where the relay NAS authentication request message carries the NAS authentication request.
A method according to any one of claims 7 to 9, further comprising:

The relay terminal sends relay access information to the CN-CP, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, an identifier of the relay terminal Relay UE ID.
The method of claim 7, wherein the receiving, by the relay terminal, the NAS authentication response from the CN-CP comprises:

The relay terminal receives a downlink general NAS transmission message from the CN-CP, where the downlink general NAS transmission message carries the NAS authentication response, and the downlink general NAS transmission message indicates that the service type is medium Following the NAS authentication business;

The relay terminal receives a relay NAS authentication response message from the CN-CP, wherein the relay NAS authentication response message carries the NAS authentication response.
The method of claim 7 or 11, wherein the NAS authentication response comprises:

The authentication result and the temporary identifier assigned by the CN-CP to the remote terminal.
The method of claim 7 or 11 or 12, further comprising:

The relay terminal receives the identifier Remote UE ID of the remote terminal from the CN-CP, where the identifier of the remote terminal, the Remote UE ID, includes at least one of the following: a network identity of the remote terminal, The neighbor communication identifier of the remote terminal.
The method according to claim 7 or 13, wherein the forwarding of the NAS authentication response by the relay terminal to the remote terminal comprises:

The relay terminal points to the farther according to the identifier of the remote terminal, the Remote UE ID The terminal terminal forwards the NAS authentication response.
The method according to any one of claims 7 to 14, wherein after the relay terminal forwards the NAS authentication request to the core network control plane function CN-CP, the method further includes:

Receiving, by the relay terminal, an authentication challenge sent by the CN-CP;

The relay terminal forwards the authentication challenge to the remote terminal;

Receiving, by the relay terminal, an authentication challenge response sent by the remote terminal in response to the authentication challenge;

The relay terminal forwards the authentication challenge response to the CN-CP.
A terminal authentication method includes:

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

The CN-CP authenticates the remote terminal to generate a NAS authentication response;

The CN-CP returns the NAS authentication response to the remote terminal by forwarding by the relay terminal.
The method of claim 16, wherein the receiving, by the CN-CP, the NAS authentication request sent by the remote terminal by using the relay terminal comprises:

The CN-CP receives an uplink general-purpose NAS transmission message sent by the relay terminal, where the uplink general-purpose NAS transmission message carries the NAS authentication request, and the uplink general-purpose NAS transmission message indicates that the service type is medium Following the NAS authentication business; or,

The CN-CP receives a relay NAS authentication request message sent by the relay terminal, where the relay NAS authentication request message carries the NAS authentication request.
The method according to claim 16 or 17, wherein the NAS authentication request received by the CN-CP comprises:

The network identity and authentication parameters of the remote terminal.
The method according to claim 16 or 18, wherein the NAS authentication request received by the CN-CP comprises:

The neighbor communication identifier of the remote terminal.
The method of claim 16 or 18 or 19, further comprising:

The CN-CP receives the relay access information sent by the relay terminal, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and the relay terminal Identifies the Relay UE ID.
The method according to any one of claims 16 to 20, wherein after the CN-CP authenticates the remote terminal, the method further includes:

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

Remote terminal information, where the remote terminal information includes one or a combination of the following: an identifier of the remote terminal, a Remote UE ID, and an IP address of the remote terminal;

And relaying the access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID.
The method according to claim 21, wherein after the CN-CP authenticates the remote terminal, the method further includes:

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

The information of the remote terminal accessed by the relay terminal, wherein the information of the remote terminal accessed by the relay terminal includes one or a combination of the following information: an identifier of the remote terminal accessed by the relay terminal Remote UE ID, the IP address of the remote terminal accessed through the relay terminal.
The method according to claim 16, wherein the returning, by the CN-CP, the NAS authentication response to the remote terminal by forwarding of the relay terminal comprises:

The CN-CP sends a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries the NAS authentication response, and the downlink general NAS transmission message indicates that the service type is a relay NAS authentication service;

The CN-CP sends a relay NAS authentication response message to the relay terminal, where the relay NAS authentication response message carries the NAS authentication response.
The method of claim 16 or 23, wherein the NAS authentication response comprises:

The authentication result and the temporary identifier assigned by the CN-CP to the remote terminal.
A method according to claim 16, 23 or 24, further comprising:

The CN-CP sends the identifier of the remote terminal to the relay terminal, where the remote UE ID includes at least one of the following information: a network identity of the remote terminal, The neighbor communication identifier of the remote terminal.
The method according to any one of claims 16 to 25, wherein after the core network control plane function CN-CP receives the non-access stratum NAS authentication request sent by the remote terminal through the relay terminal, the method further includes:

Sending, by the relay terminal, the authentication challenge to the remote terminal by using the relay terminal;

The CN-CP receives an authentication challenge response returned by the remote terminal through the relay terminal.
The method according to any one of claims 16 to 26, wherein after the CN-CP authenticates the remote terminal, the method further includes:

Transmitting, by the CN-CP, remote terminal information to a core network user plane function CN-UP, where the remote terminal information includes one or a combination of the following information: an identifier of the remote terminal, a Remote UE ID, and an IP of the remote terminal. Address, whether the remote terminal is authenticated Information.
A terminal state switching method includes:

The core network control plane function CN-CP receives a connection release request from the wireless node RAN, wherein the connection release request is used to request to release the connection of the relay terminal;

The CN-CP releases the connection of the relay terminal, puts the relay terminal into an idle state, and places the remote terminal accessed through the relay terminal into an idle state.
The method according to claim 28, wherein the CN-CP puts the remote terminal accessed by the relay terminal into an idle state, including:

Determining, by the CN-CP, the remote terminal accessed by the relay terminal according to user context information of the relay terminal or user context information of the remote terminal;

The CN-CP places the determined remote terminal into an idle state.
The method of claim 29, wherein

The user context information of the relay terminal includes: information of a remote terminal accessed by the relay terminal; and the CN-CP determines, according to user context information of the relay terminal, access through the relay terminal. The remote terminal includes: the CN-CP searching for the remote terminal accessed by the relay terminal in user context information of the relay terminal;

and / or,

The user context information of the remote terminal includes: remote terminal information and relay access information; and determining, by the CN-CP, the remote terminal accessed by the relay terminal according to the user context information of the remote terminal includes: Determining, by the CN-CP, whether the remote terminal accesses via the relay terminal according to the relay access information in user context information of the remote terminal.
A downlink data delivery method includes:

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

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

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

Remote terminal information, where the remote terminal information includes one or a combination of the following: an identifier of the remote terminal, a Remote UE ID, and an IP address of the remote terminal;

And relaying the access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID.
The method according to claim 31, wherein, before the remote terminal is in an idle state, before the CN-CP sends the downlink data to the remote terminal by using the relay terminal, the method further includes:

The CN-CP initiates a paging request, where the paging request carries an identifier Relay UE ID of the relay terminal and an identifier of the remote terminal, a Remote UE ID, where the identifier of the remote terminal is a Remote UE. The ID includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.
The method of claim 31, wherein the transmitting, by the CN-CP, the downlink data to the remote terminal by using a relay terminal comprises:

The CN-CP sends the downlink data sent to the remote terminal to the relay terminal according to the relay access information of the remote terminal.
The method of claim 31, wherein the transmitting, by the CN-CP, the downlink data to the remote terminal by using a relay terminal comprises:

The CN-CP sends a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries the downlink data, and the downlink general NAS transmission message indicates that the service type is relay data delivery. Or,

The CN-CP sends a relay data delivery message to the relay terminal corresponding to the remote terminal, where the relay data delivery message carries the downlink data.
The method according to claim 35, wherein the downlink universal NAS transmission message or the relay data delivery message carries an identifier of the remote terminal, the Remote UE ID, wherein the identifier of the remote terminal, the Remote UE ID, includes the following At least one of the information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.
The method according to any one of claims 31 to 36, wherein the CN-CP determines that the downlink data is downlink data addressed to the remote terminal by at least one of:

In a case where the downlink data is short message service SMS information, the CN-CP determines, according to an SMS delivery request message, that the SMS information is sent to the remote terminal;

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 a downlink data notification request message from the core network user plane function CN-UP.
A downlink data delivery method includes:

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

The relay terminal sends the downlink data to the remote terminal.
The method according to claim 38, wherein before the receiving, by the relay terminal, the downlink data sent by the CN-CP to the remote terminal accessed by the relay terminal, the method further includes:

The relay terminal receives the paging request sent by the CN-CP, where the paging request carries the identifier of the remote terminal, the Remote UE ID, where the identifier of the remote terminal, the Remote UE ID, includes the following information. At least one of: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal;

The relay terminal initiates a service request procedure to the CN-CP if it is acknowledging that the remote terminal is reachable.
The method according to claim 38 or 39, wherein the transmitting, by the relay terminal, the downlink data to the remote terminal comprises:

The relay terminal transmits the downlink data to the remote terminal through a PC5 interface with the remote terminal.
A terminal authentication device is applied to a remote terminal, and the device includes:

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

The first receiving module is configured to receive a NAS authentication response returned by the CN-CP through the relay terminal.
The device according to claim 41, wherein the NAS authentication request sent by the first sending module comprises:

The network identity and authentication parameters of the remote terminal.
The device according to claim 41 or 42, wherein the NAS authentication request sent by the first sending module comprises:

The neighbor communication identifier of the remote terminal.
The apparatus of any one of claims 41 to 43, wherein the NAS authentication response comprises:

The authentication result and the temporary identifier assigned by the CN-CP to the remote terminal.
A terminal authentication device is applied to a relay terminal, and the device includes:

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

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

a third receiving module, configured to receive a NAS authentication response from the CN-CP;

And a second forwarding module, configured to forward the NAS authentication response to the remote terminal.
The apparatus according to claim 45, wherein the first forwarding module is further configured to send relay access information to the CN-CP, wherein the relay access information comprises one or a combination of the following information: The relay access indication Relay Indicator, the relay terminal ID of the relay terminal.
The apparatus of claim 45 wherein said NAS authentication response comprises:

The authentication result and the temporary identifier assigned by the CN-CP to the remote terminal.
The apparatus according to claim 45 or 47, wherein the third receiving module is further configured to:

Receiving an identifier of the remote terminal from the CN-CP, the remote UE ID, where the identifier of the remote terminal includes at least one of the following: a network identity of the remote terminal, and a remote terminal Neighboring communication logo.
The apparatus of claim 48, wherein the second forwarding module is configured to forward the NAS authentication response to the remote terminal based on an identifier Remote UE ID of the remote terminal.
A terminal authentication device is applied to a core network control plane function CN-CP, and the device includes:

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

An authentication module configured to authenticate the remote terminal to generate a NAS authentication response;

a second sending module, configured to forward to the remote terminal by the relay terminal The terminal returns the NAS authentication response.
The device according to claim 50, wherein the NAS authentication request received by the fourth receiving module comprises:

The network identity and authentication parameters of the remote terminal.
The device according to claim 50 or 51, wherein the NAS authentication request received by the fourth receiving module comprises:

The neighbor communication identifier of the remote terminal.
The apparatus according to claim 50 or 51 or 52, wherein the fourth receiving module is further configured to receive relay access information transmitted by the relay terminal, wherein the relay access information comprises the following information One or a combination: a relay access indication Relay Indicator, and an identifier Relay UE ID of the relay terminal.
The apparatus according to any one of claims 50 to 53, further comprising a first storage module, configured to store user context information of the remote terminal after the authentication module authenticates the remote terminal, wherein The user context information of the remote terminal includes:

Remote terminal information, where the remote terminal information includes one or a combination of the following: an identifier of the remote terminal, a Remote UE ID, and an IP address of the remote terminal;

And relaying the access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID.
The apparatus according to claim 54, wherein the first storage module is further configured to store user context information of the relay terminal after the remote terminal performs authentication, wherein a user of the relay terminal The context information includes:

The information of the remote terminal accessed by the relay terminal, wherein the information of the remote terminal accessed by the relay terminal includes one or a combination of the following information: an identifier of the remote terminal accessed by the relay terminal Remote UE ID, accessed through the relay terminal The IP address of the remote terminal.
The apparatus of claim 50 wherein said NAS authentication response comprises:

The result of the authentication and the temporary identification assigned to the remote terminal.
The apparatus according to claim 50 or 56, wherein the second transmitting module is further configured to send an identifier of the remote terminal, the Remote UE ID, to the relay terminal, wherein the identifier of the remote terminal is a Remote UE ID The method includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.
A terminal state switching device is applied to a core network control plane function CN-CP, and the device includes:

a fifth receiving module, configured to receive a connection release request from the wireless node RAN, where the connection release request is used to request to release the connection of the relay terminal;

Connecting a release module, configured to release a connection of the relay terminal;

The status setting module is configured to put the relay terminal into an idle state, and place the remote terminal accessed through the relay terminal into an idle state.
The apparatus of claim 58, wherein the state setting module comprises:

a determining unit, configured to determine, according to user context information of the relay terminal or user context information of the remote terminal, the remote terminal accessed by the relay terminal;

a status setting unit configured to put the determined remote terminal into an idle state.
The device according to claim 59, wherein

The user context information of the relay terminal includes: information of a remote terminal accessed by the relay terminal; the determining unit is configured to look up the user context information of the relay terminal by using the relay terminal The remote terminal that is entered;

and / or,

The user context information of the remote terminal includes: remote terminal information and relay access information; the determining unit is configured to determine the remote terminal according to the relay access information in the user context information of the remote terminal. Whether to access via the relay terminal.
A downlink data delivery device is applied to a core network control plane function CN-CP, and the device includes:

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

The third sending module is configured to send the downlink data to the remote terminal by using a relay terminal.
The apparatus of claim 61, further comprising a second storage module configured to store context information of the remote terminal, wherein the context information of the remote terminal comprises:

Remote terminal information, where the remote terminal information includes one or a combination of the following: an identifier of the remote terminal, a Remote UE ID, and an IP address of the remote terminal;

And relaying the access information, where the relay access information includes one or a combination of the following information: a relay access indication Relay Indicator, and an identifier of the relay terminal, a Relay UE ID.
The apparatus of claim 61, further comprising a paging module configured to transmit, at said third transmitting module, said remote terminal to said remote terminal via said relay terminal if said remote terminal is in an idle state Before the downlink data, a paging request is initiated, where the paging request carries an identifier Relay UE ID of the relay terminal and an identifier of the remote terminal, a Remote UE ID, where the identifier of the remote terminal is a Remote UE ID. The method includes at least one of the following: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.
The apparatus according to claim 61, wherein said third transmitting module is configured to send a destination to said relay terminal according to relay access information of said remote terminal The downlink data of the remote terminal.
The apparatus of claim 61, wherein the third transmitting module is configured to:

Sending a downlink general NAS transmission message to the relay terminal, where the downlink general NAS transmission message carries the downlink data, and the downlink general NAS transmission message indicates that the service type is relay data delivery; or

And transmitting, to the relay terminal corresponding to the remote terminal, a relay data delivery message, where the relay data delivery message carries the downlink data.
The apparatus according to claim 65, wherein the downlink universal NAS transmission message or the relay data delivery message carries an identifier of the remote terminal, the Remote UE ID, wherein the identifier of the remote terminal, the Remote UE ID, includes the following At least one of the information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal.
A downlink data delivery device is applied to a relay terminal, and the device includes:

The seventh receiving module is configured to receive downlink data sent by the core network control plane function CN-CP to the remote terminal accessed through the relay terminal;

The fourth sending module is configured to send the downlink data to the remote terminal.
The apparatus of claim 67, further comprising:

And an eighth receiving module, configured to receive a paging request sent by the CN-CP, where the paging request carries an identifier of the remote terminal, a Remote UE ID, where the identifier of the remote terminal includes: At least one of the following information: a network identity of the remote terminal, and a neighbor communication identifier of the remote terminal;

The service request module is configured to initiate a service request process to the CN-CP in the case of confirming that the remote terminal is reachable.