Apparatus, method and computer program relating to multiple registration

Abstract

An apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving a registration request from a user device to register with a network; and sending a registration response to the request to the user equipment, the registration response having an indication to indicate whether more than one registration of the user equipment is simultaneously supported for the same access type.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to communication systems, and in particular, but not exclusively, to apparatuses, methods and computer programs related to multiple registration. BACKGROUND

[0002] A communication system can be seen as a facility that enables communication between two or more communication devices or provides access to a communication system for a communication device. A mobile or wireless network is an example of a communication system.

[0003] Such communication systems operate in accordance with standards, such as those provided by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of a standard is the so-called 5G (Fifth Generation) standard provided by 3GPP. SUMMARY

[0004] Some embodiments of the disclosure will be described in relation to certain aspects. These aspects are not intended to indicate key or essential features of embodiments of the disclosure or to limit the scope thereof, nor are they intended to exclude any embodiment that does not meet one or more of such aspects. Other features, aspects and elements would be apparent and suggested to those skilled in the art from consideration of the disclosure.

[0005] According to an aspect, there is provided an apparatus comprising: means for receiving, from a user equipment, a registration request for registering with a network; and means for sending, to the user equipment, a registration response to the request, the registration response having an indication, the indication being to indicate whether more than one registration of the user equipment for a same access type is supported simultaneously by the network.

[0006] The indication can be to indicate that the network does not support more than one registration of the user equipment for the same access type simultaneously.

[0007] The indication can be to indicate that the network does support more than one registration of the user equipment for the same access type simultaneously.

[0008] The registration request can comprise information indicating that the user equipment supports more than one registration for the same access type simultaneously.

[0009] The apparatus can comprise means for determining whether the user equipment supports more than one registration for the same access type simultaneously, and the sending means can be to send the registration response to the user equipment when the user equipment supports more than one registration for the same access type simultaneously.

[0010] The apparatus can comprise means for determining whether the registration request is a first active request from the user equipment for registering with the network for a first access type.

[0011] When a registration request is determined to be a first activity request for registering with the network for a first access type, the registration response may include a registration acceptance response.

[0012] If the registration request is determined not to be a first activity request for registration with the network for the first access type, and the network does not simultaneously support more than one registration for a user device for the same access type, the registration response may include a registration rejection response.

[0013] The registration request may include a registration request for 3GPP access or a registration request for non-3GPP access.

[0014] The network may include either a public land mobile network or an independent non-public network.

[0015] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least perform: receiving a registration request from a user equipment for registering with a network; and sending a registration response to the request to the user equipment, the registration response having an indication for indicating whether more than one registration of a user equipment for the same access type is simultaneously supported.

[0016] According to one aspect, a method is provided, the method comprising: receiving from a user equipment a registration request for registering with a network; and sending to the user equipment a registration response to the request, the registration response having an indication for indicating whether more than one registration of a user equipment for the same access type is supported simultaneously.

[0017] This instruction can be used to indicate that the network does not simultaneously support more than one registration for user devices of the same access type.

[0018] This instruction can be used to indicate that the network actually supports more than one registration for user equipment of the same access type at the same time.

[0019] The registration request may include information indicating that the user equipment supports more than one registration for the same access type simultaneously.

[0020] The method may include: determining whether the user equipment simultaneously supports more than one registration for the same access type, and when the user equipment simultaneously supports more than one registration for the same access type, the sending component may be used to send a registration response to the user equipment.

[0021] The method may include: determining whether the registration request is a first activity request from a user equipment for a first access type, for registering with the network.

[0022] When a registration request is determined to be a first activity request for registering with the network for a first access type, the registration response may include a registration acceptance response.

[0023] If the registration request is determined not to be a first activity request for registration with the network for the first access type, and the network does not simultaneously support more than one registration for a user device for the same access type, the registration response may include a registration rejection response.

[0024] The registration request may include a registration request for 3GPP access or a registration request for non-3GPP access.

[0025] The network may include either a public land mobile network or an independent non-public network.

[0026] According to another aspect, a user equipment is provided, the user equipment comprising: components for sending a first registration request for registering with a network; and components for receiving a registration response to the request, the registration response having an indication for indicating whether more than one registration for a user equipment of the same access type is supported simultaneously.

[0027] This instruction can be used to indicate that the network does not simultaneously support more than one registration for user devices of the same access type.

[0028] This instruction can be used to indicate that the network actually supports more than one registration for user equipment of the same access type at the same time.

