METHOD, UE AND NETWORK APPARATUS TO HANDLE SERVICE REQUEST PROCEDURE IN WIRELESS NETWORK

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate.

A method for handling Service Request (SR) procedure in a wireless network by a network apparatus is provided. The method includes initiating a User Equipment Configuration Update (UCU) procedure. Further, the method includes receiving a SR message from a Multi SIM (MUSIM) UE before completion of the UCU procedure. Further, the method includes determining whether the SR message comprises a User Equipment (UE) request type Information Element (IE) set to “Non-Access Stratum (NAS) signaling connection release”. In an embodiment, the method includes aborting the UCU procedure and processing the SR procedure in response to determining that the service request message comprises the UE request type IE set to “NAS signaling connection release”. In another embodiment, the method includes processing both the UCU procedure and the SR procedure in response to determining that the SR message does not comprises the UE request type IE set to “NAS signaling connection release”.

Claims

1. A method performed by a network apparatus in a wireless network, the method comprising: initiating a user equipment (UE) configuration update (UCU) procedure; receiving a service request (SR) message from a UE before completion of the UCU procedure; determining whether the SR message includes a UE request type information set to a value indicating non-access stratum (NAS) signaling connection release; and performing one of: aborting the UCU procedure and progressing an SR procedure in response to determining that the SR message includes the UE request type information, or progressing both the UCU procedure and the SR procedure in response to determining that the SR message does not include the UE request type information.

2. The method of claim 1, wherein the UE is a multi subscriber identity module (SIM) (MUSIM) UE.

3. The method of claim 1, wherein the SR message includes flag indicating to release connection.

4. A method performed by a user equipment (UE) in a wireless network, the method comprises: transmitting a service request (SR) message to a network apparatus; receiving a UE configuration update (UCU) message from the network apparatus before completion of an SR procedure; and performing one of: aborting a UE configuration update (UCU) procedure by ignoring the UCU message received from the network apparatus and proceeding with the SR procedure, in case that the SR message includes UE request type information set to a value indicating non-access stratum (NAS) signaling connection release, or proceeding both the UCU procedure and the SR procedure in case that the SR message does not include the UE request type information.

5. The method of claim 4, wherein the UE is a multi subscriber identity module (SIM) (MUSIM) UE.

6. The method of claim 4, wherein the SR message includes flag indicating to release connection.

7. The method of claim 4, in case that a collision between the network initiated deregister message and the SR message occurs, further comprising: aborting a deregister procedure.

8. A network apparatus in a wireless network, wherein the network apparatus comprises: transceiver; at least one processor communicatively connected to the transceiver, wherein the at least one processor is configured to: initiate a user equipment (UE) configuration update (UCU) procedure, receive a service request (SR) message from a UE before completion of the UCU procedure, determine whether the SR message includes a UE request type information set to a value indicating non-access stratum (NAS) signaling connection release; and perform one of: aborting the UCU procedure and progressing an SR procedure in response to determining that the SR message includes the UE request type information, and progressing both the UCU procedure and the SR procedure in response to determining that the SR message does not include the UE request type information.

9. The network apparatus of claim 8, wherein the UE is a multi subscriber identity module (SIM) (MUSIM) UE.

10. The network apparatus of claim 8, wherein the SR message includes flag indicating to release connection.

11. A user equipment (UE) in a wireless network, wherein the UE comprises: a transceiver; and at least one processor, communicatively connected to the transceiver, wherein the at least one processor is configured to: transmit a service request (SR) message to a network apparatus, receive a UE configuration update (UCU) message from the network apparatus before completion of an SR procedure, and perform one of: aborting a UCU procedure by ignoring the UCU message received from the network apparatus and proceeding with the SR procedure, in case that the SR message includes UE request type information set to a value indicating non-access stratum (NAS) signaling connection release, or proceeding both the UCU procedure and the SR procedure in case that the SR message does not include the UE request type information.

12. The UE of claim 11, wherein the UE is a multi subscriber identity module (SIM) (MUSIM) UE.

13. The UE of claim 11, wherein the SR message includes flag indicating to release connection.

14. The UE of claim 11, wherein, in case that a collision between the network initiated deregister message and the SR message occurs, the at least one processor is further configured to abort a deregister procedure.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0042] FIG. 1 is an example scenario in which a service request and de-registration procedure collision is depicted, according to the related art;

