WO2018120225A1

WO2018120225A1 - Access method and apparatus

Info

Publication number: WO2018120225A1
Application number: PCT/CN2016/113960
Authority: WO
Inventors: 权威; 李秉肇; 张戬
Original assignee: 华为技术有限公司
Priority date: 2016-12-30
Filing date: 2016-12-30
Publication date: 2018-07-05

Abstract

An access method and apparatus. The access method comprises: a first core network device determines that a terminal that has been connected or attempts to connect the first core network device needs to be handed over to a second core network device, the first core network device and the second core network device communicate with the terminal by using a same access network device; and the first core network device sends a core network repositioning request message to the second core network device, the core network repositioning request message being used for instructing the second core network device to establish a connection with the terminal. In this way, the terminal can rapidly roll back to the second core network device, and establishes a service connection with the second core network device, thereby reducing the service failure probability and the service delay.

Description

Access method and device

Technical field

The present application relates to the field of communications technologies, and in particular, to an access method and apparatus.

Background technique

In the existing wireless communication field, the terminal only accesses the core network through a Radio Access Technology (RAT), such as a GSM EDGE Radio Access Network (GERAN) or Universal Mobile. A Universal Mobile Telecommunications System (UMTS) or Long Term Evolution (LTE), even including a future 5G access technology accessing the core network; or using multiple RATs to access the core network, such as LTE. And WIreless-Fidelity (WIFI) aggregation.

However, terminals usually only use the same core network. The terminal can only connect to the core network through a RAT. When the terminal needs to try to access a RAT, it may need to be handed over to another RAT. In this case, the access procedure between the terminal and another RAT needs to be re-established. For example, due to the core network (such as system overload), the core network can only reject the terminal. Then, the terminal may need to reselect a new RAT to access the core network, such as the terminal retreating from LTE to UMTS. When the terminal needs to switch from one RAT that has already been accessed to another RAT, it needs to be implemented through an internal RAT handover procedure.

One design of the future evolution of the wireless access technology is that the evolved LTE base station (e-eNB) can simultaneously connect to the LTE Evolved Packet Core (EPC) and the next generation core network (Next Generation Core). , Ng-core), to provide more services for future evolution of LTE networks. At the same time, the air interface technology can be backward compatible in the process of evolution, that is, the evolved LTE still supports traditional terminal access.

For the scenario where the access network device can connect to the EPC and the Ng-core at the same time, the terminal supporting the eLTE needs a new technology to avoid the service delay and improve the user experience when the terminal is connected or attempts to connect to the Ng-core.

Summary of the invention

The embodiment of the present application provides an access method and apparatus to avoid service delay.

In a first aspect, an access method is provided, where a first core network device determines that a terminal that has been connected to or attempts to connect to the first core network device needs to switch to a second core network device, where the first core network device and The second core network device uses the same access network device to communicate with the terminal; the first core network device sends a core network relocation request message to the second core network device, where the core network relocation request message is used. And indicating that the second core network device establishes a connection with the terminal through the access network device. Optionally, the core network relocation request message carries the information of the access network device identifier and/or the information of the terminal identifier.

With the above solution, if the terminal determines that the terminal needs to switch to the second core network device, the terminal directly sends the core network weight to the second core network device, if the terminal is connected to or attempts to connect to the first core network device. The positioning request message can be quickly accessed to the second core network device by the interaction with the second core network device, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

With reference to the first aspect, in a possible design, the first core network device receives an initial terminal message sent by the access network device, where the initial terminal message carries a message sent to the first core network device. Protocol Data Unit PDU for non-access stratum NAS. Optionally, the initial terminal message is used to indicate that the first core network device needs to establish a connection with the terminal.

With reference to the first aspect, in a possible design, the core network relocation request message further carries any one of the following information or a combination thereof: security key information; security algorithm information; the terminal has been established. Quality of service Qos information. Carrying the foregoing information may facilitate the direct connection between the second core network device and the terminal, thereby saving time.

The second aspect provides an access method, where the second core network device receives a core network relocation request message sent by the first core network device, where the core network relocation request message is used to indicate the second core network device and The terminal establishes a connection; the second core network device determines an access network device of the terminal according to the core network relocation request message; and the second core network device sends the access network to the access network The device sends an initial context setup request message, where the initial context setup request message is used to instruct the access network device to access the terminal to the second core network device; the first core network device and the first The two core network devices communicate with the terminal using the same access network device. Optionally, the core network relocation request message carries the information of the access network device identifier and/or the information of the terminal identifier.

After the core network device receives the core network relocation request message sent by the first core network device, the second core network device determines the access network device of the terminal, and rapidly establishes a connection with the terminal through the access network device, thereby If the terminal does not return to the idle state, the service connection is directly established with the second core network device, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

With reference to the second aspect, in a possible design, the initial context setup request message carries any combination of the QoS information and the backoff indication information of the service that the terminal has established, and the back indication information is used by Instructing the terminal to fall back to the second core network device. The QoS information of the service that has been established by the terminal is convenient for the terminal to establish a service connection with the second core network device, which saves time.

With reference to the second aspect, in a possible design, the second core network device sends a core network relocation complete message to the first core network device, where the core network relocation complete message is used to indicate completion to the The relocation process of the second core network device. In this way, the first core network device can determine that the terminal has accessed the second core network device, thereby releasing the bearer established for the terminal, and alleviating the load pressure of the first core network device.

A third aspect provides an access method, where an access network device receives a first message sent by a terminal, where the first message carries a protocol data unit of a non-access stratum NAS that is sent to the first core network device. PDU; Optionally, the first message indicates that the terminal has been connected to or attempts to connect to the first core network device. The access network device sends an initial terminal message to the first core network device, where the initial terminal message carries a PDU sent to the NAS layer of the first core network device; optionally, the initial terminal The message is used to indicate that the terminal needs to establish with the first core network device. connection. Receiving, by the access network device, an initial context request message sent by the second core network device, where the initial context setup request message is used to indicate that the access network device accesses the terminal to the second core network device; The access network device sends a second message to the terminal, where the second message is used to indicate that the terminal accesses the second core network device.

With the above solution, the access network device sends an access to the second terminal to the terminal after receiving the initial context request message sent by the second core network device, if the terminal has connected or attempts to connect to the first core network device. The indication message of the core network device can directly establish a connection with the second core network device when the terminal returns to the idle state, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

With reference to the third aspect, in a possible design, the first message is an RRC connection setup request message or an RRC connection setup complete message; and the second message is a security mode command message or an RRC connection reconfiguration message. The second message enables the terminal to quickly access the second core network device through the access network device. Further, because the fast access to the second core network device can improve the connection efficiency and save the connection time.

A fourth aspect provides an access method, where a terminal sends a first message to an access network device, where the first message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device. Optionally, the first message indicates that the terminal has been connected to or attempts to connect to the first core network device. Receiving, by the terminal, a second message sent by the access network device, where the second message is used to indicate that the terminal accesses the second core network device; and the terminal uses the access network device and the second core Network device communication.

When the service is not established between the terminal and the first core network device, the first core network device moves back to the second core network device through the interaction with the second core network device. Establishing a service with the terminal, the terminal first establishes a service with the first core network device, and returns to the second core network device without returning to the idle (IDLE) state, thereby effectively reducing the probability of failure of the service and reducing the service. Establishing a delay can also reduce signaling overhead.

In a fifth aspect, an access method is provided, where the first core network device determines that it has been connected or tried The terminal connected to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device communicate with the terminal using the same access network device; The core network device sends a core network relocation indication message to the terminal by using the access network device. Optionally, the core network relocation indication message is used to indicate that the terminal establishes a connection with the second core network device by using the access network device.

With the above solution, if the terminal determines that the terminal needs to switch to the second core network device, the terminal directly sends a core network relocation indication to the terminal, if the terminal is connected to or attempts to connect to the first core network device. The message, by the interaction with the terminal, enables the terminal to quickly access the second core network device, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

With reference to the fifth aspect, in a possible design, the first core network device receives an initial terminal message sent by the terminal, where the initial terminal message carries non-access information sent to the first core network device. Protocol Data Unit PDU of the layer NAS. Optionally, the initial terminal message is used to indicate that the terminal needs to establish a connection with the first core network device. At this time, the first core network NAS layer of the terminal is in a connected state.

The sixth aspect provides an access method, where the terminal receives a core network relocation indication message sent by the first core network device by using the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the a second core network device; the terminal generates a NAS message sent to the second core network device based on the core network relocation indication message;

Optionally, the core network relocation indication message carries the second core network device identification information, so that the terminal quickly connects to the second core network after receiving the core network relocation indication message. The device can quickly reduce the probability of service failure because the second core network device establishes a service bearer for the terminal because the device is quickly connected to the second core network device.

The terminal sends the NAS message to the access network device, and sends an initial terminal message to the second core network device by using the access network device, where the initial terminal message includes sending to the NAS message for the second core network device.

After the terminal receives the core network relocation indication message for instructing the terminal to access the second core network device, the terminal can generate the NAS message sent to the second core network device, and access the network through the access network. The device establishes a service connection with the second core network device, and the terminal does not need to return to the idle state to initiate an access process with the second core network device, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

With reference to the sixth aspect, in a possible design, the terminal sends the first indication information to the access network device before sending the initial terminal message to the second core network device by using the access network device, The first indication information is used to indicate that the access network device sends an initial terminal message to the second core network device, where the initial terminal message includes a NAS message sent to the second core network device.

