Interface for multicast and broadcast services (MBS)

Abstract

This disclosure provides systems, methods, and apparatus, including computer programs encoded on a computer readable medium, for an application processor (AP) (160) of a user equipment (UE) (150) to communicate with a modem (170) of the UE (150) to set, define, and request a state of a multicast and broadcast service (MBS) protocol data unit (PDU) supported by a (PDU) session. For example, an AP (160) may communicate with a modem (170) using one or more attention (AT) commands, such as an MBS session context (+ CMSCONT) command (109) or an MBS session read dynamic parameter (+ CMSRDP) command (124). The AP (160) may communicate with the modem (170) to modify an existing PDU session to support the MBS, or to establish a new PDU session for the MBS. The MBS PDU session requested by the UE (150) may be modified, accepted, or rejected by the network (180).

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and to 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 receivers, either to all users in a broadcast service area or to users that have joined a specific multicast group. The corresponding MBS session types are: broadcast MBS session and multicast MBS session. For both types of MBS sessions, MBS service data is transmitted over 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, which is incorporated herein by reference. Traditional techniques for managing PDU sessions are not sufficient to support new features associated with UE 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 how to request, modify, accept, or reject a multicast and broadcast service (MBS). 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 communicate with the modem to reconfigure or establish an MBS PDU session. For example, the AP may communicate with the modem using one or more attention (AT) commands, such as an MBS Session Context (+CMSCONT) command or an MBS Session Read Dynamic Parameters (+CMSRDP) command. The modem of the UE may coordinate with a network entity to manage the MBS PDU session.

[0007] One innovative aspect of the subject matter described in this disclosure may be implemented as a method for managing an MBS PDU session by a UE. The method includes communicating one or more AT commands for the MBS PDU session from an AP of the UE to a modem of the UE.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented to manage an MBS PDU session by a UE. The method includes receiving, at a modem of the UE, one or more AT commands for the MBS PDU session from an AP of the UE.

[0009] Details of one or more implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, 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 MBS on an existing PDU session in accordance with some implementations, in which the interface between the AP and the modem includes one or more attention (AT) commands that define the MBS session operation and trigger the PDU session modification procedure.

[0011] Figure 2 An example message flow for a UE to join an MBS on an existing PDU session according to some implementations is shown, in which the interface between the AP and the modem includes an AT command to join the MBS on the existing PDU session.

[0012] Figure 3 An example message flow is shown for a UE to join an MBS by establishing a new PDU session associated with the MBS in accordance with some implementations.

[0013] Figure 4 An example message flow is shown in which a UE requests to join an MBS on an existing PDU session but the network rejects the MBS join request according to some implementations.

[0014] Figure 5An example message flow is shown in which a UE requests to join an MBS session over an existing PDU session but the network rejects the PDU session modification request according to some implementations.

[0015] Figure 6 An example message flow is shown in which a UE requests to join an MBS session and establish a new PDU session associated with the MBS session, but the network rejects the MBS join request, according to some implementations.

[0016] Figure 7 An example message flow is shown in accordance with some implementations, in which a UE requests to join an MBS session and establish a new PDU session associated with the MBS session, but the network rejects the PDU session establishment request.

[0017] Figure 8 Examples of AT commands for setting or defining an MBS PDU session according to some implementations are shown.

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

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

[0020] Fig.11 An example of an AT command for querying the status of an active MBS PDU session is shown in accordance with some embodiments.

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

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

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

[0024] Multicast and broadcast services (MBS) are transmitted on associated protocol data unit (PDU) sessions. A user equipment (UE) (also referred to as a terminal equipment (TE)) can join or leave 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 MBSPDU session. The UE may join one or more MBS sessions via an MBS PDU session. In some implementations, commands between an application processor (AP) and a modem of the UE are used to define, modify or establish an MBS PDU session. The AP of the UE may set or define an MBS session context for an MBS PDU session by providing an attention (AT) command to the modem of the UE. In addition, the AP may initiate a PDU session modification process or a PDU session establishment process for an MBS PDU session by communicating an AT command to the modem. The modem of the UE may coordinate with a network entity to manage the MBS PDU session.

[0025] If the MBS session is multicast, the service announcement (on the application layer) can 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) can also be pre-configured in the UE.

[0026] If there is an existing PDU session that the UE can use to send a join request for an MBS session, the UE sends a PDU Session Modification Request on that PDU session. If the UE does not have an appropriate PDU session established using the DNN and S-NSSAI for the MBS session, the UE joins the MBS session by sending a PDU Session Establishment Request requesting establishment of an associated PDU session, along with one or several MBS session IDs and a Join Request, as further described below.

[0027] Either the UE or the network can request to leave the MBS session. When the UE determines to leave the 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 leaving operation. When the network determines to remove the UE from the MBS session, the core network component (such as the Session Management Function (SMF)) initiates the PDU Session Modification procedure (i.e., sends a PDU Session Modification Command) to notify the UE about the MBS session release.

[0028] 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 local multicast services including MBS service areas via service announcements on the application layer. If the UE determines that it is located within the MBS service area (based on information about local multicast services such as obtained via Service Announcements), the UE sends a PDU Session Modification Request (with MBS Session ID) or a PDU Session Establishment Request (with MBS Session ID) to join the multicast group.

