WO2024025180A1

WO2024025180A1 - Method and device for distinguishing sidelink relay transmission data usage

Info

Publication number: WO2024025180A1
Application number: PCT/KR2023/009157
Authority: WO
Inventors: 배범식; 강현정
Original assignee: 삼성전자 주식회사
Priority date: 2022-07-28
Filing date: 2023-06-29
Publication date: 2024-02-01
Also published as: KR20240016106A

Abstract

The present invention relates to a method comprising the steps of: transmitting a first message including information indicating whether a remote user equipment (UE) is in a state of being connected through a sidelink relay to a central unit-user plane (CU-UP) of a base station; when a preconfigured condition is satisfied, receiving, from the CU-UP, a second message including information on data usage using the sidelink relay of the remote UE; and transmitting a third message including the information on the data usage using the sidelink relay of the remote UE to an access and mobility management function (AMF).

Description

Method and device for distinguishing sidelink relay transmission data usage

The present invention relates to the operation of base stations, terminals, and core networks in mobile communication systems.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

One embodiment of the present invention is in a mobile communication system, when a terminal receives a mobile communication network service by connecting to a mobile communication network using sideline relay technology through connection to a relay-supporting terminal, the data usage time received through the sidelink relay It provides a method to distinguish between overload and usage, and data usage information through differentiated sidelink relays is intended to be used for billing information, etc.

In addition, an embodiment of the present invention is a method in which the base station transmits to the core network whether the terminal is directly connected to the mobile communication base station and whether it is connected to the mobile communication base station through a sidelink relay, and changes the connection policy, for example, QoS parameter settings. The purpose is to provide.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

A method performed by a central unit-control plane (CU-CP) of a base station of a wireless communication system according to an embodiment of the present invention to solve the above problem is that a remote user equipment (UE) Transmitting a first message containing information indicating whether the device is connected through a sidelink relay to a central unit-user plane (CU-UP) of the base station; if preset conditions are met, Receiving a second message from the CU-UP containing information about data usage using the sidelink relay of the remote user terminal; and receiving information about the data usage using the sidelink relay of the remote user terminal It may include transmitting a third message containing the message to an access and mobility management function (AMF).

In addition, the method includes information indicating that the connection through the sidelink relay is in a released state when the connection state of the remote user terminal changes from a connection through the sidelink relay to a wireless interface connection with the base station. transmitting a fourth message to the CU-UP; Receiving a fifth message from the CU-UP containing information on data usage using the sidelink relay of the remote user terminal until the connection through the sidelink relay is released; And it may further include transmitting a sixth message containing information about the data usage using the sidelink relay of the remote user terminal to the AMF.

Additionally, the first message may include at least one of a bearer context setup request message or a bearer context modification request message.

Additionally, the information about the data usage using the sidelink relay of the remote user terminal may be a value calculated for each protocol data unit (PDU) session or for each quality of service (QoS) flow.

In addition, the information on the amount of data usage using the sidelink relay of the remote user terminal is information related to the start time of data transmission and reception using the sidelink relay, and information related to the start time of data transmission and reception using the sidelink relay. It may include at least one of information related to an end time, uplink data usage information, or downlink data usage information.

In addition, a method performed by a central unit-user plane (CU-UP) of a base station of a wireless communication system according to an embodiment of the present invention to solve the above problem is a remote user equipment (UE). ) receiving from a central unit-control plane (CU-CP) of a base station a first message containing information indicating whether the device is connected through a sidelink relay; based on the information, Identifying information about data usage using the sidelink relay of a remote user terminal; and, if a preset condition is satisfied, comprising information about the data usage using the sidelink relay of the remote user terminal. 2 It may include the step of transmitting a message to the CU-CP.

In addition, the method provides information indicating that the connection through the sidelink relay is in a released state when the connection state of the remote user terminal changes from connection through the sidelink relay to a wireless interface connection with the base station. Receiving a fourth message including from the CU-CP; stopping calculation of the data usage using the sidelink relay of the remote user terminal; And it may further include transmitting a fifth message containing information about the data usage using the sidelink relay of the remote user terminal identified up to the time when the calculation is stopped to the CU-CP.

In addition, a central unit-user plane (CU-UP) of a base station of a wireless communication system according to an embodiment of the present invention to solve the above problems includes a transceiver; And a first message connected to the transceiver and containing information indicating whether a remote user equipment (UE) is connected through a sidelink relay is sent to the base station's CU-UP (central unit-user plane), and when preset conditions are met, a second message containing information on data usage using the sidelink relay of the remote user terminal is received from the CU-UP, and the remote user terminal It may include a control unit that transmits a third message containing information about the data usage using the sidelink relay of the user terminal to an access and mobility management function (AMF).

In addition, a central unit-user plane (CU-UP) of a base station of a wireless communication system according to an embodiment of the present invention to solve the above problems includes a transceiver; And a first message connected to the transceiver and containing information indicating whether a remote user equipment (UE) is connected through a sidelink relay is sent to the central CU-CP (central) of the base station. unit-control plane), and based on the information, identify information on data usage using the side link relay of the remote user terminal, and if preset conditions are satisfied, the side link of the remote user terminal It may include a control unit that transmits a second message containing information about the data usage using a link relay to the CU-CP.

One embodiment of the present invention is in a mobile communication system, when a terminal receives a mobile communication network service by connecting to a mobile communication network using sideline relay technology through connection to a relay-supporting terminal, the data usage time received through the sidelink relay It provides a method to distinguish between overload and usage, and data usage information through differentiated sidelink relays can be used for billing information, etc.

In addition, an embodiment of the present invention is a method in which the base station transmits to the core network whether the terminal is directly connected to the mobile communication base station or whether it is connected to the mobile communication base station through a sidelink relay, and changes the connection policy, for example, QoS parameter settings. can be provided.

The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

1 is a diagram illustrating an example structure of a next-generation mobile communication system according to an embodiment of the present invention.

Figure 2 is a signal flow diagram illustrating a procedure for using control information signaling between a CU and a DU to transmit control signals and user data between a remote UE and a base station according to an embodiment of the present invention.

Figure 3a is a diagram illustrating a process in which a remote user terminal performs a connection procedure with a base station through a relay support terminal according to an embodiment of the present invention.

Figure 3b is a diagram illustrating a process in which a remote user terminal performs a connection procedure with a base station through a relay support terminal according to an embodiment of the present invention.

Figure 4 is a diagram showing a process in which a remote user terminal performs a path switch procedure through a wireless interface connection with the base station while the remote user terminal is connected to the base station through a relay support terminal according to an embodiment of the present invention. .

Figure 5 shows an example of a message for a base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 6a is a diagram illustrating a process in which a remote user terminal performs a connection procedure with a base station through a relay support terminal according to an embodiment of the present invention.

Figure 6b is a diagram illustrating a process in which a remote user terminal performs a connection procedure with a base station through a relay support terminal according to an embodiment of the present invention.

Figure 7 is a diagram illustrating a process in which a remote user terminal performs a path switch procedure through a wireless interface connection with the base station while the remote user terminal is connected to the base station through a relay support terminal according to an embodiment of the present invention. .

Figure 8a shows an example of a message for a base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 8b shows an example of a message for the base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 9 is for receiving information on whether a remote user terminal receives a mobile communication service using a sidelink relay from the UPF according to an embodiment of the present invention, so that the UPF can create or stop data usage information provided by the sidelink relay. This is a diagram explaining the base station procedures.

Figure 10 is a diagram for receiving information on whether a remote user terminal receives a mobile communication service using the sidelink relay method in the UPF according to an embodiment of the present invention, so that the UPF can create or stop data usage information provided by the sidelink relay. This is a diagram explaining the UPF procedure.

FIG. 11A is a diagram illustrating a process in which a remote user terminal performs a connection procedure with a base station through a relay support terminal in a separate base station structure according to an embodiment of the present invention.

Figure 11b is a diagram illustrating a process in which a remote user terminal performs a connection procedure with the base station through a relay support terminal in a separate base station structure according to an embodiment of the present invention.

Figure 12 shows a process in which a remote user terminal performs a path switch through a wireless interface connection with the base station while the remote user terminal is connected to the base station through a relay support terminal in a separate base station structure according to an embodiment of the present invention. This is a drawing.

Figure 13a shows an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the CU-UP of the base station according to an embodiment of the present invention.

Figure 13b shows an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the CU-UP of the base station according to an embodiment of the present invention.

Figure 14a shows an example of a message for the CU-UP of the base station to transmit status information of a remote user terminal to the CU-CP of the base station according to an embodiment of the present invention.

Figure 14b shows an example of a message for the CU-UP of the base station to transmit status information of a remote user terminal to the CU-CP of the base station according to an embodiment of the present invention.

Figure 14c shows an example of a message for the CU-UP of the base station to transmit status information of a remote user terminal to the CU-CP of the base station according to an embodiment of the present invention.

Figure 15a shows an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 15b shows an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 15c shows an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Figure 16 shows whether a remote user terminal (remote UE) receives a mobile communication service using a sidelink relay method from the CU-UP of the base station according to an embodiment of the present invention, and the information provided to the sidelink relay from the CU-UP of the base station is shown. This is a diagram explaining the CU-CP procedure of the base station to create or stop data usage information.

Figure 17 shows whether a remote user terminal (remote UE) receives a mobile communication service by a sidelink relay method from the CU-UP of the base station according to an embodiment of the present invention, and the information provided by the CU-UP of the base station to the sidelink relay is shown in Figure 17. This is a diagram explaining the CU-UP procedure of the base station to create or stop data usage information.

Figure 18 shows whether the remote user terminal receives a mobile communication service in the sidelink relay method in 5GC in the process of performing a connection procedure with the base station through a relay support terminal according to an embodiment of the present invention. This is a signal flow diagram that explains the procedure for changing connection policy.

Figure 19 is a diagram showing the configuration of a terminal according to an embodiment of the present invention.

Figure 20 is a diagram showing the configuration of a network entity according to an embodiment of the present invention.

In the following description of the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the attached drawings. And the terms described below are terms defined in consideration of their functions in the present invention. Since this may vary depending on the intention or custom of the user or operator, the definition should be determined according to the contents throughout this specification.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and to provide common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the disclosure.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored on a computer-usable or computer-readable storage medium that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer program instructions are computer-usable or computer-readable. The instructions stored in the storage medium also make it possible to produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA or ASIC, and the '~unit' performs certain roles. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