With reference to the sixth aspect, in a possible design, the terminal sends, by using the access network device, the first core network device, to indicate that the terminal has the capability of accessing the second core network device. Second indication information. In this way, the first core network device can determine that the terminal supports access to the second core network device, and prevents the terminal from being unable to access the second core network device and causing service interruption.

With reference to the sixth aspect, in a possible design, the second indication information is an RRC connection setup request message or an RRC connection setup complete message or a NAS message.

When the service is not established between the terminal and the first core network device, the first core network device moves back to the second core network device and continues to establish with the terminal by interacting with the terminal. In the service, the terminal first establishes a service with the first core network device, and returns to the second core network device without returning to the idle (IDLE) state, which can effectively reduce the failure probability of the service and reduce the service establishment delay.

According to a seventh aspect, an access method is provided, where a first core network device determines that a terminal that has been connected to or attempts to connect to the first core network device needs to switch to a second core network device, where the first core network device and The second core network device uses the same access network device to communicate with the terminal; the first core network device sends a core network relocation indication message to the access network device, where the core network relocation indication message is used Instructing the terminal to access the second core network through the access network device device.

With the above solution, if the terminal determines that the terminal needs to switch to the second core network device, the terminal directly accesses the access network to the terminal, if the terminal is connected to or attempts to connect to the first core network device. The device sends a core network relocation indication message, and the terminal can quickly access the second core network device through the access network device by using the interaction with the access network device, thereby effectively reducing the service establishment delay. . Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Optionally, the core network relocation indication message includes indication information indicating that the terminal relocates to the second core network device device.

With reference to the seventh aspect, in a possible design, the first core network device receives the first core network device before determining that a terminal that has been connected to or attempts to connect to the first core network device needs to be handed over to the second core network device An initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit PDU of the non-access stratum NAS that is sent to the first core network device.

The eighth aspect provides an access method, where an access network device receives a core network relocation indication message for a terminal sent by a first core network device, where the access network device sends the core network relocation to the terminal And the indication message, the core network relocation indication message is used to indicate that the terminal accesses the second core network device by using the access network device.

Optionally, the core network relocation indication message includes indication information that indicates that the terminal relocates to the second core network device device.

With reference to the eighth aspect, in a possible design, after the core network relocation indication message is sent to the terminal, the access network device receives, by the terminal, the sending to the second core network device a non-access stratum NAS message, where the NAS message is generated by the terminal based on the core network relocation indication message; the access network device sends an initial terminal message to the second core network device, where the initial The terminal message carries a protocol data unit PDU that is sent to the NAS layer of the second core network device, where the initial terminal message is used to instruct the second core network device to send an initial context setup request message to the access network device. .

According to the above technical solution, when the service cannot be established between the terminal and the first core network device, The interaction between the core network device and the access network device accessed by the terminal causes the terminal to roll back and access the second core network device to continue to establish a service with the terminal, and the terminal first establishes a service with the first core network device. If the IDLE state is not returned, the service back delay can be effectively reduced by rolling back to the second core network device. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

A ninth aspect provides an access method, including: determining, by a first core network device, that a terminal cannot access the first core network device; and sending, by the first core network device, an indication message to the access network device, where The indication message is used to indicate that the terminal cannot access the first core network device.

In the above solution, if the first core network device determines that the terminal cannot access the first core network device and sends an indication message to the access network device, the terminal cannot access the terminal after the terminal is not connected to the first core network device. To the first core network device, this can prevent the terminal from continuing to access the first core network device for service interruption.

With reference to the ninth aspect, in a possible design, the indication information carries any type of terminal type information, service type information, radio access technology type information, and time information that cannot be accessed to the first core device. combination.

The tenth aspect provides an access method, where the access network device receives an indication message sent by the first core network device, where the indication message is used to indicate that the terminal cannot access the first core network device; Receiving, by the network device, a radio resource control RRC connection setup request message sent by the terminal, where the RRC connection setup request message carries a protocol data unit PDU of the non-access stratum NAS sent to the first core network device; The access network device sends an RRC connection setup message to the terminal, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device; the access network device receives the The RRC connection setup complete message sent by the terminal, where the RRC connection setup complete message carries the PDU of the NAS layer sent to the second core network device.

With the above solution, the access network device receives the indication message that the first core network device sends the indication that the terminal cannot access the first core network device, and if the RRC connection initiated by the terminal is received, the terminal directly connects the terminal. Entering the second core network device to prevent the terminal from continuing to access the first core If the network device fails to access the second core network device after the failure, the service establishment delay can be effectively reduced. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

In an eleventh aspect, an access method is provided, where a terminal sends a radio resource control RRC connection setup request message to an access network device when it has connected or attempts to connect to the first core network device, where the RRC connection setup request message is And carrying the RRC connection setup message sent by the access network device, where the RRC connection setup message carries an indication The terminal cannot access the indication message of the first core network device; the terminal sends an RRC connection setup complete message to the access network device, where the RRC connection setup complete message carries the message to the The PDU of the NAS layer of the second core network device is used to enable the terminal to access the second core network device.

When the service is not established between the terminal and the first core network device, the first core network device moves back to the second core through interaction with the access network device accessed by the terminal. The network device continues to establish a service with the terminal, and the terminal first establishes a service with the first core network device, and returns to the second core network device without returning to the idle (IDLE) state, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

According to a twelfth aspect, there is provided an access device having the function of implementing the behavior of the first core network device in any of the possible aspects of the first aspect and the first aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a thirteenth aspect, a core network device is provided, the core network device comprising a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the memory storage The program is to perform the method as described in any of the possible aspects of the first aspect and the first aspect described above.

In a fourteenth aspect, an access device is provided, the device having the functionality to implement the behavior of the second core network device in any of the possible aspects of the second aspect and the second aspect described above. The function can be passed The hardware implementation can also be implemented by hardware implementation of the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifteenth aspect, a core network device is provided, the structure of the core network device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the memory storage The program is to perform the method as described in any of the possible aspects of the second aspect and the second aspect described above.

In a sixteenth aspect, there is provided an access device having the functionality to implement the behavior of an access network device in any of the possible aspects of the third aspect and the third aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventeenth aspect, an access network device is provided, the structure of the access network device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the memory The stored program is to perform the method described in any of the possible designs of the third and third aspects above.

In an eighteenth aspect, there is provided an access device having a function of implementing terminal behavior in any of the possible aspects of the fourth aspect and the fourth aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

According to a nineteenth aspect, a terminal device is provided, the structure of the terminal device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke a program stored by the memory to The method described in any of the possible designs of the fourth and fourth aspects above is performed.

In a twentieth aspect, there is provided an access device having the function of implementing the behavior of the first core network device in any of the possible aspects of the fifth aspect and the fifth aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a twenty-first aspect, a core network device is provided, where the structure of the core network device includes a transceiver, a memory and a processor, wherein the memory is for storing a set of programs, the processor for calling the memory stored program to perform as described in any of the possible aspects of the fifth aspect and the fifth aspect above Methods.

According to a twenty-second aspect, there is provided an access device having a function of realizing terminal behavior in any of the possible aspects of the sixth aspect and the sixth aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a twenty-third aspect, a terminal device is provided, the structure of the terminal device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the program stored in the memory To perform the method as described in any of the possible aspects of the sixth aspect and the sixth aspect described above.

In a twenty-fourth aspect, there is provided an access device having the function of implementing the behavior of the first core network device in any of the possible aspects of the seventh aspect and the seventh aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a twenty-fifth aspect, a core network device is provided, the structure of the core network device comprising a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the memory storage The program is executed to perform the method described in any of the possible aspects of the seventh aspect and the seventh aspect described above.

In a twenty-sixth aspect, there is provided an access device having the function of implementing the behavior of an access network device in any of the possible aspects of the eighth aspect and the eighth aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

A twenty-seventh aspect, an access network device is provided, the structure of the access network device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the The memory stores the program to perform the method as described in any of the possible aspects of the eighth and eighth aspects above.

In a twenty-eighth aspect, there is provided an access device having the function of implementing the behavior of the first core network device in any of the possible aspects of the ninth and ninth aspects described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

According to a twenty-ninth aspect, a core network device is provided, the structure of the core network device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the memory storage The program is executed to perform the method as described in any of the possible aspects of the ninth and ninth aspects above.

In a thirtieth aspect, there is provided an access device having the function of implementing the behavior of an access network device in any of the possible aspects of the above tenth and tenth aspects. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a thirty-first aspect, an access network device is provided, the structure of the access network device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the The program stored in the memory is to perform the method described in any of the possible designs of the tenth and tenth aspects above.

According to a thirty-second aspect, there is provided an access device having a function of realizing terminal behavior in any of the possible designs of the eleventh and eleventh aspects described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

A thirty-third aspect, a terminal device is provided, the structure of the terminal device includes a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the program stored in the memory To perform the method described in any of the possible designs of the eleventh and eleventh aspects above.

A thirty-fourth aspect, a computer storage medium for storing computer software instructions for use in a terminal as described in the above aspects, comprising a program for performing the above aspects.

In a thirty-fifth aspect, a computer storage medium is provided for storage as described in the above aspect Computer software instructions for use with the first core network device, including programs designed to perform the above aspects.

In a thirty-sixth aspect, a computer storage medium is provided for storing computer software instructions for use in the first core network device of the above aspect, comprising a program designed to perform the above aspects.

