Efficient registration in area where slice service is supported partially

Abstract

To provide systems, methods, apparatuses, and computer program products for efficient registration for partially supported service areas.SOLUTION: One method may include providing, to at least one user equipment registered to a network within a registration area, information comprising one or more pieces of single network slice selection assistance information (S-NSSAIs) and one or more pieces of tracking area identities (TAIs). Each of the one or more pieces of single network slice selection assistance information (S-NSSAIs) is included in a list of rejected single network slice selection assistance information (S-NSSAIs) or in a list of extended rejected single network slice selection assistance information (S-NSSAIs), and is associated with a cause value indicating that the one or more pieces of single network slice selection assistance information (S-NSSAIs) is not supported uniformly in the registration area and is not supported in a current tracking area.SELECTED DRAWING: Figure 5B

Description

Technical Field

[0001] The present disclosure generally relates to communications including mobile or wireless communication systems, such as mobile or wireless communication systems based on Long Term Evolution (LTE) or fifth generation (5G) or new radio (NR) radio access technologies, or other mobile or wireless communication system telecommunications systems. For example, certain exemplary aspects may generally relate to systems and / or methods for efficient registration in an area where a service is partially supported.

Background Art

[0002] The mobile body or the wireless communication system may include a Universal Mobile Telecommunications System (UMTS), a Terrestrial Radio Access Network (UTRAN), a Long Term Evolution (LTE) evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MultiFire, LTE-A Pro and / or a fifth generation (5G) radio access technology, or a New Radio (NR) access technology. The 5G wireless communication system refers to a next generation (NG) radio access network and network architecture for the core network. The 5G system is often built based on 5G New Radio (NR), but it is also possible to build a 5G system based on E-UTRA radio. NR is expected to provide bitrates on the order of 10 G - 20 G bits / second or higher and support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) and massive machine type communication (mMTC). NR is expected to provide ultra-wideband and ultra-robust low-latency connectivity and large-scale networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more prevalent, there will be an increasing need for a wireless access network that meets the needs of lower power, lower data rate, and longer battery life. The next generation radio access network (NG-RAN) represents the RAN for the 5G system that can provide wireless access using both NR and LTE (and LTE-Advanced).In the NG-RAN, note that a node that can provide a radio access function to a user equipment (i.e., similar to Node B in UTRAN, NB, or evolved NB (eNB) in LTE) may be referred to as a next-generation NB (gNB) when constructed based on NR, and may be referred to as a next-generation eNB (NG-eNB) when constructed based on LTE.

SUMMARY OF THE INVENTION

MEANS FOR SOLVING THE PROBLEM

[0003] One aspect can be directed to a method that may include providing information including one or more single network slice selection assistance information (S-NSSAI) and one or more tracking area identities (TAI) to at least one user equipment registered with a network in a registration area. Each of the one or more single network slice selection assistance information (S-NSSAI) can be included in a list of rejected single network slice selection assistance information (S-NSSAI) or a list of extended rejected single network slice selection assistance information (S-NSSAI), and can be associated with a cause value indicating that the single network slice selection new information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

[0004] ​One aspect can be directed to an apparatus that can include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to cause the at least one processor to cause the apparatus to provide, to at least one user equipment registered in a network within a registration area, information including one or more single network slice selection assistance information (S-NSSAI) and one or more tracking area identifiers (TAI). Each of the one or more single network slice selection assistance information (S-NSSAI) can be included in a list of rejected single network slice selection assistance information (S-NSSAI) or a list of extended rejected single network slice selection assistance information (S-NSSAI), and can be associated with a cause value indicating that the single network slice selection new information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

[0005] One aspect can be directed to a method that can include receiving, at a user equipment registered in a network within a registration area from a network (e.g., from an access and mobility management function of a core network), information including one or more single network slice selection assistance information (S-NSSAI) and one or more tracking area identifiers (TAI). Each of the one or more single network slice selection assistance information (S-NSSAI) can be included in a list of rejected single network slice selection assistance information (S-NSSAI) or a list of extended rejected single network slice selection assistance information (S-NSSAI), and can be associated with a cause value indicating that the single network slice selection new information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

[0006] One aspect can be directed to an apparatus that can include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to cause the at least one processor to cause the apparatus to receive, at least from a network, information including one or more single network slice selection assistance information (S-NSSAI) and one or more tracking area identifiers (TAI), and the apparatus is registered with the network within a registration area. Each of the one or more single network slice selection assistance information (S-NSSAI) can be included in a list of rejected single network slice selection assistance information (S-NSSAI) or a list of extended rejected single network slice selection assistance information (S-NSSAI), and can be associated with a cause value indicating that the single network slice selection new information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

[0007] For a correct understanding of the exemplary embodiments, reference will be made to the following accompanying drawings.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4

Figure 5A

Figure 5B

Figure 6A

Figure 6B

[0009] It will be readily understood that the components of the specific exemplary embodiments outlined herein and shown in the drawings can be configured and designed in a variety of different configurations. Accordingly, the following detailed description of some exemplary embodiments of a system, method, apparatus, and computer program product for efficient registration of a partially supported service area is not intended to limit the scope of the specific embodiments, but rather represents the selected exemplary embodiments.

