WO2018059401A1

WO2018059401A1 - Network switching method, device and system, and network access method and device

Info

Publication number: WO2018059401A1
Application number: PCT/CN2017/103504
Authority: WO
Inventors: 卢飞
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-09-30
Filing date: 2017-09-26
Publication date: 2018-04-05
Also published as: CN107889175A

Abstract

Provided are a network switching method, device and system, and a network access method and device. The network switching method comprises: when a user equipment (UE) moves from a first network to a second network, sending network switching information to a control plane entity of the second network, wherein the network switching information at least comprises a packet data network (PDN) type, an access point name (APN) and a service entity identifier corresponding to a service entity accessed by the UE, and the network switching information is used for indicating a service entity selected by the control plane entity of the second network to access, and the service entity comprises: an SCEF and an anchor point GW. By means of the present disclosure, the problem in the related art that a previous used service entity cannot be selected and data is interrupted or service continuity cannot be ensured caused by the fact that a UE uses the same APN is solved.

Description

Network switching method, device and system, network access method and device

Technical field

The present disclosure relates to the field of communications, and relates to a network switching method, device and system, network access method and device.

Background technique

Mobile communications have now evolved to the 4G phase. Compared with previous generations, the 4G network architecture is based on full IP transmission. Currently 3GPP is studying the 5G network architecture.

FIG. 1 is a structural diagram of interworking between a 4G network and a 5G network in the related art. The functions of each network element in the network architecture are as follows:

The terminal (User Equipment, UE for short) accesses the 4G network through the wireless air interface and obtains the service. The terminal exchanges information through the air interface and the base station, and moves through the non-access stratum (NAS) and the core network. Sexual management entity interaction information.

A radio access network (Radio Access Network, RAN for short) is responsible for air interface resource scheduling and air interface connection management of the terminal access network. In a 4G network, a base station is called an eNodeB, and in a 5G network, a base station carries an NG RAN.

Mobility Management Entity (MME): 4G core network control plane entity, which is mainly responsible for authentication, authorization and subscription checking of users to ensure users are legitimate users; user mobility management, including location registration and temporary identification Allocation; maintenance of IDLE and CONNECT status and state transition; switching in CONNECT state; public data network (Punlic Data Network, PDN) connection and bearer maintenance, including session management functions such as creation, modification and deletion; user IDLE status Trigger paging and other functions. In the 5G core network, the control plane entity may include multiple functions, mobility management functions, session management functions, authentication functions, and the like.

Serving GateWay (SGW): The functional entity of the core network user plane, which is mainly responsible for the interaction with the public data network gateway PGW in the case of roaming; Receive downlink packets for buffering and notify the MME to page users; user plane anchors across base stations and user plane anchors across 2G/3G/4G mobility.

Service Capability Exposure Function (SCEF): Its functions include non-IP data transmission authorization check, T6 connection management, and uplink and downlink non-IP data delivery.

Anchoring GW: It is the terminal accessing PDN network access point, responsible for allocating user IP address, network triggered bearer establishment, modification and deletion, and also having QoS control charging function, etc., which is user in 3GPP system and non-3GPP system. The anchor point is switched between, so that the IP address is kept unchanged and business continuity is guaranteed.

2 is a flow chart of a UE implementing network handover in the related art. Including the following steps:

Step 201: The UE sends an attach request message to the MME, where the attach request message carries a Globally Unique Temporary Identity (GUTI) or an International Mobile Subscriber Identification (IMSI); the message carries the PDN. The connection request, the PDN connection request message carries an Access Point Name (APN), a PDN type, and an initial access indication; the PDN type includes IPv4, IP v6, IPv4v6, and non-IP (non-IP);

Step 202: If the GUTI is carried in the step 201, the MME needs to obtain the user IMSI through the GUTI, and the MME sends a location update request message to the Home Subscriber Server (HSS), where the message carries the user IMSI, and the MME address

Step 203: The HSS returns a location confirmation message to the MME, where the message carries the subscription data of the user, including a default APN, and a default QoS.