[0029] The Requested MBS container information element (IE) (as shown in Table 1) is used by the UE to request to join or leave one or more MBS sessions in a PDU Session Establishment Request message or a PDU Session Modification Request message. Table 1 Table 2

[0030] As shown in Table 2, the main parameters are: "Type of MBS session ID" and "MBS operation". "Type of MBS session ID" 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 "Leave MBS session".

[0031] As shown in Table 3, the network uses the Received MBS container information element to indicate the information of the MBS session to the UE. Table 3 Table 4

[0032] As shown in Table 4, the "MBS Decision (MD)" parameter can be set to "MBS service area update", "MBS join is accepted", "MBS join is rejected", or "Remove UE from MBS session". The rejection reason is set to the reason when MD is set to "MBS join is rejected" or "Remove UE from MBS session". "MBS service area" is set to the service area applicable for the MBS service. This parameter can contain an MBS TAI list, an NR CGI list, or both, which identify the service area for the local MBS service. "MBS timers" are used to indicate the back-off timer for joining an MBS session or the start time of this MBS session. The “MBS security container” includes an MBS service key identifier (MBS Service Key Identifier), an MBS service key (MBS Service Key) (MSK), an MBS traffic key identifier (MBS Traffic Key Identifier) ​​(MTK ID) and an encrypted MBS traffic key (Encrypted MBS Traffic Key) (Encrypted MTK).

[0033] As previously mentioned, the present disclosure includes various examples of how to request, modify, accept or reject an MBS PDU session.

[0034] In some aspects, the AP sets or defines the MBS session context of the MBS PDU session by providing a setup AT command to the modem. The setup AT command may be referred to as an MBS session context (+CMSCONT) command or a +CMSCONT AT command. The setup AT command may include various parameters, such as a context identifier (CID), an MBS session ID, an MBS session ID type, and an MBS operation. In some implementations, the AP reads the currently set parameters of one or more MBS sessions by communicating a first read AT command such as a +CMSCONT? or +CMSCONT? AT command to the modem. In some implementations, the AP initiates a PDU session modification procedure for the MBS PDU session by communicating an AT command such as a +CGCMOD command or a +CGCMOD AT command to the modem. The AP initiates a PDU session establishment procedure for the MBS PDU session by communicating an AT command such as a +CGACT command or a +CGACT AT command to the modem. In some implementations, instead of providing two separate AT commands (such as +CMSCONT command and +CGACT command), the AP sets up the MBS session context and initiates the PDU session modification procedure by providing a single AT command such as MBS Session Operation (+CMOP) command or +CMOP AT command to the modem.

[0035] In some aspects, the AP reads dynamic parameters associated with one or more MBS sessions by providing a second read AT command to the modem. The second read AT command may be referred to as an MBS session read dynamic parameters (+CMSRDP) command or a +CMSRDP AT command. The second read AT command includes the CID of the MBS PDU session to identify the specific MBS PDU session. The modem may respond to the second read AT command by providing a response indicating one or more dynamic parameters associated with the MBS session. The dynamic parameters include: CID, temporary mobile group identity (TMGI), MBS tracking area identity list (MBS_TAI_list), MBS cell global identifier list (MBS_CGI_list), source IP address (Source_IP), destination address (Destination_IP), MBS session start time (MBS_Start_Time), MBS session residual timer (MBS_residual_timer), MBS service key (MSK), MBS service key identifier (MSK_ID), MBS business key identifier (MTK_ID), and encrypted MBS business key (Enc_MTK).

[0036] Figure 1is an example message flow for a UE to join an MBS on an existing PDU session according to some implementations, in which the interface between the AP and the modem includes one or more AT commands that define the MBS session operation and trigger the PDU session modification process. Figure 1 As shown in , UE 150 includes AP 160 and modem 170. MBS application runs on the AP side, while the protocol for configuring MBS session operation and parameter exchange (i.e., 3GPP non-access stratum (NAS) protocol) 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 Peripheral Component Interconnect Express (PCIe), shared memory, or Universal Serial Bus (USB), and the software interface may be a remote procedure call (RPC) interface or an AT command interface. In some implementations, client software runs on AP 160 and server software runs on modem 170 to implement communication between AP 160 and modem 170 via the interface (e.g., the commands described below). Similar interfaces implementing MBS services may be provided in Figures 2 to 7 is implemented in .

[0037] In step 103, a PDU session suitable for the MBS service is established. In step 106, the MBS application starts and then checks whether there is a suitable PDU session established. In order to check whether there is a suitable PDU session, the AP 160 can read the DNN and S-NSSAI of all existing PDU sessions (such as through the +CGCONTRDP command) and determine whether the DNN and S-NSSAI match the required settings of the MBS session. In step 109, if there is a suitable PDU session, the AP 160 can send an AT command such as a +CMSCONT command to the modem 170 to define or set the MBS session context including the MBS session operation (i.e., join the MBS session). For example, the +CMSCONT command can be a setup AT command such as a +CMSCONT= command. The setup AT command can include at least a CID identifying the PDU session, an MBS session ID, and an MBS operation. The setup AT command can also include an MBS session ID type. In some implementations, the modem 170 responds with an "OK" response message (not shown). For example, AP 160 may wait for an OK response message before continuing to execute the next AT command. In step 112, AP 160 triggers the PDU session modification process by communicating an AT command such as a +CGCMOD command to modem 170. In step 115, modem 170 may request to join the MBS session via a NAS message such as a PDU session modification request message. In step 118, network 180 accepts the MBS join request and returns a PDU session modification command message indicating that the MBS join request is accepted. In some implementations, modem 170 sends a response message to AP 160 for the PDU session modification process in step 121. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS join request. In some implementations, the response message shown in step 121 is optional. In some implementations, AP 160 waits for an OK message (not shown) before continuing to the next step.

