CN116113072A

CN116113072A - Mobility management method and device, equipment, communication system and storage medium

Info

Publication number: CN116113072A
Application number: CN202211714218.4A
Authority: CN
Inventors: 陈扬; 颜安
Original assignee: Zeku Technology Beijing Corp Ltd
Current assignee: Zeku Technology Beijing Corp Ltd
Priority date: 2022-12-29
Filing date: 2022-12-29
Publication date: 2023-05-12

Abstract

The application discloses a mobility management method and device, equipment, a communication system and a storage medium, wherein the method comprises the following steps: transmitting a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network; receiving a PDN connection response corresponding to the PDN connection request, and establishing PDN connection on the first communication network; wherein the PDN connection response includes second PDU session information determined from the first PDU session information; second PDU session information is saved. In this way, when the terminal equipment activates PDN connection, the terminal and the network realize PDU session information sharing through PDN connection request and PDN connection response, and when the terminal equipment is switched from the first communication network to the second communication network, the PDU session is directly established by using the stored second PDU session information, so that the modification flow of the PDU session is not required to be executed, and the air interface resource is saved.

Description

Mobility management method and device, equipment, communication system and storage medium

Technical Field

The present disclosure relates to the field of mobile communications technologies, and in particular, to a mobility management method and apparatus, a device, a communication system, and a storage medium.

Background

Because the coverage of the fourth Generation (4G) network is comprehensive at present and can meet the demands of most people, operators now select a mode of combining a fifth Generation (5th Generation,5G) network and the 4G network, so that the requirements of people on daily life can be met and a 5G network can be built step by step under the condition of saving cost. From the current networking situation, the 4G network and the 5G network are a long-term coexistence process. In order to realize smooth transition of services, an N26 interface is added between a mobility management entity (Mobility Management Entity, MME) of the 4G core network and an access and mobility management function (Access and Mobility Management Function, AMF) of the 5G core network.

A protocol data unit (Protocol Data Units, PDU) session is established when there is data transfer between the terminal and the 5G network, and a public data network (Packet Data Network, PDN) connection is established when there is data transfer between the terminal and the 4G network. In the scenario that there is an N26 interface between the 4G core network MME and the 5G core network AMF, the PDU session and the evolved packet system (Evolved Packet System, EPS) bearers have a mapping relationship with each other. The 5G allocates a mapped EPS bearer when establishing a PDU session, and the 4G allocates mapped PDU session related parameters when establishing a PDN connection. Aiming at the scene with an N26 interface, when a 4G network is to a 5G network, a terminal is required to initiate a modification flow, PDU session related parameters of the network and the terminal are synchronized, and the waste of air interface resources is increased.

Disclosure of Invention

The embodiment of the application expects to provide a mobility management method, a mobility management device, a communication system and a storage medium.

The technical scheme of the application is realized as follows:

in a first aspect, a mobility management method is provided, applied to a terminal device, and includes:

transmitting a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network;

receiving a PDN connection response corresponding to the PDN connection request, and establishing PDN connection on the first communication network; wherein the PDN connection response includes second PDU session information determined from the first PDU session information;

and saving the second PDU session information.

In a second aspect, a mobility management method is provided, applied to a network device,

receiving a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information to establish a PDU session over a second communication network;

determining second PDU session information according to the first PDU session information;

generating PDN connection response according to the second PDU session information;

and sending the PDN connection response, and establishing PDN connection on the first communication network.

In a third aspect, a mobility management device is provided, applied to a terminal device, where the mobility management device may be the terminal device or a chip applied to the terminal device. In this application, the mobility management device may implement the functions of the multiple units by using either software, hardware, or a combination of software and hardware, so that the device may perform the mobility management method provided in any one of the first aspects. The effects of each technical solution in the second aspect may refer to the corresponding technical solution in the first aspect, which is not described in detail herein.

Illustratively, the apparatus includes:

the first communication unit is used for: transmitting a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network;

the first communication unit is further configured to: receiving a PDN connection response corresponding to the PDN connection request, and establishing PDN connection on the first communication network; wherein the PDN connection response includes second PDU session information determined from the first PDU session information;

the storage unit is used for: and saving the second PDU session information.