In step 204, the MME selects the anchor GW to serve according to the PDN type and the APN in step 201. If the PDN type is a non-IP type, the MME may also select the SCEF to serve it; if the message in step 201 does not carry the APN, the MME Select the default APN as its service and select PGW or SCEF according to the default APN. If the MME selects the PGW, the MME sends a setup session request message to the PGW, where the message carries the user IMSI, the PDN type, the bearer ID, and the tunnel ID. If the MME selects the SCEF, the MME sends the message to the SCEF. The SCEF connection request message is set up, and the message carries the IMSI, the PDN type, and the MME identifier.

Step 205: The PGW returns a setup session response message to the MME, where the message carries an uplink PGW tunnel ID, and the SCEF returns a SCEF connection response message to the MME.

Step 206: The MME sends an attach accept message to the UE, where the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID, bearer QoS, and the like.

Step 207: The UE returns an attach complete message to the MME, where the message carries an active default bearer accept message.

Step 208, considering that the UE can move to the 5G system, the MME sends a notification request message to the HSS, where the message carries the selected anchor GW ID or SCEF ID, APN;

In step 209, the HSS returns a notification confirmation message to the MME.

Step 210: The UE enters an idle state in the 4G network, and the RAT selection and the cell selection may be selected to access the 5G network, and the UE sends an attach request message to the 5G CP, where the attach request message carries the GUTI allocated in the 4G system; Carrying a PDN connection request, the PDN connection request message carries an APN, a PDN type, and a handover access indication; the PDN type includes IPv4, IP v6, IPv4v6, and non-IP (non-IP);

Step 211: The 5G CP needs to obtain the user IMSI through the GUTI, and the 5G CP sends a location update request message to the HSS, where the message carries the user IMSI, and the 5G CP address

Step 212: The HSS returns a location confirmation message to the 5G CP, where the message carries the subscription data of the user, including the default APN, the default QoS, and the message also carries the anchor GW/SCEF ID and the APN that the UE has accessed.

Step 213: The MME selects the anchor GW or the SCEF in the step 212 to serve the service according to the APN, the handover indication in the step 210. If the MME selects the PGW, the MME sends a setup session request message to the PGW, where the message carries the user IMSI, the PDN. Type, bearer ID, and tunnel ID. If the MME selects the SCEF, the MME sends a SCEF connection request message to the SCEF, where the message carries the IMSI, the PDN type, and the MME identity.

Step 214: The PGW returns a session establishment response message to the MME, where the message carries the uplink. PGW tunnel ID; the SCEF returns a SCEF connection response message to the MME;

Step 215: The MME sends an attach accept message to the UE, where the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID, bears the QoS, and the like.

Step 216: The UE returns an attach complete message to the MME, where the message carries an active default bearer accept message.

When the UE uses the same APN and different types of PDN types, the MME may select different types of service entities (PGW or SCEF) for connection. For example, when the UE first requests an IP type PDN connection such as IPv4, IPv6, or IPv4v6, the MME selects the PGW to serve it. For interworking with the 5G system, the MME saves the APN and the PGW ID in the HSS; the UE requests the same APN. However, different types of PDNs are used for connection, and the MME selects SCEF for its service. In order to communicate with the 5G system, the MME saves the APN and the PGW ID in the HSS, but when the UE moves to the 5G system, the 5G CP cannot be based on Different PDN type selection service entities can only choose to serve according to the last saved APN, and the service entity chooses to serve the original service entity, which results in data interruption or business continuity cannot be guaranteed.

Summary of the invention

The embodiments of the present disclosure provide a network handover method, apparatus, and system, a network access method, and a device, to at least solve the related art, because the UE uses the same APN, and cannot select the service entity originally used, and cause data interruption or service continuity. Sexually unguaranteable issues.

According to an embodiment of the present disclosure, a network handover method is provided, including: transmitting, when a user equipment UE moves from a first network to a second network, network handover information to a control plane entity of the second network; The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the network switching information is used to indicate that the The control plane entity of the second network selects the accessed service entity, and the service entity includes: SCEF and anchor GW.

