State update for multicast and broadcast services (MBS)

Abstract

This disclosure provides systems, methods, and apparatus, including computer programs encoded on a computer readable medium, for causing an application processor (AP) (160) of a user equipment (EU) (150) to communicate with a modem (170) of the UE (150) to set and update a state of a multicast and broadcast service (MBS). The AP (160) may send (109) a first attention (AT) command that includes an MBS session state setting that controls MBS session state reporting for the MBS session. The modem (170) may send (127) a second AT command including an MBS session status report. The second AT command may be an unsolicited AT command. The modem (170) may send (127) a second AT command when it detects a change in one or more parameters of the MBS session. The one or more parameters of the MBS session status report may include MBS decisions and MBS rejection causes.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and multicast and broadcast services (MBS). Background Art

[0002] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent that it is described in this background section, and aspects of the specification that otherwise may not be considered prior art at the time of filing, are neither explicitly nor implicitly admitted to be prior art to the present disclosure.

[0003] A wireless communication system may support multicast and broadcast services (MBS). MBS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients, either to all users in a broadcast service area, or to users who have joined a specific multicast group. The corresponding types of MBS sessions are: broadcast MBS sessions and multicast MBS sessions. For both types of MBS sessions, MBS service data is transmitted via an associated protocol data unit (PDU) session between a user equipment (UE) of a wireless communication session and a data network (DN). A PDU session defines an end-to-end user plane connection between a UE and a DN. The UE coordinates with a network entity (such as a base station or a core network) to manage and configure PDU sessions associated with services of the wireless communication system. The 3rd Generation Partnership Project (3GPP) standards body has described MBS in technical specifications (such as Technical Specification (TS) 27.007) incorporated herein by reference. Traditional techniques for transmitting or updating the state of a PDU session are insufficient to support new features associated with UEs utilizing MBS. Summary of the invention

[0004] The systems, methods and devices of the present disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] The present disclosure includes various examples of transmitting and updating the state of a multicast and broadcast service (MBS) session. In some implementations, a user equipment (UE) reconfigures an existing protocol data unit (PDU) session to support MBS. In some implementations, the UE establishes a new PDU session for MBS. A PDU session supporting MBS may be referred to as an MBS PDU session.

[0006] In some implementations, the UE includes an application processor (AP) and a modem. The AP may send a first attention (AT) command including an MBS session state setting to the modem, the MBS session state setting controlling an MBS session state report for an MBS session. The first AT command may be a set AT command, such as an MBS session state report (+CMSSR=) command. The modem may send a second AT command, such as a +CMSSRI command, to the AP, the second AT command including an MBS session state report. In some implementations, the second AT command is an unsolicited AT command that the modem sends to the AP when it detects a change in the MBS session state of the MBS session.

[0007] One innovative aspect of the subject matter described in the present disclosure may be implemented as a method for managing an MBS PDU session by a UE. The method includes transmitting a first AT command indicating an MBS session state setting for an MBS session to a modem of the UE from an AP of the UE, and receiving a second AT command including an MBS session state report for the MBS session from the modem.

[0008] Another innovative aspect of the subject matter described in the present disclosure can be implemented as a method for managing an MBS PDU session by a UE. The method includes receiving, at a modem of the UE, from an AP of the UE, a first AT command indicating an MBS session state setting for the MBS session, and transmitting, from the modem to the AP, a second AT command including an MBS session state report for the MBS session.

[0009] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will be apparent from the detailed description, drawings, and claims. Note that the relative sizes of the following drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 An example message flow is shown for a UE to join an MBS session over an existing PDU session, where an AP turns on MBS status updates and receives MBS status updates from a modem, according to some implementations.

[0011] Figure 2 Example message flows are shown for a UE to establish a new PDU session supporting one or more MBS sessions and for an AP to turn on MBS status updates and receive MBS status updates from a modem in accordance with some implementations.

[0012] Figure 3Example message flows are shown for a UE to join an MBS session over an existing PDU session but the network rejects the MBS join request and the AP receives an MBS status update from a modem in accordance with some implementations.

[0013] Figure 4A Example message flows are shown for a UE to join an MBS session and establish a new PDU session supporting one or more MBS sessions, but the network rejects the MBS join request and the AP receives an MBS status update from a modem, according to some implementations.

[0014] Figure 4B Another example message flow is shown for a UE to join an MBS session and establish a new PDU session supporting one or more MBS sessions, but the network rejects the MBS join request and the AP receives an MBS status update from a modem, according to some implementations.

[0015] Figure 5 An example message flow is shown in which the network updates MBS parameters and the AP receives MBS status updates from a modem according to some implementations.

[0016] Figure 6 An example message flow is shown in which the network removes a UE from an MBS session and the AP receives an MBS status update from a modem in accordance with some implementations.

[0017] Figure 7 Example AT commands for MBS session status reporting according to some implementations are shown.

[0018] Figure 8 Example AT commands for setting up or defining an MBS PDU session according to some implementations are shown.

[0019] Fig. 9 Example AT commands are shown for both setting up or defining an MBS session context for an MBS PDU session and triggering a PDU session modification procedure according to some implementations.

[0020] Fig.10 An example AT command for querying the status of an active MBS PDU session according to some implementations is shown.

[0021] Fig.11 An example AT command for querying the status of an active MBS PDU session according to some implementations is shown.

[0022] Fig.12 An example implementation of a UE is shown.

[0023] Fig.13 An example implementation of a network is shown.

[0024] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0025] Multicast and Broadcast Service (MBS) is transmitted via associated protocol data unit (PDU) sessions. A user equipment (UE) (also referred to as a terminal equipment (TE)) can join or exit an MBS session of an MBS. In some implementations, the UE modifies an existing PDU session or establishes a new PDU session supporting MBS. A PDU session supporting MBS may be referred to as an MBS PDU session. A UE may join one or more MBS sessions via an MBS PDU session. In some implementations, commands between an application processor (AP) of the UE and a modem are used to transmit status updates of the MBS session regarding the MBS PDU session. The AP of the UE may configure status update settings and provide status updates or status reports of the MBS session by providing an attention (AT) command to the modem of the UE. The modem of the UE may coordinate with a network entity to manage the MBS PDU session.

