Terminal resident network management method and wireless communication system

Abstract

The invention discloses a terminal resident network management method and a wireless communication system. The method comprises: in response to a joint attach request message of a terminal, obtaining first subscription information of the terminal, the terminal accessing a network based on IoT NTN, and the joint attach request message being used for requesting to attach to a data exchange domain network and a circuit exchange domain network; according to the first subscription information, determining a first network residence strategy after the terminal completes circuit switched fallback and voice service interaction, the first network residence strategy comprising one of the following: switching back to the data switching domain network and residing in the circuit switching domain network; and sending an attachment acceptance message carrying the first network resident strategy to the terminal. The technical problems that in a terminal communication scene based on IoT NTN, a user who only signs a voice service needs to fall back to a circuit switching domain network from a data switching domain network during calling, time delay is large, and efficiency is low are solved.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a terminal resident network management method and a wireless communication system. Background Art

[0002] In the non-terrestrial network environment of the Internet of Things, especially when the UE (User Equipment) uses satellite-based communication services, the UE may need to access the data exchange domain network (such as LTE (Long Term Evolution) network) and the circuit switching domain network (such as 2G / 3G network) at the same time. This dual-mode access requirement is most obvious when the UE performs a joint attachment process, which follows the process specified in 3GPP TS 23.401. Joint attachment is a protocol process performed when the UE first accesses the network or when a major change occurs in the network. It is necessary to determine whether the UE supports both EPS (Evolved Packet System) and CS (Circuit Switched), whether it supports CSFB (Circuit Switched FallBack), and whether it is limited to SMS services (SMS-only). When the UE completes the voice service and needs to perform CSFB, the network needs to decide whether the UE returns to the LTE network to continue the data service after the voice service ends, or continues to stay in the 2G / 3G network. This decision-making process is crucial to improving the utilization efficiency of network resources and user experience. However, the current network architecture and process are insufficient in handling such decisions, especially when the UE has only subscribed to voice services, resulting in low utilization efficiency of network resources and poor user experience.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a terminal resident network management method and a wireless communication system to at least solve the technical problem that in a terminal communication scenario based on IoT NTN, users who have only signed up for voice services need to fall back from a data switching domain network to a circuit switching domain network when making a call, resulting in large latency and low efficiency.

[0005] According to one aspect of an embodiment of the present application, a terminal residency network management method is provided, including: in response to a joint attachment request message of the terminal, obtaining first subscription information of the terminal, wherein the terminal accesses the network based on the IoT NTN, and the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network; determining a first network residency strategy of the terminal after completing circuit switching fallback and voice service interaction based on the first subscription information, wherein the first network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; and sending an attachment acceptance message carrying the first network residency strategy to the terminal.

[0006] Optionally, determining a first network residence strategy of the terminal after completing circuit switching fallback and voice service interaction based on the first signing information includes: when the first signing information indicates that the terminal has signed up for both data service and voice service, determining the first network residence strategy to be switching back to the data switching domain network; when the first signing information indicates that the terminal has only signed up for voice service, determining the first network residence strategy to be staying in the circuit switching domain network.

[0007] Optionally, obtaining the first subscription information of the terminal includes: obtaining the first subscription information of the terminal from a home user server.

[0008] Optionally, obtaining the first subscription information of the terminal includes: obtaining the first subscription information of the terminal from a mobile switching center or a home location register corresponding to the circuit switching domain network.

[0009] Optionally, sending an attachment acceptance message carrying a first network residency policy to the terminal includes: sending an attachment acceptance message carrying a first parameter to the terminal, wherein the first parameter is used to indicate the first network residency policy, and the first parameter is a custom parameter newly added in the attachment acceptance message or is modified based on a reserved bit parameter in the attachment acceptance message.

[0010] Optionally, the method further includes: when the first subscription information indicates that the terminal has only subscribed to voice service, sending a joint attachment failure message carrying a failure cause value to the terminal, wherein the failure cause value is used to indicate that the terminal has only subscribed to voice service.

[0011] Optionally, the method also includes: receiving an inserted subscription data request message from a home user server or a home location register, wherein the inserted subscription data message carries a second contract information after the terminal is changed; determining a second network residence strategy of the terminal after completing circuit switching fallback and voice service interaction based on the second contract information, wherein the second network residence strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; sending a first request message carrying the second network residence strategy to the terminal for triggering the terminal to perform a location update or service request.

[0012] Optionally, the second network residence strategy of the terminal after completing the circuit switching fallback and voice service interaction is determined based on the second signing information, including: when the second signing information indicates that the terminal has changed to signing up for both data services and voice services, determining the second network residence strategy to switch back to the data switching domain network; when the second signing information indicates that the terminal has changed to signing up for only voice services, determining the second network residence strategy to reside in the circuit switching domain network.

[0013] Optionally, sending a first request message carrying a second network residence policy to trigger the terminal to perform a location update or service request includes: sending a first request message carrying a second parameter to the terminal, wherein the second parameter is used to indicate the second network residence policy, and the second parameter is a custom parameter newly added in the first request message or is modified based on a reserved bit parameter in the first request message.

[0014] Optionally, the method further includes: receiving a first response message fed back by the terminal in response to the first request message; and sending an insertion subscription data response message to a home subscriber server or a home location register.

[0015] Optionally, the method also includes: when the second signing information indicates that the terminal has changed to signing only for voice service, sending a second request message carrying a failure reason value to the terminal for triggering the terminal to perform location update or service request, wherein the failure reason value is used to indicate that the terminal has signed only for voice service.

[0016] Optionally, the terminal is applied to a terminal based on an IoT NTN access network, including: sending a joint attachment request message to a mobile management network element in a core network, wherein the joint attachment request message is used to request attachment to a data exchange domain network and a circuit switching domain network; receiving an attachment acceptance message sent by the mobile management network element and carrying a first network residence policy, wherein the first network residence policy includes one of the following: switching back to the data exchange domain network, residing in the circuit switching domain network; after completing the circuit switching fallback and voice service interaction, executing the first network residence policy.

