Method for processing abnormal IP address allocation and mobile terminal

Abstract

The present invention provides a method for handling IP address allocation anomalies and a mobile terminal. The method comprises: during the process of establishing a new PDN / PDU session, when it is detected that the IP address allocated by the network side is the same as the IP address of an established PDN / PDU session, the mobile terminal queries the status of the established PDN / PDU session; if the established PDN / PDU session is still in an activated state, the mobile terminal determines whether to retain the established PDN / PDU session or retain a new PDN / PDU session based on configuration parameters; if the established PDN / PDU session is already in the process of deactivation, the mobile terminal considers that the new PDN / PDU session is successfully established. The present invention can improve the fault tolerance capability of the mobile terminal to IP address allocation anomalies.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method for processing abnormal IP address allocation and a mobile terminal. Background Art

[0002] When establishing a packet data network (PDN) connection or protocol data unit session (PDU session) between a mobile terminal and a mobile wireless network, the mobile wireless network must assign a correct IP address to the mobile terminal to meet its network connection requirements. However, if an anomaly occurs in the mobile wireless network, an incorrect IP address may be assigned to the mobile terminal, affecting the transmission of IP packets on the mobile terminal.

[0003] For example, a user equipment (UE) establishes two PDN / PDU sessions, but the network incorrectly assigns the same IPv4 address to the mobile terminal when establishing the second PDN / PDU session as the first. In this case, the mobile terminal's IP packet transmission will be erroneous, resulting in unstable network connection or inability to access network resources.

[0004] Therefore, in order to deal with the problem of abnormal IP address allocation, it is particularly important to improve the fault tolerance of mobile terminals. Summary of the Invention

[0005] The present invention provides a method for processing an IP address allocation anomaly and a mobile terminal, which are used to improve the fault tolerance capability of the mobile terminal to the IP address allocation anomaly.

[0006] The technical solutions provided by the present invention are as follows:

[0007] A method for handling an abnormal IP address allocation, applied to a mobile terminal, comprising:

[0008] During the process of establishing a new PDN / PDU session, when it is detected that the IP address allocated by the network side to the new PDN / PDU session is the same as the IP address of the established PDN / PDU session, the mobile terminal queries the status of the established PDN / PDU session;

[0009] If the established PDN / PDU session is still active, the mobile terminal decides whether to retain the established PDN / PDU session or the new PDN / PDU session according to the configuration parameters;

[0010] If the established PDN / PDU session is already in the deactivation process, the mobile terminal considers that the new PDN / PDU session is successfully established.

[0011] In some embodiments, the mobile terminal determines whether to retain the established PDN / PDU session or retain the new PDN / PDU session based on configuration parameters, including:

[0012] If it is determined according to the configuration parameters to retain the established PDN / PDU session, the mobile terminal notifies the network side that the establishment of the new PDN / PDU session has failed;

[0013] If it is decided to retain the new PDN / PDU session according to the configuration parameters, the mobile terminal considers that the new PDN / PDU session is established successfully, and then deactivates the established PDN / PDU session.

[0014] In some embodiments, it further includes:

[0015] During establishment of a new PDN / PDU session, when it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session does not include the requested IP address type, the mobile terminal notifies the network side that establishment of the new PDN / PDU session has failed;

[0016] When it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session includes the requested IP address type, the mobile terminal selects an IP address consistent with the requested IP address type from the allocated IP addresses as the IP address of the new PDN / PDU session, and considers that the new PDN / PDU session is established successfully.

[0017] In some embodiments, the mobile terminal deems that the new PDN is established successfully, including:

[0018] The mobile terminal sends an activate default EPS bearer context accept message to the network side.

[0019] In some embodiments, the mobile terminal notifying the network side that the new PDN establishment fails includes:

[0020] The mobile terminal sends an activate default EPS bearer context reject message to the network side, and carries a cause value, where the cause value indicates an invalid PDN address.

[0021] In some embodiments, the mobile terminal notifying the network side that the new PDU session establishment failure occurs includes:

