Associating a remote UE with a relay UE in 5GC

Abstract

Methods of operating a radio access network node (1100) and a core network node (1108, 1110) to link a remote user equipment, RMUE, device (1102) to a relay user equipment, RLUE, device (1104) in a communication network (1106) are described. The radio access network node (1100) operates to receive a message including information corresponding to the RMUE device (1102) or the RLUE device (1104) that has a connection established and used with a first access and mobility management function, AMF (1108) between the radio access network node (1100) and a corresponding one of the RMUE device (1102) or the RLUE device (1104). The radio access network node (1100) further operates to link the RMUE device (1102) to the RLUE device (1104) using the first AMF (1108). The core network node (1108, 1110) operates to receive a message that the first AMF (1108) includes data corresponding to the RLUE device (1104) and link the RMUE device (1102) to the RLUE device (1104) based on the message.

Description

Technical Field

[0001] This disclosure relates generally to communications, and more specifically to communication methods supporting wireless communications, as well as related devices and nodes. Background Technology

[0002] A remote user equipment (remote UE) can communicate with a wireless communication network (e.g., a 5GC communication network) via a relay user equipment (relay UE). The relay UE includes a Layer 2 relay, in which the relay UE supports indirect 3GPP communication between the remote UE and the wireless communication network. Therefore, indirect signaling and communication occur between the remote UE and the wireless communication network, with the relay UE acting as an intermediary between the remote UE and the wireless communication network.

[0003] In this setup, paging signaling for the remote UE is initially received and processed by the relay UE. In some implementations, the relay UE achieves this by only monitoring its own paging offset (PO), and within the relay UE's PO, paging of the remote UE is sent from the wireless network. However, this implementation requires that the wireless network link or associate the remote UE with the relay UE. Therefore, a solution is needed to efficiently link or associate the remote UE with the relay UE at the wireless network to enable efficient paging of the remote UE. Summary of the Invention

[0004] According to some embodiments, a method for operating a radio access network node to link a remote user equipment (RMUE) device to a relay user equipment (RLUE) device in a communication network is described. The method includes: receiving a message from either the RMUE device or the RLUE device, the message including information corresponding to the RMUE device or the RLUE device, the RMUE device or the RLUE device having a connection established between the radio access network node and the corresponding one of the RMUE device or the RLUE device using a first access and mobility management function (AMF). The method further includes: linking the RMUE device to the RLUE device using the first AMF.

[0005] According to some embodiments, a method for operating a core network node to link a Remote User Equipment (RMUE) device to a Relay User Equipment (RLUE) device in a communication network is described. The method includes: receiving a message from a radio access network node regarding a first AMF (Automatic Access Function), including data corresponding to the RLUE device, and receiving the message into the core network. The method further includes: linking the RMUE device to the RLUE device based on the message. Attached Figure Description

[0006] The accompanying drawings illustrate certain non-limiting embodiments of this disclosure. These drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application. In the drawings:

[0007] Figure 1 This is a block diagram showing the user plane radio protocol stack for UE-to-network relay in Layer 2 evolution;

[0008] Figure 2 This is a block diagram showing the control plane radio protocol stack for UE-to-network relay in Layer 2 evolution;

[0009] Figure 3 This is a signaling diagram illustrating the Option 2 paging process for the evolved ProSe remote UE;

[0010] Figure 4 This is a signaling diagram illustrating the Option 3 paging process of the evolved ProSe remote UE;

[0011] Figure 5 This is a signaling diagram showing a service request triggered by a remote UE;

[0012] Figure 6 This is a signaling diagram illustrating the connection establishment process for indirect communication from a UE to a network relay UE.

[0013] Figure 7 This is a signaling diagram illustrating the link between a remote UE and a relay UE according to some embodiments of this disclosure;

[0014] Figure 8 This is a block diagram illustrating a wireless device UE according to some embodiments of the present disclosure;

[0015] Figure 9 This is a block diagram illustrating a radio access network RAN ​​node (e.g., a base station eNB / gNB) according to some embodiments of the present disclosure;

[0016] Figure 10 This is a block diagram illustrating core network CN nodes (e.g., AMF nodes, SMF nodes, etc.) according to some embodiments of the present disclosure;

[0017] Figure 11 This is a block diagram of a communication network according to an embodiment of the present disclosure;

[0018] Figure 12 This is a flowchart illustrating the operation of linking a remote user equipment (RMUE) device to a radio network node of a relay user equipment (RLUE) device in a communication network according to some embodiments of the present disclosure;

[0019] Figure 13This is a flowchart illustrating the operation of linking an RMUE device to a core network node of an RLUE device according to some embodiments of the present disclosure;

[0020] Figure 14 This is a block diagram of a wireless network according to some embodiments;

[0021] Figure 15 This is a block diagram of a user equipment according to some embodiments;

[0022] Figure 16 This is a block diagram of a virtualized environment according to some embodiments;

[0023] Figure 17 This is a block diagram of a telecommunications network connected to a host computer via an intermediate network, according to some embodiments;

[0024] Figure 18 This is a block diagram of a host computer that communicates with a user equipment via a base station through a partially wireless connection, according to some embodiments.

[0025] Figure 19 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0026] Figure 20 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0027] Figure 21 This is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments; and

[0028] Figure 22 This is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments. Detailed Implementation

[0029] In the following description, the present disclosure will be described in more detail with reference to the accompanying drawings, which illustrate examples of embodiments of the present disclosure. However, the present disclosure may be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed by default to be present / used in another embodiment.

[0030] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as illustrative examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the embodiments may be modified, omitted, or expanded without departing from the scope of the subject matter.

[0031] In 3GPP 15, Layer 2 evolved UE-to-network relay was studied in 3GPP TR 36.746 (Release 15) and 3GPP TR 23.733, but is not included in any normative specification. User plane and control plane data of remote UEs are relayed over Radio Link Control (RLC) via UE-to-network relay. Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) terminate between the evolved remote UE and the eNB, while RLC, Media Access Control (MAC), and Physical Layer (PHY) terminate at each hop. The user plane protocol stack and control plane protocol stack are as follows: Figure 1 and Figure 2 As shown. The adaptation layer between the evolved UE to network relay UE and the eNB distinguishes between the Uu bearers of a specific evolved remote UE. Different evolved remote UEs and different Uu bearers of evolved remote UEs are indicated by additional information (e.g., UE ID and bearer ID) included in the adaptation layer header, which is added to the PDCP Protocol Data Unit (PDU). The adaptation layer can be considered as part of a PDCP sublayer or a separate new layer between a PDCP sublayer and an RLC sublayer. One function of the adaptation layer is to map bearers associated with similar Quality of Service (QoS) characteristics to the same Logical Channel (LCH) in the Uu interface between the Layer 2 evolved UE to network relay and the gNB, with the bearers targeting one or more remote UEs or Layer 2 evolved UE to network relay. In the PC5 interface, different Uu bearers of evolved remote UEs are distinguished by different Sidelink Logical Channel IDs (LCIDs).

[0032] TR 36.746 examines three paging options. Paging option 1 is not applicable to situations outside of coverage and is therefore not discussed in this paper. Paging option 2 assumes that the remote UE and the trunk UE are not linked in the core network, while paging option 3 requires that the UE and the trunk UE be linked in the core network. Figure 3The solution proposed in paging option 2 is illustrated. The Evolved Proximity Service (ProSe) UE to Network Relay UE 302 monitors the paging opportunities (POs) of its linked Evolved ProSe Remote UE 300, in addition to its own PO. The Evolved ProSe Remote UE 300 does not need to attempt paging reception via the downlink when linked to the Evolved ProSe UE to Network Relay UE 302. The Evolved ProSe UE to Network Relay UE 302 may need to monitor multiple paging opportunities. The Evolved ProSe UE to Network Relay UE 302 must know the paging opportunities of the Evolved ProSe Remote UE 300 and must decode the paging message and determine which Evolved ProSe Remote UE 300 is being paging to. Furthermore, the Evolved ProSe UE to Network Relay UE 302 may need to relay the paging of the Evolved ProSe Remote UE 300 via a short-range link.

[0033] Paging option 2 is typically applicable both within and outside E-UTRAN coverage for the Evolved ProSe Remote UE 300. The Evolved ProSe Remote UE 300 does not need to attempt paging reception via DL when linked to the Evolved ProSe UE to Network Relay UE 302. This is more energy-efficient for the Evolved ProSe Remote UE 300. Furthermore, the network does not need to know whether the Evolved ProSe Remote UE 300 and the Evolved ProSe UE to Network Relay UE 302 are linked or associated. However, this solution requires the Evolved ProSe UE to Network Relay UE 302 to monitor multiple POs. This is less energy-efficient for the Evolved ProSe UE to Network Relay UE 302, as power consumption can increase depending on the number of Evolved ProSe Remote UE 300s linked to the Evolved ProSe UE to Network Relay UE 302. Furthermore, the evolved ProSe UE to network relay UE302 requires a short-range link to relay paging of the evolved ProSe remote UE 300. This results in additional power consumption and additional use of SL resources for the evolved ProSe UE to network relay UE 302.

[0034] Figure 4The solution proposed in paging option 3 is illustrated. The evolved ProSe UE to network relay UE 402 only monitors its own PO, and paging for the linked evolved ProSe remote UE 400 is also sent in the PO of the evolved ProSe UE to network relay UE 402. The evolved ProSe remote UE 400 does not need to attempt paging reception via the downlink when linked to the evolved ProSe UE to network relay UE 402. The evolved ProSe UE to network relay UE 402 must decode the paging message, determine which evolved ProSe remote UE 400 is being paging for, and relay the paging of the evolved ProSe remote UE 400 via a short-range link. In order to page the evolved ProSe remote UE 400, the core network (e.g., MME 406) needs to know the link status between the evolved ProSe UE to network relay UE 402 and the evolved ProSe remote UE 400, and when the evolved ProSe remote UE 400 is linked, the paging message of the evolved ProSe remote UE 400 is remapped so that it appears on the PO of the evolved ProSe UE to network relay UE 402.

[0035] Paging option 3 typically applies both within and outside E-UTRAN coverage for the Evolved ProSe Remote UE 400. The Evolved ProSe Remote UE 400 does not need to attempt paging reception via DL when linked to the Evolved ProSe UE to Network Relay UE 402. This is more energy-efficient for the Evolved ProSe Remote UE 400. The Evolved ProSe UE to Network Relay UE 402 does not need to monitor multiple POs. This is more energy-efficient for the Evolved ProSe UE to Network Relay UE 402 compared to option 2. However, the Evolved ProSe UE to Network Relay UE 402 needs to relay paging from the Evolved ProSe Remote UE 400 via a short-range link. This results in additional power consumption and additional use of SL resources for the Evolved ProSe UE to Network Relay UE 402. In addition, the network needs to know the link status between the evolved ProSe UE and the network relay UE 402 and the evolved ProSe remote UE 400 in order to implement paging option 3.

