Patent Description:
Therefore, the <NUM> or pre-<NUM> communication system is also called a "beyond <NUM> network" communication system or a "post LTE" system.

The <NUM> communication system is considered to be implemented in ultrahigh frequency (mmWave) bands (e.g., <NUM> bands) so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance in the ultrahigh frequency bands, beamforming, massive multiple-input multiple-output (massive MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam forming, large scale antenna techniques are discussed in <NUM> communication systems.

In addition, in <NUM> communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (cloud RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), receptionend interference cancellation and the like.

In the <NUM> system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have also been developed.

Standard-related document "<NPL>, discloses the service-based architecture used for location services in the <NUM> system and corresponding Network Functions (NFs).

Document "<NPL>, discloses reply LS on DRX parameters negotiation, especially a requirement whether the AMF need change the UE requested DRX parameters value.

Standard-related document "<NPL>, discloses procedures for <NUM> system.

Standard-related document "<NPL>, discloses service requirements for <NUM> system.

Based on the above-mentioned discussion, the disclosure provides a method and apparatus for providing a low-latency location information service in a wireless communication system.

According to various embodiments of the disclosure, an operation method of an access and mobility function (AMF) is provided. The method may include an operation of receiving, from a user equipment (UE), a UE-originated location information request (mobile originated location request) message including first location quality of service (QoS) information, an operation of receiving a UE-terminated location information request (mobile terminated location request) message including second location QoS information from a gateway mobile location center (GMLC) or a network exposure function (NEF), an operation of determining updating of a UE configuration (UE configuration update) based on the first location QoS information and second location QoS information, an operation of transmitting a UE configuration update command message to the UE, and an operation of transmitting, to a base station (radio access network (RAN)) related to the UE, a RAN update (update RAN) message, in response to reception of a UE configuration update complete message.

According to various embodiments of the disclosure, an apparatus of an access and mobility function (AMF) in a wireless communication system is provided. The apparatus includes a transceiver and at least one processor. The at least one processor is configured to receive, from a user equipment (UE), a UE-originated location information request (mobile originated location request) message including first location quality of service (QoS) information, to receive a UE-terminated location information request (mobile terminated location request) message including second location QoS information from a gateway mobile location center (GMLC) or a network exposure function (NEF), to determine updating of UE configuration based on the first location QoS information and the second location QoS information, to transmit a UE configuration update command message to the UE, and to transmit, to a base station (radio access network (RAN)) related to the UE, a RAN update (update RAN) message in response to reception of a UE configuration update complete message.

A method and apparatus according to various embodiments of the disclosure may provide a method and apparatus for providing a low-latency location information service in a wireless communication system.

Advantageous effects obtainable from the disclosure may not be limited to the above mentioned effects, and other effects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

In the following description, the invention is described with particular reference to <FIG>, while the description of the remaining figures is provided for illustrative purposes for a better understanding of the invention.

The terms used in the disclosure are only used to describe specific embodiments, and are not intended to limit the disclosure. A singular expression may include a plural expression unless they are definitely different in a context. Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as those commonly understood by a person skilled in the art to which the disclosure pertains. Such terms as those defined in a generally used dictionary may be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the disclosure. In some cases, even the term defined in the disclosure should not be interpreted to exclude embodiments of the disclosure.

Hereinafter, various embodiments of the disclosure will be described based on an approach of hardware. However, various embodiments of the disclosure include a technology that uses both hardware and software, and thus the various embodiments of the disclosure may not exclude the perspective of software.

In the following description, terms referring to signals, terms referring to channels, terms referring to control information, terms referring to network entities, terms referring to device elements, and the like are illustratively used for the sake of convenience. Therefore, the disclosure is not limited by the terms as used below.

In the following description, terms for identifying access nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, and the like are illustratively used for the sake of convenience. Therefore, the disclosure is not limited by the terms as used below.

Further, in the following description of the disclosure, various embodiments will be described using terms and names employed in some communication standards (e.g., 3rd generation partnership project (3GPP)) only for the sake of illustration. However, various embodiments of the disclosure may be easily applied to other communication systems through modifications.

<FIG> is a diagram illustrating an example of a <NUM> system architecture using expression of a reference point in a wireless communication system.

Referring to <FIG>, the <NUM> system architecture may include various elements (i.e., network functions (NF)), and <FIG> illustrates some of the various elements such as an authentication server function (AUSF), a (core) access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF), a unified data management (UDM), a data network (DN), a user plane function (UPF), a (radio) access network ((R)AN), and a terminal, that is, a user equipment (UE).

Each NF may support a function as follows.

Specifically, the AMF may support functions such as signaling between CN nodes for mobility among 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), termination of a NAS signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, an idle mode UE reachability (including controlling and performing of paging retransmission), mobility management control (subscription and policy), supporting an intra-system mobility and inter-system mobility, supporting network slicing, selecting an SMF, lawful intercept (with respect to an AMF event and an interface to an L1 system), providing delivery of a session management (SM) message between a UE and an SMF, a transparent proxy for routing an SM message, access authentication, access authorization including checking of the right of roaming, providing delivery of an SMS message between a UE and an SMSF, a security anchor function (SAF), and/or security context management (SCM), and the like.

Some or all of the functions of an AMF may be supported in a single instance of a single AMF.

Specifically, the SMF supports functions such as session management (e.g., establishing, correcting, and releasing a session including maintaining a tunnel between a UPF and an AN node), allocating and managing a UE IP address (selectively including authentication), selecting and controlling a UP function, setting a traffic steering for routing traffic from a UPF to an appropriate destination, termination of an interface for policy control functions, performing the control part of a policy and quality of service (QoS), lawful intercept (with respect to an SM event and an interface to an L1 system), termination of an SM part of a NAS message, downlink data notification, an initiator of AN-specific SM information (transferring to an AN through N2 via an AMF), determining an SSC mode of a session, a roaming function, and the like.

Some or all of the functions of an SMF may be supported in a single instance of a single SMF.

The FE includes a UDM FE that is in charge of processing location management, subscription management, a credential, and the like, and includes a PCF that is in charge of policy control. The UDR stores data required for functions provided by the UDM-FE and stores a policy profile required by the PCF. The data stored in the UDR includes user subscription data including a subscription identifier, a security credential, access and mobility related subscription data, and session-related subscription data, and may include policy data. The UDM-FE supports functions such as accessing subscription information stored in the UDR, authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, SMS management, and the like.

Specifically, the UPF may support functions such as an anchor point for intra/inter RAT mobility, an external PDU session point of interconnection (interconnect) to a data network, packet routing and forwarding, a user plane part of implementation of policy rules and packet inspection, lawful intercept, reporting the amount of traffic used, an uplink classifier for supporting routing of a traffic flow to a data network, a branching point for supporting a multi-homed PDU session, QoS handling for a user plane (e.g., packet filtering, gating, implementing uplink/downlink rate), verifying uplink traffics (SDF mapping between a service data flow (SDF) and a QoS flow), marking a transport level packet in an uplink and downlink, buffering a downlink packet, triggering a downlink data notification, and the like. Some or all of the functions of a UPF may be supported in a single instance of a single UPF.

The gNB supports functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources (i.e., scheduling) to a UE in an uplink/downlink), Internet protocol (IP) header compression, encryption of a user data stream and integrity protection, selecting an AMF in the case of attachment of a UE if routing to the AMF is not determined based on information provided to a UE, user plane data routing to UPF(s), control plane information routing to an AMF, connection setup and release, scheduling and transmitting a paging message (generated from an AMF), scheduling and transmitting system broadcast information (generated from an AMF or operating and maintenance (O&M)), measuring for mobility and scheduling and configuring a measurement report, transport level packet marking in an uplink, session management, supporting network slicing, QoS flow management and mapping to a data radio bearer, supporting a UE in an inactive mode, distributing a NAS message, a NAS node selecting function, sharing a radio access network, dual connectivity, tight interworking between an NR and a E-UTRA, and the like.

Although an unstructured data storage network function (UDSF), a structured data storage network function (SDSF), a network exposure function (NEF), and an NF repository function (NRF) are not illustrated for explicit description in <FIG>, all NFs illustrated in <FIG> may interoperate with a UDSF, an NEF, and an NRF when needed.