[0017] Optionally, the first network residence strategy is determined by the mobile management network element based on the first contract information of the terminal. When the first contract information indicates that the terminal has signed a contract for both data services and voice services, the first network residence strategy is to switch back to the data switching domain network. When the first contract information indicates that the terminal has only signed a contract for voice services, the first network residence strategy is to reside in the circuit switching domain network.

[0018] Optionally, the method also includes: receiving a joint attachment failure message carrying a failure cause value sent by a mobile management network element, wherein the failure cause value is used to indicate that the terminal is only subscribed to voice services; identifying the failure cause value, and re-sending an attachment request message to the mobile management network element, wherein the attachment request message is used to request attachment to the circuit switching domain network.

[0019] Optionally, the method also includes: receiving a first request message sent by a mobile management network element and carrying a second network residence policy for triggering the terminal to perform a location update or service request, wherein the second network residence policy includes one of the following: switching back to the data exchange domain network, residing in the circuit switching domain network; executing the second network residence policy in an idle state; sending a first response message corresponding to the first request message to the mobile management network element.

[0020] Optionally, the second network residence strategy is determined by the mobile management network element based on the second contract information after the terminal is changed. When the second contract information indicates that the terminal is changed to sign a contract for data service and voice service, the second network residence strategy is to switch back to the data exchange domain network. When the second contract information indicates that the terminal is changed to sign a contract for only voice service, the second network residence strategy is to reside in the circuit switching domain network.

[0021] Optionally, the method also includes: receiving a second request message sent by a mobile management network element and carrying a failure cause value for triggering the terminal to perform a location update or service request, wherein the failure cause value is used to indicate that the terminal changes to only contract for voice services; identifying the failure cause value, switching to a circuit switching domain network in an idle state; and sending a second response message corresponding to the second request message to the mobile management network element.

[0022] According to another aspect of an embodiment of the present application, a wireless communication system is also provided, including: a mobile management network element in a core network and a terminal based on an IoT NTN access network, wherein the terminal is used to send a joint attachment request message to the mobile management network element, wherein the joint attachment request message is used to request attachment to a data exchange domain network and a circuit switching domain network; the mobile management network element is used to respond to the joint attachment request message and obtain the first contract information of the terminal; determine a first network residence strategy of the terminal after completing circuit switching fallback and voice service interaction based on the first contract information, wherein the first network residence strategy includes one of the following: switching back to the data exchange domain network, residing in the circuit switching domain network; the terminal is also used to execute the first network residence strategy after completing circuit switching fallback and voice service interaction.

[0023] Optionally, the mobile management network element is used to determine that the first network residence strategy is to switch back to the data switching domain network when the first subscription information indicates that the terminal has subscribed to both data service and voice service; and to determine that the first network residence strategy is to reside in the circuit switching domain network when the first subscription information indicates that the terminal has subscribed to only voice service.

[0024] Optionally, the mobile management network element is used to send a joint attachment failure message carrying a failure cause value to the terminal when the first subscription information indicates that the terminal has only subscribed to voice service, wherein the failure cause value is used to indicate that the terminal has only subscribed to voice service; the terminal is used to identify the failure cause value and re-send an attachment request message to the mobile management network element, wherein the attachment request message is used to request attachment to the circuit switching domain network.

[0025] Optionally, a mobile management network element is used to receive an inserted subscription data request message from a home user server or a home location register, wherein the inserted subscription data message carries a second contract information after the terminal is changed; determine a second network residence strategy of the terminal after completing circuit switching fallback and voice service interaction based on the second contract information, wherein the second network residence strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; sending a first request message carrying the second network residence strategy to the terminal to trigger the terminal to perform a location update or service request; the terminal is used to execute the second network residence strategy in an idle state; and send a first response message corresponding to the first request message to the mobile management network element.

[0026] Optionally, the mobile management network element is used to determine that the second network residence strategy is to switch back to the data switching domain network when the second signing information indicates that the terminal has changed to signing a contract for both data and voice services; and to determine that the second network residence strategy is to reside in the circuit switching domain network when the second signing information indicates that the terminal has changed to signing a contract for only voice services.

[0027] Optionally, the mobile management network element is used to send a second request message carrying a failure cause value to the terminal for triggering the terminal to perform a location update or service request when the second subscription information indicates that the terminal has changed to only subscribe to voice services, wherein the failure cause value is used to indicate that the terminal has only subscribed to voice services; the terminal is used to identify the failure cause value and switch to the circuit switching domain network in an idle state; and send a second response message corresponding to the second request message to the mobile management network element.

[0028] According to another aspect of an embodiment of the present application, a computer program product is further provided, the computer program product comprising: a computer program, wherein when the computer program is executed by a processor, the above-mentioned terminal resident network management method is implemented.

[0029] According to another aspect of an embodiment of the present application, an electronic device is further provided, the electronic device comprising: a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the above-mentioned terminal resident network management method through the computer program.

[0030] In an embodiment of the present application, when the terminal sends a joint attachment request message requesting simultaneous access to a data exchange domain network (such as LTE) and a circuit switching domain network (such as 2G / 3G), the mobile management network element can respond quickly and obtain the first contract information of the terminal, so that the mobile management network element can make more accurate and timely decisions based on the actual contract status of the terminal (including voice, data services or a combination thereof), thereby avoiding unnecessary waste of network resources and user service interruption; the mobile management network element automatically determines the best network residence strategy for the terminal after completing the circuit switching fallback and voice service interaction based on the first contract information. This strategy can be to switch back to the data exchange domain network to continue the data service, or to reside in the circuit switching domain network to maintain the continuity of the voice service, avoiding a "one-size-fits-all" network management strategy, making the allocation of network resources more reasonable and the user experience more optimized; the mobile management network element sends an attachment acceptance message carrying the first network residence strategy to the terminal, ensuring that the terminal can efficiently and unimpededly execute the network residence strategy according to its own business needs and network instructions. This method enhances the communication efficiency between the network and the terminal, ensures the execution effect of the network decision, and thus solves the IoT-based In the terminal communication scenario of NTN, users who have only signed up for voice services need to fall back from the data switching domain network to the circuit switching domain network when making calls, which causes technical problems such as high latency and low efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0032] Figure 1 is a schematic diagram of the structure of an optional wireless communication system according to an embodiment of the present application;