[0036] Figure 5The procedure for establishing UE-NW relay service is illustrated as described in 3GPP TR 23.733. Based on the solution selected for critical issue 2, e-remote UE 500 and e-relay UE 502 perform PC5 discovery in step 1 of this procedure. Triggered by the upper layer, e-remote UE 500 initiates a one-to-one communication with e-relay UE 502 by sending INDIRECT_COMMUNICATION_REQUEST to e-relay UE 502 in step 2. Triggered by the request received from e-remote UE 500, e-relay UE 502 sends a service request message (e-relay UE 502 identifier, such as GUTI, S-TMSI) to e-relay UE's MME 506 in step 3 of this procedure. This step is in accordance with Section 5.3.4 of TS 23.401. In step 4, e-relay UE 502 sends an INDIRECT_COMMUNICATION_RESPONSE message to e-remote UE 500. If INDIRECT_COMMUNICATION_REQUEST is accepted, then e-remote UE 500 sends a service request (5) (e-remote UE 500 identifier, such as GUTI, S-TMSI) to e-remote UE MME 508. The service request message is encapsulated in an RRC message sent to eNB 504. e-relay UE 502 forwards the message to eNB 504 using the L2 relay method specified by the RAN.

[0037] exist Figure 5 In step 6 of the process, the eNB 504 uses the identifier of the e-remote UE 500 to derive the identifier of the e-remote UE MME 508, and forwards the NAS message in the S1-MME control message, such as... Figure 5 As shown. This step is in accordance with Section 5.3.4 of TS 23.401. Whether the eNB 504 appends the identifier of the e-relay UE 502 or any other information to the S1-MME control message depends on the final selection of the idle mode operation and billing solution for the e-remote UE 500. In step 7, the NAS authentication / security process as defined in Section 5.3.10 of TS 23.401 regarding "Security Functions" can be performed. Figure 5It is also shown that in step 8 of the procedure, MME 508 sends an S1-AP Initial Context Establishment Request message to eNB 504. In step 9 of the procedure, eNB 504 performs a radio bearer establishment procedure according to section 5.3.4 of TS 23.401. eRelay UE 502 uses the RAN-specified L2 relay method to forward all messages between eRemote UE 500 and eNB 504. In step 10, uplink data (10) from eRemote UE 500 can now be forwarded by eRelay UE 502 and eNB 504 to serving GW 512. Figure 5 The process also illustrates how the serving GW 512 forwards uplink data to the PDN GW 512. In step 11 of this procedure, the eNB 504 sends an S1-AP message "Initial context establishment complete" to the MME 508. This step is described in detail in TS 36.300.

[0038] Research on system enhancements in Proximity-Based Services (ProSe) in 5G systems is described in 3GPP TR 23.752. Section 6.7 describes indirect communication via Layer 2 UE to network relay UE and the following functions: control and user plane protocols, network selection, authorization and provisioning, registration and connection management, QoS, mobility (e.g., mobility restrictions), and security. Figure 6 The steps for establishing a connection for indirect communication via a Layer 2 UE to a network relay UE are illustrated. Figure 6 As shown, if the remote UE is within coverage area, in step 0, the remote UE and the UE-to-network relay UE can independently perform initial registration with the network according to the registration procedure in TS 23.502. When subsequent NAS signaling between the remote UE and the network is exchanged via the UE-to-network relay UE, the assigned 5G globally unique temporary ID (GUTI) of the remote UE is maintained. It should be noted that... Figure 6 The process shown assumes a single-hop relay.

[0039] Figure 6It is also shown that if, within coverage area, the remote UE and the UE-to-network relay UE independently obtain service authorization for indirect communication from the network, as shown in step 1. In steps 2 and 3 of this procedure, the remote UE and the UE-to-network relay UE perform UE-to-network relay UE discovery and selection. By sending an indirect communication request message to the UE-to-network relay in step 4 of this procedure, the remote UE initiates a one-to-one communication connection with the selected UE-to-network relay UE via PC5. In step 5, if the UE-to-network relay UE is in the CM_IDLE state, triggered by the communication request received from the remote UE, the UE-to-network relay UE sends a service request message to its serving AMF via PC5. The relay's AMF can perform authentication of the UE-to-network relay UE based on NAS message verification, and the AMF will check subscription data if necessary. If the UE-to-network relay UE is already in the CM_CONNECTED state and authorized to perform relay services, step 5 is omitted.

[0040] exist Figure 6 In step 6 of the process, the UE-to-Network Relay UE sends an indirect communication response message to the remote UE. In step 7, the remote UE sends a NAS message to the serving AMF. The NAS message is encapsulated in an RRC message sent to the UE-to-Network Relay UE via PC5, and the UE-to-Network Relay UE forwards this message to the NG-RAN. The NG-RAN derives the serving AMF of the remote UE and forwards the NAS message to that AMF. It is assumed that the remote UE's PLMN is accessible by the UE-to-Network Relay PLMN, and that the UE-to-Network Relay UE's AMF supports all S-NSSAIs that the remote UE might want to connect to. If the remote UE has not yet performed initial registration with the network in step 0, the NAS message is an initial registration message. Otherwise, the NAS message is a service request message.

[0041] If a remote UE performs initial registration via a network relay, the remote UE's serving AMF can perform authentication of the remote UE based on NAS message verification, and, if necessary, the remote UE's AMF checks the subscription data. Figure 6 In step 8, the remote UE can trigger a PDU session establishment procedure as defined in section 4.3.2.2 of TS 23.502. In step 9, data is transmitted between the remote UE and the UPF via the UE-to-Network Relay UE and the NG-RAN. The UE-to-Network Relay UE uses the L2 relay method specified by the RAN to forward all data messages between the remote UE and the NG-RAN.

[0042] As discussed above, in events employing paging option 3, the prerequisite is that the relay UE and the remote UE need to be linked or associated in a wireless communication network (e.g., 5GC). However, how the relay UE and the remote UE should be linked or associated is unclear in the current 3GPP specification. To address this issue, this disclosure describes systems and methods for efficiently linking / unlinking between a remote UE and a relay UE.

[0043] Figure 8 This is a block diagram illustrating the elements of a communication device UE 300 (also referred to as a mobile terminal, mobile communication terminal, wireless device, wireless communication equipment, wireless terminal, mobile device, wireless communication terminal, user equipment UE, user equipment node / terminal / device, etc.) configured to provide wireless communication according to embodiments of this disclosure. (A communication device 800 may be provided, for example, as described below regarding...) Figure 14 (As discussed in the wireless device 4110.) As shown in the figure, the communication device UE may include an antenna 807 (e.g., corresponding to...) Figure 14 Antenna 4111) and transceiver circuit 801 (also referred to as transceiver, for example, corresponding to Figure 14 The transceiver circuit 801 includes a transmitter and a receiver, which are configured to provide communication with a base station of a radio access network (e.g., corresponding to a base station of a radio access network). Figure 14 The network node 4160 (also referred to as the RAN node) provides uplink and downlink radio communication. The communication device UE may further include: a processing circuit 803 (also referred to as a processor, corresponding to processing circuit 4120 in Figure 14), coupled to the transceiver circuitry; and a memory circuit 805 (also referred to as a memory, corresponding to...). Figure 14 A device-readable medium 4130 is coupled to the processing circuitry. Memory circuitry 805 may include computer-readable program code that, when executed by processing circuitry 803, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 803 may be defined to include memory, thereby eliminating the need for a separate memory circuitry. The communication device UE may also include an interface (e.g., a user interface) coupled to processing circuitry 803, and / or the communication device UE may be incorporated into a vehicle.

[0044] As discussed herein, the operation of the communication device UE can be performed by processing circuitry 803 and / or transceiver circuitry 801. For example, processing circuitry 803 can control transceiver circuitry 801 to send communications to a radio access network node (also known as a base station) via a radio interface and / or to receive communications from a RAN node via a radio interface. Furthermore, modules can be stored in memory circuitry 805, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 803, processing circuitry 803 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to wireless communication devices).

[0045] Figure 19 This is a block diagram illustrating elements of a radio access network (RAN) node 900 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communications according to embodiments of this disclosure. (RAN node 900 may be provided, for example, as described below regarding...) Figure 14 (As discussed in the network node 4160.) As shown in the figure, the RAN node may include transceiver circuitry 901 (also referred to as a transceiver, for example, corresponding to...) Figure 14 The transceiver circuit 901 (part of interface 4190) includes a transmitter and a receiver, configured to provide uplink and downlink radio communication with the mobile terminal. The RAN node may include network interface circuitry 907 (also referred to as the network interface, corresponding to...) Figure 14 The network interface circuit 907 (part of interface 4190) is configured to provide communication with other nodes of the RAN and / or core network CN (e.g., other base stations). The RAN node may also include: a processing circuit 903 (also referred to as a processor, corresponding to processing circuit 4170), coupled to transceiver circuitry; and a memory circuit 905 (also referred to as a memory, corresponding to...). Figure 14 A device-readable medium (4180) is coupled to the processing circuitry. The memory circuitry 905 may include computer-readable program code that, when executed by the processing circuitry 903, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 903 may be defined to include memory, thereby eliminating the need for a separate memory circuitry.

[0046] As discussed herein, the operation of the RAN node can be performed by processing circuitry 903, network interface 907, and / or transceiver 901. For example, processing circuitry 903 can control transceiver 901 to transmit downlink communications to one or more mobile terminal UEs via the radio interface and / or receive uplink communications from one or more mobile terminal UEs via the radio interface. Similarly, processing circuitry 903 can control network interface 907 to transmit communications to one or more other network nodes and / or receive communications from one or more other network nodes via the network interface. Furthermore, modules can be stored in memory 905, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 903, processing circuitry 903 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to the RAN node).

[0047] According to some other embodiments, the network node can be implemented as a core network (CN) node without a transceiver. In this embodiment, transmissions to the wireless communication device (UE) can be initiated by the network node, such that the transmissions to the UE are provided via a network node including a transceiver (e.g., via a base station or RAN node). According to an embodiment where the network node is an RAN node including a transceiver, initiating the transmission can include transmissions performed via the transceiver.

[0048] Figure 10 This is a block diagram illustrating elements of a CN node (e.g., SMF node, AMF node, etc.) of a core network configured to provide cellular communications according to embodiments of the present disclosure. As shown, the CN node may include network interface circuitry 1007 (also referred to as a network interface) configured to provide communication with other nodes in the core network and / or radio access network (RAN). The CN node may also include: processing circuitry 1003 (also referred to as a processor) coupled to the network interface circuitry; and memory circuitry 1005 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 1005 may include computer-readable program code that, when executed by the processing circuitry 1003, causes the processing circuitry to perform operations according to embodiments of the present disclosure. According to other embodiments, the processing circuitry 1003 may be defined to include memory, thereby eliminating the need for a separate memory circuitry.

[0049] As discussed herein, the operation of the CN node can be performed by processing circuitry 1003 and / or network interface circuitry 1007. For example, processing circuitry 1003 can control network interface circuitry 1007 to send communications to or / or receive communications from one or more other network nodes via network interface circuitry 1007. Furthermore, modules can be stored in memory 1005, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 1003, processing circuitry 1003 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to the core network node).

[0050] Figure 7 An example signaling diagram is shown, illustrating an example signaling procedure for linking a remote (RM) UE 700 to a relay (RL) UE 702 according to an embodiment of this disclosure. For example, Figure 7 This illustrates that in step 8 of the signaling process, gNB 704 selects to use the same AMF 706 for both RMUE 700 and RL UE 702. For example, in Figure 7 In this scenario, when RM UE 700 is linked to RL UE 702, the AMF 706 used for RL UE 702 is also used for RM UE 700. It is also possible that when RM UE 700 is linked to RL UE 702, the AMF 708 used for RM UE 700 is also used for RL UE 702. Assuming that the AMF 706 used for RL UE 702 will also be used for RM UE 700, in step 9, gNB 704 sends an NGAPINITIAL UE message for RM UE 700 to the AMF 706 currently used for RL UE 702, and includes the information of RL UE 702 (i.e., NG-RAN NGAP ID and AMF NGAP ID) in the NGAP INITIAL UE message.

