Paging a remote UE using a relay

Abstract

The method, system and device disclosed in the present invention can solve the problem of sending a paging message to a remote UE that is more than one hop away from a base station.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 950,256, filed on December 19, 2019, entitled “Methods and Apparatus For Paging Remote UE,” the contents of which are hereby incorporated by reference into this document. Background Art

[0003] Discontinuous Reception of Paging

[0004] The UE may use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The UE monitors one paging occasion (PO) in each DRX cycle. A PO is a set of PDCCH monitoring occasions and may consist of multiple time slots (e.g., subframes or OFDM symbols) in which paging DCI may be sent, 3GPP TS 38.213, Physical Layer Control Procedure (Release 15), V15.7.0 ([1]). A paging frame (PF) is a radio frame and may contain one or more POs or the start of a PO.

[0005] In multi-beam operation, the UE assumes that the same paging message and the same short message are repeated in all transmit beams, and therefore the selection of beams for receiving paging messages and short messages depends on the UE specific implementation. The paging message is the same for RAN initiated paging and CN initiated paging.

[0006] The UE initiates the RRC connection recovery procedure when receiving a RAN initiated paging. If the UE receives a CN initiated paging in the RRC_INACTIVE state, the UE moves to RRC_IDLE and notifies the NAS.

[0007] PF and PO are determined by the following formula:

[0008] The SFN of a PF is determined by:

[0009] (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N)

[0010] Index(i_s), indicating that the index of the PO is determined by:

[0011] i_s=floor(UE_ID / N)mod Ns

[0012] The PDCCH monitoring occasion for paging is determined according to the pagingSearchSpace as specified in [1] and the firstPDCCH-MonitoringOccasionOfPO (if configured) as specified in [1].When SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring occasion for paging is the same as the RMSI as defined in clause 13 of [1].

[0013] When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO in PF starting from the first PDCCH monitoring occasion of paging. For Ns=2, the PO is located in the first half frame (i_s=0) or the second half frame (i_s=1) of PF.

[0014] When the SearchSpaceId configured for pagingSearchSpace is non-zero, the UE monitors the (i_s+1)th PO. A PO is a set of "S" consecutive PDCCH monitoring opportunities, where "S" is the number of SSBs actually transmitted determined according to ssb-PositionsInBurst in SIB1. The Kth PDCCH monitoring opportunity for paging in the PO corresponds to the Kth SSB transmitted. The PDCCH monitoring opportunities for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially in the PF starting from zero starting from the first PDCCH monitoring opportunity for paging. When firstPDCCH-MonitoringOccasionOfPO exists, the starting PDCCH monitoring opportunity number of the (i_s+1)th PO is the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S.

[0015] NOTE 1: A PO associated with a PF can start either in the PF or after the PF.

[0016] Note 2: The PDCCH monitoring occasions of PO can span multiple radio frames. When SearchSpaceId is configured as non-zero for pagingSearchSpace, the PDCCH monitoring occasions of PO can span multiple periods of the paging search space.

[0017] The following parameters are used to calculate the above PF and i_s:

[0018] T: DRX cycle of the UE (T is determined by the shortest value of the UE-specific DRX value (if configured by RRC and upper layers) and the default DRX value broadcast in the system information. If UE-specific DRX is not configured by RRC or not configured by upper layers, the default value applies).

[0019] N: total number of paging frames in T

[0020] Ns: Number of paging occasions of PF

[0021] PF_offset: offset used for PF determination

[0022] UE_ID: 5G-S-TMSI mod 1024

[0023] The parameters Ns, nAndPagingFrameOffset and the length of the default DRX cycle are signaled in SIB1. The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in 3GPP TS 38.331, Radio Resource Control (RRC) Protocol Specification (Release 15), V15.7.0 ([2]). The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0024] If the UE does not have a 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE shall use the default identity UE_ID=0 in the above PF and i_s formulas.

[0025] The 5G-S-TMSI is a 48-bit string as defined in 3GPP TS 23.501, System Architecture for 5G Systems, Stage 2 (Release 15), V15.6.0 ([3]). The 5G-S-TMSI should be interpreted as a binary number in the above formula, where the leftmost bit represents the most significant bit.

[0026] Layer 2 Evolved UE to Network Relay Solution

[0027] Architecture

[0028] For the protocol architecture of the user plane and the control plane, relaying is performed above the RLC sublayer. The user plane data and control plane data of the evolved ProSe remote UE are relayed from the evolved ProSe remote UE to the network via the evolved ProSe UE to the network relay UE and vice versa above the RLC. The Uu PDCP and RRC are terminated between the evolved ProSe remote UE and the eNB, while the RLC, MAC and PHY and non-3GPP transport layers are terminated in each link (i.e., the link between the evolved ProSe remote UE and the evolved ProSe UE to the network relay UE, and the link between the evolved ProSe UE to the network relay UE and the eNB). Figure 1 and Figure 2 ] shows the user plane protocol stack and the control plane protocol stack when PC5 is used between an evolved ProSe remote UE and an evolved ProSe UE to a network relay UE.

[0029] Paging for Evolved ProSe Remote UE

[0030] It is assumed that an evolved ProSe Remote UE shall be linked with an evolved ProSe UE to Network Relay UE in order to receive paging via the evolved ProSe UE to Network Relay UE. The evolved ProSe Remote UE supports receiving paging through the linked evolved ProSe UE to Network Relay UE when the evolved ProSe Remote UE is within E-UTRAN coverage and outside of coverage. The evolved ProSe UE to Network Relay UE supports forwarding paging for evolved ProSe Remote UEs located within and outside of E-UTRAN coverage. There are multiple possible paging options with which an evolved ProSe Remote UE in RRC_IDLE can be reached on the downlink when it is within E-UTRAN coverage or outside of coverage, as shown below.

[0031] Option 1: The evolved ProSe UE to network relay UE monitors the PO of the evolved ProSe remote UE to which it is linked in addition to its own PO. When linked to the evolved ProSe UE to network relay UE, the evolved ProSe remote UE does not need to attempt to receive paging over the downlink. The evolved ProSe UE to network relay UE may need to monitor multiple paging occasions. The evolved ProSe UE to network relay UE must be aware of the paging occasions of the evolved ProSe remote UE and must decode the paging message and determine the evolved ProSe remote UE to which the paging is directed. Furthermore, the evolved ProSe UE to network relay UE may need to relay the paging of the evolved ProSe remote UE over a short range link. This option is not recommended in the future. Figure 3 Shown in.

[0032] Option 2: The evolved ProSe UE to network relay UE only monitors its own PO, and paging for the linked evolved ProSe remote UE is also sent in the PO of the evolved ProSe UE to network relay UE. When linked to the evolved ProSe UE to network relay UE, the evolved ProSe remote UE does not need to attempt to receive paging over the downlink. The evolved ProSe UE to network relay UE must decode the paging message, determine the evolved ProSe remote UE to which the paging is targeted, and needs to relay the paging of the evolved ProSe remote UE over a short-range link. In order to page the evolved ProSe remote UE, the core network (i.e., MME) is required to understand the link status between the evolved ProSe UE to network relay UE and the evolved ProSe remote UE, and when the evolved ProSe remote UE is linked, remap the paging message of the evolved ProSe remote UE to appear on the PO of the evolved ProSe UE to network relay UE. This option is Figure 4 Shown in.

[0033] This background information is provided for the purpose of revealing information believed by the applicant to be of possible relevance. It is not necessary to admit, nor should it be construed, that any of the foregoing information constitutes prior art. Summary of the invention

[0034] This document discloses subject matter that can solve the problem of sending paging messages to remote UEs that are more than one hop away from a base station. Specifically, the following subject matter is disclosed.

[0035] A relay UE election method is disclosed, which is used to enable or disable a relay function of a UE with relay capability to act as a UE-to-network relay or a UE-to-UE relay for paging messages.

[0036] A paging path establishment method is disclosed, which is used to establish a path between a remote UE and the gNB before the gNB sends a paging message to the remote UE. A paging path discovery process is disclosed, which is used by the gNB to discover multiple candidate paging paths between the remote UE and the gNB. A paging path configuration process is disclosed, which is used by the gNB to select and configure the adaptation layer of the UE-to-network relay and zero or more UE-to-UE relays that forward paging along the paging path. A selection-based paging path establishment method is also disclosed, that is, the remote UE establishes the paging path of the remote UE along the paging path of the relay UE by configuring the adaptation layer of the UE-to-UE relay and the UE-to-network relay located on the paging path.

[0037] A paging propagation method is disclosed for propagating a paging message from a gNB to a remote UE via an established paging path. In a first disclosed method, a UE-to-network relay UE monitors the PO of the remote UE in addition to its own PO. In a second disclosed method, a UE-to-network relay monitors only its own PO, and paging for the remote UE is also sent in the PO of the UE-to-network relay UE.

[0038] A paging path maintenance method is disclosed, which is used for a remote UE, a UE-to-UE relay, or a UE-to-network relay in a network to dynamically maintain a paging path between a remote UE and a gNB when the topology changes. In a first disclosed method, the remote UE may select a new relay UE and establish a new paging path to the gNB. In a second disclosed method, one or more relay UEs on the paging path of the remote UE may select a new relay UE and establish a new paging path to the gNB.

[0039] A UE reachability management method is disclosed, which is used for a remote UE to maintain a paging path by periodically sending a path update message.

