Method and apparatus for handling session reestablishment procedure

Abstract

Various solutions for handling a protocol data unit (PDU) session reestablishment process are described herein. A user equipment (UE) sends a request message to a network node. The UE then receives an acceptance message from the network node in response to the request message. The accept message includes a cause value for releasing the session. The UE may determine whether to reestablish the session according to the cause value.

Description

Technical Field

[0001] This disclosure generally relates to mobile communications, and more specifically, to methods and apparatus for processing Protocol Data Unit (PDU) session reconstruction procedures. Background Technology

[0002] Unless otherwise stated herein, the methods described in this section are not prior art to the claims listed below, and are not acknowledged as prior art by virtue of their inclusion in this section.

[0003] Over the years, wireless communication networks have grown exponentially. Long-Term Evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and reduced operating costs due to a simplified network architecture. LTE systems, also known as 4G systems, also provide seamless integration with legacy wireless networks such as Global System for Mobile Communication (GSM), Code-Division Multiple Access (CDMA), and Universal Mobile Telecommunication System (UMTS). In LTE systems, the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) comprises multiple evolved Node-Bs (eNodeBs or eNBs) that communicate with multiple mobile stations, known as user equipment (UEs). 3rd Generation Partner Project (3GPP) networks typically include a hybrid of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) Committee has decided to focus future NGMN activities on defining the end-to-end requirements for 5G New Radio (NR) systems.

[0004] In 5G / NR systems, UEs access the data network by establishing PDU sessions. Each PDU session is identified by a PDU session identity (PSI), which is assigned within a predefined range (e.g., 1 to 15). When the network intends to release a PDU session, it initiates the PDU session release process by sending a PDU session release command message to the UE, indicating the PSI to be released. Upon receiving the PDU session release command message, the UE responds with a PDU session release complete message, after which both the UE and the network consider the corresponding PDU session to be released.

[0005] Furthermore, the synchronization of active PDU sessions between the UE and the network can be achieved through a PDU session state information element (IE), which can be included in the registration request message and the registration acceptance message. When a PDU session remains active on the UE but has been deactivated on the network, the UE will locally release the PDU session upon receiving the corresponding PDU session state IE.

[0006] However, problems may arise when the UE is located in an area with poor or no radio signal. In this situation, the PDU session release command message sent by the network may fail to reach the UE. Since the network does not receive a corresponding PDU session release completion message from the UE, it may decide to release the PDU session locally. Later, when the UE performs the registration process, it may learn of the deactivation status through the PDU session state (IE) and release the PDU session locally accordingly. However, since the UE is unaware of the reason for the network's release of the PDU session, it may attempt to re-establish the locally released PDU session by initiating a new PDU session establishment process. However, such a process may be rejected by the network, potentially leading to unnecessary signaling and inefficiency.

[0007] Therefore, a solution is needed to enable the UE to know the reason why the network releases the PDU session, so as to operate more efficiently. Summary of the Invention

[0008] The following overview is illustrative only and is not intended to be limiting in any way. That is, it is provided to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. The chosen embodiments will be further described in detail below. Therefore, the following overview is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] One objective of this disclosure is to propose a solution or approach to address the aforementioned issues related to the processing of PDU session reconstruction.

[0010] In one aspect, a method involves an apparatus sending a request message to a network node. The method also involves the apparatus receiving an acceptance message from the network node in response to the request message. The acceptance message includes a reason value for releasing the session. The method further involves the apparatus determining, based on the reason value, whether to re-establish the session.

[0011] In one aspect, an apparatus includes a transceiver that wirelessly communicates with a network during operation. The apparatus also includes a processor communicatively connected to the transceiver. During operation, operations performed by the processor include sending a request message to a network node via the transceiver. During operation, operations also performed by the processor include receiving an acceptance message from the network node via the transceiver in response to the request message. The acceptance message includes a reason value for releasing a session. During operation, operations also performed by the processor include determining whether to re-establish the session based on the reason value.

[0012] On the other hand, one approach involves a network node determining the release of a session with the UE. This approach also involves the network node including a reason value for releasing the session in an accept message. Furthermore, this approach involves the network node sending an accept message to the UE.

[0013] It is worth noting that although the descriptions provided herein may be in the context of certain wireless access technologies, networks, and network topologies, such as LTE, LTE-Advanced, LTE-Advanced Pro, 5G, NR, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Beyond 5G (B5G), and 6th Generation (6G), the proposed concepts, schemes, and any variations / derivatives thereof may be implemented, applied, and carried out in other types of wireless access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0014] The accompanying drawings are included to provide a further understanding of this disclosure, and are incorporated into and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that, in order to clearly illustrate the concepts of the disclosure, the drawings are not necessarily drawn to scale, and some components may be shown out of proportion to their actual dimensions in the embodiments.

