Network interoperability information transmission method, apparatus, device, medium, and program product

Abstract

The application relates to a network interoperation information sending method, device, equipment, medium and program product. The method comprises the following steps: an access management network element acquires network interoperation information, the network interoperation information is used for indicating switching capability between a third generation partnership project (3GPP) network and a non-3GPP network; in the process of terminal registration or terminal registration update, the access management network element sends the network interoperation information to a terminal. By using the method, the switching failure of the terminal during network switching can be avoided to a certain extent.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method, apparatus, device, medium, and program product for transmitting network interoperable information. Background Technology

[0002] Deploying next-generation cellular networks to achieve continuous wide-area coverage presents significant challenges. To compensate for the shortcomings of cellular network coverage, services are provided indoors via WiFi (Wireless Fidelity) networks. Supporting IP continuity between WiFi (Wireless Fidelity) and cellular networks ensures a smooth handover of services when a terminal moves to an area without cellular or WiFi coverage.

[0003] Currently, the standard does not define how a terminal can determine whether the current cellular network supports switching to a Wi-Fi network. This leads to situations where the terminal attempts to switch even when switching between cellular and Wi-Fi networks is not supported, resulting in switching failures. Summary of the Invention

[0004] This application provides a method, apparatus, device, medium, and program product for sending network interoperability information, which can, to a certain extent, prevent the terminal from failing to switch networks.

[0005] In a first aspect, a method for sending network interoperability information is provided, characterized in that the method includes:

[0006] The access management network element obtains network interoperability information, which is used to indicate the handover capability between 3GPP networks and non-3GPP networks under the 3GPP program; during terminal registration or terminal registration update, the access management network element sends the network interoperability information to the terminal.

[0007] In one embodiment, the access management network element sends the network interoperability information to the terminal, including:

[0008] The access management network element sends the network interoperability information to the terminal by registering and accepting instructions.

[0009] In one embodiment, if the terminal is attached to the Evolved Packet Core (EPC), the access management element is a Mobility Management Entity (MME). The access management element sends the network interoperability information to the terminal through a registration acceptance instruction, including:

[0010] The MME sends the network interoperability information to the terminal by attaching and receiving information.

[0011] In one embodiment, the MME sends the network interoperability information to the terminal via attach response information, including:

[0012] The MME sends the network interoperability information to the terminal through the Evolved Packet System Network Support Feature cell in the attach and receive information.

[0013] In one embodiment, if the terminal registers in the 5G core network 5GC, then the access management network element is the Access and Mobility Management Function (AMF). The access management network element sends the network interoperability information to the terminal through a registration acceptance instruction, including:

[0014] The AMF sends the network interoperability information to the terminal through registration and acceptance information.

[0015] In one embodiment, the AMF sends the network interoperability information to the terminal via registration acceptance information, including:

[0016] The AMF sends the network interoperability information to the terminal through the 5G system network support feature information element in the registration acceptance information.

[0017] In one embodiment, the access management network element acquires network interoperability information, including:

[0018] The access management network element determines the interoperability supported by the network; the access management network element determines the network interoperability information based on the interoperability supported by the network.

[0019] In one embodiment, the access management network element determines the interoperability supported by the network, including:

[0020] The access management network element determines the interoperability supported by the network based on the interoperability supported by the access management network element; or,

[0021] The access management network element determines the interoperability supported by the network based on the interoperability supported by the access management network element and the interoperability supported by the session management network element.

[0022] In one embodiment, before the access management network element determines the network-supported interoperability based on the interoperability supported by the access management network element and the interoperability supported by the session management network element, the method further includes:

[0023] The access management network element queries the subscription management network element to obtain the interoperability supported by the session management network element.

[0024] In one embodiment, the method further includes:

[0025] During the terminal registration or terminal registration update process, the access management network element obtains interoperability requirement information, which is used to indicate the network interoperability requirements of the service to which the terminal belongs.

[0026] In one embodiment, the access management network element acquires interoperability requirement information, including:

[0027] The access management network element obtains the session management network element selection subscription data from the subscription management network element, and the session management network element selection subscription data includes the interoperability requirement information.

[0028] In one embodiment, if the terminal is registered with 5GC, the session management network element selects subscription data as session management function (SMF) selected subscription data, and the DNNInfo in subscribedSnssaiInfos of the SMF selected subscription data contains the interoperability requirement information.

[0029] In one embodiment, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or...

[0030] The interoperability requirement information includes multiple interoperability requirement indication fields, each of which indicates a different interoperability requirement.

[0031] In one embodiment, the interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

[0032] In one embodiment, the service to which the terminal belongs includes at least one of the following:

[0033] The access point used by the terminal;

[0034] The data network connected to the terminal;

[0035] The slice information of the network slice to which the terminal belongs.

[0036] In one embodiment, the method further includes:

[0037] The access management network element selects the session management network element based on the interoperability requirement information and the interoperability supported by the session management network element.

[0038] In one embodiment, the method further includes:

[0039] During terminal registration or terminal registration update, the access management network element obtains the context data of the original session management network element of the terminal from the subscription management network element. The context data is used by the access management network element to select the session management network element.

[0040] In one embodiment, the network interoperability information is used to indicate at least one of the following handover capabilities:

[0041] Does it support the handover between the Long Term Action Plan (LTAP) LTE network and the network accessing the EPC via the Evolved Packet Data Gateway (ePDG)?

[0042] Whether it supports switching between LTE networks and 5GC networks accessed through non-3GPP interoperability network element N3IWF;

[0043] Does it support switching between NR networks and networks accessing EPC via ePDG?

[0044] Does it support switching between NR networks and networks accessed via N3IWF to 5GC?

[0045] In one embodiment, if the network interoperability information does not indicate a certain handover capability, then it is assumed that the handover capability is not supported by the network.

[0046] In one embodiment, the access management network element sends the network interoperability information to the terminal, including:

[0047] If the terminal is attached to an EPC, the access management network element sends first network interoperability information to the terminal, the first network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the LTE network; or, the access management network element sends second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the LTE network and the handover capability between 3GPP networks and non-3GPP networks related to the NR network.