[0043] FIG. 2 is an example scenario in which a service request and identification procedure is depicted, according to the related art;

[0044] FIG. 3 illustrates an overview of a network apparatus, according to an embodiment of the disclosure;

[0045] FIG. 4 illustrates various hardware components of a network apparatus, according to an embodiment of the disclosure;

[0046] FIG. 5 illustrates various hardware components of a MUSIM UE, according to an embodiment of the disclosure;

[0047] FIG. 6 is a flow chart illustrating a method, implemented by a network apparatus, for handling an SR procedure in a wireless network, according to an embodiment of the disclosure;

[0048] FIG. 7 is a flow chart illustrating a method, implemented by MUSIM UE, for handling an SR procedure in a wireless network, according to an embodiment of the disclosure;

[0049] FIG. 8 is an example in which a service request and a de-registration procedure collision is depicted, according to an embodiment of the disclosure;

[0050] FIG. 9 is an example scenario in which a service request and identification procedure is depicted, according to an embodiment of the disclosure; and

[0051] FIG. 10 is an example scenario in which a paging procedure and service request procedure collision is depicted, according to an embodiment of the disclosure.

[0052] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.

DETAILED DESCRIPTION

[0053] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0054] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0055] It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

[0056] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are 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 and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0057] Accordingly, the embodiment herein is to provide a method for handling an SR procedure in a wireless network. The method includes initiating, by a network apparatus in the wireless network, a UCU procedure. Further, the method includes receiving, by the network apparatus, an SR message from a Multi SIM (MUSIM) UE before completion of the UCU procedure. Further, the method includes determining, by the network apparatus, whether the SR message comprises a UE request type IE set to “NAS signaling connection release”. In an embodiment, the method includes aborting the UCU procedure and processing the SR procedure in response to determining that the service request message comprises the UE request type IE set to “NAS signaling connection release”. In another embodiment, the method includes processing both the UCU procedure and the SR procedure in response to determining that the SR message does not comprises the UE request type IE set to “NAS signaling connection release”.

[0058] In an embodiment, the UE transmits service request with UE request type set to “NAS signaling connection release”. IF the UE receives UE configuration update command, before completion of service request procedure i.e., before service accept message is received from the network apparatus. The UE aborts the UE configuration update procedure by ignoring the UCU message and progresses the Service request procedure, if the service request includes UE request type set to “NAS signaling connection release”. If the UE has not included UE request type set to “NAS signaling connection release” both service request and UCU procedures are progressed.

[0059] The terms UCU message, CONFIGURATION UPDATE COMMAND message, and UE configuration update message are used interchangeable and have same meaning.

[0060] The terms Release request, release flag, release, UE request type IE set to “NAS signaling connection release” are used interchangeable and have same meaning. This flag is used by the UE in service request or registration request message to request network to release the UE to IDLE or RRC Inactive state.

[0061] The terms UCU procedure and generic UE configuration update procedure are used interchangeably and have same meaning.

[0062] Referring now to the drawings and more particularly to FIGS. 3 through 10, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0063] FIG. 3 illustrates an overview of a wireless network, according to an embodiment of the disclosure.

[0064] Referring to FIG. 3, a wireless network 1000 includes a MUSIM UE 100 and a network apparatus 400. The wireless network 1000 may be, for example, but not limited to a 5.sup.th wireless network, 6G network, an ORAN or the like. The MUSIM UE 100 can be, for example, but not limited to a laptop, a desktop computer, a notebook, a relay device, a Device-to-Device (D2D) device, a vehicle to everything (V2X) device, a smartphone, a tablet, an immersive device, or an internet of things (IoT) device.

[0065] The MUSIM UE 100 is configured to initiate the SR procedure and transmit an SR message by including or not including a UE request type IE set to “NAS signaling connection release” to the network apparatus 400 in the wireless network 1000. Further, the MUSIM UE 100 is configured to receive the UCU message from the network apparatus 400 before completion of the SR procedure. In an embodiment, the MUSIM UE 100 is configured to abort a UE configuration update procedure by ignoring the UCU message received from the network apparatus 400 and progress the SR procedure, when the SR message includes the UE request type IE set to “NAS signaling connection release”. In another embodiment, the MUSIM UE 100 is configured to process both the UCU procedure and the SR procedure in response to when the SR message does not comprise the UE request type IE set to “NAS signaling connection release”.

