KR20240016106A - Method and apparatus to support counting of data usage via sidelink relay - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. This disclosure proposes a method and device for distinguishing sidelink relay transmission data usage.

Description

Method and device for distinguishing sidelink relay transmission data usage {METHOD AND APPARATUS TO SUPPORT COUNTING OF DATA USAGE VIA SIDELINK RELAY}

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.

The present invention to solve the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

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 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. 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 3 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 6 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 8 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 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.
Figure 11 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 13 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 14 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 15 shows an example of a message for the CU-CP of a 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 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 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 in a sidelink relay method from the CU-UP of the base station according to an embodiment of the present invention, and the CU-UP of the base station provides a sidelink relay. 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. This is a diagram. The RAN Node 30 specified in this structure may 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 is an LTE eNB. Or it may be an NR gNB, etc. In Figure 1 (a), the terminal 10 is directly connected to the mobile communication base station 30 or through a sidelink relay through another terminal 20 connected to the same mobile communication base station 30. It shows that receiving mobile communication services through technology and path switching between direct connection and indirect connection through sidelink relay are possible. In Figure 1 (b), the terminal 10 is directly connected to the mobile communication base station 30. When receiving a mobile communication service through sidelink relay technology or through another terminal 20 connected to another mobile communication base station 30, a path switch between a direct connection and an indirect connection through a sidelink relay to another base station is possible. It shows.

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. It operates as a user terminal (remote user equipment: UE) 10 and connects to a relay-supporting user terminal (relay UE) 20 through a direct terminal-to-terminal communication radio interface (for example, PC5 interface), The relay support terminal 20 can receive mobile communication services by connecting to a base station (RAN Node) 30 through a radio interface (for example, Uu interface). 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. PC5 interface) and the connection via a communication radio interface (for example, Uu interface) with the mobile communication of the relay support terminal 20 can be supported by a path switch operation that switches between them. 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 devices through a relay UE (20) connected to the connected RAN Node (30) and another RAN Node (30), a radio interface (for example, PC5 interface) and a relay support terminal. (20) Communication with mobile communication In contrast to the case of receiving a mobile communication service using a radio interface (for example, Uu interface) connection, the connection is switched from a relay connection to a direct connection to the base station. It can be supported by path switch operation.

Figure 2 is a diagram showing an example of the 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 distributed unit (DU) are used to transmit control signals and user data between a remote UE (10) and the base station (30) according to an embodiment of the present invention. A signal flow diagram illustrating the procedure for using control information signaling between 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 5GC (5G Core Network). 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 to it, 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 Access and Mobility Management Function (AMF) (40), Session Management Function (SMF) (50), 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) (e.g., 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).

Figure 3 shows the UPF in the process of a remote user terminal (remote UE) 10 performing a connection procedure with the base station 30 through a relay support terminal (relay UE) 20, according to an embodiment of the present invention. A procedure to receive information on whether the remote UE (10) receives a mobile communication service using the sidelink relay method at (60) and to generate data usage information provided by the sidelink relay in the UPF (60). This is a signal flow diagram explaining. In FIG. 3, 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.

