Method and apparatus for communication

Abstract

Systems, methods, apparatus, and computer program products for efficient registration for partially supported service areas are provided. A method may include providing information including one or more single network slice selection assistance information (S‑NSSAI) and one or more tracking area identifiers (TAIs) to at least one user equipment registered to a network in a registration area. Each of the one or more single network slice selection assistance information (S‑NSSAI) is included in a rejected single network slice selection assistance information (S‑NSSAI) list, or an extended rejected single network slice selection assistance information (S‑NSSAI) list, and is associated with a cause value indicating that the single network slice selection assistance information (S‑NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

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) wireless access technology, or other mobile or wireless communication system telecommunication systems. For example, certain example aspects may generally relate to systems and / or methods for efficient registration in areas where services are partially supported. Background Art

[0002] A mobile or 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), MulteFire, LTE-A Pro and / or a fifth generation (5G) radio access technology or a new radio (NR) access technology. A 5G wireless telecommunication system refers to a next generation (NG) radio access network and a network architecture for a core network. A 5G system is primarily built on 5G New Radio (NR), but a 5G system may also be built on E-UTRA radio. It is estimated that NR provides bit rates of 10-20Gbit / s or more and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC) service categories. NR is expected to provide extremely broadband, ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). As the Internet of Things and machine-to-machine (M2M) communications become more prevalent, there will be an increasing demand for wireless access networks that meet the requirements of low power consumption, low data rates, and long battery life. The Next Generation Radio Access Network (NG-RAN) refers to the RAN of a 5G system, which can provide radio access using both NR and LTE (and LTE-Advanced). It is worth noting that in NG-RAN, the nodes that can provide wireless access functions for user equipment (i.e., similar to Node B, NB in ​​UTRAN or evolved NB, eNB in ​​LTE) can be named as the next generation NB (gNB) when built on NR, and can be named as the next generation eNB (NG-eNB) when built on LTE. Summary of the invention

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

[0004] In one aspect, it may be directed to an apparatus, which may 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, together with the at least one processor, cause the apparatus to at least: provide information to at least one user equipment registered to a network in a registration area, the information including one or more single network slice selection assistance information (S-NSSAI), and one or more tracking area identifiers (TAIs), wherein each of the one or more single network slice selection assistance information (S-NSSAI) is included in a rejected single network slice selection assistance information (S-NSSAI) list or an extended rejected single network slice selection assistance information (S-NSSAI) list, and is associated with a cause value, the cause value indicating that the single network slice selection assistance information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area.

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

[0006] In one aspect, it may be directed to an apparatus, which may 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, together with the at least one processor, cause the apparatus to at least: receive information including one or more single network slice selection assistance information (S-NSSAI) and one or more tracking area identifiers (TAI) from a network, wherein the apparatus is registered to the network within a registration area. Each of the one or more single network slice selection assistance information (S-NSSAI) is included in a rejected single network slice selection assistance information (S-NSSAI) list or an extended rejected single network slice selection assistance information (S-NSSAI) list, and is associated with a cause value, the cause value indicating that the single network slice selection assistance information (S-NSSAI) is not uniformly supported in the registration area and is not supported in the current tracking area. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings, in which:

[0008] Figure 1 An example deployment method according to one embodiment is shown;

[0009] Figure 2 Another example deployment method according to one embodiment is shown;

[0010] Figure 3A shows an example of possible trajectories of a UE as it moves along a path and the required registration procedures according to one embodiment;

[0011] Figure 3B Another example of possible trajectories of a UE as it moves along a path and the required registration procedures according to one embodiment is shown;

[0012] Figure 4 An example diagram depicting network slicing and service mapping based on frequency band allocation according to one embodiment is shown;

[0013] Figure 5A An example flow chart of a method according to one embodiment is shown;

[0014] Figure 5B An example flow chart of a method according to one embodiment is shown;

[0015] Fig. 6A An example block diagram of an apparatus according to one embodiment is shown; and

[0016] Figure 6B An example block diagram of an apparatus according to an embodiment is shown. DETAILED DESCRIPTION

[0017] It is readily understood that the components of certain example embodiments generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for efficient registration of partially supported service areas is not intended to limit the scope of certain embodiments, but rather represents selected example embodiments.

