Patent Description:
In the <NUM> system, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier(FBMC), non-orthogonal multiple access(NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

Wireless communication technology has grown heaps and bounds in recent times and also penetrated every sector of technology. One of the latest advancements in the domain is non-public networks or stand-alone non-public networks (SNPN) which are intended for sole use of a private entity such as an enterprise. The SNPN is self-contained and the private entity which owns the SNPN is responsible for radio access network (RAN) and core elements, with no interaction with a mobile service provider. <NPL>), relates to network management and routing protocols in communication networks. <NPL>), provides a consideration on Topology Management for IAB. <NPL>), provides a discussion on IAB node discovery and topology/route management.

In the SNPN an unauthorised user equipment (UE) which is not associated with the private entity may not attempt to access the SNPN. Therefore, resources of the SNPN limited to the UEs of the private entity only. However, according to the current 3GPP TS <NUM> and <NUM>, the UE can be configured with a list of subscriber data related to the SNPN. Each subscriber data consists of a subscriber identifier in the form of a subscription permanent identifier (SUPI) containing a network-specific identifier, credentials and an SNPN identity. A user can select a SNPN subscriber data i.e. an SNPN identity.

Consider a scenario, where the UE is registered to a first SNPN of an enterprise and the UE selects a second SNPN of the enterprise due to mobility or user preference. Conventionally, the UE performs a registration update procedure with the second SNPN. The first SNPN and the second SNPN are independent networks and hence, the first SNPN does not share a UE context with the second SNPN resulting in a failure of the registration update procedure with the second SNPN. In the enterprise comprising a plurality of UEs, multiple failures of the registration update procedure results in wastage of resources and needs to be addressed.

Thus, it is desired to address the above-mentioned disadvantages or other shortcomings or at least provide a useful alternative.

Accordingly, the embodiments herein disclose a method performed by a terminal in a mobile communication system. The method includes performing a registration procedure on a first standalone non-public network (SNPN); selecting a second SNPN based on a predetermined condition; and transmitting, to a network entity, a registration request message on the second SNPN for an initial registration, in case that the second SNPN differs from the first SNPN.

Accordingly, the embodiments herein disclose a terminal in a mobile communication system. The terminal includes a transceiver; and a controller configured to: perform a registration procedure on a first standalone non-public network (SNPN), select a second SNPN based on a predetermined condition, and transmit, to a network entity via the transceiver, a registration request message on the second SNPN for an initial registration, in case that the second SNPN differs from the first SNPN.

The principal object of the embodiments herein is to provide a method and user equipment (UE) for handling mobility procedure in standalone non-public networks (SNPN).

Another object of the embodiments herein is to determine a selection of a second SNPN due to mobility of the UE when the UE is registered with a first standalone non-public network (SNPN).

Another object of the embodiments herein is to reset a registration attempt counter on selection of the second SNPN.

Another object of the embodiments herein is to initiate the registration procedure by performing an initial registration to the second SNPN.

This disclosure is 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:.

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 units or modules or the like, are physically implemented by analog 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.

The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.

Accordingly, the embodiments herein disclose a method for handling mobility procedure for user equipment (UE) (<NUM>) in standalone non-public networks (SNPN). The method includes determining, by the UE (<NUM>), a selection of a second SNPN due to mobility of the UE (<NUM>). The UE (<NUM>) is registered with a first standalone non-public networks (SNPN). Further, the method includes resetting, by the UE (<NUM>), a registration attempt counter on selection of the second SNPN; and initiating, by the UE (<NUM>), the registration procedure by performing an initial registration to the second SNPN.

Referring now to the drawings and more particularly to <FIG>, where similar reference characters denote corresponding features consistently throughout the figure, these are shown preferred embodiments.

<FIG> is a block diagram of user equipment (UE) (<NUM>) for for handling mobility procedure for user equipment (UE) (<NUM>) in standalone non-public networks (SNPN) according to the embodiments as disclosed herein.

Referring to the <FIG>, the UE (<NUM>) can be, for example, a mobile phone, a smart phone, Personal Digital Assistant (PDA), a tablet, a wearable device, or the like. In an embodiment, the UE (<NUM>) includes a communicator (<NUM>), a memory (<NUM>), a processor (<NUM>) and a mobility management controller (<NUM>).

