Multicast and Broadcast Services for User Equipment in Idle and Inactive States

Abstract

Embodiments of the present disclosure provide a method, user equipment (UE), network node, and computer program product for providing multicast and broadcast services (MBS) to one or more user equipment (UE) (104a-104n) in a wireless communication network (100). The method is implemented by a network node (102) in the wireless communication network (100). The method includes determining one or more UEs (104a-104n) that are in one of a radio resource control (RRC) idle state and an RRC inactive state. The method includes transmitting a paging message indicating point-to-multipoint (PTM) configuration information to be acquired by the determined one or more UEs (104a-104n) to enable reception of the MBS data in one of the RRC idle state and the RRC inactive state. Further, the method includes transmitting the MBS data to the determined one or more UEs (104a-104n) using the PTM configuration indicated by the PTM configuration information. A corresponding base station, UE, and computer program product are also disclosed.

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 multicast and broadcast services (MBS) to one or more user equipments in an idle state and an inactive state.

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 defined by 3GPP can not only achieve the multicast and broadcast of low-rate plain text messages, but also achieve the 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 on a point-to-multipoint (PTM) interface designed to provide efficient delivery of broadcast and multicast services within the 3GPP cellular network. When an MBMS service is broadcast, all cells within 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. A base station, sometimes called an eNode B, provides wireless services to wireless communication devices, sometimes called User Equipment (UE), within a cell.

[0006] The UE can be in at least one of two modes, including the connected mode and the idle mode. The UE is in the connected mode when a Radio Resource Control (RRC) connection is established. If the RRC connection is not established, the UE is in the idle mode. Thus, the connected mode includes an established RRC connection, while there is no established RRC connection in the idle mode. The UE receives MBMS content in the connected mode after establishing an RRC connection.

[0007] In existing New Radio (NR) specifications, 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 UEs in the RRC connected state. However, there are limitations on the number of UEs that can receive MBS data in the connected state for each gNB or NR cell. Therefore, an NR cell may not be able to transmit MBS data to all UEs in the RRC connected state.

[0008] Therefore, there is a need for improved methods and configurations for providing multicast and broadcast services (MBS) to UEs that mitigate at least some of the problems cited above.

[0009] US Patent Application No. 2019 / 182632 (A1) relates to an operation pattern for directly notifying UEs of the start of distribution of a specific MBMS service. SUMMARY OF THE INVENTION

[0010] The present invention is disclosed in accordance with the independent claims. The subject matter disclosed below in the description and exceeding the scope of the claims should be regarded as examples even if words such as "embodiments" or "invention" are used in connection therewith, and should not be regarded as embodiments.

[0011] In particular, in a geographical area, when there is a need to broadcast data or security alerts simultaneously to a very large number, even an infinite number, of user equipment (UEs), such as for public safety applications, it may be advantageous to move the UEs to the RRC_CONNECTED state or directly serve UEs in the RRC_IDLE or RRC_INACTIVE state without the need for prior configuration in the RRC connected state.

[0012] Accordingly, an object of the present disclosure is to pursue reducing, alleviating, or eliminating all or at least some of the above-described drawbacks of the currently known solutions, and to provide a method, a user equipment, a network node, and a computer program product for providing multicast and broadcast services (MBS).

[0013] This and other objects are achieved by the methods, computer program products, and devices defined in the appended claims. The term exemplary is to be understood in this context as serving as an instance, example, or illustration.

[0014] According to a first aspect of the present disclosure, a method for providing multicast and broadcast services (MBS) to one or more user equipments (UEs) in a wireless communication network is provided. The method is implemented by a network node in the wireless communication network. The method includes determining one or more UEs that are in one of a radio resource control (RRC) idle state and an RRC inactive state. The method includes transmitting a paging message that instructs point-to-multipoint (PTM) configuration information to be obtained by the determined one or more UEs to enable reception of MBS data in one of the RRC idle state and the RRC inactive state. Further, the method includes transmitting MBS data to the determined one or more UEs using the PTM configuration indicated by the PTM configuration information.

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

[0016] In some embodiments, the method further includes determining whether to send PTM configuration information to one or more UEs that are in one of the RRC idle state and the RRC inactive state through a common control channel. Further, the method includes sending the PTM configuration information to one or more UEs through the common control channel when it is determined that the PTM configuration should be sent through the common control channel.

[0017] In some embodiments, the paging message includes a service identifier (ID) for the MBS, a session ID for the MBS, an indication to at least one of the determined one or more UEs for receiving MBS data in the RRC idle state, the RRC inactive state, or the RRC connected state, an indication to at least one of the determined one or more UEs to enter the RRC connected state to obtain PTM configuration information, a preamble indicating a PTM configuration for receiving MBS data to be obtained in the RRC connected state, an indicator to be monitored by each of the UEs to obtain the preamble, an indication as to whether to use pre-stored PTM configuration information for the determined one or more UEs or to enter the RRC connected state through a random access procedure to obtain the PTM configuration, an indication as to whether to reuse the most recent PTM configuration or to obtain the PTM configuration for at least one of the determined one or more UEs, an indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and the RRC inactive state, an indication as to whether the PTM transmission is the last PTM transmission in a session related to the PTM configuration information, and an indication as to whether one or more UEs need to respond to the paging message.

[0018] In some embodiments, when a paging message including an instruction to enter the RRC connected state is transmitted, the PTM configuration information is transmitted to one or more UEs in the RRC connected state.

[0019] In some embodiments, the PTM configuration information includes one or more of a service ID, a session ID, information related to scheduling of PTM data, information related to neighboring cells that transmit MBS data, information on ongoing MBS sessions, and information on all MBS sessions.

[0020] In some embodiments, the PTM configuration information is transmitted through a common control channel in a system information block (SIB) periodically transmitted by a network node.

[0021] In some embodiments, the common control channel is a PTM downlink control channel.

[0022] In some embodiments, the PTM configuration information is transmitted to one or more UEs through a common control channel based on receipt of a request for PTM configuration information from one or more UEs (104a - 104n) in one of the RRC idle state and the RRC inactive state.

[0023] In some embodiments, transmitting a paging message that indicates PTM configuration information to be acquired by one or more UEs includes indicating the PTM configuration information through one or more SIBs periodically broadcast by a network node.

[0024] In some embodiments, transmitting a paging message that indicates PTM configuration information to be obtained by one or more UEs includes receiving a request for the PTM configuration information from one or more UEs that are in one of an RRC idle state and an RRC inactive state. Further, the method includes indicating the PTM configuration information to one or more UEs in a system information block (SIB).

[0025] In some embodiments, transmitting a paging message that indicates PTM configuration information to be obtained by one or more UEs includes indicating the PTM configuration information through a PTM downlink common control channel.

[0026] In some embodiments, transmitting a paging message that indicates PTM configuration information to be obtained by one or more UEs includes receiving, from one or more UEs, information about a session related to MBS data in a message 3 (MSG3) of a random access procedure. Further, the method includes indicating, to one or more UEs, PTM configuration information related to the MBS data in a message 4 (MSG4) of the random access procedure.

[0027] According to a second aspect of the present disclosure, a method for receiving multicast and broadcast services (MBS) from a network node in a wireless communication network is provided. The method is performed by a user equipment in the wireless communication network. The method includes transitioning to one of a radio resource control (RRC) idle state and an RRC inactive state. The method includes receiving a paging message that indicates point-to-multipoint (PTM) configuration information to be obtained for receiving MBS data in one of the RRC idle state and the RRC inactive state. Further, the method includes receiving MBS data from the network node using a PTM configuration indicated by the PTM configuration information.

[0028] In some embodiments, the method further includes determining PTM configuration information to be obtained on a common control channel. Further, the method includes receiving the PTM configuration information through the common control channel when the PTM configuration is determined on the common control channel.

[0029] In some embodiments, the paging message includes a service identifier (ID) for the MBS, a session ID for the MBS, an indication to at least one of the determined one or more UEs for receiving MBS data in the RRC idle state and the RRC inactive state or the RRC connected state, an indication to at least one of the determined one or more UEs to enter the RRC connected state to obtain the PTM configuration information, a preamble indicating the PTM configuration for receiving the MBS data to be obtained in the RRC connected state, an indicator to be monitored by each of the UEs to obtain the preamble, an indication as to whether to use the pre-stored PTM configuration information for the determined one or more UEs or to enter the RRC connected state through a random access procedure to obtain the PTM configuration, an indication as to whether to reuse the most recent PTM configuration or to obtain the PTM configuration for at least one of the determined one or more UEs, an indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and the RRC inactive state, an indication as to whether the PTM transmission is the last PTM transmission in the session related to the PTM configuration information, and one or more of an indication as to whether to respond to the paging message.

[0030] In some embodiments, the step of receiving MBS data from a network node includes configuring a PTM radio bearer based on the PTM configuration information. Further, the method includes receiving the MBS data using the PTM radio bearer.

[0031] In some embodiments, when a paging message including an instruction for the UE to enter the RRC connected state to obtain PTM configuration is received, the PTM configuration information is received in the RRC connected state.

[0032] In some embodiments, the PTM configuration information includes one or more of a service ID, a session ID, information related to scheduling of PTM data, information related to neighboring cells transmitting MBS data, information on an ongoing MBS session, and information on all MBS sessions.

[0033] In some embodiments, the PTM configuration information is received through a common control channel in a system information block (SIB) periodically transmitted by a network node.

[0034] In some embodiments, the common control channel is a PTM downlink control channel.

[0035] In some embodiments, in response to transmission of a request for PTM configuration in one of the RRC idle state and the RRC inactive state, PTM configuration information is received through a control channel.

[0036] In some embodiments, receiving a paging message instructing PTM configuration information to be acquired by the UE includes receiving an instruction for PTM configuration through one or more SIBs periodically broadcast by a network node.

[0037] In some embodiments, receiving a paging message instructing PTM configuration information to be acquired by the UE includes transmitting a request for PTM configuration information in one of the RRC idle state and the RRC inactive state. Further, the method includes receiving an instruction for PTM configuration information in an SIB.

[0038] In some embodiments, receiving a paging message that instructs point-to-multipoint (PTM) configuration information to be acquired by a UE includes receiving an instruction of the PTM configuration through a PTM downlink common control channel.

[0039] In some embodiments, receiving a paging message that instructs point-to-multipoint (PTM) configuration information to be acquired by a UE includes transmitting information of a session related to MBS data in message 3 (MSG3) of a random access procedure. Further, the method includes receiving PTM configuration information related to MBS data in message 4 (MSG4) of the random access procedure.

[0040] According to a third aspect of the present disclosure, in a wireless communication network, a network node for providing a multicast and broadcast service (MBS) to one or more user equipments (UEs) is provided. The network node is adapted to determine (202) one or more UEs that are in one of a radio resource control (RRC) idle state and an RRC inactive state. The network node is adapted to transmit a paging message that instructs point-to-multipoint (PTM) configuration information to be acquired by the determined one or more UEs in order to enable reception of MBS data in one of the RRC idle state and the RRC inactive state. Further, the network node is adapted to transmit MBS data to the determined one or more UEs using the PTM configuration indicated by the PTM configuration information.

