access control

Abstract

The present disclosure provides a method for a user equipment (UE), the method comprising: obtaining a notification for participating in an access control procedure of a multicast / broadcast service (MBS) session; and participating in the access control procedure of the MBS session by using MBS specific configuration information.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and more specifically to access control for multicast / broadcast services (MBS). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include, but are not limited to, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); 5th Generation (5G) 3GPP New Radio (NR) standards; and technologies beyond 5G. In a 5G wireless RAN, RAN nodes may include 5G nodes, NR nodes, or gNodeBs (gNBs), which communicate with wireless communication equipment (also known as User Equipment). Summary of the Invention

[0003] According to one aspect of this disclosure, a method for a user equipment (UE) is provided, the method comprising: obtaining a notification of an access control procedure for participating in a multicast / broadcast service (MBS) session; and participating in the access control procedure for the MBS session by using MBS-specific configuration information.

[0004] According to one aspect of this disclosure, a method for a base station is provided, the method comprising: providing notification of an access control procedure for a multicast / broadcast service (MBS) session; and performing the access control procedure of the MBS session using MBS-specific configuration information.

[0005] According to one aspect of this disclosure, an apparatus for a user equipment (UE) is provided, the apparatus comprising one or more processors configured to perform the steps of the method described above.

[0006] According to one aspect of this disclosure, an apparatus for a base station is provided, the apparatus comprising: one or more processors configured to perform the steps of the method described above.

[0007] According to one aspect of this disclosure, a computer-readable medium having a computer program stored thereon is provided, which, when executed by one or more processors, causes a device to perform the steps of the method described above.

[0008] According to one aspect of this disclosure, an apparatus for a communication device is provided, the apparatus including means for performing the steps of the method described above.

[0009] According to one aspect of this disclosure, a computer program product is provided, the computer program product comprising a computer program that, when executed by one or more processors, causes a device to perform the steps of the method described above. Attached Figure Description

[0010] The features and advantages of this disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate the features of this disclosure by way of example.

[0011] Figure 1 It is a block diagram of a system including base stations and user equipment (UE) according to some implementation schemes.

[0012] Figure 2 A flowchart of an exemplary method for a UE according to some implementation schemes is shown.

[0013] Figure 3 A schematic diagram of an MBS-specific UAC mechanism according to some implementation schemes is shown.

[0014] Figure 4 A schematic diagram of an MBS-specific RACH configuration according to some implementation schemes is shown.

[0015] Figure 5 A schematic diagram of MBS-specific controls during the initial access process is shown according to some implementation schemes.

[0016] Figure 6 A flowchart of an exemplary method for a base station according to some implementation schemes is shown.

[0017] Figure 7 Communication devices (e.g., UEs or base stations) according to some implementation schemes are shown.

[0018] Figure 8 An exemplary interface of a baseband circuit according to some implementation schemes is shown.

[0019] Figure 9 The components are shown according to some implementation schemes.

[0020] Figure 10 The architecture of a wireless network according to some implementation schemes is shown. Detailed Implementation

[0021] In this disclosure, a "base station" may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) node B (also commonly referred to as an evolved node B, enhanced node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) and / or a 5G node, New Radio (NR) node, or g node B (gNB), which communicates with wireless communication equipment also referred to as User Equipment (UE). Although some examples may be described with reference to any of E-UTRAN node B, eNB, RNC, and / or gNB, such equipment can be replaced by any type of base station.

[0022] In this field, access control mechanisms for multicast / broadcast services (MBS) are still under research. UEs in an idle / inactive state need to restore or establish a connection to receive an active MBS. However, if many UEs initiate connection establishment or restoration processes simultaneously, network congestion will occur in the absence of a suitable access control mechanism.

[0023] To achieve this objective, this disclosure provides access control for MBS. Various aspects of this disclosure will now be described in conjunction with the accompanying drawings.

[0024] Figure 1 It is a block diagram of a system including base stations and user equipment (UE) according to some implementation schemes. Figure 1 A wireless network 100 according to some embodiments is shown. The wireless network 100 includes a UE 101 and a base station 150 connected via an air interface 190.

[0025] UE 101 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, printer, machine-type device such as a smart meter or dedicated device for healthcare monitoring, remote security monitoring, intelligent transportation systems, or any other wireless device with or without a user interface. Base station 150 can provide UE 101 with network connectivity to a wider network (not shown) via air interface 190 within the base station service area provided by base station 150. In some embodiments, such a wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with base station 150 is supported by an antenna integrated with base station 150. The service area is divided into multiple sectors associated with certain antennas. Such sectors can be physically associated with fixed antennas, or can be assigned to physical areas with tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a particular sector. For example, one implementation of base station 150 includes three sectors, each covering a 120-degree area, wherein the antenna array is pointed at each sector to provide 360-degree coverage around base station 150.

[0026] UE 101 includes control circuitry 105 coupled to transmission circuitry 110 and reception circuitry 115. Transmission circuitry 110 and reception circuitry 115 may each be coupled to one or more antennas. Control circuitry 105 may be adapted to perform operations associated with MTC. In some embodiments, control circuitry 105 of UE 101 may perform calculations or initiate measurements associated with air interface 190 to determine the channel quality of an available connection to base station 150. These calculations may be performed in conjunction with control circuitry 155 of base station 150. Transmission circuitry 110 and reception circuitry 115 may be adapted to transmit and receive data, respectively. Control circuitry 105 may be adapted or configured to perform various operations, such as those associated with the UE described elsewhere in this disclosure. Transmission circuitry 110 may transmit multiple multiplexed uplink physical channels. These multiple uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM). Transmission circuitry 110 may be configured to receive block data from control circuitry 105 for transmission across air interface 190. Similarly, receiving circuitry 115 can receive multiple multiplexed downlink physical channels from air interface 190 and relay these physical channels to control circuitry 105. Uplink and downlink physical channels can be multiplexed according to TDM or FDM. Transmitting circuitry 110 and receiving circuitry 115 can transmit and receive structured control data and content data (e.g., messages, images, video, etc.) within data blocks carried by the physical channels.

[0027] Figure 1 Base station 150 according to various embodiments is also shown. Base station 150 circuitry may include control circuitry 155 coupled to transmission circuitry 160 and receiving circuitry 165. Transmission circuitry 160 and receiving circuitry 165 may each be coupled to one or more antennas, which may be used for communication via air interface 190.

[0028] Control circuitry 155 can be adapted to perform operations associated with the MTC. Transmit circuitry 160 and receive circuitry 165 can be adapted to transmit and receive data respectively within a narrow system bandwidth, which is narrower than the standard bandwidth used for personal communications. In some embodiments, for example, the transmission bandwidth can be set to or close to 1.4 MHz. In other embodiments, other bandwidths can be used. Control circuitry 155 can perform various operations, such as those associated with the base station described elsewhere in this disclosure.

[0029] Within a narrow system bandwidth, transmission circuit 160 can transmit multiple multiplexed downlink physical channels. These multiple downlink physical channels can be multiplexed according to TDM or FDM. Transmission circuit 160 can transmit these multiple multiplexed downlink physical channels in a downlink superframe composed of multiple downlink subframes.