In one embodiment, the communicator (<NUM>) is configured to send a registration request message to the second SNPN. The registration request message is sent to the second SNPN in a security command complete message.

The memory (<NUM>) can 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 (<NUM>) 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 (<NUM>) is non-movable. In some examples, the memory (<NUM>) is configured to store larger amounts of information than the memory. 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).

The processor (<NUM>) is configured to execute various instructions stored in the memory (<NUM>).

The mobility management controller (<NUM>) includes a registration management engine (<NUM>), an authentication management engine (<NUM>) and a security mode management engine (<NUM>).

In one embodiment, the registration management engine (<NUM>) is configured to determine a selection of a second SNPN due to mobility of the UE (<NUM>) or the user selection of the second SNPN (e.g., as a result of manual SNPN selection procedure). Further, the registration management engine (<NUM>) is configured to perform a de-registration procedure to the first SNPN and initiate the transmission of a registration request message to the second SNPN and initiate the registration procedure by performing the initial registration to the second SNPN. The registration request message to the second SNPN is sent in a security command complete message. The registration request message is ciphered using a <NUM> NAS security context established due to the execution of the security mode procedure on receiving a security mode command message. The registration request message comprises cleartext IE(s) and a non-cleartext IE(s). The cleartext IEs are information elements that can be sent without confidentiality protection in initial NAS messages. The non-cleartext IEs are information elements that are not cleartext IEs.

When the initial NAS message is a REGISTRATION REQUEST message, then the cleartext IEs are one of: extended protocol discriminator; security header type; spare half octet; registration request message identity; 5GS registration type; ngKSI; 5GS mobile identity; UE security capability; additional GUTI; UE status; and EPS NAS message container.

The UE (<NUM>) is already registered with the first standalone non-public networks (SNPN) and may be configured with multiple subscriptions for a plurality of the standalone non-public networks (SNPN). The SNPN networks are independent networks and may not communicate with each other. The selection of the second SNPN may be necessitated due to user selection or because the UE (<NUM>) may have lost coverage of the first SNPN to which the UE (<NUM>) is registered. The second SNPN is selected by one of: automatic SNPN selection mode procedure and manual SNPN mode selection procedure. Further, the registration management engine (<NUM>) is configured to reset a registration attempt counter on selection of the second SNPN. The registration request message comprises a subscription concealed identifier (SUCI) and cleartext IE (s), wherein the SUCI is determined from subscription permanent identifier (SUPI) of the second SNPN available at the UE (<NUM>).

In one embodiment, the authentication management engine (<NUM>) is configured to determine initiation of an authentication procedure by the second SNPN and determine a completion of the authentication procedure with the second SNPN.

In one embodiment, the security mode management engine (<NUM>) is configured to initiate a security mode command procedure with the second SNPN and determine a completion of the security mode command procedure with the second SNPN.

Although the <FIG> shows the hardware elements of the UE (<NUM>) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (<NUM>) may include less or more number of elements. Further, the labels or names of the elements 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.

<FIG> is a flow chart illustrating a method for handling the mobility procedure for the UE (<NUM>) in the standalone non-public networks (SNPN) according to the embodiments as disclosed herein.

Referring to the <FIG>, at step <NUM>, the UE (<NUM>) determines the selection of the second SNPN due to mobility of the UE (<NUM>) or user selection of a second SNPN using the manual SNPN selection mode procedure. For example, in the UE (<NUM>) as illustrated in the <FIG>, the mobility management controller (<NUM>) can be configured to determine the selection of the second SNPN due to mobility of the UE (<NUM>).

At step <NUM>, the UE (<NUM>) resets the registration attempt counter on selection of the second SNPN. For example, in the UE (<NUM>) as illustrated in the <FIG>, the mobility management controller (<NUM>) can be configured to reset the registration attempt counter on selection of the second SNPN.

At step <NUM>, the UE (<NUM>) initiates the registration procedure by performing the initial registration to the second SNPN. For example, in the UE (<NUM>) as illustrated in the <FIG>, the mobility management controller (<NUM>) can be configured to initiate the registration procedure by performing the initial registration to the second SNPN.