[0066] In an embodiment, the network apparatus 400 is configured to initiate a UCU procedure and receive an SR message from the MUSIM UE 100 before completion of the UCU procedure. Further, the network apparatus 400 is configured to determine whether the SR message comprises a UE request type IE set to “NAS signaling connection release”. In response to determining that the service request message comprises the UE request type IE set to “NAS signaling connection release”, the network apparatus 400 is configured to abort the UCU procedure and process the SR procedure. In response to determining that the SR message does not comprises the UE request type IE set to “NAS signaling connection release”, the network apparatus 400 is configured to process both the UCU procedure and the SR procedure.

[0067] The first UE of the MUSIM UE 100 transmits a NAS message to the network apparatus 400 by including a release request flag to indicate to the network apparatus 400 that it wants to release the signaling connection and get into either INACTIVE state or IDLE state so that the MUSIM UE 100 initiates operation on the second SIM.

[0068] In the proposed method all the description is provided with the NAS message for e.g., service request message (with release request flag) as a description but same disclosure holds good when the MUSIM UE 100 has initiated service request message without release request flag.

[0069] In the proposed method all the description explains taking the NAS message, service request message as an example. Same is applied to all other UE initiated NAS procedures too unless explicitly mentioned for any particular NAS message name.

[0070] All the description provided here is from the perspective of 5GS but same disclosure is equally applicable for an Evolved Packet System (EPS) case core network node is a Mobility Management Entity (MME) instead of an Access and Mobility Management Function (AMF).

[0071] In this document, the first UE of MUSIM UE 100 is assumed to initiate service request in connected mode (or connected state) is only for illustration but the disclosure is equally applicable for first UE in the IDLE or INACTIVE state.

[0072] FIG. 4 illustrates various hardware components of a MUSIM UE, according to an embodiment of the disclosure.

[0073] Referring to FIG. 4, the MUSIM UE 100 includes a processor 110, a communicator 120 (transceiver), a memory 130, and an SR procedure controller 140. The processor 110 is coupled with the communicator 120, the memory 130, and the SR procedure controller 140.

[0074] The SR procedure controller 140 is configured to initiate the SR procedure and transmit the SR message by including or not including the UE request type IE set to “NAS signaling connection release” to the network apparatus 400 in the wireless network 1000. Further, the SR procedure controller 140 is configured to receive the UCU message from the network apparatus 400 before completion of the SR procedure. In an embodiment, the SR procedure controller 140 is configured to abort a UE configuration update procedure by ignoring the UCU message received from the network apparatus 400 and progress the SR procedure, when the SR message includes the UE request type IE set to “NAS signaling connection release”. In another embodiment, the SR procedure controller 140 is configured to process both the UCU procedure and the SR procedure in response when the SR message does not comprise the UE request type IE set to “NAS signaling connection release”.

[0075] The SR procedure controller 140 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.

[0076] Further, the processor 110 is configured to execute instructions stored in the memory 130 and to perform various processes. The communicator 120 is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory 130 also stores instructions to be executed by the processor 110. The memory 130 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 130 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 130 is non-movable. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0077] Although the FIG. 4 shows various hardware components of the MUSIM UE 100 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the MUSIM UE 100 may include lessor or greater 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 disclosure. One or more components can be combined together to perform same or substantially similar function in the MUSIM UE 100.

[0078] FIG. 5 illustrates various hardware components of a network apparatus, according to an embodiment of the disclosure.

[0079] Referring to FIG. 5, the network apparatus 400 includes a processor 410, a communicator 420 (transceiver), a memory 430, and an SR procedure controller 440. The processor 410 is coupled with the communicator 420, the memory 430, and the SR procedure controller 440.

[0080] The SR procedure controller 440 is configured to initiate a UCU procedure and receive an SR message from the MUSIM UE 100 before completion of the UCU procedure. Further, the SR procedure controller 440 is configured to determine whether the SR message comprises a UE request type IE set to “NAS signaling connection release”. In response to determining that the service request message comprises the UE request type IE set to “NAS signaling connection release”, the SR procedure controller 440 is configured to abort the UCU procedure and process the SR procedure. In response to determining that the SR message does not comprises the UE request type IE set to “NAS signaling connection release”, the SR procedure controller 440 is configured to process both the UCU procedure and the SR procedure.