[0010] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more of the exemplary embodiments. For example, the use of the phrases "specific embodiment", "some embodiments", or other similar language throughout this specification refers to the fact that the specific features, structures, or characteristics described in connection with a particular embodiment may be included in at least one embodiment. Accordingly, the phrases "in a specific embodiment", "in some embodiments", "in other embodiments", or other similar language throughout this specification do not necessarily all refer to the same group of embodiments, and the features, structures, or characteristics described may be combined in any suitable manner in one or more of the exemplary embodiments.

[0011] Furthermore, if desired, the different functions or procedures discussed below may be performed in a different order and / or in parallel with each other. Also, if desired, one or more of the functions or procedures described may be optional or may be combined. Accordingly, the following description should be regarded as illustrative of the principles and teachings of certain exemplary embodiments and not as limiting thereof.

[0012] Depending on frequency band allocation and availability, it may be desirable to have an area, referred to as area X, with a Tracking Area Identity (TAI) J, which is smaller than existing tracking areas and supports a specific Single Network Slice Selection Assistance Information (S-NSSAI), referred to as S-NSSAI m. Note that a network slice may refer to a logical network that provides specific network capabilities and network characteristics, and the S-NSSAI can be used to uniquely identify a network slice.

[0013] The dimensioning of the Tracking Area (TA) is done at the time of network deployment, so the needs for network slices and service support become known at a fairly late stage. Also, the area where a particular service needs to be supported may be relatively small compared to the size of the TA (e.g., a pop-up store advertising new applications using augmented reality or virtual reality) in some use cases, and there may be uneven coverage provided by cells operating with high priority.

[0014] Figures 1 and 2 show examples of two possible deployment methods according to certain embodiments. In the examples of Figures 1 and 2, the hatched area is referred to as area X, and the non-hatched area represents an existing tracking area with TAI K; furthermore, the S-NSSAI supported in the existing tracking area may be shown as S-NSSAI n.

[0015] In the first deployment method (Deployment Method 1) shown in the example of FIG. 1, there is no overlay, that is, the cells used to cover area X support S-NSSAI m and S-NSSAI n. In the second deployment method (Deployment Method 2) shown in the example of FIG. 2, new cells (possibly with different frequency bands) are further deployed in area X, and these new cells support S-NSSAI m and S-NSSAI n.

[0016] The registration procedure enables the network to provide (i) information regarding a single area (i.e., a tracking area identifier (TAI) or a set of registration areas) and (ii) a single list of S-NSSAIs that are uniformly permitted in the area defined by (i). Thus, the permitted S-NSSAI may refer to the S-NSSAI that is valid in a particular registration area. A UE that wants to use S-NSSAI m needs to always perform the registration procedure when entering and leaving area X, which may result in frequent registration procedures. FIGS. 3A and 3B show an example of a possible trace of a UE and the registration procedures (le) required when the UE moves along path 305. FIG. 4 shows an exemplary diagram illustrating a network slice and services mapped based on frequency band allocation, together with the frequent registration area (RA) updates that occur.

[0017] As detailed below, certain embodiments can provide systems and methods for efficient registration for partially supported service areas. As a result, some embodiments can avoid the frequent registration procedures that would otherwise be required.

[0018] According to certain embodiments, when the Access and Mobility Management Function (AMF) of the network receives a registration request message from the UE (i.e., when the UE performs the registration procedure), the AMF can provide a plurality of sets including a list of Tracking Area Identifiers (TAIs) and a list of Slice / Network Slice Selection Assistance Information (S-NSSAIs), which the UE can use to determine a TAI that supports an appropriate network slice according to the type of service or slice required by the UE. For example, in one embodiment, the AMF can provide one or more of the following to the UE: (1) a registration area including a list of TAIs, (2) a permitted NSSAI including a list of S-NSSAIs supported in all Registered Areas (RAs), (3) one or more restricted registration areas (subsets of RAs) including a list of TAIs, and / or (4) a partially permitted S-NSSAI that is supported and permitted only within the corresponding restricted RA.

[0019] In some embodiments, the UE can determine the permitted S-NSSAI based on, for example, the current TAI broadcast by the NG-RAN node and the plurality of sets of {TAI list, S-NSSAI list} received from the AMF. According to one embodiment, the UE does not need to perform the registration procedure when moving between TAIs included in the registration area received from the network. In one embodiment, in a scenario as shown in the example of FIG. 2 where the UE detects the presence of two TAIs with different associated S-NSSAIs, the UE can prioritize cell (re)selection based on its preferred S-NSSAI.

[0020] According to a first alternative, the AMF can send a registration acceptance message to the UE, and the registration acceptance message can include the following information elements: registration area, permitted NSSAI, restricted registration area, and partially permitted NSSAI. Table 1 below shows how the above information elements can be populated in the registration acceptance message according to the exemplary deployment method introduced above.

[0021]

Table 1

