WIRELESS NETWORK AND METHODS TO MAINTAIN MA PDU SESSION AT NSACF

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose a wireless network and methods to maintain a MA PDU session at a NSACF entity. The method includes determining, by a SMF entity, that a PDU session is the MA PDU session based on an indication from a UE. Further, the method includes indicating, by the SMF entity, that the PDU session is the MA PDU session to the NSACF entity in response to determination. The wireless network may maintain the count accurately even though the PDU session is a MA PDU session.

Claims

1. A method of a session management function (SMF) entity for managing a multiple access protocol data unit (MA PDU) session in a wireless communication network, the method comprising: receiving, from a user equipment (UE), an indication indicating that a PDU session is the MA PDU session; and transmitting, to a network slice admission control function (NSACF) entity, information on multiple access types and a PDU update request message.

2. The method as claimed in claim 1, wherein the PDU update request message includes a request to increase or decrease a number of PDU sessions during a MA PDU session establishment procedure or a PDU session release procedure.

3. The method as claimed in claim 1, wherein the PDU update request message indicates at least one of a 3.sup.rd generation partnership project (3GPP) access type or a non-3GPP access type.

4. The method as claimed in claim 1, comprises: receiving, from the NSACF entity, a result indication for each of the multiple access types and a back-off timer.

5. A method performed by a network slice admission control function (NSACF) entity for managing a multiple access protocol data unit (MA PDU) session in a wireless communication network, the method comprising: receiving, from a session management function (SMF) entity, information on multiple access types and a PDU update request message; and updating a number of the PDU sessions for at least one of the multiple access types based on the PDU update request message and the information.

6. The method as claimed in claim 5, wherein updating the number of the PDU sessions comprises at least one of increasing a count of the PDU session or decreasing the count of the PDU session.

7. The method as claimed in claim 5, wherein the PDU update request message indicates at least one of a 3.sup.rd generation project partnership (3GPP) access type or a non-3GPP access type.

8. The method as claimed in claim 5, comprises: transmitting, to the SMF entity, a result indication for each of the multiple access types and a back-off timer.

9. A session management function (SMF) entity for managing a multiple access protocol data unit (MA PDU) session in a wireless communication network, the SMF entity comprising: a processor; a communicator; and a MA PDU session managing controller, coupled with the processor and the communicator, configured to: receive, from a user equipment (UE), an indication indicating that a PDU session is the MA PDU session, and transmit, to a network slice admission control function (NSACF) entity (300), information on multiple access types and a PDU update request message.

10. The SMF entity as claimed in claim 9, wherein the PDU update request message includes a request to increase or decrease a number of PDU sessions during a MA PDU session establishment procedure or a PDU session release procedure.

11. The SMF entity as claimed in claim 9, wherein the PDU update request message indicates at least one of a 3.sup.rd generation partnership project (3GPP) access type or a non-3GPP access type.

12. The SMF entity as claimed in claim 9, wherein the MA PDU session managing controller is further configured to receive, from the NSACF entity, a result indication for each of the multiple access types and a back-off timer.

13. A network slice admission control function (NSACF) entity for managing a multiple access protocol data unit (MA PDU) session in a wireless communication network, the NSACF entity comprising: a processor; a communicator; and a MA PDU session managing controller, coupled with the processor and the communicator, configured to: receive, from a session management function (SMF) entity, information on multiple access types and a PDU update request message, and update a number of the PDU sessions for at least one of the multiple access types based on the PDU update request message and the information.

14. The NSACF entity as claimed in claim 13, wherein updating the number of the PDU sessions comprises at least one of increasing a count of the PDU session or decreasing the count of the PDU session.

15. The NSACF entity as claimed in claim 13, wherein the PDU update request message indicates at least one of a 3.sup.rd generation project partnership (3GPP) access type or a non-3GPP access type.

16. The NSACF entity as claimed in claim 13, wherein the MA PDU session managing controller is further configured to transmit, to the SMF entity, a result indication for each of the multiple access types and a back-off timer.