[0081] The SR procedure controller 440 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.

[0082] Further, the processor 410 is configured to execute instructions stored in the memory 430 and to perform various processes. The communicator 420 is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory 430 also stores instructions to be executed by the processor 410. The memory 430 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 430 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 430 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).

[0083] Although the FIG. 5 shows various hardware components of the network apparatus 400 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the network apparatus 400 may include lessor or greater 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 disclosure. One or more components can be combined together to perform same or substantially similar function in the network apparatus 400.

[0084] FIG. 6 is a flow chart illustrating a method, implemented by a network apparatus, for handling SR procedure in a wireless network, according to an embodiment of the disclosure.

[0085] Referring to FIG. 6, in a method S600, operations S602-S610 are handled by the SR procedure controller 240.

[0086] At operation S602, the method includes initiating the UE UCU procedure. At operation S604, the method includes receiving the SR message from the MUSIM UE 100 before completion of the UCU procedure. At operation S606, the method includes determining whether the SR message comprises the UE request type IE set to “NAS signaling connection release”. In response to determining that the SR message comprises the UE request type IE set to “NAS signaling connection release” then, a S608, the method includes aborting the UCU procedure and processes the SR procedure.

[0087] Determine whether the SR message comprises a UE request type IE set to “NAS signaling connection release” In response to determining that the SR message does not comprise the UE request type IE set to “NAS signaling connection release”, At operation S610, the method includes Process both the UCU procedure and the SR procedure.

[0088] FIG. 7 is a flow chart illustrating a method, implemented by a MUSIM UE, for handling an SR procedure in a wireless network, according to an embodiment of the disclosure.

[0089] Referring to FIG. 7, in a method S700, operations S702-S710 are handled by the SR procedure controller 140.

[0090] At operation S702, the method includes initiating the SR procedure. At operation S704, the method includes transmitting the SR message by including or not including UE request type IE set to “NAS signaling connection release” to the network apparatus 400. At operation S706, the method includes receiving the UCU message from the network apparatus 400 before completion of the SR procedure.

[0091] At operation S708, the method includes aborting the UE configuration update procedure by ignoring the UCU message received from the network apparatus 400 and progressing the SR procedure, when the SR message includes the UE request type IE set to “NAS signaling connection release”. At operation S710, the method includes processing both the UCU procedure and the SR procedure in response when the SR message does not comprise the UE request type IE set to “NAS signaling connection release.

[0092] FIG. 8 is an example scenario in which a service request and de-registration procedure collision is depicted, according to an embodiment of the disclosure.

[0093] Referring to FIG. 8, unlike to the methods and systems of the related art, the following operations: operation S801, i) The MUSIM capable UE's first UE (belonging to first SIM) is in Connected Mode, ii) MUSIM UE 100 wants to initiate operation on second SIM, iii) the First UE transmits SR with release flag. Requesting network to release the connection and move the UE to either IDLE mode or INACTIVE state.

[0094] At operation S802, the AMF entity 300 decides to send the network initiated deregister message to the MUSIM UE 100. At operation S803, the MUSIM UE 100 transmits the service request message (with release flag) to the g-NodeB 200. At operation S804, the network apparatus initiated the deregistration procedure. At operation S805, the collision between the network initiated deregister and the service request message occurs. At operation S806, the deregistration procedure is aborted at the MUSIM UE 100 and the service request procedure is progressed at the MUSIM UE 100. At operation S807, the deregistration procedure is aborted at the AMF entity 300 and the service request procedure is progressed at the AMF entity 300.

[0095] The UE and network apparatus 400 shall abort the network initiated deregistration procedure and proceed with service request procedure, so that UE can get the release and move to either an IDLE state or an INACTIVE state and it can start the required operation/service on the second SIM as quickly as possible.

[0096] In yet another embodiment, the UE and the network apparatus 400 shall abort the network initiated deregistration procedure and progress with SR procedure with release flag if the network apparatus 400 initiated deregistration procedure does not indicate the same access type on which service request was transmitted. For example, if the service request is transmitted on 3GPP access and network initiated deregistration procedure only indicates non-3GPP access type then network initiated deregistration procedure should be aborted and service request procedure should be progressed.