[0041] According to a fourth aspect of the present disclosure, a user equipment (UE) for receiving multicast and broadcast services (MBS) from a network node in a wireless communication network is provided. The UE is adapted to transition to one of a radio resource control (RRC) idle state and an RRC inactive state. The UE is adapted to receive a paging message that indicates point-to-multipoint (PTM) configuration information to be acquired for receiving MBS data in one of the RRC idle state and the RRC inactive state. Further, the UE is adapted to receive MBS data from the network node using the PTM configuration indicated by the PTM configuration information.

[0042] According to a fifth aspect of the present disclosure, a computer program product comprising a non-transitory computer-readable medium having thereon a computer program comprising program instructions is provided. The computer program is loadable into a data processing unit and is configured to cause execution of a method according to either the first aspect or the second aspect when the computer program is run by the data processing unit.

[0043] Advantages of some embodiments are alternative and / or improved techniques for providing MBS to UEs in the RRC idle or RRC inactive state.

[0044] Advantages of some embodiments are enabling a UE to acquire PTM configuration information for multicast or broadcast services for a UE in the RRC idle or RRC inactive state without the need for the UE to acquire PTM configurations in the RRC connected state or to transition to the RRC connected state for PTM configuration acquisition.

[0045] The advantages of some embodiments are that reception of MBS by a UE in the RRC idle or RRC inactive state can reduce the signaling overhead that may be required for connection establishment before the UE can receive MBS data, thereby achieving an improved battery life for the UE.

[0046] The advantages of some embodiments are that reception of MBS services by a UE in the RRC idle or RRC inactive state can mitigate a potentially overloaded situation at the base station or cell serving the UE due to a large number of UEs being in the connected state at the same time.

[0047] The advantages of some embodiments are that minimal or reduced overhead can occur by transmitting PTM configuration information between the UE and the base station.

[0048] The advantages of some embodiments are that the UE can utilize the PTM configuration information to set up or establish a PTM radio bearer for reception of MBS data in the RRC idle or RRC inactive state.

[0049] The above will become apparent from the following more specific description of exemplary embodiments shown in the accompanying drawings in which like reference numerals refer to the same parts throughout different figures. The drawings are not necessarily to scale; rather, emphasis is placed on illustrating exemplary embodiments.

Brief Description of the Drawings

[0050]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

[0051] Aspects of the present disclosure will be described in more detail below with reference to the accompanying drawings. However, the apparatus and methods disclosed herein may be implemented in many different forms and should not be construed as limited to the aspects described herein. Like numbers in the drawings refer to like elements throughout.

[0052] The terminology used herein is for the purpose of describing particular aspects of the present disclosure only and is not intended to be limiting of the invention. The terms "comprises / comprising" as used herein are to be construed as specifying the presence of the stated features, integers, steps, or components, but not precluding the presence or addition of one or more other features, integers, steps, components, or groups thereof. The singular forms "a", "an", and "the" as used herein are to be construed to include the plural forms as well, unless the context clearly dictates otherwise.

[0053] Embodiments of the present disclosure will be described and illustrated in more detail below with reference to the accompanying drawings. However, the solutions disclosed herein may be implemented in many different forms and should not be construed as limited to the embodiments described herein.

[0054] When the present disclosure is described with respect to a method, it may also be embodied in one or more processors, and one or more memories coupled to the one or more processors, where the one or more memories store one or more programs that, when executed by the one or more processors, implement the steps, services, and functions disclosed herein.

[0055] In the present disclosure, a user equipment (UE), also known as a mobile terminal, and / or a wireless terminal is enabled to communicate wirelessly with a network node in a wireless communication network.

[0056] Generally, a network node may serve or cover one or several cells of a wireless communication network. That is, a network node provides wireless coverage in a (one or more) cell and communicates on an air interface with a (one or more) UE operating on a radio frequency within its range. A network node may also be referred to as an "eNB", "e-node B", "node B" or "gNB" depending on the technology and terminology used. In the present disclosure, a network node device may also be referred to as a base station (BS).

[0057] In the present disclosure, it is assumed that the connection establishment between a (one or more) UE and a network node has already been completed.

[0058] Throughout the description, the terms "inactive" state and "RRC inactive" are considered to have the same meaning, and the terms "idle" state and "RRC idle" state are considered to have the same meaning.

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

[0060] FIG. 1 discloses an exemplary wireless communication network 100. As shown in FIG. 1, the wireless communication network 100 includes a base station 104 and a plurality of user equipments (UEs) 104a - 104n. Although there may be a plurality of UEs 104a - 104n, in some embodiments of the present disclosure, a single UE may sometimes be referred to as UE104.

[0061] The base station 102 can be, for example, a new radio (NR) base station, i.e., a gNB, or an evolved Node B base station, i.e., an eNB, etc. The UEs 104a to 104n communicate with the base station 102. The communication from the base station 102 to the UEs 104a to 104n is called downlink (DL) communication, and the communication from the UEs 104a to 104n to the base station 102 is called uplink (UL) communication. Therefore, the UEs 104a to 104n are involved in two-way wireless communication with the base station 102.

[0062] The plurality of UEs 104a to 104n can belong to a group, and the UEs 102a to 102n in the group can be identified using a group ID.

[0063] The base station 102 includes a scheduler for dynamically scheduling downlink transmissions. The scheduler dynamically allocates resources for the physical downlink shared channel (PDSCH) and sends scheduling information to the UEs 104a to 104n through a control channel.

[0064] To facilitate communication, among the channels, a plurality of different communication channels including the physical downlink control channel (PDCCH) are established between the base station 102 and the UEs 104a to 104n. The PDCCH is a channel that enables the base station to control the UE 104a during downlink data communication. For this purpose, the PDCCH is used to send a scheduling allocation or control information called downlink control information (DCI) to the UE 102 to indicate the scheduling to be used by the UE 104a to receive downlink communication on the physical downlink shared channel (PDSCH).

[0065] To effectively utilize mobile network resources, the 3rd Generation Partnership Project (3GPP) proposes a multimedia broadcast multicast service (MBMS), which is a technology for transmitting data from one data source to multiple target mobile terminals.

[0066] MBMS defined by 3GPP can not only achieve the multicast and broadcast of low-rate plane text messages, but also achieve the broadcast and multicast of high-speed multimedia services. Therefore, it can provide a wide range of rich video, audio and multimedia services. MBMS is transmitted on a point-to-multipoint (PTM) interface designed to provide efficient delivery of broadcast and multicast services within the 3GPP cellular network.

[0067] UE104a to 104n can be in at least one of two modes including the connected mode and the idle mode. For example, UE104a is in the connected mode when a radio resource control (RRC) connection is established. When the RRC connection is not established, UE104a is in the idle mode. Therefore, the connected mode includes an established RRC connection, while there is no established RRC connection in the idle mode. After establishing an RRC connection, UE104a to 104n receive MBMS content in the connected mode.

[0068] In the existing new radio (NR) specifications, there are no broadcast or multicast features for PTM transmission to the UE, and the available point-to-point transmission can be extended for PTM transmission to the UE in the RRC connected state. However, there is a limit on the number of UEs that can receive MBS data in the connected state for each gNB or NR cell. Therefore, the NR cell may not be able to transmit MBS data to all UEs in the RRC connected state.

[0069] Therefore, according to some embodiments of the present disclosure, the base station 102 implements a method for efficiently providing MBS to (one or more) UE104a to 104n as described herein. Alternatively, UE104 may implement a method for efficient reception of MBS data from the base station 102.

[0070] According to some embodiments of the present disclosure, the base station 102 determines one or more UEs 104a to 104n that are in one of the radio resource control (RRC) idle state and the RRC inactive state. For example, the base station 102 determines the UEs 104a to 104n that are in the RRC idle state and the RRC inactive state in the coverage area of the base station.

[0071] When the base station 102 determines the UEs 104a to 104n that are in the RRC idle state and the RRC inactive state, the base station 102 transmits a paging message instructing the point-to-multipoint (PTM) configuration information to be acquired by the determined one or more UEs 104a to 104n in order to enable reception of MBS data in the RRC idle state and the RRC inactive state.

[0072] The paging message sent to UE104a to UE104n includes one or more of a service identifier (ID) for MBS, a session ID for MBS, an indication to at least one of the determined one or more UE104a to UE104n for receiving MBS data in the RRC idle state and RRC inactive state or RRC connected state, an indication to at least one of the determined one or more UE104a to UE104n to enter the RRC connected state to obtain PTM configuration information, a preamble indicating the PTM configuration for receiving MBS data to be obtained in the RRC connected state, an indicator to be monitored by each of UE104a to UE104n to obtain the preamble, an indication as to whether the pre-stored PTM configuration information should be used for the determined one or more UE104a to UE104n or whether to enter the RRC connected state through a random access procedure to obtain the PTM configuration, an indication as to whether the most recent PTM configuration should be reused or the PTM configuration should be obtained for at least one of the determined one or more UE104a to UE104n, an indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and RRC inactive state, an indication as to whether the PTM transmission is the last PTM transmission in the session related to the PTM configuration information, and an indication as to whether one or more UEs need to respond to a paging message or the like.

[0073] Furthermore, the base station 102 transmits MBS data to the determined one or more UE104a to UE104n using the PTM configuration indicated by the PTM configuration information.

[0074] In some embodiments, the base station may determine whether to send PTM configuration information to one or more UEs 104a - 104n in one of the RRC idle state and the RRC inactive state through a common control channel. When the base station 102 determines to send the PTM configuration information to one or more UEs 104a - 104n in one of the RRC idle state and the RRC inactive state, the base station 102 sends the PTM configuration information to the one or more UEs 104a - 104n through the common control channel. For example, the common control channel is a PTM downlink control channel.

[0075] The PTM configuration information includes one or more of a service ID, a session ID, information related to the scheduling of PTM data, information about adjacent cells that transmit MBS data, information about ongoing MBS sessions, and information about all MBS sessions. Various embodiments in which one or more UEs 104a - 104n receive PTM configurations from the base station 102 for the reception of MBS data are described in the later part of the description.

[0076] FIG. 2 is a flowchart showing an exemplary method 200 for providing multicast and broadcast services (MBS) in a wireless communication network. As described above, the base station implements a method 400 for providing MBS to UEs in the wireless communication network.

[0077] MBS data or MBS content, which may be a service, data, or program accessible through a UE, is referred to herein as a PTM - compliant service. Examples of PTM - compliant services include streaming audio and video and other multimedia data.

[0078] The UE can be in one of the following modes, including the idle mode, the inactive mode, and the connected mode. When operating according to the 3GPP communication specifications, the operation is defined at least for the idle mode and the connected mode. For example, two of the UEs can be in the idle mode and are called idle mode UEs. Further, some of the UEs can be in the connected mode and they are called connected mode UEs. The connected mode UEs are different from the idle mode UEs in that at least the connected mode UEs have an established RRC connection defined by a specific 3GPP specification, while the idle mode UEs do not have an established RRC connection.

[0079] Furthermore, some of the UEs in the wireless communication network 100 shown in FIG. 1 can be in the inactive state, and these UEs in the inactive state during a specific or predefined time interval can be set by the base station when there is no data reception in these UEs.

