Management of ue configuration in serving plmn in presence of default configuration for ue for all plmns
Patent Information
- Application Number
- JP2024150617
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2018-07-23
- Filing Date
- 2024-09-02
- Publication Date
- 2025-01-24
AI Technical Summary
Existing cellular systems face challenges in efficiently managing user equipment (UE) configurations when roaming, as both resource-intensive network-specific configurations and complex home network management are undesirable solutions for updating UE configurations in visited networks.
A method where the UE detects its default configuration and sends explicit notifications to the serving network, allowing the network to provide network-specific configurations when necessary, thereby optimizing resource usage and simplifying management.
This approach enables efficient and optimized configuration updates for UEs in visited networks, reducing resource consumption and complexity in network management.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application No. 62 / 702,291, filed July 23, 2018, entitled "MANAGING UE CONFIGURATION IN A SERVING PLMN IN THE PRESENCE OF A DEFAULT CONFIGURATION FOR THE UE FOR ALL PLMNS," the disclosure of which is incorporated herein by reference for all purposes.
[0002] Field The technical subject matter described in this specification relates to wireless.
[0003] As cellular systems, including Fifth Generation (5G) systems, support an ever-increasing number of devices and services, including applications with a wide range of use cases and diverse needs for bandwidth, latency, and reliability requirements, the cellular systems may need to prioritize resources across the radio access network and core network (and / or prioritize across the control plane and user plane, for example) to support differentiation between different services.
[0004] SUMMARY OF THE DISCLOSURE Methods and apparatus, including computer program products, for managing configuration updates are provided.
[0005] In some example embodiments, an apparatus may be provided that includes at least one processor and at least one memory including computer program code configured to cause the apparatus to at least detect a network for registration by the at least one processor, and when the apparatus is configured with a default configuration but does not include a network-specific configuration for the network, send an indication to the network that the apparatus is using the default configuration for at least one service available on the network.
[0006] In some variations, the present invention may include one or more of the features disclosed herein, including the following features, possibly in any feasible combination: The default configuration may include a configuration for accessing the at least one service on all public land mobile networks that the device may access while roaming. The network-specific configuration may include a configuration for accessing the at least one service, the configuration being specific to the network that serves the device. The default configuration may include a default set of requested network slice selection assistance information valid for all public land mobile networks that the device may access while roaming. The network-specific configuration may include requested network slice selection assistance information specific to the network that serves the device. The network may be accessed by the default configuration or the network-specific configuration for the at least one service. The notification may be an explicit notification carried by a registration message, an authentication message, and / or a request message. The network-specific configuration may be received from the network in response to the notification that the device is using a default configuration, a network-specific configuration. When the device is configured with the default configuration and includes a network-specific configuration for the network, a notification may be sent to the network that the device is using the network-specific configuration for the at least one service available on the network. The notification that the device is using a network-specific configuration may be implicit.
[0007] In some example embodiments, an apparatus may be provided that includes at least one processor and at least one memory including computer program code configured to at least: when a user equipment is configured with a default configuration but does not include a network-specific configuration for the network, receive a notification by the at least one processor that the user equipment is using a default configuration for at least one service available on the network, detect based on the notification that the user equipment should be updated with a network-specific configuration, and send the network-specific configuration in response to the detected notification.
[0008] In some variations, the present invention may include one or more of the features disclosed herein, including the following features, possibly in any feasible combination: The default configuration may include a configuration for accessing the at least one service on all public land mobile networks that the user equipment may access while roaming. The network-specific configuration may include a configuration for accessing the at least one service, the configuration being specific to the network that serves the user equipment. The default configuration may include a default set of requested network slice selection assistance information that is valid for all public land mobile networks that the user equipment may access while roaming. The network-specific configuration may include requested network slice selection assistance information specific to the network that serves the user equipment. The notification may be an explicit notification included in a registration message, an authentication message, and / or a request message received by the device. A network-specific configuration may be sent in response to the notification that the user equipment is using a default configuration, a network-specific configuration. When the user equipment is configured with the default configuration and includes a network-specific configuration for the network, an indication may be received that the user equipment is using the network-specific configuration for the at least one service available on the network. The indication that the device is using a network-specific configuration may be implicit. The device may include or be included in a network node. In this case, the network node may include a base station and / or an access and mobility management function.
[0009] The above aspects and features may be implemented in a system, apparatus, method, and / or product, depending on the desired configuration. Details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. Features and advantages of the subject matter described herein will be apparent from the specification and drawings, and from the claims. [Brief description of the drawings]
[0010] In the drawings:
[0011] [Figure 1] 1 illustrates an example of a portion of a 5G wireless network in accordance with some exemplary embodiments.
[0012] [Figure 2A] 1 illustrates several example process flows for UE configuration, according to some exemplary embodiments. [Figure 2B] 1 illustrates several example process flows for UE configuration, according to some exemplary embodiments. [Figure 2C] 1 illustrates several example process flows for UE configuration, according to some exemplary embodiments.
[0013] [Diagram 3] 13 illustrates another example of a process flow for UE configuration, according to some exemplary embodiments.
[0014] [Figure 4] 1 illustrates an example of a network node, according to some exemplary embodiments.
[0015] [Diagram 5] 1 illustrates an example of an apparatus, according to some exemplary embodiments.
[0016] In the drawings, like labels are used to refer to the same or similar items.
[0017] In systems such as cellular systems, a user equipment (UE) may be provided with a default configuration, such as one or more settings, applicable to the UE while the UE is roaming as well as while in the UE's home network. This default configuration may enable the UE to have immediate access to a particular service provided by a network. The network may grant access based on the UE's (or the associated user's) subscription and the support of the particular service by the serving network operator. However, if the serving network has a specific configuration that should be applied to override the default configuration in the UE, there may be a problem on how to configure the UE with the serving network's specific configuration. One solution may be for the serving network (e.g., a network that may provide a network specific configuration to the UE) to always provide a configuration to the UE upon the UE's visit to the serving network. However, this may be resource intensive in terms of network resources. Another possible solution may be to let the UE's home network handle the configuration of the UE for all networks, but this may require the home network to know details of all possible serving networks for the UE. However, this solution may be undesirable because it may be overly complicated to manage, at least from the home network's perspective (because the home network would need to have up-to-date, updated network-specific configuration information for a relatively large number of serving networks).
[0018] In some exemplary embodiments, a method is provided whereby a serving network can detect that a UE is operating using a pre-configured configuration, such as a default configuration. In this case, the serving network may begin updating the UE with a more current UE configuration, such as a network-specific configuration for the serving network. In some exemplary embodiments, the pre-configured configuration is related to the UE's access to at least one service available on the network. In some exemplary embodiments, the at least one service includes multiple network slices, although other types of services may also be used.
[0019] In some example embodiments, an explicit notification may be provided to the network so that the network knows that the UE is using a pre-configured, default, etc. configuration. In some example embodiments, this notification is carried in a request, such as a registration request, or other type of message sent by the UE to the network.
[0020] Before providing additional information regarding UE configurations according to some example embodiments, an example of a portion of a 5G wireless network 100 will be described with respect to FIG.
[0021] 5G wireless network 100 may include user equipment (UE) 150 configured to wirelessly couple to a radio access network (RAN) 152 served by wireless access points such as base stations, wireless local area network access points, home base stations, and / or other types of wireless access points. When visiting a network, the UE may access the radio access network of that network.
[0022] Network 100 may include a core network. The core network may include an access and mobility management function (AMF) 154, a visiting session management function (V-SMF) 156, a visiting policy control function (v-PCF) 160, a visiting network slice selection function (v-NSSF) 164, and / or a visiting user plane function (V-UPF) 158. In the example of FIG. 1, devices 152-164 may be associated with a visiting public land mobile network (VPLMN) 166.
[0023] Network 100 and / or the core network may also include devices having functions supporting a home public land mobile network (HPLMN) 170. For example, the devices in the HPLMN 170 may include devices and corresponding functions for “home” wireless local area network (WLAN) access, offloading, and / or non-3GPP access. These devices may include a home SMF 172, a home PCF 174, a home NSSF 176, a unified data management 178, an authentication server function (AUSF) 180, an application function (AF) 182, a home user plane function (H-UPF) 184, and a data network (DN) 186.
[0024] 1 also shows service interfaces such as N1, N2, N3, N4, N6, N7, N11, N15, N18, N24, and / or the like. The architecture, nodes (including the AMF, V-PCF, H-PCF, H-SMF, and V-SMF, as well as other devices shown in FIG. 1), and service interfaces may be defined according to a standard such as 3GPP TS 23.501, although other standards and proprietary interfaces may also be used. Although FIG. 1 shows a single visited network and a single home network, other numbers of visited and / or home networks may also be included.
[0025] A network slice, as described above, refers to a logical network that provides certain network capabilities and network characteristics. A network slice can be considered as a logical end-to-end network that can be dynamically created so that a given UE can access multiple different network slices on the same radio access network (e.g., via the same radio interface). Each network slice can provide different services and / or have different QoS needs / requirements. 3GPP TS 23.501, the system architecture for 5G systems, describes multiple examples of network slices.
[0026] The UE's subscription information may specify configuration information regarding the number, QoS type, and / or identity of network slices. The UE's configuration information (provided by the network upon registration in a PLMN, such as a VPLMN and / or HPLMN) may include one or more network slice identifiers, such as one or more single network slice selection assistance information (S-NSSAI). The S-NSSAI may include: It may consist of a) a slice / service type (SST), which refers to the expected network slice behavior in terms of features and services, and / or b) a slice differentiator (SD), which is optional information that complements one or more slice / service types to distinguish multiple network slices of the same slice / service type.
[0027] The following example uses an example with respect to network slicing, but this is for illustrative purposes and other types of services may be used. For example, in the case of 5G, the UE may be configured with information, such as configuration information for enabling services such as network slicing, by a serving network, such as a visited public land mobile network (VPLMN) and / or a home public land mobile network (HPLMN), for example according to 3GPP TS 23.501. This configuration information enables the UE to use and thus access one or more services, such as network slicing, in the serving network based on the UE's subscription (as well as the PLMN configuration information provided to the UE by the network). This configuration information may change over time due to local decisions by the VPLMN or for other reasons, as well as the home network or HPLMN implementing changes to the UE's subscription. For example, in the case of 3GPP TS 23.501, the configuration information may relate to network slicing. The configuration information in this case may be referred to as configured network slice selection assistance information (NSSAI). Each S-NSSAI in the S-NSSAI collection may point to a given network slice.
[0028] For example, in 3GPP TS 23.501, registration to a network slice set may be performed according to the following: When a requested NSSAI is not included in the UE's request (e.g., registration request) and / or when the mapping between each S-NSSAI in the requested NSSAI and each corresponding value in the NSSAI configured for the HPLMN is invalid and / or when the S-NSSAI is rejected in the PLMN, the access and mobility management function (AMF) 154 may update the UE's 150 configuration information for one or more network slices associated with the PLMN. When the UE does not have "slice" configuration information to use in the PLMN, the UE may not include a requested NSSAI (e.g., an NSSAI including an S-NSSAI for each slice for which the UE requests the network to provide access) in the PLMN registration request. In this case, the PLMN may configure the UE with the NSSAI configured for the PLMN. Furthermore, when the PLMN detects an invalid requested NSSAI, the UE configuration may be performed.
[0029] However, if a default configuration exists in the UE, the requested NSSAI can be provided to the PLMN in either case. This can be considered as a valid requested NSSAI. The default configuration represents a configuration that the UE should use, for example, when the UE does not have a PLMN / network specific configuration to be used in a particular serving network, and is considered valid for some, if not all, PLMNs. For example, this configuration information can include an S-NSSAI or an S-NSSAI set that is understood by some, if not all, PLMNs in which the UE can roam, in the case of multiple network slices. Thus, if more S-NSSAIs are used in the PLMN, these additional S-NSSAIs cannot be configured in the UE. The reason is that the UE has not provided an incorrect requested NSSAI (e.g., an incorrect requested NSSAI would trigger the network to update the UE with updated configuration information). Since the UE has a default NSSAI that is used in some, if not all, PLMNs, the UE can include the default NSSAI in a registration message sent to the network, for example. Therefore, the UE cannot send an empty requested NSSAI in the registration request. If the UE does have a specific configuration for the serving PLMN, but only uses network slices that are present in the default configuration for some, if not all, PLMNs, the serving network may not be able to detect that the UE did not have a PLMN-specific configuration, since the default configuration is used by the UE. This example with respect to the network slice illustrates the need for a notification to be sent to the network to enable the network to detect if the UE is using the default configuration.
[0030] In some example embodiments, when a UE is configured with a default configuration that applies to some, if not all, PLMNs that do not have a PLMN-specific configuration and is registering with a serving network (e.g., a serving PLMN) for which the UE does not have specific configuration information, the UE may use a pre-configured configuration, such as the default configuration, as its configuration. Additionally, the UE may inform (indicate) the network of the use of a pre-configured configuration, such as the default configuration. According to some example embodiments, the UE may inform the network of its use via a request message, such as a network registration message, and / or other types of messages.
[0031] If the serving PLMN is operated such that the UE is expected to be configured with a network-specific (e.g., PLMN-specific) configuration in the serving PLMN, the serving PLMN may provide the necessary PLMN-specific configuration to the UE. The serving PLMN may provide the PLMN-specific configuration to the UE in response to a request or notification, such as a registration message, sent by the UE to the network. If the serving PLMN is operated such that the UE is expected to use only default configurations for all PLMNs in the PLMN, the serving PLMN does not need to provide the PLMN-specific configuration to the UE (e.g., because there is no PLMN-specific configuration available to the UE). The serving PLMN may provide the PLMN-specific configuration to the UE in response to a request or notification, such as a registration message, sent by the UE to the network. The serving PLMN may be a visited PLMN, but may also be a home PLMN.
[0032] When a UE includes as part of its configuration a PLMN-specific configuration for a serving network and a default configuration for all PLMNs, the UE may register with the PLMN-specific configuration in the serving PLMN, but the UE may not inform the network that the UE also has the default configuration.
[0033] FIG. 2A illustrates an example of a process 200 for configuring a UE, according to some example embodiments.
[0034] At 210, according to some example embodiments, the UE may detect a candidate network for registration. For example, the UE 150 may roam and / or visit another network. In this case, the UE 150 may detect radio access networks 152 served by base stations and / or other network nodes. As described above, the UE 150 may have a network-specific configuration that the UE 150 should use to access services, such as network slices, in the VPLMN associated with the RAN 152. Alternatively or in addition, the UE 150 may not have a network-specific configuration. Instead, the UE 150 may have a pre-configured, or default, configuration that the UE 150 should use when accessing multiple services on multiple networks. This default configuration should be used by the UE 150 in some, if not all, networks / PLMNs if a given visited serving network does not have its own network-specific configuration that the UE 150 should use to access the services. Thus, once the registration is accepted by the network, the UE may access default-configured services in that network.
[0035] According to some example embodiments, when a UE is configured with a default configuration for at least one service available on the network, but does not include a network-specific configuration for the network, the UE may send a notification to the network at 215 that the UE is using a default configuration for the at least one service. For example, the UE 150 may send a notification (which may be carried by or include a message, request, registration request, and / or the like) to the radio access network 152. This notification may be an explicit notification that the UE 150 is configured for a pre-configured, or default, configuration to access at least one service on the network.
[0036] For example, in the case of network slicing, the registration request may include an indication that a default set of requested NSSAIs is to be used, although this indication may also correspond to other types of services. This indication may be explicit, such as a flag, bit, value, or other indication in the registration request. Alternatively, or in addition, the registration request may also include a default set of requested NSSAIs to be used. For example, the registration message may include a default configuration (e.g., a configured NSSAI that is valid for all PLMNs that do not have a network / PLMN-specific NSSAI) and an indication that UE 150 is configured with the default configuration to access at least one service on the network.
[0037] In some example embodiments, the notification sent at 215 may inform various configurations, such as whether a default configuration or other configurations (e.g., network-specific configurations) are used at the UE. Alternatively or additionally, the notification may inform of a default network slicing configuration, while other notifiers may be used for other configuration aspects at the UE. In some example embodiments, the notifier may be realized by one or more bits (or other types of notifiers) carried by the message to inform the network whether a default configuration is used, and / or the like. Returning to the previous example, the registration message may include an explicit notification that the UE 150 is configured for a pre-set, or default, configuration to access at least one service on the network. The registration message may include one or more other notifications to inform the network of other UE configuration aspects at the UE, such as other types of services. To further explain, a first notification may be used to inform the network of the network slicing configuration present at the UE, while another notification may be used to inform the network of another service configuration handled at the UE. For example, a UE may have a default configuration for network slicing and one default configuration for RAT selection. For example, if the UE prioritizes use of WIFI for services that use 3GPP access on PLMNs other than the serving PLMN, the default configuration for RAT may prioritize 3GPP access or WiFi for a particular service, where the serving PLMN may be configured differently. In this example, the UE may obtain a new RAT policy from the network upon UE registration.
[0038] At 220, the UE may receive a network-specific configuration from the network according to some example embodiments. This network-specific configuration may be received by the UE 150 in response to sending a notification to the network at 215. As noted, the notifier sent at 215 allows the network (e.g., a network node such as a base station, an AMF, and / or the like) to detect whether a default configuration is being used at the UE and, if so, whether the network wants to update the configuration at the UE. If the network has a network-specific configuration to be used by the UE 150 instead of the default configuration, the network may provide another configuration, such as a network-specific configuration for the service to be accessed. For example, in the case of network slicing, the network may provide the UE with a configured NSSAI to be used by the UE 150. A network-specific configuration refers to a configuration specifically for the network. In this sense, a network-specific configuration is specific to the network.
[0039] When the UE is configured with a default configuration for at least one service available on the network and includes a network-specific configuration for the network, the UE may send a notification to the network, at 230, that the UE is using a network-specific configuration for the at least one service. For example, the UE 150 may send a notification (which may be carried by or include a message, request, registration request, and / or the like) to the radio access network 152. The notification may inform the radio access network 152 that the UE 150 is configured for a network-specific configuration to access at least one service on the network. However, the UE may not inform the network that it has a pre-configured, or default, configuration. For example, in the case of network slicing, the registration request may include a network-specific set of requested NSSAIs. In some example embodiments, the notification that the UE is using a network-specific configuration may be explicit. In this case, the notification may include a flag, bit, value, or any other type of notification that indicates that the UE is using a network-specific configuration for at least one service. Alternatively, or in addition, the notification that the UE is using a network-specific configuration may be implicit (e.g., the absence of a notification (sent by the UE at 215) may inform the network that the UE is using a network-specific configuration for at least one service).
[0040] At 240, the UE may access a network, such as the RAN 152, using a default configuration or a network-specific configuration for at least one service. For example, once the registration is accepted by the network, the UE may access a network-specific service on the network using the default configuration signaled at 215 or the network-specific configuration received at 220 (or pre-stored in the UE).
[0041] 2B illustrates a UE registration request process 299 according to some example embodiments. The notification described above in 215 and 230 of FIG. 2A may be sent at 250 (FIG. 2B). For example, in the case of network slicing, the UE 150 may include a notification at 250 that, if not configured with PLMN-specific configured NSSAI information, it is using information from NSSAIs configured for some, if not all, PLMNs to configure the requested NSSAI.
[0042] If the AMF expects the UE to use one configured NSSAI for the PLMN and the UE has indicated at 250 that the UE was using information from a configured NSSAI that is valid for some, if not all, PLMNs that do not have a network / PLMN-specific configured NSSAI, the AMF 154 may return the configured NSSAI for the PLMN at 252. When the requested NSSAI was not included and / or the mapping between the S-NSSAI in the requested NSSAI and the corresponding value in the NSSAI configured for the HPLMN is incorrect and / or the S-NSSAI is rejected in the PLMN and / or the UE has indicated that it is operating using information in the configured NSSAI for some, if not all, PLMNs and the serving PLMN expects the UE to use the PLMN-specific configured NSSAI, the AMF may update the UE network slice configuration information for the PLMN, e.g., according to TS 23.501 (see, e.g., clause 5.15.4.2).
[0043] 2C illustrates an AMF performing UE configuration using a UE configuration update, such as according to clause 4.2.4 of TS 23.502. FIG. 2C illustrates a process 290 that includes sending configuration information by the AMF 154 to the UE 150 via the RAN 152. In this example, the configuration information is an updated configuration (e.g., a more recent default configuration and / or a network-specific configuration) for the UE 152. In the case of network slicing, the AMF may provide configured NSSAI information for the particular network / PLMN being accessed.
[0044] Although some of the examples described herein refer to a service as network slicing, the service may also correspond to other services, as noted.
[0045] Although some of these examples describe notification being sent by a registration message at 210 and 230, other types of messages to the network may also carry this notification. For example, an authentication message or other types of messages may provide this notification to the network.
[0046] 3 illustrates an example of a process 300 according to some example embodiments. The description of FIG. 2 also refers to FIG.
[0047] According to some example embodiments, a network node, such as a base station serving the radio access network 152, may receive 310 from the AMF 154 an indication as to whether the UE is using a default configuration for at least one service or a network-specific configuration for the at least one service. The indication may be provided as part of a message, a request, an authentication message, a network registration request, and / or other type of message. For example, the network node may receive an explicit indication from the UE that the UE is using a default configuration (available on some, if not all, PLMNs) for at least one service available on the network. The network node may receive an explicit indication from the UE when the UE is configured with a default configuration but does not include a network-specific configuration for the network.
[0048] Based on this notification, the network node may detect that the UE has a default configuration at 315. Thus, the network node has the knowledge to determine at the network node whether to update the default configuration with a network-specific configuration for the network, e.g., in the case of network slicing:
[0049] At 320, the network node may provide (e.g., send) configuration information to the UE. For example, a network, such as a network node, may provide configuration information for updating the UE to use at least one service on the network. In the case of network slicing, the network node may respond with a network-specific configuration of the NSSAI configured for use in the visited serving network.
[0050] Figure 4 illustrates a block diagram of a network node 400 according to some example embodiments. The network node 400 may be configured to provide one or more network side operations, for example, as described with respect to Figure 3. Furthermore, a mobile wireless network may also have multiple network nodes 400. For example, a network node may be incorporated in one or more of the devices 152-180.
[0051] The network node 400, according to some example embodiments, may include a network interface 402, a processor 420, and a memory 404. The network interface 402 may include wired and / or wireless transceivers to enable access to other nodes, including base stations, the devices 152-180, the Internet, and / or other nodes. The memory 404 may comprise volatile and / or non-volatile memory containing program code that, when executed by the at least one processor 420, provides processes disclosed herein, including, among others, processes 200, 300, 400, and / or the like.
[0052] FIG. 5 illustrates a block diagram of the device 10 according to some example embodiments.
[0053] Apparatus 10 may represent user equipment, such as user equipment 150. Apparatus 10, or portions thereof, may be implemented in other network nodes, including base stations / WLAN access points, as well as other network nodes (e.g., devices 152-184).
[0054] The device 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively, the transmitting and receiving antennas may be separate. The device 10 may further include a processor 20. The processor 20 is configured to provide and receive signals to and from the transmitter and receiver, respectively, and to control the functions of the device. The processor 20 may be configured to control the functions of the transmitter and receiver by transmission of control signals to the transmitter and receiver via electrical leads. Similarly, the processor 20 may be configured to control other elements of the device 10 by transmission of control signals via electrical leads connecting the processor 20 to the other elements, such as a display or memory. The processor 20 may be embodied in various ways, for example. For example, the processor 20 may include circuitry, at least one processing core, one or more microprocessors having one or more digital signal processors, one or more processors without an associated digital signal processor, one or more co-processors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and / or the like), or combinations thereof. Thus, although processor 20 is illustrated in FIG. 5 as a single processor, in some exemplary embodiments, processor 20 may comprise multiple processors or processing cores.
[0055] The device 10 may be operable with one or more air interface standards, communication protocols, modulation types, access types, and / or the like. Signals transmitted and received by the processor 20 may include signal information according to any number of different wired or wireless networking schemes, including, but not limited to, the air interface standard of the relevant cellular system, Wi-Fi, and / or wireless local access network (WLAN) schemes such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and / or the like. Additionally, these signals may include voice data, user generated data, user requested data, and / or the like.
[0056] For example, device 10 and / or a cellular modem therein may be capable of operating according to various first generation (1G), second generation (2G or 2.5G), third generation (3G), fourth generation (4G), fifth generation (5G), Internet Protocol Multimedia Subsystem (IMS) communications protocols (e.g., session initiation protocol (SIP)), and / or the like. For example, device 10 may be capable of operating according to 2G wireless communication protocols IS-136, Time Division Multiple Access (TDMA), Global System for Mobile communications (GSM), IS-95, Code Division Multiple Access (CDMA), and / or the like. Additionally, for example, device 10 may be capable of operating according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and / or the like. Further, for example, device 10 may be capable of operating according to 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), WCDMA, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and / or the like.Apparatus 10 may further be capable of operating according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or the like. Additionally, for example, apparatus 10 may be capable of operating according to 4G wireless communication protocols, such as LTE-Advanced, 5G, and / or the like, as well as similar wireless communication protocols that may be subsequently developed.
[0057] It should be understood that the processor 20 may include circuitry for implementing the audio / video and logic functions of the device 10. For example, the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and / or the like. The control and signal processing functions of the device 10 may be allocated among these devices according to their respective capabilities. The processor 20 may further comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and / or the like. Additionally, the processor 20 may include functionality for running one or more software programs. These programs may be stored in memory. In general, the processor 20 and the stored software instructions may be configured to cause the device 10 to perform a number of actions. For example, the processor 20 may run a connectivity program such as a web browser. The connectivity program may enable device 10 to send and receive web content, such as location-based content, according to protocols such as wireless application protocol (WAP), hypertext transfer protocol (HTTP), and / or the like.
[0058] The device 10 may further include a user interface that may be operatively coupled to the processor 20. The user interface may include, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and / or the like. The display 28 may include a touch-sensitive display, as described above, in which a user may make selections, input values, and / or the like by touch and / or gestures. The processor 20 may also include user interface circuitry configured to control at least some functionality of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and / or the like. The processor 20 and / or user interface circuitry comprising the processor 20 may be configured to control one or more elements of the user interface by computer program instructions, e.g., software and / or firmware, stored in, for example, a memory accessible to the processor 20, e.g., a volatile memory 40, a non-volatile memory 42, and / or the like. Device 10 may include a battery for powering various mobile device related circuits, such as circuitry for providing mechanical vibration as a detectable output. A user input interface may include devices for receiving data into device 20, such as a keypad 30 (possibly a virtual keyboard displayed on display 28 or an externally connected keyboard) and / or other input devices.
[0059] As shown in FIG. 5, the device 10 may also include one or more mechanisms for sharing and / or obtaining data. For example, the device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64 so that it can share data with and / or obtain data from multiple electronic devices according to RF methods. The device 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a Bluetooth (BT) transceiver 68 operating using Bluetooth wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth low energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and / or any other short-range wireless technology. The device 10, particularly the short-range transceiver, may be capable of transmitting data to and / or receiving data from electronic devices in the vicinity of the device, such as within 10 meters. The device 10, which includes a Wi-Fi or wireless local area networking modem, may also be capable of transmitting data to and / or receiving data from a number of electronic devices according to various wireless networking standards, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN standards such as IEEE 802.11, IEEE 802.15, IEEE 802.16, and / or the like.
[0060] The device 10 may include memory that may store information about a mobile subscriber, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, a UICC, and / or the like. The device 10 may include other removable and / or fixed memory in addition to the SIM. The device 10 may include volatile memory 40 and / or non-volatile memory 42. For example, the volatile memory 40 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, and / or the like. The embedded and / or removable non-volatile memory 42 may include, for example, read-only memory, flash memory, magnetic storage devices, such as hard disks, floppy disk drives, magnetic tapes, optical disk drives and / or media, non-volatile random access memory (NVRAM), and / or the like. Similar to the volatile memory 40, the non-volatile memory 42 may include a cache area for temporary storage of data. At least a portion of the volatile and / or non-volatile memory may be embedded in the processor 20. These memories may store one or more software programs, instructions, information, data, and / or the like that may be used by the device to perform the operations disclosed herein. Alternatively, or in addition, the device may be configured to cause network nodes, including base stations / WLAN access points and UEs, to perform the operations disclosed herein.
[0061] The memory may include an identifier capable of uniquely identifying device 10, such as an international mobile equipment identification (IMEI) code. The memory may include an identifier capable of uniquely identifying device 10, such as an international mobile equipment identification (IMEI) code. In the exemplary embodiment, processor 20 may be configured using computer code stored in memory 40 and / or 42 to provide operations disclosed herein (e.g., see processes 200, 290, 299, 300, and / or the like) for network nodes, including base stations / WLAN access points and UEs.
[0062] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside, for example, in memory 40, controller 20, or electronic components. In some exemplary embodiments, the application logic, software, or instruction set may be held in any one of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any non-transitory medium capable of containing, storing, communicating, propagating, or transporting instructions for use by or in connection with an instruction execution system, apparatus, or device such as a computer or data processor circuit. In the example shown in FIG. 5, the computer-readable medium may comprise a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium may comprise a non-transitory computer-readable medium, which may be any medium capable of containing or storing instructions for use by or in connection with an instruction execution system, apparatus, or device such as a computer.
[0063] Without limiting the scope, interpretation, or application of the appended claims in any way, a technical effect of one or more of the example embodiments disclosed herein may be an improved UE configuration.
[0064] The subject matter described herein may be embodied in a system, apparatus, method, and / or product, depending on the desired configuration. For example, the base station and user equipment (or one or more components therein) and / or the processes described herein may be implemented using one or more of a processor executing a program code, an application specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and / or a combination thereof. These various implementations may include implementation as one or more computer programs executable and / or interpretable on a programmable system including at least one dedicated or general-purpose programmable processor coupled to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented programming language, and / or assembly / machine language. The term "computer-readable medium" as used herein refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus, and / or device (e.g., magnetic disks, optical disks, memory, programmable logic devices (PLDs)) used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium that accepts machine instructions. Also described herein are systems that may include a processor and a memory coupled to the processor. The memory may contain one or more programs that cause the processor to perform one or more of the operations described herein.
[0065] Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and / or variations may be provided in addition to those described herein. Moreover, the above implementations may relate to various combinations and subcombinations of the features disclosed and / or combinations and subcombinations of some further features disclosed above. Other embodiments may fall within the scope of the appended claims.
[0066] If desired, different functions described herein may be performed in different orders and / or simultaneously with each other. Furthermore, if desired, one or more of the above functions may be optional or combined. Various aspects of some of the embodiments are set forth in the independent claims, while other aspects of some of the embodiments include other combinations of features of the described embodiments and / or dependent claims with features of the independent claims, as well as combinations explicitly set forth in the claims. It should also be noted that while several exemplary embodiments are described above, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of some of the embodiments as defined in the appended claims. Other embodiments may be included within the scope of the appended claims. The term "based on" includes "based on at least". The use of the phrase "such as" means "such as for example", unless otherwise indicated.
Claims
1. At least one processor; at least one memory containing computer program code; wherein the computer program code, when executed by the at least one processor, causes the device to sending a notification to the network during registration request processing and when the device is not configured with public land mobile network-specific configured network slice selection assistance information for the network, that the device is using configured network slice selection assistance information valid for all public land mobile networks that do not have public land mobile network-specific configured network slice selection assistance information to configure requested network slice selection assistance information; receiving from the network in response to the notification during the registration request processing network slice selection assistance information of a public land mobile network specific configuration for the network; The apparatus is configured to cause
2. The apparatus of claim 1 , wherein the notification is sent in a registration request message.
3. 3. The apparatus of claim 2, wherein the registration request message further comprises the configured network slice selection assistance information valid for all public land mobile networks that do not have public land mobile network-specific configured network slice selection assistance information.
4. The apparatus of any one of claims 1 to 3, wherein network slice selection assistance information of the public land mobile network specific configuration for the network is received in a registration acceptance message.
5. The apparatus of any one of claims 1 to 4, wherein the apparatus comprises a user equipment.
6. sending, by the device and to the network, during registration request processing and when the device is not configured with public land mobile network-specific configured network slice selection assistance information for the network, a notification that the device is using configured network slice selection assistance information valid for all public land mobile networks that do not have public land mobile network-specific configured network slice selection assistance information to configure requested network slice selection assistance information; receiving, by the device and from the network during the registration request processing, network slice selection assistance information of a public land mobile network specific configuration for the network in response to the notification; A method comprising:
7. The method of claim 6 , wherein the notification is sent in a registration request message.
8. 8. The method of claim 7, wherein the registration request message further comprises the configured network slice selection assistance information valid for all public land mobile networks that do not have public land mobile network-specific configured network slice selection assistance information.
9. The method according to any one of claims 6 to 8, wherein network slice selection assistance information of the public land mobile network specific configuration for the network is received in a registration accept message.
10. The method of any one of claims 6 to 9, wherein the apparatus comprises a user equipment.
11. A non-transitory computer readable medium encoded with instructions and instructions for causing a processor to perform the method of any one of claims 6 to 10.