[0030] Within a narrow system bandwidth, receiver circuit 165 can receive multiple multiplexed uplink physical channels. These multiple uplink physical channels can be multiplexed according to TDM or FDM. Receiver circuit 165 can receive these multiple multiplexed uplink physical channels in an uplink superframe composed of multiple uplink subframes.

[0031] As further described below, control circuits 105 and 155 may be involved in measuring the channel quality of air interface 190. Channel quality may be based, for example, on physical barriers between UE 101 and base station 150, electromagnetic interference from other sources, reflections, or indirect paths between UE 101 and base station 150, or other such signal noise sources. Based on channel quality, multiple retransmissions of data blocks can be scheduled, allowing transmission circuit 110 to transmit multiple copies of the same data, and receiving circuit 115 to receive multiple copies of the same data.

[0032] The UE and various base stations described in the following implementation schemes can be provided by, for example Figure 1 The UE 101 and base station 150 are implemented as described above.

[0033] Figure 2 A flowchart of an exemplary method for a UE according to some implementation schemes is shown. Figure 2 The method 200 shown can be derived from, for example Figure 1 The UE 101 implementation is described above.

[0034] like Figure 2 As shown, the method 200 for a UE may include the following steps: S202, obtaining a notification for an access control procedure to participate in a multicast / broadcast service (MBS) session; and S204, participating in the access control procedure for an MBS session using MBS-specific configuration information.

[0035] In step S202, the UE can obtain notification of the access control procedure for participating in the MBS session from the base station. Here, the base station can be configured as follows: Figure 1 The aforementioned base station 150 is implemented.

[0036] In some implementations, notifications for participating in the access control process of an MBS session may include an activation notification for the MBS session.

[0037] Upon receiving an activation notification for an MBS session, a UE in a state such as idle or inactive can enter a connected state to receive the activated MBS session.

[0038] In the following text, each of the idle state, inactive state, and connected state refers to a Radio Resource Control (RRC) state, and may be referred to as the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state, respectively. Therefore, the transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state can respectively refer to the process of RRC connection establishment or RRC recovery.

[0039] In other words, when the RRC connection establishment or RRC recovery process of the UE is triggered by the activation notification of the MBS session, an access control process will be performed between the UE and the base station.

[0040] In some implementations, notifications for participating in access control procedures for an MBS session can be associated with events other than MBS events. In this case, MBS-specific access control mechanisms can also be applied if a UE in the RRC_IDLE or RRC_INACTIVE state is interested in some MBS services that have been activated and wish to enter the RRC_CONNECTED state.

[0041] At step S204, the UE can participate in the access control process of the MBS session by using MBS-specific configuration information.

[0042] In this disclosure, MBS-specific configuration information refers to information specifically or specially configured for the MBS to introduce into the access control process.

[0043] Access control processes can involve various phases, such as Unified Access Control (UAC), Random Access Channel (RACH) configuration (e.g., RACH backoff), and the initial access procedure. Therefore, MBS-specific configuration information can be used in those phases in which the UE participates.

[0044] In other words, to implement access control over the MBS (i.e., MBS reception, since the MBS is only used for the downlink (DL)), this disclosure proposes an MBS-specific UAC mechanism, an MBS-specific RACH configuration (e.g., a RACH backoff mechanism), and MBS-specific control during the initial access process. Reference will be made below. Figures 3 to 5 Describe more details.

[0045] According to some implementation schemes of this disclosure, dynamic access control of MBS can be achieved, thereby mitigating or avoiding network congestion.

[0046] Figure 3 A schematic diagram of an MBS-specific UAC mechanism according to some implementation schemes is shown. Similar to the above, as... Figure 3 The UE and base station shown can be constructed by, for example Figure 1The UE 101 and base station 150 are implemented as described above.

[0047] As mentioned above, UAC is one of the phases that a UE can participate in using MBS-specific configuration information. Therefore, Figure 3 A method 300 for a UE in an MBS-specific UAC mechanism is shown, which can be as follows: Figure 2 The implementation scheme of step 204.

[0048] Method 300 may include the following steps: S302, obtaining MBS-specific Access Class Block (ACB) parameters as MBS-specific configuration information; and S304, applying MBS-specific ACB parameters to trigger the restoration or establishment of a radio resource control (RRC) connection for the MBS session.

[0049] For unicast services, the ACB parameter typically refers to the prohibition factor (called the parameter "uac-BarringFactor") and the prohibition time (called the parameter "uac-BarringTime") used in the UAC process.

[0050] In this disclosure, in order to implement access control over the MBS, the ACB parameters are redesigned as MBS-specific ACB parameters to process the MBS, enabling the restoration or establishment of the MBS's RRC connection to be triggered for UEs in the RRC_IDLE or RRC_INACTIVE state.

[0051] The MBS-specific UAC mechanism proposed in this disclosure can be implemented in two options.

[0052] Option 1 :

[0053] In some implementations, step S302, which involves obtaining MBS-specific ACB parameters, can be associated with the UE's use of the Non-Access Stratum (NAS). In this case, the UE can obtain the Access Category (AC) and Access Identification (AI) information of the MBS session ID mapped to the MBS session, and then identify the MBS-specific ACB parameters from the AC and AI information.

[0054] In this way, the ACB parameters used in the UAC process can have a link or mapping relationship with the MBS session, and therefore the UE can subsequently use the ACB parameters to trigger the RRC connection establishment or RRC recovery process of the MBS session.

[0055] In some implementations, AC and AI information can be pre-configured in the UE's user data or received via System Information Block (SIB) broadcast or NAS MBS session joint procedure. In the broadcast case, AC and AI information can be provided conventionally via SIB1. Therefore, the UE can have various opportunities to obtain the required AC and AI information.

[0056] Option 2 :

[0057] In some implementations, step S302 of obtaining MBS-specific ACB parameters may be associated with the use of the UE's access stratum (AS) rather than NAS. In this case, the UE may receive an MBS session-specific ACB configuration with an MBS session ID linked to the MBS session, and then the MBS-specific ACB parameters may be identified by the MBS session-specific ACB configuration.

[0058] Here is an example of MBS session-specific ACB configuration:

[0059]

[0060] The item associated with "uac-BarringForMBS" is a new item specifically configured for MBS, added to the current ACB configuration for services such as unicast.

[0061] Since the MBS session ID is visible to the UE's AS, the UAC procedure can skip the use of NAS, and therefore the ACB parameter can be directly linked to the MBS session. Thus, the UE can then use the ACB parameter to trigger the MBS session's RRC connection establishment or RRC recovery procedure in a simpler way.

[0062] Therefore, according to some embodiments of this disclosure, dynamic access control of MBS can be implemented during the UAC process, thereby mitigating or avoiding network congestion.

[0063] According to one aspect of this disclosure, in practical applications, there may be situations where a UE simultaneously receives multiple MBS session activation notifications. Therefore, the UE can simultaneously obtain multiple MBS-specific ACB parameters corresponding to multiple MBS sessions, but... Figure 3 The image shows a scenario of an MBS session.

[0064] In this situation, the UE needs to decide which MBS session to follow. In other words, the UE should select the appropriate MBS-specific ACB parameter from among the multiple MBS-specific ACB parameters acquired simultaneously.