[0022] In a particular embodiment, the UE will be considered to support a partially permitted NSSAI including S-NSSAI m when the UE is within TAI J. Also, in the above example, when the UE is in TAI K, the UE is considered to be permitted only for the S-NSSAI (i.e., S-NSSAI n in this example) within the permitted NSSAI. When the UE needs to be paged, the AMF can select a paging area based on the S-NSSAI associated with the protocol data unit (PDU) session of that UE. In this example, for the PDU session related to S-NSSAI n → paging area: TAI J, TAI K; for the PDU session related to S-NSSAI m → paging area: only TAI J. When the UE moves between TAI J and TAI K, the UE does not perform a registration area update.

[0023] According to a second alternative, the AMF sends a registration acceptance message to the UE, and the registration acceptance message includes the following information elements: the registration area, the permitted NSSAI, the rejected NSSAI with a cause code for each S-NSSAI within the rejected NSSAI indicating that the S-NSSAI is not uniformly supported in the registration area, and the TAI for which each S-NSSAI is supported. Note that the rejected NSSAI may refer to the NSSI that is rejected within its registration area (or for the entire PLMN). Therefore, the UE will not attempt to use the rejected NSSAI again when the UE is within its registration area. Table 2 below shows how the above information elements can be populated in the registration acceptance message for this alternative according to the exemplary deployment method introduced above. In this example, the UE can be considered to support S-NSSAI m when the UE is in TAI J. Without loss of generality, what is applicable to the rejected NSSAI is applicable to the extended rejected NSSAI.

[0024]

Table 2

[0025] According to the third alternative form, the AMF can include the following information elements in the registration acceptance message sent to the UE: registration area, permitted NSSAI, rejected NSSAI with a cause code indicating that the corresponding S-NSSAI is not uniformly supported in that registration area, and TAI where the S-NSSAI(s) in the S-NSSAI list is not supported. Table 3 below shows how the above information elements can be populated in this alternative form according to the exemplary deployment method introduced above. In this example, the UE is considered to support S-NSSAI m when the UE is in TAI J. Without loss of generality, what is applicable to the rejected NSSAI is applicable to the extended rejected NSSAI.

[0026]

Table 3

[0027] According to a particular embodiment, the access and mobility management function (AMF) can update the partially permitted NSSAI, or the rejected NSSAI with a cause code indicating that the S-NSSAI is not uniformly supported in the registration area. Furthermore, the area information can also be updated. The AMF can use the UE configuration update command message to update these parameters. Note that in a particular embodiment, the information element and / or the cause code are provided to the UE based on the UE signaling its support of such information in the registration request message.

[0028] FIG. 5A shows an exemplary flowchart of a method for beam obstruction detection and / or beam obstruction recovery according to an exemplary embodiment. In a particular exemplary embodiment, the flowchart of FIG. 5A may be performed by a network entity or network node in a communication system such as LTE or 5G NR. In some exemplary embodiments, the network entity performing the method of FIG. 5A may include or may be included in a base station, access node, Node B, eNB, gNB, NG-RAN node, transmission-reception point (TRP), high altitude platform station (HAPS), relay station, etc. In one embodiment, the network node performing the method of FIG. 5A may include an access management node such as an AMF or a similar radio node.

[0029] As shown in the example of FIG. 5A, in one embodiment, the method can include, at 500, receiving a registration request message from one or more UEs registered with a network within a registration area. In one embodiment, the method can include, at 510, providing information to the UE that includes one or more lists of TAI and one or more lists of S-NSSAI. For example, providing at 510 may include transmitting this information to the UE in a registration acceptance message. Additionally, or alternatively, providing at 510 may include transmitting this information to the one or more UEs in a UE configuration update command message. In one embodiment, one or more S-NSSAIs can indicate S-NSSAIs that are not uniformly supported in the registration area, and one or more lists of TAI may be associated with the one or more S-NSSAIs. According to one embodiment, each of the one or more S-NSSAIs may be included in a list of rejected S-NSSAIs or a list of extended rejected S-NSSAIs, and may be associated with a cause value indicating that the one or more S-NSSAIs are not uniformly supported in the registration area and / or are not supported in the current tracking area. In one embodiment, each of the one or more lists of TAI can identify an area where each of the one or more S-NSSAIs is not supported. According to a particular embodiment, providing at 510 can include providing information and / or a cause value to the UE when the UE signals support for such information in a registration request message.

[0030] According to one embodiment, one or more S-NSSAIs may be included in an information element that identifies S-NSSAIs that are permitted for the UE but are not uniformly supported within the registration area. In one embodiment, each of the one or more lists of TAI can identify an area where each of the one or more S-NSSAIs is supported.

