User equipment (UE)

Abstract

Provided are: a means for specifying various kinds of information which are required to establish a communication channel for multi-hop communication and to provide a UE policy for ProSe multi-hop communication, and further for transmitting and receiving a control message including the information between UEs; and a method for implementing processing and behavior by each UE on the basis of the message.

Description

UE (User Equipment)

[0001] This embodiment relates to User Equipment (UE). This application claims priority to Japanese Patent Application No. 2025-006686, filed in Japan on January 17, 2025, and the contents of that application are incorporated herein by reference.

[0002] The 3GPP (3rd Generation Partnership Project: registered trademark) is considering the system architecture for 5GS (5G System), the fifth-generation (5G) mobile communication system, and discussions are underway to support new procedures and functions (see Non-Patent Documents 1-4). In Release 19 of the 5G standard, the architecture for extending Proximity Based Services (ProSe) functionality, procedures for communication and control, etc., are being considered (see Non-Patent Document 4).

[0003] 3GPP TS 23.304 V19.2.0 (2024-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity based Services (ProSe) in the 5G System (5GS); (Release 19)3GPP TS 24.554 V18.6.0 (2024-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 (Release 18)3GPP TS 24.555 V18.4.0 (2024-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 (Release 18)3GPP TS 24.501 V19.1.0 (2024-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 19)3GPP TR 23.700-03 V19.0.0 (2024-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 3 (Release 19).

[0004] In the 5G System (5GS), Proximity-services (ProSe) is being studied to enable proximity wireless communication between UEs. Furthermore, in Release 19 of the 5G standard, multi-hop communication between UEs via multiple relay UEs is being studied.

[0005] On the other hand, various information necessary for establishing a communication path for multi-hop communication and providing a UE policy for ProSe multi-hop communication, the transmission and reception of control messages including such information between each UE, and the behavior and processing of each UE based on such messages are not clear.

[0006] One aspect of this embodiment is made in view of the above circumstances, and its purpose is to clarify various information necessary for establishing a communication path for multi-hop communication and providing a UE policy for ProSe multi-hop communication, and further to provide means for transmitting and receiving control messages including such information between each UE, and a method for executing the behavior and processing of each UE based on such messages.

[0007] In one embodiment of this model, User Equipment (UE) includes a transmitting and receiving unit, and if the UE supports operating as a 5G ProSe multi-hop L3 (Layer-3) UE-to-UE (U2U) relay UE, the transmitting and receiving unit includes a first piece of information and a second piece of information in the registration request message and transmits the registration request message to the network, wherein the first piece of information indicates that the UE supports the 5G ProSe multi-hop relay communication function, and the second piece of information indicates that the UE supports operating as a 5G ProSe L3 U2U relay UE.

[0008] According to one aspect of this embodiment, various information necessary for establishing a communication path for multi-hop communication and providing a UE policy for ProSe multi-hop communication is clarified, and means for sending and receiving control messages containing such information between UEs, and methods for executing the behavior and processing of each UE based on such messages are provided.

[0009] This diagram outlines the mobile communication system (EPS / 5GS). This diagram explains the detailed configuration of the mobile communication system (EPS / 5GS). This diagram explains the equipment configuration of the UE. This diagram explains the configuration of the access network equipment (gNB) in 5GS. This diagram explains the configuration of the core network equipment (AMF / SMF / UPF) in 5GS. This diagram explains the registration procedure. This diagram explains the network request UE policy management procedure. This diagram explains the UE request ProSeP provision procedure.

[0010] The best mode for carrying out one aspect of this embodiment will be described below with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system when one aspect of this embodiment is applied will be described.

[0011] [1. System Overview] First, Figure 1 is a diagram illustrating the general structure of the mobile communication system 1 used in each embodiment, and Figure 2 is a diagram illustrating the detailed configuration of the mobile communication system 1.

[0012] Figure 1 shows that mobile communication system 1 consists of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0013] In the following, these devices and functions may be referred to using abbreviations such as UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0014] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as the interfaces that connect these devices and functions to each other.

[0015] In the following, these devices and functions may be described using abbreviations such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0016] Furthermore, the 4G system, EPS (Evolved Packet System), consists of access network_A and core network_A, but may also include UE and / or PDN. Similarly, the 5G system, 5GS (5G System), consists of UE, access network_B and core network_B, but may also include DN.

[0017] A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to both EPS and 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). A UE may also be referred to as a user device or a terminal device.

[0018] Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points.

[0019] Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR Node B)122 are located in the NG-RAN. Note that, below, gNB122 may be written simply as gNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE and is connected to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a gNB is a base station device newly designed for 5GS and has different functions from the base station device (eNB) used in the 4G system, EPS. Also, if there are multiple gNBs, each gNB is connected to the others, for example, via an Xn interface.

[0020] Furthermore, a non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, an untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public Wi-Fi network. On the other hand, a trusted non-3GPP access network may be an access network defined by 3GPP and may be equipped with a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0021] Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, nodes located in access network_B may be collectively referred to as NG-RAN nodes.

[0022] Furthermore, in the following, access network_A and / or access network_B and / or the devices included in access network_A and / or the devices included in access network_B may be referred to as access networks or access network devices.

[0023] Furthermore, Core Network A corresponds to EPC (Evolved Packet Core). EPC is configured with, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc.

[0024] Furthermore, Core Network B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC.

[0025] Furthermore, in this specification, Core Network A and / or Core Network B and / or devices included in Core Network A and / or devices included in Core Network B may be referred to as the Core Network, or Core Network Devices or Devices within the Core Network, or Network, or NW. In other words, for example, when Network, or NW is referred to in this specification, it may mean Core Network A or Core Network B.

[0026] The core network (Core Network A and / or Core Network B) may be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network (Access Network A and / or Access Network B) to the PDN and / or DN; it may be a core network for a mobile network operator that operates and manages the mobile communication system 1; or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

[0027] Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a Data Network (DN) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to the PDN may also mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with the PDN may also mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN.

[0028] Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures.

[0029] Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication.

[0030] Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached.

[0031] Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may include devices not shown in Figure 2. For example, core network_A and / or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0032] Here, AUSF is a core network device equipped with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure.

[0033] Furthermore, the AAA server is a device equipped with authentication, authorization, and billing functions, which connects directly or indirectly to the AUSF via other network devices. The AAA server may be a network device within the core network. However, the AAA server may not be included in core network_A and / or core network_B, but may be included in PLMN. In other words, the AAA server may be a core network device or a device located outside the core network. For example, the AAA server may be a server device within PLMN managed by a third party.

[0034] Note that in Figure 2, for the sake of simplification, only one of each device / function is shown; however, multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0035] UPF_A235 connects to DN, SMF, other UPFs, and access networks. UPF_A235 may also perform roles such as anchoring to intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, UL CL (Uplink Classifier) ​​functionality supporting routing of multiple traffic flows to a single DN, branching point functionality supporting multi-homed PDU sessions, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and triggering of downlink data notification. Furthermore, UPF_A235 may also act as a relay device for transferring user data, serving as a gateway between the DN and the core network_B190. In addition, UPF_A235 may also act as a gateway for IP communication and / or non-IP communication. Moreover, UPF_A235 may have the functionality to forward IP communication and the functionality to convert between non-IP and IP communication. Furthermore, the multiple gateways that are deployed may also be gateways that connect the core network_B190 to a single DN. Note that UPF_A235 may have connectivity to other NFs and may connect to each device via other NFs.

[0036] Furthermore, a different UPF, UPF_C239 (also referred to as branching point or uplink classifier), may exist as a device or NF between UPF_A235 and the access network. If UPF_C239 exists, the PDU session between the UE and DN will be established via the access network, UPF_C239, and UPF_A235.

[0037] Furthermore, UPF130 may be the same device as UPF_A235. Note that UPF130 and UPF_A235 may be written with the symbols omitted, like UPF.

[0038] [2. Configuration of Each Device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0039] Furthermore, each memory unit within each device / function described below (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network devices, and / or core network devices, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc., contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS occurs, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, not only data transmitted and received via the N26 interface can be stored, but also data transmitted and received without using the N26 interface.

[0040] [2.1. UE Device Configuration] First, an example of the device configuration of a UE (User Equipment) will be described using FIG. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0041] The control unit _A300 is a functional unit that controls the operations and functions of the entire UE. The control unit _A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

[0042] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in an access network via an antenna. That is, the UE can transmit and receive user data and / or control information with an access network device, and / or a core network device, and / or a PDN, and / or a DN using the transceiver unit _A320.

[0043] Referring to FIG. 2 for a detailed description, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. Also, the UE can communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. Further, the UE can transmit and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, the communication between the UE and the AMF is performed via the 5G AN.

[0044] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[0045] [2.2 gNB Device Configuration] Next, an example of the gNB device configuration will be described using FIG. 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510. [[ID=]] [[ID=]]

[0046] The control unit _B500 is a functional unit that controls the operations and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

[0047] The network connection unit _B520 is a functional unit for the gNB to communicate with the AMF and / or UPF. That is, the gNB can transmit and receive user data and / or control information to and from the AMF and / or UPF using the network connection unit _B520.

[0048] The transceiver unit _B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit _B530.

[0049] Explaining in detail with reference to FIG. 2, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit _B520. Also, the gNB can communicate with the UE by using the transceiver unit _B530.

[0050] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0051] [2.3. AMF Device Configuration] Next, an example of the AMF device configuration will be described using Figure 5. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane. The AMF may also be a network device. In other words, for example, in this specification, a network device may mean an AMF.

[0052] The control unit B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit B700 implements various processes in the AMF by reading and executing various programs stored in the memory unit B740 as needed.

[0053] The network connection unit_B720 is a functional unit for the AMF to connect to base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. In other words, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. To put it another way, for example, the network connection unit may also be a transmitting and receiving unit.

[0054] Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620.

[0055] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the AMF.

[0056] Furthermore, the AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM), support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF.

[0057] Furthermore, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. There are two RM states: unregistered state (RM-DEREGISTERED state) and registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location or routing information for that UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, so the UE can receive services that require registration with the network. Note that the RM state may also be expressed as the 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

[0058] In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0059] Furthermore, 5GMM-DEREGISTERED may occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure.

[0060] Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

[0061] Furthermore, connection management may be handled separately for CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access may include an unconnected state (CM-IDLE state over 3GPP access) and a connected state (CM-CONNECTED state over 3GPP access). Furthermore, the CM states in non-3GPP access may include an unconnected state (CM-IDLE state over non-3GPP access) and a connected state (CM-CONNECTED state over non-3GPP access). Note that the unconnected state may be expressed as idle mode, and the connected state may be expressed as connected mode.

[0062] Furthermore, the CM state may be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Additionally, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that 5GMM-IDLE mode may also be expressed as idle mode, and 5GMM-CONNECTED mode may also be expressed as connected mode.

[0063] Furthermore, one or more AMFs may be placed within core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0064] Furthermore, N3IWF is a device and / or function placed between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.

[0065] [2.4. SMF Device Configuration] Next, an example of an SMF device configuration will be explained using Figure 5. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0066] The control unit_B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_B700 implements various processes in the SMF by reading and executing various programs stored in the memory unit_B740 as needed.

