Combined attachment methods, devices and electronic equipment

Abstract

This application provides a combined attach method, apparatus, and electronic device, including: receiving an Attach request initiated by a UE; if the Attach request carries first target information related to VoLTE, rejecting the UE from performing combined attach through the SGs interface, wherein the first target information at least indicates that the Attach request is a 4G combined attach request, and the first target information at least indicates that the Attach request is a 4G combined attach request or a 5G combined attach request; if the Attach request does not carry the first target information, allowing the UE to perform combined attach through the SGs interface.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, and in particular to a joint attachment method, apparatus and electronic device. Background Technology

[0002] To ensure user equipment (UE) mobility, the network needs to identify and track the UE's location. When a UE attaches to a Long Term Evolution (LTE) network, it requests LTE Evolved Packet System (EPS) network services to initiate joint attach, i.e., registering its location. After the UE's location is registered with the LTE network, it also performs periodic Tracking Area (TUA) updates. The TUA is the location area registered by the UE with the LTE network. The most important interface during joint attach or TUA update is the SGs interface, which is the interface between the Mobility Management Entity (MME) and the Mobile Switching Center (MSC). Joint attach and TUA updates are completed through this interface and stored on the MSC.

[0003] In some scenarios, Voice over Long-Term Evolution (VoLTE) is a high-speed wireless communication standard for mobile phones and data terminals. VoLTE can carry voice and SMS services in 4G networks without requiring joint attach via the SGs interface. However, in practical applications, even for 4G VoLTE users, when the UE initiates a joint attach request, the LTE network will unconditionally perform joint attach via the SGs interface. This results in the inefficient use of SGs interface and MSC resources, leading to low resource utilization of both. Summary of the Invention

[0004] The purpose of this application is to provide a combined attachment method, apparatus, and electronic device to solve the problem of invalid occupation of SGs interface and MSC resources.

[0005] To solve the above-mentioned technical problems, the embodiments of this application are implemented as follows:

[0006] In a first aspect, embodiments of this application provide a joint attach method, comprising: receiving an Attach request initiated by a UE; if the Attach request carries first target information related to VoLTE, rejecting the UE from performing joint attach through the SGs interface, wherein the first target information at least indicates that the Attach request is a 4G joint attach request; and if the Attach request does not carry the first target information, allowing the UE to perform joint attach through the SGs interface.

[0007] Secondly, embodiments of this application provide a joint attach device, comprising: a receiving module for receiving an Attach request initiated by a UE; a rejecting module for rejecting the UE from performing joint attach via the SGs interface if the Attach request carries first target information related to VoLTE, wherein the first target information at least indicates that the Attach request is a 4G joint attach request or a 5G joint attach request; and an allowing module for allowing the UE to perform joint attach via the SGs interface if the Attach request does not carry the first target information.

[0008] Thirdly, embodiments of this application provide an electronic device, including a processor, a communication interface, a memory, and a communication bus; wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory is used to store computer programs; and the processor is used to execute the programs stored in the memory to implement the joint attachment method steps as described in the first aspect.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the joint attachment method steps as described in the first aspect.

[0010] As can be seen from the technical solutions provided in the above embodiments of this application, by receiving the Attach request initiated by the UE, if the Attach request carries first target information related to VoLTE, the UE is rejected from performing joint attach through the SGs interface. The first target information at least indicates that the Attach request is a 4G joint attach request. If the Attach request does not carry the first target information, the UE is allowed to perform joint attach through the SGs interface. This means that when the Attach request is a VoLTE-related request, the UE is not allowed to perform joint attach. In other words, when the UE performs joint attach, the LTE network will not allow the UE to perform joint attach through the SGs interface if the UE does not meet the joint attach conditions. This will prevent the UE from ineffectively occupying the resources of the SGs interface and MSC, thereby improving the resource utilization of the SGs interface and MSC. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram of a first process of the combined attachment method provided in an embodiment of this application;

[0013] Figure 2 This is a second flowchart illustrating the combined attachment method provided in the embodiments of this application;