17. A wireless communication network for managing a multiple access protocol data unit (MA PDU) session, the wireless communication network comprising: a network slice admission control function (NSACF) entity; and a session management function (SMF) entity configured to: receive, from a user equipment (UE), an indication indicating that a PDU session is the MA PDU session, and transmit, to a NSACF entity, information on multiple access type and a PDU update request message; and wherein the NSACF entity is configured to: receive, from the SMF entity, the information on multiple access types and the PDU update request message, and update a number of the PDU sessions for at least one of the multiple access type based on the PDU update request message and the information.

18. The wireless communication network as claimed in claim 17, wherein the PDU update request message indicates at least one of a 3.sup.rd generation partnership project (3GPP) access type or a non-3GPP access type.

19. The wireless communication network as claimed in claim 17, wherein the PDU update request message includes a request to increase or decrease a number of PDU sessions during a MA PDU session establishment procedure or a PDU session release procedure.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0038] FIG. 1 illustrates an example scenario, where the NSACF decrease count of number of PDU sessions for a PDU session ID=1, but the PDU session is still active on non-3GPP access of MA PDU session, which results in the PDU session no longer being counted for the threshold according to prior arts;

[0039] FIG. 2 illustrates an example scenario in which the NSACF does not have access to type information and does not know that the PDU session type is MA PDU according to prior arts;

[0040] FIG. 3 illustrates an example scenario in which a count per access type is increased for the MA PDU session according to embodiments of the present disclosure;

[0041] FIG. 4 illustrates an example sequential flow diagram of an increasing count per access type for MA PDU session according to embodiments of the present disclosure;

[0042] FIG. 5 illustrates an example sequential flow diagram of a decreasing of a count per access type for MA PDU session during release according to embodiments of the present disclosure;

[0043] FIG. 6 illustrates an example sequential flow diagram of a threshold reached case according to embodiments of the present disclosure;

[0044] FIGS. 7A and 7B illustrate example scenarios in which the count per access type is decreased for the MA PDU session during release according to embodiments of the present disclosure;

[0045] FIG. 8 illustrates an example scenario in which a single count per access type is maintained for the MA PDU session according to embodiments of the present disclosure;

[0046] FIG. 9 illustrates an example scenario in which a single count per access type is maintained for the MA PDU session according to embodiments of the present disclosure;

[0047] FIG. 10 illustrates an example scenario in which the count per access type is decreased for the MA PDU session during release according to embodiments of the present disclosure;

[0048] FIG. 11 illustrates various hardware components of a SMF (e.g., SMF entity) for managing MA PDU session in a wireless network according to embodiments of the present disclosure;

[0049] FIG. 12 illustrates various hardware components of a NSACF (e.g., NSACF entity) for managing MA PDU session in the wireless network according to embodiments of the present disclosure;

[0050] FIG. 13 illustrates a flow chart of a method, implemented by the SMF entity, for managing the MA PDU session in the wireless network according to of the present disclosure; and

[0051] FIG. 14 illustrates a flow chart of a method, implemented by the NSACF entity, for managing the MA PDU session in the wireless network according to the present disclosure.

DETAILED DESCRIPTION

[0052] FIGS. 1 through 14, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0053] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0054] The embodiments herein achieve methods and a wireless network for managing a MA PDU session in the wireless network. The method includes determining, by a SMF entity, that a PDU session is the MA PDU session based on an indication from a UE. Further, the method includes indicating, by the SMF entity, that the PDU session is the MA PDU session to a NSACF entity in response to determination.

[0055] In an embodiment, the SMF entity indicates to the NSACF entity that the PDU session is for multiple access type then the NSACF entity increases the count of number of PDU sessions separately for each access type. Further, if release procedure is executed then, the SMF indicates that a MA PDU session is released. Further, the NSACF entity automatically reduces the count on both the accesses, if only one of the access is released, this is indicated to the NSACF entity which may release the respective access type. Hence, the accurate count is maintained at the NSACF entity.