[0031] According to certain embodiments, the information provided at 510 can include at least a registered area including a list of TAI, a permitted NSSAI including a list of S-NSSAI supported in the registered area, one or more restricted registered areas including a list of TAI of the restricted registered area, and / or a partially permitted S-NSSAI permitted in the corresponding restricted registered area. Additionally, or alternatively, in some embodiments, the information provided to the UE at 510 can further include a cause-value-attached rejected NSSAI for each S-NSSAI in a rejected NSSAI indicating that the S-NSSAI is not uniformly supported in the registered area, and the TAI for which each S-NSSAI is supported. Additionally, or alternatively, in certain embodiments, the information provided to the UE at 510 can further include a cause-value-attached rejected NSSA indicating that the corresponding S-NSSAI is not uniformly supported in the registered area and / or is not supported in the current tracking area, and the TAI for which the S-NSSAI in the list of S-NSSAI is not supported.

[0032] According to one embodiment, if a UE needs to be paged, the method can include selecting a paging area based on the S-NSSAI associated with the PDU session of the UE.

[0033] FIG. 5B shows an exemplary flowchart of a method for beam obstruction detection and / or beam obstruction recovery according to one embodiment. In a particular exemplary embodiment, the flowchart of FIG. 5B can be performed by a network entity or network node in a communication system such as LTE or 5G NR. In some embodiments, the network entity performing the method of FIG. 5B can include or be included in a UE (e.g., a multi-panel UE), a communication node, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other devices. According to one embodiment, the UE executing the method of FIG. 5B can be a UE registered to a network within a registered area.

[0034] As shown in the example of FIG. 5B, in one embodiment, the method can include, at 550, sending a registration request message to a network node such as a gNB or an AMF. In one embodiment, the method can include, at 560, receiving information including one or more lists of TAI and one or more lists of S-NSSAI that can be used by the UE to determine a TAI that supports an appropriate network slice according to the type of service the UE requires. According to one embodiment, one or more S-NSSAIs indicate S-NSSAIs that are not uniformly supported in the registration area, and one or more lists of TAI are associated with one or more S-NSSAIs. For example, receiving at 560 may include receiving information in a registration acceptance message from the AMF. In one embodiment, receiving at 560 may include receiving information in a UE configuration update command message from the AMF. According to some embodiments, receiving at 560 can include receiving information and / or a cause value when the UE signals support for such information of the UE in a registration request message.

[0035] In one embodiment, one or more S-NSSAIs can indicate S-NSSAIs that are not uniformly supported in the registration area, and one or more lists of TAI may be associated with one or more S-NSSAIs. According to one embodiment, each of the one or more S-NSSAIs may be included in a list of rejected S-NSSAIs or a list of extended rejected S-NSSAIs, and may be associated with a cause value indicating that one or more S-NSSAIs are not uniformly supported in the registration area and / or are not supported in the current tracking area. In one embodiment, each of the one or more lists of TAI can identify an area where each of the one or more S-NSSAIs is not supported.

[0036] According to one embodiment, one or more S-NSSAIs may be included in an information element that identifies S-NSSAIs that are permitted for the UE but not uniformly supported in the registration area. In one embodiment, each of one or more lists of TAI can identify an area in which each of one or more S-NSSAIs is supported.

[0037] According to certain embodiments, the received information can include at least a registration area including a list of TAI, a permitted NSSAI including a list of S-NSSAIs supported in the registration area, one or more restricted registration areas including a list of TAI of the restricted registration area, and / or a partially permitted S-NSSAI permitted in the corresponding restricted registration area. Additionally, or alternatively, in some embodiments, the received information can further include a cause value - attached rejection NSSAI for each S-NSSAI in a rejection NSSAI indicating that the S-NSSAI is not uniformly supported in the registration area, and the TAI in which each S-NSSAI is supported. Additionally, or alternatively, in certain embodiments, the received information can further include a cause value - attached rejection NSSAI indicating that the corresponding S-NSSAI is not uniformly supported in the registration area and / or not supported in the current tracking area, and the TAI in which the S-NSSAI in the list of S-NSSAIs is not supported.

[0038] According to some embodiments, the method can include, at 570, determining a permitted S-NSSAI for the UE based on the current TAI broadcast by a radio access network node (e.g., an NG-RAN node) and one or more lists of TAI and one or more S-NSSAIs.

[0039] According to one embodiment, the method can further include, at 580, the UE detecting or determining whether it is within a tracking area (TA) of a registration area that supports at least one single network slice selection assistance information (S-NSSAI) that is not part of the permitted network slice selection assistance information (NSSAI) and for which the UE needs to request at least one S-NSSAI. The method can then include, at 585, the UE starting the registration procedure, for example by sending a registration request message, when the UE detects that it is in an area where at least one of the one or more S-NSSAIs not uniformly supported in the registration area is supported. The registration message can include one of the one or more S-NSSAIs that is not uniformly supported in the registration area but is supported in the current area.

[0040] In one embodiment, the method can include the UE skipping the registration procedure when moving between tracking area identifiers (TAIs) included in the registration area received from the access and mobility management function (AMF).

[0041] According to some embodiments, the method can include the UE, when detecting that it is in an area where at least one of the one or more S-NSSAIs not uniformly supported in the registration area is supported, considering or determining that at least one of the one or more S-NSSAIs not uniformly supported in the registration area is permitted.