[0038] In step 124, AP 160 may then query the status of the MBS session after the PDU session modification process is completed by sending a query message to modem 170. In some implementations, AP 160 queries the status of multiple MBS sessions by sending a query message to modem 170. For example, the query message may be a read AT command such as a +CMSRDP command that reads dynamic parameters associated with one or more MBS sessions. The +CMSRDP command may include the CID of the MBS PDU session to identify a specific MBS PDU session. At step 125, modem 170 may respond to the +CMSRDP command by providing a response message indicating one or more dynamic parameters associated with the MBS session (or multiple MBS sessions). In some implementations, the dynamic parameters 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. In step 127, the MBS may continue on the MBS PDU session.

[0039] Figure 2 FIG. 2 shows an example message flow for UE 250 to join MBS on an existing PDU session according to some implementations, in which the interface between AP 260 and modem 270 includes a command to join MBS on an existing PDU session. Figure 2 In the example of FIG. 1 , UE 250 may join an MBS session on an existing PDU session. A PDU session supporting MBS may be referred to as an MBS PDU session. AP 260 does not define an MBS PDU session and trigger a PDU session modification procedure in two steps (such as, for example, Figure 1 Instead of using two different commands as shown in ), a single AT command such as a +CMOP command may be used to trigger the MBS session join request directly on the PDU session modification procedure, as further described below.

[0040] In step 203, a PDU session suitable for the MBS service is established. In step 206, the MBS application is started and then checks for a suitable PDU session that has been established. In step 208, if there is a suitable PDU session, the AP 260 may send an AT command such as a +CMOP command to the modem 270 to define or set the MBS session context and trigger both the PDU session modification process. For example, the +CMOP command may be a setup AT command such as a +CMOP= command. The setup AT command may include at least a CID identifying the PDU session, an MBS session ID, and an MBS operation. The setup AT command may also include an MBS session ID type. In some implementations, the modem 270 responds with an "OK" response message (not shown). The modem 270 may then request 215 to join the MBS session via a PDU session modification request message. In step 218, the network 280 accepts the MBS join request and returns a PDU session modification command message indicating acceptance of the MBS join request. In some implementations, in step 221, modem 270 sends a response message to the PDU session modification procedure to AP 260. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS session join request. In some implementations, the response message shown in step 221 is optional. In some implementations, AP 260 waits for an OK message (not shown) before proceeding to the next step.

[0041] Figure 2 Elements 224 to 227 and their Figure 1 The corresponding ones in elements 124 to 127 are similar.

[0042] Figure 3 is an example message flow for a UE 350 to join an MBS session and establish a new PDU session associated with the MBS session according to some implementations. Figure 3In the example of , in step 306, the MBS application is started and then checks whether there is a suitable PDU session established. AP 360 determines that there is no suitable PDU session when the MBS application is started. In step 307, AP 360 configures a suitable PDU session by sending an AT command such as a +CGDCONT= command indicating the CID of the MBS session and the corresponding DNN and S-NSSAI to the modem 370. In step 309, AP 360 may send an AT command such as a +CMSCONT command to the modem 370 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 setup AT command such as a +CMSCONT= command. The setup AT command may include at least a CID identifying the PDU session, an MBS session ID, and an MBS operation. The setup AT command may also include an MBS session ID type. In some implementations, the modem 370 responds with an "OK" response message (not shown). For example, AP 360 may wait for the OK response message before continuing to execute the next AT command.

[0043] In step 311, after configuring the parameters for the PDU session establishment and the MBS PDU session, the AP 360 triggers the PDU session establishment process for the MBS PDU session by conveying an AT command such as a +CGACT command to the modem 370. In step 314, the modem 370 may send a PDU session establishment request message to the network 380 to complete the PDU session establishment process and request to join the MBS session. In step 317, the network 380 accepts the MBS join request and returns a PDU session establishment accept message indicating that the MBS join request is accepted. In some implementations, the modem 370 sends a response message to the AP 360 for the PDU session establishment process in step 322. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS session join request. In some implementations, the response message shown in step 322 is optional. Figure 3 Elements 324 to 327 of Figure 1 The corresponding ones in elements 124 to 127 are similar.