[0040] The purpose of providing this summary is to introduce selected concepts in a simplified form, which are further described in the following detailed description. This summary is neither intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. In addition, the claimed subject matter is not limited to limitations that address any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which:

[0042] Figure 1 An exemplary user plane radio protocol stack for Layer 2 Evolved UE to Network Relay (PC5) is shown;

[0043] Figure 2 An exemplary control plane radio protocol stack for Layer 2 Evolved UE to Network Relay (PC5) is shown;

[0044] Figure 3 Exemplary paging for an Evolved ProSe Remote UE (option 1) is shown;

[0045] Figure 4 Exemplary paging for Evolved ProSe Remote UE (option 2) is shown;

[0046] Figure 5An exemplary control plane radio protocol stack for layer 2 UE-to-network relay (PC5) and UE-to-UE relay (PC5) is shown;

[0047] Figure 6 An exemplary user plane radio protocol stack for layer 2 UE-to-network relay (PC5) and UE-to-UE relay (PC5) is shown;

[0048] Figure 7 An exemplary relay UE election and configuration by a gNB is shown;

[0049] Figure 8 An exemplary paging path discovery process is shown;

[0050] Fig. 9 An exemplary end-to-end paging path configuration is shown;

[0051] Fig.10 An exemplary hop-by-hop paging path configuration is shown;

[0052] Fig.11 An exemplary paging path is shown to be established through existing paging;

[0053] Fig.12 shows an exemplary paging propagation process when a UE-to-network relay UE monitors the remote UE's PO in addition to its own PO;

[0054] Fig.13 An exemplary paging propagation process is shown when a UE-to-network relay monitors only its own PO and pages for remote UEs are also sent in the PO of the UE-to-network relay UE;

[0055] Fig.14 An exemplary paging path establishment process for a remote UE to reselect a new relay UE is shown;

[0056] Fig.15 An exemplary paging path establishment process is shown when a relay UE reselects a new relay UE;

[0057] Fig.16 An exemplary paging path update for remote UE reachability management is shown;

[0058] Fig.17 An exemplary paging method is shown;

[0059] Fig.18 An exemplary display (e.g., a graphical user interface) that may be generated based on the methods, systems, and apparatus for paging a remote UE is shown;

[0060] Fig.19A An exemplary communication system is shown;

[0061] Fig.19B An exemplary system including a RAN and a core network is shown;

[0062] Fig.19C An exemplary system including a RAN and a core network is shown;

[0063] Fig.19C An exemplary system including a RAN and a core network is shown;

[0064] Fig.19E Another exemplary communication system is shown;

[0065] Fig.19F is a block diagram of an exemplary apparatus or device, such as a WTRU; and

[0066] Figure 19G is a block diagram of an exemplary computing system. DETAILED DESCRIPTION

[0067] In LTE and NR, when the UE is in RRC_Idle, the granularity of the UE's location context is in the "tracking area", and when the UE is in RRC_Inactive, the granularity of the UE's location context is in the "RAN notification area". In order to send paging to the UE, the gNB within the TA and RNA broadcasts the paging to all UEs in the area. However, in the case where there are multiple relays in the area, broadcasting paging through relay UEs will cause the paging message to be flooded in the area, thereby introducing huge overhead. Therefore, one or more paging paths need to be established to propagate the paging message from the gNB to the remote UE. The first set of problems that need to be solved is how to establish one or more paging paths between the gNB and the remote UE.

[0068] Problem 1 - Relay UE election for relaying paging: In a network, some UEs support a relay function for relaying paging messages, while some UEs do not support the relay function, for example, due to their hardware and software capabilities. However, for UEs supporting the relay function, the relay function may not be enabled or elected to relay paging messages due to UE conditions or network conditions. How is the relay function of a UE with relay capability enabled to act as a relay for paging messages?

[0069] Problem 2 - Remote UE selection of relay UE for paging reception: If the remote UE needs to select a (new) relay UE for paging reception, how does the remote UE select the relay UE for paging reception?

[0070] Question 3 - Determination by the relaying UE of which remote UE(s) to forward the page: How does the relaying UE know which remote UE to relay the page to? Is this knowledge explicit or implicit?

[0071] Question 4 - Knowing the Remote UE PO at the Relay UE: How does the Relay UE know that the PO of the Remote UE paging is being relayed?

[0072] The remote UE may be moving. The mobility of the remote UE introduces another set of problems.

[0073] Issue 5 - The traditional RAN area update procedure, registration area update procedure or UE periodic registration area update is limited to one hop. The UE needs to switch to RRC connected mode to send RANU or registration area update. How the remote UE maintains the UE reachability status in the NW (CN or RAN) through other relay UEs should be solved.

[0074] Question 6 - How can the paging relay path be quickly reestablished so that the remote UE can seamlessly receive paging from the NW.

[0075] The present invention discloses subject matter that can solve the problem of sending paging messages to remote UEs that are more than one hop away from a base station. The disclosed subject matter includes a remote UE that establishes one or more paths for receiving paging messages from a gNB, or a relay UE that forwards paging messages from a gNB to a remote UE.

[0076] Methods, systems, and devices, etc. as described herein may provide for paging a remote UE. The method, system, computer-readable storage medium, or device provides for receiving relay context information from one or more neighboring UEs; based on the obtained relay context information, initiating a discovery-based paging path establishment process by sending a paging path discovery request to one or more neighboring relay UEs to discover one or more paths to a gNB and receiving a paging path discovery response from a neighboring UE or gNB to confirm the establishment of the paging path to discover and establish one or more paging paths between the remote UE and the gNB; based on the obtained relay context information, instructing a selection-based paging path establishment process by sending a paging path establishment request to select and configure a neighboring UE of the remote UE that has established one or more paging paths to the gNB and receiving a paging path establishment response to confirm the establishment of the paging path, i.e., the remote UE establishes the paging path of the remote UE along the paging path of the neighboring relay UE of the remote UE; selecting a new relay UE and establishing a new paging path to the gNB; and maintaining the paging path and updating the reachability of the network by sending a path update to the gNB

[0077] Methods, systems, computer-readable storage media, or apparatuses are provided for enabling a relay function or disabling a relay function based on a trigger condition or configuration by a gNB; and enabling sending relay context information or disabling sending relay context information based on a trigger condition (e.g., state, context information, etc.) or configuration by a gNB. In a discovery-based paging path establishment process: receiving a paging path discovery request message; determining whether to act as a paging relay for a remote UE, and forwarding the paging message to the gNB based on one or more criteria; inserting the UE ID of the relay UE into the paging path discovery request message and forwarding it to the gNB; receiving a path discovery response message to configure an adaptation layer of the relay UE to forward paging from the gNB to the remote UE; and receiving a paging path configuration message to configure an adaptation layer of the relay UE to forward paging from the gNB to the remote UE. In a selection-based paging path establishment process, a paging path establishment request may be received to configure an adaptation layer of the relay UE to forward paging from the gNB to the remote UE. A method, system, computer-readable storage medium, or apparatus provides for receiving a paging message from a gNB; extracting remote UE information in the paging message; and forwarding the paging message to the next UE on the paging path. A method, system, computer-readable storage medium, or apparatus provides for receiving a paging message from a UE and forwarding the paging message toward the remote UE to the next UE on the paging path. A method, system, computer-readable storage medium, or apparatus provides for selecting a new relay UE and establishing a new paging path to the gNB, which may include reestablishing the paging path for all UEs to which the relay UE forwards the paging message and updating the new paging path information to the UEs to which the relay UE forwards the paging message. The triggering condition may include a threshold capability of the UE, a threshold state of the UE, or a threshold number of relay UEs in a defined geographic area. All combinations of this and previous paragraphs (including deletions or additions of steps) are contemplated.

[0078] Architecture and protocol stack

[0079] Figure 5 and Figure 6The control plane protocol stack and user plane protocol stack when PC5 is used between a remote UE, a UE-to-UE relay UE, and a UE-to-network relay UE are shown in the figure. For the protocol architecture of the user plane and the control plane, relaying is performed above the RLC sublayer. The user plane and control plane data of the remote UE 201 are relayed from the remote UE 201 to the network via the UE-to-UE relay UE 202 or the UE-to-network relay UE 203 above the RLC, and vice versa. The Uu PDCP and RRC are terminated between the remote UE 201 and the gNB 204, while the RLC, MAC, and PHY are terminated in each link (e.g., the link between the remote UE 201 and the UE-to-UE relay UE 201, the link between the UE-to-UE relay UE 201 and the network relay UE 203, and the link between the UE-to-network relay UE 203 and the gNB 204). In the following (e.g., Figure 5 or Figure 6 ), it is shown that the RLC layer is terminated at each hop. However, the RLC layer from the remote UE 201 may also be terminated at the gNB 204.

[0080] A paging message may be sent by a gNB 204 and forwarded by a UE-to-network relay 203 and zero or more UE-to-UE relays 202 along one or more paths to a remote UE 201. In the present disclosure, these paths are named paging paths. First, a relay UE election method is disclosed, which is used to enable or disable a UE with relay capability to act as a relay function of a UE-to-network relay 203 or a UE-to-UE relay 202 for paging messages, as associated with "relay UE election". Before a gNB 204 sends a paging message to a remote UE 201, a paging path may be established between the remote UE 201 and the gNB 204, as associated with "paging path establishment". Methods are disclosed on how a paging message may be propagated from a gNB 204 to a remote UE 201 via an established paging path, as associated with "paging propagation". Due to topology changes caused by mobility and relay UE election changes, the remote UE 201, UE-to-UE relay 202 or UE-to-network relay 203 in the network needs to dynamically maintain the paging path between the remote UE 201 and the gNB 204, as associated with "Paging Path Maintenance and Reachability Management".

