Method and apparatus for handling location based procedure in a wireless communication system

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond a 4G communication system such as long term evolution (LTE). Embodiments herein disclose methods and systems for handling location based procedures for store and forward in wireless communication networks with satellite access. Embodiments herein disclose one or more actions to be performed by a UE, when a wait timer expires, wherein the UE has received the wait timer and satellite IDs from MME on-board when MME ground is not available. Embodiments herein disclose a time period for which the UE should consider the satellite IDs as valid for Attach or TAU procedures, after expiry of the wait timer. Embodiments herein disclose one or more actions to be performed by a UE, if Satellite IDs are not included in the NAS message (for example, Partial Attach Accept / Partial TAU accept or any other NAS message).

Description

METHOD AND APPARATUS FOR HANDLING LOCATION BASED PROCEDURE IN A WIRELESS COMMUNICATION SYSTEM

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to managing store and forward operations in wireless communication networks with satellite access.

[0002] Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks. Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

[0003] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bit per second (bps) and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1 / 10 radio latency thereof.

[0004] In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz (THz) band (for example, 95 gigahertz (GHz) to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, Radio Frequency (RF) elements, antennas, novel waveforms having a better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming and massive Multiple-input Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS).

[0005] Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, High-Altitude Platform Stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collision avoidance based on a prediction of spectrum usage; an use of Artificial Intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as Mobile Edge Computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mechanisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

[0006] It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive eXtended Reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

[0007] For a 5G system with satellite access, the following requirement applies: the 5G system shall support service continuity between NR terrestrial access network and NR satellite access networks owned by the same operator or owned by 2 different operators having an agreement.

[0008] The Store and Forward Satellite operation in a 5G system with satellite access is intended to provide some level of communication service for UEs under satellite coverage with intermittent / temporary satellite connectivity (for example, when the satellite is not connected via a feeder link or via ISL to the ground network) for delay-tolerant communication service.

[0009] An example of “S&F Satellite operation” is illustrated in FIG. 1, in contrast to what could be considered the current assumption for the “normal / default Satellite operation” of a 5G system with satellite access. As shown in FIG. 1, under “normal / default Satellite operation” mode, signalling and data traffic exchange between a UE with satellite access and the remote ground network requires the service and feeder links to be active simultaneously, so that, at the time that the UE interacts over the service link with the satellite, there is a continuous end-to-end connectivity path between the UE, the satellite and the ground network.

[0010] In contrast, under “S&F Satellite operation” mode, the end-to-end exchange of signalling / data traffic is now handled as a combination of two steps not concurrent in time (steps A and B in FIG. 1). In step A, signalling / data exchange between the UE and the satellite occurs, without the satellite being simultaneously connected to the ground network (i.e., the satellite can operate the service link without an active feeder link connection). In step B, connectivity between the satellite and the ground network is established so that communication between the satellite and the ground network can take place. So, the satellite moves from being connected to the UE in step A to being connected to the ground network in step B.

[0011] As depicted in FIG. 1, the Satellite has AMF / MME on board or any other network function to support S&F registration procedure. The AMF / MME or any other Network Function (NF) may be with complete capability or some lighter version of the NF, with capabilities required to handle the registration procedure on board. Here, the MME / eNB / AMF / gNB will not be able to accurately determine the location of the UE because when the UE interacts with functions (for example, MME / eNB / AMF / gNB) on the satellite, they cannot interact with the GMLC / E-SMLC / SMLC or any other network function which is responsible for location based services which is located on the ground network and the ground network is not connected because feeder link is not available.

[0012] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0013] The principal object of embodiments herein is to disclose methods and systems for handling location based procedures for store and forward in wireless communication networks with satellite access.

[0014] Accordingly, the embodiments herein provide a method for handling a location-based procedure for store and forward in a wireless communication network. The Mobility Management Entity (MME)functionality is split into the MME-onboard, and a MME-ground, and the satellite comprises an Evolved Serving Mobile Location Centre (E-SMLC), and the MME-onboard. The method comprises the MME-onboard determining a current location of a User Equipment (UE) without any interaction with other core network entities deployed on the ground, and determining if the UE is allowed to operate at the determined current location. The method comprises the MME-onboard rejecting a Non-Access Stratum (NAS) request from the UE, on determining that the UE is not allowed to operate at the determined current location; and initiating an explicit detach of the UE, if the UE is registered to the network, on determining that the UE is not allowed to operate at the determined current location.

[0015] Accordingly, the embodiments herein provide a satellite comprising a Mobility Management Entity (MME)-onboard, wherein MME functionality is split into the MME-onboard, and a MME-ground; and an Evolved Serving Mobile Location Centre (E-SMLC). The MME-onboard is configured to determine a current location of a User Equipment (UE); determine if the UE is allowed to operate at the determined current location; reject a Non-Access Stratum (NAS) request from the UE, on determining that the UE is not allowed to operate at the determined current location; and initiate an explicit detach of the UE, if the UE is registered to the network, on determining that the UE is not allowed to operate at the determined current location.

[0016] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0017] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

[0018] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0019] FIG. 1 depicts an example scenario, wherein the MME / eNB / AMF / gNB will not be able to accurately determine the location of the UE, according to existing arts;

[0020] FIG. 2 depicts a wireless communication network comprising at least one satellite, according to embodiments as disclosed herein;

