Continuity of multicast and broadcast services for user devices in mobility

Abstract

To provide a method, a user equipment (UE), a network node, and a computer program product for transmission of multicast and broadcast services (MBS) to one or more UEs in mobility.SOLUTION: A method is performed by a target network node in a wireless communication network. The method comprises determining whether a UE is involved in an MBS session with a source network node. Upon determining that the UE is involved in the MBS session with the source network node, the method comprises obtaining an MBS context of the UE related to the MBS session. Further, the method comprises determining provisioning of a Point-To-Multipoint (PTM) configuration information associated with the MBS session to be acquired by the UE for enabling continuous reception of MBS data from the target network node.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure generally relates to the field of wireless communications. More particularly, the present disclosure relates to a method, a user equipment (UE), a network node, and a computer program product for providing continuity of multicast and broadcast services (MBS) to one or more UEs in mobility.

Background Art

[0002] With the rapid development of the Internet and the popularization of large-screen multifunctional mobile terminals, a number of mobile data multimedia services and various high-bandwidth multimedia services have emerged, such as video conferencing, television broadcasting, video on demand, advertising, online education, and interactive games. In particular, these mobile data multimedia services require that multiple users can receive the same data simultaneously. Compared with general data services, mobile data multimedia services have characteristics such as a large data volume, a long duration, and sensitivity to delay.

[0003] To effectively utilize mobile network resources, the 3rd Generation Partnership Project (3GPP) proposes Multimedia Broadcast Multicast Service (MBMS), a technology for transmitting data from one data source to multiple target mobile terminals.

[0004] MBMS, as defined by 3GPP, can achieve not only multicast and broadcast of low-rate plain text messages, but also broadcast and multicast of high-speed multimedia services, and thus can provide a wide range of rich video, audio, and multimedia services. MBMS is transmitted over point-to-multipoint (PTM) interfaces designed to provide efficient delivery of broadcast and multicast services within a 3GPP cellular network. When an MBMS service is broadcast, all cells in a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) area transmit the same MBMS service.

[0005] Users access these services and obtain MBMS content through wireless communication devices, such as cellular phones, tablets, laptop computers, and other devices with wireless transceivers that communicate with base stations within the wireless communication system. Base stations, sometimes called eNode B, provide wireless services to wireless communication devices, sometimes called User Equipment (UEs), within the cell.

[0006] A UE can be in one of at least two modes, including connected mode and idle mode. A UE is in connected mode when a Radio Resource Control (RRC) connection is established. If no RRC connection is established, the UE is in idle mode. Therefore, connected mode includes established RRC connections, but idle mode does not include established RRC connections. After establishing an RRC connection, the UE receives MBMS content in connected mode. The Third Generation Partnership Project (3GPP) specified support for multicast and broadcast services in new radio (NR) systems in technical specifications TS38.300, TS38.331, TS38.413, TS38.423, TS23.501, and TS23.502.

[0007] Existing NR specifications lack broadcast or multicast features for PTM transmissions to UEs, and available point-to-point transmissions can be extended for PTM transmissions to UEs in RRC-connected states. The lack of broadcast or multicast features for PTM transmissions to UEs in NR systems means there is no mobility support for providing continuous MBS services to UEs.

[0008] Therefore, improved methods and configurations are needed to provide multicast and broadcast services (MBS) to mobile UEs, mitigating at least some of the problems cited above. [Overview of the project]

[0009] In particular, when user equipment (UE) is in mobility, it is desirable to provide service continuity for MBS services for UEs in the RRC_CONNECTED state and RRC_IDLE or inactive state. In addition to service continuity, providing MBS services to UEs in mobility can be beneficial, for example, to conserve the UE's battery life. Therefore, it is desirable to enable the UE to continue receiving the same MBS service with minimal interruption at a new gNB. To provide service continuity for MBS services, the UE needs to collect PTM configuration information at the target network node, which is necessary for the UE to receive the same MBS that it was receiving from the last serving network node.

[0010] Therefore, the purpose of this disclosure is to provide methods, network nodes, user equipment, and computer program products for transmitting multicast and broadcast services (MBS) in mobility that seek to mitigate, mitigate, or eliminate all or at least some of the shortcomings of currently known solutions described above.

[0011] These and other objectives are achieved by the methods, computer program products, and devices set forth in the attached claims. The term "exemplary" should be understood in this context as serving as an example, illustration, or reference.

[0012] A first aspect of this disclosure provides a method for transmitting multicast and broadcast services (MBS) to user equipment (UEs) in a wireless communication network. The method is performed by a target network node in the wireless communication network. The method includes the UE deciding to engage in an MBS session with a source network node. Once the UE decides to engage in an MBS session with a source network node, the method includes obtaining the MBS context of the UE involved in the MBS session. Furthermore, the method includes determining the provisioning of point-to-multipoint (PTM) configuration information related to the MBS session that should be collected by the UE to enable continuous reception of MBS data from the target network node.

[0013] In some embodiments, the method further includes determining the RRC status of one or more UEs for receiving MBS data based on one or more network parameters for the MBS, capability information of one or more UEs, and one or more MBS parameters.

[0014] In some embodiments, the method includes receiving a message from the UE instructing the UE to engage in an MBS session with the source network node.

[0015] In some embodiments, the message is one of the random access procedure messages A (MSG A), 3 (MSG3), and 5 (MSG5).

[0016] In some embodiments, MSG3 includes one or more of a cause-related RRC setup request, a cause-related RRC restart request, an RRC system information request, and one or more temporary mobile group identifiers (TMGIs).

[0017] In some embodiments, MSG5 includes one or more of an RRC setup completion message including TMGI and an RRC restart completion message including TMGI.

[0018] In some embodiments, the method further includes receiving a handover request message from a source network node, containing the MBS context of the UE relating to the MBS session, when the UE is in an RRC connection state.

[0019] In some embodiments, the MBS context of a UE related to an MBS session includes one or more of the following: a UE identifier, a session identifier, temporary mobile group identification information (TMGI), and a source network node identifier.

[0020] In some embodiments, when a UE engages in an MBS session with a source network node, the step of obtaining the MBS context of the UE involved in the MBS session includes obtaining the MBS context from one or more of the source network node and / or the Access and Mobility Management Function (AMF) in the Core Network (CN).

[0021] In some embodiments, the step of obtaining the MBS context from the source network node includes determining that the UE is in an RRC inactive state. The method includes receiving restart identification information related to the MBS session from the UE. Furthermore, the method includes sending the restart identification information to the source network node to identify the UE's MBS context at the source network node. The method includes obtaining the UE's MBS context from the source network node.

[0022] In some embodiments, the step of obtaining the MBS context of a UE related to an MBS session from the AMF in the CN includes determining that the UE is in an RRC idle state. Furthermore, the method includes receiving information related to the MBS session, wherein the information includes one or more of the following from the UE: Serving Temporary Mobile Subscriber Identification (S-TMSI), Temporary Mobile Group Identification (TMGI), and Session Identifier (ID). Furthermore, the method includes establishing an RRC connection with the AMF by sending an initial UE message to the AMF and sending the UE-related TMGI to the AMF. The method includes determining that the UE's MBS context is available in the AMF. Furthermore, the method includes obtaining the UE's MBS context in an NGAP message when the MBS context is available in the AMF.

[0023] In some embodiments, the method further includes determining that the UE's MBS context is unavailable in the AMF, and receiving instructions from the AMF to start a new session for the UE when the UE's MBS context is unavailable in the AMF.

[0024] In some embodiments, the PTM configuration information includes a PTM configuration for an MBS session, the PTM configuration for an MBS session including one or more of a service identifier, a session identifier, a group radio network temporary identifier (G-RNTI), information relating to scheduling of PTM data, information instructing at least one neighboring node to transmit an MBS session, a PTM configuration for a cell served by a target network node, and a PTM configuration for one or more MBS sessions at the target network node.

[0025] In some embodiments, the step of transmitting PTM configuration information related to an MBS session includes transmitting the PTM configuration to the UE 103 in message B (MSG B) or message 4 (MSG 4). Furthermore, the method includes transmitting the PTM configuration to the UE in message 6 (MSG 6), and transmitting the PTM configuration to the source network node in a handover request acknowledgment message containing the MBS configuration information when a handover request message is received from the source network node.

[0026] In some embodiments, MSG B or MSG 4 includes a System Information Block (SIB) that indicates PTM configuration information, a New Information Element (IE) that indicates PTM configuration information, an instruction on whether to change the RRC state to continue receiving MBS data from the target network node, an instruction to resume a suspended PTP radio bearer when the UE is in an RRC inactive state, and an instruction to set up a new PTP radio bearer when the UE is in an RRC connected state.

[0027] In some embodiments, MSG6 includes one or more of the following: an instruction on whether to change the RRC state in order to continue receiving MBS data from the target network node, and an instruction on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data.

[0028] In some embodiments, the method comprises determining that the UE's MBS session is to be provided to one or more additional UEs in an area served by a target network node, and further comprises determining that the UE's MBS session is to be provided to one or more additional UEs, wherein the MBS session is provided to the one or more additional UEs (103a - 103n) using a point-to-point (PTP) bearer. The method includes determining to switch the PTP bearer to a PTM bearer for one or more additional UEs. Further, the method includes determining to provision the one or more additional UEs with PTM settings for transmission of MBS data to the UE.

[0029] In some embodiments, the method further comprises determining that the UE's MBS session is not to be provided to one or more additional UEs in an area served by a target network node. Further, the method includes initiating a new MBS session joining procedure with the AMF and transmitting an instruction to the UE to use a PTP bearer for provisioning of PTM settings for reception of MBS data.

[0030] According to a second aspect of the present disclosure, a method is provided for enabling a user equipment (UE) in a wireless communication network to perform continuous reception of multicast and broadcast services (MBS). The method is performed by a source network node in the wireless communication network. The method includes determining that the UE is in mobility and is involved in an MBS session with the source network node, and transmitting an MBS context related to the MBS session to one or more adjacent network nodes while the UE is in mobility, wherein one of the one or more adjacent network nodes is a target network node.

[0031] In some embodiments, the step of sending an MBS context related to an MBS session to one or more neighboring network nodes while the UE is in mobility includes determining that the UE is in an RRC connection state during mobility and receiving a handover request message from the UE. Furthermore, the method includes sending a handover request message to one or more neighboring network nodes containing the UE's MBS context related to the MBS session.

[0032] In some embodiments, the method further includes receiving PTM settings from one or more neighboring network nodes in a handover request acknowledgment message containing MBS session configuration information, and sending an RRC reconfiguration message containing MBS session configuration information to the UE.

[0033] In some embodiments, the PTM configuration information includes a PTM configuration for an MBS session, the PTM configuration for an MBS session includes one or more of a service identifier, a session identifier, a group radio network temporary identifier (G-RNTI), information relating to scheduling of PTM data, and information indicating that at least one neighboring node transmits the MBS session.

[0034] In some embodiments, the MBS context is identified using a context identifier assigned by the source network node.

[0035] A third aspect of this disclosure provides a method for receiving multicast and broadcast services (MBS) from a target network node in a wireless communication network. The method is performed by user equipment (UE) in the wireless communication network. The method includes determining that an MBS session with a source network node is in progress at the UE. Furthermore, the method includes sending a message indicating that an MBS session with a source network node is in progress, and determining, based on the transmitted message, to receive point-to-multipoint (PTM) configuration information related to the MBS session that should be collected for the continued reception of MBS data from the target network node.

[0036] In some embodiments, the step of sending a message indicating that a UE MBS session with a source network node is in progress further includes sending a message to a target network node indicating that the UE should engage in an MBS session with the source network node while the UE is in one of the idle or inactive states.

[0037] In some embodiments, the message is one of the random access procedure messages B or 3 (MSG3), and message 5 (MSG5).

[0038] In some embodiments, MSG B or MSG3 includes one or more of a cause-based RRC setup request, a cause-based RRC restart request, an RRC system information request, instructions, and one or more temporary mobile group identifiers (TMGIs).

[0039] In some embodiments, MSG5 includes one or more of an RRC setup completion message including TMGI and an RRC restart completion message including TMGI.

[0040] In some embodiments, the method further includes sending a handover request message to the source network node, while the UE is in an RRC connection state, containing the MBS context of the UE related to the MBS session.

[0041] In some embodiments, the MBS context of a UE related to an MBS session includes one or more of the following: a UE identifier, a session identifier, temporary mobile group identification information (TMGI), and a source node identifier.

[0042] In some embodiments, the PTM configuration information includes a PTM configuration for an MBS session, the PTM configuration for an MBS session includes one or more of the following: a service identifier, a session identifier, a group radio network temporary identifier (G-RNTI), information relating to scheduling of PTM data, information instructing at least one neighboring node to transmit an MBS session, and PTM configuration information for one or more ongoing MBS sessions in a cell served by a target node.

[0043] In some embodiments, the step of receiving PTM configuration information related to an MBS session from a target network node includes receiving the PTM configuration in message B (MSG B) and message 4 (MSG4), receiving the PTM configuration in the message 6 (MSG6) procedure, and receiving the PTM configuration from a source network node in a handover request acknowledgment message containing MBS configuration information.

