WO2019129115A1

WO2019129115A1 - System handover method and communication entity

Info

Publication number: WO2019129115A1
Application number: PCT/CN2018/124112
Authority: WO
Inventors: 孙海洋; 吴义壮; 熊春山
Original assignee: 华为技术有限公司
Priority date: 2017-12-29
Filing date: 2018-12-27
Publication date: 2019-07-04
Also published as: CN109996303A; CN109996303B

Abstract

The present application provides a system handover method and a communication entity. The method comprises: a PCF receives capability information of a terminal device; the PCF sends a request message to an NWDAF according to the capability information of the terminal device, the request message being used for requesting for EPC information; the EPC information being information of an EPC to which the terminal device possibly accesses; the PCF receives the EPC information sent by the NWDAF; the PCF determines, at least according to the EPC information, whether to release a PDU session. By obtaining the possibility that a UE moves to EPCs in advance, the PCF can determine, according to the obtained possibility that the UE moves to the EPC, whether the PDU session of the UE needs to be released after the UE moves to a particular position, thereby ensuring that the PDU session state of the UE and that of the EPC is synchronous, and the UE does not fail to execute a TAU when moving to the EPC so as to save a radio signaling and reduce a radio delay.

Description

System switching method and communication entity

This application claims the priority of the Chinese Patent Application filed on December 29, 2017, the Chinese National Intellectual Property Office, the application number is 201711487978.5, and the application name is "a system switching method and communication entity", the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of wireless communication technologies, and in particular, to a system switching method and a communication entity in a wireless communication system.

Background technique

Interworking between 5G network and 4G network In the existing 3GPP (3rd Generation Partnership Project) standard, there are two interworking modes: single registration mode and dual registration mode. In the registration mode, when the UE (ueser equipment) supports the single registration mode and the network supports the interworking with the N26 interface, the evolution from 5GC (5th generation core, fifth generation core network) to EPC (evolved packet core) The idle state of the packet core network), the UE performs a TAU (tracking area update) process of 4G-GUTI mapped from 5G-GUTI (globally unique temporary identity) if the UE has established A Packet Data Unit (PDU) session, or if the UE or EPC supports "connectionless attachment", the MME acquires the MM (mobility management) and SM (session management) context of the UE. If the UE does not have a PDU session registration in the 5GC, and the UE or EPC does not support "connectionless attachment", the UE performs an attach procedure. For the connection state movement from 5GC to EPC, inter-system switching is performed. For idle state mobility from EPC to 5GC, the UE performs the registration process of 5G-GUTI mapped from 4G-GUTI, Access and Mobility Management Function (AMF) entity and session management function (Session Management function) , SMF) The entity obtains the MM and SM context of the UE from the EPC. For the connected state movement from EPC to 5GC, an intersystem switching is performed.

That is, in the single registration mode, when the UE in the idle state moves from the 5GC to the EPC, both the UE and the EPC support connectionless attachment, and the UE performs TAU; when at least one of the UE and the EPC does not support connectionless attachment, the UE senses that it has established. The TAU operation is performed during the PDU session; otherwise, the attach operation is performed. In the 5G, when the UE is in the idle state, the core network implicitly deactivates the PDU session, so that the PDU session state of the UE and the PDU session state of the core network may be out of synchronization, that is, the UE perceives that it has a PDU session, but the network The side believes that there is no PDU session. The idle UE moves from the 5GC to the EPC. If it senses that it has a PDU session, it will initiate a TAU process. When the UE or the EPC does not support the connectionless connection, the network side detects that the UE does not establish a PDU session, the TAU of the UE is rejected, and the UE re-initiates the attach procedure. Such a trial and error approach increases the latency and signaling of the air interface.

Summary of the invention

The present application provides a method for system handover, which is used to ensure that the UE synchronizes with the EPC PDU session state when the UE switches from the 5G network to the EPC network, and does not fail to perform TAU when the UE moves to the EPC.

In a first aspect, an embodiment of the present application provides an analysis method for system handover, where the method is that a first communication entity receives capability information of a terminal device, and the first communication entity is configured according to the capability information of the terminal device. The second communication entity sends a request message, where the request message is used to request EPC information; wherein the EPC information is information of an EPC that the terminal device may access; the first communication entity receives the location sent by the second communication entity Declaring EPC information; the first communication entity determines whether to release the PDU session based at least on the EPC information. The first communication entity can determine whether the UE needs to release the PDU session of the UE according to the possibility that the acquired UE moves to the EPC after the UE moves to the specific location. Therefore, the UE is synchronized with the EPC PDU session state, and the TAU is not executed when the UE moves to the EPC, thereby saving air interface signaling and reducing air interface delay.

In a possible design, the first communication entity generates policy information according to the EPC information, and sends the policy information to a third communication entity, where the first communication entity receives the third communication entity to satisfy the policy. The PDU session of the terminal device reported when the information is reported.

In another possible design, the first communication entity updates the policy information according to the information reported by the fourth communication entity.

In another possible design, the first communication entity determines whether to release the PDU session according to at least one of the EPC information and the status information.

In another possible design, when the first communication entity determines not to release the PDU session, the first communication entity sends a reject message to the third communication entity.

In another possible design, the first communication entity determines to release the PDU session, and when the user equipment is in the idle state, the first communication entity pages the user equipment.

In a second aspect, the embodiment of the present application provides a communication entity, which can perform any of the methods provided by implementing the foregoing first aspect.

In a possible design, the communication entity has the function of implementing the behavior of the first communication entity in any of the foregoing methods, the function may be implemented by hardware, or may be implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. Optionally, the communication entity may be an AMF entity, an MME, a session management entity, a policy control entity, or a UE.

In a possible design, the structure of the communication entity includes a processor and a transceiver, the processor being configured to support the communication entity to perform a corresponding function in any of the methods of the above first aspect, such as generating, receiving or processing the above Data and/or information involved in the method. The transceiver is for supporting communication between a communication entity and other entities, and transmitting or receiving information or instructions involved in any of the methods of the first aspect to other entities. The communication entity can also include a memory for coupling with the processor that holds the program instructions and data necessary for the communication entity.