[0080] The embodiments disclosed herein are more applicable for providing MBS data to the UE when one or more UEs are in one of the idle state and the inactive state.

[0081] In step 202, method 300 includes determining one or more UEs that are in one of the idle state and the inactive state. For example, the UEs 104a - 104n shown in FIG. 1 can be in the connected state, the idle state, and the inactive state. The base station determines one or more UEs that are in either the idle state or the inactive state for transmitting MBS data to the one or more UEs in the idle state or the inactive state.

[0082] The base station determines one or more UEs that are either in the idle state or the non-active state for the transmission of MBS data to one or more UEs. However, the base station may determine the RRC state of one or more UEs for the transmission of MBS data, as specified in optional step 201. For example, the base station may determine the RRC state of one or more UEs based on one or more network parameters for MBS, the capability information of one or more UEs, and one or more MBS parameters, the capability information of one or more UEs, and one or more MBS parameters.

[0083] In some examples, if the base station determines that MBS data will only be received in the connected state, the base station determines one or more UEs to be in the connected state for the reception of MBS data.

[0084] In another example, if the base station determines that there are a greater number of UEs equal to the maximum number of UEs that can receive MBS data in the connected state, the base station may determine one or more UEs to be in the idle state or the non-active state for the reception of MBS data.

[0085] In another example, if the capability information of one or more UEs indicates that one or more UEs cannot receive MBS data in the idle state or the non-active state, the base station may determine the RRC state of one or more UEs for the reception of MBS data. Therefore, the base station may determine the RRC state of one or more UEs based on the network parameters for MBS, the capability information of one or more UEs 104a, and one or more MBS parameters.

[0086] In step 204, method 200 includes determining to send PTM configuration information through a control channel. The PTM configuration information should be obtained by one or more UEs for receiving MBS data in an idle state or a non-active state. The base station determines whether to send the PTM configuration information through a control channel. If the base station determines to send the PTM configuration information through a control channel, in step 205, method 200 includes sending the PTM configuration information to one or more UEs (104a - 104n) through a common control channel. For example, the base station sends the PTM configuration information through a common control channel in a system information block (SIB) periodically transmitted by a network node.

[0087] In one example, the common control channel is a PTM downlink control channel. In an alternative example, the common control channel can be a new PTM downlink control channel (DCCH), for example, a newly defined multicast broadcast common control channel (MBCCH) that can be carried on a physical downlink shared channel (PDSCH) used for PTM. The scheduling information of this common control channel, such as the repetition period, modification period, first subframe, offset, and DRX parameters, which enables the UE to know when to monitor for PTM acquisition, can be provided in another SIB known to the UE.

[0088] In one embodiment, the base station sends the PTM configuration information to one or more UEs through a common control channel based on receiving a request for the PTM configuration information from one or more UEs in one of an idle state and a non-active state.

[0089] In one example, the base station receives a request for PTM configuration information from one or more UEs in an idle state or a non-active state. In response to the request for PTM configuration information from one or more UEs, the base station transmits the PTM configuration information to the one or more UEs.

[0090] In step 204, if the base station determines not to transmit the PTM configuration information through the common control channel, in step 206, method 200 includes transmitting a paging message to one or more UEs indicating the PTM configuration information for receiving the MBS data.

[0091] In one example, the paging message includes PTM configuration information along with related information for obtaining the PTM configuration information to receive MBS data. The paging message includes a service identifier (ID) for the MBS, a session ID for the MBS, an indication to at least one of the determined one or more UEs 104a - 104n for receiving MBS data in the RRC idle state and RRC inactive state or RRC connected state, an indication to at least one of the determined one or more UEs 104a - 104n to enter the RRC connected state to obtain the PTM configuration information, a preamble indicating the PTM configuration for receiving the MBS data to be obtained in the RRC connected state, an indicator to be monitored by each of the UEs 104a - 104n to obtain the preamble, an indication as to whether to use the pre - stored PTM configuration information for the determined one or more UEs 104a - 104n or to enter the RRC connected state through a random access procedure to obtain the PTM configuration, an indication as to whether to reuse the most recent PTM configuration or to obtain the PTM configuration for at least one of the determined one or more UEs 104a - 104n, an indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and RRC inactive state, an indication as to whether the PTM transmission is the last PTM transmission in the session related to the PTM configuration information, and one or more of an indication as to whether one or more UEs need to respond to a paging message etc.

[0092] In one example, a unique factor for MBS can be the service identifier. Each of the MBS services is associated with a unique service identifier. Thus, the paging message transmitted to one or more UEs includes the unique service identifier related to the MBS for receiving the MBS.

[0093] In one example, each MBS session is identified using a session identifier (ID). The session ID for an MBS session is transmitted in a paging message.

[0094] In some examples, the base station may determine some of the UEs that should receive MBS data in the RRC idle state and the RRC inactive state, and the base station may determine some of the UEs that should receive MBS data in the connected state. In such a scenario, the base station may send an indication to the UE to receive MBS data in the RRC idle state and the RRC inactive state or the RRC connected state. Thus, the base station may determine the state of one or more UEs for receiving MBS data, and thus, the base station may send a paging message including an indication to instruct one or more UEs for receiving MBS data in the RRC idle state and the RRC inactive state or the RRC connected state.

[0095] In some examples, the base station may determine to enable the determined one or more UEs to enter the RRC connected state for receiving MBS data. When the base station determines to enable the determined one or more UEs to enter the RRC connected state for receiving MBS data, the base station may send a paging message together with an indication to the determined one or more UEs to enter the RRC connected state for receiving MBS data.

[0096] In some examples, the base station may transmit PTM configuration information through a preamble, and the preamble instructs one or more UEs of the PTM configuration information. Thus, the base station may send a paging message together with a preamble that instructs the PTM configuration information to be obtained by one or more UEs in the RRC connected state. When the preamble is used to instruct the PTM configuration information, the paging message may also include an indicator to be monitored by one or more UEs to obtain the preamble.

[0097] In some examples, the base station may indicate to one or more UEs whether it should use pre-stored PTM configuration information for receiving MBS data or whether one or more UEs should be allowed to enter the RRC connected state through a random access procedure to obtain the PTM configuration information. Accordingly, the base station may transmit a paging message with an indication for indicating to one or more UEs whether it should use pre-stored PTM configuration information or whether one or more UEs should be allowed to enter the RRC connected state through a random access procedure to obtain the PTM configuration information. When receiving the paging message with the indication, one or more UEs may either use the stored PTM configuration information or enter the RRC connected state through a random access procedure to obtain the PTM configuration information.

[0098] In some examples, the base station may allow one or more UEs to enter the RRC connected state from the idle state or the inactive state for receiving MBS data. In some examples, the base station may transmit a paging message with an indication for instructing one or more UEs to enter the RRC connected state from the idle state or the inactive state for receiving MBS data.

[0099] In some examples, the base station may also indicate whether the PTM transmission is the last PTM transmission in a session related to the PTM configuration information. To indicate whether the PTM transmission is the last PTM transmission, the base station transmits a paging message with an indication for indicating to one or more UEs that the PTM transmission is the last PTM transmission in a session related to the PTM configuration information.

[0100] In another example, the base station may also send a paging message along with an indication indicating whether one or more UEs need to respond to the paging message. If the base station intends to have a response message from one or more UEs for the paging message to be sent, the base station may send a paging message along with an indication for instructing one or more UEs to respond to the paging message.

[0101] In some examples, the base station may instruct one or more UEs regarding the start time interval and end time interval of an MBS session or MBS data. To instruct one or more UEs regarding the start time interval and end time interval of MBS data, the base station may send a paging message along with an indication for instructing one or more UEs regarding the start time interval and end time interval of an MBS session or MBS data.

[0102] Accordingly, the paging message includes PTM configuration information along with related information for obtaining the PTM configuration information for receiving MBS data. The paging message may include any of the above-mentioned indications that enable one or more UEs to obtain the PTM configuration information.

[0103] Furthermore, in step 208, method 200 includes transmitting MBS data to one or more UEs using the PTM configuration indicated by the PTM configuration information. The MBS data may be transmitted to one or more UEs using multicast or broadcast using the PTM configuration indicated by the PTM configuration information.

[0104] Figures 3 to 5 are flowcharts showing exemplary methods 300, 400, and 500 for receiving MBS in a wireless communication network. A UE performs various steps of methods 300, 400, and 500 for receiving MBS data in a wireless communication network.

[0105] Note that the UE can be in one of the following modes, including the idle mode, the inactive mode, and the connected mode. When operating according to the 3GPP communication specifications, the operation is defined at least for the idle mode and the connected mode. For example, two of the UEs can be in the idle mode and are called idle mode UEs. Further, some of the UEs can be in the connected mode and they are called connected mode UEs. The connected mode UEs are different from the idle mode UEs in that at least the connected mode UEs have an established RRC connection defined by a specific 3GPP specification, while the idle mode UEs do not have an established RRC connection.

[0106] Consider that one or more UEs are in the RRC connected state. When one or more UEs are in the RRC connected state, at step 302, method 300 includes transitioning to the idle state or the inactive state. One or more UEs transition from the connected state to the idle state or the inactive state. When transitioning from the connected state to the idle state or the inactive state, at step 304, method 300 includes determining the PTM configuration information to be obtained on the common control channel. If the PTM configuration information is determined on the common control channel, one or more UEs receive the PTM configuration information through common control. For example, the UE can receive the PTM configuration information through the common control channel in the SIB periodically transmitted by the base station.

[0107] In one example, the common control channel is the PTM downlink control channel.

[0108] In one embodiment, the PTM configuration information includes one or more of a service ID, a session ID, information related to the scheduling of PTM data, information related to adjacent cells transmitting MBS data, information on ongoing MBS sessions, and information on all MBS sessions.

[0109] If the PTM configuration information is not determined on the common control channel, at step 306, method 300 includes receiving a paging message that indicates the PTM configuration information. One or more UEs receive a paging message that indicates the PTM configuration information from the base station.

[0110] As already explained above, the paging message received from the base station includes a service identifier (ID) for the MBS, a session ID for the MBS, an indication to at least one of the determined one or more UEs 104a - 104n for receiving MBS data in the RRC idle state and RRC inactive state or RRC connected state, an indication to at least one of the determined one or more UEs 104a - 104n to enter the RRC connected state to obtain the PTM configuration information, a preamble indicating the PTM configuration for receiving the MBS data to be obtained in the RRC connected state, an indicator to be monitored by each of UEs 104a - 104n to obtain the preamble, an indication as to whether to use the pre - stored PTM configuration information for the determined one or more UEs 104a - 104n or to enter the RRC connected state through a random access procedure to obtain the PTM configuration, an indication as to whether to reuse the most recent PTM configuration or to obtain the PTM configuration for at least one of the determined one or more UEs, an indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and RRC inactive state, an indication as to whether the PTM transmission is the last PTM transmission in the session related to the PTM configuration information, and an indication as to whether one or more UEs need to respond to a paging message or the like, including one or more of these.