[0081] Relay UE election

[0082] In a network, some UEs support a relay function for relaying paging messages, while some UEs do not support the relay function due to their hardware and software capabilities. However, for UEs supporting the relay function, the relay function may not be enabled or elected to relay paging messages. When the relay function of the UE is enabled, the UE becomes a relay UE. In order to solve the problem 1 in the problem description, a relay UE election method is disclosed, which is used to enable or disable a UE with a relay capability to act as a relay function of a UE to network relay 203 or a UE to UE relay 202 for paging messages.

[0083] The UE may enable and disable its own relay function based on its status (e.g., capabilities). For example, if the battery level of the UE is below a preconfigured threshold, the UE may disable its relay function. If the UE has a Uu interface with the gNB 204, the UE may enable its relay function and self-select as a UE-to-network relay UE 203. If the UE does not have a Uu interface with the gNB 204, the UE may enable its relay function and self-select as a UE-to-UE relay 202. If the relay UE is willing to act as a relay UE for a new neighboring UE, the relay UE may periodically broadcast its relay context information as listed in Table 1 to its neighboring UEs. Otherwise, based on its status, the relay UE may stop broadcasting its relay context information to its neighboring UEs. For example, if the number of UEs that select the relay UE as a relay is greater than a preconfigured threshold, the UE may stop broadcasting its relay context information to its neighboring UEs. When the UE receives relay context information from a neighboring relay UE, the UE should know that the neighboring relay UE is willing to act as a relay UE. It should be noted that when the relay function on the UE is disabled, the UE may send a stop relay request to each UE that selects it as a relay UE, to its neighboring UE that selects it as a relay UE, or to all neighboring UEs of the UE, that is, the UE stops acting as a relay UE. The relay UE may not send its relay context information until it receives a request from its neighboring UE.

[0084] The UE may enable and disable its relay function based on the number of relay UEs in its vicinity. For example, if there is no relay UE broadcasting relay context information in its vicinity, the UE may enable its relay function. If the UE receives relay context information from its neighboring UEs, the UE may disable its relay function. The relay UE may enable or disable broadcasting its relay context information based on the number of relay UEs in its vicinity. For example, if there is no relay UE broadcasting relay context information in its vicinity, the UE may enable broadcasting. If the UE receives relay context information from its neighboring UEs, the UE may disable broadcasting.

[0085] The UE may enable and disable its relay functionality configured by the gNB 204, such as Figure 7 shown. Figure 7An exemplary relay UE election and configuration by a gNB is shown. At step 221, relay UE 202 may receive a relay configuration request from gNB 204. At step 222, relay parameters are configured based on information (e.g., context information) of the relay configuration request of step 221. At step 223, a relay configuration response is sent to gNB 204. gNB 204 may send a relay configuration request to enable or disable the relay UE to broadcast its relay context information based on criteria such as the UE's location, beam direction, capabilities, traffic load, or based on enabling or disabling relay functionality via a dedicated message through network requirements and policies. gNB 204 may send criteria for the UE to enable or disable the relay functionality, enable or disable the relay UE to broadcast its relay context information, and the UE may use the criteria to determine whether to disable or enable. The relay UE may confirm or reject the relay configuration request in the request.

[0086] Paging path establishment

[0087] Paging may be sent by gNB 204 and forwarded by UE-to-network relay 203 and zero or more UE-to-UE relays 202 to remote UE 201. Before gNB 204 sends a paging message to remote UE 201, a paging path may be established between remote UE 201 and gNB 204. To address Problem 2, Problem 3, or Problem 4 in the problem description, a method for establishing one or more paging paths between gNB 204 or remote UE 201 is disclosed. In the first disclosed method (e.g., discovery-based paging path establishment), a paging path discovery process may be triggered by remote UE 201 for gNB 204 to discover multiple candidate paging paths between remote UE 201 and gNB 204. gNB 204 may then select and configure an adaptation layer of UE-to-network relay 203 and zero or more UE-to-UE relays 202 that forwards paging along the paging path. In another disclosed method associated with establishing a paging path on an existing paging path, the remote UE 201 may select a relay UE among the relay UEs that have established one or more paging paths to the gNB 204, and may then establish the paging path of the remote UE along the paging path of the relay UE by configuring an adaptation layer of the relay UE on the paging path.

[0088] Discovery-based paging path establishment

[0089] In the discovery-based paging path establishment method, a paging path discovery procedure may be triggered by the remote UE 201 for the gNB 204 to discover multiple candidate paging paths between the remote UE 201 and the gNB 204, as associated with a “paging path discovery procedure”. The gNB 204 may then select one or more paging paths and establish the paging paths by configuring the relay UEs located on the paths, as associated with a “paging path configuration procedure”.

[0090] 1. Paging path discovery process

[0091] A paging path discovery process is disclosed, which is used by the gNB 204 to discover multiple candidate paging paths between the remote UE 201 and the gNB 204, such as Figure 8 As shown. The remote UE 201 triggers the process by sending (e.g., at step 233) a paging path discovery request to the gNB 204. The paging path discovery request is forwarded by one or more relay UEs to the gNB 204 (e.g., steps 234-237). As a result, the gNB 204 may discover multiple candidate paging paths between the remote UE 201 and the gNB 204. The gNB 204 may select one or more paging paths at the end of the process based on several criteria (e.g., step 238).

[0092] At step 231, a discovery process may be performed between remote UE 231 and relay 202. Remote UE 201 and relay UE 202 may discover each other via the discovery process. During the discovery process, relay UE 202 may broadcast or send its relay context information, as shown in Table 1.

[0093] Table 1 Relay context information

[0094]

[0095] At step 232, a PC5 connection may be established between the remote UE 201 and the relay 202. The remote UE 201 and the relay UE 202 may establish the PC5 connection after discovery. The remote UE 201 may further collect relay context information of the relay UE 202, such as the link quality between the remote UE 201 and the relay UE 202, and the sidelink (SL) DRX cycle of the relay UE 202.

[0096] At step 233, the relay 202 receives a paging path discovery request from the remote UE 201. The remote UE 201 sends a paging path discovery request message to the relay UE discovered during step 231. The remote UE 201 may send the message to all relay UEs within the broadcast communication range using broadcast, or send the message to each discovered relay UE 202 using unicast. The paging path discovery request message may include, but is not limited to, the information shown in Table 2.

[0097] Table 2 Paging path discovery request message

[0098]

[0099] At step 234, the relay 202 determines whether it should act as a paging relay for the remote UE 201. When the relay UE 202 receives the Paging Path Discovery Request message, it checks whether to act as a paging relay for the remote UE and forwards the paging message to the gNB based on criteria as described in the following example. In the example, there may be a forwarding if the gNB ID in the message is the same as the gNB 204 that the relay UE 202 is communicating with or the gNB ID field is not specified. In the example, there may be a forwarding if the gNB ID in the message is the same as the gNB 204 that the relay UE 202 is communicating with or the gNB ID field is not specified. In the example, there may be a forwarding if the relay UE 202 has the ability to act as a paging relay. In the example, there may be a forwarding if the relay hierarchy in the message is greater than the hierarchy of the relay UE 202. The relay hierarchy of a UE is the number of hops from the UE to the gNB. For example, the relay level from UE to network relay UE is 1, because the distance from UE to network relay gNB is only one hop. Figure 8 The relay level of the relay UE 202 shown is 2, because the UE-to-UE relay distance gNB is 2 hops. In the example, if the relay UE 202 has never received a message with the same sequence number from the same remote UE 201, then there may be forwarding.

[0100] If the relay UE 202 forwards the message, the relay UE 202 may insert its UE ID appended in the paging path discovery request message. The ID of the relay UE 202 may be an AS layer ID or a network ID.

[0101] At step 235, relay 202 may send a paging path discovery request to relay 203. Relay UE 202 forwards the paging path discovery request message to gNB 204. Relay UE 202 may send the message to relay UEs using broadcast within the broadcast communication range. Alternatively, relay UE 202 may send the message to each relay UE with a PC5 connection using unicast. Relay UE 202 may send only to another relay UE connected to the same gNB 204 as indicated in the paging path discovery message, and the layer number of the other UE is less than the layer number of the relay UE itself.

[0102] At step 236, the relay 203 determines whether to act as a paging relay for the remote UE 201. The relay UE 203 checks whether to act as a paging relay for the remote UE 201 or forward the paging message to the gNB 204, which is the same as step 234.

[0103] At step 237, relay 203 sends a paging path discovery request to gNB 204. Relay UE 203 forwards the paging path discovery request message to gNB 204 because the relay UE has a direct connection with gNB 204.

[0104] At step 238, gNB 204 selects a paging path for remote UE 201. gNB 204 may receive multiple paging path discovery requests sent by the same remote UE 201 with the same sequence number, and gNB 204 may select one of the multiple paging paths for remote UE 204.

[0105] Paging Path Configuration Process

[0106] A paging path configuration process is disclosed, which is used by the gNB 204 to establish one or more paging paths between the remote UE 201 and the gNB 204. The gNB 204 triggers the process after selecting one of the multiple paging paths of the remote UE 201.