[0051] If RM UE 700 includes the 5G GUTI in the registration request, and the 5G GUTI points to a different AMF 708 (previously serving the UE), then a Namf_Communication_UEContextTransfer is sent to the old AMF 708 to retrieve the UE's (currently remote UE 700) context, such as... Figure 7As shown in step 10. In step 11, RL UE 702 and RM UE 700 are now linked in the AMF 706 currently used for RL UE 702. From now on, this AMF will be used for both RL UE 702 and RM UE 700. AMF 706 can adjust the paging parameters of RM UE 700 to align with the paging parameters of RL UE 702, thereby allowing paging option 3 to be applied.

[0052] If the remote UE 700 leaves the relay UE 702 and connects directly to the wireless communication network via the Uu interface, it may be necessary to disconnect the remote UE 700 from the relay UE 702. If the remote UE 700 moves and becomes directly connected via the Uu interface, it becomes a normal UE. In this case, gNB 704 (or another gNB) sends an NGAP INITIAL UE message (e.g., for a NAS registration request) for the UE, similar to... Figure 7 Step 9 differs in that gNB 704 does not include information about the RL UE 702 previously linked to the remote UE 700. Upon receiving such an NGAP message, AMF 706 understands that the UE is now directly connected via Uu and should perform the disconnection of the UE 700 from the previously linked RL UE 702.

[0053] When UE 700 becomes directly connected via Uu, the new AMF currently serving UE 700 (previously a remote UE) may or may not change. If the AMF remains unchanged, AMF 706 will remove the old link between the UE and the RL UE 702 previously linked to UE 700. If the AMF changes, the new AMF will first retrieve the UE 700 context from the old AMF 706, for example, if there is no information about the old link. The old AMF 706 will then remove the UE 700 context.

[0054] If the remote UE 700 connects to another relay UE, it may also be necessary to disconnect. In this case, the gNB NGAP INITIAL message for the remote UE 700 will include information about the different relay UE. Alternatively or additionally, the gNB NGAPINITIAL message explicitly indicates that the remote UE 700 has left the previous relay UE 702. Following a process similar to the above, the old AMF 706 that previously served the UE 700 will remove the link between the UE 700 and the old relay UE 702 that was previously linked to the UE 700. Also following a process similar to the above, the new AMF currently serving the UE 700 will add the link between the UE 700 and the new relay UE to which the UE 700 is currently connected. The above operations for the remote UE 700 and relay UE 702 can be performed using the above... Figure 8 This is implemented using a structure. For example, modules can be stored in... Figure 8 The memory 805 contains these modules, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding UE communication device processing circuit 803, the processing circuit 803 performs the corresponding operations described above.