For ease of description, although <FIG> illustrates a reference model in the case in which a UE accesses a single DN using a single PDU session, the disclosure is not limited thereto.

The UE may simultaneously access two data networks (i.e., a local data network and a central data network) using multiple PDU sessions. In this instance, two SMFs may be selected for different PDU sessions. Each SMF may have a capability of controlling both a local UPF and a central UPF in a PDU session.

In addition, the UE may simultaneously access two data networks (i.e., a local data network and a central data network) provided in a single PDU session.

In 3GPP system, a conceptual link that connects NFs in the <NUM> system is defined as a reference point. Examples of a reference point included in the <NUM> system architecture expressed in <FIG> are as follows.

<FIG> is a diagram illustrating the configuration of a network entity in a wireless communication system according to various embodiments.

A network entity of the disclosure is a concept including a network function according to the implementation of a system. The ending 'unit' or '-er' used hereinafter may refer to a unit by which at least one function or operation is performed, and may be embodied as hardware, software, or a combination of hardware and software.

The network entity according to various embodiments of the disclosure may include a communication unit <NUM>, a storage <NUM>, and a controller <NUM> that controls the overall operation of a network entity <NUM>.

The communication unit <NUM> performs signal transmission and reception with other network entities. Accordingly, a part or all of the communication unit <NUM> may be referred to as a 'transmitter' <NUM>, a 'receiver' <NUM>, or a 'transceiver' <NUM>.

The storage <NUM> stores data, such as a basic program, an application program, configuration information, and the like for operating the network entity <NUM>. The storage <NUM> may be embodied as a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. The storage <NUM> provides data stored therein in response to a request from the controller <NUM>.

The controller <NUM> controls the overall operation of the network entity <NUM>. For example, the controller <NUM> performs signal transmission and reception via the communication unit <NUM>. In addition, the controller <NUM> records data in the storage <NUM>, and reads the recorded data. The controller <NUM> may perform the functions of a protocol stack that the communication standard requires. To this end, the controller <NUM> may include a circuit, an application-specific circuit, at least one processor, or micro-processor, or may be a part of a processor. In addition, a part of the communication unit <NUM> and the controller <NUM> may be referred to as a communication processor (CP). The controller <NUM> may control the network entity <NUM> to perform any one of the operations disclosed in various embodiments of the disclosure.

The communication unit <NUM> and the controller <NUM> may not necessarily need to be embodied as separate modules, and may be embodied as a single component in the form of a single chip or a software block. The communication unit <NUM>, the storage <NUM>, and the controller <NUM> may be electrically connected. In addition, the operations of the network entity <NUM> may be implemented by including the storage <NUM> that stores corresponding program code in the network entity <NUM>.

The network entity <NUM> may include a network node, and may be one of a base station (RAN), an AMF, an SMF, a UPF, an NF, an NEF, an NRF, a CF, an NSSF, a UDM, an AF, an AUSF, an SCP, a UDSF, an NWDAF, a context storage, an OAM (operations, administration, and maintenance), an EMS, a configuration server, and an identifier (ID) management server.

The <NUM>rd generation partnership project (3GPP) that works on the standard of the cellular mobile communication names a new core network structure '<NUM> core (5GC)' and proceeds with standardization in order to evolve the legacy <NUM> long term evolution (LTE) system to a <NUM> system.

Compared to an evolved packet core (EPC) that is a network core for the legacy <NUM>, the 5GC may support a differentiated function as follows.

First, the 5GC introduces a network slice function. Requirements for the <NUM>, the 5GC needs to support various types of UE and services. Examples of the <NUM> service may include an enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine type communications (mMTC). Such UE/service may require different requirements from each core network. For example, in the case of an eMBB service, a high data transmission speed (data rate) is required, and in the case of a URLLC service, high reliability and low latency are required. Technology provided to satisfy such various service requirements is a network slice scheme. A network slice is a method of configuring multiple logical networks via virtualization of a single physical network, and each network slice instance (NSI) may have a characteristic different from one another. Therefore, each NSI may have a network function (NF) appropriate for its characteristic, and thus various service requirements may be satisfied. Various <NUM> services may be efficiently supported by allocating an NSI appropriate for the characteristic of a service that each UE requires.

Second, the 5GC may easily support a network virtualization paradigm via separating a mobility management function and a session management function. In the legacy <NUM> LTE, all UEs may receive a service over a network by exchanging signaling with single core equipment named 'mobility management entity' (MME) that is in charge of registration, authentication, mobility management and session management functions. However, in the <NUM>, the number of UEs is explosively increased and mobility and traffic/session characteristic that needs to be supported for each type of UE is subdivided. Accordingly, when single equipment such as an MME supports all functions, scalability that adds an entity for each function needed may deteriorate. Therefore, based on a structure that separates a mobility management function and a session management function in order to improve scalability from the perspective of a signaling load and the function/implementation complexity of core equipment that is in charge of a control plane, various functions are being developed.

Various embodiments of the disclosure provide a method and apparatus for providing a low-latency location information service in a wireless communication system. A high-precision and low-latency location information service that the <NUM> service requires may need a service response time less than or equal to <NUM> second. In the case of the discontinuous reception (DRX) cycle of a UE, <NUM> seconds is default for a voice over LTE (VoLTE) UE. Accordingly, if such DRX cycle is maintained, requirements of the high-precision and low-latency location information service may not be satisfied. In the case in which a request for the high-precision and low-latency location information service is received, various embodiments of the disclosure may provide a method and apparatus for providing a location information service that satisfies the requirements of a low-latency service response time.

According to various embodiments of the disclosure, in order to satisfy the requirements of the location information service, by shortening a period that periodically inspects a paging message in an idle state of a UE, a low-latency location information service may be provided even in the case in which the UE is in the idle state.

<FIG> is a diagram illustrating a network structure (including an LMF) that provides a core network location information service and an interface in a wireless communication system according to various embodiments of the disclosure.

Specifically, <FIG> illustrates a network architecture that supports a location measurement service in a wireless communication system according to various embodiments of the disclosure. <FIG> illustrates the network structure (or the network architecture) of the <NUM> system and an interface according to various embodiments.

Referring to <FIG>, the network structure of the <NUM> system may include a user equipment (UE), a radio access network ((R)AN), a user plane function (UPF), a data network (DN), an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a network slice selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), a policy control function (PCF), a unified data management (UDM), an application function (AF), or the like.

According to various embodiments of the disclosure, the UE may be a terminal. The AMF is a network function that manages the mobility of a UE. The SMF is a network function that manages a packet data network connection provided to a UE. The connection is referred to as a protocol data unit (PDU) session. The PCF is a network function that applies the service policy and the charging policy of a mobile communication operator for a UE, and a policy associated with a PDU session. The unified data management (UDM) is a network function that stores and manages information associated with a subscriber. The NEF is capable of accessing information that manages a UE in the <NUM> network, and may be connected to <NUM> core network functions (NF) so as to transfer information associated with a UE to corresponding NFs and to report information associated with the UE to the outside, such as subscribing a mobility management event of the corresponding UE, subscribing a session management event of the corresponding UE, requesting for session-related information, configuring charging information of the corresponding UE, requesting for changing a PDU session policy for the corresponding UE, and the like. The <NUM>-radio access network (<NUM>-RAN) is a base station that provides a radio communication function to a UE. In <FIG>, it is illustrated as a (R)AN. The user plane function (UPF) may act as a gateway that transfers a packet transmitted or received. The UPF is connected to a data network (DN), and may perform a function of transferring a data packet produced from the <NUM> system to an external data network. The UPF may be connected to, for example, a data network connected to the Internet, and may perform routing a data packet transmitted from a UE to the Internet.

The <NUM> system may provide a high-precision and low-latency location information service.

Referring to <FIG>, a location management function (LMF) may be a network function that is in charge of generally managing resources needed for providing the location information of a UE registered in the <NUM> system. The LMF calculates the location information of a UE or finally identifies the location of the UE, and reports the same to a global mobile location center (GMLC).

The LMF may receive a location information request associated with an objective UE from the AMF via an Nlmf interface. The LMF may exchange location information needed for a UE-based positioning method or a UE-assisted positioning method, and such protocol is referred to as an LTE positioning protocol.

