Method and apparatus for transmitting and receiving user data between terminals in mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a first UE that is a 5G ProSe UE-to-UE relay in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: transmitting, to a second UE that is another 5G ProSe UE-to-UE relay, a request message including information about a user ID of the first UE and an RSC; and receiving, from the second UE, a message in response to the request message on the basis of the RSC.

Description

Method and device for transmitting and receiving user data between terminals in a mobile communication system

[0001] The present disclosure relates to terminals and their operations in a wireless communication system. More specifically, the present disclosure relates to an environment in which terminals directly communicate with each other to transmit and receive user data without going through a base station in a wireless communication system (i.e., terminal-to-terminal communication). When a terminal transmitting data (hereinafter, a transmitting terminal or a transmitting terminal) and a terminal receiving data (hereinafter, a receiving terminal) are separated by a predetermined distance, the two terminals can perform terminal-to-terminal communication by requesting relay transmission from other terminals. The present disclosure relates to a method and apparatus for relay terminals to provide a data relay service.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with 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 terrestrial networks is impossible, and Positioning.

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] Meanwhile, with the development of communication systems, various demands for improving communication between terminals are increasing.

[0009] 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 can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0010] According to one embodiment proposed in the present disclosure, a method performed by a first UE, which is a 5G ProSe (proximity service) user equipment (UE)-to-UE relay, includes the steps of transmitting a solicitation message including information about user information ID (identity) of the first UE and a relay service code (RSC) to a second UE, which is another 5G ProSe UE-to-UE relay; and receiving a message from the second UE in response to the solicitation message based on the RSC.

[0011] According to one embodiment proposed in the present disclosure, a method performed by a second UE, which is a 5G ProSe (proximity service) user equipment (UE)-to-UE relay, comprises the steps of: receiving, from a first UE, which is another 5G ProSe UE-to-UE relay, a solicitation message including information about a user information ID (identity) of the first UE and a relay service code (RSC); and transmitting, to the first UE, a message in response to the solicitation message based on the RSC.

[0012] According to one embodiment proposed in the present disclosure, a first UE, which is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay, comprises at least one transceiver; at least one processor communicatively coupled to the at least one transceiver; and at least one memory communicatively coupled to the at least one processor and storing instructions, wherein the instructions are individually or in any combination executed by the at least one processor, such that the first UE: transmits a solicitation message including information about user information ID (identity) of the first UE and a relay service code (RSC) to a second UE, which is another 5G ProSe UE-to-UE relay, and receives a message from the second UE in response to the solicitation message based on the RSC.

[0013] According to one embodiment proposed in the present disclosure, a second UE, which is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay, comprises at least one transceiver; at least one processor communicatively coupled to the at least one transceiver; and at least one memory communicatively coupled to the at least one processor and storing instructions, wherein the instructions are individually or in any combination executed by the at least one processor, such that the second UE: receives a solicitation message from a first UE, which is another 5G ProSe UE-to-UE relay, the solicitation message including information about user information ID (identity) of the first UE and a relay service code (RSC), and transmits a message to the first UE in response to the solicitation message based on the RSC.

[0014] One embodiment of the present invention provides a device and method capable of effectively providing a service related to communication between terminals in a wireless communication system.

[0015] 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 a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0016] FIG. 1 illustrates the structure of a wireless communication system according to various embodiments of the present disclosure.

[0017] FIG. 2 illustrates a 5G ProSe (Proximity based Services) UE (user equipment)-to-UE Relay structure according to an embodiment of the present disclosure.

[0018] Figure 3 illustrates a multi-hop 5G ProSe UE-to-UE Relay structure.

[0019] Figure 4 illustrates a method for an existing 5G ProSe UE-to-UE Relay Cloud to discover a new 5G ProSe UE-to-UE Relay in its vicinity.

[0020] Figure 5a illustrates a MANET (mobile ad hoc network) Network Announcement procedure.

[0021] Figure 5b illustrates another MANET Network Announcement procedure.

[0022] Figure 6 illustrates a method for a new 5G ProSe UE-to-UE Relay to discover a 5G ProSe UE-to-UE Relay Cloud in its surroundings in order to join the surrounding 5G ProSe UE-to-UE Relay Cloud.

[0023] Figure 7 illustrates the MANET Network Solicitation procedure.

[0024] Figure 8 illustrates the configuration of a terminal according to embodiments of the present disclosure.

[0025] FIG. 9 illustrates a configuration of a base station or network entity according to embodiments of the present disclosure.

[0026] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0027] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0028] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0029] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0030] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0031] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, in the following, LTE (long-term evolution), LTE-A (LTE-advanced) or 5G (5 th Although the present disclosure may be described as an example of a 5G (new radio (NR)) system, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include the 5G (new radio (NR)) mobile communication technology developed after LTE-A, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0032] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0033] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0034] Here, the term '~ unit' used in the present embodiments means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to reproduce one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0035] Wireless communication systems have evolved from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0036] As a representative example of a broadband wireless communication system, the LTE system uses the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink. The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above-described multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources to be transmitted, including data or control information, so that they do not overlap with each other (i.e., so that orthogonality is established).