In a fourth aspect, a mobility management device is provided, which is applied to a network device, and the mobility management device may be a terminal device or a chip applied to the terminal device. In this application, the mobility management device may implement the functions of the multiple units by using either software, hardware, or a combination of software and hardware, so that the device may perform the mobility management method provided in any one of the first aspects. The effects of each technical solution in the second aspect may refer to the corresponding technical solution in the first aspect, which is not described in detail herein.

Illustratively, the apparatus includes:

the second communication unit is used for: receiving a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information to establish a PDU session over a second communication network;

the processing unit is used for: determining second PDU session information according to the first PDU session information; generating PDN connection response according to the second PDU session information;

the second communication unit is further configured to: and sending the PDN connection response, and establishing PDN connection on the first communication network.

In a fifth aspect, a mobility management device is provided, where the mobility management device is applied to a terminal device or a network device, and the mobility management device may be the terminal device or a chip applied to the terminal device. The mobility management device includes: a processor and a memory configured to store a computer program capable of running on the processor,

Wherein the processor is configured to execute the steps of the aforementioned method when the computer program is run.

A sixth aspect is a communication system, comprising: a terminal device and a network device;

the terminal device is used for: transmitting a PDN connectivity request of a first communication network to the network device; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network;

the network device is configured to: receiving a PDN connection request of a first communication network; determining second PDU session information according to the first PDU session information; generating PDN connection response according to the second PDU session information; sending the PDN connection response to the terminal equipment, and establishing PDN connection with the terminal equipment on the first communication network;

the terminal device is further configured to: and saving the second PDU session information.

In a seventh aspect, a computer readable storage medium is provided, on which a computer program is stored, wherein the computer program, when being executed by a processor, implements the steps of the aforementioned method.

Drawings

Fig. 1 is a schematic diagram of a system architecture of a communication system according to an embodiment of the present application;

Fig. 2 is a second schematic diagram of a system architecture of a communication system according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a mobility management method according to an embodiment of the present application;

fig. 4 is a schematic format diagram of a 5GSM capability information element in an embodiment of the present application;

fig. 5 is a second flow chart of a mobility management method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a PDU session establishment procedure in an embodiment of the present application;

fig. 7 is a schematic diagram of a PDN connection establishment procedure according to an embodiment of the present application;

fig. 8 is a schematic diagram of a network system switching process in an embodiment of the present application;

fig. 9 is a schematic diagram of a session modification flow in an embodiment of the present application;

fig. 10 is a schematic diagram of the structural composition of a mobility management device according to an embodiment of the present application;

fig. 11 is a schematic diagram of a second structural component of the mobility management device according to the embodiment of the present application;

fig. 12 is a schematic structural diagram of a mobility management device according to an embodiment of the present application;

FIG. 13 is a schematic block diagram of a chip of an embodiment of the present application;

fig. 14 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

For a more complete understanding of the features and technical content of the embodiments of the present application, reference should be made to the following detailed description of the embodiments of the present application, taken in conjunction with the accompanying drawings, which are for purposes of illustration only and not intended to limit the embodiments of the present application.

Fig. 1 is a schematic diagram of a system architecture of a communication system according to an embodiment of the present application. As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that the present embodiments are illustrated by way of example only with respect to communication system 100, but the present embodiments are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 may be any terminal device including, but not limited to, a terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example a session management function+a data gateway (Session Management Function + Core Packet Gateway, smf+pgw-C) device of the core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form a new network entity by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface. For example, the terminal device establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

It should be noted that fig. 1 illustrates, by way of example, a system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication that there is an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that, in the embodiments of the present application, reference to "corresponding" may mean that there is a direct correspondence or an indirect correspondence between the two, or may mean that there is an association between the two, or may be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (e.g., including terminal devices and network devices), and the present application is not limited to a specific implementation thereof. Such as predefined may refer to what is defined in the protocol. It should also be understood that, in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited in the embodiment of the present application.

From the current networking situation, the 4G network and the 5G network are a long-term coexistence process. In order to realize smooth transition of services, an N26 interface is added between a mobility management entity (Mobility Management Entity, MME) of the 4G core network and an access and mobility management function (Access and Mobility Management Function, AMF) of the 5G core network, so as to realize information interaction between the 5GC and the EPC. Whether the mobile network operator supports the N26 interface in the 4G network and the 5G network is optional. After opening the N26 interface, the terminals can exchange their Mobility Management (MM) and service Session (SM) states between the source network and the target network when performing 4G and 5G interoperability. The N26 interface can also support the switching of the terminal between 4G and 5G and the registration information of the terminal.