[0048] In one embodiment, the access management network element sends the network interoperability information to the terminal, including:

[0049] If the terminal is registered with 5GC, the access management network element will send third network interoperability information to the terminal. The third network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the NR network. Alternatively, the access management network element will send second network interoperability information to the terminal.

[0050] Secondly, a network interoperability information sending device is provided for accessing a management network element, the device comprising:

[0051] The acquisition module is used to acquire network interoperability information, which is used to indicate the handover capability between 3GPP networks and non-3GPP networks under the 3rd Generation Partnership Project.

[0052] The sending module is used to send the network interoperability information to the terminal during the terminal registration or terminal registration update process.

[0053] In one embodiment, the sending module is specifically used to: send the network interoperability information to the terminal by registering and accepting instructions.

[0054] In one embodiment, if the terminal attaches to the Evolved Packet Core (EPC), the access management element is the Mobility Management Entity (MME), and the sending module is specifically used to send the network interoperability information to the terminal through the attach receiving information.

[0055] In one embodiment, the sending module is specifically configured to send the network interoperability information to the terminal via the Evolved Packet System Network Support Feature (ESLSN) information element in the attached acceptance information.

[0056] In one embodiment, if the terminal is registered in the 5G core network 5GC, the access management network element is the Access and Mobility Management Function (AMF), and the sending module is specifically used to: send the network interoperability information to the terminal through the registration acceptance information.

[0057] In one embodiment, the sending module is specifically used to: send the network interoperability information to the terminal through the 5G system network support feature information element in the registration acceptance information.

[0058] In one embodiment, the acquisition module is specifically used to: determine the interoperability supported by the network; and determine the network interoperability information based on the network-supported interoperability.

[0059] In one embodiment, the acquisition module is specifically used to: determine the network-supported interoperability based on the interoperability supported by the access management network element; or, determine the network-supported interoperability based on the interoperability supported by the access management network element and the interoperability supported by the session management network element.

[0060] In one embodiment, the acquisition module is further configured to: query the interoperability supported by the session management network element from the subscription management network element.

[0061] In one embodiment, the acquisition module is further configured to: acquire interoperability requirement information during terminal registration or terminal registration update, wherein the interoperability requirement information is used to indicate the network interoperability requirements of the service to which the terminal belongs.

[0062] In one embodiment, the acquisition module is specifically used to: acquire session management element selection subscription data from the subscription management element, wherein the session management element selection subscription data includes the interoperability requirement information.

[0063] In one embodiment, if the terminal is registered with 5GC, the session management network element selects subscription data as session management function (SMF) selected subscription data, and the DNNInfo in subscribedSnssaiInfos of the SMF selected subscription data contains the interoperability requirement information.

[0064] In one embodiment, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or...

[0065] The interoperability requirement information includes multiple interoperability requirement indication fields, each of which indicates a different interoperability requirement.

[0066] In one embodiment, the interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

[0067] In one embodiment, the service to which the terminal belongs includes at least one of the following:

[0068] The access point used by the terminal;

[0069] The data network connected to the terminal;

[0070] The slice information of the network slice to which the terminal belongs.

[0071] In one embodiment, the apparatus further includes a network element selection module, which is configured to: select a session management network element based on the interoperability requirement information and the interoperability supported by the session management network element.

[0072] In one embodiment, the acquisition module is further configured to: during the terminal registration or terminal registration update process, acquire the context data of the original session management network element of the terminal from the subscription management network element, wherein the context data is used for selecting the session management network element.

[0073] In one embodiment, the network interoperability information is used to indicate at least one of the following handover capabilities:

[0074] Does it support the handover between the Long Term Action Plan (LTAP) LTE network and the network accessing the EPC via the Evolved Packet Data Gateway (ePDG)?

[0075] Whether it supports switching between LTE networks and 5GC networks accessed through non-3GPP interoperability network element N3IWF;

[0076] Does it support switching between NR networks and networks accessing EPC via ePDG?

[0077] Does it support switching between NR networks and networks accessed via N3IWF to 5GC?

[0078] In one embodiment, if the network interoperability information does not indicate a certain handover capability, then it is assumed that the handover capability is not supported by the network.

[0079] In one embodiment, the sending module is specifically configured to: if the terminal is attached to an EPC, send first network interoperability information to the terminal, the first network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with an LTE network; or send second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with an LTE network and the handover capability between a 3GPP network and a non-3GPP network associated with an NR network.

[0080] In one embodiment, the sending module is specifically configured to: if the terminal is registered with 5GC, send third network interoperability information to the terminal, the third network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the NR network; or, send second network interoperability information to the terminal.

[0081] Thirdly, an access management network element is provided, including a memory, a transceiver, and a processor:

[0082] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing any of the methods described in the first aspect by controlling the transceiver.

[0083] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements any of the methods described in the first aspect above.

[0084] Fifthly, a computer program product is provided, comprising a computer program that, when executed by a processor, implements any of the methods described in the first aspect above.

[0085] The aforementioned network interoperability information transmission method, apparatus, device, medium, and program products obtain network interoperability information from the access management network element and transmit this information to the terminal during terminal registration or registration update. This network interoperability information indicates the handover capability between 3GPP and non-3GPP networks. Thus, the terminal can obtain this information during registration or registration update, thereby acquiring the handover capability between 3GPP and non-3GPP networks. Therefore, in subsequent communication, the terminal can decide whether to perform a network handover, or how to perform a network handover, based on the handover capability between 3GPP and non-3GPP networks, thereby mitigating handover failures to some extent. Attached Figure Description

[0086] Figure 1 This is an application environment diagram of a network interoperability information sending method in one embodiment;

[0087] Figure 2 This is a diagram illustrating another application environment for the network interoperability information sending method in one embodiment;

[0088] Figure 3 This is a flowchart illustrating a method for sending network interoperability information in one embodiment;

[0089] Figure 4 This is a flowchart illustrating the steps of an access management network element obtaining network interoperability information in one embodiment.

[0090] Figure 5 This is a structural block diagram of a network interoperability information sending device in one embodiment;