[0055] Based on some embodiments of this disclosure, reference will now be made to Figure 12 Flowcharts and Figure 11 The example RAN node 1100 shown is used to discuss RAN node 900 (using... Figure 9 The operation is implemented using a structure. For example, modules can be stored in... Figure 9 The memory 905 contains these modules, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding RAN node processing circuit 903, the processing circuit 903 performs the corresponding operation of the flowchart.

[0056] Figure 12 A method for operating a radio access network node according to an embodiment is illustrated to link a remote user equipment (RMUE) device to a relay user equipment (RLUE) device in a communication network. For example, Figure 11 An example RAN node 1100 is shown, which operates to link RMUE device 1102 to RLUE 1104 in a communication network 1106. In some embodiments, RAN node 1100 includes a gNB, such as gNB 704 discussed above. However, it should be noted that RAN node 1100 may include different types of radio access network nodes (e.g., the different types described herein) and is not limited to gNB-type radio access network nodes.

[0057] return Figure 12The method includes: receiving a 1200 message from either an RMUE device or an RLUE device, the message including information corresponding to the RMUE device or RLUE device, the RMUE device or RLUE device having a connection established between a radio access network node and the corresponding RMUE device or RLUE device and using a first access and mobility management function (AMF). Continuing with the previous example, Figure 11 The diagram illustrates RAN node 1100 receiving a message from RMUE device 1102 or RLUE device 1104, the message including information corresponding to RMUE device 1102 or RLUE device 1104 having a connection established between RAN 110 and the corresponding one of RMUE device 1102 or RLUE device 1104 and using a first AMF 1108 operating in core network 1112.

[0058] Figure 12 A method is also illustrated that includes linking an RMUE device 1202 to an RLUE device using a first AMF. For example, according to an embodiment, RAN 1100 uses AMF 1108 to link the RMUE device 1102 to the RLUE device 1104. In some embodiments, the method includes sending a message to the core network regarding the first AMF including data corresponding to the RLUE device or the RMUE device. For example, RAN 1100 operates to send a message to the core network 1112 regarding AMF 1108 including data corresponding to RLUE 1104 or RMUE 1102. According to some embodiments, the method includes sending a registration message to the core network including information corresponding to the RLUE device. For example, RAN 1100 operates to send a registration message to the core network 1112 including information corresponding to RLUE 1104. In this embodiment, the information corresponding to the RLUE device may include: a Next Generation Application Protocol Identifier (NGAP ID) corresponding to the RLUE, and an AMF identifier corresponding to the RLUE. For example, the information corresponding to RLUE device 1104 may include: the NGAP ID corresponding to RLUE 1104, and the AMF identifier corresponding to AMF 1108 of RLUE 1104.

[0059] In one embodiment, the RMUE device is registered with the core network based on a first AMF, and the RLUE device is linked to the RMUE device using the first AMF that is being used by the RMUE device. For example, RMUE device 1102 registers with the core network 1112 based on AMF 1110. In this example, RLUE device 1104 is linked to RMUE device 1102 using AMF 1110, which is being used by RMUE device 1102. In another embodiment, the RLUE device is registered with the core network based on a first AMF, and the RMUE device is linked to the RLUE device using the first AMF that is being used by the RLUE device. For example, RLUE device 1104 registers with the core network 1112 based on AMF 1108. In this example, RMUE device 1102 is linked to RLUE device 1104 using AMF 1108, which is being used by RLUE device 1106.

[0060] According to some embodiments, the method further includes: linking the RMUE device to the RLUE device using a first AMF by modifying the paging parameters of the RMUE device to align with the paging parameters of the RLUE device. For example, RAN 1100 operates to modify the paging parameters of the RMUE device 1102 to align with the paging parameters of the RLUE device 1104. In another example, RAN 1100 operates to modify the paging parameters of the RMUE device 1102, similarly as described above regarding... Figure 7 As described.

[0061] According to some embodiments, the method further includes: based on the RMUE device moving and becoming directly linked to the radio access network node, disconnecting the RMUE device and the RLUE device. For example, Figure 11 RAN 1100 operates based on RMUE device 1102 moving and becoming directly linked to RAN 1100, terminating the link between RMUE device 1102 and RLUE device 1104 (not shown). In some embodiments, the method further includes sending a message to a first AMF that does not include information corresponding to the RLUE device. In some other embodiments, the first AMF removes the link between the RMUE device and the RLUE device, wherein the first AMF corresponds to the RMUE device. Continuing the previous example, RAN 1100 sends a message to AMF 1108 that does not include information corresponding to the RLUE device 1104. In this example, AMF 1108 corresponds to RMUE device 1102, and AMF 1108 removes the link between RMUE 1102 and RLUE 1104.

[0062] In some other embodiments, a second AMF, different from the first AMF, corresponds to the RMUE device, and the second AMF retrieves the link to the RLUE device. Furthermore, in this embodiment, the first AMF removes the link between the RMUE device and the RLUE device. For example, Figure 11 AMF 1110 is different from AMF 1108, and AMF 1110 corresponds to RMUE device 1102. In this example, AMF 1110 retrieves the link from RLUE device 1104. Furthermore, in this example, AMF 1108 removes the link between RMUE device 1102 and RLUE device 1104.

[0063] In some embodiments, the RLUE device includes a first RLUE device. In this embodiment, the RLUE device moves from the first RLUE device to a second RLUE device. For example, Figure 11 RLUE 1104 includes a first RLUE device 1104, and RMUE device 1102 moves from RLUE 1104 to a second RLUE device 1114. In some embodiments, the method further includes receiving information corresponding to the first RLUE device and the second RLUE device from the RMUE device or the second RLUE device. The method further includes, according to this embodiment, linking the RMUE device to the second RLUE device using a second AMF. Continuing with the previous example, Figure 11 The RAN 1100 shown receives information corresponding to the first RLUE device 1104 and the second RLUE device 1114 from either the RMUE device 1102 or the second RLUE device 1114. In this example, the RAN 110 links the RMUE device 1104 to the RLUE 1114 using the AMF 1110. In this example, the RLUE 1114 is associated with the AMF 1110.

[0064] According to some embodiments, the method further includes: delinking the RMUE device and the first RLUE device based on the RMUE device moving to a second RLUE device different from the first RLUE device. For example, Figure 11The RAN 1100 shown disconnects the link between RMUE device 1102 and RLUE device 1104 based on RMUE device 1102 moving to RLUE device 1114, which is different from RLUE device 1104. In some embodiments, the method further includes sending a registration message to the core network, the registration message including information corresponding to the second RLUE device. For example, RAN 1100 sends a registration message to core network 1112, the registration message including information corresponding to the second RLUE device 1114. According to some embodiments, the information corresponding to the second RLUE device includes: the NGAP ID corresponding to the second RLUE device, and the second AMF identifier corresponding to the second RLUE device. Continuing the previous example, the information corresponding to the second RLUE device 1114 would include: the NGAP ID corresponding to the second RLUE device 1114, and the identifier of the AMF 1110 corresponding to the second RLUE device 1114.

[0065] Based on some embodiments of this disclosure, reference will now be made to Figure 14 Flowcharts and Figure 11 The example AMF nodes 1108 and 1110 are shown to discuss the core network CN node 1000 (using...). Figure 10 The operation is implemented using a structure. For example, modules can be stored in... Figure 10 The modules are stored in the memory 1005, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding CN node processing circuit 1003, the processing circuit 1003 performs the corresponding operation of the flowchart.

[0066] Figure 14 A method for operating a core network node according to an embodiment of the present disclosure to link a remote user equipment (RMUE) device to a relay user equipment (RLUE) device in a communication network is illustrated. Figure 14 The method is illustrated by: receiving a message 1300 regarding a first AMF, including data corresponding to an RLUE device, from a radio access network node, and receiving the message into the core network. For example, Figure 11 The AMF 1108 shown receives a message from RAN node 1100 containing data corresponding to RLUE device 1104 regarding AMF 1108, and receives this message into core network 1112. (Return) Figure 14 The method includes: linking the RMUE device 1302 to the RLUE device based on the message. Continuing the previous example, based on a message about AMF 1108 including data corresponding to RLUE device 1104, AMF 1108 links the RMUE device 1102 to the RLUE device.

[0067] According to some embodiments, the method includes receiving a registration message in a core network, the registration message including information corresponding to an RLUE device. In some embodiments, the information corresponding to the RLUE device includes: a Next Generation Application Protocol Identifier (NGAP ID) corresponding to the RLUE, and an AMF identifier corresponding to the RLUE. For example, Figure 11 The AMF 1108 receives a registration message, which includes information corresponding to the RLUE device 1104. The registration message includes: the NGPID corresponding to the RLUE 1104, and the AMF identifier corresponding to the RLUE 1104.

[0068] In some embodiments, the RMUE device is registered with the core network based on a first AMF, and the RLUE is linked to the RMUE using the first AMF that is being used by the RMUE. For example, Figure 11 The illustrated RMUE device 1102 registers with the core network 1112 based on AMF 1108, and uses AMF 1108, which is being used by RMUE 1102, to link RLUE 1104 to RMUE 1102. In some other embodiments, the RLUE device registers with the core network based on a first AMF, and uses the first AMF, which is being used by the RLUE, to link RMUE to RLUE. For example, Figure 11 The RMUE device 1102 shown registers with the core network 1112 based on AMF 1108, and uses AMF 1108 to link RLUE 1104 to RMUE 1102 based on AMF 1108 being used by RLUE 1104.

[0069] According to some embodiments, the method further includes: linking the RMUE device to the RLUE device using a first AMF by modifying the paging parameters of the RMUE device to align with the paging parameters of the RLUE device. For example, Figure 11 The AMF 1108 modifies the paging parameters of RMUE device 1102 to align with the paging parameters of RLUE device 1104. The method also includes: based on the RMUE device moving and becoming directly linked to the core network node, disconnecting the RMUE device and the RLUE device. For example, Figure 11The AMF 1108, based on the RMUE device 1102 moving and becoming directly linked to the AMF 1108, disconnects the RMUE device 1102 and the RLUE device 1104. In this embodiment, the method may further include: receiving a message associated with the RMUE device, the message not including information corresponding to the RLUE device. Continuing the previous example, the AMF 1108 receives a message associated with the RMUE device 1102, the message not including information corresponding to the RLUE device 1104. In one embodiment, the first AMF corresponds to the RMUE device, and the first AMF removes the link between the RMUE and the RLUE. For example, Figure 11 The AMF 1108 shown corresponds to the RMUE device 1102, and the AMF 1108 removes the link between the RMUE 1102 and the RLUE 1104.

[0070] In some other embodiments, a second AMF, different from the first AMF, corresponds to the RMUE device, and the second AMF retrieves the link to the RLUE device. In this embodiment, the first AMF removes the link between the RMUE device and the RLUE device. For example, Figure 11 The AMF 1110 shown is different from the AMF 1108 corresponding to RMUE device 1102. In this example, AMF 1110 retrieves the link from RLUE device 1104. AMF 1108 removes the link between RMUE 1102 and RLUE 1104.

[0071] According to some embodiments, the RLUE device includes a first RLUE device, and the RMUE device moves from the first RLUE device to a second RLUE device. For example, Figure 11 RLUE 1104 includes a first RLUE device 1104, and RMUE device 1102 moves from RLUE 1104 to a second RLUE device 1114. In some embodiments, the method further includes receiving information corresponding to the first RLUE device and the second RLUE device. For example, AMF 1108 receives information corresponding to RLUE device 1104 and RLUE device 1114. In this embodiment, the method further includes linking the RMUE device to the second RLUE device. In this example, AMF 1108 links the RMUE device 1102 to RLUE device 1114.

[0072] In some embodiments, the method further includes: disconnecting the RMUE device and the first RLUE device based on the RMUE device moving to a second RLUE device different from the first RLUE device. For example, based on the RMUE 1102 moving to RLUE 1114 different from RLUE 1104, AMF 1108 disconnects the RMUE device 1102 and RLUE device 1104. According to some embodiments, the method further includes: receiving a registration message in the core network, the registration message including information corresponding to the second RLUE device. In this embodiment, the information corresponding to the second RLUE device includes: the NGAP ID corresponding to the second RLUE device, and a second AMF identifier corresponding to the RLUE device. Continuing the previous example, AMF 1108 receives a registration message including information corresponding to RLUE device 1114. The information corresponding to RLUE device 1114 includes: the NGAP ID corresponding to RLUE device 1114, and a second AMF identifier corresponding to RLUE device 1114. In this example, the second AMF identifier identifies AMF 1110 as corresponding to RLUE device 1114.

[0073] The following discusses example implementations.

[0074] Example 1. A method for operating a radio access network node to link a remote user equipment (RMUE) device to a relay user equipment (RLUE) device in a communication network, the method comprising:

[0075] Receive a message from either the RMUE device or the RLUE device, the message including information corresponding to the RMUE device or RLUE device, the RMUE device or RLUE device having a connection established between a radio access network node and the corresponding RMUE device or RLUE device using a first access and mobility management function (AMF); and

[0076] Use the first AMF to link the RMUE device to the RLUE device.

[0077] Example 2. The method according to Example 1 further includes: sending a message to the core network about the first AMF including data corresponding to the RLUE device or the RMUE device.

[0078] Example 3. The method according to Example 1 further includes: sending a registration message to the core network, the registration message including information corresponding to the RLUE device.

[0079] Example 4. According to the method described in Example 3, the information corresponding to the RLUE device includes: a Next Generation Application Protocol Identifier (NGAP ID) corresponding to the RLUE device; and an AMF identifier corresponding to the RLUE device.

[0080] Example 5. According to the method of Example 1, wherein the RMUE device registers with the core network based on the first AMF, and wherein the RLUE device is linked to the RMUE device using the first AMF based on the first AMF used by the RMUE device.

[0081] Example 6. According to the method of Example 1, the RLUE device is registered with the core network based on the first AMF, and the RMUE device is linked to the RLUE device device using the first AMF based on the first AMF being used by the RLUE.

[0082] Example 7. According to the method of Example 1, linking the RMUE device to the RLUE device using the first AMF includes: modifying the paging parameters of the RMUE device to align with the paging parameters of the RLUE device.

[0083] Example 8. The method according to Example 1 further includes: based on the RMUE device moving and becoming directly linked to the radio access network node, disconnecting the RMUE device and the RLUE device.

[0084] Example 9. The method according to Example 8 further includes: sending a message to the AMF device, the message not including information corresponding to the RLUE device.

[0085] Example 10. The method according to any one of Examples 8 and 9, wherein the first AMF corresponds to the RMUE device, and wherein the first AMF removes the link between the RMUE device and the RLUE device.

[0086] Example 11. The method according to Example 8, wherein the second AMF, different from the first AMF, corresponds to the RMUE device, wherein the second AMF retrieves the link of the RLUE device, and

[0087] Specifically, the first AMF removes the link between the RMUE device and the RLUE device.

[0088] Example 12. The method according to Example 1, wherein the RLUE device includes a first RLUE device, wherein the RMUE device moves from the first RLUE device to a second RLUE device, and the method further includes:

[0089] Receive information corresponding to the first RLUE device and the second RLUE device from the RMUE device or the second RLUE device; and

[0090] Use the second AMF to link the RMUE device to the second RLUE device.

[0091] Example 13. According to the method of Example 1, wherein the RLUE device includes a first RLUE device, the method further includes: disconnecting the RMUE device and the first RLUE device based on the RMUE device moving to a second RLUE device different from the first RLUE device.

[0092] Example 14. According to the embodiment described in Example 13, it further includes: sending a registration message to the core network, the registration message including information corresponding to the second RLUE device.

[0093] Example 15. According to the embodiment described in Example 14, the information corresponding to the second RLUE device includes: a Next Generation Application Protocol Identifier (NGAP ID) corresponding to the second RLUE device; and a second AMF identifier corresponding to the second RLUE device.

[0094] Example 16. A radio access network (RAN) node, comprising:

[0095] Processing circuitry; and

[0096] A memory, coupled to processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the RAN node to perform the operations described in any one of embodiments 1 to 15.

[0097] Example 17. A computer program comprising program code to be executed by processing circuitry of a radio access network (RAN) node, wherein execution of the program code causes the RAN node to perform the operations described in any one of Examples 1 to 15.

[0098] Example 18. A method for operating a network node to link a Remote User Equipment (RMUE) device to a Relay User Equipment (RLUE) device in a communication network, the method comprising:

[0099] Receive a message from the radio access network node regarding the first AMF, including data corresponding to the RLUE device, and receive the message into the core network; and

[0100] Based on this message, the RMUE device is linked to the RLUE device.

[0101] Example 19. The method according to Example 18 further includes: receiving a registration message in the core network, the registration message including information corresponding to the RLUE device.

[0102] Example 20. The method according to Example 19, wherein the information corresponding to the RLUE device includes: a next-generation application protocol identifier corresponding to the RLUE device; and an AMF identifier corresponding to the RLUE device.

[0103] Example 22. The method according to Example 18, wherein the RMUE device registers with the core network based on a first AMF, and wherein the RLUE is linked to the RMUE device using the first AMF based on the first AMF used by the RMUE device.

[0104] Example 23. The method according to Example 18, wherein the RLUE device is registered with the core network based on the first AMF, and wherein the RMUE device is linked to the RLUE device device using the first AMF based on the first AMF being used by the RLUE.

[0105] Example 24. The method according to Example 18, wherein linking the RMUE device to the RLUE device using the first AMF includes: modifying the paging parameters of the RMUE device to align with the paging parameters of the RLUE device.

[0106] Example 25. The method according to Example 18 further includes: disconnecting the RMUE device and the RLUE device based on the RMUE device moving and becoming directly linked to the radio access network node.

[0107] Example 26. The method according to Example 25 further includes: receiving a message associated with an RMUE device, the message not including information corresponding to an RLUE device.

[0108] Example 27. The method according to any one of Examples 25 and 26, wherein the first AMF corresponds to the RMUE device, and wherein the first AMF removes the link between the RMUE device and the RLUE device.

[0109] Example 28. The method according to Example 25, wherein the second AMF, different from the first AMF, corresponds to the RMUE device, wherein the second AMF retrieves the link of the RLUE device, and

[0110] Specifically, the first AMF removes the link between the RMUE device and the RLUE device.

[0111] Example 29. The method according to Example 18, wherein the RLUE device includes a first RLUE device.

[0112] The method further includes: RMUE device moving from first RLUE device to second RLUE device;

[0113] Receive information corresponding to the first RLUE device and the second RLUE device; and

[0114] Link the RMUE device to the second RLUE device.

[0115] Example 30. The method according to Example 18, wherein the RLUE device includes a first RLUE device, and the method further includes: disconnecting the RMUE device and the first RLUE device based on the RMUE device moving to a second RLUE device different from the first RLUE device.

[0116] Example 31. The method according to Example 30 further includes: receiving a registration message in the core network, the registration message including information corresponding to the second RLUE device.

[0117] Example 32. According to the embodiment described in Example 31, the information corresponding to the second RLUE device includes: a Next Generation Application Protocol Identifier (NGAP ID) corresponding to the second RLUE; and a second AMF identifier corresponding to the second RLUE.

[0118] Example 33. A core network CN node, comprising:

[0119] Processing circuitry; and

[0120] A memory coupled to processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the CN node to perform the operations described in any of embodiments 18 to 32.

[0121] The references are as follows.

[0122] 3GPP TS 38.300

[0123] 3GPP TS 38.331

[0124] 3GPP TS 23.502

[0125] 3GPP TS 36.746

[0126] 3GPP TS 23.733

[0127] 3GPP TS 23.752

[0128] Additional notes are provided below.

[0129] Generally, unless explicitly stated and / or implied from the context, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to “an element, device, component, apparatus, step, etc.” shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. Unless it must be explicitly described that a step is after or before another step and / or implicitly implied that a step must be after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Further objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0130] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0131] Figure 14 A wireless network according to some embodiments is shown.