[0107] In such Fig. 9 In the first disclosed process shown, the gNB 204 sends a paging path discovery response to the remote UE 201. The discovery response may include complete paging path information and may be forwarded via all or some of the relay UEs 202 on the path. When the relay UE 202 receives the paging path discovery response, the relay UE 202 may configure its adaptation layer to forward paging messages from the gNB 204 to the remote UE 201 in the future.

[0108] Continue to refer Fig. 9At step 241, gNB 204 sends a paging path discovery response to the UE-to-network relay 203 located on the paging path. The message may include, but is not limited to, the information shown in Table 3.

[0109] Table 3 Paging Path Discovery Response Message

[0110]

[0111] At step 242, the UE-to-network relay UE 302 uses the information received in the message of step 241 to configure its adaptation layer to receive and forward paging messages for the remote UE 201 in the future. If the UE-to-network relay UE 203 monitors the PO of the remote UE 201 in addition to monitoring its own PO, the UE-to-network relay UE 203 extracts parameters for calculating the paging occasion of the remote UE 201. The UE-to-network relay UE 203 should also extract information about the next relay located on the paging path. This information can be stored in association with the remote UE ID or the paging path ID. Therefore, the UE-to-network relay UE 203 can know which relay is used to forward the paging message in the future.

[0112] At step 243, the UE-to-network relay UE 203 may forward the paging path discovery response message to the next relay UE (e.g., relay UE 202) on the paging path. The UE-to-network relay 203 may delete the "parameters for calculating the paging occasion and DRX of the remote UE 201" field in the message before forwarding the paging path discovery response message. Alternatively, the UE-to-network relay 203 may add a SL DRX configuration for the next-hop relay UE regarding which slot is used to receive paging messages in the future.

[0113] At step 244, relay UE 202 receives the paging path discovery response and uses the information in the message to configure its adaptation layer to receive or forward paging messages for remote UE 201 in the future. Relay UE 202 should extract information about the next relay located on the paging path. This information can be stored in association with the remote UE ID or the paging path ID. Therefore, relay UE 202 can know which relay is used to forward paging messages in the future. Relay UE 202 can add SL DRX configuration for remote UE 201 about which slot is used to receive paging messages in the future.

[0114] At step 245, the relay UE 202 forwards the paging path discovery response message to the remote UE 201. After receiving the message, the remote UE establishes a paging path from the gNB. The remote UE 201 stores the UE ID to the network relay UE 203, the paging path ID, or the ID of the relay UE that forwards the paging message to the remote UE in the future. The remote UE 201 may configure its DRX based on the SL DRX information in the message of step 244.

[0115] Fig.10 An exemplary hop-by-hop paging path configuration is provided. In the second disclosed process, gNB 204 sends a paging path configuration message to each relay UE on the paging path and configures the adaptation layer. After configuring each relay UE on the paging path, gNB 204 sends a paging path discovery response to remote UE 201.

[0116] At step 251, the gNB sends a paging path configuration message to the UE-to-network relay 203 located on the paging path. The message may include but is not limited to the information shown in Table 4.

[0117] Table 4 Paging Path Configuration Message

[0118]

[0119]

[0120] At step 252, the UE-to-network relay UE 203 receives the paging path configuration message and uses the information in the message to configure the adaptation layer of the UE-to-network relay UE 203 to receive and forward paging messages for the remote UE 201 in the future. If the UE-to-network relay UE 203 monitors the PO of the remote UE 201 in addition to monitoring its own PO, the UE-to-network relay UE 203 extracts parameters for calculating the paging occasion of the remote UE 201. The UE-to-network relay UE 203 should also extract information about the next relay located on the paging path. This information is stored in association with the remote UE ID or the paging path ID. Therefore, the UE-to-network relay UE 203 can know which relay is used to forward the paging message in the future.

[0121] At step 253, gNB 204 sends a paging path configuration message to the next relay UE 202 located on the paging path. The message may include, but is not limited to, the information shown in Table 4.

[0122] At step 254, relay UE 202 uses the information in the message in step 253 to configure its adaptation layer to receive or forward paging messages for remote UE 201 in the future. Relay UE 202 needs to extract information about the next relay located on the paging path. This information can be stored in association with the remote UE ID or the paging path ID. Therefore, relay UE 202 can know which relay is used to forward paging messages in the future.

[0123] At step 255, gNB 204 sends a paging path discovery response message to the remote UE 101 located on the paging path. The message may include, but is not limited to, the information shown in Table 4. After receiving the message, the remote UE 201 may establish a paging path from the gNB. The remote UE may store the UE to network relay UE 2013 ID, the paging path ID, or the ID of the relay UE 202 that forwards the paging message to the remote UE in the future.

[0124] Establishing a paging path on an existing paging path

[0125] In the paging path establishment method, the remote UE 201 selects one or more relay UEs that have established one or more paging paths to the gNB 204, and then establishes the paging path of the remote UE along the paging path of the relay UE 202 by configuring the adaptation layer of the UE-to-UE relay and the UE-to-network relay located on the paging path, as shown in FIG. Fig.11 As shown. In this method, one or more neighboring relay UEs have established a paging path from gNB 204.

[0126] At step 260, the paging path has been established. At step 261, the remote UE 201 and the relay UE 202 discover each other via a discovery process. During the discovery process, the relay UE 202 may broadcast or send its relay context information, as shown in Table 1.

[0127] At step 262 , the remote UE 201 and the relay UE 202 may establish a PC5 connection after discovery. The remote UE 201 may further collect information of the relay UE 202 , such as link quality between the relay UE 202 , and SL DRX cycle of the relay UE 202 .

[0128] At step 263, based on the discovered information, the remote UE 201 selects one or more relay UEs that have established a paging path to the gNB 204, and then sends a paging path establishment request message to the relay UE 202. The paging path establishment request message may include, but is not limited to, the information shown in Table 5.

[0129] Table 5 Paging path establishment request message

[0130]

[0131] At step 264, when the relay UE 202 receives the paging path establishment request message, the relay UE 202 determines whether to act as a paging relay for the remote UE 201 or allow the remote UE 201 to share the same paging path. If the relay UE 202 determines to act as a paging relay for the remote UE 201 or allow the remote UE 201 to share the same paging path, the relay UE 202 configures its adaptation layer to receive the paging message or forward the paging message to the remote UE 201.

[0132] At step 265a, relay UE 202 forwards the paging path establishment request message to gNB 204 along its paging path.

[0133] At step 265b, the relay UE 202 sends a paging path establishment response to indicate whether to act as a paging relay for the remote UE or to allow the remote UE to share the same paging path.

[0134] At step 266, the relay UE 203 configures its adaptation layer to receive the paging message and forward it to the remote UE 201. Fig.11 When the relay 203 in the network receives the paging message sent to the remote UE 201, the relay 203 forwards the paging message to the relay 202. If the relay UE is a UE-to-network relay UE 203 and monitors the PO of the remote UE 201 in addition to monitoring the PO of the relay UE 203, the relay UE 203 extracts the parameters in the request for calculating the paging occasion of the remote UE 201. If the UE-to-network relay 203 cannot know the paging occasion based on the information in the paging path establishment request, the relay 203 sends the paging path establishment request to the gNB 204 to obtain the paging occasion of the remote UE 201. Alternatively, if the UE-to-network relay 203 monitors only its own PO and the paging for the remote UE 201 is also sent in the PO of the UE-to-network relay UE, the relay 203 forwards the paging path establishment request to the gNB 204 to notify the gNB 204.

[0135] At step 267, relay UE 203 forwards the paging path establishment request message to gNB 204 because the relay UE has a direct connection with gNB 204.

[0136] At step 228, if the UE-to-network relay UE 203 monitors the PO of the remote UE 201 in addition to its own PO, the gNB 204 sends a response with parameters for calculating the paging occasion of the remote UE 201 to the UE-to-network relay UE 203. Alternatively, if the UE-to-network relay 203 monitors only its own PO and paging for the remote UE 201 is also sent in the PO of the UE-to-network relay UE, the gNB 204 updates the paging configuration of the remote UE 201 and sends paging using its UE-to-network relay PO.

[0137] At step 229, gNB 204 sends a response with parameters for calculating the paging occasion of remote UE 201 to UE-to-network relay UE 203. gNB 204 may also include the UE_ID or I-RNTI-Value of remote UE 201 in the response.

[0138] Paging broadcast

[0139] Methods are disclosed on how to propagate paging messages from a gNB to a remote UE via an established paging path. In a first disclosed method, a UE-to-network relay UE 203 monitors the PO of a remote UE 201 in addition to its own PO, such as Fig.12 As shown. In the paging message sent from gNB 204 at step 271, the paging UE identity field in the paging record is the ID of the remote UE 201 or the ID of the paging path associated with the remote UE 201. Upon receiving the paging message, for each paging record in the paging record, if the UE identity in the paging record matches the UE identity of the remote UE 201 monitored by the UE-to-network relay 203, the UE-to-network relay 203 forwards the paging message (see step 272) to the next relay UE, such as the relay 202 on the sidelink. At step 273, the adaptation layer of the relay 202 forwards the paging message to the remote UE 201.