Specific terms used in the following description are provided to aid understanding of the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

Terms referring to network entities, terms referring to messages, and terms referring to identification information used in this publication are examples for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

For convenience, the present invention uses terms and names defined in the 5G system standard, but is not limited by the terms and names, and can be equally applied to systems that comply with other standards.

Figure 1 is a diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present invention.

Referring to FIG. 1, it shows an example of the structure of a next-generation mobile communication system in which a terminal (user equipment) 10 can receive mobile communication services by connecting to a mobile communication base station 30 through sidelink relay technology. It is a drawing. The RAN Node (30) specified in this structure can be a mobile communication base station connected to a Core Network (CN) (70) such as a 5G Core Network (5GC). For example, the RAN Node 30 may be an LTE eNB or NR gNB. (a) in Figure 1 is a case where the terminal 10 receives a mobile communication service through sidelink relay technology by directly connecting to the mobile communication base station 30 or through another terminal 20 connected to the same mobile communication base station 30. As shown, it shows that path switching between a direct connection and an indirect connection through a sidelink relay is possible. (b) in Figure 1 is a case where the terminal 10 receives a mobile communication service through sidelink relay technology through a direct connection to the mobile communication base station 30 or through another terminal 20 connected to another mobile communication base station 30. As shown, it shows that a path switch between a direct connection and an indirect connection through a sidelink relay to another base station is possible.

In (a) of FIG. 1, a user equipment (UE) 10 receives a mobile communication service through a communication radio interface (for example, Uu interface) with the mobile communication base station 30, or receives a remote communication service. Operates as a user terminal (remote user equipment: UE) (remote UE, remote terminal) (10) and supports relay through a radio interface (for example, PC5 interface) for direct communication between terminals. It connects to the relay UE (relay terminal) 20, and the relay support terminal 20 connects to the base station (RAN Node) 30 through a radio interface (for example, Uu interface) to provide mobile communication service. You will be able to receive. The terminal 10 is connected through a communication radio interface (e.g., Uu interface) with mobile communication, and a direct communication radio interface (e.g., Uu interface) between terminals through the relay support terminal 20. It is possible to support a path switch operation that mutually switches the connection through a communication radio interface (for example, Uu interface) with the mobile communication of the relay support terminal 20 (PC5 interface).

In (b) of FIG. 1, a user equipment (UE) 10 receives a mobile communication service through a communication radio interface (for example, Uu interface) with the mobile communication base station 30. , Direct communication between the terminals through the RAN Node 30 to which the terminal 10 is connected and the relay UE 20 connected to another RAN Node 30 (for example, PC5 interface) ) and the case of switching the connection to receiving a mobile communication service using a communication radio interface (for example, Uu interface) connection with the mobile communication of the relay support terminal 20, and on the contrary, the terminal 10 It can support path switch operation when switching from this relay connection to a direct connection to the base station.

Figure 2 is a diagram showing an example structure of a next-generation mobile communication system according to an embodiment of the present invention.

Referring to FIG. 2, a central unit (CU) and a DU (CU) for transmitting control signals and user data between a remote user terminal (remote UE) 10 and the base station 30 according to an embodiment of the present invention. A signal flow diagram illustrating a procedure using control information signaling between distributed units is shown. The RAN (radio access network) Node 30 specified in this structure can be a mobile communication base station connected to a Core Network (CN) such as a 5G core network (5GC). For example, the RAN Node 30 may be an LTE eNB or NR gNB. For example, the RAN Node 30 is connected to the core network through an interface such as NG (next generation), and may also be connected to another base station (not shown) through an interface such as Xn. Additionally, when the RAN Node 30 has a separate base station structure, the base station 30 may include a central unit (CU) 32 and 34 and a distributed unit (DU) 36. The central unit (CU) may again include a control plane (CU-CP) 32 and a user plane (CU-UP) 34. In one embodiment, the RAN Node (30) consists of one CU-CP (32), one or more CU-UPs (34) and one or more DUs (36) connected thereto, or may be composed of other combinations. . CU-CP (32), CU-UP (34), and DU (36) can support each base station function separately. As an example, the CU-CP 32 processes RRC (radio resource control) and interfaces between base stations, such as the X2 interface and Xn interface, and interfaces between the base station 30 and the Core Network (CN), such as the NG interface and S1 interface. It is responsible for the function of The CU-UP 34 is responsible for processing user data packets by supporting functions such as PDCP (packet data convergence protocol) and SDAP (service data adaptation protocol). The DU 216 supports the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer and can be responsible for radio transmission and reception functions with the terminal. An interface between base station internal functions, such as an F1 or W1 interface, may be connected between the CUs 32 and 34 and the DU 36. In one embodiment, each DU 36 may be divided into a part supporting RLC/MAC/High-PHY and a part supporting Low-PHY/RF layers.

Figure 2 shows the 5GC (5G Core Network) function among the Core Network. 5GC may be composed of an access and mobility management function (AMF) (40), a session management function (SMF) (50), a user plane function (UPF) (60), etc. Other 5GC functions that do not affect the present invention (network entity/function) etc. are not shown.

In FIG. 2, a remote user equipment (UE) 10 is connected to a relay UE 20 through a direct communication radio interface (e.g., PC5 interface) between devices. In this way, the relay support terminal 20 is connected to the base station (RAN Node) 30 through a radio interface (eg, Uu interface). The remote UE 10 performs a communication connection with the base station 30 through the relay UE 20 and sends control signals (eg, RRC signaling) and User data (user plane data) (eg, Internet Protocol packets) can be transmitted and received. Additionally, a remote user equipment (UE) 10 may perform a connection operation with the base station 30 through a radio interface (eg, Uu interface).

Figures 3a and 3b show the process in which a remote user terminal (remote UE) 10 performs a connection procedure with the base station 30 through a relay support terminal (relay UE) 20, according to an embodiment of the present invention. In this case, the UPF (60) receives information about whether the remote UE (10) receives mobile communication service using the sidelink relay method, so that the UPF (60) can generate data usage information provided by the sidelink relay. This is a signal flow diagram explaining the procedure. In FIGS. 3A and 3B, more than one SMF 50 and UPF 60 may be used to provide a mobile communication service for a remote UE 10, but in this signal flow diagram, one SMF 50 is used. ) and UPF 60 are used, and even when multiple SMFs and UPFs are used, the same signal procedure from the AMF 40 can be used.

Referring to FIGS. 3A and 3B, in

steps

301 and 303, the remote user terminal (remote UE) 10 performs a discovery procedure for PC5 link connection for direct communication with the relay support terminal (relay UE) 20. and PC5 connection establishment procedure can be performed. In step 303, settings may be included for the remote user terminal (remote UE) 10 to communicate with the base station 30 of the mobile communication network through the relay support terminal (relay UE) 20.

In step 305, the remote UE 10 transmits an RRC connection request message (for example, an RRCSetupRequest message) to be sent to the base station 30 to the relay UE 20 using the PC5 link. And, the relay support terminal (relay UE) 20 may transmit this RRC connection request message (for example, an RRCSetupRequest message) to the base station 30. When the base station 30 receives the RRC connection request message of the remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20, in step 307, the base station 30 sends the remote user terminal (remote UE) ) An RRC connection setup message (for example, an RRCSetup message) for 10 may be generated and transmitted to a remote user terminal (remote UE) 10 through a relay support terminal (relay UE) 20. And, in step 309, the remote UE (10), relay support terminal (20), and base station 30 set the Uu RLC channel for PC5 connection and SRB1 (Signaling Radio Bearer 1). You can perform operations and signal transmission/reception procedures. Step 309 is a known technique, so detailed procedures are omitted. In step 311, the remote UE 10 may transmit an RRC connection setup complete message (for example, an RRCSetupComplete message) to the base station 30 through the relay UE 20. The base station 30, which has received an RRC connection setup complete message (for example, an RRCSetupComplete message) from the remote UE 10, selects in step 313 to service the remote UE 10 of 5GC. and transmits an INITIAL UE MESSAGE message to the AMF 40 in operation, and sidlelink relay through the relay support terminal 20 to provide mobile communication services to the remote UE 10 up to step 343. You can perform the connection mode setting procedure. In step 313, the AMF 40, which has received the INITIAL UE MESSAGE message from the base station 30, confirms the SMF 50 for connection to a protocol data unit (PDU) session for the service of the remote UE 10. Afterwards, in step 315, Nsmf_PDUSession_UpdateSMContext can be transmitted to the corresponding SMF (50). Then, in step 317, the SMF 50 may again check the UPF 60 for the corresponding PDU session service and then transmit an N4 Session Modification Request to the corresponding UPF 60. In step 319, the UPF (60) responds to the SMF (50) with an N4 Session Modification Response, and the SMF (50) that receives this may transmit Nsmf_PDUSession_UpdateSMContextResponse to the AMF (40) in step 321. Then, the AMF 40 receives a message in step 321 from all SMFs for the service of the remote UE 10, and then transmits an INITIAL UE CONTEXT SETUP REQUEST message to the base station 30 in step 323. (30) may be requested to set context and radio resources for the remote UE (10). The base station 30, which has received the INITIAL UE CONTEXT SETUP REQUEST message from the AMF 40, communicates with the remote user terminal 10 through the relay UE 20 in steps 325 and 327. You can exchange RRC SecurityModeCommand messages and RRC SecurityModeComplete messages for encryption settings. Then, in

steps

329 and 331, the base station 30 transmits an RRC reset message (for example, an RRCReconfiguration message) to the remote UE 10 through the relay UE 20, and An RRC reconfiguration complete message (for example, an RRCReconfigurationComplete message) may be received (via the relay support terminal (relay UE) 20) from the user terminal (remote UE) 10. And, in step 333, the remote UE (10), relay support terminal (20), and base station 30 connect PC5, Signaling Radio Bearer 2 (SRB2), and one or more Data Radio Bearers (DRB). ), the operation and signal transmission/reception procedures for setting up the Uu RLC channel can be performed. This is a known technology, so detailed procedures are omitted. After the setup is completed, the base station 30 transmits an INITIAL UE CONTEXT SETUP RESPONSE message to the AMF 40 in step 335 to set the context and radio resources for the remote UE 10. can be informed to AMF (40). In step 337, the AMF (40) transmits Nsmf_PDUSession_UpdateSMContext to the SMF (50), in step 339, the SMF (50) transmits an N4 Session Modification Request to the UPF (60), and in step 341, the UPF (60) sends the SMF ( 50) can be responded to with N4 Session Modification Response. In step 343, the SMF 50 may transmit Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40. If the process progresses to step 343, the connection procedure for the remote UE 10 is completed, and data packets associated with the remote UE 10 can be transmitted and received in step 345.