In a third aspect, the embodiment of the present application provides another method for system switching, including: receiving, by a communication network entity, mobile information of a user equipment, where the mobile information is information that the user equipment moves between multiple EPCs; The network entity determines, based on the movement information, the likelihood that the user device may move each EPC. The probability that the NWDAF performs statistical analysis on the mobile information can save the processing resources of the PCF and improve the accuracy of the PCF judgment.

In a fourth aspect, the embodiment of the present application provides a communication entity, which can perform a method for determining any one of the parameters provided by the foregoing third aspect.

In a fifth aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the communication entity provided by the second aspect, which includes a program designed to execute the above first aspect.

In a sixth aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the communication entity provided in the fourth aspect, which includes a program designed to execute the foregoing third aspect.

In a seventh aspect, the present application further provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method of the above first aspect, the computer program product comprising computer execution instructions, the computer executing The instructions are stored in a computer readable storage medium. The processor of the communication entity can read the computer execution instructions from the computer readable storage medium; the processor executes the computer to execute the instructions, such that the communication entity performs the steps performed by the communication entity in the above method provided by the embodiments of the present application, or causes the communication The entity deploys the functional unit corresponding to this step.

In an eighth aspect, the present application further provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method of the above third aspect, the computer program product comprising computer execution instructions, the computer executing The instructions are stored in a computer readable storage medium. The processor of the communication entity can read the computer execution instructions from the computer readable storage medium; the processor executes the computer to execute the instructions, such that the communication entity performs the steps performed by the communication entity in the above method provided by the embodiments of the present application, or causes the communication The entity deploys the functional unit corresponding to this step.

In a ninth aspect, the present application further provides a chip system, including a processor, for supporting a communication entity to implement the functions involved in the foregoing aspects, for example, generating, receiving, or processing data involved in the foregoing method. And / or information. In a possible design, the chip system further comprises a memory for storing necessary program instructions and data of the terminal device. The chip system can be composed of chips, and can also include chips and other discrete devices.

DRAWINGS

The embodiments of the present application will be described in more detail below with reference to the accompanying drawings.

FIG. 1 is a schematic diagram of a possible application scenario provided by the present application;

2 is a schematic diagram of a possible application environment of another embodiment of the present application;

3 is a schematic diagram of a possible application environment of another embodiment of the present application;

4 is a schematic diagram of a possible application environment of another embodiment of the present application;

FIG. 5 is a flowchart of a method provided by an embodiment of the present application;

6 is a schematic diagram of interaction of a communication method according to another embodiment of the present application;

FIG. 7 is a schematic diagram of interaction of a communication method according to another embodiment of the present application; FIG.

8 is a schematic diagram of interaction of a communication method according to an embodiment of the present application;

9 is a schematic diagram of interaction of a communication method according to another embodiment of the present application;

FIG. 10 is a schematic diagram of interaction of a communication method according to an embodiment of the present application;

11 is a schematic diagram of interaction of a communication method according to another embodiment of the present application;

Figure 12 is a schematic view of the apparatus provided by the present application;

Figure 13 is a schematic diagram of another device provided by the present application;

FIG. 14 is a schematic diagram of a communication entity provided by the present application.

Detailed ways

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

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

The terminal device in the embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or User device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or in the future evolution of the Public Land Mobile Network (PLMN) The terminal device and the like are not limited in this embodiment of the present application.

The base station in this embodiment of the present application may be a device for communicating with a terminal device, which may be in a Global System of Mobile communication (GSM) system or in Code Division Multiple Access (CDMA). Base station (Base Transceiver Station, BTS), which may also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (Evolutional NodeB in an LTE system). The eNB or the eNodeB) may also be a wireless controller in a cloud radio access network (CRAN) scenario, and the embodiment of the present application is not limited.

The network element in the embodiment of the present application may include a network device in a 5G system architecture and/or a 4G system architecture. The 4G system architecture may include an EPS system architecture. For example, the network element may include an Access and Mobility Management Function (AMF) entity, a Mobility Management Entity (MME), a Session Management Function (SMF) entity, and a unified data management. (Unified Data Management, UDM), Policy Control Function (PCF) entity, Policy and Charging Rule Function (PCRF) entity, Packet Data Network (PDN), packet data Packet Data Unit (PDU), PDN Gateway-Control Plane (PGW-C), PDN Gateway-User plane (PGW-U), home Subscriber Server (HSS) , Application Function (AF), etc.

The network architecture and the service scenario described in this application are for the purpose of more clearly explaining the technical solutions of the present application, and do not constitute a limitation on the technical solutions provided by the present application. Those skilled in the art may know that with the evolution of the network architecture and new services. The appearance of the scenario, the technical solution provided by the present application is equally applicable to similar technical problems.

As shown in FIG. 1 , it is a schematic diagram of a possible application scenario of the present application, including at least one terminal device 10, which communicates with a radio access network (English: Radio Access Network, RAN for short) through a radio interface, where the RAN At least one base station 20 is included, and for the sake of clarity, only one base station and one terminal device are shown. The terminal device 10 can also communicate with another terminal device 10, such as a device-to-device (English: Device to Device, D2D) or machine-to-machine (English: Machine to Machine, M2M) scenario. The base station 20 can communicate with the terminal device 10 or with another base station 20, such as communication between the macro base station and the access point. The RAN is connected to a core network (English: core network, referred to as CN). Optionally, the CN may be coupled to one or more data networks (English: Data Network, DN for short), such as the Internet, public switched telephone network (PSTN). .

In the present application, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning.

To facilitate understanding, some of the terms related to this application are described below.