[0014] Figure 3 A third flowchart illustrating the combined attachment method provided in the embodiments of this application;

[0015] Figure 4 A schematic diagram of the modular composition of the combined attachment device provided in the embodiments of this application;

[0016] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0017] This application provides a joint attachment method, apparatus, and electronic device that solves the problem of invalid occupation of SGs interface and MSC resources.

[0018] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0019] For example, such as Figure 1 As shown in the figure, this application provides a joint attach method. The executing entity of the method can be a server, which can be an independent server or a server cluster composed of multiple servers. Moreover, the server can be a server capable of joint attach. The joint attach method specifically includes the following steps:

[0020] In step S101, an Attach request initiated by the UE is received.

[0021] Specifically, when a UE needs to access the network, it needs to send a joint attach request message to the MME, i.e., an attach request, to perform joint attach.

[0022] In step S102, if the Attach request carries first target information related to VoLTE, the UE is denied joint attach via the SGs interface. If the Attach request does not carry first target information, the UE is allowed to perform joint attach via the SGs interface.

[0023] Specifically, the first target information at least indicates that the Attach request is a 4G combined attach request. This first target information includes, but is not limited to, the second type of the Attach request related to VoLTE and the values ​​of VoLTE-related cells. The second type of the Attach request related to VoLTE includes, but is not limited to, a 4G combined attach request, which may include combined EPS attach and combined IMSI attach. The VoLTE-related cells may be voice domain preference and UE's Usage Setting cells, and the values ​​of the VoLTE-related cells include, but are not limited to, IMS PS voice preferred and IMS PS voice only.

[0024] Furthermore, a `VOLTE_USER_Indication` variable can be set as the primary variable in the MME. When the user is identified as a non-VoLTE user, the `VOLTE_USER_Indication` variable is set to 0, and the MME can perform joint attach normally through the SGs interface after the UE initiates an attach request. When the user is identified as a VoLTE user, the `VOLTE_USER_Indication` variable is set to 1, and the MME will not allow joint attach through the SGs interface after the UE initiates an attach request.

[0025] Upon receiving an Attach request, if the second type of the Attach request is a 4G joint attach request, it indicates that the UE is in a 4G network environment, and the VOLTE_USER_Indication variable is set to 1. If the second type of the Attach request is not a 4G joint attach request, it indicates that the UE is not in a 4G network environment, and the VOLTE_USER_Indication variable is set to 0. If the UE is in a 4G network environment, it is further determined whether the Attach request carries VoLTE-related information. If it does, it indicates that in a 4G network environment, voice services can be conducted via VoLTE without needing joint attach via SGs, and the VOLTE_USER_Indication variable is set to 1. In this case, joint attach via the SGs interface is rejected. If the Attach request does not carry VoLTE-related information, it indicates that joint attach via SGs is required, and the VOLTE_USER_Indication variable is set to 0. In this case, joint attach via the SGs interface is allowed.

[0026] Therefore, the first target information can be used to distinguish whether the UE user is a VoLTE user. If the UE user is a VoLTE user and is in a 4G network environment, it can complete voice and other services through VoLTE without needing to perform joint attach. Therefore, the UE is rejected from performing joint attach, thus performing joint attach differently to avoid occupying SGs interface and MSC resources.

[0027] As can be seen from the technical solutions provided in the embodiments of this application above, when the Attach request is a VoLTE-related request, the UE is not allowed to perform joint attach. In other words, when the UE performs joint attach, the LTE network will not allow the UE to perform joint attach through the SGs interface if the UE does not meet the joint attach conditions. This achieves differentiated joint attach, thus avoiding the ineffective occupation of SGs interface and MSC resources, improving the resource utilization of SGs interface and MSC. By performing differentiated joint attach, VoLTE users in 4G networks do not need to perform SGs interface process judgments, reducing network signaling processes and shortening signaling latency. Furthermore, the resources of SGs interface and MSC will not be occupied for a long time, reducing network costs and ensuring that non-VoLTE users can use SGs interface and MSC resources normally, achieving optimal matching of network resource utilization.