Fig. 2 is a second schematic diagram of a system architecture of a communication system according to an embodiment of the present application, where the core network device 130 includes: 5G core network (5 GC) and 4G core network (EPC), the access network device includes a base station (gNB) in an NR system and a base station (eNB) in an LTE system. The 5GC includes at least AMF devices, and is mainly responsible for registration management, connection management, and mobility management for the terminal. The EPC includes at least MME equipment, and is mainly responsible for authentication, authorization, mobility management, and session management for the terminal. An N26 interface is added between the AMF and the MME so as to realize information interaction between the 5GC and the EPC.

In the scenario that there is an N26 interface between the 4G core network MME and the 5G core network AMF, the PDU session and the EPS bearer have a mapping relationship with each other. Corresponding EPS bearing is allocated when the PDU session is established by the 5G, and corresponding PDU session related parameters are allocated when the PDN connection is established by the 4G.

Protocol data network (Protocol Data Network, PDN) connection: a combination of a set of EPS bearers established on a terminal in a 4G network, the EPS bearers having the same IP address and access point name (Access Point Name, APN), the EPS bearers referring to data transport channels in the 4G network. At the terminal and network side, a PDN connection is identified by an IP address and an APN.

PDU Session (Session): refers to a process of communication between a user terminal UE and a data network DN. After the PDU session is established, a data transmission channel between the UE and the DN is established. Within a 5G network, a set of QoS flows (flows) are established on the terminal, which have the same IP address and data network name (Data Network Name, DNN). QoS flows refer to data transmission channels within a 5G network. At the terminal and network side, one PDU session is identified by IP address and DNN.

Aiming at the scene with an N26 interface, when a 4G network is to a 5G network, a terminal is required to initiate a modification flow, PDU session related parameters of the network and the terminal are synchronized, and the waste of air interface resources is increased.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

Fig. 3 is a first flow chart of a mobility management method in an embodiment of the present application, as shown in fig. 3, where the method is applied to a terminal device, and may specifically include:

step 301: transmitting a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network;

here, the first PDU session information may be understood as PDU session information sent by the terminal device to the network device, and used for performing PDU session negotiation with the network device to implement PDU session information sharing. The network equipment generates and transmits second PDU session information to the terminal equipment according to the first PDU session information, wherein the second PDU session information comprises all the information of PDU session establishment.

In some alternative embodiments, the first PDU session information includes a first information element, which may be an information element sent to the network device when the terminal initiates the modification procedure. For example, the first information element includes one of: maximum number of packet filters supported, PDU session permanent online request, integrity protection maximum data rate, PDU session management capability.

Wherein the integrity protection maximum data rate indicates a maximum data rate that the terminal device can support uplink integrity protection. The terminal will request a "PDU permanent online session" SMF to participate in deciding whether or not a "PDU permanent online session" needs to be established. The number of packet filters represents the number of packet filters that the protocol describes that the signaling QoS rules support. The PDU session management capability is used to indicate UE capabilities related to PDU session management.

Fig. 4 is a schematic diagram of a format of a 5GSM capability information element in the embodiment of the present application, and as shown in fig. 4, the format includes 16 bytes, byte 1 is a 5GSM capability information element flag bit, byte 2 is a 5GSM capability content length, byte 3 is a 5GSM capability content, the upper three bits are reserved bits, and byte 4-byte 15 is reserved bits.

In some optional embodiments, the first information element is an added information element in the first connection request; alternatively, the first information element is an added information element of a protocol configuration option (Protocol Configuration Option, PCO) in the first connection request.

Step 302: receiving a PDN connection response corresponding to the PDN connection request, and establishing PDN connection on the first communication network; wherein the PDN connection response includes second PDU session information determined from the first PDU session information;

In some alternative embodiments, the second PDU session information comprises a second information element generated from the first information element; and/or, an acknowledgement of the first information element.

The network device returns a confirmation response when the network device determines that the first information element is consistent with the PDU session reference information stored by the network side; or the first information element is directly used as a second information element to be issued to the terminal equipment; or when the first information element is determined to be inconsistent with the PDU session reference information stored in the network side, modifying the first information element according to the stored PDU session reference information to generate a second information element and transmitting the second information element to the terminal equipment; alternatively, a part of the first information element returns an acknowledgement, and another part returns an information element. And realizing information sharing between the network and the terminal.