[0026] If the MBS session is multicast, the service announcement (on the application layer) may include the data network name (DNN) and network slice selection assistance information (S-NSSAI) of the PDU session to indicate which PDU session should be associated with the MBS. MBS service related information (such as the default public land mobile network identifier (PLMN ID), DNN and S-NSSAI) may also be pre-configured in the UE.

[0027] If there is an existing PDU session available for the UE to use to send a join request for the MBS session, the UE sends a PDU session modification request through the PDU session. If the UE does not have a suitable PDU session established for the MBS session using the DNN and S-NSSAI, the UE joins the MBS session by sending a PDU session establishment request requesting establishment of an associated PDU session together with one or several MBS session IDs and a join request, as further described below.

[0028] The UE or the network may request to exit an MBS session. When the UE determines to exit a multicast MBS session, the UE sends a PDU Session Modification Request to notify the core network (such as a network entity of the 5G Core Network (5GC)) of the exit operation. When the network determines to remove the UE from the MBS session, a core network component (such as a Session Management Function (SMF)) initiates a PDU Session Modification procedure (e.g., sends a PDU Session Modification Command) to notify the UE of the MBS session release.

[0029] MBS sessions may be location dependent. For local multicast services, MBS service area information is provided to the UE. The UE may have information about the local multicast service including the MBS service area via a service announcement on the application layer. If the UE determines (based on information about the local multicast service such as obtained via a service announcement) that it is located in the MBS service area, the UE sends a PDU Session Modification Request (with the MBS Session ID) or a PDU Session Establishment Request (with the MBS Session ID) to join the multicast group.

[0030] The requested MBS container information element (IE) (as shown in Table 1) is used for the UE to request to join or exit one or more MBS sessions in a PDU session establishment request message or a PDU session modification request message. Table 1 Table 2

[0031] As shown in Table 2, the main parameters are: "MBS session ID type" and "MBS operation". "MBS session ID type" can be "temporary mobile group identity (TMGI)", "source-specific IP multicast address for IPv4" or "source-specific IP multicast address for IPv6". "MBS operation" can be "join MBS session" or "exit MBS session".

[0032] As shown in Table 3, the network indicates the information of the MBS session to the UE using the received MBS container information element. Table 3 Table 4

[0033] As shown in Table 4, the "MBS Decision (MD)" parameter can be set to "MBS Service Area Update", "Accept MBS Join", "Reject MBS Join", or remove the UE from the MBS session. The rejection reason is set to the reason when the MD is set to "Reject MBS Join" or "Remove UE from MBS Session". "MBS Service Area" is set to the service area in which the MBS service is applicable. This parameter may contain an MBS TAI list, an NR CGI list, or both that identify the service area of ​​the local MBS service. "MBS Timer" is used to indicate the back-off timer for joining the MBS session or the start time of the MBS session. "MBS Security Container" includes an MBS service key identifier, an MBS service key (MSK), an MBS business key identifier (MTK ID), and an encrypted MBS business key (encrypted MTK).

[0034] As mentioned earlier, the present disclosure includes various examples of transmitting and updating the status of an MBS.

[0035] In some aspects, a command between an AP and a modem of a UE is used to configure an MBS session state update or provide an MBS session state update about one or more MBS sessions supported by an MBS PDU session. The AP may send a first AT command including an MBS session state setting that controls an MBS session state update (which may be referred to as an MBS session state report) for an MBS session. In some implementations, the first AT command may be a set AT command sent from the AP to the modem, such as an MBS session state report (+CMSSR=) command. The MBS session state setting may enable or disable an MBS session state report from the modem.

[0036] In some aspects, the modem sends a second AT command including an MBS session status report, such as a +CMSSRI command. The modem may determine whether to send the second AT command to the AP depending on the MBS session status setting. In some implementations, the second AT command is an unsolicited AT command including an MBS session status report. In some implementations, the modem sends the second AT command when it detects a change in one or more parameters indicating the MBS session state of the MBS session. In some implementations, one or more parameters of the MBS session status report include an MBS decision (MBS_decision) and an MBS rejection reason (MBS_reject_cause). The MBS decision may indicate a network decision that affects the MBS session. For example, the MBS decision may indicate whether to accept an MBS join request, reject an MBS join request, or remove the UE from the MBS session. The MBS rejection reason may indicate a reason for rejecting the MBS session or a reason for removing the UE from the MBS session. In some implementations, one or more parameters of the MBS session status report include a context identifier (CID), a temporary mobile group identifier (TMGI), an MBS decision (MBS_decision), an MBS rejection cause (MBS_reject_cause), an MBS tracking area identifier list (MBS_TAI_list), an MBS cell global identifier list (MBS_CGI_list), a source IP address (Source_IP), a destination address (Destination_IP), an MBS start time (MBS_Start_Time), an MBS timer (MBS_timer), an MBS service key identifier (MSK_ID), an MBS service key (MSK), an MBS traffic key identifier (MTK_ID), and an encrypted MBS traffic key (Enc_MTK).

[0037] Figure 1 An example message flow for enabling a UE to join an MBS session over an existing PDU session according to some implementations is shown, wherein the AP turns on MBS status updates and receives status updates from a modem. Figure 1 As shown, UE 150 includes AP 160 and modem 170. MBS application is running on the AP side, and the protocol (e.g., 3GPP non-access stratum (NAS) protocol) for configuring MBS session operation and parameter exchange is implemented on the modem side. The interface between AP 160 and modem 170 implements MBS service. For example, the interface includes a physical interface and / or a software interface. The physical interface may include a peripheral component interconnect express (PCIe), a shared memory, or a universal serial bus (USB), and the software interface may be a remote procedure call (RPC) interface or an AT command interface. Figures 2 to 6 Similar interfaces supporting MBS services may be implemented in . In some implementations, client software runs on AP 160 and server software runs on modem 170 to enable communication between AP 160 and modem 170 via an interface (eg, commands described below).