According to various embodiments of the disclosure, the protocol named 'LPP' is a protocol used between a UE and a location information positioning server (an LMF or an LMC in various embodiments of the disclosure), for the UE-based positioning method or the UE-assisted positioning method. The LPP protocol is a protocol that is not necessarily limited to the <NUM> LTE, and may be used for <NUM> new radio (NR).

The LMF may determine a positioning result on geographical co-ordinates described in the technical document TS <NUM> that is the 3GPP standard. The positioning result determined by the LMF may include the speed of a UE. In addition, the LMF may perform the following functions.

In the embodiment of <FIG>, the gateway mobile location centre (GMLC) may provide a function needed for providing a location information service (location service). One or more GMLCs may be present in a single operator. A single GMLC is a first node that an external LCS client accesses when the external LCS client accesses an operator network. An AF and an NF in the <NUM> core (5GC) network that accesses the GMLC may directly access the GMLC, or may access the GMLC via an NEF. The GMLC may request routing information and the personal information of an objective UE from an UDM via a Nudm interface. After identifying the authorities of the AF and the external LCS client, and verifying the personal information of an objective UE, the GMLC may forward a location information request to the serving AMF via a Namf interface. In the case in which the UE performs roaming, the GMLC may forward a location information request to a PLMN of another operator network. Before transmitting a positioning result associated with the objective UE, the personal information configuration of the UE needs to be identified, and the personal information configuration always needs to be identified in a home operator network of the UE. A visited GMLC (VGLMC) is a GMLC that is present in a serving operator network of an objective UE.

A home GMLC (HGLMC) is a GMLC that is present in a home operator of an objective UE and performs a function of identifying the personal information of the objective UE.

<FIG> is a diagram illustrating a network structure (including an LMC) that provides a RAN-based location information service and an interface in a wireless communication system according to various embodiments of the disclosure.

Particularly, <FIG> is a diagram illustrating a RAN-based location information service providing structure in a wireless communication system according to various embodiments of the disclosure. The embodiment of <FIG> shows a network configuration that is different from the embodiment of <FIG> that provides a location information service in the <NUM> system.

An LMF that performs a function of measuring location information in the embodiment of <FIG> is configured to be connected to an AMF in the <NUM> core network via an interface. However, in the embodiment of <FIG>, a location management component (LMC) performs a function of measuring the location information of a UE, and the LMC is located in a RAN. The LMC of <FIG> performs the function of an LMF which has been described in the embodiment of <FIG>. However, the LMC is present in an NG-RAN, and the LMC is connected to a gNB or ng-gNB via an L-IF. A UE, a GMLC, a UDM, an LCS client, an AF, and an NEF in the embodiment of <FIG> may perform the same functions which have been described in the embodiment of <FIG>. In the case in which the GLMC receives a location information request, the GMLC transfers the location information request to the AMF, and the AMF transfers the location information request to an NG-RAN via an N2 reference point. A gNB (or ng-gNB) transfers the received location information request to the LMC via the L-IF.

The location management component (LMC) is a network function that is in charge of generally managing resources needed for providing the location information of a UE. The LMC may calculate the location information of a UE or may finally identify the location of the UE, and may report the same to a global mobile location center (GMLC).

The LMC may receive the location information request associated with an objective UE that is transferred to the NF-RAN from the AMF via the N2 reference point. In the case in which the LMC is present as a separate NF in the NG-RAN as illustrated in <FIG>, the LMC may be connected to a gNB via the L-IF interface. The gNB transfers, to the LMC, the location information request received from the AMF via the N2 reference. The LMC receives the location information request forwarded from the AMF via the gNB. The function of the LMC may be implemented in the gNB or NG-gNB, and in this instance, the L-IF is present inside the gNB or NG-gNB and may not be exposed to the outside.

The LMC may exchange location information needed for a UE-based positioning method or a UE-assisted positioning method, and such protocol is referred to as an LTE positioning protocol. According to various embodiments of the disclosure, the protocol named 'LPP' is a protocol used between a UE and a location information positioning server (an LMF or an LMC in various embodiments of the disclosure) for the UE-based positioning method or UE assisted positioning method. The LPP protocol is a protocol that is not necessarily limited to the <NUM> LTE, and may be used for the <NUM> NR. The LMF determines a positioning result on geographical co-ordinates described in TS <NUM> that is the 3GPP technical document. The positioning result determined by the LMC may include the speed of a UE.

In addition, the LMC may perform the following functions.

<FIG> is a diagram illustrating a system structure wherein an LMC and an LMF coexist in a wireless communication system according to various embodiments of the disclosure.

Specifically, <FIG> is a diagram illustrating a <NUM> system structure showing a structure in which a location management component (LMC) and a location management function (LMF) are present in a single serving operator. The LMC performs a function of a local LMF.

The descriptions associated with individual network functions are identical to the functions that have been described with reference to <FIG> and <FIG>. In the system structure of the embodiment of <FIG>, an AMF may be aware of whether an LMC and an LMF are coexist. In addition, when receiving a location information request, the AMF may determine whether to use an LMC location information service or an LMF location information service in consideration of whether a protocol and function provided by a UE is provided, a precision level and positioning method provided by the LMC and the LMF, a location information request service quality included in a location information request message, a type of service and a service identifier, a location information service identifier, a location information response time, required precision of location information, and the like.

In the <NUM> service, there are requirements in associated with high-precision and low-latency positioning, as shown in Table <NUM> below.

Table <NUM> below lists requirements associated with high-precision and low-latency positioning.

Referring to Table <NUM>, in the case of positioning service levels <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, a positioning service latency is <NUM> second. That is, the positioning service levels <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may requires a response time with low-latency.

<FIG> and <FIG> are diagrams illustrating a response time in association with a location information service (positioning service) in the case in which a UE is in a connected state or the UE is in an idle state in a wireless communication system.

The problem of the current technology is that a UE in the idle state is incapable of satisfying a service response time of approximately <NUM> second. In the case in which the UE is in the idle state, a provided service response time does not satisfy a service response time required based on a discontinuous reception (DRX) cycle.

For ease of description, <FIG> illustrates a response time associated with a location information service (positioning service) in the case in which a UE is in the connected state, and <FIG> illustrates a response time associated with a location information service (positioning service) in the case in which a UE is in the idle state.

Referring to <FIG>, T is the total time spent on a location information service, P is the time spent on a UE positioning procedure. The UE in the connected state performs UE positioning-related measurement and calculation of an estimated location immediately in response to a location information request, and thus T that is the total time spent on the location information service and P that is the time spent on the UE positioning procedure are the same.

<FIG> illustrates the time taken from the point in time of receiving a service location information service request and to the point in time of responding to the request for the location information service, in the case in which the UE is in the idle state. Referring to <FIG>, in the case in which the UE is in the idle state, the total time T spent on the total location information service may be calculated as shown in Equation <NUM> below.

In Equation <NUM>, T is the total time spent on a location information service. W is the time spent on standing by, staying in the idle state, until the UE requests a service. S is the time spent on performing a service request procedure after the UE awakes upon receiving a paging message. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning-related measurement and calculation of an estimated location.

In the case in which the UE is in the connected state, the total time spent on a location information service is the same as the time spent on performing a UE positioning procedure. Equation <NUM> below expresses the total time T spent on a location information service in the case in which the UE is in the connected state.

In Equation <NUM>, T is the total time spent on a location information service. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning-related measurement and calculation of an estimated location.

For example, in the case in which the UE is in the connected state and the time P spent on performing the UE positioning procedure is <NUM> seconds, T = <NUM>, and a location information service may be provided within <NUM> second that is a required service response time.

In the case in which the UE is in the idle state, the time spent on performing a UE positioning procedure is P, the time spent on a service request procedure is S, the time spent while the UE stands by in the idle state is W, and a set DRX cycle is D, W may be greater than or equal to <NUM> and less than or equal to D. In the case in which the UE is in the idle state, the total time T spent on a location information service may be calculated as shown in Equation <NUM> below.

In Equation <NUM>, T is the total time spent on a location information service. W is the time spent while the UE stays in the idle state and stands by until requesting for a service. S is the time spent on performing a service request procedure after the UE awakes upon receiving a paging message. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning-related measurement and calculation of an estimated location.

D is a set DRX cycle. For example, in the case in which S = <NUM> and P = <NUM>, the total time T spent on the location information service may be calculated as shown in Equation <NUM> below.

In Equation <NUM>, T is the total time spent on a location information service.