1) Terminal Equipment, also known as User Equipment (English: User Equipment, UE for short), or Terminal (Terminal), is a device that provides voice and/or data connectivity to users. For example, a handheld device having a wireless connection function or a wireless communication function, an in-vehicle device, a wearable device, a computing device, a control device, or other processing device connected to a wireless modem, and various forms of mobile stations (English: Mobile station , referred to as: MS) and so on. Common terminal devices include: mobile phones, tablets, notebooks, handheld computers, mobile internet devices (English: mobile internet device, MID for short), wearable devices such as smart watches, smart phones. Ring, pedometer, etc. For convenience of description, in the present application, the above-mentioned devices are collectively referred to as terminal devices.

2) The access network entity is divided into a 5G access network entity and a 4G access network entity, and is a device for accessing the terminal device to the wireless network, including but not limited to: an evolved Node B (English: evolved Node B, referred to as: eNB), radio network controller (English: radio network controller, referred to as: RNC), node B (English: Node B, referred to as: NB), base station controller (English: Base Station Controller, referred to as: BSC) Base transceiver station (English: Base Transceiver Station, BTS for short), home base station (for example, Home evolved NodeB, or Home Node B, HNB for short), baseband unit (English: BaseBand Unit, BBU for short), base station ( English: g NodeB, abbreviation: gNB), transmission point (English: Transmitting and receiving point, referred to as: TRP), transmission point (English: Transmitting point, referred to as: TP), mobile switching center, etc. In addition, it can also include Wifi connection In Point (English: Access Point, AP for short), etc., can also include various forms of macro base stations, micro base stations, relay stations, access points or radio remote units (English: Remote Radio Un It, referred to as: RRU) and so on. In different systems, the name of a device with a base station function may be different, for example, in an LTE network, called an evolved NodeB (eNB or eNodeB), in the 3rd Generation (3G) In the network, it is called Node B and so on.

3), MME: is the key control node of the 3GPP protocol Long Term Evolution (English: Long Term Evolution, LTE for short) access network, which is responsible for the positioning of the UE in idle state, paging process, including relay, simply say MME is Responsible for the control plane signaling processing part. It involves the bearer activation/modification/deletion process and selects an SGW entity for this UE when it is initialized and connected.

4), AMF entity: AMF is responsible for access and mobility management, is the termination point of NG2 interface, terminates the non-access stratum (English: Non-Access Stratum, referred to as: NAS) message, complete registration management, connection management and Continuity management, mobility management, etc., and transparent routing session management messages to the session management function (English: Session Management Function, SMF) entity.

5) SGW entity: is an important network element in the Evolved Packet Core Network (EPC). The function and role of the SGW and the serving GPRS support node (English: Serving GPRS Support Node, SGSN) network element in the original 3G core network The user's face is quite. Moreover, the SGW entity can be split into a control plane SGW-C entity and a user plane SGW-U entity, the SGW-C entity has an interface with the PGW-C entity and the SGW-U entity, and the SGW-U entity has an interface with the PGW-U entity. .

6), PGW entity: the PGW network element entity introduced in the EPC system, which is similar to the function of the GPRS support node (English: Gateway GPRS Support Node, GGSN) network element, and provides the user with the border gateway of the EPC network. Session management and bearer control, data forwarding, IP address allocation, and non-3GPP user access. It is the anchor point for 3GPP access and non-3GPP access public data network PDN. The PGW entity can be split into control plane PGW-C. Entity and user plane PGW-U entities.

7) SMF entity: responsible for session management, IP address allocation and management of the UE, allocation and selection of anchor functions, and responsibility for (heavy) selection of UPF and user plane paths.

8), PCF entity: The main function is the policy decision point, providing rules based on service data flow and application detection, gating, QoS and flow-based charging control, which is the policy control function entity in the 5G system.

9): Policy and Charging Rules Function (PCRF) entity: is the policy and charging control policy decision point for service data flow and IP bearer resources, which is the policy and charging execution function. The entity selects and provides available policy and charging control decisions, and the PCRF entity is a 4G policy and charging control functional unit.

10) User plane function (English: User Plane Function, UPF for short) Entity: used for packet routing and transmission, user plane QoS processing, uplink service verification, transport layer packet identification, downlink data packet buffer, and downlink data packet User plane functions such as instructions and lawful interception.

11), User Data Management (English: Unified Data Managemen, referred to as: UDM) entity: responsible for handling credentials, location management, contract management. Provide access to user data storage units to support access authentication, registration, and mobility management.

12) Home Subscriber Server (English: Home Subscriber Server, HSS for short) Entity: It is a server for storing user subscription information in the EPS, and is mainly responsible for managing the subscription data of the user and the location information of the mobile user.

The following is a description of some common concepts or definitions involved in the embodiments of the present application. It should be noted that some of the English abbreviations in this document are described by using the LTE system as an example, which may be related to the network. The evolution changes, and the specific evolution can refer to the description in the corresponding standard.

In the present application, the 4G network may also be referred to as an EPS network, the access network of the 4G network is referred to as E-UTRAN, and the core network of the 4G network is referred to as an EPC network. The 5G network can also be called a new wireless (English: New Radio, NR for short) network, and the 5G system is simply referred to as 5GS. A plurality of nouns of the same meaning in this application will be used interchangeably.

The “data” described in the present application generally refers to service data, but may also include signaling, messages, and the like that the system needs to transmit, for example, reference signals, uplink and downlink control messages, and the like.

The term “and/or” in the present application is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

In the embodiment of the present application, the background of the user equipment switching in the EPS system and the 5G system is illustrated.

The application environment of the embodiment of the present application is introduced below with reference to FIG. 2 and FIG. 3. 2 and 3 are schematic diagrams of possible system architectures of embodiments of the present application, respectively. FIG. 2 shows an interworking architecture between a 5G system and an EPS system in a non-roaming scenario. Figure 3 shows the interworking architecture of a 5G system and an EPS system in a local breakout roaming scenario.

In the architecture shown in Figures 2 and 3, in order to support interworking between the 5G system and the EPS system, a first interface is introduced. The first interface refers to a communication interface between a mobility management entity of the 5G system and a mobility management entity of the EPS system. The mobility management entity of the 5G system may be an AMF, and the mobility management entity of the EPS system may be an MME. In the embodiment of the present application, the foregoing first interface may be represented by an N26 interface. In the case that the system architecture supports the N26 interface, the interworking architecture can support switching between 5G and EPS systems. It should be noted that, in the interworking architecture, the support for the N26 interface is optional. Only in the interworking network supporting the N26 interface can the switching process be used to ensure service continuity.