[0038] like Figure 1 As shown, a PDU session suitable for an MBS service is established 103. An MBS application starts 106, and the AP 160 turns on or enables 109 an MBS session status update from the modem 170. The MBS status update may also be referred to as an MBS session status report. In some implementations, the AP 160 enables MBS session status updates or reports by transmitting an AT command including an MBS session status setting to the modem 170. The AT command may be a set AT command sent from the AP 160 to the modem 170, such as an MBS session status report (+CMSSR=) command. The MBS session status setting controls MBS status reporting for an MBS session. In some implementations, the MBS session status setting enables or disables MBS status reporting for an MBS session. For example, the MBS session status setting may include parameters that may be set by the AP 160 for enabling or disabling MBS status reporting.

[0039] The AP 160 then checks whether a suitable PDU session is established. To check whether a suitable PDU session exists, the AP 160 may read the DNN and S-NSSAI of all existing PDU sessions (such as through a +CGCONTRDP command) and determine whether the DNN and S-NSSAI match the desired settings for the MBS session. If a suitable PDU session exists, the AP 160 may send 114 an AT command (such as a +CMSCONT command) to the modem 170 to define or set an MBS session context including an MBS session operation (i.e., join an MBS session). For example, the +CMSCONT command may be a set AT command, such as a +CMSCONT= command. The AT command may include a CID identifying the PDU session, an MBS session ID, and an MBS operation. The set AT command may also include an MBS session ID type. In some implementations, the modem 170 responds with an "OK" response message (not shown). For example, the AP 160 may wait for the OK response message before continuing with the next AT command. The AP 160 triggers the PDU session modification process by transmitting 115 an AT command (such as a +CGCMOD command) to the modem 170. The modem 170 may request 118 to join the MBS session via a NAS message (such as a PDU session modification request message). The network accepts 121 the MBS join request and returns a PDU session modification command message indicating that the MBS join request is accepted. In some implementations, the modem 170 sends 126 a response message to the PDU session modification process to the AP 160. For example, the response message may be an AT command, such as a +CGEV command, for indicating the result of the MBS join session. In some implementations, the response message shown in element 126 is optional. In some implementations, the AP 160 waits for an OK message (not shown) before proceeding to the next step.

[0040] After the PDU session modification procedure is completed, the modem 170 sends 127 an AT command, such as a +CMSSRI command, including an MBS session status update, which may also be referred to as an MBS session status report. In some implementations, the AT command is an unsolicited AT command including an MBS session status report. The modem 170 may send the AT command when the modem 170 detects a change in one or more parameters indicating the MBS session state of the MBS session. In some implementations, one or more parameters of the MBS session status report include an MBS decision (MBS_decision) and an MBS rejection cause (MBS_reject_cause). The MBS decision may indicate a network decision affecting the MBS session. For example, the MBS decision may indicate whether to accept an MBS join request, reject an MBS join request, or remove the UE 150 from the MBS session. The MBS rejection cause may indicate a reason for rejecting the MBS session or a reason for removing the UE 150 from the MBS session. In some implementations, the one or more parameters of the MBS session status report include one or more of the following: a context identifier (CID), a temporary mobile group identifier (TMGI), an MBS decision (MBS_decision), an MBS rejection cause (MBS_reject_cause), an MBS tracking area identifier list (MBS_TAI_list), an MBS cell global identifier list (MBS_CGI_list), a source IP address (Source_IP), a destination address (Destination_IP), an MBS start time (MBS_Start_Time), an MBS timer (MBS_timer), an MBS service key identifier (MSK_ID), an MBS service key (MSK), an MBS traffic key identifier (MTK_ID), and an encrypted MBS traffic key (Enc_MTK), as described below with reference to Figure 7 Further described.

[0041] As previously described, the MBS session status setting controls whether the MBS session status report is enabled or disabled. In some implementations, the modem 170 checks whether the MBS session status report is enabled before sending the AT command. If the MBS session status report is enabled, the modem 170 may send an AT command including the MBS session status report. If the MBS status report is disabled, the modem 170 does not send the MBS session status report. The MBS session may continue 129 via the MBS PDU session.

[0042] Figure 2An example message flow is shown for UE 250 to establish a new PDU session supporting an MBS session and AP 260 to turn on MBS status updates and receive status updates from modem 270 according to some implementations. Figure 2 In the example of , the MBS application starts 206 and then checks whether a suitable PDU session is established. When the MBS application starts, the AP 260 may determine that there is no suitable PDU session. Figure 2 Similar to element 109 of , AP 260 may turn on or enable 209 MBS session status updates (or MBS session status reports) from modem 270. AP 260 configures the appropriate PDU session by sending 213 an AT command to modem 370, such as a +CGDCONT= command indicating the CID of the MBS session and the corresponding DNN and S-NSSAI. Figure 1 Similar to element 114 in , AP 260 may then send an AT command (such as a +CMSCONT command) to modem 270 to define or set an MBS session context including MBS session operations (ie, joining an MBS session).

[0043] After the parameters for PDU session establishment and MBS PDU session are configured, AP 260 triggers the PDU session establishment process of the MBS PDU session by transmitting an AT command (such as a +CGACT command) to the modem 270. The modem 270 may send 218 a PDU session establishment request message to the network 280 to complete the PDU session establishment process and request to join the MBS session. The network 280 accepts the MBS join request and returns 221 a PDU session establishment accept message indicating that the MBS join request is accepted. In some implementations, the modem 270 sends 226 a response message to the AP 260 for the PDU session establishment process. For example, the response message may be an AT command, such as a +CGEV command, for indicating the result of the MBS join session. In some implementations, the response message shown in element 226 is optional. Figure 1 Similar to element 127 of , after receiving an indication that the MBS join request was accepted during the PDU session establishment process, the modem 270 sends 227 an AT command including an MBS session status update, such as a +CMSSRI command, which may also be referred to as an MBS session status report. The MBS session may continue 229 via the MBS PDU session.