[0037] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC).

[0038] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0039] At the same time, massive Machine Type Communications (mMTC) is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting a large number of terminals within a cell, improving terminal coverage, extending battery life, and reducing terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0040] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must provide extremely low latency and high reliability. For example, services supporting URLLC must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide a shorter transmission time interval (TTI) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0041] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0042] According to various embodiments of the present disclosure, phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used merely to distinguish the corresponding element from other corresponding elements and do not limit the corresponding elements in any other respect (e.g., importance or order).

[0043] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0044] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs (network functions) in a 5G core network (CN), and since a related description may refer to a standard specification (e.g., TS 23.501), a detailed description will be omitted.

[0045] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0046] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0047] FIG. 1 illustrates the structure of a wireless communication system according to various embodiments of the present disclosure. More specifically, FIG. 1 illustrates an example configuration of a 5G system. Referring to FIG. 1 , a 5G network may include at least one of the following network entities (NEs) or network functions (or network functions) (NFs).

[0048] According to one embodiment, the (R)AN ((Radio) Access Network) is an entity that performs radio resource allocation of a terminal, and may include at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0049] According to one embodiment, the terminal may include a User Equipment (UE), a Next Generation UE (NG UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, an Internet of Things (IoT) device, or a multimedia system capable of performing a communication function.

[0050] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0051] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network can virtualize all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0052] According to one embodiment of the present disclosure, 5GC may include one or more NFs illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the NFs illustrated in FIG. 1.

[0053] In one embodiment, the Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0054] In one embodiment, a Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a User Equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining tunnels between a User Plane Function (UPF) and the RAN, selecting and controlling a User Plane (UPF), controlling traffic processing in the UPF, and controlling the collection of charging data.

[0055] In one embodiment, the Policy Control Function (PCF) may be a network function that applies a mobile communication operator's service policy, charging policy, and policy for PDU Session to a terminal.

[0056] In one embodiment, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting UEs, and managing subscription information.

[0057] In one embodiment, the Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Furthermore, NEF may provide the ability to provide information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0058] In one embodiment, the User Plane Function (UPF) may be a function that acts as a gateway to transmit user data (e.g., PDU) to the Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF may perform network functions such as serving as an anchor between Radio Access Technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report generation, and buffering.

[0059] In one embodiment, the Network Repository Function (NRF) may store profiles of NFs and perform discovery of NFs.

[0060] In one embodiment, the Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0061] According to one embodiment, the Network Slice Selection Function (NSSF) may perform a function of selecting a Network Slice Instance provided to a terminal.

[0062] In one embodiment, the Network Data Analytics Function (NWDAF) may collect data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. In one embodiment, the collected data may be analyzed using a machine learning (ML) model, and the analyzed results may be provided back to the NFs to help each NF provide efficient network services.

[0063] In one embodiment, an Application Function (AF) can communicate with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. Depending on the deployment entity, an AF can be classified as an internal AF or an external AF. An internal AF deployed by a network operator can communicate directly with NFs within the network operator. An AF deployed by a third-party service provider (3rd-party service provider) may need to go through an NEF to communicate with NFs within the network operator.

[0064] In one embodiment, the DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0065] In one embodiment, the Network Slice Admission Control Function (NSACF) may limit the number of PDU sessions of registered terminals in each slice, thereby performing a resource management function.

[0066] In one embodiment, the Network Slice-Specific Authentication and Authorization Function (NSSAAF) may create a slice authentication context for a terminal and perform slice-specific authentication and authorization procedures.

[0067] In one embodiment, the Edge Application Server Discovery Function (EASDF) may create a domain name system (DNS) context for a PDU session and may perform functions such as storing a UE IP (internet protocol) address, DNS message processing rules, etc. in the context.

[0068] In one embodiment, a Service Communication Proxy (SCP) may perform indirect communication functions such as service discovery, call response, etc.

[0069] In one embodiment, the terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such an IoT device may be referred to as an ambient IoT device (or Ambient IoT).

[0070] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in Figure 1.

[0071] - N1: Reference point between UE and AMF

[0072] - N2: Reference point between (R)AN and AMF

[0073] - N3: Reference point between (R)AN and UPF

[0074] - N4: Reference point between SMF and UPF

[0075] - N6: Reference point between UPF and DN

[0076] - N9: Reference point between two core UPFs

[0077] Additionally, in 3GPP systems, the 5G system architecture may include service-based interfaces such as the following examples.

[0078] - Nnssf: Service-based interface by NSSF

[0079] - Nnssaaf: Service-based interface by NSSAAF (Network Slice-Specific Authentication and Authorization Function)