Specifically, in the architecture shown in FIG. 2 and FIG. 3, the network element in the EPS system and the network element in the 5G system may be included. Some modules in the architecture include the functions of network elements in the EPS system and network elements in the 5G system. For example, HSS+UDM module, PCF+PDRF module, SMF+PGW-C module, UPF+PGW-U module, the modules and communication interfaces involved in architecture 100-300 are described below.

UPF+PGW-U module: used for transmission and management of user data. In the interworking architecture, this module can be used for both EPS data transmission and 5G data transmission.

SMF+PGW-C module: used for session establishment, deletion and modification management. In the interworking architecture, this module can not only provide EPS session management functions, but also provide 5G session management functions.

PCF+PCRF module: used for policy and charging control entities. In the interworking architecture, the module can provide EPS policy and charging control for the UE, and provide 5G policy and charging control.

The HSS+UDM module is used to store subscription data of a user. In the interworking architecture, the module stores both the subscription information of the EPS of the UE and the subscription information of the 5G of the UE.

5G radio access network (RAN): Provides the radio air interface to the core network for the UE to obtain the corresponding service.

Application function: (Application Function, AF), interacts with the core network to provide services or services, supports access capability open functions, interacts with the policy architecture, and provides application information.

Evolved universal terrestrial radio access network (E-UTRAN): used for radio resource management to establish, modify, or delete air interface resources for the UE. Provide data and signaling transmission for the UE, and so on.

AMF module: for user access and mobility management, mainly including user registration management, reachability management mobility management, paging management, access authentication, and encryption and integrity protection for authorized non-access layer signaling. Wait.

MME module: Mobility management for users. For example, it mainly includes user attachment management, reachability management, mobility management, paging management, access authentication, and encryption and integrity protection for authorizing non-access stratum signaling.

SGW module: the gateway of the user plane, and the user plane endpoint of E-UTRAN. As a local mobility anchor for switching between base stations. Manage the routing and transmission of data packets, add packet labels for the transport layer, and more.

S1-MME interface: A control plane interface between the MME and the E-UTRAN.

S1-U interface: User plane interface between S-GW and E-UTRAN.

S5-U interface: A user plane interface between the SGW and the PGW-U for transmitting user plane data of the UE.

The S5-C interface is a control plane management interface between the SGW and the PGW-U, and is used to establish an SGW and a PGW-U user plane connection for the UE.

S6a interface: An interface between the MME and the HSS, configured to acquire subscription data of the user and perform authentication and authorization functions for the UE.

S11 interface: An interface between the SGW and the MME, used to establish a bearer of the user plane.

N1 interface: interface between the UE and the AMF, signaling management and transmission of the user non-access stratum.

N2 interface: (R) The interface between AN and AMF for signaling transmission.

N3 interface: A direct interface between UPF and (R)AN for transmitting user data.

N4 interface: An interface between the SMF and the UPF to establish a transmission channel for the user plane.

N7 interface: An interface between the SMF and the PCF. It is used to formulate and deliver policy control and accounting information.

N8 interface: An interface between the AMF and the UDM, which is used to obtain the mobility related subscription information of the user.

N10 interface: An interface between the SMF and the UDM. It is used to obtain the session management related subscription information of the user.

N11 interface: An interface between SMF and AMF for the transmission of session management information.

N15 interface: An interface between AMF and PCF for obtaining access and mobility related policy information.

In the architecture 300 shown in Figure 3:

v-PCF+v-PCRF indicates the policy control body that supports interworking in the roaming network or the visited network. It supports both 4G policy and charging control functions, and 5G policy and charging control functions.

v-SMF represents the SMF in the roaming network.

v-PCF represents a PCF in a roaming network.

In addition, the HPLMN in FIG. 3 represents a local network, and the VPLMN represents an access network or a roaming network. For example, HPLMN stands for public land mobile network (HPLMN), and VPLMN stands for visit or roaming PLMN. N24 is the reference point or interface between HPLMN and VPLMN.

It is to be understood that the foregoing description of the functions of the various modules is only a few examples, and the modules may have other functions, which are not limited by the embodiments of the present invention.

Figure 4 shows the 5G policy control architecture. The network structure of the policy control has a network data analytics function (NWDAF) network element. NWDAF can analyze big data and can control the network element in the network architecture. The (policy control function, PCF) sends the analysis information obtained based on the analysis, and the PCF can generate a policy based on the analysis information sent by the NWDAF, and can send the generated policy to the policy control execution network element, for example, access or mobile in the network architecture. The Access Control Mobility Management Function (AMF), or the Session Management Function (SMF), etc., the Policy Control Execution Network element can control the execution of the policy.

The solution provided by the embodiments of the present application will be described in more detail below with reference to the accompanying drawings.

Referring to FIG. 5, a flowchart of a method for determining parameters provided by the present application is applied to a UE switching from a 5GS network to an EPS network, including the following steps:

Step 501: The first communication entity receives capability information of the terminal device.

Step 502: The first communications entity sends a request message to the second communications entity according to the capability information of the terminal device, where the request message is used to request EPC information, where the EPC information is the terminal device. Information about the EPC that may be accessed;

Step 503: The first communications entity receives the EPC information sent by the second communications entity.

Step 504: The first communications entity determines, according to the EPC information, whether to release the PDU session.

In the embodiment shown in FIG. 5, the first communication entity may obtain the possibility that the UE moves to the respective EPC in advance, and after the UE moves to the specific location, the first communication entity may move to the EPC according to the acquired UE. If the UE needs to release the PDU session of the UE, the PDU session state of the UE is synchronized with the EPC, and the TAU does not fail when the UE moves to the EPC, thereby saving air interface signaling and reducing air interface delay.