A thirty-seventh aspect, a computer storage medium for storing computer software instructions for use in the first core network device of the above aspect, comprising a program designed to perform the above aspects.

It should be understood that the twenty-fourth to thirty-seventh aspects of the embodiments of the present application are consistent with the technical solutions of the first to twenty-third aspects of the embodiments of the present application, and the beneficial effects obtained by the aspects and the corresponding implementable design manners. Similar, no longer repeat them.

DRAWINGS

1A is a structural diagram of a communication system in an embodiment of the present application;

1B is a structural diagram of a 5G communication system in an embodiment of the present application;

2 is a schematic diagram of a protocol stack on a terminal side in the present application;

FIG. 3 is a schematic flowchart of an access method according to an embodiment of the present application;

4 is a schematic flowchart of an access method in an embodiment of the present application;

FIG. 5 is a schematic flowchart of an access method according to an embodiment of the present application;

FIG. 6 is a schematic flowchart of an access method according to an embodiment of the present application;

FIG. 7 is a schematic flowchart of an access method according to an embodiment of the present application;

FIG. 8 is a schematic flowchart of an access method according to an embodiment of the present application;

FIG. 9 is a schematic flowchart of an access method in an embodiment of the present application;

FIG. 10 is a schematic flowchart of an access method according to an embodiment of the present application;

FIG. 11 is a structural diagram of an access device according to an embodiment of the present application;

FIG. 12 is a structural diagram of a core network device according to an embodiment of the present application;

FIG. 13 is a structural diagram of an access device according to an embodiment of the present application;

FIG. 14 is a structural diagram of a core network device according to an embodiment of the present application;

FIG. 15 is a structural diagram of an access device according to an embodiment of the present application;

FIG. 16 is a structural diagram of an access network device according to an embodiment of the present application;

17 is a structural diagram of an access device in an embodiment of the present application;

FIG. 18 is a structural diagram of a terminal device according to an embodiment of the present application;

FIG. 19 is a structural diagram of an access device according to an embodiment of the present application;

20 is a structural diagram of a core network device in an embodiment of the present application;

FIG. 21 is a structural diagram of an access device according to an embodiment of the present application;

FIG. 22 is a structural diagram of a terminal device according to an embodiment of the present application;

FIG. 23 is a structural diagram of an access device according to an embodiment of the present application;

FIG. 24 is a structural diagram of a core network device according to an embodiment of the present application;

25 is a structural diagram of an access device in an embodiment of the present application;

FIG. 26 is a structural diagram of an access network device according to an embodiment of the present application;

Figure 27 is a structural diagram of an access device in an embodiment of the present application;

28 is a structural diagram of a core network device in an embodiment of the present application;

29 is a structural diagram of an access device in an embodiment of the present application;

FIG. 30 is a structural diagram of an access network device according to an embodiment of the present application;

Figure 31 is a structural diagram of an access device in an embodiment of the present application;

FIG. 32 is a structural diagram of a terminal device according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments.

As shown in FIG. 1A, which is a structural diagram of a communication system in an embodiment of the present application, the communication system includes a terminal, an access network device, a first core network device, and a second core network device, where the first core network device and The second core network device communicates with the terminal device using the same access network device.

The communication modes of the first core network device and the second core network device are different.

For example, the wireless communication system of the first core network device is a 5G system, and the wireless communication system of the second core network device is an LTE system;

For example, the wireless communication system of the first core network device is a 5G system, and the wireless communication system of the second core network device is a TD-SCDMA system;

For another example, the wireless communication system of the first core network device is a 5G system, and the wireless communication system of the second core network device is a GSM system.