The base station 30 can confirm that the remote user terminal (remote UE) 10 is connected through the relay support terminal (relay UE) 20. In this case, the base station 30 sends a message to the AMF 40 in step 347. A SIDELINK RELAY CONNECTION REPORT message can be transmitted. Additionally, this message may include information indicating that the remote UE 10 is connected to a sidelink relay (for example , Sidelink Relay Connection Status IE is set to 'Connected'), and depending on the embodiment, relay support Identifier information of the terminal (relay UE) 20 may be included. The AMF 40, which has received this, may transmit Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 349. The Nsmf_PDUSession_UpdateSMContext message may include information indicating that the sidelink relay is connected (for example, Sidelink Relay Connection Status is set to 'Connected'), and depending on the embodiment, includes Identifier information of the relay support terminal (relay UE) 20. can do. In step 351, the SMF 50 may transmit an N4 Session Modification Request to the UPF 60. The N4 Session Modification Request message may include information indicating that the sidelink relay is connected (for example, Sidelink Relay Connection Status is set to 'Connected'), and depending on the embodiment, the identifier of the relay support terminal (relay UE) 20. May contain information. The UPF 60, which has received the N4 Session Modification Request in step 351, begins counting the user data packet service of the remote UE 10 as data usage using a sidelink relay in step 357, and the data usage information is Data usage information can be generated by counting the amount of packets by terminal, PDU session, or QoS (quality of service) flow, connection usage time, or other methods. In step 353, the UPF 60 responds by sending an N4 Session Modification Response to the SMF 50, and in step 355, the SMF 50 may transmit an Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

Depending on the embodiment, the SIDELINK RELAY CONNECTION REPORT message sent from the base station 30 to the AMF 40 in step 347 is simultaneously with the INITIAL UE CONTEXT SETUP RESPONSE message from the base station 30 to the AMF 40 in step 335, or in step 335. Immediately after 335, the base station 30 may transmit to the AMF 40. In this case, the AMF 40 may receive a SIDELINK RELAY CONNECTION REPORT message from the base station 30 before step 337, in which the AMF 40 sends Nsmf_PDUSession_UpdateSMContext to the SMF 50. When the AMF (40) receives the SIDELINK RELAY CONNECTION REPORT message from the base station (30) before the step 337 procedure, the AMF (40) sends information indicating that the sidelink relay is connected to the Nsmf_PDUSession_UpdateSMContext sent to the SMF (50) in step 337 (for example, Sidelink Relay Connection Status is set to 'Connected') and Identifier information of the relay support terminal (relay UE) 20 may be included, and in step 339, the SMF 50 sends a sidelink to the N4 Session Modification Request sent to the UPF 60. Information indicating that the relay is connected (for example, Sidelink Relay Connection Status is set to 'Connected') and identifier information of the relay support terminal (relay UE) 20 may be included. So, when the AMF (40) receives the SIDELINK RELAY CONNECTION REPORT message from the base station (30) before the step 337 procedure, a sidelink relay is sent from the AMF (40) to the SMF (50) and from the SMF (50) to the UPF (60). Since connection status information is delivered in

steps

337 and 339, additional procedures from steps 349 to 355 may not be performed.

Figure 4 shows a remote user terminal (remote UE) 10 connected to the base station 30 through a relay support terminal (relay UE) 20, according to an embodiment of the present invention. (10) In the process of performing a path switch procedure by connecting a radio interface (for example, Uu interface) with the base station 30, the UPF 60 is connected to a remote user terminal (remote UE). This is a signal flow diagram illustrating a procedure for receiving information about whether (10) is receiving a mobile communication service using the sidelink relay method and allowing the UPF (60) to stop generating data usage information provided to the sidelink relay. In FIG. 4, more than one SMF 50 and UPF 60 may be used to provide mobile communication services to the remote UE 10, but in this signal flow diagram, one SMF 50 and UPF are used. Only the case where (60) is used is shown, and the same signal procedure from AMF (40) can be used even when multiple SMFs and UPFs are used. In addition, Figure 4 shows the procedure when the remote user terminal (remote UE) 10 and the relay support terminal (relay UE) 20 are connected to the same base station 30, but the remote user terminal (remote UE) 10 ) and the relay support terminal (relay UE) 20 are connected to different base stations, the procedure of FIG. 4 can be used, but only the procedure for handover between base stations can be added and operated.

Referring to FIG. 4, a remote user terminal (remote UE) 10 is connected to the base station 30 through a relay support terminal (relay UE) 20 and receives a mobile communication service, and in step 410, the remote user The terminal (remote UE) 10 can transmit and receive data packets of the remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20. As in step 415, the UPF 60 may be counting the user data packet service of the remote UE 10 as data use using a sidelink relay. In step 420, the remote UE 10 measures signals according to the measurement settings for neighboring base stations and relay support candidate terminals 20 set by the base station 30, and then sends the measured results to the base station 30. will report. The base station 30, which has received measurement report information from the remote UE 10, connects the remote UE 10 to a radio interface (e.g., radio interface) with the base station 30 in step 425. For example, it is decided to change to a Uu interface) connection, and an indirect-to-direct path switch procedure is performed to change the connection path of the remote UE (10) from step 430 to step 450. You can do it. When the base station 30 determines a path switch in step 425, the base station 30 connects the relay UE 20 to change the connection path of the remote UE 10 in step 430. An RRC reconfiguration message (for example, an RRCReconfiguration message) can be transmitted to the remote UE 10 through . The remote UE 10 that has received the RRC reset message (for example, the RRCReconfiguration message) performs random access to the base station 30 in step 435 based on the RRC reset message (for example, the RRCReconfiguration message) information. When the procedure is performed and random access is completed, the remote UE 10 may transmit an RRC reconfiguration complete message (for example, an RRCReconfigurationComplete message) to the base station 30 in step 440. The base station 30, which has received a reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE 10, relays in step 445 to cancel the sidelink relay transmission of the remote UE 10. Performs an RRC connection reset procedure with the relay UE (20), and in step 450, the relay support terminal (relay UE) 20 terminates the connection to the remote user terminal (remote UE) 10 and the PC5 link. The procedure can be performed.

If the remote UE 10 confirms in step 440 that the connection procedure through the radio interface (for example, Uu interface) with the base station 30 is completed, the base station 30 performs step 455. A SIDELINK RELAY CONNECTION REPORT message can be transmitted to the AMF 40, and this message contains information indicating that the remote UE 10 is in a sidelink relay disconnected state (for example , Sidelink Relay Connection Status IE as 'Disconnected'). (set to) may be included. Depending on the embodiment, this message may include Identifier information of the relay support terminal (relay UE) 20. The AMF 40, which has received this, may transmit Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 460. The Nsmf_PDUSession_UpdateSMContext message may include information indicating that the sidelink relay is disconnected (for example, Sidelink Relay Connection Status is set to 'Disconnected'). Depending on the embodiment, this message may include Identifier information of the relay support terminal (relay UE) 20. In step 465, the SMF 50 may transmit an N4 Session Modification Request to the UPF 60. The N4 Session Modification Request message may include information indicating that the sidelink relay is disconnected (for example, Sidelink Relay Connection Status is set to 'Disconnected'). Depending on the embodiment, this message may include Identifier information of the relay support terminal (relay UE) 20. The UPF 60, which has received the N4 Session Modification Request in step 465, stops counting the user data packet service of the remote UE 10 as data use using the sidelink relay in step 480, and the remote UE 10 Start counting the user data packet service of (remote UE) 10 as data used in a radio interface (for example, Uu interface) between a general terminal and the base station. Data usage information can be generated by counting the amount of packets for each terminal, PDU session, or QoS flow, connection usage time, or other methods. In step 470, the UPF 60 responds by sending an N4 Session Modification Response to the SMF 50, and in step 475, the SMF 50 may transmit a Nsmf_PDUSession_UpdateSMContextResponse to the AMF.

After the remote user terminal (remote UE) 10 completes the connection procedure with the radio interface (e.g., Uu interface) with the base station 30 in step 440, the remote user terminal (remote UE) 10 is connected to the base station 30 in step 485. Data packets of the UE 10 may be transmitted using a radio interface (eg, Uu interface) between the terminal 10 and the base station 30.

Referring to FIG. 5, the base station 30 connects the sidelink relay of the remote UE 10 to the AMF 40 of the 5GC, used in step 347 of FIGS. 3A and 3B and step 455 of FIG. 4. Shows an example of the configuration of an NGAP message (for example, the SIDELINK RELAY CONNECTION REPORT message) used to convey status information. The NGAP message (e.g., SIDELINK RELAY CONNECTION REPORT message) used to convey sidelink relay connection status information includes Message Type information to distinguish the message type and an identifier to distinguish the terminal in UE-associated signaling, for example, AMF UE NGAP. Contains ID and RAN UE NGAP ID. In addition, it may include Sidelink Relay Connection Status information for the present invention. For example, the Sidelink Relay Connection Status information may include 'Connected' and 'Disconnected' status information, and may be named differently. Additionally, only one of 'Connected' or 'Disconnected' values can be included, or other additional information can be included. This message may additionally include the identifier of the relay UE 20 when the remote UE 10 is connected through the relay UE 20. In addition, the identifier of the relay support terminal (relay UE) 20 may be transmitted in INTEGER format or other formats in addition to OCTET string format. Figure 5 shows an example of an NGAP message (for example, a SIDELINK RELAY CONNECTION REPORT message) used to convey sidelink relay connection status information, but the sidelink relay of the remote UE 10 included in Figure 5 The base station 30 can transmit the connection status information and the identifier information of the relay support terminal (relay UE) 20 to the AMF 40 by including it in an existing NGAP message. In addition, the sidelink relay connection status information of the remote user terminal (remote UE) 10 and the identifier information of the relay support terminal (relay UE) 20 included in FIG. 5 are the same as those in step 349 of FIGS. 3A and 3B. It may also be included in Nsmf_PDUSession_UpdateSMContext, N4 Session Modification Request in step 351, and Nsmf_PDUSession_UpdateSMContext in step 460 of FIG. 4, N4 Session Modification Request in step 465, and the format included in the message depends on the message structure format used in each case. It may vary.