If it is assumed that a required service response time is <NUM> second, and the time spent on arrival of a location information service request is uniform, the probability that the total time spent on the location information service be less than or equal to a service response time, that is, the probability that the condition of a required service response time be satisfied may be as given in Equation <NUM> below.

In Equation <NUM>, T is the total time spent on a location information service. P is the probability that the total time spent on the location information service be less than or equal to a required service response time, that is, the probability that a required service response time be satisfied.

Based on Equation <NUM>, in the case in which the UE is in the idle state, if <NUM> location information services that require a service response time of <NUM> second are present, a response time for <NUM> requests will be <NUM> or more seconds and service requirements may not be satisfied.

Hereinafter, an embodiment of <FIG> provides a method of solving a problem in that the probability that a service requirement not be satisfied is high in the case in which a UE is in the idle state as described in the embodiment of <FIG>.

<FIG> is a diagram illustrating a response time in association with a location information service (positioning service) in the case in which a UE is in an idle state in a wireless communication system according to various embodiments of the disclosure.

Specifically, in order to solve the problem of the embodiment of <FIG>, the embodiment of <FIG> provides a scheme of re-configuration a DRX cycle in the state in which the UE is the idle state.

In Equation <NUM>, W is the time spent while the UE stands by, staying in the idle state, until requesting for a service. S is the time spent on performing a service request procedure after the UE awakes upon receiving a paging message. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning-related measurement and calculation of an estimated location. R is a required response time.

In the case in which the time spent while the UE stands by in the idle state is W and a set DRX cycle is D, W is greater than <NUM> and less than D. W may have a value in the range of <NUM> to D, and thus in the case in which the value of W is set to D in order to satisfy the requirements of a service, this may be as given in Equation <NUM> below.

In Equation <NUM>, D is a set DRX cycle, and S is the time spent on performing a service request procedure after the UE awakes upon receiving a paging message. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning-related measurement and calculation of an estimated location. R is a required response time.

If Equation <NUM> is transposed to the left-hand side of D, it is equal to Equation <NUM> as given below.

In order to satisfy the requirements of a service, that is, a required service response time, a DRX cycle D may be set to a value of R - ( S + P ). For example, when it assumed that R = <NUM> seconds, S = <NUM> seconds, and P = <NUM> seconds, if D is set to D = <NUM> seconds, the requirements of the service may be satisfied.

<FIG> is a diagram illustrating a process of re-configuration a DRX cycle of a UE in a wireless communication system according to various embodiments of the disclosure.

Specifically, in the embodiment of <FIG>, there is provided a process of reconfiguration a DRX cycle of an objective UE <NUM> in the case in which an AMF <NUM> receives a location information service request including the requirements of a service response time, or in the case in which the AMF <NUM> receives a location information service request from which the requirements of a service response time are inferable.

Operations 801a to 801c correspond to a process in which a location information service client transfers a location information service request. The request for a location information service may be initiated by a UE <NUM>, a base station <NUM>, or an external location service (LCS) client.

In operation 801a, the UE <NUM> transmits a UE-originated location information request (mobile originated location request) message to the AMF <NUM>. In the case in which the UE <NUM> initiates a location information service, the UE <NUM> may transfer a location information request to the AMF <NUM> via an NAS message in operation 801a.

In operation 801b, the (R)AN <NUM> transmits a base station induced location information request (RAN induced location request) message to the AMF <NUM>. In operation 801b, the base station <NUM> transfers a location information request to the AMF <NUM> via an N2 message.

In operation 801c, a GMLC or NEF <NUM> transmits a UE terminated location information request (a mobile terminated location request) message to the AMF <NUM>. In operation 801c, an external LCS client of a system transfers a location information request to the AMF <NUM> via the GMLC or NEF <NUM>. In the case in which the GMLC <NUM> receives the location information service request, the GMLC <NUM> transfers a UE context management (UECM) obtaining request to a UDM <NUM>. The GMLC <NUM> receives, from the UDM <NUM>, the address or the identifier of the AMF <NUM> that manages an objective UE of which the location is requested. The GMLC <NUM> transfers the location information request to the AMF <NUM>.

The AMF <NUM> receives a location information request message from at least one of the UE <NUM>, the base station <NUM>, or the GMLC <NUM>. In addition, the AMF <NUM> may receive a location information request message from the NEF <NUM>. In addition, the AMF <NUM> may receive a location information subscription request from the UDM <NUM>. A location provision request message or a subscription request message associated with a location provision service report received by the AMF <NUM> includes the information as follows.

In operation <NUM>, the AMF <NUM> determines to update a UE configuration based on a location information QoS (location QoS), and a <NUM> enhanced positioning area. According to an embodiment, the location information QoS includes location precision, a service level, a response time, and the like, and the UE configuration includes a DRX cycle. In operation <NUM>, the AMF <NUM> receives the location information request in operations 801a to 801c. The time P spent on performing a positioning procedure of the UE <NUM> and the time S spent while the UE performs a service request procedure are set in advance in the AMF <NUM>. Based on a required response time for the location information service request and the values set in advance, the AMF <NUM> calculates a DRX cycle that needs to be set for the UE <NUM>. Alternatively, the AMF <NUM> may obtain, from information mapped in advance, a service response time required by the type of location information service or a service identifier, and may calculate a DRX parameter (e.g., a DRX cycle) that needs to be set for the UE based on the service response time or may obtain the same from information set in advance.

Subsequently, in operations <NUM> to <NUM>, a UE configuration update procedure is performed. When it is determined that a DRX parameter currently set is incapable of satisfying a service response time of a location information service request that may be continuously provided in the future, the AMF <NUM> determines to change the configuration of the DRX parameter. In the case in which the AMF <NUM> determines to change the DRX parameter, the AMF <NUM> initiates the UE configuration update procedure.

In operation <NUM>, the AMF <NUM> transmits a UE configuration update command message to the UE <NUM>. According to an embodiment, the UE configuration update command message includes DRX parameters, an indication of re-registration, and the like. In operation <NUM>, the AMF <NUM> calculates a DRX cycle length required for providing a low-latency location information service, and determines a DRX parameter to be transferred to the UE <NUM>. When the AMF <NUM> desires to update a parameter related to access ad mobility for the UE <NUM>, the AMF <NUM> initiates the UE configuration update procedure. In order to change a UE specific DRX cycle for the UE <NUM>, the AMF <NUM> performs the UE configuration update procedure so that the UE <NUM> re-performs a registration procedure in the connected state. When performing the UE configuration update procedure, the AMF <NUM> transmits, to the UE <NUM>, an indicator indicating initiation of the registration procedure. The procedure may be transferred to the UE via 3GPP access or Non-3GPP access. The AMF <NUM> transfers, to the UE <NUM>, the UE configuration update command including a DRX parameter (e.g., including a DRX cycle length) proposed by the AMF <NUM>, and an indicator indicating initiation of the registration procedure. In the case of transferring the UE configuration update command message, if the AMF <NUM> transfers the UE configuration update command to the UE <NUM>, the AMF <NUM>, to the UE <NUM>, one or more UE parameters, for example, a configuration change indicator, a globally unique temporary identifier (<NUM>-GUTI), a tracking area identity (TAI) list, allowed network slice selection assistance information (NSSAI), allowed NSSAI mapping information, a rejected S-NSSAI list, mobility restriction information, local access data network (LADN) information, mobile initiated connection only (MICO), access classification definition information defined by an operator, and the like, together with a DRX parameter.

In the case in which the DRX parameter (e.g., including a DRX cycle defined for each UE) proposed by the AMF <NUM> is transferred to the UE <NUM>, the UE <NUM> may select a parameter that is acceptable by the UE <NUM> from among the "DRX parameters proposed by the AMF <NUM>" received from the AMF <NUM>, and may set the same as a DRX parameter requested by the UE <NUM>.

The AMF <NUM> calculates a DRX cycle length required for providing a low-latency location information service, draws a DRX parameter to be transferred to the UE <NUM>, and transmits, to the RAN <NUM>, a request for configuring the DRX parameter for the UE <NUM> in operation <NUM>.