[0018] The features, structures or characteristics of the example embodiments described in this specification may be combined in any suitable manner in one or more example embodiments. For example, the phrases "certain embodiments", "some embodiments" or other similar language used in this specification refer to specific features, structures or characteristics associated with an embodiment that may be included in at least one embodiment. Therefore, the phrases "certain embodiments", "in some embodiments", "in other embodiments" or other similar language appearing in this specification do not necessarily refer to the same set of embodiments, and the features, structures or characteristics of the described example embodiments may be combined in any suitable manner in one or more example embodiments.

[0019] Furthermore, if desired, the different functions or procedures discussed below may be performed in a different order and / or simultaneously. Furthermore, if desired, one or more of the functions or procedures described may be optional or combined. Therefore, the following description should be viewed as an illustration of the principles and teachings of certain example embodiments, rather than as a limitation thereof.

[0020] Depending on frequency band allocation and availability, an area, which may be referred to as area X (with tracking area identifier J), may be required that is smaller than the existing tracking area and supports a specific single network slice selection assistance information (S-NSSAI) that may be referred to as S-NSSAI m. It should be noted that a network slice may refer to a logical network that provides specific network functions and network characteristics, and S-NSSAI may be used to uniquely identify a network slice.

[0021] Since the size of the Tracking Area (TA) is determined at network deployment time, the need for network slicing and service support is known at a much later time. In addition, in some use cases, the area where a particular service needs to be supported (e.g., a pop-up store promoting a new application using augmented or virtual reality) may be small relative to the size of the TA, and coverage provided by cells operating at a high priority may be sporadic.

[0022] Figure 1 and Figure 2 Examples of two possible deployment methods according to certain embodiments are shown. Figure 1 and Figure 2In the example of , the cross-hatched area is referred to as area X, and the area without cross-hatching represents the existing tracking area of ​​TAI K; in addition, the S-NSSAI supported in the existing tracking area can be expressed as S-NSSAI n.

[0023] exist Figure 1 In the first deployment method (deployment method 1) described in the example of , there is no coverage, that is, the cells for coverage area X support S-NSSAI m and S-NSSAI n. Figure 2 In the second deployment method (deployment method 2) described in the example, new cells (possibly with different frequency bands) may be additionally deployed in area X, and these new cells support S-NSSAI m and S-NSSAI n.

[0024] The registration procedure allows the network to provide: (i) information about a single area (i.e., a set of Tracking Area Identifiers (TAIs) or registration areas), and (ii) a single list of uniformly allowed S-NSSAIs in the areas defined by (i). Thus, an allowed S-NSSAI may refer to an S-NSSAI that is valid within a particular registration area. A UE that wants to use S-NSSAI m needs to perform a registration procedure when entering and leaving area X, which may result in frequent registration procedures. Figure 3A and 3B The possible trajectories of the UE as it moves along path 305 and the required registration procedures (√) are shown. Figure 4 An example diagram is shown describing network slicing and service mapping based on frequency band allocation with frequent Registration Area (RA) updates.

[0025] As will be discussed in detail below, some embodiments may provide a system and method for efficient registration of regions that partially support services. Thus, some embodiments may avoid frequent registration procedures that may be required.

[0026] According to certain embodiments, when an access and mobility management function (AMF) of a network receives a registration request message from a UE (i.e., when the UE performs a registration procedure), the AMF may provide a plurality of groups including a TAI list and an S-NSSAI list, which the UE may 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 may provide the UE with one or more of the following: (1) a registration area consisting of (multiple) TAI lists, (2) an allowed NSSAI consisting of (multiple) S-NSSAI lists supported in a complete RA, (3) one or more restricted registration areas consisting of (multiple) TAI lists (subsets of RAs), and / or (4) a portion of the allowed S-NSSAI that is only supported and allowed in the corresponding restricted RA.

[0027] In some embodiments, the UE may determine the S-NSSAI allowed by the UE based on the current TAI (e.g., TAI broadcasted by the NG-RAN node) and based on multiple groups {TAI list, S-NSSAI list} received from the AMF. According to one embodiment, when moving between TAIs included in the registration area received from the network, the UE does not need to perform the registration procedure. In one embodiment, for example, Figure 2 In the scenario described in the example, the UE detects the existence of two TAIs with different associated S-NSSAIs. The UE may prioritize cell (re)selection based on its preferred S-NSSAI.