Figures 6a and 6b show the process in which a remote user terminal (remote UE) 10 performs a connection procedure with the base station 30 through a relay support terminal (relay UE) 20 according to an embodiment of the present invention. , UPF 60 receives information about whether the remote UE 10 receives mobile communication services using the sidelink relay method, so that the UPF 60 can generate data usage information provided by the sidelink relay. This is a signal flow diagram explaining the procedure. In FIGS. 6A and 6B, more than one SMF 50 and UPF 60 may be used to provide a mobile communication service for a remote UE 10, but in this signal flow diagram, one SMF 50 is used. ) and UPF 60 are used, and even when multiple SMFs and UPFs are used, the same signal procedure from AMF 40 is used. In the embodiment of FIGS. 3A and 3B, the base station 30 transmits the sidelink relay connection status information of the remote UE 10 to the AMF 40, and the AMF 40 processes the related message and sends the corresponding SMF. The sidelink relay connection status information of the remote UE (10) is added to the message delivered to (50) and delivered. On the other hand, in the embodiment of FIGS. 6A and 6B, the base station 30 adds sidelink relay connection status information to the message content delivered to the SMF 50 through the AMF 40, and the AMF 40 transmits it to the base station 30. ) can simply be transmitted to the SMF (50). In the embodiment of FIGS. 3A and 3B, the AMF 40 must perform additional message processing, while the base station 30 only needs to include the terminal's sidelink relay connection status information once in the message delivered to the AMF 40. In the embodiment of FIGS. 6A and 6B, no additional message processing by the AMF 40 occurs, but the terminal's sidelink relay is connected for each PDU session to the message delivered by the base station 30 to the SMF 50 through the AMF 40. Since status information must be included redundantly, the amount of message information may increase.

Referring to FIGS. 6A and 6B, steps 601 to 645 are performed in the same manner as steps 301 to 345 of FIGS. 3A and 3B. During the process from step 601 to step 645, the base station 30 can confirm that the remote user terminal (remote UE) 10 is connected through the relay support terminal (relay UE) 20. In this case, the base station 30 may transmit a PDU SESSION RESOURCE NOTIFY message to the AMF 40 in step 647. The PDU SESSION RESOURCE NOTIFY message may include a PDU Session Resource Notify Transfer IE to be delivered to the SMF 50 for each PDU session. The PDU Session Resource Notify Transfer IE may include information indicating that the remote UE (10) is connected to the sidelink relay (for example, setting the Sidelink Relay Connection Status IE to 'Connected'), and depending on the embodiment, the relay Identifier information of the support terminal (relay UE) 20 may be included. The AMF 40, which has received the PDU SESSION RESOURCE NOTIFY message from the base station 30 in step 647, transmits Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 649, indicating the PDU session handled by the SMF 50 included in the PDU SESSION RESOURCE NOTIFY message. The PDU Session Resource Notify Transfer IE information may be included and transmitted as is, and the PDU Session Resource Notify Transfer IE information may include information indicating that the sidelink relay is connected (for example, setting the Sidelink Relay Connection Status to 'Connected'), , Depending on the embodiment , the PDU Session Resource Notify Transfer IE information may include Identifier information of the relay support terminal (relay UE) 20. In step 651, the SMF 50 may transmit an N4 Session Modification Request to the UPF 60. The N4 Session Modification Request message may include information indicating that the sidelink relay is connected (for example, Sidelink Relay Connection Status is set to 'Connected'), and depending on the embodiment, the identifier of the relay support terminal (relay UE) 20. May contain information. The UPF 60, which has received the N4 Session Modification Request in step 651, begins counting the user data packet service of the remote UE 10 using the sidelink relay in step 657, and the data usage information is Data usage information can be generated by counting the amount of packets by terminal, PDU session, or QoS flow, connection usage time, or other methods. In step 653, the UPF 60 responds by sending an N4 Session Modification Response to the SMF 50, and in step 655, the SMF 50 may transmit an Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

Figure 7 shows a remote user terminal (remote UE) (10) connected to the base station 30 through a relay support terminal (relay UE) 20 according to an embodiment of the present invention. 10) In the process of performing a path switch procedure by connecting a radio interface (for example, Uu interface) with the base station 30, the UPF 60 connects a remote user terminal (remote UE) ( 10) This is a signal flow diagram explaining the procedure for receiving information on whether a mobile communication service is received through the sidelink relay method and allowing the UPF 60 to stop generating data usage information provided to the sidelink relay. In FIG. 7, more than one SMF 50 and UPF 60 may be used to provide mobile communication services for the remote UE 10, but in this signal flow diagram, one SMF 50 and UPF are used. Only the case where (60) is used is shown, and even when multiple SMFs and UPFs are used, the same signal procedure from AMF (40) is used. In addition, Figure 7 shows the procedure when the remote user terminal (remote UE) 10 and the relay support terminal (relay UE) 20 are connected to the same base station 30, but the remote user terminal (remote UE) 10 ) and the relay support terminal (relay UE) 20 are connected to different base stations, the procedure of FIG. 7 can be used, but only the procedure for handover between base stations can be added and operated. In the embodiment of FIG. 4, the base station 30 transmits the sidelink relay connection status information of the remote UE 10 to the AMF 40, and the AMF 40 processes the related message and sends it to the corresponding SMF 50. The sidelink relay connection status information of the remote UE 10 is added to the message delivered to the message. On the other hand, in the embodiment of FIG. 7, the base station 30 adds sidelink relay connection status information to the message content delivered to the SMF 50 through the AMF 40, and the AMF 40 transmits the message received from the base station 30. The information is simply transmitted to the SMF (50). In the embodiment of FIG. 4, the AMF 40 must perform additional message processing, while the base station 30 only needs to include the terminal's sidelink relay connection status information once in the message delivered to the AMF 40, as shown in FIG. 7. In the embodiment, no additional message processing by the AMF (40) occurs, but the sidelink relay connection status information of the terminal is redundantly included for each PDU session in the message that the base station 30 delivers to the SMF (50) through the AMF (40). Since it must be included, the amount of message information may increase.

Referring to FIG. 7, steps 710 to 750 are performed in the same manner as steps 410 to 450 of FIG. 4. If the remote UE 10 confirms in step 740 that the connection procedure through the radio interface (for example, Uu interface) with the base station 30 is completed, the base station 30 performs step 755. A PDU SESSION RESOURCE NOTIFY message can be transmitted to the AMF 40. Additionally, the PDU SESSION RESOURCE NOTIFY message may include a PDU Session Resource Notify Transfer IE to be delivered to the SMF 50 for each PDU session. The PDU Session Resource Notify Transfer IE may include information indicating that the remote UE 10 is in a sidelink relay disconnected state (for example , Sidelink Relay Connection Status IE is set to 'Disconnected'). Depending on the embodiment , the PDU Session Resource Notify Transfer IE may include identifier information of the relay support terminal (relay UE) 20. The AMF 40, which has received the PDU SESSION RESOURCE NOTIFY message from the base station 30 in step 755, transmits Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 760, indicating the PDU session handled by the SMF 50 included in the PDU SESSION RESOURCE NOTIFY message. The PDU Session Resource Notify Transfer IE information can be included and transmitted as is, and the PDU Session Resource Notify Transfer IE information can include information indicating that the sidelink relay is disconnected (for example, setting the Sidelink Relay Connection Status to 'Disconnected'). And, depending on the embodiment , the PDU Session Resource Notify Transfer IE information may include Identifier information of the relay support terminal (relay UE) 20. In step 765, the SMF 50 may transmit an N4 Session Modification Request to the UPF 60. The N4 Session Modification Request message may include information indicating that the sidelink relay is disconnected (for example, Sidelink Relay Connection Status is set to 'Disconnected'), and depending on the embodiment, the relay support terminal (relay UE) 20 Identifier information may be included. The UPF 60, which has received the N4 Session Modification Request in step 765, stops counting the user data packet service of the remote UE 10 as data use using the sidelink relay in step 780, and the remote UE 10 stops counting the user data packet service using the sidelink relay. Start counting the user data packet service of (remote UE) 10 as data used in a radio interface (for example, Uu interface) between a general terminal and the base station. Data usage information can be generated by counting the amount of packets for each terminal, PDU session, or QoS flow, connection usage time, or other methods. In step 770, the UPF 60 responds by sending an N4 Session Modification Response to the SMF 50, and in step 775, the SMF 50 may transmit a Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

After the remote user terminal (remote UE) 10 completes the connection procedure with the radio interface (e.g., Uu interface) with the base station 30 in step 740, the remote user terminal (remote UE) 10 is connected to the base station 30 in step 785. Data packets of the UE 10 may be transmitted using a radio interface (eg, Uu interface) between the terminal 10 and the base station 30.

Figures 8a and 8b show an example of a message for a base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Referring to FIGS. 8A and 8B, used in step 647 of FIGS. 6A and 6B and step 755 of FIG. 7, the base station 30 sends a remote user terminal (remote) to the SMF 50 through the AMF 40 of the 5GC. It shows an example of the configuration of an NGAP message (for example, a PDU SESSION RESOURCE NOTIFY message) used to deliver sidelink relay connection status information of a UE. The NGAP message (eg, PDU SESSION RESOURCE NOTIFY message) used to transmit sidelink relay connection status information shown in FIG. 8A includes a PDU Session Resource Notify Transfer IE for the base station 30 to transmit to the SMF 50. there is. The PDU Session Resource Notify Transfer IE shown in Figure 8b may include Sidelink Relay Connection Status information for the present invention. For example, the Sidelink Relay Connection Status information may include 'Connected' and 'Disconnected' status information, The name may be referred to differently. Additionally, only one of 'Connected' or 'Disconnected' values can be included, or other additional information can be included. This PDU Session Resource Notify Transfer IE additionally includes an identifier of the relay UE (20) when the remote UE (10) is connected through the relay UE (20). ), and the identifier of the relay support terminal (relay UE) 20 may be transmitted in INTEGER format or other formats in addition to OCTET string format. Figures 8a and 8b show an example of an NGAP message (for example, a SIDELINK RELAY CONNECTION REPORT message) used to convey Sidelink relay connection status information, but the remote UE included in Figures 8a and 8b (remote UE) ( The base station 30 includes the sidelink relay connection status information of 10) and the identifier information of the relay support terminal (relay UE) 20 by defining another existing NGAP message or a new NGAP message and the AMF 40. can be sent to.