[0097] In yet another embodiment, the UE and the network apparatus 400 shall progress the network initiated deregistration procedure and abort the service request with release flag if the network apparatus 400 initiated deregistration procedure does not indicate the same access type on which service request was transmitted. For example, if the service request message is transmitted on 3GPP access and network initiated deregistration procedure only indicates non-3GPP access type then network initiated deregistration procedure should be aborted and service request procedure should be progressed.

[0098] In yet another embodiment, the UE and the network apparatus 400 shall progress the network initiated deregistration procedure and also progress with service request procedure optionally if the access type in the deregistration message and access over which the service request message is transmitted is the same, so that the UE can get the release and move to either IDLE state or INACTIVE state and it may start the required operation/service on the second SIM.

[0099] FIG. 9 is an example scenario in which a service request and a network initiated NAS procedure is depicted, according to of the disclosure embodiment of the disclosure.

[0100] Unlike to the methods and systems of the related art, referring to the FIG. 9, consider a proposed method, provides collision of service request and NAS procedures like identification procedure/DL NAS TRANSPORT procedure/Generic UE configuration update procedure/Network slice-specific authentication and authorization procedure. Followings are the operations: operation S901, MUSIM capable UE's first UE (belonging to first SIM) is in Connected Mode, ii) MUSIM UE wants to initiate operation on second SIM, iii) First UE transmits SR with release flag. At operation S902, requesting network to release the connection and now if the UE receives identify request message or DL NAS transport message or CONFIGURATION UPDATE COMMAND message or NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message for processing.

[0101] At operation S903, the MUSIM UE 100 transmits the service Request message (With Release Flag) to the AMF. At operation S904, the AMF entity 300 transmits the identity request message, the DL NAS TRANSPORT message, the UE configuration update or the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND towards the UE. At operation S905, the collision between the network initiated procedure and the service request message is detected by the UE and the AMF. At operation S906, the network-initiated NAS transport procedure or identity request procedure or UE configuration update or NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND procedure is aborted by ignoring the respective network initiated NAS procedure. The service request procedure is progressed. At operation S907, the network-initiated NAS transport procedure or identify request procedure or UE configuration update or NETWORK SLICE-SPECIFIC AUTHENTICATION procedure is aborted by forgetting that network ever transmitted those respective network initiated or network transmitted NAS messages. The service request procedure is progressed.

[0102] At both the UE and the network apparatus 400, the network apparatus 400 initiated the NAS transport procedure, identity request procedure, the CONFIGURATION UPDATE COMMAND or Network slice-specific authentication and authorization procedure is aborted. Service request procedure is progressed.

[0103] In yet another embodiment, if the downlink NAS message (for example DL NAS TRANSPORT message due to network-initiated NAS transport procedure or CONFIGURATION UPDATE COMMAND message due to Generic UE configuration update procedure) does not require UE to transmit the response message (for example in this case UL NAS TRANSPORT message or CONFIGURATION UPDATE COMPLETE or the registration request message) due to no acknowledgement is requested in the DL NAS TRANSPORT message or CONFIGURATION UPDATE COMMAND message or registration requested bit is not set. Then the UE and the network shall continue with both the procedures.

[0104] For example, when the SOR TRANSPARENT CONTAINER or the UE parameters update transparent container is received with ACK bit set (i.e. acknowledgement is requested) then only Service request procedure is progressed and network-initiated NAS transport procedure is aborted. Otherwise, when ACK bit is not set (i.e., no acknowledgement is requested) then both the procedures are progressed.

[0105] In yet another embodiment, at both the UE and the network, network-initiated NAS transport procedure or Identify request procedure or Network slice-specific authentication and authorization procedure shall be progressed and the Service request procedure is also progressed. So that required configuration in the MUSIM UE 100 can be received before UE can be released to IDLE or INACTIVE state (i.e., 5GMM-CONNECTED mode with RRC inactive indication). In yet another embodiment, this step can be done irrespective of whether the MUSIM UE 100 has set the Release request flag in the service request message.

[0106] At both, the MUSIM UE 100 and the network apparatus 400: The network apparatus 400 initiated downlink NAS TRANSPORT message can be aborted (also called as ignored in this embodiment) and Service request procedure with release flag can be progressed if:

[0107] Network-initiated NAS transport procedure is to provide a transport for one or more of the:

[0108] a single 5GSM message;

[0109] SMS;

[0110] an LPP message;

