Apparatus and method for recovering missing information in wireless communication system
The SMF in wireless communication systems addresses message loss by detecting and restoring lost usage through cumulative usage comparison, improving data transmission accuracy and reducing network congestion.
Patent Information
- Application Number
- KR1020210018649
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-09
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2041-02-09
AI Technical Summary
Existing wireless communication systems face inefficiencies in recovering lost usage information due to message loss during network congestion, which can cause network congestion and delay in billing settlements.
A method involving a session management function (SMF) that detects lost usage by comparing cumulative usage information from a user plane function (UPF) and transmits restored usage information to an online charging system (OCS) using a separate cumulative usage IE, minimizing network congestion and ensuring accurate billing.
This approach enhances data transmission accuracy by efficiently restoring lost information, reducing network congestion and minimizing user-perceived delay during network switching.
Smart Images

Figure 112021016794745-PAT00006_ABST
Abstract
Description
Technology Field
[0001] Various embodiments of the present disclosure relate to wireless communication systems, for example, to electronic devices or methods for recovering lost information. Background Technology
[0002] Efforts are being made to develop improved 5G (5th generation) communication systems or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G (4th generation) communication systems. For this reason, 5G communication systems or pre-5G communication systems are referred to as Beyond 4G Network communication systems or Post-LTE systems.
[0003] To achieve high data transmission rates, 5G communication systems are being considered for implementation in the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.
[0004] In addition, to improve the network of the system, technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, mobile telecommunication, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems.
[0005] In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed in 5G systems.
[0006] To improve equipment efficiency in wireless communication, a separation method between control plane and user plane equipment was introduced, and an interface (Sx Interface) was added between the control plane and the user plane to facilitate information exchange between the two devices.
[0007] Using the Sx Interface, the control plane performs the action of requesting usage from the user plane or transferring usage to the control plane when specific conditions (trigger conditions) are met from the user plane.
[0008] In the above operation process, the control plane Message loss can occur between user planes, and to compensate for this, the standard defines time-out detection and retransmission via timers. (Refer to 3GPP 29.244-6.4) The problem to be solved
[0009] Various embodiments of the present disclosure may provide an apparatus and method for efficiently restoring the loss of usage information transmitted between devices in a wireless communication system. means of solving the problem
[0010] A method of operation of a session management function (SMF) according to one embodiment of the present disclosure comprises the steps of: transmitting a request message to a user plane function (UPF) based on session settings; receiving a response message from the UPF; determining whether there is lost usage based on the response message; and, if there is lost usage, transmitting restored usage information to an online charging system (OCS). The response message may include current usage information and cumulative usage information of the UPF. Effects of the invention
[0011] The apparatus and method according to various embodiments of the present disclosure can provide the effect of improving the accuracy of data transmission by efficiently restoring information lost in a wireless communication system.
[0012] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below. Brief explanation of the drawing
[0013] FIG. 1 illustrates a wireless communication system according to various embodiments of the present disclosure. FIG. 2 illustrates an example of a wireless communication system according to various embodiments of the present disclosure. FIG. 3 illustrates an example of a wireless protocol structure in a wireless communication system according to various embodiments of the present disclosure. FIG. 4 illustrates an operation for detecting and restoring message loss in a wireless communication system according to one embodiment of the present disclosure. FIG. 5 illustrates the processing of loss of usage through a retransmission operation in a wireless communication system according to one embodiment of the present disclosure. FIG. 6 illustrates a recovery operation in the event that a session request message is lost in a wireless communication system according to one embodiment of the present disclosure. FIG. 7 illustrates a recovery operation in the event that a session modification request message is lost in a wireless communication system according to one embodiment of the present disclosure. FIG. 8 illustrates a recovery operation in the event that a session report request message is lost in a wireless communication system according to one embodiment of the present disclosure. FIG. 9 illustrates a recovery operation in the event that a session modification response message is lost in a wireless communication system according to one embodiment of the present disclosure. FIG. 10 illustrates a recovery operation for loss outside the Sx interface section in a wireless communication system according to one embodiment of the present disclosure. Specific details for implementing the invention
[0014] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art described in this disclosure. Terms used in this disclosure that are defined in a general dictionary may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure. In some cases, even terms defined in this disclosure are not to be interpreted to exclude the embodiments of this disclosure.
[0015] In the various embodiments of the present disclosure described below, a hardware-based approach is described as an example. However, since the various embodiments of the present disclosure include techniques using both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.
[0016] The present disclosure describes a technology for reducing user-perceived delay by shortening the time required for switching communication networks in a wireless communication system through an apparatus and method for switching communication networks based on the communication quality between an electronic device and an access point in a wireless communication system.
[0017] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."
[0018] In the present disclosure, upper signaling may refer to a signal transmission method transmitted from a base station to an electronic device using a physical layer downlink data channel, or from an electronic device to a base station using a physical layer uplink data channel. Upper signaling may be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).
[0019] Additionally, in this disclosure, expressions such as "greater than" or "less than" have been used to determine whether specific conditions are satisfied or fulfilled; however, this is merely for illustrative purposes and does not exclude descriptions of "greater than" or "less than." Conditions described as "greater than" may be replaced with "greater than," conditions described as "less than" with "less than," and conditions described as "greater than and less than" with "greater than and less than."
[0020] Additionally, various embodiments of the present disclosure describe various embodiments using terms used in some communication standards (e.g., 3GPP (3rd generation partnership project)), but this is merely for illustrative purposes. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.
[0022] FIG. 1 illustrates a wireless communication system according to various embodiments of the present disclosure.
[0023] Referring to FIG. 1, the wireless communication system includes a radio access network (RAN) 102 and a core network (CN) 104.
[0024] A wireless access network 102 is a network directly connected to a user device, for example, a terminal 120, and is an infrastructure that provides wireless access to the terminal 120. The wireless access network 102 includes a set of multiple base stations, including a base station 110, and the multiple base stations can perform communication through interfaces formed between them. At least some of the interfaces between the multiple base stations may be wired or wireless. The base station 110 may have a structure separated into a central unit (CU) and a distributed unit (DU). In this case, one CU can control multiple DUs. In addition to the base station, the base station 110 includes an access point (AP), a gNB (next generation node B), and a 5G node (5 thIt may be referred to as a 'generation node', 'wireless point', 'transmission / reception point (TRP)', or other terms having an equivalent technical meaning. Terminal 120 connects to a wireless access network 102 and communicates with base station 110 via a wireless channel. In addition to terminal, Terminal 120 may be referred to as 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device', or other terms having an equivalent technical meaning.
[0025] The core network 104 is a network that manages the entire system, controls the wireless access network 102, and processes data and control signals for terminals 120 transmitted and received through the wireless access network 102. The core network 104 performs various functions, such as controlling the user plane and control plane, processing mobility, managing subscriber information, billing, and interoperability with other types of systems (e.g., LTE (long term evolution) systems). To perform the various functions described above, the core network 104 may include multiple functionally separated entities having different network functions (NFs). For example, the core network 104 may include an access and mobility management function (AMF) 130a, a session management function (SMF) 130b, a user plane function (UPF) 130c, a policy and charging function (PCF) 130d, a network repository function (NRF) 130e, a user data management function (UDM) 130f, a network exposure function (NEF) 130g, and a unified data repository function (UDR) 130h.
[0026] Terminal 120 is connected to the wireless access network 102 and connects to AMF 130a, which performs the mobility management function of the core network 104. AMF 130a is a function or device responsible for both the connection to the wireless access network 102 and the mobility management of Terminal 102. SMF 130b is an NF that manages sessions. AMF 130a is connected to SMF 130b, and AMF 130a routes session-related messages for Terminal 120 to SMF 130b. SMF 130b is connected to UPF 130c to allocate user plane resources to be provided to Terminal 120 and establishes a tunnel for transmitting data between Base Station 110 and UPF 130c. PCF 130d controls information related to policy and charging for the sessions used by Terminal 120. NRF 130e stores information about NFs installed in the mobile operator network and performs the function of providing the stored information. NRF 130e can be connected to all NFs. When each NF starts operating in the operator network, it registers with NRF 130e to notify NRF 130e that the corresponding NF is operating within the network. UDM 130f is an NF that performs a role similar to the HSS (home subscriber server) of a 4G network and stores the subscriber information of Terminal 120, or the context used by Terminal 120 within the network.
[0027] NEF 130g is a third party (3 rdIt performs the role of connecting the server (party) and the NF within the 5G mobile communication system. It also performs the role of providing, updating, or acquiring data to UDR 130h. UDR 130h stores subscriber information of terminal 120, stores policy information, stores data exposed externally, or third-party applications (3 rd It performs the function of storing information required by the party application. In addition, UDR 103h also performs the role of providing stored data to other NFs.
[0029] FIG. 2 illustrates an example of a wireless communication system according to various embodiments of the present disclosure.
[0030] Referring to FIG. 2, the wireless communication system is composed of several base stations (205)(210)(215)(220), an MME (Mobility Management Entity) (220), and an S-GW (Serving-Gateway) (230). A user terminal (User Equipment, hereinafter UE or terminal) (235) connects to an external network through the base stations (205)(210)(215)(220) and the S-GW (230).
[0031] The above base stations (205)(210)(215)(220) serve as connection nodes of a cellular network and provide wireless access to terminals connected to the network. That is, the above base stations (205)(210)(215)(220) collect status information such as the buffer status, available transmission power status, and channel status of terminals to schedule and support the connection between the terminals and the core network (CN) in order to service the traffic of users. The MME (225) is a device that is responsible for various control functions as well as mobility management functions for terminals and is connected to multiple base stations, and the S-GW (230) is a device that provides a data bearer. Additionally, the MME (225) and S-GW (230) can further perform authentication for terminals connected to the network, bearer management, etc., and process packets received from the base station (205)(210)(215)(220) or packets to be delivered to the base station (205)(210)(215)(220).
[0033] FIG. 3 illustrates an example of a wireless protocol structure in a wireless communication system according to various embodiments of the present disclosure.
[0034] Referring to FIG. 3, the wireless protocol of the LTE system consists of a Packet Data Convergence Protocol (PDCP) (355)(390), Radio Link Control (RLC) (360)(385), and Medium Access Control (MAC) (365)(390) at the terminal and ENB, respectively. The Packet Data Convergence Protocol (PDCP) (355)(390) is responsible for operations such as IP header compression / recovery, and the Radio Link Control (hereinafter referred to as RLC) (360)(395) reconstructs the PDCP Packet Data Unit (PDU) into an appropriate size. The MAC (365)(390) is connected to multiple RLC layer devices configured in a terminal and performs the operation of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The physical layer (370)(385) performs the operation of channel coding and modulating upper layer data, creating OFDM symbols to transmit to the wireless channel, or demodulating and channel decoding OFDM symbols received through the wireless channel to transmit to the upper layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiving end transmits a 1-bit indicating whether the packet transmitted by the transmitting end has been received. This is called HARQ ACK / NACK information. In the case of LTE, downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the PHICH (Physical Hybrid-ARQ Indicator Channel) physical channel, and
[0035] Although not shown in this drawing, an RRC (Radio Resource Control) layer exists above the PDCP layer of the terminal and the base station, respectively, and the RRC layer can exchange connection and measurement-related setting control messages for wireless resource control.
[0036] Meanwhile, the above PHY layer can be composed of one or more frequencies / carriers, and the technology of setting and using multiple frequencies simultaneously is called carrier aggregation (hereinafter referred to as CA). CA technology allows for a significant increase in transmission capacity by the number of secondary carriers by using one or more secondary carriers in addition to the main carrier, whereas previously only one carrier was used for communication between a terminal (or User Equipment, UE) and a base station (E-UTRAN NodeB, eNB). Meanwhile, in LTE, a cell within a base station that uses the main carrier is called a primary cell or PCell (Primary Cell), and a cell within a base station that uses a secondary carrier is called a secondary cell or SCell (Secondary Cell).
[0038] The retransmission operation defined in the 3GPP standard can be a sufficient solution for one-time lost messages and messages lost while the network is in a smooth state of communication. However, due to the limitations of UDP communication and the finite number of retransmissions supported at the PFCP stage, it cannot be a solution for all lost messages, and the waiting time required for retransmission itself may cause congestion.
[0039] For example, when usage is retransmitted through a retransmission operation, the total number of messages entering the network temporarily increases. This can cause network congestion and affect delays in messages delivered to other equipment. For this reason, the configured short duration and few retransmission operations are not a sufficient solution for continuous message loss during periods of network congestion, and recovery or correction operations for lost message usage are not defined.
[0041] The purpose of this disclosure is to minimize usage loss caused by message loss by using a different IE than the existing 3GPP-defined IE to transmit cumulative usage information between the SMF and UPF, and utilizing the difference value of cumulative usage, in response to the problem of in-network message loss that is not supported by retransmission operations.
[0042] The present disclosure relates to an operation for recognizing and recovering lost usage in the event of loss of a message including usage transmitted in an Sx / N4 interface.
[0043] By recognizing usage data present in lost messages, restoring it, and transmitting it separately or together with existing usage, it prevents usage omissions during settlement at the billing unit; furthermore, the recognized accumulated usage is aggregated and delivered based on events that can affect rate plan settlement, such as the CHANGE_CONDITION Event.
[0044] This means using a separate cumulative usage IE to serve as a comparison value other than the standard configured IE.
[0046] According to one embodiment of the present disclosure, since no new message or message is added for the transmission of lost message information, the effect of recovering the usage of lost messages can be provided without causing network congestion.
[0047] In addition, if usage loss is minimized, the value of N1 / T1 can be minimized; therefore, in the event of temporary network congestion, it is possible to reduce the number of incoming retransmission messages, thereby providing the effect of reducing the duration of network congestion or reducing the network itself.
[0049] FIG. 4 illustrates an operation for detecting and restoring message loss in a wireless communication system according to one embodiment of the present disclosure.
[0050] Referring to Fig. 4, the operation of an SMF can be described as detecting lost usage based on information received from a UDF and sending a message to restore the lost usage.
[0051] In step (401), the SMF may send a request message to the UPF based on the session establishment. The sending of the request message may be an action performed after the session establishment between the SMF and the UPF. The request message may refer to a request message associated with the session. For example, it may be a request message regarding the session established between the UPF and the SMF, such as a session deletion request, a session modification request, or a session report request.
[0052] In step (403), the SMF can receive a response message from the UPF.
[0053] The response message received by the SMF from the UPF may be received after the transmission of the request message. The response message may refer to a response message associated with a session established between the UPF and the SMF. For example, it may be a response message regarding the session established between the UPF and the SMF, such as a session deletion response, a session modification response, or a session report response.
[0054] The response message received by the SMF may include usage information. This usage information may be information regarding the amount of traffic used by the UPF. Additionally, this usage information may be divided into the UPF's current usage information and cumulative usage information. Current usage information may be information regarding the amount of traffic used by the UPF but not reported, while cumulative usage information may refer to the total amount of traffic used by the UPF from the time of call establishment until the time of call deletion.
[0055] In step (405), the SMF can determine whether there is any lost usage based on the response message received from the UPF.
[0056] Lost usage may refer to information regarding the amount of traffic that was used by UPF but was not reported to SMF. Therefore, if there is lost usage, UPF may report the amount of traffic to the billing server while omitting the lost usage.
[0057] The SMF can determine existing accumulated usage information that is already stored. Based on the determined existing accumulated usage information and the usage information received from the UPF, it can determine whether there is any lost usage. Specifically, it can determine whether the sum of the usage corresponding to the existing accumulated usage information and the usage corresponding to the current usage information among the usage information received from the UPF is equal to the usage corresponding to the accumulated usage information received from the UPF. If they are equal, it can be determined that there is no lost usage. If the sum is smaller than the usage corresponding to the accumulated usage information, the usage corresponding to the difference can be determined as lost usage.
[0058] In step (407), the SMF can transmit restored usage information to the OCS (online charging system) in response to determining that there is lost usage.
[0059] The restored usage information may mean the usage corresponding to the current usage information determined based on the lost usage determined in step (405) and the response message received from UPF.
[0061] FIG. 5 illustrates the processing of loss of usage through a retransmission operation in a wireless communication system according to one embodiment of the present disclosure.
[0062] Referring to FIG. 5, potential problems that may occur during the process of handling usage loss through retransmission operations can be explained. The operations illustrated in FIG. 5 are basically associated with operations after a call is created. Message loss that may occur at the Sx / N4 interface during call creation may be unrelated to usage loss. If the retransmission operation does not successfully finish in operations 7 to 7-2 among the operations included in FIG. 5, the used usage is lost, and an error may occur where the actual usage is calculated as only 20M instead of 100M.
[0063] A retransmission operation may fail to complete successfully in situations where continuous message loss occurs during network congestion. If, upon message transmission failure, retransmission operations are performed more than the maximum number of times but the message still fails, it can be determined that the retransmission operation was not successfully completed. The specific operation is described below.
[0064] In step (501), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used by the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage.
[0065] In this case, usage may be information related to traffic used in UPF.
[0066] In step (502), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on usage information included in the session report request message received from the UPF.
[0067] For example, SMF can record MSCC / USU information based on usage and time event information included in the received session report request message and send it to OCS.
[0068] In step (503), the OCS receives usage and time event information from the CCR.
[0069] In step (504), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0070] In step (505), the SMF can send a session modification request message to the UPF. At this time, the session modification request message may include the Quota information and event information received from the OCS in the Update URR.
[0071] In step (506), UPF may send a session modification response message to SMF. The session modification response message may include information confirming that the session modification request message transmitted from SMF has been successfully received and processed.
[0072] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur. For example, when the threshold usage is 80M, if UPF's traffic usage reaches 80M after step (506), UPF may generate a session report request message to send to SMF.
[0073] In step (507), UPF may send a session report message to SMF. At this time, the session report message may include information indicating that traffic usage has reached a threshold usage. More specifically, it may include information on the traffic usage used by UPF after step (506). For example, UPF may include information in the session report message indicating that UPF has used traffic corresponding to 80M.
[0074] In step (507-1), UPF may resend the session report message to SMF. Specifically, if UPF determines that no response has arrived to the session report message sent in step (507), it may resend the same message as the session report message sent in step (507) to SMF.
[0075] In step (507-2), UPF may resend the session report message to SMF. Specifically, if UPF determines that no response has arrived to the session report message sent in step (507-1), it may resend the same message as the session report message sent in step (507) to SMF.
[0076] UPF may repeat step (507) until it reaches a maximum number of retransmissions N1, and when the transmission of session report messages reaches N1, it may no longer report existing usage. In this case, information regarding UPF's traffic usage of 80M and threshold usage may be lost. Consequently, SMF cannot recognize that traffic corresponding to 80M has been used.
[0077] If UPF uses an additional 20M of the remaining quota after excluding the 80M already used out of the total 100M quota, no more traffic will flow, so a call deletion operation to reconnect may be performed by the user.
[0078] In step (508), the SMF can receive a delete session request from the MME.
[0079] In step (509), in response to receiving a session deletion request from the MME, the SMF may send a session deletion request message to the UPF. This may be for performing call deletion by releasing existing resources.
[0080] In step (510), UPF can send a session deletion response message to SMF. The session deletion response message may include usage and related information up to that point. For example, if the amount of traffic used by UPF reaches a threshold usage and the transmission of the threshold usage information fails, and UPF uses an additional 20M, the session deletion response message may include information about the additional 20M used.
[0081] In step (511), the SMF can transmit the received usage to the OCS.
[0082] In step (512), the SMF can terminate the session by receiving CCA-T from the OCS.
[0083] In step (513), the SMF can send a delete session response to the MME, and the MME can terminate the session normally.
[0084] FIG. 6 illustrates a recovery operation in the event that a session request message is lost in a wireless communication system according to one embodiment of the present disclosure.
[0085] Referring to Fig. 6, a recovery operation can be described in the case where a session report request message is lost in a message loss scenario caused by a retransmission operation.
[0086] Referring to FIG. 6, potential problems that may occur during the processing of usage loss through existing retransmission operations can be explained. The operations illustrated in FIG. 6 are basically associated with operations after a call is created. Message loss that may occur at the Sx / N4 interface during call creation may be unrelated to usage loss. If the retransmission operation does not successfully finish in the operations of steps (607), (607-1), and (607-2) among the operations included in FIG. 6, the amount of traffic used is lost, and according to one embodiment, the UPF supports service for 20M after the loss. Subsequently, at the time the call is deleted, it is checked whether there is any lost usage and how much the lost usage is through the received usage and accumulated usage, and then it is recovered and the recovered usage is transmitted to the OCS, thereby preventing usage loss.
[0087] Each action described in detail below is exemplary, and each value corresponding to cumulative usage or traffic volume (e.g., 20M, 400M, etc.) may be applied differently depending on traffic conditions or environment.
[0088] In step (601), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used in the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage. At this time, the usage may be information related to traffic used in the UPF.
[0089] In addition, the session report request message may include the amount of traffic used (e.g., 80M) along with the accumulated usage (e.g., 300M).
[0090] In step (602), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on usage information included in the session report request message received from the UPF.
[0091] SMF adds the new usage (80M) to the existing accumulated usage (220M) and can check whether this combined usage is the same as the newly received accumulated usage (300M).
[0092] In step (603), in response to confirming that the summed usage of SMF is the same as the newly received cumulative usage, the received usage is determined to be normal and the usage of 80M can be transmitted to OCS.
[0093] In step (604), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0094] In step (605), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0095] In step (606), UPF may send a session modification response message to SMF. The session modification response message may include information confirming that the session modification request message transmitted from SMF has been successfully received and processed.
[0096] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur. For example, when the threshold usage is 80M, if UPF's traffic usage reaches 80M after step (506), UPF may generate a session report request message to send to SMF.
[0097] In step (607), UPF may send a session report message to SMF. At this time, the session report message may include information indicating that traffic usage has reached a threshold usage. More specifically, it may include information on the traffic usage used by UPF after step (506). For example, UPF may include information in the session report message indicating that UPF has used traffic corresponding to 80M.
[0098] Additionally, UPF may include information on the cumulative usage of traffic used to date in session report messages. For example, if the cumulative usage already used by UPF is 300M before traffic usage reaches a threshold usage (e.g., 80M), the cumulative usage information of 380M, which is the sum of the existing cumulative usage of 300M and the threshold usage of 80M, may be included in the session report message.
[0099] In step (607-1), UPF may resend the session report message to SMF. Specifically, if UPF determines that no response has arrived to the session report message sent in step (607), it may resend the same message as the session report message sent in step (607) to SMF.
[0100] In step (607-2), UPF may resend the session report message to SMF. Specifically, if UPF determines that no response has arrived to the session report message sent in step (607-1), it may resend the same message as the session report message sent in step (607) to SMF.
[0101] UPF may repeat step (607) until it reaches a maximum number of retransmissions N1, and when the transmission of session report messages reaches N1, it may no longer report existing usage. In this case, information regarding UPF's traffic usage of 80M and threshold usage may be lost. Consequently, SMF will not be able to recognize that traffic corresponding to 80M has been used.
[0102] If UPF uses an additional 20M of the remaining quota after excluding the 80M already used out of the total 100M quota, no more traffic will flow, so a call deletion operation to reconnect may be performed by the user.
[0103] In step (608), the SMF can receive a delete session request from the MME.
[0104] In step (609), in response to receiving a session deletion request message from the MME, the SMF may forward the session deletion request message to the UPF. This may be for performing call deletion by releasing existing resources.
[0105] In step (610), UPF can send a session deletion response message to SMF. The session deletion response message may include usage and related information up to that point. For example, if the amount of traffic used by UPF reaches a threshold usage and the transmission of the threshold usage information fails, and UPF uses an additional 20M, the session deletion response message may include information about the additional 20M used.
[0106] In addition, the session deletion response message may include cumulative usage information. The cumulative usage information may include information corresponding to a total cumulative usage (e.g., 400M) by adding the amount of additional traffic used by the UPF after a retransmission failure (e.g., 20M) to the cumulative usage (e.g., 380M) included in the session report message.
[0107] At this time, the SMF can check the usage based on the session deletion response message received from the UPF. While the SMF confirms that the accumulated usage is 320M (300M + 20M), which is the sum of the existing accumulated usage of 300M and the usage of 20M received from the UPF, it can be confirmed that the total accumulated usage transmitted by the UPF is 400M. In this case, the SMF recognizes the lost usage of 80M.
[0108] In step (611), the SMF can transmit usage information to the OCS. The usage information transmitted to the OCS may include information regarding lost usage. Specifically, if the lost usage recognized by the SMF is 80M, the usage information transmitted to the OCS may include total usage information corresponding to 100M by adding the usage of 20M received from the UPF and the lost usage of 80M.
[0109] In step (612), the SMF can terminate the session by receiving the CCA-T from the OCS.
[0110] In step (613), the SMF can send a delete session response to the MME, and the MME can terminate the session normally.
[0112] FIG. 7 illustrates a recovery operation in the event that a session modification request message is lost in a wireless communication system according to one embodiment of the present disclosure.
[0113] Referring to FIG. 7, a recovery operation according to another embodiment can be described in the case where a session modification request message is lost in a message loss scenario caused by a retransmission operation.
[0114] The operations illustrated in FIG. 7 can basically be associated with operations after a call is created. Message loss that may occur at the Sx / N4 interface at the time of call creation may be unrelated to usage loss.
[0115] If the retransmission operation does not successfully finish in the operations of steps (709), (711), and (713) included in Fig. 7, the used usage is lost, and UPF can support the service for 20M after the loss.
[0116] Subsequently, at the time the order is deleted, the received usage and accumulated usage are used to determine if the usage is lost and to recover it; since the recovered usage is transmitted to the OCS, usage loss can be prevented.
[0117] In addition, even if a session modification response message is successfully received during the retransmission process, the lost usage can be included after recovery through accumulated usage and transmitted to the OCS to prevent loss.
[0118] In step (701), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used in the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage. At this time, the usage may be information related to traffic used in the UPF.
[0119] In addition, the session report request message may include the amount of traffic used (e.g., 80M) along with the accumulated usage (e.g., 300M).
[0120] In step (702), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on usage information included in the session report request message received from the UPF.
[0121] SMF adds the new usage (80M) to the existing accumulated usage (220M) and can check whether this combined usage is the same as the newly received accumulated usage (300M).
[0122] In step (703), in response to confirming that the summed usage of SMF is the same as the newly received cumulative usage, the received usage is determined to be normal and the usage of 80M can be transmitted to OCS.
[0123] In step (704), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0124] In step (705), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0125] In step (706), UPF may send a session modification response message to SMF. The session modification response message may include information confirming that the session modification request message transmitted from SMF has been successfully received and processed.
[0126] After UPF sends a session modification response message to SMF, UPF can use a certain amount of traffic (e.g., 40M).
[0127] In step (707), the SMF can receive an event from the MME. At this time, the event may take the form of receiving a modify bearer request from the MME. Here, the modify bearer request may be performed when a change in the Modify Event or Mobility occurs, such as with the Location CHG / Serving Node CHG.
[0128] In step (708), the SMF can determine whether to forward usage to the billing server after checking the registered Event Trigger. Depending on whether it is necessary to forward usage to the billing server, the SMF can perform an action to request usage from the UPF. The action to request usage from the UPF may include sending a session modification request message to the UPF.
[0129] In step (709), the UPF may send a session modification response message to the SMF in response to the session modification request message received from the SMF. The session modification response message may include information regarding usage. In this case, the information regarding usage may include information regarding usage used to date (40M) and total accumulated usage (340M).
[0130] After the session modification response message is sent, UPF can use a certain amount of traffic (e.g., 25M).
[0131] In step (710), as the transmission of the session modification response message fails, i.e., is lost, the SMF can request usage by retransmitting a session modification request message requesting usage to the UPF.
[0132] In step (711), in response to the session modification request message received from the SMF, a session modification response message may be sent to the SMF. The session modification response message may include information regarding usage. The information regarding usage may include information regarding the currently used usage (25M) and the accumulated usage (365M).
[0133] After the session modification response message is sent, UPF can use a certain amount of traffic (e.g., 15M).
[0134] In step (712), as the transmission of the session modification response message fails, i.e., is lost, the SMF can request usage by retransmitting a session modification request message requesting usage to the UPF.
[0135] In step (713), in response to the session modification request message received from the SMF, a session modification response message may be sent to the SMF. The session modification response message may include information regarding usage. The information regarding usage may include information regarding the currently used usage (15M) and the accumulated usage (380M).
[0136] In the event of a loss of usage due to a failure in some of steps (709), steps (711) and steps (713), SMF can recognize and recover the lost usage through CCR-U instead of CCR-T.
[0137] In step (714), the SMF can transmit a modify bearer response to the MME. Since the SMF failed to receive a session modify response message in the Sx (N4) interface section and thus could not perform the operation for the modify bearer normally, the modify bearer response may include information indicating failure.
[0138] In step (715), the MME can check whether the modification bearer request failed in response to receiving the modification bearer response message. Additionally, in response to checking the failure of the modification bearer request, the MME can request the SMF to delete the session or the bearer.
[0139] In step (716), in response to receiving a session deletion request message from the MME, the SMF may forward the session deletion request message to the UPF. This may be for performing call deletion by releasing existing resources.
[0140] In step (717), UPF can send a session deletion response message to SMF. The session deletion response message may include usage and related information up to that point. For example, if the amount of traffic used by UPF reaches a threshold usage and the transmission of the threshold usage information fails, and UPF uses an additional 20M, the session deletion response message may include information about the additional 20M used.
[0141] In addition, the session deletion response message may include cumulative usage information. The cumulative usage information may include information corresponding to a total cumulative usage (e.g., 400M) by adding the amount of additional traffic used by the UPF after a retransmission failure (e.g., 20M) to the cumulative usage (e.g., 380M) included in the session report message.
[0142] At this time, the SMF can check the usage based on the session deletion response message received from the UPF. While the SMF confirms that the accumulated usage is 320M (300M + 20M), which is the sum of the existing accumulated usage of 300M and the usage of 20M received from the UPF, it can be confirmed that the total accumulated usage transmitted by the UPF is 400M. In this case, the SMF recognizes the lost usage of 80M.
[0143] In step (718), the SMF can transmit usage information to the OCS. The usage information transmitted to the OCS may include information regarding lost usage. Specifically, if the lost usage recognized by the SMF is 80M, the usage information transmitted to the OCS may include total usage information corresponding to 100M by adding the usage of 20M received from the UPF and the lost usage of 80M.
[0144] In step (719), the SMF can terminate the session by receiving CCA-T from the OCS.
[0145] In step (720), the SMF can send a Delete Session Response to the MME, and the MME can terminate the session normally.
[0147] FIG. 8 illustrates a recovery operation in the event that a session report request message is lost in a wireless communication system according to one embodiment of the present disclosure.
[0148] Referring to Fig. 8, in a scenario where a message is lost due to a retransmission operation, a recovery operation can be described for cases where a Session Report Request message is lost when a Session Modification Request and a Session Report Request occur simultaneously.
[0149] The operations illustrated in FIG. 8 can basically be associated with operations after a call is created. Message loss that may occur at the Sx / N4 interface at the time of call creation may be unrelated to usage loss.
[0150] In the operation of step (807) of the operation included in Fig. 8, if the delivery of the Report Request message fails and a request for usage is received from SMF, the current usage and the lost usage are delivered together to OCS to recover the usage lost due to the message loss, and since the accumulated usage of SMF and UPF is the same, normal service can proceed.
[0151] For steps (807-1, not shown) and (807-2, not shown), even if subsequent retransmission is successful, it can be ignored because the accumulated usage is smaller than the accumulated usage currently set in the SMF.
[0152] In step (801), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used in the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage. At this time, the usage may be information related to traffic used in the UPF.
[0153] In addition, the session report request message may include the amount of traffic used (e.g., 80M) along with the accumulated usage (e.g., 300M).
[0154] In step (802), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on the usage information included in the session report request message received from the UPF.
[0155] SMF adds the new usage (80M) to the existing accumulated usage (220M) and can check whether this combined usage is the same as the newly received accumulated usage (300M).
[0156] In step (803), in response to confirming that the summed usage of SMF is the same as the newly received cumulative usage, the received usage is determined to be normal and the usage of 80M can be transmitted to OCS.
[0157] In step (804), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0158] In step (805), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0159] In step (806), the UPF may send a session modification response message to the SMF. The session modification response message may include information confirming that the session modification request message transmitted from the SMF has been successfully received and processed.
[0160] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur. For example, when the threshold usage is 80M, if UPF's traffic usage reaches 80M after step (806), UPF may generate a session report request message to send to SMF.
[0161] In step (807), UPF may send a session report request message to SMF. At this time, the session report message may include information indicating that traffic usage has reached a threshold usage. More specifically, it may include information on the traffic usage used by UPF after step (806). For example, UPF may include information in the session report message indicating that UPF has used traffic corresponding to 80M.
[0162] Additionally, UPF may include information on the cumulative usage of traffic used to date in session report messages. For example, if the cumulative usage already used by UPF is 300M before traffic usage reaches a threshold usage (e.g., 80M), the cumulative usage information of 380M, which is the sum of the existing cumulative usage of 300M and the threshold usage of 80M, may be included in the session report message.
[0163] If the transmission of the session report request message fails, UPF may repeatedly retransmit the session report request message. In this case, the operation of repeated transmission may be referred to as steps (807-1) and (807-2). However, since the accumulated usage transmitted in steps (807-1) and (807-2) is less than the accumulated usage transmitted in step (810) described later, it may be determined as the accumulated usage already transmitted and not considered.
[0164] In step (808), the SMF may receive an event from the MME. At this time, the event may take the form of receiving a modify bearer request from the MME. Here, the modify bearer request may be performed when a Modify Event or a change in Mobility occurs, such as a Location CHG / Serving Node CHG.
[0165] In step (809), the SMF can check the registered Event Trigger and determine whether to forward the usage to the billing server. Depending on whether it is necessary to forward the usage to the billing server, the SMF can perform an action to request the usage from the UPF. The action to request the usage from the UPF may include an action to send a session modification request message to the UPF.
[0166] In step (810), the UPF may send a Session Modification Response message to the SMF in response to the session modification request message received from the SMF. The session modification response message may include information regarding usage. In this case, the information regarding usage may include information regarding usage used to date (10M) and total accumulated usage (390M).
[0167] In step (811), the SMF can transmit usage information to the OCS. The usage information transmitted to the OCS may include information regarding lost usage. Specifically, if the lost usage recognized by the SMF is 80M, the usage information transmitted to the OCS may include total usage information corresponding to 90M, which is the sum of the usage of 10M received from the UPF and the lost usage of 80M.
[0168] In step (812), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0169] In step (813), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0170] In step (814), UPF may send a session modification response message to SMF. The session modification response message may include information confirming that the session modification request message transmitted from SMF has been successfully received and processed.
[0171] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur.
[0173] FIG. 9 illustrates a recovery operation in the event that a session modification response message is lost in a wireless communication system according to one embodiment of the present disclosure.
[0174] Referring to Fig. 9, a recovery operation can be described for the case where a session modification response message is lost when a session modification request and a session reporting request occur simultaneously in a message loss scenario caused by a retransmission operation.
[0175] The operations illustrated in FIG. 9 can basically be associated with operations after a call is created. Message loss that may occur at the Sx / N4 interface at the time of call creation may be unrelated to usage loss.
[0176] In the operation of step (907) of the operation included in Fig. 9, if the delivery of the Report Response message fails and a usage report is received from the UPF, the current usage and the lost usage are delivered together to the OCS to recover the usage lost due to the message loss, and the usage is recovered in the same way during subsequent Session deletion or Bearer deletion operations to prevent usage loss.
[0177] The loss of usage occurring during a collision between Session Modification Events and the loss of usage occurring between Session Modification / Session Deletion messages may also correspond to the extended concept of the embodiment illustrated in FIG. 9.
[0178] In step (901), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used in the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage. At this time, the usage may be information related to traffic used in the UPF.
[0179] In addition, the session report request message may include the amount of traffic used (e.g., 80M) along with the accumulated usage (e.g., 300M).
[0180] In step (902), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on the usage information included in the session report request message received from the UPF.
[0181] SMF adds the new usage (80M) to the existing accumulated usage (220M) and can check whether this combined usage is the same as the newly received accumulated usage (300M).
[0182] In step (903), in response to confirming that the summed usage of SMF is the same as the newly received cumulative usage, the received usage is determined to be normal and the usage of 80M can be transmitted to OCS.
[0183] In step (904), the OCS checks the usage received by the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage. For example, the OCS can set the threshold usage to 20M and the quota to 100M and transmit the relevant information to the SMF.
[0184] In step (905), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0185] In step (906), the UPF may send a session modification response message to the SMF. The session modification response message may include information confirming that the session modification request message transmitted from the SMF has been successfully received and processed.
[0186] In step (907), the SMF may receive an event from the MME. At this time, the event may take the form of receiving a modify bearer request from the MME. Here, the modify bearer request may be performed when a change in the Modify Event or Mobility occurs, such as with the Location CHG / Serving Node CHG.
[0187] In step (908), the SMF can check the registered Event Trigger and determine whether to forward the usage to the billing server. Depending on whether it is necessary to forward the usage to the billing server, the SMF can perform an action to request the usage from the UPF. The action to request the usage from the UPF may include an action to send a session modification request message to the UPF.
[0188] In step (909), the UPF may send a Session Modification Response message to the SMF in response to the session modification request message received from the SMF. The session modification response message may include information regarding usage. In this case, the information regarding usage may include information regarding usage used to date (40M) and total accumulated usage (340M).
[0189] In step (910), if the message is lost due to a failure to transmit the session modification response message, the SMF may request usage by retransmitting a session modification request message to the UPF. However, before the retransmission operation of the SMF, the UPF may use some of the traffic (e.g., 25M).
[0190] In step (911), UPF may resend a session modification response message in response to a session modification request message received from SMF. At this time, the session modification response message resent may include information corresponding to current usage (e.g., 25M) and cumulative usage (e.g., 365M). Afterwards, UPF may use some of the traffic (e.g., 5M).
[0191] In step (912), the UPF may send a session report request message to the SMF. The session report request message may be sent to the SMF based on a timer event, such as Validity Time. The session report request message may include information corresponding to current usage (5M) and cumulative usage (370M).
[0192] In step (913), if the SMF receives the usage information normally without a retransmission failure, the SMF can send a session report response message to the UPF.
[0193] In step (914), the SMF can transmit usage information to the OCS. The usage information transmitted to the OCS may include information regarding lost usage. Specifically, if the lost usage recognized by the SMF is 80M, the usage information transmitted to the OCS may include total usage information corresponding to 70M, which is the sum of the usage of 5M received from the UPF and the lost usage of 65M.
[0194] In other words, SMF recognizes message loss by comparing the value of the existing accumulated usage (e.g., 300M) + current usage (e.g., 5M) with the accumulated usage received from UPF (e.g., 370M), and can send the usage (e.g., 70M) including the lost usage, rather than the usage (e.g., 5M), to OCS.
[0195] In step (915), the OCS checks the usage received from the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage.
[0196] In step (916), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0197] In step (917), UPF may send a session modification response message to SMF. The session modification response message may include information confirming that the session modification request message transmitted from SMF has been successfully received and processed.
[0198] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur.
[0199] In step (918), SMF may request usage by resending a session modification request message to UPF requesting usage as the session modification response message is lost. Before that, UPF may use some traffic (e.g., 10M).
[0200] In step (919), the UPF may resend a session modification response message in response to the session modification request message received from the SMF. At this time, the session modification response message resent may include information corresponding to the current usage (e.g., 10M) and the cumulative usage (e.g., 380M).
[0201] In step (920), the SMF can transmit a modify bearer response to the MME. Since the SMF failed to receive the session modify response message in the Sx (N4) interface section and thus could not perform the operation for the modify bearer normally, the modify bearer response may include information indicating failure.
[0202] In step (921), the MME can check whether the modification bearer request failed in response to receiving the modification bearer response message. Additionally, in response to checking the failure of the modification bearer request, the MME can request the SMF to delete the session or the bearer.
[0203] In step (922), in response to receiving a session deletion request message from the MME, the SMF may forward the session deletion request message to the UPF. This may be for performing call deletion by releasing existing resources.
[0204] In step (923), UPF can send a session deletion response message to SMF. The session deletion response message may include usage and related information up to that point. For example, if the amount of traffic used by UPF reaches a threshold usage and the transmission of the threshold usage information fails, and UPF uses an additional 20M, the session deletion response message may include information about the additional 20M used.
[0205] In addition, the session deletion response message may include cumulative usage information. The cumulative usage information may include information corresponding to a total cumulative usage (e.g., 400M) by adding the amount of additional traffic used by the UPF after a retransmission failure (e.g., 20M) to the cumulative usage (e.g., 380M) included in the session report message.
[0206] In step (924), in response to checking the usage received from UPF, SMF can confirm that the accumulated usage of SMF is 390M (370M + 20M), but the accumulated usage transmitted from UPF is 400M, resulting in a usage loss of 10M. Subsequently, when SMF reports the usage to OCS, it can transmit 30M, which is the sum of the usage of 20M received from UPF and the confirmed loss of 10M.
[0207] In step (925), the SMF can terminate the session by receiving CCA-T from the OCS.
[0208] In step (926), the SMF can send a Delete Session Response to the MME, and the MME can terminate the session normally.
[0210] FIG. 10 illustrates a recovery operation for loss outside the Sx interface section in a wireless communication system according to one embodiment of the present disclosure.
[0211] Referring to Fig. 10, when usage loss occurs due to order reversal within the system or other reasons other than loss in the Sx / (N4) interval, usage recovery operation can be described by detecting the lost usage.
[0212] In step (1001), the GWU (UPF) may send a session report request message to the GWC (SMF). At this time, the session report request message may be sent when the usage used in the UPF corresponds to a trigger condition. The session report request message may include information such as usage reporting and trigger information, the sequence number of the URR, and the start / end times of traffic occurrence for the URR usage. At this time, the usage may be information related to traffic used in the UPF.
[0213] In addition, the session report request message may include the amount of traffic used (e.g., 80M) along with the accumulated usage (e.g., 300M).
[0214] In step (1002), the SMF can send a session report response message to the UPF. Additionally, the SMF can generate a message to be sent to the OCS based on usage information included in the session report request message received from the UPF.
[0215] SMF adds the new usage (80M) to the existing accumulated usage (220M) and can check whether this combined usage is the same as the newly received accumulated usage (300M).
[0216] In step (1003), in response to confirming that the summed usage of SMF is the same as the newly received cumulative usage, the received usage is determined to be normal and the usage of 80M can be transmitted to OCS.
[0218] In step (1004), the OCS checks the usage received from the CCR, determines the remaining quota based on the checked usage, and can transmit the quota available to the subscriber and event trigger conditions to the SMF. The event trigger conditions may be information related to the threshold usage.
[0219] In step (1005), the SMF may send a session modification request message to the UPF. At this time, the session modification request message may include Quota information and event information received from the OCS in the Update URR. Additionally, the session modification request message may include information regarding usage and event occurrence conditions received from the OCS.
[0220] In step (1006), the UPF may send a session modification response message to the SMF. The session modification response message may include information confirming that the session modification request message transmitted from the SMF has been successfully received and processed.
[0221] After UPF sends a session modification response message to SMF, if the amount of traffic used by UPF reaches a threshold usage, a session report request may occur. UPF may generate a session report request message to send to SMF.
[0223] In step (1007), the SMF may receive an event from the MME. At this time, the event may take the form of receiving a modify bearer request from the MME. Here, the modify bearer request may be executed when a Modify Event or a change in Mobility occurs, such as with a Location CHG / Serving Node CHG.
[0224] In step (1008), the SMF can determine whether to forward usage to the billing server after checking the registered Event Trigger. Depending on whether it is necessary to forward usage to the billing server, the SMF can perform an action to request usage from the UPF. The action to request usage from the UPF may include an action to send a session modification request message to the UPF.
[0225] In step (1009), the UPF may send a Session Modification Response message to the SMF in response to the session modification request message received from the SMF. The session modification response message may include information regarding usage. In this case, the information regarding usage may include information regarding usage used to date (40M) and total accumulated usage (340M).
[0226] In step (1010), if the event transmitted from the MME is an event that requires PCRF (PCF) interoperability, the SMF can perform PCRF (PCF) interoperability without transmitting usage to the billing system.
[0227] In step (1011), the PCRF (PCF) can request the deletion of an existing Rule from the SMF through the RAR.
[0228] In step (1012), SMF can notify PCRF (PCF) through RAA that the Rule has been successfully deleted.
[0229] In step (1013), SMF sends deletion information to UPF to delete information regarding the Rule received from RAR, and may request the usage of the related Rule.
[0230] In step (1014), UPF can transfer usage (25M) and cumulative usage (365M) to SMF.
[0231] In step (1015), the SMF detects the amount of loss between its own accumulated usage (300M) + current usage (25M) and the accumulated usage (365M) received from the UPF, and can transmit usage information of 65M instead of 25M to the OCS.
[0232] In step (1016), after settling the received usage, OCS can send a message to SMF indicating that it has been processed successfully.
[0233] In step (1017), the SMF can receive a delayed CCA-U message.
[0234] In step (1018), the operation for the delayed modification bearer request event is resumed, and the used usage (40M) and the accumulated usage (340M) used in the UPF are checked, and by comparing it with the current accumulated usage (365M) of the SMF, it is detected that the lost usage has already been recovered, so no additional message is sent.
[0235] In step (1018), since the modification bearer request is completed, the response message is sent to the MME. Afterwards, the cumulative usage of SMF and UPF remains the same at 365M, and normal service can be supported.
[0237] According to one embodiment of the present disclosure, a method of operation of a session management function (SMF) includes the steps of: transmitting a request message to a user plane function (UPF) based on session settings; receiving a response message from the UPF; determining whether there is lost usage based on the response message; and, if there is lost usage, transmitting restored usage information to an online charging system (OCS). The response message may include current usage information and cumulative usage information of the UPF.
[0239] Preferably, the process of determining whether the above-mentioned lost usage exists may include a process of comparing the sum of the usage corresponding to the current usage information of the UPF and the usage corresponding to the accumulated usage information stored in the SMF with the usage corresponding to the accumulated usage information.
[0240] Preferably, the restored usage information may be information corresponding to the sum of the usage corresponding to the current usage and the lost usage.
[0241] Preferably, the lost usage amount may be determined based on the usage amount corresponding to the difference between the sum value and the usage amount corresponding to the accumulated usage information.
[0242] Preferably, the request message is a request message associated with a session established for the UPF, and the response message may be a message received in response to the request message.
[0244] According to another aspect of the present disclosure, a session management function (SMF) device comprises: a communication unit; and at least one control unit operably connected to the communication unit, wherein the at least one control unit is configured to transmit a request message to the user plane function (UPF) based on session settings, receive a response message from the UPF, determine whether there is any lost usage based on the response message, and if there is any lost usage, transmit restored usage information to an online charging system (OCS), wherein the response message may include current usage information and cumulative usage information of the UPF.
[0245] Preferably, the at least one processor may be further configured to compare the sum of the usage corresponding to the current usage information of the UPF and the usage corresponding to the cumulative usage information stored in the SMF with the usage corresponding to the cumulative usage information in order to determine whether the lost usage exists.
[0246] Preferably, the restored usage information may be information corresponding to the sum of the usage corresponding to the current usage and the lost usage.
[0247] Preferably, the lost usage amount may be determined based on the usage amount corresponding to the difference between the sum value and the usage amount corresponding to the accumulated usage information.
[0249] Preferably, the request message is a request message associated with a session established for the UPF, and the response message may be a message received in response to the request message.
[0250] According to another embodiment of the present disclosure, a method of operation of a user plane function (UPF) includes the process of receiving a request message from a session management function (SMF) based on session setup and the process of sending a response message from the SMF in response to receiving the request message, wherein the response message includes current usage information and cumulative usage information of the UPF, and the cumulative usage information may be information corresponding to the total amount of traffic used by the UPF since session setup.
[0251] Preferably, the request message is a request message associated with a session established for the UPF, and the response message may be a message received in response to the request message.
[0252] According to another aspect of the present disclosure, a user plane function (UPF) device comprises: a communication unit; and
[0253] It includes at least one control unit, wherein the at least one control unit is configured to receive a request message from the SMF based on the session management function (SMF) and the session setup, and to transmit a response message from the SMF in response to receiving the request message, wherein the response message includes current usage information and cumulative usage information of the UPF, and the cumulative usage information may be information corresponding to the total amount of traffic used by the UPF since the session setup.
[0254] Preferably, the request message is a request message associated with a session established for the UPF, and the response message may be a message received in response to the request message.
[0256] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or multiple items unless the relevant context clearly indicates otherwise. In this document, phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may each include any one of the items listed together in the corresponding phrase, or any combination thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as "coupled" or "connected" to another (e.g., 2nd) component, with or without the terms "functionally" or "communicationly," it means that the component may be connected to the other component directly (e.g., via a wire), wirelessly, or through a third component.
[0257] As used in this document, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be a component formed as a whole, or a minimum unit of a component or part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).
[0258] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) that can be read by a machine (e.g., electronic device (101) (101)). For example, a processor (e.g., processor (120)) of a device (e.g., electronic device (101)) may call at least one of one or more instructions stored from a storage medium and execute it. This enables the device to operate to perform at least one function according to at least one called instruction. One or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium readable by the device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain a signal (e.g., EM wave), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.
[0259] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., CD-ROM (compact disc read-only memory)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
[0260] According to various embodiments, each component (e.g., module or program) of the described components may include a singular or multiple entities. According to various embodiments, one or more of the components or operations among the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as they were performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically; one or more of the operations may be executed in a different order; omitted; or one or more other operations may be added.
Claims
Claim 1 A method performed by an SMF (session management function) entity, comprising: a process of transmitting a request message to a UPF (user plane function) entity based on session settings; a process of receiving a response message from the UPF entity including first information regarding current usage and second information regarding cumulative usage; a process of determining whether there is lost usage based on the first information, the second information and third information regarding previous cumulative usage; and, if there is lost usage, a process of transmitting fourth information regarding restored usage to an OCS (online charging system) entity. Claim 2 A method according to claim 1, wherein the process of determining whether the lost usage exists comprises comparing the sum of the current usage and the previous cumulative usage with the cumulative usage. Claim 3 A method according to claim 2, wherein the fourth information is information corresponding to the sum of the current usage and the lost usage. Claim 4 A method according to claim 2, wherein the lost usage amount is determined based on the difference between the sum value and the accumulated usage amount. Claim 5 A method according to claim 1, wherein the request message is a request message associated with a session established for the UPF entity, and the response message is a message received in response to the request message. Claim 6 An SMF (session management function) entity comprises: a transceiver; a processor; and a memory for storing instructions, wherein the instructions, when executed by the processor, cause the SMF entity to: transmit a request message to a UPF (user plane function) entity based on session settings; receive a response message from the UPF entity including first information regarding current usage and second information regarding cumulative usage; determine whether there is lost usage based on the first information, the second information and third information regarding previous cumulative usage; and if there is lost usage, transmit fourth information regarding restored usage to an OCS (online charging system) entity. Claim 7 In claim 6, the memory further comprises, when executed by the processor, an instruction to the SMF entity to compare the sum of the current usage and the previous cumulative usage with the cumulative usage in order to determine whether the lost usage exists. Claim 8 In claim 7, the fourth information is an SMF entity that is information corresponding to the sum of the current usage and the lost usage. Claim 9 In claim 7, the lost usage is an SMF entity determined based on the difference between the sum value and the accumulated usage. Claim 10 In claim 6, the request message is a request message associated with a session established for the UPF entity, and the response message is an SMF entity that is a message received in response to the request message. Claim 11 A method performed by a user plane function (UPF) entity, comprising: receiving a request message based on session settings from a session management function (SMF) entity; and transmitting a response message to the SMF entity, in response to receiving the request message, the response message including first information regarding current usage and second information regarding cumulative usage, wherein the lost usage is determined based on the first information, the second information, and third information regarding previous cumulative usage, and the second information is information corresponding to the total amount of traffic used by the UPF entity since the session settings. Claim 12 A method according to claim 11, wherein the request message is a request message associated with a session established for the UPF entity, and the response message is a message received in response to the request message. Claim 13 A user plane function (UPF) entity comprises: a transceiver; a processor; and a memory for storing instructions, wherein the instructions, when executed by the processor, cause the UPF entity to: receive a request message based on a session setup from an SMF (session management function) entity, and to send a response message to the SMF entity, in response to receiving the request message, the response message including first information regarding current usage and second information regarding cumulative usage, wherein the lost usage is determined based on the first information, the second information and third information regarding previous cumulative usage, and the second information is information corresponding to the total amount of traffic used by the UPF entity since the session setup. Claim 14 In claim 13, the request message is a request message associated with a session established for the UPF entity, and the response message is a UPF entity that is a message received in response to the request message.
Citation Information
Patent Citations
Systems and methods for tracking and calculating network usage in a network with multiple user plane functions
US20200022020A1
Packet Duplication by Core Network
US20200107213A1