[0044] Figure 4 FIG. 4 shows an example case where the MBS join request of the PDU session modification process is rejected by the network 480. Figure 4 In the example of , network 480 may explicitly reject the MBS join request received from UE 450, as further described below. Figure 1Similar to the example of , in step 403, a PDU session suitable for the MBS service is established. In step 406, the MBS application is started and then checks whether there is a suitable PDU session established. In step 409, if there is a suitable PDU session, the AP 460 can send an AT command such as a +CMSCONT command to the modem 470 to define or set an MBS session context including an MBS session operation (i.e., join the MBS session). For example, the +CMSCONT command can be a setting AT command such as a +CMSCONT= command. In step 412, the AP 460 triggers the PDU session modification process by conveying an AT command such as a +CGCMOD command to the modem 470. The modem 470 can request to join the MBS session by sending a PDU session modification request message in step 415. In step 418, the network 480 can reject the MBS join request and return a PDU session modification command message indicating that the MBS join request is rejected. Among other examples, the network 480 may reject the MBS join request based on conditions such as when the UE is not in the service area, when the UE is not authorized / has no subscription, when the MBS service has not yet started or is otherwise unavailable, or due to congestion control / resource limitations. In some implementations, the modem 470 sends a response message to the AP 460 for the PDU session modification process in step 421. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS session join request. In some implementations, the response message shown in step 421 is optional. In step 424, the AP 460 may then query the status of the MBS session by sending a query message to the modem 470 after the PDU session modification process is completed. In some implementations, the AP 460 queries the status of multiple MBS sessions by sending a query message to the modem 470. For example, the query command may be a read AT command such as a +CMSRDP command that reads dynamic parameters associated with one or more MBS PDU sessions. If the query command is only for an active MBS session (i.e., the MBS session that the UE is currently joining), then AP 460 may determine that the MBS join request failed. If the query command is applied to an inactive MBS session (such as an MBS session that includes an attempt by UE 450 to join but failed), then AP 460 may also get an error due to an unsuccessful MBS join request, a backoff timer, and / or an MBS session start time. Based on these parameters, AP 460 may determine to retry the MBS join request at an appropriate time or location. Figure 4In the example case of , the MBS join request may be communicated via a PDU session modification request. The PDU session modification request is an example NAS protocol message. At step 425, the modem 470 may respond to the +CMSRDP command by providing a response message indicating one or more dynamic parameters associated with the PDU session (or multiple MBS sessions). At step 428, the AP 460 may proceed with an MBS application determination or reaction associated with the MBSPDU session.

[0045] Figure 5 An example message flow is shown where a UE 550 joins an MBS session over an existing PDU session but the network 580 rejects the PDU session modification request in accordance with some implementations. Figure 5 and Figure 4 Similar, except that the network 580 implicitly rejects the MBS join request (sent in step 515) by sending a PDU session modification reject message in step 516, as further described below. In step 503, a PDU session suitable for the MBS service is established. In step 506, the MBS application is started and then checks whether there is a suitable PDU session established. In step 509, if there is a suitable PDU session, the AP 560 can send an AT command such as a +CMSCONT command to the modem 570 to define or set an MBS session context including an MBS session operation (i.e., join the MBS session). For example, the +CMSCONT command can be a setting AT command such as a +CMSCONT= command. In step 512, the AP 560 triggers the PDU session modification process by communicating an AT command such as a +CGCMOD command to the modem 570. The modem 570 can request to join the MBS session by sending a PDU session modification request message in step 515. In step 516, the network 580 may implicitly reject the MBS join request by sending a PDU session modification reject message to the modem 570. In some implementations, after the modem 570 receives the PDU session modification reject message, the modem 570 communicates a message (such as an AT+CME ERROR command) to the AP 560 (not shown). Figure 5 Elements 524 to 525 and their Figure 1 The corresponding elements 124 to 125 of are similar. At step 528, the AP 460 may proceed with the MBS application determination or reaction associated with the MBS PDU session.

[0046] Figure 6 FIG. 6 shows an example case where the MBS join request of the PDU session establishment process is rejected by the network 680. Figure 6In the example of , network 680 may explicitly reject the MBS join request received from UE 650, as further described below. Figure 3 Similar to the example of , in step 606, the MBS application is started and then checks whether there is a suitable PDU session established. AP 660 determines that there is no suitable PDU session when the MBS application is started. In step 607, AP 660 configures a suitable PDU session by sending an AT command such as a +CGDCONT= command indicating the CID of the MBS session and the corresponding DNN and S-NSSAI to the modem 670. In step 609, AP 660 may send an AT command such as a +CMSCONT command to the modem 670 to define or set an MBS session context including an MBS session operation (i.e., joining an MBS session). For example, the +CMSCONT command may be a setting AT command such as a +CMSCONT= command. In step 611, after configuring the parameters for PDU session establishment and MBS PDU session, AP 660 triggers the PDU session establishment process for the MBS PDU session by conveying an AT command such as a +CGACT command to the modem 670. In step 614, the modem 670 may send a PDU session establishment request message to the network 680 to complete the PDU session establishment process and request to join the MBS session. In step 617, the network 680 may reject the MBS join request and return a PDU session modification command message indicating that the MBS join request is rejected. Among other examples, the network 680 may reject the MBS join request based on conditions such as: when the UE is not in the service area, when the UE 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. In some implementations, the modem 670 sends a response message to the AP 660 for the PDU session establishment process in step 619. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS session join request. In some implementations, the response message shown in step 619 is optional.