Referring to FIG. 3, in steps 110 and 120, the remote user terminal (remote UE) 10 performs a discovery procedure for PC5 link connection and PC5 connection for direct communication with the relay support terminal (relay UE) 20. Perform a connection establishment procedure. In step 120, 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 210, the remote UE 10 sends an RRC connection request message (for example, RRCSetupRequest ) to the base station 30 to the relay UE 20 using the PC5 link. message), and the relay support terminal (relay UE) 20 sends this RRC connection request message (for example , RRCSetupRequest message) is transmitted to the base station 30. When the base station 30 receives the RRC connection request message of the remote user terminal 10 through the relay UE 20, in step 220, the base station 30 sends the relay UE 20 to the base station 30. ) (20) generates an RRC connection setup message (for example, an RRCSetup message) for the remote UE (10) and sends it to the remote UE (10). And, in step 230, 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). Can perform operations and signal procedures for Step 230 is a known technique, so detailed procedures are omitted. In step 240, the remote UE 10 transmits 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 completion message (for example, an RRCSetupComplete message) from the remote UE 10, selects in step 310 to service the remote UE 10 of 5GC. sidlelink relay connection through the relay support terminal (relay UE) (20) to provide mobile communication services to the remote user terminal (remote UE) (10) up to step 550 by sending an INITIAL UE MESSAGE message to the AMF (40) in operation. Follow the mode procedure as is. The AMF 40, which has received the INITIAL UE MESSAGE message from the base station 30 in step 310, checks the SMF for PDU Session connection for the service of the remote UE 10, and then sends the corresponding SMF in step 320. Nsmf_PDUSession_UpdateSMContext is transmitted to 50), and in step 330, the SMF 50 again checks the UPF 60 for the corresponding PDU Session service and transmits an N4 Session Modification Request to the corresponding UPF 60. In step 340, the UPF 60 responds to the SMF 50 with an N4 Session Modification Response, and the SMF 50, which receives this, transmits Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40 in step 350. Then, the AMF 40 receives the message in step 350 from all SMFs for the service of the remote UE 10 and then sends an INITIAL UE CONTEXT SETUP REQUEST message to the base station 30 in step 360 to establish the base station ( 30) is requested to set the 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 410 and 420. The RRC SecurityModeCommand message and RRC SecurityModeComplete message for encryption settings are exchanged. Then, in steps 430 and 440, the base station 30 sends an RRC reset message (for example, an RRCReconfiguration message) to the remote UE 10 through the relay UE 20, and the remote user After receiving an RRC reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE (10), in step 450, the remote user terminal (remote UE) (10), the relay support terminal (relay UE) (20) and the base station ( 30) can perform operations and signaling procedures to configure the Uu RLC channel for PC5 connection, SRB2 (Signaling Radio Bearer 2), and one or more DRB (Data Radio Bearer). 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 510 to set the context and radio resources for the remote UE 10. inform. In step 520, the AMF (40) sends Nsmf_PDUSession_UpdateSMContext to the SMF (50), in step 530, the SMF (50) sends an N4 Session Modification Request to the UPF (60), and in step 540, the UPF (60) sends an N4 Session Modification Request to the SMF (50). It responds with an N4 Session Modification Response. In step 550, the SMF 50 sends Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40. If the process progresses to step 550, the connection procedure for the remote UE 10 is completed, and data packets of the remote UE 10 can be transmitted and received as in step 610.

The base station 30 can confirm that the remote UE 10 is connected through the relay UE 20. In this case, the base station 30 sends a message to the AMF 40 in step 710. A SIDELINK RELAY CONNECTION REPORT message is sent, and this message contains 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') and a relay support terminal (relay It may include Identifier information of UE (20). Upon receiving this, the AMF 40 sends Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 720, sending information indicating the sidelink relay connection status (for example, setting the Sidelink Relay Connection Status to 'Connected') and relay support terminal (relay UE) ( 20) Identifier information may be included, and in step 730, the SMF (50) sends an N4 Session Modification Request to the UPF (60) and information indicating the sidelink relay connection status (for example, Sidelink Relay Connection Status is set to 'Connected'). settings) and identifier information of the relay support terminal (relay UE) 20. The UPF 60, which has received the N4 Session Modification Request in step 730, begins counting the user data packet service of the remote UE 10 as data usage using a sidelink relay in step 760, 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 740, the UPF (60) responds by sending an N4 Session Modification Response to the SMF (50), and in step 750, the SMF (50) transmits an Nsmf_PDUSession_UpdateSMContextResponse to the AMF (40).