[0022] The mobile terminal sends a PDU session release request message to the network side, and carries the new PDU session ID and a release reason value, where the release reason value indicates an invalid PDU address.

[0023] In some embodiments, the mobile terminal deactivating the established PDU session includes:

[0024] The mobile terminal sends a PDU session release request message to the network side, and carries the established PDU session ID.

[0025] In some embodiments, it further includes:

[0026] During the process of establishing a new PDU session, when it is detected that the IP address allocated to the new PDU session in the PDU session establishment accept message sent by the network side is incompatible with the selected PDU session type, the mobile terminal notifies the network side to release the new PDU session;

[0027] When it is detected that the IP address allocated to the new PDU session in the PDU session establishment acceptance message sent by the network side is compatible with the selected PDU session type, the mobile terminal considers that the new PDU session is successfully established.

[0028] In some embodiments, the mobile terminal notifies the network side to release the new PDU session, including:

[0029] The new PDU session release request message carries a release reason value, where the release reason value indicates an invalid PDU address.

[0030] The present invention also provides a mobile terminal, comprising: a memory for storing a program; and a processor for implementing the method for handling an abnormal IP address allocation as described in any one of the aforementioned embodiments when running the program.

[0031] The method for processing an IP address allocation anomaly and the mobile terminal provided by the present invention can at least bring the following beneficial effects: the present invention can improve the fault tolerance of the mobile terminal to IP address allocation anomalies and enhance the protocol compatibility of the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The following will explain a preferred embodiment in a clear and understandable manner with reference to the accompanying drawings, and further explain a method for handling an abnormal IP address allocation, the above-mentioned characteristics, technical features, advantages and implementation methods of the mobile terminal.

[0033] Figure 1 It is a flow chart of an embodiment of a method for handling abnormal IP address allocation according to the present invention;

[0034] Figure 2 It is a flowchart of another embodiment of a method for handling abnormal IP address allocation of the present invention;

[0035] Figure 3 It is a flowchart of another embodiment of a method for handling abnormal IP address allocation of the present invention;

[0036] Figure 4 It is a flowchart of another embodiment of a method for handling abnormal IP address allocation of the present invention;

[0037] Figure 5 It is a flowchart of another embodiment of a method for handling abnormal IP address allocation of the present invention;

[0038] Figure 6 It is a flowchart of another embodiment of a method for handling abnormal IP address allocation of the present invention;

[0039] Figure 7 It is a structural diagram of an embodiment of a mobile terminal of the present invention. DETAILED DESCRIPTION

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific embodiments of the present invention will be described below with reference to the accompanying drawings. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings and other embodiments can be obtained based on these drawings without inventive work.

[0041] To simplify the drawings, only the parts relevant to the present invention are schematically depicted in each figure. These parts do not represent the actual structure of the product. Furthermore, to simplify the drawings and facilitate understanding, in some figures, only one component with the same structure or function is schematically depicted or labeled. As used herein, "one" not only means "only one" but also "more than one."

[0042] One embodiment of the present invention, as Figure 1 As shown, a method for handling an abnormal IP address allocation is applied to a mobile terminal, comprising:

[0043] Step S100: During the process of establishing a new PDN / PDU session, when it is detected that the IP address allocated by the network side to the new PDN / PDU session is the same as the IP address of the established PDN / PDU session, the mobile terminal queries the status of the established PDN / PDU session;

[0044] In step S110, if the established PDN / PDU session is still active, the mobile terminal decides whether to retain the established PDN / PDU session or retain a new PDN / PDU session based on the configuration parameters;

[0045] In step S120, if the established PDN / PDU session is already in the process of being deactivated, the mobile terminal notifies the network side that the new PDN / PDU session is successfully established.

[0046] Specifically, in a 4G / 5G network, a mobile terminal (also known as user equipment (UE)) has established one or more PDN / PDU sessions. When the mobile terminal establishes a new PDN / PDU session, the IP address assigned to the mobile terminal by the mobile wireless network is the same as the IP address of the established PDN / PDU session (also known as the old PDN / PDU session). In this case, the UE performs different processing based on the status of the old PDN / PDU session:

[0047] If the old PDN / PDU session is still in the active state, the UE determines which PDN / PDU session to use based on the configuration parameters. If the old PDN / PDU session is already in the deactivation process, the UE accepts the success of the current PDN / PDU session activation.

[0048] In 4G networks, such as Figure 2 As shown in Figure 1, the process of establishing a PDN between the UE and the core network (EPC) is as follows:

[0049] 1. When the UE needs to establish a new PDN connection using an APN (Access Point Name), it sends a PDN connectivity request message to the EPC.

[0050] 2. If the request is accepted, the EPC sends an Activate default EPS bearer context request message to the UE. The message carries the PDN address parameter, which is the IP address (such as IPv4 address, IPv6 address, or both) assigned by the network to the current PDN connection.

[0051] 3a. Scenario 1: After receiving the Activate default EPS bearer context request message, the UE checks the assigned IP address. If the IP address of the current PDN duplicates the IP address of another existing PDN, and the old PDN is still active, and the UE is configured to reject the new PDN, the UE sends an Activate default EPS bearer context reject message to notify the network of the PDN establishment failure.

[0052] If the UE is configured to accept the new PDN and deactivate the old PDN, the UE first sends an Activate default EPS bearer context accept message to notify the network side that the new PDN is successfully established, and then deactivates the old PDN.

[0053] In one embodiment, the Activate default EPS bearer context reject or PDN disconnect request message (PDN disconnect request) may also carry a PDN establishment failure cause value, and a new cause value may be added to indicate an invalid PDN address, such as " – Invalid PDN address value”, or use an existing cause value to indicate an invalid PDN address.

[0054] After receiving the Activate default EPS bearer context reject message, if the reason value is "Invalid PDN address", the network side needs to record the log information to remind maintenance personnel to configure the correct IP address.

[0055] 3b. Scenario 2: Although the IPv4 address of the current PDN overlaps with the IPv4 address of another existing PDN, since the old PDN is already in the process of being deactivated, the UE sends an Activate default EPS bearer context accept message to notify the network side that the PDN establishment is successful.

[0056] It should be noted that the diagram uses IPv4 as an example, but this application does not impose such restrictions on IP addresses.

[0057] In 5G networks, such as Figure 3 As shown in the figure, the process of establishing a PDN between the UE and the core network (5GC, 5G core network) is as follows:

[0058] 1. When the UE needs to establish a new PDN using a certain APN, it sends a PDU session establishment request message to the network.

[0059] 2. If the request is accepted, 5GC sends a PDU session establishment accept message to the UE and allocates an IP address for the current PDU session.

[0060] 3a. Scenario 1: After receiving the PDU session establishment accept message, the UE checks the assigned IP address. If the IPv4 address of the current PDU session duplicates the IPv4 address of another existing PDU session, and the old PDU session is still active, the UE, if configured to reject new PDU sessions, sends a PDU session release request message carrying the new PDU session ID to notify the network to deactivate the new PDU session.

[0061] If it is configured to accept a new PDU session and deactivate the old PDU session, the UE sends a PDU session release request message carrying the old PDU session ID to notify the network side to deactivate the old PDU session.

[0062] In one implementation, a release reason value may also be carried in the PDU session release request message, and a new release reason value may be added to indicate an invalid PDU address, such as " - Invalid PDU address value", or use the existing cause value of the protocol.

[0063] After receiving the PDU session release request message, if the release reason value is an invalid PDU address, the network side needs to record log information to remind maintenance personnel to configure the correct IP address.

[0064] 3b. Scenario 2: Although the IPv4 address of the current PDU session overlaps with the IPv4 address of another existing PDU session, the UE accepts the new PDU session because the old PDU session is already in the process of being deactivated.

[0065] It should be noted that the diagram uses IPv4 as an example, but this application does not impose such restrictions on IP addresses.

[0066] Another embodiment of the present invention provides a method for handling an IP address allocation anomaly, for a mobile terminal, comprising:

[0067] In step S200, during the process of establishing a new PDN / PDU session, when it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session does not include the requested IP address type, the mobile terminal notifies the network side that the new PDN / PDU session establishment fails.