Referring to FIG. 6 , an embodiment of the present application, another embodiment shown in FIG. 7 and FIG. 8 , wherein FIG. 7 shows a related process after initial registration of the UE, and FIG. 8 shows a process of establishing a PDU session. After the related process. In the embodiment shown in FIG. 6 to FIG. 8, the first communication entity is a PCF, the second communication entity is NWDAF, and the third communication entity is an IWK (interworking) SMF. Further, in the embodiment shown in FIG. 5, the fourth communication entity is an AMF. The following is a specific process of the embodiment shown in FIG. 6 to FIG. 9, including:

Step 1. The UE reports its own capability, that is, UE capability information. Optionally, the UE may perform capability reporting when the PDU session is established, and may perform capability reporting when registering. The manner shown in FIG. 6 is an example of performing capability reporting when the PDU session is established. In the embodiment shown in FIG. 7 and FIG. 9, the capability reporting is performed at the time of registration, and the IWK SMF requests the policy information from the PCF during the PUD session establishment process;

The UE may separately send the capability information, and may also carry the capability information in other messages. In the embodiment shown in FIG. 6, the capability information of the UE may be included in the session establishment request message, where the capability information is used to indicate whether the UE is Support for connectionless attachment. The IWK SMF reports the UE capability information to the PCF. Optionally, the IWK SMF sends the capability information of the UE to the PCF by including the capability information of the UE in the policy request message. In the embodiment shown in FIG. 7, the UE capability information is included in the registration message and reported to the AMF. The AMF reports the UE capability information to the PCF by including the UE capability information in the UE context setup/modification message. The IWK SMF is an SMF+PGW-C module, and the IWK SMF can be an SMF that supports interworking between 4G and 5G systems.

The UE capability information includes at least information indicating whether the UE supports connectionless attachment.

In the embodiment shown in FIG. 6, the PDU session is an IWK PDU session, and the UE reports its own capability when establishing a session of the IWK DNN (data network name). The IWK PDU session is established for the UE to support both IWK and the session of the APN of the EPS system and the DNN of the 5G system. The UE has the ability to determine if the session is an IWK PDU session.

Step 2. The PCF subscribes to different services to the NWDAF according to the capability information of the UE, and the NWDAF subscription service may point to the NWDAF request information.

When the capability information of the UE indicates that the UE does not support the UE without connection attachment, the PCF requests the NWDAF to initiate location information of the TAU when the UE moves to all EPCs;

When the capability information of the UE indicates that the UE supports the connectionless attached UE, the PCF requests the NWDAF to move the location information to initiate the TAU when the connectionless attached EPC is not supported.

The PCF may also initiate location information of the TAU when requesting all EPCs to which the UE moves, regardless of the capability information of the UE. Compared with the solution, when the UE requests different location information according to the capability information, the signaling resource is further saved, and the analysis efficiency of the requested location information is improved.

The request message sent by the PCF to the NWDAF may include UE parameter information, such as UE identification information; and may also include IWK error information. The IWK error information is used to indicate that an error occurs when the PCF or the AMF requests the NWDAF to indicate interworking.

In addition, the PCF subscribes to different services to the NWDAF, and the subscribed information may be mobile information of the UE, for example, location information of the TAU initiated when the UE moves to all EPCs, or the UE may move to the TAU when the connectionless EPC is not supported. Location information, optionally, the location information may be indicated by the AMF ID; the subscribed information may also be probability statistical analysis information made by the NWDAF according to the UE mobility information, or corresponding to at least one location information that the UE is most likely to move to. AMF ID. The PCF subscribes to the NWDAF for different services, that is, the EPC information requested by the PCF to the NWDAF, and may be at least one of mobile information or probabilistic statistical analysis information.

Step 3. The NWDAF sends the information requested by the UE to the PCF.

The NWDAF collects mobile information of the UE, where the mobile information may be a cell identifier where the UE is located, or an AMF ID, or geographic location information from a third-party application, a mobility pattern, etc., and the mobile information may include one of the above contents. Or a variety. The AMF ID may be an AMF ID corresponding to at least one location information that the UE is most likely to move to. Mobility mode is the concept used by AMF to characterize and optimize UE mobility. The AMF determines and updates the UE's mobility mode based on the UE's subscription, UE mobility statistics, network local policy, and UE assistance information, or any combination thereof. The statistics of UE mobility may be historical or expected UE movement trajectories. The AMF can use the UE mobility mode to optimize mobility support provided to the UE, for example, registration area allocation. All the collected mobile information constitutes big data, and the NWDAF can perform statistics according to the big data to obtain the mobility rule of each UE, thereby obtaining the probability that the UE moves to one or more EPCs to initiate a TAU. Further, the UE may further perform statistics, and may calculate a probability that each UE moves to a specific EPC to initiate a TAU when it is in a specific time period and/or a specific location. The probability that NWDAF statistically analyzes big data can save PCF processing resources and improve the accuracy of PCF judgment.

Optionally, the message sent by the MWDAF may also include an IWK error message. The IWK error information is used to indicate that an error occurs when the PCF or the AMF requests the NWDAF to indicate interworking.

Step 4. The PCF generates policy information and sends the policy information to the IWK SMF. The policy information is used to indicate the IWK SMF, and if the policy information is met, the PCF is reported to the PDU session, and the PCF decides whether to release the PDU session. The policy indicated by the policy information may be that the IWK SMF reports the IWK PDU session when the UE reaches a specific area. The policy information may be a trigger, and the IWK SMF reports the PDU session when the trigger condition is met. Optionally, in the embodiment shown in FIG. 9, the PCF may first receive the policy request information sent by the IWK SMF, and then send the policy information.

Step 5. When the IWK SMF satisfies the policy indicated by the policy information, if the IWK SMF determines that the PDU session needs to be released to the IWK DNN, the IWK SMF reports to the PCF, requesting the PCF to determine whether to release. The PDU session can be the last PDU session of the IWK DNN. Among them, IWK DNN is a DNN that supports both 4G and 5G systems.