And, as shown in FIG. 8A, the PDU SESSION RESOURCE NOTIFY message may include a PDU session resource notify list, and the PDU session resource notify list may include a PDU Session Resource Notify Transfer IE for each PDU session. Accordingly, a PDU session ID to identify the PDU session corresponding to each PDU Session Resource Notify Transfer IE may be included in the PDU SESSION RESOURCE NOTIFY message.

Figure 8b shows that Sidelink Relay Connection Status information can be set for each PDU session. However, in another embodiment of the present invention, Sidelink Relay Connection Status information may be set for each QoS flow. For example, in order to indicate the Sidelink Relay Connection Status for each QoS flow, the PDU Session Resource Notify Transfer IE may be configured so that the Sidelink Relay Connection Status information is included in the QoS flow notify item included in the QoS flow notify list. For example, the PDU Session Resource Notify Transfer IE may be configured as follows: QoS Flow Notify List >QoS Flow Notify Item >>QoS Flow Identity >>Notification Cause >>Sidelink Realy Connection Status. Additionally, depending on the embodiment, identifier information of the relay support terminal (relay UE) 20 may also be included in the QoS flow notify item.

Figure 9 shows a method of receiving information on whether a remote user terminal (remote UE) receives a mobile communication service using a sidelink relay method in the UPF according to an embodiment of the present invention, and generating or stopping data usage information provided by the sidelink relay in the UPF. This is a diagram explaining the base station's procedures to enable this. The embodiment of FIG. 9 is a base station for transmitting sidelink relay connection status information of a remote user terminal (remote UE) at the base station according to the embodiments of FIGS. 3A, 3B, 4, 6A, 6B, and 7. Shows a flowchart showing the operation.

Referring to FIG. 9, in step 910, when the base station detects a change in connection operation (status) of a remote user terminal (remote UE) through a sidelink relay through a relay support terminal (relay UE), in step 920 A remote user terminal (remote UE) can determine whether a connection is established through a sidelink relay through a relay support terminal (relay UE). And, as a result of the determination in step 920, if the remote user terminal (remote UE) is connected to the sidelink relay through the relay support terminal (relay UE), the base station connects the remote user terminal (remote UE) through the sidelink relay in step 930. An NGAP message containing information indicating that a connection has been established can be transmitted to 5GC. This message may also include identifier information of the relay support terminal (relay UE). In step 920, if it is determined that the remote user terminal (remote UE) has changed from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (e.g., Uu interface) connection with the base station, In step 940, the base station may transmit an NGAP message including information indicating that the remote UE has been disconnected through the sidelink relay to the 5GC. Depending on the embodiment, 5GC may be AMF.

Figure 10 shows a method of receiving information on whether a remote user terminal (remote UE) receives a mobile communication service using a sidelink relay method in the UPF according to an embodiment of the present invention, and generating or stopping data usage information provided by the sidelink relay in the UPF. This is a diagram explaining the UPF procedure to enable this. The embodiment of FIG. 10 generates or generates data usage information provided by a sidelink relay of a remote UE in the UPF according to the embodiment of FIGS. 3A, 3B, 4, 6A, 6B, and 7. Shows a flow chart illustrating the stopping operation.

Referring to FIG. 10, when the UPF receives information indicating a change in connection operation through the sidelink relay of the remote user terminal (remote UE) using the N4 message from the SMF in step 1010, the UPF receives information indicating a change in connection operation through the sidelink relay of the remote user terminal (remote UE) in step 1020. The terminal (remote UE) can determine whether a connection is established through a sidelink relay through a relay support terminal (relay UE). And, as a result of the determination in step 1020, if the remote user terminal (remote UE) is connected to the sidelink relay through the relay support terminal (relay UE), the UPF is connected to the user of the remote user terminal (remote UE) 10 in step 1030. Stop counting the data packet service as data used as a radio interface (e.g., Uu interface) between a general terminal and the base station, and stop counting the user data packet service of a remote user terminal (remote UE) 10. Start counting by using data using sidelink relay. In step 1020, if it is determined that the remote user terminal (remote UE) has changed from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (e.g., Uu interface) connection with the base station, In step 1040, the UPF stops counting the user data packet service of the remote UE (10) as data use using the sidelink relay, and stops counting the user data packet service of the remote UE (10). Counting begins with data used through a radio interface (for example, Uu interface) between a general terminal and a base station.

11A and 11B show a remote user terminal (remote UE) 10 performing a connection procedure with the base station 30 through a relay support terminal (relay UE) 20 in a separate base station structure according to an embodiment of the present invention. In the process, the CU-UP (Central Unit-User Plane) 34 of the base station 30 receives information about whether the remote UE 10 receives a mobile communication service using a sidelink relay method, This is a signal flow diagram explaining the procedure for generating and transmitting data usage information provided from the CU-UP (34) to the sidelink relay. In FIGS. 11A and 11B, more than one SMF 50 and UPF 60 may be used to provide mobile communication services to the remote UE 10, but in this signal flow diagram, only one SMF 50 is used. ) and UPF 60 are used, and even when multiple SMFs and UPFs are used, the same signal procedure from the AMF 40 can be used.

Referring to FIGS. 11A and 11B, in

steps

1101 and 1103, the remote UE (10) performs a discovery procedure for PC5 link connection for direct communication with the relay support terminal (relay UE) (20). and PC5 connection establishment procedure can be performed. In step 1103, settings for the remote user terminal (remote UE) 10 to communicate with the base station 30 of the mobile communication network through the relay support terminal (relay UE) 20 may be included.

In step 1105, the remote UE 10 transmits an RRC connection request message (for example, an RRCSetupRequest message) to be sent to the base station 30 to the relay UE 20 using the PC5 link. And, the relay support terminal (relay UE) 20 may transmit this RRC connection request message (for example, an RRCSetupRequest message) to the base station 30. And, the RRC connection request message (for example, the RRCSetupRequest message) is transmitted to the CU-CP 32 through the DU 36 of the base station 30. When the CU-CP (32) of the base station receives the RRC connection request message of the remote user terminal (remote UE) (10) through the relay support terminal (relay UE) (20), the CU-CP (32) in step 1107 Generates an RRC connection setup message (e.g., RRCSetup message) for the remote UE (10) and sends it to the remote UE (remote UE) through the DU (36) and the relay support terminal (relay UE) (20). An RRC connection setup message (for example, an RRCSetup message) can be transmitted to (10). And, in step 1109, the remote user terminal (remote UE) (10), relay support terminal (relay UE) (20), and base station (30; 32, 34, 36) for PC5 connection and SRB1 (Signaling Radio Bearer 1). The operation and signal transmission/reception procedures for setting up the Uu RLC channel can be performed. This is a known technology, so detailed procedures are omitted. In step 1111, the remote UE 10 may transmit an RRC connection setup complete message (for example, an RRCSetupComplete message) to the base station 30 through the relay UE 20. The CU-CP 32, which has received an RRC connection setup completion message (for example, an RRCSetupComplete message) from the remote UE 10 via the DU 36 of the base station 30, sets the remote UE 10 to a remote location of 5GC in step 1113. An INITIAL UE MESSAGE message is transmitted to the AMF 40 that is selected and operating to service the user terminal (remote UE) 10, and the process for providing mobile communication service to the remote user terminal (remote UE) 10 is performed until step 1147. The sidlelink relay connection mode setting procedure can be performed through the relay support terminal (relay UE) 20. In step 1113, the AMF 40, which has received the INITIAL UE MESSAGE message from the CU-CP 32 of the base station 30, sends the SMF 50 to the PDU session connection for the service of the remote UE 10. After checking, Nsmf_PDUSession_UpdateSMContext can be transmitted to the corresponding SMF 50 in step 1115. Then, in step 1117, the SMF 50 may again check the UPF 60 for the corresponding PDU session service and then transmit an N4 Session Modification Request. In step 1119, the UPF 60 responds to the SMF 50 with an N4 Session Modification Response, and the SMF 50 that receives this may transmit Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40 in step 1121. Then, the AMF 40 receives a message in step 1121 from all SMFs for the service of the remote UE 10, and then sends INITIAL UE CONTEXT to the CU-CP 32 of the base station 30 in step 1123. By transmitting a SETUP REQUEST message, the base station 30 can be requested to set up context and radio resources for the remote UE 10. The CU-CP 32 of the base station 30, which has received the INITIAL UE CONTEXT SETUP REQUEST message from the AMF 40, may transmit a BEARER CONTEXT SETUP REQUEST message to the CU-UP 34 in step 1125. The BEARER CONTEXT SETUP REQUEST message may include information indicating that the remote UE 10 is in a sidelink relay connection state (for example , Sidelink Relay Connection Status IE is set to 'Connected'). In step 1127, the CU-UP 34 may respond by sending a BEARER CONTEXT SETUP RESPONSE message to the CU-CP 32.

In

steps

1129 and 1131, the CU-CP (32) sends an RRC SecurityModeCommand message and an RRC SecurityModeComplete message to the remote user terminal (remote UE) (10) and radio section encryption settings through the relay support terminal (relay UE) (20). You can give and receive. And, in

steps