[0015] Figure 1An example NR network is described in accordance with an embodiment of this disclosure, illustrating the process of reconstructing a PDU session.

[0016] Figure 2 A schematic diagram illustrating an example flow of a PDU session reconstruction process according to an embodiment of the present disclosure is provided.

[0017] Figure 3 This is a block diagram of a communication system according to an embodiment of the present disclosure.

[0018] Figure 4 This is a flowchart of an example process according to an embodiment of the present disclosure.

[0019] Figure 5 This is a flowchart of another example process according to an embodiment of the present disclosure. Detailed Implementation

[0020] The embodiments and implementations of the claimed subject matter are described in detail below. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter implemented in various forms. This disclosure can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that the description of this disclosure is thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. In the following description, known features and technical details are omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0021] Overview The embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions for processing PDU session reconstruction. According to this disclosure, many possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in some combination.

[0022] Figure 1 An example NR network 100 is described according to an embodiment of the present disclosure, illustrating the processing of a PDU session reconstruction procedure. The NR network 100 includes a data network 110 and an application server 111, providing various services through communication with multiple UEs (including UE 114). Figure 1In the example, UE 114 and its serving base station (BS) 115 are part of radio access network (RAN) 120. RAN 120 provides radio access to UE 114 via radio access technology (RAT). Application server 111 communicates with UE 114 via User Plane Function (UPF) 116 and BS 115. Access and mobility function (AMF) 117 communicates with BS 115 to manage access and mobility of radio access devices in NR network 100. Session management function (SMF) 118 is primarily responsible for interacting with the decoupled data plane, creating, updating, and deleting PDU sessions, and managing session context with UPF 116. UE 114 can be equipped with one or more radio frequency (RF) transceivers to provide different application services through different RATs / CNs. UE 114 can be a smartphone, wearable device, IoT device, tablet, etc.

[0023] In 5G / NR, a PDU session defines the association between a UE and the data network providing PDU connectivity services. Each PDU session is identified by a PSI and may include multiple QoS flows and QoS rules. The network or the UE can initiate different PDU session procedures, such as PDU session establishment, PDU session modification, and PDU session release. When the UE receives a PDU session release command message from the network, the UE sends a PDU session release completion message to the network. However, when the UE is in an area with poor or no signal, it may not receive the PDU session release command message sent by the network. In this case, the network can release the session locally, and the UE will later become aware of the release through the PDU session state (IE) during registration. Since the UE is unaware of the reason for the release, it may attempt to rebuild the session, which may be rejected by the network and result in unnecessary signaling.

[0024] According to a new aspect, on the UE side, UE 114 first initiates the registration process by sending a registration request message 130 to BS 115. When UE 114 later receives an acceptance message 140 from BS 115 containing a reason value for releasing the session, UE 114 determines whether to rebuild the session based on the reason value.

[0025] Figure 2 An example flow 200 of the process for reconstructing a PDU session according to an embodiment of the present disclosure is described.

[0026] In step S211, network 202 determines to release the session with UE 201 by sending a PDU session release command message to UE 201. Note that network 202 can refer to any node in the wireless communication network. For example, network 202 can correspond to an access node (e.g., a base station, eNB, or gNB) or a core network node (e.g., AMF, SMF, or other core network entities). Network 202 may initiate the release of the PDU session with UE 201 for various reasons, including policy or subscription restrictions, resource management considerations, error handling (e.g., abnormal session establishment or context inconsistency), and mobility-related processes that cannot maintain the session. In these cases, network 202 may send a PDU session release command message to UE 201 to terminate the corresponding session. However, the PDU session release command message does not reach UE 201.

[0027] In step S212, UE 201 may trigger the registration process. For example, UE 201 may trigger the registration process in the following situations: periodic registration update, movement across registration areas, recovery from failed service requests, loss or failure of security or session context, and when specific services (such as emergency services, SMS-only services, or voice fallback) are required.

[0028] In step S213, UE 201 may send a request message (e.g., a registration request) to network 202 to initiate the registration process.