[0033] Figure 2 is a schematic diagram of a process of determining and executing a first network residency strategy between an optional terminal and a mobility management network element according to an embodiment of the present application;

[0034] Figure 3 It is a schematic diagram of an optional process of transmitting a joint attachment failure message between a terminal and a mobility management network element according to an embodiment of the present application;

[0035] Figure 4is a schematic diagram of a process of determining and executing a second network residency strategy between an optional terminal and a mobility management network element according to an embodiment of the present application;

[0036] Figure 5 It is a flowchart of an optional terminal resident network management method according to an embodiment of the present application;

[0037] Figure 6 It is a flowchart of an optional terminal resident network management method according to an embodiment of the present application;

[0038] Figure 7 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0040] It should be noted that the terms "first", "second", etc. in the specification, claims and drawings of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0041] Example 1

[0042] According to an embodiment of the present application, a wireless communication system is also provided. Figure 1 As shown, the wireless communication system at least includes: a mobile management network element 11 in the core network and a terminal 12 based on the IoT NTN access network, wherein:

[0043] The terminal 12 runs under the IoT NTN access network and can simultaneously request to attach to the data exchange domain network and the circuit switching domain network to support data and voice services. The terminal 12 can also identify the network residence policy indication in the attachment acceptance or failure message sent by the mobile management network element 11, and make corresponding network selection actions based on the indication, such as switching back to the data exchange domain network (such as LTE) after the voice service ends or continuing to reside in the circuit switching domain network (such as 2G / 3G). The mobile management network element 11 receives and responds to the joint attachment request of the terminal 12, and dynamically determines the network residence policy of the terminal after completing the circuit switching fallback and voice service interaction according to the acquired contract information. The mobile management network element 11 can also interact with the terminal 12 by sending an attachment acceptance or failure message carrying an indication policy to ensure that its communication behavior complies with the network policy and user service requirements. When the contract information changes, the mobile management network element 11 can also determine the corresponding network residence policy of the terminal 12 based on the changed contract information or send a request message with a failure reason value for triggering the terminal to perform a location update or service request. The terminal 11 receives and executes the corresponding policy or responds.

[0044] The functions of the various components of the wireless communication system are described below in conjunction with a specific implementation process.

[0045] When the terminal initiates a joint attachment request, the mobility management network element determines the terminal's residence strategy after completing the CSFB and voice service interaction based on the terminal's subscription information. The following are the system's execution steps in this process:

[0046] In this process, the mobility management network elements include: MME (Mobility Management Entity).

[0047] S11, the terminal sends a joint attachment request message to a mobility management network element in the core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network.

[0048] For example, when the UE needs data and voice services, it sends an Attach Request to the MME, requesting to attach to both the data switching domain network and the circuit switching domain network. The request message includes the UE's identity information, the UE's capability information (such as supported network types), and an indication of requesting a joint attachment.

[0049] S12, the mobility management network element in the core network obtains the first subscription information of the terminal in response to the joint attachment request message of the terminal.

[0050] To obtain the first subscription information of the terminal, the following steps may be adopted: obtaining the first subscription information of the terminal from a home user server, or obtaining the first subscription information of the terminal from a mobile switching center or a home location register corresponding to a circuit switching domain network.

[0051] For example, after the eNodeB receives the joint attachment request message from the UE, the MME starts to process the joint attachment request. In order to determine whether the UE can indeed perform joint attachment and CSFB, the MME needs to obtain the UE's contract information, that is, the service information signed by the UE in the operator's network (whether it includes data and voice services). The MME sends a request to the HSS to obtain the UE's contract information from the HSS. The HSS stores all the UE's contracted service information, including authorization information for voice and data services, and network access restrictions. The HSS returns the UE's contract data to the MME based on the UE's identity information. The MME uses this information to determine whether the UE is allowed to perform joint attachment.

[0052] In addition to obtaining information directly from the HSS, the MME can also initiate a request to the MSC (Mobile Switching Center) or HLR (Home Location Register) to obtain the UE's subscription information. The MSC and HLR are part of the circuit switching domain network and are used to store user information and subscription information in the current visited area. By querying the MSC / HLR, the MME can obtain detailed information on whether the user has signed a voice service contract in the current network, which is crucial for decisions on CSFB and joint attachment.

[0053] S13, the mobility management network element in the core network determines, based on the first subscription information, a first network residence strategy of the terminal after completing the circuit switching fallback and voice service interaction, wherein the first network residence strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network, and the process can be performed in the following steps:

[0054] When the first subscription information indicates that the terminal has subscribed to both data and voice services, the first network residency strategy is determined to be switching back to the data switching domain network; when the first subscription information indicates that the terminal has only subscribed to the voice service, the first network residency strategy is determined to be staying in the circuit switching domain network.

[0055] For example, based on the first subscription information obtained from the HSS or MSC / HLR, the MME determines whether the UE has subscribed to data and voice services, and whether the UE is allowed to perform a joint attachment. If the UE has subscribed to data and voice services, the MME will allow the UE's joint attachment request and perform subsequent CSFB and attachment procedures. If the UE has only subscribed to voice services, the MME may need to adjust its processing strategy to ensure that the UE remains in the 2 / 3G network after completing the voice call, rather than returning to the LTE network unnecessarily.

[0056] S14, the mobility management network element in the core network sends an attachment acceptance message carrying the first network residence policy to the terminal. The process may be performed in the following steps:

[0057] An attach accept message carrying a first parameter is sent to the terminal, where the first parameter is used to indicate a first network residency strategy, and the first parameter is a custom parameter newly added in the attach accept message or modified based on a reserved bit parameter in the attach accept message.

[0058] S15, the terminal receives an attach accept message carrying the first network residency policy sent by the mobility management network element.

[0059] S16, after completing the circuit switching fallback and voice service interaction, executing the first network resident strategy.

[0060] For example, the MME responds to the UE's joint attach request message based on its decision and sends an attach accept message. For UEs subscribed to data and voice services, the attach accept message will include indication information to inform the UE that it can directly return to the LTE network to continue data services after completing voice communication.

[0061] The above process can refer to Figure 2 The execution process, in Figure 2 In the joint attach process 1, the MME interacts with the HSS or MSC / HLR to obtain the first subscription information of the UE, and the joint attach process 2 represents the joint attach process related to clause 5.6 of 3GPP TS 23.401[2].

[0062] When a terminal attempts to jointly attach to a data switching domain network (i.e., an LTE network) and a circuit switching domain network (i.e., a 2G / 3G network), if it is found that the terminal has only subscribed to a voice service, the steps for the mobility management network element in the core network to respond to and process this situation may be as follows:

[0063] In this process, the mobility management network elements include: MME.

[0064] S21, the terminal sends a joint attachment request message to a mobility management network element in the core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network.

[0065] S22, the mobility management network element in the core network obtains the first subscription information of the terminal in response to the joint attachment request message of the terminal.

[0066] To obtain the first subscription information of the terminal, the following steps may be adopted: obtaining the first subscription information of the terminal from a home user server, or obtaining the first subscription information of the terminal from a mobile switching center or a home location register corresponding to a circuit switching domain network.

[0067] S23, when the first subscription information indicates that the terminal has only subscribed to the voice service, the mobility management network element sends a joint attachment failure message carrying a failure cause value to the terminal, wherein the failure cause value is used to indicate that the terminal has only subscribed to the voice service.

[0068] For example, the failure cause value carried in the combined attach failure message sent by the MME is standardized to ensure that the UE can correctly understand the cause. This cause value may be a specific cause code, for example: only voice services are subscribed, and combined attach is not allowed.

[0069] S24, the terminal receives a joint attachment failure message carrying a failure cause value sent by the mobility management network element, identifies the failure cause value, and resends an attachment request message to the mobility management network element, wherein the attachment request message is used to request attachment to the circuit switching domain network.

[0070] When the attach request message is resent, the attach type in the request message will be modified from Combined EPS / IMSI Attach to CS Attach. The UE protocol stack will handle this change to ensure that the request message correctly reflects the UE's subscription status.

[0071] The above process can refer to Figure 3 The execution process, in Figure 3 In the joint attachment process 1, the MME interacts with the HSS to obtain the first subscription information of the UE. The joint attachment process is specifically defined in 3GPP TS23.272 and 3GPP TS23.401.

[0072] When the subscription information is changed initiated by the HSS or HLR, the MME obtains the changed subscription information (second subscription information) and adjusts the network residence policy of the UE accordingly. The steps in the process may be as follows:

[0073] In this process, the mobility management network elements may include: MME, MSC, VLR (Visitor Location Register), and SGSN (Serving GPRS Support Node).

[0074] S31, the mobility management network element receives an insertion subscription data request message from a home subscriber server or a home location register, wherein the insertion subscription data message carries the second subscription information after the terminal is changed;

[0075] For example, the MME receives an insert subscription data request message from the HSS or HLR, which indicates that the UE's subscription information has changed, and the request message carries the changed second subscription information of the UE, that is, the latest service subscription status. This may be because the UE has updated its service plan or service type at the operator, such as switching from voice-only service to data and voice service, or vice versa, from data+voice to voice-only service.

[0076] S32, the mobility management network element determines a second network residency strategy of the terminal after completing the circuit switching fallback and voice service interaction according to the second subscription information, wherein the second network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network, and the process can be performed in the following steps:

[0077] When the second subscription information indicates that the terminal has changed to signing up for both data and voice services, the second network residency strategy is determined to be switching back to the data switching domain network; when the second subscription information indicates that the terminal has changed to signing up for only voice services, the second network residency strategy is determined to be staying in the circuit switching domain network.

[0078] For example, after receiving a change in contract information, the MME determines the network residence strategy after completing the CSFB and voice service interaction based on the UE's new contract status (second contract information), that is, whether the UE should return to the data switching domain network (LTE) or continue to reside in the circuit switching domain network (2 / 3G).

[0079] S33, the mobility management network element sends a first request message carrying a second network residence policy to the terminal for triggering the terminal to perform location update or service request. The process may be performed in the following steps:

[0080] A first request message carrying a second parameter is sent to the terminal, wherein the second parameter is used to indicate a second network residency strategy, and the second parameter is a custom parameter newly added in the first request message or modified based on a reserved parameter in the first request message.

[0081] For example, the MME will trigger the UE to perform location update or service request by sending a first request message with a second parameter according to the determined network residence strategy, where the second parameter is a custom parameter used to indicate the second network residence strategy determined by the MME. The second parameter may be a modification of a reserved bit, for example, adding a new bit or modifying an existing bit in an existing field in a Location Area Update or Service Request message to indicate the network residence strategy, or it may be a newly added custom parameter specifically used to transmit network residence strategy information.

[0082] S35, the terminal receives a first request message sent by the mobility management network element and carrying a second network residency policy for triggering the terminal to perform location update or service request;

[0083] If the UE should switch back to the data switching domain network, the MME sets the second parameter in the first request message to switch back to LTE, and if the UE should stay in the circuit switching domain network, the second parameter is set to stay in 2 / 3G.

[0084] For example, the first request message may be a location update request, such as Location Area Update or Tracking Area Update, or a Service Request message, depending on the current state of the UE and network policy.