[0091] Figure 6 This is another structural block diagram of the network interoperability information sending device in one embodiment;

[0092] Figure 7 This is an internal structure diagram of the access management network element in one embodiment. Detailed Implementation

[0093] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0094] Currently, cellular networks suffer from insufficient coverage, particularly indoors, where this issue exacerbates problems for voice calls, SMS messages, and other communication services. To address this, many operators have deployed Wireless Fidelity (WiFi) networks to provide communication services. This allows terminals to switch between cellular and WiFi networks, enabling communication in areas without cellular coverage via WiFi or vice versa, thus achieving continuous wide-area network coverage and ensuring uninterrupted communication for the terminal.

[0095] Currently, whether to switch between cellular and Wi-Fi networks, and how to switch between them, is generally determined by the terminal itself. However, current communication standards do not define how the terminal knows whether the current cellular network supports switching with Wi-Fi. This causes the terminal to attempt to switch even when it does not support switching between cellular and Wi-Fi networks, resulting in switching failures.

[0096] In view of this, embodiments of this application provide a method for sending network interoperability information. In this method, an access management network element can obtain network interoperability information and send it to the terminal during terminal registration or registration update. The network interoperability information is used to indicate the handover capability between 3GPP and non-3GPP networks. In this way, the terminal can obtain the network interoperability information during registration or registration update, thereby obtaining the handover capability between 3GPP and non-3GPP networks. Therefore, in subsequent communication, the terminal can decide whether to perform network handover or how to perform network handover based on the handover capability between 3GPP and non-3GPP networks, thereby avoiding handover failure to a certain extent.

[0097] It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, but may also be other implicit or related problems. For details, please refer to the description of the embodiments below.

[0098] Please refer to Figure 1 It illustrates a schematic diagram of an application environment involved in the network interoperability information sending method provided in the embodiments of this application, such as... Figure 1As shown, the application environment may include terminal 101, access network device 102, and access management network element 103. Access management network element 103 is deployed in the core network, and terminal 101 communicates with access management network element 103 deployed in the core network through access network device 102.

[0099] If the core network mentioned above is the Evolved Packet Core (EPC), that is, the core network in LTE (long term evolution), then the access management network element 103 is the Mobility Management Entity (MME) in the EPC. If the core network mentioned above is the 5G Core Network (5GC), then the access management network element 103 is the Access and Mobility Management Function (AMF) in the 5GC.

[0100] Additionally, terminal 101 can be a wireless terminal, which can be a device providing voice and / or other service data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. The wireless terminal can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, user agent, user device, or user equipment, without limitation herein.

[0101] Terminal 101 can access the core network via 3GPP (3rd Generation Partnership Project) access or non-3GPP access. Correspondingly, access network equipment 102 can be either 3GPP access network equipment or non-3GPP access network equipment.

[0102] Among them, 3GPP access network equipment can be, for example, a base station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station in a 5G network, etc., and is not limited here.

[0103] Non-3GPP access network equipment can be, for example, an evolved packet data gateway (ePDG) or a non-3GPP interworking function (N3IWF). Terminal 101 can access EPC through ePDG and 5GC through N3IWF.

[0104] Please refer to Figure 2 This illustration shows a schematic diagram of another application environment involved in the network interoperability information sending method provided in the embodiments of this application, such as... Figure 2 As shown, in addition to the terminal 101, access network device 102, and access management network element 103, the application environment may also include session management network element 104 and subscription management network element 105. Both session management network element 104 and subscription management network element 105 are deployed in the core network. Access management network element 103 can communicate with session management network element 104 and subscription management network element 105 through the network.

[0105] If the core network is EPC, then the session management network element 104 is the Packet Data Network Gateway (PGW) in EPC, and the subscription management network element 105 is the Home Subscriber Server (HSS) in EPC. If the core network is 5GC, then the session management network element 104 is the Session Management function (SMF) in 5GC, and the subscription management network element 105 is the Unified Data Management (UDM) in 5GC.

[0106] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0107] In one embodiment, such as Figure 3 As shown, a method for sending network interoperability information is provided, which can be applied to... Figure 1 and Figure 2 Taking the access management network element as an example, the explanation includes the following steps:

[0108] Step 301: Access management network element to obtain network interoperability information.

[0109] As mentioned above, if the terminal is attached to the EPC, the access management network element is the MME; if the terminal is registered to the 5GC, the access management network element is the AMF.

[0110] This network interoperability information is used to indicate the network handover capabilities supported by the network. Specifically, it is used to indicate the handover capabilities between 3GPP networks and non-3GPP networks supported by the network.

[0111] Typical 3GPP networks include LTE networks and NR (New Radio) networks. It should be noted that in this embodiment, the LTE network refers to the network where the terminal accesses the EPC via an eNB, and the NR network refers to the network where the terminal accesses the 5GC via a gNB. Typical non-3GPP networks include the network where the terminal accesses the EPC via an ePDG, and the network where the terminal accesses the 5GC via an N3IWF. In this embodiment, 3GPP networks can also be understood as cellular networks, and non-3GPP networks as WiFi networks.

[0112] It should be noted that the 3GPP networks and non-3GPP networks mentioned above are merely illustrative examples and are not intended to limit the scope of this application. In actual applications, other types of 3GPP networks and non-3GPP networks may also exist.

[0113] Step 302: During the terminal registration or terminal registration update process, the access management network element sends network interoperability information to the terminal.

[0114] It should be noted that the signaling interaction process during terminal registration or terminal registration update involves the exchange of various types of information. In step 302, the access management network element can reuse a certain piece of information from the signaling interaction process during terminal registration or terminal registration update to carry the network interoperability information. Alternatively, the access management network element can send the network interoperability information to the terminal during the terminal registration or terminal registration update process based on a newly defined piece of information. This application embodiment does not specifically limit this aspect.

[0115] The network interoperability information sending method provided in this embodiment obtains network interoperability information by the access management network element and sends it to the terminal during the terminal registration or registration update process. This network interoperability information indicates the handover capability between 3GPP and non-3GPP networks. Thus, the terminal can obtain the network interoperability information during registration or registration update, thereby acquiring the handover capability between 3GPP and non-3GPP networks. Therefore, in subsequent communication, the terminal can decide whether to perform a network handover, or how to perform a network handover, based on the handover capability between 3GPP and non-3GPP networks, thereby mitigating handover failures to some extent.