Optionally, the PDN type and the APN are used to determine a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate that the second network is in control The entity accesses the service entity corresponding to the specified service entity identifier.

Optionally, before the sending the network handover information to the second network control plane entity, the method further includes: receiving network handover information sent by the first network control plane entity.

Optionally, the PDN type includes at least the following types: an IP type and a non-IP type; and the IP type includes at least one of the following: IPv4, IPv6, or IPv4v6.

The control plane entity of the first network includes at least: a mobility control entity MME in a 4G system or a control plane entity in a 5G system, and the control plane entity of the second network at least includes: a mobility control entity MME in a 4G system or Control plane entities in 5G systems. Optionally, the control plane entity of the first network at least includes: a mobility control entity MME, where the control plane entity of the second network at least includes: the MME.

According to another embodiment of the present disclosure, a network access method is provided, including: acquiring network handover information sent by a server when a user equipment UE moves from a first network to a second network, where the network handover information Included in the packet data network PDN type, the access point name APN, and the service entity identifier corresponding to the service entity that the UE has accessed, the network handover information is used to indicate the control plane entity by the second network Selecting a service entity to be accessed, the service entity includes: an SCEF and an anchor GW; and selecting a service entity to perform access according to the network handover information.

Optionally, selecting the serving entity to perform access according to the network switching information, further comprising: determining, by using the PDN type and the APN, a specified service entity identifier, and accessing a service entity corresponding to the specified service entity identifier. .

Optionally, the server at least includes: a home subscription subscriber server HSS.

According to still another embodiment of the present disclosure, there is provided a network switching apparatus, a sending module, configured to send network switching information to a control of the second network when the user equipment UE moves from the first network to the second network The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the network switching information is used to indicate The service entity accessed by the control plane entity of the second network, the service entity includes: an SCEF and an anchor GW.

Optionally, the PDN type and the APN are used to determine a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate that the control plane entity of the second network accesses the specified service entity identifier The corresponding service entity.

Optionally, the device further includes: a receiving module, configured to receive network switching information sent by the first network control plane entity.

According to still another embodiment of the present disclosure, a network access apparatus is provided, including: a first acquiring module, configured to acquire network switching information sent by a server when a user equipment UE moves from a first network to a second network; a second obtaining module, configured to acquire PDN connection request information sent by the UE during the UE attaching process or the PDN connection establishing process; and the access module is configured to perform, according to the network switching information, the PDN connection request Information, the service entity is selected to be accessed; wherein the network handover information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, The PDN connection request information includes at least: the PDN type, the APN, the network handover information, and PDN connection request information used to indicate a service entity selected by the control plane entity of the second network, the service entity Including: SCEF and anchor GW.

Optionally, the access module is further configured to determine, by using the PDN type and the APN, a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate control of the second network The polygon entity accesses the service entity corresponding to the specified service entity identifier.

According to another embodiment of the present disclosure, a network switching system is provided, the system comprising: a server configured to send network switching information to the first when a user equipment UE moves from a first network to a second network a control plane entity of the network; wherein the network handover information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed; the service entity And including: an SCEF and an anchor GW; the control plane entity of the second network is configured to acquire network handover information sent by the server, and acquire the UE by using the UE during the UE attach process or the PDN connection establishment process. And sending the PDN connection request information, and selecting a service entity to perform access according to the network switching information and the PDN connection request information.

Optionally, the system further includes: a control plane entity of the first network, configured to send the network handover information to the server.

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

S1, when the user equipment UE is moved from the first network to the second network, sending network switching information to the control plane entity of the second network, where the network switching information includes at least a packet data network PDN type An in-point name APN and a service entity identifier corresponding to the service entity that the UE has accessed, the network handover information being used to indicate a service entity selected by the control plane entity of the second network, the service Entities include: SCEF and anchor GW.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

S2. Receive network switching information sent by the first network control plane entity.

S1. Acquire network switching information sent by the server when the user equipment UE moves from the first network to the second network.