The terminal is also called a user equipment (User Equipment, UE), and the wireless transceiver function can cooperate with the network device to provide a communication service for the user, which can be a wireless terminal, and the wireless terminal can provide voice and/or data connectivity to the user. Device, handheld device with wireless connectivity, or other processing device connected to a wireless modem. The wireless terminal can communicate with one or more core networks via a radio access network (eg, Radio Access Network, RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal The computers, for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. A wireless terminal may also be called a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, a Remote Station, an Access Point, and a Remote Terminal. (Remote Terminal), Access Terminal, User Terminal, User Agent, User Device, or User Equipment.

The access network device can connect with the UE, receive the UE data, and send the data to the core network device. The RAN corresponds to different devices in different systems, and the access network device may include a base station or a control base. A radio resource management device of the station, or a base station and a radio resource management device for controlling the base station. The base station may be a macro station or a small station, such as a small cell or a pico cell, and the base station may also be a home base station, such as a Home NodeB (HNB) or a Home evolved Node B. (Home eNodeB, HeNB), etc., the base station may also include a relay node or the like.

For example, for an LTE system such as TDD LTE, FDD LTE, or LTE-A, the access network device in the wireless communication system provided by the embodiment of the present application may be an evolved Node B (eNodeB), and the terminal may be a UE; The SCDMA system or the WCDMA system, the access network device in the wireless communication system provided by the embodiment of the present application may include: a Node B (NodeB) and/or a Radio Network Controller (RNC), and the terminal 102 may be a user. (User Equipment, UE); for the GSM system, the access network device provided by the embodiment of the present application may include a Base Transceiver Station (BTS) and/or a Base Station Controller (BSC); The terminal is a mobile station (MS); for the WiFi system, the access network device may include: an access point (AP) and/or an access controller (AC), and the terminal may be a station ( STAtion, STA); For the 5G communication system, there is no official name for the access network device in the 5G. In this paper, the 5G access network device is represented by e-eNB.

The core network device may be a device used in the core network after the access network device, and is generally connected to the access network device, and may be divided into multiple core network devices according to functions. In systems with different wireless access technologies, the names of devices with core network device functions may vary, for example, Serving GPRS Support Node (SGSN) in the 3G communication system, Gateway GPRS A Gateway GPRS Support Node (GGSN), such as a Mobility Management Entity (MME) and/or a Serving GateWay (S-GW) in 4G, has no official name in 5G. In this paper, the 5G core network device is called Ng-core.

It can be understood that the terminal identifier includes the identifier of the terminal in the second core network, and the identifier of the terminal in the first core network, and may only include one of the foregoing. For example, the terminal uses the identity in the second core network to communicate with devices in the second core network, such as the second core network device. Corresponding The security key information, the security algorithm information, and the QoS information also include corresponding information of the first core network or the second core network, respectively.

In the implementation of the present application, the communication system in the future is taken as an example, that is, the first core network device is an Ng-core in the 5G, the second core network device is an EPC in the LTE, and the access network device is a 5G access network. The device e-eNB is used as an example. In this case, the e-eNB can simultaneously connect the EPC of the LTE to the Ng-core of the communication system of the future evolved. The interface between the e-eNB and the EPC is called an S1 interface, and the e-eNB and the Ng- The interface between the cores is called the Ng1 interface. For details, see Figure 1B.

As the terminal can access the EPC of the LTE and the NG-core of the 5G through the e-eNB, the protocol stack of the terminal side can be referred to FIG. 2, where the upper layer of the 5G core network is called a new (new) non-connected. The upper layer (Non Access Stratum, NAS), the upper layer of the LTE core network is called LTE EPC.

Of course, the above names are only for convenience of presentation, and the above names may change during the subsequent standard evolution. But it does not affect the functional and logical relationship between the nodes.

As shown in the communication system shown in FIG. 1A, it can be seen that the access network device has a direct connection with the first core network device and the second core network device, and if the UE also passes the conventional handover process with the first core network device or When the second core network device communicates, it requires excessive processes, especially on the access network device. Specifically, when the terminal and the first core network device cannot establish a service, the terminal needs to return to the idle state first, and wait for a new opportunity to establish a connection with the second core network device, which may cause a large delay or even a service interruption. Various embodiments of the present application provide new solutions that overcome the above disadvantages.

As shown in FIG. 3, an access method includes:

The terminal establishes a connection with the first core network device through an access network device or attempts to establish a connection;

The access network device receives a first message sent by the terminal when it is connected to or attempts to connect to the first core network device; the first message carries a protocol data unit of the NAS layer that is sent to the first core network device (Protocol Data Unit, PDU);

Sending, by the access network device, an initial terminal message to the first core network device;

Optionally, the initial terminal message is used to indicate that the first core network device needs to establish a connection with the terminal, and the initial terminal message carries a PDU that is sent to the NAS layer of the first core network device;

When the first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, sends a core network relocation request message to the second core network device, where the core network relocation The request message is used to indicate that the second core network device establishes a connection with the terminal through the access network device.

Optionally, the core network relocation request message carries the information of the access network device identifier and/or the information of the terminal identifier.

Optionally, the core network relocation request message further includes any one of security key information, security algorithm information, and quality of service (Qos) information of the established service of the terminal or their combination.

Determining, by the second core network device, the access network device of the terminal according to the core network relocation request message;

The second core network device sends an initial context setup request message to the access network device, where the initial context setup request message is used to indicate that the terminal accesses the second core by using the access network device Network equipment;

Optionally, the initial context setup request message carries any combination of the QoS information and the fallback indication information of the service that has been established by the terminal, where the backoff indication information is used to indicate that the terminal falls back to The second core network device.

The access network device sends a second message to the terminal, where the second message is used to enable the terminal to access the second core network device.

After receiving the second message, the terminal uses the access network device to communicate with the second core network device.

On the premise that the terminal has accessed or attempts to access the first core network device, when the terminal cannot establish a service with the first core network device, the first core network device interacts with the second core network device. The terminal is rolled back and accessed to the second core network device to continue to establish a service with the terminal, and the terminal first establishes a service with the first core network device, and returns to the second in the middle without returning the idle (IDLE) state. The core network equipment can effectively reduce the service establishment delay. Further, because it is omitted A redundant process can also reduce signaling overhead. Further, because of the fast response, the probability of business failure can also be reduced.

Specifically, the first core network device is used as the 5G core network device, and the access method in FIG. 3 is applied to the network architecture shown in FIG. 2 . For the specific process, refer to FIG. 4 .

In step 41, the new NAS layer of the UE notifies the UE to establish a Radio Resource Control (RRC) connection. At this time, the new NAS and the EPC NAS of the UE are in the IDLE state, and the UE sends an RRC connection setup request message to the e-eNB.

Optionally, the message may carry the PDU of the new NAS;

Step 42: The e-eNB sends an RRC connection setup message to the UE, where the message is used to notify the UE to establish a signaling radio bearer 1 (SRB1).

Step 43: The UE sends an RRC connection setup complete message to the e-eNB. Optionally, the message may carry the PDU of the new NAS.

It should be noted that the PDU of the above new NAS may be carried in a message in step 41 or step 43, and may not be sent repeatedly.

Step 44: The e-eNB sends an initial UE message to the Ng-core, where the message carries the PDU of the new NAS.

Optionally, when the PDU of the new NAS is carried in step 41, step 44 may be placed after step 41, and may be interchanged with step 42, or step 43, for example, step 41->step 44->step 42->step 43. Or step 41->step 42->step 44->step 43, which is not limited in this application.

Step 45: The Ng-core determines that the UE needs to access the EPC, and sends a core network relocation request message to the EPC.

For example, Ng-core can consider that its load is too large to accept more terminals and confirm that the UE needs to access the EPC. Or Ng-core believes that the UE's service characteristics determine the use of EPC to complete more reasonable.

Optionally, the Ng-core may already be aware of the basic information of the EPC, or may be obtained by using a message sent by the e-eNB, which is not limited herein. According to the basic information of the EPC, the Ng-core can obtain routing information with the EPC.

Optionally, the core network relocation request message may carry one of the following information or a combination thereof: an identifier of the e-eNB, an identifier of the cell (such as ECGI), an identifier of the UE, and the like.

The identifier of the e-eNB is used to enable the EPC to determine the e-eNB to which the UE accesses, the identifier of the cell is used to enable the EPC and or the e-eNB to determine the cell to which the UE accesses, and the UE identifier is used to allow the EPC and the EPC. Or the e-eNB and or the Cell determine the UE. The UE identifier may be a temporary network identifier configured by the e-eNB for the UE, such as a (Cell Radio Network Temporary Identity, C-RNTI), or may be an identifier of the UE in Ng1, such as an e-eNB NG1AP ID.

Further, optionally, the core network relocation request message further carries security key information, and or security algorithm information, such as an integrity protection algorithm and an encryption algorithm. Carrying the security key information can facilitate the direct connection establishment of the core network and save time.

Optionally, the core network relocation request message carries QoS information of a service to be established or established by the UE. Specifically, the QoS information may be a parameter that is categorized by the New Core according to the UE, and is converted into a parameter indicating the QoS information in the LTE network, such as a QoS class identifier (QCI) and an address resolution protocol (ARP). And other parameters; or the QoS information may be sent by the Ng-core according to the service that the UE needs to establish, and sent to the EPC in the form of QoS information parameters in the 5G network, and then converted by the EPC into parameters representing the QoS information in the LTE network. There are no restrictions in this application.

Step 46: The EPC determines a serving e-eNB and a cell of the UE according to the core network relocation request message, and sends an initial context setup request message to the e-eNB.

Optionally, the EPC finds the corresponding e-eNB according to the identifier of the e-eNB in the relocation request message, and sends an initial context request message to the e-eNB.

Specifically, the initial context setup request message carries the service identifier and the service QoS information to be established or established by the UE.

Optionally, the initial context setup request message carries the backoff indication information, where the backoff indication information is used to indicate that the UE falls back to the LTE network or falls back to the EPC network.

Optionally, the EPC sends a core network relocation complete message to the Ng-core.

Step 47: After receiving the initial context setup request message sent by the EPC, the e-eNB sends a security mode command message and/or an RRC connection reconfiguration message to the UE.

Optionally, the security mode command message and the RRC connection reconfiguration message are sent by using a message of the LTE network.

Optionally, the security mode command message and the RRC connection reconfiguration message carry the backoff indication information, where the backoff indication information is used to indicate that the UE falls back to the LTE network or falls back to the EPC network.

Step 48: The UE receives the security mode message, activates the security, and receives the RRC connection reconfiguration message, performs SRB2, and establishes a Data Radio Bearer (DRB).

Optionally, you may need to reconfigure the previously created SRB1.

At this time, the RRC layer of the UE sends the backoff indication information to the EPC NAS layer, instructing the UE to fall back to the LTE network or fall back to the EPC network.

The subsequent EPC NAS layer continues to process other processes in this service until the end of the business. At this point, the EPC NAS layer is in the connected state.

Optionally, the RRC layer of the UE sends the fallback indication information to the new NAS layer, instructing the UE to fall back to the LTE network or fall back to the EPC network. Subsequent new NAS layers do not perform other processing in this service. At this point, New NAS returns to the IDLE state.

Optionally, the UE may continue to perform step 49 and step 410.

Step 49: The UE sends a security mode command completion message and/or an RRC connection reconfiguration complete message to the e-eNB.

In step 410, the e-eNB sends an initial context setup message to the EPC.

Through the foregoing embodiment, when the UE and the Ng-core have established services or need to establish services, but the Ng-core cannot perform service establishment, the UE quickly returns to the EPC without returning to the IDLE state, and directly If the UE is rejected, the UE returns to the idle state, and then re-establishes the service with the EPC, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Embodiments of the present application provide an access method. The method is applied to the communication system as shown in FIG. 1A. Unified. As shown in FIG. 5, the method includes:

The access network device receives a first message that is sent by the terminal when it is connected to or attempts to connect to the first core network device; the first message carries a PDU that is sent to the NAS layer of the first core network device;

Optionally, the terminal sends the first indication information to the access network device, where the first indication information is used to indicate that the access network device sends an initial terminal message to the first core network device.

The access network device sends an initial terminal message to the first core network device, where the initial terminal message carries a PDU sent to the NAS layer of the first core network device;

Optionally, the initial terminal message is used to indicate that the terminal needs to establish a connection with the first core network device.

Optionally, the terminal sends, by using the access network device, second indication information, to indicate, by the first core network device, that the terminal has the capability of accessing the second core network device;

Optionally, the second indication information may be carried by an RRC connection setup request message or an RRC connection setup complete message or a NAS message, which is not limited in the present invention.

When the first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, the core network relocation indication message is sent to the terminal by the access network device, where The core network relocation indication message is used to indicate that the terminal accesses the second core network device;

The core network relocation indication message includes indication information indicating that the terminal relocates to the second core network device.

Optionally, the terminal registers with the first core network device and the second core network device to obtain the first core network device and the foregoing before attempting to connect to the first core network device. The information of the second core network device is connected to the second core network device after receiving the core network relocation indication message. The specific registration method may be that the terminal sends a registration request message to the first core network device and the second core network device, respectively, to register, obtain information about the corresponding core network device, or the terminal The first core network device or the second core The heart network device sends a joint registration request message, and then one of the core network devices sends a message to another core network device to complete the joint registration of the terminal.

Optionally, the core network relocation indication message carries the second core network device identification information, so that the terminal connects to the second core network device after receiving the core network relocation indication message.

The terminal generates, according to the core network relocation indication message, a NAS message sent to the second core network device;

Transmitting, by the terminal, the NAS message to an access network device;

Sending, by the access network device, an initial terminal message to the second core network device;

The initial terminal message includes a NAS message sent to the second core network device.

The second core network device sends an initial context setup request message to the access network device according to the initial terminal message.

The initial context setup request message is used to indicate that the terminal accesses the second core network device by using the access network device.

On the premise that the terminal has accessed or attempts to access the first core network device, when the terminal cannot establish a service with the first core network device, the first core network device interacts with the terminal to make the terminal back. Retiring and accessing the second core network device to continue to establish a service with the terminal, the terminal first establishes a service with the first core network device, and returns to the second core network device without returning to the idle (IDLE) state. Can effectively reduce the business establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Specifically, the access method in FIG. 5 is applied to the network architecture shown in FIG. 2 by using a 5G communication system as an example. For the specific process, refer to FIG. 6 .

For the steps 61 to 64, refer to Step 41 to Step 44 in the foregoing embodiment, and details are not described herein again.

Step 65: The Ng-core determines that the Ue needs to access the EPC, and sends a core network relocation indication message to the UE.

The core network relocation indication message is used to indicate that the UE switches from accessing the Ng-core to accessing. EPC.

The core network relocation indication message is first sent to the e-eNB through the Ng1 interface, and the e-eNB forwards the message to the New NAS layer of the UE through the RRC message.

Step 66: The UE generates an EPC NAS message and sends the message to the e-eNB.

After receiving the core network relocation indication message, the UE's New NAS layer notifies the EPC NAS layer.

Specifically, the New NAS layer may directly notify the LTE NAS layer, or may notify the RRC layer first, and then notify the EPC NAS layer by the RRC layer, which is not limited in this application. At this point, the NEW NAS layer returns to the IDLE state.

The EPC NAS layer of the UE generates an EPC NAS message according to the notification message and sends it to the e-eNB.

Specifically, the EPC NAS message may be delivered to the UE RRC layer, and then sent by the RRC layer to the e-eNB; or the EPC NAS message is sent to the e-eNB in the form of a direct transmission message, which is not limited in this application.

Step 67: The e-eNB sends an initial UE message to the EPC, where the initial UE message carries the PDU of the EPC NAS layer.

Step 68: The EPC sends an initial context setup request message to the e-eNB according to the initial terminal message.

Step 69: After receiving the initial context setup request message sent by the EPC, the e-eNB sends a security mode command message and/or an RRC connection reconfiguration message to the UE.

Step 610: The UE receives the security mode message, activates the security, and receives the RRC connection reconfiguration message, performs SRB2, and establishes the DRB.

Optionally, you may need to reconfigure the previously created SRB1.

Optionally, the UE may continue to perform step 611 and step 612.

Step 611: The UE sends a security mode command completion message and/or an RRC connection reconfiguration complete message to the e-eNB.

At this time, the UE's EPC NAS is in the connected state.

In step 612, the e-eNB sends an initial context setup message to the EPC.

Embodiments of the present application provide an access method. The method is applied to a communication system as shown in FIG. 1A. As shown in FIG. 7, the method includes:

When the first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, sends a core network relocation indication message to the access network device, where the core network weight The location indication message is used to indicate that the terminal accesses the device through the access network device. Said second core network device;

After receiving the core network relocation indication message, the access network device sends the core network relocation indication message to the terminal;

Specifically, the core network relocation indication message is transparently transmitted to the terminal by using the access network device; or, by using a message between the first core network device and the access network, and between the access network device and the terminal The message was sent.

Transmitting, by the terminal, the NAS message to an access network device;

On the premise that the terminal has accessed or attempts to access the first core network device, when the terminal cannot establish a service with the first core network device, the first core network device accesses the access network device connected to the terminal. The interaction causes the terminal to roll back and access the second core network device to continue to establish a service with the terminal, and the terminal first establishes a service with the first core network device, and rolls back in the middle without returning the idle (IDLE) state. To the second core network device, the service establishment delay can be effectively reduced. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Specifically, the access method in FIG. 7 is applied to the network architecture shown in FIG. 2 by using a 5G communication system as an example. For the specific process, refer to FIG. 8.

For the steps 81 to 84, refer to Step 41 to Step 44 in the foregoing embodiment, and details are not described herein again.

Step 85: The Ng-core determines that the Ue needs to access the EPC, and sends a core network relocation indication message to the e-eNB.

The core network relocation indication message is used to indicate that the UE switches from accessing the Ng-core to accessing the EPC.

The core network relocation indication message is first sent to the e-eNB through the Ng1 interface.

Step 86: The e-eNB generates a core network relocation indication message and sends the message to the UE.

The core network relocation indication message is used to indicate that the UE switches from accessing the Ng-core to accessing the EPC, and the message is sent by using an RRC message.

In step 87, the UE generates an EPC NAS message and sends the message to the e-eNB.

After receiving the core network relocation indication message, the RRC layer of the UE notifies the EPC NAS layer to perform core network relocation.

Further, the RRC layer of the UE notifies the NEW NAS layer core network to relocate to the EPC, and the NEW NAS layer returns to the IDLE state after receiving the notification.

Step 88: The e-eNB sends an initial UE message to the EPC, where the initial UE message carries the PDU of the EPC NAS layer.

Step 89: The EPC sends an initial context setup request message to the e-eNB according to the initial terminal message.

Step 810: After receiving the initial context setup request message sent by the EPC, the e-eNB sends a security mode command message and/or an RRC connection reconfiguration message to the UE.

Step 811: The UE receives the security mode message, activates the security, and receives the RRC connection reconfiguration message, performs SRB2, and establishes the DRB.

Optionally, you may need to reconfigure the previously created SRB1.

Optionally, the UE may continue to perform step 812 and step 813.

Step 812: The UE sends a security mode command completion message and/or an RRC connection reconfiguration complete message to the e-eNB.

At this time, the UE's EPC NAS is in the connected state.

In step 813, the e-eNB sends an initial context setup message to the EPC.

Embodiments of the present application provide an access method. The method is applied to a communication system as shown in FIG. 1A. As shown in FIG. 9, the method includes:

When the first core network device determines that the terminal cannot access the first core network device, sends an indication message to the access network device, where the indication message is used to indicate that the terminal cannot access the first core network device. .

The indication information carries any combination of terminal type information, service type information, radio access technology type information, and time information that cannot be accessed to the first core device.

The terminal sends an RRC connection setup request message to the access network device when the terminal is connected to or attempts to connect to the first core network device, where the RRC connection setup request message carries the NAS sent to the first core network device. Layer PDU;

Optionally, the UE carries, in the RRC connection setup request message, indication information that supports the capability of accessing the second core network device.

And the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The terminal sends an RRC connection setup complete message to the access network device, where the RRC connection setup complete message carries the PDU of the NAS layer sent to the second core network device.

The access network device receives an RRC connection setup complete message sent by the terminal. Further, the process of accessing the device to the second core network is performed, and the present invention is not described again.

Optionally, in a possible implementation, the RRC connection setup request message does not carry the PDU of the NAS layer that sends the first core network device, and correspondingly, the RRC connection setup message does not carry the indication. The terminal cannot access the indication message of the first core network device, and correspondingly, the RRC connection setup complete message carries the PDU of the NAS layer that is sent to the first core network device.

Then, the access network device sends, to the terminal, an RRC message carrying an indication message indicating that the terminal cannot access the first core network device.

The terminal sends an RRC message carrying the PDU of the NAS layer sent to the second core network device to the access network device.

After the access network device receives the RRC message that is sent by the terminal to the PDU of the NAS layer that is sent to the second core network device, the process of accessing the second core network device is performed, and the application process is not described herein again. .

On the premise that the terminal has accessed or attempts to access the first core network device, when the terminal cannot establish a service with the first core network device, the first core network device accesses the access network device with the terminal. The interaction causes the terminal to fall back and access the second core network device to continue to establish a service with the terminal, and the terminal first establishes a service with the first core network device, and does not return to the idle (IDLE) state in the middle. Falling back to the second core network device can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Specifically, the access method in FIG. 9 is applied to the network architecture shown in FIG. 2 by using a 5G communication system as an example. For the specific process, refer to FIG. 10 .

Step 11: The Ng-core sends indication information to the e-eNB, where the indication information is used to indicate that the UE cannot access the Ng-core.

Optionally, before performing step 11, the Ng-core needs to determine that the terminal cannot access the Ng-core. For example, the Ng-core can consider that its own load is too large to accept more terminals, and confirm that the UE needs to be connected. Enter the EPC. Or Ng-core believes that the UE's service characteristics determine the use of EPC to complete more reasonable.

Specifically, the indication information may indicate that the Ng-core cannot be accessed, or a cause value indicating that the Ng-core cannot be accessed, such as an overload, or other cause value.

Optionally, the indication information may also carry a UE type, or a service type, or an access technology type, that cannot access the Ng-core.

Optionally, the indication information may also carry a time when the Ng-core cannot be accessed, that is, the UE cannot access the Ng-core for a period of time.

Step 12: The new NAS layer of the UE notifies the UE to establish an RRC connection.

At this time, the UE's new NAS and LTE NAS are both in the IDLE state.

In step 13, the UE sends an RRC connection setup request message to the e-eNB.

Optionally, the RRC connection setup request message may carry the PDU of the new NAS.

In step 14, the e-eNB sends an RRC connection setup message to the UE.

When the e-eNB determines that the UE cannot access the Ng-core according to the indication information obtained from the Ng-core, the RRC connection setup message carries the indication information obtained by the e-eNB from the Ng-core.

The RRC Connection Setup message is used to notify the UE to establish SRB1.

The RRC connection setup message carries a backoff indication that the UE falls back to the LTE EPC network or the EPC NAS.

Step 15: The UE sends an RRC Connection Setup Complete message to the e-eNB.

Optionally, the RRC connection setup complete message may carry the PDU of the EPC NAS.

With the above embodiment, when the UE cannot establish a service with the Ng-core, but the UE needs to establish a service with the Ng-core, the UE quickly returns to the EPC without returning to the IDLE state, and directly rejects the UE. The UE returns to the idle state, and then re-establishes the service with the EPC, which can effectively reduce the service establishment delay. Further, the signaling overhead can also be reduced because redundant processes are omitted. Further, because of the fast response, the probability of business failure can also be reduced.

Based on the foregoing method embodiments in FIG. 3 and FIG. 4, referring to FIG. 11, the embodiment of the present application further provides an access device 1100, which has the first method in the foregoing manner as shown in FIG. 3 and FIG. The function of the core network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is shown in FIG. 11. The device 1100 includes a transceiver unit 1101 and a processing unit 1102.

The processing unit 1102 is configured to determine that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device use the same access The network device communicates with the terminal;

The transceiver unit 1101 is configured to send a core network relocation request message to the second core network device, where the core network relocation request message is used to indicate that the second core network device passes the access network device and the The terminal establishes a connection.

Optionally, the transceiver unit 1101 is further configured to receive an initial terminal message sent by the access network device, where the initial terminal message carries a non-access stratum NAS that is sent to the first core network device. Protocol Data Unit PDU.

Optionally, the core network relocation request message further carries any one of the following information. Or their combination:

Security key information;

Security algorithm information;

The quality of service Qos information of the established service of the terminal.

Based on the same concept, as shown in FIG. 12, the embodiment of the present application further provides a core network device 1200. The structure of the device 1200 includes a transceiver 1201, a processor 1202, and a memory 1203. The memory 1203 is configured to store a set of programs. The processor 1202 is configured to invoke a program stored in the memory 1203 to perform the functions of the first core network device in the method shown in FIGS. 3 and 4.

Based on the foregoing method embodiments in FIG. 3 and FIG. 4, referring to FIG. 13, the embodiment of the present application further provides an access device 1300, which has the second method in the foregoing manner as shown in FIG. 3 and FIG. The function of the core network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is shown in FIG. 13, and the device 1300 includes a transceiver unit 1301 and a processing unit 1302.

The transceiver unit 1301 is configured to receive a core network relocation request message sent by the first core network device, where the core network relocation request message is used to indicate that the second core network device establishes a connection with the terminal.

The processing unit 1302 is configured to determine, according to the core network relocation request message, an access network device of the terminal;

The transceiver unit 1301 is further configured to send an initial context setup request message to the access network device, where the initial context setup request message is used to indicate that the terminal accesses the second core by using the access network device Network equipment;

The first core network device and the second core network device communicate with the terminal using the same access network device.

Optionally, the initial context setup request message carries any combination of the quality of service QoS information and the fallback indication information of the service that has been established by the terminal, where the backoff indication information is used. Instructing the terminal to fall back to the second core network device.

Optionally, the transceiver unit 1301 is further configured to:

Sending a core network relocation complete message to the first core network device, where the core network relocation complete message is used to indicate that the relocation process to the second core network device is completed.

Based on the same concept, as shown in FIG. 14, the embodiment of the present application further provides a core network device 1400. The structure of the device 1400 includes a transceiver 1401, a processor 1402, and a memory 1403. The memory 1403 is configured to store a set of programs. The processor 1402 is configured to invoke a program stored in the memory 1403 to perform the functions of the second core network device in the method shown in FIGS. 3 and 4.

Based on the foregoing method embodiments in FIG. 3 and FIG. 4, referring to FIG. 15, the embodiment of the present application further provides an access device 1500, which has access to the method shown in FIG. 3 and FIG. The function of network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 15. The device 1500 includes a transceiver unit 1501 and a processing unit 1502.

The processing unit 1502 is configured to generate an initial terminal message.

The transceiver unit 1501 is configured to receive a first message sent by the terminal when it is connected to or attempted to connect to the first core network device, where the first message carries a non-access layer sent to the first core network device. NAS protocol data unit PDU;

The transceiver unit 1501 is further configured to send an initial terminal message to the first core network device, where the initial terminal message carries a PDU sent to a NAS layer of the first core network device;

The transceiver unit 1501 is further configured to receive an initial context request message sent by the second core network device, where the initial context request message is used to notify the second core network device to notify the access network device to establish a service bearer for the terminal.

The transceiver unit 1501 is further configured to send a second message to the terminal, where the second message is used to enable the terminal to access the second core network device.

Optionally, the first message is an RRC connection setup request message or an RRC connection setup complete message; and the second message is a security mode command message or an RRC connection reconfiguration message.

Based on the same concept, as shown in FIG. 16, the embodiment of the present application further provides an access network device 1600. The structure of the device 1600 includes a transceiver 1601 for storing a set of programs, and a processor 1602 for calling a program stored in the memory 1603 to execute the method shown in FIG. 3 and FIG. The function of the access network device.

Based on the foregoing method embodiments in FIG. 3 and FIG. 4, referring to FIG. 17, the embodiment of the present application further provides an access device 1700, which has the terminal behavior in the method shown in FIG. 3 and FIG. The function. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 17, and the device 1700 includes a transceiver unit 1701 and a processing unit 1702.

The processing unit 1702 is configured to generate a first message.

The transceiver unit 1701 is configured to send a first message to the access network device, where the first message carries a protocol data unit PDU of the non-access stratum NAS that is sent to the first core network device;

The transceiver unit 1701 is configured to receive a second message sent by the access network device, where the second message is used to enable the terminal to access the second core network device.

The transceiver unit 1701 is further configured to communicate with the second core network device by using the access network device.

Optionally, the first message is used to indicate that the terminal is connected to or attempts to connect to the first core network device.

Based on the same concept, as shown in FIG. 18, the embodiment of the present application further provides a terminal device 1800. The structure of the device 1800 includes a transceiver 1801, a processor 1802, and a memory 1803. The memory 1803 is configured to store a set of programs and process The device 1802 is configured to call a program stored in the memory 1803 to perform the functions of the terminal in the method shown in FIGS. 3 and 4.

Based on the method embodiment in FIG. 5 and FIG. 6 above, referring to FIG. 19, the embodiment of the present application further provides an access device 1900, which has the first method in the foregoing manner as shown in FIG. 5 and FIG. The function of the core network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 19. The device 1900 includes a transceiver unit 1901 and a processing unit 1902.

The processing unit 1902 is configured to determine that the terminal device that has been connected to or attempts to connect to the first core network device The terminal needs to switch to the second core network device, where the first core network device and the second core network device use the same access network device to communicate with the terminal;

The transceiver unit 1901 is configured to send, by using the access network device, a core network relocation indication message to the terminal, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device.

Optionally, the transceiver unit 1901 is further configured to receive an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit of a non-access stratum NAS that is sent to the first core network device. PDU.

Based on the same concept, as shown in FIG. 20, the embodiment of the present application further provides a core network device 2000. The structure of the device 2000 includes a transceiver 2001, a processor 2002, and a memory 2003, where the memory 2003 is used to store a set of programs. The processor 2002 is configured to call a program stored in the memory 2003 to perform the functions of the first core network device in the method shown in FIGS. 5 and 6.

Based on the foregoing method embodiments in FIG. 5 and FIG. 6, referring to FIG. 21, the embodiment of the present application further provides an access device 2100, which has the terminal behavior in the method shown in FIG. 5 and FIG. The function. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 21. The device 2100 includes a transceiver unit 2101 and a processing unit 2102.

The transceiver unit 2101 is configured to receive a core network relocation indication message sent by the first core network device by using the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device ;

The processing unit 2102 is configured to generate, according to the core network relocation indication message, a non-access stratum NAS message sent to the second core network device.

The transceiver unit 2101 is further configured to send the NAS message to an access network device, and send, by using the access network device, an initial terminal message to the second core network device, where the initial terminal message is A NAS message sent to the second core network device is included.

Optionally, the transceiver unit 2101 is further configured to:

Sending, to the access network device, first indication information, where the first indication information is used to indicate the The access network device sends an initial terminal message to the second core network device.

Optionally, the transceiver unit 2101 is further configured to:

And transmitting, by the access network device, second indication information, to the first core network device, to indicate that the terminal has the capability of accessing the second core network device.

Optionally, the second indication information is an RRC connection setup request message or an RRC connection setup complete message or a NAS message.

Based on the same concept, as shown in FIG. 22, the embodiment of the present application further provides a terminal device 2200. The structure of the device 2200 includes a transceiver 2201, a processor 2202, and a memory 2203. The memory 2203 is configured to store a set of programs and process The processor 2202 is configured to call a program stored in the memory 2203 to perform the functions of the terminal in the method shown in FIGS. 5 and 6.

Based on the method embodiment in FIG. 7 and FIG. 8 above, referring to FIG. 23, the embodiment of the present application further provides an access device 2300, which has the first method in the foregoing manner as shown in FIG. 7 and FIG. The function of the core network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is shown in FIG. 23. The device 2300 includes a transceiver unit 2301 and a processing unit 2302.

The processing unit 2302 is configured to determine that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device use the same The access network device communicates with the terminal;

The transceiver unit 2301 is configured to send a core network relocation indication message to the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core by using the access network device Network equipment.

Optionally, the transceiver unit 2301 is further configured to receive an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit of a non-access stratum NAS that is sent to the first core network device. PDU.

Based on the same concept, as shown in FIG. 24, the embodiment of the present application further provides a core network device 2400. The structure of the device 2400 includes a transceiver 2401, a processor 2402, and a memory 2403. The memory 2403 is configured to store a set of programs. The processor 2402 is configured to call a program stored in the memory 2403 to The functions of the first core network device in the method shown in FIGS. 7 and 8 are performed.

Based on the foregoing method embodiments in FIG. 7 and FIG. 8 , referring to FIG. 25 , the embodiment of the present application further provides an access device 2500, which has access to the foregoing method as shown in FIG. 7 and FIG. 8 . The function of network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 25. The device 2500 includes a transceiver unit 2501 and a processing unit 2502.

The transceiver unit 2501 is configured to receive a core network relocation indication message for the terminal sent by the first core network device.

The processing unit 2502 is configured to determine, according to the core network relocation indication message, a terminal;

The transceiver unit 2501 is further configured to send the core network relocation indication message to the terminal, where the core network relocation indication message is used to indicate that the terminal accesses the Two core network equipment.

Optionally, the transceiver unit 2501 is further configured to:

Receiving, by the terminal, a non-access stratum NAS message sent to the second core network device, where the NAS message is generated by the terminal based on the core network relocation indication message;

Sending an initial terminal message to the second core network device, where the initial terminal message carries a protocol data unit PDU sent to a NAS layer of the second core network device, where the initial terminal message is used to indicate the second The core network device sends an initial context setup request message to the access network device.

Based on the same concept, as shown in FIG. 26, the embodiment of the present application further provides an access network device 2600. The structure of the device 2600 includes a transceiver 2601, a processor 2602, and a memory 2603. The memory 2603 is configured to store a set of programs. The processor 2602 is configured to call a program stored in the memory 2603 to perform the functions of the access network device in the method shown in FIGS. 7 and 8.

Based on the foregoing method embodiments in FIG. 9 and FIG. 10, referring to FIG. 27, the embodiment of the present application further provides an access device 2700, which has the first method in the foregoing manner as shown in FIG. 9 and FIG. The function of the core network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more of the above functions The module should be. One possible structure is as shown in FIG. 27. The device 2700 includes a transceiver unit 2701 and a processing unit 2702.

The processing unit 2702 is configured to determine that the terminal cannot access the first core network device.

The transceiver unit 2701 is configured to send an indication message to the access network device, where the indication message is used to indicate that the terminal cannot access the first core network device.

Optionally, the indication information carries any combination of terminal type information, service type information, radio access technology type information, and time information that cannot be accessed by the first core device.

Based on the same concept, as shown in FIG. 28, the embodiment of the present application further provides a core network device 2800. The structure of the device 2800 includes a transceiver 2801, a processor 2802, and a memory 2803. The memory 2803 is configured to store a set of programs. The processor 2802 is configured to call a program stored in the memory 2803 to perform the functions of the first core network device in the method shown in FIGS. 9 and 10.

Based on the foregoing method embodiment in FIG. 9 and FIG. 10, referring to FIG. 29, the embodiment of the present application further provides an access device 2900, which has the access method as shown in FIG. 9 and FIG. The function of network device behavior. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is as shown in FIG. 29, and the device 2900 includes a transceiver unit 2901 and a processing unit 2902.

The transceiver unit 2901 is configured to receive an indication message sent by the first core network device, where the indication message is used to indicate that the terminal cannot access the first core network device;

The transceiver unit 2901 is further configured to receive a radio resource control RRC connection setup request message sent by the terminal, where the RRC connection setup request message carries a non-access stratum NAS that is sent to the first core network device. Protocol data unit PDU;

The processing unit 2902 is configured to generate an RRC connection setup message.

The transceiver unit 2901 is further configured to send the RRC connection setup message to the terminal, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The transceiver unit 2901 is further configured to receive an RRC connection setup complete message sent by the terminal, where The RRC connection setup complete message carries a PDU that is sent to the NAS layer of the second core network device.

Based on the same concept, as shown in FIG. 30, the embodiment of the present application further provides an access network device 3000. The structure of the device 3000 includes a transceiver 3001, a processor 3002, and a memory 3003, where the memory 3003 is used to store a set of programs. The processor 3002 is configured to invoke a program stored in the memory 3003 to perform the functions of the access network device in the method shown in FIGS. 9 and 10.

Based on the foregoing method embodiments in FIG. 9 and FIG. 10, referring to FIG. 31, the embodiment of the present application further provides an access device 3100, which has the terminal behavior in the method shown in FIG. 9 and FIG. The function. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. One possible structure is shown in FIG. 31. The device 3100 includes a transceiver unit 3101 and a processing unit 3102.

The transceiver unit 3101 is configured to send a radio resource control RRC connection setup request message to the access network device when the terminal has been connected to or attempts to connect to the first core network device, where the RRC connection setup request message is carried and sent to the a protocol data unit PDU of the non-access stratum NAS of the first core network device;

The transceiver unit 3101 is further configured to receive an RRC connection setup message sent by the access network device, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device. ;

The processing unit 3102 is configured to generate an RRC connection setup complete message.

The transceiver unit 3101 is further configured to send the RRC connection setup complete message to the access network device, where the RRC connection setup complete message carries a PDU sent to the NAS layer of the second core network device, Used to enable the terminal to access the second core network device.

Based on the same concept, as shown in FIG. 32, the embodiment of the present application further provides a terminal device 3200. The structure of the device 3200 includes a transceiver 3201, a processor 3202, and a memory 3203. The memory 3203 is configured to store a set of programs and process The processor 3202 is configured to call a program stored in the memory 3203 to perform the functions of the terminal device in the method shown in FIGS. 9 and 10.

It should be noted that the connection between the parts shown in FIG. 11 to FIG. 32 is only one possible. For example, the transceiver and the memory are both connected to the processor, and there is no connection between the transceiver and the memory, or other possible connection manners. The processor may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP.

The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof. The above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.

The memory may include a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory). For example, flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory may also include a combination of the above types of memory.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by a program, and the program may be stored in a computer readable storage medium, which is non-transitory ( English: non-transitory) media, such as random access memory, read-only memory, flash memory, hard disk, solid state disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), CD (English: optical disc) And any combination thereof.