[0065] As described above, since the ACB parameters used in the UAC process can have a link or mapping relationship with the MBS session (i.e., the MBS session ID), the UE can select an MBS-specific ACB parameter according to one of the following rules:

[0066] 1) Maximum MBS session ID; 2) Minimum MBS session ID; 3) MBS session ID with the highest QoS requirements; 4) ACB parameter with the highest prohibition factor; 5) ACB parameter with the shortest prohibition time; 6) Up to the UE specific implementation.

[0067] therefore, Figure 2 Step S202 may also include simultaneously acquiring multiple activation notifications from multiple MBS sessions, and therefore Figure 3 Step S302 may include simultaneously acquiring multiple MBS-specific ACB parameters corresponding to multiple MBS sessions. In this case, Figure 2 Method 200 may further include: prior to step 204 of the access control process for participating in the MBS session, selecting an appropriate MBS-specific ACB parameter from among multiple MBS-specific ACB parameters based on the above rules.

[0068] This provides a faster access mechanism when the UE has difficulty selecting an MBS session when multiple MBS session activation notifications are received simultaneously.

[0069] According to one aspect of this disclosure, in practical applications, there will also be situations where the UE simultaneously receives activation notifications for both MBS and non-MBS sessions. Therefore, the UE can simultaneously obtain MBS-specific ACB parameters and non-MBS-specific ACB parameters, but... Figure 3 The example shown is for MBS sessions only.

[0070] In this scenario, the UE can follow either the MBS session or a non-MBS session by applying the corresponding ACB parameters. That is, the UE can follow a non-MBS session to select non-MBS-specific ACB parameters, or follow an MBS session to select MBS-specific ACB parameters.

[0071] Furthermore, the UE can prioritize sessions with higher priority between MBS and non-MBS sessions. For example, a non-MBS session could be a RAN update triggering event, which has a lower priority than an MBS session. Alternatively, a non-MBS session could be an AS / NAS signaling triggering event, which has a higher priority than an MBS session. Additionally, sessions with higher Quality of Service (QoS) requirements (MBS or non-MBS sessions) can have higher priority.

[0072] In other words, Figure 2Step S202 may include simultaneously obtaining activation notifications for both MBS sessions and non-MBS sessions, and therefore Figure 3 Step S302 may include simultaneously acquiring MBS-specific ACB parameters and non-MBS-specific ACB parameters corresponding to non-MBS sessions. In this case, Figure 3 Method 300 may also include determining compliance with the MBS session prior to step S304.

[0073] Figure 4 A schematic diagram of an MBS-specific RACH configuration according to some implementation schemes is shown. Similar to the above, as... Figure 4 The UE and base station shown can be constructed by, for example Figure 1 The UE 101 and base station 150 are implemented as described above.

[0074] As mentioned above, RACH configuration is also one of the phases that the UE can participate in using MBS-specific configuration information. Therefore, Figure 4 A method 400 for a UE in an MBS-specific RACH configuration is shown, which can be as follows: Figure 2 Another implementation of step 204.

[0075] Method 400 may include the following steps: S404, obtaining the dedicated random access channel (RACH) configuration of the RACH triggered by the activation notification of the MBS session as MBS-specific configuration information; and S406, applying the dedicated RACH configuration to the initial access triggered by the activation notification of the MBS session.

[0076] Prior to step S404, the UE may have transmitted a random access preamble (S402) to the base station of the RACH triggered by the activation notification of the MBS session. However, the UE does not receive its own MAC random access response (RAR), but will receive information for performing RACH backoff at step S404.

[0077] In some implementations, a dedicated RACH configuration may include an MBS-specific backoff parameter that indicates the priority of one or more MBS sessions. Therefore, step S406 of applying the dedicated RACH configuration may include: S406-1, determining a delay period for retransmitting the random access preamble by multiplying the MBS-specific backoff parameter by a backoff indicator (BI); and S406-2, retransmitting the random access preamble after the delay period has elapsed.

[0078] Examples of MBS-specific backoff parameters are as follows:

[0079]

[0080] As shown above, MBS-specific backoff parameters can be associated with one or more MBS sessions. That is, the same MBS-specific backoff parameter can be used for multiple MBS sessions. Furthermore, MBS-specific backoff parameters can indicate the priority of an MBS session. Because it is associated with one or more MBS sessions, it can also indicate the priority of one or more MBS sessions.

[0081] Priority can refer to prioritization or de-priorification, meaning a reduction or increase in the RACH backoff period. Since the BI, with its fixed value, indicates the delay period used for the UE to retransmit the random access preamble, the RACH backoff period can be reduced or increased by multiplying the BI by a designed factor or coefficient. In this paper, the designed factor or coefficient is the MBS-specific backoff parameter as described above. This allows for dynamic control of RACH backoff to avoid congestion.

[0082] For example, assuming BI is 100ms, if the MBS specific backoff parameter is less than 1, the RACH backoff time period can be reduced, and if it is greater than 1, the RACH backoff time period can be increased.

[0083] Therefore, according to some embodiments of this disclosure, dynamic access control of MBS can be implemented during RACH configuration, thereby mitigating or avoiding network congestion.

[0084] If the base station does not provide MBS-specific backoff parameters, the UE can use the public RACH configuration for initial access triggered by the MBS activation notification.

[0085] Figure 5 A schematic diagram of MBS-specific controls during the initial access process is shown according to some implementation schemes. Similar to the above, as... Figure 5 The UE and base station shown can be constructed by, for example Figure 1 The UE 101 and base station 150 are implemented as described above.

[0086] As mentioned above, the initial access process is also one of the stages that the UE can participate in using MBS-specific configuration information. Therefore, Figure 5 A method 500 for a UE in MBS-specific control during the initial access process is shown, the method being as follows: Figure 2 Another implementation of step 204.

[0087] In some implementations, MBS-specific configuration information includes MBS-specific information that will be used during the initial access process triggered by an activation notification of the MBS session. Therefore, step 204, which involves participating in the access control process of the MBS session using MBS-specific configuration information, may include applying the MBS-specific information during the initial access process.

[0088] This allows for dynamic control of the initial access process to mitigate or avoid network congestion.

[0089] In some implementations, applying MBS session-specific information may include the following steps: S502, generating the reason for accessing the MBS session as MBS session-specific information in a request to resume (referred to as “RRCResumeRequest”) or establish an RRC connection (referred to as “RRCSetupRequest”); and S504, transmitting the request to resume or establish an RRC connection.

[0090] Examples of RRCResumeRequest and RRCSetupRequest are as follows:

[0091]

[0092] Each of the items “resumeCause” and “establishmentCause” is the reason mentioned above for accessing the MBS session. Note that the initial items “spare1” and “spare 6” have been changed to “MBS-access”.

[0093] Access to MBS sessions can be further categorized into high or low access, indicating the priority of the MBS session. High or low access can be pre-configured by the UE's NA or AS.

[0094] By using the MBS access reason, the base station can distinguish MBS access from other types of access.

[0095] In some implementations, applying MBS session-specific information may include the following steps: S506, obtaining a time period for de-prioritizing access to the MBS session as MBS session-specific information; and S508, re-accessing the MBS session after the time period has elapsed.