[0029] In step S214, UE 201 receives an acceptance message (e.g., registration acceptance REGISTRATIONACCEPT) from network 202, wherein the acceptance message may further include a reason value for releasing the session. In one embodiment, the reason value may include at least one of the following: reason code #8 corresponds to "operator-determined prohibition", #26 corresponds to "insufficient resources", #29 corresponds to "user authentication or authorization failure", #36 corresponds to "normal deactivation", #38 corresponds to "network failure", #39 corresponds to "reactivation request", #46 corresponds to "outside the Local Area Data Network (LADN) service area", #67 corresponds to "insufficient resources for a specific slice and data network name (DNN)", #69 corresponds to "insufficient resources for a specific slice", etc.

[0030] In step S215, UE 201 determines whether to rebuild the session based on the cause value. In some implementations, UE 201 may perform at least one of the following operations based on the cause value: rebuild the session, rebuild the session in response to a timer expiration, or not rebuild the session. For example, UE 201 may rebuild the session when cause code #36 corresponds to "normal deactivation" or #39 corresponds to "reactivation request". UE 201 may rebuild the session in response to a timer expiration when cause code #26 corresponds to "insufficient resources", #67 corresponds to "insufficient resources for a specific slice and DNN", or #69 corresponds to "insufficient resources for a specific slice". UE 201 may not rebuild the session when cause code #8 corresponds to "operator-determined ban", #29 corresponds to "user authentication or authorization failure", #38 corresponds to "network failure", or #46 corresponds to "outside LADN service area".

[0031] It should be understood that, despite Figure 2 The registration process is illustrated through a registration request and registration acceptance, but this disclosure is not limited thereto. In some cases, the request message may be a service request message, and the corresponding message may be a service acceptance message.

[0032] Example Implementation Figure 3 An example system 300, having at least an example communication device 310 and an example network device 320 according to an embodiment of the present disclosure, is shown. Each of the communication device 310 and the network device 320 can perform various functions to implement the schemes, techniques, processes, and methods described herein regarding the processing of PDU session reconstruction, including the scenarios / schemes described above and the processes 400 and 500 described below.

[0033] The communication device 310 may be part of an electronic device, which may include, for example, a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 310 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. The communication device 310 may also be part of a machine-type device, which may be an IoT, NB-IoT, eMTC, or IIoT device, such as a fixed or stationary device, a home appliance, a wired communication device, or a computing device. Alternatively, the communication device 310 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. The communication device 310 includes at least... Figure 3 Part of the components shown, such as processor 312. Communication device 310 further includes one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the scheme presented in this disclosure; therefore, for the sake of brevity, the aforementioned other components of communication device 310 are not shown. Figure 3 The middle part will not be described below.

[0034] Network device 320 may be part of a network device, which may be a network node such as a satellite, base station, small cell, router, or gateway. For example, network device 320 may be implemented in an eNB in ​​an LTE network, in a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or in a satellite or base station in a 6G network. Network device 320 includes at least... Figure 3 As shown, this is part of a component, such as processor 322. Processor 322 may also include a protocol stack and a set of control function modules and circuitry. Network device 320 also includes one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the scheme presented in this disclosure; therefore, for the sake of brevity, the aforementioned other components of network device 320 are not shown. Figure 3 The middle part will not be described below.

[0035] In one aspect, either processor 312 or processor 322 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though the singular term "processor" is used herein to refer to processor 312 and processor 322, in this disclosure, either processor 312 or processor 322 may include multiple processors in some embodiments and a single processor in others. In another aspect, either processor 312 or processor 322 may be implemented as hardware (and optionally, firmware) having electronic components, including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes configured for a particular purpose according to this disclosure. In other words, at least in some embodiments, processors 312 and 322 are special purpose machines specifically designed, arranged and configured to perform specific tasks in devices (e.g., represented by communication device 310) and network nodes (e.g., represented by network device 320) according to various embodiments of this disclosure.

[0036] In some embodiments, the communication device 310 further includes a memory 314 coupled to the processor 312, which can be accessed by the processor 312 and stores data therein. In some embodiments, the communication device 310 may also include a transceiver 316 coupled to the processor 312, which is capable of wirelessly transmitting and receiving data. In some embodiments, the transceiver 316 may be capable of wireless communication with wireless networks of different types of UEs and / or different RATs (e.g., 2G GSM, 3G UMTS, 4G LTE, 5G NR, and / or 6G).

[0037] In some embodiments, network device 320 further includes a memory 324 coupled to and accessible by processor 322 and storing data therein, and a transceiver 326 coupled to processor 322 and capable of wirelessly transmitting and receiving data. Therefore, communication device 310 and network device 320 can wirelessly communicate with each other via transceiver 316 and transceiver 326, respectively.