[0028] According to the first alternative, the AMF may send a registration accept message to the UE in a registration accept message, and the registration accept message may include the following information elements: registration area, allowed NSSAI, restricted registration area, and partially allowed NSSAI. Table 1 below describes how to fill in the above information elements in the registration accept message according to the example deployment method described above.

[0029] Table 1

[0030] Deployment Method 1 Deployment Method 2 Registration Area TAI J,TAI K TAI J,TAI K Permitted NSSAI S-NSSA S-NSSA Restricted registration area TAI J TAI J Partially allowed NSSAI S-NSSAI m S-NSSAI m

[0031] In certain embodiments, when the UE is in TAI J, the UE will consider some of the allowed NSSAIs (including S-NSSAI m) to be supported. In addition, in the above example, when the UE is in TAI K, the UE only considers the S-NSSAI among the allowed NSSAIs (i.e., S-NSSAI n in this example) to be allowed. 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 for the UE. In this example, PDU session associated with S-NSSAI n → paging area: TAI J, TAI K; and PDU session associated with S-NSSAI m → paging area: TAI J only. When the UE moves between TAI J and TAI K, the UE does not perform a registration area update.

[0032] According to the second alternative, the AMF may transmit a registration accept message to the UE in a registration accept message, and the registration accept message may include the following information elements: registration area, allowed NSSAI, rejected NSSAI, in which each S-NSSAI has a reason code indicating that the S-NSSAI is not uniformly supported in the registration area, and (multiple) TAIs supporting each S-NSSAI. It should be noted that the rejected NSSAI may refer to an NSSAI that is rejected in the registration area (or the entire PLMN). Therefore, when the UE is in the registration area, it may not be attempted to use the rejected NSSAI again. Table 2 below describes how to fill in the information elements of this alternative mentioned above in the registration accept message according to the example deployment method introduced above. In this example, when the UE is in TAI J, the UE may consider that S-NSSAI m is supported. Without loss of generality, the content that can be applied to the rejected NSSAI can also be applied to the extended rejected NSSAI.

[0033] Table 2

[0034]

[0035] According to the third alternative, the AMF may include the following information elements in the registration accept message transmitted to the UE: registration area, allowed NSSAI, rejected NSSAI with a reason code indicating that the corresponding S-NSSAI is not uniformly supported in the registration area, and the S-NSSAI (each) in the S-NSSAI list is not supported TAI. Table 3 below describes how to fill in the above information elements of this alternative according to the example deployment method introduced above. In this example, when the UE is in TAI J, the UE will consider S-NSSAI m to be supported. Without loss of generality, what can be applied to rejected NSSAI can also be applied to extended rejected NSSAI.

[0036] Table 3

[0037]

[0038] According to certain embodiments, the access and mobility management function (AMF) may update a partially allowed NSSAI or a rejected NSSAI using a reason code indicating that the S-NSSAI is not uniformly supported in the registration area. In addition, the area information may be updated. The AMF may update these parameters using a UE configuration update command message. It should be noted that in certain embodiments, (multiple) information elements and / or reason codes are provided to the UE based on the UE's support signaling for such information in the registration request message.

[0039] Figure 5AAn example flow chart of a beam failure detection and / or beam failure recovery method according to an example embodiment is shown. In some example embodiments, Figure 5A The flowchart may be executed by a network entity or a network node in a communication system (e.g., LTE or 5G NR). In some example embodiments, the execution Figure 5A The network entity of the method may include or be included in a base station, an access node, a Node B, an eNB, a gNB, a NG-RAN node, a transmission reception point (TRP), a high altitude platform station (HAPS), a relay station, or the like. In one embodiment, executing Figure 5A The network node of the method may comprise an access management node, such as an AMF or similar radio node.

[0040] like Figure 5A In the example shown, in one embodiment, the method may include, at 500, receiving a registration request message from one or more UEs registered to a network within a registration area. In one embodiment, at 510, the method may include providing information including one or more TAI lists and one or more S-NSSAI lists to (multiple) UEs. For example, providing 510 may include transmitting information in a registration acceptance message to the UE. Additionally or alternatively, providing 510 may include transmitting information in a UE configuration update command message to one or more UEs. In one embodiment, one or more S-NSSAIs may indicate an S-NSSAI that is not uniformly supported in the registration area, and one or more TAI lists 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 rejected S-NSSAI list or an extended rejected S-NSSAI list, 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 TAI lists may identify an area where each of the one or more S-NSSAIs is not supported. According to certain embodiments, providing 510 may include providing information and / or a cause value to the UE when the UE signals support for such information in a registration request message.