[0096] The time period used to de-prioritize access to an MBS session can be indicated by a parameter called "RejectWaitTimer" in a message sent by the base station called "RRCReject" or "RRCRelease". This means that congestion has occurred, and therefore the base station provides a time period for the UE to wait for the next initial access to the MBS session.

[0097] During the RejectWaitTimer period, if other events (e.g., unicast service, NAS procedure) trigger the initial access, the UE can directly trigger the initial access.

[0098] Here is an example of RejectWaitTimer:

[0099]

[0100] In some implementations, applying MBS session-specific information may include the following steps: S510, generating information about the activated MBS session as MBS session-specific information in a message notifying that the initial access to the MBS session is complete; and S512, transmitting a message notifying that the initial access to the MBS session is complete.

[0101] Messages notifying MBS sessions of the completion of initial access may include messages called “RRCResumeComplete” or “RRCSetupComplete”.

[0102] After completing the initial access to the MBS session, the base station can determine the point-to-multipoint (PTM) or point-to-point (PTP) MBS configuration in RRC_CONNECTED mode, or switch the UE to a cell that will provide the MBS session that the UE is interested in.

[0103] Therefore, according to some embodiments of this disclosure, dynamic access control of the MBS can be implemented during the initial access process, thereby mitigating or avoiding network congestion.

[0104] Please note that steps S502 to S512 do not necessarily need to be executed consecutively. Additional or extra steps can be inserted in between for the corresponding functions. Furthermore, steps S502 to S512 may not all be executed, depending on the actual application.

[0105] Figure 6 A flowchart of an exemplary method for a base station according to some implementation schemes is shown. Figure 6 The method 600 shown can be derived from, for example Figure 1 The aforementioned base station 150 is implemented.

[0106] like Figure 6 As shown, the method 600 for a base station may include the following steps: S602, providing notification of an access control procedure for a multicast / broadcast service (MBS) session; and S604, performing an access control procedure for an MBS session using MBS-specific configuration information.

[0107] In step S602, the base station may provide the UE with notification of the access control procedure for the MBS session. Here, the UE may be provided with notification such as... Figure 1 The UE implementation described above.

[0108] In some implementations, notifications for the access control process of an MBS session may include an activation notification for the MBS session.

[0109] Upon receiving an activation notification for an MBS session, a UE in the RRC_IDLE or RRC_INACTIVE state can enter the RRC_CONNECTED state to receive the activated MBS session. Therefore, the transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state can refer to the process of RRC connection establishment or RRC recovery, respectively.

[0110] If you have already referred to Figure 2 As mentioned above, when the RRC connection establishment or RRC recovery process of the UE is triggered by the activation notification of the MBS session, an access control process will be performed between the UE and the base station.

[0111] In some implementations, notifications for access control procedures used in MBS sessions can be associated with events other than MBS events. In this case, MBS-specific access control mechanisms can also be applied if a UE in the RRC_IDLE or RRC_INACTIVE state is interested in some MBS services that have been activated and wish to enter the RRC_CONNECTED state.

[0112] At step S604, the base station can perform the access control procedure for the MBS session by using MBS-specific configuration information.

[0113] If you have already referred to Figures 2 to 5 In detail, MBS-specific configuration information can refer to information that is specifically or specially configured for MBS and incorporated into the access control process.

[0114] To implement access control over MBS, this disclosure proposes an MBS-specific UAC mechanism, an MBS-specific RACH configuration (e.g., a RACH backoff mechanism), and MBS-specific control during the initial access process.

[0115] According to some implementation schemes of this disclosure, dynamic access control of MBS can be achieved, thereby mitigating or avoiding network congestion.

[0116] In some implementations, step 604 may further include: providing an MBS-specific Access Class Block (ACB) parameter as MBS-specific configuration information, said parameter being used to trigger the resumption or establishment of a Radio Resource Control (RRC) connection for the MBS session. This step of the base station may correspond to, for example... Figure 3 Step S302 of the UE.

[0117] In some implementations, providing MBS-specific ACB parameters may include providing access class (AC) and access identification (AI) information of the MBS session ID mapped to the MBS session, from which the MBS-specific ACB parameters are identified. This step of the base station may correspond to, for example... Figure 3 The steps of the UE in "Option 1" are described above.

[0118] In some implementations, providing AC and AI information may include sending AC and AI information via System Information Block (SIB) broadcast or Non-Access Stratum (NAS) MBS session federation procedure.

[0119] In some implementations, providing MBS-specific ACB parameters may include: sending an MBS session-specific ACB configuration with the MBS session ID linked to the MBS session, wherein the MBS-specific ACB parameters are identified by the configuration. This step of the base station may correspond to, for example: Figure 3 The steps of the UE in "Option 2" are described above.

[0120] In some implementations, step 604 may include: providing a dedicated random access channel (RACH) configuration for the RACH triggered by an activation notification of the MBS session as MBS-specific configuration information, said configuration being used for the initial access triggered by the activation notification of the MBS session. This step by the base station may correspond to, for example... Figure 4 Step S404 of the UE.

[0121] In some implementations, a dedicated RACH configuration may include an MBS-specific backoff parameter indicating the priority of one or more MBS sessions, which is multiplied by a backoff indicator (BI) to determine the delay period used for retransmitting the random access preamble. This may correspond to, for example... Figure 4 Step S406-1 of the UE.

[0122] In some implementations, MBS-specific configuration information may include MBS session-specific information that will be used during the initial access process triggered by an activation notification of the MBS session. This has been referenced. Figure 5 Describe it.

[0123] In some implementations, step 604 may further include: receiving a reason for accessing the MBS session as MBS session-specific information, the reason being used to restore or establish an RRC connection for the MBS session. This step of the base station may correspond to, for example... Figure 5 Step S504 of the UE.

[0124] In some implementations, step 604 may include: providing a time period for de-prioritizing access to the MBS session as MBS session-specific information, said time period being used to re-access the MBS session after that time period has elapsed. This step by the base station may correspond to, for example... Figure 5 Step S506 of the UE.

[0125] In some implementations, step 604 may include: receiving information about the activated MBS session as MBS session-specific information via a message notifying the completion of the initial access to the MBS session. This step of the base station may correspond to, for example... Figure 5 Step S512 of the UE.

[0126] In some implementations, after completing the initial access to the MBS session, the base station can determine the point-to-multipoint (PTM) or point-to-point (PTP) MBS configuration in RRC connection mode, or perform a handover to the cell that will provide the MBS session.

[0127] Figure 7 Communication devices (e.g., UEs or base stations) according to some implementation schemes are shown. Figure 7 Example components of a device 700 according to some embodiments are shown. In some embodiments, device 700 may include at least application circuitry 702, baseband circuitry 704, radio frequency (RF) circuitry (shown as RF circuitry 720), front-end module (FEM) circuitry (shown as FEM circuitry 730), one or more antennas 732, and power management circuitry (PMC) (shown as PMC 734) coupled together as shown. Components of the illustrated device 700 may be included in a UE or RAN node. In some embodiments, device 700 may include fewer components (e.g., the RAN node may not utilize application circuitry 702, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 700 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0128] Application circuitry 702 may include one or more application processors. For example, application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 700. In some embodiments, the processor of application circuitry 702 may process IP data packets received from the EPC.