[0038] For illustrative purposes only and not for limitation, the capabilities of communication device 310 and network device 320 are described below through processes 400 and 500. Communication device 310 is implemented in or as a communication device or UE, and network device 320 is implemented in or as a network node of a communication network (e.g., a core network node).

[0039] Example Process Figure 4 Example flow 400 according to embodiments of this disclosure is described. Whether partially or entirely, flow 400 represents an example implementation of the scenarios and schemes presented above regarding the processing of PDU session reconstruction. Flow 400 represents an example implementation of the functionality of communication device 310. Flow 400 may include one or more operations, actions, or functions, as shown in one or more of steps 410, 420, and 430. Although described as discrete steps, the individual steps of flow 400 may be divided into additional steps, combined into fewer steps, or deleted as needed. Furthermore, the steps / sub-steps of flow 400 may be arranged according to… Figure 4 The process may be executed in the order shown, or in another order. Furthermore, one or more steps / sub-steps of process 400 may be repeated. Process 400 may be implemented by communication device 310 or any suitable UE (e.g., UE114) or machine-type device. For illustrative purposes only, but not limited thereto, process 400 is described in the context of communication device 310 as a UE. Process 400 begins at step 410.

[0040] In step 410, process 400 involves the processor 312 of communication device 310 sending a request message to a network node (e.g., network device 320) via transceiver 316. Process 400 continues from step 410 to step 420.

[0041] In step 420, process 400 involves processor 312 receiving an acceptance message from the network node via transceiver 316 in response to the request message, wherein the acceptance message includes a reason value for releasing the session. Process 400 continues from step 420 to step 430.

[0042] In step 430, process 400 involves processor 312 determining whether to rebuild the session based on the cause value.

[0043] In some implementations, process 400 involves processor 312 performing at least one of the following actions based on a cause value: re-establishing the session, re-establishing the session in response to a timer expiration, and not re-establishing the session.

[0044] In some implementations, the message to be accepted includes a registration acceptance message or a service acceptance message.

[0045] In some implementations, the session is a PDU session.

[0046] In some implementations, the cause value includes at least one of the following: 8 corresponds to "operator-determined ban", 26 corresponds to "insufficient resources", 29 corresponds to "user authentication or authorization failure", 36 corresponds to "normal shutdown", 38 corresponds to "network failure", 39 corresponds to "reactivation request", 46 corresponds to "outside LADN service area", 67 corresponds to "insufficient resources for specific slice and DNN", and 69 corresponds to "insufficient resources for specific slice".

[0047] In some implementations, process 400 involves processor 312 performing at least one of the following actions based on the cause value: re-establishing the session if the cause value is 36 or 39; re-establishing the session in response to the expiration of a timer if the cause value is 26, 67 or 69; and not re-establishing the session if the cause value is 8, 29, 38 or 46.

[0048] In some implementations, the network node is the core network node of the wireless communication network, and the wireless communication network is a 4G, 5G, or 6G cellular network.

[0049] Figure 5 An example flow 500 according to an embodiment of this disclosure is described. Whether partially or entirely, flow 500 represents an example implementation of the scenarios and schemes presented above regarding the processing of PDU session reconstruction. Flow 500 represents an example implementation of the functionality of network device 320. Flow 500 may include one or more operations, actions, or functions, as shown in one or more of steps 510, 520, and 530. Although described as discrete steps, the individual steps of flow 500 may be divided into additional steps, combined into fewer steps, or deleted as needed. Furthermore, the steps / sub-steps of flow 500 may be arranged according to… Figure 5 The steps / sub-steps of process 500 may be executed in the order shown, or in another order. Furthermore, one or more steps / sub-steps of process 500 may be repeated. Process 500 may be implemented by network device 320 or any network entity in a 4G, 5G, or 6G network, including base stations, AMFs, or SMFs. For illustrative purposes only, but not limited thereto, process 500 is described in the context of network device 320. Process 500 begins at step 510.

[0050] In step 510, process 500 involves the processor 322 of network device 320 determining to release the session with the UE (e.g., communication device 310). Process 500 continues from step 510 to step 520.

[0051] In step 520, process 500 involves processor 322 including the reason value for releasing the session in the accept message. Process 500 continues from step 520 to step 530.

[0052] In step 530, process 500 involves processor 322 sending an accept message to UE via transceiver 326.