[0111] One or more instructions in the paging message enable the UE to obtain PTM configuration information for receiving MBS data. The UE monitors the paging message to determine the PTM configuration to be obtained for receiving MBS data. The UE may receive one or more of the above instructions in the paging message for obtaining the PTM configuration information.

[0112] In step 308, method 300 includes receiving MBS data from the base station based on the PTM configuration information. The MBS data may be received from the base station using multicast or broadcast using the PTM configuration information received through the paging message or through the common control channel.

[0113] Figure 4 is a flowchart showing an exemplary method 400 for determining PTM configuration information based on new PTM configuration information.

[0114] In step 402, method 400 includes transitioning to the idle state or the inactive state. For example, when the UE transitions to the idle state, in step 404, method 400 includes releasing the radio resources associated with the PTM bearer. In response to transitioning to the idle state or the inactive state and while in the idle state or the inactive state, in step 406, method 400 includes receiving a paging message including an instruction for determining new PTM configuration information. In step 408, method 400 includes determining the PTM configuration based on the new PTM configuration information.

[0115] In some embodiments, the paging message includes instructions for initiating a random access (RA) procedure and for transitioning to the connected state. Determining the new PTM configuration information includes, in response to receiving the paging message, the UE transitioning to the connected state and receiving the new PTM configuration information through a radio resource control (RRC) procedure.

[0116] In some embodiments, the paging message further instructs the UE with new PTM configuration information. Determining the new PTM configuration information includes the UE monitoring a communication channel while in an idle state or inactive. The new PTM configuration information may be determined via an SIB or a PTM downlink channel during a predetermined time period. Existing SIBs in the current NR standard, such as SIB2 to SIB14, may be extended to include PTM configuration information, or a new SIB may be defined.

[0117] In some embodiments, the paging message further instructs the UE with the determined PTM configuration information. Determining the PTM configuration information includes transmitting a message 3 (Msg3) as part of a RA procedure in response to receiving the paging message and while in an idle state or inactive state, where Msg3 includes a request for PTM configuration, and receiving the PTM configuration as part of a message 4 (Msg4) while in an idle state or inactive state in response to transmitting Msg3.

[0118] In some embodiments, determining the PTM configuration information includes the PTM configuration information of all ongoing MBS sessions on a common control channel via an SIB periodically transmitted by a base station.

[0119] In some embodiments, determining the PTM configuration information includes transmitting a request for PTM configuration information to a base station during a random access (RA) procedure and receiving the PTM configuration information via an SIB in response to transmitting the request.

[0120] In some embodiments, determining the PTM configuration information includes receiving scheduling information for the PTM downlink control channel via the SIB and receiving the PTM configuration information via the PTM downlink control channel based on the scheduling information.

[0121] Note that the PTM downlink channel includes the multicast broadcast common control channel (MBCCH) carried on the physical downlink shared channel (PDSCH) for PTM. The scheduling information includes at least one of a repetition period, a modification period, a first subframe, an offset, and discontinuous reception (DRX) parameters.

[0122] FIG. 5 is a flowchart showing an exemplary method 500 for determining a PTM configuration based on stored PTM configuration information.

[0123] In step 502, method 500 includes transitioning to an idle state or an inactive state. In step 504, in response to transitioning to the idle state, method 500 includes interrupting and storing radio resources associated with the PTM radio bearer. In step 506, in response to transitioning to the idle state or the inactive state and while in the idle state or the inactive state, method 500 includes receiving a paging message including an indication to use the stored PTM configuration information. In step 508, method 500 includes determining the PTM configuration information based on the stored PTM configuration information. The UE determines the stored PTM configuration information to determine the PTM configuration information.

[0124] FIG. 6 is an exemplary schematic diagram showing functional modules of a UE according to some embodiments. As shown in FIG. 6, the UE 104 may include, for example, an antenna 607 corresponding to the antenna 4111 in FIG. 9, and a transmitter and receiver configured to provide uplink wireless communication and downlink wireless communication with one or more base stations corresponding to, for example, the network node 4160 in FIG. 9, also referred to as a radio access network, for example, a transceiver circuit 601, also referred to as a transceiver, corresponding to the interface 4114 in FIG. 9. The UE 104 may also include a processing circuit 603, also referred to as a processor, coupled to the transceiver circuit and corresponding to, for example, the processing circuit 4120 in FIG. 9, and a memory circuit 605, also referred to as a memory, coupled to the processing circuit and corresponding to, for example, the device-readable medium 4130 in FIG. 9. The memory circuit 605 may include computer-readable program code that, when executed by the processing circuit 303, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 603 may be defined to include a memory such that a separate memory circuit is not required.

[0125] Various operations of the UE 104 may be performed by the processing circuit 603 and / or the transceiver circuit 301. For example, the processing circuit 303 may control the transceiver circuit 601 to transmit communications through the transceiver circuit 601 on a wireless interface to a radio access network node that is a base station and / or to receive communications from the base station through the transceiver circuit 601 on a wireless interface. Additionally, modules may be stored in the memory circuit 605, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 303, the processing circuit 303 performs each of the operations defined in the steps shown in FIGS. 3-5.

[0126] FIG. 7 is an exemplary schematic diagram showing the functional modules of network node 102 according to some embodiments. As shown, network node 102 may include a transceiver circuit 701 (also referred to as a transceiver, e.g., corresponding to part of interface 4190 in FIG. 9) configured to provide uplink and downlink wireless communication with mobile terminals. Network node 102 may also include a network interface circuit 707 (also referred to as a network interface, e.g., corresponding to part of interface 4190 in FIG. 9) configured to provide communication with other nodes in the radio access network and / or core network, e.g., with other base stations. Network node 102 may further include a processing circuit 703 (also referred to as a processor, e.g., corresponding to processing circuit 4170) coupled to the transceiver circuit, and a memory circuit 705 (also referred to as a memory, e.g., corresponding to device-readable medium 4180 in FIG. 9) coupled to the processing circuit. 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 the embodiments disclosed in FIG. 2. In some embodiments, the processing circuit 703 may be defined to include memory such that a separate memory circuit is not required.

[0127] The various operations of the network node 400 may be performed by the processing circuitry 703, the network interface 707, and / or the transceiver 701. For example, the processing circuitry 703 may control the transceiver 701 to transmit downlink communications to one or more UEs over the radio interface through the transceiver 701 and / or receive uplink communications from one or more UEs over the radio interface through the transceiver 701. Similarly, the processing circuitry 703 may control the network interface 707 to transmit communications to one or more other network nodes through the network interface 707 and / or receive communications from one or more other network nodes through the network interface. Additionally, modules may be stored in the memory 705, and these modules may provide instructions such that when the instructions of the module are executed by the processing circuitry 403, the processing circuitry 403 performs respective operations, such as the operations described below with respect to the embodiments related to the network node described in FIG. 2.

[0128] In some embodiments, the network node 102 may be implemented as a core network (CN) node without a transceiver. In such embodiments, the transmission to the UE may be initiated by the network node 102 such that the transmission to the UE is provided through a network node 102 that includes a transceiver, for example, through a base station or a RAN node.

[0129] FIG. 8 is an exemplary schematic diagram showing the functional modules of a core network (CN) node 106 according to some embodiments. The CN node 106 can be a session management function (SMF) or an access and mobility management function (AMF). The CN node 106 can include a network interface 807 configured to provide communication with other nodes of the core network and / or the RAN. The CN node 106 can include a processor 803 coupled to the network interface 807 and a memory 805 coupled to the processor 803. The memory 805 can include computer-readable program code that, when executed by the processor 803, causes the processing circuitry to perform the various steps described in FIG. 2.

[0130] The various operations of the CN node 106 can be performed by the processor 803 and / or the network interface 807. For example, the processor 803 can control the network interface 507 to transmit communications to one or more other network nodes through the network interface 807 and / or receive communications from one or more other network nodes through the network interface 807. Additionally, modules can be stored in the memory 805, and these modules can provide instructions such that when the module instructions are executed by the processor 803, the processor 803 performs each of the operations described in FIG. 2.

[0131] FIG. 9 is another block diagram of a wireless network according to some embodiments. The subject matter described herein can be implemented in any suitable type of system using any suitable components, but the embodiments disclosed herein are described with respect to wireless networks such as the exemplary wireless network shown in FIG. 9. For simplicity, the wireless network of FIG. 9 only shows network 4106, network nodes 4160 and 4160b, and WDs (also referred to as mobile terminals) 4110, 4110b, and 4110c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device such as a landline phone, a service provider, or any other network node or end device. Among the components shown, network node 4160 and wireless device (WD) 4110 are illustrated with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access of the wireless devices to the wireless network and / or use of services provided by or via the wireless network.

[0132] A wireless network may comprise any type of communication, telecommunication, data, cellular, and / or wireless network, or other similar type of system, and / or interface with them. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as the pan-European digital cellular 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 Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0133] 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 (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

[0134] Network nodes 4160 and WD4110 include various components that are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing a wireless connection in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired connection or a wireless connection.

[0135] As used herein, a network node refers to a device that is configured, constructed, and / or operable to communicate directly or indirectly with a wireless device and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node B, evolved Node B (eNB), and NR Node B (gNB)). Base stations can be categorized based on the amount of coverage provided by the base station (or, alternatively, the transmission power level of the base station), in which case they may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which may sometimes be referred to as 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 may sometimes be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include MSR devices such as multi-standard radio (MSR) BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multi-cast coordination entities (MCEs), 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 can be a virtual network node, as described in more detail below.However, more generally, a network node can represent any suitable device (or group of devices) that is configured, constructed, and / or operable to enable access to a wireless network and / or provide it to, or provide some service to, a wireless device that has accessed the wireless network.

[0136] In FIG. 9, 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. The network node 4160 shown in the exemplary wireless network of FIG. 9 can represent a device that includes the shown combination of hardware components, although other embodiments can include network nodes with different combinations of components. It should be understood that a network node can include any suitable combination of hardware and / or software required to implement the tasks, features, functions, and methods disclosed herein. Moreover, although the components of network node 4160 are illustrated as a single box located within a larger box or as a single box nested within multiple boxes, in reality, a network node can include multiple different physical components that make up a single shown component (e.g., device-readable medium 4180 can include multiple separate hard drives as well as multiple RAM modules).

[0137] Similarly, network node 4160 can be assembled from a plurality of physically distinct components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which can have its own respective components. In some scenarios where network node 4160 includes a plurality of distinct components (e.g., a BTS component and a BSC component), one or more of the distinct components can be shared among several network nodes. For example, a single RNC can control multiple Node Bs. In such scenarios, each unique pair of Node B and RNC can, in some cases, be regarded as a single distinct network node. In some embodiments, network node 4160 can be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components can be replicated (e.g., separate device-readable media 4180 for different RATs), and some components can be reused (e.g., the same antenna 4162 can be shared by RATs). Network node 4160 can also include a plurality of sets of various illustrated components for different radio technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth radio technologies, integrated into network node 4160. These radio technologies can be integrated with the same or different chips or sets of chips, and other components within network node 4160.