[0067] The network connection unit B720 is a functional unit for the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can use the network connection unit B720 to send and receive user data and / or control information with the AMF, and / or UPF, and / or PCF, and / or UDM.

[0068] Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620.

[0069] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF.

[0070] SMF has session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing traffic to appropriate destinations; functions for sending and receiving the SM portion of NAS messages; functions for notifying when downlink data has arrived (Downlink Data Notification); functions for providing AN-specific (AN-specific) SM information sent to ANs via the N2 interface through AMF; functions for determining the SSC mode (Session and Service Continuity mode) for sessions; and roaming functions.

[0071] [2.5. UPF Device Configuration] Next, an example of the UPF device configuration will be explained using Figure 5. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0072] The control unit B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit B700 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed.

[0073] The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN.

[0074] Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620.

[0075] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF.

[0076] UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (Uplink Classifier) ​​function that supports routing multiple traffic flows to a single DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notification.

[0077] Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs.

[0078] Furthermore, the user plane refers to user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. In addition, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane may be referred to as U-Plane.

[0079] Furthermore, the control plane refers to the control messages transmitted and received for communication control of the UE, etc. The control plane may be transmitted and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. In addition, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In addition, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

[0080] Furthermore, the U-Plane (User Plane; UP) may also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers.

[0081] [2.6. Description of Other Devices and / or Functions] Next, we will describe the other devices and / or functions.

[0082] PCF has functions such as providing policy rules.

[0083] Furthermore, UDM has functions such as authentication credential processing, user identification processing, access authentication, registration / mobility management, and subscription management.

[0084] Furthermore, the PCRF is connected to the PGW and / or PDN and has functions for managing QoS for data delivery. For example, it manages the QoS of the communication channel between UE_A10 and the PDN. In addition, the PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.

[0085] Furthermore, the HSS is connected to the MME and / or SCEF and has functions such as managing subscriber information. The subscriber information of the HSS is referenced, for example, when the MME performs access control. In addition, the HSS may be connected to a location management device other than the MME.

[0086] [3. Explanation of Terms and Identification Information Used in Each Embodiment] Next, we will explain in advance the specialized terms and identification information used in each embodiment.

[0087] [3.1. Explanation of Terms Used in Each Embodiment] Next, we will explain the specialized terms used in each embodiment.

[0088] The term "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device. In other words, the statement that a network performs message transmission and / or processing may also mean that devices within the network (network devices, and / or control devices) perform message transmission and / or processing. Conversely, the statement that devices within the network perform message transmission and / or processing may also mean that the network performs message transmission and / or processing.

[0089] SM (Session Management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM (SM procedures), and may be control messages sent and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, SM messages may include PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, PDU session release complete messages, etc. Also, procedures for SM or SM procedures may include PDU session establishment procedures, PDU session modification procedures, and UE-requested PDU session release procedures.Each procedure may be initiated from the UE (User Environment) or from the NW (Network).

[0090] Mobility management (MM) messages (also referred to as NAS MM messages) may be NAS messages used for MM procedures, and may be control messages sent and received between UE_A10 and AMF_A240. Furthermore, MM messages may include registration request messages, registration accept messages, registration reject messages, de-registration request messages, de-registration accept messages, configuration update command messages, configuration update complete messages, service request messages, service accept messages, service reject messages, notification messages, notification response messages, etc. Furthermore, procedures for or for MM may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure (also simply called a UE configuration update procedure), an authentication and / or authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure.

[0091] The 5GS (5G System) service is a connectivity service provided using the core network B190. Furthermore, the 5GS service may be a different service from the EPS service, or it may be a service similar to the EPS service.

[0092] Non-5GS services may be any service other than 5GS services, and may include EPS services and / or non-EPS services.

[0093] The PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it means that data will be sent and received using IPv4. If IPv6 is specified, it means that data will be sent and received using IPv6. If IPv4v6 is specified, it means that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it means that communication will be conducted using a communication method other than IP, rather than IP.

[0094] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the relationship between a DN (Digital Network) and an UE (User Environment) that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN. Each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or other information may be included. Furthermore, when multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different.

[0095] A DNN (Data Network Name) can be any identification information that identifies the core network and / or external networks such as DNs. Furthermore, the DNN can also be used as information to select gateways such as PGW / UPFs that connect to the core network B190. Additionally, the DNN may be equivalent to an APN (Access Point Name).

[0096] The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. Specifying IPv4 indicates that data will be sent and received using IPv4. Specifying IPv6 indicates that data will be sent and received using IPv6. Specifying Ethernet indicates that Ethernet frames will be sent and received. Ethernet may also indicate that IP-based communication will not be used. Specifying Unstructured indicates that data will be sent and received to application servers, etc., on the DN using Point-to-Point (P2P) tunneling technology. P2P tunneling technology may include, for example, UDP / IP encapsulation technology. In addition to the above, IP may also be included as a PDU session type. IP can be specified when the UE (User Environment) can use both IPv4 and IPv6.

[0097] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by a telecommunications operator, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). Furthermore, a UE may maintain an Equivalent HPLMN list (also called an Equivalent HPLMN; also called an Equivalent PLMN) in its USIM to identify one or more EPLMNs. A PLMN that is different from an HPLMN and / or EPLMN may be a VPLMN (Visited PLMN). A PLMN that has been successfully registered by a UE may be a RPLMN (Registered PLMN).

[0098] A tracking area is one or more ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may also consist of multiple cells. Furthermore, a tracking area may be the range where control messages such as paging are broadcast, or the range where UE_A10 can move without handover procedures. Additionally, a tracking area may be a routing area, a location area, or something similar. Hereinafter, a tracking area may also be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN.

[0099] A registration area is a set of one or more TAs assigned by the AMF to a UE. Furthermore, while UE_A10 is moving within one or more TAs included in the registration area, it may move without sending or receiving signals for tracking area updates. In other words, a registration area may be a set of information indicating an area that UE_A10 can move to without performing the tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0100] The current TAI is the TAI broadcast by the selected PLMN within the cell where the UE is located or camping. If the cell is a satellite NG-RAN cell broadcasting multiple TACs in the selected PLMN, the UE NAS layer may select the current TAI from among the multiple TACs in the selected PLMN.

[0101] The Lists of 5GS forbidden tracking areas may be a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional provision of service, stored by a UE not operating in SNPN access operation mode. In other words, a UE not operating in SNPN access operation mode must store a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional service provisioning. Furthermore, the UE must find a suitable cell belonging to a TA that is not included in the list of 5GS forbidden tracking areas within the same PLMN.

[0102] Furthermore, if a UE is in a TA cell that belongs to a list of 5GS forbidden tracking areas for regional provision of service, they are not permitted to request 5GS services other than emergency services.

[0103] Furthermore, the UE may store the prohibited tracking area ID (TAI) in a list of 5GS prohibited tracking areas for regional service provision in order to prevent repeated attempts to access cells in prohibited tracking areas. In addition, the list of 5GS prohibited tracking areas for regional service provision may be deleted when the UE is powered off, the SIM is removed, or periodically (for periods ranging from 12 to 24 hours).

[0104] Furthermore, information indicating 5GS forbidden tracking areas for roaming may be included in an Information Element (IE) containing one or more Forbidden TAIs (also referred to as Forbidden TAIs) for the list of "5GS forbidden tracking areas for roaming" and transmitted to the UE in a message sent by the network.

[0105] Additionally, 5GS forbidden tracking areas for regional service provision may be included in an Information Element (IE) containing one or more Forbidden TAIs for the list of "5GS forbidden tracking areas for regional provision of service" and transmitted to the UE within a message sent by the network.

[0106] A UE ID is information used to identify a UE (User Account). For example, a UE ID may be a SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, a UE ID may be other information configured within an application or network. Furthermore, a UE ID may be information used to identify a user.

[0107] PC5 is a reference point. PC5 may also be a reference point between ProSe-enabled UEs. Furthermore, PC5 may be a reference point for 5G ProSe Direct Discovery, and / or 5G ProSe Direct Communication, and / or 5G ProSe U2N (UE-to-Network) Relay, and / or 5G ProSe U2U (UE-to-UE) Relay.

[0108] A PC5 path may be a communication channel on PC5. A PC5 path may also be a communication channel between ProSe-compatible UEs. Furthermore, a PC5 path may be PC5 itself. A PC5 path may also be referred to as a PC5 interface.

[0109] A PC5 link may be a PC5 path. A PC5 link may also be called a PC5 direct link, a 5G ProSe direct link, a direct link, or simply a link.

[0110] Uu may be a wireless interface. Furthermore, Uu may be a wireless interface between a 5G AN and an UE.

[0111] A Uu path may be a communication channel on Uu. A Uu path may also be a communication channel between a 5G AN and a UE. Furthermore, a Uu path may be Uu itself. A Uu path may also be referred to as a Uu interface. A Uu path may also be referred to as a Uu link.

[0112] 5G ProSe (Proximity-based Services) may be services provided by 5GS based on UEs that are in close proximity to each other. Furthermore, 5G ProSe may simply be referred to as ProSe.

[0113] A 5G ProSe-enabled UE may be a UE that supports 5G ProSe requirements and related procedures. A 5G ProSe-enabled UE may also be referred to as a ProSe-enabled UE.

[0114] The initiating UE may be the UE that sends the PROSE direct link establishment request message.

[0115] The target UE may be the UE that sends the PROSE direct link establishment acceptance message.

[0116] A remote UE may be a ProSe-enabled UE that communicates with the DN via a U2N relay UE.

[0117] The remote UE may be a 5G ProSe remote UE, a 5G ProSe layer-2 remote UE, or a 5G ProSe layer-3 remote UE. Furthermore, the 5G ProSe layer-2 remote UE may be a 5G ProSe-compatible UE that communicates with the DN via a 5G ProSe layer-2 UE-to-network relay UE. Similarly, the 5G ProSe layer-3 remote UE may be a 5G ProSe-compatible UE that communicates with the DN via a 5G ProSe layer-3 UE-to-network relay UE.

[0118] A remote UE may also be referred to as a UE that operates as a remote UE.

[0119] Furthermore, the 5G ProSe layer-2 remote UE is a 5G ProSe-compatible UE that communicates with the DN via the 5G ProSe layer-2 U2N relay UE. The 5G ProSe layer-2 remote UE may also be referred to as a layer-2 remote UE.

[0120] Furthermore, a 5G ProSe layer-3 remote UE is a 5G ProSe-compatible UE that communicates with the DN via a 5G ProSe layer-3 UE-to-network relay UE. A 5G ProSe layer-3 remote UE can also be referred to as a layer-3 remote UE.

[0121] A remote UE may be any UE that has been approved to operate as a remote UE.

[0122] A U2N (UE-to-network) relay UE may be a ProSe-enabled UE that provides functionality to support the network connectivity of a remote UE.

[0123] The U2N relay UE may be a 5G ProSe U2N relay UE, a 5G ProSe layer-2 U2N relay UE, or a 5G ProSe layer-3 U2N relay UE. Furthermore, the 5G ProSe layer-2 U2N relay UE may be a 5G ProSe-compatible UE that provides functionality to support network connectivity for a 5G ProSe layer-2 remote UE via a Layer 2 protocol. Additionally, the 5G ProSe layer-3 U2N relay UE may be a 5G ProSe-compatible UE that provides functionality to support network connectivity for a 5G ProSe layer-3 remote UE via a Layer 3 protocol.