[0080] - Nnef: Service-based interface by NEF

[0081] - Nausf: Service-based interface by AUSF

[0082] - Nnrf: Service-based interface by NRF

[0083] - Namf: Service-based interface by AMF

[0084] - Npcf: Service-based interface by PCF

[0085] - Nsmf: Service-based interface by SMF

[0086] - Nupf: Service-based interface by UPF

[0087] - Nudm: Service-based interface by UDM

[0088] - Naf: Service-based interface by AF

[0089] - Nasaf: Service-based interface by AUSF

[0090] - Neasdf: Service-based interface by EASDF (Edge Application Server Discovery Function)

[0091] - Nnwdaf: Service-based interface by NWDAF

[0092] According to one embodiment of the present disclosure, 5G ProSe (Proximity-based Services) may refer to a form of communication that enables direct communication between nearby 5G ProSe-enabled terminals without going through a network. In this case, if direct communication is not possible due to a long distance between two 5G ProSe-enabled terminals, the two 5G ProSe-enabled terminals may perform relay communication via 5G ProSe Relay. The present disclosure proposes a method for 5G ProSe-enabled terminals to perform communication using 5G ProSe Relay.

[0093] FIG. 2 illustrates a 5G ProSe (Proximity based Services) UE-to-UE Relay structure according to an embodiment of the present disclosure.

[0094] Referring to FIG. 2, both the 5G ProSe End UE and the 5G ProSe UE-to-UE Relay are 5G ProSe enabled UEs, and the 5G ProSe End UE can communicate with the counterpart 5G ProSe End UE using the 5G ProSe UE-to-UE Relay. Referring to FIG. 2, the 5G ProSe UE-to-UE Relay can provide a data relay service to enable 5G ProSe End UEs to communicate. In addition, the 5G ProSe enabled UEs use the PC5 interface to transmit data and signaling.

[0095] Figure 3 illustrates a multi-hop 5G ProSe UE-to-UE Relay structure.

[0096] In a structure that supports multi-hop relay, 5G ProSe End UEs can transmit data to the other 5G ProSe End UE using multiple 5G ProSe UE-to-UE relays. In particular, when transmitting IP PDU (Protocol Data Unit) data in a multi-hop 5G ProSe UE-to-UE relay, the 5G ProSe UE-to-UE relays can perform multi-hop data transmission using MANETs (Mobile Ad Hoc Networks).

[0097] MANETs can refer to a type of network formed by wireless terminals without infrastructure (e.g., base stations). In MANETs, ​​data transmission paths typically span several hops due to the relatively short wireless transmission distances between each wireless terminal. Furthermore, the mobility of each wireless terminal can cause data transmission paths to change or data transmission failures.

[0098] In MANET, when transmitting data using wireless resources shared between non-coordinated wireless terminals, a MAC (Medium Access Control) protocol is proposed to avoid wireless data transmission collisions, and a routing protocol to set up and manage data transmission paths is proposed.

[0099] In Figure 3, 5G ProSe UE-to-UE Relays can configure a 5G ProSe UE-to-UE Relay Cloud for each Relay Service Code (RSC) using the MANET protocol. 5G ProSe UE-to-UE Relays are connected via a PC5 link. The process of establishing or managing data transmission paths within the 5G ProSe UE-to-UE Relay Cloud can be performed based on the MANET protocol.

[0100] When a 5G ProSe End UE wants to transmit data to a counterpart 5G ProSe End UE, it can transmit the data to a 5G ProSe UE-to-UE Relay that supports the same RSC as the RSC to be transmitted among the 5G ProSe UE-to-UE Relays within its transmission range. Through this process, 5G ProSe UE-to-UE Relays within the 5G ProSe UE-to-UE Relay Cloud can transmit data to the counterpart 5G ProSe End UE using the MANET protocol.

[0101] In this disclosure, a method for configuring a 5G ProSe UE-to-UE Relay Cloud to provide a multi-hop 5G ProSe UE-to-UE Relay service is proposed.

[0102] Figure 4 illustrates a method for an existing 5G ProSe UE-to-UE Relay Cloud to discover a new 5G ProSe UE-to-UE Relay in its vicinity.

[0103] A 5G ProSe UE-to-UE Relay Cloud consists of one or more 5G ProSe UE-to-UE Relays that support the same RSC. 5G ProSe UE-to-UE Relays are also mobile because they are wireless terminals. Therefore, a 5G ProSe UE-to-UE Relay that constitutes the 5G ProSe UE-to-UE Relay Cloud may move and leave the Cloud, or a new 5G ProSe UE-to-UE Relay supporting the same RSC as the Cloud may approach the Cloud.

[0104] Figure 4 illustrates a method for a 5G ProSe UE-to-UE Relay forming a 5G ProSe UE-to-UE Relay Cloud to discover a new 5G ProSe UE-to-UE Relay in the vicinity.