[0085] S36, the terminal executes the second network residence strategy in the idle state, and sends a first response message corresponding to the first request message to the mobility management network element;

[0086] For example, the UE sends a first response message to the MME to confirm that it has performed corresponding network residence or switching according to the second network residence policy. This response message may be Location Area Update Accept or Service RequestAcknowledgement, depending on the type of the first request message to which the UE responds.

[0087] S37: The mobility management network element receives a first response message fed back by the terminal in response to the first request message, and sends an insertion subscription data response message to the home subscriber server or the home location register.

[0088] After receiving the confirmation from the UE, the MME sends an Insert Subscriber Data Answer to the HSS or HLR to confirm that the UE has taken action based on the new subscription information and network residency policy.

[0089] The above process can refer to Figure 4 The execution process.

[0090] When the MME receives a subscription information change of the UE from the HSS or HLR, indicating that the UE has only subscribed to the voice service, the MME sends a request message carrying a failure cause value to the UE, prompting the UE to switch to the circuit switched domain network. The process may include the following steps:

[0091] In this process, the mobility management network elements include: MME, MSC, VLR, and SGSN.

[0092] S41, the mobility management network element receives an insertion subscription data request message from a home subscriber server or a home location register, wherein the insertion subscription data message carries the second subscription information after the terminal is changed;

[0093] S42, when the second subscription information indicates that the terminal has changed to only subscribe to voice services, the mobile management network element sends a second request message carrying a failure cause value to the terminal for triggering the terminal to update the location or request a service, wherein the failure cause value is used to indicate that the terminal has only subscribed to voice services.

[0094] For example, if the MME finds in the second subscription information that the UE has only subscribed to voice services and has no data service rights, the MME will notify the UE by sending a second request message with a specific failure cause value. This second request message can be a Service Request, Attach Request, or Location Update Request, depending on the current state and action of the UE. The failure cause value is a code indicating that the UE has only subscribed to voice services, which tells the UE that the current data exchange domain network (such as LTE) is not suitable for its only voice service needs.

[0095] S43, the terminal receives a second request message sent by the mobility management network element and carrying a failure cause value for triggering the terminal to perform a location update or service request, wherein the failure cause value is used to indicate that the terminal is changed to a voice service only contract;

[0096] S44, the terminal identifies the failure reason value and switches to the circuit switching domain network in the idle state;

[0097] For example, after the terminal identifies the failure cause value in the second request message, the UE will switch to the circuit switching domain network (such as 2 / 3G network) in the idle state. Because it no longer has the authority to reside and perform data services in the data switching domain network (such as LTE), switching to the circuit switching domain network may involve the UE performing a series of network access and attachment steps to ensure that it can receive services in the new network.

[0098] S45, the terminal sends a second response message corresponding to the second request message to the mobility management network element.

[0099] In an embodiment of the present application, when the terminal sends a joint attachment request message requesting simultaneous access to a data exchange domain network (such as LTE) and a circuit switching domain network (such as 2G / 3G), the mobile management network element can respond quickly and obtain the first contract information of the terminal, so that the mobile management network element can make more accurate and timely decisions based on the actual contract status of the terminal (including voice, data services or a combination thereof), thereby avoiding unnecessary waste of network resources and user service interruption; the mobile management network element automatically determines the best network residence strategy for the terminal after completing the circuit switching fallback and voice service interaction based on the first contract information. This strategy can be to switch back to the data exchange domain network to continue the data service, or to reside in the circuit switching domain network to maintain the continuity of the voice service, avoiding a "one-size-fits-all" network management strategy, making the allocation of network resources more reasonable and the user experience more optimized; the mobile management network element sends an attachment acceptance message carrying the first network residence strategy to the terminal, ensuring that the terminal can efficiently and unimpededly execute the network residence strategy according to its own business needs and network instructions. This method enhances the communication efficiency between the network and the terminal, ensures the execution effect of the network decision, and thus solves the IoT-based In the terminal communication scenario of NTN, users who have only signed up for voice services need to fall back from the data switching domain network to the circuit switching domain network when making calls, which causes technical problems such as high latency and low efficiency.

[0100] Example 2

[0101] According to an embodiment of the present application, a terminal resident network management method is provided, which is applied to a mobile management network element in a core network. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0102] Figure 5 is a flow chart of a terminal resident network management method provided according to an embodiment of the present application, such as Figure 5 As shown, the method comprises the following steps:

[0103] Step S502, in response to a joint attachment request message of the terminal, obtaining first subscription information of the terminal, wherein the terminal accesses the network based on the IoT NTN, and the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network;

[0104] Step S504, determining a first network residency strategy of the terminal after completing circuit switching fallback and voice service interaction according to the first subscription information, wherein the first network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network;

[0105] Step S506: Send an attach accept message carrying the first network residency policy to the terminal.

[0106] The following describes each step of the terminal resident network management method in conjunction with a specific implementation process.

[0107] In response to the joint attachment request message of the terminal, the mobility management network element in the core network obtains the first subscription information of the terminal, wherein the terminal accesses the network based on the IoT NTN, and the joint attachment request message is used to request attachment to the data switching domain network and the circuit switching domain network;

[0108] Among them, the first subscription information of the terminal can be obtained by taking the following steps: obtaining the first subscription information of the terminal from a home user server, or obtaining the first subscription information of the terminal from a mobile switching center or a home location register corresponding to a circuit switching domain network.

[0109] The mobility management network element in the core network determines, based on the first subscription information, a first network residency strategy of the terminal after completing circuit switching fallback and voice service interaction, wherein the first network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network;

[0110] Among them, the mobile management network element in the core network determines the first network residence strategy of the terminal after completing the circuit switching fallback and voice service interaction based on the first signing information, and can take the following steps: when the first signing information indicates that the terminal has signed up for both data services and voice services, the first network residence strategy is determined to be switching back to the data switching domain network; when the first signing information indicates that the terminal has only signed up for voice services, the first network residence strategy is determined to be staying in the circuit switching domain network.