[0047] In step 624, the AP 660 may then query the status of the MBS session by sending a query message to the modem 670 after the PDU session establishment process is completed. In some implementations, the AP 660 queries the status of multiple MBS sessions by sending a query message to the modem 670. For example, the query command may be a read AT command such as a +CMSRDP command that reads dynamic parameters associated with one or more MBS PDU sessions. If the query command is only for active MBS sessions (i.e., the UE is joining the MBS session), the AP 660 may determine that the MBS join request failed. If the query command is applied to an inactive MBS session (such as an MBS session that includes the UE 650 attempting to join but failed), the AP 660 may also receive an error due to an unsuccessful MBS join request, a backoff timer, and / or an MBS session start time. Based on these parameters, the AP 660 may determine to retry the MBS join request at an appropriate time or location. Figure 6 In the example case of , the MBS join request may be communicated via a PDU session establishment request. The PDU session establishment request is an example NAS protocol message. At step 625, the modem 670 may respond to the +CMSRDP command by providing a response message indicating one or more dynamic parameters associated with the MBS session (or multiple MBS sessions). At step 628, the AP 660 may proceed with an MBS application determination or reaction associated with the MBS PDU session.

[0048] Figure 7 is an example message flow in which UE 750 joins an MBS session and establishes a new PDU session associated with the MBS session, but network 780 rejects the PDU session establishment request according to some implementations. Figure 7 Elements 706 to 714 of Figure 3 The network 780 may use a PDU session establishment accept message (such as Figure 3 ) or a PDU session establishment rejection message (as shown in step 317 of Figure 7 ) in step 720 of the embodiment. Figure 4 and Figure 6As described, the network 780 may reject the PDU session establishment based on conditions (among other examples, such as congestion control / resource limitations, the UE is not authorized / has no subscription, or the requested PDU session is not a permitted duplicate). In some implementations, the modem 770 sends 719 a response message to the PDU session establishment process to the AP 760. For example, the response message may be an AT command such as a +CGEV command to indicate the result of the MBS session join request, in this case the failure of the PDU session establishment process. In some implementations, the response message shown in step 719 is optional. Figure 7 Elements 724 to 725 and their Figure 1 The corresponding elements 124 to 125 of are similar. At step 728, the AP 660 may proceed with the MBS application determination or reaction associated with the MBS PDU session.

[0049] although Figures 4 to 7 Not shown, but some implementations of the protocol between the modem and the AP include additional messages. For example, when the modification process is unsuccessful (such as in Figure 4 418) or the PDU session establishment process is unsuccessful (such as in Figure 6 In step 617 of ), the modem (such as modem 470 or modem 670) may send an "OK" command indicating the result of the PDU session. Additionally or alternatively, the modem (such as modem 470 or modem 670) may communicate a command (such as an AT + CGEV command) to indicate the rejection result of the MBS join request. In some implementations, the OK command (for the PDU session) is located before or after the +CGEV command (for the rejected MBS join request). In some implementations, the OK message (from the modem or the AP) is used as a confirmation in response to receiving a command (from the other of the modem or the AP).

[0050] 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.

[0051] exist Figure 8 In some implementations, an example AT command has a +CMSCONT command syntax 830 that can define or set an MBS PDU session. The +CMSCONT= command 809 is a setup AT command for defining or setting an MBS session context for an MBS PDU session. Figure 8As shown in , the +CMSCONT= command 809 includes various parameters of the MBS PDU session, including CID, MBS session ID, MBS session ID type, and MBS operation. If there is an error in setting or defining the MBS session context, an error response message such as a +CME ERROR message 810 may be received from the modem. The +CME ERROR message 810 may include one or more error (err) values ​​to indicate one or more types of errors. The +CMSCONT? command 831 is a read AT command for reading the currently set parameters of one or more MBS sessions. As shown in Figure 8 As shown in FIG. 8 , the modem may respond to a +CMSCONT? command 831 received from the AP by sending a response message 832 including various parameters of the current settings for one or more MBS sessions.

[0052] In some implementations, the CID field of the +CMSCONT= command 809 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 809 indicates an MBS Session ID having an Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) multicast address in a format including source_IP_address and destination_IP_address. In some implementations, the MBS Session ID Type field of the +CMSCONT= command 809 is populated with a first value indicating a Temporary Mobile Group Identity (TMGI), a second value indicating a source-specific IP multicast address for IPv4, or a third value indicating a source-specific IP multicast address for IPv6. In some implementations, the MBS Operation field of the +CMSCONT= command 809 is populated with a first value indicating joining an MBS PDU session, or a second value indicating leaving an MBS PDU session.

[0053] The +CMSCONT=? command 833 is a test AT command for requesting the modem to return the range of supported parameters (for an MBS PDU session) as a composite value. Figure 8 As shown in FIG. 8 , the modem may respond to the +CMSCONT=? command 833 received from the AP by sending a response message 834 including a range of supported parameters for the MBS PDU session.

[0054] exist Fig. 9In the example AT command is shown as having a +CMOP command syntax 935, which can define or set the MBS session context of the MBS PDU session and trigger the PDU session modification process according to some implementations. Fig. 9 As shown in , the +CMOP= command 922 includes various parameters of the MBS PDU session, including CID, MBS session ID, MBS session ID type, and MBS operation. If there is an error in setting or defining the MBS session context, an error response message such as a +CME ERROR message 936 may be received from the modem. The +CME ERROR message 936 may include one or more error (err) values ​​to indicate one or more types of errors. The +CMOP? command 937 is a read AT command for reading the currently set parameters of one or more MBS sessions. As shown in Fig. 9 As shown in FIG. 9 , the modem may respond to a +CMOP? command 937 received from the AP by sending a response message 938 including various parameters of the current settings for one or more MBS sessions.