[0138] The processing circuit 4170 is configured to perform any decision-making operation, computational operation, or similar operation (e.g., some acquisition operations) as described herein as provided by the network node. These operations performed by the processing circuit 4170 may include processing the information obtained by the processing circuit 4170, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and as a result of the processing having made a decision.

[0139] The processing circuit 4170 can be a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, one or a combination of multiple resources, or a combination of hardware, software, and / or encoded logic, operable to provide the network node 4160 function either alone or in combination with other network node 4160 components such as the device-readable medium 4180. For example, the processing circuit 4170 can execute instructions stored in the device-readable medium 4180 or instructions stored in the memory within the processing circuit 4170. Such functions may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 4170 may include a system-on-chip (SOC).

[0140] In some embodiments, the processing circuit 4170 may include one or more of a radio frequency (RF) transceiver circuit 4172 and a 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 a radio unit and a digital unit. 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.

[0141] In some embodiments, some or all of the functions described herein as 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 a 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 discrete device-readable medium, such as in a hardwired fashion. In any of those embodiments, whether or not executing instructions stored in a device-readable storage medium, the processing circuit 4170 may be configured to implement the described functions. The benefits provided by such functions are not limited to the processing circuit 4170 alone, or to other components of the network node 4160, but are enjoyed generally by the network node 4160 as a whole, and / or by end users and the wireless network.

[0142] The device-readable medium 4180 can comprise any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage, solid-state memory, remotely-mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that can store information, data, and / or instructions used by the processing circuit 4170. The device-readable medium 4180 can store any suitable instructions, data, or information, including an application that includes one or more of a computer program, software, logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuit 4170 and utilized by the network node 4160. The device-readable medium 4180 can 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 can be considered integrated.

[0143] Interface 4190 is used for wired or wireless communication of signaling and / or data between network node 4160, network 4106, and / or WD 4110. As shown, interface 4190 comprises (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 radio front-end circuit 4192 that is coupled to antenna 4162 or, in some embodiments, can be part of antenna 4162. The radio front-end circuit 4192 comprises a filter 4198 and an amplifier 4196. The radio front-end circuit 4192 can be connected to antenna 4162 and processing circuit 4170. The radio front-end circuit can be configured to condition signals communicated between antenna 4162 and processing circuit 4170. The radio front-end circuit 4192 can receive digital data to be transmitted to other network nodes or WDs via a wireless connection. The radio front-end circuit 4192 can convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of filter 4198 and / or amplifier 4196. The wireless signal can then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 can collect the wireless signal, which is then converted into digital data by radio front-end circuit 4192. The digital data can be passed to processing circuit 4170. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0144] In some alternative embodiments, the network node 4160 may not include a separate radio front - end circuit 4192. Instead, the processing circuit 4170 may comprise a radio front - end circuit and may 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 regarded as part of the interface 4190. In still other embodiments, the interface 4190 may include, as part of a wireless unit (not shown), one or more ports or terminals 4194, a radio front - end circuit 4192, and an RF transceiver circuit 4172, and the interface 4190 may communicate with a baseband processing circuit 4174 that is part of a digital unit (not shown).

[0145] The antenna 4162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 4162 may be coupled to the radio front - end circuit 4192 and can be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 4162 may comprise one or more omnidirectional, sector, or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive wireless signals in any direction, sector antennas can be used to transmit / receive wireless signals from devices within a particular area, and panel antennas can be line - of - sight antennas used to transmit / receive wireless 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, the antenna 4162 may be separate from the network node 4160 and may be connectable to the network node 4160 through an interface or port.

[0146] Antenna 4162, interface 4190, and / or processing circuit 4170 may be configured to perform any receiving operations and / or some acquisition operations 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 transmission operations 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.

[0147] Power circuit 4187 may comprise a power management circuit or be coupled to a power management circuit and is configured to supply power for performing the functions described herein to the components of network node 4160. Power circuit 4187 may receive power from power source 4186. Power source 4186 and / or power circuit 4187 may be configured to provide power to the various components of network node 4160 in a suitable form (e.g., at the voltage and current levels required for each respective component). Power source 4186 may be either included in power circuit 4187 and / or network node 4160 or external to power circuit 4187 and / or network node 4160. For example, network node 4160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to power circuit 4187. As a further example, power source 4186 may comprise a power source in the form of a battery or battery pack connected to or integrated in power circuit 4187. The battery may provide backup power in the event that the external power source fails. Other types of power sources such as photovoltaic devices may also be used.

[0148] An alternative embodiment of network node 4160 may be responsible for providing some aspects of the functionality of a network node, including any of the functions described herein and / or any of the functions necessary to support the subject matter described herein, and may include additional components other than those shown in FIG. 9. For example, network node 4160 may include a user interface device to enable input of information to network node 4160 and to enable output of information from network node 4160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 4160.

[0149] As used herein, a wireless device (WD) refers to a UE or device that is configured, arranged, and / or operable to wirelessly communicate with a network node and / or another wireless device. Unless otherwise specified, 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 conveying information through the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network at a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communication device.

[0150] As yet another specific example, in a Machine-to-Internet (IoT) scenario, the 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. The WD may in this case be a Machine-to-Machine (M2M) device, which may be referred to as an MTC device in a 3GPP context. As one specific example, the WD may be a UE implementing the 3GPP NarrowBand Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal electrical appliances such as refrigerators, televisions, personal wearables such as watches, fitness trackers, etc. In other scenarios, the WD may represent a vehicle or other equipment, which is capable of monitoring its operating status and / or reporting on its operating status, or other functions associated with its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may sometimes be referred to as a wireless terminal. Further, the WD described above may be mobile, in which case the device may also sometimes be referred to as a mobile device or mobile terminal.

[0151] 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 source 4136, and a power circuit 4137. The WD 4110 may include one or more sets of the shown components for different wireless technologies supported by the WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few. These wireless technologies may be integrated on the same or different chips or sets of chips as other components within the WD 4110.

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

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

[0154] The processing circuit 4120 can be a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, resource, one or a combination of multiple ones thereof, or a combination of hardware, software and / or encoded logic, which is operable, either alone or in combination with other WD4110 components such as the device-readable medium 4130, to provide the WD4110 functions. Such functions can include providing any of the various wireless features or benefits described herein. For example, the processing circuit 4120 can execute instructions stored in the device-readable medium 4130 or instructions stored in the memory within the processing circuit 4120 to provide the functions disclosed herein.

[0155] As shown, processing circuit 4120 includes one or more of RF transceiver circuit 4122, baseband processing circuit 4124, and 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 system-on-a-chip (SOC). In some embodiments, RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be on separate chips or a set of chips. In an alternative embodiment, some or all of baseband processing circuit 4124 and application processing circuit 4126 may be combined to form one chip or a set of chips, and RF transceiver circuit 4122 may be on a separate chip or a set of chips. In yet another alternative embodiment, some or all of RF transceiver circuit 4122 and baseband processing circuit 4124 may be on the same chip or a set of chips, and application processing circuit 4126 may be on a separate chip or a set of chips. In still other alternative embodiments, some or all of RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be combined within the same chip or a set of chips. In some embodiments, RF transceiver circuit 4122 may be part of interface 4114. RF transceiver circuit 4122 may condition RF signals for processing circuit 4120.

[0156] 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 on 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 on a separate or discrete device-readable storage medium, such as in a hardwired fashion. In any of those particular embodiments, whether or not executing instructions stored on a device-readable storage medium, the processing circuit 4120 may be configured to perform the functions described. The benefits provided by such functions are not limited to the processing circuit 4120 alone or to other components of the WD4110, but are enjoyed by the WD4110 as a whole and / or generally by the end user and the wireless network.

[0157] The processing circuit 4120 may be configured to perform any decision-making operation, computational operation, or similar operation (e.g., some acquisition operations) described herein as being performed by the WD. These operations as performed by the processing circuit 4120 may include processing information obtained by the processing circuit 4120, e.g., by converting the obtained information into other information, comparing the obtained or converted information with information stored by the WD4110, and / or performing one or more operations based on the obtained or converted information and as a result of the processing having made a decision.

[0158] The device-readable medium 4130 may be operable to store one or more of a computer program, software, logic, rules, code, tables, and other applications, and / or other instructions that may be executed by the processing circuitry 4120. The device-readable medium 4130 may include a computer memory, such as random access memory (RAM) or read-only memory (ROM), a mass storage medium, such as a hard disk, a removable storage medium, and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that may store information, data, and / or instructions used by the processing circuitry 4120. In some embodiments, the processing circuitry 4120 and the device-readable medium 4130 may be considered integrated.

[0159] The user interface device 4132 may provide components that enable a human user to interact with the WD4110. Such interaction may take many forms, such as visual, auditory, tactile, etc. The user interface device 4132 may be operable to create 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 touch screen, and 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, devices and circuits, as well as an output interface, devices and circuits. The user interface device 4132 is configured to enable 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, a proximity or other sensor, 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 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.

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

[0161] Power source 4136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source, for example, an electrical outlet, a photovoltaic device, or a battery. The WD 4110 may further include a power circuit 4137 for distributing power from the power source 4136 to various parts of the WD 4110 that require power to perform any of the functions described or indicated herein. The power circuit 4137 may, in some embodiments, include a power management circuit. The power circuit 4137 may alternatively or additionally be operable to receive power from an external power source, in which case the WD 4110 may be connectable to an external power source (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 source to the power source 4136. This may be, for example, for charging the power source 4136. The power circuit 4137 may perform any formatting, converting, or other modification to the power from the power source 4136 to make it suitable for each component of the WD 4110 to which the power is supplied.

[0162] Figure 10 is another block diagram of a user equipment according to some embodiments. As used herein, a UE 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, such as a smart sprinkler controller, that is intended for sale to, or operation by, a human user, but may not be associated with, or initially associated with, a particular human user. Alternatively, a UE may represent a device, such as a smart power meter, that is not intended for sale to, or operation by, an end user, but may be associated with a user or operated for the benefit of a user. UE4200 can be any UE identified by 3GPP, including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE4200 shown in FIG. 10 is an example of a WD configured for communication according to one or more communication standards published by 3GPP, such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As described above, the terms WD and UE may be used interchangeably. Thus, although FIG. 10 is a UE, the components described herein are equally applicable to a WD, and vice versa.

[0163] In FIG. 10, the UE 4200 includes a processing circuit 4201 operably coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, a memory 4215 including a random access memory (RAM) 4217, a read-only memory (ROM) 4219, a storage medium 4221, etc., a communication subsystem 4231, a power supply 4213, and / or any other components, or any combination thereof. 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 FIG. 10 or only a subset of those components. The level of integration between components may vary from UE to UE. Further, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0164] In FIG. 10, the processing circuit 4201 may be configured to process computer instructions and data. The processing circuit 4201 may be operable to execute machine instructions stored in the memory as a machine-readable computer program, such as any sequential state machine, programmable logic together with appropriate firmware, a microprocessor or a digital signal processor (DSP) together with appropriate software, etc., such as one or more hardware-implemented state machines in discrete logic, FPGA, ASIC, etc., one or more program-embedded, general-purpose processors, or any combination of the above. For example, the processing circuit 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

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