[0056] In an embodiment, if threshold is reached then, the NSACF entity indicates to the SMF entity, the Access type-combination on which establishing the PDU session is not successful. The SMF entity indicates to the UE in one of the 5GMM or 5GSM signaling message, the cause, back-off timer, access-type combination on which establishing the MA PDU session is not successful. The UE attempts again on respect access type-combination after back-off timer is expired. The wireless network may maintain the count accurately even though the PDU session is a MA PDU session. Referring now to the drawings, and more particularly to FIGS. 3 through 14, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0057] In an embodiment, the SMF+PGW-C can be the SMF alone or packet data network (PDN) gateway (PGW) alone or a combined node, performing the actions discussed herein.

[0058] In an embodiment, on 3GPP access of MA PDU session can be applicable to one of an evolved packet system (EPS) and a 5G core (5GC).

[0059] In an embodiment, the indication of the MA PDU session from SMF to NSACF is optional. The NSACF can increase or decrease based on access type as discussed herein.

[0060] FIG. 3 illustrates example scenario in which the count per access type is increased for the MA PDU session. The NSACF (300) controls (i.e., increases or decreases) the current number of PDU sessions per network slice, so that the current number of PDU sessions does not exceed the maximum number of PDU sessions allowed to be served by that network slice. As per the provided method, the SMF (200) provides the access type to the NSACF (300), when triggering a request to increase the number of PDU sessions during MA PDU session establishment on one or both the access types as applicable. The user plane resources of one access type of MA PDU session may be established at a later point, when the UE (100) and a network deem necessary.

[0061] The SMF (200) may also provide the PDU session type as a MA PDU session to the NSACF (300). The NSACF (300) may also determine a PDU session as a MA PDU session, if the same PDU session ID, UE ID is received on both 3GPPA and N3GPPA. The NSACF (300) takes the access type and/or the PDU session type into account for increasing the number of PDUs per network slice. The NSACF (300) stores the PDU session ID with the associated one or more access type(s), i.e., the NSACF (300) is able to add a PDU session ID for each access Type for MA PDU sessions. When the current number of PDU sessions with the network slice is to be increased for the MA PDU session for any of the access type, the NSACF (300) first checks whether the maximum number of PDU sessions for that network slice has already been reached.

[0062] In step 1, the PDU session establishment with request type as “MA PDU request” is sent by the UE (100) in UL NAS transport message and its ATSSS capabilities. In step 2, the AMF supports the MA PDU sessions, then the AMF selects the SMF (200), which supports the MA PDU sessions. In step 3, the SMF+PGW-C (200) triggers interaction with the NSACF (300) to increase the number of PDU session counts for the 3GPP access (400). The SMF+PGW-C (200) indicates the PDU session type as MA PDU session. In step 4, the NSACF (300) checks if the current PDU session is a MA PDU session and increases the number of PDU sessions for 3GPP access (400). In step 5, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to increase the number of PDU session counts for non 3GPP access (500). The SMF+PGW-C (200) indicates the PDU session type as a MA PDU session. In step 6, the NSACF (300) checks if the current PDU session is a MA PDU session and increases the number of PDU sessions for non-3GPP access (500) (if the current PDU session is a MA PDU session).

[0063] FIG. 4 illustrates an example sequential flow diagram of increasing count per access type for a MA PDU session according to embodiments of the present disclosure.

[0064] At 1, the PDU session establishment with a request type as “MA PDU request” in UL NAS transport message and its ATSSS capabilities is shared between the UE (100) and the AMF over the 3GPP access (400). At 2, the AMF supports the MA PDU sessions, then the AMF selects an SMF, which supports MA PDU sessions. At 3, the SMF+PGW-C triggers (200) interaction with the NSACF (300) to increase number of PDU session counts. The SMF+PGW-C (200) indicates the PDU session type as an MA PDU session for example the SMF+PGW-C (200) indicates the PDU session as an MA PDU session by providing multiple access types/additional access type to the NSACF (300).