[0055] exist Fig.10 In some implementations, an example AT command is shown as having a +CMSRDP command syntax 1040, which can query the status of one or more active MBS sessions. Fig.10 As shown in , the query command may be an execution AT command such as +CMSRDP= command 1024, which reads dynamic parameters of one or more MBS sessions. The +CMSRDP= command 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 in FIG. 1 , the modem may respond to a +CMSRDP= command 1024 received from the AP by sending a response message 1025 including various dynamic parameters for one or more active MBS sessions associated with the CID.

[0056] exist Fig.11 In some implementations, an example AT command is shown as having a +CMSRDP command syntax 1045, which can query the status of one or more active MBS sessions. Fig.11As shown in , the query command may be an execution AT command such as +CMSRDP= command 1024, which reads dynamic parameters of one or more MBS sessions. The +CMSRDP= command 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.11 As shown in , the modem may respond to the +CMSRDP= command 1024 received from the AP by sending a response message 1025 including various dynamic parameters of one or more active MBS sessions associated with the CID. The +CMSRDP=? command 1147 is a test AT command for requesting the modem to return a list of CIDs associated with one or more active MBS PDU sessions. Fig.11 As shown in FIG. 1 , the modem may respond to a +CMSRDP=? command 1147 received from the AP by sending a response message 1148 including a list of CIDs associated with one or more active MBS PDU sessions.

[0057] Fig.12 1260 and a modem 1270, which may be the example UE 1250 described above. Figures 1 to 7 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 communication of messages (e.g., AT commands and / or RPC function calls) exchanged between the modem 1270 and the AP 1260.

[0058] 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 communication 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.

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

[0060] Fig.13 is an example network including UE 1350, next generation NodeB or gNodeB (gNB) 1385, and user plane function (UPF) 1388, which can be an implementation of the above Figures 1 to 12 An example network with the features described in . Figures 1 to 7 As described above, a PDU session 1390 is established. As described above, a PDU session 1390 supporting MBS may be referred to as an MBS PDU session. The PDU session 1390 may be implemented across UE 1350, gNB 1385, and UPF 1388 via one or more data radio bearers (DRBs) such as DRB 1396 and DRB 1397 between UE 1350 and gNB 1385 and a GTP-U tunnel 1398 between gNB 1385 and 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 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.

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

[0062] 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.

[0063] 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 remote procedure call (RPC) interfaces. 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.

[0064] 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, operations performed in parallel or in a different order, and some operations performed differently.

[0065] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the various aspects to the precise forms disclosed. Modifications and variations may be made based on the above disclosure, or may be obtained from the practice of these aspects. Although aspects of the present disclosure have been described with respect to various examples, any combination of aspects from any example 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 include any combination of the following implementation options (listed as clauses for clarity).

[0066] Terms

[0067] Clause 1. A method for managing a multicast and broadcast service (MBS) protocol data unit (PDU) session by a user equipment (UE), comprising: communicating one or more attention (AT) commands for the MBS PDU session from an application processor (AP) of the UE to a modem of the UE.

[0068] Clause 2. The method of clause 1, wherein communicating one or more AT commands for an MBS PDU session comprises: setting an MBS session context for the MBS PDU session by communicating the MBS session context from the AP to the modem via a first AT command; and requesting the modem to initiate a PDU session establishment or a PDU session modification for the MBS PDU session.

[0069] Clause 3. The method of clause 2, wherein setting the MBS session context comprises setting one or more parameters of the MBS session context for the MBS PDU session.

[0070] Clause 4. The method of clause 3, further comprising reading one or more parameters of the current settings of the MBS session by communicating a second AT command from the AP to the modem.

[0071] Clause 5. A method as described in any of clauses 3 to 4, wherein the one or more parameters include at least one of: a context identifier (CID), an MBS session ID, an MBS session ID type, or an MBS operation.

[0072] Clause 6. A method as described in any of clauses 2 to 5, wherein the first AT command includes a CID field indicating a quality of service (QoS) flow definition, an evolved packet system (EPS) traffic flow definition, and a packet data protocol (PDP) context definition.

[0073] Clause 7. A method according to any one of clauses 2 to 6, wherein the first AT command includes an MBS session ID field, the MBS session ID field indicating an MBS session ID having an Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) multicast address in a format including source_IP_address and destination_IP_address.

[0074] Clause 8. A method according to any one of clauses 2 to 7, wherein the first AT command includes an MBS Session ID Type field, which is populated with a first value for indicating a temporary mobile group identity (TMGI), a second value for indicating a source-specific IP multicast address for IPv4, or a third value for indicating a source-specific IP multicast address for IPv6.

[0075] Clause 9. A method according to any of clauses 2 to 8, wherein the first AT command comprises an MBS Operation field populated with a first value indicating joining an MBS PDU session, or a second value indicating leaving an MBS PDU session.

[0076] Clause 10. The method of any of clauses 4 to 9, wherein reading the one or more parameters of the current settings for the MBS session comprises receiving a response from the modem indicating the one or more parameters of the current settings for the MBS session.

[0077] Clause 11. The method of clause 1, wherein communicating one or more AT commands for the MBS PDU session comprises setting an MBS session context for the MBS PDU session and requesting the modem to initiate a PDU session modification for the MBS PDU session by communicating a first AT command from the AP to the modem.