[0044] In some embodiments, MSG4 includes a System Information Block (SIB) that indicates PTM configuration information, a New Information Element (IE) that indicates PTM configuration information, an instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, an instruction to resume a suspended PTP radio bearer when the UE is in an RRC inactive state, and an instruction to set up a new PTP radio bearer when the UE is in an RRC connected state.

[0045] In some embodiments, MSG6 includes one or more of the following: an instruction on whether to change the RRC state in order to continue receiving MBS data from the target network node, and an instruction on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data.

[0046] A fourth aspect of this disclosure provides a target network node for transmitting multicast and broadcast services (MBS) to user equipment (UEs) in a wireless communication network. The target network node is adapted to enable the UE to decide to engage in an MBS session with a source network node. When the target network node enables the UE to decide to engage in an MBS session with a source network node, the target network node is adapted to obtain the MBS context of the UE involved in the MBS session and to transmit point-to-multipoint (PTM) configuration information related to the MBS session that should be collected by the UE to enable continuous reception of MBS data from the target network node.

[0047] A fifth aspect of this disclosure provides a source network node for enabling a user device (UE) in a wireless communication network to perform continuous reception of multicast and broadcast services (MBS). The source network node is adapted to enable the UE to determine that it is in mobility and to engage in an MBS session with the source network node. Furthermore, the source network node is adapted to enable the UE to transmit an MBS context relating to an MBS session to one or more neighboring network nodes while the UE is in mobility, wherein one of the one or more neighboring network nodes is the target network node.

[0048] A sixth aspect of this disclosure provides a user equipment (UE) for receiving multicast and broadcast services (MBS) from a target network node in a wireless communication network. The UE is adapted to determine that an MBS session with a source network node is in progress at the UE. Furthermore, the UE is adapted to transmit a message indicating that an MBS session with a source network node is in progress and to receive point-to-multipoint (PTM) configuration information related to the MBS session that should be collected for the continued reception of MBS data from the target network node, based on the transmitted message.

[0049] A seventh aspect of this disclosure provides a computer program product comprising a non-temporary computer-readable medium having a computer program comprising program instructions thereon. The computer program is loadable into a data processing unit and is configured to cause the execution of a method according to any of the first, second, or third aspects when the computer program is run by the data processing unit.

[0050] One advantage of some embodiments is that the service continuity of the MBS is maintained for UEs that are in mobility.

[0051] An advantage of some embodiments is that it allows the UE to collect PTM configuration information for multicast or broadcast services for UEs that are in an RRC idle or RRC inactive state, without requiring the UE to transition to an RRC connected state.

[0052] One advantage of some embodiments is the efficient handling of MBS context transfer by the UE, which avoids the need for new session joining with a different MBS context at the target network node.

[0053] The above will become clear from the following more specific description of exemplary embodiments shown in the accompanying drawings, where similar reference numerals across different figures refer to the same parts. The drawings are not necessarily to a constant scale, and instead, the emphasis is on illustrating exemplary embodiments. [Brief explanation of the drawing]

[0054] [Figure 1] This is a diagram disclosing an exemplary wireless communication network. [Figure 2] This flowchart illustrates exemplary method steps of a method implemented by a target network node for transmitting multicast and broadcast services (MBS) to user equipment (UE) in a wireless communication network. [Figure 3] This flowchart shows exemplary method steps of a method implemented by a source network node to enable the UE for continuous reception of the MBS. [Figure 4] This flowchart shows exemplary method steps of a method implemented by a UE for receiving MBS. [Figure 5]This signal flow diagram illustrates exemplary operation in a wireless communication network, initiated by a UE (User Engine) in a mobile device that is in an RRC (Rapid Radio Control) inactive state. [Figure 6] This signal flow diagram illustrates exemplary operation in a wireless communication network, initiated by a UE (User Engine) in a mobility device that is in an RRC idle state. [Figure 7] This is an illustrative schematic diagram showing a functional module of UE. [Figure 8] This is an illustrative schematic diagram showing a functional module of a wireless access network node. [Figure 9] This is an illustrative schematic diagram showing the functional modules of a core network (CN) node. [Figure 10] This is a block diagram of an exemplary wireless network. [Figure 11] This is an example block diagram of a UE. [Figure 12] This is a block diagram of a virtualized environment. [Figure 13] This is a block diagram of a communication network connected to a host computer via an intermediate network. [Figure 14] This is a block diagram showing how a host computer communicates with a UE (Unified Entity) via a base station over a partial wireless connection. [Figure 15] This is a block diagram of a method implemented in a communication system including a host computer, a base station, and an UE (Unified User). [Figure 16] This is a block diagram of a method implemented in a communication system including a host computer, a base station, and an UE (Unified User). [Figure 17] This is a block diagram of a method implemented in a communication system including a host computer, a base station, and an UE (Unified User). [Figure 18] This is a block diagram of a method implemented in a communication system including a host computer, a base station, and an UE (Unified User). [Figure 19] This is a diagram disclosing an exemplary computing environment. [Modes for carrying out the invention]

[0055] Aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, the apparatus and methods disclosed herein can be implemented in many different forms and should not be construed as being limited to the embodiments described herein. Similar numbers in the drawings refer to similar elements throughout.

[0056] The technical terms used herein are for the purpose of describing specific aspects of this disclosure and do not limit the invention. The terms “comprises” and “comprising” as used herein are taken to indicate the presence of a described feature, complete, step, or component, but should be emphasized that they do not exclude the presence or addition of one or more other features, completes, steps, components, or groups thereof. The singular forms “a,” “an,” and “the” as used herein also include the plural form unless the context otherwise explicitly indicates.

[0057] Embodiments of this disclosure are described and illustrated more thoroughly below with reference to the accompanying drawings. However, the solutions disclosed herein can be realized in many different forms and should not be construed as being limited to the embodiments described herein.

[0058] When this disclosure describes a method, it should be understood that it may also be embodied in one or more processors and one or more memories coupled to one or more processors, the one or more memories storing one or more programs that, when executed by one or more processors, perform the steps, services, and functions disclosed herein.

[0059] This disclosure enables user devices (UEs), also known as mobile terminals, and / or wireless terminals to communicate wirelessly with network nodes in a wireless communication network.

[0060] Generally, a network node may serve or cover one or more cells in a wireless communication network. A network node can be a source network node or a target network node. The source network node serves the UE initially and when the UE performs a handover from the source network node to the target network node, and the target network node serves the UE after the UE performs a handover to the target network node. Thus, a network node can be a source network node or a target network node. Generally, a network node provides radio coverage in one or more cells and communicates over an air interface with one or more UEs operating on radio frequencies within its range. A network node may also be called an “eNB,” “eNode B,” “Node B,” or “gNB,” depending on the technology and terminology used. In this disclosure, a network node may also be referred to as a base station (BS).

[0061] This disclosure assumes that a connection has already been established between (one or more) UEs and network nodes.

[0062] Throughout this explanation, the terms "inactive" and "RRC inactive" are assumed to have the same meaning, and the terms "idle" and "RRC idle" are assumed to have the same meaning.

[0063] In the following description of exemplary embodiments, the same reference numerals indicate the same or similar components.

[0064] Figure 1 discloses an exemplary wireless communication network 100. As shown in Figure 1, the wireless communication network 100 includes multiple radio access nodes, RANs 101a, 101b, 101c, such as gNBs, gNB distributed units (gNB-DUs), or network nodes, or other types of radio access points, each defining a corresponding coverage area. Each RAN 101a, 101b, 101c is connectable to a core network node 105 (i.e., a core node or CN) over a wired or wireless connection.

[0065] In some embodiments, the first RAN101a is a source network node configured to connect wirelessly to the UE103a.

[0066] In some embodiments, the second RAN 101b is a target network node. For example, the target network node may be one of the adjacent RANs to the first RAN 101a, i.e., network node 101b or network node 101c.

[0067] Although multiple UE103a, 103b are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in a corresponding coverage area or where a single UE is connected to a corresponding RAN. Therefore, it should be noted that there may be multiple UE103a-103n (not shown in Figure 1), and in some embodiments of this disclosure, a single UE may be referred to as UE103.

[0068] Source network node 101a and target network node 101b may be, for example, new radio (NR) base stations, i.e., gNBs, or evolved node base stations, i.e., eNBs. Communication from source network node 101a or target network node 101b to UEs 103a and 103b is called downlink (DL) communication, and communication from UEs 103a and 103b to source network node 101a or target network node 101b is called uplink (UL) communication. Thus, UEs 103a and 103b are involved in bidirectional wireless communication with source network node 101a or target network node 101b.

[0069] The source network node 101a or the target network node 101b is equipped with a scheduler for dynamically scheduling downlink transmissions. The scheduler dynamically allocates resources for the physical downlink shared channel (PDSCH) and sends scheduling information to UEs 103a and 103b through the control channel.

[0070] To make effective use of mobile network resources, the Third Generation Partnership Project (3GPP) proposes Multimedia Broadcast Multicast Service (MBMS), a technology for transmitting data from a single data source to multiple target mobile devices.

[0071] MBMS, as defined by 3GPP, can achieve not only multicast and broadcast of low-rate plain text messages, but also broadcast and multicast of high-speed multimedia services, and thus can provide a wide range of rich video, audio, and multimedia services. MBMS is transmitted over point-to-multipoint (PTM) interfaces designed to provide efficient delivery of broadcast and multicast services within 3GPP cellular networks.

[0072] UE103a and 103b can be in at least one of two modes, including connected mode and idle mode. For example, UE103a is in connected mode when a Radio Resource Control (RRC) connection is established with a source network node. If no RRC connection is established, UE103a is in idle mode. Thus, connected mode includes an established RRC connection, while idle mode does not include an established RRC connection. UE103a and 103b receive MBMS content in connected mode after establishing an RRC connection.

[0073] In the existing New Radio (NR) specification, there are no broadcast or multicast features for PTM transmission to UEs, and the available point-to-point transmission can be extended for PTM transmission to UE103a and 103b in RRC connected state. Because there are no broadcast or multicast features for PTM transmission to UE103a and 103b in the NR system, there is no mobility support for providing ongoing MBS services to the UEs.

[0074] In particular, when UE103a and 103b are in mobility, it is desirable to provide service continuity for MBS services for UE103a and 103b in the RRC_CONNECTED state and RRC_IDLE or inactive state. In addition to service continuity, providing MBS services to UE103a and 103b in mobility may be beneficial, for example, to conserve the battery life of UE103a and 103b. Therefore, it is desirable to enable UE103a and 103b to continue receiving the same MBS services with minimal interruption at the target network node 101b.

[0075] To provide service continuity for the MBS service, the UE needs to collect PTM configuration information on the target network node 101b, which is necessary for UE 103a to receive the same MBS that it was receiving from the serving network node 101a.

[0076] Accordingly, according to some embodiments of this disclosure, the target network node 101b implements a method for transmitting MBS to the UE 103a as described herein. Alternatively, the UE 103a may also implement a method for receiving MBS data from the target network node 101b.

[0077] According to some embodiments of this disclosure, the target network node 101b determines that UE 103a is engaged in an MBS session with the source network node 101a. For example, UE 103b may engage in an MBS session with the source network node 101a when UE 103a is being served by the source network node 101a. The target network node 101b may determine that UE 103 is in one of the following states: RRC idle, RRC inactive, and RRC connected. Furthermore, when the UE is in one of the idle and inactive states, the target network node 101b may receive a message from UE 103b indicating that the UE is engaged in an MBS session with the source network node 101a. In some examples, the message from UE 103 may be message 3 (MSG3) or message 5 of the random access procedure.

[0078] When the target network node 101b determines that UE 103 will engage in an MBS session with the source network node 101a, the target network node 101b obtains the MBS context related to the MBS session. For example, the MBS context of a UE related to an MBS session includes the identifier of UE 103, the session identifier, the temporary mobile group identifier (TMGI), and the source network node identifier.

[0079] After obtaining the MBS context related to the MBS session, the target network node 101b transmits point-to-multipoint (PTM) configuration information related to the MBS session. The PTM configuration information should be collected by the UE 103, which enables the UE 103 to continuously receive MBS data from the target network node 101b.

[0080] In some examples, the PTM configuration information includes a service identifier for the MBS, a session ID for the MBS, a Group Radio Network Temporary Identifier (G-RNTI), information related to scheduling PTM data, information instructing at least one neighboring node to transmit an MBS session, one or more PTM configurations for cells served by the target network node, and PTM configurations for one or more MBS sessions at the target network node.

[0081] In one example, when the UE is in an RRC inactive state, the target network node 101b sends PTM configuration information to the UE in message 4 (MSG4).

[0082] In another example, when the UE is in an RRC idle state, the target network node 101b sends PTM configuration information to the UE in message 6 (MSG6).

[0083] In another example, the target network node 101b sends PTM configuration information to the source network node 101a in a handover request acknowledgment message, for example, and the source network node 101a sends PTM configuration information to the UE 103.

[0084] Therefore, UE103 collects PTM configuration information from target network node 101b in order to continue receiving MBS services from target network node 101a. Various embodiments in which the UE receives PTM configuration in order to continue receiving MBS data are described in the later parts of this description.