1133 and 1135, the CU-CP 32 sends an RRC reset message (for example, RRCReconfiguration ) to the remote UE 10 through the DU 36 and the relay UE 20. message) and receive an RRC reset completion message (for example, an RRCReconfigurationComplete message) from a remote user terminal (remote UE) 10 (via relay UE 20 and DU 36). there is. And in step 1137, the remote user terminal (remote UE) 10, relay support terminal 20, and base station 30 connect PC5, Signaling Radio Bearer 2 (SRB2), and one or more Data Radio Bearers (DRB). The operation and signal transmission/reception procedures for setting up the Uu RLC channel can be performed. This operation is a known technique, so detailed procedures are omitted. After setup is complete, the CU-CP (32) may transmit a BEARER CONTEXT MODIFICATION REQUEST message to the CU-UP (34) in step 1139. The BEARER CONTEXT MODIFICATION REQUEST message may include information indicating that the remote UE 10 is in a sidelink relay connection state (for example , Sidelink Relay Connection Status IE is set to 'Connected'). In step 1141, the CU-UP 34 may respond by sending a BEARER CONTEXT MODIFICATION RESPONSE message to the CU-CP 32.

Information indicating that the remote UE (10) is in a sidelink relay connection state included in the message transmitted by the CU-CP (32) in step 1125 or step 1139 (for example , Sidelink Relay Connection Status IE to 'Connected') According to the settings), in step 1143, the CU-UP 34 starts counting the data use of the user data packet service of the remote UE 10 using the sidelink relay.

Depending on the embodiment, information indicating that the remote UE 10 is in a sidelink relay connection state (for example, setting Sidelink Relay Connection Status IE to 'Connected') included in the message transmitted in step 1125 is remote UE 10. This may indicate the initial connection status of the user terminal (remote UE) 10. In addition, information indicating that the remote UE 10 is in a sidelink relay connection state (for example, setting Sidelink Relay Connection Status IE to 'Connected') included in the message transmitted in step 1139 is used by the remote user during the connection setup process. When the connection state of the remote UE 10 changes (for example, when the sidelink relay is changed from a non-connected state to a connected state), the changed state information may be indicated. Depending on the embodiment, if the connection status of the remote UE 10 has not changed, the message transmitted in step 1139 may not include connection status information of the remote UE 10. there is.

Depending on the embodiment, connection status information of the remote UE 10 may be included in either the message transmitted in step 1125 or the message transmitted in step 1139. For example, the message transmitted in step 1125 does not include connection status information of the remote UE 10, and the message transmitted in step 1139 does not include connection status information of the remote UE 10. may be included.

In step 1145, the CU-CP (32) transmits an INITIAL UE CONTEXT SETUP RESPONSE message to the AMF (40) to send the context and radio resource settings for the remote UE (10) to the AMF. You can inform (40). In step 1147, the AMF (40) transmits Nsmf_PDUSession_UpdateSMContext to the SMF (50), and in step 1149, the SMF (50) may transmit an N4 Session Modification Request to the UPF (60). And, in step 1151, the UPF 60 may respond to the SMF 50 with an N4 Session Modification Response. In step 1153, the SMF 50 may transmit Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40. If the process progresses to step 1153, the connection procedure for the remote UE 10 is completed, and data packets associated with the remote UE 10 can be transmitted and received in step 1155.

Thereafter, according to the information set for reporting Sidelink Relay data usage to the CU-UP 34 (e.g., cycle information set by OAM or implementation), the CU-UP 34 performs a Sidelink Relay data usage report in step 1157. If necessary, in step 1159, CU-UP (34) passes Sidelink Relay data usage information to CU-CP (32) (for example, using the SIDELINK RELAY DATA USAGE REPORT message), and in step 1161, CU-CP (32) Can deliver Sidelink Relay data usage information to the AMF 40 (as an example, using the SIDELINK RELAY DATA USAGE REPORT message). Depending on the embodiment, in step 1157, the CU-UP 34 may identify that Sidelink Relay data usage reporting will be performed when the cycle or condition indicated by the configuration information is satisfied according to the configuration information received from the core network entity. . Alternatively, depending on the embodiment, the CU-UP 34 may identify that reporting will be performed when receiving an instruction from another network entity to report Sidelink Relay data usage in step 1157. The Sidelink Relay data usage information includes information related to the start time of transmitting and receiving data using the Sidelink Relay (e.g., start time stamp), information related to the end time (e.g., end time stamp), and downlink usage. It may include at least one of usage information (eg, usage count DL) and uplink usage information (eg, usage count UL). Depending on the embodiment, the Sidelink Relay data usage information may be calculated for each PDU session and reported by the CU-UP (34) to the CU-CP (32). Alternatively, depending on the embodiment, the Sidelink Relay data usage information may be calculated for each QoS flow and reported by the CU-UP (34) to the CU-CP (32). The AMF 40 may transmit the Sidelink Relay data usage information received from the base station 30 in step 1163 by including it in the Nsmf_PDUSession_UpdateSMContext message to the SMF 50 in charge of the corresponding PDU session. In step 1165, the SMF 50 may respond by sending Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

Figure 12 shows a remote user terminal (remote UE) 10 connected to the base station 30 through a relay UE 120 in a separated base station structure according to an embodiment of the present invention. In the process of the remote UE (10) performing a path switch procedure through a radio interface (e.g., Uu interface) connection with the base station (30), the CU-UP (CU-UP) of the base station (30) The Central Unit-User Plane (34) receives information on whether the remote UE (10) receives mobile communication services using a sidelink relay, and receives data usage information provided by the sidelink relay from the CU-UP (34). This is a signal flow diagram explaining the procedure for stopping generation. In FIG. 12, more than one SMF 50 and UPF 60 may be used to provide mobile communication services to the remote UE 10, but in this signal flow diagram, one SMF 50 and UPF are used. Only the case where (60) is used is shown, and the same signal procedure from AMF (40) can be used even when multiple SMFs and UPFs are used. In addition, Figure 12 shows the procedure when the remote user terminal (remote UE) 10 and the relay support terminal (relay UE) 20 are connected to the same base station 30, but the remote user terminal (remote UE) 10 ) and the relay support terminal (relay UE) 20 are connected to different base stations, the procedure of FIG. 12 can be used, but only the procedure for handover between base stations can be added and operated.

Referring to FIG. 12, in a state where a remote user terminal (remote UE) 10 is connected to the base station 30 through a relay support terminal (relay UE) 20 and receives a mobile communication service, the remote user UE 10 receives a mobile communication service. The terminal (remote UE) 10 can transmit and receive data packets of the remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20. In step 1215, the CU-UP 34 of the base station 30 may be counting the data usage of the user data packet service of the remote UE 10 using a sidelink relay.

In step 1220, the remote user terminal (remote UE) 10 measures signals according to the measurement settings for neighboring base stations and relay support candidate terminals set by the base station 30, and then reports the measured results to the relay support terminal (relay UE) ( 20) and is reported to the CU-CP (32) of the base station (30) through the DU (36) of the base station (30). The CU-CP 32, which has received measurement report information from the remote UE 10, connects the remote UE 10 to a radio interface with the base station 30 in step 1225. (e.g., Uu interface) decides to change to a connection, and performs an indirect-to-direct path switch procedure to change the connection path of the remote UE (10) from step 1230 to step 1250. You can. When the CU-CP 32 determines a path switch in step 1225, the DU 36 and the relay UE (relay UE) are used to change the connection path of the remote UE 10 in step 1230. An RRC reconfiguration message (for example, an RRCReconfiguration message) can be transmitted to the remote UE 10 through 20). The remote UE 10 that has received the RRC reset message (for example, the RRCReconfiguration message) performs random access to the base station 30 in step 1235 based on the RRC reset message (for example, the RRCReconfiguration message) information. After performing the procedure and completing random access, in step 1240, the remote UE 10 sends an RRC reset completion message (for example, an RRCReconfigurationComplete message) to the CU-CP 32 through the DU 36. ) can be transmitted. The CU-CP 32, which has received a reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE 10, performs step 1245 to cancel the sidelink relay transmission of the remote UE 10. An RRC connection re-establishment procedure is performed with the relay UE 20 through the DU 32, and in step 1250, the relay UE 20 is connected to a remote user terminal 10. ) and PC5 links can be disconnected.