S2. Acquire PDN connection request information sent by the UE during the UE attach process or the PDN connection establishment process.

S3. Select a service entity to perform access according to the network switching information and the PDN connection request information.

Through the present disclosure, since the information transmitted to the MME carries the PDN type, the APN, and the identifier corresponding to the accessed service entity, the HHS uses the information to access and use the information in the network handover process. The network service entity accesses before the handover, so that the related services cannot be selected due to the use of the same APN by the UE in the related art. The problem of the data and the interruption of the data or the continuity of the business cannot be guaranteed, thereby achieving the effect of ensuring the continuity of the service data when the UE uses the same APN.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the disclosure, and are intended to be a In the drawing:

1 is an architectural diagram of a 4G network and a 5G network interworking in the related art;

2 is a flowchart of a UE implementing network handover in the related art;

FIG. 3 is a flowchart of a network switching method according to an embodiment of the present disclosure; FIG.

4 is a flowchart of a network switching method according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of a UE switching from a 4G network to a 5G network according to an embodiment of the present disclosure; FIG.

6 is a flowchart of a UE switching from a 5G network to a 4G network according to an embodiment of the present disclosure;

FIG. 7 is a structural diagram of a network switching apparatus according to an embodiment of the present disclosure; FIG.

FIG. 8 is a structural diagram of a network switching apparatus according to an embodiment of the present disclosure; FIG.

9 is a structural diagram of a network switching system according to an embodiment of the present disclosure.

detailed description

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

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

Example 1

In this embodiment, a network switcher running in the network architecture shown in FIG. 1 is provided. law,

It should be noted that, in this embodiment, the handover between the 4G network and the 5G network of the UE can be implemented, that is, when the first network is a 4G network, the second network is a 5G network, and when the second network is a 5G network, A network is a 4G network. Of course, in this embodiment, switching between other network systems, such as switching between a 5G network and a 3G network, can also be implemented. Of course, 2G networks, wireless fidelity networks are also applicable. Therefore, the above idea of any technology, the network used to implement network switching should be considered within the scope of protection of this embodiment.

FIG. 3 is a flowchart of a network switching method according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps:

Step S302, when the user equipment UE moves from the first network to the second network, sending network switching information to the control plane entity of the second network;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the network switching information is used to indicate that The control plane entity of the second network selects the accessed service entity, and the service entity includes: SCEF and anchor GW.

The PDN type includes at least: an IP type and a non-IP type. Among them, IP types include: IPv4, IPv6, and IPv4v6.

Optionally, the APN and the PDN in the network switching information are used to determine a specified service entity identifier in the service entity identifier, where the specified entity identifier is used to indicate that the control plane entity of the second network accesses the service corresponding to the specified service entity identifier. entity.

Optionally, before sending the network handover information to the second network control plane entity, receiving, by the first network control plane entity, the network handover information sent during an attach procedure or a PDN connection setup process.

Through the above steps, the problem that the UE can not select the original service entity and the data interruption or the service continuity cannot be guaranteed due to the use of the same APN by the UE in the related art can be solved, thereby achieving the guarantee of the service data when the UE uses the same APN. The effect of continuity.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, portions of the technical solution of the present disclosure that contribute substantially or to the related art may be embodied in the form of a software product stored in a storage medium (eg, ROM/RAM, disk, optical disk). The instructions include a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

Example 2

In this embodiment, a network access method running in the network architecture shown in FIG. 1 is provided.

FIG. 4 is a flowchart of a network switching method according to an embodiment of the present disclosure. As shown in FIG. 4, the process includes the following steps:

Step S402: Acquire network switching information sent by the server when the user equipment UE moves from the first network to the second network.

Step S404: Acquire PDN connection request information sent by the UE in the process of the UE attaching or the PDN connection establishment process;

Step S406, selecting a service entity to perform access according to the network handover information and the PDN connection request information;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed. The PDN connection request information includes: the PDN type, the APN, the network handover information, and PDN connection request information used to indicate a service entity selected by a control plane entity of the second network, where Service entities include: SCEF and anchor GW.