[0065] At 4, the NSACF (300) identifies that a PDU session is a MA PDU session based on indication from SMF+PGW-C (200) and and controls the count of access type combination of the PDU session based on the access type configured for the NSAC. That is, if the NSACF (300) is configured to count 3GPP access count then the NSACF (300) increases the count of 3GPP access, if the NSACF (300) is configured to count non-3GPP access count then NSACF (300) increases the count of non-3GPP access. If the NSACF (300) is configured to count both 3GPP access and non-3GPP access then NSACF (300) increases the count of both the 3GPP access and non-3GPP access.

[0066] FIG. 5 illustrates an example sequential flow diagram of decreasing count per access type for a MA PDU session during release according to embodiments of the present disclosure.

[0067] At 1, the PDU session release triggered by the UE (100) or network request for a MA PDU session or the SMF triggers the PDU session release for the MA PDU session for both access type. At 2, the SMF+PGW-C (200) triggers interaction with the NSACF (300) to decrease number of PDU session counts because the PDU session has to be released on both the legs of 3GPP access and non-3GPP access. The SMF+PGW-C (200) indicates the PDU session type as the MA PDU session for example the SMF+PGW-C (200) indicates the PDU session as a MA PDU session by providing multiple access types/additional access type to the NSACF (300). At 3, the NSACF (300) identifies that the PDU session is a MA PDU session based on indication from the SMF+PGW-C (200) and and controls the count of access type combination of the PDU session based on the access type configured for the NSAC. That is, if the NSACF (300) is configured to count 3GPP access count then the NSACF (300) decreases the count of 3GPP access. If the NSACF (300) is configured to count the non-3GPP access count then the NSACF (300) decrease the count of non-3GPP access. If NSACF is configured to count both 3GPP access and non-3GPP access then the NSACF (300) decreases the count of both the 3GPP access and non-3GPP access.

[0068] FIG. 6 illustrates an example sequential flow diagram of a threshold reached case according to embodiments as of the present disclosure.

[0069] At 1, the PDU session establishment with request type as “MA PDU request” in UL NAS Transport message and its ATSSS capabilities is transferred between the UE (100) and the AMF over the 3GPP access (400). At 2, the AMF supports the MA PDU sessions, then the AMF selects the SMF, which supports a MA PDU sessions. At 3, the SMF+PGW-C (200) triggers the interaction with the NSACF (300) to increase number of PDU session counts. The SMF+PGW-C (200) indicates the PDU session type as MA PDU session for example the SMF+PGW-C (200) indicates the PDU session as a MA PDU session by providing multiple access types/additional access type to the NSACF (300).

[0070] At 4, the NSACF (300) identifies that a PDU session is a MA PDU session based on indication from SMF+PGW-C (200) and and controls the count of access type combination of the PDU session based on the access type configured for the NSAC. That is, if the NSACF (300) is configured to count 3GPP access count then the NSACF (300) increases the count of 3GPP access, the if NSACF (300) is configured to count non-3GPP access count then the NSACF (300) increases the count of non-3GPP access. If the NSACF (300) is configured to count both 3GPP access and non-3GPP access then the NSACF (300) increases the count of both the 3GPP access and non-3GPP access.

[0071] At 5, if at least one of the access type count threshold is reached (i.e. already maximum allowable PDU sessions are established for a given access) then the NSACF (300) indicates failure to the SMF+PGW-C (300). The NSACF (300) indicates “maximum number of PDU sessions per S-NSSAI reached” associated with the access type. At 6, the SMF-PGW-C (200) sends the PDU session establishment reject/PDU session establishment accept or any other 5GSM/5GMM signaling message with the result indication including “maximum number of PDU sessions per S-NSSAI reached,” optionally a back-off timer and the access type to the UE (100). The UE (100) may consider that PDU session establishment was not successful for the access type indicated by the SMF. The access type can be 3GPP access, non-3GPP access or both 3GPP access and non-3GPP access. The UE (100) is expected to retry the establishment of the PDU session on the failed access again optionally after the back-off timer is expired.