[0021] FIGs. 3A and 3B depict example scenarios, wherein the Satellite has AMF on board or any other network function to support S&F registration procedure, according to embodiments as disclosed herein;

[0022] FIG. 4 depicts an example scenario, wherein the UE is rejected, as the UE is not in a location, where it can be served, according to embodiments as disclosed herein; and

[0023] FIG. 5 depicts an example scenario, wherein the Attach Request / Tracking Area Request / Service Request message or any other NAS message is triggered by the UE on to the satellite access supporting store and forward operation, according to embodiments as disclosed herein

[0024] FIG. 6 is a flowchart depicting the process of handling a location-based procedure for store and forward in a wireless communication network, when the feeder link is available, according to embodiments as disclosed herein; and

[0025] FIG. 7 is a flowchart depicting the process of handling a location-based procedure for store and forward in a wireless communication network, when the feeder link is not available, according to embodiments as disclosed herein.

[0026] FIG. 8 is a block diagram of a terminal or user equipment (UE) 800 according to an embodiment of the disclosure.

[0027] FIG. 9 is a block diagram of a base station (BS) 900 according to an embodiment of the disclosure.

[0028] FIG.10 is a block diagram of a network entity 1000 according to an embodiment of the disclosure.

[0029] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0030] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0031] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0032] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0033] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0034] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0035] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0036] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0037] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0038] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0039] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0040] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0041] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0042] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0043] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0044] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0045] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0046] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0047] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0048] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0049] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0050] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0051] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0052] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0053] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0054] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0055] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0056] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0057] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0058] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0059] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0060] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0061] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) where appropriate.

[0062] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0063] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0064] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0065] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0066] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0067] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0068] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0069] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0070] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0071] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0072] The embodiments herein achieve methods and systems for handling location based procedure for store and forward in wireless communication networks with satellite access. Referring now to the drawings, and more particularly to FIGS. 2 through 7, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0073] The following terms and abbreviations have been referred to herein:

[0074] 3GPP: Third Generation Partnership Project

[0075] 4G-GUTI: 4G-Globally Unique Temporary Identifier

[0076] 5G-BRG: 5G Broadband Residential Gateway

[0077] 5GC: 5G Core

[0078] 5GCN: 5G Core Network

[0079] 5G-CRG: 5G Cable Residential Gateway

[0080] 5G-GUTI: 5G-Globally Unique Temporary Identifier

[0081] 5GMM: 5G Mobility Management

[0082] 5G-RG: 5G Residential Gateway

[0083] 5GS: 5G System

[0084] 5GSM: 5GS Session Management

[0085] 5G-S-TMSI: 5G S-Temporary Mobile Subscription Identifier

[0086] 5G-TMSI: 5G Temporary Mobile Subscription Identifier

[0087] 5QI: 5G QoS Identifier

[0088] ACS: Auto-Configuration Server

[0089] AKA: Authentication and Key Agreement

[0090] A-KID: AKMA Key Identifier

[0091] AKMA: Authentication and Key Management for Applications

[0092] AMBR: Aggregate Maximum Bit Rate

[0093] AMF: Access and Mobility Management Function

[0094] APN: Access Point Name

[0095] ARP: Allocation and Retention Policy

[0096] AS: Access Stratum

[0097] A-TID: AKMA Temporary Identifier

[0098] ATSSS: Access Traffic Steering, Switching and Splitting

[0099] AUSF: Authentication Server Function

[0100] CAG: Closed access group

[0101] CAG ID: Closed Access Group Identifier

[0102] CHAP: Challenge Handshake Authentication Protocol

[0103] CU: Centralized Unit

[0104] DC: Discontinuous Coverage

[0105] DisCo: Discontinuous Coverage

[0106] DL: Downlink

[0107] DND: Do not Disturb

[0108] DRX: Discontinuous Reception

[0109] DU: Distributed Unit

[0110] eDRX: Extended Discontinuous Reception

[0111] EHPLMN: Equivalent Home Public Land Mobile Network

[0112] EMM: EUTRA Mobility Management

[0113] eNB: Evolved Node-B

[0114] eNPN: Enhanced Non-Public Networks

[0115] EPC: Evolved Packet Core

[0116] EPLMN: Equivalent Public Land Mobile Network

[0117] EPS: Evolved Packet System

[0118] eSIM: embedded Subscriber Identity Module

[0119] E-UTRA: Evolved Universal Mobile Telecommunication Access

[0120] EUTRAN: Evolved Universal Mobile Telecommunication Access Network

[0121] FPLMN: Forbidden Public Land Mobile Network

[0122] FR: Frequency Range

[0123] GEO: Geostationary Orbit

[0124] GERAN: GSM Edge Radio Access Network

[0125] GERAN EC-GSM-IoT: GSM Edge Radio Access Network Extended Coverage -GSM-Internet of Things

[0126] gNB: Next generation Node-B

[0127] gNB - CU: Next generation Node-B Control Unit

[0128] gNB - DU: Next generation Node-B Distributive Unit

[0129] GPRS: General Packet Radio Service

[0130] GPS: Global Positioning System

[0131] GSM: Global System for Mobile Communication

[0132] HPLMN: Home Public Land Mobile Network

[0133] IAB: Integrated access and backhaul