The present application is described with reference to the respective flowcharts and block diagrams of the method and apparatus of the embodiments of the present application. It will be understood that each flow and block of the flowchart illustrations. FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Implement one or more blocks in a process or multiple processes and block diagrams in the flowchart The device of the function specified in the box.

The foregoing is only an optional embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any change that can be easily conceived by those skilled in the art within the technical scope disclosed by the present application is not limited thereto. Or, replacement, should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of protection of the claims.

Claims

A first core network device, comprising:

a processing unit, configured to determine that a terminal that has been connected to or attempts to connect to the first core network device needs to switch to a second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

a transceiver unit, configured to send a core network relocation request message to the second core network device, where the core network relocation request message is used to indicate that the second core network device passes the access network device and the terminal establish connection.
The device according to claim 1, wherein the core network relocation request message carries information of the access network device identifier and/or information of the terminal identifier.
The device according to claim 1, wherein the transceiver unit is further configured to:

Receiving an initial terminal message sent by the access network device, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
The device according to any one of claims 1-3, wherein the core network relocation request message further carries any one of the following information or a combination thereof:

Security key information;

Security algorithm information;

The quality of service Qos information of the established service of the terminal.
A second core network device, comprising:

a transceiver unit, configured to receive a core network relocation request message sent by the first core network device, where the core network relocation request message is used to indicate that the second core network device establishes a connection with the terminal;