Optionally, determining, according to the PDN type in the PDN connection request information, the APN, the PDN type in the network handover information, and the APN, determining, by the service entity that the UE has accessed The specified service entity identifier in the service entity identifier and access to the service entity corresponding to the specified service entity identifier.

The network handover information sent by the HSS to the MME includes a service entity identifier PGW ID corresponding to the IP type of the PDN, and also includes a service entity identifier SCEF ID corresponding to the non-IP type PDN. When the UE is in the IDLE state on the 4G network, and then sends an attach request to the MME in the 5G network, the UE also sends the APN corresponding to the attach request and the IP type in the PDN type to the MME. The MME compares the two types of information. Since the PDN of the IP type corresponds to the PGW ID, the MME selects the PGW ID from the service entity identifier for access instead of the SCEF ID.

Further, in the present disclosure, a scenario based on the above two embodiments is also provided to facilitate understanding of the technical solutions described in the embodiment.

scene 1:

The UE switches from the 4G network to the 5G network. FIG. 5 is a flowchart of a UE switching from a 4G network to a 5G network according to an embodiment of the present disclosure. As shown in Figure 5:

Step 501: The UE sends an attach request message to the MME, where the attach request message carries the GUTI or the IMSI; the message carries the PDN connection request, the PDN connection request message carries the APN, the PDN type, and the initial access indication; the PDN type includes IPv4, IP v6 , IPv4v6, non-IP (non-IP);

Step 502: If the GUTI is carried in the step 301, the MME needs to obtain the user IMSI through the GUTI, and the MME sends a location update request message to the HSS, where the message carries the user IMSI, and the MME address

Step 503: The HSS returns a location confirmation message to the MME, where the message carries the subscription data of the user, including a default APN, and a default QoS.

Step 504: The MME selects the anchor GW to serve according to the PDN type and the APN in step 301. If the PDN type is a non-IP type, the MME may also select the SCEF to serve the MME. If the message is not carried in the step 301, the MME Select the default APN as its service and select PGW or SCEF according to the default APN. If the MME selects the PGW, the MME sends a setup session request message to the PGW, where the message carries the user IMSI, the PDN type, the bearer ID, and the tunnel ID. If the MME selects the SCEF, the MME sends a SCEF connection request message to the SCEF, and the message carries the message. IMSI, PDN type, MME identity.

Step 505: The PGW returns a setup session response message to the MME, where the message carries an uplink PGW tunnel ID, and the SCEF returns a SCEF connection response message to the MME.

In step 506, the MME sends an attach accept message to the UE, and the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID, bears the QoS, and the like.

Step 507: The UE returns an attach complete message to the MME, where the message carries an active default bearer accept message.

Step 508: Considering that the UE can move to the 5G system, the MME sends a notification request message to the HSS, where the message carries a service entity identifier (PGW ID or SCEF ID), an APN, a PDN type, where the PDN type includes an IP type or a non-IP type. IP types can also include IPv4, IPv6 or IPv4v6;

In step 509, the HSS returns a notification confirmation message to the MME.

Step 510: The UE enters an idle state in the 4G network, and the RAT selection and the cell selection may be selected to access the 5G network, and the UE sends an attach request message to the 5G CP, where the attach request message carries the GUTI allocated in the 4G system; Carrying a PDN connection request, the PDN connection request message carries an APN, a PDN type, and a handover access indication; the PDN type includes IPv4, IP v6, IPv4v6, non-IP (non-IP);

Step 511: The 5G CP needs to obtain the user IMSI through the GUTI, and the 5G CP sends a location update request message to the HSS, where the message carries the user IMSI, and the 5G CP address

Step 512: The HSS returns a location confirmation message to the 5G CP, where the message carries the user's subscription data, including the default APN, the default QoS, and the message also carries the service entity identifier, APN, and PDN type that the UE has accessed.