[0085] Figure 2 is a flowchart illustrating an exemplary method 200 for transmitting multicast and broadcast services (MBS) to one or more UEs in a wireless communication network. As described above, a target network node implements method 200 to provide MBS to a UE in a wireless communication network.

[0086] MBS data or MBS content, which may be services, data, or programs accessible through the UE, are referred to herein as PTM-compliant services. Examples of PTM-compliant services include streaming audio and video, as well as other multimedia data.

[0087] The UE shown in Figure 1 can be in one of three modes, including idle mode, inactive mode, and connected mode. When operating according to the 3GPP communication specification, the operation is defined for at least idle mode and connected mode. For example, two of the UEs may be in idle mode and are called idle mode UEs. Furthermore, some of the UEs may be in connected mode and are called connected mode UEs. Connected mode UEs differ from idle mode UEs in that, at least, connected mode UEs have an established RRC connection as defined by a particular 3GPP specification, while idle mode UEs do not have an established RRC connection.

[0088] Furthermore, some of the UEs in the wireless communication network 100 shown in Figure 1 may be inactive, and these UEs, which are inactive for a specific or predetermined time interval, can be activated by the RAN or network node when there is no data reception at these UEs.

[0089] The embodiments disclosed herein are more applicable to the transmission of MBS to a UE when (one or more) UEs perform a handover from a source network node 101a to a target network node, and when (one or more) UEs are in one of the idle, inactive, and connected states.

[0090] In step 202, method 200 includes the UE deciding to engage in an MBS session with a source network node. For example, the UE may engage in communication with the source network node. When the UE engages in communication with the source network node, the UE may engage in an MBS session with the source network node. When the UE engages in an MBS session with the source network node, the UE may be in mobility. While in mobility, and while engaging in an MBS session with the source network node, the UE may perform a handover from the source network node to the target network node with the target network node.

[0091] In some embodiments, the UE may be in one of the following states during mobility, such as idle, inactive, or connected, while engaging in an MBS session with the source network node.

[0092] After the UE performs a handover to the target network node, the target network node decides, for example, that the UE will engage in the MBS session with the source network node in order to continue the MBS session for the UE on the target network node.

[0093] In some embodiments, the target network node 101b may receive a message from the UE instructing it to engage in an MBS session with the source network node when the UE is in one of the idle or inactive states. In some examples, the message from the UE may be message 3 (MSG3) or message 5 of the random access procedure.

[0094] For example, MSG3 includes one or more of the following: an RRC setup request with a cause, an RRC restart request with a cause, an RRC system information request, and one or more TMGIs; MSG5 includes one or more of the following: an RRC setup completion message including a TMGI and an RRC restart completion message including a TMGI.

[0095] In some examples, the target network node determines whether one or more UEs are idle, inactive, or connected in order to send MBS data to them.

[0096] The target network node determines which of the (one or more) UEs is idle / inactive or connected in order to continue transmitting MBS data to the UEs, but the target network node may determine the RRC state of the (one or more) UEs in order to continue transmitting MBS data, as specified in optional step 201. For example, the target network node may determine the RRC state of the (one or more) UEs based on one or more network parameters for MBS, capability information of the (one or more) UEs and one or more MBS parameters, capability information of the (one or more) UEs and one or more MBS parameters.

[0097] In some cases, if a target network node determines that MBS data will only be received when connected, the target network node will determine that one or more UEs are connected for receiving MBS data.

[0098] In another example, if a target network node determines that it has a number of UEs equal to the maximum number of UEs that can receive MBS data in a connected state, the base station may determine that one or more UEs are idle or inactive for receiving MBS data.

[0099] In another example, if capability information for one or more UEs indicates that one or more UEs cannot receive MBS data while idle or inactive, the target network node may determine the RRC state of one or more UEs for receiving MBS data. Thus, the target network node may determine the RRC state of one or more UEs based on network parameters for MBS, capability information for one or more UEs, and one or more MBS parameters.

[0100] In step 208, method 200 includes obtaining the MBS context of the UE related to the MBS session. For example, the UE's MBS context represents the MBS context related to the MBS session with the source network node in which the UE was involved. The UE's MBS context may include the UE identifier, the session identifier related to the MBS session, the TMGI, and the source network node identifier.

[0101] In one embodiment, a target network node may obtain the UE's MBS context from the UE. In another embodiment, a target network node may obtain the UE's MBS context from the source network node. In yet another embodiment, a target network node may obtain the UE's MBS context from the AMF in the core network.

[0102] In some embodiments, the target network node may determine whether the UE is idle or inactive in order to obtain the UE's MBS context. If the target network node determines that the UE is inactive, the target network node may receive restart identification information related to the MBS session from the UE. Furthermore, the target network node may send the restart identification information to the source network node to identify the UE's MBS context at the source network node. The source network node uses the restart identification information received from the target network node to identify the UE's MBS context and sends the identified MBS context of the UE to the target network node. Thus, the target network node obtains the MBS context.

[0103] In another embodiment, when a target network node determines that a UE is idle, the target network node may receive information related to the MBS session, including Serving Temporary Mobile Subscriber Identification (S-TMSI), Temporary Mobile Group Identification (TMGI), and Session Identifier (ID) from the UE. Furthermore, the target network node may establish an RRC connection with the AMF by sending an initial UE message to the AMF, and send the TMGI related to the UE to the AMF. Using the TMGI received from the target network node, the AMF identifies the MBS context stored in the AMF. If the MBS context is available in the AMF, the AMF sends the UE's MBS context in an NGAP message. Thus, the target network node obtains the UE's MBS context when the MBS context is available in the AMF.

[0104] If the MBS context is unavailable in the AMF, the AMF may send instructions to the target network node to start a new MBS session for the UE. Thus, the target network node may receive instructions from the AMF to start a new MBS session for the UE when the UE's MBS context is unavailable in the AMF.

[0105] Therefore, the target network node can obtain the UE's MBS context using one of the examples described above.

[0106] In step 210, method 200 includes determining provisioning PTM configuration information related to the MBS session to the UE. The target network node sends the PTM configuration information related to the MBS session to the UE. The PTM configuration information should be collected by the UE for receiving MBS data in idle or inactive states.

[0107] The PTM configuration information includes a service identifier, a session identifier, a Group Radio Network Temporary Identifier (G-RNTI), information relating to scheduling of PTM data, information instructing at least one neighboring node to transmit an MBS session, a PTM configuration for a cell served by a target network node, and a PTM configuration for one or more MBS sessions at the target network node, including a PTM configuration for an MBS session.

[0108] For example, a target network node may decide whether to provision PTM configuration information through a control channel. If the target network node decides to transmit PTM configuration information through a control channel, it may transmit PTM configuration information to the UE through a common control channel. For example, the target network node may transmit PTM configuration information through a common control channel in a System Information Block (SIB) that is periodically transmitted by network nodes.

[0109] In one example, the common control channel is the PTM downlink control channel. In an alternative example, the common control channel may be a newly defined multicast broadcast common control channel (MBCCH) that can be carried over a new PTM downlink control channel (DCCH), for example, a physical downlink shared channel (PDSCH) used for PTMs. Scheduling information for this common control channel, such as the repetition period, correction period, first subframe, offset, and DRX parameters, which allows the UE to know when to monitor for PTM collection, may be provided in a separate SIB where the scheduling information is known to the UE.

[0110] In one example, a target network node may send PTM configuration information to one or more UEs via a common control channel based on receiving a request for PTM configuration information from a UE that is in either an idle or inactive state.

[0111] In one example, a target network node receives a request for PTM configuration information from an idle or inactive UE. In response to the request from the UE for PTM configuration information, the target network node sends the PTM configuration information to the UE.

[0112] In some examples, the target network node may send a PTM configuration to the UE in message 4 (MSG4) when the UE is in an RRC inactive state. When a PTM configuration is sent in MSG4, the MSG4 from the target network node may include an SIB indicating the PTM configuration information, a new information element (IE) indicating the PTM configuration information, an instruction on whether the UE needs to change its RRC state in order to continue receiving MBS data from the target network node, and an instruction to restart a suspended PTP radio bearer when the UE is in an RRC inactive state.

[0113] In some examples, the target network node may send a PTM configuration to the UE in message 6 (MSG6) when the UE is in an RRC idle state. When a PTM configuration is sent in MSG6, the MSG6 from the target network node may include instructions on whether the UE needs to change its RRC state in order to continue receiving MBS data from the target network node, and whether a PTP radio bearer or a PTM radio bearer should be used to receive the MBS data.

[0114] In some examples, the target network node may send the PTM configuration to the source network node in a handover request acknowledgment message in response to receiving a handover request message from the source network node. Furthermore, the source network node sends the PTM configuration received from the target network node to the UE.

[0115] Furthermore, in some embodiments, the target network node may determine that the UE's MBS session is being provided to one or more additional UEs in the area served by the target network node using a point-to-point (PTP) bearer. When the target network node determines that the UE's MBS session is being provided to one or more additional UEs in the area served by the target network node using a PTP bearer, the target network node may decide to switch the PTP bearer to a PTM bearer for one or more additional UEs. Having decided to switch the PTP bearer to a PTM bearer for one or more additional UEs, the target network node may send a PTM configuration to one or more additional UEs for sending MBS data to the UEs. Thus, the additional UEs in the area served by the target network node, along with the UEs, may receive continued MBS transmissions from the target network node.

[0116] If the target network node determines that the UE's MBS session will not be provided to one or more additional UEs in the area served by the target network node, the target network node may initiate a new MBS session join procedure with the AMF. Once a new MBS session with the UE is initiated, the target network node may send instructions to the UE to use a PTP bearer to continue receiving MBS data from the target network node.

[0117] Figure 3 is a flowchart illustrating an exemplary method implemented by a source network node to enable a UE for continuous reception of MBS data. The source network node enables the handover of the UE to the target network node. Furthermore, the source network node enables the UE to receive the PTM settings of the target network node in order to continue receiving MBS data from the target network node.

[0118] In step 302, method 300 includes determining that the UE is in mobility and is engaged in an MBS session with a source network node. The source network node may determine the movement or mobility of the UE within or outside the area covered by the source network node. For example, source network node 101a may enable the UE to perform a handover of the UE to an adjacent network node, i.e., either network node 101b or 101c shown in Figure 1. Thus, any of the adjacent network nodes of source network node 101a shown in Figure 1 may be the target network node for the UE to perform a handover from the source network node to the target network node. Furthermore, the source network node may also determine the UE's MBS session when the UE is being served by the target network node. The source network node may also identify the MBS context of the UE involved in the MBS session. Furthermore, the source network node may identify the UE's MBS context using a context identifier assigned by the source network node.

[0119] In step 308, method 300 includes transmitting an MBS context related to an MBS session to one or more neighboring network nodes while the UE is in mobility. One or more neighboring network nodes may be target network nodes for the UE after the handover from the source network node. Thus, the source network node transmits the UE's MBS context to one or more neighboring nodes which may be target network nodes for the UE after the handover from the source network node. Thus, one or more neighboring network nodes or target network nodes may receive the UE's MBS context so that one or more neighboring network nodes may receive the UE's MBS context in advance in order to provide the UE with a continuing MBS after the handover from the source network node.

[0120] In some embodiments, sending an MBS context related to an MBS session to one or more neighboring network nodes while the UE is in mobility includes determining that the UE is connected during mobility. When the UE is connected, the source network node receives a handover request message from the UE and sends a handover request message to one or more neighboring network nodes, i.e., the target network node, containing the UE's MBS context related to the MBS session.

[0121] Furthermore, the source network node receives PTM configuration information from one or more neighboring network nodes in a handover request acknowledgment message containing MBS session configuration information, and the source network node sends an RRC reconfiguration message to the UE containing the MBS session configuration information. Thus, the source network node sends an RRC reconfiguration message to the UE containing the neighboring network node's PTM configuration information to enable the UE to receive continued MBS transmissions from the neighboring network node, i.e., the target network node.

[0122] Figure 4 is a flowchart illustrating an exemplary method 400 performed by a UE for receiving an MBS. As shown in Figure 1, the UE may be in mobility while being served by the source network node 101a in order to acquire the MBS from the source network node 101a. The UE may perform a handover from the source network node 101a to the target network node 101b, as shown in Figure 1. After performing the handover from the source network node to the target network node, the UE may perform method 400 to continue receiving the MBS from the target network node.

[0123] In step 402, method 400 includes determining that an MBS session with a source network node is in progress at the UE. The UE engages in an MBS session with a source network node when it is being served by the source network node. Therefore, the UE determines that an MBS session with a source network node is in progress.

[0124] In step 404, method 400 includes sending a message indicating that an MBS session is in progress with the source network node. After performing a handover to the target network node, the UE sends a message to the target network node indicating that an MBS session is in progress with the source network node.

[0125] In some embodiments, prior to sending a message to the target network node, the method includes determining that the UE is in one of the following states: RRC idle, RRC inactive, and RRC connected. When the UE is in the RRC idle or RRC inactive state, the method includes sending a message to the target network node instructing the UE to engage in an MBS session with the source network node.