The second information element is an newly added information element in the first connection response; or, the second information element is a new information element in the protocol configuration options of the first connection response.

In some alternative embodiments, the first PDU session information further comprises a third information element, the third information element comprising at least one of: PDU session identification, request QoS rules, request QoS flow description.

The second PDU session information further includes a fourth information element generated from the third information element, illustratively, the fourth information element including at least one of: network slice parameters, qoS rules, session aggregate maximum bit rate, PDU session address lifecycle, qoS flow description, qoS rules with two octets length, qoS flow description with two octets length.

Here, the third information element may be understood as a request message sent by the terminal to the network, requesting the network device to issue the fourth information element.

Step 303: and saving the second PDU session information.

In some alternative embodiments, upon switching from the first communication network to the second communication network, a PDU session is established on the second communication network based on the second PDU session information.

By adopting the technical scheme, when the terminal equipment activates PDN connection, the terminal and the network realize PDU session information sharing through PDN connection request and PDN connection response, and when the terminal equipment is switched from the first communication network to the second communication network, the PDU session is directly established by using the stored second PDU session information, so that the modification flow of the PDU session is not required to be executed, and the air interface resources are saved.

As shown in fig. 5, the method is applied to a network device, and specifically may include:

step 501: receiving a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information to establish a PDU session over a second communication network;

Step 502: determining second PDU session information according to the first PDU session information;

in some optional embodiments, the second PDU session information generated according to the first PDU session information includes: acquiring PDU session reference information of the second communication network; and generating the second PDU session information according to the first PDU session information and the PDU session reference information.

Here, the PDU session reference information is PDU session related information acquired in advance by the network device of the first communication network, for example: related information such as PDU session ID, session type (IPv 4, IPv6, IPv4v6, ethenet, unstructured), uplink and downlink rate, charging ID, roaming status information, IP information of the terminal, PCF information, qos information, tunnel information, destination address, SMF identification, slice information (if supported), default DRB information, data network name, AMF information, user location information, session management information, UPF ID, online charging identification, offline charging identification, etc.

In some optional embodiments, the acquiring PDU session reference information of the second communication network includes: and acquiring the PDU session reference information sent by the network equipment corresponding to the second communication network through a connection interface between the network equipment corresponding to the second communication network. The connection interface may be an N26 interface between the 4G core network MME and the 5G core network AMF, where the 4G core network MME obtains PDU session reference information sent by the 5G core network AMF through the N26 interface.

In some optional embodiments, the acquiring PDU session reference information of the second communication network includes: acquiring subscription information of the second communication network sent by the operator equipment; and acquiring the PDU session reference information from the subscription information of the second communication network.

That is, the PDU session reference information may be obtained by communication with a network device corresponding to the second communication network, or may be obtained from subscription information of the second communication network issued by the operator device.

Step 503: generating PDN connection response according to the second PDU session information;

in some alternative embodiments, the activate default EPS bearer context request is generated from a PDN connection request; and generating a PDN connection response according to the second PDU session information and the activated default EPS bearing context request. The network issues a default EPS bearer context activation request to establish a default EPS bearer context between the terminal and the network.

Step 504: and sending the PDN connection response, and establishing PDN connection on the first communication network.

In the embodiment of the application, when the terminal equipment activates PDN connection, the terminal and the network realize PDU session information sharing through PDN connection request and PDN connection response, and when the terminal equipment is switched from the first communication network to the second communication network, the PDU session is directly established by using the stored second PDU session information, so that the modification flow of the PDU session is not required to be executed, and the air interface resources are saved. The first communication network (e.g., 4G network) and the second communication network (e.g., 5G network) are of different network types, and the terminal device from the first communication network to the second communication network may include a cross-type procedure such as Handover/reselection/redirection.

An application scenario of the mobility management method according to the embodiment of the present application is illustrated below.

Scene one: and establishing and storing a corresponding mapping EPS bearing by the PDU, carrying an EPS bearing context in the PDU session establishment process, and storing the corresponding EPS bearing context by the terminal. As shown in fig. 6, the PDU session establishment procedure specifically includes:

1. generating a registration request (REGISTRATION REQUEST) by a mobility management (Mobility Management, MM) unit of the terminal device, and sending the registration request to the 5G network device (NET);

mm receives a registration accept (REGISTRATION ACCEPT) message;

mm sends a registration complete (REGISTRATION COMPLETE) message to NET1;