[0140] In the second disclosed method, the UE-to-network relay monitors only its own PO, and paging for the remote UE is also sent in the PO of the UE-to-network relay UE, such as Fig.13As shown. At step 281, in the paging message sent from the gNB 204, the paging UE identity field in the paging record may be the ID of the UE to network relay 203, and an additional field is added in the paging record to indicate the target UE identity of the paging message, such as the identity of the remote UE 201. Alternatively, in the paging message sent from the gNB 204, the UE identity field in the paging record may be the ID of the target UE, such as the identity of the remote UE 201. Upon receiving the paging message, for each paging record in the paging record, if the target UE identity in the paging record matches the UE identity of the remote UE 201 monitored by the UE to network relay 203, the UE to network relay 203 forwards the paging message (see step 282) to the next relay UE, such as the relay 202 on the sidelink. Similarly, at step 283, the adaptation layer of the relay 202 forwards the paging message to the remote UE 201. In another alternative, in the paging message sent from gNB 204 at step 281, the paging UE identity field in the paging record may be the ID of UE-to-network relay 203, and no additional field is added in the paging record to indicate the target UE identity of the paging message, such as the identity of remote UE 201. Upon receiving the paging message, UE-to-network relay 203 forwards (see step 282) the paging message to each remote UE it monitors. In each forwarding, UE-to-network relay 203 inserts the identity of remote UE 201 and forwards the paging message to the next relay UE, such as relay 202 on the sidelink. Similarly, the adaptation layer of relay 202 forwards (see step 283) the paging message to the remote UE.

[0141] Paging path maintenance and reachability management

[0142] In order to solve the problems 5 and 6 in the problem description, a method is disclosed in which a remote UE, a UE-to-UE relay, and a UE-to-network relay in a network can dynamically maintain a paging path between a remote UE and a gNB when the topology changes. Exemplary scenarios of paging path changes are disclosed. In a first scenario, the remote UE 201 selects a new relay UE and establishes a new paging path to the gNB 204. In a second scenario, one of the relay UEs located on the paging path of the remote UE 201 selects a new relay UE and establishes a new paging path to the gNB 204. In this scenario, the paging path of the remote UE 201 should also be updated. Multiple events can trigger the UE to reselect the paging path based on changes in the state of the sidelink, such as the signal quality of the link, and the state of the neighboring relay UE, such as the neighboring relay UE has fewer hops from the gNB or has more sidelink capabilities or a lighter load.

[0143] Fig.14The process of the remote UE selecting a new relay UE and establishing a new relay path is shown in FIG. Fig.14 In the example of FIG. 2 , the remote UE 201 at step 290 has already established a paging path by the relay 202 and intends to establish a new paging path via the relay 207. This process is similar to the paging path establishment process associated with establishing a paging path on an existing paging path. When the remote UE 201 discovers a new relay UE, such as the relay 207, the relay UE 207 may obtain the ID of the UE-to-network relay UE 203 associated with the relay 203 in step 291. In the scenario where the UE-to-network relay 203 associated with the relay 207 is the same as the UE-to-network relay 203 on its previous paging path, the remote UE 201 may not need to include its parameters for calculating paging occasions and DRX in the paging path establishment request in step 293. In this scenario, if the UE-to-network relay 203 still has the parameters for calculating the paging occasion and DRX of the remote UE 201, the UE-to-network relay 203 does not need to send a paging path establishment request to the gNB 204 in step 297. Step 292 is the same as Fig.11 Steps 294-296 are the same as step 262 in Fig.11 Steps 264-296 are the same as in Fig.11 The same as steps 268-269 in .

[0144] Fig.15 2 shows the process when one of the relay UEs on the paging path of the remote UE selects a new relay UE. Fig.15 In the example, remote UE 201 has established a paging path via relay 202 in a first period, and relay 202 intends to establish a new paging path via relay 207 in a second period. Relay 202 should establish a new paging path to gNB 204. Fig.15 ) is similar to establishing a paging path over an existing paging path (e.g., Fig.11) associated paging path establishment process. During the paging path establishment process, relay 202 sends a paging path establishment request to all relay UEs located on its paging path, such as relay 207 and UE-to-network relay 203, at step 303 to re-establish the paging path of all UEs to which it forwards paging messages. For example, in step 303, relay 202 indicates in the paging path establishment request that the paging path also needs to be re-established for remote UE 201. Upon receiving the message of 303, relay 207 configures its adaptation layer (at step 304) to forward paging for both remote UE 201 and relay 202 (at steps 305a and 305b). Similarly, when relay 207 forwards the paging path establishment request to the UE-to-network relay in step 305a, relay 207 indicates that the paging path also needs to be re-established for remote UE 201 and relay 202. Upon receiving the message, UE-to-network relay 203 configures its adaptation layer (at step 306a) to forward the paging for both remote UE 201 and relay 202. If the UE-to-network relay 203 on the paging path changes, and the Option 1 method (e.g., Figure 3 ), the paging path establishment also includes parameters for calculating the paging occasions and DRX of the relay 202 and the remote UE 201 in the paging path establishment. If the UE-to-network relay 203 does not know the parameters for calculating the paging occasions and DRX of the relay 202 or the remote UE 202, the relay 203 may send a request to the relay 202, the remote UE 201, or the gNB 204 to obtain this information. If the UE-to-network relay 203 on the paging path changes and the Option 2 method is used (e.g., Figure 4 ), then UE to network relay 203 forwards the paging path establishment request to gNB 204 at step 307, i.e., paging for remote UE 201 should be sent in the PO of the new UE to network relay UE. If the UE to network relay 203 on the paging path changes, relay 202 needs to update the new paging path information to the UE to which it forwards the paging message. For example, relay 202 notifies remote UE 201 about the new UE to network relay 203 information. Those steps that are not explicitly called are the same as Fig.11 The steps are the same as in .

[0145] The remote UE should maintain the paging path by periodically sending path updates. During the paging path establishment, a paging path update timer may be configured at the remote UE 201 by the gNB 204 or relay UE located on the paging path. The paging path update timer may be less than the periodic registration update timer of the UE to network relay and the RAN notification area update associated with the remote UE. Upon expiration of the paging path update timer, the remote UE 201 sends a paging path update to the gNB 204 at step 311 to update the reachability of the network, such as Fig.16 As shown. The paging path update may include the ID of the remote UE 201 or the paging path ID. When a relay UE on the path (e.g., relay 202) receives the paging path update from the remote UE 201, the relay UE 202 knows that the remote UE can still be reached via the paging path, and resets the timer associated with the paging path of the remote UE 201 as shown in step 312. If the relay UE 202 is not a UE-to-network relay 203, the relay 202 forwards the paging path update to the next relay towards the gNB 204 in step 313. When forwarding the paging path to the next relay UE located on the paging path, the relay UE 202 may also attach (e.g., insert) its UE ID or paging path ID. In this scenario, the paging path update may include UE reachability information of the remote UE 201 or the relay 202. When the next relay UE on the paging path, e.g., relay 202, receives the message, it extracts the reachability information and knows that the remote UE 201 and relay 202 are still reachable via the paging path, and resets the timer associated with the paging path of the remote UE 201 and relay 202 as shown in step 314. If the relay UE 202 is the UE-to-network relay 203 of the remote UE 201, then the relay 203 sends an RNA update or a registration update to the gNB 204 depending on the RRC state of the relay (see step 315). Further explaining step 315, it is noted that since the remote UE 201 does not have a direct link with the gNB 204, the RRC state of the remote UE 201 can be the same as that of the UE-to-network relay 203 located on its paging path, and the UE-to-network relay completes the RNA update and registration update on behalf of the remote UE 201 and all UEs to which it forwards the paging message. At step 316, the RNA update or registration update is completed.

[0146] Fig.17 An exemplary method for paging a UE is shown. As disclosed herein, it is contemplated that the same method as other figures such as Figure 7 , Figure 8 , Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 , Fig.16 , Table 3, Table 4 and other related topics are combined.

[0147] At step 321, the first device (UE-to-UE relay 202) may enable or disable a relay function for relaying paging messages. The trigger for enabling may be a self-initiated request or a request from an external physical or virtual device. The request may include a configuration for acting as a paging relay, or the configuration may be obtained after the determination of step 322. The configuration may include a paging occasion or a parameter for calculating the paging occasion of the second device, an indication to the next device to forward the paging message. For example, see Table 3 or Table 4.

[0148] At step 322, it is determined whether to act as a paging relay for a second device (e.g., UE 201) (e.g., enable or disable the relay function). Step 322 may be triggered by the request of step 321 or another request. The determination may be based on a state (e.g., capability). For example, if the battery level of the UE is below a preconfigured threshold, the UE may disable its relay function. The determination may be based on proximity. For example, is there a relay UE broadcasting relay context information near the first device, such as within a threshold radial distance (e.g., within 400 feet). The determination may be based on an analysis of the relay context information (e.g., one or a combination of the relay context information of Table 1). For example, detection of a specific tracking area code may help determine whether to disable or enable the paging relay function. The determination may be based on an analysis of a standard received from the second device. At step 323, the first device may monitor paging occasions based on information from the second device (e.g., UE to network relay 203 or UE 201). This information may be received from the second device, preconfigured, etc. At step 324, if the first device determines and is also enabled as a paging relay, the first device may receive and process paging messages from a third device (e.g., UE to network relay 203 or gNB 204). At step 325, the first device may forward paging messages from one or more other devices (e.g., the third device). At step 326, the first device may maintain (e.g., update) the state of being a paging relay for the second device. Other devices (e.g., the third device and the second device) may be sent messages with status updates. The paging path may be updated based on detecting topology changes or threshold signal quality, etc. The first device may act as a paging relay or disable this functionality. The second device may be a remote UE (e.g., UE 201). The third device may be a base station.