[0116] In optional embodiments of this application, network interoperability information can be used to indicate at least one of the following handover capabilities: 1. Whether handover between an LTE network and a network accessing the EPC via ePDG is supported; 2. Whether handover between an LTE network and a network accessing the 5GC via N3IWF is supported; 3. Whether handover between an NR network and a network accessing the EPC via ePDG is supported; 4. Whether handover between an NR network and a network accessing the 5GC via N3IWF is supported.

[0117] In an optional embodiment of this application, if the terminal is attached to the EPC, the MME can send the first network interoperability information to the terminal, or send the second network interoperability information to the terminal.

[0118] The first network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks associated with the LTE network, and the second network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks associated with the LTE network and the handover capability between 3GPP networks and non-3GPP networks associated with the NR network.

[0119] For example, the first network interoperability information may indicate the following handover capabilities: 1. Whether handover between an LTE network and a network accessing the EPC via an ePDG is supported; 2. Whether handover between an LTE network and a network accessing the 5GC via an N3IWF is supported. The second network interoperability information may indicate the following handover capabilities: 1. Whether handover between an LTE network and a network accessing the EPC via an ePDG is supported; 2. Whether handover between an LTE network and a network accessing the 5GC via an N3IWF is supported; 3. Whether handover between an NR network and a network accessing the EPC via an ePDG is supported; 4. Whether handover between an NR network and a network accessing the 5GC via an N3IWF is supported.

[0120] In an optional embodiment of this application, if the terminal is registered with 5GC, the AMF can send the third network interoperability information to the terminal, or send the aforementioned second network interoperability information to the terminal.

[0121] The third network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks associated with the NR network. For example, the third network interoperability information can indicate the following handover capabilities: 1. Whether handover between the NR network and the network accessing the EPC via ePDG is supported; 2. Whether handover between the NR network and the network accessing the 5GC via N3IWF is supported.

[0122] In an optional embodiment of this application, if the network interoperability information does not indicate a certain handover capability, then it is assumed that the network does not support that handover capability. For example, if the network interoperability information does not indicate that the network has the capability to support handover between an LTE network and a network accessing the EPC via ePDG, then it is assumed that the network does not support handover between an LTE network and a network accessing the EPC via ePDG.

[0123] In an optional embodiment of this application, if the network interoperability information does not indicate that a certain handover capability is not supported by the network, then it is assumed that the certain handover capability is supported by the network. For example, if the network interoperability information does not indicate that the network does not have the capability to support handover between an LTE network and a network accessing the EPC via ePDG, then it is assumed that the network supports handover between an LTE network and a network accessing the EPC via ePDG.

[0124] Please refer to Figure 4It illustrates a technical process for optionally accessing management network elements to obtain network interoperability information, such as... Figure 4 As shown, the technical process includes the following steps:

[0125] Step 401: The access management network element determines the interoperability supported by the network.

[0126] It should be noted that, in the embodiments of this application, "interoperability" refers to the ability to switch between 3GPP networks and non-3GPP networks.

[0127] In one alternative implementation, the access management network element can determine the interoperability supported by the network based on its own supported interoperability capabilities. For example, the access management network element can use its own supported interoperability capabilities as the network's supported interoperability capabilities.

[0128] In another possible implementation, the access management network element can determine the network-supported interoperability based on its own supported interoperability and the interoperability supported by the session management network element. For example, the access management network element can use the intersection of its own supported interoperability and the interoperability supported by the session management network element as the network-supported interoperability.

[0129] In an optional embodiment of this application, the interoperability supported by the access management network element can be configured locally on the access management network element. In an optional embodiment of this application, the interoperability supported by the session management network element can be stored in the subscription management network element, and the access management network element can query the interoperability supported by the session management network element from the subscription management network element.

[0130] Step 402: The access management network element determines the network interoperability information based on the interoperability capabilities supported by the network.

[0131] In an optional embodiment of this application, the access management network element can generate network interoperability information based on the interoperability capabilities supported by the network. For example, in one possible implementation, the network interoperability information includes multiple fields, and the value of each field is used to indicate whether different handover capabilities are supported. After obtaining the interoperability capabilities supported by the network, the access management network element can determine the value of each field in the network interoperability information based on the interoperability capabilities supported by the network, thereby generating the network interoperability information.

[0132] In an optional embodiment of this application, after determining the network interoperability information, the access management network element can send the network interoperability information to the terminal through a registration acceptance instruction sent during the terminal registration or terminal registration update process. In other words, the network interoperability information can be carried in the registration acceptance instruction.

[0133] If the terminal is attached to the EPC, the registration acceptance instruction can be an attach acceptance message. That is, in an optional embodiment of this application, if the terminal is attached to the EPC, the MME can send network interoperability information to the terminal through the attach acceptance message. Optionally, the MME can send network interoperability information to the terminal through the evolved packet system network feature support element (EPS network feature support IE) in the attach acceptance message.

[0134] If the terminal registers with 5GC, the registration acceptance instruction can be a registration acceptance message (English: RegistrationACCEPT). That is, in the optional embodiment of this application, if the terminal registers with 5GC, AMF can send network interoperability information to the terminal through the registration acceptance message. Optionally, AMF can send network interoperability information to the terminal through the 5G system network feature support element (English: 5GS network feature support IE) in the registration acceptance message.

[0135] Please refer to Table 1, which illustrates the contents of the 5G system network support feature information element. As shown in Table 1, this embodiment adds IWKePDG and IWKN3IWF indicator bits to the 5G system network support feature information element. IWKePDG indicates whether switching to the EPC network via ePDG is supported, and IWKN3IWF indicates whether switching to the 5GC network via N3IWF is supported. As shown in Table 1, IWKePDG is located in octet 5 and bit 8 of the 5G system network support feature information element, and its value can be 0 or 1. 1 indicates support for switching to the EPC network via ePDG, and 0 indicates no support for switching to the EPC network via ePDG. IWKN3IWF is located in octet 6 and bit 1 of the 5G system network support feature information element, and its value can be 0 or 1. 1 indicates support for switching to the 5GC network via N3IWF, and 0 indicates no support for switching to the 5GC network via N3IWF. Additionally, as shown in Table 1, octet6 and bits 2 to 8 in the 5G system network support feature information elements are reserved fields, and their values ​​can be defaulted to 0.