The SIDELINK RELAY CONNECTION REPORT message sent from the base station 30 to the AMF 40 in step 710 is sent by the base station 30 to the AMF 40 in step 510 simultaneously with the INITIAL UE CONTEXT SETUP RESPONSE message or immediately after step 510. It can be sent to this AMF (40). In this case, the AMF 40 may receive a SIDELINK RELAY CONNECTION REPORT message from the base station 30 before step 520, 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 520 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 520 (for example, Sidelink Relay Connection Status is set to 'Connected') and identifier information of the relay support terminal (relay UE) 20. In step 530, the SMF 50 sends an N4 Session Modification Request to the UPF 60. It may include information indicating that the sidelink relay is connected (for example, Sidelink Relay Connection Status is set to 'Connected') and Identifier information of the relay support terminal (relay UE) 20. So, when the AMF (40) receives the SIDELINK RELAY CONNECTION REPORT message from the base station (30) before the step 520 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 520 and 530, additional procedures from steps 720 to 750 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) 120, 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, a remote user terminal (remote UE) is connected to the UPF 60. This is a signal flow diagram explaining the procedure for receiving information on whether (10) is receiving a mobile communication service using the sidelink relay method and stopping the generation of data usage information provided by the UPF (60) 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 a remote user terminal (remote UE) 10 and a relay support terminal (relay UE) 20 are connected to the same base station 30, but the relay support terminal (relay UE) 20 ) is connected to another base station, 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 110, the remote user terminal The (remote UE) 10 transmits, receives, and transmits data packets from the remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20. In step 210, 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 220. For example, if you decide to change to a Uu interface) connection, you can perform an indirect-to-direct path switch procedure to change the connection path of the remote UE (10) from step 310 to step 420. . When the base station 30 determines a path switch in step 220, the base station 30 connects the relay UE 20 to change the connection path of the remote UE 10 in step 310. An RRC reconfiguration message (for example, an RRCReconfiguration message) is sent 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 320 based on the RRC reset message (for example, the RRCReconfiguration message) information. When the procedure is performed and random access is completed, in step 330, the remote UE 10 transmits an RRC reconfiguration complete message (for example, an RRCReconfigurationComplete message) to the base station 30. The base station 30, which has received a reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE 10, relays in step 410 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 420, the relay UE 20 terminates the connection with the remote user terminal 10 and the PC5 link. Carry out the procedure.

If the remote UE 10 confirms in step 330 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 510. A SIDELINK RELAY CONNECTION REPORT message is sent 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 is set to 'Disconnected') ) may include. The AMF 40, which has received this, may send Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 520 and include information indicating that the sidelink relay is disconnected (for example, setting the Sidelink Relay Connection Status to 'Disconnected'), step 530 The SMF 50 may send an N4 Session Modification Request to the UPF 60 and include information indicating that the sidelink relay is disconnected (for example, setting the Sidelink Relay Connection Status to 'Disconnected'). The UPF 60, which has received the N4 Session Modification Request in step 530, stops counting the user data packet service of the remote UE 10 as data use using a sidelink relay in step 550, 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 540, the UPF 60 responds to the SMF 50 by sending an N4 Session Modification Response, and in step 550, the SMF 50 transmits 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 330, the remote user terminal (remote UE) 10 is connected to the base station 30 in step 610. Data packets from the UE (10) are transmitted using a radio interface (eg, Uu interface) between the terminal and the base station.

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.

Referring to FIG. 5, the sidelink relay connection status information of the remote UE 10 is transmitted from the base station 30 to the AMF 40 of the 5GC, used in step 710 of FIG. 3 and step 510 of FIG. 4. It shows an example of the configuration of the NGAP message (for example, the SIDELINK RELAY CONNECTION REPORT message) used to transmit. 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 Nsmf_PDUSession_UpdateSMContext, step in step 720 of FIG. It may also be included in the N4 Session Modification Request at 730, the Nsmf_PDUSession_UpdateSMContext at step 520 of FIG. 4, and the N4 Session Modification Request at step 530, and the format included in the message may vary depending on the message structure format used in each case. .