[0028] In one possible implementation, before rejecting the UE's joint attach through the SGs interface, the joint attach method further includes: obtaining the Home Subscriber Server (HSS) subscription data of the user corresponding to the UE. Rejecting the UE's joint attach through the SGs interface includes: if the HSS subscription data contains VoLTE service subscription data, then rejecting the UE's joint attach through the SGs interface.

[0029] Specifically, after identifying whether a UE user is a VoLTE user through the initial target information, in order to further determine whether the user has subscribed to the VoLTE service and thus provide a better service experience, the system further checks whether the user's HSS subscription data contains VoLTE service subscription data. If the HSS subscription data contains VoLTE service subscription data, it means that the user has indeed subscribed to the VoLTE service, and VOLTE_USER_Indication is set to 1, thus rejecting the UE's joint attach attempt via the SGs interface. If the HSS subscription data does not contain VoLTE service subscription data, VOLTE_USER_Indication is set to 0, allowing the UE to perform joint attach through the SGs interface. This further distinguishes whether the user has truly subscribed to the VoLTE service, improving the accuracy of identifying whether a user is a VoLTE user and increasing the precision of the UE's joint attach attempt.

[0030] For example, such as Figure 2 As shown in the figure, this application provides a joint attach method. The executing entity of the method can be a server, which can be an independent server or a server cluster composed of multiple servers. Moreover, the server can be a server capable of joint attach. The joint attach method specifically includes the following steps:

[0031] In step S201, an Attach request initiated by the UE is received.

[0032] In step S202, if the Attach request carries first target information related to VoLTE, the interoperability inactivity time between the SGs interface and the 2G or 3G network is determined; if the Attach request does not carry the first target information, the UE is allowed to perform joint attach through the SGs interface.

[0033] Specifically, a second variable, `23G_INACTIVE_TIMER`, can be added to the MME to record the inactive time of interoperation between the user's SGs interface and the 2G or 3G network. This indirectly indicates the network coverage (network quality) of the area where the UE is located. The inactive time of interoperation is directly proportional to the network quality of the 4G network in the UE's area; the larger the inactive time value, the better the network quality of the 4G network in the UE's area, i.e., the better the network coverage. A threshold can be set for this second variable, and the relative magnitude of the inactive time of interoperation with the threshold can be used to determine the network quality of the 4G network where the UE is located. This threshold can be determined according to the actual network situation, and this embodiment does not limit it. The inactive time of interoperation indicates the network quality of the 4G network in the UE's area.

[0034] The first target information indicates that the Attach request is a 4G joint attach request. If the Attach request carries the first target information related to VoLTE, it means that the user is a VoLTE user. In order to further determine whether the user does not really need to perform joint attach, it can be further determined whether the inactive time of interoperation (the second variable) is greater than or equal to the threshold. If the inactive time of interoperation (the second variable) is less than the threshold, it means that the 4G network coverage in the area where the UE device is located is poor, that is, the 4G network quality is poor, and the user has a need to communicate with the 2G network or 3G network. In this case, the UE device is allowed to perform joint attach.

[0035] In step S203, if the interoperability inactivity time is not less than a threshold, the UE is denied joint attachment via the SGs interface.

[0036] If the inactive time of interoperation (the second variable) is greater than or equal to the threshold, the UE is denied joint attach through the SGs interface, and the user is marked as a user who "does not actually need" joint attach through the SGs interface. When the user accesses the network again, the UE corresponding to the user can be directly denied joint attach through the SGs interface based on this mark, which reduces signaling procedures and saves the user's network access time.

[0037] Furthermore, an SGS_NOT_REQUIRED variable can be set as a third variable in the MME to identify users who need to perform federated attachment and those who do not, as determined by the interop inactivity period. For users who need to perform federated attachment as determined by the interop inactivity period, the SGS_NOT_REQUIRED variable is set to 0, and federated attachment is performed normally through the SGs interface. For users who do not need to perform federated attachment as determined by the interop inactivity period, the SGS_NOT_REQUIRED variable is set to 1, and federated attachment is no longer performed through the SGs interface.