In addition, after the step 4, the PCF may also update the policy information, and send the new policy information to the IWK SMF. The IWK SMF determines whether the report needs to be reported according to the new policy information.

Optionally, the PCF may receive the information reported by the AMF to update the policy information, where the information reported by the AMF includes at least one of information such as the location and time of the UE;

Optionally, the IWK SMF sends policy control request information to the PCF, where the policy control request information may include an SMF ID of the IWK SMF. The PCF judges it as an IWK SMF based on the SMF ID, and then issues the policy.

Step 6. If the PCF is based on the information obtained from the NWDAF, it may further refer to the status information, such as the time status or the location status of the UE, to determine that the PDU session is not released, and then send a message rejecting the IWK SMF. Otherwise, the release of the PDU session is allowed.

The PCF rejects the release of the PDU session and can notify the IWK SMF to reject the release of the PDU session by sending a message.

FIG. 9 is a flowchart of another embodiment of the present application. In FIG. 9, the embodiment is that the first communication entity is a PCF, the second communication entity is NWDAF, and the third communication entity is an AMF. The flow of the embodiment shown in Figure 9 includes:

Step 1: The UE reports its own capability. In the schematic diagram 9, the capability is reported when the UE performs the capability reporting PDU session establishment when the UE is registered. In another optional implementation manner, the UE performs the capability when the PDU session is established. Reported.

The UE may separately transmit the capability information, and may also carry the capability information in other messages.

Optionally, the PDU session is an IWK PDU session, and the UE reports its own capability when establishing an IWK DNN session. The IWK PDU session is established for the UE to support both IWK and the session of the APN of the EPS system and the DNN of the 5G system. The UE has the ability to determine if the session is an IWK PDU session.

Step 2. The PCF subscribes to different services to the NWDAF according to the capability information of the UE, and the NWDAF subscription service may request information from the NWDAF, including:

In addition, the PCF subscribes to different services to the NWDAF, and the subscribed information may be mobile information of the UE, for example, location information of the TAU initiated when the UE moves to all EPCs, or the UE may move to the TAU when the connectionless EPC is not supported. Location information, optionally, the AMF ID may be used to indicate location information; the AMF ID may be an AMF ID corresponding to at least one location information that the UE is most likely to move to. The subscribed information may also be probability statistical analysis information made by the NWDAF according to the UE mobile information. The PCF subscribes to the NWDAF for different services, that is, the EPC information requested by the PCF to the NWDAF, and may be at least one of mobile information or probabilistic statistical analysis information.

Step 3. The NWDAF sends the information requested by the PCF to the PCF.

The NWDAF collects mobile information of the UE, where the mobile information may be a cell identifier of the UE, or an AMF ID, geographic location information from a third-party application, a mobility pattern, etc., and the mobile information may include one of the above content or A variety. The AMF ID may be an AMF ID corresponding to at least one location information that the UE is most likely to move to. Mobility mode is the concept used by AMF to characterize and optimize UE mobility. The AMF determines and updates the UE's mobility mode based on the UE's subscription, UE mobility statistics, network local policy, and UE assistance information, or any combination thereof. The statistics of UE mobility may be historical or expected UE movement trajectories. The AMF can use the UE mobility mode to optimize mobility support provided to the UE, for example, registration area allocation. All the collected mobile information constitutes big data, and the NWDAF can perform statistics according to the big data to obtain the mobility rule of each UE, thereby obtaining the probability that the UE moves to one or more EPCs to initiate a TAU. Further, the UE may further perform statistics, and may calculate a probability that each UE moves to a specific EPC to initiate a TAU when it is in a specific time period and/or a specific location. The probability that NWDAF statistically analyzes big data can save PCF processing resources and improve the accuracy of PCF judgment.

Step 4: When the UE moves to the AMF corresponding to the AMF ID sent by the NWDAF, the PCF sends a paging trigger, which includes the UE location information, where the location information is used to indicate the location of the location information by the UE. When the AMF determines that the PDU session is released and the UE is in an idle state, the trigger is triggered.

Step 5. After the UE determines that the last PDU session is released after the UE is in the specified position and in the idle state, the UE is paged. Wherein the specified location is a location indicating the location information included in the trigger.

Step 6. The AMF performs paging by the UE, and the UE receives the paging to synchronize the UE and the EPC session state, and the UE performs an attach procedure when moving to the EPC. With this embodiment, the UE performs the attach execution directly when moving to the EPC, thereby reducing the delay of the air interface.

Optionally, based on the embodiment shown in FIG. 9, the embodiment shown in FIG. 10 is a scenario in which the UE switches or registers to a new AMF. In the case that the PCF receives the information sent by the NWDAF in step 3 shown in FIG. 9, the UE accesses a new AMF through an existing registration or handover procedure, and the new AMF sends a UE context establishment request to the PCF. Or the UE context modification request message, the PCF sends a paging trigger to the AMF newly accessed by the UE. After the UE determines that the last PDU session is released after the UE is in the specified state and in the idle state, the UE is paged. Wherein the specified location is a location indicating the location information included in the trigger. The AMF performs paging by paging the UE, and the UE receives the paging so that the UE and the EPC session state are synchronized, and the UE performs an attach procedure when moving to the EPC. With this embodiment, the UE performs the attach execution directly when moving to the EPC, thereby reducing the delay of the air interface.

FIG. 11 shows another embodiment of the present application. The first communication entity is an AMF, and the second communication entity is an NWDAF. The process of the embodiment shown in FIG. 11 includes:

Step 1. The UE reports its capabilities. The UE may perform capability reporting when the capability reporting PDU session is established at the time of registration. In another optional implementation manner, the UE may also perform a handover procedure each time, and access the new AMF through different AMF accesses. Report capability information.

Optionally, the PDU session is an IWK PDU session, and the UE reports its own capability when establishing an IWK DNN session. The IWK PDU session is an IWK (interworking) session established for the UE. This type of session is a session that supports both the APN of the EPS system and the DNN of the 5G system. The UE has the ability to determine if the session is an IWK PDU session.