[0044] Figure 3An example message flow is shown for UE 350 to join an MBS session over an existing PDU session but the network rejects the MBS join request and AP 360 receives an MBS status update from modem 370 in accordance with some implementations. Figure 3 Elements 314 to 318 of Figure 1 The corresponding elements 124 to 118 are similar. Figure 3 As shown, the network 380 may reject the MBS join request by sending 319 a PDU session modification command message indicating that the MBS join request is rejected. The network 380 may reject the MBS join request based on conditions such as: when the UE 350 is not within the service area, when the UE 350 is not authorized / has no subscription, when the MBS service has not been started or is otherwise unavailable, or due to congestion control / resource limitations, among other examples. In some implementations, the modem 370 sends 326 an AT command (such as a +CGEV command) as a response message indicating the result of the MBS join session. In some implementations, the response message shown in element 326 is optional. Figure 1 127, the modem 370 may send 327 an AT command including an MBS session state update, such as a +CMSSRI command, to the AP 360, which may also be referred to as an MBS session state report. In some implementations, in the MBS session state report, the AP 360 receives an indication of the failure cause, the MBS start time, the back-off timer, and / or the MBS service area information from the modem 370. The AP 360 may proceed 328 with an MBS application determination or reaction associated with the MBS PDU session.

[0045] Figure 4A An example message flow is shown for UE 450 to join an MBS session and establish a new PDU session supporting the MBS session, but network 480 rejects the MBS join request and AP 460 receives an MBS status update from modem 470, according to some implementations. Figure 4A Elements 406 to 418 of Figure 2 The elements 206 to 218 have similar counterparts. Figure 4A In the example depicted in , the network 480 may reject the MBS join request by transmitting 420 a PDU session setup accept message. The network 480 may reject the MBS join request based on conditions such as when the UE 450 is not within the service area, when the UE 450 is not authorized / has no subscription, when the MBS service has not been started or is otherwise unavailable, or due to congestion control / resource limitations, among other examples. Figure 4AIn the example of , the network 480 can establish a PDU session while concurrently rejecting the MBS join request. In some implementations, the modem 470 sends 426 an AT command (such as a +CGEV command) as a response message indicating the result of the MBS join session. In some implementations, the response message shown in element 426 is optional. Figure 1 Similar to element 127 of , modem 470 may send 427 an AT command including an MBS session state update, such as a +CMSSRI command, to AP 460, which may also be referred to as an MBS session state report. AP 460 may proceed 428 with an MBS application determination or reaction associated with the MBS PDU session.

[0046] Figure 4B Another example message flow is shown for UE 450 to join an MBS session and establish a new PDU session supporting the MBS session, but network 480 rejects the MBS join request and AP 460 receives an MBS status update from modem 470 in accordance with some implementations. Figure 4B Elements 406 to 418 of Figure 2 4. In this case, the network 480 may determine that the PDU session establishment is unnecessary and therefore reject the PDU session establishment by sending 422 a PDU session establishment reject message to the modem 470. In some implementations, the network 480 includes the received MBS container information element indicating the failure reason, MBS start time, back-off timer, and / or MBS service area information to the UE 450. The AP 460 may proceed 428 with an MBS application determination or reaction associated with the MBS PDU session.

[0047] Figure 5 An example message flow is shown in which the network 580 updates MBS parameters and the AP 560 of the UE 550 receives the MBS status update from the modem 570 according to some implementations. Figure 5 Elements 506 to 509 and their Figure 1 The corresponding elements 106 to 109 of are similar. UE 550 may join 510 an MBS session via an existing PDU session supporting one or more MBS sessions. Figure 55, the network 580 updates the MBS parameters of the active MBS session. The network 580 updates 511 MBS session parameters, such as service area or security information. The network 580 may perform a PDU session modification procedure. For example, the network 580 may send 523 a PDU session modification command to indicate the updated parameters to the modem 570. The modem 570 may respond to the PDU session modification command by transmitting 526 a PDU session modification complete message. Figure 1 Similar to element 127 of , after the PDU session modification process is completed, the modem 570 may send 527 an AT command including an MBS session state update, such as a +CMSSRI command, to the AP 560, which may also be referred to as an MBS session state report. The AP 560 receives the MBS session state report, which includes an indication of updated parameters from the modem 570, such updates being related to the MBS service area and / or security information. The AP 560 may proceed 528 with an MBS application determination or reaction associated with the MBS PDU session.

[0048] Figure 6 An example message flow is shown in which a network 680 removes a UE from an MBS session and an AP 660 of a UE 650 receives an MBS status update from a modem 670 in accordance with some implementations. Figure 6 Elements 606 to 609 and their Figure 1 The elements 106 to 109 of UE 650 are similar in their counterparts. UE 650 may join 610 an MBS session via an existing PDU session supporting one or more MBS sessions. Figure 6 , the network 680 removes 612 the UE 650 from the MBS session. The network 680 may remove the MBS session based on conditions such as the UE 650 being outside of an MBS service area, the MBS session being terminated, the UE subscription expiring / ending, or congestion control / resource limitations, among other examples. For example, the network 680 may determine to remove the UE from the MBS session, such as because the UE 650 is outside of a service area, a subscription is updated, or the MBS session is released, among other reasons. The network 680 may trigger the PDU session modification procedure by sending 624 a PDU session modification command including an indication of the removal decision and optionally with a cause and / or updated parameters, such as an MBS service area and an MBS session start time. The modem 670 may respond to the PDU session modification command by transmitting 626 a PDU session modification complete message. Figure 1Similar to element 127 of , after the PDU session modification procedure is completed, the modem 670 may send 627 an AT command including an MBS session state update, such as a +CMSSRI command, to the AP 660, which may also be referred to as an MBS session state report. The AP 660 receives the MBS session state report, which includes an indication of the MBS session state (e.g., inactive state) from the modem 670 and optionally has a cause and / or updated parameters (such as MBS service area, MBS session start time, and backoff timer). The AP 660 may proceed 628 with an MBS application determination or reaction associated with the MBS PDU session.

[0049] although FIG. 4A to FIG. 7 Not shown in FIG, but some implementations of the protocol between the modem and the AP may include additional messages. For example, when the modification process is successful (such as in Figure 3 Element 318 of ) or the PDU session establishment process is successful (such as in Figure 4A ), the modem may send an "OK" command indicating the result of the PDU session. Additionally or alternatively, the modem may send a command (such as an AT + CGEV command) to indicate the result of the rejected MBS join request. In some implementations, the OK command for the PDU session is located before or after the + CGEV command. In some implementations, the OK message (from the modem or the AP) is used as an acknowledgement in response to receiving the command (from the other of the modem or the AP). In some implementations, the status update command is acknowledged by the OK command.