In operation <NUM>, the UE <NUM> transmits a UE configuration update complete message to the AMF <NUM>. In the case in which the UE configuration update indicator that the UE <NUM> receives in operation <NUM> requests the UE to transmit a response message to the UE configuration update command, the UE <NUM> transfers the UE configuration update complete message to the AMF <NUM> in operation <NUM>. In the case in which the UE <NUM> selects a DRX parameter that is acceptable by the UE <NUM> from among the DRX parameters transferred from the AMF <NUM>, the UE <NUM> may transfer the UE configuration update complete message including the list of DRX parameters that the UE <NUM> allows.

In operation <NUM>, the AMF <NUM> transmits a Nudm_SDM_Info service message to the UDM <NUM>. In operation <NUM>, the AMF <NUM> stores a DRX parameter defined for each UE, which is to be set for the UE <NUM>, in the UDM <NUM>.

In operation <NUM>, the AMF <NUM> transmits a RAN update (update RAN) message to the (R)AN <NUM>. After performing operation <NUM>, the AMF <NUM> may proceed with operation <NUM>. Alternatively, the AMF <NUM> may not perform operations <NUM>, <NUM>, and <NUM>, and may only proceed with operation <NUM>. The AMF <NUM> sets a DRX parameter that is calculated and determined for the UE <NUM> in operation <NUM>, which is to be proposed to the RAN <NUM>, and may transfer the DRX parameter proposed by the AMF <NUM> to the RAN <NUM>. In the case in which the RAN <NUM> receives a DRX parameter, the RAN <NUM> may change a configuration of the DRX parameter transferred to the UE <NUM>. Particularly, the RAN <NUM> determines a DRX parameter to be set for the UE <NUM>, and transfers an RRC-reconfiguration message to the UE <NUM> so as to set a DRX cycle defined for each UE.

In operation <NUM>, the UE <NUM> decides to re-configure a DRX parameter. In the case in which parameters for which the UE <NUM> needs to change an RRC configuration in an AS layer are present among DRX parameters received via the UE reconfiguration update command (UE configuration update command) message, the UE <NUM> may transfer an indicator indicating change of a DRX configuration parameter to the AS layer in the UE <NUM>. The UE <NUM> may store or change a DRX set value in the AS layer.

In operation <NUM>, the UE <NUM> transmits a registration request message to the AMF <NUM>. According to an embodiment, the registration request message includes DRX parameters. The UE <NUM> may finally determine a DRX parameter that the UE <NUM> is to use from among the DRX parameters received from the AMF <NUM>. The UE <NUM> determines to update a registration procedure, and transmits the registration request message including the determined DRX parameter to the AMF <NUM>. The AMF <NUM> receives a UE request DRX parameter included in the registration request message. The DRX parameter includes an idle state DRX cycle. The value of the idle state DRX cycle is a value equal to the value of D in above-described Equation <NUM>, and may be a value for determining the maximum value of W of the location information service.

The DRX cycle in the idle state may correspond to both cases, that is, the case in which the UE <NUM> is in an CM-IDLE state and the case in which the UE <NUM> is in an RRC inactive state. After the UE <NUM> determines a DRX cycle value to be used by the UE <NUM> based on the DRX parameter that the AMF <NUM> proposes and is received via the UE configuration update command message, and determines to use the DRX cycle value, in the case in which the UE <NUM> transfers a registration request message including a UE requested DRX parameter to the AMF <NUM>, the AMF <NUM> determines an allowed DRX parameter according to the UE requested DRX parameter transmitted by the UE <NUM>. When determining the DRX parameter, the AMF <NUM> may adopt the value requested by the UE <NUM>, as it is. Alternatively, the AMF <NUM> changes the DRX parameter value requested by the UE <NUM> according to an operator policy.

In the case in which the UE <NUM> is an RRC inactive with CM-CONNECTED, the UE <NUM> may apply a DRX cycle broadcasted by the RAN <NUM>. Alternatively, the UE <NUM> may set a DRX cycle set by the RAN <NUM>.

In operation <NUM>, the AMF <NUM> transmits a registration accept message to the UE <NUM>. According to an embodiment, the registration accept message includes an accepted DRX parameter. The AMF <NUM> transfers the adopted DRX parameter that the AMF <NUM> finally determines to the UE <NUM>. After operation <NUM>, the AMF <NUM> transmits a DRX parameter to the RAN <NUM> as shown in operation <NUM>, and the RAN <NUM> may change a set value for the DRX parameter transferred to the UE <NUM> via broadcasting. Alternatively, the RAN <NUM> may change an RRC configuration associated with a DRX parameter defined for each UE, with respect to the corresponding UE <NUM>.

<FIG> is a diagram illustrating a process of performing a UE configuration update procedure after performing a UE positioning procedure in a wireless communication system according to various embodiments of the disclosure.

In operation 901a to 901c, an AMF <NUM> receives a location information service request as described in operations 801a to 801c of the embodiment of <FIG>.

In operation 901a, a UE <NUM> transmits a UE-originated location information request (mobile originated location request) message to the AMF <NUM>.

In operation 901b, an (R)AN <NUM> transmits a base station induced location information request (RAN induced location request) message to the AMF <NUM>.

In operation 901c, a GMLC or NEF <NUM> transmits a UE terminated location information request (mobile terminated location request) message to the AMF <NUM>.

In operations 902a to 902c, a LMC-based location information service request function is performed. Based on the location information request message received in operation 901a to 901c and existing information available for the AMF <NUM>, the AMF <NUM> may determine information included in an N2 location control request.

The information available for the AMF <NUM> are as follows.

Based on information available for the AMF <NUM>, information to be included in a message (e.g., a N2 location control request) related to location information to be requested from the RAN <NUM> is determined.

The information included in the N2 location control request are as follows.

In operation 902a, the AMF <NUM> transmits an N2 location information request (N2 location request) message to the (R)AN <NUM>.

The AMF <NUM> transfers the N2 location control request message to the RAN <NUM>.

To measure the time spent on UE positioning, the AMF <NUM> records the times at which the identifier of a request of a message transferred to the AMF <NUM> or a transaction identifier, the identifier of the UE <NUM>, and a message for requesting the RAN <NUM> node to measure location information are transmitted.

In order to measure, by the RAN <NUM> or the LMC <NUM>, the time spent on UE positioning, the AMF <NUM> includes an indicator indicating measurement of a positioning measurement time required and report of the same (i.e., a UE positioning time required report indicator) in the N2 location control request and transmits the same. The RAN <NUM> or the LMC <NUM> that receives the UE positioning time required report indicator measures the time spent on UE positioning, includes the time actually spent on UE positioning in a location measurement response message or a location measurement report message and transfers the same.

In operation 902b, a UE positioning procedure is performed.

The RAN node <NUM> that receives the N2 location control request message determines, based on information included in the location control request message, the following items.

In the case in which an LMC capable of performing a requested N2 location control request is present, the RAN <NUM> initiates a positioning request procedure of the LMC. Via a positioning request initiating message, a content included in the N2 location control request message received from the AMF is transferred. The content included in the control request message is as follows.

The LMC <NUM> that receives a request for initiating a positioning procedure determines a positioning procedure and performs the positioning procedure based on the content included in the message received from the RAN node <NUM>.

The UE <NUM> and the LMC <NUM> may perform the positioning procedure according to a positioning protocol (e.g., an LPP, or an LPP over an RRC (LPP over RRC)) or an LPP over a NAS (LPP over NAS). The positioning procedure may be performed as a procedure of determining a UE-based positioning method or as a procedure of a UE-assisted positioning method. According to the UE-based positioning method, the UE <NUM> directly calculates the location of a UE based on the location measurement information of the UE <NUM>. In the case in which the UE <NUM> measures an estimated location, the UE <NUM> reports, to the LMC <NUM>, the estimated location of the UE <NUM> that is calculated based on a location measurement protocol (e.g., an LPP).

According to the UE-assisted positioning method, the UE <NUM> reports, to the LMC <NUM> that is a location information server, measurement information needed for measuring the location of the UE <NUM>, and the LMC <NUM> calculates the estimated location of the UE <NUM> based on the location measurement information received from the UE <NUM>.

The LMC <NUM> that completes measuring the location of the objective UE <NUM> transfers a positioning report message to the NG-RAN <NUM>. The positioning report message may include the identifier of a request so that a receiver determines a location information report associated with a report corresponding to the corresponding request.

The positioning report message of the UE <NUM> may include the following content of the location information report according to the location information request associate with the UE <NUM>.