[0111] The mobile management network element in the core network sends an attachment acceptance message carrying a first network residence policy to the terminal. The process can be carried out in the following steps: sending an attachment acceptance message carrying a first parameter to the terminal, wherein the first parameter is used to indicate the first network residence policy, and the first parameter is a custom parameter newly added in the attachment acceptance message or is modified based on the reserved bit parameter in the attachment acceptance message.

[0112] In addition, there is the following method: when the first signing information indicates that the terminal is only subscribed to voice services, the mobile management network element in the core network sends a joint attachment failure message carrying a failure cause value to the terminal, wherein the failure cause value is used to indicate that the terminal is only subscribed to voice services.

[0113] When receiving an Interactive Subscription Data Request message from a Home Subscriber Server or Home Location Register, the following steps are taken:

[0114] The mobility management network element in the core network receives an insertion subscription data request message from a home subscriber server or a home location register, wherein the insertion subscription data message carries the second subscription information after the terminal is changed.

[0115] The mobility management network element in the core network determines, based on the second subscription information, a second network residency strategy of the terminal after completing the circuit switching fallback and the voice service interaction, wherein the second network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network;

[0116] Among them, when the second signing information indicates that the terminal has changed to signing a contract for both data and voice services, the second network residence strategy is determined to switch back to the data exchange domain network; when the second signing information indicates that the terminal has changed to signing a contract for only voice services, the second network residence strategy is determined to reside in the circuit switching domain network.

[0117] The mobile management network element in the core network sends a first request message carrying a second network residence policy to the terminal to trigger the terminal to update its location or request a service. The process can be carried out in the following steps: sending a first request message carrying a second parameter to the terminal, wherein the second parameter is used to indicate the second network residence policy, and the second parameter is a custom parameter newly added in the first request message or is modified based on a reserved bit parameter in the first request message.

[0118] The mobility management network element in the core network receives a first response message fed back by the terminal in response to the first request message, and sends an insertion subscription data response message to the home subscriber server or the home location register.

[0119] In the above process, when the second subscription information indicates that the terminal has changed to only subscribe to voice services, the mobile management network element in the core network sends a second request message carrying a failure cause value to the terminal for triggering the terminal to update the location or request a service, wherein the failure cause value is used to indicate that the terminal has only subscribed to voice services.

[0120] It should be noted that the implementation steps of the terminal resident network management method in the embodiment of the present application correspond one by one to the implementation steps of the wireless communication system in Example 1. Since a detailed description has been given in Example 1, some details not reflected in this embodiment can be referred to Example 1 and will not be repeated here.

[0121] Example 3

[0122] According to an embodiment of the present application, a terminal resident network management method is provided, which is applied to a terminal based on an IoT NTN access network. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0123] Figure 6 is a flow chart of a terminal resident network management method provided according to an embodiment of the present application, such as Figure 6 As shown, the method comprises the following steps:

[0124] Step S602, sending a joint attachment request message to a mobility management network element in the core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network;

[0125] Step S604: receiving an attachment acceptance message carrying a first network residency policy sent by a mobility management network element, wherein the first network residency policy includes one of the following: switching back to a data switching domain network, residing in a circuit switching domain network;

[0126] Step S606: After completing the circuit switching fallback and voice service interaction, execute the first network residence strategy.

[0127] The following describes each step of the terminal resident network management method in conjunction with a specific implementation process.

[0128] The terminal sends a joint attachment request message to a mobility management network element in the core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network.

[0129] The terminal receives an attachment acceptance message carrying a first network residency policy sent by a mobility management network element, wherein the first network residency policy includes one of the following: switching back to a data switching domain network and residing in a circuit switching domain network.

[0130] Among them, the first network residence strategy is determined by the mobile management network element based on the first contract information of the terminal. When the first contract information indicates that the terminal has signed a contract for both data services and voice services, the first network residence strategy is to switch back to the data exchange domain network. When the first contract information indicates that the terminal has only signed a contract for voice services, the first network residence strategy is to reside in the circuit switching domain network.

[0131] After completing the circuit switching fallback and voice service interaction, the terminal executes the first network resident strategy.

[0132] In the above process, the terminal receives a joint attachment failure message carrying a failure cause value sent by the mobile management network element, wherein the failure cause value is used to indicate that the terminal is only subscribed to voice services, and identifies the failure cause value, and re-sends an attachment request message to the mobile management network element, wherein the attachment request message is used to request attachment to the circuit switching domain network.

[0133] When the second contract information changes, you can take the following steps:

[0134] A first request message carrying a second network residency policy for triggering a terminal to perform location update or service request is received from a mobility management network element, wherein the second network residency policy includes one of the following: switching back to a data switching domain network, and residing in a circuit switching domain network.

[0135] Among them, the second network residence strategy is determined by the mobile management network element based on the second contract information after the terminal is changed. When the second contract information indicates that the terminal is changed to sign a contract for data service and voice service, the second network residence strategy is to switch back to the data exchange domain network. When the second contract information indicates that the terminal is changed to sign a contract for only voice service, the second network residence strategy is to reside in the circuit switching domain network.

[0136] After receiving the request, the terminal executes the second network residence strategy in the idle state, and sends a second response message corresponding to the second request message to the mobility management network element.

[0137] It should be noted that the implementation steps of the terminal resident network management method in the embodiment of the present application correspond one by one to the implementation steps of the wireless communication system in Example 1. Since a detailed description has been given in Example 1, some details not reflected in this embodiment can be referred to Example 1 and will not be repeated here.

[0138] Example 4

[0139] According to an embodiment of the present application, a computer program product is also provided, which includes a computer program, wherein when the computer program is executed by a processor, the terminal resident network management method in Example 2 or Example 3 is implemented.