[0134] IAB-UE: The part of the IAB node that supports the Uu interface towards the IAB-donor or another parent IAB-node (and thus manages the backhaul connectivity with either PLMN or SNPN it is registered with) is referred to as an IAB-UE.

[0135] LADN: Local Area Data Network

[0136] LCS: Location services

[0137] LEO: Low Earth Orbit

[0138] MBSR: Mobile Base Station Relay

[0139] MCC: Mobile Country Code

[0140] MCS: Mission Critical Service

[0141] ME: Mobile Equipment

[0142] MEC: Multi-Access Edge Computing

[0143] MEO: Medium Earth Orbit

[0144] MICO : Mobile Initiated Communication Only

[0145] MINT : Minimization of service interruption

[0146] MME: Mobility Management Entity

[0147] MNC: Mobile Network Code

[0148] MPS: Multimedia Priority Service

[0149] MS: Mobile Station. The present document makes no distinction between MS and UE.

[0150] NAS: Non-Access Stratum

[0151] NB-S1 Mode: Narrow Band with S1 Interface

[0152] NGAP: Next Generation Application Protocol

[0153] NG-RAN: Next Generation Radio Access Network

[0154] NPN: Non-Public Networks

[0155] NR: New Radio

[0156] NTN: Non Terrestrial Networks

[0157] NW: Network

[0158] OOS: Out of Service

[0159] OS Upgrade: Operating System Upgrade

[0160] PDN: Packet Data Network

[0161] PDU: Packet Data Unit

[0162] PLMN ID: Public Land Mobile Network Identity

[0163] PSM: Power Saving Mode

[0164] QoS: Quality Of Service

[0165] RAT: Radio Access Technology

[0166] RPLMN: Registered Public Land Mobile Network

[0167] RRC: Radio Resource Control

[0168] RU: Registration Update

[0169] SAT: Satellite

[0170] Satellite: An artificial body placed in orbit around the earth or moon or another planet in order to collect information or for communication.

[0171] Satellite Constellation: A group of satellites, placed in orbit round the earth or moon or another planet in order to collect information or for communication.

[0172] Service User: An individual who has received a priority level assignment from a regional / national authority (i.e., an agency authorised to issue priority assignments) and has a subscription to a mobile network operator

[0173] SIM: Subscriber Identity Module

[0174] SNPN : Standalone Non-Public Networks

[0175] SUCI: Subscription Concealed Identifier

[0176] SW: Software

[0177] TAC: Tracking Area Code

[0178] TAI: Tracking Area Identity

[0179] TAU: Tracking Area Update

[0180] TER: Terrestrial

[0181] TN: Terrestrial Networks

[0182] UCU: UE Configuration Update

[0183] UDM: Unified Data Management Function

[0184] UE: User Equipment

[0185] UL: Uplink

[0186] ULI: User Location Information

[0187] UPU: UE Parameters Update

[0188] USIM: Universal Subscriber Identification Module

[0189] Uu: The radio interface between the UE and the Node B

[0190] VMR: Vehicle Mounted Relay

[0191] VPLMN: Visited Public Land Mobile Network

[0192] WB-S1 Mode : Wide Band with S1 Interface

[0193] Visited PLMN (VPLMN): This is a PLMN different from the HPLMN (if the EHPLMN list is not present or is empty) or different from an EHPLMN (if the EHPLMN list is present).

[0194] Allowable PLMN: In the case of an MS operating in MS operation mode A or B, this is a PLMN which is not in the list of "forbidden PLMNs" in the MS. In the case of an MS operating in MS operation mode C or an MS not supporting A / Gb mode and not supporting Iu mode, this is a PLMN which is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS.

[0195] Available PLMN: PLMN(s) in the given area which is / are broadcasting capability to provide wireless communication services to the UE.

[0196] Camped on a cell: The MS (ME if there is no SIM) has completed the cell selection / reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN or the SNPN may not be aware of the existence of the MS (ME) within the chosen cell.

[0197] EHPLMN: Any of the PLMN entries contained in the Equivalent HPLMN list.

[0198] Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for PLMN selection purposes.

[0199] Home PLMN: This is a PLMN where the MCC and MNC of the PLMN identity match the MCC and MNC of the IMSI.

[0200] Registered PLMN (RPLMN): This is the PLMN on which certain LR (location registration which is also called as registration procedure) outcomes have occurred. In a shared network the RPLMN is the PLMN defined by the PLMN identity of the CN operator that has accepted the LR.

[0201] Registration: This is the process of camping on a cell of the PLMN or the SNPN and doing any necessary LRs.

[0202] UPLMN : PLMN / access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order).

[0203] OPLMN: PLMN / access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order).

[0204] Serving satellite: A satellite providing the satellite access to a UE. In the case of a Non-Geostationary Satellite Orbit (NGSO), the serving satellite is always changing due to the nature of the constellation.

[0205] Store & Forward Satellite operation: In the context of this study, it is an operation mode of a 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently / temporarily unavailable; for example, to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.

[0206] S&F data retention period: It is the data storage validity period for the 5G system with satellite access supporting store and forward operation (for example, after which undelivered data stored is discarded).

[0207] UE-Satellite-UE Communication: For the 5G system with satellite access, it refers to the communication between UEs under the coverage of one or more serving satellites, using satellite access without going through the ground segment.