In the case in which the LMC <NUM> receives, via the RAN <NUM>, a UE positioning time required report indicator transferred from the AMF <NUM>, the LMC <NUM> calculates the time spent on performing UE positioning. In order to measure the time spent on performing UE positioning, the LMC <NUM> may record the time at which a UE positioning protocol (e.g., an LPP) is initiated, and measures the time spent on performing UE positioning by calculating the difference between the initiation time and the time at which the UE positioning protocol is completely performed.

In operation 902c, the (R)AN <NUM> transmits an N2 location information report (N2 location report) message to the AMF <NUM>. The AMF <NUM> receives the location information report from the base station <NUM>. The location information report may include information associated with the location information request that the base station <NUM> receives in operation 902a. The AMF <NUM> identifies the information associated with the location information request via a request identifier included in the location information request. The AMF <NUM> determines a node to which a report message or a response to the location information request is to be transmitted based on the information identified from the request identifier.

In operation 902c, in order to calculate the time that the AMF <NUM> spends on location information measurement, the AMF <NUM> records a location information request time, a UE identifier, and a location information request identifier, and receives a response corresponding thereto. The AMF <NUM> calculates the difference between the current time and the time at which location information is requested, so as to calculate the time spent on performing UE positioning.

Alternatively, in order to calculate, by the AMF <NUM>, the time spent on location information measurement, in the case in which a location information request includes a UE positioning time required report indicator, the AMF <NUM> may receive the time spent on performing UE positioning via a response message corresponding to the location information request or a UE location measurement report message. The AMF <NUM> may calculate the time spent on UE location measurement by adding the time spent on performing UE positioning in the LMC <NUM> or the RAN <NUM> and a backhaul network delay time.

A control plane backhaul network delay time may be the time spent on transferring a control message between the AMF <NUM> and the NG-RAN <NUM>. Measuring the control plane backhaul network delay time may be calculated by measuring a round trip delay time of an NG-AP that is a control plane interface between the AMF <NUM> and the NG-RAN <NUM>. Alternatively, that may be set in advance based on configuration information of a backhaul network installed between the AMF <NUM> and the NG-RAN <NUM>.

In operation <NUM>, the AMF <NUM> determines to update UE configuration based on a location information QoS (location QoS) and a <NUM> enhanced positioning area. According to an embodiment, the location information QoS includes location precision, a service level, a response time, and the like, and the UE configuration includes a DRX cycle.

As described above, Equation <NUM> is given as D + S + P <= R.

In operation <NUM>, the AMF <NUM> calculates a D value based on a P value, an R value, and an S value in Equation <NUM>. Specifically, the AMF <NUM> obtains the time (P in Equation <NUM>) spent on performing UE location measurement that includes measurement or calculation performed in operations 902a to 902c. In addition, in operations 901a to 901c, the AMF <NUM> obtains a location information service response time (R in Equation <NUM>) included in location information request service quality information included in the received location measurement request. The AMF <NUM> may obtain a service request performing time (S in Equation <NUM>) that is set and stored in the AMF <NUM>, that is, the time spent on performing a procedure in which the UE <NUM> is changed from a CM-IDLE state to a CM-CONNECTED state. Based on the P value, R value, and S value in Equation <NUM>, the AMF <NUM> calculates a DRX cycle length value (D in Equation <NUM>) that satisfies Equation <NUM>.

Subsequently, in operations <NUM> to <NUM>, a UE configuration update procedure is performed. The AMF <NUM> performs the UE configuration update procedure in operations <NUM> to <NUM>, and performs a procedure of changing a DRX parameter calculated by the AMF <NUM>. Alternatively, the AMF <NUM> performs operation <NUM> (the same procedure as operation <NUM> in the embodiment of <FIG>), and configures a DRX parameter for the RAN <NUM>.

In operation <NUM>, the AMF <NUM> transmits a UE configuration update command message to the UE <NUM>. According to an embodiment, the UE configuration update command message may include DRX parameters, an indication of re-registration, and the like. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the UE <NUM> transmits a UE configuration update complete message to the AMF <NUM>. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the AMF <NUM> transmits a Nudm_SDM_Info service message to the UDM <NUM>. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the AMF <NUM> transmits a RAN update message (update RAN) to the (R)AN <NUM>. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the UE <NUM> decides to re-configure a DRX parameter. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the UE <NUM> transmits a registration request message to the AMF <NUM>. According to an embodiment, the registration request message includes DRX parameters. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the AMF <NUM> transmits a registration accept message to the UE <NUM>. According to an embodiment, the registration accept message includes an accepted DRX parameter. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

<FIG> is a diagram illustrating a process of performing a UE configuration update procedure after performing a location information service using an LMF in a location information service structure including an LMF in a wireless communication system according to various embodiments of the disclosure.

Operation 1001a to 1001c are the same as operations 801a to 801c in the embodiment of <FIG>.

In operation 1001a, a UE <NUM> transmits a UE-originated location information request (mobile originated location request) message to an AMF <NUM>.

In operation 1001b, a (R)AN <NUM> transmits a base station induced location request (RAN induced location request) message to the AMF <NUM>.

In operation 1001c, a GMLC or NEF <NUM> transmits a UE terminated location information request (mobile terminated location request) message to the AMF <NUM>.

Operations 1002a to 1002c correspond to a location information measurement procedure using the LMF <NUM>.

In operation 1002a, the AMF <NUM> transmits a positioning request message to an LMF <NUM>. The AMF <NUM> transmits the positioning request message to the LMF <NUM>.

In operation 1002b, a UE positioning procedure is performed. The LMF <NUM> performs the UE positioning procedure together with the UE <NUM> by utilizing a UE positioning protocol (e.g., an LPP over an NAS (LPP over NAS)).

In operation 1002c, the LMF <NUM> transmits a positioning response message to the AMF <NUM>. When the LMF <NUM> completes positioning associated with the location of the UE <NUM>, the LMF <NUM> transmits the positioning response message to the AMF <NUM>.

To measure the time spent on positioning of the UE <NUM>, the AMF <NUM> may record the times at which the identifier of a request of a message transferred to the AMF <NUM> or a transaction identifier, the identifier of the UE <NUM>, and a message for requesting the LMF <NUM> to measure location information are transmitted.

In order to measure, by the LMF <NUM>, the time spent on UE positioning, the AMF <NUM> includes an indicator indicating measurement of a positioning measurement time required and report of the same (i.e., a UE positioning time required report indicator) in a positioning request (location determination request), and transmits the same. The RAN <NUM> or the LMF <NUM> that receives the UE positioning time required report indicator measures the time spent on performing UE positioning, and includes the time actually spent on UE positioning in a location measurement response message or a location measurement report message.

The content included in the positioning request message is as follows.

The LMF <NUM> that receives a request for initiating a positioning procedure determines, based on information included in the received message, a positioning procedure and performs the positioning procedure. The UE <NUM> and the LMF <NUM> performs the positioning procedure according to a positioning protocol (e.g., an LPP, or an LPP over an RRC (LPP over RRC)) or an LPP over a NAS (LPP over NAS). The positioning procedure may be performed as a procedure of determining a UE-based positioning method or as a procedure of a UE-assisted positioning method. According to the UE-based positioning method, the UE <NUM> directly calculates the location of the UE <NUM> via the location measurement information of the UE <NUM>. In the case in which the UE <NUM> measures an estimated location, the UE <NUM> reports, to the LMF <NUM> that is a location information server, the estimated location of the UE <NUM> that the UE <NUM> calculates according to a location measurement protocol (e.g., an LPP).

According to the UE-assisted positioning method, the UE <NUM> reports, to the LMF <NUM> that is the location information server, measurement information needed for measuring the location of the UE <NUM>, and the LMF <NUM> calculates the estimated location of the UE <NUM> based on the location measurement information received from the UE <NUM>.

The LMF <NUM> that completes measuring the location of the objective UE <NUM> transfers a positioning report message to the LMF <NUM>. The positioning report message includes the identifier of a request so that a receiver determines a location information report associated with a report corresponding to the corresponding request.

In the case in which the LMF <NUM> receives a UE positioning time required report indicator transferred from the AMF <NUM>, the LMF <NUM> calculates the time spent on performing UE positioning. In order to measure the time spent on performing UE positioning, the LMF <NUM> may record the time at which a UE positioning protocol (e.g., an LPP) is initiated, and may measure the time spent on performing UE positioning by calculating the difference between the initiation time and the time at which the UE positioning protocol is completely performed.