[0126] In some cases, a message indicating that an MBS session with the source network node is in progress is sent during MSG3 or MSG5 of the random access procedure.

[0127] When a message is sent using the random access procedure MSG3, MSG3 includes a cause-based RRC setup request, a cause-based RRC restart request, an RRC system information request, instructions, and one or more temporary mobile group identifiers (TMGIs).

[0128] When a message is sent using the random access procedure MSG5, MSG5 includes an RRC setup complete message containing the TMGI and an RRC restart complete message containing the TMGI. Therefore, a message instructing the UE to engage in an MBS session with the source network node may be sent using the random access procedure MSG3 or MSG5.

[0129] In some embodiments, method 400 includes sending an MBS context related to the MBS session to a target network node, as shown by an optional step 406. In some examples, the MBS context of a UE related to an MBS session includes one or more of the following: a UE identifier, a session identifier, a TMGI, and a source node identifier.

[0130] To transmit the MBS context relating to the MBS session, Method 400 includes determining that the UE is in an RRC idle state. When the UE is idle, Method 400 includes obtaining MBS session information from the UE and transmitting information relating to the MBS session information, the transmitted information including one or more of the following: Serving Temporary Mobile Subscriber Identification Information (S-TMSI), Temporary Mobile Group Identification Information (TMGI), and Session Identifier (ID).

[0131] In step 408, method 400 includes deciding to receive PTM configuration information related to an MBS session. The PTM configuration information for an MBS session includes a service identifier, a session identifier, a G-RNTI, information relating to scheduling of PTM data, information instructing at least one neighboring node to transmit an MBS session, and PTM configuration information for one or more ongoing MBS sessions in a cell served by the target node.

[0132] In some examples, PTM settings may be received in MSG4 of the Random Access Procedure when the UE is in an inactive state. When PTM settings are received in MSG4, MSG4 may include an SIB indicating the PTM settings information, a new information element (IE) indicating the PTM settings information, an instruction on whether to change the RRC state to continue receiving MBS data from the target network node, an instruction to resume a suspended PTP radio bearer when the UE is in an RRC inactive state, and an instruction to set up a new PTP radio bearer when the UE is in an RRC connected state.

[0133] In some examples, the PTM setting is received in MSG6 of the random access procedure when the UE is idle. When the PTM setting is received in MSG6, MSG6 may include instructions on whether the UE should change the RRC state to continue receiving MBS data from the target network node, and whether a PTP radio bearer or a PTM radio bearer should be used to receive the MBS data.

[0134] In some cases, the PTM configuration is received from the source network node in a handover request acknowledgment message that includes MBS configuration information.

[0135] Therefore, the UE may receive the PTM configuration by any of the examples described above in order to continue receiving MBS data from the target network node after the handover from the source network node.

[0136] Figure 5 is a signal flow diagram illustrating exemplary operation in a wireless communication network initiated by a UE in mobility while RRC is inactive. In various embodiments of this disclosure, the UE indicates its interest in performing random access to a new RAN node, i.e., a target network node, and continuing to receive (one or more) MBS sessions, and receives a corresponding PTM configuration. The PTM configuration to be collected may include configurations for only (one or more) sessions of interest to the UE, or configurations for all ongoing sessions in the cell. Depending on the load conditions and service requirements, the target network node may provide the PTM configuration to the UE with or without transferring the UE to RRC_CONNECTED.

[0137] As shown in Figure 5, during mobility, UE103a moved from the source network node and handed over to the target network node 101b. The UE performs random access to the target network node 101b and, at 501, sends a random access preamble to the target network node 101b. At 502, UE103a receives a random access response message from the target network node 101b. The random access response message includes a UL grant for sending an MSG3 to the target network node. Using the UL grant, UE103a sends an MSG3 at 503 that contains a cause indicating that the UE is interested in the MBS session that the UE was receiving from the source network node. The MSG3 may be sent to the target network node 101b over the common control channel. Upon receiving MSG3 from UE103a, the target network node may, at 504a, receive the MBS context related to the MBS session from the last serving node 101a if that context is available at the last serving node 101, which is the source network node.

[0138] If the MBS context of UE103a related to the MBS session is unavailable at the last serving node 101a, the target network node 101b may, at 504b, initiate the MBS session join procedure with AMF105 if UE103a is the first UE for the MBS session. For example, if UE103a is the first UE interested in the session, it needs to communicate with AMF105 to join the session, obtain the MBS session context, and, at 504c, have NGAP route switching before it can deliver MBS data to UE103a.

[0139] Furthermore, UE103a receives PTM settings from target network node 101b in MSG4 via the downlink control channel at 505. Additionally, target network node 101b may instruct UE in MSG4 whether or not the UE should change the RRC state. Based on the instruction received in MSG4, the UE may remain in an inactive state, as shown in Figure 5, or the UE may enter a connected state.

[0140] UE103a sends MSG5 to target network node 101b informing it that UE has resumed the RRC connection with target network node 101b at 506. UE103a establishes an MBS session with AMF at 507 and receives MBS data. Furthermore, when the MBS session is started, UE releases the RRC connection with target network node 101b to enter an inactive state, and at 508, releases the RRC connection and then receives a transmission of MBS data from target network node 101b.

[0141] Figure 6 is a signal flow diagram illustrating exemplary operation in a wireless communication network, initiated by a UE in a mobility device that is in an RRC idle state.

[0142] As shown in Figure 6, during mobility, UE103a moved from the source network node and handed over to the target network node 101b. UE103a performs random access to the target network node 101b and, at 601, sends a random access preamble to the target network node 101b. At 602, UE103a receives a random access response message from the target network node 101b. The random access response message includes a UL grant for sending MSG3 to the target network node. Using the UL grant, UE103a sends MSG3, containing an RRC setup request, to the target network node 101b at 603. MSG3 can be sent to the target network node 101b over the common control channel. Upon receiving MSG3 from UE103a, the target network node 101b sends MSG4, with cause as RRC setup, to UE103a over the downlink control channel at 604. Furthermore, upon receiving MSG4, UE103a enters RRC connection state and, at 605, sends MSG5 along with TMGI, indicating that RRC setup is complete. Along with MSG5, UE103a indicates that it had received MBS data from the source network node and that it is interested in receiving the same MBS from the target network node 101b.

[0143] The target network node may receive the MBS context related to the MBS session from the last serving node 101a at 606aa if the MBS context is available at the last serving node 101, which is the source network node.

[0144] If the MBS context of UE103a related to the MBS session is unavailable at the last serving node 101a, the target network node 101b may, at 606b, initiate the MBS session join procedure with AMF105 if UE103a is the first UE for the MBS session. For example, if UE103a is the first UE interested in the session, it needs to communicate with AMF105 to join the session, obtain the MBS session context, and, at 606c, have NGAP route switching before it can deliver MBS data to UE103a.

[0145] Furthermore, UE103a receives PTM settings from target network node 101b in MSG6 via the downlink control channel at 607. Additionally, target network node 101b may instruct UE in MSG6 whether or not the UE should change its RRC state. Based on the instruction received in MSG6, the UE may remain idle, as shown in Figure 6.

[0146] At 608, UE103a establishes an MBS session with the AMF and receives MBS data. Furthermore, once the MBS session is started, at 609, the UE releases the RRC connection with the target network node 101b to enter an inactive state and continues to receive MBS data transmissions from the target network node 101b.

[0147] Figure 7 is an exemplary schematic diagram showing a functional module of a UE according to several embodiments. As shown in Figure 7, UE 103 may include, for example, an antenna 707 corresponding to antenna 4111 in Figure 10, and a transceiver circuit 701, also called a transceiver, corresponding to interface 4114 in Figure 10, which includes a transmitter and receiver configured to provide uplink and downlink radio communication with (one or more) base stations, also called a radio access network, corresponding to network node 4160 in Figure 10. UE 103 may also include a processing circuit 703, also called a processor, coupled to the transceiver circuit, corresponding to, for example, processing circuit 4120 in Figure 10, and a memory circuit 705, also called a memory, coupled to the processing circuit, corresponding to, for example, device-readable medium 4130 in Figure 10. The memory circuit 705 may include computer-readable program code that, when executed by the processing circuit 703, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 703 may be defined to include a memory such that a separate memory circuit is not required.

[0148] Various operations of the UE103 can be performed by the processing circuit 703 and / or the transceiver circuit 701. For example, the processing circuit 703 may control the transceiver circuit 701 to transmit communications to a radio access network node, which is a base station, via the transceiver circuit 701 over a radio interface, and / or receive communications from the base station via the transceiver circuit 701 over a radio interface. Furthermore, modules may be stored in the memory circuit 705, and these modules may provide instructions such that when the instructions of the module are executed by the processing circuit 703, the processing circuit 703 performs each of the operations defined in the steps shown in Figure 4.

[0149] Figure 8 is an exemplary schematic diagram showing functional modules of a radio access network node 101a / 101b according to several embodiments. As shown, the network node 101a / 101b may include a transceiver circuit 801 (also called a transceiver, for example, corresponding to the portion of interface 4190 in Figure 10) which includes a transmitter and receiver configured to provide uplink and downlink radio communication with a mobile terminal. The network node 101a / 101b may also include a network interface circuit 807 (also called a network interface, for example, corresponding to the portion of interface 4190 in Figure 10) which is configured to provide communication with other nodes in the radio access network and / or core network, for example, with other base stations. The network node 101a / 101b may also include a processing circuit 803 (also called a processor, for example, corresponding to processing circuit 4170) coupled to the transceiver circuit and a memory circuit 805 (also called a memory, for example, corresponding to device-readable medium 4180 in Figure 10) coupled to the processing circuit. The memory circuit 805 may include computer-readable program code that, when executed by the processing circuit 803, causes the processing circuit to perform the operations according to the embodiments disclosed in Figures 2 and 3. In some embodiments, the processing circuit 803 may be defined to include memory such that a separate memory circuit is not required.

[0150] Various operations of network nodes 101a / 101b can be performed by the processing circuit 803, the network interface 807, and / or the transceiver 801. For example, the processing circuit 803 may control the transceiver 801 to transmit downlink communications to one or more UEs via the transceiver 801 on the radio interface, and / or receive uplink communications from one or more UEs via the transceiver 801 on the radio interface. Similarly, the processing circuit 803 may control the network interface 807 to transmit communications to one or more other network nodes via the network interface, and / or receive communications from one or more other network nodes via the network interface. Furthermore, modules may be stored in memory 805, and these modules may provide instructions such that when the module's instructions are executed by the processing circuit 803, the processing circuit 803 performs its respective operations, for example, the operations described below with respect to embodiments relating to the network nodes described in Figures 2 and 3.

[0151] In some embodiments, network nodes 101a / 101b may be implemented as core network (CN) nodes without transceivers. In such embodiments, transmission to the UE may be initiated by network nodes 101a / 101b so that transmission to the UE is provided through network nodes 101a / 101b that include transceivers, for example, through base stations or RAN nodes.

[0152] Figure 9 is an exemplary schematic diagram showing functional modules of a core network (CN) node 900 according to several embodiments. The CN node 900 may be a session management function (SMF) or an access and mobility management function (AMF). The CN node 900 may include a network interface 907 configured to provide communication with other nodes in the core network and / or RAN. The CN node 900 may include a processor 903 coupled to the network interface 907 and a memory 905 coupled to the processor 903. The memory 905 may contain computer-readable program code that, when executed by the processor 903, causes processing circuits to perform various steps described in Figures 2 and 3.

[0153] Various operations of the CN node 900 can be performed by the processor 903 and / or the network interface 907. For example, the processor 903 may control the network interface 907 to send communications to and / or receive communications from one or more other network nodes through the network interface 907. Furthermore, modules may be stored in memory 905, and these modules may provide instructions such that when the instructions of the modules are executed by the processor 903, the processor 903 performs the respective operations described in Figures 2 and 3.

[0154] Figure 10 is another block diagram of a wireless network according to several embodiments. The subject matter described herein can be implemented in any suitable type of system using any preferred components, but the embodiments disclosed herein are described in relation to wireless networks such as the exemplary wireless network shown in Figure 10. For simplicity, the wireless network in Figure 10 illustrates only the network 4106, network nodes 4160 and 4160b, and WDs 4110, 4110b, and 4110c (also called mobile terminals). In practice, a wireless network may further include any additional elements suitable for supporting communication between wireless devices, or communication between wireless devices and other communication devices such as fixed telephones, service providers, or any other network nodes or end devices. Of the components shown, network node 4160 and wireless devices (WDs) 4110 are illustrated with additional details. A wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices' access to the wireless network and / or use of services provided by or through the wireless network.