Figure 6 shows that in the process of a remote user terminal (remote UE) 10 performing 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 ( In 60), a procedure is performed to receive information on whether the remote UE (10) receives a mobile communication service using a sidelink relay, and to generate data usage information provided by the sidelink relay in the UPF (60). This is a signal flow diagram explaining it. In FIG. 6, 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 the embodiment of FIG. 3, 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. 6, 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. Information can simply be transmitted to the SMF (50). In the embodiment of FIG. 3, 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. 6. 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. 6, steps 110 to 610 are performed in the same manner as steps 110 to 610 of FIG. 3. During the process from step 110 to step 610, 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 PDU SESSION RESOURCE NOTIFY message to the AMF 40 in step 710, and this message includes 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 includes information indicating that the remote user terminal (remote UE) (10) is connected to the sidelink relay (for example, Sidelink Relay Connection Status IE is set to 'Connected') and the relay support terminal (relay UE) (20) ) can include Identifier information. The AMF 40, which has received the PDU SESSION RESOURCE NOTIFY message from the base station 30 in step 710, sends Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 720, 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 for the PDU is transmitted as is, and the PDU Session Resource Notify Transfer IE information includes information indicating the sidelink relay connection status (for example, setting the Sidelink Relay Connection Status to 'Connected') and a relay support terminal ( It may include identifier information of relay UE (20). In step 730, the SMF (50) sends an N4 Session Modification Request to the UPF (60) and sends information indicating that the sidelink relay is connected (for example, setting the Sidelink Relay Connection Status to 'Connected') and a relay support terminal (relay UE) ( 20) Identifier information may be included. The UPF (60), which has received the N4 Session Modification Request in step 730, begins counting the user data packet service of the remote UE (10) using the sidelink relay in step 760, 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 740, the UPF (60) responds by sending an N4 Session Modification Response to the SMF (50), and in step 750, the SMF (50) transmits 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) 120 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, 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 a remote user terminal (remote UE) 10 and a relay support terminal (relay UE) 20 are connected to the same base station 30, but the relay support terminal (relay UE) 20 ) is connected to another base station, 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 110 to 420 are performed in the same manner as steps 110 to 420 of FIG. 4. If the remote UE 10 confirms in step 330 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 510. sends a PDU SESSION RESOURCE NOTIFY message to the AMF (40), and this message includes 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'). The AMF 40, which has received the PDU SESSION RESOURCE NOTIFY message from the base station 30 in step 510, sends Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 520, 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 for the PDU is transmitted as is, and the PDU Session Resource Notify Transfer IE information may include information indicating that the sidelink relay is disconnected (for example, setting the Sidelink Relay Connection Status to 'Disconnected'). there is. In step 530, the SMF 50 may send an N4 Session Modification Request to the UPF 60 and include information indicating that the sidelink relay is disconnected (for example, setting the Sidelink Relay Connection Status to 'Disconnected'). The UPF 60, which has received the N4 Session Modification Request in step 530, stops counting the user data packet service of the remote UE 10 as data use using the sidelink relay in step 550, 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 540, the UPF 60 responds to the SMF 50 by sending an N4 Session Modification Response, and in step 550, the SMF 50 transmits an Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

After the remote user terminal (remote UE) 10 completes the connection procedure with the radio interface (for example, Uu interface) with the base station 30 in step 330, the remote user terminal (remote UE) 10 is connected to the base station 30 in step 610. Data packets of the UE (10) are transmitted using a radio interface (eg, Uu interface) between the terminal (10) and the base station (30).

Figure 8 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.

Referring to FIG. 8, used in step 710 of FIG. 6 and step 510 of FIG. 7, the base station 30 connects the sidelink relay of the remote UE 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 convey status information. The NGAP message (for example, the PDU SESSION RESOURCE NOTIFY message) used to transmit the sidelink relay connection status information shown in Figure 8 (a) includes the PDU Session Resource Notify Transfer IE for the base station 30 to transmit to the SMF 50. It includes, and the PDU Session Resource Notify Transfer IE shown in Figure 8 (a) may include Sidelink Relay Connection Status information for the present invention. For example, the Sidelink Relay Connection Status information includes 'Connected' and 'Disconnected'. It may contain status information, and 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. Figure 8 shows an example of an NGAP message (for example, the SIDELINK RELAY CONNECTION REPORT message) used to convey sidelink relay connection status information, but the sidelink relay connection of the remote UE 10 included in Figure 8 The base station 30 can transmit the status information and the identifier information of the relay support terminal (relay UE) 20 to the AMF 40, including other existing NGAP messages or by defining a new NGAP message.

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 shows a flow chart illustrating a base station operation for transmitting sidelink relay connection status information of a remote UE at the base station according to the embodiment of FIGS. 3, 5, 6, and 7. .