In operation 1002c, the LMF <NUM> transmits a positioning response message to the AMF <NUM>. The AMF <NUM> receives a location information report from the LMF <NUM>. The location information report may include information associated with the location information request that the LMF <NUM> receives in operation 1002a. The AMF <NUM> identifies the information associated with the location information request via a request identifier included in the location information request. The AMF <NUM> determines a node (e.g., the UE <NUM>, the base station <NUM>, the GMLC or NEF <NUM>) to which a report message or a response to the location information request is to be transmitted based on the information identified from the request identifier.

In operation 1002c, in order to calculate the time that the AMF <NUM> spends on location information measurement, the AMF <NUM> records a location information request time, a UE identifier, and a location information request identifier, and receives a response corresponding thereto. The AMF <NUM> calculates the difference between the current time and the time at which location information is requested, so as to calculate the time spent on performing UE positioning.

Alternatively, in order to calculate the time that the AMF <NUM> spends on location information measurement, in the case in which the location information request includes a UE positioning time required report indicator, the AMF <NUM> may receive the time spent on performing UE positioning via a response message corresponding to the location information request or a UE location measurement report message. The AMF <NUM> may calculate the time spent on UE location measurement by adding the time spent on performing UE positioning in the LMF <NUM> and an additional delay time between the AMF and the LMF.

In operation <NUM>, the AMF <NUM> determines to update a UE configuration based on a location information QoS (location QoS) and a <NUM> enhanced positioning area. According to an embodiment, the location information QoS includes location precision, a service level, a response time, and the like, and the UE configuration includes a DRX cycle.

In operation <NUM>, the AMF <NUM> calculates a D value based on a P value, an R value, and an S value in Equation <NUM>. Specifically, the AMF <NUM> obtains the time (P in Equation <NUM>) spent on performing UE location measurement that includes measurement or calculation performed in operations 1002a to 1002c. In addition, in operations 1001a to 1001c, the AMF <NUM> obtains a location information service response time (R in Equation <NUM>) included in location information request service quality information included in the received location measurement request. The AMF <NUM> may obtain a service request performing time (S in Equation <NUM>) that is set and stored in the AMF <NUM>, that is, the time spent on performing a procedure in which the UE <NUM> is changed from a CM-IDLE state to a CM-CONNECTED state. Based on the P value, R value, and S value in Equation <NUM>, the AMF <NUM> calculates a DRX cycle length value (D in Equation <NUM>) that satisfies Equation <NUM>.

In operation <NUM>, the AMF <NUM> transmits a UE configuration update command message to the UE <NUM>. According to an embodiment, the UE configuration update command message includes DRX parameters, an indication of re-registration, and the like. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

In operation <NUM>, the AMF <NUM> transmits a RAN update (update RAN) message to the (R)AN <NUM>. In operation <NUM>, the AMF <NUM> performs the same procedure as operation <NUM> in the embodiment of <FIG>.

<FIG> is a diagram illustrating a process in which an AMF requests RRC reconfiguration in the case in which an RRC inactive state is applied to a RAN in a wireless communication system according to various embodiments of the disclosure.

Operations 1101a to 1101c are the same as operations 801a to 801c in the embodiment of <FIG>.

In operation 1101a, a UE <NUM> transmits a UE-originated location information request (mobile originated location request) message to an AMF <NUM>.

In operation 1101b, a (R)AN <NUM> transmits a base station induced location information request (RAN induced location request) message to the AMF <NUM>.

In operation 1101c, a GMLC or NEF <NUM> transmits a UE terminated location information request (mobile terminated location request) message to the AMF <NUM>.

In operation <NUM>, in the case in which an RRC inactive state is applied to the NG-RAN <NUM>, the AMF <NUM> transmits a recommendation for RRC configuration update.

In operation <NUM>, the AMF <NUM> calculates a D value based on a P value, an R value, and an S value in Equation <NUM>. Specifically, the AMF <NUM> obtains the time (P of Equation <NUM>) spent on UE location measurement. In addition, in operations 1101a to 1101c, the AMF <NUM> obtains a location information service response time (R in Equation <NUM>) included in location information request service quality information included in the received location measurement request. The AMF <NUM> obtain a service request performing time (S in Equation <NUM>) that is set and stored in the AMF <NUM>, that is, the time spent on performing a state change procedure in which the UE <NUM> is changed from an RRC inactive state to an RRC active state. Based on the P value, R value, and S value in Equation <NUM>, the AMF <NUM> calculates a DRX cycle length value (D in Equation <NUM>) that satisfies Equation <NUM>.

D in Equation <NUM> is a set DRX cycle. S' is the time while the UE <NUM> spends on a state change from an RRC inactive state to an RRC active state. P is the time spent on a UE positioning procedure, that is, the time spent on UE positioning related measurement and calculation of an expected location. R is a required response time.

In operation <NUM>, the AMF <NUM> transmits a RAN configuration update (update RAN configuration) message to the (R)AN <NUM>. According to an embodiment, the RAN configuration update message includes an RRC configuration update indicator. The AMF <NUM> transmits an N2 message that corrects a RAN configuration to the RAN <NUM>. The N2 message includes a DRX parameter of which a configuration needs to be changed in the RAN configuration information. The DRX parameter includes an idle mode DRX cycle.

In operation <NUM>, an RRC re-configuration is performed. For example, RRC reconfiguration applied in an RRC inactive state is performed. The RAN <NUM> receives a message that changes a configuration of the RAN configuration. A message that changes a configuration of the RAN configuration may include a DRX parameter, and the DRX parameter may include an idle model DRX cycle. The RAN <NUM> changes a configuration for the set value of an idle mode DRX cycle applied in the RRC inactive state. In order to change the configuration of the UE <NUM>, the RAN <NUM> performs an RRC re-configuration procedure.

In operation <NUM>, the (R)AN <NUM> transmits, to the AMF <NUM>, a RAN configuration update acknowledgement (update RAN configuration ACK) message. The RAN node <NUM> that successfully performs the RRC re-configuration reports, to the AMF <NUM>, that a RAN configuration is successfully changed. The message reporting that a RAN configuration is changed may include re-set DRX parameters. The DRX parameter may include a newly set idle mode DRX parameter.

In operation 1106a, the AMF <NUM> stores an updated RAN mode (the update RAN mode). The AMF <NUM> stores the reset DRX parameters. When DRX parameter configuration is successfully completed, the AMF <NUM> stores the state associated with a low-latency response RRC mode together with the DRX parameter reset for the UE <NUM>. The stored DRX parameter and the low-latency response RRC mode state may be used by the AMF <NUM> during a movement procedure. When a new AMF performs a registration procedure for the UE <NUM>, a DRX parameter included in the context of the UE that a previous AMF stores and a response RRC mode state are transmitted to the new AMF. Based on the context information stored in relation to the DRX parameter of the UE <NUM>, the response RRC mode state, and a location information request, the new AMF may determine whether to perform an RRC configuration update on a new RAN. In the case in which the new AMF determines an RRC configuration, a RAN configuration information update procedure may be performed according to procedures <NUM> to <NUM> in the embodiment.

In operation 1106b, the AMF <NUM> transmits a Nudm_SDM_Info service message to the UDM <NUM>. The AMF <NUM> may store, in the UDM <NUM>, the state related to processing of a location information request associated with the UE <NUM>, a successfully set DRX parameter, and the state associated with a low-latency response RRC mode.

<FIG> is a diagram illustrating a process of restoring an existing DRX cycle to an original value after successfully completing a UE location information service in a wireless communication system according to various embodiments of the disclosure.

A DRX parameter restoration procedure may be performed even when a UE <NUM> in the idle state (a CM-IDLE state or an RRC inactive) does not need to be promptly changed to a connected state (CM-CONNECTED or RRC connected) any longer due to the movement of the UE <NUM>. After performing a location information service or detecting a change of the location information of the UE <NUM>, an AMF <NUM> performs a procedure of restoring a DRX cycle to the value of a previous DRX cycle that was used before the DRX parameter of the UE <NUM> is corrected, that is, performs a UE configuration update procedure.