[0068] In step S210, when it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session includes the requested IP address type, the mobile terminal selects an IP address that is consistent with the requested IP address type from the allocated IP addresses as the IP address of the new PDN / PDU session, and considers that the new PDN / PDU session is established successfully.

[0069] Specifically, when the UE establishes a PDN / PDU session, due to network side anomalies, the type of the IP address assigned by the network may be inconsistent with the type of the IP address requested by the UE. This can be divided into two scenarios:

[0070] If the current PDN / PDU session is only assigned an IPv4 address and the UE requests an IPv6 address, or if the current PDN / PDU session is only assigned an IPv6 address and the UE requests an IPv4 address, the UE considers that the PDN / PDU session establishment has failed because the service requirements of the UE cannot be met.

[0071] If the current PDN / PDU session is allocated IPv4 and IPv6 addresses, and the UE only requests an IPv4 or IPv6 address, the UE only selects the address required for the service and discards the remaining addresses. This can meet the UE's service needs, so the UE considers that the PDN / PDU session is successfully established.

[0072] In 4G networks, such as Figure 4 As shown in the figure, the process of establishing a PDN between the UE and the 4G core network (EPC) is as follows:

[0073] 1. When the UE needs to establish a new PDN connection using a certain APN, it sends a PDN Connectivity Request message to the EPC.

[0074] 2. If the request is accepted, the EPC sends an Activate default EPS bearer context request message to the UE, carrying the PDN address parameter, which is the IP address assigned to the UE.

[0075] 3a. Scenario 1: After receiving the Activate default EPS bearer context request message, the UE checks the address type in the PDN address. If the current PDN only has an IPv4 address assigned and the UE requested an IPv6 address, or if the current PDN only has an IPv6 address assigned and the UE requested an IPv4 address, the UE sends an Activate default EPS bearer context reject message to notify the network of the PDN establishment failure because the PDN cannot meet the UE's service requirements.

[0076] In one embodiment, the Activate default EPS bearer context reject message may also carry a cause value, and a new cause value may be added to indicate an invalid PDN address, such as " – Invalid PDNaddress value", or use an existing cause value.

[0077] After receiving the Activate default EPS bearer context reject message, if the reason value is an invalid PDN address, the network side needs to record the log information to remind maintenance personnel to configure the correct IP address.

[0078] 3b. Scenario 2: After receiving the Activate default EPS bearer context request message, the UE checks the address type of the IP address in the PDN address. If the current PDN allocates both IPv4 and IPv6 addresses, and the UE requests only an IPv4 or IPv6 address, the UE selects only the address required for the service and discards any remaining addresses. If the UE's service requirements are met, the UE sends an Activate default EPS bearer context accept message to notify the network of the successful PDN establishment.

[0079] In 5G networks, such as Figure 5 As shown in the figure, the process of establishing a PDU session between the UE and the core network (5GC) is as follows:

[0080] 1. When the UE needs to establish a new PDU session connection using an APN (Access Point Name), it sends a PDU session establishment request message to the 5GC.

[0081] 2. If the request is accepted, 5GC sends a PDU session establishment accept message to the UE, carrying parameters such as the PDN address.

[0082] 3a. Scenario 1: After receiving the PDU session establishment accept message, the UE checks the address type of the IP address in the PDU address. If the current PDU session is only assigned an IPv4 address and the UE requests an IPv6 address, or if the current PDU session is only assigned an IPv6 address and the UE requests an IPv4 address, the UE sends a PDU session release request message to notify the network to deactivate the PDU session because the service requirements of the UE cannot be met.

[0083] In one embodiment, the PDU session release request message carries a release reason value, and a new release reason value can be added to indicate an invalid PDU address, such as " – Invalid PDU address value", or use an existing cause value.

[0084] After receiving the PDU session release request message, if the release reason value is an invalid PDU address, the 5GC needs to record the log information to remind maintenance personnel to configure the correct IP address.