[0105] A 5G ProSe UE-to-UE Relay UE that constitutes a 5G ProSe UE-to-UE Relay Cloud may periodically transmit a predetermined message (e.g., a MANET Network Announcement message) to its surroundings. According to one embodiment, such a message may include at least one of information related to a Type of Discovery Message, a MANET Network Group ID, an RSC (Relay Service Code), or a User Info ID of a 5G ProSe UE-to-UE Relay.

[0106] In one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay UE (e.g., MANET Network Announcement message).

[0107] In one embodiment, the MANET Network Group ID is an identifier (ID) for identifying a 5G ProSe UE-to-UE Cloud. Since multiple 5G ProSe UE-to-UE Clouds may support the same RSC, an ID is required to distinguish each Cloud. The MANET Network Group ID may include the RSC supported by the Cloud.

[0108] In one embodiment, the RSC represents a service that the 5G ProSe UE-to-UE Cloud supports for data transmission services. All 5G ProSe UE-to-UE Relays that constitute the 5G ProSe UE-to-UE Cloud support the RSC.

[0109] In one embodiment, the User Info ID of 5G ProSe UE-to-UE Relay is an ID for globally and uniquely distinguishing a 5G ProSe UE-to-UE Relay in the corresponding service (i.e., a service corresponding to RSC). This User Info ID of 5G ProSe UE-to-UE Relay may include not only the User Info ID of the 5G ProSe UE-to-UE Relay transmitting the message, but also a list of User Info IDs of all 5G ProSe UE-to-UE Relays constituting the 5G ProSe UE-to-UE Cloud.

[0110] In one embodiment, a MANET Network Announcement message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message.

[0111] The Destination Layer-2 ID can be set to a Broadcast transmission value. Since this message should only be received by 5G ProSe UE-to-UE Relay, it can be set to a value indicating Partially Broadcast (e.g., only receiving 5G ProSe UE-to-UE Relay, or only receiving 5G ProSe UE-to-UE Relay that supports only specific RSCs, reflecting MANET Network Group ID, etc.). The Destination Layer-2 ID value can be set to the 5G ProSe UE-to-UE Relay from the PCF or ProSe Application Server.

[0112] Figures 5a and 5b illustrate the MANET Network Announcement procedure.

[0113] In step 1 of FIGS. 5a and 5b, a 5G ProSe UE-to-UE Relay belonging to a 5G ProSe UE-to-UE Relay Cloud may periodically transmit a MANET Network Announcement message to surrounding 5G ProSe UE-to-UE Relays (or 5G ProSe UE-to-UE Relay UEs).

[0114] In step 2 of FIGS. 5A and 5B , 5G ProSe UE-to-UE Relays around the 5G ProSe UE-to-UE Relay (i.e., within the communication range of the 5G ProSe UE-to-UE Relay) can receive this message. Since the Destination Layer-2 ID value is set to a value that only the Relay can receive, the surrounding 5G ProSe End UEs (i.e., UEs that cannot perform the relay function) do not receive this message. In some cases, if the Destination Layer-2 ID value includes or indicates an RSC value, only the Relays that serve the same RSC among the 5G ProSe UE-to-UE Relays may receive the message. Alternatively, if the Destination Layer-2 ID value includes or indicates a MANET Network Group ID value, the 5G ProSe UE-to-UE Relays belonging to the existing 5G ProSe UE-to-UE Relay Cloud may not receive this message.

[0115] 5G ProSe UE-to-UE Relays that receive a MANET Network Announcement message in step 2 of FIGS. 5a and 5b can check at least one of the Type of Discovery Message, MANET Network Group ID, RSC, or User Info ID of 5G ProSe UE-to-UE Relay values ​​included in the received message. If a 5G ProSe UE-to-UE Relay checks the above values ​​and determines that the MANET Network Announcement message is transmitted by a MANET Network Group to which it already belongs, the 5G ProSe UE-to-UE Relay can discard the message.

[0116] If the 5G ProSe UE-to-UE Relay checks the above value and finds that the MANET Network Announcement is not transmitted from the MANET Network Group to which it belongs or has the same RSC value as the RSC it supports, the 5G ProSe UE-to-UE Relay may decide to join this 5G ProSe UE-to-UE Relay Cloud. For example, this process may be performed by performing the procedure in step 3 and / or by establishing direct communication with the 5G ProSe UE-to-UE relay cloud (using step 5).

[0117] In step 3 of FIGS. 5A and 5B , if the 5G ProSe UE-to-UE Relay decides to join the 5G ProSe UE-to-UE Relay Cloud in step 2, the 5G ProSe UE-to-UE Relay may send a message (e.g., a MANET Network Join Request message) to the 5G ProSe UE-to-UE Relay that sent the MANET Network Announcement message.