[0042] FIG. 6A shows an example of an apparatus 10 according to one embodiment. In one embodiment, the apparatus 10 may be a node, host, or server that is in or serves such a communication network. For example, the apparatus 10 may be a network node, a sensing node, a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), a TRP, a HAPS, an integrated access and backhaul (IAB) node, and / or a WLAN access point associated with a radio access network such as an LTE, 5G, or NR radio access network. In some exemplary embodiments, the apparatus 10 may be, for example, an access and mobility management node or other similar network node. In some exemplary embodiments, the apparatus 10 may implement network functions such as the above-described AMF. In some exemplary embodiments, the apparatus 10 may implement multiple network functions of a core network, including the above-described AMF, a policy control function, and a session management function.

[0043] It should be understood that in some exemplary embodiments, the apparatus 10 may consist of an edge cloud server (or distributed computing system) and a radio node, where the edge cloud server and the radio node can communicate with each other via a wireless path or a wired connection. For example, in a particular exemplary embodiment where the apparatus 10 represents a gNB, the apparatus may be configured as a central unit (CU) and one or more distributed units (DUs) that split the gNB function. In one such exemplary embodiment, the CU may be a logical node that includes gNB functions such as user data transfer, mobility control, radio access network sharing, positioning, and / or session management. The CU may control the operation of the DU on a fronthaul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the function split option. It should be noted that those skilled in the art will understand that the apparatus 10 may include components or mechanisms not shown in FIG. 6A.

[0044] As shown in the example of FIG. 6A, the apparatus 10 can include a processor 12 for processing information and executing instructions or operations. The processor 12 can be any type of general-purpose or dedicated processor. In fact, the processor 12 can include, by way of example, a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture, or one or more of any other processing means. Although a single processor 12 is shown in FIG. 6A, according to other embodiments, multiple processors may be used. For example, in certain embodiments, the apparatus 10 may include two or more processors that can form a multi-processor system capable of supporting multi-processing (for example, in this case, the processor 12 may represent a multi-processor). It should be understood that in certain embodiments, the multi-processor system can be tightly or loosely coupled (such as to form a computer cluster).

[0045] The processor 12 can execute functions related to the operation of the apparatus 10, which can include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10 including processes related to the management of communication or communication resources.

[0046] Device 10 may include or be coupled to (internally or externally) a memory 14 that can be coupled to processor 12 for storing information and instructions executable by processor 12. Memory 14 may be one or more memories and can be any suitable for a local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 14 can consist of random access memory (RAM), read-only memory (ROM), static storage such as magnetic or optical disks, hard disk drive (HDD), or any other type of non-transitory, machine or computer-readable medium, or any combination of other suitable storage means. The instructions stored in memory 14 can include program instructions or computer program code that, when executed by processor 12, enable device 10 to perform the tasks described herein.

[0047] In one embodiment, device 10 may further include or be coupled to (internally or externally) a drive or port configured to receive and read an external computer-readable storage medium, such as an optical disk, USB drive, flash drive, or any other storage medium. For example, the external computer-readable storage medium can store a computer program or software for execution by processor 12 and / or device 10.

[0048] In some embodiments, the apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and / or receiving signals and / or data to / from the apparatus 10. The apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of wireless interfaces that can be coupled to the antenna 15, or may include any other suitable transmitting and receiving means. The wireless interfaces may be compatible with one or more of a plurality of wireless access technologies, including GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identification (RFID), ultra-wideband (UWB), MulteFire, etc. The wireless interface may include components such as filters, converters (such as digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via an uplink).

[0049] Accordingly, the transceiver 18 can be configured to modulate information into a carrier waveform for transmission by the antenna 15 and demodulate the information received via the antenna 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally, or alternatively, in some embodiments, the apparatus 10 may include input and / or output devices (I / O devices) or input / output means.

[0050] In one embodiment, the memory 14 can store software modules that, when executed by the processor 12, provide functions. The modules can include, for example, an operating system that provides operating system functions to the device 10. The memory can also store one or more functional modules such as applications or programs to provide additional functions to the device 10. The components of the device 10 can be implemented in hardware, or any suitable combination of hardware and software.

[0051] According to some embodiments, the processor 12 and the memory 14 may be included in or form part of a processing circuit / means or a control circuit / means. Further, in some embodiments, the transceiver 18 may be included in or form part of a transceiver circuit / means.

[0052] As used herein, the term "circuit" refers to a circuit implementation of only hardware (e.g., analog and / or digital circuits), a combination of a hardware circuit and software that together function to cause a device (e.g., device 10) to perform various functions, a combination of analog and / or digital hardware circuits with software / firmware, any portion of a hardware processor with software (including a digital signal processor), and / or a hardware circuit and / or processor, or a portion thereof, that uses software for operation but may not have software present if the software is not necessary for operation. As a further example, the term "circuit" as used herein can cover a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, and its attendant software and / or firmware implementation. The term "circuit" can cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing device or network device.