[0166] In FIG. 10, the RF interface 4209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 4211 can be configured to provide a communication interface to the network 4243a. The network 4243a can 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 4243a can include a Wi-Fi network. The network connection interface 4211 can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices on a communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 4211 can implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0167] RAM 4217 can be configured to interface with the processing circuit 4201 via the 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 can be configured to provide computer instructions or data to the processing circuit 4201. For example, ROM 4219 can be configured to store invariant low-level system code or data for basic system functions such as basic input / output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. The storage medium 4221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 4221 can be configured to include 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 can store any of a variety of operating systems or combinations of operating systems for use by the UE 4200.

[0168] The storage medium 4221 can be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high definition digital versatile disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a subscriber identity module or a removable user identity information (SIM / RUIM) module such as a smart card memory, other memories, or any combination thereof. The storage medium 4221 can enable the UE4200 to access computer-executable instructions, application programs, etc. stored in a temporary or non-temporary memory medium, offload data, or upload data. A manufactured product such as a manufactured product using a communication system can be tangibly embodied in the storage medium 4221, and the storage medium 4221 can comprise a device-readable medium.

[0169] In FIG. 10, the processing circuit 4201 can be configured to communicate with the network 4243b using the communication subsystem 4231. The network 4243a and the network 4243b can be the same one or more networks or different one or more networks. The communication subsystem 4231 can be configured to include one or more transceivers used to communicate with the network 4243b. For example, the communication subsystem 4231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another WD, UE, or base station capable of wireless communication, such as another device capable of wireless access network (RAN) according to one or more communication protocols, such as IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver can include a transmitter 4233 and / or a receiver 4235 for implementing a transmitter function or a receiver function suitable for the RAN link, respectively. Further, the transmitter 4233 and the receiver 4235 of each transceiver can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0170] The communication functions of the communication subsystem 4231 can 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) for determining location, other similar communication functions, or any combination thereof. For example, the communication subsystem 4231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 4243b can 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, other similar networks, or any combination thereof. For example, the network 4243b can be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 4213 can be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 4200.

[0171] The features, benefits, and / or functions described herein can be implemented in one of the components of the UE 4200 or can be divided across multiple components of the UE 4200. Further, the features, benefits, and / or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 4231 can be configured to include any of the components described herein. Further, the processing circuit 4201 can be configured to communicate with any of such components over the bus 4202. In another example, any of such components can be represented by program instructions stored in a memory that, when executed by the processing circuit 4201, implement the corresponding functions described herein. In another example, the functions of any of such components can be divided between the processing circuit 4201 and the communication subsystem 4231. In another example, the non-computation-intensive functions of any of such components can be implemented in software or firmware, and the computation-intensive functions can be implemented in hardware.

[0172] FIG. 11 is a block diagram of a virtualized environment 4300 in which functions implemented by some embodiments can be virtualized. In this context, virtualizing means creating a virtual version of a device or apparatus that may include virtualizing the hardware platform, memory devices, and networking resources. As used herein, virtualization can be applied to nodes, such as virtualized base stations or virtualized radio access nodes, or to devices, such as UEs, wireless devices, or any other type of communication device, or components of such devices, and at least a portion of the functions are implemented as one or more virtual components that are executed via one or more applications, components, functions, virtual machines, or containers that execute on one or more physical processing nodes in one or more networks.

[0173] Some or all of the functions described herein can be implemented as virtual components that are executed by one or more virtual machines hosted in one or more virtualized environments 4300 by one or more of the hardware nodes 4330. Further, in embodiments where the virtual node is not a radio access node or does not require wireless connectivity, the network node can be fully virtualized.

[0174] The functionality may be implemented by one or more applications 4320, alternatively referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc., that are operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The application 4320 is operative in a virtualization environment 4300 that provides hardware 4330 comprising a processing circuit 4360 and a memory 4390. The memory 4390 contains instructions 4395 executable by the processing circuit 4360 such that the application 4320 is operable to provide one or more of the features, benefits, and / or functions disclosed herein.

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

[0176] The virtual machine 4340 comprises virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be operated by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of virtual appliances 4320 can be implemented on one or more of the virtual machines 4340, and the implementation can be done in different ways.

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

[0178] As shown in FIG. 11, the hardware 4330 can be a stand-alone network node with general or specific components. The hardware 4330 can include an antenna 43225 and can implement some functions through virtualization. Alternatively, the hardware 4330 can be part of a larger class of hardware, such as in the case of a data center or customer premise equipment, where multiple hardware nodes cooperate and are managed through a management and orchestration (MANO) 43100 that oversees, in particular, the lifecycle management of the application 4320.

[0179] The virtualization of hardware is called network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premise equipment.

[0180] In the context of NFV, the virtual machines 4340 can be software implementations of physical machines that run programs as if those programs were running on a non-virtualized physical machine. Each of the virtual machines 4340 forms a separate virtual network element (VNE) with that part of the hardware 4330 that executes the virtual machine, whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines among the virtual machines 4340.

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

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

[0183] Some signaling can be implemented using a control system 43230 that can alternatively be used for communication between the hardware node 4330 and the radio unit 43200.

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

[0185] The communication network 4410 is itself connected to a host computer 4430, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources within a server farm. The host computer 4430 may be under the ownership or 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 them. The intermediate network 4420 may, if any, be a backbone network or the Internet. In particular, the intermediate network 4420 may comprise two or more sub-networks (not shown).

[0186] The communication system of FIG. 12 enables connectivity between the connected UEs 4491, 4492 and the host computer 4430. The connectivity can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491, 4492 are configured to communicate data and / or signaling via the OTT connection 4450, mediated by the access network 4411, the core network 4414, any intermediate network 4420, and any additional infrastructure (not shown) that may be considered. The OTT connection 4450 can be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 4412 may not be informed or need to be informed about the past routing of an incoming downlink communication with data originating from the host computer 4430 that is to be forwarded (e.g., handed over) to the connected UE 4491. Similarly, the base station 4412 does not need to be aware of the future routing of an outgoing uplink communication originating from the UE 4491 and destined for the host computer 4430.

[0187] FIG. 13 is a block diagram of a host computer communicating with a 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 FIG. 13. In the communication system 4500, the host computer 4510 comprises hardware 4515 including a communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of different communication devices of the communication system 4500. The host computer 4510 further comprises a processing circuit 4518, which may have a memory capacity and / or a processing capacity.

[0188] 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 that 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 operable to provide services to remote users, such as the UE 4530, that connect via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. When providing services to a remote user, the host application 4512 may provide user data transmitted using the OTT connection 4550.

[0189] The communication system 4500 further includes a base station 4520 provided in the communication system, and the base station 4520 includes hardware 4525 that enables the base station 4520 to communicate with the host computer 4510 and the UE 4530. The hardware 4525 includes a communication interface 4526 for setting up and maintaining a wired or wireless connection with an interface 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 a coverage area (not shown in FIG. 13) served by the base station 4520. The communication interface 4526 can be set to facilitate the connection 4560 to the host computer 4510. The connection 4560 can be direct, or the connection 4560 can pass through the core network of the communication system (not shown in FIG. 13) and / or one or more intermediate networks external to the communication system. In the illustrated embodiment, the hardware 4525 of the base station 4520 further includes a processing circuit 4528, and the processing circuit 4528 can include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 4520 further has software 4521 stored internally or accessible via an external connection.

[0190] The communication system 4500 further includes the UE 4530 already mentioned. The hardware 4535 of the UE 4530 may include a radio interface 4537 configured to set up and maintain a radio connection 4570 with a base station serving the coverage area where the UE 4530 is currently located. The hardware 4535 of the UE 4530 further includes a processing circuit 4538, which 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 UE 4530 further comprises software 4531 stored in or accessible by the UE 4530 and executable by the processing circuit 4538. The software 4531 includes a client application 4532. The client application 4532 may be operable to provide services to a human or non-human user via the UE 4530 under the support of the host computer 4510. In the host computer 4510, the running host application 4512 may communicate with the running client application 4532 via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. When providing services to the user, the client application 4532 may receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 may transfer both the request data and the user data. The client application 4532 may interact with the user to generate the user data provided by the client application 4532.

[0191] Note that the host computer 4510, base station 4520, and UE 4530 shown in FIG. 16 can be the same as or equivalent to one of the host computer 4430, base stations 4412a, 4412b, 4412c in FIG. 15, and one of the UEs 4491, 4492, respectively. That is, the operation inside these entities can be as shown in FIG. 13, and separately, the surrounding network topology can be the same as that in FIG. 12.

[0192] In FIG. 13, the OTT connection 4550 is abstractly depicted to show communication between the host computer 4510 and the UE 4530 via the base station 4520 without explicit mention of the mediation device and the exact routing of messages through these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the UE 4530, from the service provider operating the host computer 4510, or from both. While the OTT connection 4550 is active, the network infrastructure can further make a decision to dynamically change the routing (e.g., based on network load distribution considerations or reconfiguration).

[0193] The radio connection 4570 between the UE 4530 and the base station 4520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments can use the OTT connection 4550 of which the radio connection 4570 forms the last segment to improve the performance of the OTT service provided to the UE 4530. More precisely, the teachings of these embodiments can improve the random access speed and / or reduce the random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0194] Measurement procedures can be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve. There may further be optional network functions for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to variations in the measurement results. The measurement procedures and / or the network functions for reconfiguring the OTT connection 4550 can be implemented in the software 4511 and hardware 4515 of the host computer 4510 or in the software 4531 and hardware 4535 of the UE 4530, or both. In an embodiment, a sensor (not shown) can be deployed in or associated with a communication device through which the OTT connection 4550 passes, and the sensor can participate in the measurement procedure 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. The reconfiguration of the OTT connection 4550 can include message format, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 4520 and can be unknown or imperceptible to the base station 4520. Such procedures and functions are known and can be practiced in the art. In some embodiments, the measurement can involve proprietary UE signaling that facilitates measurement of the host computer 4510 such as throughput, propagation time, latency, etc. The measurement can be implemented in that the software 4511 and 4531 cause messages, particularly empty or "dummy" messages, to be transmitted using the OTT connection 4550 while the software 4511 and 4531 monitor propagation time, errors, etc.

[0195] FIG. 14 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment according to some embodiments. The communication system may be the one described with reference to FIGS. 9-10 and includes a host computer, a base station, and a UE. For simplicity of the present disclosure, only the drawing reference to FIG. 14 is included in this section. In step 4610, the host computer provides user data. In an optional sub-step 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 conveys the user data to the UE. In an optional step 4630, the base station transmits the user data conveyed in the transmission initiated by the host computer to the UE according to the teachings of the embodiments described throughout the present disclosure. In an also optional step 4640, the UE executes a client application related to the host application executed by the host computer.

[0196] FIG. 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 some embodiments. The communication system may be the one described with reference to FIGS. 9-10 and includes a host computer, a base station, and a UE. For simplicity of the present disclosure, only the drawing reference to FIG. 15 is included in this section. In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 4720, the host computer initiates a transmission that conveys the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout the present disclosure. In an optional step 4730, the UE receives the user data conveyed in the transmission.