[0124] A U2N relay UE may also be referred to as a UE that operates as a U2N relay UE. Furthermore, a U2N relay UE may also be referred to as a target relay UE. Finally, a U2N relay UE may also be referred to as a U2N relay.

[0125] Furthermore, the 5G ProSe layer-2 U2N relay UE is a 5G ProSe-enabled UE that provides functionality to support network connectivity for the 5G ProSe layer-2 remote UE via the layer-2 protocol.

[0126] Furthermore, the 5G ProSe layer-3 U2N relay UE is a 5G ProSe-enabled UE that provides the functionality to support network connectivity for the 5G ProSe layer-3 remote UE via the layer-3 protocol.

[0127] Furthermore, the communication method in which a remote UE connects to the network via a U2N relay UE may be referred to as 5G ProSe UE-to-network relaying. 5G ProSe UE-to-network relaying may also be simply referred to as relaying, 5G ProSe UE-to-network relay, relay, or U2N relay.

[0128] A U2N relay UE may be any UE that has been approved to operate as a U2N relay UE.

[0129] A remote UE that supports multi-hop communication may be a ProSe-enabled UE that communicates with the DN via a U2N intermediate UE and a multi-hop U2N relay UE.

[0130] A remote UE that supports multi-hop may be a 5G ProSe remote UE supporting 5G ProSe multi-hop U2N Relay, or a 5G ProSe remote UE supporting 5G ProSe Layer-3 multi-hop U2N Relay.

[0131] Furthermore, the 5G ProSe remote UE supporting 5G ProSe Layer-3 multi-hop U2N Relay may be a 5G ProSe-compatible UE that communicates with the DN via a 5G ProSe Layer-3 U2N intermediate UE and / or a 5G ProSe U2N relay UE supporting 5G ProSe Layer-3 multi-hop U2N Relay. Furthermore, the 5G ProSe remote UE supporting 5G ProSe Layer-3 multi-hop U2N Relay may also be referred to as a multi-hop layer-3 remote UE.

[0132] A remote UE that supports multi-hop may also be referred to as a UE that operates as a multi-hop supporting remote UE. Furthermore, a remote UE that supports multi-hop may also be referred to as a multi-hop remote UE. Additionally, a multi-hop remote UE may be referred to as a 5G ProSe multi-hop remote UE.

[0133] A multi-hop remote UE may be any remote UE that supports multi-hop.

[0134] A multi-hop remote UE may be any UE that is authorized to operate as a multi-hop remote UE.

[0135] A multi-hop remote UE may also be referred to as a 5G ProSe multi-hop remote UE, a 5G ProSe multi-hop layer-2 remote UE, or a 5G ProSe multi-hop layer-3 remote UE.

[0136] A 5G ProSe multi-hop layer-2 remote UE may be a ProSe-enabled UE that communicates with a DN via zero or more 5G ProSe layer-2 intermediate UE-to-Network relay UEs and 5G ProSe multi-hop layer-2 UE-to-Network relay UEs.

[0137] A 5G ProSe multi-hop layer-3 remote UE may be a ProSe-enabled UE that communicates with a DN via zero or more 5G ProSe layer-3 intermediate UE-to-Network relay UEs and 5G ProSe multi-hop layer-3 UE-to-Network relay UEs.

[0138] A U2N (UE-to-network) relay UE that supports multi-hop can be a ProSe-enabled UE that provides functionality to support network connectivity for multi-hop remote UEs.

[0139] A U2N relay UE that supports multi-hop may be a 5G ProSe U2N relay UE supporting 5G ProSe multi-hop U2N Relay, or a 5G ProSe U2N relay UE supporting 5G ProSe Layer-3 multi-hop U2N Relay.

[0140] Furthermore, the 5G ProSe U2N relay UE supporting 5G ProSe Layer-3 multi-hop U2N Relay may be a 5G ProSe-enabled UE that provides the functionality to support network connectivity for the 5G ProSe remote UE supporting 5G ProSe Layer-3 multi-hop U2N Relay via the Layer 3 protocol. Furthermore, the 5G ProSe U2N relay UE supporting 5G ProSe Layer-3 multi-hop U2N Relay may also be referred to as a multi-hop layer-3 U2N relay UE.

[0141] A U2N relay UE that supports multi-hop may also be referred to as a UE that operates as a U2N relay UE that supports multi-hop. Furthermore, a U2N relay UE that supports multi-hop may also be referred to as a multi-hop U2N relay UE. Furthermore, a multi-hop U2N relay UE may also be referred to as a multi-hop U2N relay. Finally, a multi-hop U2N relay UE may also be referred to as a 5G ProSe multi-hop U2N relay UE.

[0142] A multi-hop U2N relay UE may be a U2N relay UE that supports multi-hop.

[0143] A multi-hop U2N relay UE may be any UE that is authorized to operate as a multi-hop U2N relay UE.

[0144] The multi-hop U2N relay UE may also be referred to as the 5G ProSe multi-hop UE-to-network relay UE, the 5G ProSe multi-hop layer-2 UE-to-network relay UE, or the 5G ProSe multi-hop layer-3 UE-to-network relay UE.

[0145] A 5G ProSe multi-hop UE-to-Network relay UE may be a 5G ProSe UE-to-network relay UE that supports 5G ProSe multi-hop UE-to-network relay.

[0146] A 5G ProSe multi-hop layer-2 UE-to-network relay UE may be a 5G ProSe layer-2 UE-to-network relay UE that supports 5G ProSe multi-hop layer-2 UE-to-network relay.

[0147] A 5G ProSe multi-hop layer-3 UE-to-network relay UE may be a 5G ProSe layer-3 UE-to-network relay UE that supports 5G ProSe multi-hop layer-3 UE-to-network relay.

[0148] A U2N (UE-to-network) intermediate UE may be a ProSe-enabled UE that provides functionality to support connectivity between a multi-hop remote UE and a multi-hop U2N relay UE.

[0149] The U2N intermediate UE may be a 5G ProSe U2N intermediate UE or a 5G ProSe layer-3 U2N intermediate UE. Furthermore, the 5G ProSe layer-3 U2N intermediate UE may be a 5G ProSe-enabled UE that provides functionality to support network connectivity for a 5G ProSe remote UE supporting a 5G ProSe Layer-3 multi-hop U2N Relay via a Layer 3 protocol and / or a 5G ProSe U2N relay UE supporting a 5G ProSe Layer-3 multi-hop U2N Relay. The 5G ProSe layer-3 U2N intermediate UE may also be referred to as a layer-3 U2N intermediate UE.

[0150] A U2N intermediate UE may also be referred to as a UE that operates as a U2N intermediate UE. A U2N intermediate UE may also be referred to as an intermediate U2N UE.

[0151] Furthermore, there may be one or more U2N intermediate UEs. For example, between a multi-hop remote UE and a multi-hop U2N relay UE, there may be a first U2N intermediate UE and a second U2N intermediate UE, from left to right.

[0152] Furthermore, the U2N intermediate UE may also be referred to as Relay participated in multi-hop U2N relaying, or as 5G ProSe Intermediate Relay. The U2N intermediate UE may also be referred to as multi-hop U2N relay UE, or as 5G ProSe multi-hop U2N relay UE. The U2N intermediate UE may also be referred to as 5G ProSe layer-3 multi-hop U2N relay UE. Furthermore, the U2N intermediate UE may also be referred to as 5G ProSe L3 (Layer-3) Intermediate relay, or as 5G ProSe L3 (Layer-3) Intermediate relay UE.

[0153] Furthermore, the U2N intermediate UE may also be referred to as the 5G ProSe Intermediate U2N Relay UE or the 5G ProSe Intermediate U2N Relay.

[0154] A U2N intermediate UE may be any UE that has been authorized to operate as a U2N intermediate UE.

[0155] The U2N intermediate UE may also be referred to as the 5G ProSe intermediate UE-to-network relay UE, the 5G ProSe layer-2 intermediate UE-to-network relay UE, or the 5G ProSe layer-3 intermediate UE-to-network relay UE.

[0156] A 5G ProSe intermediate UE-to-network relay UE may be a ProSe-enabled UE that provides the functionality to support network connectivity for multi-hop remote UEs by using other ProSe-enabled UEs and a PC5 reference point. The 5G ProSe intermediate UE-to-network relay UE may be located on the path between the multi-hop remote UE and the multi-hop U2N relay UE.

[0157] A 5G ProSe layer-2 intermediate UE-to-network relay UE may be a ProSe-enabled UE that provides the ability to support connection to a network of 5G ProSe multi-hop layer-2 remote UEs using a PC5 reference point with other ProSe-enabled UEs via the layer-2 protocol.

[0158] A 5G ProSe layer-3 intermediate UE-to-network relay UE may be a ProSe-enabled UE that provides the ability to support connection to a network of 5G ProSe multi-hop layer-3 remote UEs using other ProSe-enabled UEs and PC5 reference points via the layer-3 protocol.

[0159] The End UE may be a ProSe-enabled UE that communicates with another ProSe-enabled UE via a U2U (UE-to-UE) relay UE. The end UE may be a ProSe-enabled UE that communicates with another ProSe-enabled UE via a U2U relay UE. In this specification, a 5G ProSe End UE is also simply referred to as an End UE.

[0160] The End UE may be a 5G ProSe end UE, a 5G ProSe layer-2 end UE, or a 5G ProSe layer-3 end UE. Furthermore, the 5G ProSe layer-2 end UE may be a 5G ProSe-compatible UE that communicates with other 5G ProSe-compatible UEs via a 5G ProSe layer-2 UE-to-UE relay UE. Similarly, the 5G ProSe layer-3 end UE may be a 5G ProSe-compatible UE that communicates with other 5G ProSe-compatible UEs via a 5G ProSe layer-3 UE-to-UE relay UE.

[0161] An End UE may also be referred to as a UE that acts as an End UE. More specifically, an End UE may consist of a source End UE and a destination End UE (or target End UE). Here, the source end UE may be the end UE that sends the request message, and the target end UE may be the end UE that receives the request message.

[0162] Furthermore, the 5G ProSe layer-2 end UE is a 5G ProSe-enabled UE that communicates with another 5G ProSe-enabled UE via the 5G ProSe layer-2 U2U relay UE.

[0163] Furthermore, the 5G ProSe layer-3 end UE is a 5G ProSe-enabled UE that communicates with another 5G ProSe-enabled UE via the 5G ProSe layer-3 U2U relay UE.

[0164] A multi-hop End UE may be an End UE that supports multi-hop. A multi-hop UE may be a 5G ProSe multi-hop layer-3 end UE. A multi-hop End UE may be a 5G ProSe Layer-3 End UE that supports 5G ProSe Layer-3 multi-hop UE-to-UE Relay.

[0165] A U2U (UE-to-UE) relay UE may be a ProSe-enabled UE that provides functionality to support connectivity between two end UEs. One or more U2U relay UEs may be ProSe-enabled UEs that provide functionality to support connectivity between two end UEs.