[0129] Baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 704 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 720 and to generate baseband signals for the transmit signal path of RF circuitry 720. Baseband circuitry 704 may interact with application circuitry 702 to generate and process baseband signals and control the operation of RF circuitry 720. For example, in some embodiments, baseband circuitry 704 may include a third-generation (3G) baseband processor (3G baseband processor 706), a fourth-generation (4G) baseband processor (4G baseband processor 708), a fifth-generation (5G) baseband processor (5G baseband processor 710), or other existing, under development, or future generations (e.g., second-generation (2G), sixth-generation (6G), etc.) baseband processor 712. Baseband circuitry 704 (e.g., one or more processors in the baseband processor suite) may handle various radio control functions capable of communicating with one or more radio networks via RF circuitry 720. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in modules stored in memory 718 and executed via a central processing unit (CPU 714). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 704 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0130] In some embodiments, the baseband circuit 704 may include a digital signal processor (DSP), such as one or more audio DSPs 716. The audio DSP 716 may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuit may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuit 704 and the application circuit 702 may be implemented together, for example, on a system-on-a-chip (SoC).

[0131] In some implementations, baseband circuit 704 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 704 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 704 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0132] RF circuit 720 can communicate with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 720 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 720 may include a receive signal path that includes circuitry for down-converting an RF signal received from FEM circuit 730 and providing a baseband signal to baseband circuit 704. RF circuit 720 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 704 and providing an RF output signal for transmission to FEM circuit 730. In some embodiments, the receive signal path of RF circuit 720 may include mixer circuit 722, amplifier circuit 724, and filter circuit 726. In some embodiments, the transmit signal path of RF circuit 720 may include filter circuit 726 and mixer circuit 722. RF circuit 720 may also include synthesizer circuit 728 for synthesizing frequencies used by mixer circuit 722 for the receive signal path and / or transmit signal path. In some embodiments, the mixer circuit 722 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 730 based on the synthesized frequency provided by the synthesizer circuit 728. The amplifier circuit 724 may be configured to amplify the down-converted signal, and the filter circuit 726 may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 704 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, the mixer circuit 722 of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0133] In some implementations, the mixer circuit 722 of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 728 to generate an RF output signal for the FEM circuit 730. The baseband signal can be provided by the baseband circuit 704 and can be filtered by the filter circuit 726.

[0134] In some embodiments, the mixer circuit 722 for the receive signal path and the mixer circuit 722 for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 722 for the receive signal path and the mixer circuit 722 for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 722 for the receive signal path and the mixer circuit 722 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 722 for the receive signal path and the mixer circuit 722 for the transmit signal path may be configured for superheterodyne operation.

[0135] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 720 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 704 may include a digital baseband interface for communicating with the RF circuit 720.

[0136] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0137] In some implementations, synthesizer circuit 728 may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 728 may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0138] Synthesizer circuit 728 can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 722 of RF circuit 720. In some embodiments, synthesizer circuit 728 may be a fractional N / N+1 synthesizer.

[0139] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuitry 704 or the application circuitry 702 (such as an application processor) according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuitry 702.

[0140] The synthesizer circuit 728 of the RF circuit 720 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0141] In some embodiments, the synthesizer circuit 728 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (f LO In some implementations, the RF circuit 720 may include an IQ / polarity converter.

[0142] The FEM circuit 730 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 732, amplify the received signals, and provide an amplified version of the received signals to the RF circuit 720 for further processing. The FEM circuit 730 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by the RF circuit 720 for transmission by one or more of the one or more antennas 732. In various embodiments, amplification via either the transmit or receive signal path may be performed only in the RF circuit 720, only in the FEM circuit 730, or in both the RF circuit 720 and the FEM circuit 730.

[0143] In some embodiments, FEM circuit 730 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 730 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 730 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 720). The transmit signal path of FEM circuit 730 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 720), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more antennas in one or more antennas 732).

[0144] In some implementations, the PMC 734 manages the power supplied to the baseband circuitry 704. Specifically, the PMC 734 controls power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 734 is typically included when the device 700 is capable of being battery powered, for example, when the device 700 is included in an EGE. The PMC 734 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0145] Figure 7 The diagram shows that the PMC 734 is coupled only to the baseband circuit 704. However, in other embodiments, the PMC 734 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 702, the RF circuit 720, or the FEM circuit 730) and perform similar power management operations for those components.

[0146] In some implementations, the PMC 734 may be controlled or otherwise incorporated into various power-saving mechanisms of the device 700. For example, if the device 700 is in an RRC connected state, and in this state the device remains connected to the RAN node because it anticipates receiving communication soon, the device may enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the device 700 may be powered down for short intervals, thereby saving power.

[0147] If there is no data traffic activity during the extended period, device 700 may transition to an RRC idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 700 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 700 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC connected state.

[0148] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0149] The processors of application circuit 702 and baseband circuit 704 are elements that can be used to execute one or more instances of a protocol stack. For example, the processor of baseband circuit 704 can be used alone or in combination to execute Layer 3, Layer 2, or Layer 1 functions, while the processor of application circuit 702 can utilize data received from these layers (e.g., packet data) and further execute Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0150] Figure 8 An exemplary interface 800 of a baseband circuit according to some embodiments is shown. As described above, Figure 7 The baseband circuit 704 may include a 3G baseband processor 706, a 4G baseband processor 708, a 5G baseband processor 710, other baseband processors 712, a CPU 714, and a memory 718 for use by the processors. As shown, each processor in the processor may include a corresponding memory interface 802 for sending / receiving data to / from the memory 718.

[0151] The baseband circuit 704 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 804 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704) and an application circuit interface 806 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704). Figure 7 The application circuit 702 is an interface for sending / receiving data, and the RF circuit interface 808 is used for sending / receiving data to / from the application circuit 702. Figure 7 The RF circuit 720 is an interface for transmitting / receiving data, and the wireless hardware connection interface 810 is used for transmitting / receiving data to / from near field communication (NFC) components. Components (e.g.) (low power consumption) Interfaces for sending / receiving data to / from components and other communication components) and power management interface 812 (e.g., an interface for sending / receiving power or control signals to / from the PMC 734).

[0152] Figure 9 This is a block diagram illustrating a component 900, according to some exemplary embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of executing any or more of the methods discussed herein. Specifically, Figure 9 A schematic diagram of hardware resource 902 is shown, which includes one or more processors 912 (or processor cores), one or more memory / storage devices 918, and one or more communication resources 920, each of which is communicatively coupled via bus 922. For implementations utilizing node virtualization (e.g., NFV), a hypervisor 904 can be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 902.

[0153] Processor 912 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 914 and processor 916.

[0154] The memory / storage device 918 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 918 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0155] Communication resource 920 may include interconnection devices or network interface components or other suitable devices for communicating with one or more peripheral devices 906 or one or more databases 908 via network 910. For example, communication resource 920 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g.) (low power consumption) Components and other communication components.

[0156] Instruction 924 may include software, programs, applications, applets, or other executable code for causing at least any one of the processors 912 to perform any or more of the methods discussed herein. Instruction 924 may reside wholly or partially within processor 912 (e.g., within the processor's cache memory), memory / storage device 918, or any suitable combination thereof. Furthermore, any portion of instruction 924 may be transferred to hardware resource 902 from any combination of peripheral device 906 or database 908. Thus, the memory of processor 912, memory / storage device 918, peripheral device 906, and database 908 are examples of computer-readable and machine-readable media.

[0157] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0158] Figure 10 The architecture of a system 1000 of a network according to some embodiments is shown. System 1000 includes one or more user equipment (UEs), shown in this example as UE 1002 and UE 1004. UE 1002 and UE 1004 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but these UEs may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless handheld terminal, or any computing device that includes a wireless communication interface.