[0053] In some implementations, the message to be accepted includes a registration acceptance message or a service acceptance message.

[0054] In some implementations, the session is a PDU session.

[0055] In some implementations, the cause value includes at least one of the following: 8 corresponds to "operator-determined ban", 26 corresponds to "insufficient resources", 29 corresponds to "user authentication or authorization failure", 36 corresponds to "normal shutdown", 38 corresponds to "network failure", 39 corresponds to "reactivation request", 46 corresponds to "outside LADN service area", 67 corresponds to "insufficient resources for specific slice and DNN", and 69 corresponds to "insufficient resources for specific slice".

[0056] In some implementations, reason value 36 or 39 indicates that the UE should rebuild the session, reason value 26, 67 or 69 indicates that the UE should rebuild the session when the timer expires, and reason value 8, 29, 38 or 46 indicates that the UE should not rebuild the session.

[0057] In some implementations, the network node is the core network node of the wireless communication network, and the wireless communication network is a 4G, 5G, or 6G cellular network.

[0058] Additional notes The subjects described in this disclosure are sometimes illustrated as different components included within or connected to other components. It should be understood that the architectures depicted are merely examples, and in reality, many other architectures can be implemented to achieve the same functionality. Conceptually, any arrangement of components used to achieve the same functionality is effectively “associated” to achieve the desired functionality. Therefore, any two components combined in this disclosure to achieve a particular function can be considered “associated” with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific examples of operably coupled components include, but are not limited to, physically pairable and / or physically interactive components and / or wirelessly interactive and / or logically interactive and / or logically interactive components.

[0059] Furthermore, in relation to virtually any use of plural and / or singular terms in this disclosure, those skilled in the art may convert plural to singular and / or singular to plural to suit the context and / or application. For clarity, various singular / plural substitutions may be explicitly set forth in this disclosure.

[0060] Furthermore, those skilled in the art should understand that, in general, the terms used in this disclosure, particularly in the appended claims (e.g., the body of the appended claims), are intended to be “open” terms. For example, the term “comprising” should be interpreted as “including but not limited to,” and the term “having” should be interpreted as “having at least,” etc. Those skilled in the art should also understand that if there is an intention to refer to a specific number of claim statements, this intention will be explicitly stated in the claims, and without such a statement, this intention does not exist. For example, to aid understanding, the following appended claims may include the use of the introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of these phrases should not be construed as implying that introducing a claim statement with the indefinite article “a” or “an” limits any particular claim that includes this introduced claim statement to an implementation that includes only this one statement, even when the claim includes the introductory phrase “one or more” or “at least one” and an indefinite article such as “a” or “an,” for example, “a” and / or “an” should be interpreted as meaning “at least one” and “one or more,” and the same applies to the use of definite articles for introducing claim statements. Furthermore, even in claims that explicitly state a specific number, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the stated number; for example, the plain statement "two statements" without other modifications means at least two statements or two or more statements. Moreover, in cases where the convention of "at least one of A, B, and C" is used, generally, from the perspective of those skilled in the art to understand this convention, the construction contemplated, for example, "a system having at least one of A, B, and C," will include, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In other cases where the convention of "at least one of A, B, or C" is used, generally, from the perspective of those skilled in the art to understand this convention, the construction contemplated, for example, "a system having at least one of A, B, or C," will include, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art should also understand that any conjunction and / or phrase (whether in the specification, claims, or drawings) that actually represents two or more alternative terms should be understood to imply the possibility of including one, any, or both of the terms. For example, the phrase “A or B” would be understood to include the possibility of including “A” or “B” or “A and B”.

[0061] Based on the foregoing, it should be understood that various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, wherein the true scope and spirit are indicated by the claims.

Claims

1. A method for processing session reconstruction, comprising: The device's processor sends a request message to the network node; The processor receives an acceptance message from the network node in response to the request message, wherein the acceptance message includes a reason value for releasing the session; as well as The processor determines whether to rebuild the session based on the cause value.

2. The method for processing session reconstruction as described in claim 1, characterized in that, Determining whether to rebuild the session based on the cause value also includes: Perform at least one of the following based on the stated cause value: Rebuild the session; The session is rebuilt in response to the expiration of the timer; and The session will not be rebuilt.

3. The method for processing session reconstruction as described in claim 1, characterized in that, The acceptance message includes a registration acceptance message or a service acceptance message.

4. The method for processing session reconstruction as described in claim 1, characterized in that, The session is a packet data unit session.