[0166] The UE-to-UE relay (U2U Relay) UE may be a 5G ProSe U2U relay UE, a 5G ProSe layer-2 U2U relay UE, or a 5G ProSe layer-3 U2U relay UE. In this specification, the 5G ProSe UE-to-UE Relay is also referred to simply as U2U Relay or U2U Relay UE. Furthermore, when describing multiple U2U Relay UEs in this specification, each U2U Relay UE is also referred to as U2U Relay UE#1, U2U Relay UE#2, etc., to distinguish them.

[0167] Here, the 5G ProSe layer-2 U2U relay UE may be a 5G ProSe-enabled UE that provides the functionality to support connectivity between two 5G ProSe layer-2 end UEs via a Layer 2 protocol.

[0168] Furthermore, the 5G ProSe layer-3 U2U relay UE may be a 5G ProSe-enabled UE that provides the functionality to support connectivity between two 5G ProSe layer-3 end UEs via the Layer 3 protocol.

[0169] A U2U relay UE may also be referred to as a UE that operates as a U2U relay UE. A U2U relay UE may also be referred to as a U2U relay.

[0170] Furthermore, the 5G ProSe layer-2 U2U relay UE is a 5G ProSe-enabled UE that provides the functionality to support connectivity between two 5G ProSe layer-2 end UEs via the layer-2 protocol.

[0171] Furthermore, the 5G ProSe layer-3 U2U relay UE is a 5G ProSe-enabled UE that provides the functionality to support connectivity between two 5G ProSe layer-3 end UEs via the layer-3 protocol.

[0172] Furthermore, a 5G ProSe multi-hop layer-3 UE-to-UE relay UE may be a 5G ProSe layer-3 UE-to-UE relay UE that supports 5G ProSe multi-hop layer-3 UE-to-UE relay.

[0173] Furthermore, a 5G ProSe multi-hop layer-2 UE-to-UE relay UE may be a 5G ProSe layer-2 UE-to-UE relay UE that supports 5G ProSe multi-hop layer-2 UE-to-UE relay.

[0174] A 5G ProSe multi-hop L3 U2U relay UE may be a 5G ProSe multi-hop layer-3 UE-to-UE relay UE, or a 5G ProSe multi-hop layer-2 UE-to-UE relay UE.

[0175] The discovery procedure may be a procedure for detecting and identifying another nearby UE using NR radio signals. More specifically, the discovery procedure may be a 5G ProSe direct discovery procedure, a 5G ProSe U2N relay discovery procedure, or a 5G ProSe U2U relay discovery procedure. The discovery procedure may also be referred to as 5G ProSe direct discovery or 5G ProSe discovery.

[0176] Multi-hop communication may refer to communication via two or more UEs. Alternatively, multi-hop communication may refer to a UE communicating with another UE or network via two or more other UEs.

[0177] More specifically, for example, multi-hop communication may be communication between End UEs via two or more U2U (UE-to-UE) Relay UEs.

[0178] Furthermore, for example, when a multi-hop remote UE connects to a network via one or more U2N intermediate UEs and a multi-hop U2N relay UE, this may be referred to as multi-hop communication. In this case, the multi-hop remote UE and / or U2N intermediate UE and / or multi-hop U2N relay UE may support multi-hop.

[0179] Here, multi-hop communication may be UE-to-network relay multi-hop communication, UE-to-UE relay multi-hop communication, 5G ProSe U2N(UE-to-network) relay multi-hop communication, or 5G ProSe U2U(UE-to-UE) relay multi-hop communication.

[0180] Multi-hop communication may simply be referred to as multi-hop. Furthermore, a UE that supports multi-hop may be a multi-hop UE. Also, a UE that supports multi-hop may be a UE that supports operating as a multi-hop UE.

[0181] The multi-hop relay may be a 5G ProSe multi-hop U2N relay, a 5G ProSe multi-hop layer-2 U2N relay, a 5G ProSe multi-hop layer-3 U2N relay, a 5G ProSe multi-hop U2U relay, a 5G ProSe multi-hop layer-2 U2U relay, or a 5G ProSe multi-hop layer-3 U2U relay.

[0182] Furthermore, a UE that supports multi-hop communication may be a multi-hop UE. Also, a UE that supports multi-hop communication may be a UE that supports operating as a multi-hop UE. More specifically, for example, a UE that supports multi-hop communication may be a 5G ProSe U2U (UE-to-UE) Relay UE and / or a 5G ProSe U2N (UE-to-Network) Relay UE. Or, for example, a UE that supports multi-hop communication may be a 5G ProSe U2U (UE-to-UE) Relay UE and / or a 5G ProSe U2N (UE-to-Network) Relay UE and / or a 5G ProSe U2U Relay UE and / or a 5G ProSe U2U End UE.

[0183] Supporting multi-hop means supporting 5G ProSe multi-hop U2N relay and / or U2U relay, supporting 5G ProSe multi-hop layer-2 U2N relay, supporting 5G ProSe multi-hop layer-3 U2N relay, supporting 5G ProSe multi-hop layer-2 U2U relay, and supporting 5G ProSe multi-hop layer-3 U2U relay.

[0184] The Application Layer ID is an identifier that identifies a 5G ProSe-enabled UE within the context of a particular application.

[0185] The Relay Service Code (RCS) may be information used to identify the connection services provided by U2U-relay and / or U2N relay, and the authorized users to whom U2U-relay and / or U2N relay provides these services. In this specification, the Relay Service Code is also referred to as RCS.

[0186] Furthermore, for example, the relay service code may be information used to identify communication or communication services between End UEs via a multi-hop communication path using one or more U2U-relay UEs.

[0187] Furthermore, the relay service code may select security policies and information necessary for authentication and authorization between the End UE and the U2U relay UE.

[0188] Furthermore, the relay service code may be information included in the configuration parameters for U2U-relay and / or U2N relay. The relay service code may be information included in the configuration parameters for U2U-relay and / or U2N relay. The relay service code may be information included in the configuration parameters for End UE.

[0189] ProSeP may be a 5G ProSe policy, or information that indicates or includes a 5G ProSe policy. Furthermore, ProSeP may be a UE policy for ProSe, or a UE policy for ProSe services. ProSeP may also be provided from the network to the UE through the network-requested UE policy management procedure and / or the UE-requested ProSeP provision procedure described below. Furthermore, ProSeP may be information determined by the PCF and provided to the UE via the AMF. ProSeP may also be referred to as a ProSe policy.

[0190] ProSeP may include UE policies for 5G ProSe direct discovery, UE policies for 5G ProSe direct communications, UE policies for 5G ProSe UE-to-network relay, UE policies for 5G ProSe usage information reporting, UE policies for 5G ProSe UE-to-UE relay, UE policies for 5G ProSe multi-hop UE-to-network relay, and / or UE policies for 5G ProSe multi-hop UE-to-UE relay.

[0191] Here, the UE policy for 5G ProSe multi-hop UE-to-network relay may be a UE policy for 5G ProSe multi-hop UE-to-network relay UE, a UE policy for 5G ProSe intermediate UE-to-network relay UE, and / or a UE policy for 5G ProSe multi-hop UE-to-network remote UE.

[0192] Here, the UE policy for 5G ProSe multi-hop UE-to-UE relay may be the UE policy for 5G ProSe multi-hop UE-to-UE relay UE, and / or the UE policy for 5G ProSe multi-hop UE-to-UE end UE.

[0193] [3.2. Description of Identification Information in Each Embodiment] Next, the identification information used in each procedure of each embodiment will be described. Note that each piece of identification information may be control information or information, and in this specification, it will be referred to as control information or simply information.

[0194] In this embodiment, the first identification information is information indicating the UE's capability with respect to the 5G ProSe function. The first identification information may also be information included in the 5GMM (5GS mobility management) capability information element (IE).

[0195] More specifically, for example, the first identification information is "5G ProSe direct discovery" and / or "5G ProSe Direct Communication" and / or "5G ProSe L2 U2N relay (5G ProSe Layer-2 UE-to-Network Relay)" and / or "5G ProSe L3 U2N relay (5G ProSe Layer-3 UE-to-Network Relay)" and / or "5G ProSe L2 remote UE (5G ProSe Layer-2 Remote UE)" and / or "5G ProSe L3 remote UE (5G ProSe Layer-3 Remote UE)" and / or "5G ProSe L2 U2U relay UE (5G ProSe Layer-2 UE-to-UE Relay UE)" and / or "5G ProSe Information indicating whether the UE supports operating as "L2 End UE (5G ProSe Layer-2 End UE)" and / or "5G ProSe L3 End UE (5G ProSe Layer-3 End UE)," or information indicating whether the UE supports these functions or operations.

[0196] In other words, for example, if a UE supports any of the 5G ProSe features, the UE may set or configure the corresponding bit in the 5GMM capability IE included in the registration request message to indicate that it supports that feature. In addition, if the feature is supported, the bit may be set to "1".

[0197] In this embodiment, the second identification information indicates the capability of the UE, or is information related to the capability of the UE. The second identification information indicates that the UE supports the 5G ProSe multi-hop relay function. The second identification information may also be information included in the 5GMM capability information element. Furthermore, the second identification information may be a single piece of information, or it may be a single bit of information within the 5GMM capability information element.

[0198] Furthermore, the second identification information may be combined with the first identification information to indicate whether or not the UE supports the multi-hop function corresponding to the function supported by the first identification information. Here, combining the second identification information and the first identification information means that the UE includes the second identification information and the first identification information in the same control message and sends it to the network. Note that the control message including the second identification information and the first identification information may be an MM (Mobility Management) message, for example, a registration request message.

[0199] Furthermore, the condition for the UE to include the second identification information in the 5GMM capability information element in the registration request message may be that the first identification information is included in the said 5GMM capability information element. Alternatively, the condition for the UE to include the second identification information in the 5GMM capability information element in the registration request message may be independent of whether the first identification information is included in the said 5GMM capability information element. Alternatively, the condition for the UE to include the second identification information in the 5GMM capability information element in the registration request message may be that the first identification information is not included in the said 5GMM capability information element.

[0200] More specifically, for example, the second identification information and the first identification information indicate a combination of "5G ProSe Layer-3 UE-to-Network Relay" and / or "5G ProSe Layer-3 Remote UE" and / or "5G ProSe Layer-2 UE-to-UE Relay" and / or "5G ProSe Layer-3 UE-to-UE Relay" and / or "5G ProSe Layer-3 End UE" to indicate whether the UE supports or does not support "5G ProSe Layer-3 multi-hop UE-to-Network Relay" and / or "5G ProSe Layer-3 multi-hop Remote UE" and / or "5G ProSe Layer-2 multi-hop UE-to-UE Relay" and / or "5G ProSe Layer-3 multi-hop UE-to-UE Relay" and / or "5G ProSe multi-hop Layer-3 End UE".

[0201] Furthermore, for example, a UE may indicate that it supports "5G ProSe L3 multi-hop U2U relay" by including a first identifier and a second identifier in the 5GMM capability information element of a registration request message and sending it to the network. In addition, a network or AMF that receives the registration request message from the UE may recognize and remember that the UE supports "5G ProSe L3 multi-hop U2U relay" from the combination of the first and second identifiers.

[0202] In other words, for example, if a UE supports any of the functions related to 5G ProSe multi-hop relay, the UE may set or configure the corresponding bit in the 5GMM capability IE included in the registration request message, along with the first identification information, to indicate that it supports that function. If the function is supported, the bit may be set to "1".