Step 2. The AMF subscribes to different services to the NWDAF according to the capability information of the UE, and the NWDAF subscription service may request information from the NWDAF, including:

The request message sent by the AMF to the NWDAF may further include at least one of UE parameter information, such as UE identification information and IWK error information. The IWK error information is used to indicate that an error occurs when the PCF or the AMF requests the NWDAF to indicate interworking.

In addition, the AMF subscribes to different services to the NWDAF, and the subscribed content may be mobile information of the UE, for example, location information of the TAU initiated when the UE moves to all EPCs, or the UE may move to the TAU when the connectionless EPC is not supported. Location information, optionally, the AMF ID may be used to indicate location information; the subscribed information may also be probability statistical analysis information performed by the NWDAF according to the UE mobility information. The PCF subscribes to the NWDAF for different services, that is, the EPC information requested by the PCF to the NWDAF, and may be at least one of mobile information or probabilistic statistical analysis information.

Step 3. The NWDAF sends the information requested by the AMF to the AMF.

The NWDAF collects mobile information of the UE, where the mobile information may be a cell identifier of the UE, or an AMF ID, geographic location information from a third-party application, a mobility pattern, etc., and the mobile information may include one of the above content or A variety. The mobility mode is the concept used by AMF to characterize and optimize UE mobility. The AMF determines and updates the UE's mobility mode based on the UE's subscription, UE mobility statistics, network local policy, and UE assistance information, or any combination thereof. The statistics of UE mobility may be historical or expected UE movement trajectories. The AMF can use the UE mobility mode to optimize mobility support provided to the UE, for example, registration area allocation. All the collected mobile information constitutes big data, and the NWDAF can perform statistics according to the big data to obtain the mobility rule of each UE, thereby obtaining the probability that the UE moves to one or more EPCs to initiate a TAU. Further, the UE may further perform statistics, and may calculate a probability that each UE moves to a specific EPC to initiate a TAU when it is in a specific time period and/or a specific location. The probability that NWDAF statistically analyzes big data can save PCF processing resources and improve the accuracy of PCF judgment.

Step 4. When the UE is in the idle state, the AMF determines that the last PDU session is released, and then pages the UE. Wherein the specified location is a location indicating the location information included in the trigger.

Step 5. The AMF performs paging by paging the UE, and the UE receives the paging so that the UE and the EPC session state are synchronized, and the UE performs an attach procedure when moving to the EPC. With this embodiment, the UE performs the attach execution directly when moving to the EPC, thereby reducing the delay of the air interface.

The communication method of the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 11. The network element of the embodiment of the present application will be described below with reference to FIG.

FIG. 12 is a schematic block diagram of an apparatus 1200 in an embodiment of the present application. It should be understood that apparatus 1200 is capable of performing the various steps performed by the first communicating entity in the methods of FIGS. 5-11, which are not described in detail herein in order to avoid redundancy. The device 1200 includes a processing unit 1201 and a transceiver unit 1202.

The transceiver unit 1202 is configured to receive capability information of the terminal device, and send a request message to the second communication entity, where the request message is used to request EPC information; wherein the EPC information is an EPC that the terminal device may access. The information is further configured to receive the EPC information sent by the second communication entity;

The processing unit 1201 is configured to determine, according to the EPC information, whether to release a PDU session.

FIG. 13 is a schematic block diagram of an apparatus 1300 according to an embodiment of the present application. It should be understood that apparatus 1300 is capable of performing the various steps performed by the second communicating entity in the methods of FIGS. 5-11, which are not described in detail herein in order to avoid redundancy. The apparatus 1300 includes a processing unit 1301 and a transceiver unit 1302.

The transceiver unit 1302 is configured to receive mobile information of a user equipment, where the mobile information is information that the user equipment moves between multiple EPCs;

The processing unit 1301 determines, according to the movement information, a possibility that the user device may move each EPC.

The transceiver unit 1302 is further configured to send information requested by the first communication entity to the transmitter.

In the embodiment provided by the present application, the method for determining the parameters provided by the embodiments of the present application is introduced from the perspective of the interaction between the network elements and the network elements. It can be understood that each network element, such as a terminal device (such as a UE), a network device (such as a base station), etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to the respective functions. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

Based on the same inventive concept, the embodiment of the present application further provides a communication entity 1400. As shown in FIG. 11, the communication entity 1400 includes at least a processor 1401 and a memory 1402, and further includes a transceiver 1403, and may further include a bus. 1404.

The processor 1401, the memory 1402, and the transceiver 1403 are all connected by a bus 1404;

The memory 1402 is configured to store a computer execution instruction;

The processor 1401 is configured to execute a computer execution instruction stored by the memory 1402;

When the communication entity 1400 is the first communication entity in the foregoing embodiment, the processor 1401 executes the computer execution instruction stored in the memory 1402, so that the communication entity 1400 performs any of the foregoing implementations provided by the embodiments of the present application. The steps performed by the first communicating entity in the example, or causing the communicating entity to deploy a functional unit corresponding to the step.

When the communication entity 1400 is the second communication entity in the foregoing embodiment, the processor 1401 executes the computer execution instruction stored in the memory 1402, so that the communication entity 1400 performs any of the foregoing implementations provided by the embodiments of the present application. The steps performed by the third communicating entity in the example, or causing the communicating entity to deploy a functional unit corresponding to the step.

The processor 1401 may include different types of processors 1401, or include the same type of processor 1401; the processor 1401 may be any one of the following: a central processing unit (English: Central Processing Unit, CPU for short), ARM processing AMR's English full name: Advanced RISC Machines, RISC's English full name: Reduced Instruction Set Computing, Chinese translation: Reduced instruction set:), Field Programmable Gate Array (English: Field Programmable Gate Array, referred to as: FPGA) A device with computational processing power, such as a dedicated processor. In an optional implementation manner, the processor 1401 may be integrated into a many-core processor.