The various actions, acts, blocks, steps, or the like in the method 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 disclosure.

<FIG> illustrates a scenario of handling the mobility procedure for the UE (<NUM>) in the standalone non-public networks (SNPN).

Referring to the <FIG>, at step <NUM>, the UE (<NUM>) is registered to the SNPN-<NUM> and the SNPN-<NUM> is selected due to for example the mobility of the UE (<NUM>). At step <NUM>, the UE (<NUM>) initiates a registration procedure for mobility registration to the SNPN-<NUM>. The SNPN-<NUM> may not get UE context from the SNPN-<NUM> as the SNPN-<NUM> and the SNPN-<NUM> are independent networks (as shown in the <FIG>). Therefore, at step <NUM>, the mobility registration procedure fails as an AMF of the SNPN-<NUM> may not fetch the context from the AMF of the SNPN-<NUM>. The mobility regisration procedure to the SNPN-<NUM> may always fail which may create unnecessary signaling in the SNPN-<NUM> and also delay in attaching to the network and therefore delay in providing services to user.

According to 3GPP TS <NUM> and <NUM>, a universal subscriber identity module (USIM) can have two subscription permanent identifier (SUPI) one with SUPI type international mobile subscriber identity (IMSI) and other with SUPI type network specific identifier (NSI) in a USIM profile. The UE (<NUM>) can register to a network by using one type of the SUPI. The UE (<NUM>) knows that the USIM has two SUPIs however the AMF does not know that the USIM has two SUPIs. The problem also arises due to lack of clarity as to how the AMF retrieves the second SUPI.

According to 3GPP TS <NUM> the UE (<NUM>) supports the SNPN network and the SNPN related configuration (an SNPN identity, user identity (SUPI), credentials and UAC parameters) which is stored in the ME. The UE (<NUM>) have the USIM and the operator configures the ME or the USIM to calculate the subscription concealed identifier (SUCI) from the SUPI of the SNPN configuration in the USIM. However, the method of calculation of the SUPI which needs to be followed by the UE (<NUM>) is not described.