To implement the embodiment of <FIG>, the AMF stores an existing DRX parameter in a UE context in operation <NUM> of the embodiment of <FIG>. Alternatively, in operation <NUM> of the embodiment of <FIG> or operation <NUM> of the embodiment of <FIG>, or operation <NUM> of the embodiment of <FIG>, the AMF stores an existing DRX parameter in a UE context.

Operations 1201a to 1201d correspond to a triggering condition for performing operation <NUM>. An AMF <NUM> detects a change of the location information of a UE <NUM>. Operations 1201a to 1201d corresponds to a procedure for triggering a procedure of a restoring DRX parameter configuration information in operation <NUM>, due to a change of the location of the UE.

In operation 1201a, a (R)AN <NUM> transmits a handover completion message to the AMF <NUM>. In an N2/Xn handover procedure, the AMF <NUM> detects a change of the location of the UE <NUM>.

In operation 1201b the (R)AN <NUM> transmits an NG-RAN location information report (NG-RAN location report) message to the AMF <NUM>. Via NG-RAN location reporting, the AMF <NUM> detects a change of the location of the UE <NUM>.

In operation 1201c, the (R)AN <NUM> transmits a location information report using an LMC (location report using LMC) to the AMF <NUM>. After performing an LMC-based UE positioning procedure, the RAN <NUM> or the LMC transfers the location information of the UE <NUM> to the AMF <NUM>.

In operation 1201d, a UDM <NUM> transmits a positioning response (location determination response) message to the AMF <NUM>. After performing the UE positioning procedure of an LMF, the LMF transfers the location information of the UE <NUM> to the AMF <NUM>.

Operations 1202a to 1202c correspond to a triggering condition for performing operation <NUM>.

In operation 1202a, the AMF <NUM> transmits a location information response (location response) message to the UE <NUM>.

In operation 1202b, the AMF <NUM> transmits a location information response (location response) message to the (R)AN <NUM>.

In operation 1202c, the AMF <NUM> transmits a location information response (location response) message to a GMLC or NEF <NUM> or an AF.

In the case in which the AMF <NUM> performs a UE location information obtaining procedure in response to a location information request such as operations 801a to 801c of the embodiment of <FIG>, the AMF <NUM> transfers UE location information to an entity that requests the UE location information, for example, the UE <NUM>, the base station <NUM>, the GMLC or the NEF <NUM>, or the AF.

In the case in which the AMF <NUM> transmits a message that indicates completion of performing associated with the UE location information request in response to the request, in the case in which the AMF <NUM> transmits a UE location information report message, or in the case in which the AMF <NUM> determines that a quick location information service is not needed any longer, operation <NUM> of the AMF <NUM> is triggered.

In operation <NUM>, the AMF <NUM> detects whether the location of the UE <NUM> is changed or whether the UE <NUM> leaves a location area (detect UE location is changed and UE moved out of location area), and determines to re-store a DRX configuration (decide to re-store the DRX configuration).

Due to the movement of the UE <NUM> such as operations 1201a to 1201d, the AMF <NUM> determines that the low-latency location information service is not needed in the area from which the UE <NUM> leaves in operation <NUM>. Alternatively, due to completion of the location information service such as operations 1202a to 1202c, the AMF <NUM> determines that the low-latency location information service is not needed any longer in operation <NUM>.

To perform the embodiment of <FIG>, an AMF stores an existing DRX parameter in a UE context in operation <NUM> of the embodiment of <FIG>. Alternatively, in operation <NUM> of the embodiment of <FIG> or operation <NUM> of the embodiment of <FIG>, or operation <NUM> of the embodiment of <FIG>, an AMF stores an existing DRX parameter in a UE context.

The AMF <NUM> performs a UE configuration update procedure in operations <NUM> to <NUM> in order to restore a previous DRX parameter configuration that was stored in the UE context.

Alternatively, the AMF <NUM> includes a DRX parameter in a message for changing a RAN configuration of operation <NUM> and transmits the same to the RAN node <NUM>, in order to restore a previous DRX parameter configuration that was stored in the UE context.

Subsequently, in operations <NUM> to <NUM>, a UE configuration update procedure is performed. In operations <NUM> to <NUM>, the AMF <NUM> restores the DRX cycle of the UE <NUM> to an original value via the UE configuration update procedure.

<FIG> is a diagram illustrating a process in which an AMF updates a DRX parameter according to movement of a UE in a wireless communication system according to various embodiments of the disclosure.

In the embodiment of <FIG>, a registration request message that the UE <NUM> transmits triggers the AMF <NUM> to update a DRX parameter.

The AMF <NUM> receives a registration request message from the UE <NUM>, and detects that the location of the UE is changed. When the AMF <NUM> determines that the UE <NUM> is currently in the state in which a DRX parameter for a low-latency location service is adjusted and the current location of the UE is in a location that does not require low-latency requirement, the AMF <NUM> determines restoration of the DRX parameter.

When the AMF <NUM> determines that the UE <NUM> is currently in the state in which a DRX parameter for a low-latency location service is adjusted and the current location of the UE is in a location that does not require low-latency requirement, and a response of a low-latency location service is not present that is performed periodically, delayed, pending, or triggered by a change of the location of the UE, the AMF <NUM> determines the restoration of the DRX parameter. The AMF <NUM> that determines restoration of the DRX parameter determines to update a UE configuration (UE configuration update) or determines to change a DRX parameter configuration in the RAN <NUM> and performs the same.

In operation <NUM>, the UE <NUM> transmits a registration request message to the (R)AN <NUM>. According to an embodiment, the registration request message of operation <NUM> includes a DRX parameter. The UE <NUM> transfers the registration request message to the RAN <NUM>. In order to request updating a DRX parameter, the registration request message may include the value of a DRX parameter with which a DRX parameter desires to be updated.

In operation <NUM>, the (R)AN <NUM> transmits a registration request message to the AMF <NUM>. According to an embodiment, the registration request message of operation <NUM> includes a DRX parameter and UE location information (UE location). The NR-RAN <NUM> transfers, to the AMF <NUM>, the registration request message together with the UE location information, for example, a cell ID, an NG-RAN node ID, or a tracking area.

In operation <NUM>, the AMF <NUM> detects whether the location of the UE <NUM> is changed or whether the UE <NUM> leaves a location area (detect UE location is changed and UE moved out of location area), and determines to re-store a DRX configuration (decide to re-store the DRX configuration). When receiving a UE registration message, the AMF <NUM> detects that the location of the UE <NUM> is changed. The AMF <NUM> determines whether the UE leaves a location area requested by the location request, or a pending location request is present. The AMF <NUM> determines whether it is a shorted DRX cycle mode. The AMF <NUM> determines whether to restore a DRX cycle.

In operation <NUM>, the AMF <NUM> transmits a registration accept message to the UE <NUM>. According to an embodiment, the registration accept message includes an accepted DRX parameter. In the case in which the AMF <NUM> determines to restore a DRX cycle to an original value, the AMF <NUM> sets a DRX parameter to be restored in the accepted DRX cycle, and transmits a registration response message to the UE <NUM>.

In operation <NUM>, the AMF <NUM> transmits a RAN update (update RAN) message to the (R)AN <NUM>. According to an embodiment, the RAN update message includes a DRX parameter. In the case in which the AMF <NUM> determines restoration or change of a DRX parameter, the AMF <NUM> transmits, to the RAN <NUM>, a message that requests restoration of the value of a DRX parameter.

In operation <NUM>, the AMF <NUM> transmits a UE's DRX parameter update report message to a GMLC or the NEF <NUM>.

The methods according to embodiments described in the claims or the specification of the disclosure may be implemented by hardware, software, or a combination of hardware and software.

Although specific embodiments have been described in the detailed description of the disclosure, various modifications and changes may be made thereto without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be defined as being limited to the embodiments, but should be defined by the appended claims.

Claim 1:
A method performed by an access and mobility function, AMF, entity in a wireless communication system, the method comprising:
receiving, from a user equipment, UE, a location information request message including location quality of service, QoS, information, wherein the location QoS information includes at least information on a location precision and information on a service response time;
determining at least one discontinuous reception, DRX, parameter to be updated based on the service response time;
identifying a cycle of a DRX for the UE based on the location QoS information; and
transmitting, to the UE, a UE configuration update command message including information on the cycle of the DRX for the UE.