[0132] While the subjects described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein pertain to wireless networks (e.g., Figure 14 The example wireless network shown is described. For simplicity, Figure 14 The wireless network depicted only includes network 4106, network nodes 4160 and 4160b, and WD 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 4160 and wireless device (WD) 4110 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0133] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems, and / or interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network can implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards (e.g., IEEE 802.11); and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0134] Network 4106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0135] Network node 4160 and WD 4110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components that can facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections).

[0136] As used herein, a network node refers to a device capable of, configured, deployed, and / or operatively communicating directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified based on the coverage they provide (or, in other words, based on their transmit power levels), and thus they can also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). These remote radio units may be integrated with an antenna to form an antenna-integrated radio, or they may not be integrated with an antenna to form an antenna-integrated radio. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (e.g., MSRBS), network controllers (e.g., Radio Network Controller (RNC) or Base Station Controller (BSC)), base transceiver stations (BTS), transmitting points, transmitting nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless communication network for wireless devices, or to provide some service to wireless devices already connected to the wireless network.

[0137] exist Figure 14 In this network node 4160, processing circuitry 4170, device-readable medium 4180, interface 4190, auxiliary equipment 4184, power supply 4186, power supply circuitry 4187, and antenna 4162 are included. Although Figure 14The network node 4160 shown in the exemplary wireless network may represent a device including a combination of the illustrated hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 4160 are depicted as a single box within a larger box, or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 4180 may include multiple separate hard disk drives and multiple RAM modules).

[0138] Similarly, network node 4160 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own corresponding components. In some scenarios where network node 4160 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some cases. In some embodiments, network node 4160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 4180 for different RATs), and some components may be reused (e.g., the same antenna 4162 may be shared by the RATs). Network node 4160 may also include multiple sets of various illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 4160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 4160.

[0139] Processing circuitry 4170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by processing circuitry 4170 may include information acquired by processing circuitry 4170 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0140] Processor circuitry 4170 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide network node 4160 functionality, either alone or together with other network node 4160 components (e.g., device-readable medium 4180). For example, processing circuitry 4170 may execute instructions stored in device-readable medium 4180 or in memory stored within processing circuitry 4170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 4170 may include a system-on-a-chip (SoC).

[0141] In some embodiments, the processing circuitry 4170 may include one or more of a radio frequency (RF) transceiver circuitry 4172 and a baseband processing circuitry 4174. In some embodiments, the RF transceiver circuitry 4172 and the baseband processing circuitry 4174 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 4172 and the baseband processing circuitry 4174 may be on the same chip or chipset, board, or unit group.

[0142] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 4170, which executes instructions stored on device-readable medium 4180 or memory within processing circuitry 4170. In alternative embodiments, some or all of the functions may be provided by processing circuitry 4170, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 4170 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 4170 or other components of network node 4160, but are enjoyed as a whole by network node 4160 and / or generally by end users and wireless networks.

[0143] Device-readable medium 4180 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted storage, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuitry 4170. Device-readable medium 4180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuitry 4170 and used by network node 4160. Device-readable medium 4180 may be used to store any calculations performed by processing circuitry 4170 and / or any data received via interface 4190. In some embodiments, the processing circuitry 4170 and the device-readable medium 4180 may be considered as integrated.

[0144] Interface 4190 is used for wired or wireless communication of signaling and / or data between network node 4160, network 4106, and / or WD 4110. As shown, interface 4190 includes a port / terminal 4194 for sending and receiving data to and from network 4106, for example, via a wired connection. Interface 4190 also includes radio front-end circuitry 4192, which may be coupled to antenna 4162, or is part of antenna 4162 in some embodiments. Radio front-end circuitry 4192 includes filter 4198 and amplifier 4196. Radio front-end circuitry 4192 may be connected to antenna 4162 and processing circuitry 4170. Radio front-end circuitry 4192 may be configured to modulate the signals communicating between antenna 4162 and processing circuitry 4170. Radio front-end circuitry 4192 may receive digital data that will be transmitted wirelessly to other network nodes or WD. The radio front-end circuit 4192 can use a combination of filter 4198 and / or amplifier 4196 to convert digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 can collect radio signals, which are then converted into digital data by the radio front-end circuit 4192. The digital data can be passed to processing circuitry 4170. In other embodiments, the interface may include different components and / or different combinations of components.

[0145] In some alternative embodiments, network node 4160 may not include a separate radio front-end circuitry 4192. Instead, processing circuitry 4170 may include radio front-end circuitry and may be connected to antenna 4162 without requiring a separate radio front-end circuitry 4192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 4172 may be considered part of interface 4190. In other embodiments, interface 4190 may include one or more ports or terminals 4194, radio front-end circuitry 4192, and RF transceiver circuitry 4172 as part of a radio unit (not shown), and interface 4190 may communicate with baseband processing circuitry 4174, which is part of a digital unit (not shown).

[0146] Antenna 4162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 4162 may be coupled to radio front-end circuitry 4192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 4162 may include one or more omnidirectional, sector, or planar antennas operably transmitting / receiving radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals relative to a device within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 4162 may be separate from network node 4160 and may be connected to network node 4160 via an interface or port.

[0147] Antenna 4162, interface 4190, and / or processing circuitry 4170 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 4162, interface 4190, and / or processing circuitry 4170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0148] Power supply circuit 4187 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 4160 for performing the functions described herein. Power supply circuit 4187 may receive power from power source 4186. Power source 4186 and / or power supply circuit 4187 may be configured to provide power to various components of network node 4160 in a manner suitable for the individual components (e.g., at the voltage and current levels required by each respective component). Power source 4186 may be included in or external to power supply circuit 4187 and / or network node 4160. For example, network node 4160 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a cable, thereby supplying power to power supply circuit 4187. As another example, power source 4186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 4187. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0149] Alternative embodiments of network node 4160 may include more than Figure 14 Additional components of the illustrated components may be responsible for providing certain aspects of the functionality of the network node (including any of the functionalities described herein and / or any functionality required to support the subject matter described herein). For example, network node 4160 may include a user interface device to allow information to be input into and output from network node 4160. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 4160.

[0150] As used herein, a wireless device (WD) means a device capable of, configured, positioned, and / or operable for wireless communication with network nodes and / or other wireless devices. Unless otherwise stated, the term WD is used interchangeably with User Equipment (UE) herein. Wireless communication may include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, portable computers, portable embedded devices (LEEs), portable-installed devices (LMEs), smart devices, wireless client devices (CPEs), in-vehicle wireless terminal devices, etc. A UE can, for example, support device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-anything (V2X) communication by implementing 3GPP standards for sidelink communication, and in this case, can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which in the 3GPP context can be referred to as an MTC device. As a specific example, a WD can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machines, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a UE can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As mentioned above, WD can represent a wireless connection endpoint, in which case the device can be referred to as a wireless terminal. Furthermore, as mentioned above, UE can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0151] As shown in the figure, wireless device 4110 includes an antenna 4111, an interface 4114, processing circuitry 4120, a device-readable medium 4130, a user interface device 4132, auxiliary devices 4134, a power supply 4136, and a power supply circuit 4137. WD 4110 may include one or more of the components shown for various wireless technologies supported by WD 4110 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within WD 4110.

[0152] Antenna 4111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and connected to interface 4114. In some alternative embodiments, antenna 4111 may be separate from WD 4110 and may be connected to WD 4110 via an interface or port. Antenna 4111, interface 4114, and / or processing circuitry 4120 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 4111 may be considered as an interface.

[0153] As shown in the figure, interface 4114 includes radio front-end circuitry 4112 and antenna 4111. Radio front-end circuitry 4112 includes one or more filters 4118 and amplifiers 4116. Radio front-end circuitry 4112 is connected to antenna 4111 and processing circuitry 4120 and is configured to modulate the signal communicating between antenna 4111 and processing circuitry 4120. Radio front-end circuitry 4112 may be coupled to antenna 4111 or is part of antenna 4111. In some embodiments, WD 4110 may not include separate radio front-end circuitry 4112; instead, processing circuitry 4120 may include radio front-end circuitry and may be connected to antenna 4111. Similarly, in some embodiments, some or all of RF transceiver circuitry 4122 may be considered part of interface 4114. Radio front-end circuitry 4112 can receive digital data that will be transmitted wirelessly to other network nodes or WD. The radio front-end circuit 4112 can use a combination of filter 4118 and / or amplifier 4116 to convert digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 can collect radio signals, which are then converted into digital data by the radio front-end circuit 4112. The digital data can be passed to processing circuitry 4120. In other embodiments, the interface may include different components and / or different combinations of components.

[0154] Processor circuitry 4120 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide WD 4110 functionality, either alone or together with other WD 4110 components (e.g., device-readable medium 4130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 4120 may execute instructions stored in device-readable medium 4130 or in memory within processing circuitry 4120 to provide the functionality disclosed herein.

[0155] As shown in the figure, the processing circuit 4120 includes one or more of an RF transceiver circuit 4122, a baseband processing circuit 4124, and an application processing circuit 4126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 4120 of WD 4110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126 may be on a separate chip or chipset. In an alternative embodiment, a portion or all of the baseband processing circuit 4124 and the application processing circuit 4126 may be combined into a single chip or chipset, and the RF transceiver circuit 4122 may be on a separate chip or chipset. In another alternative embodiment, a portion or all of the RF transceiver circuit 4122 and the baseband processing circuit 4124 may be on the same chip or chipset, and the application processing circuit 4126 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 4122 may be part of interface 4114. The RF transceiver circuit 4122 may modulate the RF signal used for processing circuit 4120.

[0156] In some embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuitry 4120 that executes instructions stored on device-readable medium 4130, which may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 4120, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of those particular embodiments, processing circuitry 4120 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 4120 or other components of WD 4110, but are enjoyed as a whole by WD 4110 and / or generally by end users and wireless networks.

[0157] Processing circuitry 4120 can be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. These operations performed by processing circuitry 4120 may include information acquired by processing circuitry 4120 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored by WD 4110, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0158] Device-readable medium 4130 operatively stores computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 4120. Device-readable medium 4130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry 4120. In some embodiments, processing circuitry 4120 and device-readable medium 4130 may be considered integrated.

[0159] User interface device 4132 can provide components that allow a human user to interact with WD 4110. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 4132 is operable to produce output to the user and allow the user to provide input to WD 4110. The type of interaction can vary depending on the type of user interface device 4132 installed in WD 4110. For example, if WD 4110 is a smartphone, interaction can be made via a touchscreen; if WD 4110 is a smart meter, interaction can be made via a screen providing a purpose (e.g., the number of gallons used) or a speaker providing an audible alarm (e.g., if smoke is detected). User interface device 4132 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 4132 is configured to allow information to be input into WD 4110 and is connected to processing circuitry 4120 to allow processing circuitry 4120 to process the input information. User interface device 4132 can include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 4132 is also configured to allow information output from WD 4110 and to allow processing circuitry 4120 to output information from WD 4110. User interface device 4132 may include, for example, a speaker, display, vibration circuitry, a USB port, a headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of user interface device 4132, WD 4110 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0160] Auxiliary device 4134 is operable to provide more specific functions that may not typically be performed by the WD. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The contents and types of components of auxiliary device 4134 may vary depending on the embodiment and / or scenario.