[0208] Examples of the NAS messages can be, but not limited to, REGISTRATION REQUEST message; DEREGISTRATION REQUEST message; SERVICE REQUEST message; CONTROL PLANE SERVICE REQUEST; IDENTITY REQUEST; AUTHENTICATION REQUEST; AUTHENTICATION RESULT; AUTHENTICATION REJECT; REGISTRATION REJECT; REGISTRATION ACCEPT; DEREGISTRATION ACCEPT; SERVICE REJECT; SERVICE ACCEPT; UE CONFIGURATION UPDATE command; UE PARAMETERS UPDATE command; and so on.

[0209] The term RAT as defined in this embodiment can be one of the following: NG-RAN, 5G, 4G, 3G, 2G, EPS, 5GS, NR, NR in unlicensed bands, NR (LEO) satellite access, NR (MEO) satellite access, NR (GEO) satellite access, NR (OTHERSAT) satellite access, NR RedCap, E-UTRA, E-UTRA in unlicensed bands, NB-IoT, WB-IoT, LTE-M, and so on

[0210] 5GS registration type can be initial registration, mobility registration updating, periodic registration updating, emergency registration,

[0211] SNPN onboarding registration, disaster roaming initial registration, disaster roaming mobility registration updating, and so on.

[0212] not set the registration type to disaster roaming initial registration or disaster roaming mobility registration updating means 5GS registration type is set to value other than "disaster roaming initial registration” or “"disaster roaming mobility registration updating” at least one of initial registration, mobility registration updating, periodic registration updating, emergency registration, SNPN onboarding registration, and so on.

[0213] The NTN and TN could either operate in two different frequency bands (for example, FR1 vs FR2), or in the same frequency band (for example, FR1 or FR2).

[0214] The Satellite System or Satellite Access as used or defined in this embodiment is applicable for both 5G system with satellite access and / or 4G system with satellite access or any RAT with satellite access.

[0215] The terms 'Satellite 3GPP access', 'Satellite access', 'Satellite Access Network', 'NR Satellite Access Network', 'Satellite NG-RAN Access Technology', and 'NR Satellite' access have been used interchangeably and have the same meaning.

[0216] The methods, issues or solutions disclosed in this embodiment are explained using NR satellite access or Satellite NG-RAN Access Technology as an example and are not restricted or limited to NR Satellite access only. However, the solutions proposed in this embodiment are also applicable for Satellite E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB(Wide Band)-S1 mode via satellite E-UTRAN access and / or NB-IOT (NarrowBand Internet Of Things) or WB-IOT (WideBand Internet Of Things) Satellite Access / Architecture.

[0217] The solutions which are defined for NR (5GC) are also applicable to legacy RATs like E-UTRA / LTE, the corresponding CN entities need to be replaced by LTE entities; for example, AMF with MME, g-nodeB with e-nodeB, UDM with HSS, and so on. But principles of the solution remains same. In a similar way, embodiments herein which are defined for LTE (EPC) are also applicable to other RAT(s) (for example, 5G or 5GC and other RATs)

[0218] An example list of NAS messages can be, but not limited to, REGISTRATION REQUEST message; DEREGISTRATION REQUEST message; SERVICE REQUEST message; CONTROL PLANE SERVICE REQUEST; IDENTITY REQUEST; AUTHENTICATION REQUEST; AUTHENTICATION RESULT; AUTHENTICATION REJECT; REGISTRATION REJECT; DEREGISTRATION ACCEPT; SERVICE REJECT; SERVICE ACCEPT, and so on.

[0219] The Network used in this embodiment is explained using any 5G Core Network Function (for example. AMF). However, the network could be any 5G / EUTRAN Core Network Entities (such as, but not limited to, AMF / SMF / MME / UPF) or the Network could be any 5G / EUTRAN RAN Entity (such as, but not limited to, eNodeB (eNB) or gNodeB (gNB) or NG-RAN, and so on).

[0220] The messages used or indicated in this embodiment are shown as an example. The messages could be any signalling message between the UE and the Network Functions / Entities or between different Network functions / entities.

[0221] The terms 'area', 'location', and 'geographical area' as referred to herein may refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, latitude / longitude, CAG cell or any geographical location / coordinate.

[0222] The Network used in this embodiment is explained using any EPS / 4GS system (for example, MME and eNB). However, the network could be any 5G / EUTRAN Core Network Entities (such as, but not limited to, AMF / SMF / MME / UPF, and so on) or the Network could be any 5G / EUTRAN RAN Entity (such as, but not limited to, eNodeB (eNB) or gNodeB (gNB) or NG-RANm and so on).

[0223] The methods, issues or solutions disclosed in this embodiment are explained using NR access or NG-RAN Access Technology as an example and is not restricted or limited to NR access only. However, the solutions proposed in this embodiment are also applicable for E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB (Wide Band)-S1 mode via E-UTRAN access and / or NB-IOT (NarrowBand Internet Of Things) or WB-IOT (WideBand Internet Of Things) Access / Architecture.

[0224] The solutions which are defined for NR (5GC) are also applicable to legacy RATs like E-UTRA / LTE, the corresponding CN entities need to be replaced by LTE entities (for example, AMF with MME, g-nodeB with e-nodeB, UDM with HSS, and so on). But principles of the solution remains same.