[0159] In some implementations, either UE 1002 or UE 1004 may include an Internet of Things (IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connectivity. The IoT UE may exchange data with an MTC server or device via technologies such as machine-to-machine (M2M) or machine-type communication (MTC), through a Public Land Mobile Network (PLMN), Proximity-Based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or an IoT network. M2M or MTC data exchange may be machine-initiated. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connectivity. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity to the IoT network. UE 1002 and UE 1004 may be configured to connect (e.g., communicatively coupled) to a Radio Access Network (RAN) (shown as RAN 1006). RAN1006 can be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. UE 1002 and UE 1004 utilize connection 1008 and connection 1010, respectively, where each connection includes a physical communication interface or layer (discussed in further detail below); in this example, connection 1008 and connection 1010 are shown as air interfaces for communication coupling and can be consistent with cellular communication protocols such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, Cellular PTT protocols (POC), Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, New Radio (NR) protocols, etc.

[0160] In this implementation, UE 1002 and UE 1004 can also directly exchange communication data via ProSe interface 1012. ProSe interface 1012 may alternatively be referred to as a sidelink interface including one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0161] UE 1004 is shown configured to access an access point (AP) (shown as AP1014) via connection 1016. Connection 1016 may include local wireless connectivity, such as a connection consistent with any IEEE 802.11 protocol, where AP 1014 will include Wireless Fidelity. Router. In this example, AP1014 is connected to the Internet but not to the core network of the wireless system (described in further detail below).

[0162] RAN 1006 may include one or more access nodes that enable connection 1008 and connection 1010. These access nodes (ANs) may be referred to as base stations (BS), node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). RAN 1006 may include one or more RAN nodes for providing macrocell coverage, such as macro RAN node 1018, and one or more RAN nodes for providing femtocells or picocells (e.g., cells with smaller coverage, smaller user capacity, or higher bandwidth compared to macrocells), such as low-power (LP) RAN nodes (e.g., LP RAN node 1020). Either macro RAN node 1018 or LP RAN node 1020 may terminate the air interface protocol and may be the first point of contact for UE 1002 and UE 1004. In some implementations, either the macro RAN node 1018 or the LP RAN node 1020 can fulfill various logical functions of the RAN 1006, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management.

[0163] According to some implementations, UE 1002 and UE 1004 may be configured to communicate with each other or with either macro RAN node 1018 or LP RAN node 1020 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, based on various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0164] In some implementations, the downlink resource grid can be used for downlink transmissions from either RAN node 1018 or LP RAN node 1020 to UE 1002 and UE 1004, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0165] The Physical Downlink Shared Channel (PDSCH) delivers user data and higher-layer signaling to UE 1002 and UE 1004. The Physical Downlink Control Channel (PDCCH) carries information about the transmission format and resource allocation associated with the PDSCH channel. It also notifies UE 1002 and UE 1004 of the transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1004 within the cell) can be performed at either macro RAN node 1018 or LP RAN node 1020 based on channel quality information fed back from either UE 1002 or UE 1004. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each of UE 1002 and UE 1004.

[0166] PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH are first organized into quadruplets, which are then arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to a set of four physical resource elements (REGs) of nine. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the Downlink Control Information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8) can exist.

[0167] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similarly, each ECCE may correspond to a set of nine physical resource elements, referred to as an enhanced resource element group (EREG). In some cases, an ECCE may have a different number of EREGs.

[0168] RAN 1006 is communicatively coupled to the core network (CN) (shown as CN1028) via S1 interface 1022. In various embodiments, CN 1028 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 1022 is divided into two parts: S1-U interface 1024, which carries traffic data between macro RAN node 1018 and LP RAN node 1020 and the serving gateway (S-GW) (shown as S-GW 1032); and S1-Mobility Management Entity (MME) interface (shown as S1-MME interface 1026), which is the signaling interface between macro RAN node 1018 and LP RAN node 1020 and MME 1030. In this implementation, CN 1028 includes an MME 1030, an S-GW 1032, a Packet Data Network (PDN) Gateway (P-GW) (shown as P-GW 1034), and a Home Subscriber Server (HSS) (shown as HSS 1036). The MME 1030 can functionally resemble the control plane of a legacy General Packet Radio Service (GPRS) Support Node (SGSN). The MME 1030 manages access-related mobility aspects such as gateway selection and tracking area list management. The HSS 1036 may include a database for network users, containing subscription-related information to support network entities in handling communication sessions. Depending on the number of mobile subscribers, equipment capacity, network organization, etc., CN 1028 may include one or more HSS 1036s. For example, the HSS 1036 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0169] The S-GW 1032 can terminate the S1 interface 1022 toward RAN 1006 and route data packets between RAN 1006 and CN 1028. Additionally, the S-GW 1032 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and enforcement of certain policies.

[0170] P-GW 1034 can terminate the SGi interface toward the PDN. P-GW 1034 can route data packets between CN 1028 (e.g., an EPC network) and external networks such as a network including application server 1042 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface (shown as IP communication interface 1038). Generally, application server 1042 can be an element that provides applications that use IP bearer resources with the core network (e.g., ETMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, P-GW 1034 is shown communicatively coupled to application server 1042 via IP communication interface 1038. Application server 1042 can also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 1002 and UE 1004 via CN 1028.

[0171] P-GW 1034 can also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) (shown as PCRF 1040) is the policy and charging control element of CN 1028. In non-roaming scenarios, a single PCRF may exist in the domestic public land mobile network (HPLMN) associated with the ETE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic breaches, two PCRFs may exist associated with the UE's IP-CAN session: the home PCRF (H-PCRF) in the HPLMN and the visited PCRF (V-PCRF) in the visited public land mobile network (VPLMN). PCRF 1040 can be communicatively coupled to application server 1042 via P-GW 1034. Application server 1042 can signal PCRF 1040 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 1040 can configure the rule as a policy and charging enforcement function (PCEF) (not shown) with an appropriate communication flow template (TFT) and QoS category identifier (QCI), which begins with QoS and charging specified by application server 1042.

[0172] Additional Examples

[0173] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0174] The following examples relate to other implementation schemes.

[0175] Example 1 is a method for a user equipment (UE), the method comprising: obtaining a notification of an access control procedure for participating in a multicast / broadcast service (MBS) session; and participating in the access control procedure of the MBS session by using MBS-specific configuration information.

[0176] Example 2 is the method according to Example 1, wherein the notification for participating in the access control process of the MBS session includes an activation notification of the MBS session.

[0177] Example 3 is the method according to Example 2, wherein the access control process of participating in the MBS session by using the MBS-specific configuration information includes: obtaining the MBS-specific access class prohibition (ACB) parameter as the MBS-specific configuration information; and applying the MBS-specific ACB parameter to trigger the recovery or establishment of the radio resource control (RRC) connection of the MBS session.