[0203] In this embodiment, the third identification information is information indicating the capability of the UE. The third identification information indicates whether the UE supports "5G ProSe layer-3 intermediate relay" or whether the UE supports operating as a 5G ProSe layer-3 intermediate relay. The third identification information may also be information included in the 5GMM capability information element (IE).

[0204] Here, the third identification information may be, for example, a single piece of information, or it may be one bit of information within the 5GMM capability information element.

[0205] In other words, for example, if a UE supports operating as a 5G PeoSe L3 intermediate relay, the UE may set the 5G PeoSe L3 intermediate relay bit in the 5GMM capability IE included in the registration request message to "Acting as a 5G ProSe layer-3 intermediate relay UE supported". If this function is supported, the bit may be set to "1".

[0206] Furthermore, the third identification information may be transmitted from the UE to the network together with the first identification information and / or the second identification information and / or the fourth identification information and / or the fifth identification information.

[0207] Furthermore, the condition for the UE to include the third identification information in the 5GMM capability information element in the registration request message may be that the fourth identification information is included in the 5GMM capability information element. Alternatively, the condition for the UE to include the third identification information in the 5GMM capability information element in the registration request message may be independent of whether the first identification information is included in the 5GMM capability information element. Alternatively, the condition for the UE to include the third identification information in the 5GMM capability information element in the registration request message may be that the first identification information is not included in the 5GMM capability information element.

[0208] In this embodiment, the fourth identification information indicates the capability of the UE, or is information relating to the capability of the UE. The second identification information indicates that the UE supports the 5G ProSe multihop relay function, and / or indicates the existence of a fifth identification information indicating one or more of the 5G ProSe multihop relay functions supported by the UE. The fourth identification information may also be information included in the 5GMM capability information element. Furthermore, the fourth identification information may be a single piece of information, or it may be a single bit of information within the 5GMM capability information element.

[0209] In other words, for example, if a UE supports any of the functions related to 5G ProSe multi-hop relay, the UE may set the corresponding bit in the 5GMM capability IE included in the registration request message to indicate that it supports the function or that it contains a fifth identification. If the function is supported, the bit may be set to "1".

[0210] Furthermore, the condition for the UE to include the fourth identification information in the 5GMM capability information element in the registration request message is that the fourth identification information is already included in the 5GMM capability information element. Alternatively, the condition for the UE to include the fourth identification information in the 5GMM capability information element in the registration request message is independent of whether the first identification information is included in the 5GMM capability information element. Alternatively, the condition for the UE to include the fourth identification information in the 5GMM capability information element in the registration request message is that the first identification information is not included in the 5GMM capability information element.

[0211] More specifically, for example, the UE may include the fourth and fifth identification information in the registration request message and send it to the network. Furthermore, for example, the UE may indicate that it supports the 5G ProSe multi-hop relay function by including the fourth and fifth identification information in the registration request message and sending it to the network. Conversely, the UE may indicate that it does not support the 5G ProSe multi-hop relay function by not including the fourth identification information in the registration request message and sending it.

[0212] Furthermore, the UE may include the fourth and fifth identification information in a control message (such as a registration request message) and send it to the network, thereby indicating that the fourth identification information supports the 5G ProSe multi-hop relay function, and also indicating that the fifth identification information is included.

[0213] Alternatively, the UE may include the fourth identification information in a control message (such as a registration request message) and send it to the network, but without including the fifth identification information.

[0214] In this embodiment, the fifth identification information is information indicating the UE's capability regarding the multi-hop 5G ProSe function. The fifth identification information may also be information included in an information element other than the 5GMM capability information element. Here, the information element containing the fifth identification information may be, for example, an extended 5GMM capability information element, an information element indicating multi-hop 5G ProSe support, or another existing information element other than the 5GMM capability IE included in the registration request message, but is not limited to these.

[0215] Furthermore, the condition for the UE to include the fifth identification information in the 5GMM capability information element in the registration request message is that the fifth identification information is included in the 5GMM capability information element. Alternatively, the condition for the UE to include the fifth identification information in the 5GMM capability information element in the registration request message is independent of whether the first identification information is included in the 5GMM capability information element. Alternatively, the condition for the UE to include the fifth identification information in the 5GMM capability information element in the registration request message is that the first identification information is not included in the 5GMM capability information element.

[0216] More specifically, for example, the fifth identification information could be "5G ProSe L3 U2N relay supporting 5G ProSe Layer-3 multi-hop U2N relay" and / or "5G ProSe L3 U2N remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay" and / or "5G ProSe L3 intermediate U2N relay" and / or "5G ProSe L3 U2U relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE relay" Information indicating whether the UE supports operating as a "5G ProSe Layer-3 End UE (5G ProSe Layer-3 multi-hop UE-to-UE Relay)" and / or as a "5G ProSe Layer-3 multi-hop UE-to-UE Relay," or information indicating whether the UE supports these functions or operations.

[0217] Furthermore, when the UE includes the fifth identification information in a control message (such as a registration request message) and transmits it to the network, it may or may not include the fourth identification information in the control message.

[0218] Alternatively, the UE may include the fifth identification information in a control message (such as a registration request message) and send it to the network, but without including the fourth identification information.

[0219] In other words, for example, if a UE supports any of the features related to 5G ProSe multi-hop relay, the UE may set the corresponding bit in the information element indicating multi-hop 5G ProSe support included in the registration request message to indicate that it supports the feature or that it includes a fifth identification information. If the feature is supported, the bit may be set to "1".

[0220] In this embodiment, the tenth identification information may be a policy for the UE for the multi-hop 5G ProSe UE. Alternatively, the tenth identification information may be a ProSe Policy (ProSeP). Furthermore, the tenth identification information may be information included in UE Policies IE.

[0221] More specifically, the tenth identification information may be a UE policy for a "5G ProSe multi-hop U2N relay UE (5G ProSe multi-hop UE-to-network relay UE)", and / or a "5G ProSe intermediate U2N relay UE (5G ProSe intermediate UE-to-network relay UE)", and / or a "5G ProSe multi-hop U2N remote UE (5G ProSe multi-hop UE-to-network remote UE)", and / or a "5G ProSe multi-hop U2U relay UE (5G ProSe multi-hop UE-to-UE relay UE)", and / or a "5G ProSe multi-hop U2U end UE (5G ProSe multi-hop UE-to-UE end UE)".

[0222] Details of the behavior of the UE and network based on one or more combinations of the above identification information from the first to the fifth are not limited to those described in this chapter, but are also described in Chapter 4 and / or Chapter 5.

[0223] [4. Description of Procedures Used in Each Embodiment] Next, the procedures used in each embodiment will be described. Here, the procedures used in each embodiment may include a registration procedure, a network request UE policy management procedure, a UE request ProSeP provision procedure, and a 5G ProSe UE-to-UE Relay communication procedure by integrated discovery.

[0224] In each embodiment, the explanation will be based on the example where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software), as shown in Figure 2. However, the contents described in this embodiment are also applicable when these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between them, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0225] [4.1. Registration Procedure] The registration procedure will be explained using Figure 6.

[0226] The registration procedure is initiated and executed by the UE in 5GS. Hereafter, in this section, this procedure will also be referred to as the registration procedure. The registration procedure is a procedure initiated by the UE to register with access network_B and / or core network_B and / or DN. The UE can execute this procedure at any time, for example, when powering on, if it is not registered with the network. In other words, the UE can start this procedure at any time as long as it is in the unregistered state (RM-DEREGISTERED state). Furthermore, each device (especially the UE and AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0227] Furthermore, the registration procedure may be an initial registration initiated by the UE, or a mobility and periodic registration update, or a mobility registration update procedure. Here, the mobility registration update procedure may also be called a registration procedure for mobility updates. These registration procedures may also be MM procedures.

[0228] Furthermore, the registration procedure may also be a procedure for updating the location registration information of the UE in the network, and / or for the UE to periodically notify the network of the status of the UE, and / or for updating specific parameters related to the UE in the network.

[0229] Furthermore, in this procedure, each UE may be permitted by the network to use multi-hop communication or multi-hop functionality via two or more U2U relay UEs. In addition, after the completion of this procedure, each UE may, based on permission from the network, establish a ProSe Layer-3 multi-hop UE-to-UE Relay communication path and initiate or execute ProSe Layer-3 multi-hop UE-to-UE Relay communication.

[0230] A UE may initiate the registration process when it moves across TAs. More specifically, a UE may initiate a Mobility Registration Update process to re-register when it moves to a TA different from the one indicated in its TA list. Furthermore, a UE may initiate this process when a running timer expires. Furthermore, a UE may initiate the registration process when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, a UE may initiate the registration process if there is a change in capability information and / or preferences related to the establishment of a UE PDU session. Furthermore, a UE may initiate the registration process periodically. Furthermore, a UE may initiate the registration process based on the completion of a UE configuration update process. Note that a UE can perform the registration process at any time it chooses, not limited to these.

[0231] Furthermore, a UE may initiate a registration process periodically, even if it is already registered. In other words, a UE may initiate a registration process based on the expiration of a timer. In other words, a registration process performed periodically may be a Periodic Registration Update process.

[0232] Furthermore, the registration procedure performed based on the mobility of the UE and the registration procedure performed periodically will also be referred to as the registration procedure for mobility and registration renewal, or the registration renewal procedure. In other words, the registration procedure for mobility and registration renewal may be a registration procedure performed based on the mobility of the UE, or it may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a configuration update of the UE. Furthermore, the registration procedure for mobility and registration renewal may be a registration procedure performed to establish a communication channel for sending and receiving user data. Furthermore, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a request from the network. In other words, the registration procedure for mobility and registration renewal may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration renewal may be referred to as "this procedure".

[0233] Next, we will explain each step of the registration process. Note that the registration process described below may refer to the initial registration process or the registration process for mobility and registration renewal.

[0234] First, the UE initiates the registration process by sending a Registration request message to the AMF (S600)(S602)(S604). Specifically, the UE sends an RRC message containing the Registration request message to the 5G AN (or gNB) (S600). The Registration request message is a NAS message. The RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

[0235] Here, the UE may include one or more of the first to fifth identification information in the registration request message and / or RRC message and transmit it to the network. More specifically, the UE may include one or more of the first to fifth identification information in the registration request message and / or RRC message and transmit it, or it may include it in a different control message, for example, a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer).

[0236] Specific examples of one or more of the first to fifth identification information that the UE includes in the registration request message are detailed in Chapter 5.

[0237] In this case, if multiple pieces of identification information are sent and received between the UE and the network, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Furthermore, the information indicating support for each function and the information indicating a request to use each function may be sent and received as the same piece of identification information, or as different pieces of identification information.

[0238] Furthermore, the UE may indicate to the network that it supports each function, or indicate the UE's request, by sending a registration request message containing one or more of the identification information from the first to fifth categories.

[0239] Furthermore, the UE may include each piece of identification information in the registration request message and send it, thereby indicating to the network what the identification information included in the registration request message represents.

[0240] Furthermore, the UE may select and decide whether or not to include one or more of the first to fifth types of identification information in the registration request message, based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE.

[0241] When a 5G AN (or gNB) receives an RRC message containing a registration request message, it selects an AMF to forward the registration request message (S602). The 5G AN (or gNB) may select an AMF based on the information contained in the registration request message and / or RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards it to the selected AMF (S604).