[0149] It should be understood that the entities that perform the steps shown herein may be logical entities. These steps may be stored in a Fig.19F or Figure 19G The device, server, or computer system shown in the embodiment of the present invention is stored in the memory and executed on the processor thereof. It is contemplated that the present invention may be performed in the present invention (e.g., Figures 7 to 16 ) skip steps, combine steps or add steps between the exemplary methods disclosed. Table 6 provides abbreviations and definitions used in the subject matter of this article.

[0150] Table 6 - Abbreviations and definitions

[0151]

[0152] Fig.18 An exemplary display (e.g., a graphical user interface) that may be generated based on the methods, systems, and devices in the methods and apparatuses for paging a remote UE as discussed herein is shown. A display interface 901 (e.g., a touch screen display) may provide text associated with the methods and apparatuses for paging a remote UE in box 902, such as RRC-related parameters. The progress of any step discussed herein (e.g., a message sent or the success of a step) may be displayed in box 902. In addition, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be a device topology implementing the methods, systems, and apparatuses for paging a remote UE, a graphical output of the progress of any method or system discussed herein, etc.

[0153] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities, including research on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE Advanced Standards, and New Radio (NR) (also referred to as "5G"). It is hoped that the 3GPP NR standards will continue to develop and include the definition of the next generation of radio access technology (new RAT), which is expected to provide new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. The flexible radio access is expected to include new non-backward compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different needs. It is expected that ultra-mobile broadband includes centimeter wave and millimeter wave spectrum, which will provide opportunities for ultra-mobile broadband access for indoor applications and hotspots, for example. In particular, ultra mobile broadband is expected to share a common design framework with sub-7 GHz flexible radio access, while having centimeter-wave and millimeter-wave specific design optimizations.

[0154] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy conservation), and enhanced connected vehicles to everything (eV2X) communications, which may include any of vehicle-to-vehicle communications (V2V), vehicle-to-infrastructure communications (V2I), vehicle-to-network communications (V2N), vehicle-to-pedestrian communications (V2P), and vehicle communications with other entities. Specific services and applications within these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, cloud-based wireless offices, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, home automation, robotics, and drones. This article considers all of these use cases and others.

[0155] Fig.19A An exemplary communication system 100 is shown in which methods and apparatus for paging a remote UE, such as those described and claimed herein, may be used. Figures 9 to 16 The system and method shown. The communication system 100 may include a wireless transmit / receive unit (WTRU) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (which may be generally or collectively referred to as WTRU 102 or WTRUs 102). The communication system 100 may include a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. The network services 113 may include, for example, a V2X server, a V2X function, a ProSe server, a ProSe function, an IoT service, video streaming, or edge computing.

[0156] It should be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be a wireless network, the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be a wireless network. Fig.19A , Fig.19B , Fig.19C , Fig.19D , Fig.19E or Fig.19F Although described as a handheld wireless communication device, it should be understood that in the various use cases contemplated for 5G wireless communications, each WTRU may include or be embodied as any type of device or equipment configured to send or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronics product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, bus, truck, train or airplane), etc.

[0157] The communication system 100 may also include a base station 114a and a base station 114b. Fig.19A In the example of , each base station 114a and 114b is shown as a single element. In practice, the base stations 114a and 114b may include any number of interconnected base stations or network elements. The base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks (such as the core network 106 / 107 / 109, the Internet 110, the network services 113, or other networks 112). Similarly, the base station 114b may be any type of device configured to wire or wirelessly interface with at least one of the remote radio heads (RRHs) 118a, 118b, the transmit and receive points (TRPs) 119a, 119b, or the roadside units (RSUs) 120a and 120b to facilitate access to one or more communication networks (such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, or the network services 113). The RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102 (e.g., WTRU 102c) to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112.

[0158] The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the network services 113, or the other networks 112. The RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, or the network services 113. By way of example, the base stations 114a, 114b may be base transceiver stations (BTSs), Node-Bs, eNode Bs, home Node Bs, home eNode Bs, next generation Node-Bs (gNode Bs), satellites, site controllers, access points (APs), wireless routers, and the like.

[0159] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. Similarly, the base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as a BSC, an RNC, a relay node, etc. The base station 114a may be configured to send or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). Similarly, the base station 114b may be configured to send or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown) for methods, systems, and devices for paging remote UEs, as disclosed herein. Similarly, the base station 114b may be configured to send or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one example, the base station 114a may include three transceivers, eg, one transceiver for each sector of the cell. In one example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may therefore utilize multiple transceivers for each sector of the cell.

[0160] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, or 102g over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0161] The base station 114b can communicate with one or more of the RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which can be any suitable wired communication link (e.g., cable, optical fiber, etc.) or a wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be established using any suitable radio access technology (RAT).

[0162] The RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120b may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0163] The WTRUs 102a, 102b, 102c, 102d, 102e, or 102f may communicate with each other, such as sidelink communications, over an air interface 115d / 116d / 117d, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).

[0164] The communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, the TRPs 119a, 119b and the RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) or High Speed ​​Uplink Packet Access (HSUPA).

[0165] In one example, the base station 114a and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish an air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively, using Long Term Evolution (LTE) or LTE Advanced (LTE-A). In the future, the air interface 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies and interfaces (such as sidelink communications, etc.). Similarly, 3GPP NR technology includes NR V2X technology and interfaces (such as sidelink communication, etc.).

[0166] The base station 114a and the WTRUs 102a, 102b, 102c, and 102g in the RAN 103 / 104 / 105 or the RRHs 118a, 118b, TRPs 119a, 119b or the RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 1X, or CDMA2000 802.16+. EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0167] Fig.19A The base station 114c in the example may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business district, a home, a vehicle, a train, an airline, a satellite, a manufacturing plant, a campus, etc., to implement the methods, systems, and devices for paging remote UEs as disclosed herein. In one example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, the base station 114c and the WTRU 102d may implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or a femtocell. Fig.19A As shown, the base station 114c may have a direct connection to the Internet 110. Therefore, the base station 114c may not need to access the Internet 110 via the core network 106 / 107 / 109.

[0168] The RAN 103 / 104 / 105 or the RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform high-level security functions, such as user authentication.

[0169] Although not in Fig.19A Although not shown in the figure, it will be appreciated that the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b, which may utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM or NR radio technology.

[0170] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned or operated by other service providers. For example, the networks 112 may include any type of packet data network (e.g., IEEE 802.3 Ethernet) or another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 or the RAN 103b / 104b / 105b or a different RAT.

[0171] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capabilities, for example, the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links to implement the methods, systems, and apparatuses for paging a remote UE as disclosed herein. For example, Fig.19A The illustrated WTRU 102g may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0172] Despite Fig.19A It is not shown, but it should be understood that the user equipment may be wired to the gateway. The gateway may be a home gateway (RG). The RG may provide a connection to the core network 106 / 107 / 109. It should be understood that many of the ideas included herein are equally applicable to UEs that are WTRUs and UEs that are connected to the network using a wired connection. For example, the ideas applied to the wireless interfaces 115, 116, 117, and 115c / 116c / 117c are equally applicable to wired connections.

[0173] Fig.19B 1 is a system diagram of an exemplary RAN 103 and a core network 106 that may implement the methods, systems, and apparatuses for paging a remote UE as disclosed herein. As described above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. Fig.19B As shown, the RAN 103 may include Node-Bs 140a, 140b, and 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node-Bs 140a, 140b, and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and radio network controllers (RNCs).

[0174] like Fig.19BAs shown, Node-B 140a, 140b can communicate with RNC 142a. In addition, Node-B 140c can communicate with RNC 142b. Node-B 140a, 140b and 140c can communicate with corresponding RNC 142a and 142b via Iub interface. RNC 142a and 142b can communicate with each other via Iur interface. Each of RNC 142a and 142b can be configured to control the corresponding Node-B 140a, 140b and 140c to which it is connected. In addition, each of RNC 142a and 142b can be configured to perform or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, switching control, macro diversity, security functions, data encryption, etc.

[0175] Fig.19B The illustrated core network 106 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is illustrated as part of the core network 106, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator.

[0176] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuPS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices.

[0177] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0178] The core network 106 may also be connected to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0179] Fig.19C1 is a system diagram of an exemplary RAN 104 and a core network 107 that may implement the methods, systems, and apparatus for paging a remote UE as disclosed herein. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[0180] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0181] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink or downlink, etc. Fig.19C As shown, eNode-Bs 160a, 160b, and 160c may communicate with one another via an X2 interface.

[0182] Fig.19C The illustrated core network 107 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator.

[0183] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0184] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode-B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing the context of the WTRUs 102a, 102b, and 102c, and the like.

[0185] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0186] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0187] Fig.19D 1 is a system diagram of an exemplary RAN 105 and a core network 109 that may implement the methods, systems, and apparatuses for paging a remote UE as disclosed herein. The RAN 105 may employ NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 117. The RAN 105 may also be in communication with the core network 109. A non-3GPP interworking function (N3IWF) 199 may employ non-3GPP radio technology to communicate with the WTRU 102c over the air interface 198. The N3IWF 199 may also be in communication with the core network 109.