[0041] According to one embodiment, one or more S-NSSAIs may be included in an information element identifying S-NSSAIs that the (multiple) UEs are allowed to use but are not uniformly supported in the registration area. In one embodiment, each of the one or more TAI lists may identify an area in which each of the one or more S-NSSAIs is supported.

[0042] According to certain embodiments, the information provided at 510 may include a registration area including at least a TAI list, an allowed NSSAI including a list of S-NSSAIs supported in the registration area, one or more restricted registration areas including a TAI list for a restricted registration area, and / or a portion of allowed S-NSSAIs allowed in the corresponding restricted registration area. Additionally or alternatively, in some embodiments, the information provided to the (multiple) UEs at 510 may also include a rejected NSSAI with a cause value for each S-NSSAI in the rejected NSSAI, the cause value indicating that the S-NSSAI is not uniformly supported in the registration area, and the TAI for which each S-NSSAI is supported. Additionally or alternatively, in certain embodiments, at 510, the information provided to the (multiple) UEs may also include a rejected NSSAI with a cause value indicating that the corresponding S-NSSAI is not uniformly supported in the registration area, and / or is not supported in the current tracking area, and the TAI for which the S-NSSAI in the S-NSSAI list is not supported.

[0043] According to one embodiment, when UE(s) need to be paged, the method may include selecting a paging area based on the S-NSSAI associated with the PDU session for the UE(s).

[0044] Figure 5B An example flow chart of a method for beam failure detection and / or beam failure recovery according to one embodiment is shown. In some example embodiments, Figure 5B The flowchart may be executed by a network entity or a network node in a communication system (e.g., LTE or 5G NR). In some example embodiments, the execution Figure 5B The network entity of the method may 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 execution Figure 5B The UE of the method may be a UE registered with the network within a registration area.

[0045] like Figure 5BIn the example shown, in one embodiment, the method may include, at 550, sending a registration request message to a network node (e.g., a gNB or an AMF). In one embodiment, the method may include receiving information including one or more TAI lists and one or more S-NSSAI lists at 560, which the UE may use to determine a TAI that supports an appropriate network slice based on the type of service required by the UE. According to one embodiment, one or more S-NSSAIs indicate S-NSSAIs that are not uniformly supported in the registration area, and the one or more TAI lists are associated with the one or more S-NSSAIs. For example, receiving 560 may include receiving information in a registration accept message from the AMF. In one embodiment, receiving 560 may include receiving information in a UE configuration update command message from the AMF. According to some embodiments, receiving 560 may include receiving the information and / or cause value when the UE signals support for such information in a registration request message.

[0046] In one embodiment, one or more S-NSSAIs may indicate an S-NSSAI that is not uniformly supported in a registration area, and one or more TAI lists 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 rejected S-NSSAI list or an extended rejected S-NSSAI list, and may be associated with a cause value indicating that the one or more S-NSSAIs are not uniformly supported in a registration area and / or are not supported in a current tracking area. In one embodiment, each of the one or more TAI lists may identify an area where each of the one or more S-NSSAIs is not supported.

[0047] According to one embodiment, one or more S-NSSAIs may be included in an information element identifying S-NSSAIs that the (multiple) UEs are allowed to use but are not uniformly supported in the registration area. In one embodiment, each of the one or more TAI lists may identify an area in which each of the one or more S-NSSAIs is supported.

[0048] According to certain embodiments, the received information may include at least a registration area including a TAI list, an allowed NSSAI including a list of S-NSSAIs supported in the registration area, one or more restricted registration areas including a TAI list for restricting the registration area, and / or a portion of the allowed S-NSSAIs allowed in the corresponding restricted registration area. Additionally or alternatively, in some embodiments, the received information may also include a rejected NSSAI with a cause value, the cause value of each S-NSSAI in the rejected NSSAI indicating that the corresponding S-NSSAI is not uniformly supported in the registration area and / or is not supported in the current tracking area, and the TAI in the S-NSSAI list for which the S-NSSAI is not supported.

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