[0118] A MANET Network Join Request message transmitted by a 5G ProSe UE-to-UE Relay that has decided to join a 5G ProSe UE-to-UE Relay Cloud may include information related to at least one of a Type of Discovery Message, a MANET Network Group ID, (its) User Info ID, (target) User Info ID, or an RSC.

[0119] In one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay (e.g., MANET Network Join Request message).

[0120] In one embodiment, the MANET Network Group ID is a value included in the received MANET Network Announcement message. That is, the MANET Network Group ID is the ID of the MANET Network Group that the Relay is attempting to join.

[0121] In one embodiment, RSC is an RSC value that it supports and is a value that was included in the received MANET Network Announcement message.

[0122] In one embodiment, (its) User Info ID is the User Info ID of the Relay itself that wants to join the Cloud.

[0123] According to one embodiment, the (target) User Info ID is the ID of the recipient of the MANET Network Join Request message. That is, the (target) User Info ID is the value included in the received MANET Network Announcement message.

[0124] According to one embodiment, a MANET Network Join Request message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. This message may be transmitted unicast. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message. The Destination Layer-2 ID may be set to the Source Layer-2 ID of the received MANET Network Announcement message.

[0125] In step 4 of FIGS. 5a and 5b, the 5G ProSe UE-to-UE Relay may send a message (e.g., a MANET Network Join Response message) in response to the MANET Network Join Request message.

[0126] The MANET Network Join Response message transmitted by the 5G ProSe UE-to-UE Relay in response to the Cloud's join request may include information related to at least one of the Type of Discovery Message, MANET Network Group ID, (its) User Info ID, (target) User Info ID, or RSC.

[0127] According to one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay (e.g., MANET Network Join Response message).

[0128] In one embodiment, the MANET Network Group ID is a MANET Network Group ID.

[0129] In one embodiment, the RSC is an RSC of a service for which a 5G ProSe UE-to-UE Relay Cloud supports a data transmission service.

[0130] In one embodiment, (its) User Info ID is the User Info ID of the Relay itself responding to the join request.

[0131] According to one embodiment, the (target) User Info ID is the recipient of the MANET Network Join Response message, i.e., the value included in the received MANET Network Join Request message.

[0132] According to one embodiment, a MANET Network Join Response message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. This message may be transmitted unicast. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message. The Destination Layer-2 ID may be set to the Source Layer-2 ID of the received MANET Network Join Request message.

[0133] In step 5 of FIGS. 5a and 5b, a 5G ProSe Direct Communication Establishment procedure may be performed to establish a PC5 link between a Source 5G ProSe UE-to-UE Relay and a Target 5G ProSe UE-to-UE Relay.

[0134] In step 6 of FIGS. 5a and 5b, the MANET Neighborhood Discovery Protocol (NHDP) can be performed using the PC5 link established between the Source 5G ProSe UE-to-UE Relay and the Target 5G ProSe UE-to-UE Relay in step 5. Through the NHDP protocol execution process, a MANET link can be established between the two Relays.

[0135] According to the embodiment of FIG. 5b, the model B-based procedure according to steps 3 and 4 can be performed based on the parameters received through the model A-based procedure according to steps 1 and 2. According to these procedures, the MANET Network Announcement procedure can be performed in a form corresponding to a combination of model A and model B.

[0136]

[0137] Figure 6 illustrates the process of discovering surrounding 5G ProSe UE-to-UE Relay Clouds in order for a new 5G ProSe UE-to-UE Relay to join the surrounding 5G ProSe UE-to-UE Relay Clouds.

[0138] A 5G ProSe UE-to-UE Relay Cloud consists of one or more 5G ProSe UE-to-UE Relays that support the same RSC. 5G ProSe UE-to-UE Relays are also mobile because they are wireless terminals. Therefore, a 5G ProSe UE-to-UE Relay that constitutes the 5G ProSe UE-to-UE Relay Cloud may move and leave the Cloud, or a new 5G ProSe UE-to-UE Relay supporting the same RSC as the Cloud may approach the Cloud.

[0139] Figure 6 illustrates a method for a 5G ProSe UE-to-UE Relay that has moved to a new location to find a 5G ProSe UE-to-UE Relay Cloud in the vicinity.

[0140] A 5G ProSe UE-to-UE Relay may transmit a predetermined message (e.g., a MANET Network Solicitation message) to discover a 5G ProSe UE-to-UE Relay Cloud in the vicinity. According to one embodiment, such a message may include information related to at least one of a Type of Discovery Message, a List of RSC(s) (Relay Service Code(s)), a List of MANET Network Group ID(s), or a User Info ID of a 5G ProSe UE-to-UE Relay.

[0141] According to one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay (e.g., MANET Network Solicitation message).