[0242] The AMF receives a registration request message containing one or more of the first to fifth types of identification information. Here, the AMF, having received a registration request message from the UE containing one or more of the first to fifth types of identification information, may recognize and store what one or more of the first to fifth types of identification information included in the registration request message means.

[0243] Furthermore, the AMF may determine whether the UE is authorized to use the 5G ProSe L3 multihop communication service based on one or more of the first to fifth identification pieces received from the UE. Also, the AMF may authorize the UE to use the 5G ProSe L3 multihop communication service based on one or more of the first to fifth identification pieces received from the UE.

[0244] Furthermore, AMF may transmit one or more of the first to fifth identification pieces received from UE to PCF. Also, AMF may transmit one or more of the first to fifth identification pieces received from UE to PCF that are approved by the network or AMF.

[0245] When the AMF receives a registration request message, it can perform a first conditional determination. This first conditional determination determines whether the network (or the AMF) will accept the UE's request. If the first conditional determination is true, the AMF initiates the procedure shown in Figure 6(A); if the first conditional determination is false, it initiates the procedure shown in Figure 6(B).

[0246] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each piece of identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF, etc. For example, if the network permits the UE's request, the first condition determination is true, and if the network does not permit the UE's request, the first condition determination may be false. Also, if the network to which the UE is registered, and / or the devices within the network, support the function requested by the UE, the first condition determination is true, and if they do not support the function requested by the UE, the first condition determination may be false. Furthermore, if the transmitted and received identification information is permitted, the first condition determination is true, and if the transmitted and received identification information is not permitted, the first condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the first condition determination are not limited to those described above.

[0247] First, let's explain the case where the first condition is true.

[0248] In the procedure shown in Figure 6(A), AMF sends a Registration Accept message to the UE via the 5G AN (or gNB) as a response message to the Registration Request message (S608). The Registration Accept message is a NAS message sent and received on the N1 interface, but it is included in the RRC message when sent and received between the UE and the 5G AN (gNB).

[0249] Furthermore, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message based on the identification information received from the UE, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF. Here, the various identification information received by the AMF from the UE may be one or more of the first to fifth identification information included by the UE in the registration request message. In addition, the AMF may send a registration acceptance message to the UE if it accepts one or more of the first to fifth identification information provided by the UE.

[0250] In this case, if multiple pieces of identification information are sent and received between the UE and the network, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Furthermore, information indicating support for each function and information indicating a request to use each function may be sent and received with the same piece of identification information, or with different pieces of identification information.

[0251] Furthermore, AMF may select and decide whether or not to include identification information in the registration acceptance message based on the identification information received by AMF from the UE or each device, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by AMF.

[0252] Furthermore, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF.

[0253] Furthermore, the AMF may include information in the registration acceptance message indicating that some of the UE's requests have been rejected, or may indicate the reason why some of the UE's requests have been rejected by sending information indicating that some of the UE's requests have been rejected. Furthermore, the UE may become aware of the reason why some of its requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may also be information indicating that the content of the identification information received by the AMF is not permitted.

[0254] The UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S608). Upon receiving the registration acceptance message, the UE can recognize that its request in the registration request message has been accepted, and can also recognize the content of the various identification information contained in the registration acceptance message.

[0255] Furthermore, the UE can send a Registration Complete message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S610). Here, the registration complete message is a NAS message sent and received on the N1 interface, but it is included in the RRC message when sent and received between the UE and the 5G AN (gNB).

[0256] The AMF can receive a registration completion message via 5G AN(gNB) (S610). The UE and each device may also complete the procedure in Figure 6(A) or the registration procedure based on the sending and receiving of the registration acceptance message and / or registration completion message.

[0257] Next, we will explain the case where the first condition determination is false. In the procedure shown in Figure 6(B), the AMF sends a registration rejection message to the UE via the 5G AN(gNB) as a response message to the registration request message (S612). Here, the registration rejection message is a NAS message sent and received on the N1 interface, but it is included in the RRC message sent and received between the UE and the 5G AN(gNB).

[0258] Furthermore, the AMF may indicate that the UE's request has been rejected by sending a registration rejection message based on the identification information received from the UE, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF.

[0259] In this case, when multiple pieces of identification information are sent and received between the UE and the network, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Furthermore, information indicating support for each function and information indicating a request to use each function may be sent and received with the same piece of identification information, or they may be sent and received with different pieces of identification information.

[0260] Furthermore, AMF may select and decide whether or not to include identification information in the registration rejection message based on each piece of identification information received by AMF, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by AMF.

[0261] Furthermore, the AMF may indicate that the UE's request in the registration request message has been rejected by sending a registration rejection message. The AMF may also include information indicating the reason for the rejection in the registration rejection message, or may indicate the reason for the rejection by sending the reason for the rejection separately. Furthermore, the UE may recognize the reason for the rejection of its request by receiving information indicating the reason for the rejection of its request. The reason for the rejection may also be information indicating that the content of the identification information received by the AMF is not permitted.

[0262] The UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S612). Upon receiving the registration rejection message, the UE can recognize that its request via the registration request message has been rejected, and can also recognize the content of the various identification information contained in the registration rejection message. Furthermore, if the UE does not receive a registration rejection message after a predetermined period has elapsed since sending the registration request message, it may recognize that its request has been rejected. Each device completes procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0263] Furthermore, the procedure in Figure 6(B) may be initiated if the procedure in Figure 6(A) is discontinued.

[0264] Each device completes the registration procedure based on the completion of either procedure (A) or (B) in Figure 6. Furthermore, each device may transition to a state where the UE is registered with the network (RM-REGISTERED state) based on the completion of procedure (A) in Figure 6, or it may maintain a state where the UE is not registered with the network (RM-DEREGISTERED state) based on the completion of procedure (B) in Figure 6, or it may transition to a state where the UE is not registered with the network. Additionally, each device may transition to each state based on the completion of the registration procedure or based on the establishment of a PDU session.

[0265] Furthermore, the UE may complete the registration process based on the reception of a registration acceptance message or a registration rejection message from the network.

[0266] Furthermore, each device may perform processing based on the information sent and received during the registration process, upon completion of the registration procedure. For example, if it receives information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform the procedure again based on the reason why the UE's requests were rejected, or it may perform the registration procedure for core network_B or another cell.

[0267] Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message and / or registration rejection message, and may recognize the network's decision.

[0268] The UE may recognize the content of the above identification information by receiving a registration acceptance message or a registration rejection message.

[0269] Furthermore, the actions taken upon receiving each piece of identification information may be performed based on the received identification information.

[0270] [4.2. Network-requested UE policy management procedure] Next, the network-requested UE policy management procedure will be explained using Figure 7. Hereafter in this section, the network-requested UE policy management procedure will also be referred to as "this procedure." This procedure may be initiated by the network.

[0271] This procedure may be initiated upon completion of the registration procedure. Alternatively, this procedure may be initiated when the PCF decides to update the UE policy.

[0272] Next, we will explain each step of this procedure.

[0273] First, the PCF sends a manage UE policy command message to the UE via the AMF (S700).

[0274] At this point, the PCF may send a managed UE policy command message to the UE that includes the tenth identification information. Alternatively, the PCF may indicate to the UE what each identification information represents by sending the tenth identification information.

[0275] Furthermore, the PCF may select and / or decide whether or not to include the tenth identification information in the management UE policy command message, based on the status of the UE and / or information received from other NFs, etc.

[0276] Furthermore, the PCF may determine whether or not to send a management UE policy command message and / or identification information based on the status of the UE, and / or information received from the ProSe application server, and / or information received from other NFs.

[0277] More specifically, for example, the PCF may decide whether to include and send the 10th identifier in the managed UE policy command message based on what the UE has accepted from the network during the registration procedure. In other words, for example, during the registration procedure, the PCF may decide whether to include and send the 10th identifier in the managed UE policy command message, which corresponds to the content indicated by the first to fifth identifiers that the UE has included in the registration request message.

[0278] More specifically, for example, if, during the registration procedure, the UE requests from the network the content indicated by one or more of the first to fifth pieces of identification information, and this procedure is executed after the network has accepted the content indicated by said identification information, the PCF may send a management UE policy command to the UE that includes the tenth piece of identification information.

[0279] Specific examples of the content of the UE policy included in the 10th identification information that the UE receives from the network will be described in detail in each embodiment of Chapter 5.

[0280] Next, the UE receives a management UE policy command message from the PCF via the AMF. The UE may also receive a management UE policy command message from the PCF that includes a tenth identification piece.

[0281] Furthermore, based on the receipt of a management UE policy command message, the UE may store each piece of identification information received with the management UE policy command message, or recognize a network decision. The UE may also recognize the content of the identification information received with the management UE policy command message.

[0282] More specifically, for example, if the UE receives a 10th piece of identification information, it may recognize and remember that it is the ProSeP corresponding to the identification information requested by the UE in the registration request message.

[0283] Next, when the UE receives a management UE policy command message, it can perform a third conditional determination. This third conditional determination determines whether the UE will accept the network request. If the third conditional determination is true, the UE initiates the procedure shown in Figure 7(A); if the third conditional determination is false, it initiates the procedure shown in Figure 7(B).

[0284] Furthermore, the third condition determination may be performed based on the reception of a management UE policy command message, and / or the identification information contained in the management UE policy command message, and / or subscriber information, and / or UE capability information, and / or UE policy, and / or the state of the UE, and / or the context held by the UE, etc. For example, if the UE permits the network request, the third condition determination may be true, and if the UE does not permit the network request, the third condition determination may be false. Also, if the UE supports the functionality requested by the network, the third condition determination may be true, and if the UE does not support the functionality requested by the network, the third condition determination may be false. In addition, if the transmitted and received identification information is permitted, the third condition determination may be true, and if the transmitted and received identification information is not permitted, the third condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the third condition determination are not limited to those described above.

[0285] First, let's explain the case where the third condition is true.

[0286] In the procedure shown in Figure 7(A), the UE sends a "manage UE policy complete" message to the PCF via the 5G AN (or gNB) and / or AMF as a response message to the managed UE policy command message (S702).

[0287] Next, PCF receives a management UE policy completion message from the UE via AMF.

[0288] Furthermore, based on the receipt of the managed UE policy completion message, the PCF may store the identification information received along with the managed UE policy completion message, or recognize the UE's decision. The PCF may also recognize the content of the identification information received along with the managed UE policy completion message.

[0289] Furthermore, the above PCF behavior may be performed after receiving the management UE policy completion message.

[0290] Furthermore, when PCF receives a Management UE policy completion message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the Management UE policy completion message.

[0291] Furthermore, the PCF may forward each piece of received identification information to another NF (e.g., a ProSe application server).

[0292] Each device may complete the procedure in Figure 7(A) based on the sending and receiving of a management UE policy command message and / or a management UE policy completion message.

[0293] Next, we will explain the case where the third condition is false.

[0294] In the procedure shown in Figure 7(B), the UE sends a manage UE policy command reject message to the PCF via the 5G AN (or gNB) and / or AMF as a response message to the managed UE policy command message (S704).

[0295] Next, PCF receives a management UE policy command rejection message from the UE via AMF.