The memory 1402 may be any one or any combination of the following: a random access memory (English: Random Access Memory, RAM for short), a read only memory (English: read only memory, abbreviated as: ROM), nonvolatile Memory (English: non-volatile memory, referred to as: NVM), solid state drive (English: Solid State Drives, SSD for short), mechanical hard disk, disk, disk array and other storage media.

The bus 1404 can include an address bus, a data bus, a control bus, etc., for ease of representation, Figure 14 shows the bus with a thick line. The bus 1404 can be any one or any combination of the following: an industry standard architecture (English: Industry Standard Architecture, ISA for short), and a Peripheral Component Interconnect (PCI) bus. And expand the industry standard structure (English: Extended Industry Standard Architecture, referred to as: EISA) bus and other wired data transmission devices.

The embodiment of the present application provides a computer readable storage medium. The computer readable storage medium stores a computer execution instruction. The processor of the terminal device executes the computer to execute an instruction, so that the communication entity executes the method for determining the parameter provided by the application. A step performed by the first communicating entity or causing the communicating entity to deploy a functional unit corresponding to the step.

The embodiment of the present application provides a computer readable storage medium. The computer readable storage medium stores a computer execution instruction. The processor of the communication entity executes the computer to execute an instruction, so that the communication entity performs the determination method of the foregoing parameter provided by the application. A step performed by the third communicating entity or causing the communicating entity to deploy a functional unit corresponding to the step.

Embodiments of the present application provide a computer program product comprising computer executed instructions stored in a computer readable storage medium. The processor of the communication entity may read the computer execution instructions from the computer readable storage medium; the processor executes the computer to execute the instructions, so that the terminal device performs the steps performed by the first communication entity in the above method provided by the embodiments of the present application, or The communication entity is caused to deploy a functional unit corresponding to the step.

Embodiments of the present application provide a computer program product comprising computer executed instructions stored in a computer readable storage medium. The processor of the communication entity can read the computer execution instructions from the computer readable storage medium; the processor executes the computer to execute the instructions, such that the communication entity performs the steps performed by the third communication entity in the above method provided by the embodiments of the present application, or The communication entity is caused to deploy a functional unit corresponding to the step.

The present application also provides a chip system including a processor for supporting a communication entity to implement the functions involved in the above aspects, for example, generating, receiving or processing data and/or processing involved in the above methods. information. In one possible design, the chip system further includes a memory that can be used to store program instructions and data necessary for the terminal device. The chip system may be composed of a chip, or may include a chip and other discrete devices.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center To another website, computer, server, or data center by wire (for example, coaxial cable, fiber, digital subscriber line (DSL), or wireless (such as infrared, wireless, microwave, etc.) Transfer. The computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes a plurality of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed herein can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the design requirements of the particular application and the overall system. Those skilled in the art can implement the described functions using various methods for each particular application, but such implementation should not be construed as being beyond the scope of the present disclosure.

The various illustrative logic units and circuits described in this application may be implemented by a general purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), or a field programmable gate array (English: Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the above is designed to implement or operate the described functionality. A general purpose processor may be a microprocessor. Alternatively, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.

The steps of a method or algorithm described in this application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. The software unit can be stored in a random access memory (English: Random-Access Memory, RAM for short), flash memory, read-only memory (English: Read-Only Memory, abbreviation: ROM), erasable programmable read-only register (English) : Erasable Programmable Read Only Memory (EPROM), Register, Hard Disk, Removable Disk, CD-ROM (English: Compact Disc Read-Only Memory, CD-ROM) or any other form of storage medium in the field . Illustratively, the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in the terminal device or the network device. Alternatively, the processor and the storage medium may also be disposed in different components in the terminal device or the network device.

In one or more exemplary designs, the functions described above may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer readable medium or transmitted as one or more instructions or code to a computer readable medium. Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another. The storage medium can be any available media that any general purpose or special computer can access. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general purpose or special processor. In addition, any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium. The disk and the disc include a compressed disk, a laser disk, an optical disk, a digital versatile disk (DVD), a floppy disk, and a Blu-ray disk. The disk usually replicates data magnetically. Discs are typically optically replicated with a laser. Combinations of the above may also be included in a computer readable medium.

Those skilled in the art will appreciate that in one or more examples described above, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

The specific embodiments of the present invention have been described in detail with reference to the specific embodiments of the present application. It is to be understood that the foregoing description is only The scope of protection, any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application are included in the scope of protection of the present application. The above description of the specification of the present application may enable any of the art to utilize or implement the content of the present application. Any modification based on the disclosure should be considered as being obvious in the art. The basic principles described in the present application can be applied to other variants. Without departing from the spirit and scope of the invention. Therefore, the disclosure of the present application is not limited to the described embodiments and designs, but may be extended to the maximum extent consistent with the principles of the present application and the novel features disclosed.

Claims

An analysis method for system switching, characterized in that the method comprises:

Receiving, by the first communication entity, capability information of the terminal device;

The first communication entity sends a request message to the second communication entity according to the capability information of the terminal device, where the request message is used to request the evolved packet core network EPC information; wherein the EPC information is the Information about the EPC that the terminal device may access;

Receiving, by the first communications entity, the EPC information sent by the second communications entity;

The first communication entity determines whether to release the packet data unit PDU session based at least on the EPC information.
The method of claim 1 comprising:

The first communication entity generates policy information according to at least the EPC information;

Transmitting, by the first communications entity, the policy information to a third communications entity;

The first communication entity receives the PDU session of the terminal device that is reported by the third communication entity when the policy information is met.
The method according to claim 1 or 2, wherein the first communication entity updates the policy information according to information reported by the fourth communication entity.
The method according to any one of claims 1 to 3, wherein the first communication entity determines whether to release the PDU session according to at least one of the EPC information and the status information.
A method according to any one of claims 1 to 4, characterized in that

When the first communication entity determines not to release the PDU session, the first communication entity sends a reject message to the third communication entity.
A method according to any one of claims 1 to 4, characterized in that

The first communication entity determines to release the PDU session, and when the user equipment is in an idle state, the first communication entity pages the user equipment.
A device, characterized in that the device is for performing the system switching method according to any one of claims 1 to 6.