4. a SESSION management (Session Management, SM) unit of the terminal device generates a PDU SESSION establishment request (sm_pdu_session_est_req) and transmits it to the MM;

mm sends an uplink non-access stratum TRANSPORT (UL NAS TRANSPORT) message including pdu_session_req to NET;

PDU SESSION establishment success, NET sending a downlink non-access stratum TRANSPORT (DL NAS TRANSPORT) message comprising a PDU SESSION establishment ACCEPT message (pdu_session_accept) to MM, wherein pdu_session_accept comprises: a mapped EPS bearer context (Mapped EPS bearer contexts);

mm sends a PDU SESSION establishment ACCEPT indication (sm_pdu_session_accept_ind) containing Mapped EPS bearer contexts to SM, SM save Mapped EPS bearer contexts for establishment of PDN connection according to Mapped EPS bearer contexts when switching from 5G network to 4G network.

Scene II: and the 4G PDN establishes and stores the corresponding PDU session information, and when the terminal equipment activates the 4G PDN connection, the PDU session information is requested and stored. As shown in fig. 7, the PDN connection establishment procedure specifically includes:

the sm generates a PDN connection request (PDN CONNECTIVITY REQUEST) to send to the MM, the PDN CONNECTIVITY REQUEST including first PDU session information for the terminal-to-network direction;

wherein the first PDU session information includes:

-001AH (PDU session ID), PDU session identity;

0023H (QoS rules with the length of two octets support indicator), a support indicator of a requested QoS rule, in particular a QoS rule of two octets length;

0024H (QoS flow descriptions with the length of two octets support indicator), a support indicator requesting a QoS flow description, in particular a two octet length QoS flow description;

maximum number of supported packet filters, the maximum number of packet filters supported;

always-on PDU session requested, i.e. PDU session permanent online request;

integrity protection maximum data rate, i.e. the integrity-protected maximum data rate;

5GSM capability, PDU session management capability.

Mm sends an ATTACH REQUEST (ATTACH REQUEST) including PDN CONNECTIVITY REQUEST to the 4G network device (NET); the purpose of the PDN connection request is to establish a default bearer (default bearer) between the terminal and the P-GW of the 4G network, which will remain connected until the terminal detaches (detach) LTE network.

Net sends attach accept (ATTACH ACCEPT) including activate default EPS bearer context request (ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST); activating a default EPS bearer context request to include second PDU session information of a network-to-terminal direction;

wherein the second PDU session information includes:

-001BH (S-nsai), i.e. single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-nsai);

001CH (QoS rules), i.e. QoS rules;

001DH (Session-AMBR), i.e. Session aggregate maximum bit rate (Session-aggregate maximum bit rate, session-AMBR)

-001EH (PDU session address lifetime), PDU session address life cycle;

-001FH (QoS flow descriptions), qoS flow description;

0023H (QoS rules with the length of two octets), a QoS rule with a length of two octets;

0024H (QoS flow descriptions with the length of two octets), a QoS flow description with a length of two octets;

Maximum number of supported packet filters, i.e. the maximum number of packet filters supported,

always-on PDU session requested, i.e. PDU session permanent online request;

5GSM capability, PDU session management capability.

The MM sends a request for activating default EPS bearing context to the SM;

the SM stores second PDU session information;

sm sends an activate default EPS bearer context accept (ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT) to MM;

mm sends ATTACH COMPLETE (ATTACH COMPLETE) including activate default EPS bearer context accept to NET.

Scene III: and the 4G network is connected with the 5G network, the 4G PDN establishes and stores corresponding PDU session information, and when the 4G-to-5G cross-system processes such as Handover (Handover)/reselection/redirection are carried out, PDN session is directly established according to the stored PDU session information, a PDU session modification flow is not required to be initiated, and air interface resources are saved. As shown in fig. 8, the 4G network to 5G network specifically includes:

1. and when the terminal equipment activates the 4G PDN connection, the PDU session information is requested and stored.

2. The access layer (Access Stratum AS) of the terminal device generates a handover instruction (AS_NAS_IRAT_CHANGE_IND (4- > 5)) and sends the handover instruction to the MM;

MM sends a PDP CONTEXT query request (mm_sm_pdp_context_query_req) to SM;

SM sends a PDP CONTEXT query response (mm_sm_pdp_context_query_cnf) including the allowed PDU session state (Allowed PDU session status) to MM;