[0111] an SOR transparent container;

[0112] a single uplink 5GSM message which was not forwarded due to routing failure;

[0113] a single uplink 5GSM message which was not forwarded due to congestion control;

[0114] a UE policy container;

[0115] a single uplink 5GSM message which was not forwarded, because the PLMN's maximum number of PDU sessions has been reached;

[0116] a single uplink 5GSM message which was not forwarded, because the maximum number of PDU sessions with active user-plane resources has been reached;

[0117] a single uplink 5GSM message which was not forwarded, because of ongoing network slice-specific authentication and authorization procedure for the S-NSSAI that is requested;

[0118] a single uplink 5GSM message which was not forwarded due to service area restrictions;

[0119] UE parameters update transparent container;

[0120] a location services message;

[0121] a CIoT user data container;

[0122] a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure;

[0123] a single uplink CIoT user data container which was not forwarded due to congestion control; or

[0124] multiple of the above types.

[0125] At both, UE and Network: The generic UE configuration update procedure can be aborted and Service request procedure with release flag can be progressed if, following parameters are transmitted by the generic UE configuration update procedure optionally without the need to request the UE to perform the registration procedure for mobility and periodic registration update:

[0126] a) 5G-GUTI;

[0127] b) TAI list;

[0128] c) Service area list;

[0129] d) Network identity and time zone information (Full name for network, short name for network, local time zone, universal time and local time zone, network daylight saving time);

[0130] e) LADN information;

[0131] f) Rejected NSSAI;

[0132] g) void;

[0133] h) Operator-defined access category definitions;

[0134] i) SMS indication;

[0135] j) Service gap time value;

[0136] k) “CAG information list”;

[0137] 1) UE radio capability ID;

[0138] m) 5GS registration result; and

[0139] n) Truncated 5G-S-TMSI configuration.

[0140] Optionally, the following parameters can be transmitted to the UE with or without a request to perform the registration procedure for mobility and periodic registration update:

[0141] a) Allowed NSSAI;

[0142] b) Configured NSSAI; or

[0143] c) Network slicing subscription change indication.

[0144] Optionally, the following parameters are transmitted to the UE with a request to perform the registration procedure for mobility and periodic registration update:

[0145] a) MICO indication;

[0146] b) UE radio capability ID deletion indication; and

[0147] c) Additional configuration indication.

[0148] The abort in this disclosure means that respective message (either incoming message or outgoing message) on the UE side and the network side is ignored. For example, CUC procedure is aborted means UE ignores/also called as aborted the received CUC message and network ignores/aborts the transmitted (outgoing) CUC message.

[0149] FIG. 10 is an example scenario in which a paging procedure and service request procedure collision, according to an embodiment of the disclosure.

[0150] Referring to the FIG. 10 consider methods and systems, the paging procedure and service request procedure collision are as follows: operation S1001, i) MUSIM capable UE's first UE (of first SIM) is in Connected Mode, ii) MUSIM UE wants to initiate operation on second SIM, iii) First UE transmits SR with release flag. Requesting network to release the connection, OR iv) The UE transmits Release request (also called as Paging reject) indication in response to Paging message to indicate busy to the network.

[0151] At operation S1002, the AMF entity 300 decides to transmit with access type set to 3GPP access (Paging message over 3GPPA or Notification message over N3GPPA). At operation S1003, the MUSIM UE 100 transmits the service Request message (With Release Flag) to the g-NodeB 200. At operation S1004, the AMF entity 300 transmits the paging message over 3GPPA or Notification message over non-3GPP access to the g-NodeB 200. At operation S1005, the g-NodeB 200 detects the collision between network initiated procedure and service request message. At operation S1006, the MUSIM UE 100 ignores the i) paging message received over 3GPPA with access type set to 3GPP access or ii) notification message received over N3GPPA with access type set to 3GPP access.

[0152] At the same time while the service request procedure is ongoing, the MUSIM UE 100 receives the Paging message over 3GPP access or Notification message over non-3GPP access (with access type set to non-3GPP access).

[0153] As per the methods of the related art, received paging message or notification message over non-3GPP access is ignored by the MUSIM UE 100. But, if the received Paging message or Notification message is for some other Paging cause (or incoming service) like for example earlier transmitted Service request (SR) was Paging cause non-voice which is indicated to the UE with empty paging cause or with paging cause others. Now this is second Paging message with different Paging cause for example voice. Then if the UE ignores the received Paging message, then the UE will lose the incoming service.