[0050] According to one embodiment, the method may further include, at 580, detecting or determining whether the UE is in a TA of the registration area, the TA supporting at least one S-NSSAI that is not in the allowed NSSAIs, and the UE needs to request at least one S-NSSAI. Then, the method may include, at 585, when the UE detects that the UE is currently located in an area supporting at least one S-NSSAI of one or more S-NSSAIs that are not uniformly supported in the registration area, initiating the UE to perform a registration process, for example, by sending a registration request message. The registration message may include one S-NSSAI of the one or more S-NSSAIs that are not uniformly supported in the registration area and supported in the current area.

[0051] In one embodiment, the method may include the UE skipping performing the registration procedure when moving between TAIs included in the registration area received from the AMF.

[0052] According to some embodiments, if the UE detects that the UE is in an area that supports at least one of one or more S-NSSAIs that are not uniformly supported in the registration area, the method may include the UE considering or determining to allow at least one of the one or more S-NSSAIs that are not uniformly supported in the registration area.

[0053] Fig. 6AAn example of a device 10 according to an embodiment is shown. In one embodiment, the device 10 may be a telecommunications network or a node, host or server serving in such a telecommunications network. For example, the device 10 may be a network node, a sensor 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 (e.g., an LTE, 5G or NR radio access network). In some example embodiments, the device 10 may be an access and mobility management node or other similar network node. In some example embodiments, the device 10 may implement a network function, such as the AMF described above. In some example embodiments, the device 10 may implement multiple network functions of a core network, including the AMF, policy control function, session management function,

[0054] It should be understood that in some example embodiments, the device 10 may be composed of an edge cloud server (or distributed computing system) and a radio node, wherein the edge cloud server and the radio node may communicate with each other via a wireless path or via a wired connection. For example, in certain example embodiments where the device 10 represents a gNB, it may be configured as a central unit (CU) and one or more distributed units (DUs) to divide the gNB functionality. In such an example embodiment, the CU may be a logical node that includes gNB functionality such as user data transmission, mobility control, radio access network sharing, positioning and / or session management. The CU may control the operation of (multiple) DUs via a fronthaul interface. Depending on the functional splitting option, the DU may be a logical node that includes a subset of gNB functionality. It should be noted that a person of ordinary skill in the art may understand that the device 10 may include Fig. 6A Components or functions not shown.

[0055] like Fig. 6A In the example shown, the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, the processor 12 may include one or more of a general purpose computer, a special purpose 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 any other processing component as an example. Although Fig. 6AA single processor 12 is shown, but multiple processors may be used according to other embodiments. For example, it should be understood that in some embodiments, the device 10 may include two or more processors that may form a multiprocessor system that can support multiprocessing (e.g., processor 12 in this example may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., forming a computer cluster).

[0056] Processor 12 may perform functions associated with the operation of device 10, including, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that constitute communication information, formatting of information, and overall control of device 10, including processes related to communication or communication resource management.

[0057] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that can be executed by the processor 12. The memory 14 may be one or more memories, which may be of any type suitable for the local application environment, and may 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, the memory 14 may be composed of any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium or other suitable storage methods. The instructions stored in the memory 14 may include program instructions or computer program codes, which, when executed by the processor 12, may cause the device 10 to perform the tasks described herein.

[0058] In one embodiment, the device 10 may also include or be coupled to a (internal or external) 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 may store a computer program or software executed by the processor 12 and / or the device 10.

[0059] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for sending and receiving signals and / or data to and from the device 10. The device 10 may also include or be coupled to a transceiver 18 configured to send and receive information. For example, the transceiver 18 may include multiple radio interfaces that can be coupled to the antenna 15, and may also include any other suitable transceiver components. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, etc. The radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., for generating symbols for transmission via one or more downlinks and receiving symbols (e.g., via uplinks).

[0060] Thus, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15, and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly sending 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 components.

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

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