[0188] The RAN 105 may include gNode-Bs 180a and 180b. It should be appreciated that the RAN 105 may include any number of gNode-Bs. The gNode-Bs 180a and 180b may each include one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117. When an integrated access and backhaul connection is used, the same air interface may be used between the WTRUs and the gNode-Bs, which may be the core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming techniques. Thus, the gNode-B 180a may, for example, use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 202a. It should be appreciated that the RAN 105 may employ other types of base stations, such as an eNode-B. It should also be appreciated that the RAN 105 may employ more than one type of base station. For example, the RAN may employ both eNode-Bs and gNode-Bs.

[0189] The N3IWF 199 may include a non-3GPP access point 180c. It should be appreciated that the N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with the WTRU 102c over the air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c over the air interface 198 using the 802.11 protocol.

[0190] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink or downlink, etc. Fig.19D As shown, gNode-Bs 180a and 180b may communicate with each other, for example, via an Xn interface.

[0191] Fig.19D The core network 109 shown may be a 5G core network (5GC). The core network 109 may provide a variety of communication services to customers interconnected by a radio access network. The core network 109 includes multiple entities that perform the functionality of the core network. As used herein, the term "core network entity" or "network function" refers to any entity that performs one or more functions of the core network. It should be understood that such core network entities may be logical entities implemented in the form of computer executable instructions (software) stored in a device or computer system (such as a computer system) configured for wireless or network communications. Figure 19G The system 90 shown is stored in a memory and executed on a processor thereof.

[0192] exist Fig.19DIn the example of , the 5G core network 109 may include access and mobility management function (AMF) 172, session management function (SMF) 174, user plane function (UPF) 176a and 176b, user data management function (UDM) 197, authentication server function (AUSF) 190, network exposure function (NEF) 196, policy control function (PCF) 184, non-3GPP interworking function (N3IWF) 199, user data repository (UDR) 178. Although each of the foregoing elements is depicted as part of the 5G core network 109, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator. It should also be understood that the 5G core network may not include all of these elements, may include additional elements, and may include multiple instances of each of these elements. Fig.19D The network functions are shown connected directly to each other, however, it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus.

[0193] exist Fig.19D In the example of , the connection between network functions is realized via a set of interfaces or reference points. It should be understood that network functions can be modeled, described or realized as a set of services called or invoked by other network functions or services. The invocation of network function services can be realized via direct connection between network functions, message exchange on a message bus, calling software functions, etc.

[0194] The AMF 172 may be connected to the RAN 105 via an N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. The AMF may be responsible for forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface is Fig.19D Not shown in FIG.

[0195] The SMF 174 may be connected to the AMF 172 via the N11 interface. Similarly, the SMF may be connected to the PCF 184 via the N7 interface and to the UPFs 176a and 176b via the N4 interface. The SMF 174 may serve as a control node. For example, the SMF 174 may be responsible for session management, IP address allocation for the WTRUs 102a, 102b, and 102c, management and configuration of traffic steering rules in the UPFs 176a and 176b, and generation of downlink data notifications to the AMF 172.

[0196] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b, and 102c with access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or any type of network that switches data packets. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to the packet data network by connecting to the packet data network via the N6 interface or by connecting to each other and to other UPFs via the N9 interface. In addition to providing access to the packet data network, UPF 176 may also be responsible for packet routing and forwarding, policy rule enforcement, quality of service handling for user plane traffic, and downlink packet buffering.

[0197] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates connectivity between the WTRU 102c and the 5G Core Network 170, for example, via a radio interface technology that is not defined by 3GPP. The AMF may interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0198] PCF 184 may be connected to SMF 174 via an N7 interface, to AMF 172 via an N15 interface, and to application function (AF) 188 via an N5 interface. The N15 and N5 interfaces are Fig.19D 102a, 102b, and 102c. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, thereby allowing the control plane nodes to implement these rules. The PCF 184 may send policies for the WTRUs 102a, 102b, and 102c to the AMF 172 so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via the N1 interface. The policies may then be implemented or applied at the WTRUs 102a, 102b, and 102c.

[0199] The UDR 178 may act as a repository for authentication credentials and subscription information. The UDR may interface with network functions so that the network functions may add to, read from, and modify data in the repository. For example, the UDR 178 may interface with the PCF 184 via an N36 interface. Similarly, the UDR 178 may interface with the NEF 196 via an N37 interface, and the UDR 178 may interface with the UDM 197 via an N35 interface.

[0200] The UDM 197 may serve as an interface between the UDR 178 and other network functions. The UDM 197 may authorize network functions to access the UDR 178. For example, the UDM 197 may be connected to the AMF 172 via an N8 interface, and the UDM 197 may be connected to the SMF 174 via an N10 interface. Similarly, the UDM 197 may be connected to the AUSF 190 via an N13 interface. The UDR 178 and the UDM 197 may be tightly integrated.

[0201] AUSF 190 performs authentication-related operations and is connected to UDM 178 via an N13 interface and to AMF 172 via an N12 interface.

[0202] NEF 196 exposes the capabilities and services in the 5G core network 109 to the application function (AF) 188. The exposure may occur on the N33 API interface. NEF can be connected to AF 188 via the N33 interface, and NEF can be connected to other network functions to expose the capabilities and services of the 5G core network 109.

[0203] The application function 188 may interact with the network functions in the 5G core network 109. The interaction between the application function 188 and the network functions may occur via a direct interface or may occur via the NEF 196. The application function 188 may be considered part of the 5G core network 109 or may be external to the 5G core network 109 and deployed by an enterprise having a business relationship with a mobile network operator.

[0204] Network slicing is a mechanism that can be used by mobile network operators to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing enables operators to create customized networks to provide optimized solutions for different market scenarios that require diverse requirements in terms of functionality, performance and isolation, for example.

[0205] 3GPP has designed the 5G core network to support network slicing. Network slicing is a good tool that network operators can use to support a variety of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband) that require very diverse and sometimes extreme requirements. Without the use of network slicing technology, when each use case has its own set of specific requirements for performance, scalability, and availability, the flexibility and scalability of the network architecture may not be sufficient to effectively support a wider range of use case requirements. In addition, new network services should be introduced more efficiently.

[0206] See again Fig.19DIn a network slicing scenario, the WTRU 102a, 102b, or 102c may be connected to the AMF 172 via an N1 interface. The AMF may be a logical part of one or more slices. The AMF may coordinate the connection or communication of the WTRU 102a, 102b, or 102c with one or more of the UPFs 176a and 176b, the SMF 174, and other network functions. Each of the UPFs 176a and 176b, the SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[0207] The core network 109 may facilitate communications with other networks. For example, the core network 109 may include, or may communicate with, an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between the 5G core network 109 and the PSTN 108. For example, the core network 109 may include, or may communicate with, a short message service (SMS) service center that facilitates communications via a short message service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and a server or application function 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0208] This article describes and Fig.19A , Fig.19C , Fig.19D or Fig.19E The core network entities shown in are identified by the names given to those entities in certain existing 3GPP specifications, but it should be understood that in the future, those entities and functions may be identified by other names, and that certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Fig.19A , Fig.19B , Fig.19C , Fig.19D or Fig.19E The specific network entities and functionality described and illustrated in the present disclosure are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or defined in the future.

[0209] Fig.19EAn exemplary communication system 111 is shown in which the systems, methods, and apparatus described herein for implementing paging remote UEs may be used. The communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and road side units (RSUs) 123a and 123b. In fact, the concepts presented herein may be applied to any number of WTRUs, base stations gNBs, V2X networks, or other network elements. One or several or all WTRUs A, B, C, D, E, and F may be outside the range of access network coverage 131. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0210] If WTRUs A, B, C, D, E, and F are within access network coverage 131, they may communicate with each other via gNB 121 over the Uu interface 129. Fig.19E In the example of FIG. 1 , WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate directly with one another via a sidelink interface (e.g., PC5 or NR PC5) such as interfaces 125a, 125b, or 128, regardless of whether they are within or outside access network coverage 131. For example, in Fig.19E In the example of , WTRU D outside the access network coverage 131 communicates with WTRU F inside the coverage 131.

[0211] WTRUs A, B, C, D, E, and F may communicate with the RSU 123a or 123b via the vehicle-to-network (V2N) 133 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the V2X server 124 via the vehicle-to-infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate with another UE via the vehicle-to-pedestrian (V2P) interface 128.

[0212] Fig.19F is a block diagram of an exemplary apparatus or device WTRU 102 that may be configured for wireless communication and operation in accordance with the systems, methods, and apparatus described herein to implement paging a remote UE, such as Fig.19A , Fig.19B , Fig.19C , Fig.19D or Fig.19E or Figures 5 to 16 WTRU 102 (e.g., UE). Fig.19FAs shown, the exemplary WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements. In addition, the base stations 114a and 114b or the nodes that the base stations 114a and 114b may represent (such as but not limited to a transceiver station (BTS), an eNode-B, a site controller, an access point (AP), a home Node-B, an evolved home eNode-B (eNodeB), a home evolved eNode-B (HeNB), a home evolved eNode-B gateway, a next generation eNode-B (gNode-B), and a proxy node, etc.) may include Fig.19F Some or all of the depicted elements may be exemplary implementations of the disclosed systems and methods for paging a remote UE as described herein.