[0050] Figure 7 An example AT command for MBS session status reporting and having a +CMSSR command syntax 730 is shown according to some implementations. The +CMSSR= command 709 can be a set AT command that is sent from the AP to the modem to control MBS session status reporting for an MBS session. The +CMSSR= command 709 includes an MBS session status setting that enables or disables MBS session status reporting from the modem. For example, the MBS session status setting can include a parameter n that can be set to 0 to disable MBS session status reporting or set to 1 to enable MBS session status reporting. If an error occurs when configuring the MBS session status setting, an error response message, such as a +CME ERROR message 731, can be received from the modem. The +CME ERROR message 731 can include one or more error (err) values ​​to indicate one or more types of errors.

[0051] The +CMSSRI command 727 is an AT command that includes an MBS session status report for an MBS session. The modem determines whether to send the +CMSSRI command 727 to the AP depending on whether the MBS session status setting is enabled or disabled (as described above). In some implementations, the +CMSSRI command 727 is an unsolicited AT command that includes an MBS session status report. The modem may send the +CMSSRI command 727 when it detects a change in one or more parameters indicating the MBS session status of the MBS session. In some implementations, one or more parameters of the MBS session status report include an MBS decision (MBS_decision) and an MBS rejection cause (MBS_reject_cause). The MBS decision may indicate a network decision that affects the MBS session. For example, the MBS decision may indicate (0) an MBS service area update, (1) accepting an MBS join request, (2) rejecting an MBS join request, or (3) removing the UE from the MBS session. The MBS rejection cause may indicate a reason for rejecting the MBS session or a reason for removing the UE from the MBS session. For example, the MBS rejection reason may indicate (0) no additional information is provided, (1) insufficient resources, (2) the user is not authorized to use the MBS service, (3) the MBS session has not been started or will not start soon, (4) the user is outside the local MBS service area, (5) the session context is not found, or (6) the MBS session is released.

[0052] In some implementations, one or more parameters of the MBS session status report include one or more of the following: a context identifier (CID), a temporary mobile group identifier (TMGI), an MBS decision (MBS_decision), an MBS rejection cause (MBS_reject_cause), an MBS tracking area identifier list (MBS_TAI_list), an MBS cell global identifier list (MBS_CGI_list), a source IP address (Source_IP), a destination address (Destination_IP), an MBS start time (MBS_Start_Time), an MBS timer (MBS_timer), an MBS service key identifier (MSK_ID), an MBS service key (MSK), an MBS traffic key identifier (MTK_ID), and an encrypted MBS traffic key (Enc_MTK).

[0053] The +CMSSRI? command 732 may be a read AT command that requests the current value of the MBS session state setting (or parameter n) for the MBS session. The modem may respond with a response message 733 indicating the current value of the MBS session state setting (or parameter n). The +CMSSRI=? command 734 may be a test AT command that requests a list of supported values ​​for the MBS session state setting (such as supported values ​​for parameter n). The modem may respond with a response message 735 indicating a list of supported values ​​for the MBS session state setting (such as supported values ​​for parameter n).

[0054] Figures 8 to 11 Examples of interface commands (referred to as attention or AT commands) are included. Example AT commands may be used by a UE's AP to communicate with the UE's modem.

[0055] exist Figure 8 In some implementations, an example AT command has a +CMSCONT command syntax 840 that can define or set an MBS PDU session. The +CMSCONT= command 814 is a configured AT command for defining or setting an MBS session context for an MBS PDU session. Figure 8 As shown, the +CMSCONT= command 814 includes various parameters for the MBS PDU session, including CID, MBS session ID, MBS session ID type, and MBS operation. If an error occurs when setting or defining the MBS session context, an error response message such as a +CME ERROR message 839 may be received from the modem. The +CME ERROR message 839 may include one or more error (err) values ​​indicating one or more types of errors. The +CMSCONT? command 841 is a read AT command used to read the currently set parameters of one or more MBS sessions. Figure 8 As shown, the modem may respond to a +CMSCONT? command 841 received from the AP by sending a response message 842 including various parameters of the current settings for one or more MBS sessions.

[0056] In some implementations, the CID field of the +CMSCONT= command 814 indicates a quality of service (QoS) flow definition, an evolved packet system (EPS) service flow definition, and a packet data protocol (PDP) context definition. In some implementations, the MBS session ID field of the +CMSCONT= command 814 indicates an MBS session ID of an Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) multicast address, the multicast address having a format including source_IP_address and destination_IP_address. In some implementations, the MBS session ID type field of the +CMSCONT= command 814 is filled with a first value indicating a temporary mobile group identity (TMGI), a second value indicating a source specific IP multicast address of IPv4, or a third value indicating a source specific IP multicast address of IPv6. In some implementations, the MBS operation field of the +CMSCONT= command 814 is filled with a first value indicating joining an MBS PDU session or a second value indicating exiting an MBS PDU session.

[0057] +CMSCONT=? command 843 is a test AT command used to request the modem to return the range of supported parameters (for MBS PDU sessions) as a composite value. Figure 8 As shown, the modem may respond to the +CMSCONT=? command 843 received from the AP by sending a response message 844 including a range of supported parameters for the MBS PDU session.

[0058] exist Fig. 9 , an example AT command with a +CMOP command syntax 945 is shown according to some implementations, which +CMOP command syntax can define or set the MBS session context of the MBS PDU session and trigger the PDU session modification procedure. Fig. 9 As shown, the +CMOP= command 946 includes various parameters for the MBS PDU session, including CID, MBS session ID, MBS session ID type, and MBS operation. If an error occurs when setting or defining the MBS session context, an error response message such as a +CME ERROR message 947 may be received from the modem. The +CME ERROR message 947 may include one or more error (err) values ​​indicating one or more types of errors. The +CMOP? command 948 is a read AT command used to read the currently set parameters of one or more MBS sessions. Fig. 9As shown, the modem may respond to a CMOP? command 948 received from the AP by sending a response message 949 including various parameters of the current settings for one or more MBS sessions.