[0053] As introduced above, in certain embodiments, the apparatus 10 may be a network element or a RAN node such as a base station, an access point, a Node B, an eNB, a gNB, a TRP, a HAPS, an IAB node, a WLAN access point, etc. In one exemplary embodiment, the apparatus 10 may be a gNB, an AMF or other radio node. According to certain embodiments, the apparatus 10 can be controlled by the memory 14 and the processor 12 to perform functions associated with any of the embodiments described herein. For example, in some embodiments, the apparatus 10 can be configured to perform one or more of the processes shown in any of the flowcharts or signaling diagrams described herein, such as those shown in FIG. 5A or FIG. 5B, or any other method described herein. In some embodiments, as described herein, the apparatus 10 can be configured to perform procedures related to efficient registration for, for example, a partially supported service area.

[0054] FIG. 6B shows an example of an apparatus 20 according to another embodiment. In one embodiment, the apparatus 20 may be a node or element in a communication network or associated with such a network, such as a UE, a communication node, a mobile device (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. Alternatively, as described herein, a UE may be referred to, for example, as a mobile station, a mobile device, a mobile unit, a mobile device, a user device, a subscriber station, a wireless terminal, a tablet, a smartphone, an IoT device, a sensor or NB-IoT device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and its applications (e.g., remote surgery), an industrial device and its applications (e.g., robots and / or other wireless devices operating in the context of a production and / or automated processing chain), a home electronic device, a device operating in a commercial and / or industrial wireless network, etc. As an example, the apparatus 20 may be implemented, for example, in a wireless handheld device, a wireless plug-in accessory, etc.

[0055] In some exemplary embodiments, the apparatus 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more wireless access components (e.g., a modem, a transceiver, etc.), and / or a user interface. In some embodiments, the apparatus 20 may be configured to operate using one or more wireless access technologies such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other wireless access technology. It should be noted that those skilled in the art will appreciate that the apparatus 20 can include components or features not shown in FIG. 6B.

[0056] As shown in the example of FIG. 6B, the apparatus 20 can include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 can be any type of general-purpose or dedicated processor. In fact, the processor 22 can include, by way of example, one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although a single processor 22 is shown in FIG. 6B, according to other embodiments, multiple processors may be used. For example, in certain embodiments, the apparatus 20 may include two or more processors that can form a multi-processor system capable of supporting multi-processing (for example, in this case, the processor 22 may represent a multi-processor). It should be understood that in certain embodiments, the multi-processor system can be tightly or loosely coupled (such as to form a computer cluster).

[0057] As some examples, the processor 22 can perform functions related to the operation of the apparatus 20, including overall control of the apparatus 20, which includes processes related to pre-coding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and management of communication resources.

[0058] Device 20 may include or be coupled to (internally or externally) a memory 24 that can be coupled to processor 22 for storing information and instructions executable by processor 22. Memory 24 may be one or more memories and can be of any type suitable for a local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 24 can consist of a random access memory (RAM), a read-only memory (ROM), static storage such as a magnetic or optical disk, a hard disk drive (HDD), or any other combination of any other type of non-transitory machine or computer-readable medium. The instructions stored in memory 24 can include program instructions or computer program code that, when executed by processor 22, enable device 20 to perform the tasks described herein.

[0059] In one embodiment, device 20 may further include or be coupled to (internally or externally) a drive or port configured to receive and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium can store a computer program or software for execution by processor 22 and / or device 20.

[0060] In some embodiments, the apparatus 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting via the uplink from the apparatus 20. The apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a wireless interface (such as a modem) coupled to the antenna 25. The wireless interface may be capable of supporting multiple radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The wireless interface may include other components such as filters, converters (such as digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc. for processing symbols such as OFDMA symbols carried by the downlink or uplink.

[0061] For example, the transceiver 28 can be configured to modulate information into a carrier waveform for transmission by the antenna 25 and demodulate the information received via the antenna 25 for further processing by other elements of the apparatus 20. In other embodiments, the transceiver 28 may be capable of directly transmitting and receiving signals or data. Additionally, or alternatively, in some embodiments, the apparatus 20 may include an input and / or output device (I / O device). In certain embodiments, the apparatus 20 may further include a user interface such as a graphical user interface or a touch screen.

[0062] In one embodiment, memory 24 stores software modules that, when executed by processor 22, provide functions. The modules may include, for example, an operating system that provides operating system functions to device 20. The memory can also store one or more functional modules such as applications or programs to provide additional functions to device 20. The components of device 20 can be implemented in hardware, or any suitable combination of hardware and software. According to an exemplary embodiment, device 20 can optionally be configured to communicate with device 10 via a wireless or wired communication link 70 in accordance with any wireless technology such as NR.

[0063] According to some embodiments, processor 22 and memory 24 may be included in or form part of a processing circuit or a control circuit. Further, in some embodiments, transceiver 28 may be included in or form part of a transmitting and receiving circuit.

[0064] As described above, according to some embodiments, device 20 may be, for example, a UE, a SL UE, a relay UE, a mobile device, a mobile station, an ME, an IoT device, and / or an NB-IoT device. According to a particular embodiment, device 20 can be controlled by memory 24 and processor 22 to perform functions associated with any of the embodiments described herein, such as one or more of the operations shown or described in relation to FIGS. 5A or 5B, or any other method described herein. For example, in one embodiment, device 20 can be controlled to perform a process related to efficient registration for a partially supported service area as detailed elsewhere in this document.

[0065] In some embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) can include means for performing any of the methods, processes, or variations described herein. Examples of means can include one or more processors, memories, controllers, transmitters, receivers, displays, and / or computer program code for causing any of the operations described herein to be performed.

[0066] In light of the above, certain exemplary embodiments provide several technical improvements, enhancements, and / or advantages over existing technical processes, and constitute improvements at least in the technical field of wireless network control and / or management. For example, as detailed above, certain exemplary embodiments can provide methods and / or apparatuses for efficient registration for a partially supported service area. As a result of certain embodiments, a UE can be informed of available network slices without performing a registration update procedure, can request establishment of a PDU session, or can initiate a scheduling request (SR) for a particular slice. Also, the exemplary embodiments can enable reduction of control plane (C-plane) traffic, thereby reducing the possibility of procedure collisions in the gNB / AMF, such as the possibility of RU and paging collisions that can cause disappearance of paging messages. Thus, as a result of the use of certain exemplary embodiments, the functions of communication networks and network nodes such as base stations, eNBs, gNBs, and / or IoT devices, UEs or mobile stations are improved.

[0067] In some exemplary embodiments, any of the functions of the methods, processes, signaling diagrams, algorithms, or flowcharts described herein can be implemented by software and / or computer program code or a portion of the code stored in a memory or other computer-readable or tangible medium and executable by a processor.

[0068] In some exemplary embodiments, the apparatus can include or be associated with at least one software application, module, unit, or entity configured as an arithmetic operation or a program or part of a program (including an added or updated software routine) executable by at least one arithmetic processor or controller. A program, also referred to as a program product or computer program, including software routines, applets, and macros, can be stored on any device-readable data storage medium and can include program instructions for performing a particular task. The computer program product can include one or more computer-executable components configured to implement some exemplary embodiments when the program is executed. The one or more computer-executable components can be at least one software code or part of the code. The routines necessary for implementing the functions of an exemplary embodiment can be performed as routines that can be implemented as added or updated software routines. In one example, the software routine is downloadable to the apparatus.

[0069] As an example, the software or computer program code or part of the code can be in source code form, object code form, or some intermediate form, and can be stored on any kind of carrier, distribution medium, or computer-readable medium, which can be any entity or device capable of carrying the program. Such carriers can include, for example, recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, electrical communication signals, and / or software distribution packages. Depending on the required processing power, the computer program can be executed on a single electronic digital computer or distributed among several computers. The computer-readable medium or computer-readable storage medium can be a non-transitory medium.

[0070] In other exemplary embodiments, the functions of the exemplary embodiments may be performed by hardware or circuitry included in a device, such as, for example, an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another exemplary embodiment, the functions of the exemplary embodiments may be implemented as a signal, such as a non-tangible medium that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0071] According to one exemplary embodiment, a device, such as a node, device, or corresponding component, can be configured as a single-chip computer element, such as a circuit, computer, or microprocessor, or as a chipset, that includes at least a memory for providing storage capacity used in arithmetic operations and / or an arithmetic processor for performing arithmetic operations.