[0072] FIGS. 7A and 7B illustrate example scenarios in which the count per access type is decreased for the MA PDU session during release. As per the provided method, the SMF (200) provides the access type to the NSACF (300), when triggering a request to decrease the number of PDUs during the MA PDU session release on one or both the access types as applicable. The SMF (200) may also provide the PDU session type as a MA PDU session to the NSACF (300). The NSACF (300) takes an access type and/or a PDU session type into account for decreasing the number of PDUs per network slice. The NSACF (300) stores the PDU session ID with the associated one or more access type(s), i.e. the NSACF (300) is able to remove PDU session ID for each access Type for the MA PDU sessions.

[0073] Referring to FIG. 7A, in step 1, a PDU session release is triggered by the UE (100) or the network request for the MA PDU session or the SMF (200) triggers the PDU session release for the MA PDU session for both access types. In step 2, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to decrease the number of PDU session counts for 3GPP access (400). The SMF+PGW-C (200) indicates the PDU session type as a MA PDU session. In step 3, the NSACF (300) checks if the current PDU session is a MA PDU session and decreases the number of PDU sessions for 3GPP access (400). In step 4, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to decrease the number of PDU session counts for non 3GPP access (400). The SMF+PGW-C (200) indicates the PDU session type as a MA PDU session. In step 5, the NSACF (300) checks if the current PDU session is a MA PDU session and decreases the number of PDU sessions for non 3GPP access (400).

[0074] Referring to FIG. 7B, in step 1, the UE (100) provides a PDU session release request for the MA PDU session or the SMF (200) triggers a PDU session release for the MA PDU session for 3GPP access type. In step 2, the SMF+PGW-C (200) triggers the interaction with the NSACF (300) to decrease the number of PDU session counts for the 3GPP access (400). The SMF+PGW-C (200) indicates the PDU session type as a MA PDU session. In step 3, the NSACF (300) checks if the current PDU session is a MA PDU session and decreases the number of PDU sessions for 3GPP access (400).

[0075] FIG. 8 illustrates an example scenario in which the single count per access type is maintained for the MA PDU session. The NSACF (300) controls (i.e., increases or decreases) the current number of PDU sessions per network slice, so that the current number of PDU sessions does not exceed the maximum number of PDU sessions allowed to be served by that network slice. As per the provided method, the SMF (200) provides the PDU session type as a MA PDU to the NSACF (300), when triggering a request to increase the number of PDU sessions during MA PDU session establishment on one or both the access types (as applicable). The NSACF (300) may also determine a PDU session as a MA PDU session, if the same PDU session ID, a UE ID is received on both 3GPPA and N3GPPA. The NSACF (300) increases the number of PDU sessions only once for a MA PDU session irrespective of access type(s).

[0076] In step 1, the UE (100) provides the request type as “MA PDU request” in UL NAS transport message and its ATSSS capabilities. In step 2, the AMF supports the MA PDU sessions, then the AMF selects an SMF (200), which supports the MA PDU sessions. In step 3, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to increase the number of PDU session counts for 3GPP access (400) and indicates the PDU session type as a MA PDU session. In step 4, the NSACF (300) checks if the current PDU session is a MA PDU session and increases the number of PDU sessions. In step 5, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to increase the number of PDU session counts for non 3GPP access (400) and indicates the PDU session type as a MA PDU session. In step 6, the NSACF (300) checks if the current PDU session is a MA PDU session and already exists, the PDU session count may not be increased. In step 7, the NSACF (300) identifies that a given PDU session ID is a MA PDU session, when the MA PDU session is indicated from the SMF (200) or if the PDU session ID is the same for both 3GPP access type and non-3GPP access type. A MA PDU session second request to increase the PDU session count of second access type is neglected by the NSACF (300) and is not counted against the threshold.