[0225] The Network used in this embodiment is explained using any 5G Core Network Function (for example, AMF). However, the network could be any 5G / EUTRAN Core Network Entities (such as, but not limited to, AMF / SMF / MME / UPF, and so on or the Network could be any 5G / EUTRAN RAN Entity (such as, but not limited to, eNodeB (eNB) or gNodeB (gNB) or NG-RAN, and so on.

[0226] The messages used or indicated in this embodiment are shown as an example. The messages could be any signalling message between the UE and the Network Functions / Entities or between different Network functions / entities.

[0227] The terms 'camp' and 'register' are used interchangeably and have the same meaning.

[0228] The terms 'wait timer', 'DisCo wait timer', 'Discontinuous Coverage wait timer', 'Random timer', 'Random wait timer', and 'DCW Timer' are all used interchangeably and have the same meaning.

[0229] The terms 'wait range', 'Disco Wait Range', 'Discontinuous Coverage Wait Range', and 'DCW Range' are all used interchangeably and have the same meaning.

[0230] The term 'area' as used in this embodiment may refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, any CAG / CAG identifier or any geographical location / coordinate.

[0231] The cause names in this embodiment are for illustration purposes, and it can have any name. The non access stratum (NAS) messages and access stratum (AS) messages described in this embodiment are only for illustration purposes, and it can be any NAS or AS messages as per defined protocol between the UE and the AMF / MME or the UE and the gNB (NG-RAN / any RAN node) / eNB.

[0232] In this embodiment, the term 'Satellite' is used interchangeably with 5G or 4G system with satellite access and is used to represent any satellite(s) or constellation of satellites(s) or any aerial body / satellite in any of the Satellite orbits (for example, LEO / MEO / GEO / HEO, and so on) or any 5G system with Satellite Access or 4G System with Satellite Access or any RAN Entity or Core Network Entity or any Network Function(s) associated with the Satellite Access / RAT / PLMN / Network.

[0233] FIG. 2 depicts a wireless communication network comprising at least one satellite. The network 200 comprises at least one satellite 201, at least one ground network 202, and at least one User Equipment (UE) 203. The Mobility Management Entity (MME) function can be split into two parts, an MME-onboard 201A, and a MME-ground 202A. The MME-onboard 201A can be deployed on the satellite 201. The MME-ground 202A can be deployed in the ground network 202, wherein the ground network 202 further comprises an AMF / MME 202B. The satellite 201 can further comprise at least one Evolved Serving Mobile Location Centre (E-SMLC) 201B, and an onboard eNB 201C. The MME-onboard 201A can handle the S1 interface with the onboard eNB 201C. The MME-onboard 201A can handle the NAS protocol signalling from / to UEs via the onboard eNB 201C.

[0234] The E-SMLC 201B can receive information about the UE 203, wherein the information can be, but not limited to, Narrowband Internet of Things (NB-IoT), and coarse location information from the UE 203. The E-SMLC 201B can perform the verification of UE location functionality. The E-SMLC 201B can use the information received from the UE 203, for determining the location of the UE 203. In an embodiment herein, full functionality of the E-SMLC 201B can be implemented on-board the satellite 201. In an embodiment herein, partial functionality of the E-SMLC 201B can be implemented on-board the satellite 201, and the remaining functionality of the E-SMLC 201B can be implemented on the ground network 202.

[0235] The MME-onboard 201A can determine a current location of the UE 203 without any interaction with other core network entities deployed on the ground 202. In an embodiment herein, the MME-onboard 201A can determine the location of the UE based on a Public Land Mobile Network (PLMN) ID selected by the UE 203, and identity of a cell serving the UE 203. In an embodiment herein, consider that the feeder link (i.e., a link between the satellite 201, and the ground network 202) is not available, the MME-onboard 201A can determine the location of the UE 203, based on an interaction with the E-SMLC 201B using a Coarse Location Information of the UE 203. The E-SMLC 201B can use information such as, but not limited to, Narrowband Internet of Things (NB-IoT), and coarse location information, which has been received from the UE 203, for determining the location of the UE 203.

[0236] On determining the current location of the UE 203, the MME-onboard 201A can determine whether the UE 203 is allowed to or not allowed to operate at the determined current location of the UE 203. If the UE 203 is not allowed to operate at the determined current location of the UE 203 and the UE is not already registered to the network, the MME-onboard 201A can reject any NAS request from the UE 203 with a suitable Cause value. If the UE is already registered to the network, and on determining that the UE 203 is not allowed to operate at the determined current location of the UE 203, the MME-onboard 201A can initiate an explicit detach procedure with the UE 203. In an embodiment herein, the MME-onboard 201A may not reject the NAS request from the UE 203, or detach the UE 203, unless the MME-onboard 201A has sufficiently accurate location information of the UE 203 to determine that the UE 203 is located in a geographical area where the PLMN is not allowed to operate.

[0237] As depicted in FIGs. 3A, and 3B, consider that the Satellite has an AMF / MME on board or any other NF to support the S&F registration procedure. The AMF / MME or any other NF may have complete capability or a lighter version of the NF, wherein the lighter version of the NF (i.e., MME-onboard 201A) can handle the registration procedure on board. The GMLC / E-SMLC / SMLC or any other network function (i.e., MME-onboard 201A) can be responsible for location-based services that have been deployed onboard the satellite. In an embodiment herein, the full function (for example, E-SMLC) can be onboarded on the satellite. In an embodiment herein, a partial function of the core network entities (for example, E-SMLC) can be onboarded on the satellite, which is responsible for determining the location of the UE, and the rest of the functions for maintaining the UE Location context, and so on, are on the ground network.

[0238] As depicted in FIG. 4, an Attach Request / Tracking Area Request / Service Request message or any other NAS message can be triggered by the UE 203 onto the satellite access supporting store and forward operation. The MME or eNB function onboard the satellite determines the location of the UE with the help of E-SMLC or GMLC function which is onboard the satellite. The MME interacts with the network node, which is responsible for managing / maintaining / determining the UE location. If the UE is not in a location, where it can be served, then the UE is rejected by the network.

[0239] As depicted in FIG. 5, consider that the Attach Request / Tracking Area Request / Service Request message or any other NAS message is triggered by the UE on to the satellite access supporting store and forward operation. The MME or eNB function determines the location of the UE with the help of E-SMLC or GMLC function which is onboard the satellite. The MME interacts with the network node which is responsible for managing / maintaining / determining the UE location. If the UE is not in the location where it can be served, then the UE is rejected by the network. Otherwise, the NAS procedure is accepted, and a respective accept message (such as, but not limited to, TAU accept / attach accept / service accept / registration accept) is given to the UE. The E-SMLC / GMLC / SMLC (which is onboard the satellite) synchronizes its context with the respective ground E-SMLC / GMLC / SMLC when the feeder link is established. The E-SMLC / GMLC / SMLC in the ground acts as an anchor node, and shares / manages the context on all the respective onboard E-SMLCs / GMLCs / SMLCs.

[0240] FIG. 6 is a flowchart depicting the process of handling a location-based procedure for store and forward in a wireless communication network, when the feeder link is available. In step 601, the MME-onboard 201A determines the current location of the UE 203 based on a Public Land Mobile Network (PLMN) ID selected by the UE 203, and identity of a cell serving the UE 203. On determining the current location of the UE 203, in step 602, the MME-onboard 201A determines whether the UE 203 is allowed to or not allowed to operate at the determined current location of the UE 203. If the UE 203 is not allowed to operate at the determined current location of the UE 203 and the UE is not already registered to the network (step 603), in step 604, the MME-onboard 201A rejects any NAS request from the UE 203 with a suitable Cause value. If the UE is already registered to the network (step 603), and on determining that the UE 203 is not allowed to operate at the determined current location of the UE 203, in step 605, the MME-onboard 201A initiates an explicit detach procedure with the UE 203. If the UE 203 is allowed to operate at the determined current location of the UE 203, in step 606, the MME-onboard 201A enables the UE 203 to operate at the determined current location of the UE 203. The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0241] FIG. 7 is a flowchart depicting the process of handling a location-based procedure for store and forward in a wireless communication network, when the feeder link is not available. In step 701, the E-SMLC 201B receives information from the UE 203 or about the UE 203 from any NF (for example, MME-onboard or AMF-onboard the satellite, wherein the information can be, but not limited to, Narrowband Internet of Things (NB-IoT) RAT, and coarse location information from the UE 203). In step 702, the E-SMLC 201B determines the location of the UE 203 using the information received from the UE 203. In step 703, the MME-onboard 201A determines the current location of the UE 203 without any interaction with other core network entities deployed on the ground 202, and based on an interaction with the E-SMLC 201B using the Coarse Location Information of the UE 203. On determining the current location of the UE 203, in step 704, the MME-onboard 201A determines whether the UE 203 is allowed to or not allowed to operate at the determined current location of the UE 203. If the UE 203 is not allowed to operate at the determined current location of the UE 203 and the UE is not already registered to the network (step 705), in step 706, the MME-onboard 201A rejects any NAS request from the UE 203 with a suitable Cause value. If the UE is already registered to the network (step 705), and on determining that the UE 203 is not allowed to operate at the determined current location of the UE 203, in step 707, the MME-onboard 201A initiates an explicit detach procedure with the UE 203. If the UE 203 is allowed to operate at the determined current location of the UE 203, in step 708, the MME-onboard 201A enables the UE 203 to operate at the determined current location of the UE 203. The various actions in method 700 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0242] FIG. 8 is a block diagram of a terminal or user equipment (UE) 800 according to an embodiment of the disclosure.