[0063] As used herein, the term "circuitry" may refer to any portion of a hardware circuit implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, (multiple) hardware processors and software (including digital signal processors) that work together to enable a device (e.g., device 10) to perform various functions, and / or (multiple) hardware circuits and / or (multiple) processors, or portions thereof, but the software may not be present when not required for operation. As a further example, as used herein, the term "circuitry" may also encompass an implementation consisting solely of a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its attached software and / or firmware. For example, the term circuitry may also encompass, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0064] As described above, in some embodiments, the device 10 may be a network element or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, HAPS, IAB node, WLAN access node, etc. In an example embodiment, the device 10 may be a gNB, AMF, or other radio node. According to some embodiments, the device 10 may 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 device 10 may be configured to execute any of the flowcharts or signaling diagrams described herein (such as Figure 5A 5B), or any other method described herein. In some embodiments, as discussed herein, the device 10 may be configured to perform procedures related to, for example, efficient registration of a region supporting a portion of a service.

[0065] Figure 6B An example of an apparatus 20 according to another embodiment is shown. In one embodiment, the apparatus 20 may be a node or element in a communication network or a node or element associated with the 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. As described herein, a UE may also be referred to as, for example, a mobile base station, a mobile device, a mobile unit, a mobile device, a user device, a subscriber station, a wireless terminal, a tablet, a smart phone, an IoT device, a sensor or an NB-IoT device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in an industrial and / or automated processing chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. For example, the apparatus 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, or a similar device.

[0066] In some example 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 radio access components (e.g., modems, transceivers, 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 a person of ordinary skill in the art will appreciate that the apparatus 20 may include Figure 6B Components or functions not shown.

[0067] like Figure 6B In the example shown, the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, the processor 22 may include one or more of a general purpose computer, a special purpose 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 any other processing means as an example. Although Figure 6B A single processor 22 is shown, but multiple processors may be used according to other embodiments. For example, it should be understood that in some embodiments, the device 20 may include two or more processors that may form a multiprocessor system that can support multiprocessing (e.g., processor 22 in this example may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., forming a computer cluster).

[0068] Processor 22 may perform functions associated with the operation of device 20, including, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits constituting communication information, formatting of information, and overall control of device 20, including processes related to communication or communication resource management.

[0069] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that can be executed by the processor 22. The memory 24 may be one or more memories, which may be of any type suitable for the local application environment, and may 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, the memory 24 may be composed of any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium or other suitable storage methods. The instructions stored in the memory 24 may include program instructions or computer program codes, which, when executed by the processor 22, may cause the device 20 to perform the tasks described herein.

[0070] In one embodiment, the device 20 may also include or be coupled to a (internal or external) 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 may store a computer program or software executed by the processor 22 and / or the device 20.

[0071] In some embodiments, the device 20 may further include or be coupled to one or more antennas 25 for receiving downlink signals and for uplink transmission via the device 20. The device 20 may further include a transceiver 28 configured to transmit and receive information. For example, the transceiver 28 may further include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), UWB, etc. The radio interface may include, for example, filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols (e.g., OFDMA symbols) carried by a downlink or uplink.

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

[0073] In one embodiment, the memory 24 may store software modules that provide functionality when executed by the processor 22. For example, the module may include an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules, such as applications or programs, that provide additional functionality for the device 20. The components of the device 20 may be implemented by hardware or any suitable combination of hardware and software. According to an example embodiment, the device 20 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (e.g., NR).

[0074] According to some embodiments, the processor 22 and the memory 24 may be included in or may constitute part of a processing circuit or a control circuit. In addition, in some embodiments, the transceiver 28 may be included in or may constitute part of a transceiver circuit.

[0075] As discussed above, according to some embodiments, the apparatus 20 may be a UE, a SL UE, a relay UE, a mobile device, a mobile station, a ME, an IoT device, and / or a NB-IoT device, etc., for example. According to some embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with any of the embodiments described herein, for example Figure 5A or Figure 5B One or more operations shown or described, or any other method described herein. For example, in one embodiment, the device 20 may be controlled to perform processes related to efficient registration of a partial support service area, as described in detail elsewhere herein.

[0076] In some embodiments, a device (e.g., device 10 and / or device 20) may include components for performing directions, procedures, or any variations discussed herein. Examples of components may include one or more processors, memories, controllers, transmitters, receivers, displays, and / or computer program codes for performing any of the operations described herein.