[0059] exist Fig.10 , an example AT command with a +CMSRDP command syntax 1051 is shown according to some implementations, which can query the status of one or more active MBS sessions. Fig.10 As shown, the query command may be an execution AT command to read dynamic parameters of one or more MBS sessions, such as +CMSRDP= command 1052. +CMSRDP= command 1052 may include the CID of the MBS PDU session to identify the specific MBS PDU session. In some implementations, the dynamic parameters may include CID, TMGI, MBS_TAI_list, MBS_CGI_list, Source_IP, Destination_IP, MBS_Start_Time, MBS_residual_timer, MSK, MSK_ID, MTK_ID, and Enc_MTK. Fig.10 As shown, the modem may respond to the +CMSRDP= command 1052 received from the AP by sending a response message 1053 including various dynamic parameters for one or more active MBS sessions associated with the CID.

[0060] exist Fig.11 , an example AT command with a +CMSRDP command syntax 1155 is shown according to some implementations, which can query the status of one or more active MBS sessions. Fig.11 As shown, the query command may be an execution AT command to read dynamic parameters of one or more MBS sessions, such as +CMSRDP= command 1152. +CMSRDP= command 1152 may include the CID of the MBS PDU session to identify the specific MBS PDU session. In some implementations, the dynamic parameters may include CID, TMGI, MBS_TAI_list, MBS_CGI_list, Source_IP, Destination_IP, MSK, MSK_ID, MTK_ID, and Enc_MTK. Fig.11As shown, the modem may respond to the +CMSRDP= command 1152 received from the AP by sending a response message 1153 including various dynamic parameters of one or more active MBS sessions associated with the CID. The +CMSRDP=? command 1156 is a test AT command that is used to request the modem to return a list of CIDs associated with one or more active MBS PDU sessions. Fig.11 As shown, the modem may respond to a +CMSRDP=? command 1156 received from the AP by sending a response message 1158 including a list of CIDs associated with one or more active MBS PDU sessions.

[0061] Fig.12 1260 and a modem 1270, which may be the UE 1250 described above. Figures 1 to 6 1270. The modem 1270 includes a processor 1271, an MBS RRC controller 1274, an MBS NAS controller 1276, and an interface controller 1278. The processor 1271 processes data to be transmitted by the UE 1250 in the uplink direction, or processes data received by the UE 1250 in the downlink direction. The MBS Radio Resource Controller (RRC) controller 1274 can be configured to support RRC configuration, procedures, and messaging associated with the MBS process, and / or support necessary operations. The MBS NAS controller 1276 can be configured to support NAS configuration, procedures, and messaging associated with the MBS process, and / or support necessary operations. The interface controller 1278 manages the transmission of messages (e.g., AT commands and / or RPC function calls) exchanged between the modem 1270 and the AP 1260.

[0062] AP 1260 includes a processor 1261, an interface controller 1268, and an MBS application 1265. Processor 1261 is configured to run an operating system (e.g., Android, iOS, Windows, or Linux). Interface controller 1268 manages the transmission of messages (e.g., AT commands and / or RPC function calls) exchanged between modem 1270 and AP 1260. Interface controller 1268 may run on processor 1261. MBS application 1265 is configured to receive one or more MBS services. For example, MBS application 1265 includes an IP streaming application or a software update application.

[0063] In some implementations, the modem 1270 may be referred to as a terminal adapter (TA) and the AP 1260 may be referred to as terminal equipment (TE).

[0064] Fig.13 13 is an example network including a UE 1350, a next generation NodeB or gNodeB (gNB) 1385, and a user plane function (UPF) 1388, which may be an implementation of the above Figures 1 to 12 An example network with the features described in . Figures 1 to 7 The PDU session 1390 is established as described above. As previously described, the PDU session 1390 supporting MBS may be referred to as an MBS PDU session. The PDU session 1390 may be implemented across the UE 1350, gNB 1385, and UPF 1388 via one or more data radio bearers (DRBs) between the UE 1350 and the gNB 1385 (such as DRB 1396 and DRB 1397) and the GTP-U tunnel 1398 between the gNB 1385 and the UPF 1388. The PDU session 1390 also includes one or more quality of service (QoS) flows, such as QoS flows 1391 to 1393. The MBS supported by the PDU session 1390 is also supported by the QoS flows 1391 to 1393, DRB 1396, DRB 1397, and GTP-U tunnel 1398. The MBS PDU session may support various MBS applications, such as IP streaming applications, Voice over IP (VoIP) applications, and software update applications, among others.

[0065] The following additional considerations apply to the present disclosure.

[0066] Example AT commands described in this article include: • +CMSCONT: defines the MBS session context +CMSCONT, please refer to Figure 8 . • +CGCMOD: PDP context modification +CGCMOD. • +CGEV: Used to indicate the bearer operation status. • +CMSRDP: MBS session reads dynamic parameters +CMSRDP, please refer to Fig.10 and Fig.11 . • +CMOP: MBS session operation +CMOP, please refer to Fig. 9 . • +CGACT: PDP context activation or deactivation +CGACT.

[0067] Although the above-mentioned AT commands are used as examples to explain the present disclosure, it should be noted that these examples can be applied to other interfaces, such as a remote procedure call (RPC) interface. For example, the AT command sent by the AP to the modem can be replaced by one or more RPC function calls, and the parameters (i.e., arguments) of the AT command are the arguments of the one or more RPC function calls. The return result in the response of the AT command is the return result of the one or more RPC function calls. In another example, two or more AT commands can be combined into a single RPC function call, and the parameters (i.e., arguments) of the AT command are the arguments of the RPC function call. The return result in the response of the AT command is the return result of the RPC function call.

[0068] Figures 1 to 13 The operations described herein are examples intended to aid in understanding example implementations and should not be used to limit potential implementations or to limit the scope of the claims. Some implementations may perform additional operations, fewer operations, perform operations in parallel or in a different order, and perform some operations in a different manner.

[0069] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the various aspects to the precise form disclosed. In view of the above disclosure, modifications and changes may be made, or modifications and changes may be obtained from the practice of various aspects. Although various aspects of the present disclosure have been described with respect to various examples, any combination of various aspects from any one of the examples is also within the scope of the present disclosure. The examples in the present disclosure are provided for teaching purposes only. Alternatively, or in addition to other examples described herein, the examples also include any combination of the following implementation options (listed as clauses for clarity). Terms

[0070] Clause 1. A method for managing an MBS PDU session by a UE, comprising: transmitting, from an AP of the UE to a modem of the UE, a first AT command indicating an MBS session state setting for an MBS session; and receiving, from the modem, a second AT command including an MBS session state report for the MBS session.