Referring to FIG. 9, when the remote user terminal (remote UE) detects a change in connection operation through a sidelink relay through a relay support terminal (relay UE) at step 110, the remote user terminal (remote UE) at step 210 If the connection is established through a sidelink relay through a relay support terminal (relay UE), in step 310, the remote user terminal (remote UE) sends an NGAP message containing information indicating that the connection has been established through the sidelink relay to the 5GC. send. This message may also include identifier information of the relay support terminal (relay UE). In step 210, if the remote user terminal (remote UE) changes from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (for example, Uu interface) connection with the base station, in step 320 The remote UE transmits an NGAP message containing information indicating that the connection has been disconnected to the 5GC through the sidelink relay.

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

Referring to FIG. 10, when a change in the connection operation through the sidelink relay of the remote UE is received from the SMF in step 110 using the N4 message, the remote UE supports the relay in step 210. When a connection is established through a sidelink relay through a terminal (relay UE), in step 310, the user data packet service of the remote user terminal (remote UE) 10 is transmitted through a radio interface (e.g., a radio interface) between a general terminal and a base station. For example, it stops counting the data used by the Uu interface and starts counting the user data packet service of the remote UE (10) using the data used by the sidelink relay. In step 210, when the remote user terminal (remote UE) changes from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (for example, Uu interface) connection with the base station, the remote user Stop counting the user data packet service of the remote UE (10) by data use using a sidelink relay, and replace the user data packet service of the remote UE (10) with a wireless connection between a general terminal and the base station. Start counting with the data used by the radio interface (e.g. Uu interface).

Figure 11 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 in a separate base station structure according to an embodiment of the present invention. In this case, 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, and CU-UP This is a signal flow diagram explaining the procedure for generating and transmitting data usage information provided to the sidelink relay in (34). In FIG. 11, 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.

Referring to FIG. 11, in steps 110 and 120, the remote UE (10) performs a discovery procedure for PC5 link connection and PC5 connection for direct communication with the relay support terminal (relay UE) (20). Perform a connection establishment procedure. In step 120, 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 210, the remote UE 10 sends an RRC connection request message (for example, RRCSetupRequest ) to the base station 30 to the relay UE 20 using the PC5 link. message), and the relay support terminal (relay UE) 20 sends this RRC connection request message (for example , RRCSetupRequest message) is transmitted to the base station 30 and 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 UE 10 through the relay UE 20, in step 220, the CU-CP 32 An RRC connection setup message (for example, an RRCSetup message) is generated for a remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20, and the DU 36 and the relay support terminal (relay UE) It is sent to a remote user terminal (remote UE) (10) through (20). And, in step 230, 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). You can perform operations and signaling procedures to set up the Uu RLC channel. This is a known technology, so detailed procedures are omitted. In step 240, the remote UE 10 transmits 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, sends the remote user terminal of the 5GC ( An INITIAL UE MESSAGE message is transmitted to the AMF (40) selected and operating to service the remote UE (10), and a relay support terminal (relay support terminal) is provided to provide mobile communication services to the remote user terminal (remote UE) (10) up to step 550. Perform the sidlelink relay connection mode procedure as is through relay UE (20). The AMF (40), which has received the INITIAL UE MESSAGE message from the base station CU-CP (32) in step 310, checks the SMF (50) for PDU Session connection for the service of the remote UE (10), In step 320, Nsmf_PDUSession_UpdateSMContext is transmitted to the corresponding SMF (50), and in step 330, the SMF (50) again checks the UPF (60) for the corresponding PDU Session service and transmits an N4 Session Modification Request. In step 340, the UPF 60 responds to the SMF 50 with an N4 Session Modification Response, and the SMF 50, which receives this, transmits Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40 in step 350. And after receiving the message in step 350 from all SMFs for the service of the remote UE (10), the AMF (40) sends an INITIAL UE CONTEXT SETUP REQUEST message to the CU-CP (32) of the base station in step 360. is sent to request the base station to set up context and radio resources for the remote UE (10). The CU-CP (32) of the base station, which has received the INITIAL UE CONTEXT SETUP REQUEST message from the AMF (40), transmits a BEARER CONTEXT SETUP REQUEST message to the CU-UP (34) in step 370, and includes a remote user terminal (remote) in this message. It may include information indicating that the UE (10) is in a sidelink relay connection state (for example, Sidelink Relay Connection Status IE is set to 'Connected'). In step 380, the CU-UP 34 responds to the CU-CP 32 by sending a BEARER CONTEXT SETUP RESPONSE message.

In steps 410 and 420, the CU-CP (32) sends an RRC SecurityModeCommand message and an RRC SecurityModeComplete message to the remote user terminal (10) and the radio section encryption setting through the relay support terminal (relay UE) 20. Give and receive. And, in steps 430 and 440, 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 after receiving an RRC reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE 10, the remote UE 10 and the relay support terminal 10 perform a relay UE in step 450. (20) and the base station can perform operations and signaling procedures to establish a Uu RLC channel for PC5 connection and SRB2 (Signaling Radio Bearer 2) and one or more DRB (Data Radio Bearer). This operation is a known technique, so detailed procedures are omitted. After setup is completed, the CU-CP (32) transmits a BEARER CONTEXT MODIFICATION REQUEST message to the CU-UP (34) in step 510, and this message notifies that the remote UE (10) is connected to the sidelink relay. It may include information (for example, setting Sidelink Relay Connection Status IE to 'Connected'). In step 520, the CU-UP 34 responds to the CU-CP 32 by sending a BEARER CONTEXT MODIFICATION RESPONSE message.

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 370 or step 510 (for example , Sidelink Relay Connection Status IE to 'Connected') According to the settings), in step 530, the CU-UP 34 starts counting the data usage of the user data packet service of the remote UE 10 using the sidelink relay.