[0077] In view of the above, certain example embodiments provide a variety of technical improvements, enhancements and / or advantages over prior art processes, and at least constitute improvements in the field of wireless network control and / or management technology. For example, as discussed in detail above, certain example embodiments may provide methods and / or devices for efficient registration of areas that partially support services. As a result of certain embodiments, the UE can be aware of available network slices without performing a registration update procedure, and can request to establish a PDU session or initiate a scheduling request (SR) for a specific slice. In addition, the example embodiments allow for a reduction in control plane (C-plane) traffic, thereby reducing the probability of program collisions in the gNB / AMF, for example, a collision of RU and paging may result in the loss of a paging message. Therefore, the use of certain example embodiments results in improved functionality of communication networks and their nodes (e.g., base stations, eNBs, gNBs and / or IoT devices, UEs or mobile stations).

[0078] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flowchart described herein may be implemented by software and / or computer program code or portion of code stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0079] In some example embodiments, the device may include or be associated with at least one software application, module, unit, or entity that is configured as (multiple) arithmetic operations, or as a program or part of a program (including added or updated software routines), executable by at least one operating processor or controller. Programs, also known as program products or computer programs, include software routines, applets, and macros, which may be stored in any device-readable data storage medium and may include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. One or more computer executable components may be at least one software code or partial code. Modifications and configurations required to implement the functionality of the example embodiments may be performed as (multiple) routines, which may be performed as added or updated (multiple) software routines. In one example, (multiple) software routines may be downloaded to the device.

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

[0081] In other example embodiments, the functions of the example embodiments may be performed by hardware or circuitry contained in a device, such as by using 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 another example embodiment, the functions of the example embodiments may be implemented as a signal, such as a non-tangible means that may be carried by an electromagnetic signal downloaded from the Internet or other network.

[0082] According to an example embodiment, an apparatus, such as a node, a device or a corresponding component, may be configured as a circuit, a computer or a microprocessor, such as a single-chip computer element, or as a chipset, and may include at least a memory for providing memory for (multiple) computing operations and / or operating a processor to perform (multiple) computing operations.

[0083] The example embodiments described herein may apply to both singular and plural embodiments, regardless of whether singular or plural language is used when describing certain embodiments. For example, an embodiment describing the operation of a single network node may also apply to an embodiment including multiple network node instances, and vice versa.

[0084] It is readily understood by those skilled in the art that the example embodiments discussed above may be implemented with different sequences of procedures and / or hardware elements that are different from the disclosed configurations. Therefore, although some embodiments have been described based on these example embodiments, certain modifications, variations, and alternative structures are apparent to those skilled in the art while remaining within the spirit and scope of the example embodiments.

Claims

1. A method for communication, comprising: receiving, at an access and mobility function of a network, a registration request from a user equipment within a registration area, the registration area comprising a plurality of tracking areas, the registration request comprising a plurality of single network slice selection assistance information (S-NSSAI); determining, at the access and mobility function of the network, for at least one corresponding S-NSSAI of the plurality of S-NSSAIs, whether the corresponding S-NSSAI is supported in a current tracking area of ​​the user equipment, each tracking area of ​​the plurality of tracking areas being identified by a tracking area identifier (TAI), wherein when the corresponding S-NSSAI is supported in the current tracking area, the S-NSSAI is accepted, and when the S-NSSAI is not supported in the current tracking area, the S-NSSAI is rejected; as well as At the access and mobility function of the network, a response to the registration request is sent to the user equipment, the response including which S-NSSAI among the at least one S-NSSAI among the multiple S-NSSAIs is accepted or rejected in the current tracking area, and a list of one or more TAIs among a plurality of TAIs, in which the accepted or rejected S-NSSAIs are supported or not supported.

2. The method of claim 1 , wherein the list comprises one or more TAIs for tracking areas in the plurality of tracking areas that support the corresponding S-NSSAI that is rejected, and wherein the corresponding S-NSSAI that is rejected is partially allowed.

3. The method of claim 1 , wherein the list comprises one or more TAIs for tracking areas among the plurality of tracking areas that do not support the rejected corresponding S-NSSAI, the one or more TAIs including the TAI of the current tracking area.