[0071] Clause 2. The method of Clause 1, wherein the first AT command is a set AT command, and the MBS session status setting includes parameters controlling MBS session status reporting for the MBS session from the modem.

[0072] Clause 3. The method of Clause 2, wherein the MBS session status setting enables or disables MBS session status reporting from the modem for the MBS session.

[0073] Clause 4. The method of any of Clauses 1 to 3, wherein the second AT command is an unsolicited AT command from the modem that includes the MBS session status report.

[0074] Clause 5. The method of any of clauses 1 to 4, wherein receiving the second AT command including the MBS session status report is in response to the modem detecting a change in one or more parameters indicative of an MBS session status of the MBS session.

[0075] Clause 6. A method as described in Clause 5, wherein the MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including an MBS decision (MBS_decision) and an MBS rejection cause (MBS_reject_cause), the MBS decision indicating a network decision of the MBS session, and the MBS rejection cause indicating a reason for rejecting the MBS session or a reason for removing the UE from the MBS session.

[0076] Clause 7. A method as described in any of clauses 5 to 6, wherein the MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including one or more of the following: a context identifier (CID), a temporary mobile group identifier (TMGI), the MBS decision (MBS_decision), the MBS rejection cause (MBS_reject_cause), an MBS tracking area identifier list (MBS_TAI_list), an MBS cell global identifier list (MBS_CGI_list), a source IP address (Source_IP), a destination address (Destination_IP), an MBS start time (MBS_Start_Time), an MBS timer (MBS_timer), an MBS service key identifier (MSK_ID), an MBS service key (MSK), an MBS traffic key identifier (MTK_ID), and an encrypted MBS traffic key (Enc_MTK).

[0077] Clause 8. The method of any one of clauses 1 to 7, further comprising transmitting a third AT command to the modem, the third AT command requesting a current value of the MBS session state setting for the MBS session.

[0078] Clause 9. The method of Clause 8, further comprising receiving a response message from the modem indicating the current value of the MBS session status setting for the MBS session, the current value indicating whether MBS session status reporting is enabled or disabled for the MBS session.

[0079] Clause 10. The method of any of clauses 1 to 9, further comprising transmitting a fourth AT command to the modem, the fourth AT command requesting a list of supported values ​​for the MBS session state setting.

[0080] Clause 11. A UE comprising: a modem; and an AP coupled to the modem and configured to perform any of clauses 1 to 10.

[0081] Clause 12. A method for managing an MBS PDU session by a UE, comprising: receiving, at a modem of the UE from an AP of the UE, a first AT command indicating an MBS session state setting for an MBS session; and transmitting, from the modem to the AP, a second AT command including an MBS session state report for the MBS session.

[0082] Clause 13. The method of Clause 12, wherein the first AT command is a set AT command, and the MBS session status setting includes parameters controlling MBS session status reporting for the MBS session from the modem.

[0083] Clause 14. The method of any of clauses 12 to 13, further comprising determining, prior to transmitting the second AT command, that the MBS session status setting enables the MBS session status reporting for the MBS session from the modem.

[0084] Clause 15. The method of any of Clauses 12 to 14, wherein the second AT command is an unsolicited AT command from the modem that includes the MBS session status report.

[0085] Clause 16. The method of any of clauses 12 to 15, wherein transmitting the second AT command including the MBS session status report is in response to the modem detecting a change in one or more parameters indicative of an MBS session status of the MBS session.

[0086] Clause 17. A method as described in Clause 16, wherein the MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including an MBS decision (MBS_decision) and an MBS rejection cause (MBS_reject_cause), the MBS decision indicating a network decision of the MBS session, and the MBS rejection cause indicating a reason for rejecting the MBS session or a reason for removing the UE from the MBS session.

[0087] Clause 18. A method as described in any of clauses 16 to 17, wherein the MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including one or more of the following: a context identifier (CID), a temporary mobile group identifier (TMGI), the MBS decision (MBS_decision), the MBS rejection cause (MBS_reject_cause), an MBS tracking area identifier list (MBS_TAI_list), an MBS cell global identifier list (MBS_CGI_list), a source IP address (Source_IP), a destination address (Destination_IP), an MBS start time (MBS_Start_Time), an MBS timer (MBS_timer), an MBS service key identifier (MSK_ID), an MBS service key (MSK), an MBS traffic key identifier (MTK_ID), and an encrypted MBS traffic key (Enc_MTK).

[0088] Clause 19. The method of any of Clauses 12 to 18, further comprising: receiving a third AT command from the AP, the third AT command requesting a current value of the MBS session state setting for the MBS session.

[0089] Clause 20. The method of Clause 19, further comprising transmitting, from the modem to the AP, a response message indicating the current value of the MBS session status setting for the MBS session, the current value indicating whether MBS session status reporting is enabled or disabled for the MBS session.

[0090] Clause 21. The method of any of clauses 12 to 20, further comprising: receiving a fourth AT command from the AP, the fourth AT command requesting a list of supported values ​​for the MBS session state setting.

[0091] Clause 22. A UE comprising: an AP; and a modem coupled to the AP and configured to perform any of clauses 12 to 21.

[0092] Another innovative aspect of the subject matter described in the present disclosure can be implemented as a wireless communication device of a UE. The wireless communication device may include at least one interface and a processing system that is communicatively coupled to the at least one interface. The processing system may be configured to implement any of the above clauses.

[0093] Another innovative aspect of the subject matter described in the present disclosure can be implemented as a portable electronic device, the portable electronic device comprising: a wireless communication device; a plurality of antennas coupled to at least one transceiver to wirelessly transmit signals output from at least one transceiver; and a housing that surrounds at least a portion of the wireless communication device, at least one transceiver, and the plurality of antennas. The wireless communication device may include at least one interface and a processing system that is communicatively coupled to the at least one interface. The processing system may be configured to implement any of the above clauses.

[0094] Another innovative aspect of the subject matter described in this disclosure may be implemented as a machine-readable medium having stored therein processor-readable instructions that, when executed by a processing system of a UE, cause the UE to implement any of the above clauses.

[0095] Another innovative aspect of the subject matter described in this disclosure can be implemented as a device. The device may include means for implementing any of the above clauses.