[0029] The first registration request may include information indicating that the user equipment supports more than one registration for the same access type simultaneously.

[0030] When the registration request is a first activity request for registering with the network for a first access type, the first registration response may include a registration acceptance response.

[0031] When the first registration request is not a first activity request for registering with the network for the first access type, and the network does not simultaneously support more than one registration for user equipment of the same access type, the registration response may include a registration rejection response.

[0032] The first registration request may include a registration request for 3GPP access or a registration request for non-3GPP access.

[0033] User equipment may include components for determining whether a second registration request for registering with the network for the same access type as the first registration request should be sent, the determination being based on an indication received in a registration response.

[0034] The user equipment may include components for selecting a network to which a second registration request of the same access type as the first registration request is to be sent, the selection being based on one or more of an instruction or a local network selection policy.

[0035] According to another aspect, a user equipment is provided, the user equipment comprising: at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the user equipment to at least perform: sending a first registration request for registration with a network; and receiving a registration response to the request, the registration response having an indication for indicating whether more than one registration of the user equipment for the same access type is supported simultaneously.

[0036] According to another aspect, a method is provided, the method comprising: sending a first registration request for registering with a network; and receiving a registration response to the request, the registration response having an indication for indicating whether more than one registration for user equipment of the same access type is supported simultaneously.

[0037] This instruction can be used to indicate that the network does not simultaneously support more than one registration for user devices of the same access type.

[0038] This instruction can be used to indicate that the network actually supports more than one registration for user equipment of the same access type at the same time.

[0039] The first registration request may include information indicating that the user equipment supports more than one registration for the same access type simultaneously.

[0040] When the registration request is a first activity request for registering with the network for a first access type, the first registration response may include a registration acceptance response.

[0041] When the first registration request is not a first activity request for registering with the network for the first access type, and the network does not simultaneously support more than one registration for user equipment of the same access type, the registration response may include a registration rejection response.

[0042] The first registration request may include a registration request for 3GPP access or a registration request for non-3GPP access.

[0043] The method may include: determining whether a second registration request for registering with the network for the same access type as the first registration request should be sent, the determination being based on an indication received in a registration response.

[0044] The method may include: selecting a network to which a second registration request of the same access type as the first registration request should be sent, the selection being based on one or more of an instruction or a local network selection policy.

[0045] This method can be executed by a device. The device can be a user equipment.

[0046] According to another aspect, a computer program including instructions is provided that, when executed by a device, causes the device to perform any of the methods previously described.

[0047] According to another aspect, a computer program including instructions is provided that, when executed, cause any of the methods previously described to be performed.

[0048] According to one aspect, a computer program including computer-executable code is provided, which, when run, causes any of the methods previously described to be performed.

[0049] According to one aspect, a computer-readable medium is provided, the computer-readable medium including program instructions stored thereon for performing at least one of the methods described above.

[0050] According to one aspect, a non-transitory computer-readable medium is provided that includes program instructions that, when executed by a device, cause the device to perform any of the methods previously described.

[0051] According to one aspect, a non-transitory computer-readable medium is provided that includes program instructions, which, when executed, cause any of the methods previously described to be performed.

[0052] According to one aspect, a non-volatile tangible storage medium is provided, the non-volatile tangible storage medium including program instructions stored thereon for performing at least one of the methods described above.

[0053] As described above, many different aspects have been described. It should be understood that additional aspects can be provided through any combination of two or more of the above aspects.

[0054] Various other aspects are also described in the following detailed description and claims. Attached Figure Description

[0055] Some embodiments will now be described by way of non-limiting and illustrative examples only, with reference to the accompanying drawings, in which: Figure 1 An overview of a system in which some embodiments may be provided is shown; Figure 2 A first method of some embodiments is shown; Figure 3An overview of a 5G system in which some embodiments may be provided is shown; Figure 4 A second method is shown, representing some embodiments provided in a 5G system; Figure 5a and Figure 5b An example registration process is shown; Figure 6 The device is shown; Figure 7 The user equipment (UE) is shown. Figure 8 A third method is shown in some embodiments; and Figure 9 A fourth method is shown in some embodiments. Detailed Implementation

[0056] Multiple registration refers to a situation where a UE can register with one or more networks two or more times. In the case of multiple registration, the two or more registrations can be concurrent. In other words, a UE can have two or more active registrations simultaneously (e.g., concurrently or synchronously). In the case of multiple registration, a UE with a public USIM (Universal Subscriber Identity Module) or similar identity can be configured to register with one or more networks more than once. Therefore, a UE can register with one or more networks two or more times simultaneously. The access types of the different registrations can be the same or different.