[0197] FIG. 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 some embodiments. The communication system can be the one described with reference to FIGS. 9 - 10 and includes a host computer, a base station, and a UE. For simplicity of the present disclosure, only the reference to FIG. 16 is included in this section. Optionally, in step 4810, the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In an optional sub - step 4821 of step 4820, the UE provides user data by executing a client application. In an optional sub - step 4811 of step 4810, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the particular manner in which user data is provided, the UE, in an optional sub - step 4830, initiates the transmission of the user data to the host computer. In step 4840 of the method, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout the present disclosure.

[0198] FIG. 17 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. FIG. 17 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may be the one described with reference to FIGS. 9-10 and includes a host computer, a base station, and a UE. For the sake of simplicity of the present disclosure, only the reference to FIG. 17 is included in this section. In an optional step 4910, according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In an optional step 4920, the base station initiates transmission of the received user data to the host computer. In an optional step 4930, the host computer receives the user data carried in the transmission initiated by the base station.

[0199] Any suitable steps, methods, features, functions, or benefits 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 a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or several 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 the memory includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the present disclosure.

[0200] FIG. 18 discloses an exemplary computing environment 1800 implementing a method and network node and UE for MBS services to UEs in the idle state and non - active state as described in FIGS. 2 and 3 - 5. As shown in FIG. 18, the computing environment 1800 includes at least one data processing unit 1806 equipped with a control unit 1802 and an arithmetic logic unit (ALU) 1804, a memory 1808, a storage 1810, a plurality of networking devices 1814, and a plurality of input / output (I / O) devices 1812. The data processing unit 1806 is responsible for processing algorithmic instructions. For example, the data processing unit 1806 is equivalent to a processor of a network node. The data processing unit 1806 is capable of executing software instructions stored in the memory 1808. The data processing unit 1806 receives commands from the control unit 1802 to perform its processing. Further, the logical and arithmetic operations involved in the execution of instructions are calculated with the help of the ALU 1804.

[0201] A computer program may be loadable into the data processing unit 1806, which may be provided in an electronic device (such as a UE or a network node). When loaded into the data processing unit 1806, the computer program may be stored in the memory 1808, which is associated with or provided in the data processor. According to some embodiments, when the computer program is loaded into and operated by the data processing unit 1806, it may cause the execution of method steps, for example, according to any of the methods shown in FIGS. 2 and 3 - 5 or otherwise described herein.

[0202] The overall computing environment 1800 may be composed of multiple homogeneous and / or heterogeneous cores, multiple CPUs of different types, special media, and other accelerators. The data processing unit 1806 is responsible for processing the instructions of the algorithm. Further, the multiple data processing units 1806 may be located on a single chip or across multiple chips.

[0203] The algorithm including the instructions and code required for implementation is stored in either the memory 1808 or the storage 1810, or both. At runtime, the instructions can be fetched from the corresponding memory 1808 and / or storage 1810 and executed by the data processing unit 1806.

[0204] In the case of a hardware implementation form, various networking devices 1814 or external I / O devices 1812 can be connected to the computing environment to support the implementation through the networking devices 1814 and the I / O devices 1812.

[0205] The embodiments disclosed herein can be implemented through at least one software program that runs on at least one hardware device and implements a network management function to control elements. The elements shown in FIG. 18 include blocks that can be at least one of a hardware device or a combination of a hardware device and a software module.

[0206] The foregoing description of specific embodiments fully discloses the general nature of the embodiments herein, such that others can, by applying current knowledge, readily modify and / or adapt such specific embodiments for various applications without departing from the general concept, and thus, such adaptations and modifications should and are to be understood to be within the meaning and equivalence of the disclosed embodiments. It is to be understood that the terminology or phraseology employed herein is for the purpose of description and not of limitation. Accordingly, while embodiments of the present disclosure have been described with reference to preferred embodiments, those skilled in the art will recognize that the embodiments of the present disclosure can be practiced with modification within the scope of the present disclosure.

Claims

1. In a wireless communication network (100), a method (200) implemented by a network node (102) for providing a multicast and broadcast service (MBS) to one or more user equipments (UE) (104a - 104n), the method comprising: - determining, based on one or more of the one or more network parameters for the MBS, the capability information of the one or more UEs (104a - 104n), and one or more MBS parameters, an RRC state of the one or more UEs (104a - 104n) for receiving MBS data, the RRC state including one of an RRC idle state, an RRC inactive state, and an RRC connected state (201); - determining the one or more UEs (104a - 104n) that are in one of the RRC idle state and the RRC inactive state (202); - transmitting a paging message including an instruction to enable the determined one or more UEs (104a - 104n) to obtain point - to - multipoint (PTM) configuration information for receiving the MBS data in the determined RRC state (206); - transmitting the MBS data to the determined one or more UEs (104a - 104n) using the PTM configuration indicated by the PTM configuration information (208) The method (200) comprising.

2. The capability information of the one or more UEs (104a - 104n) includes the capability information of the one or more UEs (104a - 104n) for receiving the MBS data, The method according to claim 1, wherein the RRC state of the one or more UEs (104a - 104n) is determined based at least on the capability information of the one or more UEs (104a - 104n) for receiving the MBS data.

3. - determining whether to transmit the PTM configuration information to the one or more UEs (104a - 104n) that are in one of the RRC idle state and the RRC inactive state through a common control channel (204); - When it is determined that the PTM setting should be transmitted through the common control channel, transmitting the PTM setting information through the common control channel to the one or more UEs (104a - 104n) (205); The method according to claim 1 or 2, further comprising.

4. The paging message includes - A session ID for the MBS, - An indication to at least one of the determined one or more UEs (104a - 104n) for receiving the MBS data in the RRC idle state and the RRC inactive state or the RRC connected state, - An indication to at least one of the determined one or more UEs (104a - 104n) to enter the RRC connected state to obtain the PTM setting information, - A preamble indicating the PTM setting for receiving the MBS data to be obtained in the RRC connected state, - An indicator to be monitored by each of the UEs (104a - 104n) to obtain the preamble, - An indication as to whether to use pre - stored PTM setting information for the determined one or more UEs (104a - 104n), or to enter the RRC connected state through a random access procedure to obtain the PTM setting, - An indication as to whether to reuse the most recent PTM setting or to obtain the PTM setting for at least one of the determined one or more UEs (104a - 104n), - An indication as to whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and the RRC inactive state, - An indication as to whether the PTM transmission is the last PTM transmission in the session related to the PTM setting information, - An indication regarding the start time interval and end time interval of the MBS session, - An indication as to whether the one or more UEs need to respond to the paging message The method according to any one of claims 1 to 3, including one or more of.

5. When the paging message including the indication for entering the RRC connected state is transmitted, the PTM configuration information is transmitted to the one or more UEs (104a-104n) in the RRC connected state. The method according to any one of claims 1 to 4.

6. The PTM configuration information includes one or more of a service ID, a session ID, information related to scheduling of PTM data, information related to adjacent cells transmitting the MBS data, information on ongoing MBS sessions, and information on all MBS sessions. The method according to any one of claims 1 to 5.

7. The PTM configuration information is transmitted through a common control channel in a system information block (SIB) periodically transmitted by the network node (102). The method according to any one of claims 1 to 6.

8. The common control channel is a PTM downlink control channel. The method according to claim 7.

9. The PTM configuration information is transmitted to the one or more UEs (104a-104n) through the common control channel based on receiving a request for the PTM configuration information from the one or more UEs (104a-104n) in one of the RRC idle state and the RRC inactive state. The method according to claim 7 or 8.

10. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a-104n) - indicating the PTM configuration information periodically broadcast by the network node (102) through one or more SIBs includes information for notifying the one or more UEs (104a-104n). The method according to any one of claims 1 to 9.

11. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a-104n) - receiving a request for the PTM configuration information from the one or more UEs (104a-104n) in one of the RRC idle state and the RRC inactive state, and - indicating the PTM configuration information to the one or more UEs (104a-104n) in an SIB The method according to any one of claims 1 to 10, comprising information for notifying the one or more UEs (104a to 104n).

12. The paging message that indicates the PTM setting information to be obtained by the one or more UEs, - indicating the PTM setting information through a PTM downlink common control channel The method according to any one of claims 1 to 11, comprising information for notifying the one or more UEs (104a to 104n).

13. The paging message that indicates the PTM setting information to be obtained by the one or more UEs (104a to 104n), - receiving, from the one or more UEs (104a to 104n), information on a session related to MBS data in a message 3 (MSG3) of a random access procedure; - indicating, in a message 4 (MSG4) of the random access procedure, the PTM setting information related to the MBS data to the one or more UEs (104a to 104n) The method according to any one of claims 1 to 12, comprising information for notifying the one or more UEs (104a to 104n).

14. A method (300) performed by a user equipment (UE) (104) for receiving multicast and broadcast services (MBS) from a network node (102) in a wireless communication network (100), the method (300) comprising: - transitioning (302) to one of a radio resource control (RRC) idle state and an RRC inactive state; - receiving a paging message including an indication for enabling the UE (104) to obtain point-to-multipoint (PTM) setting information for receiving MBS data in an RRC state including one of the RRC idle state, the RRC inactive state, and the RRC connected state, the RRC state being determined by the network node (102) for receiving MBS data based on one or more of one or more network parameters for the MBS, capability information of the UE (104), and one or more MBS parameters; - Receiving the MBS data from the network node (102) using the PTM setting indicated by the PTM setting information (308); A method (300) comprising. **Claim 15** - Determining PTM setting information to be obtained on a common control channel (304); - Receiving the PTM setting information through the common control channel when the PTM setting is determined on the common control channel (305); The method according to claim 14, further comprising. **Claim 16** The paging message is - A session ID; - An indication for receiving the MBS data in the RRC idle state and the RRC inactive state or the RRC connected state; - An indication to enter the RRC connected state to obtain the PTM setting information; - A preamble for obtaining the PTM setting for receiving the MBS data in the RRC connected state; - An indicator to be monitored for obtaining the preamble; - An indication as to whether to use pre-stored PTM setting information or to enter the RRC connected state through a random access procedure to obtain the PTM setting; - An indication as to whether to reuse the most recent PTM setting or to obtain the PTM setting; - An indication to enter the RRC connected state from one of the RRC idle state and the RRC inactive state; - An indication as to whether the PTM transmission is the last PTM transmission in a session related to the PTM setting; - An indication regarding the start time interval and the end time interval of the MBS session; - An indication as to whether to respond to the paging message The method according to claim 14 or 15, comprising one or more of. **Claim 17** Receiving the MBS data from the network node (102) is - Setting a PTM radio bearer based on the PTM setting information; - Receiving the MBS data using the PTM radio bearer The method according to any one of claims 14 to 16, comprising. **Claim 18** The method according to any one of claims 14 to 17, wherein when the paging message including the instruction for the UE to enter the RRC connected state to obtain the PTM setting is received, the PTM setting information is received in the RRC connected state.

19. The method according to any one of claims 14 to 18, wherein the PTM setting information includes one or more of a service ID, a session ID, information related to scheduling of PTM data, information related to adjacent cells transmitting the MBS data, information on an ongoing MBS session, and information on all MBS sessions.