[0077] FIG. 9 illustrates an example scenario in which a single count per access type is maintained for the MA PDU session. In step 1, the PDU session establishment, request type are sent by the UE (100) as “MA PDU request” in UL NAS transport message and its ATSSS capabilities. In step 2, the AMF supports the MA PDU sessions, then the AMF selects an SMF (200), which supports the MA PDU sessions. In step 3, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to increase the number of PDU session counts for 3GPP access (400) and indicates the PDU session type as a MA PDU session. SMF+PGW-C (200) also stores the MA PDU session ID. In step 4, the NSACF (300) checks if the current PDU session is a MA PDU session and increases the number of PDU sessions. In step 5, the MA PDU session is established over non 3GPP access (500). In step 6, the SMF+PGW-C (200) checks if the current PDU session is a MA PDU session and admission control has already been done. The SMF+PGW-C (200) may not trigger interaction with the NSACF (300) to increase the number of PDU session counts for non-3GPP access type. Thus, maintaining the single count. Similarly, when the PDU session is released, the SMF+PGW-C (200) may trigger an interaction with the NSACF (300) to decrease the number of PDU session counts when the PDU session is released, i.e., on both the access types. When the PDU session or user plane resources are released on first access type, but second access type PDU session is active of MA-PDU session, then the SMF+PGW-C (200) does not trigger an interaction with the NSACF (300) to decrease the number of PDU session counts.

[0078] FIG. 10 illustrates an example scenario in which the count per access type is decreased for the MA PDU session during release. As per the provided method, the SMF (200) provides the PDU session type as a MA PDU session to the NSACF (300), when triggering a request to decrease the number of PDUs during MA PDU session release on one or both the access types as applicable. The NSACF (300) takes PDU session type into account for decreasing the number of PDUs per network slice. The NSACF (300) removes the PDU session ID for the MA PDU session only, when the PDU session is being released for all corresponding access types.

[0079] In step 1, the UE (100) provides a PDU session release request for MA PDU session or SMF (200) triggers PDU session release for a MA PDU session for both access types. In step 2, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to decrease the number of PDU session counts for 3GPP access (400). The SMF+PGW-C (200) indicates the PDU session type as MA PDU session. In step 3, the NSACF (300) checks if the current PDU session is a MA PDU session and does not decrease the number of PDU counts. In step 4, the SMF+PGW-C (200) triggers an interaction with the NSACF (300) to decrease the number of PDU session counts for non 3GPP access (500). The SMF+PGW-C (200) indicates the PDU session type as a MA PDU session. In step 5, the NSACF (300) checks if the current PDU session is a MA PDU session and decreases the number of PDU sessions as no other access type has the MA PDU session active.

[0080] Embodiments herein can convert the MA PDU to a normal PDU. While indicating the increment for the second access type, if the threshold is reached, then the MA-PDU session is converted into a normal PDU session; i.e., in response to PDU session establishment request requesting to establish the MA PDU session, the SMF (200) may indicate to the UE (100) that one of the access either 3GPP access type or non-3GPP access type PDU session establishment is not successful and this PDU session may be considered as single access PDU session. The SMF (200) can decide based on the access type on which SMF (200) received the PDU session establishment request only to be allowed.

[0081] For this, SMF (200) always sends NSACF_PDU session increment requests for the first access type (e.g., 3GPP access type) on which the SMF received PDU session establishment request message from the UE. Once this check is successful and is allowed, the second PDU session establishment check i.e. NSACF_PDU session increment requests for second access i.e. other access type (for e.g., non-3GPP access type) is sent and if the second access type check is also successful, then the MA PDU session is established. The SMF (200) indicates to the UE (100) in the NAS signalling message like 5GMM or 5GSM signalling message that this request to establish a MA PDU session is not successful and the current PDU session has to be considered as a single access PDU session.