[0161] In some embodiments, power supply 4136 may be in the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery cell. WD 4110 may also include power circuitry 4137 for supplying power from power supply 4136 to various parts of WD 4110 that require power from power supply 4136 to perform any functions described or indicated herein. In some embodiments, power circuitry 4137 may include power management circuitry. Power circuitry 4137 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 4110 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry 4137 may also be operable to supply power from an external power source to power supply 4136. This may be used, for example, for charging power supply 4136. Power circuitry 4137 may perform any formatting, conversion, or other modifications on the power from power supply 4136 to suit the power supply for the various components of WD 4110 that are powered thereto.

[0162] Figure 15 A user device according to some embodiments is shown.

[0163] Figure 15 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, "User Equipment" or "UE" may not necessarily have the meaning of a "user" in the sense of a human user who owns and / or operates the associated equipment. Alternatively, a UE may refer to a device intended to be sold to or operated by a human user but may not or initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 42200 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 15 As shown, UE 4200 is an example of a WD configured for communication according to one or more communication standards (e.g., 3GPP's GSM, UMTS, LTE, and / or 5G standards) published by the 3rd Generation Partnership Project (3GPP). As previously stated, the terms WD and UE are used interchangeably. Therefore, although... Figure 15 This is for UE, but the components discussed in this article also apply to WD, and vice versa.

[0164] exist Figure 15In this embodiment, UE 4200 includes processing circuitry 4201 operatively coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connectivity interface 4211, a memory 4215 including random access memory (RAM) 4217, read-only memory (ROM) 4219, and a storage medium 4221, a communication subsystem 4231, a power supply 4213, and / or any other component, or any combination thereof. Storage medium 4221 includes an operating system 4223, application programs 4225, and data 4227. In other embodiments, storage medium 4221 may include other similar types of information. Some UEs may use... Figure 15 All components can be shown, or only a subset of components can be used. The level of integration between components can vary from one UE to another. Furthermore, some UEs can contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0165] exist Figure 15 In this embodiment, processing circuitry 4201 can be configured to process computer instructions and data. Processor 4201 can be configured to execute any sequential state machine containing machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and suitable firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and suitable software; or any combination thereof. For example, processing circuitry 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0166] In the depicted embodiments, the input / output interface 4205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 4200 can be configured to use an output device via the input / output interface 4205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 4200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 4200 can be configured to use an input device via the input / output interface 4205 to allow a user to capture information into the UE 4200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional keyboard, a touchpad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, another type of sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0167] exist Figure 15 In this configuration, RF interface 4209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network interface 4211 can be configured to provide a communication interface to network 4243a. Network 4243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 4243a may include a Wi-Fi network. Network interface 4211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network interface 4211 can implement receiver and transmitter functions suitable for the communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components or software, or alternatively, may be implemented separately.

[0168] RAM 4217 can be configured to interface with processing circuitry 4201 via bus 4202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 4219 can be configured to provide computer instructions or data to processing circuitry 4201. For example, ROM 4219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 4221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In one example, storage medium 4221 can be configured to include operating system 4223, application 4225 such as a web browser application, widget or utility engine or another application, and data file 4227. Storage medium 4221 can store any one or a combination of various operating systems for use by UE 4200.

[0169] Storage medium 4221 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile optical disc (HD-DVD) drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory such as a user identification module or a removable user identifier (SIM / RUIM) module, other memory, or any combination thereof. Storage medium 4221 can allow UE 4200 to access computer-executable instructions, applications, etc., stored on a transient or non-transient storage medium to unload or upload data. Articles such as those utilizing a communication system can be tangibly embodied in storage medium 4221, which may include a device-readable medium.

[0170] exist Figure 15In this configuration, processing circuitry 4201 can be configured to communicate with network 4243b using communication subsystem 4231. Networks 4243a and 4243b can be one or more of the same networks or one or more different networks. Communication subsystem 4231 can be configured to include one or more transceivers for communicating with network 4243b. For example, communication subsystem 4231 can be configured to include one or more remote transceivers for communicating with another device (e.g., another WD, UE) or a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 4233 and / or receiver 4235 to implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for the RAN link, respectively. Furthermore, the transmitter 4233 and receiver 4235 of each transceiver can share circuit components, software, or firmware, or they can be implemented separately.

[0171] In the illustrated embodiment, the communication functions of the communication subsystem 4231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as the use of a Global Positioning System (GPS) for determining location), another type of communication function, or any combination thereof. For example, the communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 4243b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 4243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 4213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 4200.

[0172] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 4200 or divided among multiple components of UE 4200. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 4231 may be configured to include any of the components described herein. Additionally, the processing circuitry 4201 may be configured to communicate with any such component via bus 4202. In another example, any such component may be represented by program instructions stored in memory, which, when executed by the processing circuitry 4201, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between the processing circuitry 4201 and the communication subsystem 4231. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0173] Figure 16 A virtualized environment according to some embodiments is shown.

[0174] Figure 16 This is a schematic block diagram illustrating a virtualized environment 4300, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication equipment) or components thereof, and relates to an implementation in which at least some partial functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0175] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted on one or more hardware nodes 4330. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may then be fully virtualized.

[0176] These functionalities can be implemented by one or more applications 4320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Application 4320 runs in a virtualization environment 4300, which provides hardware 4330 including processing circuitry 4360 and memory 4390. Memory 4390 contains instructions 4395 executable by processing circuitry 4360, thereby enabling application 4320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0177] The virtualization environment 4300 includes general-purpose or special-purpose network hardware devices 4330, which include one or more processors or processing circuitry 4360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 4390-1, which may be non-permanent memory for temporarily storing instructions 4395 or software executed by the processing circuitry 4360. Each hardware device may include one or more network interface controllers (NICs) 4370, also referred to as network interface cards, which include physical network interfaces 4380. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 4390-2 in which the software 4395 and / or instructions executable by the processing circuitry 4360 are stored. The software 4395 may include any type of software, including software for instantiating one or more virtualization layers 4350 (also referred to as hypervisors), software for executing virtual machines 4340, and software that allows them to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0178] Virtual machine 4340 includes virtual processing, virtual memory, virtual networking or interface, and virtual storage, and can be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of virtual device 4320 can be implemented on one or more of virtual machines 4340, and this implementation can be made in different ways.

[0179] During operation, the processing circuitry 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 4350 can present a virtual operating platform that appears as networked hardware of the virtual machine 4340.

[0180] like Figure 16As shown, hardware 4330 can be a standalone network node with general or specific components. Hardware 4330 may include antenna 43225 and may implement some functions through virtualization. Alternatively, hardware 4330 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and coordination (MANO) 43100, which in particular oversees the lifecycle management of application 4320.

[0181] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0182] In the context of NFV, virtual machine 4340 can be a software implementation of a physical machine, and its running programs are executed as if they were running on a physical, non-virtualized machine. Each virtual machine 4340, along with the portion of hardware 4330 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in virtual machine 4340), forms a separate virtual network element (VNE).

[0183] Still within the context of NFV, Virtual Network Functions (VNFs) are responsible for handling one or more virtual machines 4340 running on top of the hardware network infrastructure 4330 and corresponding to... Figure 16 The application of 4320 specific network functions.

[0184] In some embodiments, each of the one or more radio units 43200, including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio unit 43200 may communicate directly with the hardware node 4330 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0185] In some embodiments, the control system 43230 may be used to implement some signaling, and the control system 4230 may alternatively be used for communication between the hardware node 4330 and the radio unit 43200.

[0186] Figure 17 A telecommunications network connected to a host computer via an intermediate network is shown according to some embodiments.

[0187] refer to Figure 17According to an embodiment, the communication system includes: a telecommunications network 4410, such as a 3GPP-type cellular network, which includes an access network 4411 (such as a radio access network) and a core network 4414. The access network 4411 includes multiple base stations 4412a, 4412b, and 4412c, such as NB, eNB, gNB, or other types of wireless access points, each base station defining a corresponding coverage area 4413a, 4413b, or 4413c. Each base station 4412a, 4412b, or 4412c can be connected to the core network 4414 via a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to or be paged by the corresponding base station 4412c. A second UE 4492 located in coverage area 4413a can wirelessly connect to the corresponding base station 4412a. Although multiple UEs 4491 and 4492 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is located in the coverage area or a single UE is connected to the corresponding base station 4412.

[0188] Telecommunications network 4410 is connected to host computer 4430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server cluster. Host computer 4430 may be owned by or under the control of a service provider, or may be operated by or on behalf of a service provider. Connections 4421 and 4422 between telecommunications network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430, or may pass through optional intermediate network 4420. Intermediate network 4420 may be one or more of a public, private, or hosted network; intermediate network 4420 (if any) may be a backbone network or the Internet; specifically, intermediate network 4420 may include two or more subnetworks (not shown).

[0189] Figure 17The communication system as a whole enables connectivity between connected UEs 4491 and 4492 and host computer 4430. This connection can be described as an over-the-top (OTT) connection 4450. Host computer 4430 and connected UEs 4491 and 4492 are configured to transmit data and / or signaling via OTT connection 4450 using access network 4411, core network 4414, any intermediate network 4420, and possibly other intermediate infrastructure (not shown). The participating communication devices through which OTT connection 4450 passes are unaware of the routes of uplink and downlink communications; in this sense, OTT connection 4450 can be transparent. For example, base station 4412 may not be informed, or need not be informed, about the past routes of incoming downlink communications containing data originating from host computer 4430 and to be forwarded (e.g., handed over) to connected UE 4491. Similarly, base station 4412 does not need to know the future routes of uplink communications originating from UE 4491 and outputting toward host computer 4430.

[0190] Figure 18 A host computer is shown communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments;

[0191] Now refer to Figure 18 The following describes an example implementation of the UE, base station, and host computer according to the embodiments discussed in the preceding paragraphs. In the communication system 4500, the host computer 4510 includes hardware 4515, which includes a communication interface 4516 configured to establish and maintain a wired or wireless connection with interfaces of different communication devices of the communication system 4500. The host computer 4510 also includes processing circuitry 4518, which may have storage and / or processing capabilities. In particular, the processing circuitry 4518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) adapted to execute instructions. The host computer 4510 also includes software 4511, which is stored in or accessible by the host computer 4510 and can be executed by the processing circuitry 4518. The software 4511 includes a host application 4512. Host application 4512 can be operated to provide services to remote users, such as UE 4530 connected via OTT connection 4550, which terminates between UE 4530 and host computer 4510. When providing services to remote users, host application 4512 can provide user data sent using OTT connection 4550.

[0192] The communication system 4500 also includes a base station 4520 disposed in the telecommunications system. The base station 4520 includes hardware 4525 enabling it to communicate with the host computer 4510 and the UE 4530. Hardware 4525 may include: a communication interface 4526 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 4500; and a radio interface 4527 for establishing and maintaining connections with the coverage area served by the base station 4520 (in...). Figure 18 At least one wireless connection 4570 of UE 4530 (not shown in the diagram). Communication interface 4526 can be configured to facilitate connection 4560 to host computer 4510. Connection 4560 can be a direct connection, or alternatively, the connection can be through the core network of a telecommunications network (in the diagram). Figure 18 (Not shown) and / or via one or more intermediate networks outside the telecommunications network. In the illustrated embodiment, the hardware 4525 of the base station 4520 also includes processing circuitry 4528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 4520 also has software 4521 stored internally or accessible via an external connection.