a processing unit, configured to determine, according to the core network relocation request message, an access network device of the terminal;

The transceiver unit is further configured to send an initial context setup request message to the access network device, where the initial context setup request message is used to instruct the access network device to access the terminal to the second core Network equipment;

The first core network device and the second core network device communicate with the terminal using the same access network device.
The device according to claim 5, wherein the core network relocation request message carries information of the access network device identifier and/or information of the terminal identifier.
The device according to claim 5, wherein the initial context setup request message carries any combination of quality of service QoS information and backoff indication information of the service that the terminal has established, and the fallback The indication information is used to indicate that the terminal falls back to the second core network device.
The device according to any one of claims 5-7, wherein the transceiver unit is further configured to:

Sending a core network relocation complete message to the first core network device, where the core network relocation complete message is used to indicate that the relocation process to the second core network device is completed.
An access network device, comprising:

a transceiver unit, configured to receive a first message sent by the terminal, where the first message carries a protocol data unit PDU of the non-access stratum NAS that is sent to the first core network device;

a processing unit, configured to generate an initial terminal message;

The transceiver unit is further configured to send the initial terminal message to the first core network device, where the initial terminal message carries a PDU sent to a NAS layer of the first core network device;

The transceiver unit is further configured to receive an initial context request message sent by the second core network device, where the initial context request message is used to notify the second core network device to notify the access network device to establish a service bearer for the terminal;