[0155] A wireless network may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or wireless network, or other similar types of systems. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, a particular embodiment of a wireless network may implement communication standards such as the Pan-European Digital Mobile Telephone System (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 such as the IEEE 802.11 standard, and / or any other suitable wireless communication standards such as Global Interoperability for Microwave Access (WiMAX), Bluetooth, Z-Wave, and / or ZigBee standards.

[0156] Network 4106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

[0157] Network nodes 4160 and WD4110 comprise various components, which are described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0158] As used herein, a network node refers to a device that is configured, set up, and / or operable to communicate directly or indirectly with a radio device and / or with other network nodes or devices in a radio network for the purpose of enabling and / or providing radio access to the radio device and / or performing other functions in the radio network (e.g., administration). 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 B, evolved node B (eNB), and NR node B (gNB)). Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power level), in which case they may be called femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or relay donor node that controls relays. Network nodes may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or remote radio unit (RRU), sometimes called a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station are sometimes called nodes in a distributed antenna system (DAS). Further examples of network nodes include MSR equipment such as multistandard radio (MSR) BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base station transceiver stations (BTS), transmit points, transmit nodes, multicell / multicast cooperative entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC), and / or MDT. As another example, a network node may be a virtual network node, as will be described in more detail below.However, more generally, a network node may represent any suitable device (or group of devices) that is configured, set up, and / or operational to enable, and / or provide access to a wireless network to wireless devices, or to wireless devices that have accessed the wireless network.

[0159] In Figure 10, the network node 4160 includes a processing circuit 4170, a device-readable medium 4180, an interface 4190, auxiliary equipment 4184, a power supply 4186, a power circuit 4187, and an antenna 4162. While the network node 4160 shown in the exemplary wireless network of Figure 10 may represent a device comprising the shown combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of the network node 4160 are illustrated as a single box located within a larger box, or as a single box nested within multiple boxes, in practice, a network node may comprise multiple different physical components that constitute a single shown component (for example, the device-readable medium 4180 may comprise multiple separate hard drives and multiple RAM modules).

[0160] Similarly, network node 4160 may be assembled from multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own respective components. In some scenarios where network node 4160 has multiple distinct components (e.g., BTS components and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. 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 RATs). The network node 4160 may also include multiple sets of various indicated components for different radio technologies, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth radio technologies, which are integrated into the network node 4160. These radio technologies may be integrated into the same or different chips or sets of chips, and other components within the network node 4160.

[0161] The processing circuit 4170 is configured to perform any decision, calculation, or similar operations (e.g., several acquisition operations) provided by the network node, as described herein. These operations performed by the processing circuit 4170 may include processing the information acquired by the processing circuit 4170, for example by 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 as a result of the decisions made by the processing.

[0162] The processing circuit 4170 may comprise one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, capable of operating to provide network node 4160 functionality, either alone or in conjunction with other network node 4160 components such as the device-readable medium 4180. For example, the processing circuit 4170 may execute instructions stored in the device-readable medium 4180 or instructions stored in memory within the processing circuit 4170. Such functionality may include providing any of the various radio features, functions, or benefits described herein. In some embodiments, the processing circuit 4170 may include a system-on-a-chip (SOC).

[0163] In some embodiments, the processing circuit 4170 may include one or more of the radio frequency (RF) transceiver circuit 4172 and the baseband processing circuit 4174. In some embodiments, the radio frequency (RF) transceiver circuit 4172 and the baseband processing circuit 4174 may be on separate chips (or sets of chips), boards, or units such as radio and digital units. In alternative embodiments, some or all of the RF transceiver circuit 4172 and the baseband processing circuit 4174 may be on the same chip or set of chips, board, or unit.

[0164] 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 implemented by a processing circuit 4170 that executes instructions stored in a device-readable medium 4180 or in memory within the processing circuit 4170. In alternative embodiments, some or all of the functions may be provided by the processing circuit 4170 without executing instructions stored in a separate or individual device-readable medium, such as in a hardwired manner. In any of those embodiments, whether or not it executes instructions stored in a device-readable storage medium, the processing circuit 4170 may be configured to implement the functions described. The benefits provided by such functions are enjoyed by the processing circuit 4170 alone, or by the network node 4160 as a whole, but not limited to other components of the network node 4160, and / or generally by the end user and the wireless network.

[0165] The device-readable medium 4180 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid memory, remote-mount memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuit 4170. The device-readable medium 4180 may store any suitable instructions, data, or information, including other instructions, that can be executed by the processing circuit 4170 and utilized by the network node 4160, including applications that include one or more computer programs, software, logic, rules, code, tables, etc. The device-readable medium 4180 may be used to store calculations performed by the processing circuit 4170 and / or data received via the interface 4190. In some embodiments, the processing circuit 4170 and the device-readable medium 4180 may be considered integrated.

[0166] Interface 4190 is used in wired or wireless signaling and / or data between network node 4160, network 4106, and / or WD 4110. As shown, interface 4190 includes (one or more) ports / (one or more) terminals 4194 for sending and receiving data to and from network 4106, for example, over a wired connection. Interface 4190 also includes a wireless front-end circuit 4192, which is coupled to or, in some embodiments, may be part of antenna 4162. The wireless front-end circuit 4192 includes a filter 4198 and an amplifier 4196. The wireless front-end circuit 4192 may be connected to antenna 4162 and processing circuit 4170. The wireless front-end circuit may be configured to adjust signals communicated between antenna 4162 and processing circuit 4170. The wireless front-end circuit 4192 may receive digital data to be sent to other network nodes or WDs via the wireless connection. The wireless front-end circuit 4192 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 4198 and / or amplifier 4196. The radio signal can then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit 4192. The digital data can then be passed to processing circuit 4170. In other embodiments, the interface may comprise different components and / or different combinations of components.

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

[0168] Antenna 4162 may include one or more antennas or antenna arrays configured to transmit and / or receive radio signals. Antenna 4162 may be coupled to the radio front-end circuit 4192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 4162 may comprise one or more omnidirectional, sector, or panel antennas capable of transmitting / receiving radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from devices within a specific area, and panel antennas may be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of two or more antennas may be referred to as MIMO. In some embodiments, antenna 4162 may be separate from the network node 4160 and may be connectable to the network node 4160 through an interface or port.

[0169] Antenna 4162, interface 4190, and / or processing circuit 4170 may be configured to perform any receiving operations and / or certain acquisition operations as described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 4162, interface 4190, and / or processing circuit 4170 may be configured to perform any transmitting operations as described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0170] The power circuit 4187 may include or be coupled to a power management circuit and be configured to supply power to the components of the network node 4160 to perform the functions described herein. The power circuit 4187 may receive power from a power supply 4186. The power supply 4186 and / or the power circuit 4187 may be configured to supply power to the various components of the network node 4160 in a manner suitable for each component (for example, at the voltage and current levels required for each respective component). The power supply 4186 may be included in the power circuit 4187 and / or the network node 4160, or it may be outside the power circuit 4187 and / or the network node 4160. For example, the network node 4160 may be connectable to an external power supply (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, thereby the external power supply supplying power to the power circuit 4187. As a further example, power supply 4186 may include a power source in the form of a battery or battery pack, connected to or integrated within power circuit 4187. The battery may provide backup power in the event of an external power failure. Other types of power sources, such as photovoltaic devices, may also be used.

[0171] Alternative embodiments of network node 4160 may include additional components other than those shown in Figure 10 that may be responsible for providing several aspects of the network node's functionality, including any of the functions described herein and / or functions necessary to support the subject matter described herein. For example, network node 4160 may include user interface equipment for enabling information input to and output from network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 4160.

[0172] As used herein, a wireless device (WD) refers to a UE or device that is capable, configured, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD may be used interchangeably with UE herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information in 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 transmit information to a network on 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, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop onboard devices (LMEs), smart devices, wireless customer equipment (CPEs), and in-vehicle wireless terminal devices. WDs may also support D2D (device-to-device) communication by implementing 3GPP standards for sidelink communication, V2V (Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure), and V2X (Vehicle-to-Everything), in which case they may be called D2D communication devices.

[0173] In another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, a WD may be a machine-to-machine (M2M) device, which is sometimes called an MTC device in a 3GPP context. In one specific example, a WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices include sensors, measuring devices such as power meters, industrial machinery, or household or personal electrical appliances such as refrigerators, televisions, and personal wearables such as watches and fitness trackers. In other scenarios, a WD may represent a vehicle or other equipment that can monitor its operational status and / or report on its operational status, or perform other functions associated with its operation. The WDs described above may represent wireless connectivity endpoints, in which case the device may be called a wireless terminal. Furthermore, the WD described above can be mobile, in which case the device may also be called a mobile device or mobile terminal.

[0174] As shown, the wireless device 4110 includes an antenna 4111, an interface 4114, a processing circuit 4120, a device-readable medium 4130, a user interface device 4132, an auxiliary device 4134, a power supply 4136, and a power circuit 4137. The WD4110 may include one or more sets of the shown components for different wireless technologies supported by the WD4110, such as, to name just a few, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or sets of chips as the other components within the WD4110.

[0175] Antenna 4111 may include one or more antennas or antenna arrays configured to transmit and / or receive radio signals and connected to interface 4114. In some alternative embodiments, antenna 4111 may be separate from WD4110 and connectable to WD4110 through 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 being performed by a WD. Any information, data, and / or signals may be received from network nodes and / or other WDs. In some embodiments, the radio front-end circuitry and / or antenna 4111 may be considered an interface.

[0176] As shown, interface 4114 comprises a radio front-end circuit 4112 and an antenna 4111. The radio front-end circuit 4112 comprises one or more filters 4118 and an amplifier 4116. The radio front-end circuit 4112 is connected to the antenna 4111 and a processing circuit 4120 and is configured to adjust signals communicated between the antenna 4111 and the processing circuit 4120. The radio front-end circuit 4112 may be coupled to or be part of the antenna 4111. In some embodiments, the WD 4110 may not include a separate radio front-end circuit 4112; rather, the processing circuit 4120 may comprise the radio front-end circuit and be connected to the antenna 4111. Similarly, in some embodiments, part or all of the RF transceiver circuit 4122 may be considered part of interface 4114. The radio front-end circuit 4112 may receive digital data to be sent to other network nodes or WDs via the radio connection. The wireless front-end circuit 4112 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 4118 and / or amplifier 4116. The radio signal can then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit 4112. The digital data can then be passed to processing circuit 4120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0177] The processing circuit 4120 may comprise one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, either alone or in combination with other WD4110 components such as the device-readable medium 4130, that are capable of operating to provide WD4110 functionality. Such functionality may include providing any of the various radio features or benefits described herein. For example, the processing circuit 4120 may execute instructions stored in the device-readable medium 4130 or instructions stored in memory within the processing circuit 4120 in order to provide the functionality disclosed herein.

[0178] As shown, the processing circuit 4120 includes one or more of the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuit 4120 of WD4110 may comprise a SOC. In some embodiments, the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126 may reside on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuit 4124 and the application processing circuit 4126 may be combined to form a single chip or set of chips, while the RF transceiver circuit 4122 may reside on a separate chip or set of chips. In further alternative embodiments, some or all of the RF transceiver circuit 4122 and the baseband processing circuit 4124 may reside on the same chip or set of chips, while the application processing circuit 4126 may reside on a separate chip or set of chips. 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 set of chips. In some embodiments, the RF transceiver circuit 4122 may be part of the interface 4114. The RF transceiver circuit 4122 may adjust the RF signal for the processing circuit 4120.

[0179] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 4120 that executes instructions stored in a device-readable medium 4130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 4120 without executing instructions stored in a separate or individual device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuit 4120 may be configured to perform the functions described, whether or not it executes instructions stored in a device-readable storage medium. The benefits provided by such functions are enjoyed by the processing circuit 4120 alone, or by the WD4110 as a whole, but not limited to other components of the WD4110, and / or generally by the end user and the wireless network.

[0180] The processing circuit 4120 may be configured to perform any decision, calculation, or similar operations (e.g., several acquisition operations) as described herein as being performed by the WD. These operations, such as those performed by the processing circuit 4120, may include processing the information acquired by the processing circuit 4120, for example by converting the acquired information into other information, comparing the acquired or converted information with information stored by the WD 4110, and / or performing one or more operations based on the acquired or converted information and as a result of the decisions made by the processing.

[0181] The device-readable medium 4130 may be operable to store applications, including one or more computer programs, software, logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuit 4120. The device-readable medium 4130 may include computer memory, such as random access memory (RAM) or read-only memory (ROM), mass storage media, such as hard disks, removable storage media, and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuit 4120. In some embodiments, the processing circuit 4120 and the device-readable medium 4130 may be considered integrated.

[0182] The user interface device 4132 may provide components that enable a human user to interact with the WD4110. Such interaction can take many forms, such as visual, auditory, or tactile. The user interface device 4132 may be operable to produce an output to the user and to enable the user to provide input to the WD4110. The type of interaction may vary depending on the type of user interface device 4132 installed on the WD4110. For example, if the WD4110 is a smartphone, the interaction may be via a touchscreen; if the WD4110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 4132 may include an input interface, device, and circuitry, as well as an output interface, device, and circuitry. The user interface device 4132 is configured to enable the input of information to the WD4110 and is connected to the processing circuit 4120 to enable the processing circuit 4120 to process the input information. The user interface device 4132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 4132 is also configured to enable the output of information from the WD4110, and to enable the processing circuit 4120 to output information from the WD4110. The user interface device 4132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 4132, the WD4110 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functions described herein.