[0243] The terminal is an electronic device capable of wireless communication, may include a User Equipment (UE), a portable phone, a smartphone, a tablet, an Internet of things (IoT) device, etc., having various form factors, and may perform wireless communication with a base station (BS) through a wireless channel.

[0244] Referring to FIG. 8, the UE 800 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 801, at least one processor (hereinafter, referred to as simply “processor”) 802, and at least one memory (hereinafter, referred to as simply “memory”) 803. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 801, the processor 802, and the memory 803 of the UE 800 may operate. However, components of the UE 800 are not limited to the exemplary components illustrated in FIG. 8. In another embodiment, the UE 800 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 801, the processor 802, or the memory 803 may be integrated in the form of one component.

[0245] The transceiver 801 may be a communication circuit or communication circuitry that enables the UE 800 to perform wireless communication with a node or an entity of a network. For example, the transceiver 801 may enable the UE 800 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 801 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (801) may include all subsequent generations of evolved wireless communications.

[0246] According to an embodiment, the UE 800 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 800 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 800 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 800 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0247] According to an embodiment, the transceiver 801 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 801 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 801 may output a signal received through a wireless channel to the processor 802 and may transmit, through a wireless channel, a signal output from the processor 802.

[0248] The processor 802 may control general operations of the UE 800 according to embodiments of the disclosure. The processor 802 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 802 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 803, individually, collectively or in any combination thereof. Further, the processor 802 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0249] The processor 802 may be electrically, operatively, or communicatively coupled to the transceiver 801 to control the transceiver 801.