[0136] Table 1

[0137]

[0138] In an optional embodiment of this application, during the terminal registration or terminal registration update process, the access management network element can also obtain interoperability requirement information. This interoperability requirement information is used to indicate the network interoperability requirements of the service to which the terminal belongs. For example, the English expression for the interoperability requirement information may be "interworking with non-3GPP indication".

[0139] Optionally, the service to which the terminal belongs may include at least one of the following: 1. The access point (AP) used by the terminal; 2. The data network (DN) to which the terminal is connected; 3. The slice information of the network slice to which the terminal belongs.

[0140] In an optional embodiment of this application, the access management network element can select a session management network element based on interoperability requirement information and the interoperability supported by the session management network element. For example, if the interoperability requirement information indicates that the service to which the terminal belongs requires the network to support the ability to switch between an LTE network and a network accessing the EPC via ePDG, then the access management network element can select a session management network element that has the ability to switch between an LTE network and a network accessing the EPC via ePDG.

[0141] In an optional embodiment of this application, the access management network element may also obtain the context data of the terminal's original session management network element from the subscription management network element during the terminal registration or terminal registration update process, so as to select the session management network element using the context data. Optionally, the context data may include a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), a PDU (Protocol Data Unit) session ID, an SMF ID, etc.

[0142] In an optional embodiment of this application, the access management network element can select a session management network element by combining the interoperability requirement information and the context data of the terminal's original session management network element.

[0143] In an optional embodiment of this application, the access management network element can obtain session management network element selection subscription data from the subscription management network element. The session management network element selection subscription data includes interoperability requirement information, and the access management network element can obtain the interoperability requirement information from the session management network element selection subscription data.

[0144] If the terminal registers with 5GC, the session management network element selects the subscription data as SMF selection subscription data. The DNNInfo in subscribedSnssaiInfos of the SMF selection subscription data contains the interoperability requirement information.

[0145] Specifically, if the terminal is registered with 5GC, the AMF can request the terminal's subscription data from UDM during the terminal registration or registration update process. The terminal's subscription data may include SMF selection subscription data and the context data of the terminal's original session management network element. The AMF can obtain the interoperability requirement information from DNNInfo in subscribedSnssaiInfos in the SMF selection subscription data. Optionally, the AMF can select the SMF based on the interoperability requirement information and the context data of the terminal's original session management network element.

[0146] Please refer to Table 2, which shows an exemplary illustration of the interoperability information contained in the DNNInfo within the subscribedSnssaiInfos in the SMF selected contract data.

[0147] Table 2

[0148]

[0149] In Table 2, "Attribute name" translates to "attribute name," and its corresponding "iwkNon-3GPPInd" can be understood as the name corresponding to the interoperability information. "Data type" translates to "data type," and its corresponding "array" refers to an array type. In other words, the data type of the interoperability information is an array type. "P" indicates whether the field is mandatory, and its corresponding "O" is short for "optional," meaning that the interoperability information is not a required field but an optional one. "Cardinality" translates to "cardinality," meaning the number of bits occupied by the interoperability information. "Description" refers to the scope of the description, and its corresponding "Indicates whether interworking with Non-3GPP is subscribed, including EPS interworking with epdg, 5GS interworking with epdg, EPS interworking with N3IWF, 5GS interworking with..." "N3IWF" is the description of interoperability capability information, which translates to "indicating whether to sign up for interoperability with non-3GPP networks, including EPS and ePDG interoperability, 5GS and ePDG interoperability, EPS and N3IWF interoperability, and 5GS and N3IWF interoperability". Here, 5GS is short for 5G System, and EPS is short for Evolved Packet System.

[0150] In an optional embodiment of this application, the interoperability requirement information may also be included in the registration information of the access management network element stored in the subscription management network element storage, and / or in the registration information of the session management network element. For example, if the terminal is registered in 5GC, the interoperability requirement information may also be included in the AMF registration information stored in UDM, and / or in the SMF registration information, so that other network elements in 5GC can request and obtain it from UDM when needed. For example, the other network elements in 5GC may be NWDAF (Network Data Analytics Function).

[0151] In an optional embodiment of this application, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits (e.g., four indication bits), each indicating a different interoperability requirement; or, the interoperability requirement information includes multiple interoperability requirement indication fields (e.g., four interoperability requirement indication fields), each indicating a different interoperability requirement. The interoperability requirement indication field can be a Boolean type field.

[0152] It should be understood that, although Figure 3-4 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 3-4 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0153] In one embodiment, such as Figure 5 As shown, a network interoperability information sending device 500 is provided for accessing management network elements, including: an acquisition module 501 and a sending module 502.

[0154] The acquisition module 501 is used to acquire network interoperability information, which is used to indicate the handover capability between 3GPP networks and non-3GPP networks.

[0155] The sending module 502 is used to send network interoperability information to the terminal during the terminal registration or terminal registration update process.

[0156] In an optional embodiment of this application, the sending module 502 is specifically used to: send network interoperability information to the terminal through a registration acceptance instruction.

[0157] In an optional embodiment of this application, if the terminal is attached to the EPC, the access management network element is the MME, and the sending module 502 is specifically used to send network interoperability information to the terminal through the attachment acceptance information.

[0158] In an optional embodiment of this application, the sending module 502 is specifically used to send network interoperability information to the terminal by attaching Evolved Packet System Network Support Feature cells in the received information.

[0159] In an optional embodiment of this application, if the terminal registers with 5GC, the access management network element is AMF, and the sending module 502 is specifically used to: send network interoperability information to the terminal through registration acceptance information.