In step 540, the CU-CP (32) transmits an INITIAL UE CONTEXT SETUP RESPONSE message to the AMF (40) to inform it of the context and radio resource settings for the remote UE (10). . In step 550, the AMF (40) sends Nsmf_PDUSession_UpdateSMContext to the SMF (50), in step 560, the SMF (50) sends an N4 Session Modification Request to the UPF (60), and in step 570, the UPF (60) sends an Nsmf_PDUSession_UpdateSMContext to the SMF (50). It responds with an N4 Session Modification Response. In step 580, the SMF 50 sends Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40. If the process progresses to step 580, the connection procedure for the remote UE 10 is completed, and data packets of the remote UE 10 can be transmitted and received as in step 610.

Afterwards, if Sidelink Relay data usage reporting needs to be performed in step 710 according to the information set for Sidelink Relay data usage reporting in the CU-UP 34 (e.g., cycle information set by OAM or implementation), in step 720 CU-UP (34) transmits Sidelink Relay data usage information to CU-CP (32) (for example, using the SIDELINK RELAY DATA USAGE REPORT message), and in step 730, CU-CP (32) sends Sidelink Relay data usage information to AMF (40). Delivers relay data usage information (as an example, using the SIDELINK RELAY DATA USAGE REPORT message). The AMF (40) transmits the Sidelink Relay data usage information received from the base station in step 740 to the SMF (50) in charge of the corresponding PDU session by including it in the Nsmf_PDUSession_UpdateSMContext message. In step 750, the SMF 50 responds 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) From the Central Unit-User Plane (34), whether the remote UE (10) receives mobile communication service using the sidelink relay method is received, and data usage information provided from the CU-UP (34) to the sidelink relay is received. This is a signal flow diagram that explains the procedure for stopping the creation of . 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 a remote user terminal (remote UE) 10 and a relay support terminal (relay UE) 20 are connected to the same base station 30, but the relay support terminal (relay UE) 20 ) is connected to another base station, 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, 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 the remote user terminal 10 receives a mobile communication service. (remote UE) 10 is transmitting and receiving data packets of the remote user terminal (remote UE) 10 through the relay support terminal (relay UE) 20, and in step 120, the CU- of the base station 30 The UP 34 performs counting of data usage of the user data packet service of the remote UE 10 using a sidelink relay.