[0038] It is worth noting that the same or similar parts of the above embodiments can be referred to each other, and the embodiments of this application will not be repeated here.

[0039] As can be seen from the technical solutions provided in the embodiments of this application above, when the Attach request is a VoLTE-related request, the UE is not allowed to perform joint attach. That is, when the UE performs joint attach, the LTE network will not allow the UE to perform joint attach through the SGs interface if the UE does not meet the joint attach conditions, thus avoiding the ineffective occupation of SGs interface and MSC resources and improving the resource utilization of SGs interface and MSC. Furthermore, by using the inactive interoperability time between the SGs interface and the 2G or 3G network, areas with good and poor 4G network quality in the VoLTE user's location can be further determined, thereby determining whether the user has an actual need for joint attach. Users are divided into two camps: those with genuine need and those without. Based on this separation, joint attach is allowed when the user has an actual need, achieving differentiated joint attach, thereby meeting the user's actual needs and improving the user experience.

[0040] In one possible implementation, when the interoperability inactivity time is less than a threshold, the joint attach method further includes: monitoring the UE's behavior, and allowing the UE to perform joint attach via the SGs interface when the UE performs at least one of the preset behaviors; the preset behaviors include at least one of the following: the UE issues an SGs interface service request; the UE interacts with a 2G PS domain network; the UE interacts with a 3G PS domain network; the UE requests a paging process; and the UE requests an SMS process, etc. Specifically, when the UE performs at least one of the preset behaviors, it indicates that the network coverage (network quality) in the area where the UE is located is poor, i.e., the 4G network quality is poor, the inactivity time of the user's SGs interface interoperating with the 2G or 3G network is less than a threshold, and the user needs to communicate with the 2G or 3G network, so the UE is allowed to perform joint attach. In this way, by determining whether the UE performs at least one of the preset behaviors, it is determined whether the user truly needs to perform joint attach. When the user has an actual need, joint attach is allowed, achieving differentiated joint attach, thereby meeting the user's actual needs and improving the user experience.

[0041] For example, such as Figure 3 As shown in the figure, this application provides a joint attach method. The executing entity of the method can be a server, which can be an independent server or a server cluster composed of multiple servers. Moreover, the server can be a server capable of identifying encrypted services. The joint attach method specifically includes the following steps:

[0042] In step S301, an Attach request initiated by the UE is received.

[0043] In step S302, if the Attach request carries first target information related to VoLTE, the UE is denied joint attach via the SGs interface; if the Attach request does not carry first target information, the UE is allowed to perform joint attach via the SGs interface.

[0044] The first target information indicates at least that the Attach request is a 4G joint attach request.

[0045] In step S303, a TUA update request initiated by the UE is received. If the TUA update request carries second target information related to VoLTE, the UE is denied from performing a TUA update through the SGs interface. If the TUA update request does not carry second target information, the UE is allowed to perform a TUA update through the SGs interface.

[0046] The second target information indicates at least that the TUA update request is a 4GTUA update request.

[0047] Specifically, the second target information includes the type of TUA update request related to VoLTE and the values ​​of VoLTE-related information elements. The types of TUA update requests include, but are not limited to, 4G TUA update requests, which include, but are not limited to, combined TAUpdate and combined LAUpdate. The VoLTE-related information elements can be voice domain preference and UE's Usage Setting information elements, and the values ​​of VoLTE-related information elements include, but are not limited to, VoLTE preferred (IMS PS voice preferred) and VoLTE only (IMS PS voice only).

[0048] Furthermore, a `VOLTE_USER_Indication` variable can be set as the primary variable in the MME. When a non-VoLTE user is identified, the `VOLTE_USER_Indication` variable is set to 0, and the MME performs the TUA update normally through the SGs interface after the UE initiates a TUA update request. When a VoLTE user is identified, the `VOLTE_USER_Indication` variable is set to 1, and the MME does not allow the TUA update to be performed through the SGs interface after the UE initiates a TUA update request.