[0178] Example 4 is the method according to Example 3, wherein obtaining the MBS-specific ACB parameter includes: obtaining the access category (AC) and access identification (AI) information of the MBS session ID mapped to the MBS session; and identifying the MBS-specific ACB parameter by the AC and AI information.

[0179] Example 5 is the method according to Example 4, wherein the AC and AI information are pre-configured in the user data of the UE, or received via System Information Block (SIB) broadcast or Non-Access Stratum (NAS) MBS session federation procedure.

[0180] Example 6 is the method according to Example 3, wherein obtaining the MBS-specific ACB parameter includes: receiving an MBS session-specific ACB configuration of an MBS session ID linked to the MBS session; and identifying the MBS-specific ACB parameter by the MBS session-specific ACB configuration.

[0181] Example 7 is the method according to Example 3, wherein obtaining the activation notification of the MBS session further includes: simultaneously obtaining multiple activation notifications of multiple MBS sessions, and wherein obtaining the MBS-specific ACB parameter further includes simultaneously obtaining multiple MBS-specific ACB parameters corresponding to the multiple MBS sessions, and wherein the method further includes: before participating in the access control process of the MBS session, selecting an appropriate MBS-specific ACB parameter among the multiple MBS-specific ACB parameters based on one of the following: the largest or smallest MBS session ID among the MBS session IDs of the multiple MBS sessions, the MBS session ID with the highest QoS requirement, the MBS-specific ACB parameter with the highest priority, or the specific implementation of the UE itself.

[0182] Example 8 is the method according to Example 3, wherein obtaining the activation notification of the MBS session further includes: simultaneously obtaining the activation notification of the MBS session and the activation notification of a non-MBS session, and wherein obtaining the MBS-specific ACB parameter further includes: simultaneously obtaining the MBS-specific ACB parameter and a non-MBS-specific ACB parameter corresponding to the non-MBS session, and wherein participating in the access control process of the MBS session using the MBS-specific configuration information further includes: determining compliance with the MBS session before applying the MBS-specific ACB parameter.

[0183] Example 9 is the method according to Example 2, wherein the access control process of participating in the MBS session by using the MBS-specific configuration information includes: obtaining a dedicated RACH configuration of the Random Access Channel (RACH) triggered by the activation notification of the MBS session as the MBS-specific configuration information; and applying the dedicated RACH configuration to the initial access triggered by the activation notification of the MBS session.

[0184] Example 10 is the method according to Example 9, wherein the dedicated RACH configuration includes an MBS-specific backoff parameter indicating the priority of one or more MBS sessions, and wherein applying the dedicated RACH configuration includes: determining a delay period for retransmitting the random access preamble by multiplying the MBS-specific backoff parameter by a backoff indicator (BI); and retransmitting the random access preamble after the delay period has elapsed.

[0185] Example 11 is the method according to Example 2, wherein the MBS-specific configuration information includes MBS session-specific information to be used during the initial access process triggered by the activation notification of the MBS session, and wherein participating in the access control process of the MBS session by using the MBS-specific configuration information includes: applying the MBS session-specific information during the initial access process.

[0186] Example 12 is the method according to Example 11, wherein applying the information specific to the MBS session includes: generating a reason for accessing the MBS session as the information specific to the MBS session in a request to restore or establish an RRC connection; and transmitting the request to restore or establish the RRC connection.

[0187] Example 13 is the method according to Example 11, wherein applying the information specific to the MBS session includes: obtaining a time period for de-prioritizing access to the MBS session as the information specific to the MBS session; and re-accessing the MBS session after the time period has elapsed.

[0188] Example 14 is the method according to Example 11, wherein applying the information specific to the MBS session includes: generating information about the activated MBS session as the MBS session-specific information in a message notifying the MBS session that the initial access has been completed; and transmitting the message notifying the MBS session that the initial access has been completed.

[0189] Example 15 is a method for a base station, the method comprising: providing notification of an access control procedure for a multicast / broadcast service (MBS) session; and executing the access control procedure of the MBS session using MBS-specific configuration information.

[0190] Example 16 is the method according to Example 15, wherein the notification for the access control procedure of the MBS session includes an activation notification of the MBS session.

[0191] Example 17 is the method according to Example 16, which executes the access control process of the MBS session by using the MBS-specific configuration information, including: providing an MBS-specific access class prohibition (ACB) parameter as the MBS-specific configuration information, which will be used to trigger the restoration or establishment of the radio resource control (RRC) connection of the MBS session.

[0192] Example 18 is the method according to Example 17, wherein providing the MBS-specific ACB parameter includes: providing access category (AC) and access identification (AI) information of the MBS session ID mapped to the MBS session, and identifying the MBS-specific ACB parameter by the AC and AI information.

[0193] Example 19 is the method according to Example 18, wherein providing the AC and AI information includes: sending the AC and AI information via System Information Block (SIB) broadcast or Non-Access Stratum (NAS) MBS session federation procedure.

[0194] Example 20 is the method according to Example 17, wherein providing the MBS-specific ACB parameter includes: sending an MBS session-specific ACB configuration of an MBS session ID linked to the MBS session, wherein the MBS session-specific ACB configuration identifies the MBS-specific ACB parameter.

[0195] Example 21 is the method according to Example 16, wherein performing the access control process of the MBS session by using the MBS-specific configuration information includes: providing a dedicated RACH configuration for a random access channel (RACH) triggered by the activation notification of the MBS session as the MBS-specific configuration information, the configuration being used for initial access triggered by the activation notification of the MBS session.

[0196] Example 22 is the method according to Example 21, wherein the dedicated RACH configuration includes an MBS-specific backoff parameter indicating the priority of one or more MBS sessions, which is multiplied by a backoff indicator (BI) to determine a delay period for retransmitting the random access preamble.

[0197] Example 23 is the method according to Example 16, wherein the MBS-specific configuration information includes MBS session-specific information to be used during the initial access process triggered by the activation notification of the MBS session.

[0198] Example 24 is the method according to Example 23, wherein the access control process of the MBS session performed by using the MBS-specific configuration information further includes: receiving the reason for accessing the MBS session as information specific to the MBS session, which will be used to restore or establish an RRC connection for the MBS session.

[0199] Example 25 is the method according to Example 23, wherein the access control process of the MBS session executed by using the MBS-specific configuration information further includes: providing a time period for de-prioritizing access to the MBS session as the MBS session-specific information, which will be used to re-access the MBS session after the time period has elapsed.

[0200] Example 26 is the method according to Example 23, wherein the access control process of the MBS session performed by using the MBS-specific configuration information further includes: receiving information about the activated MBS session as the MBS session-specific information via a message notifying the MBS session that the initial access has been completed.

[0201] Example 27 is the method according to Example 26, the method further comprising: after completing the initial access of the MBS session, determining a point-to-multipoint (PTM) or point-to-point (PTP) MBS configuration in RRC connection mode, or performing a handover to the cell that will provide the MBS session.

[0202] Example 28 is an apparatus for a user equipment (UE), the apparatus comprising: one or more processors configured to perform the steps of the method according to any one of Examples 1 to 14.

[0203] Example 29 is an apparatus for a base station, the apparatus comprising: one or more processors configured to perform the steps of the method according to any one of Examples 15 to 27.