[0142] In one embodiment, the RSC represents a relay service supported by the 5G ProSe UE-to-UE Relay. Since a single 5G ProSe UE-to-UE Relay can support relay services for more than one service, in one embodiment, the RSC may include multiple RSC values ​​in the form of a list.

[0143] In one embodiment, the MANET Network Group ID is the ID of the group to which the 5G ProSe UE-to-UE Relay currently belongs. Since a single Relay may belong to one or more MANET Network Groups, in one embodiment, the MANET Network Group ID may include MANET Network Group ID(s) in the form of a list.

[0144] According to one embodiment, the User Info ID of 5G ProSe UE-to-UE Relay is an ID for globally uniquely distinguishing the 5G ProSe UE-to-UE Relay in the corresponding service (i.e., the service corresponding to the RSC). The User Info ID of 5G ProSe UE-to-UE Relay includes the User Info ID value of the 5G ProSe UE-to-UE Relay transmitting the message.

[0145] According to one embodiment, a MANET Network Solicitation message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message.

[0146] In one embodiment, the Destination Layer-2 ID may be set to a Broadcast transmission value. Since this message should only be received by 5G ProSe UE-to-UE Relay, it may be set to a value indicating partial broadcast (e.g., receiving only 5G ProSe UE-to-UE Relay, or receiving only 5G ProSe UE-to-UE Relay that supports only specific RSCs). The Destination Layer-2 ID value may be configured in the 5G ProSe UE-to-UE Relay from the PCF or ProSe Application Server.

[0147]

[0148] Figure 7 illustrates the MANET Network Solicitation procedure.

[0149] In step 1 of FIG. 7, in order to search for surrounding 5G ProSe UE-to-UE Relay Clouds, the 5G ProSe UE-to-UE Relay can send a MANET Network Solicitation message to surrounding 5G ProSe UE-to-UE Relays (or 5G ProSe UE-to-UE Relay UEs).

[0150] In step 2 of FIG. 7, 5G ProSe UE-to-UE Relays around a 5G ProSe UE-to-UE Relay (i.e., within the communication range of the 5G ProSe UE-to-UE Relay) can receive a MANET Network Solicitation message. Since the Destination Layer-2 ID value is set to a value that only the Relay can receive, the surrounding 5G ProSe End UEs (i.e., UEs that cannot perform the relay function) do not receive this message. In some cases, if the Destination Layer-2 ID value includes or indicates an RSC value, only Relays that service the same RSC among the 5G ProSe UE-to-UE Relays may receive it. Alternatively, if the Destination Layer-2 ID value includes or indicates a MANET Network Group ID value, 5G ProSe UE-to-UE Relays belonging to an existing 5G ProSe UE-to-UE Relay Cloud may not receive this message.

[0151] In step 2 of FIG. 7, 5G ProSe UE-to-UE Relays that receive a MANET Network Solicitation message can check at least one of the Type of Discovery Message, List of MANET Network Group ID(s), List of RSC(s), or User Info ID of 5G ProSe UE-to-UE Relay values ​​included in the message. If the 5G ProSe UE-to-UE Relay checks the above values ​​and the MANET Network Solicitation message is transmitted from a MANET Network Group to which the 5G ProSe UE-to-UE Relay already belongs, the 5G ProSe UE-to-UE Relay can discard this message. Additionally, the 5G ProSe UE-to-UE Relay can discard this message if the RSC it supports does not match any of the List of RSC(s) included in the received message.

[0152] If the 5G ProSe UE-to-UE Relay checks the above value and determines that the MANET Network Solicitation message is not transmitted from the MANET Network Group to which it belongs or has the same RSC value as the RSC supported by its MANET Network Group, it can decide to invite the 5G ProSe UE-to-UE Relay to its 5G ProSe UE-to-UE Relay Cloud.

[0153] In step 3 of FIG. 7, if the 5G ProSe UE-to-UE Relay decides to invite the 5G ProSe UE-to-UE Relay Cloud in step 2, the 5G ProSe UE-to-UE Relay may send a MANET Network Invite Request message to the 5G ProSe UE-to-UE Relay that sent the MANET Network Solicitation message to it.

[0154] The MANET Network Invite Request message transmitted by the 5G ProSe UE-to-UE Relay may include information about at least one of the Type of Discovery Message, MANET Network Group ID, (source) User Info ID, (target) User Info ID, or RSC.

[0155] According to one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay (e.g., MANET Network Invite Request message).

[0156] In one embodiment, the MANET Network Group ID is the ID of the MANET Network Group to which the Relay intends to invite a specific 5G ProSe UE-to-UE Relay.

[0157] According to one embodiment, RSC is an RSC value supported by the MANET Network Group to which the 5G ProSe UE-to-UE Relay belongs, and RSC is one of the RSC values ​​included in the received MANET Network Solicitation message (or values ​​included in the list of RSCs).

[0158] In one embodiment, the (source) User Info ID is the User Info ID of the 5G ProSe UE-to-UE Relay that transmits the MANET Network Invite Request message.