[0096] The user device (such as UE) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. In some implementations, UE can be referred to as a terminal device (TE). Further, in some cases, the user device can be embedded in an electronic system, such as a head unit (head unit) or an advanced driver assistance system (ADAS) of a vehicle. Still further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0097] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (such as code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system (circuitry) or logic (such as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) that is permanently configured to perform certain operations. A hardware module may also include programmable logic or circuit systems (such as contained in a general-purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. The decision to implement a hardware module with a dedicated and permanently configured circuit system or with a temporarily configured circuit system (such as configured by software) may be driven by cost and time considerations.

[0098] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method for managing a multicast and broadcast service MBS protocol data unit (PDU) session (1390) by a user equipment UE (150, 250, 350, 450, 550, 650, 1250, 1350), comprising: transmitting a first attention AT command (109, 209, 309, 409, 509, 609, 709) indicating an MBS session state setting for an MBS session from an application processor AP (160, 260, 360, 460, 560, 660, 1260) of the UE to a modem (170, 270, 370, 470, 570, 670, 1270) of the UE; and A second AT command (127, 227, 327, 427, 527, 627, 727) including an MBS session status report for the MBS session is received from the modem.

2. The method of claim 1, wherein: The first AT command is a set AT command, and the MBS session status setting includes parameters controlling an MBS session status report for the MBS session from the modem.

3. The method of claim 2, wherein: The MBS session status setting enables or disables MBS session status reporting for the MBS session from the modem.

4. The method according to any one of claims 1 to 3, wherein: The second AT command is an unsolicited AT command from the modem including the MBS session status report.

5. The method according to any one of claims 1 to 4, wherein: Receiving the second AT command including the MBS session status report is in response to the modem detecting a change in one or more parameters indicative of an MBS session status of the MBS session.

6. The method of claim 5, wherein: The MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including an MBS decision MBS_decision and an MBS rejection cause MBS_reject_cause, the MBS decision indicating a network decision of the MBS session, and the MBS rejection cause indicating a reason for rejecting the MBS session or a reason for removing the UE from the MBS session.

7. The method according to any one of claims 5 to 6, wherein: The MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, and the one or more parameters include one or more of the following: a context identifier CID, a temporary mobile group identifier TMGI, the MBS decision MBS_decision, the MBS rejection cause MBS_reject_cause, an MBS tracking area identifier list MBS_TAI_list, an MBS cell global identifier list MBS_CGI_list, a source IP address Source_IP, a destination address Destination_IP, an MBS start time MBS_Start_Time, an MBS timer MBS_timer, an MBS service key identifier MSK_ID, an MBS service key MSK, an MBS service key identifier MTK_ID, and an encrypted MBS service key Enc_MTK.

8. The method according to any one of claims 1 to 7, further comprising: A third AT command (732) is transmitted to the modem, the third AT command requesting a current value of the MBS session state setting for the MBS session.

9. The method of claim 8, further comprising: A response message is received from the modem indicating the current value of the MBS session status setting for the MBS session, the current value indicating whether MBS session status reporting is enabled or disabled for the MBS session.

10. The method according to any one of claims 1 to 9, further comprising: A fourth AT command (734) is transmitted to the modem, the fourth AT command requesting a list of supported values ​​for the MBS session state setting.

11. A method for managing a multicast and broadcast service MBS protocol data unit (PDU) session (1390) by a user equipment UE (150, 250, 350, 450, 550, 650, 1250, 1350), comprising: receiving, at a modem (170, 270, 370, 470, 570, 670, 1270) of the UE, a first attention AT command (109, 209, 309, 409, 509, 609, 709) indicating an MBS session state setting for an MBS session from an application processor AP (160, 260, 360, 460, 560, 660, 1260) of the UE; and A second AT command (127, 227, 327, 427, 527, 627, 727) including an MBS session status report for the MBS session is transmitted from the modem to the AP.

12. The method of claim 11, wherein: The first AT command is a set AT command, and the MBS session status setting includes parameters controlling an MBS session status report for the MBS session from the modem.

13. The method of any one of claims 11 to 12, wherein: The second AT command is an unsolicited AT command from the modem including the MBS session status report.

14. The method of any one of claims 11 to 13, wherein: Transmitting the second AT command including the MBS session status report is in response to the modem detecting a change in one or more parameters indicative of an MBS session status of the MBS session.

15. The method of claim 14, wherein: The MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, the one or more parameters including an MBS decision MBS_decision and an MBS rejection cause MBS_reject_cause, the MBS decision indicating a network decision of the MBS session, and the MBS rejection cause indicating a reason for rejecting the MBS session or a reason for removing the UE from the MBS session.

16. The method of any one of claims 14 to 15, wherein: The MBS session status report includes the one or more parameters indicating the MBS session status of the MBS session, and the one or more parameters include one or more of the following: a context identifier CID, a temporary mobile group identifier TMGI, the MBS decision MBS_decision, the MBS rejection cause MBS_reject_cause, an MBS tracking area identifier list MBS_TAI_list, an MBS cell global identifier list MBS_CGI_list, a source IP address Source_IP, a destination address Destination_IP, an MBS start time MBS_Start_Time, an MBS timer MBS_timer, an MBS service key identifier MSK_ID, an MBS service key MSK, an MBS service key identifier MTK_ID, and an encrypted MBS service key Enc_MTK.

17. The method of any one of claims 11 to 16, further comprising: A third AT command (732) is received from the AP, the third AT command requesting a current value of the MBS session state setting for the MBS session.

18. The method of claim 17, further comprising: A response message is transmitted from the modem to the AP indicating the current value of the MBS session status setting for the MBS session, the current value indicating whether MBS session status reporting is enabled or disabled for the MBS session.

19. The method of any one of claims 11 to 18, further comprising: A fourth AT command (734) is received from the AP, the fourth AT command requesting a list of supported values ​​for the MBS session state setting.

20. A user equipment UE (150, 250, 350, 450, 550, 650, 1250, 1350), comprising: Application processor AP (160, 260, 360, 460, 560, 660, 1260); and A modem (170, 270, 370, 470, 570, 670, 1270) coupled to the AP, wherein the AP and the modem are configured to perform any one of the methods of claims 1 to 19.

Images