[0154] Unlike to the methods and systems of the related art, when paging message over 3GPP access or notification message over non-3GPP access is received:

[0155] The UE shall check the reason why service request is ongoing.

[0156] If the UE transmitted the first Service request (or any other NAS message) in response to first Paging message or first Notification message and now the second Paging message or second notification message is received by the UE and this second Paging/Notification message contains a different paging cause or access type (in general contents are different in Paging/Notification message) or indicates different incoming (downlink) service is pending for the UE—or—if the conditions in the MUSIM UE has changed then MUSIM UE may re-initiate the service request (or any other NAS) procedure again after the completion of the current ongoing service request (or any other NAS procedure) or the specific procedure to receive the incoming service (or downlink data or signaling) from the network due to second Paging message or second notification message.

[0157] If the UE transmitted the Service request (with release request flag) and now the Paging message or notification message is received by the UE and this Paging/Notification message contains a paging cause or indicates incoming (downlink) service is pending for the UE—or—if the conditions in the MUSIM UE has changed, then MUSIM UE may re-initiate the service request procedure again after the completion of the current ongoing service request or the specific procedure to receive the incoming service (or downlink data or signaling) from the network due to Paging message or Notification message (over non-3GPP access). In other words, the UE will not ignore the received Paging message over 3GPP access or Notification message received over non-3GPP access and the UE will respond back with appropriate NAS message. The paging message here is transmitted over 3GPP access and Notification message is transmitted over non-3GPP access to indicate to the UE that data or signaling is pending to be received for the UE over 3GPP access.

[0158] In some embodiment of the disclosure, when UE is executing leaving procedure by triggering SR with NAS signalling connection release procedure if there is a collision with UCU procedure then it's not clear if network will release the NAS signalling connection or wait for UE to send the response message like CUC response or registration procedure based on indication in the CUC message. Given that UE has decided to leave the current network it is proposed that leaving procedure takes precedence so that there is no delay in execution of leaving procedure and as a consequence less delay in initiating the services on alternate SIM.

[0159] If UE triggers SR with NAS signalling connection release and if there is a collision with UCU procedure. UCU procedure is aborted and SR procedure is progressed.

[0160] Leaving procedure from the UE may be delayed. If CUC indicates to perform registration then UE will end up executing the registration procedure due to which there will be delay in starting service on another SIM.

[0161] In abnormal cases in the UE, The following abnormal cases can be identified:

[0162] a) Transmission failure of the CONFIGURATION UPDATE COMPLETE message with TAI change from lower layers

[0163] If the current TAI is not in the TAI list, the generic UE configuration update procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated.

[0164] If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the generic UE configuration update procedure.

[0165] b) Transmission failure of CONFIGURATION UPDATE COMPLETE message indication without TAI change from lower layers

[0166] It is up to the UE implementation how to re-run the ongoing procedure that triggered the generic UE configuration update procedure.

[0167] c) Generic UE configuration update and de-registration procedure collision

[0168] If the UE receives CONFIGURATION UPDATE COMMAND message after sending a DEREGISTRATION REQUEST message and the access type included in the DEREGISTRATION REQUEST message is same as the access in which the CONFIGURATION UPDATE COMMAND message is received, then the UE shall ignore the CONFIGURATION UPDATE COMMAND message and proceed with the de-registration procedure. Otherwise, the UE shall proceed with both the procedures.

[0169] d) Void

[0170] e) Generic UE configuration update and service request procedure collision

[0171] If the SERVICE REQUEST message does not include UE request type IE with Request type value set to “NAS signalling connection release” and the UE receives a CONFIGURATION UPDATE COMMAND message before the ongoing service request procedure has been completed, the UE shall proceed with both the procedures.

[0172] If the SERVICE REQUEST message includes UE request type IE with Request type value set to “NAS signalling connection release” and the UE receives a CONFIGURATION UPDATE COMMAND message before the ongoing service request procedure has been completed, the UE shall ignore the CONFIGURATION UPDATE COMMAND message and proceed with the service request procedure.

[0173] f) “CAG information list” is received and the UE is operating in SNPN access operation mode