[0078] Clause 12. The method of clause 1, wherein communicating one or more AT commands for an MBS PDU session comprises: setting an MBS session context for the MBS PDU session by communicating the MBS session context from the AP to the modem via a first AT command; and requesting the modem to initiate a PDU session modification or a PDU session establishment by communicating a second AT command or a third AT command, respectively, from the AP to the modem.

[0079] Clause 13. The method of clause 12, wherein requesting the modem to initiate a PDU session modification or a PDU session establishment comprises communicating a second AT command if the PDU session is already established, or communicating a third AT command if the PDU session is not already established.

[0080] Clause 14. The method of clause 1, wherein communicating one or more AT commands for the MBS PDU session comprises reading one or more dynamic parameters of the MBS session by communicating a first AT command from the AP to the modem.

[0081] Clause 15. The method of clause 14, wherein the first AT command includes a CID of the MBS PDU session.

[0082] Clause 16. The method of any of clauses 14 to 15, wherein reading the one or more dynamic parameters comprises receiving a response from the modem indicating the one or more dynamic parameters of the MBS session.

[0083] Clause 17. A method according to any one of clauses 14 to 16, wherein the one or more dynamic parameters include at least one of the following: CID, temporary mobile group identity (TMGI), MBS tracking area identity list (MBS_TAI_list), MBS cell global identifier list (MBS_CGI_list), source IP address (Source_IP), destination address (Destination_IP), MBS session start time (MBS_Start_Time), MBS session residual timer (MBS_residual_timer), MBS service key (MSK), MBS service key identifier (MSK_ID), MBS traffic key identifier (MTK_ID) and encrypted MBS traffic key (Enc_MTK).

[0084] Clause 18. A user equipment (UE) comprising: a modem; and an application processor (AP) coupled to the modem and configured to perform any of the methods of clauses 1 to 17.

[0085] Clause 19. A method for managing a multicast and broadcast service (MBS) protocol data unit (PDU) session by a user equipment (UE), comprising: receiving, at a modem of the UE, one or more attention (AT) commands for the MBS PDU session from an application processor (AP) of the UE.

[0086] Clause 20. The method of clause 19, wherein receiving one or more AT commands for an MBS PDU session comprises: receiving, at a modem, a first AT command from an AP, the first AT command requesting the modem to set up an MBS session context for the MBS PDU session; and initiating a PDU session establishment or a PDU session modification for the MBS PDU session.

[0087] Clause 21. The method of clause 20, wherein the first AT command comprises one or more parameters of an MBS session context of the MBS PDU session.

[0088] Clause 22. The method of clause 21, further comprising: receiving, at the modem, a second AT command from the AP, the second AT command requesting the modem to send one or more parameters of the current settings of the MBS session.

[0089] Clause 23. The method of clause 22, further comprising: communicating, from the modem to the AP, a response indicating one or more parameters of current settings for the MBS session.

[0090] Clause 24. A method as described in any of clauses 21 to 23, wherein the one or more parameters include at least one of: a context identifier (CID), an MBS session ID, an MBS session ID type, or an MBS operation.

[0091] Clause 25. The method of clause 20, wherein initiating a PDU session establishment or a PDU session modification for the MBS PDU session comprises initiating a PDU session modification in response to receiving a second AT command from the AP, or initiating a PDU session establishment in response to receiving a third AT command from the AP.

[0092] Clause 26. The method of clause 19, wherein receiving one or more AT commands for an MBS PDU session comprises: receiving, at a modem, a first AT command from an AP, the first AT command requesting the modem to set up an MBS session context for the MBS PDU session and initiate a PDU session modification for the MBS PDU session.

[0093] Clause 27. The method of clause 19, wherein receiving one or more AT commands for the MBS PDU session comprises receiving, at the modem, a first AT command from the AP, the first AT command requesting the modem to send one or more dynamic parameters of the MBS session.

[0094] Clause 28. The method of clause 27, further comprising: communicating, from the modem to the AP, a response indicating one or more dynamic parameters of the MBS session.

[0095] Clause 29. A method according to any one of clauses 27 to 28, wherein the one or more dynamic parameters include at least one of the following: CID, temporary mobile group identity (TMGI), MBS tracking area identity list (MBS_TAI_list), MBS cell global identifier list (MBS_CGI_list), source IP address (Source_IP), destination address (Destination_IP), MBS session start time (MBS_Start_Time), MBS session residual timer (MBS_residual_timer), MBS service key (MSK), MBS service key identifier (MSK_ID), MBS business key identifier (MTK_ID) and encrypted MBS business key (Enc_MTK).

[0096] Clause 30. A user equipment (UE), comprising: an application processor (AP); and a modem coupled to the AP and configured to perform any of the methods of clauses 19 to 29.

[0097] 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 communicatively coupled to the at least one interface. The processing system may be configured to implement any of the above clauses.

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

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

[0100] 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.

[0101] 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. Further, in some cases, the user device may be embedded in an electronic system such as a head unit of a vehicle or an advanced driver assistance system (ADAS). 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.

[0102] 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 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 in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (such as, configured by software) may be driven by cost and time considerations.

[0103] 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, 750, 1250, 1350), comprising: One or more attention AT commands for the MBS PDU session are communicated from an application processor AP (160, 260, 360, 460, 560, 660, 760, 1260) of the UE to a modem (170, 270, 370, 470, 570, 670, 770, 1270) of the UE.