[0296] Furthermore, based on the receipt of a managed UE policy command rejection message, the PCF may store the identification information received along with the managed UE policy command rejection message, or recognize the UE's decision. The PCF may also recognize the content of the identification information received along with the managed UE policy command rejection message.

[0297] Furthermore, the above PCF behavior may be performed after receiving a management UE policy command rejection message.

[0298] Furthermore, if PCF receives a management UE policy command rejection message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the management UE policy command rejection message.

[0299] Furthermore, the PCF may forward each piece of received identification information to another NF (e.g., a ProSe application server).

[0300] Each device may complete the procedure in Figure 7(B) based on the sending and receiving of a managed UE policy command message and / or a managed UE policy command rejection message.

[0301] Furthermore, each device may complete the network request UE policy management procedure based on the completion of the above-described process and / or the sending and receiving of a management UE policy command message and / or the sending and receiving of a management UE policy completion message and / or the sending and receiving of a management UE policy command rejection message.

[0302] Furthermore, each device may perform processing based on the identification information transmitted and received during this procedure, upon completion of this procedure.

[0303] Furthermore, based on the completion of the network request UE policy management procedure, the UE may add new UE policies, modify existing UE policies, or delete existing UE policies.

[0304] [4.3. UE-requested ProSeP provisioning procedure] Next, the UE-requested ProSeP provisioning procedure will be explained using Figure 8. Hereafter, the UE-requested ProSeP provisioning procedure will also be referred to as this procedure. This procedure may be led by the UE.

[0305] Furthermore, this procedure may be initiated upon or in conjunction with the completion of the registration procedure. It may also be initiated when the UE requests a UE policy or ProSe policy. Furthermore, this procedure may be a UE policy provisioning procedure.

[0306] Furthermore, this procedure may also be performed to update a ProSeP upon the expiration of a timer indicating each validity period, which is set for each ProSeP indicated by the tenth identification information, either set in the UE or stored by the UE.

[0307] Next, we will explain each step of this procedure.

[0308] First, the UE sends a UE policy provisioning request message (S800) to the PCF via the AMF.

[0309] Next, PCF receives a UE policy provision request message from UE via AMF.

[0310] Furthermore, based on the receipt of the UE policy request message, the PCF may store the identification information received along with the UE policy request message, or recognize the network decision. The PCF may also recognize the content of the identification information received along with the UE policy request message.

[0311] Furthermore, the above PCF behavior may be performed after receiving the UE policy command message.

[0312] Furthermore, when PCF receives a UE policy provision request message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the UE policy provision request message.

[0313] When the PCF receives a UE policy provision request message, it can perform a fourth condition determination. The fourth condition determination determines whether the network will accept the UE's request. If the fourth condition determination is true, the PCF initiates the procedure shown in Figure 8(A); if the fourth condition determination is false, it initiates the procedure shown in Figure 8(B).

[0314] Furthermore, the fourth condition determination may be performed based on the receipt of the UE policy provision request message, and / or each piece of identification information contained in the UE policy provision request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the PCF, etc. For example, if the network permits the UE's request, the fourth condition determination may be true, and if the network does not permit the UE's request, the fourth condition determination may be false. Also, if the network to which the UE is registered, and / or the devices within the network, support the function requested by the UE, the fourth condition determination may be true, and if they do not support the function requested by the UE, the fourth condition determination may be false. Furthermore, if the transmitted and received identification information is permitted, the fourth condition determination may be true, and if the transmitted and received identification information is not permitted, the fourth condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the fourth condition determination are not limited to those described above.

[0315] First, let's explain the case where the fourth condition is true.

[0316] The PCF may perform the network request policy management procedure in the procedure shown in Figure 8(A) (S802). Here, the network request policy management procedure may be the procedure described in the network request UE policy management procedure in Chapter 4.2 (Chapter 4.2) above.

[0317] Each device may complete the procedure in Figure 8(A) based on the sending and receiving of UE policy provision request messages and / or the completion of the network request policy management procedure. In the procedure in Figure 8(A), i.e., the network request policy management procedure, the UE policy received by the UE from the network may be the 10th identification information. Specific examples of the content of the 10th identification information received by the UE from the network will be described in detail in each embodiment of Chapter 5.

[0318] Next, we will explain the case where the fourth condition is false.

[0319] In the procedure shown in Figure 8(B), the PCF sends a UE policy provisioning rejection message to the UE via the 5G AN (or gNB) and / or AMF as a response message to the UE policy provisioning request message (S804).

[0320] Furthermore, the PCF may determine whether or not to send a UE policy refusal message and / or each piece of identification information based on the UE status and / or information received from the ProSe application server and / or information received from other NFs.

[0321] Next, the UE receives a UE policy provision refusal message from the PCF via the AMF.

[0322] Furthermore, based on the receipt of a UE policy denial message, the UE may store the identification information received along with the UE policy denial message, or recognize the network decision. The UE may also recognize the content of the identification information received along with the UE policy denial message.

[0323] Furthermore, the above UE behavior may be performed after receiving a UE policy provision denial message.

[0324] Furthermore, if the UE receives a UE policy refusal message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the UE policy refusal message.

[0325] Each device may complete the procedure in Figure 8(B) based on the sending and receiving of UE policy provision request messages and / or UE policy provision denial messages.

[0326] Furthermore, each device may complete this procedure based on the completion of the above-described process and / or the sending and receiving of UE policy provision request messages and / or the completion of the network request policy management procedure and / or the sending and receiving of UE policy provision refusal messages.

[0327] Furthermore, each device may perform processing based on the identification information transmitted and received during this procedure, upon completion of this procedure.

[0328] Furthermore, upon completion of this procedure, UE may add new UE policies, modify existing UE policies, or delete existing UE policies.

[0329] [5. Embodiments] Next, each embodiment in this embodiment will be described. The embodiments described in this chapter are based on the definitions of terms and various identification information explained in Chapter 3, and the procedures explained in Chapter 4. Furthermore, in this chapter, each embodiment described will be referred to as the embodiment of this chapter, or simply as each embodiment.

[0330] Furthermore, each embodiment in this chapter may include, in the registration procedure described in Chapter 4.1, the UE sending a registration request message to the network that includes UE capability information regarding the UE's support for 5GProSe multihop functionality, by including one or more of the first to fifth identification information in the registration request message. Moreover, each embodiment in this chapter may complete the registration procedure if the network accepts and completes the registration request that includes the UE capability information provided by the UE.

[0331] Furthermore, each embodiment in this chapter may be an embodiment in which a policy corresponding to the UE capability information accepted in the registration procedure is provided by the UE policy provisioning procedure in Chapters 4.2 and 4.3. Here, the UE capability information accepted in the registration procedure may be the UE capability information indicated by one or more of the first to fifth identification information, and may be the 5G ProSe multi-hop function and / or the 5G ProSe (single-hop) function supported by the UE.

[0332] Furthermore, unless otherwise specified, each embodiment described in each section of this chapter may be performed individually and independently, or one or more of the procedures of the embodiments described in each section may be performed in combination, or one or more of the procedures of the embodiments described in each section may be performed in any order.

[0333] The following describes each embodiment.

[0334] [5.1. First Embodiment] The first embodiment in this embodiment will be described below. Hereinafter, in this section, the first embodiment will also be referred to as this embodiment.

[0335] This embodiment relates to the content of the identification information indicating the capabilities of the UE to be included in the registration request message that the UE sends to the network during the registration procedure (Chapter 4.1), and to the provision of ProSeP after the registration request is accepted and the registration procedure is completed (Chapters 4.2 and 4.3).

[0336] Furthermore, this embodiment may be one in which the UE capability is indicated by one or more of the first to third identification information. In other words, the UE of this embodiment may indicate its UE capability by one or more of the first to third identification information.

[0337] In this embodiment, the UE may, during the registration procedure, include one or more of the first to third identification pieces in a registration request message and transmit it to the network. Subsequently, the AMF, upon receiving the registration request message containing one or more of the first to third identification pieces transmitted by the UE, may recognize and / or store the UE capability information indicated by the received identification pieces. Furthermore, the AMF may accept the content requested by one or more of the first to third identification pieces received from the UE and transmit a registration acceptance message to the UE. The AMF may further transmit to the PCF the content indicated by one or more of the first to third identification pieces, i.e., information indicating the UE's support for 5G ProSe multi-hop functionality.

[0338] The UE of this embodiment, having completed the registration procedure, may receive a 10th identification information from the network during the UE policy provisioning procedure, which is a UE policy corresponding to the content indicated by one or more of the first to third identification information, i.e., information indicating the UE's support for the 5G ProSe multi-hop function. Here, the UE may receive the 10th identification information indicating the UE policy from the PCF via the AMF.

[0339] More specifically, for example, a UE capability indicating that a UE supports operating as a 5G ProSe Layer-3 multi-hop UE-to-Network Relay UE may be indicated by a combination of a first identifier indicating support for 5G ProSe Layer-3 UE-to-Network Relay and a second identifier.

[0340] Furthermore, for example, a UE's ability to support operating as a 5G ProSe multi-hop layer-2 remote UE may be indicated by a combination of a first identifier indicating support for operating as a 5G ProSe Layer-3 Remote UE and a second identifier.

[0341] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay UE may be indicated in a third identification.

[0342] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE may be indicated by a combination of a first identifier indicating support for operating as a 5G ProSe Layer-3 UE-to-UE Relay UE and a second identifier.

[0343] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 end UE may be indicated by a combination of a first identifier indicating support for operating as a 5G ProSe Layer-3 End UE and a second identifier.

[0344] Based on the above, for example, if the UE of this embodiment supports 5G ProSe multi-hop L3 (Layer-3) UE-to-UE (U2U) relay and 5G ProSe L3 intermediate relay UE, it may include a first identification information, a second identification information, and a third identification information in the registration request message and send the registration request message to the network.

[0345] Here, the first identification information may be information indicating that the UE supports the 5G ProSe multi-hop relay function, or information indicating that the UE supports operating as a 5G ProSe multi-hop relay UE. The second identification information may be information indicating that the UE supports the 5G ProSe L3 U2U relay, or information indicating that the UE supports operating as a 5G ProSe L3 U2U relay UE. The third identification information may be information indicating that the UE supports the 5G ProSe L3 intermediate relay, or information indicating that the UE supports operating as a 5G ProSe L3 intermediate relay UE.

[0346] Subsequently, the network or AMF may accept a registration request message from the UE containing the first, second, and third identification information, and the registration procedure may be completed.

[0347] After the registration procedure is completed, the UE may receive UE policies for the 5G ProSe multi-hop L3 U2U relay UE and policies for the 5G ProSe L3 intermediate relay from the network or from the PCF via the AMF during the UE policy provisioning procedure, corresponding to the content indicated by the combination of the first, second, and third identification information. In other words, after the registration procedure is completed, the UE may receive a management UE policy command message from the network, which includes a ProSe policy. Here, the ProSe policy may include a UE policy for the 5G ProSe multi-hop L3 U2U relay UE and a UE policy for the 5G ProSe L3 intermediate relay.

[0348] Furthermore, after the registration procedure is completed, the UE may store the UE policy for the 5G ProSe multi-hop L3 U2U relay UE and the policy for the 5G ProSe L3 intermediate relay UE, which were received from the network or from the PCF via the AMF, in a storage unit within the UE or in the USIM (User Service Identity Module).