mm sends a registration request (REGISTRATION REQUEST) including an allowed PDU session state (Allowed PDU session status) to the 5G network device (NET);

net sends registration accept (REGISTRATION ACCEPT) including PDU session state (PDU session status) to MM;

MM sends a PDU SESSION message (mm_sm_pdu_session_net_ind) including the PDU SESSION state (PDU SESSION status) to SM, which does not need to initiate a modification procedure.

As shown in fig. 9, when the terminal currently resides in the 4G network, if the PDN connection is a 4G newly activated PDN connection and PDU session information is stored, and when the terminal switches from the 4G newly activated PDN connection to the 5G, the terminal needs to initiate a modification procedure of the PDU session information to obtain all PDU session information corresponding to the newly activated PDN connection when the newly activated PDN connection is mapped to the PDU session. As shown in fig. 9, the SM needs to initiate a modification procedure (Mobile registration) to obtain the maximum number of supported packet filters, PDU session permanent online request, integrity protection maximum data rate, 5G mobility management capability, etc.

The embodiment of the present application further provides a mobility management device, applied to a terminal device, fig. 10 is a schematic structural diagram of the mobility management device provided in the embodiment of the present application, as shown in fig. 10, and the mobility management device 1000 includes:

the first communication unit 1001 is configured to: transmitting a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information for the terminal device to establish a PDU session on a second communication network;

the first communication unit 1001 is further configured to: receiving a PDN connection response corresponding to the PDN connection request, and establishing PDN connection on the first communication network; wherein the PDN connection response includes second PDU session information determined from the first PDU session information;

the storage unit 1002 is configured to: and saving the second PDU session information.

In some alternative embodiments, the first PDU session information comprises a first information element comprising one of: maximum number of packet filters supported, PDU session permanent online request, integrity protection maximum data rate, PDU session management capability.

In some optional embodiments, the first information element is an added information element in the first connection request; or, the first information element is a new information element in the protocol configuration option of the first connection request.

In some optional embodiments, the second information element is an added information element in the first connection response; or, the second information element is a new information element in the protocol configuration options of the first connection response.

In some alternative embodiments, the first PDU session information further comprises a third information element, the third information element comprising at least one of: PDU session identification, request QoS rule, request QoS flow description; the second PDU session information further includes a fourth information element generated from the third information element, the fourth information element including at least one of: network slice parameters, qoS rules, session aggregate maximum bit rate, PDU session address lifecycle, qoS flow description, qoS rules with two octets length, qoS flow description with two octets length.

In some alternative embodiments, the first communications unit 1001 is further configured to: and when switching from the first communication network to the second communication network, establishing a PDU session on the second communication network according to the second PDU session information.

The embodiment of the present application further provides a mobility management device, which is applied to a network device, fig. 11 is a schematic structural diagram of the mobility management device provided in the embodiment of the present application, as shown in fig. 11, and the mobility management device 1100 includes:

the second communication unit 1101 is configured to: receiving a PDN connection request of a first communication network; wherein the PDN connection request includes first PDU session information to establish a PDU session over a second communication network;

the processing unit 1102 is configured to: determining second PDU session information according to the first PDU session information; generating PDN connection response according to the second PDU session information;

the second communication unit 1101 is further configured to: and sending the PDN connection response, and establishing PDN connection on the first communication network.

The processing unit 1102 is configured to: acquiring PDU session reference information of the second communication network;

and generating the second PDU session information according to the first PDU session information and the PDU session reference information.

In some alternative embodiments, the second communication unit 1101 is further configured to: acquiring the PDU session reference information sent by the network equipment corresponding to the second communication network through a connection interface between the network equipment corresponding to the second communication network; or acquiring subscription information of the second communication network sent by the operator equipment; and acquiring the PDU session reference information from the subscription information of the second communication network.

Fig. 12 is a schematic structural diagram of a mobility management device according to an embodiment of the present application. The mobility management device may be a terminal device or a network device. The mobility management device 1200 shown in fig. 12 comprises a processor 1210, which processor 1210 may call and run a computer program from memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 12, the mobility management device 1200 may further include a memory 1220. Wherein the processor 1210 may call and run computer programs from the memory 1220 to implement the methods in embodiments of the present application.

The memory 1220 may be a separate device from the processor 1210, or may be integrated into the processor 1210.