[0049] Upon receiving a TUA update request, if the second type of the TUA update request is a 4G TUA update request, it indicates that the UE is in a 4G network environment, and the VOLTE_USER_Indication variable is set to 1. If the second type of the TUA update request is not a 4G TUA update request, it indicates that the UE is not in a 4G network environment, and the VOLTE_USER_Indication variable is set to 0. If the UE is in a 4G network environment, it is further determined whether the TUA update request carries VoLTE-related information elements. If it does, it indicates that in a 4G network environment, voice services can be performed via VoLTE, and a TUA update via SGs is not required; the VOLTE_USER_Indication variable is set to 1, and the UE is denied a TUA update via the SGs interface. If the TUA update request does not carry VoLTE-related information elements, it indicates that a TUA update via SGs is required, and the VOLTE_USER_Indication variable is set to 0; in this case, the UE is allowed a TUA update via the SGs interface.

[0050] Therefore, the second target information can be used to distinguish whether the UE user is a VoLTE user. If the UE user is a VoLTE user and is in a 4G network environment, it can complete voice and other services through VoLTE and does not need to perform TUA update. Therefore, the UE is refused TUA update, thus performing TUA update in a differentiated manner to avoid occupying SGs interface and MSC resources.

[0051] It is worth noting that steps S301 to S302 have the same or similar implementation as steps S101 to S102 in the above embodiments, and they can be referred to each other. The embodiments of this application will not be described again here.

[0052] As can be seen from the technical solutions provided in the embodiments of this application above, when the Attach request or TUA update request is a VoLTE-related request, the UE is not allowed to perform joint attach or TUA update. In other words, when the UE performs joint attach or TUA update, the LTE network will not allow the UE to perform joint attach or TUA update through the SGs interface if the UE does not meet the joint attach or TUA update conditions. This achieves differentiated joint attach or TUA update, thus avoiding ineffective occupation of SGs interface and MSC resources and improving the resource utilization of SGs interface and MSC. Furthermore, by performing differentiated joint attach or TUA update, VoLTE users in 4G networks do not need to perform process judgments on the SGs interface, reducing network signaling processes and shortening signaling latency. Moreover, the resources of SGs interface and MSC will not be occupied for a long time, reducing network costs and ensuring that non-VoLTE users can normally use the resources of SGs interface and MSC, achieving optimal matching of network resource utilization.

[0053] In one possible implementation, before denying the UE from performing a TUA update through the SGs interface, the joint attach method further includes: determining the interoperability inactivity time between the SGs interface and the 2G or 3G network, wherein the interoperability inactivity time indicates the network quality of the 4G network in the area where the UE is located; denying the UE from performing a TUA update includes: denying the UE from performing a TUA update if the interoperability inactivity time is not less than a threshold.

[0054] Specifically, a second variable, `23G_INACTIVE_TIMER`, can be added to the MME to record the inactive time of interoperation between the user's SGs interface and the 2G or 3G network. This indirectly indicates the network coverage (network quality) of the area where the UE is located. The inactive time of interoperation is directly proportional to the network quality of the 4G network in the UE's area; the larger the inactive time value, the better the network quality of the 4G network in the UE's area, i.e., the better the network coverage. A threshold can be set for this second variable, so that the relative magnitude of the inactive time of interoperation and the threshold can be used to determine the network quality of the 4G network where the UE is located. This threshold can be determined according to the actual network conditions, and this embodiment does not limit it.

[0055] When the TUA update request carries second target information related to VoLTE, it indicates that the user is a VoLTE user. To further determine whether the user truly does not need a TUA update, it can be further determined whether the interoperation inactivity time (second variable) is greater than or equal to a threshold. If the interoperation inactivity time (second variable) is less than the threshold, it indicates that the 4G network coverage in the area where the UE device is located is poor, i.e., the 4G network quality is poor, and the user needs to communicate with the 2G or 3G network, so the UE device is allowed to perform a TUA update. If the interoperation inactivity time (second variable) is greater than or equal to the threshold, the UE is denied a TUA update through the SGs interface, and the user is marked as a user who "does not actually need" a TUA update through the SGs interface. The next time the user accesses the network, the UE corresponding to that user can be directly denied a TUA update through the SGs interface based on this mark, reducing signaling procedures and saving the user's network access time.