In step 513, the MME selects the service entity identifier that has been accessed in step 512 according to the APN in the step 510, the handover indication, the PDN type, and the APN and PDN types obtained by the MME from the HSS in step 512 to determine whether to serve the service entity through the PGW or the SCEF. If the MME selects the PGW, the MME sends a setup session request message to the PGW, where the message carries the user IMSI, the PDN type, the bearer ID, and the tunnel ID. If the MME selects the SCEF, the MME sends a SCEF connection request message to the SCEF, in the message. Carry IMSI, bearer ID, PDN type, MME identity.

Step 514: The PGW returns a setup session response message to the MME, where the message carries an uplink PGW tunnel ID, and the SCEF returns a SCEF connection response message to the MME.

In step 515, the MME sends an attach accept message to the UE, and the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID, bearer QoS, and the like;

Step 516: The UE returns an attach complete message to the MME, where the message carries an active default bearer accept message.

scene 1:

The UE switches from the 4G network to the 5G network. FIG. 6 is a flowchart of a UE switching from a 5G network to a 4G network according to an embodiment of the present disclosure. As shown in Figure 6:

Step 601: The UE sends an attach request message to the 5G CP, where the attach request message carries the GUTI or the IMSI; the message carries the PDN connection request, and the PDN connection request message carries the APN, the PDN Type, initial access indication; PDN type includes IPv4, IP v6, IPv4v6, non-IP (non-IP);

Step 602: If the GUTI is carried in step 401, the 5G CP needs to obtain the user IMSI through the GUTI, and the 5G CP sends a location update request message to the HSS, where the message carries the user IMSI, and the 5G CP address

Step 603: The HSS returns a location confirmation message to the 5G CP, where the message carries the subscription data of the user, including a default APN, and a default QoS.

Step 604, the 5G CP selects the anchor GW to serve according to the PDN type and the APN in step 401. If the PDN type is a non-IP type, the 5G CP may also select the SCEF to serve the same; if the message in step 401 does not carry the APN, Then the 5G CP selects the default APN for its service and selects the anchor GW or SCEF according to the default APN. If the 5G CP selects the anchor GW, the 5G CP sends a setup session request message to the anchor GW, where the message carries the user IMSI, the PDN type, the bearer ID, and the tunnel ID. If the 5G CP selects the SCEF, the 5G CP sends the SCEF to the SCEF. The SCEF connection request message carries the IMSI, the PDN type, and the 5G CP identifier.

Step 605: The PGW returns a session establishment response message to the 5G CP, where the message carries the uplink PGW tunnel ID; or the SCEF returns a SCEF connection response message to the 5G CP.

Step 606: The 5G CP sends an attach accept message to the UE, where the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID, carries the QoS, and the like.

Step 607: The UE returns an attach complete message to the 5G CP, where the message carries an active default bearer accept message.

Step 608, in consideration of the fact that the UE can move to the 4G system, the 5G CP sends a notification request message to the HSS, where the message carries the service entity identifier (PGW ID or SCEF ID), APN, and PDN type, wherein the PDN type includes an IP type or a non-IP type. The IP type may also include IPv4, IPv6 or IPv4v6;

In step 609, the HSS returns a notification confirmation message to the 5G CP.

In step 610, the UE enters an idle state in the 5G network, and the RAT selection and the cell selection may be selected to access the 4G network, and the UE sends an attach request message to the 5G CP, where the attach request message carries the GUTI allocated in the 5G system; Carrying a PDN connection request, the PDN connection request message carries an APN, a PDN type, and a handover access indication; the PDN type includes IPv4, IP v6, IPv4v6, and non-IP (non-IP);

In step 611, the MME needs to obtain the user IMSI through the GUTI, and the MME sends a location update request message to the HSS, where the message carries the user IMSI, and the MME address

Step 612: The HSS returns a location confirmation message to the MME, where the message carries the subscription data of the user, including the default APN, the default QoS, and the message also carries the anchor GW/SCEF ID, APN, and PDN type that the UE has accessed;