4. The method according to claim 1, further comprising: receiving, after sending the response to the registration request to the user equipment, a second registration request from the user equipment in a new tracking area among the plurality of tracking areas, the second registration request comprising at least one S-NSSAI of the plurality of S-NSSAIs indicated as supported and accepted in the new tracking area; as well as Registering the user equipment with the at least one S-NSSAI among the multiple S-NSSAIs indicated as supported and accepted, and sending a response to the second registration request to the user equipment, the response to the second registration request including which S-NSSAI among the multiple S-NSSAIs is accepted or rejected.

5. A method for communication, comprising: Sending, by a user equipment, a registration request to a network to register with the network, the user equipment being within a registration area comprising a plurality of tracking areas, the registration request comprising a plurality of single network slice selection assistance information (S-NSSAI); receiving, by the user equipment, a response to the registration request from the network, the response including which of the multiple S-NSSAIs is supported or not supported in a current tracking area of ​​the user equipment, and including a list of one or more tracking area identifiers (TAIs) in a plurality of TAIs, in which the accepted or rejected S-NSSAIs are supported or not supported, the plurality of TAIs respectively corresponding to the plurality of tracking areas, wherein when the corresponding S-NSSAI is supported in the TAI of the current tracking area, the S-NSSAI is accepted, and when the S-NSSAI is not supported in the TAI of the current tracking area, the S-NSSAI is rejected; as well as At least one S-NSSAI of the plurality of S-NSSAIs that is included in the list of supported and accepted S-NSSAIs is determined by the user equipment, and a registration procedure is initiated for the at least one supported and accepted S-NSSAI.

6. The method of claim 5, wherein the list comprises one or more TAIs for tracking areas in the plurality of tracking areas that support the corresponding S-NSSAI that is rejected, and wherein the corresponding S-NSSAI that is rejected is partially allowed.

7. The method of claim 5, wherein the list comprises one or more TAIs for tracking areas among the plurality of tracking areas that do not support the corresponding S-NSSAI that is rejected, the one or more TAIs including the TAI of the current tracking area.

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

9. The method according to claim 5, wherein the registration procedure comprises: sending a second registration request to the network, the second registration request including at least one S-NSSAI of the plurality of S-NSSAIs indicated as supported and accepted; as well as A response to the second registration request is received by the user equipment from the network, the response to the second registration request confirming registration of the user equipment with the at least one S-NSSAI of the plurality of S-NSSAIs indicated as supported and accepted.

10. An apparatus for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receiving, at an access and mobility function, a registration request from a user equipment within a registration area, the registration area comprising a plurality of tracking areas, the registration request comprising a plurality of single network slice selection assistance information (S-NSSAI); determining, at the access and mobility function, for at least one corresponding S-NSSAI of the plurality of S-NSSAIs, whether the corresponding S-NSSAI is supported in a current tracking area of ​​the user equipment, each tracking area of ​​the plurality of tracking areas being identified by a tracking area identifier (TAI), wherein when the corresponding S-NSSAI is supported in the current tracking area, the S-NSSAI is accepted, and when the S-NSSAI is not supported in the current tracking area, the S-NSSAI is rejected; as well as At the access and mobility function, a response to the registration request is sent to the user equipment, the response including which S-NSSAI among the at least one S-NSSAI among the multiple S-NSSAIs is accepted or rejected in the current tracking area, and a list of one or more TAIs among a plurality of TAIs, in which the accepted or rejected S-NSSAIs are supported or not supported.

11. The apparatus of claim 10, wherein the list comprises one or more TAIs for tracking areas among the plurality of tracking areas that support the corresponding S-NSSAI that is rejected, and wherein the corresponding S-NSSAI that is rejected is partially allowed.

12. The apparatus of claim 10, wherein the list comprises one or more TAIs for tracking areas among the plurality of tracking areas that do not support the rejected corresponding S-NSSAI, the one or more TAIs including the TAI of the current tracking area.

13. The apparatus of claim 10, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving, after sending the response to the registration request to the user equipment, a second registration request from the user equipment in a new tracking area among the plurality of tracking areas, the second registration request comprising at least one S-NSSAI of the plurality of S-NSSAIs indicated as supported and accepted in the new tracking area; registering the user equipment with the at least one S-NSSAI among the plurality of S-NSSAIs indicated as supported and accepted; as well as A response to the second registration request is sent to the at least one user equipment, the response to the second registration request including which S-NSSAI of the plurality of S-NSSAIs is accepted or rejected.

Images