The processing unit is further configured to generate a second message;

The transceiver unit is further configured to send the second message to the terminal, where the second message is used to enable the terminal to access the second core network device.
The device according to claim 9, wherein the first message is used to indicate that the terminal has connected or attempts to connect to the first core network device.
The device according to claim 9, wherein said first message is an RRC connection Establishing a request message or an RRC connection setup complete message; the second message is a security mode command message or an RRC connection reconfiguration message.
A terminal, comprising:

a processing unit, configured to generate a first message;

a transceiver unit, configured to send the first message to an access network device; the first message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device;

The transceiver unit is further configured to receive a second message sent by the access network device, where the second message is used to indicate that the terminal accesses the second core network device;

The transceiver unit is further configured to communicate with the second core network device by using the access network device.
The terminal according to claim 12, wherein the first message is used to indicate that the terminal has connected or attempts to connect to the first core network device.
A first core network device, comprising:

a processing unit, configured to determine that a terminal that has been connected to or attempts to connect to the first core network device needs to switch to a second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

And a transceiver unit, configured to send, by the access network device, a core network relocation indication message to the terminal, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device.
The device according to claim 14, wherein the transceiver unit is further configured to:

Receiving an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
A terminal, comprising:

a transceiver unit, configured to receive a core network relocation indication message sent by the first core network device by using the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device;

a processing unit, configured to generate, according to the core network relocation indication message, a non-access stratum NAS message sent to the second core network device;

The transceiver unit is further configured to send the NAS message to an access network device, and send, by using the access network device, an initial terminal message to the second core network device, where the initial terminal message is included NAS message sent to the second core network device.
The terminal according to claim 16, wherein the transceiver unit is further configured to:

Sending the first indication information to the access network device, where the first indication information is used to instruct the access network device to send an initial terminal message to the second core network device.
The terminal according to claim 16 or 17, wherein the transceiver unit is further configured to:

And transmitting, by the access network device, second indication information, to the first core network device, to indicate that the terminal has the capability of accessing the second core network device.
The terminal of claim 18, comprising:

The second indication information is an RRC connection setup request message or an RRC connection setup complete message or a NAS message.
A first core network device, comprising:

a processing unit, configured to determine that a terminal that has been connected to or attempts to connect to the first core network device needs to switch to a second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

a transceiver unit, configured to send a core network relocation indication message to the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core network by using the access network device device.
The device according to claim 20, wherein the transceiver unit is further configured to:

Receiving an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
An access network device, comprising:

a transceiver unit, configured to receive a core network relocation indication message for the terminal sent by the first core network device;

a processing unit, configured to determine, according to the core network relocation indication message, a terminal;

The transceiver unit is further configured to send the core network relocation indication message to the terminal, where the core network relocation indication message is used to indicate that the terminal accesses the second by using the access network device Core network equipment.
The device according to claim 22, wherein the transceiver unit is further configured to:

Receiving, by the terminal, a non-access stratum NAS message sent to the second core network device, where the NAS message is generated by the terminal based on the core network relocation indication message;

Sending an initial terminal message to the second core network device, where the initial terminal message carries a protocol data unit PDU sent to a NAS layer of the second core network device, where the initial terminal message is used to indicate the second The core network device sends an initial context setup request message to the access network device.
A first core network device, comprising:

a processing unit, configured to determine that the terminal cannot access the first core network device;

The transceiver unit is configured to send an indication message to the access network device, where the indication message is used to indicate that the terminal cannot access the first core network device.
The device according to claim 23, wherein the indication information carries any type of terminal type information, service type information, radio access technology type information, and time information that cannot be accessed to the first core device. Combination.
An access network device, comprising:

a transceiver unit, configured to receive an indication message sent by the first core network device, where the indication message is used to indicate that the terminal cannot access the first core network device;

The transceiver unit is further configured to receive a radio resource control RRC connection setup request message sent by the terminal, where the RRC connection setup request message carries a protocol of a non-access stratum NAS sent to the first core network device. Data unit PDU;

a processing unit, configured to generate an RRC connection setup message;

The transceiver unit is further configured to send an RRC connection setup message to the terminal, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The transceiver unit is further configured to receive an RRC connection setup complete message sent by the terminal, where the RRC connection setup complete message carries a PDU that is sent to the NAS layer of the second core network device.
A terminal, comprising:

a processing unit, configured to send a radio resource control RRC connection setup request message to the access network device when the connection to the first core network device is connected, or the RRC connection setup request message is carried in the first a protocol data unit PDU of the non-access stratum NAS of the core network device;

a transceiver unit, configured to receive an RRC connection setup message sent by the access network device, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The transceiver unit is further configured to send an RRC connection setup complete message to the access network device, where the RRC connection setup complete message carries a PDU sent to the NAS layer of the second core network device, where The terminal accesses the second core network device.
An access method, comprising:

The first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

The first core network device sends a core network relocation request message to the second core network device, where the core network relocation request message is used to indicate that the second core network device passes the access network device and the The terminal establishes a connection.
The method according to claim 28, wherein the core network relocation request message carries information of the access network device identifier and/or information of the terminal identifier.
The method of claim 28, further comprising:

The first core network device receives an initial terminal message sent by the access network device, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
Method according to any of claims 28-30, characterized in that said core network is redefined The bit request message also carries any one of the following information or a combination of them:

Security key information;

Security algorithm information;

The quality of service Qos information of the established service of the terminal.
An access method, comprising:

Receiving, by the second core network device, a core network relocation request message sent by the first core network device, where the core network relocation request message is used to indicate that the second core network device establishes a connection with the terminal;

Determining, by the second core network device, the access network device of the terminal according to the core network relocation request message;

The second core network device sends an initial context setup request message to the access network device, where the initial context setup request message is used to instruct the access network device to access the terminal to the second core network. device;

The first core network device and the second core network device communicate with the terminal using the same access network device.
The method according to claim 32, wherein the core network relocation request message carries information of the access network device identifier and/or information of the terminal identifier.
The method according to claim 32, wherein the initial context setup request message carries any combination of quality of service QoS information and fallback indication information of the service that the terminal has established, and the fallback The indication information is used to indicate that the terminal falls back to the second core network device.
The method of any of claims 32-34, further comprising:

The second core network device sends a core network relocation complete message to the first core network device, where the core network relocation complete message is used to indicate that the relocation process to the second core network device is completed.
An access method, comprising:

The access network device receives the first message sent by the terminal; the first message carries a protocol data unit PDU of the non-access stratum NAS that is sent to the first core network device;

The access network device sends an initial terminal message to the first core network device, where the initial terminal message carries a PDU sent to the NAS layer of the first core network device;

The access network device receives an initial context request message sent by the second core network device, where the initial context request message is used to instruct the second core network device to notify the access network device to establish a service bearer for the terminal;

The access network device sends a second message to the terminal, where the second message is used to enable the terminal to access the second core network device.
The method of claim 36, wherein the first message is used to indicate that the terminal has connected or attempted to connect to the first core network device.
The method according to claim 36, wherein the first message is an RRC Connection Setup Request message or an RRC Connection Setup Complete message; and the second message is a Security Mode Command message or an RRC Connection Reconfiguration message.
An access method, comprising:

The terminal sends a first message to the access network device; the first message carries a protocol data unit PDU of the non-access stratum NAS that is sent to the first core network device;

Receiving, by the terminal, a second message sent by the access network device, where the second message is used to indicate that the terminal accesses the second core network device;

The terminal uses the access network device to communicate with the second core network device.
The method of claim 39, wherein the first message is used to indicate that the terminal has connected or attempted to connect to the first core network device.
An access method, comprising:

The first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

The first core network device sends a core network relocation indication message to the terminal by using the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device .
The method of claim 41, wherein the method further comprises:

The first core network device receives an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
An access method, comprising:

Receiving, by the terminal, a core network relocation indication message sent by the first core network device by using the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the second core network device;

The terminal generates a non-access stratum NAS message sent to the second core network device based on the core network relocation indication message;

The terminal sends the NAS message to the access network device, and sends an initial terminal message to the second core network device by using the access network device, where the initial terminal message includes sending to the NAS message for the second core network device.
The method of claim 43 wherein the method further comprises:

The terminal sends the first indication information to the access network device, where the first indication information is used to instruct the access network device to send an initial terminal message to the second core network device.
The method of claim 43 or 44, wherein the method further comprises:

And transmitting, by the access network device, the second indication information used by the terminal to the first core network device to indicate that the terminal has the capability of accessing the second core network device.
The method of claim 45, comprising:

The second indication information is an RRC connection setup request message or an RRC connection setup complete message or a NAS message.
An access method, comprising:

The first core network device determines that the terminal that has been connected to or attempts to connect to the first core network device needs to switch to the second core network device, where the first core network device and the second core network device use the same connection The network access device communicates with the terminal;

The first core network device sends a core network relocation indication message to the access network device, where the core network relocation indication message is used to indicate that the terminal accesses the Second core network device.
The method of claim 47, wherein the method further comprises:

The first core network device receives an initial terminal message sent by the terminal, where the initial terminal message carries a protocol data unit PDU of a non-access stratum NAS that is sent to the first core network device.
An access method, comprising:

Receiving, by the access network device, a core network relocation indication message sent by the first core network device for the terminal;

The access network device sends the core network relocation indication message to the terminal, where the core network relocation indication message is used to indicate that the terminal accesses the second core network through the access network device device.
The method of claim 49, wherein the method further comprises:

The access network device receives a non-access stratum NAS message sent by the terminal to the second core network device, where the NAS message is generated by the terminal based on the core network relocation indication message;

The access network device sends an initial terminal message to the second core network device, where the initial terminal message carries a protocol data unit PDU sent to the NAS layer of the second core network device, where the initial terminal message is used. And instructing the second core network device to send an initial context setup request message to the access network device.
An access method, comprising:

The first core network device determines that the terminal cannot access the first core network device;

The first core network device sends an indication message to the access network device, where the indication message is used to indicate that the terminal cannot access the first core network device.
The method according to claim 50, wherein the indication information carries any type of terminal type information, service type information, radio access technology type information, and time information that cannot be accessed to the first core device. Combination.
An access method, comprising:

Receiving, by the access network device, an indication message sent by the first core network device, where the indication message is used to indicate that the terminal cannot access the first core network device;

The access network device receives a radio resource control RRC connection setup request message sent by the terminal, where the RRC connection setup request message carries a protocol data unit of a non-access stratum NAS that is sent to the first core network device. PDU;

And the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The access network device receives an RRC connection setup complete message sent by the terminal, where the RRC connection setup complete message carries a PDU sent to the NAS layer of the second core network device.
An access method, comprising:

When the terminal is connected to or attempts to connect to the first core network device, the terminal sends a radio resource control RRC connection setup request message to the access network device, where the RRC connection setup request message carries the information sent to the first core network device. Protocol data unit PDU of the non-access stratum NAS;

Receiving, by the terminal, an RRC connection setup message sent by the access network device, where the RRC connection setup message carries an indication message indicating that the terminal cannot access the first core network device;

The terminal sends an RRC connection setup complete message to the access network device, where the RRC connection setup complete message carries a PDU of the NAS layer that is sent to the second core network device, and is used to enable the terminal to access the terminal. Go to the second core network device.