[0082] In yet another embodiment, the SMF (200) can indicate cause (for e.g., congestion) to the UE (100) along with the timer and indicate the PDU session establishment has failed to establish, UE (100) is expected to retry the establishment of the PDU session again optionally after the congestion timer is expired. Meanwhile as the PDU session establishment for the first access type was successful SMF (200) may send NSACF_PDU session decrement requests for the first access type(e.g., 3GPP access type) of this PDU session. When the UE (100) (after the optionally congestion timer expires) may retry again, the SMF (200) may requests to increment again for both the access types.

[0083] FIG. 11 illustrates various hardware components of the SMF entity (200) for managing a MA PDU session in the wireless network (1000) according to embodiments of the present disclosure. In an embodiment, the SMF entity (200) includes a processor (210), a communicator (220), memory (230) and a MA PDU session managing controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the controller (240).

[0084] The MA PDU session managing controller (240) determines that the PDU session is the MA PDU session based on an indication from the UE (100). Further, the MA PDU session managing controller (240) indicates that the PDU session is the MA PDU session to the NSACF entity (300) in response to determination.

[0085] The MA PDU session managing controller (240) is physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0086] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache).

[0087] Although the FIG. 11 illustrates various hardware components of the SMF entity (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the SMF entity (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the present disclosure. One or more components can be combined together to perform same or substantially similar function in the SMF entity (200).

[0088] FIG. 12 illustrates various hardware components of the NSACF entity (300) for managing a MA PDU session in the wireless network (1000) according to the embodiments of the present disclosure. In an embodiment, the NSACF entity (300) includes a processor (310), a communicator (320), memory (330) and a MA PDU session managing controller (340). The processor (310) is coupled with the communicator (320), the memory (330) and the MA PDU session managing controller (340).

[0089] The MA PDU session managing controller (340) receives the identification that the PDU session is the MA PDU session and controls the count of access type combination of the PDU session based on the access type configured for the NSAC in the NSACF entity (300) based on the received identification. Further, the MA PDU session managing controller (340) stores the PDU session ID associated with the access type combination at the NSACF entity (300).

[0090] The MA PDU session managing controller (340) is physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0091] Further, the processor (310) is configured to execute instructions stored in the memory (330) and to perform various processes. The communicator (320) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (330) also stores instructions to be executed by the processor (310). The memory (330) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (330) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (330) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache).

[0092] Although the FIG. 12 illustrates various hardware components of the NSACF entity (300) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the NSACF entity (300) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the present disclosure. One or more components can be combined together to perform same or substantially similar function in the NSACF entity (300).

[0093] FIG. 13 illustrates a flow chart (S1300) of a method, implemented by the SMF entity (200), for managing the MA PDU session in the wireless network (1000) according to embodiments of the present disclosure.

[0094] As shown in the FIG. 13, the operations (S1302 and S1304) are handled by the MA PDU session managing controller (240). At S1302, the method includes determining that the PDU session is the MA PDU session based on an indication from the UE (100). At S1304, the method includes indicating that the PDU session is the MA PDU session to the NSACF entity (300) in response to determination.

[0095] FIG. 14 illustrates a flow chart (S1400) of a method, implemented by the NSACF entity (300), for managing the MA PDU session in the wireless network (1000) according to embodiments of the present disclosure.

[0096] As shown in the FIG. 14, the operations (S1402 and S1404) are handled by the MA PDU session managing controller (340). At S1402, the method includes receiving the identification that the PDU session is the MA PDU session. At S1404, the method includes controlling the count of access type combination of the PDU session based on the access type configured for the NSAC in the NSACF entity (300) based on the received identification.

[0097] Based on the provided methods, the wireless network may maintain the count accurately even though the PDU session is a MA PDU session.

[0098] The various actions, acts, blocks, steps, or the like in the flow charts (S1300 and S1400) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure.

[0099] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.

[0100] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

[0101] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.