[0072] The exemplary embodiments described herein are applicable to both single and multiple implementations, regardless of whether singular or plural language is used in the description of a particular embodiment. For example, an embodiment that describes the operation of a single network node is also applicable to an embodiment that includes multiple instances of network nodes, and vice versa.

[0073] Those skilled in the art will readily appreciate that the exemplary embodiments as described above may be implemented in different orders of steps and / or with hardware elements of a different configuration than those disclosed. Accordingly, while some embodiments have been described based on these exemplary embodiments, those skilled in the art will recognize that certain modifications, variations, and alternative structures will be apparent while remaining within the spirit and scope of the exemplary embodiments.

Claims

1. receiving, in an Access and Mobility Management Function (AMF) of a network, a registration request message from a user equipment (UE), wherein the user equipment is within a current tracking area of ​​a registration area (RA) that includes a plurality of tracking areas (TAs); In an AMF of the network, sending a response to the registration request message to the user equipment, the response including Single Network Slice Selection Assistance Information (S-NSSAI), one or more of the S-NSSAIs included in an information element identifying S-NSSAIs that are authorized for the UE but are not uniformly supported in the registration area, and including one or more lists of Tracking Area Identifiers (TAIs) identifying areas in which each of the one or more uniformly unsupported S-NSSAIs is supported; A method comprising:

2. 2. The method of claim 1, wherein the response includes one or more of: a registration area (RA) including a list of TAIs; an allowed NSSAI including a list of S-NSSAIs supported in all RAs; one or more restricted registration areas including a list of TAIs that are a subset of the RA; and / or partially allowed S-NSSAIs that are supported and allowed only within the corresponding restricted RAs.