[0174] If the UE receives the CAG information list IE in the CONFIGURATION UPDATE COMMAND message and the UE is operating in SNPN access operation mode, the UE shall ignore the content of CAG information list IE.

[0175] In abnormal cases on the network side, The following abnormal cases can be identified:

[0176] a) Expiry of timer T3555.

[0177] The network shall, on the first expiry of the timer T3555, retransmit the CONFIGURATION UPDATE COMMAND message and shall reset and start timer T3555. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3555, the procedure shall be aborted. In addition, if the CONFIGURATION UPDATE COMMAND message includes the 5G-GUTI IE, the network shall behave as described in case b)-1) below.

[0178] b) Lower layer failure.

[0179] If a lower layer failure is detected before the CONFIGURATION UPDATE COMPLETE message is received and:

[0180] 1) if the CONFIGURATION UPDATE COMMAND message includes the 5G-GUTI IE, the old and the new 5G-GUTI shall be considered as valid until the old 5G-GUTI can be considered as invalid by the AMF. If a new TAI list was provided in the CONFIGURATION UPDATE COMMAND message, the old and new TAI list shall also be considered as valid until the old TAI list can be considered as invalid by the AMF.

[0181] During this period the AMF:

[0182] i) may first use the old 5G-S-TMSI from the old 5G-GUTI for paging within the area defined by the old TAI list for an implementation dependent number of paging attempts for network originated transactions. If a new TAI list was provided in the CONFIGURATION UPDATE COMMAND message, the new TAI list should also be used for paging. Upon response from the UE, the AMF may re-initiate the CONFIGURATION UPDATE COMMAND. If the response is received from a tracking area within the old and new TAI list, the network shall re-initiate the CONFIGURATION UPDATE COMMAND message. If no response is received to the paging attempts, the network may use the new 5G-S-TMSI from the new 5G-GUTI for paging for an implementation dependent number of paging attempts. In this case, if a new TAI list was provided with new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the new TAI list shall be used instead of the old TAI list. Upon response from the UE the AMF shall consider the new 5G-GUTI as valid and the old 5G-GUTI as invalid.

[0183] ii) shall consider the new 5G-GUTI as valid if it is used by the UE and, additionally, the new TAI list as valid if it was provided with this 5G-GUTI in the CONFIGURATION UPDATE COMMAND message; and

[0184] iii) may use the identification procedure followed by a new generic UE configuration update procedure if the UE uses the old 5G-GUTI; or

[0185] 2) if the CONFIGURATION UPDATE COMMAND message does not include the 5G-GUTI IE and:

[0186] i) the CONFIGURATION UPDATE COMMAND message does not contain the Allowed NSSAI IE, the Rejected NSSAI IE, or the Extended rejected NSSAI IE, the network shall abort the procedure; or

[0187] ii) the CONFIGURATION UPDATE COMMAND message contains the Allowed NSSAI IE, the Rejected NSSAI IE, or the Extended rejected NSSAI IE, the network shall either abort the procedure or retransmit the CONFIGURATION UPDATE COMMAND message on expiry of the timer T3555. The retransmission shall not be repeated more than four times. If the retransmission is repeated for four times, the network shall abort the procedure.

[0188] c) Generic UE configuration update and UE initiated de-registration procedure collision.

[0189] If the network receives a DEREGISTRATION REQUEST message before the ongoing generic UE configuration update procedure has been completed, the network shall abort the generic UE configuration update procedure and shall progress the de-registration procedure.

[0190] d) Generic UE configuration update and registration procedure for mobility and periodic registration update collision

[0191] If the network receives a REGISTRATION REQUEST message before the ongoing generic UE configuration update procedure has been completed, the network shall abort the generic UE configuration update procedure and shall progress the registration procedure for mobility and periodic registration update procedure.

[0192] e) Generic UE configuration update and service request procedure collision

[0193] If the network receives a SERVICE REQUEST message before the ongoing generic UE configuration update procedure has been completed and the SERVICE REQUEST message does not include UE request type IE with Request type value set to “NAS signalling connection release”, both the procedures shall be progressed.

[0194] If the network receives a SERVICE REQUEST message before the ongoing generic UE configuration update procedure has been completed and the SERVICE REQUEST message includes UE request type IE with Request type value set to “NAS signalling connection release”, the network shall abort the generic UE configuration update procedure and shall progress the service request procedure.

[0195] 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.

[0196] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.