[0056] A third variable, SGS_NOT_REQUIRED, can be set in the MME to identify users who require TUA updates and those who do not, as determined by the interop inactivity period. For users who require TUA updates as determined by the interop inactivity period, the SGS_NOT_REQUIRED variable is set to 0, and normal federated attachment is performed through the SGs interface. For users who do not require TUA updates as determined by the interop inactivity period, the SGS_NOT_REQUIRED variable is set to 1, and TUA updates are no longer performed through the SGs interface.

[0057] In this way, by measuring the inactivity time of interoperation between the SGs interface and the 2G or 3G network, the areas with good and poor 4G network quality in the VoLTE user's location can be further determined. This helps determine whether the user actually needs a TUA update, dividing users into two camps: those who genuinely need a TUA update and those who don't. Based on this separation, users with actual needs are allowed to perform a TUA update, achieving differentiated TUA updates, thereby meeting the user's actual needs and improving the user experience.

[0058] In one possible implementation, when the interoperability inactivity time is less than a threshold, the joint attach method further includes: monitoring the behavior of the UE, and allowing the UE to perform a TUA update through the SGs interface when the UE performs at least one of the preset behaviors; the preset behaviors include at least one of the following: the UE issues an SGs interface service request; the UE has interaction behavior with a 2G PS domain network; the UE has interaction behavior with a 3G PS domain network, the UE device requests a paging process, and the UE device requests an SMS process, etc.

[0059] Specifically, when a UE performs at least one of the preset behaviors, it indicates that the network coverage (network quality) in the area where the UE is located is poor, specifically, the 4G network quality is poor, the inactivity time of the user's SGs interface interoperating with the 2G or 3G network is less than a threshold, and the user needs to communicate with the 2G or 3G network. In this case, the UE is allowed to perform a TUA update. Thus, by determining whether the UE performs at least one of the preset behaviors, it is determined whether the user truly needs a TUA update. When the user has an actual need, a TUA update is allowed, achieving differentiated TUA updates, thereby meeting the user's actual needs and improving the user experience.

[0060] In one possible implementation, before rejecting the UE from performing a TUA update, the method further includes: obtaining the HSS subscription data of the user corresponding to the UE; rejecting the UE from performing a TUA update includes: if the HSS subscription data contains VoLTE service subscription data, rejecting the UE from performing a TUA update through the SGs interface.

[0061] Specifically, after identifying whether a UE user is a VoLTE user through the second target information, in order to further determine whether the user has subscribed to the VoLTE service and thus provide a better service experience, the system further checks whether the user's HSS subscription data contains VoLTE service subscription data. If the HSS subscription data contains VoLTE service subscription data, it means that the user has indeed subscribed to the VoLTE service, and VOLTE_USER_Indication is set to 1, thus preventing the UE from performing a TUA update through the SGs interface. If the HSS subscription data does not contain VoLTE service subscription data, VOLTE_USER_Indication is set to 0, allowing the UE to perform a TUA update through the SGs interface. This further distinguishes whether a user has truly subscribed to the VoLTE service, improving the accuracy of identifying whether a user is a VoLTE user and increasing the precision of the UE's TUA update.

[0062] Corresponding to the combined attachment method provided in the above embodiments, based on the same technical concept, this application also provides a combined attachment device. Figure 4 This application provides a schematic diagram of the modular composition of a combined attachment device, which is used to perform... Figures 1 to 3 The described joint attachment method, such as Figure 4 The joint attach device 400 includes: a receiving module 401 for receiving an Attach request initiated by a UE; a rejection module 402 for rejecting the UE from performing joint attach through the SGs interface if the Attach request carries first target information related to VoLTE, wherein the first target information indicates at least that the Attach request is a 4G joint attach request or a 5G joint attach request; and an allowing module 403 for allowing the UE to perform joint attach through the SGs interface if the Attach request does not carry the first target information.