[0204] Example 30 is a computer-readable medium having a computer program stored thereon, which, when executed by one or more processors, causes a device to perform the steps of the method according to any one of Examples 1 to 27.

[0205] Example 31 is an apparatus for a communication device, the apparatus including means for performing the steps of the method according to any one of Examples 1 to 27.

[0206] Example 32 is a computer program product comprising a computer program that, when executed by one or more processors, causes a device to perform the steps of the method according to any one of Examples 1 to 27.

[0207] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0208] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters / attributes / aspects, etc., of one implementation in another implementation. For clarity, these parameters / attributes / aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters / attributes / aspects, etc., may be combined with or replace parameters / attributes, etc., of another implementation.

[0209] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0210] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of this disclosure. It should be noted that there are many alternative ways to implement both the processes and apparatus described herein. Therefore, embodiments of this disclosure should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for a user equipment (UE), the method comprising: obtaining a notification for participating in an access control procedure of a multicast / broadcast service (MBS) session, wherein the notification comprises an activation notification of the MBS session; identifying MBS-specific configuration information comprising information specific to the MBS session to be used during an initial access procedure triggered by the activation notification of the MBS session; and participating in the access control procedure of the MBS session by applying the information specific to the MBS session during the initial access procedure.

2. The method of claim 1, further comprising: obtaining MBS-specific access class barring (ACB) parameters; and applying the MBS-specific ACB parameters to trigger a radio resource control (RRC) connection to resume or establish the MBS session.

3. The method of claim 2, wherein obtaining the MBS-specific ACB parameters comprises: obtaining access class (AC) and access identity (AI) information mapped to a MBS session ID of the MBS session; and identifying the MBS-specific ACB parameters from the AC and AI information.

4. The method of claim 3, wherein the AC and AI information are pre-configured in user data of the UE or received via a system information block (SIB) broadcast or a non-access stratum (NAS) MBS session joint procedure.

5. The method of claim 2, wherein obtaining the MBS-specific ACB parameters comprises: receiving MBS session-specific ACB configurations linked to a MBS session ID of the MBS session; and identifying the MBS-specific ACB parameters from the MBS session-specific ACB configurations. the method further comprising: obtaining a plurality of activation notifications corresponding to a respective plurality of MBS sessions, wherein the plurality of activation notifications comprises the notification; simultaneously obtaining a plurality of MBS-specific ACB parameters respectively corresponding to the plurality of MBS sessions, wherein the plurality of MBS-specific ACB parameters comprises the MBS-specific ACB parameters, and selecting the MBS-specific ACB parameters from the plurality of MBS-specific ACB parameters based on a largest or smallest MBS session ID among MBS session identifiers (IDs) in the plurality of MBS sessions, a MBS session ID with a highest QoS requirement, a MBS-specific ACB parameter with a highest priority, or a specific implementation of the UE.

6. The method of claim 2, wherein, 7. The method of claim 2, wherein: the activation notification of the MBS session and an activation notification of a non-MBS session are obtained simultaneously, and obtaining the MBS-specific ACB parameters comprises simultaneously obtaining the MBS-specific ACB parameters and a non-MBS-specific ACB parameter corresponding to the non-MBS session, and prior to applying the MBS-specific ACB parameters, determining to follow the MBS session.

8. The method of claim 1, further comprising: obtaining the activation notification of the MBS session further comprises: obtaining a dedicated random access channel (RACH) configuration of a RACH triggered by the activation notification of the MBS session; and ​ ​ ​ ​ ​ applying the dedicated RACH configuration to an initial access triggered by the activation notification of the MBS session.

9. The method of claim 8, wherein the dedicated RACH configuration comprises an MBS-specific backoff parameter indicating a priority of one or more MBS sessions, and wherein applying the dedicated RACH configuration comprises: determining a delay time period for retransmission of a random access preamble by multiplying the MBS-specific backoff parameter by a backoff indicator, BI; and retransmitting the random access preamble after the delay time period has elapsed.

10. The method of claim 1, wherein applying the information specific to the MBS session comprises: generating a cause for accessing the MBS session in a request to resume or establish an RRC connection as the information specific to the MBS session; and transmitting the request to resume or establish the RRC connection.

11. The method of claim 1, wherein applying the information specific to the MBS session comprises: obtaining a time period for de-prioritizing access to the MBS session as the information specific to the MBS session; and re-accessing the MBS session after the time period has elapsed.

12. The method of claim 1, wherein applying the information specific to the MBS session comprises: generating information about the activated MBS session in a message notifying completion of the initial access of the MBS session as the information specific to the MBS session; and transmitting the message notifying completion of the initial access of the MBS session.

13. A method for a base station, the method comprising: providing a notification of an access control procedure for a multicast / broadcast service (MBS) session, wherein the notification of the access control procedure for the MBS session comprises an activation notification of the MBS session; and performing the access control procedure for the MBS session by using MBS-specific configuration information, wherein the MBS-specific configuration information comprises information specific to the MBS session to be used during an initial access triggered by the activation notification of the MBS session.

14. The method of claim 13, further comprising: providing an MBS-specific access class barring (ACB) parameter to be used for triggering a radio resource control (RRC) connection resume or establishment of the MBS session.

15. The method of claim 14, wherein providing the MBS-specific ACB parameter comprises: providing an access category (AC) and access identity (AI) information mapped to an MBS session ID of the MBS session, the AC and AI information identifying the MBS-specific ACB parameter.

16. The method of claim 15, wherein providing the AC and AI information comprises: sending the AC and AI information via a system information block (SIB) broadcast or a non-access stratum (NAS) MBS session joint procedure.

17. The method of claim 14, wherein providing the MBS-specific ACB parameter comprises: transmitting an MBS session specific ACB configuration linked to an MBS session ID of the MBS session, the MBS session specific ACB configuration identifying the MBS specific ACB parameters.

18. The method of claim 13, further comprising: providing a dedicated random access channel (RACH) configuration of a RACH triggered by the activation notification of the MBS session, which is to be used for an initial access triggered by the activation notification of the MBS session.

19. The method of claim 18, wherein the dedicated RACH configuration comprises an MBS specific backoff parameter indicating a priority of one or more MBS sessions, which is to be multiplied by a backoff indicator (BI) to determine a delay time period for retransmission of a random access preamble.

20. The method of claim 13, wherein performing the access control procedure of the MBS session by using the MBS specific configuration information further comprises: receiving a cause for accessing the MBS session as the information specific to the MBS session, which is to be used for resuming or establishing an RRC connection of the MBS session.

21. The method of claim 13, wherein performing the access control procedure of the MBS session by using the MBS specific configuration information further comprises: providing a time period for de-prioritizing an access to the MBS session as the information specific to the MBS session, which is to be used for re-accessing the MBS session after the time period has elapsed.

22. The method of claim 21, wherein performing the access control procedure of the MBS session by using the MBS specific configuration information further comprises: receiving information about an activated MBS session via a message notifying completion of the initial access of the MBS session as the information specific to the MBS session.

23. The method of claim 22, further comprising: determining a point-to-multipoint (PTM) or point-to-point (PTP) MBS configuration in an RRC connected mode or performing a handover to a cell that is to provide the MBS session upon completion of the initial access of the MBS session.

Images