[0250] The processor 802 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 802 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer) . In a specific embodiment, at least a part of the processor 802 may be included in one chip and the other part of the processor 802 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 801 or the memory 803.

[0251] The processor 802 may perform or control or cause an operation of the UE 800 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 802 may control operations of the UE 800 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 802 may execute a computer program, codes, or instructions stored in the memory 803, so as to control other components of the UE 800 to enable execution of various operations.

[0252] The memory 803 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 803 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0253] The memory 803 may be electrically, operatively, or communicatively coupled to the processor 802 and may be accessed by the processor 802.

[0254] The memory 803 may store a computer program, codes, or instructions executable by the processor 802. According to an embodiment, a computer program, codes, or instructions executable by the processor 802 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 803, the processor 802 may perform various functions according to an embodiment of the disclosure.

[0255] According to an embodiment of the disclosure, operations of the UE 800 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 803 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0256] FIG. 9 is a block diagram of a base station (BS) 900 according to an embodiment of the disclosure.

[0257] The BS 900 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 900 through a wireless channel.

[0258] Referring to FIG. 9, the BS 900 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 901, at least one processor (hereinafter, referred to as simply “processor”) 902, and at least one memory (hereinafter, referred to as simply “memory”) 903. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 901, the processor 902, and the memory 903 of the BS 900 may operate. However, components of the BS 900 are not limited to the exemplary components illustrated in FIG. 9. In another embodiment, the BS 900 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 901, the processor 902, or the memory 903 may be integrated in the form of one component.

[0259] The transceiver 901 may be a communication circuit or communication circuitry that enables the BS 900 to perform wireless communication with a node or an entity of a network. For example, the transceiver 901 may enable the BS 900 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 901 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (901) may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 901 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 901 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 901 may output a signal received through a wireless channel to the processor 902 and may transmit, through a wireless channel, a signal output from the processor 902.

[0260] Meanwhile, according to an embodiment of the present disclosure, the BS 900 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 900 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 9, when the BS 900 performs wired communication, the BS 900 may further include a separate network interface for wired communication in addition to the transceiver 901. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0261] The processor 902 may control general operations of the BS 900 according to embodiments of the disclosure. The processor 902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 903, individually, collectively or in any combination thereof. Further, the processor 902 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0262] The processor 902 may be electrically, operatively, or communicatively coupled to the transceiver 901 to control the transceiver 901.

[0263] The processor 902 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 902 may be included in one chip and the other part of the processor 902 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 901 or the memory 903.

[0264] The processor 902 may perform or control or cause an operation of the BS 900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 902 may control operations of the BS 900 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 900 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 902 may execute a computer program, codes, or instructions stored in the memory 903, so as to control other components of the BS 900 to enable execution of various operations.

[0265] The memory 903 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 903 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0266] The memory 903 may be electrically, operatively, or communicatively coupled to the processor 902 and may be accessed by the processor 902.

[0267] The memory 903 may store a computer program, codes, or instructions executable by the processor 902. According to an embodiment, a computer program, codes, or instructions executable by the processor 902 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 903, the processor 902 may perform various functions according to an embodiment of the disclosure.

[0268] According to an embodiment of the disclosure, operations of the BS 900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 903 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0269] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with network entity such as an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0270] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0271] FIG.10 is a block diagram of a network entity 1000 according to an embodiment of the disclosure.

[0272] The network entity 1000 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1000.

[0273] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0274] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0275] Referring to FIG. 10, the network entity 1000 may include at least one network interface 1001, at least one processor 1002 (hereinafter, “processor”), and at least one memory 1003 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1000, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 10. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0276] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1001, the processor 1002, and the memory 1003 of the network entity 1000 may operate. However, components of the network entity 1000 are not limited to the exemplary components illustrated in FIG. 10. In another embodiment, the network entity 1000 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1001, the processor 1002, or the memory 1003 may be integrated in the form of one component.

[0277] The network interface 1001 is a collective term for a transmitter part of the network entity 1000 and a receiver part of the network entity 1000, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1001 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1001 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1001 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0278] The processor 1002 may control general operations of the network entity 1000 according to embodiments of the disclosure. The processor 1002 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1002 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1003, individually, collectively or in any combination thereof. Further, the processor 1002 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0279] According to an embodiment, the processor 1002 may be electrically, operatively, or communicatively coupled to the network interface 1001 to control the network interface 1001.

[0280] The processor 1002 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1002 may be included in one chip and the other part of the processor 1002 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 1001 or the memory 1003.

[0281] The processor 1002 may perform or control or cause an operation of the network entity 1000 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1002 may control operations of the network entity 1000 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1002 may execute a computer program, codes, or instructions stored in the memory 1003, so as to control other components of the network entity 1000 to enable execution of various operations.