In step 1240, when the remote UE 10 confirms that the connection procedure with the radio interface (e.g., Uu interface) with the base station 30 is completed, the CU-CP 32 In step 1255, a BEARER CONTEXT MODIFICATION REQUEST message can be transmitted to the CU-UP (34), and this message includes information indicating that the remote UE (10) is in a sidelink relay disconnected state (for example , Sidelink Relay Connection Status IE (set to 'Disconnected') may be included. In step 1260, the CU-UP 34 may respond by sending a BEARER CONTEXT MODIFICATION RESPONSE message to the CU-CP 32.

In step 1255, after the CU-UP 34 receives information indicating that the remote UE 10 is in a sidelink relay disconnected state (for example , Sidelink Relay Connection Status IE is set to 'Disconnected'), 1265 At this stage, the CU-UP 34 may stop counting the user data packet service of the remote UE 10 using a sidelink relay. In addition, the CU-UP 34 may transmit Sidelink Relay data usage information to the CU-CP 32 as data usage information of the remote UE 10 in step 1270 (for example, SIDELINK RELAY DATA USAGE using the REPORT message). And, in step 1275, the CU-CP (32) can transmit Sidelink Relay data usage information to the AMF (40) (for example, using the SIDELINK RELAY DATA USAGE REPORT message). The AMF 40 may transmit the Sidelink Relay data usage information received from the base station 30 in step 1275 by including it in the Nsmf_PDUSession_UpdateSMContext message to the SMF 50 in charge of the corresponding PDU session in step 1280. In step 1285, the SMF 50 may respond by sending Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40. The Sidelink Relay data usage information includes information related to the start time of transmitting and receiving data using the Sidelink Relay (e.g., start time stamp), information related to the end time (e.g., end time stamp), and downlink usage. It may include at least one of usage information (eg, usage count DL) and uplink usage information (eg, usage count UL). And the Sidelink Relay data usage information can be determined for each PDU session or each QoS flow.

After the remote user terminal (remote UE) 10 completes the connection procedure with the radio interface (e.g., Uu interface) with the base station 30 in step 1240, the remote user terminal (remote UE) 10 is connected to the base station 30 in step 1290. Data packets of the UE 10 may be transmitted using a radio interface (eg, Uu interface) between the terminal 10 and the base station 30.

Figures 13a and 13b show an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the CU-UP of the base station according to an embodiment of the present invention.

Referring to FIGS. 13A and 13B, the CU-CP of the base station, used in step 1125 or step 1139 of FIGS. 11A and 11B, and step 1255 of FIG. 12, transmits the CU-UP of the base station to the CU-UP of the remote UE. It shows an example of the configuration of an E1AP message (for example, the BEARER CONTEXT SETUP REQUEST message and the BEARER CONTEXT MODIFICATION REQUEST message) used to convey sidelink relay connection status information. The E1AP message used to convey sidelink relay connection status information includes Message Type information to distinguish the message type and an identifier to distinguish the terminal in UE-associated signaling, such as gNB-CU-CP UE E1AP ID and RgNB-CU. -UP May include UE E1AP ID. In addition, it may include Sidelink Relay Connection Status information for the present invention. For example, the Sidelink Relay Connection Status information may include 'Connected' and 'Disconnected' status information, and may be named differently. Additionally, only one of 'Connected' or 'Disconnected' values can be included, or other additional information can be included. Figures 13a and 13b show examples of E1AP messages (for example, the BEARER CONTEXT SETUP REQUEST message and the BEARER CONTEXT MODIFICATION REQUEST message) used to convey sidelink relay connection status information, but the remote user included in Figures 11a and 11b The sidelink relay connection status information of the remote UE can be transmitted from CU-CP to CU-UP by including it in other existing E1AP messages or by defining and including a new E1AP message.

Figures 14a, 14b, and 14c show an example of a message for the CU-UP of the base station to transmit status information of a remote user terminal to the CU-CP of the base station according to an embodiment of the present invention.

Referring to FIGS. 14A, 14B, and 14C, the CU-UP 34 of the base station, used in step 1159 of FIGS. 11A and 11B and step 1270 of FIG. 12, transmits a remote signal to the CU-CP 32 of the base station. It shows an example of the configuration of an E1AP message (for example, the SIDELINK RELAY DATA USAGE REPORT message) used to deliver Sidelink Relay data usage information of a user terminal (remote UE). The E1AP message used to convey sidelink relay data usage information includes Message Type information to distinguish the message type and an identifier to distinguish the terminal in UE-associated signaling, such as gNB-CU-CP UE E1AP ID and gNB. -CU-UP May include UE E1AP ID. In addition, it may include Sidelink Relay Data Usage Information (for example , Sidelink Relay Data Usage Information IE for each PDU session) of a remote UE for the present invention. Sidelink Relay data usage information (for example , Sidelink Relay Data Usage Information IE) includes data usage time using sidelink relay for each PDU session (for example, Start timestamp and End timestamp) and data usage information (for example, Usage count UL and Usage count DL). May contain information. Data usage time and data usage information may include all or only one piece of information.

Depending on the embodiment, Sidelink Relay data usage information of a remote UE may be determined for each QoS flow. As an example, Sidelink Relay data usage information of a remote UE may include Sidelink Relay Data Usage Information IE for each QoS flow. For this purpose, information identifying the corresponding QoS flow (e.g., QoS flow indicator) may be included in the Sidelink Relay Data Usage Information IE. Sidelink Relay data usage information (for example , Sidelink Relay Data Usage Information IE) includes data usage time using sidelink relay for each QoS flow (for example, Start timestamp and End timestamp) and data usage information (for example, Usage count UL and Usage count DL) May contain information.

Figures 15a, 15b, and 15c show an example of a message for the CU-CP of the base station to transmit status information of a remote user terminal to the AMF according to an embodiment of the present invention.

Referring to FIGS. 15A, 15B, and 15C, the CU-CP 32 of the base station, used in step 1161 of FIGS. 11A and 11B and step 1275 of FIG. 12, transmits a remote user terminal signal to the AMF 40 of the 5GC. It shows an example of the configuration of an NGAP message (for example, the SIDELINK RELAY DATA USAGE REPORT message) used to deliver Sidelink Relay data usage information of (remote UE). The NGAP message used to convey sidelink relay data usage information includes Message Type information to distinguish the message type and an identifier to distinguish the terminal in UE-associated signaling, such as AMF UE NGAP ID and RAN UE NGAP ID. there is. In addition, it may include Sidelink Relay data usage information (for example , Sidelink Relay Data Usage Report Transfer IE for each PDU session) of a remote UE for the present invention, and may also include other information. Sidelink Relay data usage information (e.g., Sidelink Relay Data Usage Report Transfer IE) includes data usage time using sidelink relay for each PDU session (e.g., Start timestamp and End timestamp) and data usage information (e.g., Usage count UL and Usage count DL) ) information, and the data usage time and data usage information may include all or only one piece of information. AMF 40 transmits Sidelink Relay data usage information (for example , Sidelink Relay Data Usage Report Transfer IE) to SMF 50.

Depending on the embodiment, Sidelink Relay data usage information of a remote UE may be determined for each QoS flow. As an example, Sidelink Relay data usage information of a remote UE may include Sidelink Relay Data Usage Report Transfer IE for each QoS flow. To this end, information identifying the corresponding QoS flow (e.g., QoS flow indicator) may be included in the Sidelink Relay Data Usage Report Transfer IE. Sidelink Relay data usage information (e.g., Sidelink Relay Data Usage Report Transfer IE) includes data usage time using sidelink relay for each QoS flow (e.g., Start timestamp and End timestamp) and data usage information (e.g., Usage count UL and Usage count DL) ) information may be included.

Figure 16 shows whether a remote user terminal (remote UE) receives a mobile communication service using a sidelink relay method from the CU-UP of the base station according to an embodiment of the present invention, and the information provided to the sidelink relay from the CU-UP of the base station is shown. This is a diagram explaining the CU-CP procedure of the base station to create or stop data usage information. The embodiment of FIG. 16 is for transmitting the sidelink relay connection status information of a remote UE from the CU-CP of the base station according to the embodiment of FIGS. 11A, 11B, and 12 to the CU-UP of the base station. A flowchart showing base station operation is shown.

Referring to FIG. 16, when the CU-CP of the base station detects a change in the connection operation of a remote user terminal (remote UE) through a sidelink relay through a relay support terminal (relay UE) in step 1610, the remote UE detects a change in connection operation through a sidelink relay in step 1620. The user terminal (remote UE) can determine whether a connection is established through a sidelink relay through a relay support terminal (relay UE). And, as a result of the determination in step 1620, if the remote user terminal (remote UE) is connected to the sidelink relay through the relay support terminal (relay UE), the CU-CP of the base station determines that the remote user terminal (remote UE) is connected in step 1630. An E1AP message containing information indicating that a connection has been established can be transmitted to CU-UP through a sidelink relay. In step 1620, if it is determined that the remote user terminal (remote UE) has changed from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (e.g., Uu interface) connection with the base station, In step 1640, the CU-CP of the base station may transmit an E1AP message containing information indicating that the remote UE has been disconnected through the sidelink relay to the CU-UP.

Figure 17 shows whether a remote user terminal (remote UE) receives a mobile communication service by a sidelink relay method from the CU-UP of the base station according to an embodiment of the present invention, and the information provided by the CU-UP of the base station to the sidelink relay is shown in Figure 17. This is a diagram explaining the CU-UP procedure of the base station to create or stop data usage information. In the embodiment of FIG. 17, the CU-UP of the base station according to the embodiment of FIGS. 11A, 11B, and 12 uses a sidelink relay according to the sidelink relay connection status information of the remote UE received from the CU-CP. Shows a flowchart showing the operation of creating or stopping data usage information provided.

Referring to FIG. 17, in step 1710, the CU-UP of the base station receives information from the CU-CP indicating a change in the connection operation of the remote user terminal (remote UE) through a sidelink relay through a relay support terminal (relay UE). In this case, in step 1720, CU-UP can determine whether a connection is established through a sidelink relay through a remote user terminal (remote UE). And, as a result of the determination in step 1720, if the remote user terminal (remote UE) is connected to the remote user terminal (remote UE) through a sidelink relay through the relay support terminal (relay UE), CU-UP is connected to the remote user terminal (remote UE) (10) in step 1730. Start counting user data packet services using data usage using sidelink relay. In step 1720, if it is determined that the remote user terminal (remote UE) has changed from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (e.g., Uu interface) connection with the base station, In step 1740, CU-UP may stop counting the user data packet service of the remote UE (10) by data use using a sidelink relay.

In addition, in one embodiment of the present invention, the base station transmits to the core network whether the terminal is directly connected to the mobile communication base station and whether it is connected to the mobile communication base station through a sidelink relay, so that the connection policy, for example, QoS parameter settings, can be changed. Provides a method.

FIG. 18 shows the process in which a remote user terminal (remote UE) 10 performs a connection procedure with the base station 30 through a relay support terminal (relay UE) 20 according to an embodiment of the present invention, in 5GC. This is a signal flow diagram illustrating a procedure by which a remote UE (10) can change connection policy (for example, QoS parameter settings) by receiving information about whether it receives a mobile communication service using a sidelink relay method. In FIG. 18, more than one SMF 50 and UPF 60 may be used to provide mobile communication services to the remote UE 10, but in this signal flow diagram, one SMF 50 and UPF are used. It only shows the case where (60) is used, and even if multiple SMFs and UPFs are used, the same signaling procedure from AMF (40) can be used, and other 5GC functions that may be relevant in determining connection policy. (PCF, for example) are not included because existing procedures can be followed.