[0140] According to an embodiment of the present application, a non-volatile storage medium is also provided, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the terminal resident network management method in Example 2 or Example 3 by running the computer program.

[0141] According to an embodiment of the present application, a processor is also provided, which is used to run a computer program, wherein the terminal resident network management method in Example 2 or Example 3 is executed when the computer program is running.

[0142] According to an embodiment of the present application, an electronic device is also provided, which includes: a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the terminal resident network management method in Example 2 or Example 3 through the computer program.

[0143] Specifically, when the computer program is running, the following steps can be executed: in response to a joint attachment request message of the terminal, the first contract information of the terminal is obtained, wherein the terminal accesses the network based on the IoT NTN, and the joint attachment request message is used to request attachment to the data exchange domain network and the circuit switching domain network; based on the first contract information, a first network residence strategy of the terminal after completing the circuit switching fallback and voice service interaction is determined, wherein the first network residence strategy includes one of the following: switching back to the data exchange domain network, residing in the circuit switching domain network; and sending an attachment acceptance message carrying the first network residence strategy to the terminal.

[0144] Specifically, when the computer program is running, the following steps can be executed: sending a joint attachment request message to a mobile management network element in a core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network; receiving an attachment acceptance message sent by the mobile management network element and carrying a first network residence policy, wherein the first network residence policy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; after completing the circuit switching fallback and voice service interaction, executing the first network residence policy.

[0145] As an optional implementation, the electronic device may be in the form of a mobile terminal, a computer terminal or a similar computing device. Figure 7 The hardware structure block diagram of an electronic device for implementing the terminal resident network management method is shown. Figure 7 As shown, the electronic device 70 may include one or more (shown as 702a, 702b, ..., 702n in the figure) processors 702 (the processor 702 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 704 for storing data, and a transmission device 706 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 7 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 7 More or fewer components as shown, or with Figure 7 Different configurations are shown.

[0146] It should be noted that the one or more processors 702 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the electronic device 70. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0147] The memory 704 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the terminal resident network management method in the embodiment of the present application. The processor 702 executes various functional applications and data processing by running the software programs and modules stored in the memory 704, that is, realizing the vulnerability detection method of the above-mentioned application. The memory 704 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 704 may further include a memory remotely arranged relative to the processor 702, and these remote memories may be connected to the electronic device 70 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0148] The transmission device 706 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the electronic device 70. In one example, the transmission device 706 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 706 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0149] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the electronic device 70 .

[0150] The serial numbers of the above embodiments are only for description and do not represent the advantages or disadvantages of the embodiments.

[0151] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0152] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0153] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0154] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0155] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0156] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A terminal resident network management method, applied to a mobility management network element in a core network, characterized in that: include: In response to a joint attachment request message of a terminal, acquiring first subscription information of the terminal, wherein the terminal accesses a network based on an Internet of Things non-terrestrial network IoT NTN, and the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network; Determining, according to the first subscription information, a first network residency strategy of the terminal after completing circuit switching fallback and voice service interaction, wherein the first network residency strategy includes one of the following: switching back to a data switching domain network, residing in a circuit switching domain network; An attach accept message carrying the first network residency policy is sent to the terminal.

2. The method according to claim 1, characterized in that Determining, according to the first subscription information, a first network residence strategy of the terminal after completing circuit switching fallback and voice service interaction, includes: When the first subscription information indicates that the terminal subscribes to both the data service and the voice service, determining that the first network residency strategy is to switch back to the data exchange domain network; When the first subscription information indicates that the terminal has only subscribed to the voice service, the first network residency strategy is determined to reside in a circuit switched domain network.

3. The method according to claim 1, characterized in that Acquiring first subscription information of the terminal, including: The first subscription information of the terminal is obtained from the home subscriber server.

4. The method according to claim 1, characterized in that Acquiring first subscription information of the terminal, including: The first subscription information of the terminal is obtained from a mobile switching center or a home location register corresponding to the circuit switching domain network.

5. The method according to claim 1, characterized in that Sending an attachment acceptance message carrying the first network residency policy to the terminal includes: An attachment acceptance message carrying a first parameter is sent to the terminal, wherein the first parameter is used to indicate the first network residence strategy, and the first parameter is a custom parameter newly added in the attachment acceptance message or modified based on a reserved bit parameter in the attachment acceptance message.

6. The method according to claim 1, characterized in that The method further comprises: In a case where the first subscription information indicates that the terminal has only subscribed to the voice service, a joint attachment failure message carrying a failure cause value is sent to the terminal, wherein the failure cause value is used to indicate that the terminal has only subscribed to the voice service.

7. The method according to claim 1, characterized in that The method further comprises: Receiving an insertion subscription data request message from a home subscriber server or a home location register, wherein the insertion subscription data message carries the changed second subscription information of the terminal; Determine, according to the second subscription information, a second network residency strategy of the terminal after completing circuit switching fallback and voice service interaction, wherein the second network residency strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; A first request message carrying the second network residency policy and used to trigger the terminal to perform location update or service request is sent to the terminal.

8. The method according to claim 7, characterized in that Determining, according to the second subscription information, a second network residency strategy of the terminal after completing circuit switching fallback and voice service interaction, includes: When the second subscription information indicates that the terminal is changed to subscribe to both the data service and the voice service, determining that the second network residency strategy is to switch back to the data exchange domain network; When the second subscription information indicates that the terminal is changed to subscribe to only the voice service, the second network residency strategy is determined to reside in the circuit switching domain network.

9. The method according to claim 7, characterized in that: Sending a first request message carrying the second network residency policy to the terminal for triggering the terminal to perform location update or service request includes: The first request message carrying the second parameter is sent to the terminal, wherein the second parameter is used to indicate the second network residence strategy, and the second parameter is a custom parameter newly added in the first request message or modified based on a reserved bit parameter in the first request message.