[0085] Scenario 2: Although both IPv4 and IPv6 addresses are allocated for the current PDU session, the UE requests only an IPv4 or IPv6 address. The UE selects only the address required for the service and discards any remaining addresses. If the PDU session can satisfy the UE's service requirements, the UE accepts the PDU session.

[0086] Another embodiment of the present invention provides a method for handling an IP address allocation anomaly, for a mobile terminal, comprising:

[0087] Step S300: During the process of establishing a new PDU session, when it is detected that the IP address allocated to the new PDU session in the PDU session establishment acceptance message sent by the network side is incompatible with the selected PDU session type, the mobile terminal notifies the network side to release the new PDU session;

[0088] In step S310, when it is detected that the IP address allocated to the new PDU session in the PDU session establishment acceptance message sent by the network side is compatible with the selected PDU session type, the mobile terminal notifies the network side that the new PDU session is successfully established.

[0089] Specifically, when the UE is registered in the 5G network and a PDU session is established, if due to a network side anomaly, the type of the selected PDU session type IE in the PDU session establishment accept message may be inconsistent with the type of the actually allocated IP address in the PDU address, which is divided into two scenarios:

[0090] If the selected PDU session type IE is incompatible with the type of the IP address actually allocated in the PDU address, the network is notified to release this PDU session; if the selected PDU session type IE is compatible with the type of the IP address actually allocated in the PDU address, this PDU session continues to be used.

[0091] like Figure 6 As shown in the figure, the specific process of establishing a PDU session between the UE and the core network (5GC) is as follows:

[0092] 1. When the UE needs to establish a new PDU session using a certain APN, the UE actively sends a PDU session establishment request message to the network.

[0093] 2. If the request is accepted, the 5GC sends a PDU session establishment accept message to the UE. This message usually carries the following parameters:

[0094] Selected PDU session type IE: selected PDU session type (such as IPv4, IPv6, IPv4v6, etc.);

[0095] PDU address: The IP address assigned to the UE (such as IPv4 address, IPv6 address, or both).

[0096] 3. Scenario 1: After receiving the PDU session establishment accept message, the UE checks whether the Selected PDU session type IE matches the type of the IP address actually assigned in the PDU address. If the two are an exact match, or if the Selected PDU session type includes the address type in the PDU address, the IP address assigned by the network is considered compatible with the selected PDU session type, and the UE considers the new PDU session established successfully.

[0097] For example, if the Selected PDU type is IPv4 and the IP address assigned to the UE is the IPv4 address 192.168.1.100, the two are an exact match. Alternatively, if the Selected PDU type is IPv4v6 and the IP address assigned to the UE is either the IPv4 address 192.168.1.100 or the IPv6 address 2001:0db8::1, the Selected PDU type includes the type of the IP address in the PDU address. In both cases, the IP address is compatible with the selected PDU session type.

[0098] Scenario 2: After receiving the PDU session establishment accept message, the UE checks whether the Selected PDU session type IE matches the type of the IP address actually assigned in the PDU address. If the type of the IP address assigned to the UE is not within the Selected PDU session type range, the IP address assigned by the network is considered incompatible with the selected PDU session type. The UE considers this PDU session unavailable and notifies the network to release this PDU session.

[0099] For example, if the Selected PDU session type is IPv4 and the IP address allocated to the UE is the IPv6 address 2001:0db8::1; or if the Selected PDU session type is IPv6 and the IP address allocated to the UE is the IPv4 address 192.168.1.100. In both cases, the IP address is incompatible with the selected PDU session type.

[0100] In one embodiment, the release reason value is carried in the PDU session release request message. A new release reason value may be added to indicate an invalid PDU address, such as " –Invalid PDU address value”, or use the existing cause value defined by the protocol.

[0101] After receiving the PDU session release request message, if the release reason value is an invalid PDU address, such as " - Invalid PDU address value”, a log message is recorded to remind maintenance personnel to configure the correct IP address.

[0102] One embodiment of the present invention, as Figure 7As shown, a mobile terminal includes:

[0103] A memory 10 for storing a program 20;

[0104] The processor 30 is configured to implement the method for handling an IP address allocation anomaly of any of the aforementioned embodiments when running the program 20.