[0057] Currently, the UE is not notified whether a network that typically supports multiple registrations will allow further parallel registrations for the same access type. Even if the network will not allow the UE to have more than one registration with that network for that access type, the UE can still request further parallel registrations for the same access type. Under the current UE policy of network selection, the UE is configured to continue attempting to register with the same network. This may waste energy and / or radio resources.

[0058] Multiple registrations can be categorized as dual registrations. Some examples of dual registrations with the same access type are as follows: 1. Two registrations from the UE for 3GPP access (NR (New Radio)) in the same PLMN (Public Land Mobile Network) / SNPN (Standalone Non-Public Network).

[0059] 2. Two registrations from the UE for 3GPP access (NR) in different PLMNs.

[0060] 3. Two registrations from the UE for 3GPP access (NR), one registration to the PLMN and a second registration to the SNPN.

[0061] Dual or multiple deployments of the same type of access (e.g., PLMN or SNPN, i.e., Example 1 above) to the same service network may not be supported. However, Examples 2 or 3 above can be supported. In some cases, dual or multiple registrations can be supported only when the two registrations are not on the same network, such as in Examples 2 or 3 above.

[0062] In other embodiments, only dual registration or multiple registration may be supported, where dual registration or multiple registration is used for different access types. In other words, Examples 1 to 3 are not supported by the network, and the network only supports dual registration or multiple registration for different access types.

[0063] Currently, when a UE registers with a network, if the network supports dual or multiple registration, the network will accept the information (registration ID) provided by the UE. In its response to the UE (such as a registration acceptance message), the network will indicate the registration ID to the UE. Based on the indicated registration ID, the UE is configured to infer whether the network supports dual or multiple registration features, and / or store this indication. However, the network may not allow a UE to register twice with the same serving network using the same access type. For example, the network may only support the dual or multiple registration scenarios in Examples 2 and 3 above, but not Example 1. In another example, the network may only support dual or multiple registration, where dual or multiple registration is used for different access types. The UE may not know whether the serving network supports the UE registering twice with the same network using the same access type.

[0064] Some embodiments will now be described further. These embodiments address the problem of how a UE knows that a serving network supports multiple registrations but can only accept a single registration from a given UE. This prevents the UE from attempting a second or further registration with the same access type to the same network while the first registration is still active. The UE can, for example, select a different network for the second or further registration.

[0065] The network can be a PLMN, SNPN, or any other suitable network.

[0066] In some embodiments, a network function is provided to support UE registration with the network. The network function is responsible for determining whether to allow a registration request from the UE. The network function may support multiple registrations, but only in certain situations. In some embodiments, two or more registrations from the same UE of the same access type may not be supported when those registrations are active simultaneously.

[0067] Figure 1An example of a system in which some embodiments may be provided is shown. UE 300 is connected to a network. The UE may connect to network 100 via access network 102 of network 100. The access network may be a radio access network (RAN). In other embodiments, any other suitable access network may be used alternatively or additionally.

[0068] Network 100 may include a registration function 104. Registration function 104 may be a network function of the network. In some embodiments, registration function 104 may be provided in the core network of the network. Registration function 104 may receive a registration request from a UE via access network 102. It should be noted that in some embodiments, one or more additional network functions may be provided between access network 102 and registration function 104. Registration function 104 may provide a response to UE 300.

[0069] In some embodiments, in response to a registration request, the network will send an indication regarding allowing further parallel registration of the UE using the same access type.

[0070] The UE can provide a registration identity (ID) in the registration request. Registration function 104 can maintain a UE context with the registration ID. The registration ID can be provided to data storage device 108. Data storage device 108 can be a network function of the network. In some embodiments, data storage device 108 can be provided in the core network of the network. The data storage device can store the relationship between the registration function and the registration ID.

[0071] The registration ID can be used to distinguish different registrations of the UE. These different registrations are different activity registrations of the UE based on the same access type. For example, the UE can be configured to add "1" to its first registration, "2" to its second registration, and so on, so that the network can distinguish multiple registrations through the same UE / USIM. The data storage device 108 can receive the registration ID from each registration function of the serving network. The existence of the registration ID itself can indicate to the network that the UE is capable of multiple registrations.

[0072] In other embodiments, the information enabling the UE to perform multiple registrations can be provided by the UE in any other suitable manner, or can be retrieved from the user data storage device by the registration function. The user data storage device can be data storage device 108 or any other suitable data storage device.