[0160] In an optional embodiment of this application, the sending module 502 is specifically used to: send network interoperability information to the terminal through the 5G system network support feature information element in the registration and acceptance information.

[0161] In an optional embodiment of this application, the acquisition module 501 is specifically used to: determine the interoperability supported by the network; and determine network interoperability information based on the interoperability supported by the network.

[0162] In an optional embodiment of this application, the acquisition module 501 is specifically used to: determine the network-supported interoperability based on the interoperability supported by the access management network element; or, determine the network-supported interoperability based on the interoperability supported by the access management network element and the interoperability supported by the session management network element.

[0163] In an optional embodiment of this application, the acquisition module 501 is further configured to: query the interoperability supported by the session management network element from the subscription management network element.

[0164] In an optional embodiment of this application, the acquisition module 501 is further configured to: acquire interoperability requirement information during terminal registration or terminal registration update, wherein the interoperability requirement information is used to indicate the network interoperability requirements of the service to which the terminal belongs.

[0165] In an optional embodiment of this application, the acquisition module 501 is specifically used to: acquire session management element selection subscription data from the subscription management element, wherein the session management element selection subscription data includes interoperability requirement information.

[0166] In an optional embodiment of this application, if the terminal registers with 5GC, the session management network element selects subscription data as SMF selection subscription data, and the DNNInfo in subscribedSnssaiInfos in the SMF selection subscription data contains interoperability requirement information.

[0167] In an optional embodiment of this application, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or...

[0168] The interoperability requirement information includes multiple interoperability requirement indication fields, each indicating a different interoperability requirement.

[0169] In an optional embodiment of this application, interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

[0170] In an optional embodiment of this application, the service to which the terminal belongs includes at least one of the following:

[0171] The access point used by the terminal;

[0172] The data network to which the terminal is connected;

[0173] The slice information of the network slice to which the terminal belongs.

[0174] In an optional embodiment of this application, network interoperability information is used to indicate at least one of the following handover capabilities:

[0175] Does it support switching between LTE networks and networks accessing EPC via ePDG?

[0176] Does it support switching between LTE networks and networks accessed via N3IWF to the 5GC?

[0177] Does it support switching between NR networks and networks accessing EPC via ePDG?

[0178] Does it support switching between NR networks and networks accessed via N3IWF to 5GC?

[0179] In an optional embodiment of this application, if the network interoperability information does not indicate a certain handover capability, it is assumed that the handover capability is not supported by the network.

[0180] In an optional embodiment of this application, the sending module 502 is specifically configured to: if the terminal is attached to an EPC, send first network interoperability information to the terminal, the first network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network; or send second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network and the handover capability between a 3GPP network and a non-3GPP network associated with the NR network.

[0181] In an optional embodiment of this application, the sending module 502 is specifically used to: send third network interoperability information to the terminal if the terminal is registered in 5GC, the third network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the NR network; or send second network interoperability information to the terminal.

[0182] In an optional embodiment of this application, the acquisition module 501 is further configured to: during the terminal registration or terminal registration update process, obtain the context data of the original session management network element of the terminal from the subscription management network element, and the context data is used for selecting the session management network element.

[0183] Please refer to Figure 6 This application embodiment also provides another network interoperability information sending device 600 for access management network elements. In addition to the various modules included in the network interoperability information sending device 500, it optionally also includes a network element selection module 503.

[0184] The network element selection module 503 is used to select a session management network element based on interoperability requirement information and the interoperability supported by the session management network element.

[0185] Specific limitations regarding the network interoperability information transmission device can be found in the limitations regarding the network interoperability information transmission method described above, and will not be repeated here. Each module in the aforementioned network interoperability information transmission device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the communication device, or stored in software in the memory of the communication device, so that the processor can call and execute the operations corresponding to each module.

[0186] Figure 7 This is a schematic diagram of the structure of the access management network element provided in the embodiments of this application. Figure 7 The access management network element 700 shown includes at least one processor 701, a memory 702, and at least one network interface 704. The various components in the access management network element 700 are coupled together via a bus system 705. It is understood that the bus system 705 is used to implement communication between these components. In addition to a data bus, the bus system 705 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 7 Various buses are designated as bus system 705. Additionally, embodiments of this application also include a transceiver 706, which may consist of multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0187] It is understood that the memory 702 in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 702 of the systems and methods described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0188] In some implementations, memory 702 stores executable modules or data structures, or subsets thereof, or extended sets thereof, such as operating system 7021. Operating system 7021 includes various system programs, such as a framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks.

[0189] Some or all of the methods disclosed in the embodiments of this application can be applied to processor 701, implemented by processor 701, or implemented by processor 701 in conjunction with other components (e.g., transceivers). Processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 701 or by instructions in the form of software. The processor 701 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 702, and processor 701 reads the information from memory 702 and, in conjunction with its hardware, completes the steps of the above method.

[0190] It is understood that the embodiments described in this application can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.

[0191] For software implementation, the technology described in the embodiments of this application can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of this application. The software code can be stored in memory and executed by processor 701. The memory can be implemented in processor 701 or external to processor 701.

[0192] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0193] Obtain network interoperability information, which is used to indicate the handover capability between 3GPP networks and non-3GPP networks; send network interoperability information to the terminal during terminal registration or terminal registration update process.

[0194] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by registering an instruction to accept the instruction.

[0195] In one embodiment, if the terminal is attached to the EPC, the access management network element is the MME, and when the computer program is executed by the processor, the following steps are also implemented: sending network interoperability information to the terminal through the attachment acceptance information.

[0196] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by attaching Evolved Packet System Network Support Feature cells in the received information.

[0197] In one embodiment, if the terminal registers with 5GC, the access management network element is AMF, and when the computer program is executed by the processor, the following steps are also performed: sending network interoperability information to the terminal through registration acceptance information.

[0198] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by registering the 5G system network support feature information element in the received information.

[0199] In one embodiment, when the computer program is executed by a processor, it further performs the following steps: determining the interoperability supported by the network; and determining network interoperability information based on the interoperability supported by the network.

[0200] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the interoperability supported by the network based on the interoperability supported by the access management network element; or,