According to the 3GPP TS <NUM>, the UE (<NUM>) stores the parameters (network slice selection assistance information (NSSAI) inclusion mode(s); MPS indicator; MCS indicator; operator-defined access category definitions; and network-assigned UE radio capability IDs. ) in the non-volatile memory. These parameters may be re-used during the subsequent NAS procedure or when the UE (<NUM>) is switched off and switched on and the USIM contains the same SUPI. However, it is not clear whether these parameters are used or not when a NAS procedure is rejected for cause values (#<NUM> (illegal UE (<NUM>)); #<NUM> (illegal ME), #<NUM> (5GS services not allowed). #<NUM> (PLMN not allowed). Tracking area not allowed <NUM> (roaming not allowed in this tracking area), #<NUM> (serving network not authorized), #<NUM> (temporarily not authorized for this SNPN), #<NUM> (permanently not authorized for this SNPN).

<FIG> illustrates a scenario of handling the mobility procedure for the UE (<NUM>) in the standalone non-public networks (SNPN) according to the embodiments as disclosed herein.

Referring to the <FIG>, in conjunction with the <FIG>, the UE (<NUM>) is registered to the SNPN-<NUM> and the SNPN-<NUM> is selected due to for example the mobility of the UE (<NUM>). At step <NUM>, the UE (<NUM>) initiates the initial registration procedure to the SNPN-<NUM> instead of the registration update procedure to the SNPN-<NUM>. Therefore, at step <NUM>, the mobility registration of the UE (<NUM>) with the SNPN-<NUM> is successful.

The detailed steps are described with respect to mobile equipment (ME) below. The UE (<NUM>) has a universal subscriber identity module (USIM) and the operator configures the ME or the USIM.

In one embodiment, the UE (<NUM>) may start a timer in step <NUM> and after the timer expires the UE (<NUM>) deletes the 5GMM context.

In another embodiment, the problem associated with the AMF not knowing that the USIM has two SUPIs and also due to lack of clarity as to how the AMF retrieves the second SUPI is addressed as follows.

UDM receives the first message via AUSF then the UDM sends the message containing the second SUPI via the AUSF. In one example, if the first message contains a second SUPI type then the UDM sends a second SUPI corresponding to the second SUPI type and associated with the first SUPI. In one example, the UDM sends all the SUPIs other than the first SUPI.

In another embodiment, the issue of the method of calculation of the SUPI which needs to be followed by the UE (<NUM>) is described below:.

Parameter P2 specifies the identity context as follows: The one value of the parameter P2 identifies that the data field contains SUPI which needs to be converted to SUCI. Table <NUM> illustrates coding of the reference control P2.

All other coding are RFU. Table <NUM> illustrates command parameters/data.

Table <NUM> illustrates response parameters/data.

<NUM> illustrates subscription concealed identifier TLV data object. The length is coded according to ISO/IEC <NUM>-<NUM>.

Upon receiving the command, the USIM computes the SUPI to a SUCI and sends the SUCI to the ME.

The ME sends the SUCI to the network in a NAS procedure (e.g., registration request message to register to the network when the UE does not have a valid temporary identifier).

In another embodiment, the issue of the AMF not knowing whether the USIM has two SUPIs and how to retrieve the second SUPI, in case the AMF is aware about the two SUPIs of the USIM is addressed as below:.

In another embodiment, the issues related to whether parameters are to be re-used or not when the NAS procedure is rejected for cause values #<NUM>, #<NUM>, #<NUM>, #<NUM>, #<NUM>, #<NUM>, #<NUM>, #<NUM> is described as below:.

The UE (<NUM>) registered to a PLMN and has received at least one of the following parameters from the PLMN. p arameter(s) :.

During a subsequent NAS procedure (e.g., registration procedure or service request procedure or de-registration procedure), the UE (<NUM>) receives one of the following a 5GMM cause value in a NAS message (e.g., registration reject, service reject or deregistration message) from the network:.

Upon receiving the NAS message with one of the cause values in step <NUM>, the UE (<NUM>) may not use the parameter(s) value in subsequent NAS or AS procedure. In one example, if the parameter is NSSAI inclusion mode then the UE (<NUM>) may not use the received NSSAI inclusion mode and may not send S-NSSAI(s) during the subsequent RRC establishment procedure (e.g., RRCconnectionsetupcomplete or RRCsetupcomplete). In one example, if the parameter is MPS indicator or MCS indicator then the UE (<NUM>) may not use access identity <NUM> or <NUM> respectively in subsequent AS or NAS procedure until MPS indicator or MCS indicator is sent in the subsequent NAS procedure. In one example, if the parameter is network-assigned UE radio capability IDs, the UE (<NUM>) may not send the previously network-assigned UE radio capability ID for the radio capabilities supported by the UE (<NUM>). The AMF fetches the set of radio capabilities supported by the UE (<NUM>) during the NAS or the AS procedure (e.g., registration procedure) and assigns, a network assigned UE radio capability ID for the received radio capabilities. The UE (<NUM>) subsequently used corresponding the network assigned UE radio capability ID in the NAS or the AS procedure. The UE (<NUM>) may delete the parameter(s) from the non-volatile memory.

<FIG> illustrates a block diagram of a network entity according to embodiments of the present disclosure.

Referring to the <FIG>, the network entity (<NUM>) may include a processor (<NUM>), a transceiver (<NUM>) and a memory (<NUM>). However, all of the illustrated components are not essential. The network entity (<NUM>) may be implemented by more or less components than those illustrated in <FIG>. In addition, the processor (<NUM>) and the transceiver (<NUM>) and the memory (<NUM>) may be implemented as a single chip according to another embodiment.

<FIG> illustrates a terminal according to embodiments of the present disclosure.

Referring to the <FIG>, the terminal (<NUM>) may include a processor or a controller (<NUM>), a transceiver (<NUM>) and a memory (<NUM>). However, all of the illustrated components are not essential. The terminal (<NUM>) may be implemented by more or less components than those illustrated in <FIG>. In addition, the processor (<NUM>) and the transceiver (<NUM>) and the memory (<NUM>) may be implemented as a single chip according to another embodiment.

In the present disclosure, the terminal may be a user equipment (UE), a mobile station (MS), or a mobile equipment (ME) in a communication system.

In one embodiment, the processor (<NUM>) may perform a registration procedure on a first standalone non-public network (SNPN), select a second SNPN based on a predetermined condition, and transmit, to a network entity via the transceiver, a registration request message on the second SNPN for an initial registration, in case that the second SNPN differs from the first SNPN.

In one embodiment, a registration attempt counter is reset, in case that the second SNPN differs from the first SNPN.

In one embodiment, the network entity is an access and mobility management function (AMF).

In one embodiment, the registration request message on the second SNPN for the initial registration includes information on a type of the registration, and the information on the type of the registration indicates an initial registration, in case that the second SNPN differs from the first SNPN.

In one embodiment, the predetermined condition includes a case that the terminal has lost a coverage of the first SNPN and the terminal recovers from a lack of coverage.

In one embodiment, the second SNPN is selected based on an automatic SNPN selection mode procedure.

In one embodiment, the second SNPN is selected based on a manual SNPN selection mode procedure.

In one embodiment, the terminal is configured with a list of subscriber data, and the list of subscriber data includes an SNPN identity.

In one embodiment, the second SNPN is selected based on the list of subscriber data.

In one embodiment, the processor (<NUM>) may perform a de-registration procedure on the first SNPN, in case that the second SNPN differs from the first SNPN.

The following definitions applies to the all the above embodiments. In the aforementioned embodiments, NSI is network specific identifier.

Definitions: For the purposes of the present document, the terms and definitions given in TR <NUM> and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR <NUM>.

5GLAN Group: A set of UEs using private communication for <NUM> LAN-type service.

<NUM> Access Network: An access network comprising a NG-RAN and/or non-3GPP AN connecting to a <NUM> core network.

<NUM> Core Network: The core network specified in the present document. The core network connects to a <NUM> access network.

<NUM> LAN-Type Service: A service over the <NUM> system offering private communication using IP and/or non-IP type communications.

<NUM> LAN-Virtual Network: A virtual network over the <NUM> system capable of supporting <NUM> LAN-type service.

<NUM> System: 3GPP system consisting of <NUM> access network (AN), <NUM> core network and UE.

Allowed NSSAI: NSSAI provided by the serving PLMN during e.g., a registration procedure, indicating the S-NSSAIs values the UE could use in the serving PLMN for the current registration Area.

Configured NSSAI: NSSAI provisioned in the UE applicable to one or more PLMNs.

SNPN enabled UE: A UE configured to use stand-alone non-public networks.

SNPN access mode: A UE operating in SNPN access mode only selects stand-alone non-public networks over Uu.

Stand-alone Non-Public Network: A non-public network not relying on network functions provided by a PLMN.

Subscribed S-NSSAI: S-NSSAI based on subscriber information, which a UE is subscribed to use in a PLMN.

CAG only UE: a UE which is indicate by the network to access the 5GS by a CAG cell.

CAG Cell: The CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell.

Non-CAG cell: cell of a public PLMN. Normal cell where the UE can access public PLMN service.

Allowed CAG list: An Allowed CAG list of a UE is a list of CAG Identifiers the UE is allowed to access.

Abbreviations: For the purposes of the present document, the abbreviations given in TR <NUM> and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR <NUM>.

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 include blocks, elements, actions, acts, steps, or the like which can be at least one of a hardware device, or a combination of hardware device and software module. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification as long as they do not depart from the scope of the invention as it is depicted by the appended claims.

Claim 1:
A method for registering on a standalone non-public network, SNPN, performed by a terminal (<NUM>) in a mobile communication system, the method comprising:
performing a registration procedure on a first SNPN;
selecting a second SNPN based on a list of subscriber data including an SNPN identity of the second SNPN; and
in response to determining that the second SNPN differs from the first SNPN, resetting a registration attempt counter and transmitting, to an access and mobility management function, AMF, entity, a registration request message for an initial registration on the second SNPN,
wherein the registration request message for the initial registration on the second SNPN includes information on a registration type, and
wherein the information on the registration type indicates the initial registration, in case that the second SNPN differs from the first SNPN.