[0213] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, or the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Fig.19F The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0214] The transmit / receive element 122 of the UE may be configured to transmit data to a base station (eg, Fig.19AThe transmitting / receiving element 122 may be a base station 114a) of a wireless communication network or a base station 114b of a wireless communication network, or may be a base station 114b of a wireless communication network or a base station 114c of a wireless communication network, or may be a base station 114c of a wireless communication network or a base station 114d of a wireless communication network or a base station 114d of a wireless communication network, or may be a base station 114a of a wireless communication network or a base station 114b of a wireless communication network or a base station 114d of a wireless communication network, or may be a base station 114b of a wireless communication network or ...

[0215] Furthermore, although the transmit / receive element 122 is Fig.19F Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for sending and receiving wireless signals over the air interface 115 / 116 / 117.

[0216] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11 or NR and E-UTRA), or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0217] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. In addition, the processor 118 may access information in and store data in any type of suitable memory, such as a non-removable memory 130 or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. The processor 118 may access information from memory that is not physically located on the WTRU 102, such as on a server hosted on the cloud or on an edge computing platform or on a home computer (not shown), and store the data in the memory. The processor 118 may be configured to control a lighting pattern, image, or color on the display or indicator 128 in response to the success or failure of some of the examples described herein, or to otherwise indicate the status of paging the remote UE and associated components. The controlled lighting pattern, image, or color on the display or indicator 128 may reflect the figures shown or discussed herein (e.g., Figures 6 to 16 , etc.). Messages and processes for paging remote UEs are disclosed herein. These messages and processes may be extended to provide an interface / API for a user to request resources via an input source (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128), and to request, configure, or query information related to paging remote UEs, and other information that may be displayed on display 128, etc.

[0218] The processor 118 may receive power from the power source 134 and may be configured to distribute or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0219] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. The WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 or determine its location based on the timing of signals received from two or more nearby base stations in addition to or in lieu of the information from the GPS chipset 136. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method.

[0220] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules or hardware modules that provide additional features, functionality, or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, Internet browsers, and more.

[0221] The WTRU 102 may be included in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains, or airplanes). The WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as an interconnect interface of one of the peripheral devices 138.

[0222] Figure 19G is a block diagram of an exemplary computing system 90, in which Fig.19A , Fig.19C , Fig.19D and Fig.19E One or more devices of a communication network as shown in, and such as described and claimed herein Figures 7 to 16The illustrated system and method for paging a remote UE, such as certain nodes or functional entities in the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, other networks 112, or network services 113. The computing system 90 may include a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91, which can perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 can receive, generate and process data related to the method and apparatus for paging a remote UE disclosed herein.

[0223] In operation, processor 91 fetches, decodes and executes instructions, and transfers information to and from other resources via the computing system's main data transfer path (system bus 80). Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0224] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes a circuit system that allows information to be stored and retrieved. ROM 93 generally includes stored data that cannot be easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. Access to RAM 82 or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address conversion function that converts a virtual address into a physical address as an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.

[0225] Additionally, computing system 90 may include a peripheral device controller 83 responsible for communicating instructions from processor 91 to peripheral devices such as printer 94 , keyboard 84 , mouse 95 , and disk drive 85 .

[0226] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output can be provided in the form of a graphical user interface (GUI). The display 86 can be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.

[0227] In addition, computing system 90 may include communications circuitry such as, for example, a wireless or wired network adapter 97 that may be used to connect computing system 90 to an external communications network or device, such as Fig.19A , Fig.19B , Fig.19C , Fig.19D or Fig.19E The RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, WTRU 102 or other network 112 can be used to enable the computing system 90 to communicate with other nodes or functional entities of these networks. The communication circuit system alone or in combination with the processor 91 can be used to perform the sending and receiving steps of certain devices, nodes or functional entities described herein.

[0228] It should be understood that any or all of the devices, systems, methods, and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer executable instructions executed on a processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, tapes, magnetic disk storage or other magnetic storage devices, or any other tangible or physical media that can be used to store the desired information and can be accessed by a computing system.

[0229] In describing the preferred methods, systems or apparatuses of the disclosed subject matter - paging a remote UE - as illustrated in the accompanying drawings, specific terminology is employed for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology selected.

[0230] The various techniques described herein may be implemented in conjunction with hardware, firmware or software, or in appropriate cases with a combination thereof. Such hardware, firmware and software may reside in a device located at each node of a communication network. These devices may operate individually or in combination with each other to implement the methods described herein. As used herein, the terms "device", "network device", "node", "equipment", "network node" and the like may be used interchangeably. In addition, unless otherwise provided herein, the term "or" is generally used in a manner that includes an end value.

[0231] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the subject matter disclosed herein, including making and using any devices or systems and performing any incorporated methods. The subject matter disclosed herein may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between the exemplary methods disclosed herein, such as with Figures 7 to 17 associated).

[0232] Methods, systems, devices, etc. as described herein may provide a device for paging a remote UE. Methods, systems, computer-readable storage media, or devices provide for enabling or disabling a relay function for relaying a paging message; determining whether to act as a paging relay for a second device; monitoring a paging occasion based on information of the second device; receiving a paging message from a third device; forwarding a paging message to a second device; and maintaining the state of acting as a paging relay for a second device. The information may be a parameter for calculating a paging occasion and DRX for a remote UE. The information may be from Table 2, Table 3, Table 4, or Table 5. The second device is a remote UE. The third device is a base station. The first device may enable or disable its own relay function based on an indication of its state. The first device may enable or disable the relay function of the first device based on the number of relay UEs adjacent to the first device (e.g., in its vicinity). The first device may enable or disable the relay function of the first device based on a configuration received from the second device. The second device may send an explicit dedicated message for enabling or disabling a relay function. The second device may send a standard for enabling or disabling a relay function for a UE. If the relay function is enabled, the first device may broadcast relay context information. The first device may receive a request message to act as a paging relay for the second device. The first device may determine whether to act as a paging relay for the second device. The first device may send a request message indicating the ability to act as a paging relay to the third device. The first device may receive a configuration to act as a paging relay for the second device. The configuration may include a paging occasion or a parameter for calculating the paging occasion of the second device. The configuration may include a next device for forwarding a paging message to the second device. The first device may be triggered to select a fourth device and establish a new paging path between the second device and the third device. The first device may be triggered by a change in the state of the SL and the state of the adjacent relay UE. The fourth device may receive configuration information about the paging occasion or a parameter for calculating the paging occasion of the second device (from the first device or another device). The configuration information may include information in Table 4, such as paging occasion configuration information. The first device may receive a periodic update message from the second device and forward the update message to the third device after attaching its own update message. Relaying may be enabled based on the configuration received from the third device. The update message may be a registration update message or a RAN notification area update message. Methods, systems, and apparatuses, etc. as described herein may provide for receiving criteria for enabling or disabling a relay function from a third device. Methods, systems, and apparatuses, etc. as described herein may provide for receiving an explicit dedicated message for enabling or disabling a relay function from a third device. Methods, systems, and apparatuses, etc. as described herein may provide for receiving a configuration for acting as a paging relay for a second device from a third device.Methods, systems, and devices, etc., as described herein, may provide for: enabling a relay function for relaying a paging message; receiving a request to act as a paging relay for a second device; determining, in response to the request, to act as a paging relay for the second device; monitoring paging occasions based on information of the second device; receiving a paging message from a third device; or forwarding a paging message to the second device. All combinations of this paragraph (including deletion or addition of steps) are contemplated in a manner consistent with other parts of the detailed description.

Claims

1. A first device, comprising: processor; and A memory, the memory being coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the processor performs the following operations: receiving a path discovery message to configure an adaptation layer of the first device to forward paging from a base station to a remote user equipment UE, and receiving a paging path configuration message to configure an adaptation layer of the first device to forward paging from the base station to the remote UE; enabling a relay function for relaying a paging message, wherein the relay function is enabled based on the path discovery message and based on the paging path configuration message; receiving a request to act as a paging relay for a second device; In response to the request, determining to act as a paging relay for the second device; receiving a paging message from a third device, the paging message including a paging propagation path identifier ID; forwarding the paging message to the second device based on the paging propagation path ID; as well as The second device is a remote UE, and the third device is a base station.

2. The first device of claim 1, the operations further comprising receiving an explicit dedicated message from the third device for enabling or disabling the relay function. 3 . The first device of claim 1 , the operations further comprising receiving criteria for enabling or disabling the relay function from the third device. 4 . The first device of claim 1 , the operations further comprising broadcasting relay context information when the relay function is enabled.

5. The first device of claim 1, the operations further comprising sending a message to the third device indicating an ability to act as a paging relay.

6. The first device of claim 1, the operations further comprising selecting a fourth device to establish a new paging path between the second device and the third device.

7. The first device of claim 6, wherein the selection of the fourth device is triggered by a change in a state of a sidelink and a state of a neighboring relay WTRU. 8 . The first device according to claim 6 , the operations further comprising sending fourth device configuration information, the fourth device configuration information being about a paging occasion or a parameter for calculating a paging occasion of the second device.

9. The first device of claim 1, the operations further comprising: receiving a periodic update message from the second device; as well as After inserting the update message associated with the first device, the update message is forwarded to the third device. 10 . The first device of claim 9 , wherein the update message is a registration update message or a radio access network (RAN) notification area update message.

Images