In step 210, the remote user terminal (remote UE) 10 measures the signal 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). It is reported to the CU-CP (32) of the base station (30) through (20) and 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 220. It is decided to change to a connection (for example, Uu interface), and an indirect-to-direct path switch procedure is performed to change the connection path of the remote UE (10) from step 310 to step 420. . When the CU-CP 32 determines a path switch in step 220, the DU 36 and the relay UE (relay UE) are used to change the connection path of the remote UE 10 in step 310. An RRC reconfiguration message (for example, an RRCReconfiguration message) is sent to the remote UE 10 through 20). The remote UE 10 that has received the RRC reset message (for example, the RRCReconfiguration message) performs a random access procedure with the base station in step 320 based on the information in the RRC reset message (for example, the RRCReconfiguration message). And when random access is completed, in step 330, the remote UE 10 transmits an RRC reset completion message (for example, an RRCReconfigurationComplete message) to the CU-CP 32 through the DU 36. do. The CU-CP 32, which has received a reset completion message (for example, an RRCReconfigurationComplete message) from the remote UE 10, performs step 410 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 420, the relay UE (20) is connected to the remote user terminal (remote UE) (10). ) and perform the connection termination procedure for the PC5 link.

If the remote UE 10 confirms in step 330 that the connection procedure is completed through the radio interface (e.g., Uu interface) with the base station, the CU-CP 32 performs step 510. While transmitting the BEARER CONTEXT MODIFICATION REQUEST message to the CU-UP (34), 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. In step 520, the CU-UP 34 responds to the CU-CP 32 by sending a BEARER CONTEXT MODIFICATION RESPONSE message.

In step 510, after receiving information indicating that the remote UE (10) is in a sidelink relay disconnected state (for example, setting Sidelink Relay Connection Status IE to 'Disconnected'), the CU-UP (34) The user data packet service of the user terminal (remote UE) 10 stops counting data usage using a sidelink relay, and data usage information of the remote user terminal (remote UE) 10 is counted in step 540 through CU-CP ( 32) sends the Sidelink Relay data usage information to (as an example, using the SIDELINK RELAY DATA USAGE REPORT message), and in step 550, the CU-CP (32) delivers the Sidelink Relay data usage information to the AMF (40) (as an example, SIDELINK (using RELAY DATA USAGE REPORT message). The AMF 40 transmits the Sidelink Relay data usage information received from the base station in step 550 to the SMF 50 in charge of the corresponding PDU session in step 560 by including it in the Nsmf_PDUSession_UpdateSMContext message. In step 570, the SMF 50 responds by sending Nsmf_PDUSession_UpdateSMContextResponse to the AMF 40.

After the connection procedure of the remote UE 10 with the base station is completed in step 330, the remote UE (10) is connected to the base station as in step 610. The data packet of 10) is transmitted using a radio interface (eg, Uu interface) between the terminal 10 and the base station 30.

Figure 13 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.

Referring to FIG. 13, the CU-CP of the base station, used in step 370 or step 510 of FIG. 11 and step 510 of FIG. 12, sends the sidelink relay connection status information of the remote UE to the CU-UP of the base station. It shows an example of the configuration of the E1AP message used to transmit (for example, the BEARER CONTEXT SETUP REQUEST message and the BEARER CONTEXT MODIFICATION REQUEST message). 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 Contains 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. Figure 13 shows an example 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, but the remote UE included in Figure 11 The sidelink relay connection status information 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.

Figure 14 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.