10. The method according to claim 7, characterized in that The method further comprises: Receiving a first response message fed back by the terminal in response to the first request message; Send an Interactive Subscription Data Response message to the Home Subscriber Server or the Home Location Register.

11. The method according to claim 7, characterized in that The method further comprises: When the second subscription information indicates that the terminal has changed to signing up for voice service only, a second request message carrying a failure reason value is sent to the terminal to trigger the terminal to perform location update or service request, wherein the failure reason value is used to indicate that the terminal has signed up for voice service only.

12. A terminal resident network management method, applied to a terminal based on an IoT NTN access network, characterized in that: include: Sending a joint attachment request message to a mobility management network element in a core network, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network; Receiving an attachment acceptance message carrying a first network residency policy sent by the mobility management network element, wherein the first network residency policy includes one of the following: switching back to a data switching domain network, residing in a circuit switching domain network; After completing the circuit switching fallback and voice service interaction, the first network residence strategy is executed.

13. The method according to claim 12, characterized in that The first network residence strategy is determined by the mobile management network element based on the first subscription information of the terminal. When the first subscription information indicates that the terminal has subscribed for both data services and voice services, the first network residence strategy is to switch back to the data switching domain network. When the first subscription information indicates that the terminal has only subscribed for voice services, the first network residence strategy is to reside in the circuit switching domain network.

14. The method according to claim 12, characterized in that The method further comprises: receiving a joint attachment failure message carrying a failure cause value sent by the mobility management network element, wherein the failure cause value is used to indicate that the terminal is only subscribed to a voice service; Identify the failure cause value, and resend an attachment request message to the mobility management network element, wherein the attachment request message is used to request attachment to a circuit switched domain network.

15. The method according to claim 12, characterized in that The method further comprises: Receiving a first request message sent by the mobility management network element and carrying a second network residency policy for triggering the terminal to perform a location update or service request, wherein the second network residency policy includes one of the following: switching back to a data switching domain network, residing in a circuit switching domain network; Executing the second network residency strategy in an idle state; Sending a first response message corresponding to the first request message to the mobility management network element.

16. The method according to claim 15, characterized in that The second network residence strategy is determined by the mobile management network element based on the second contract information after the terminal is changed. When the second contract information indicates that the terminal is changed to sign a contract for data service and voice service, the second network residence strategy is to switch back to the data switching domain network; when the second contract information indicates that the terminal is changed to sign a contract for only voice service, the second network residence strategy is to reside in the circuit switching domain network.

17. The method according to claim 12, characterized in that The method further comprises: Receiving a second request message sent by the mobility management network element and carrying a failure cause value for triggering the terminal to perform a location update or service request, wherein the failure cause value is used to indicate that the terminal is changed to a voice service-only subscription; Identify the failure cause value and switch to a circuit switching domain network in an idle state; Send a second response message corresponding to the second request message to the mobility management network element.

18. A wireless communication system, characterized in that: include: Mobile management network elements in the core network and terminals based on IoT NTN access network, among which, The terminal is used to send a joint attachment request message to the mobility management network element, wherein the joint attachment request message is used to request attachment to a data switching domain network and a circuit switching domain network; The mobility management network element is used to respond to the joint attachment request message to obtain the first subscription information of the terminal; determine the first network residence strategy of the terminal after completing the circuit switching fallback and voice service interaction according to the first subscription information, wherein the first network residence strategy includes one of the following: switching back to the data switching domain network, residing in the circuit switching domain network; The terminal is further configured to execute the first network residency strategy after completing circuit switching fallback and voice service interaction.

19. The system according to claim 18, characterized in that The mobile management network element is used to determine that the first network residence strategy is to switch back to the data switching domain network when the first subscription information indicates that the terminal has subscribed for both data service and voice service; and to determine that the first network residence strategy is to reside in the circuit switching domain network when the first subscription information indicates that the terminal has only subscribed for voice service.

20. The system according to claim 18, characterized in that The mobility management network element is configured to send a joint attachment failure message carrying a failure cause value to the terminal when the first subscription information indicates that the terminal has only subscribed to a voice service, wherein the failure cause value is used to indicate that the terminal has only subscribed to a voice service; The terminal is used to identify the failure cause value and resend an attachment request message to the mobility management network element, wherein the attachment request message is used to request attachment to a circuit switching domain network.

21. The system according to claim 18, characterized in that The mobility management network element is configured to receive an inserted subscription data request message from a home user server or a home location register, wherein the inserted subscription data message carries the second subscription information of the terminal after the change; determine, according to the second subscription information, a second network residency strategy of the terminal after completing circuit switching fallback and voice service interaction, wherein the second network residency strategy includes one of the following: switching back to a data switching domain network, residing in a circuit switching domain network; sending a first request message carrying the second network residency strategy to the terminal for triggering the terminal to perform a location update or service request; The terminal is used to execute the second network residence strategy in an idle state; and send a first response message corresponding to the first request message to the mobility management network element.

22. The system according to claim 21, characterized in that The mobile management network element is used to determine that the second network residence strategy is to switch back to the data switching domain network when the second subscription information indicates that the terminal is changed to sign a contract for both data service and voice service; and to determine that the second network residence strategy is to stay in the circuit switching domain network when the second subscription information indicates that the terminal is changed to sign a contract for only voice service.

23. The system according to claim 21, characterized in that The mobility management network element is configured to send a second request message carrying a failure cause value to the terminal for triggering the terminal to perform a location update or a service request when the second subscription information indicates that the terminal has changed to a subscription for only a voice service, wherein the failure cause value is used to indicate that the terminal has only a subscription for a voice service; The terminal is used to identify the failure cause value and switch to the circuit switching domain network in an idle state; and send a second response message corresponding to the second request message to the mobility management network element.

24. A computer program product, characterized in that include: A computer program, wherein when the computer program is executed by a processor, the terminal resident network management method according to any one of claims 1 to 17 is implemented.

25. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the terminal resident network management method according to any one of claims 1 to 17 through the computer program.

Images