[0105] The memory 10 may be any internal storage unit and / or external storage device capable of storing data and programs, for example, a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, or a flash memory card.

[0106] As needed, the processor 30 can be a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a general-purpose processor or other logic devices, etc.

[0107] It should be noted that the above embodiments can be freely combined as needed. The above are only preferred embodiments of the present invention. It should be noted that those skilled in the art can make several improvements and modifications without departing from the principles of the present invention, and such improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for handling abnormal IP address allocation, characterized in that: Applied to mobile terminals, including: During the process of establishing a new PDN / PDU session, when it is detected that the IP address allocated by the network side to the new PDN / PDU session is the same as the IP address of the established PDN / PDU session, the mobile terminal queries the status of the established PDN / PDU session; If the established PDN / PDU session is still active, the mobile terminal decides whether to retain the established PDN / PDU session or the new PDN / PDU session according to the configuration parameters; If the established PDN / PDU session is already in the deactivation process, the mobile terminal considers that the new PDN / PDU session is established successfully.

2. The method for handling abnormal IP address allocation according to claim 1, characterized in that: The mobile terminal determines whether to retain the established PDN / PDU session or retain the new PDN / PDU session according to the configuration parameters, including: If it is determined according to the configuration parameters to retain the established PDN / PDU session, the mobile terminal notifies the network side that the establishment of the new PDN / PDU session has failed; If it is decided to retain the new PDN / PDU session according to the configuration parameters, the mobile terminal considers that the new PDN / PDU session is established successfully, and then deactivates the established PDN / PDU session.

3. The method for handling abnormal IP address allocation according to claim 1, wherein: Also includes: During establishment of a new PDN / PDU session, when it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session does not include the requested IP address type, the mobile terminal notifies the network side that establishment of the new PDN / PDU session has failed; When it is detected that the type of the IP address allocated by the network side to the new PDN / PDU session includes the requested IP address type, the mobile terminal selects an IP address consistent with the requested IP address type from the allocated IP addresses as the IP address of the new PDN / PDU session, and considers that the new PDN / PDU session is established successfully.

4. The method for handling abnormal IP address allocation according to claim 1, 2 or 3, characterized in that: The mobile terminal considers that the new PDN is established successfully, including: The mobile terminal sends an activate default EPS bearer context accept message to the network side.

5. The method for handling abnormal IP address allocation according to claim 2 or 3, characterized in that: The mobile terminal notifying the network side of the failure to establish the new PDN includes: The mobile terminal sends an activate default EPS bearer context reject message to the network side, and carries a cause value, where the cause value indicates an invalid PDN address.

6. The method for handling abnormal IP address allocation according to claim 2 or 3, characterized in that: The mobile terminal notifying the network side that the new PDU session establishment failure occurs includes: The mobile terminal sends a PDU session release request message to the network side, and carries the new PDU session ID and a release reason value, where the release reason value indicates an invalid PDU address.

7. The method for handling abnormal IP address allocation according to claim 2, characterized in that: Deactivating, by the mobile terminal, the established PDU session, including: The mobile terminal sends a PDU session release request message to the network side, and carries the established PDU session ID.

8. The method for handling abnormal IP address allocation according to claim 1, wherein: Also includes: During the process of establishing a new PDU session, when it is detected that the IP address allocated to the new PDU session in the PDU session establishment accept message sent by the network side is incompatible with the selected PDU session type, the mobile terminal notifies the network side to release the new PDU session; When it is detected that the IP address allocated to the new PDU session in the PDU session establishment acceptance message sent by the network side is compatible with the selected PDU session type, the mobile terminal considers that the new PDU session is successfully established.

9. The method for handling abnormal IP address allocation according to claim 8, characterized in that: The mobile terminal notifying the network side to release the new PDU session includes: The new PDU session release request message carries a release reason value, where the release reason value indicates an invalid PDU address.

10. A mobile terminal, characterized in that: include: Memory, used to store programs; A processor, configured to implement the method for handling an IP address allocation anomaly according to any one of claims 1 to 9 when running the program.

Images