[0073] Figure 2 Methods of some embodiments are illustrated. In some embodiments, the method may be provided by... Figure 1 The system shown performs the procedure. In other embodiments, the method may be performed by another suitable system.

[0074] As shown by reference numeral S1 in the attached figure, the UE sends a registration request to the registration function 104 of network 100. This registration request can indicate whether the UE can support multiple registrations.

[0075] As indicated by reference numeral S2 in the attached figure, registration function 104 sends an indication regarding allowing further parallel registration using the same access type for the UE.

[0076] This indication can be either that the network supports multiple registrations or not. In other words, it sends an indication to the UE – that multiple registrations to the same network using the same access type are supported, or that multiple registrations to the same network using the same access type are not supported.

[0077] In some embodiments, an indication may be sent only if the UE does not allow further parallel registration with the network using the same access type. In this case, the absence of any indication from the registration function means that the network actually supports the UE further parallel registration with the network using the same access type.

[0078] As indicated by reference numeral S3 in the attached figure, if the indication is received, the UE stores it. The UE stores the indication so that it can later make a decision about when to perform further registration. When selecting a network for further registration, the UE uses local policies and the indication to determine which network will be selected for further registration.

[0079] When an indication is received that further parallel registration is not permitted using the same access type, the UE will not attempt further parallel registration with that network using the same access type. This will be in the event that there is currently active registration with the network for a given access type. The UE may attempt further registration with other networks that support multiple registrations for that given access type.

[0080] When a UE receives an indication that further parallel registration is permitted using the same access type, or when no such indication is received, the UE may attempt to register further in parallel with the network using the same access type. This can be based on local policies and priorities. The UE may have policies for network selection, and the UE may prioritize or de-prioritize network selection rules / policies based on determining whether further parallel registration is permitted.

[0081] In some embodiments, the UE is configured to store information about whether further parallel registration with the network using the same access type is permitted. This information may be stored in a list.

[0082] In some embodiments, the UE is configured to store information only if parallel registration with a given network using the same access type is not permitted. In the absence of any stored information, the UE can be configured to infer that parallel registration with a given network using the same access type is permitted.

[0083] In some embodiments, the network can provide updates to this indication.

[0084] It should be understood that the embodiments can be implemented in any suitable system. By way of example only, some embodiments can be implemented in 5G systems, 6G systems, or higher. Reference will now be made to a diagram illustrating a portion of 5G. Figure 3 And show the method provided by 5GS Figure 4 This describes some implementations in a 5G system (5GS). 5GS may include a PLMN or SNPN.

[0085] First refer to Figure 3 UE 300 connects to 5GS 100'. 5GS may include a (radio) access network (RAN) 102' or more generally a 5G access network, which may correspond, for example, to a (radio) access network (RAN), a wired access gateway (W-AGF), or an N3IWF (non-3GPP interoperability function), etc. Figure 3 In the example shown, the access network is a RAN. A 5G RAN may include one or more base stations or radio access network (RAN) nodes, such as gNodeBs (gNBs). A base station or RAN node may include one or more distributed units connected to a central unit. In other embodiments, the access network may be another access network.

[0086] The 5GS may include a 5G core. Within the 5G core, an Access and Mobility Management Function (AMF) 104' is provided. AMF 104' can receive connection and session-related information from the UE and can handle connection and mobility management tasks. AMF 104' provides registration functionality within the 5GS. AMF 104' can receive registration requests from the UE via RAN 102'. It should be noted that in some embodiments, one or more additional 5G network functions may be provided between RAN 102' and AMF 104'. One or more of these 5G network functions may be provided within the 5G core. AMF 104' can provide responses to the UE 300.

[0087] The response can be as follows: Figure 1 and Figure 2 The embodiments described herein.

[0088] The response can be a registration acceptance response. This can be sent in response to the first registration request from the UE. When the serving PLMN does not support more than one 3GPP access registration from a single UE, during the first 3GPP access registration from the UE, if the UE has indicated that it can perform multiple 3GPP access registrations, the AMF includes information elements / parameters in the response message that indicate to the UE that the PLMN does not simultaneously (e.g., concurrently or synchronously) support / allow more than one 3GPP access registration.

[0089] A UE can indicate to the AMF that it is capable of multiple registrations by including an indication (such as a registration ID or any other suitable indication) in the registration request. The registration ID can be as described above.