3. 2. The method of claim 1, wherein the response includes one or more TAIs of tracking areas in which the one or more uniformly unsupported S-NSSAIs are not supported among the plurality of tracking areas, and includes a TAI of the current tracking area.

4. 2. The method of claim 1, further comprising: receiving, from a user equipment (UE), a second registration request message including at least one S-NSSAI when, after sending the response to the registration request message to the UE, the UE detects that the UE has moved to a new tracking area of ​​the registration area, and at least one of the one or more S-NSSAIs that is not supported in the user equipment's current tracking area is supported in the new tracking area, and the user equipment needs to request the at least one S-NSSAI.

5. sending, by a user equipment (UE), a registration request message to a network for registering with the network, the user equipment being within a current tracking area (TA) of a registration area (RA) including a plurality of tracking areas; receiving, by the user equipment, from the network a response to the registration request message, the response including Single Network Slice Selection Assistance Information (S-NSSAIs), one or more of the S-NSSAIs included in an information element identifying S-NSSAIs that are authorized for the UE but are not uniformly supported in the registration area, and the response including one or more lists of Tracking Area Identifiers (TAIs), each of the one or more lists of TAIs identifying an area in which each of the one or more uniformly unsupported S-NSSAIs is supported; Initiating a registration procedure by the user equipment by sending a second registration request message including the at least one S-NSSAI when the UE detects that the UE has moved to another tracking area of ​​the registration area, and at least one of the one or more S-NSSAIs that is not supported in the current tracking area of ​​the user equipment is supported in the other tracking area, and the UE needs to request the at least one S-NSSAI; A method comprising:

6. 6. The method of claim 5, further comprising: determining, by the UE, an S-NSSAI that is authorized for the UE based on a current TAI broadcast by a network and one or more lists of the TAIs and the one or more S-NSSAIs.

7. 6. The method of claim 5, wherein the response includes one or more S-NSSAIs included in a list of rejected S-NSSAIs and one or more lists of TAIs of tracking areas in which each of the rejected S-NSSAIs is not supported.

8. The method of claim 5 , wherein the registration request message is sent to an Access and Mobility Management Function (AMF) of the network.

9. at least one processor; at least one memory containing computer program code; wherein the at least one memory and the computer program code, together with the at least one processor, cause the device to include at least: receiving, in an Access and Mobility Management Function (AMF) of a network, a registration request message from a user equipment, wherein the user equipment is within a current tracking area (TA) of a registration area (RA) including a plurality of tracking areas; In the AMF, sending a response to the registration request message to the user equipment, the response including Single Network Slice Selection Assistance Information (S-NSSAI), one or more of the S-NSSAIs included in an information element identifying S-NSSAIs that are allowed for the user equipment but are not uniformly supported in the registration area, and including one or more lists of Tracking Area Identifiers (TAIs) identifying areas in which each of the one or more uniformly unsupported S-NSSAIs is supported; An apparatus configured to cause

10. 10. The apparatus of claim 9, wherein the response includes one or more of: a registration area (RA) including a list of TAIs; an allowed NSSAI including a list of S-NSSAIs supported in all RAs; one or more restricted registration areas including a list of TAIs that are a subset of the RA; and / or partially allowed S-NSSAIs that are supported and allowed only within the corresponding restricted RA.

11. 10. The apparatus of claim 9, wherein the response includes one or more TAIs of tracking areas in which the one or more uniformly unsupported S-NSSAIs are not supported among the plurality of tracking areas, and includes a TAI of the current tracking area.

12. The at least one memory and the computer program code, together with the at least one processor, provide the device with at least: receiving, from the user equipment (UE), after sending the response to the registration request message, a second registration request message including at least one S-NSSAI when the UE detects that the UE has moved to a new tracking area of ​​the registration area, and at least one of the one or more S-NSSAIs that is not supported in the current tracking area of ​​the user equipment is supported in the new tracking area, and the user equipment needs to request the at least one S-NSSAI; 10. The apparatus of claim 9, configured to cause:

13. A user equipment (UE), at least one processor; and at least one memory containing computer program code, wherein the at least one memory and the computer program code, together with the at least one processor, cause the UE to: sending a registration request message to a network to register with the network, the user equipment being within a current tracking area (TA) of a registration area (RA) that includes a plurality of tracking areas; receiving from the network a response to the registration request message, the response including Single Network Slice Selection Assistance Information (S-NSSAI), one or more of the S-NSSAIs included in an information element identifying S-NSSAIs that are authorized for the UE but are not uniformly supported in the registration area, and the response including one or more lists of Tracking Area Identifiers (TAIs), each of the one or more lists of TAIs identifying an area in which each of the one or more uniformly unsupported S-NSSAIs is supported; When the UE detects that the UE has moved to another tracking area of ​​the registration area, and at least one of the one or more S-NSSAIs that is not supported in the current tracking area of ​​the user equipment is supported in the other tracking area and the at least one S-NSSAI needs to be requested, initiating a registration procedure by sending a second registration request message including the at least one S-NSSAI; The UE is configured to cause

Images