[0159] In one embodiment, the (target) User Info ID is the recipient of the MANET Network Invite Request message, i.e., the value included in the received MANET Network Solicitation message.

[0160] According to one embodiment, a MANET Network Join Request message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. This message may be transmitted as a broadcast. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message. The Destination Layer-2 ID may be set to a Broadcast transmission value. Since this message should only be received by a 5G ProSe UE-to-UE Relay, it may be set to a value indicating a partial broadcast (for example, only receiving a 5G ProSe UE-to-UE Relay, or only receiving a 5G ProSe UE-to-UE Relay that supports only a specific RSC).

[0161] Step 4 of FIG. 7 is described. In Step 1 described above, one or more 5G ProSe UE-to-UE Relays belonging to the same MANET Network Group may receive a MANET Network Solicitation message. In this situation, if a specific 5G ProSe UE-to-UE Relay among multiple 5G ProSe UE-to-UE Relays first transmits a MANET Network Invite Request message, other member 5G ProSe UE-to-UE Relays belonging to the MANET Network Group may receive this MANET Network Invite Request message.

[0162] A 5G ProSe UE-to-UE Relay that receives a MANET Network Invite Request message must decide whether to send a MANET Network Invite Request message to the 5G ProSe UE-to-UE Relay to which it also sent a Solicitation message. If it decides to send an Invite message to the 5G ProSe UE-to-UE Relay to which it also sent a Solicitation message, the 5G ProSe UE-to-UE Relay can create a PC5 link separately from the 5G ProSe UE-to-UE Relay that sent the Solicitation message. If it decides not to send an Invite message to the 5G ProSe UE-to-UE Relay to which it sent the Solicitation message, the 5G ProSe UE-to-UE Relay does not create a PC5 link with the 5G ProSe UE-to-UE Relay that sent the Solicitation message. This decision-making process can be understood as a process to increase the reliability of the 5G ProSe UE-to-UE Relay Cloud by creating a single relay and multiple PC5 links when the reliability of the RSC's service characteristics is critical. Alternatively, the decision to create a separate PC5 link may be determined based on the battery status / power of the 5G ProSe UE-to-UE Relay or the number of RSCs it currently serves.

[0163] In step 5 of FIG. 7, the 5G ProSe UE-to-UE Relay that received the MANET Network Invite Request message can transmit a MANET Network Invite Response message as a response to the MANET Network Invite Request message.

[0164] The MANET Network Invite Response message transmitted by the 5G ProSe UE-to-UE Relay may include information about at least one of the Type of Discovery Message, MANET Network Group ID, (source) User Info ID, (target) User Info ID, or RSC.

[0165] According to one embodiment, the Type of Discovery Message may indicate the type of message transmitted by the 5G ProSe UE-to-UE Relay (e.g., MANET Network Invite Response message).

[0166] In one embodiment, the MANET Network Group ID is the MANET Network Group ID that the 5G ProSe UE-to-UE Relay is trying to join. That is, the MANET Network Group ID is the value included in the MANET Network Invite Request message.

[0167] In one embodiment, the RSC is the RSC of a data transmission service supported by the 5G ProSe UE-to-UE Relay Cloud. That is, the RSC is a value included in the MANET Network Invite Request message.

[0168] In one embodiment, the (source) User Info ID is the User Info ID of the 5G ProSe UE-to-UE Relay that transmits the MANET Network Invite Response message.

[0169] According to one embodiment, the (target) User Info ID is the recipient of the MANET Network Invite Response message, i.e., the value included in the received MANET Network Invite Request message.

[0170] According to one embodiment, a MANET Network Invite Response message may be transmitted using a Source Layer-2 ID and a Destination Layer-2 ID. This message may be transmitted unicast. The Source Layer-2 ID may be self-configured by the 5G ProSe UE-to-UE Relay transmitting the message. The Destination Layer-2 ID may be set to the Source Layer-2 ID of the received MANET Network Invite Request message.

[0171] In step 6 of FIG. 7, a 5G ProSe Direct Communication Establishment procedure may be performed to establish a PC5 link between a Source 5G ProSe UE-to-UE Relay and a Target 5G ProSe UE-to-UE Relay.

[0172] In step 7 of FIG. 7, the MANET Neighborhood Discovery Protocol (NHDP) can be performed using the PC5 link established between the Source 5G ProSe UE-to-UE Relay and the Target 5G ProSe UE-to-UE Relay in step 6. By performing the NHDP protocol, a MANET link can be established between the two Relays.

[0173] Figure 8 illustrates the configuration of a terminal according to embodiments of the present disclosure. A terminal according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the terminal, a transceiver (800) including a transmitter and a receiver, and a memory (810). Of course, the present invention is not limited to the examples described above, and the terminal may include more or fewer components than those illustrated in Figure 8.