5. The method for processing session reconstruction as described in claim 1, characterized in that, The cause value includes at least one of the following: 8 corresponds to the prohibition specified by the operator; 26 corresponds to insufficient resources; 29 corresponds to user authentication or authorization failure; 36 corresponds to regular deactivation; 38 corresponds to a network failure; 39 corresponds to a request for reactivation; 46 corresponds to the area outside the local data network service area; 67. Insufficient resources corresponding to specific slice and data network names; as well as 69 corresponds to insufficient resources for a specific slice.

6. The method for processing session reconstruction as described in claim 5, characterized in that, Determining whether to rebuild the session based on the cause value also includes: Perform at least one of the following based on the stated cause value: Rebuild the session if the cause value is 36 or 39; The session is rebuilt in response to the timer's expiration if the cause value is 26, 67, or 69; and The session will not be rebuilt if the cause value is 8, 29, 38, or 46.

7. The method for processing session reconstruction as described in claim 1, characterized in that, The network node is the core network node of the wireless communication network, which is a fourth-generation, fifth-generation, or sixth-generation cellular network.

8. An apparatus for processing a session reconstruction process, comprising: A transceiver that enables wireless communication during operation; as well as The processor, which is communicatively connected to the transceiver, performs the following operations during operation: The transceiver sends a request message to the network node. The transceiver receives an acceptance message from the network node in response to the request message, wherein the acceptance message includes a reason value for releasing the session; and Whether to rebuild the session is determined based on the stated cause value.

9. The apparatus as claimed in claim 8, characterized in that, When determining whether to rebuild the session based on the cause value, the processor also performs the following operations: Perform at least one of the following based on the stated cause value: Rebuild the session; The session is rebuilt in response to the expiration of the timer; and The session will not be rebuilt.

10. The apparatus as claimed in claim 8, characterized in that, The acceptance message includes a registration acceptance message or a service acceptance message.

11. The apparatus as claimed in claim 8, characterized in that, The session is a packet data unit session.

12. The apparatus as claimed in claim 8, characterized in that, The cause value includes at least one of the following: 8 corresponds to the prohibition specified by the operator; 26 corresponds to insufficient resources; 29 corresponds to user authentication or authorization failure; 36 corresponds to regular deactivation; 38 corresponds to a network failure; 39 corresponds to a request for reactivation; 46 corresponds to the area outside the local data network service area; 67. Insufficient resources corresponding to specific slice and data network names; as well as 69 corresponds to insufficient resources for a specific slice.

13. The apparatus as claimed in claim 12, characterized in that, When determining whether to rebuild the session based on the cause value, the processor also performs the following operations: Perform at least one of the following based on the stated cause value: Rebuild the session if the cause value is 36 or 39; The session is rebuilt in response to the timer's expiration if the cause value is 26, 67, or 69; and The session will not be rebuilt if the cause value is 8, 29, 38, or 46.

14. The apparatus as claimed in claim 8, characterized in that, The network node is the core network node of the wireless communication network, which is a fourth-generation, fifth-generation, or sixth-generation cellular network.

15. A method for processing a session reconstruction process, comprising: The network node's processor determines to release the session with the user equipment; The processor includes the reason value for releasing the session in the received message; and The processor sends the acceptance message to the user equipment.

16. The method for processing session reconstruction as described in claim 15, characterized in that, The acceptance message includes a registration acceptance message or a service acceptance message.

17. The method for processing session reconstruction as described in claim 15, characterized in that, The session is a packet data unit session.

18. The method for processing session reconstruction as described in claim 15, characterized in that, The cause value includes at least one of the following: 8 corresponds to the prohibition specified by the operator; 26 corresponds to insufficient resources; 29 corresponds to user authentication or authorization failure; 36 corresponds to regular deactivation; 38 corresponds to a network failure; 39 corresponds to a request for reactivation; 46 corresponds to the area outside the local data network service area; 67. Insufficient resources corresponding to a specific slice and data network name; as well as 69. Insufficient resources for a specific slice.

19. The method for processing session reconstruction as described in claim 18, characterized in that, The cause value 36 or 39 indicates that the user equipment should rebuild the session, the cause value 26, 67 or 69 indicates that the user equipment should rebuild the session when the timer expires, and the cause value 8, 29, 38 or 46 indicates that the user equipment should not rebuild the session.

20. The method for processing session reconstruction as described in claim 15, characterized in that, The network node is the core network node of the wireless communication network, which is a fourth-generation, fifth-generation, or sixth-generation cellular network.

Images