[0090] AMF 104' can maintain the UE context with a registration ID. The registration ID can be provided to the UDM (Unified Data Management) function 108'. The data storage device can store the relationship between the registration function and the registration ID. UDM 108' can be provided in the 5G core.

[0091] In other embodiments, the information enabling the UE to perform multiple registrations can be provided by the UE in any other suitable manner, or it can be retrieved by the AMF 104' from a user data storage device. This could be the UDM 108' and / or any other suitable data storage device.

[0092] The response could be a registration rejection message.

[0093] If a UE sends a second access registration request for 3GPP access to the same serving PLMN (e.g., due to the user's manual PLMN selection), and the serving PLMN does not simultaneously (e.g., synchronously or concurrently) support more than one 3GPP access registration from a single UE, the AMF sends a rejection message. The rejection message can be a registration rejection message. This message can provide information indicating the reason for the rejection. For example, the message may include an indication that the PLMN does not simultaneously (e.g., synchronously or concurrently) support / allow more than one 3GPP access registration.

[0094] When a UE receives an indication from the network (AMF) that a PLMN supports / allows more than one 3GPP access registration at different times (e.g., synchronous or concurrent), the UE can store the PLMN in a list of disabled PLMNs for more than one 3GPP access registration.

[0095] In the case of automatic selection, if at least one 3GPP access registration has been performed in the PLMN and is active for the UE, then the UE does not consider the PLMN for a second 3GPP access registration.

[0096] In the case of manual selection, if at least one 3GPP access registration has been performed in the PLMN and is active for the UE, then the UE does not have (e.g., avoid presenting) the PLMN for user selection for the second 3GPP access registration (or displays the PLMN as disabled).

[0097] In some embodiments, the AMF will send an indication to the UE. This indication may be that the network supports multiple registrations to the same network using the same / single access type, or does not support multiple registrations to the same network using the same / single access type. In other words, it sends an indication to the UE – to support multiple registrations to the same network using the same / single access type, or not to support multiple registrations to the same network using the same / single access type.

[0098] In some embodiments, the AMF may send an indication only if the UE does not allow further parallel registration with the network. In this case, the absence of any indication from the AMF means that the network does indeed support further parallel registration with the network using the same / single access type. (Reference) Figure 4 ,Should Figure 4 Methods for some embodiments provided in 5G systems for 3GPP access types are illustrated.

[0099] As shown by reference numeral T1 in the attached figure, the UE sends a registration request to the AMF.

[0100] As shown in the attached diagram T2, the AMF checks whether the UE supports more than one 3GPP access registration at the same time.

[0101] If not, then follow the usual registration process as indicated by reference numeral T4 in the attached figure.

[0102] If the UE supports more than one 3GPP access registration at the same time, then as shown in the attached figure T3, the AMF checks whether the PLMN supports more than one 3GPP access registration from a single UE at the same time.

[0103] If so, then follow the usual registration process as indicated by reference numeral T4 in the attached figure.

[0104] If not, then as indicated by reference numeral T5 in the attached figure, the AMF checks whether this is the first access registration request from the UE in the active PLMN.

[0105] If so, as indicated by reference numeral T6 in the attached figure, the AMF sends a registration acceptance message with the following indication: the PLMN does not simultaneously support more than one 3GPP access registration from the same UE.

[0106] If not, then as indicated by reference numeral T7 in the attached figure, the AMF sends a registration rejection message with the following indication: the PLMN does not simultaneously support more than one 3GPP access registration from the same UE.

[0107] T6 and T7 are followed by T8, where the UE stores the PLMN ID in a list of disabled PLMNs for more than one 3GPP access registration from the same UE. In other embodiments, the UE may store indications that more than one registration to a PLMN is not allowed in any other suitable manner, for example, as per [reference to...]. Figure 1 and 2 The embodiments discussed herein.

[0108] In relation to Figure 3 and Figure 4 In the example discussed, the registration request is for 3GPP access. It should be understood that in other embodiments, registration can be a request for non-3GGP access or any other suitable request for access.

[0109] In some embodiments, the registration call process, such as that described in TS 23.502, Clause 4.2.2.2.2, may be modified to support embodiments such as those previously described. In this regard, reference is made to the diagram illustrating the registration call process. Figure 5a and Figure 5b Various modifications to the registration call process used to support some embodiments will now be discussed. Parts of the process that can be modified to support some embodiments are... Figure 5a and Figure 5b The asterisk is used to indicate: Step 1: The UE simultaneously (e.g., synchronously or concurrently) provides indications of support for more than one 3GPP access registration. This can be a separate indication, or the indication of support can be implicitly derived from the presence of a "registration ID" in the registration request.

[0110] Step 3: The AMF checks whether the UE supports more than one 3GPP access registration simultaneously. This can be based on a new indication or on the presence of a "registration ID" in the registration request.

[0111] If the UE supports more than one 3GPP access registration simultaneously (e.g., synchronously or concurrently), the AMF further checks (based on local configuration and policies) whether more than one 3GPP access registration for a single UE is supported / allowed. If more than one 3GPP access registration for a single UE is not supported / allowed, the AMF further checks whether this is the first 3GPP access registration request from the UE.

[0112] - If this is not the first 3GPP access registration request from the UE, the AMF sends a registration rejection with the following indication: The PLMN does not support more than one 3GPP access registration from a single UE ( Figure 5a and Figure 5b (Not shown in the image).

[0113] - If it is the first 3GPP access registration request from the UE, the AMF continues to process the registration request further in accordance with TS 23.502, Clause 4.2.2.2.2, where changes are made relative to step 21.

[0114] Step 21: In the registration acceptance, the AMF also includes an indication that the PLMN does not simultaneously (e.g., synchronously or concurrently) support more than one 3GPP access registration from a single UE.

[0115] Step 22: The UE stores the PLMN ID in a new list “Disabled PLMNs for more than one 3GPP access registration”.

[0116] If the UE is in automatic network selection mode, then if there is at least one 3GPP (NR) access registration that has been performed and is active by the UE in the PLMN, the UE will then disregard the PLMN for a second 3GPP (NR) access registration.

[0117] If the UE is in manual network selection mode, then if there is at least one 3GPP (NR) access registration that has been performed and is active by the UE in the PLMN, then the UE does not (e.g., avoids presenting) the PLMN for user selection for a second 3GPP (NR) access registration (or displays the PLMN as disabled).

[0118] Figure 6An example of device 200 is shown. Device 200 may include or implement a registration function or AMF as previously described. Device 200 may have at least one processor and at least one memory storing instructions for the registration function or AMF, which, when executed by at least one of the at least one processor, cause the operation or action of performing the corresponding function. In this example, device 200 may include at least one random access memory (RAM) 211a and / or at least one read-only memory (ROM) 211b. Device 200 may include at least one processor 212, 213 and / or a network interface 214. At least one processor 212, 213 may be coupled to at least one memory, which in this example is RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. Software code 215 may, for example, include software code for the registration function or AMF (including software), which allows the device to perform one or more operations of one or more aspects of this aspect.

[0119] Figure 7 An example of a communication device 300 or UE is shown. The communication device 300 can be any device capable of or configured to transmit and receive signals. The communication device can be a wired or wireless device. In the case that the communication device is a wireless device, the signal can be a wireless signal, such as a radio signal. The communication device 300 can include a mobile station (MS) or mobile device, such as a mobile phone or a mobile device called a 'smartphone', a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or tablet computer, a machine-type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination thereof. The communication device can be an XR (extended reality) device, such as a headset, or can be capable of supporting XR applications (e.g., capable of executing or running XR applications). The headset can be a VR headset. The communication device can be a vehicle or part of a vehicle. The communication device 300 can be a user equipment, such as the user equipment shown in the previous figures. The communication device 300 can be configured to transmit or receive wireless signals, such as radio signals carrying communication. Communication can be one or more of the following: voice, email, text message, multimedia, data, machine data, etc.

[0120] When the communication device 300 is a wireless device, it can be configured to transmit and / or receive wireless signals, such as radio signals, via transceiver device 306 through air or radio interface 307. Transceiver device 306 may include, for example, a radio section and an associated antenna arrangement. The radio section can convert baseband signals to radio frequency and / or vice versa. The antenna arrangement can be located inside or outside the mobile device and may include a single antenna or multiple antennas. The antenna arrangement may be an antenna array comprising multiple antenna elements.

[0121] The communication device 300 may include at least one processor 301 and / or at least one memory. The at least one memory may be at least one ROM 302a and / or at least one RAM 302b. Other possible components 303 may be provided for software and hardware-assisted execution of the tasks it is designed to perform, including control of access to and communication with an access network (such as a RAN). At least one processor 301 is coupled to RAM 302b and ROM 302a. The at least one processor 301 may be configured to execute instructions of software code 308. Execution of the instructions of software code 308 may, for example, cause the communication device 300 to perform one or more operations. Software code 308 may be stored in ROM 302a. It should be understood that in other embodiments, any other suitable memory may be used alternatively or additionally.

[0122] At least one processor 301, at least one ROM 302a and / or at least one RAM 302b may be disposed on a suitable circuit board, in an integrated circuit and / or in a chipset. This feature is indicated by reference numeral 304.

[0123] The communication device 300 may optionally have a user interface, such as a keypad 305, a touchscreen or keypad, or a combination thereof. Optionally, the communication device may have one or more of a display, a speaker, and a microphone.

[0124] As provided herein, the term UE or User Equipment is used. This term covers any example of the previously discussed communication device 300 and / or any other communication device.

[0125] refer to Figure 8 ,Should Figure 8 Methods of some embodiments are shown.

[0126] This method can be executed by a device. The device can provide or implement network functionality. This network functionality can be a registration function or an AMF (Application Functionality).

[0127] The device may include suitable components, such as a circuit system for providing the method.

[0128] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.

[0129] Alternatively or additionally, the device may be, for example, regarding Figure 6 The subject of discussion.

[0130] This method can be provided by computer program code or computer executable instructions.

[0131] The method may include, as shown by reference numeral A1 in the attached figure, receiving a registration request from a user equipment for registering with the network.

[0132] The method may include, as shown by reference numeral A2 in the accompanying drawings, sending a registration response to a request to a user equipment, the registration response having an indication indicating whether more than one registration for a user equipment of the same access type is supported simultaneously.

[0133] It should be understood that Figure 8 The methods outlined herein can be modified to include any previously described features.

[0134] refer to Figure 9 ,Should Figure 9 Methods of some embodiments are shown.

[0135] This method can be executed by a device. The device can be a user equipment.

[0136] The device may include suitable components, such as a circuit system for providing the method.

[0137] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.

[0138] Alternatively or additionally, the device may be, for example, regarding Figure 7 The subject of discussion.

[0139] This method can be provided by computer program code or computer executable instructions.

[0140] The method may include, as shown by reference numeral B1 in the attached figure, sending a first registration request for registering with the network.

[0141] The method may include, as shown by reference numeral B2 in the figure, receiving a registration response to a request, the registration response having an indication indicating whether more than one registration for a user equipment of the same access type is supported simultaneously.

[0142] It should be understood that Figure 9The methods outlined herein can be modified to include any previously described features.

[0143] Computer program code can be downloaded and stored in one or more memories of the apparatus described herein.

[0144] Therefore, although certain embodiments have been described above by way of non-limiting and illustrative examples with reference to certain example architectures of communication systems operated by mobile network operators, technologies, and standards, these embodiments can be applied to any other suitable form of communication system compared to those shown and described herein. For example, although some embodiments have been described with respect to 5G systems (5GS), other embodiments can be implemented with respect to 6G systems (6GS) or higher.

[0145] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0146] Generally, various embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. Although various aspects of this disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware, or controllers or other computing devices, or some combination thereof, as non-limiting and illustrative examples.

[0147] As used herein, the term "circuit system" may refer to one or more or all of the following examples: (a) Hardware circuits only (such as analog and / or digital circuits only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor with software (including digital signal processors, software, and memory that work together to enable a device (such as a mobile phone or server) to perform various functions), hardware circuitry, and / or processor (such as a microprocessor or a part of a microprocessor) that requires software (e.g., firmware) to operate, but may not be present when operation is not required.

[0148] This definition of a circuit system applies to all uses of the term "component" herein (including in any claim). As another example, as used herein, the term circuit system also covers only hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term circuit system also covers integrated circuits, such as baseband integrated circuits or processor integrated circuits for use in mobile devices or servers, cellular network devices or other computing or networking devices.

[0149] Embodiments of this disclosure can be implemented by a data processor of a mobile device (such as in a processor entity) or by computer software executed by hardware or a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) can be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components that, when the program is run, are configured to execute the embodiments. The one or more computer-executable components may be at least one piece of software code or a portion of at least one piece of software code.

[0150] Furthermore, it should be noted in this regard that any box in the logical flow diagram may represent a program step, or an interconnected logic circuit, a box and function, or a combination of program steps and logic circuits, boxes and functions. Software may be stored on physical media (such as memory chips or memory blocks implemented within a processor), magnetic media (such as hard disks or floppy disks), and optical media (such as DVDs and their data variants, CDs). Physical media are non-transitory media.

[0151] As used herein, the term “non-transient” refers to the limitations of the medium itself (e.g., tangible rather than signaling), rather than limitations on the persistence of data storage (e.g., RAM versus ROM).

[0152] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and can include one or more of the following as non-limiting and illustrative examples: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures.

[0153] The embodiments of this disclosure can be practiced in various components such as integrated circuit modules. Integrated circuit design is a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready to be etched and formed on a semiconductor substrate.

[0154] The foregoing description has provided a complete and informative description of embodiments of this disclosure through non-limiting and illustrative examples. However, various modifications and variations may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. In fact, other embodiments exist, including combinations of one or more embodiments with any other embodiments discussed above. The scope of protection sought for some embodiments of this disclosure is set forth in the claims. Embodiments and features thereof, if any, described in this specification that are not within the scope of the claims are to be interpreted as examples for understanding the various embodiments of this disclosure. It should be noted that different claims with different scopes may be sought in related applications such as divisional or continuation applications.

Claims

1. An apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by said at least one processor, causing the apparatus to perform at least the following: Receive a registration request from the user equipment for registering with the network; and A registration response to the request is sent to the user equipment, the registration response having an indication indicating whether more than one registration for a user equipment of the same access type is supported simultaneously.

2. The apparatus of claim 1, wherein the indication is used to indicate that the network does not simultaneously support more than one registration for user equipment of the same access type.

3. The apparatus of claim 1, wherein the indication is used to indicate that the network indeed supports more than one registration for user equipment of the same access type at the same time.

4. The apparatus according to any one of the preceding claims, wherein the registration request includes information indicating that the user equipment simultaneously supports more than one registration for the same access type.

5. The apparatus according to any one of the preceding claims, wherein the apparatus is configured to: determine whether the user equipment simultaneously supports more than one registration for the same access type, and when the user equipment simultaneously supports more than one registration for the same access type, send the registration response to the user equipment.

6. The apparatus according to any one of the preceding claims, wherein the apparatus is configured to: determine whether the registration request is a first activity request from the user equipment for a first access type, for registering with the network.

7. The apparatus of claim 6, wherein when the registration request is determined to be a first activity request for registration with the network for the first access type, the registration response includes a registration acceptance response.

8. The apparatus of claim 6 or 7, wherein when the registration request is determined not to be a first activity request for registration with the network for the first access type, and the network does not simultaneously support more than one registration for a user equipment for the same access type, the registration response includes a registration rejection response.

9. A user equipment comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the user equipment to perform at least the following: Send a first registration request for network registration; and Receive a registration response to the request, the registration response having an indication indicating whether more than one registration for the user equipment of the same access type is supported simultaneously.

10. The user equipment of claim 9, wherein the indication is used to indicate that the network does not simultaneously support more than one registration of the user equipment for the same access type.

11. The user equipment of claim 9, wherein the indication is used to indicate that the network does indeed simultaneously support more than one registration of the user equipment for the same access type.

12. The user equipment according to any one of claims 9 to 11, wherein the first registration request includes information indicating that the user equipment simultaneously supports more than one registration for the same access type.

13. The user equipment according to any one of claims 9 to 12, wherein when the registration request is a first activity request for registering with the network for a first access type, the first registration response includes a registration acceptance response.

14. The user equipment according to any one of claims 9 to 12, wherein when the first registration request is not a first activity request for registration with the network for a first access type, and the network does not simultaneously support more than one registration of the user equipment for the same access type, the registration response includes a registration rejection response.

15. The user equipment according to any one of claims 9 to 14, wherein the registration request includes a registration request for 3GPP access or a registration request for non-3GPP access.

16. The user equipment according to any one of claims 9 to 15, wherein the user equipment is configured to: determine whether a second registration request for registering with the network for the same access type as the first registration request should be sent, the determination being based on the indication received in the registration response.

17. The user equipment according to any one of claims 9 to 16, wherein the user equipment is configured to: select a network to which a second registration request of the same access type as the first registration request is to be sent, the selection being based on one or more of the instruction or local network selection policy.

18. A method comprising: Receive a registration request from the user equipment for registering with the network; as well as A registration response to the request is sent to the user equipment, the registration response having an indication indicating whether more than one registration for a user equipment of the same access type is supported simultaneously.

19. A method comprising: Send a first registration request to register with the network; as well as Receive a registration response to the request, the registration response having an indication indicating whether more than one registration for the user equipment of the same access type is supported simultaneously.

20. A computer program comprising computer-executable code, said computer-executable code causing the method of claim 18 or claim 19 to be performed when executed.

Images