Optionally, as shown in fig. 12, the mobility management device 1200 may further include a transceiver 1230, and the processor 1210 may control the transceiver 1230 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein the transceiver 1230 may include a transmitter and a receiver. The transceiver 1230 may further include antennas, the number of which may be one or more.

Optionally, the mobility management device 1200 may be specifically a network device in the embodiment of the present application, and the mobility management device 1200 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the mobility management device 1200 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the mobility management device 1200 may implement corresponding flows implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

The mobility management device may be a chip, and fig. 13 is a schematic structural diagram of the chip according to an embodiment of the present application. The chip 1300 shown in fig. 13 includes a processor 1310, and the processor 1310 may call and execute a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 13, the chip 1300 may further include a memory 1320. Wherein the processor 1310 may call and run a computer program from the memory 1320 to implement the methods in embodiments of the present application.

Wherein the memory 1320 may be a separate device from the processor 1310 or may be integrated into the processor 1310.

Optionally, the chip 1300 may also include an input interface 1330. The processor 1310 may control the input interface 1330 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 1300 may also include an output interface 1340. Wherein the processor 1310 may control the output interface 1340 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 14 is a schematic block diagram of a communication system provided in an embodiment of the present application. As shown in fig. 14, the communication system 1400 includes a terminal device 1410 and a network device 1420.

The terminal device 1410 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1420 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A mobility management method applied to a terminal device, the method comprising:

and saving the second PDU session information.

2. The method of claim 1, wherein the first PDU session information comprises a first information element comprising one of: maximum number of packet filters supported, PDU session permanent online request, integrity protection maximum data rate, PDU session management capability.

3. The method of claim 2, wherein the first information element is an additional information element in the first connection request;

or, the first information element is a new information element in the protocol configuration option of the first connection request.

4. The method of claim 2, wherein the second PDU session information comprises a second information element generated from the first information element; and/or, an acknowledgement of the first information element.

5. The method according to any of claims 2-4, wherein the first PDU session information further comprises a third information element, the third information element comprising at least one of: PDU session identification, request QoS rule, request QoS flow description;

the second PDU session information further includes a fourth information element generated from the third information element, the fourth information element including at least one of: network slice parameters, qoS rules, session aggregate maximum bit rate, PDU session address lifecycle, qoS flow description, qoS rules with two octets length, qoS flow description with two octets length.

6. The method according to claim 1, wherein the method further comprises:

and when switching from the first communication network to the second communication network, establishing a PDU session on the second communication network according to the second PDU session information.

7. A mobility management method, applied to a network device, characterized in that,

8. The method of claim 7, wherein the second PDU session information generated from the first PDU session information comprises:

acquiring PDU session reference information of the second communication network;

9. The method of claim 8, wherein the obtaining PDU session reference information for the second communication network comprises:

Acquiring the PDU session reference information sent by the network equipment corresponding to the second communication network through a connection interface between the network equipment corresponding to the second communication network;

or acquiring subscription information of the second communication network sent by the operator equipment; and acquiring the PDU session reference information from the subscription information of the second communication network.

10. The method of claim 7, wherein the first PDU session information comprises a first information element comprising one of: maximum number of packet filters supported, PDU session permanent online request, integrity protection maximum data rate, PDU session management capability.

11. The method of claim 10, wherein the first information element is an additional information element in the first connection request;

12. The method of claim 10, wherein the second PDU session information comprises a second information element generated from the first information element; or, an acknowledgement of the first information element.

13. The method according to any of claims 10-12, wherein the first PDU session information further comprises a third information element, the third information element comprising at least one of: PDU session identification, request QoS rule, request QoS flow description;

14. A mobility management device for application to a terminal device, the device comprising:

The storage unit is used for: and saving the second PDU session information.

15. A mobility management device for use in a network appliance, the device comprising:

16. A mobility management device, comprising: a processor and a memory configured to store a computer program capable of running on the processor,

wherein the processor is configured to cause the mobility management device 5 to perform the steps of the method of any of claims 1 to 13 when the computer program is run.

17. A communication system, the communication system comprising: a terminal device and a network device;

the terminal device is used for: transmitting a PDN connectivity request of a first communication network to the network device; wherein the PDN connection request includes first PDU session information for the terminal device to establish PDU session 0 over a second communication network;

18. A computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a computer, causes the computer to carry out the steps of the method according to any of claims 1 to 13.