[0063] As can be seen from the technical solutions provided in the above embodiments of this application, when the Attach request is a VoLTE-related request, the UE is not allowed to perform joint attachment. In other words, when the UE performs joint attachment, the LTE network will not allow the UE to perform joint attachment through the SGs interface if the UE does not meet the joint attachment conditions. This will prevent the SGs interface and MSC resources from being ineffectively occupied, thereby improving the resource utilization of the SGs interface and MSC.

[0064] In one possible implementation, the rejection module 402 is further configured to determine the interoperability inactivity time between the SGs interface and the 2G or 3G network, wherein the interoperability inactivity time indicates the network quality of the 4G network in the area where the UE is located; if the interoperability inactivity time is not less than a threshold, the UE is rejected from performing joint attachment through the SGs interface.

[0065] In one possible implementation, the allow module 403 is further configured to monitor the behavior of the UE when the interoperability inactivity time is less than a threshold, and allow the UE to perform joint attach via the SGs interface when the UE performs at least one of the preset behaviors; the preset behaviors include at least one of the following: the UE issues an SGs interface service request; the UE has interaction behavior with the 2G PS domain network; the UE has interaction behavior with the 3G PS domain network.

[0066] In one possible implementation, the allow module 403 is further configured to receive a TUA update request initiated by the UE; if the TUA update request carries second target information related to VoLTE, the UE is denied from performing a TUA update through the SGs interface; if the TUA update request does not carry second target information, the UE is allowed to perform a TUA update through the SGs interface, wherein the second target information at least indicates that the TUA update request is a 4G TUA update request.

[0067] In one possible implementation, the rejection module 402 is further configured to determine the interoperability inactivity time between the SGs interface and the 2G or 3G network, wherein the interoperability inactivity time indicates the network quality of the 4G network in the area where the UE is located; if the interoperability inactivity time is not less than a threshold, the UE is rejected from performing a TUA update through the SGs interface.

[0068] In one possible implementation, the second target information includes a first type of the VoLTE-related TUA update request and the value of the VoLTE-related information element.

[0069] In one possible implementation, the rejection module 402 is also used to obtain the HSS subscription data of the user corresponding to the UE, and if the HSS subscription data contains VoLTE service subscription data, the UE is rejected from performing joint attach through the SGs interface.

[0070] In one possible implementation, the first target information includes a second type of Attach request related to VoLTE and the value of VoLTE-related information cells.

[0071] The combined attachment device provided in this application embodiment can realize the various processes in the embodiments corresponding to the above combined attachment method. To avoid repetition, it will not be described again here.

[0072] It should be noted that the combined attachment device and the combined attachment method provided in this application embodiment are based on the same application concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned combined attachment method, and the repeated parts will not be described again.

[0073] Corresponding to the joint attachment method provided in the above embodiments, based on the same technical concept, this application also provides an electronic device for performing the above-described joint attachment method. Figure 5 To illustrate the structure of an electronic device according to various embodiments of this application, as shown in the following diagrams... Figure 5 As shown. Electronic devices can vary considerably due to differences in configuration or performance, and may include one or more processors 501 and memory 502. Memory 502 may store one or more application programs or data. Memory 502 may be temporary or persistent storage. The application programs stored in memory 502 may include one or more modules (not shown), and each module may include a series of computer-executable instructions for the electronic device.

[0074] Furthermore, the processor 501 may be configured to communicate with the memory 502 and execute a series of computer-executable instructions stored in the memory 502 on the electronic device. The electronic device may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input / output interfaces 505, and one or more keyboards 506.

[0075] Specifically, in this embodiment, the electronic device includes a processor, a communication interface, a memory, and a communication bus; wherein, the processor, the communication interface, and the memory communicate with each other through the bus; the memory is used to store computer programs; the processor is used to execute the programs stored in the memory to implement the various steps in the above method embodiments and has the beneficial effects of the above method embodiments. To avoid repetition, the embodiments of this application will not be described again here.