[0174] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with a base station, network entities, or other terminals. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (800) can receive signals via a wireless channel, output them to the processor (820), and transmit the signals output from the processor (820) via the wireless channel.

[0175] According to one embodiment of the present disclosure, the processor (820) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (820), the memory (810), and the transceiver (800) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (820) and the transceiver (800) can be electrically connected. In addition, the processor (820) can include an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, a control unit (or controller), or at least one processor.

[0176] According to one embodiment of the present disclosure, the memory (810) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (810) provides the stored data upon request of the processor (820). The memory (810) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (810). In addition, the processor (820) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (810).

[0177] FIG. 9 illustrates a configuration of a base station or network entity according to embodiments of the present disclosure.

[0178] A network entity according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the network entity, a transceiver (900) including a transmitter and a receiver, and a memory (910). Of course, the present invention is not limited to the above-described examples, and the network entity may include more or fewer components than those illustrated in FIG. 9.

[0179] According to one embodiment of the present disclosure, the transceiver (900) can transmit and receive signals with at least one of another network entity, another base station, or a terminal. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

[0180] According to one embodiment of the present disclosure, the processor (920) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (920), the memory (910), and the transceiver (900) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (920) and the transceiver (900) can be electrically connected. In addition, the processor (920) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a control unit (or controller), or at least one processor.

[0181] According to one embodiment of the present disclosure, the memory (910) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (910) provides the stored data upon request of the processor (920). The memory (910) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (910). In addition, the processor (920) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (910).

[0182] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

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

[0184] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0185] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0186] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0187] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wireless LAN (WLAN), or a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0188] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0189] While the detailed description of the present disclosure has described specific embodiments, it should be understood that 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 claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a method performed by a first UE, which is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay in a wireless communication system, A step of transmitting a solicitation message including information about the user information ID (identity) of the first UE and a relay service code (RSC) to a second UE, which is another 5G ProSe UE-to-UE relay; and A method comprising the step of receiving a message in response to the request message based on the RSC from the second UE.

2. In paragraph 1, The above request message further includes information regarding the type of the above request message, A method wherein the message includes information about the type of the message, the user information ID of the first UE, the user information ID of the second UE, and the RSC.

3. In paragraph 1, A method wherein the RSC included in the request message matches the RSC of the second UE.

4. In paragraph 1, The first UE and the second UE are related to a MANET (mobile ad hoc network), A method wherein the first UE and the second UE are multi-hop UE-to-UE relays.

5. In a method performed by a second UE, which is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay in a wireless communication system, A step of receiving a solicitation message including information about the user information ID (identity) of the first UE and a relay service code (RSC) from a first UE, which is another 5G ProSe UE-to-UE relay; and A method comprising the step of transmitting a message in response to the request message based on the RSC to the first UE.

6. In paragraph 5, The above request message further includes information regarding the type of the above request message, A method wherein the message includes information about the type of the message, the user information ID of the first UE, the user information ID of the second UE, and the RSC.

7. In paragraph 5, The RSC included in the request message matches the RSC of the second UE, The first UE and the second UE are related to a MANET (mobile ad hoc network), A method wherein the first UE and the second UE are multi-hop UE-to-UE relays.

8. In a wireless communication system, in a first UE that is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above commands are executed individually or in any combination by the at least one processor so that the first UE: Transmit a solicitation message including information about the user information ID (identity) of the first UE and a relay service code (RSC) to a second UE, which is another 5G ProSe UE-to-UE relay; A first UE configured to receive a message from the second UE in response to the request message based on the RSC.

9. In paragraph 8, The above request message further includes information regarding the type of the above request message, The first UE, wherein the message includes information about the type of the message, the user information ID of the first UE, the user information ID of the second UE, and the RSC.

10. In paragraph 8, The RSC included in the request message is a first UE that matches the RSC of the second UE.

11. In paragraph 8, The first UE and the second UE are related to a MANET (mobile ad hoc network), The first UE and the second UE are multi-hop UE-to-UE relays.

12. In a wireless communication system, in a second UE that is a 5G ProSe (proximity service) UE (user equipment)-to-UE relay: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above commands are executed individually or in any combination by the at least one processor so that the second UE: Receive a solicitation message including information about the user information ID (identity) of the first UE and a relay service code (RSC) from the first UE, which is another 5G ProSe UE-to-UE relay; A second UE, which transmits a message to the first UE in response to the request message based on the RSC.

13. In paragraph 12, The above request message further includes information regarding the type of the above request message, The second UE, wherein the message includes information about the type of the message, the user information ID of the first UE, the user information ID of the second UE, and the RSC.

14. In paragraph 12, The RSC included in the request message matches the RSC of the second UE.

15. In paragraph 12, The first UE and the second UE are related to a MANET (mobile ad hoc network), The first UE and the second UE are multi-hop UE-to-UE relays.

Images