[0193] The communication system 4500 also includes the previously mentioned UE 4530. The hardware 4535 of the UE 4530 may include a radio interface 4537 configured to establish and maintain a wireless connection 4570 with a base station serving the coverage area currently occupied by the UE 4530. The hardware 4535 of the UE 4530 also includes processing circuitry 4538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. The UE 4530 also includes software 4531, which is stored in or accessible by the UE 4530 and can be executed by the processing circuitry 4538. The software 4531 includes a client application 4532. The client application 4532 can be operated to provide services to human or non-human users via the UE 4530, with the support of the host computer 4510. In host computer 4510, the executing host application 4512 can communicate with the executing client application 4532 via OTT connection 4550, which terminates between UE 4530 and host computer 4510. When providing services to a user, client application 4532 can receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 can transmit both request data and user data. Client application 4532 can interact with the user to generate the user data it provides.

[0194] It should be noted that Figure 18 The host computer 4510, base station 4520, and UE 4530 shown can be respectively connected to... Figure 17 The host computer 4430, one of the base stations 4412a, 4412b, and 4412c, and one of the UEs 4491 and 4492 are similar to or equivalent to each other. That is, the internal workings of these entities can be as follows: Figure 18 As shown, and independently, the surrounding network topology can be Figure 17 The network topology.

[0195] exist Figure 18 The OTT connection 4550 is abstractly depicted to illustrate communication between host computer 4510 and UE 4530 via base station 4520, but no intermediate devices or the exact routing messages via these devices are explicitly mentioned. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 4530 or the service provider operating host computer 4510, or both. When OTT connection 4550 is active, the network infrastructure can also make dynamic decisions to change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0196] The wireless connection 4570 between UE 4530 and base station 4520 is consistent with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments can improve the performance of OTT services provided to UE 4530 using OTT connection 4550, in which wireless connection 4570 forms the final part. More specifically, the teachings of these embodiments can improve random access speed and / or reduce random access failure rate, and thus provide benefits such as faster and / or more reliable random access.

[0197] Measurement procedures may be provided for monitoring data rates, latency, and other factors that are the subject of improvement in one or more embodiments. Optional network functions may also be present for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 4550 may be implemented in the software 4511 and hardware 4515 of the host computer 4510, or in the software 4531 and hardware 4535 of the UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 4550 traverses; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the software 4511, 4531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 4550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect the base station 4520 and may be unknown or imperceptible to the base station 4520. Such processes and functions may be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, which facilitates the host computer 4510 in measuring throughput, propagation time, latency, etc. Measurements may be achieved by software 4511 and 4531 using the OTT connection 4550 to send messages (especially empty messages or "virtual" messages) while simultaneously monitoring propagation time, errors, etc.

[0198] Figure 19 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0199] Figure 19 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 15 and Figure 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 19 Reference numerals are used in the accompanying drawings. In step 4610, the host computer provides user data. In sub-step 4611 of step 4610 (which may be optional), the host computer provides user data by executing a host application. In the second step 4620, the host computer initiates a transmission to the UE carrying user data. In the third step 4630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the host computer-initiated transmission to the UE. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0200] Figure 20 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0201] Figure 20 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 15 and Figure 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 20 Reference numerals are used in the accompanying drawings. In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In a second step 4720, the host computer initiates a transmission to the UE carrying user data. According to the teachings of the embodiments described throughout this disclosure, the transmission can be carried out via a base station. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0202] Figure 21 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0203] Figure 21 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 15 and Figure 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 21 Reference numerals are used in the accompanying drawings. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in a second step 4820, the UE provides user data. In a sub-step 4821 of step 4820 (which may be optional), the UE provides user data by executing a client application. In a sub-step 4811 of step 4810 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in a third sub-step 4830 (which may be optional). In step 4840 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0204] Figure 22 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0205] Figure 22 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 15 and Figure 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 22 Reference numerals are used in the accompanying drawings. In step 4910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 4920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In a third step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0206] Any suitable steps, methods, features, functions, or benefits disclosed herein can be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by processing circuitry, which may include one or more microprocessors or microcontrollers and other digital hardware (including digital signal processors (DSPs), application-specific digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions according to one or an embodiment of this disclosure.

[0207] The term "unit" may have a conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions, such as those described herein.

[0208] abbreviation

[0209] At least some of the following abbreviations may be used in this disclosure. In the event of inconsistencies between abbreviations, the usage above shall prevail. If listed multiple times below, the first listing shall take precedence over any subsequent listing.

[0210] 1x RTT CDMA2000 1x Radio Transmission Technology

[0211] 3GPP Third Generation Partnership Project

[0212] 5G (Fifth Generation)

[0213] ABS almost blank subframe

[0214] ARQ (Automatic Repeat Request)

[0215] AWGN Additive White Gaussian Noise

[0216] BCCH Broadcast Control Channel

[0217] BCH Broadcast Channel

[0218] CA carrier aggregation

[0219] CC carrier component

[0220] CCCH SDU Common Control Channel SDU

[0221] CDMA code division multiplexing access

[0222] CGI Cell Global Identifier

[0223] CIR channel impulse response

[0224] CP cyclic prefix

[0225] CPICH Common Pilot Channel

[0226] CPICH Ec / No CPICH energy received per chip divided by the power density within the frequency band

[0227] CQI Channel Quality Information

[0228] C-RNTI Community RNTI

[0229] CSI Channel State Information

[0230] DCCH Dedicated Control Channel

[0231] DL downlink

[0232] DM demodulation

[0233] DMRS demodulation reference signal

[0234] DRX discontinuous reception

[0235] DTX discontinuous transmission

[0236] DTCH Dedicated Service Channel

[0237] DUT (Device Under Test)

[0238] E-CID Enhanced Cell ID (Location Method)

[0239] E-SMLC Evolution Service Mobile Location Center

[0240] ECGI evolved from CGI

[0241] eNB E-UTRAN Node B

[0242] EPDCCH Enhanced Physical Downlink Control Channel

[0243] E-SMLC Evolution Service Mobile Location Center

[0244] E-UTRA evolved from UTRA

[0245] E-UTRAN evolved from UTRAN

[0246] FDD (Frequency Division Duplex)

[0247] FFS for further research

[0248] GERN GSM EDGE radio access network

[0249] Base stations in gNB NR

[0250] GNSS Global Navigation Satellite System

[0251] GSM Global Mobile Communication System

[0252] HARQ Hybrid Automatic Repeat Request

[0253] HO switch

[0254] HSPA High-Speed ​​Packet Access

[0255] HRPD High-Speed ​​Packet Data

[0256] LOS (Location of View)

[0257] LPP LTE positioning protocol

[0258] LTE Long Term Evolution

[0259] MAC Media Access Control

[0260] MBMS Multimedia Broadcast / Multicast Service

[0261] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0262] MBSFNABS MBSFN almost blank subframes

[0263] Minimum Drive Testing (MDT)

[0264] MIB (Master Information Block)

[0265] MME (Mobility Management Entity)

[0266] MSC Mobile Switching Center

[0267] PDCCH Narrowband Physical Downlink Control Channel

[0268] NR New Radio

[0269] OCNGOFDMA Channel Noise Generator

[0270] OFDM (Orthogonal Frequency Division Multiplexing)

[0271] OFDMA (Orthogonal Frequency Division Multiple Access)

[0272] OSS Operation Support System

[0273] OTDOA Observation Time Difference

[0274] O&M Operations and Maintenance

[0275] PBCH (Physical Broadcast Channel)

[0276] P-CCPCH Main Common Control Physical Channel

[0277] Pcell main cell

[0278] PCFICH Physical Control Format Indicator Channel

[0279] PDCCH (Physical Downlink Control Channel)

[0280] PDP distribution delay distribution

[0281] PDSCH (Physical Downlink Shared Channel)

[0282] PGW Packet Gateway

[0283] PHICH Physical Hybrid ARQ Indicator Channel

[0284] PLMN Public Land Mobile Network

[0285] PMI Precoding Matrix Indicator

[0286] PRACH (Physical Random Access Channel)

[0287] PRS Positioning Reference Signal

[0288] PSS Master Synchronization Signal

[0289] PUCCH (Physical Uplink Control Channel)

[0290] PUSCH Physical Uplink Shared Channel

[0291] PACH Random Access Channel

[0292] QAM Quadrature Amplitude Modulation

[0293] RAN (Radio Access Network)

[0294] RAT Radio Access Technology

[0295] RLM Radio Link Management

[0296] RNC Radio Network Controller

[0297] RNTI (Radio Network Temporary Identifier)

[0298] RRC Radio Resource Control

[0299] RRM Radio Resource Management

[0300] RS reference signal

[0301] RSCP Received Signal Code Power

[0302] RSRP reference symbol received power or

[0303] Reference signal received power

[0304] RSRQ reference signal reception quality or

[0305] Reference symbol reception quality

[0306] RSSI Received Signal Strength Indicator

[0307] RSTD (Reference Signal Time Difference)

[0308] SCH Synchronization Channel

[0309] Scell ​​auxiliary cell

[0310] SDU Service Data Unit

[0311] SFN system frame number

[0312] SGW Service Gateway

[0313] SI System Information

[0314] SIB System Information Block

[0315] SNR (Signal-to-Noise Ratio)

[0316] SON self-optimizing network

[0317] SS synchronization signal

[0318] SSS auxiliary synchronization signal

[0319] TDD (Time Division Duplex)

[0320] TDOA arrival time difference

[0321] TOA Arrival Time

[0322] TSS Level 3 Synchronization Signal

[0323] TTI Transmission Time Interval

[0324] UE User Equipment

[0325] UL uplink

[0326] UMTS (Universal Mobile Telecommunications System)

[0327] USIM Universal Subscriber Identification Module

[0328] UTDOA Uplink Time Difference

[0329] UTRA Universal Terrestrial Radio Access

[0330] UTRAN Evolution Universal Terrestrial Radio Access Network

[0331] WCDMA Wide CDMA

[0332] WLAN wide area network

[0333] AMF core access and mobility management functions

[0334] NGAP Next Generation Application Protocol

[0335] RL relay

[0336] RM Remote

[0337] PO paging timing

[0338] ProSe Nearby Services

[0339] GUTI (Globally Unique Temporary Identifier)

[0340] Further definitions and examples are discussed below.

[0341] In the above description of various embodiments of this disclosure, it should be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It should also be understood that terms such as those defined in general dictionaries should be interpreted as having a meaning consistent with their meaning in the context of this specification and related art, and not as having an ideal or overly superficial meaning, unless so expressly defined herein.

[0342] When an element is described as being “connected,” “coupled,” “responding,” or a variation thereof relative to another element, it may be directly connected, coupled to, or respond to the other element, or there may be intermediate elements. Conversely, when an element is described as being “directly connected,” “directly coupled,” “directly responding,” or a variation thereof relative to another element, there are no intermediate elements. Throughout the text, similar reference numerals are used to denote similar elements. Furthermore, the terms “coupled,” “connected,” “responding,” or variations thereof as used herein may include wireless coupling, connection, or response. As used herein, the singular forms “a,” “an,” and “described” are intended to also include the plural forms unless the context clearly indicates otherwise. For the sake of brevity and / or clarity, well-known functions or structures may not be described in detail. The term “and / or” (abbreviated as “ / ”) includes any and all combinations of one or more of the associated listed items.