[0076] This embodiment also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the steps in the above method embodiments and has the beneficial effects of the above method embodiments. To avoid repetition, the embodiments of this application will not be described again here.

[0077] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) in which computer-usable program code is carried.

[0078] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0079] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0080] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0081] In a typical configuration, an electronic device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0082] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0083] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0084] It should also be noted that the terms "comprising," "carrying," or any other variations thereof are intended to cover non-exclusive carrying, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0085] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) in which computer-usable program code is carried.

[0086] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A combined attachment method, characterized in that, The combined attachment method includes: Receive the Attach request initiated by the UE; If the Attach request carries first target information related to VoLTE, the UE is denied joint attach via the SGs interface. The first target information at least indicates that the Attach request is a 4G joint attach request. If the first target information is not included in the Attach request, the UE is allowed to perform joint attach via the SGs interface.

2. The combined attachment method according to claim 1, characterized in that, Before rejecting the UE's joint attach via the SGs interface, the joint attach method further includes: Determine the interoperability inactivity time between the SGs interface and the 2G or 3G network, wherein the interoperability inactivity time indicates the network quality of the 4G network in the area where the UE is located; The refusal to allow the UE to perform joint attach via the SGs interface includes: refusing the UE to perform joint attach via the SGs interface if the interoperability inactivity time is not less than a threshold.

3. The combined attachment method according to claim 2, characterized in that, If the interoperability inactivity time is less than the threshold, the joint attach method further includes: monitoring the behavior of the UE, and allowing the UE to perform joint attach through the SGs interface when the UE performs at least one of the preset behaviors; The preset behavior includes at least one of the following: The UE sends an SGs interface service request; The UE exhibits interactive behavior with the 2G PS domain network; The UE engages in interactive behavior with the 3G PS domain network.

4. The combined attachment method according to claim 1, characterized in that, After allowing the UE to perform joint attach via the SGs interface, the joint attach method further includes: Receive the TUA update request initiated by the UE; If the TUA update request carries second target information related to VoLTE, the UE is denied from performing a TUA update through the SGs interface; if the TUA update request does not carry the second target information, the UE is allowed to perform a TUA update through the SGs interface. The second target information at least indicates that the TUA update request is a 4GTUA update request.

5. The combined attachment method according to claim 4, characterized in that, Before rejecting the UE's TUA update via the SGs interface, the joint attach method further includes: Determine the interoperability inactivity time between the SGs interface and the 2G or 3G network, wherein the interoperability inactivity time indicates the network quality of the 4G network in the area where the UE is located; The step of denying the UE from performing a TUA update through the SGs interface includes: denying the UE from performing a TUA update through the SGs interface if the interoperability inactivity time is not less than a threshold.

6. The combined attachment method according to claim 4, characterized in that, The second target information includes a first type of TUA update request related to the VoLTE and the value of the information cell related to VoLTE.

7. The combined attachment method according to claim 1, characterized in that, Before rejecting the UE's joint attach via the SGs interface, the joint attach method further includes: Obtain the HSS subscription data of the user corresponding to the UE. The step of rejecting the UE from joint attaching through the SGs interface includes: if the HSS subscription data contains VoLTE service subscription data, rejecting the UE from joint attaching through the SGs interface.

8. The combined attachment method according to claim 1, characterized in that, The first target information includes a second type of Attach request related to the VoLTE and the value of the VoLTE-related information cell.

9. A combined attachment device, characterized in that, The combined attachment device includes: The receiving module is used to receive Attach requests initiated by the UE; The rejection module is configured to reject the UE from performing a joint attach via the SGs interface if the Attach request carries first target information related to VoLTE, wherein the first target information at least indicates that the Attach request is a 4G joint attach request. The permission module is configured to allow the UE to perform joint attach via the SGs interface if the first target information is not carried in the Attach request.

10. An electronic device, characterized in that, The system includes a processor, a communication interface, a memory, and a communication bus; wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory is used to store computer programs; and the processor is used to execute the programs stored in the memory to implement the steps of the joint attachment method as described in any one of claims 1-8.

Images