Referring to FIG. 14, the CU-UP (34) of the base station, used in step 720 of FIG. 11 and step 540 of FIG. 12, transmits Sidelink Relay data of a remote UE 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 convey usage information. 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 Contains 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 (e.g., Sidelink Relay Data Usage Information 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 may be included. Data usage time and data usage information may include all or only one information.

Figure 15 shows an example of a message for the CU-CP of 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 FIG. 15, the CU-CP (32) of the base station, used in step 730 of FIG. 11 and step 550 of FIG. 12, provides Sidelink Relay data usage information of the remote UE 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 convey. 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.

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 shows a base station operation for transmitting the sidelink relay connection status information of a remote UE from the CU-CP of the base station to the CU-UP of the base station according to the embodiment of FIGS. 11 and 12. Shows a flow chart.

Referring to FIG. 16, when a remote user terminal (remote UE) detects a change in connection operation through a sidelink relay through a relay support terminal (relay UE) in the CU-CP of the base station in step 110, the remote UE detects a change in connection operation through a sidelink relay through a relay support terminal (relay UE) in step 110. If the user terminal (remote UE) is connected through a sidelink relay through a relay support terminal (relay UE), in step 310, the E1AP includes information indicating that the remote user terminal (remote UE) has established a connection through the sidelink relay. Send message to CU-UP. In step 210, if the remote user terminal (remote UE) changes from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (for example, Uu interface) connection with the base station, in step 320 The remote UE transmits an E1AP message containing information indicating that the connection has been disconnected to the CU-UP through the sidelink relay.

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. The embodiment of FIG. 17 uses data provided to the sidelink relay according to the sidelink relay connection status information of the remote UE received from the CU-CP in the CU-UP of the base station according to the embodiment of FIGS. 11 and 12. Shows a flowchart depicting the operations that create or stop information.

Referring to FIG. 17, in step 110, the CU-UP of the base station receives information from the CU-CP about changes in connection operation of the remote user terminal (remote UE) through a sidelink relay through a relay support terminal (relay UE). In this case, if the remote user terminal (remote UE) is connected through a sidelink relay through a relay support terminal (relay UE) in step 210, the user data packet service of the remote user terminal (remote UE) 10 is provided in step 310. Start counting by using data using sidelink relay. In step 210, when the remote user terminal (remote UE) changes from a sidelink relay connection through a relay support terminal (relay UE) to a radio interface (for example, Uu interface) connection with the base station, the remote user Stop counting the user data packet service of the remote UE (10) by data use using the 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 for 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 they can follow existing procedures.

Referring to FIG. 18, steps 110 to 610 are the same as steps 110 to 610 of FIG. 3, so the description in FIG. 3 is followed, and separate descriptions are omitted. The base station 30 can confirm that the remote UE 10 is connected through the relay UE 20. In this case, the base station 30 sends a message to the AMF 40 in step 710. A SIDELINK RELAY CONNECTION REPORT message is sent, and this 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'). The AMF 40, which has received this, sends Nsmf_PDUSession_UpdateSMContext to the SMF 50 in step 720 and may include information indicating the sidelink relay connection status (for example, setting the Sidelink Relay Connection Status to 'Connected'), and this information In step 730, the received SMF 50 sets a policy policy (e.g., QoS for each QoS flow) for servicing the remote UE 10 according to the sidelink relay connection status information of the remote UE 10. Reset parameter settings). In step 740, the SMF 50 sends an N4 Session Modification Request to the UPF 60, and the UPF 60 responds to the SMF 50 in step 750 with an N4 Session Modification Response. In step 760, the SMF 50 transfers the changed policy policy determined in step 730 (e.g., QoS parameter settings for each QoS flow) to the AMF 40, and in step 770, the AMF 40 transmits the changed policy policy (e.g., QoS flow setting) to the AMF 40. QoS parameter settings for each QoS flow) are transmitted to the base station 30, and in step 780, the base station 30 uses the RRC of the remote UE 10 to reset the changed policy policy (e.g., QoS parameter settings for each QoS flow). Perform the connection reset procedure. 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 790, the base station 30 sends a response message to the AMF 40 indicating that the policy has been applied. After receiving the changed policy policy (e.g., QoS parameter settings for each QoS flow) in step 770, the base station 30 applies the changed policy policy (e.g., QoS parameter settings for each QoS flow) in step 800.

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

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.

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

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 (1)

In a control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
A control signal processing method comprising transmitting a second control signal generated based on the processing to the base station.

Images