[0343] It will be understood that although the terms first, second, third, etc., may be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are used only to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be referred to as a second element / operation in other embodiments without departing from the teachings of this disclosure. Throughout the specification, the same reference numerals or reference symbols denote the same or similar elements.

[0344] The terms “including,” “contains,” “comprising,” “covering,” “comprises,” “includes,” “have,” “possess,” “have,” or variations thereof, as used herein, are open-ended and include one or more of the described features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or combinations thereof. Furthermore, as used herein, the common abbreviation “eg (for example),” derived from the Latin phrase “exempligratia,” can be used to introduce or specify a general example of a previously mentioned item, and is not intended to be a limitation of that item. The common abbreviation “ie (i.e.),” derived from the Latin phrase “idest,” can be used to specify a specific item in a broader sense of reference.

[0345] This document describes exemplary embodiments with reference to block diagrams and / or flowcharts illustrating computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It should be understood that the blocks shown in the block diagrams and / or flowcharts, and combinations of blocks shown in the block diagrams and / or flowcharts, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuitry of general-purpose computer circuitry, special-purpose computer circuitry, and / or other programmable data processing circuitry to produce a machine, such that instructions executed via a processor of a computer and / or other programmable data processing apparatus translate and control transistors, values ​​stored in memory locations, and other hardware components within such circuitry to implement the functions / actions specified in the block diagrams and / or flowcharts, thereby creating means (functional bodies) and / or structures for implementing the functions / actions specified in the block diagrams and / or flowcharts.

[0346] These computer program instructions may also be stored in a tangible computer-readable medium capable of directing a computer or other programmable data processing apparatus to function in a specific manner, such that the instructions stored in the computer-readable medium produce an article of writing comprising instructions that implement the functions / actions specified in the blocks and / or flowcharts. Therefore, embodiments of this disclosure may be implemented by hardware and / or software (including firmware, resident software, microcode, etc.) running on a processor (e.g., a digital signal processor), which may be collectively referred to as a “circuit,” a “module,” or variations thereof.

[0347] It should also be noted that in some alternative implementations, the functions / actions marked in the boxes may not occur in the order indicated in the flowchart. For example, depending on the functions / actions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or the boxes may sometimes be executed in reverse order. Furthermore, the functionality of a given box in a flowchart and / or block diagram may be divided into multiple boxes, and / or the functionality of two or more boxes in a flowchart and / or block diagram may be at least partially integrated. Finally, without departing from the scope of this disclosure, other boxes may be added / inserted between the shown boxes, and / or boxes / actions may be omitted. Additionally, although some boxes include arrows indicating the main direction of communication regarding the communication path, it should be understood that communication may occur in the opposite direction to the indicated arrows.

[0348] Many variations and modifications can be made to the embodiments without substantially departing from the principles of this disclosure. All such variations and modifications are intended to be included within the scope of this disclosure herein. Therefore, the foregoing subject matter should be understood as exemplary rather than restrictive, and the examples of embodiments are intended to cover all such modifications, improvements, and other embodiments falling within the spirit and scope of this disclosure. Thus, to the fullest extent permitted by law, the scope of this disclosure should be determined by the widest permissible interpretation of this disclosure, including examples of embodiments and their equivalents, and should not be limited to or restricted to the specific implementations described above.

Claims

1. A method of operating radio access network nodes (900, 1100) to link a remote user equipment (RMUE) device (1102) to a relay user equipment (RLUE) device (1104) in a communication network (1106), the method comprising: Receive a message from either the RMUE device (1102) or the RLUE device (1104), the message including information corresponding to the RMUE device (1102) or the RLUE device (1104), the RMUE device (1102) or the RLUE device (1104) having a connection established between the radio access network node (900, 1100) and the corresponding one of the RMUE device (1102) or the RLUE device (1104) using a first access and mobility management function (AMF), wherein the first AMF was previously used for one of the RMUE device (1102) and the RLUE device (1104), and the first AMF is selected by the radio access network node (900, 1100) to currently also be used for the other of the RMUE device (1102) and the RLUE device (1104); and Linking the RMUE device (1102) to the RLUE device (1104) using the first AMF, wherein linking the RMUE device (1102) to the RLUE device (1104) using the first AMF includes: modifying the paging parameters of the RMUE device (1102) to align with the paging parameters of the RLUE device (1104).

2. The method according to claim 1, further comprising: Send a message to the core network (1112) regarding the first AMF including data corresponding to the RLUE device (1104) or the RMUE device (1102).

3. The method according to claim 1, further comprising: Send a registration message to the core network (1112), the registration message including information corresponding to the RLUE device (1104).

4. The method according to claim 3, wherein, The information corresponding to the RLUE device (1104) includes: the Next Generation Application Protocol ID (NGAP ID) corresponding to the RLUE device (1102); and the AMF identifier corresponding to the RLUE device (1104).

5. The method according to claim 1, wherein, Based on the fact that the first AMF is being used by the RMUE device (1102), the RMUE device (1102) registers with the core network (1112) based on the first AMF, and wherein the RLUE device (1104) is linked to the RMUE device (1102) using the first AMF.

6. The method according to claim 1, wherein, Based on the first AMF being used by the RLUE device (1104), the RLUE device (1104) registers with the core network (1112) based on the first AMF, and wherein the RMUE device (1102) is linked to the RLUE device (1104) using the first AMF.

7. The method according to claim 1, further comprising: Based on the RMUE device (1102) moving and becoming directly linked to the radio access network node (1100), the link between the RMUE device (1102) and the RLUE device (1104) is severed.

8. The method according to claim 7, further comprising: Send a message to the first AMF that does not include information corresponding to the RLUE device (1104).

9. The method according to claim 7 or 8, wherein, The first AMF corresponds to the RMUE device (1102), and wherein the first AMF removes the link between the RMUE device (1102) and the RLUE device (1104).

10. The method according to claim 7, wherein, The second AMF, different from the first AMF, corresponds to the RMUE device (1102), wherein the second AMF retrieves the link from the RLUE device (1104), and The first AMF removes the link between the RMUE device (1102) and the RLUE device (1104).

11. The method according to claim 1, wherein, The RLUE device (1104) includes a first RLUE device (1104). The RMUE device (1102) moves from the first RLUE device (1104) to the second RLUE device (1114), and the method further includes: Receive information corresponding to the first RLUE device (1104) and the second RLUE device (1114) from the RMUE device (1102) or the second RLUE device (1114); and The RMUE device (1102) is linked to the second RLUE device (1114) using the second AMF.

12. The method according to claim 1, wherein, The RLUE device (1104) includes a first RLUE device (1104), and the method further includes: based on the RMUE device (1102) moving to a second RLUE device (1114) different from the first RLUE device (1104), the link between the RMUE device (1102) and the first RLUE device (1104) is released.

13. The method of claim 12, further comprising: Send a registration message to the core network (1112), the registration message including information corresponding to the second RLUE device (1114).

14. The method according to claim 13, wherein, The information corresponding to the second RLUE device (1114) includes: the Next Generation Application Protocol Identifier (NGAP ID) corresponding to the second RLUE device (1114); and the second AMF identifier corresponding to the second RLUE device (1114).

15. The method according to claim 7, wherein, Delinking the RMUE device (1102) includes receiving a registration message from the RMUE device (1102) that does not include information corresponding to the RLUE device (1104).

16. A radio access network (RAN) node (900, 1100), comprising: Processing circuit (903); as well as A memory (905) coupled to the processing circuit (903), wherein the memory (905) includes instructions that, when executed by the processing circuit (903), cause the RAN node (900, 1100) to perform the operation according to any one of claims 1 to 15.

17. A method of operating a core network node (1000) to link a remote user equipment (RMUE) device (1102) to a relay user equipment (RLUE) device (1104) in a communication network (1106), the method comprising: Receive a message from the radio access network node (1100) regarding a first AMF including data corresponding to either the RMUE device (1102) or the RLUE device (1104), and receive the message into the core network (1112), wherein the first AMF was previously used for one of the RMUE device (1102) and the RLUE device (1104), and the first AMF is selected by the radio access network node (900, 1100) as the other currently also used for one of the RMUE device (1102) and the RLUE device (1104); and Linking the RMUE device (1102) to the RLUE device (1104) based on the message, wherein linking the RMUE device (1102) to the RLUE device (1104) based on the message includes: modifying the paging parameters of the RMUE device (1102) to align with the paging parameters of the RLUE device (1104).

18. The method of claim 17, further comprising: The registration message is received in the core network (1112), and the registration message includes information corresponding to the RLUE device (1104).

19. The method according to claim 18, wherein, The information corresponding to the RLUE device (1104) includes: the Next Generation Application Protocol ID (NGAP ID) corresponding to the RLUE device (1104); and the AMF identifier corresponding to the RLUE device (1104).

20. The method of claim 17, wherein, Based on the fact that the first AMF is being used by the RMUE device (1102), the RMUE device (1102) registers with the core network (1112) based on the first AMF, and wherein the RLUE device (1104) is linked to the RMUE device (1102) using the first AMF.

21. The method according to claim 17, wherein, Based on the fact that the first AMF is being used by the RLUE device (1104), the RLUE device (1104) registers with the core network (1112) based on the first AMF, and wherein the RMUE device (1102) is linked to the RLUE device (1104) using the first AMF.

22. The method of claim 17, further comprising: Based on the fact that the RMUE device (1102) moves and becomes directly linked to the core network node, the link between the RMUE device (1102) and the RLUE device (1104) is terminated.

23. The method of claim 22, further comprising: Receive a message associated with the RMUE device (1102) but not including information corresponding to the RLUE device (1104).

24. The method according to claim 22 or 23, wherein, The first AMF corresponds to the RMUE device (1102), and wherein the first AMF removes the link between the RMUE device (1102) and the RLUE device (1104).

25. The method according to claim 22, wherein, The second AMF, different from the first AMF, corresponds to the RMUE device (1102), wherein the second AMF retrieves the link from the RLUE device (1104), and The first AMF removes the link between the RMUE device (1102) and the RLUE device (1104).

26. The method according to claim 17, wherein, The RLUE device (1104) includes a first RLUE device (1104). The RMUE device (1102) moves from the first RLUE device (1104) to the second RLUE device (1114), and the method further includes: Receive information corresponding to the first RLUE device (1104) and the second RLUE device (1114); and The RMUE device (1102) is linked to the second RLUE device (1114).

27. The method according to claim 17, wherein, The RLUE device (1104) includes a first RLUE device (1104), and the method further includes: based on the RMUE device (1102) moving to a second RLUE device (1114) different from the first RLUE device (1104), the link between the RMUE device (1102) and the first RLUE device (1104) is released.

28. The method of claim 27, further comprising: A registration message is received in the core network (1112), the registration message including information corresponding to the second RLUE device (1114).

29. The method according to claim 28, wherein, The information corresponding to the second RLUE device (1114) includes: the Next Generation Application Protocol Identifier (NGAP ID) corresponding to the second RLUE device (1114); and the second AMF identifier corresponding to the second RLUE device (1114).

30. A core network CN node (1000), comprising: Processing circuit (1003); as well as A memory (1005) coupled to the processing circuit (1003), wherein the memory (1005) includes instructions that, when executed by the processing circuit (1003), cause the CN node (1000) to perform the operation according to any one of claims 17 to 29.

Images