[0201] The interoperability supported by the network is determined based on the interoperability supported by the access management network element and the interoperability supported by the session management network element.

[0202] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: querying the interoperability supported by the session management element from the subscription management element.

[0203] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: during terminal registration or terminal registration update, obtaining interoperability requirement information, which is used to indicate the network interoperability requirements of the service to which the terminal belongs.

[0204] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining session management element selection subscription data from the subscription management element, the session management element selection subscription data including interoperability requirement information.

[0205] In one embodiment, if the terminal registers with 5GC, the session management network element selects subscription data as SMF selection subscription data, and the DNNInfo in subscribedSnssaiInfos in the SMF selection subscription data contains interoperability requirement information.

[0206] In one embodiment, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or...

[0207] The interoperability requirement information includes multiple interoperability requirement indication fields, each indicating a different interoperability requirement.

[0208] In one embodiment, interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

[0209] In one embodiment, the service to which the terminal belongs includes at least one of the following:

[0210] The access point used by the terminal;

[0211] The data network to which the terminal is connected;

[0212] The slice information of the network slice to which the terminal belongs.

[0213] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: selecting a session management network element based on interoperability requirement information and the interoperability supported by the session management network element.

[0214] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: during the terminal registration or terminal registration update process, obtaining the context data of the terminal's original session management network element from the subscription management network element, the context data being used by the access management network element to select the session management network element.

[0215] In one embodiment, network interoperability information is used to indicate at least one of the following handover capabilities:

[0216] Does it support switching between LTE networks and networks accessing EPC via ePDG?

[0217] Does it support switching between LTE networks and networks accessed via N3IWF to the 5GC?

[0218] Does it support switching between NR networks and networks accessing EPC via ePDG?

[0219] Does it support switching between NR networks and networks accessed via N3IWF to 5GC?

[0220] In one embodiment, if the network interoperability information does not indicate a handover capability, then it is assumed that the handover capability is not supported by the network.

[0221] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: if the terminal is attached to the EPC, a first network interoperability information is sent to the terminal, the first network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network; or, the access management network element sends a second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network and the handover capability between a 3GPP network and a non-3GPP network associated with the NR network.

[0222] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the terminal is registered in 5GC, a third network interoperability information is sent to the terminal, the third network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks associated with the NR network; or, the access management network element sends a second network interoperability information to the terminal.

[0223] This application also provides a computer program product containing instructions that, when executed by a processor, cause the processor to perform the following steps:

[0224] Obtain network interoperability information, which is used to indicate the handover capability between 3GPP networks and non-3GPP networks; send network interoperability information to the terminal during terminal registration or terminal registration update process.

[0225] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by registering an instruction to accept the instruction.

[0226] In one embodiment, if the terminal is attached to the EPC, the access management network element is the MME, and when the computer program is executed by the processor, the following steps are also implemented: sending network interoperability information to the terminal through the attachment acceptance information.

[0227] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by attaching Evolved Packet System Network Support Feature cells in the received information.

[0228] In one embodiment, if the terminal registers with 5GC, the access management network element is AMF, and when the computer program is executed by the processor, the following steps are also performed: sending network interoperability information to the terminal through registration acceptance information.

[0229] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: sending network interoperability information to the terminal by registering the 5G system network support feature information element in the received information.

[0230] In one embodiment, when the computer program is executed by a processor, it further performs the following steps: determining the interoperability supported by the network; and determining network interoperability information based on the interoperability supported by the network.

[0231] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the interoperability supported by the network based on the interoperability supported by the access management network element; or,

[0232] The interoperability supported by the network is determined based on the interoperability supported by the access management network element and the interoperability supported by the session management network element.

[0233] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: querying the interoperability supported by the session management element from the subscription management element.

[0234] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: during terminal registration or terminal registration update, obtaining interoperability requirement information, which is used to indicate the network interoperability requirements of the service to which the terminal belongs.

[0235] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining session management element selection subscription data from the subscription management element, the session management element selection subscription data including interoperability requirement information.

[0236] In one embodiment, if the terminal registers with 5GC, the session management network element selects subscription data as SMF selection subscription data, and the DNNInfo in subscribedSnssaiInfos in the SMF selection subscription data contains interoperability requirement information.

[0237] In one embodiment, the interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or...

[0238] The interoperability requirement information includes multiple interoperability requirement indication fields, each indicating a different interoperability requirement.

[0239] In one embodiment, interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

[0240] In one embodiment, the service to which the terminal belongs includes at least one of the following:

[0241] The access point used by the terminal;

[0242] The data network to which the terminal is connected;

[0243] The slice information of the network slice to which the terminal belongs.

[0244] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: selecting a session management network element based on interoperability requirement information and the interoperability supported by the session management network element.

[0245] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: during the terminal registration or terminal registration update process, obtaining the context data of the terminal's original session management network element from the subscription management network element, the context data being used by the access management network element to select the session management network element.

[0246] In one embodiment, network interoperability information is used to indicate at least one of the following handover capabilities:

[0247] Does it support switching between LTE networks and networks accessing EPC via ePDG?

[0248] Does it support switching between LTE networks and networks accessed via N3IWF to the 5GC?

[0249] Does it support switching between NR networks and networks accessing EPC via ePDG?

[0250] Does it support switching between NR networks and networks accessed via N3IWF to 5GC?

[0251] In one embodiment, if the network interoperability information does not indicate a handover capability, then it is assumed that the handover capability is not supported by the network.

[0252] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: if the terminal is attached to the EPC, a first network interoperability information is sent to the terminal, the first network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network; or, the access management network element sends a second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between a 3GPP network and a non-3GPP network associated with the LTE network and the handover capability between a 3GPP network and a non-3GPP network associated with the NR network.

[0253] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the terminal is registered in 5GC, a third network interoperability information is sent to the terminal, the third network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks associated with the NR network; or, the access management network element sends a second network interoperability information to the terminal.