20. The method according to any one of claims 14 to 19, wherein the PTM setting information is received through a common control channel in a system information block (SIB) periodically transmitted by the network node (102).

21. The method according to any one of claim 15, claims 16 to 19 when citing claim 15, or claim 20, wherein the common control channel is a PTM downlink control channel.

22. The method according to any one of claim 15, claims 16 to 19 when citing claim 15, or claims 20 to 21, wherein in response to transmission of a request for the PTM setting in one of the RRC idle state and the RRC inactive state, the PTM setting information is received through the common control channel.

23. The paging message indicating the PTM setting information to be obtained by the UE (104) - receives an indication of the PTM setting periodically broadcast by the network node (102) through one or more SIBs The method according to any one of claims 14 to 22, including information for notifying the UE (104).

24. The paging message indicating the PTM setting information to be obtained by the UE (104) - transmitting a request for the PTM setting information in one of the RRC idle state and the RRC inactive state; - receiving an indication of the PTM setting information in the SIB The method according to any one of claims 14 to 23, including information for notifying the UE (104).

25. The paging message that instructs the PTM setting information to be acquired by the UE includes - receiving an instruction of the PTM setting through a PTM downlink common control channel The method according to any one of claims 14 to 24, including information for notifying the UE (104). **Claim 26** The paging message that instructs the PTM setting information to be acquired by the UE (104) includes - transmitting information on a session related to MBS data in Message 3 (MSG3) of a random access procedure; - receiving the PTM setting information related to the MBS data in Message 4 (MSG4) of the random access procedure The method according to any one of claims 14 to 25, including information for notifying the UE (104). **Claim 27** In a wireless communication network (100), a network node (102) for providing a multicast and broadcast service (MBS) to one or more user equipment (UE) (104a to 104n), the network node (102) - determining (201) an RRC state of the one or more UE (104a to 104n) for receiving MBS data based on one or more of one or more network parameters for the MBS, capability information of the one or more UE (104a to 104n), and one or more MBS parameters, the RRC state including one of an RRC idle state, an RRC inactive state, and an RRC connected state; - determining (202) the one or more UE (104a to 104n) in one of the RRC idle state and the RRC inactive state; - transmitting (206) a paging message including an instruction for enabling the determined one or more UE (104a to 104n) to acquire PTM setting information for receiving the MBS data in the determined RRC state; - transmitting the MBS data to the determined one or more UE (104a to 104n) using the PTM setting indicated by the PTM setting information (208) A network node (102) adapted to perform **Claim 28** The capability information of the one or more UEs (104a - 104n) includes the capability information of the one or more UEs (104a - 104n) for receiving the MBS data, The RRC state of the one or more UEs (104a - 104n) is determined based at least on the capability information of the one or more UEs (104a - 104n) for receiving the MBS data. The network node (102) according to claim 27. **Claim 29** The network node (102) is - Determining (204) whether to transmit the PTM configuration information to the one or more UEs (104a - 104n) in one of the RRC idle state and the RRC inactive state through a common control channel; - Transmitting (205) the PTM configuration information to the one or more UEs (104a - 104n) through the common control channel when it is determined that the PTM configuration should be transmitted through the common control channel The network node (102) according to claim 27 or 28, further adapted to perform **Claim 30** The paging message includes - A session ID for the MBS; - An indication to at least one of the determined one or more UEs (104a - 104n) for receiving the MBS data in the RRC idle state, the RRC inactive state or the RRC connected state; - An indication to at least one of the determined one or more UEs (104a - 104n) to enter the RRC connected state to obtain the PTM configuration information; - A preamble indicating the PTM configuration for receiving the MBS data to be obtained in the RRC connected state; - An indicator to be monitored by each of the UEs (104a - 104n) to obtain the preamble; - An indication as to whether to use pre - stored PTM configuration information for the determined one or more UEs (104a - 104n) or to enter the RRC connected state through a random access procedure to obtain the PTM configuration. - An instruction on whether to reuse the most recent PTM setting for at least one of the determined one or more UEs (104a - 104n), or whether to acquire the PTM setting, - An instruction on whether at least one of the determined one or more UEs should enter the RRC connected state from one of the RRC idle state and the RRC inactive state, - An instruction on whether the PTM transmission is the last PTM transmission in a session related to the PTM setting information, - An instruction on the start time interval and end time interval of the MBS session, - An instruction on whether the one or more UEs need to respond to the paging message One or more of which are included in the network node (102) according to any one of claims 27 to 29.

31. When the paging message including the instruction for entering the RRC connected state is transmitted, the PTM setting information is transmitted to the one or more UEs (104a - 104n) in the RRC connected state, the network node (102) according to any one of claims 27 to 30.

32. The PTM setting information includes one or more of a service ID, a session ID, information related to the scheduling of PTM data, information related to adjacent cells transmitting the MBS data, information on an ongoing MBS session, and information on all MBS sessions, the network node (102) according to any one of claims 27 to 31.

33. The PTM setting information is transmitted through a common control channel in a system information block (SIB) periodically transmitted by the network node (102), the network node (102) according to any one of claims 27 to 32.

34. The network node (102) according to claim 33, wherein the common control channel is a PTM downlink control channel.

35. The network node (102) according to claim 33 or 34, wherein the PTM configuration information is transmitted based on reception of a request for the PTM configuration information from the one or more UEs (104a to 104n) in one of the RRC idle state and the RRC inactive state, through the common control channel, to the one or more UEs (104a to 104n).

36. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a to 104n) is - indicating the PTM configuration information periodically broadcast by the network node (102) through one or more SIBs The network node (102) according to any one of claims 27 to 35, comprising information for notifying the one or more UEs (104a to 104n).

37. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a to 104n) is - receiving a request for the PTM configuration information from the one or more UEs (104a to 104n) in one of the RRC idle state and the RRC inactive state - indicating the PTM configuration information to the one or more UEs (104a to 104n) in the SIB The network node (102) according to any one of claims 27 to 36, comprising information for notifying the one or more UEs (104a to 104n).

38. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a to 104n) is - indicating the PTM configuration information through the PTM downlink common control channel The network node (102) according to any one of claims 27 to 37, comprising information for notifying the one or more UEs (104a to 104n).

39. The paging message indicating the PTM configuration information to be acquired by the one or more UEs (104a to 104n) is - In a message 3 (MSG3) of a random access procedure, receiving information on a session related to MBS data from the one or more UEs (104a to 104n); - In a message 4 (MSG4) of the random access procedure, instructing the one or more UEs (104a to 104n) of the PTM setting information related to the MBS data The network node (102) according to any one of claims 27 to 37, comprising information for notifying the one or more UEs (104a to 104n).

40. A user equipment (UE) (104) for receiving multicast and broadcast services (MBS) from a network node (102) in a wireless communication network (100), wherein the UE (104) - Transitions to one of a radio resource control (RRC) idle state and an RRC inactive state (302); - A paging message including an instruction for enabling the UE (104) to obtain point-to-multipoint (PTM) setting information for receiving MBS data in an RRC state determined by the network node (102) for receiving MBS data based on one or more network parameters for the MBS, capability information of the UE (104), and one or more of the MBS parameters, the RRC state including one of the RRC idle state, the RRC inactive state, and the RRC connected state (306); - Receiving the MBS data from the network node (102) using the PTM setting indicated by the PTM setting information (308) The user equipment (UE) (104) adapted to perform.

41. The UE (104) - Determining PTM setting information to be obtained on a common control channel (304); - Receiving the PTM setting information through the common control channel when the PTM setting is determined on the common control channel (305) The UE (104) according to claim 40, further adapted to perform.

42. The paging message - A session ID; - An instruction for receiving the MBS data in the RRC idle state, the RRC inactive state, or the RRC connected state, - An instruction for entering the RRC connected state to obtain the PTM setting information, - A preamble for obtaining the PTM setting for receiving the MBS data in the RRC connected state, - An indicator to be monitored for obtaining the preamble, - An instruction on whether to use pre-stored PTM setting information or enter the RRC connected state through a random access procedure to obtain the PTM setting, - An instruction on whether to reuse the most recent PTM setting or obtain the PTM setting, - An instruction for entering the RRC connected state from one of the RRC idle state and the RRC inactive state, - An instruction on whether the PTM transmission is the last PTM transmission in a session related to the PTM setting, - An instruction on the start time interval and end time interval of the MBS session, - An instruction on whether to respond to the paging message One or more of which are included, the UE (104) according to claim 40 or 41.

43. The UE receives the MBS data from the network node (102) by - Setting a PTM radio bearer based on the PTM setting information, - Receiving the MBS data using the PTM radio bearer Adapted to perform, the UE (104) according to any one of claims 40 to 42.

44. When the paging message including the instruction for the UE to enter the RRC connected state to obtain the PTM setting is received, the PTM setting information is received in the RRC connected state, the UE (104) according to any one of claims 40 to 43.

45. The PTM setting information includes one or more of a service ID, a session ID, information related to the scheduling of PTM data, information on adjacent cells transmitting the MBS data, information on an ongoing MBS session, and information on all MBS sessions, the UE (104) according to any one of claims 40 to 44.

46. The UE (104) according to any one of claims 40 to 45, wherein the PTM setting information is received through a common control channel in a system information block (SIB) periodically transmitted by the network node (102).

47. The UE (104) according to any one of claim 41, claims 42 to 45 when dependent on claim 41, or claim 46, wherein the common control channel is a PTM downlink control channel.

48. The UE (104) according to any one of claim 41, claims 42 to 45 when dependent on claim 41, or claims 46 to 47, wherein the PTM setting information is received through the common control channel in response to transmission of a request for the PTM setting in one of the RRC idle state and the RRC inactive state.

49. The paging message indicating the PTM setting information to be obtained by the UE (104) is - receiving, through one or more SIBs, an indication of a PTM setting periodically broadcast by the network node (102) The UE (104) according to any one of claims 40 to 48, comprising information for notifying the UE (104) of this.

50. The paging message indicating the PTM setting information to be obtained by the UE (104) is - transmitting a request for the PTM setting information in one of the RRC idle state and the RRC inactive state; and - receiving an indication of the PTM setting information in an SIB The UE (104) according to any one of claims 40 to 49, comprising information for notifying the UE (104) of this.

51. The paging message indicating the PTM setting information to be obtained by the UE (104) is - receiving an indication of the PTM setting through a PTM downlink common control channel The UE (104) according to any one of claims 40 to 50, comprising information for notifying the UE (104) of this.

52. The paging message indicating the PTM setting information to be obtained by the UE (104) is - transmitting, in a message 3 (MSG3) of a random access procedure, information on a session related to MBS data - In message 4 (MSG4) of the random access procedure, receiving the PTM configuration information related to the MBS data The UE (104) according to any one of claims 40 to 50, comprising information for notifying the UE (104). **Claim 53** A non-transitory computer-readable medium having a computer program comprising program instructions for causing the network node to execute the method according to any one of claims 1 to 13 when executed by a processor of the network node. **Claim 54** A non-transitory computer-readable medium having a computer program comprising program instructions for causing the UE to execute the method according to any one of claims 14 to 26 when executed by a processor of the UE.

Images