[0282] The memory 1003 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1003 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0283] The memory 1003 may be electrically, operatively, or communicatively coupled to the processor 1002 and may be accessed by the processor 1002.

[0284] The memory 1003 may store a computer program, codes, or instructions executable by the processor 1002. According to an embodiment, a computer program, codes, or instructions executable by the processor 1002 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1003, the processor 1002 may perform various functions according to an embodiment of the disclosure.

[0285] According to an embodiment of the disclosure, operations of the network entity 1000 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1003 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0286] According to an embodiment of the disclosure, A method for handling a location-based procedure for store and forward in a wireless communication network, the method comprising: determining, by a Mobility Management Entity (MME)-onboard a satellite, a current location of a User Equipment (UE) without any interaction with other core network entities deployed on the ground, wherein MME functionality is split into the MME-onboard, and a MME-ground, and the satellite comprises an Evolved Serving Mobile Location Centre (E-SMLC); determining, by the MME-onboard, if the UE is allowed to operate at the determined current location; rejecting, by the MME-onboard, a Non-Access Stratum (NAS) request from the UE, on determining that the UE is not allowed to operate at the determined current location; and initiating, by the MME-onboard, an explicit detach of the UE, if the UE is registered to the network, on determining that the UE is not allowed to operate at the determined current location.

[0287] In various embodiments, the method comprises determining, by the MME-onboard, the location of the UE based on a Public Land Mobile Network (PLMN) ID selected by the UE, and identity of a cell serving the UE.

[0288] In various embodiments, the method comprises determining, by the MME-onboard, the location of the UE based on an interaction with the E-SMLC, when a feeder link is not available, wherein the E-SMLC determines the location of the UE, using a Coarse Location Information of the UE.

[0289] According to an embodiment of the disclosure, A satellite comprising: a Mobility Management Entity (MME)-onboard, wherein MME functionality is split into the MME-onboard, and a MME-ground; and an Evolved Serving Mobile Location Centre (E-SMLC), wherein the MME-onboard is configured to: determine a current location of a User Equipment (UE); determine if the UE is allowed to operate at the determined current location; reject a Non-Access Stratum (NAS) request from the UE, on determining that the UE is not allowed to operate at the determined current location; and initiate an explicit detach of the UE, if the UE is registered to the network, on determining that the UE is not allowed to operate at the determined current location.

[0290] In various embodiments, wherein the MME-onboard is configured to determine the location of the UE based on a Public Land Mobile Network (PLMN) ID selected by the UE, and identity of a cell serving the UE.

[0291] In various embodiments, wherein the MME-onboard is configured to determine the location of the UE based on an interaction with the E-SMLC, when a feeder link is not available, wherein the E-SMLC determines the location of the UE, using a Coarse Location Information of the UE.

[0292] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0293] The embodiments disclosed herein describe methods and systems for handling location based procedure for store and forward in wireless communication networks with satellite access. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile deviceor any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0294] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practised with modification within the scope of the embodiments as described herein.

[0295] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

A method performed by a network entity for mobility management in a wireless communication system, the method comprising:determining that a user equipment (UE) is not allowed to operate at a present UE location; anddetermining to reject a non-access stratum (NAS) request from the UE,wherein the network entity handles an interface with a base station which is onboard a satellite.The method of claim 1, further comprising:transmitting, to the UE, a NAS reject message with a cause value based on the determination to reject the NAS request.The method of claim 1, further comprising:in case that the UE is already registered to a network, initiating an explicit detach of the UE.The method of claim 1, wherein the determining that the UE is not allowed to operate at the present UE location is based on a selected public land mobile network (PLMN) ID, and an identity of a cell serving the UE.The method of claim 1, wherein the determining that the UE is not allowed to operate at the present UE location is based on coarse location information of the UE and a reply from an evolved serving mobile location center (E-SMLC) deployed on the satellite for a verification of a UE location functionality.The method of claim 1, wherein the network entity handles a NAS protocol signalling from the UE via the base station.The method of claim 1, wherein the network entity is split into a first function and a second function, andwherein the first function is onboard the satellite and the second function is on a ground network.The method of claim 1, wherein the network entity includes a mobility management entity (MME) or access and mobility management function (AMF) entity.A network entity for mobility management comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the network entity to:determine that a user equipment (UE) is not allowed to operate at a present UE location, anddetermine to reject a non-access stratum (NAS) request from the UE,wherein the network entity handles an interface with a base station which is onboard a satellite.The network entity of claim 9, wherein the instructions further cause the satellite to:transmit, to the UE, a NAS reject message with a cause value based on the determination to reject the NAS request.The network entity of claim 9, wherein the instructions further cause the network entity to:in case that the UE is already registered to a network, initiate an explicit detach of the UE.The network entity of claim 9, wherein the determining that the UE is not allowed to operate at the present UE location is based on a selected public land mobile network (PLMN) ID, and an identity of a cell serving the UE.The network entity of claim 9, wherein the determining that the UE is not allowed to operate at the present UE location is based on coarse location information of the UE and a reply from an evolved serving mobile location center (E-SMLC) deployed on the satellite for a verification of a UE location functionality.The network entity of claim 9, wherein the network entity handles a NAS protocol signalling from the UE via the base station.The network entity of claim 9, wherein the network entity is split into a first function and a second function, andwherein the first function is onboard the satellite and the second function is on a ground network.

Images