[0349] [5.2. Second Embodiment] A second embodiment of this embodiment will be described below. In this section, the second embodiment will also be referred to as this embodiment.

[0350] This embodiment relates to the content of the identification information indicating the capabilities of the UE to be included in the registration request message that the UE sends to the network during the registration procedure (Chapter 4.1), and to the provision of ProSeP after the registration request is accepted and the registration procedure is completed (Chapters 4.2 and 4.3).

[0351] Furthermore, this embodiment may be one in which the UE capability is indicated by one or more of the fourth to fifth identification information. In other words, the UE of this embodiment may indicate its UE capability by one or more of the fourth to fifth identification information.

[0352] In this embodiment, the UE may, during the registration procedure, include one or more of the fourth to fifth identification pieces in a registration request message and transmit it to the network. Subsequently, the AMF, upon receiving the registration request message containing one or more of the fourth to fifth identification pieces transmitted by the UE, may recognize and / or store the UE capability information indicated by the received identification pieces. Furthermore, the AMF may accept the content requested by one or more of the fourth to fifth identification pieces received from the UE and transmit a registration acceptance message to the UE. The AMF may further transmit to the PCF the content indicated by one or more of the fourth to fifth identification pieces, i.e., information indicating the UE's support for 5G ProSe multi-hop functionality.

[0353] A UE of this embodiment that has completed the registration procedure may receive a 10th identification information from the network in the UE policy provisioning procedure, which is a UE policy corresponding to the content indicated by one or more of the fourth to fifth identification information, i.e., information indicating the UE's support for the 5G ProSe multi-hop function. Here, the UE may receive the 10th identification information indicating the UE policy from the PCF via the AMF. More specifically, for example, the UE capability indicating that the UE supports operating as a 5G ProSe Layer-3 multi-hop UE-to-Network Relay UE may be indicated by a combination of the fourth identification information indicating that it includes the fifth identification information, and the fifth identification information indicating that it supports operating as a 5G ProSe Layer-3 multi-hop UE-to-Network Relay UE.

[0354] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-2 remote UE may be indicated by a combination of a fourth identification information indicating that it includes a fifth identification information, and a fifth identification information indicating that it supports operating as a 5G ProSe multi-hop layer-2 remote UE.

[0355] Furthermore, for example, UE capability indicating that a UE supports 5G ProSe Layer-3 Intermediate UE-to-Network Relay may be indicated by a combination of a fourth identifier indicating that it includes a fifth identifier, and a fifth identifier indicating that it supports 5G ProSe Layer-3 Intermediate UE-to-Network Relay.

[0356] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE may be indicated by a combination of a fourth identification information indicating that it includes a fifth identification information, and a fifth identification information indicating that it supports operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE.

[0357] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 end UE may be indicated by a combination of a fourth identification information indicating that it includes a fifth identification information, and a fifth identification information indicating that it supports operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE.

[0358] Based on the above, for example, if the UE of this embodiment supports 5G ProSe multi-hop L3 (Layer-3) UE-to-UE (U2U) relay, it may include the fourth and fifth identification information in the registration request message and send the registration request message to the network.

[0359] Here, the fourth identification information may be information indicating whether or not the fifth identification information is included. The fifth identification information may also be information indicating that the UE supports 5G ProSe multi-hop L3 U2U relay.

[0360] Subsequently, the network or AMF may accept a registration request message from the UE containing the fourth and fifth identification information, and the registration procedure may be completed.

[0361] After the registration procedure is completed, the UE may receive a UE policy for the 5G ProSe multi-hop L3 U2U relay UE, corresponding to the content indicated by the combination of the fourth and fifth identification information, from the network or from the PCF via the AMF during the UE policy provisioning procedure. In other words, after the registration procedure is completed, the UE may receive a management UE policy command message from the network, which includes a ProSe policy, where the ProSe policy may include a UE policy for the 5G ProSe multi-hop L3 U2U relay UE.

[0362] Furthermore, the UE may store UE policies for the 5G ProSe multi-hop L3 U2U relay UE, received from the network or from the PCF via the AMF, in a memory unit within the UE or in the USIM (User Service Identity Module).

[0363] [5.3. Third Embodiment] A third embodiment of this embodiment will be described below. In this section, the third embodiment will also be referred to as this embodiment.

[0364] This embodiment relates to the content of the identification information indicating the capabilities of the UE to be included in the registration request message that the UE sends to the network during the registration procedure (Chapter 4.1), and to the provision of ProSeP after the registration request is accepted and the registration procedure is completed (Chapters 4.2 and 4.3).

[0365] Furthermore, this embodiment may be one in which the UE capability is indicated by the fifth identification information. In other words, the UE of this embodiment may indicate its UE capability by the fifth identification information.

[0366] In this embodiment, the UE may, during the registration procedure, include the fifth identification information in the registration request message and transmit it to the network. Subsequently, the AMF, upon receiving the registration request message containing the fifth identification information transmitted by the UE, may recognize and / or store the UE capability information indicated by the received identification information. Furthermore, the AMF may accept the content requested by the fifth identification information received from the UE and send a registration acceptance message to the UE. The AMF may further transmit to the PCF the content indicated by the fifth identification information, namely, information indicating the UE's support for 5G ProSe multi-hop functionality.

[0367] The UE of this embodiment, having completed the registration procedure, may receive a tenth identification information from the network during the UE policy provisioning procedure, which is a UE policy corresponding to the content indicated by the fifth identification information, i.e., information indicating the UE's support for the 5G ProSe multi-hop function. Here, the UE may receive the tenth identification information indicating the UE policy from the PCF via the AMF.

[0368] More specifically, for example, UE capability indicating that a UE supports operating as a 5G ProSe Layer-3 multi-hop UE-to-Network Relay UE may be indicated by a fifth identification indicating support for operating as a 5G ProSe Layer-3 multi-hop UE-to-Network Relay UE.

[0369] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-2 remote UE may be indicated by a fifth identification indicating support for operating as a 5G ProSe multi-hop layer-2 remote UE.

[0370] Furthermore, for example, UE capability indicating that a UE supports 5G ProSe Layer-3 Intermediate UE-to-Network Relay may be indicated by a fifth identifier indicating support for 5G ProSe Layer-3 Intermediate UE-to-Network Relay.

[0371] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE may be indicated by a fifth identification indicating support for operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE.

[0372] Furthermore, for example, UE capability indicating that a UE supports operating as a 5G ProSe multi-hop layer-3 end UE may be indicated by a fifth identification indicating support for operating as a 5G ProSe multi-hop layer-3 UE-to-UE relay UE.

[0373] Based on the above, for example, if the UE of this embodiment supports 5G ProSe multi-hop L3 (Layer-3) UE-to-UE (U2U) relay, it may include a fifth identification information in the registration request message and send the registration request message to the network.

[0374] Here, the fifth piece of identification information may be information indicating that the UE supports 5G ProSe multi-hop L3 U2U relay.

[0375] Subsequently, the network or AMF may accept a registration request message from the UE containing the fifth identification information, and the registration procedure may be completed.

[0376] After the registration procedure is completed, the UE may receive a UE policy for the 5G ProSe multi-hop L3 U2U relay UE corresponding to the content indicated by the fifth identification information, from the network or from the PCF via the AMF during the UE policy provisioning procedure. In other words, after the registration procedure is completed, the UE may receive a management UE policy command message from the network, which includes a ProSe policy, where the ProSe policy may include a UE policy for the 5G ProSe multi-hop L3 U2U relay UE.

[0377] Furthermore, the UE may store UE policies for the 5G ProSe multi-hop L3 U2U relay UE, received from the network or from the PCF via the AMF, in a memory unit within the UE or in the USIM (User Service Identity Module).

[0378] [5.4. Fourth Embodiment] The fourth embodiment of this embodiment will be described below. In this section, the fourth embodiment will also be referred to as this embodiment.

[0379] This embodiment relates to the content of the identification information indicating the capabilities of the UE to be included in the registration request message that the UE sends to the network during the registration procedure (Chapter 4.1), and to the provision of ProSeP after the registration request is accepted and the registration procedure is completed (Chapters 4.2 and 4.3).

[0380] Furthermore, this embodiment may be one in which the UE capability is indicated by the second or fourth identification information. More specifically, for example, a UE may indicate to the network that it supports or does not support operating as a "5G ProSe Layer-3 UE-to-Network Relay", and / or "5G ProSe Layer-3 Remote UE", and / or "5G ProSe Layer-2 UE-to-UE Relay", and / or "5G ProSe Layer-3 UE-to-UE Relay", and / or "5G ProSe Layer-3 End UE", and / or "5G ProSe Layer-3 multi-hop UE-to-Network Relay", and / or "5G ProSe Layer-3 multi-hop Remote UE", and / or "5G ProSe Layer-2 multi-hop UE-to-UE Relay", and / or "5G ProSe Layer-3 multi-hop UE-to-UE Relay", and / or "5G ProSe multi-hop Layer-3 End UE" by including a second or fourth identifier in the registration request message.

[0381] Alternatively, this embodiment may be one in which the UE capability is indicated by the first and second identification information. More specifically, for example, a UE may indicate that it supports or does not support "5G ProSe Layer-3 multi-hop UE-to-Network Relay", "5G ProSe Layer-3 multi-hop Remote UE", "5G ProSe Layer-2 UE-to-UE Relay", "5G ProSe Layer-3 UE-to-UE Relay", and / or "5G ProSe Layer-3 End UE" by including a first and second identifier in the registration request message.

[0382] Alternatively, this embodiment may be one in which the UE capability is indicated by the first and fourth identification information. More specifically, for example, a UE may indicate that it supports or does not support "5G ProSe Layer-3 multi-hop UE-to-Network Relay", "5G ProSe Layer-3 multi-hop Remote UE", "5G ProSe Layer-2 UE-to-UE Relay", "5G ProSe Layer-3 UE-to-UE Relay", and / or "5G ProSe Layer-3 End UE" by including the first and fourth identification information in the registration request message.

[0383] [6. Modifications] A program that operates in a device according to one aspect of this embodiment may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the embodiment according to one aspect of this embodiment. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage system.

[0384] Furthermore, a program for realizing the functions of one embodiment relating to this embodiment may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0385] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuits may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of this embodiment may use new integrated circuits based on such technologies.

[0386] It should be noted that this embodiment is not limited to the embodiments described above. Although one example of a device is described in this embodiment, this embodiment is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household equipment.

[0387] Although embodiments of this embodiment have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of this embodiment are also included. Furthermore, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

[0388] This embodiment can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0389] 1 Mobile Communication System 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. User Equipment (UE) comprising a transmitting and receiving unit, wherein the UE supports operation as a 5G ProSe multi-hop L3 (Layer-3) UE-to-UE (U2U) relay UE, the transmitting and receiving unit transmits the registration request message to the network, including first information and second information in the registration request message, wherein the first information is information indicating that the UE supports the 5G ProSe multi-hop relay communication function, and the second information is information indicating that the UE supports operation as a 5G ProSe L3 U2U relay UE.

2. The UE further comprises a control unit and a storage unit, the transmitting / receiving unit receives a UE policy from the network corresponding to the content indicated by the combination of the first information and the second information, and the control unit stores the UE policy in the storage unit, the UE according to claim 1.

Images