[0254] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0255] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0256] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for sending network interoperability information, characterized in that, The method includes: The access management network element uses the interoperability supported by the access management network element as the interoperability supported by the network; or, The access management network element takes the intersection between the interoperability supported by the access management network element and the interoperability supported by the session management network element as the network-supported interoperability. The access management network element determines network interoperability information based on the interoperability capabilities supported by the network. This network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks, and it indicates at least one of the following handover capabilities: Does it support handover between LTE networks under the Long Term Evolution (LTE) plan and networks accessing the EPC via the evolved Packet Data Gateway (ePDG)? Whether it supports switching between LTE networks and 5GC networks accessed through non-3GPP interoperability network element N3IWF; Does it support switching between NR networks and networks accessing EPC via ePDG? Does it support switching between NR network and network accessed via N3IWF to 5GC? During the terminal registration or terminal registration update process, the access management network element sends the network interoperability information to the terminal; The method further includes: During the terminal registration or terminal registration update process, the access management network element obtains the session management network element selection subscription data from the subscription management network element. The session management network element selection subscription data includes interoperability requirement information, which is used to indicate the network interoperability requirements of the service to which the terminal belongs. The method further includes: The access management network element selects the session management network element based on the interoperability requirement information and the interoperability supported by the session management network element.

2. The method according to claim 1, characterized in that, The access management network element sends the network interoperability information to the terminal, including: The access management network element sends the network interoperability information to the terminal by registering and accepting instructions.

3. The method according to claim 2, characterized in that, If the terminal is attached to the Evolved Packet Core (EPC), then the access management element is a Mobility Management Entity (MME). The access management element sends the network interoperability information to the terminal through a registration and acceptance instruction, including: The MME sends the network interoperability information to the terminal by attaching and receiving information.

4. The method according to claim 3, characterized in that, The MME sends the network interoperability information to the terminal via attach response information, including: The MME sends the network interoperability information to the terminal through the Evolved Packet System Network Support Feature cell in the Attach Accept information.

5. The method according to claim 2, characterized in that, If the terminal registers in the 5G core network 5GC, then the access management network element is the Access and Mobility Management Function (AMF). The access management network element sends the network interoperability information to the terminal through a registration acceptance instruction, including: The AMF sends the network interoperability information to the terminal through registration and acceptance information.

6. The method according to claim 5, characterized in that, The AMF sends the network interoperability information to the terminal through registration and acceptance information, including: The AMF sends the network interoperability information to the terminal through the 5G system network support feature information element in the registration acceptance information.

7. The method according to claim 1, characterized in that, Before the access management network element determines the interoperability supported by the network based on the interoperability supported by the access management network element and the interoperability supported by the session management network element, the method further includes: The access management network element queries the subscription management network element to obtain the interoperability supported by the session management network element.

8. The method according to claim 1, characterized in that, If the terminal is registered with 5GC, the session management network element selects subscription data as session management function (SMF) selected subscription data, and the interoperability requirement information is contained in the DNNInfo of subscribedSnssaiInfos in the SMF selected subscription data.

9. The method according to claim 8, characterized in that, The interoperability requirement information is an interoperability requirement indication field, which includes multiple indication bits, each indicating a different interoperability requirement; or... The interoperability requirement information includes multiple interoperability requirement indication fields, each of which indicates a different interoperability requirement.

10. The method according to claim 1, characterized in that, The interoperability requirement information is included in the registration information of the access management network element stored in the subscription management network element, and / or in the registration information of the session management network element.

11. The method according to claim 1, characterized in that, The services to which the terminal belongs include at least one of the following: The access point used by the terminal; The data network connected to the terminal; The slice information of the network slice to which the terminal belongs.

12. The method according to claim 1, characterized in that, The method further includes: During terminal registration or terminal registration update, the access management network element obtains the context data of the original session management network element of the terminal from the subscription management network element. The context data is used by the access management network element to select the session management network element.

13. The method according to claim 1, characterized in that, If the network interoperability information does not indicate a certain handover capability, then it is assumed that the handover capability is not supported by the network.

14. The method according to claim 1, characterized in that, The access management network element sends the network interoperability information to the terminal, including: If the terminal is attached to an EPC, the access management network element sends first network interoperability information to the terminal, the first network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the LTE network; or, the access management network element sends second network interoperability information to the terminal, the second network interoperability information being used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the LTE network and the handover capability between 3GPP networks and non-3GPP networks related to the NR network.

15. The method according to claim 14, characterized in that, The access management network element sends the network interoperability information to the terminal, including: If the terminal is registered with 5GC, the access management network element will send third network interoperability information to the terminal. The third network interoperability information is used to indicate the handover capability between 3GPP networks and non-3GPP networks related to the NR network. Alternatively, the access management network element will send second network interoperability information to the terminal.

16. A network interoperability information transmission device, characterized in that, For accessing management network elements, the device includes: The acquisition module is configured to use the interoperability supported by the access management network element as the network-supported interoperability; or, to use the intersection between the interoperability supported by the access management network element and the interoperability supported by the session management network element as the network-supported interoperability; and to determine network interoperability information based on the network-supported interoperability, wherein the network interoperability information is used to indicate the handover capability between the 3GPP network and the non-3GPP network, and the network interoperability information is used to indicate at least one of the following handover capabilities: Does it support handover between LTE networks under the Long Term Evolution (LTE) plan and networks accessing the EPC via the evolved Packet Data Gateway (ePDG)? Whether it supports switching between LTE networks and 5GC networks accessed through non-3GPP interoperability network element N3IWF; Does it support switching between NR networks and networks accessing EPC via ePDG? Does it support switching between NR network and network accessed via N3IWF to 5GC? The sending module is used to send the network interoperability information to the terminal during the terminal registration or terminal registration update process; The acquisition module is also used to acquire session management network element selection subscription data from the subscription management network element during the terminal registration or terminal registration update process. The session management network element selection subscription data includes interoperability requirement information, which is used to indicate the network interoperability requirements of the service to which the terminal belongs. The network element selection module is used to select a session management network element based on the interoperability requirement information and the interoperability supported by the session management network element.

17. An access management network element, characterized in that, Includes memory, transceiver, and processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; A processor for reading a computer program from the memory and executing the method of any one of claims 1 to 15 by controlling the transceiver.

18. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

Images