2. The method of claim 1, wherein communicating the one or more AT commands for the MBS PDU session comprises: setting the MBS session context by communicating an MBS session context of the MBS PDU session from the AP to the modem via a first AT command (109, 309, 409, 509, 609, 709, 809); as well as The modem is requested to initiate a PDU session establishment or a PDU session modification for the MBS PDU session.

3. The method according to claim 2, wherein: Setting the MBS session context includes setting one or more parameters of the MBS session context for the MBS PDU session.

4. The method according to claim 3, further comprising: The one or more parameters of the current settings of the MBS session are read by communicating a second AT command (831) from the AP to the modem.

5. The method according to any one of claims 3 to 4, wherein: The one or more parameters include at least one of: a context identifier CID, an MBS session ID, an MBS session ID type, or an MBS operation.

6. The method according to any one of claims 2 to 5, wherein the first AT command comprises: A CID field, wherein the CID field indicates a quality of service QoS flow definition, an evolved packet system EPS service flow definition, and a packet data protocol PDP context definition; an MBS session ID field indicating the MBS session ID of an Internet Protocol version 4 IPv4 and Internet Protocol version 6 IPv6 multicast address having a format including source_IP_address and destination_IP_address; an MBS Session ID Type field populated with a first value indicating a temporary mobile group identity TMGI, a second value indicating a source specific IP multicast address for IPv4, or a third value indicating a source specific IP multicast address for IPv6; or An MBS operation field, wherein the MBS operation field is filled with a first value for indicating joining the MBS PDU session, or a second value for indicating leaving the MBS PDU session.

7. The method according to any one of claims 4 to 6, wherein reading the one or more parameters of the current settings of the MBS session comprises: A response is received from the modem indicating the one or more parameters of the current settings for the MBS session.

8. The method of claim 1, wherein communicating the one or more AT commands for the MBS PDU session comprises: An MBS session context for the MBS PDU session is set by communicating a first AT command (208, 922) from the AP to the modem and requesting the modem to initiate a PDU session modification for the MBS PDU session.

9. The method of claim 1 , wherein communicating the one or more AT commands for the MBS PDU session comprises: setting the MBS session context by communicating an MBS session context of the MBS PDU session from the AP to the modem via a first AT command (109, 309, 409, 509, 609, 709, 809); as well as The modem is requested to initiate a PDU session modification or a PDU session establishment by communicating a second AT command (115, 215, 415, 515) or a third AT command (314, 614, 714), respectively, from the AP to the modem.

10. The method of claim 1, wherein communicating the one or more AT commands for the MBS PDU session comprises: One or more dynamic parameters of the MBS session are read by communicating a first AT command (124, 224, 324, 424, 524, 624, 724, 1024, 1124) from the AP to the modem.

11. The method according to claim 10, wherein: The first AT command includes the CID of the MBS PDU session.

12. The method according to any one of claims 10 to 11, wherein reading the one or more dynamic parameters comprises: A response is received from the modem indicating the one or more dynamic parameters of the MBS session.

13. The method according to any one of claims 10 to 12, wherein: The one or more dynamic parameters include at least one of the following: the CID, the temporary mobile group identity TMGI, the MBS tracking area identity list MBS_TAI_list, the MBS cell global identifier list MBS_CGI_list, the source IP address Source_IP, the destination address Destination_IP, the MBS session start time MBS_Start_Time, the MBS session residual timer MBS_residual_timer, the MBS service key MSK, the MBS service key identifier MSK_ID, the MBS service key identifier MTK_ID and the encrypted MBS service key Enc_MTK.

14. 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, 750, 1250, 1350), comprising: One or more attention AT commands for the MBS PDU session are received at a modem (170, 270, 370, 470, 570, 670, 770, 1270) of the UE from an application processor AP (160, 260, 360, 460, 560, 660, 760, 1260) of the UE.

15. The method of claim 14, wherein receiving the one or more AT commands for the MBS PDU session comprises: receiving, at the modem, a first AT command (109, 309, 409, 509, 609, 709, 809) from the AP, the first AT command requesting the modem to set up an MBS session context for the MBS PDU session; as well as Initiate a PDU session establishment or a PDU session modification for the MBS PDU session.

16. The method according to claim 15, wherein the first AT command includes one or more parameters of the MBS session context of the MBS PDU session, further comprising: receiving, at the modem, a second AT command from the AP (831), the second AT command requesting the modem to send the one or more parameters of the current settings of the MBS session; as well as A response is communicated from the modem to the AP indicating the one or more parameters of the current settings for the MBS session.

17. A method according to any one of claims 14 to 16, wherein: The one or more parameters include at least one of: a context identifier CID, an MBS session ID, an MBS session ID type, or an MBS operation.

18. The method of claim 16, wherein initiating the PDU session establishment or the PDU session modification for the MBS PDU session comprises: Initiating the PDU session modification in response to receiving a second AT command (115, 215, 415, 515) from the AP, or The PDU session establishment is initiated in response to receiving a third AT command (314, 614, 714) from the AP.

19. The method of claim 15, wherein receiving the one or more AT commands for the MBS PDU session comprises: receiving, at the modem, a first AT command (124, 224, 324, 424, 524, 624, 724, 1024, 1124) from the AP, the first AT command requesting the modem to send one or more dynamic parameters of the MBS session; and A response is communicated from the modem to the AP indicating the one or more dynamic parameters of the MBS session.

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

Images