[0183] Auxiliary equipment 4134 can be operated to provide more specific functions that may not generally be implemented by WD. These may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, and so on. The inclusion and types of components of auxiliary equipment 4134 may vary depending on the embodiment and / or scenario.

[0184] In some embodiments, the 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, for example, an electrical outlet, a photovoltaic device, or a battery. The WD4110 may further comprise a power circuit 4137 for distributing power from the power supply 4136 to various parts of the WD4110 that require power from the power supply 4136 to perform any function described or indicated herein. In some embodiments, the power circuit 4137 may comprise a power management circuit. The power circuit 4137 may, as an addition or alternative, be operable to receive power from an external power supply, in which case the WD4110 may be connectable to the external power supply (such as an electrical outlet) via an input circuit or interface such as a power cable. The power circuit 4137 may also, in some embodiments, be operable to distribute power from an external power supply to the power supply 4136. This may be, for example, for charging the power supply 4136. The power circuit 4137 may perform any formatting, converting, or other modifications to the power from the power supply 4136 to make that power suitable for each component of the WD4110 to which it is supplied.

[0185] Figure 11 is another block diagram of exemplary user equipment in several embodiments. The UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device, e.g., a smart sprinkler controller, that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, or may not initially be associated with a particular human user. Alternatively, a UE may represent a device, e.g., a smart power meter, that is 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. UE4200 may be any UE identified by 3GPP, including NB-IoT UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs. UE4200 shown in Figure 11 is an example of a WD configured for communication by one or more communication standards published by 3GPP, such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As mentioned above, the terms WD and UE can be used interchangeably. Therefore, although Figure 10 is a UE, the components described herein are equally applicable to WDs, and vice versa.

[0186] In Figure 10, the UE4200 includes an input / output interface 4205, a radio frequency (RF) interface 4209, a network connectivity interface 4211, memory 4215 including random access memory (RAM) 4217 and read-only memory (ROM) 4219 and storage medium 4221, a communication subsystem 4231, a power supply 4213, and / or any other components, or any combination thereof, operably coupled to processing circuits 4201. The storage medium 4221 includes an operating system 4223, an application program 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. Some UEs may utilize all of the components shown in Figure 11, or only a subset of those components. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0187] In Figure 11, the processing circuit 4201 may be configured to process computer instructions and data. The processing circuit 4201 may be configured to implement one or more programmable, general-purpose processors, or any combination thereof, such as one or more hardware-implemented state machines in discrete logic, FPGAs, ASICs, etc., any sequential state machine capable of executing machine instructions stored in memory as machine-readable computer programs, programmable logic with appropriate firmware, or a microprocessor or digital signal processor (DSP) with appropriate software. For example, the processing circuit 4201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0188] In the illustrated embodiment, the input / output interface 4205 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE4200 may be configured to use an output device via the input / output interface 4205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE4200. The output device may be a speaker, sound card, video card, display, monitor, printer, actuator, emitter, smart card, another output device, or any combination thereof. The UE4200 may be configured to use an input device via the input / output interface 4205 to allow a user to capture information to the UE4200. The input device may include a touch-sensitive or presence-sensitive display, camera, microphone, sensor, mouse, trackball, directional pad, trackpad, scroll wheel, smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for detecting input from the user. The sensors could be, for example, an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, light sensor, proximity sensor, another similar sensor, or any combination thereof. For example, the input devices could be an accelerometer, magnetometer, digital camera, microphone, and light sensor.

[0189] In Figure 11, the RF interface 4209 may be configured to provide a communication interface to RF components such as a transmitter, receiver, and antenna. The network connection interface 4211 may be configured to provide a communication interface to network 4243a. Network 4243a may encompass wired and / or wireless networks, such as a local area network (LAN), wide area network (WAN), computer network, wireless network, communication network, another similar network, or any combination thereof. For example, network 4243a may include a Wi-Fi network. The network connection interface 4211 may be configured to include receiver and transmitter interfaces used to communicate with one or more other devices on the communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 4211 may implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0190] RAM 4217 may be configured to interface with processing circuit 4201 via bus 4202 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, application programs, and device drivers. ROM 4219 may be configured to provide computer instructions or data to processing circuit 4201. For example, ROM 4219 may be configured to store immutable low-level system code or data for basic system functions, such as basic input / output (I / O), startup, or receiving keystrokes from a keyboard, which are stored in non-volatile memory. Storage medium 4221 may 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), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. For example, the storage medium 4221 may be configured to contain an operating system 4223, an application program 4225 such as a web browser application, a widget or gadget engine, or another application, and a data file 4227. The storage medium 4221 may store any of a variety of operating systems or combinations of operating systems for use by the UE4200.

[0191] The storage medium 4221 may be configured to include several 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 disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external microDIMM SDRAM, smart card memory such as a subscriber identification module or removable user identification information (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 4221 may enable the UE4200 to access computer executable instructions, application programs, etc., stored in temporary or non-temporary memory media, to offload data, or to upload data. Products such as products utilizing a communication system may be tangibly embodied in the storage medium 4221, and the storage medium 4221 may include a device-readable medium.

[0192] In Figure 11, the processing circuit 4201 may be configured to communicate with network 4243b using the communication subsystem 4231. Networks 4243a and 4243b may be the same one or more networks or different one or more networks. The communication subsystem 4231 may be configured to include one or more transceivers used to communicate with network 4243b. For example, the communication subsystem 4231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another wirelessly wirelessly capable device, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, or WiMax. Each transceiver may include a transmitter 4233 and / or a receiver 4235 to implement transmitter or receiver functions suitable for a RAN link, respectively. Furthermore, the transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0193] 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 the Global Positioning System (GPS) to determine location, other similar communication functions, 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 communication 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.

[0194] The features, benefits, and / or functions described herein may be implemented in one of the components of the UE4200 or distributed across multiple components of the UE4200. 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. Furthermore, the processing circuit 4201 may be configured to communicate with any of such components on the bus 4202. In another example, any of such components may be represented by a program instruction stored in memory that, when executed by the processing circuit 4201, performs the corresponding function described herein. In yet another example, the function of any of such components may be distributed between the processing circuit 4201 and the communication subsystem 4231. In yet another example, the non-computationally intensive function of any of such components may be implemented in software or firmware, while the computationally intensive function may be implemented in hardware.

[0195] Figure 12 is a block diagram of a virtualization environment 4300 in which functions implemented by several embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may be applied to nodes, for example, a virtualized base station or a virtualized radio access node, or to devices, for example, a UE, a radio device or any other type of communication device, or components of such devices, and relates to an implementation form in which at least a portion of the functions are implemented as one or more virtual components, for example, via one or more applications, components, functions, virtual machines or containers that run on one or more physical processing nodes in one or more networks.

[0196] 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 by one or more of the hardware nodes 4330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity, the network nodes may be fully virtualized.

[0197] The functionality may be implemented by one or more applications 4320, which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc., and which are capable of operating to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The application 4320 runs in a virtualized environment 4300 that provides hardware 4330 comprising a processing circuit 4360 and memory 4390. The memory 4390 contains instructions 4395 that can be executed by the processing circuit 4360, thereby enabling the application 4320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0198] The virtualization environment 4300 comprises a general-purpose or dedicated network hardware device 4330 having one or more sets of processors or processing circuits 4360, where the set of processors or processing circuits 4360 may be commercial off-the-shelf (COTS) processors, dedicated application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or dedicated processors. Each hardware device may include memory 4390-1, which may be non-persistent memory for temporarily storing instructions 4395 or software executed by the processing circuits 4360. Each hardware device may also include one or more network interface controllers (NICs) 4370, also known as network interface cards, where the network interface controllers (NICs) 4370 include a physical network interface 4380. Each hardware device may also include a non-temporary, persistent, machine-readable storage medium 4390-2 storing software 4395 and / or instructions executable by the processing circuits 4360. Software 4395 may include any type of software, including software for instantiating one or more virtualization layers 4350, software for running virtual machines 4340, and software that enables it to perform the functions, features and / or benefits described in relation to some embodiments described herein.

[0199] A virtual machine 4340 comprises virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may run on a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the virtual appliance 4320 may be implemented on one or more of the virtual machines 4340, and the implementation may be carried out in different ways.

[0200] During operation, the processing circuit 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which is sometimes referred to as the virtual machine monitor (VMM). The virtualization layer 4350 may present the virtual machine 4340 with a virtual operating platform that resembles networking hardware.

[0201] As shown in Figure 12, hardware 4330 may be a standalone network node with general or specific components. Hardware 4330 may be equipped with antenna 43225 and may implement several functions through virtualization. Alternatively, hardware 4330 may be part of a larger cluster of hardware, such as in a data center or customer premises equipment, where many hardware nodes cooperate and are managed via Management and Orchestration (MANO) 43100, which oversees the lifecycle management of applications 4320.

[0202] Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage that may reside in data centers and customer premises equipment.

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

[0204] Furthermore, in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running on one or more virtual machines 4340 on the hardware networking infrastructure 4330, corresponding to application 4320 in Figure 12.

[0205] One or more radio units 43200, each including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio units 43200 may communicate directly with hardware nodes 4330 via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0206] Some form of signaling may be implemented using a control system 43230, which can be used as an alternative for communication between the hardware node 4330 and the wireless unit 43200.

[0207] Figure 13 is a block diagram of a communication network connected to a host computer via an intermediate network, according to several embodiments. Referring to Figure 13, according to one embodiment, the communication system includes a communication network 4410, such as a 3GPP type cellular network, comprising an access network 4411, such as a radio access network, and a core network 4414. The access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to the core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to a corresponding base station 4412c or to be paged by a corresponding base station 4412c. A second UE 4492 in coverage area 4413a can wirelessly connect to the corresponding base station 4412a. Although multiple UEs 4491, 4492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area, or where only one UE is connected to the corresponding base station 4412.

[0208] The communication network 4410 is itself connected to the host computer 4430, which may be embodied in the hardware and / or software of a standalone server, a cloud implementation server, a distributed server, or as a processing resource in a server farm. The host computer 4430 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 4421 and 4422 between the communication network 4410 and the host computer 4430 may extend directly from the core network 4414 to the host computer 4430, or may proceed via an optional intermediate network 4420. The intermediate network 4420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of these, and the intermediate network 4420 may be a backbone network or the internet, if any, and in particular may comprise two or more subnets (not shown).

[0209] The communication system in Figure 13, as a whole, enables connectivity between the connected UEs 4491 and 4492 and the host computer 4430. This connectivity can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491 and 4492 are configured to communicate data and / or signaling over the OTT connection 4450, using the access network 4411, the core network 4414, an optional intermediate network 4420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 4450 can be transparent in the sense that participating communication devices through which the OTT connection 4450 passes are unaware of the routing of uplink and downlink communications. For example, base station 4412 may not be aware of, or does not need to be aware of, the past routing of incoming downlink communications with data originating from the host computer 4430 that should be forwarded (e.g., handed over) to the connected UE 4491. Similarly, base station 4412 does not need to be aware of the future routing of outgoing uplink communications originating from UE4491 and destined for host computer 4430.

[0210] Figure 14 is a block diagram of a host computer communicating with user equipment via a base station over a partial wireless connection. Next, an exemplary implementation of the UE, base station, and host computer described in the previous paragraph, according to one embodiment, will be described with reference to Figure 14. In the communication system 4500, the host computer 4510 comprises hardware 4515, including a communication interface 4516 configured to set up and maintain wired or wireless connections with the interfaces of different communication devices of the communication system 4500. The host computer 4510 further comprises processing circuitry 4518, which may have memory and / or processing capabilities.

[0211] In particular, the processing circuit 4518 may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 4510 further comprises software 4511, which is stored in or accessible by the host computer 4510 and executable by the processing circuit 4518. The software 4511 includes a host application 4512. The host application 4512 may be capable of operating to serve remote users, such as the UE 4530 connected via an OTT connection 4550 terminating at the host computer 4510. When serving remote users, the host application 4512 may provide user data transmitted using the OTT connection 4550.

[0212] The communication system 4500 further includes a base station 4520 provided within the communication system, the base station 4520 comprising hardware 4525 that enables the base station 4520 to communicate with the host computer 4510 and the UE 4530. The hardware 4525 may include a communication interface 4526 for setting up and maintaining wired or wireless connections with the interfaces of different communication devices of the communication system 4500, and a wireless interface 4527 for setting up and maintaining at least a wireless connection 4570 with the UE 4530 located in the coverage area (not shown in Figure 13) served by the base station 4520. The communication interface 4526 may be configured to facilitate a connection 4560 to the host computer 4510. The connection 4560 may be direct, or the connection 4560 may pass through the core network of the communication system (not shown in Figure 14) and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 4525 of the base station 4520 further includes a processing circuit 4528, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown), adapted to execute instructions. The base station 4520 further includes software 4521, which is stored internally or accessible via an external connection.