Referring to FIG. 18, steps 1801 to 1845 are the same as steps 301 to 345 of FIGS. 3A and 3B, so they are explained in FIGS. 3A and 3B, and separate descriptions are omitted. It can be confirmed that the remote user terminal (remote UE) 10 is connected to the base station 30 through the relay support terminal (relay UE) 20. And, in this case, the base station 30 may transmit a SIDELINK RELAY CONNECTION REPORT message to the AMF 40 in step 1847. The SIDELINK RELAY CONNECTION REPORT message may include information indicating that the remote UE 10 is connected to a sidelink relay (for example , Sidelink Relay Connection Status IE is set to 'Connected'). The AMF 40, which has received this, may transmit Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 1849, and the Nsmf_PDUSession_UpdateSMContext message may include information indicating the sidelink relay connection status (for example, setting the Sidelink Relay Connection Status to 'Connected'). . Upon receiving this information, the SMF 50 establishes a policy policy (e.g. QoS policy) for servicing the remote UE 10 according to the sidelink relay connection status information of the remote UE 10 in step 1851. QoS parameter settings for each flow can be reset. In step 1853, the SMF (50) transmits an N4 Session Modification Request to the UPF (60), and the UPF (60) may respond to the SMF (50) with an N4 Session Modification Response in step 1855. In step 1857, the SMF 50 transmits the changed policy policy determined in step 1851 (e.g., QoS parameter settings for each QoS flow) to the AMF 40, and in step 1859, the AMF 40 transmits the changed policy policy (e.g., QoS flow Separate QoS parameter settings) can be delivered to the base station 30. And, in step 1861, the base station 30 may perform an RRC connection reconfiguration procedure of the remote UE 10 to reset the changed policy policy (e.g., QoS parameter settings for each QoS flow). If necessary, the relay UE 20 can additionally perform an RRC connection reset procedure for relay-related reset to support the remote user terminal 10. In FIG. 18, this procedure is shown. It is shown omitted. In step 1863, the base station 30 may transmit a response message notifying the AMF 40 that the policy has been applied. After receiving the changed policy policy (e.g., QoS parameter settings for each QoS flow) in step 1859, the base station 30 may apply the changed policy policy (e.g., QoS parameter settings for each QoS flow) in step 1965.

Referring to FIG. 19, a terminal according to an embodiment of the present invention may include a transceiver 1920 and a control unit 1910 that controls the overall operation of the terminal. Additionally, the transmitting and receiving unit 1920 may include a transmitting unit 1925 and a receiving unit 1923. And the terminal may include one of a remote user terminal (remote UE) and a remote user terminal (remote UE).

The transceiver unit 1920 can transmit and receive signals with other network entities.

The control unit 1910 can control the terminal to perform any one of the above-described embodiments. Meanwhile, the control unit 1910 and the transmitting/receiving unit 1920 do not necessarily have to be implemented as separate modules, and of course can be implemented as a single component in the form of a single chip. Additionally, the control unit 1910 and the transmitting/receiving unit 1920 may be electrically connected. And, for example, the control unit 1910 may be a circuit, an application-specific circuit, or at least one processor. Additionally, operations of the terminal can be realized by providing a memory device storing the corresponding program code in any component part of the terminal.

Referring to FIG. 20, the network entity according to an embodiment of the present invention may include a transceiver 2020 and a control unit 2010 that controls the overall operation of the network entity. And, the transmitting and receiving unit 2020 may include a transmitting unit 2025 and a receiving unit 2023.

The transceiver unit 2020 can transmit and receive signals with other network entities.

The control unit 2010 may control the network entity to perform any one of the above-described embodiments. Meanwhile, the control unit 2010 and the transceiver unit 2020 do not necessarily have to be implemented as separate modules, and of course, they can be implemented as one component in the form of a single chip. Additionally, the control unit 2010 and the transmitting/receiving unit 2020 may be electrically connected. And, for example, the control unit 610 may be a circuit, an application-specific circuit, or at least one processor. Additionally, the operations of the network entity can be realized by providing a memory device storing the corresponding program code in any component within the network entity.

The network entity may mean any one of a base station, CU-CP of the base station, CU-UP of the base station, DU, AMF, SMF, UPF, PCF, AF, NEF, UDM, UDR, NF, AUSF, etc. of the base station. there is.

It should be noted that the configuration diagrams, illustrative control/data signal transmission method diagrams, illustrative operation procedure diagrams, and configuration diagrams illustrated in FIGS. 1 to 20 are not intended to limit the scope of the present disclosure. That is, all components, entities, or operational steps described in FIGS. 1 to 20 should not be construed as essential components for carrying out the disclosure, and the inclusion of only some components does not impair the essence of the disclosure. It can be implemented within.

The operations of the network entity or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the network entity or terminal device. That is, the control unit of the network entity or terminal device can execute the operations described above by reading and executing the program code stored in the memory device by a processor or CPU (Central Processing Unit).

The various components, modules, etc. of a network entity, base station, or terminal device described in this specification include hardware circuits, such as complementary metal oxide semiconductor-based logic circuits and firmware. ), and may be operated using hardware circuitry, such as software and/or a combination of hardware and firmware and/or software embedded in a machine-readable medium. As an example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the patent claims described later, but also by the scope of the claims and their equivalents.

Claims

In a method performed by a central unit-control plane (CU-CP) of a base station of a wireless communication system,

Transmitting a first message containing information indicating whether a remote user equipment (UE) is connected through a sidelink relay to the central unit-user plane (CU-UP) of the base station step;

Receiving a second message from the CU-UP containing information on data usage using the sidelink relay of the remote user terminal when a preset condition is satisfied; and

A method comprising transmitting a third message containing information about the data usage using the sidelink relay of the remote user terminal to an access and mobility management function (AMF).
According to claim 1,

When the connection state of the remote user terminal changes from a connection through the sidelink relay to a wireless interface connection with the base station, a fourth message including information indicating that the connection through the sidelink relay is in a released state. Transmitting to the CU-UP;

Receiving a fifth message from the CU-UP containing information on data usage using the sidelink relay of the remote user terminal until the connection through the sidelink relay is released; and

The method further comprising transmitting a sixth message containing information on the data usage amount using the sidelink relay of the remote user terminal to the AMF.
According to claim 1,

The first message includes at least one of a bearer context setup request message and a bearer context modification request message.
According to claim 1,

The information about the data usage using the sidelink relay of the remote user terminal is a value calculated for each protocol data unit (PDU) session or for each quality of service (QoS) flow,

The information about the data usage using the sidelink relay of the remote user terminal is information related to the start time of data transmission and reception using the sidelink relay, and the end time of data transmission and reception using the sidelink relay. A method comprising at least one of time-related information, uplink data usage information, and downlink data usage information.
In a method performed by a central unit-user plane (CU-UP) of a base station of a wireless communication system,

A remote user equipment (remote UE) receives a first message containing information indicating whether it is connected through a sidelink relay from the central unit-control plane (CU-CP) of the base station. step;

Based on the information, identifying information about data usage using the sidelink relay of the remote user terminal; and

A method comprising transmitting a second message containing information about the data usage amount using the sidelink relay of the remote user terminal to the CU-CP when a preset condition is satisfied.
According to clause 5,

When the connection state of the remote user terminal changes from a connection through the sidelink relay to a wireless interface connection with the base station, a fourth message including information indicating that the connection through the sidelink relay is in a released state. Receiving from the CU-CP;

stopping calculation of the data usage using the sidelink relay of the remote user terminal; and

The method further comprising transmitting to the CU-CP a fifth message containing information on the data usage using the sidelink relay of the remote user terminal identified up to the time of stopping the calculation. .
According to clause 5,

The first message includes at least one of a bearer context setup request message and a bearer context modification request message.
According to clause 5,

The information about the data usage using the sidelink relay of the remote user terminal is a value calculated for each protocol data unit (PDU) session or for each quality of service (QoS) flow,

The information about the data usage using the sidelink relay of the remote user terminal is information related to the start time of data transmission and reception using the sidelink relay, and the end time of data transmission and reception using the sidelink relay. A method comprising at least one of time-related information, uplink data usage information, and downlink data usage information.
In the central unit-control plane (CU-CP) of the base station of the wireless communication system,

Transmitter and receiver; and

A first message that is connected to the transceiver and includes information indicating whether a remote user equipment (UE) is connected through a sidelink relay is sent to the central unit (CU-UP) of the base station. -user plane), and when a preset condition is satisfied, a second message containing information on data usage using the sidelink relay of the remote user terminal is received from the CU-UP, and the remote user A CU-CP including a control unit that transmits a third message containing information about the data usage using the sidelink relay of the terminal to an access and mobility management function (AMF).
The method of claim 9, wherein the control unit,

When the connection state of the remote user terminal changes from a connection through the sidelink relay to a wireless interface connection with the base station, a fourth message including information indicating that the connection through the sidelink relay is in a released state. Transmit to the CU-UP, and receive a fifth message from the CU-UP containing information on data usage using the sidelink relay of the remote user terminal until the connection through the sidelink relay is released. and transmitting a sixth message containing information on the data usage using the sidelink relay of the remote user terminal to the AMF.
According to clause 9,

CU-CP, characterized in that the first message includes at least one of a bearer context setup request message or a bearer context modification request message.
According to clause 9,

The information about the data usage using the sidelink relay of the remote user terminal is a value calculated for each protocol data unit (PDU) session or for each quality of service (QoS) flow,

The information about the data usage using the sidelink relay of the remote user terminal is information related to the start time of data transmission and reception using the sidelink relay, and the end time of data transmission and reception using the sidelink relay. A CU-CP comprising at least one of time-related information, uplink data usage information, and downlink data usage information.
In the central unit-user plane (CU-UP) of the base station of the wireless communication system,

Transmitter and receiver; and

A first message that is connected to the transceiver and includes information indicating whether a remote user equipment (UE) is connected through a sidelink relay is sent to the central unit (CU-CP) of the base station. -control plane), and based on the information, identify information on data usage using the sidelink relay of the remote user terminal, and if preset conditions are satisfied, the sidelink of the remote user terminal CU-UP including a control unit that transmits a second message containing information on the data usage using a relay to the CU-CP.
The method of claim 13, wherein the control unit:

When the connection state of the remote user terminal changes from a connection through the sidelink relay to a wireless interface connection with the base station, a fourth message including information indicating that the connection through the sidelink relay is in a released state. Received from the CU-CP, stopped calculating the data usage using the sidelink relay of the remote user terminal, and used the sidelink relay of the remote user terminal identified up to the time of stopping the calculation. CU-UP, characterized in that a fifth message containing information about data usage is transmitted to the CU-CP.
According to claim 13,

The first message includes at least one of a bearer context setup request message or a bearer context modification request message,

The information about the data usage using the sidelink relay of the remote user terminal is a value calculated for each protocol data unit (PDU) session or for each quality of service (QoS) flow,

The information about the data usage using the sidelink relay of the remote user terminal is information related to the start time of data transmission and reception using the sidelink relay, and the end time of data transmission and reception using the sidelink relay. CU-UP comprising at least one of time-related information, uplink data usage information, and downlink data usage information.