In step 613, the MME selects the service entity identifier that has been accessed in step 612 according to the APN in the step 610, the handover indication, the PDN type, and the APN and PDN types acquired by the MME from the HSS in step 612 to determine whether to serve the service entity through the PGW or the SCEF. If the MME selects the PGW, the MME sends a setup session request message to the PGW, where the message carries the user IMSI, the PDN type, the bearer ID, and the tunnel ID. If the MME selects the SCEF, the MME sends a SCEF connection request message to the SCEF, in the message. Carry IMSI, bearer ID, PDN type, MME identity.

Step 614: The PGW returns a setup session response message to the MME, where the message carries an uplink PGW tunnel ID, and the SCEF returns a SCEF connection response message to the MME.

In step 615, the MME sends an attach accept message to the UE, and the NAS message also carries an active default bearer request message, and the default bearer request message carries the bearer ID and carries the QoS.

Step 616: The UE returns an attach complete message to the MME, where the message carries an active default bearer accept message.

Example 3

In the embodiment, a network switching device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 7 is a structural diagram of a network switching apparatus according to an embodiment of the present disclosure. As shown in FIG. 7, the apparatus includes:

The sending module 72 is configured to send the network switching information to the control plane entity of the second network when the user equipment UE moves from the first network to the second network;

Optionally, the network switching apparatus further includes: a receiving module, configured to receive network switching information sent by the first network control plane entity.

It should be noted that each of the foregoing modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the foregoing modules are in any combination. The forms are located in different processors.

Example 4

In this embodiment, a network access device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also implemented. It is possible and conceived.

FIG. 8 is a structural diagram of a network switching apparatus according to an embodiment of the present disclosure. As shown in FIG. 8, the apparatus includes: a first obtaining module 82, a second acquiring module 84, and an access module 86.

The first obtaining module 82 is configured to acquire network switching information sent by the server when the user equipment UE moves from the first network to the second network;

The second obtaining module 84 is configured to acquire PDN connection request information sent by the UE during the UE attaching process or the PDN connection establishing process;

The access module 86 is configured to select a service entity to perform access according to the network switching information and the PDN connection request information;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the PDN connection request information includes at least: The PDN type, the APN, the network handover information, and the PDN connection request information are used to indicate a service entity selected by the control plane entity of the second network, where the service entity includes: an SCEF and an anchor GW.

Optionally, the access module 86 is further configured to determine, by using the PDN type and the APN, a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate the second network. The control plane entity accesses the service entity corresponding to the specified service entity identifier.

Example 5

9 is a structural diagram of a network switching system according to an embodiment of the present disclosure. As shown in FIG. 9, the system includes a server 92 and a control plane entity 94 of the second network.

The server 92 is configured to send network switching information to the control plane entity 94 of the second network when the user equipment UE moves from the first network to the second network; wherein the network switching The information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed; the service entity includes: a SCEF and an anchor GW;

The control plane entity 94 of the second network is configured to acquire the network handover information sent by the server 92, and obtain the PDN connection request information sent by the UE during the UE attach process or the PDN connection establishment process, according to the The network switching information and the PDN connection request information selection service entity access.

Example 6

Embodiments of the present disclosure also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Example 7

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

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

Industrial applicability

With the technical solution of the present disclosure, the HHS carries the information corresponding to the PDN type, the APN, and the accessed service entity, and the HHS uses the information after receiving the information in the network handover process. Access and pre-switch network service entity access, therefore, it can solve the problem that the UE cannot use the same APN to select the original service entity and cause data interruption or service continuity cannot be guaranteed in the related art, thereby achieving the UE When using the same APN, the effect of continuity of business data is guaranteed.

Claims

A network switching method includes:

Sending network switching information to a control plane entity of the second network when the user equipment UE moves from the first network to the second network;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the network switching information is used to indicate that The control plane entity of the second network selects the accessed service entity, and the service entity includes: SCEF or anchor GW.
The method according to claim 1, wherein the PDN type and the APN are used to determine a specified service entity identifier in the service entity identifier, and the specified service entity identifier is used to indicate that the control plane entity of the second network is connected Enter the service entity corresponding to the specified service entity identifier.
The method of claim 1, wherein before the sending the network switching information to the second network control plane entity, the method further comprises:

Receiving network switching information sent by the first network control plane entity.
The method according to any one of claims 1 to 3, wherein the PDN type includes at least the following types: an IP type and a non-IP type; and the IP type includes at least one of: IPv4, IPv6, or IPv4v6.
The method according to any one of claims 1 to 3, wherein when the first network is a 4G network, the second network is a 5G network; when the first network is the 5G network, The second network is the 4G network.
The method according to any one of claims 1 to 3, wherein the control plane entity of the first network comprises at least: a mobility control entity MME in a 4G system or a control plane entity in a 5G system, the second network The control plane entity includes at least: a mobile control entity MME in a 4G system or a control plane entity in a 5G system.
A network access method includes:

Obtaining network switching information sent by the server when the user equipment UE moves from the first network to the second network;

Obtaining PDN connection request information sent by the UE during the UE attaching process or the packet data network PDN connection establishing process;

Selecting a service entity to perform access according to the network switching information and the PDN connection request information;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the PDN connection request information includes at least: The PDN type, the APN, the network handover information, and the PDN connection request information are used to indicate a service entity selected by the control plane entity of the second network, where the service entity includes: an SCEF or an anchor GW.
The method of claim 7, wherein selecting the service entity to perform access according to the network switching information further includes:

Determining, according to the PDN type in the PDN connection request information, the APN, the PDN type in the network handover information, and the APN, determining a service entity identifier corresponding to a service entity that the UE has accessed The specified service entity identifier in the medium and access to the service entity corresponding to the specified service entity identifier.
The method of claim 1 wherein said server comprises at least: a home subscriber server HSS.
A network switching device includes:

a sending module, configured to send network switching information to a control plane entity of the second network when the user equipment UE moves from the first network to the second network;

The network switching information includes at least a packet data network PDN type and a connection. An in-point name APN and a service entity identifier corresponding to the service entity that the UE has accessed, the network handover information being used to indicate a service entity selected by the control plane entity of the second network, the service Entities include: SCEF or Anchor GW.
The apparatus according to claim 10, wherein the PDN type and the APN are used to determine a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate that the control plane entity of the second network is connected Enter the service entity corresponding to the specified service entity identifier.
The device of claim 10, wherein the device further comprises:

The receiving module is configured to receive network switching information sent by the first network control plane entity.
A network access device includes:

a first acquiring module, configured to acquire network switching information sent by the server when the user equipment UE moves from the first network to the second network;

a second acquiring module, configured to acquire PDN connection request information sent by the UE during the UE attaching process or the packet data network PDN connection establishing process;

An access module, configured to select a service entity to perform access according to the network switching information and the PDN connection request information;

The network switching information includes at least a packet data network PDN type, an access point name APN, and a service entity identifier corresponding to the service entity that the UE has accessed, and the PDN connection request information includes at least: The PDN type, the APN, the network handover information, and the PDN connection request information are used to indicate a service entity selected by the control plane entity of the second network, where the service entity includes: an SCEF or an anchor GW.
The apparatus according to claim 13, wherein the access module is further configured to determine, by the PDN type and the APN, a specified service entity identifier in the service entity identifier, where the specified service entity identifier is used to indicate Control of the second network The polygon entity accesses the service entity corresponding to the specified service entity identifier.
A network switching system, the system comprising:

a server, configured to: when the user equipment UE moves from the first network to the second network, send network switching information to a control plane entity of the second network; where the network switching information includes at least a packet data network PDN type The access point name APN and the service entity identifier corresponding to the service entity that the UE has accessed; the service entity includes: a SCEF or an anchor point GW;

The control plane entity of the second network is configured to acquire the network handover information sent by the server, and obtain the PDN connection request information sent by the UE during the UE attachment process or the PDN connection establishment process, and switch according to the network. The information and the PDN connection request information select a service entity to access.
The system of claim 15 wherein said system further comprises:

A control plane entity of the first network is configured to send the network handover information to the server.
A storage medium comprising a stored program, wherein the program is executed to perform the method of any of the preceding claims 1 to 9.