[0213] The communication system 4500 further includes the UE4530 already mentioned. The hardware 4535 of the UE4530 may include a radio interface 4537 configured to set up and maintain a radio connection 4570 with a base station serving the coverage area in which the UE4530 is currently located. The hardware 4535 of the UE4530 further includes a processing circuit 4538, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. The UE4530 further includes software 4531, which is stored in or accessible by the UE4530 and executable by the processing circuit 4538. The software 4531 includes a client application 4532. The client application 4532 may be capable of operating to provide services to human or non-human users via the UE4530 with the support of a host computer 4510. On the host computer 4510, the running host application 4512 can communicate with the running client application 4532 via the UE 4530 and an OTT connection 4550 that terminates on the host computer 4510. When providing services to a user, the client application 4532 can receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 can transfer both the request data and the user data. The client application 4532 can interact with the user to generate the user data that the client application 4532 provides.

[0214] It should be noted that the host computer 4510, base station 4520, and UE4530 shown in Figure 17 may be similar to or equivalent to the host computer 4430, one of the base stations 4412a, 4412b, and 4412c, and one of the UE4491 and 4492, respectively, in Figure 16. In other words, the internal workings of these entities may be as shown in Figure 14, and separately, the surrounding network topology may be as shown in Figure 13.

[0215] In Figure 14, the OTT connection 4550 is depicted abstractly to illustrate communication between the host computer 4510 and the UE 4530 via the base station 4520, without explicit reference to the intermediary devices and the precise routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 4530, the service provider operating the host computer 4510, or both. While the OTT connection 4550 is active, the network infrastructure may also make decisions to dynamically change the routing (for example, based on network load balancing considerations or reconfiguration).

[0216] The radio connection 4570 between the UE4530 and the base station 4520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of the OTT services provided to the UE4530 by using an OTT connection 4550 in which the radio connection 4570 forms the final segment. More precisely, the teachings of these embodiments may improve random access speed and / or reduce random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0217] Measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved in one or more embodiments. Optional network functions may further be provided for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to variations in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 4550 may be implemented in software 4511 and hardware 4515 of the host computer 4510, or in software 4531 and hardware 4535 of the UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or in relation to a communication device through which the OTT connection 4550 passes, and the sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above, or values ​​of other physical quantities that the software 4511, 4531 can calculate or estimate the monitored quantities of. The reconfiguration of the OTT connection 4550 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration may not need to affect the base station 4520, and may be unknown to or imperceptible to the base station 4520. Such procedures and functions are known and practiced in the art. In some embodiments, the measurement may be accompanied by proprietary UE signaling that facilitates the measurement of the host computer 4510, such as throughput, propagation time, latency, etc. The measurement may be implemented in which software 4511 and 4531 causes messages, in particular empty or "dummy" messages, to be sent using the OTT connection 4550 while software 4511 and 4531 monitor propagation time, errors, etc.

[0218] Figure 15 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to several embodiments. The communication system includes a host computer, a base station, and a UE, which may be described with reference to Figures 10-11. For the sake of simplicity of this disclosure, only a drawing reference to Figure 15 is included in this section. In step 4610, the host computer provides user data. In an optional substep 4611 of step 4610, the host computer provides user data by executing a host application. In step 4620, the host computer initiates a transmission that carries the user data to the UE. In an optional step 4630, the base station transmits the user data carried in the transmission initiated by the host computer to the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional step 4640, the UE executes a client application related to the host application executed by the host computer.

[0219] Figure 16 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to several embodiments. The communication system may include a host computer, a base station, and an UE, as described with reference to Figures 10-11. For the sake of simplicity of this disclosure, only a drawing reference to Figure 16 is included in this section. In step 4710 of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides user data by executing a host application. In step 4720, the host computer initiates a transmission to carry the user data to the UE. The transmission may proceed via the base station as taught in the embodiments described throughout this disclosure. In (optional) step 4730, the UE receives the user data carried in the transmission.

[0220] Figure 17 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to several embodiments. The communication system includes a host computer, a base station, and a UE, which may be described with reference to Figures 10-11. For the sake of simplicity of this disclosure, only a drawing reference to Figure 16 is included in this section. In (optional) step 4810, the UE receives input data provided by the host computer. In addition or alternatively, in step 4820, the UE provides user data. In (optional) substep 4821 of step 4820, the UE provides user data by running a client application. In (optional) substep 4811 of step 4810, the UE runs a client application that provides user data in response to received input data provided by the host computer. When providing user data, the run client application may further consider user input received from the user. Regardless of the particular format in which the user data is provided, in (optional) substep 4830, the UE initiates transmission of the user data to the host computer. In step 4840 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0221] Figure 18 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment according to several embodiments. Figure 18 is a flowchart of a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and an UE, which may be described with reference to Figures 10-11. For the sake of simplicity of this disclosure, only a drawing reference to Figure 18 is included in this section. In (optional) step 4910, the base station receives user data from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In (optional) step 4920, the base station initiates a transmission of the received user data to the host computer. In (optional) step 4930, the host computer receives the user data carried in the transmission initiated by the base station.

[0222] Any suitable step, method, feature, function, or benefit disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuits, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuits 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 may include program instructions for executing one or more communication and / or data communication protocols, and instructions for performing one or more of the techniques described herein. In some implementations, the processing circuits may be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the Disclosure.

[0223] Figure 19 discloses an exemplary computing environment 1900 that implements a method for transmitting MBS services to a UE and network nodes and UEs, as described in Figures 2, 3, and 4. As shown in Figure 19, the computing environment 1900 comprises at least one data processing unit 1906 equipped with a control unit 1902 and an arithmetic logic unit (ALU) 1904, a memory 1908, storage 1910, a plurality of networking devices 1914, and a plurality of input / output (I / O) devices 1912. The data processing unit 1906 is responsible for processing algorithmic instructions. For example, the data processing unit 1906 is equivalent to the processor of the network node. The data processing unit 1906 is capable of executing software instructions stored in the memory 1908. The data processing unit 1906 receives commands from the control unit 1902 to carry out its processing. Furthermore, logical and arithmetic operations involved in the execution of instructions are computed with the help of the ALU 1904.

[0224] The computer program may be loadable into a data processing unit 1906, which may be provided in an electronic device (such as a UE or network node). When loaded into the data processing unit 1906, the computer program may be stored in memory 1908, which is associated with or provided in a data processor. According to some embodiments, when the computer program is loaded into and operated by the data processing unit 1906, it may trigger the execution of a method step, for example, by the methods shown in Figures 2, 3, and 4, or otherwise described herein.

[0225] The overall computing environment 1900 may consist of multiple homogeneous and / or heterogeneous cores, multiple CPUs of different types, special media, and other accelerators. The data processing unit 1906 is responsible for processing algorithmic instructions. Furthermore, multiple data processing units 1906 may be located on a single chip or across multiple chips.

[0226] The algorithm, containing the instructions and code required for implementation, is stored in either memory 1908 or storage 1910, or both. At runtime, the instructions can be fetched from the corresponding memory 1908 and / or storage 1910 and executed by the data processing unit 1906.

[0227] In hardware implementations, various networking devices 1914 or external I / O devices 1912 may be connected to the computing environment to support implementations via networking devices 1914 and I / O devices 1912.

[0228] Embodiments disclosed herein may be implemented through at least one software program that runs on at least one hardware device and performs network management functions to control the element. The element shown in Figure 19 includes a block which may be at least one of a hardware device or a combination of a hardware device and a software module.

[0229] The above description of specific embodiments fully illustrates the general nature of the embodiments herein so that others can readily modify and / or adapt such specific embodiments for various applications without departing from the general concept by applying their current knowledge, and such adaptations and modifications should and shall be understood within the meaning and equivalent scope of the disclosed embodiments. It should be understood that the language or terminology used herein is for illustrative purposes only and not for limiting purposes. Thus, although the embodiments herein have been described in relation to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be carried out with modifications within the scope of this disclosure.

Claims

1. A method (200) performed by a target network node (101b) for transmitting multicast and broadcast services (MBS) to user equipment (UE) (103) in a wireless communication network (100), wherein the method (200) is: - The UE (103) decides to engage in an MBS session with the source network node (101a) (202), - When the UE decides to engage in the MBS session with the source network node (101a), i. Obtaining the MBS context of the UE (103) related to the MBS session (208), ii. Determining the provisioning of point-to-multipoint (PTM) configuration information related to the MBS session to be collected by the UE (103) in order to enable the continuous reception of MBS data from the target network node (101b) (210) Includes, The step of determining that the UE (103) is involved in an MBS session with the source network node (101a) is, - When the UE(103) is in one of the idle and inactive states, the UE(103) receives a message instructing it to engage in an MBS session with the source network node. Methods that include...

2. - Determining the RRC status of the UE (103) for receiving MBS data based on one or more network parameters for the MBS, capability information of the UE (103), and one or more MBS parameters (201) The method according to claim 1, further comprising:

3. The method according to claim 1 or 2, wherein the message is one of the messages A (MSG A), 3 (MSG3), and 5 (MSG5) of a random access procedure.

4. The method according to claim 3, wherein the MSG3 includes one or more of a cause-related RRC setup request, a cause-related RRC restart request, an RRC system information request, and one or more temporary mobile group identifiers (TMGIs).

5. The method according to claim 3, wherein the MSG5 includes one or more of the following: an RRC setup completion message including TMGI and an RRC restart completion message including TMGI.

6. - When the UE is in an RRC connection state, it receives a handover request message from the source network node (101a) that includes the MBS context of the UE related to the MBS session. The method according to any one of claims 1 to 5, further comprising:

7. The method according to any one of claims 1 to 6, wherein the MBS context of the UE relating to the MBS session includes one or more of a UE(103) identifier, a session identifier, temporary mobile group identification information (TMGI), and a source network node identifier.

8. When the UE (103) engages in the MBS session with the source network node (101a), the step of obtaining the MBS context of the UE (103) related to the MBS session is: - The source network node (101a) and, - Access and mobility management functions (AMF) in the core network (CN) (105) The method according to any one of claims 1 to 7, comprising obtaining the MBS context from one or more of the following.

9. The step of obtaining the MBS context from the source network node (101a) is as follows: - The UE (103) is determined to be in an RRC inactive state, - Receiving restart identification information related to the MBS session from the UE (103), - To identify the MBS context of the UE at the source network node (101a), transmit the restart identification information to the source network node (101a), - Obtaining the MBS context of the UE from the source network node (101a) The method according to claim 8, including the method described in claim 8.

10. The step of obtaining the MBS context of the UE (103) related to the MBS session from the AMF (105) in the CN is: - The UE(103) is determined to be in an RRC idle state, - Receiving information relating to the MBS session, wherein the information includes one or more of the following: Serving temporary mobile subscriber identification information (S-TMSI) from the UE, temporary mobile group identification information (TMGI), and session identifier (ID). - By sending an initial UE message to the AMF (105), the RRC connection with the AMF (105) is established. - Transmitting the TMGI related to the UE to the AMF, - It is determined that the MBS context of the UE (103) is available in the AMF (105), - When the MBS context is available in the AMF(105), the MBS context of the UE is obtained in the NGAP message. The method according to claim 8, including the method described in claim 8.

11. - The determination that the MBS context of the UE (103) is unavailable in the AMF (105), - When the MBS context of the UE(103) is unavailable in the AMF, the UE(103) receives an instruction from the AMF(105) to start a new MBS session for the UE(103). The method according to claim 10, further comprising:

12. The PTM setting information includes the PTM settings for the MBS session, and the PTM settings for the MBS session are - Service identifier and, - Session identifier and, - Group Wireless Network Temporary Identifier (G-RNTI), - Information related to scheduling of PTM data, - Information instructing at least one neighboring node to transmit the MBS session, - PTM settings for the cell served by the target network node, - PTM configuration for one or more MBS sessions on the target network node and The method according to any one of claims 1 to 11, comprising one or more of the above.

13. The step of transmitting the PTM configuration information related to the MBS session is: - In message B (MSG B) or message 4 (MSG4), the PTM setting is sent to the UE (103), - In message 6 (MSG6), the PTM setting is sent to the UE, - When a handover request message is received from the source network node, the handover request acknowledgment message, which includes MBS configuration information, will transmit the PTM configuration to the source network node. The method according to any one of claims 1 to 6 or 12, including the method described in any one of claims.

14. The MSG B or MSG 4 is - A system information block (SIB) that instructs the aforementioned PTM setting information, - A new information element (IE) that indicates the PTM setting information, - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - When the UE (103) is in an RRC inactive state, an instruction to restart the interrupted PTP radio bearer, - When the UE (103) is in an RRC connection state, instructions are given to set up a new PTP radio bearer. The method according to claim 13, comprising one or more of the above.

15. The aforementioned MSG6 is - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node (101b), - Instructions on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data. The method according to claim 13 or 14, comprising one or more of the above.

16. - Determining that the MBS session of the UE is provided to one or more additional UEs (103a to 103n) in the area served by the target network node (101b), wherein the MBS session is provided to the one or more additional UEs (103a to 103n) using a point-to-point (PTP) bearer, and determining that the MBS session of the UE is provided to one or more additional UEs (103a to 103n), - To determine whether to switch the PTP bearer to a PTM bearer for one or more additional UEs (103a to 103n), - Deciding to provision the PTM settings to one or more additional UEs (103a to 103n) for the purpose of transmitting the MBS data to the UE (103) The method according to any one of claims 1 to 15, further comprising:

17. - It is determined that the MBS session of the UE (103) is not provided to the one or more additional UEs (103a to 103n) in the area served by the target network node (101b), - To initiate a new MBS session enrollment procedure with AMF(105), - To receive the aforementioned MBS data, send instructions to the UE(103) to use a PTP bearer for provisioning the PTM settings. The method according to claim 16, further comprising:

18. A method (400) performed by user equipment (UE) (103) for receiving multicast and broadcast services (MBS) from a target network node (101b) in a wireless communication network (100), wherein the method (400) is: - Determining that an MBS session with the source network node (101a) is in progress at the UE (103) (402), - Send a message indicating that the MBS session with the source network node is in progress (404), - Based on the transmitted message, decide to receive point-to-multipoint (PTM) configuration information related to the MBS session to be collected for the continued reception of MBS data from the target network node (101b) (408) Includes, The step (404) of sending a message indicating that the MBS session with the source network node is in progress is: - A method (400) further comprising sending a message to the target network node (101b) instructing the UE to engage in the MBS session with the source network node while the UE is in one of the idle and inactive states.

19. The method according to claim 18, wherein the message is one of the messages A (MSG A), 3 (MSG3), and 5 (MSG5) of a random access procedure.

20. The method according to claim 19, wherein MSG A or MSG 3 includes one or more of a cause-related RRC setup request, a cause-related RRC restart request, an RRC system information request, an instruction, and one or more temporary mobile group identifiers (TMGIs).

21. The method according to claim 20, wherein the MSG5 includes one or more of an RRC setup completion message including a TMGI and an RRC restart completion message including a TMGI.

22. - While the UE (103) is in an RRC connection state, send a handover request message to the source network node (101a) that includes the MBS context of the UE related to the MBS session. The method according to claim 18, further comprising:

23. The method according to any one of claims 18 to 22, wherein the MBS context of the UE relating to the MBS session includes one or more of a UE identifier, a session identifier, temporary mobile group identification information (TMGI), and a source node identifier.

24. The PTM setting information includes the PTM settings for the MBS session, and the PTM settings for the MBS session are - Service identifier and, - Session identifier and, - Group Wireless Network Temporary Identifier (G-RNTI), - Information related to scheduling of PTM data, - Information instructing at least one neighboring node to transmit the MBS session, - PTM configuration information for one or more ongoing MBS sessions in a cell served by the target network node and The method according to any one of claims 18 to 23, comprising one or more of the above.

25. The step of receiving the PTM configuration information related to the MBS session from the target network node (101b) is: - Receiving the PTM setting in message B (MSG B) or message 4 (MSG4), - In the Message 6 (MSG6) procedure, the PTM setting is received, - The PTM settings are received from the source network node in a handover request acknowledgment message containing MBS configuration information. The method according to any one of claims 18 to 24, including the method described in any one of claims 18 to 24.

26. The MSG B or MSG 4 is - A system information block (SIB) that instructs the aforementioned PTM setting information, - A new information element (IE) that indicates the PTM setting information, - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - When the UE (103) is in an RRC inactive state, an instruction to restart the interrupted PTP radio bearer, - When the UE (103) is in an RRC connection state, instructions are given to set up a new PTP radio bearer. The method according to claim 25, comprising one or more of the above.

27. The aforementioned MSG6 is - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - Instructions on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data. The method according to claim 25, comprising one or more of the above.

28. A target network node (101b) for transmitting multicast and broadcast services (MBS) to user equipment (UE) (103) in a wireless communication network (100), wherein the target network node (101b) - The UE (103) decides to engage in an MBS session with the source network node (101a) (202), - When the UE decides to engage in the MBS session with the source network node (101a), i. Obtaining the MBS context of the UE (103) related to the MBS session (208), ii. To transmit point-to-multipoint (PTM) configuration information related to the MBS session to be collected by the UE (103) in order to enable the continuous reception of MBS data from the target network node (101b) (210) Adapted to do, The aforementioned target network node (101b) is - When the UE(103) is in one of the idle and inactive states, the UE(103) receives a message instructing it to engage in an MBS session with the source network node. A target network node (101b) is configured to make the UE (103) decide to engage in an MBS session with the source network node (101a).

29. The target network node (101b) - Determining the RRC status of the UE (103) for receiving MBS data based on one or more network parameters for the MBS, capability information of the UE (103), and one or more MBS parameters (201) A target network node (101b) according to claim 28, further adapted to perform the following:

30. The target network node (101b) according to claim 28 or 29, wherein the message is one of the random access procedure messages A (MSG A), 3 (MSG3), and 5 (MSG5).

31. The target network node (101b) according to claim 30, wherein MSG A or MSG 3 includes one or more of a cause-related RRC setup request, a cause-related RRC restart request, an RRC system information request, and one or more temporary mobile group identifiers (TMGIs).

32. The target network node (101b) according to claim 30, wherein the MSG5 includes one or more of an RRC setup completion message including a TMGI and an RRC restart completion message including a TMGI.

33. The aforementioned target network node (101b) is - When the UE is in an RRC connection state, it receives a handover request message from the source network node (101a) that includes the MBS context of the UE related to the MBS session. A target network node (101b) according to any one of claims 28 to 32, further adapted for performing the following:

34. The target network node (101b) according to any one of claims 28 to 33, wherein the MBS context of the UE relating to the MBS session includes one or more of a UE(103) identifier, a session identifier, temporary mobile group identification information (TMGI), and a source network node identifier.

35. The target network node (101b) obtains the MBS context of the UE (103) related to the MBS session when the UE (103) engages in the MBS session with the source network node (101a). - The source network node (101a) and, - Access and mobility management functions (AMF) in the core network (CN) (105) A target network node (101b) according to any one of claims 28 to 34, adapted to perform the task by obtaining the MBS context from one or more of the following:

36. The target network node (101b) obtains the MBS context from the source network node (101a), - The UE (103) is determined to be in an RRC inactive state, - Receiving restart identification information related to the MBS session from the UE (103), - To identify the MBS context of the UE at the source network node (101a), transmit the restart identification information to the source network node (101a), - Obtaining the MBS context of the UE from the source network node (101a) A target network node (101b) according to any one of claims 28 to 34, adapted for use by the above.

37. The target network node (101b) obtains the MBS context of the UE (103) related to the MBS session from the AMF (105) in the CN. - The UE(103) is determined to be in an RRC idle state, - Receiving information relating to the MBS session, wherein the information includes one or more of the following: Serving temporary mobile subscriber identification information (S-TMSI) from the UE, temporary mobile group identification information (TMGI), and session identifier (ID). - By sending an initial UE message to the AMF (105), the RRC connection with the AMF (105) is established. - Transmitting the TMGI related to the UE to the AMF, - It is determined that the MBS context of the UE (103) is available in the AMF (105), - When the MBS context is available in the AMF(105), the MBS context of the UE is obtained in the NGAP message. A target network node (101b) according to claim 35, adapted to perform the following actions.

38. The aforementioned target network node (101b) is - The determination that the MBS context of the UE (103) is unavailable in the AMF (105), - When the MBS context of the UE(103) is unavailable in the AMF, the UE(103) receives an instruction from the AMF(105) to start a new session for the UE(103). A target network node (101b) according to claim 37, further adapted to perform the following:

39. The PTM setting information includes the PTM settings for the MBS session, and the PTM settings for the MBS session are - Service identifier and, - Session identifier and, - Group Wireless Network Temporary Identifier (G-RNTI), - Information related to scheduling of PTM data, - Information instructing at least one neighboring node to transmit the MBS session, - PTM settings for the cell served by the target network node, - PTM configuration for one or more MBS sessions on the target network node, - PTM configuration information for one or more ongoing MBS sessions in a cell served by the target network node and A target network node (101b) according to any one of claims 28 to 38, comprising one or more of the above.

40. The target network node (101b) transmits the PTM configuration information related to the MBS session. - In message B (MSG B) and message 4 (MSG4), the PTM setting is sent to the UE (103), - In message 6 (MSG6), the PTM setting is sent to the UE, - When a handover request message is received from the source network node, the handover request acknowledgment message, which includes MBS configuration information, will transmit the PTM configuration to the source network node. A target network node (101b) according to any one of claims 28 to 33 or 39, adapted to perform the following:

41. The aforementioned MSG4 is - A system information block (SIB) that instructs the aforementioned PTM setting information, - A new information element (IE) that indicates the PTM setting information, - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - When the UE (103) is in an RRC inactive state, an instruction to restart the interrupted PTP radio bearer, - When the UE (103) is in an RRC connection state, instructions are given to set up a new PTP radio bearer. A target network node (101b) according to claim 39 or 40, comprising one or more of the above.

42. The aforementioned MSG6 is - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node (101b), - Instructions on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data. A target network node (101b) according to any one of claims 39 to 41, comprising one or more of the above.

43. The aforementioned target network node (101b) is - Determining that the MBS session of the UE is provided to one or more additional UEs (103a to 103n) in the area served by the target network node (101b), wherein the MBS session is provided to the one or more additional UEs (103a to 103n) using a point-to-point (PTP) bearer, and determining that the MBS session of the UE is provided to one or more additional UEs (103a to 103n), - To determine whether to switch the PTP bearer to a PTM bearer for one or more additional UEs (103a to 103n), - To transmit the MBS data to the UE (103), the PTM settings are transmitted to one or more additional UEs (103a to 103n). A target network node (101b) according to any one of claims 28 to 42, further adapted for performing the following:

44. The aforementioned target network node (101b) is - It is determined that the MBS session of the UE (103) is not provided to the one or more additional UEs (103a to 103n) in the area served by the target network node (101b), - To initiate a new MBS session enrollment procedure with AMF(105), - To send instructions to the UE (103) to use the PTP bearer for receiving the MBS data. A target network node (101b) according to claim 43, further adapted to perform the following:

45. A user device (UE) (103) for receiving multicast and broadcast services (MBS) from a target network node (101b) in a wireless communication network (100), wherein the UE (103) is - Determining that an MBS session with the source network node (101a) is in progress at the UE (103) (402), - Send a message indicating that the MBS session with the source network node is in progress (404), - Based on the transmitted message, it is decided to receive (408) point-to-multipoint (PTM) configuration information related to the MBS session that should be collected for the continued reception of MBS data from the target network node (101b). It is adapted to do so, and furthermore, The UE (103) sends a message (404) indicating that the MBS session with the source network node is in progress. - While the UE is in one of the idle or inactive states, send a message to the target network node (101b) instructing the UE to engage in the MBS session with the source network node. User equipment (UE) (103) adapted to perform the task.

46. The UE (103) according to claim 45, wherein the message is one of the random access procedure messages B (MSG B), 3 (MSG 3), and 5 (MSG 5).

47. The UE(103) according to claim 46, wherein MSG B or MSG 3 includes one or more of a cause-related RRC setup request, a cause-related RRC restart request, an RRC system information request, an instruction, and one or more temporary mobile group identifiers (TMGIs).

48. The UE(103) according to claim 46, wherein the MSG5 includes one or more of an RRC setup completion message including a TMGI and an RRC restart completion message including a TMGI.

49. The aforementioned UE(103) is, - While the UE (103) is in an RRC connection state, send a handover request message to the source network node (101a) that includes the MBS context of the UE related to the MBS session. UE(103) according to claim 45, further adapted to perform the following:

50. The UE (103) according to any one of claims 45 to 49, wherein the MBS context of the UE relating to the MBS session includes one or more of a UE identifier, a session identifier, temporary mobile group identification information (TMGI), and a source node identifier.

51. The PTM setting information includes the PTM settings for the MBS session, and the PTM settings for the MBS session are - Service identifier and, - Session identifier and, - Group Wireless Network Temporary Identifier (G-RNTI), - Information related to scheduling of PTM data, - Information instructing at least one neighboring node to transmit the MBS session, - PTM configuration information for one or more ongoing MBS sessions in a cell served by the target network node and UE(103) according to any one of claims 45 to 50, comprising one or more of the above.

52. The UE (103) receives the PTM configuration information related to the MBS session from the target network node (101b). - When the UE (103) is in an RRC inactive state, the PTM setting is received in message B (MSG B) or message 4 (MSG 4), - When the UE is in an RRC idle state, the message 6 (MSG6) procedure receives the PTM setting, - The PTM settings are received from the source network node in a handover request acknowledgment message containing MBS configuration information. UE(103) according to any one of claims 45 to 51, adapted for doing so.

53. The MSG B or MSG 4 is - A system information block (SIB) that instructs the aforementioned PTM setting information, - A new information element (IE) that indicates the PTM setting information, - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - When the UE (103) is in an RRC inactive state, an instruction to restart the interrupted PTP radio bearer, - When the UE (103) is in an RRC connection state, instructions are given to set up a new PTP radio bearer. The UE (103) according to claim 52, comprising one or more of the above.

54. The aforementioned MSG6 is - An instruction on whether or not to change the RRC state in order to continue receiving MBS data from the target network node, - Instructions on whether to use a PTP radio bearer or a PTM radio bearer for receiving MBS data. The UE (103) according to claim 52, comprising one or more of the above.

Images