KR20060109234A - Method for release broadcast/multicast program - Google Patents

Abstract

A method for releasing a BCMC(Broadcast/Multicast) program is provided to solve a problem of the related art that cannot effectively release when a BCMC program includes at least one BCMC flow. A BCMC flow identifier including a BCMC program identifier and a BCMC flow identifier is transmitted from a base station to a mobile station(S31). When the mobile station determines to release the BCMC program among BCMC and P2P currently in a traffic state, the mobile station transmits information regarding a BCMC program to be released by using an RRRM(Resource Request Release Message)(S32). The base station receives the RRM from the mobile station. and when it determines to release the BCMC program, the base station transmits information regarding a BCMC flow to be released to the mobile station by using an ERM(Extended Release Message)(S33). The mobile station transmits an ERRM(Extended Release Response Message) for acknowledging reception of the ERM(S35), and thus, the BCMC program is released and only the P2P traffic state is maintained(S35).

Description

How to disable broadcast / multicast program {Method for Release Broadcast / Multicast Program}

1 is an embodiment structural diagram illustrating a BCMC flow identifier.

2 is a flowchart of a first embodiment showing a process of releasing a BCMC program;

3 is a flowchart of a second embodiment showing a process of releasing a BCMC program;

4 is a flowchart of a third embodiment showing a process of releasing a BCMC program.

The present invention relates to a method for releasing a BCMC program, and more particularly, to a method for performing this when releasing a BCMC program among BCMC program services.

Broadcast / Multicast (hereinafter, referred to as 'BCMC') is a method of transmitting data one-to-many. In broadcast mode, a subscriber in a service area can receive broadcast data by setting the mobile station to receive the broadcast service. On the other hand, in the multicast mode, only mobile stations subscribed to the service in advance can receive data.

BCMC services can be performed in three ways:

First, BCMC data may be transmitted through a forward broadcast supplemental channel (hereinafter, referred to as 'F-BSCH') shared by mobile stations in standby state. In general, the method using F-BSCH is suitable for broadcast. That is, it is suitable for broadcasting data of the same contents to an unspecified number of subscribed mobile stations for various sectors. The method using F-BSCH transmits broadcast data to an unspecified number of mobile stations that are in standby before a traffic channel is assigned. Therefore, in order for mobile stations near the cell boundary to receive broadcast data, it is necessary to statically allocate a portion of the base station transmit power.

Second, BCMC data may be transmitted through a Forward Broadcast Fundamental Channel (hereinafter, referred to as 'F-BFCH') shared by mobile stations in a traffic state. The method using the F-BFCH is suitable for one-to-one specific number of services, such as Push-To_Talk (PTT). Since this method operates after the traffic channel is allocated, it is possible to control the transmit power of the F-BFCH according to the state of mobile stations sharing the F-BFCH. Thus, BCMC data can be transmitted using less power.

Third, BCMC data may be transmitted using a forward broadcast supplemental channel (hereinafter, referred to as 'F-BSCH') shared by mobile stations in a traffic state. The method using F-BSCH is used when the number of mobile stations to receive BCMC service in a sector is small. In this case, the power consumption of the base station for BCMC data transmission is low, and the Walsh code is used less.

The base station transmits BCMC control information so that mobile stations can receive BCMC data. The BCMC control information includes content information of a service and channel information used for BCMC. The channel information used for the BCMC includes frequency, Walsh code, data rate, frame size, public long code mask (PLCM), and mobile station registration information. And the like.

The information is periodically transmitted through an overhead message. An example of the overhead message is a BCMC Service Parameters Message (BSPM). A mobile station wishing to receive BCMC services must receive a BSPM.

On the other hand, if it is desired to release the BCMC service, the mobile station transmits a release request message to the base station, requesting the release of a specific BCMC program, and releases the service by receiving a response message from the base station. According to the related art, when the BCMC program includes at least one BCMC flow, a technique for efficiently releasing it is not provided.

An object of the present invention is to provide a method for effectively releasing a BCMC program in service.

In order to achieve the above object, the present invention relates to a method for releasing the broadcast / multicast program in a mobile station receiving a broadcast / multicast (BCMC) program, the specific broadcast / multicast program. Sending a batch release request for all broadcast / multicast flows corresponding to the base station and receiving information on the batch release of the broadcast / multicast flows from the base station.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Information about which service is a BCMC service is represented by a BCMCS Flow Identifier, which is represented by a BCMC_FLOW_ID field value in a BSPM. The BCMCS flow identifier includes a BCMCS program identifier represented by the BCMC_PROGRAM_ID field in the BSPM and a BCMCS flow discriminator represented by the BCMC_FLOW_DISCRIMINATOR field.

The BCMCS program identifier indicates a specific BCMC program, and the BCMCS flow identifier indicates a specific component constituting the one BCMC program.

As an example of an audiovisual program, each audiovisual program can be distinguished by a BCMC program identifier. Meanwhile, each audio stream and video stream constituting one audiovisual program may be distinguished by BCMC flow delimiters. Hereinafter, each service component constituting one program is referred to as a BCMC flow. In the following, the BCMC flow is distinguished by a BCMC service identifier.

The BCMC flow identifier may have a length of 16 bits, 24 bits, or 32 bits, and the length of the BCMCS flow identifier may be any one of 0 to 7, which is determined by the BCMC_FLOW_DISCRIMINATOR_LEN field in the BSPM. .

1 is a structural diagram of an embodiment of a BCMC flow identifier. 1 illustrates a BCMC flow identifier having a 16 bit length. In addition, the case where the BCMC_FLOW_DISCRIMINATOR_LEN value in the BSPM is '111', that is, the BCMC flow separator has a length of 7 is illustrated.

As shown in FIG. 1, the BCMC flow identifier includes a BCMC_FLOW_DISCRIMINATOR_LEN field indicating a BCMC flow identifier length, a BCMC_PROGRAM_ID field indicating a BCMC program identifier, and a BCMC_FLOW_DISCRIMINATOR field indicating a BCMC flow identifier.

Since the BCMC_FLOW_DISCRIMINATOR_LEN field has a length of 3 bits, it may have any one of '000' to '111'. The length of the BCMC_FLOW_DISCRIMINATOR field is determined by the BCMC_FLOW_DISCRIMINATOR_LEN field value. For example, when the BCMC_FLOW_DISCRIMINATOR field is '000', the BCMC_FLOW_DISCRIMINATOR field does not exist, and when the BCMC_FLOW_DISCRIMINATOR field is '111', it has a length of 7 bits.

Meanwhile, the length of the BCMC_PROGRAM_ID field may be determined by Equation 1.

BCMC_PROGRAM_ID field length = BCMC_FLOW_ID field length-BCMC_FLOW_DISCRIMINATOR field length-BCMC_FLOW_DISCRIMINATOR_LEN field length

In the example of FIG. 1, when the BCMC_FLOW_DISCRIMINATOR_LEN field value is '111', that is, when the length of the BCMC_FLOW_DISCRIMINATOR field is 7 bits, there may be different 128 BCMC flow identifiers corresponding to one BCMC program identifier.

On the other hand, when only one flow constituting the BCMC program exists, the BCMC_FLOW_DISCRIMINATOR_LEN value is set to '000', and BCMC flows can be distinguished by BCMC_PROGRAM_ID. In one provider network, the length of BCMC_FLOW_ID and the length of BCMC_FLOW_DISCRIMINATOR for a given program can be fixed unchanged for all flows.

In the case of transmitting BCMC data in a traffic state, in particular, when a program includes several flows, the service release process will be described below.

When releasing all flows corresponding to the program, the mobile station transmits a resource release request message (RRRM) including all flow information to be released to the base station. The flow information includes a BCMC program identifier and a BCMC flow identifier.

Upon receiving the RRRM, the base station transmits information on all flows that are actually released using an extended release message (hereinafter, referred to as 'ERM') to the base station. The information about the flow includes a BCMC program identifier and a BCMC flow identifier.

2 is a flowchart of a first embodiment illustrating a process of releasing a BCMC program. Referring to FIG. 2, the mobile station is in BCMC or P2P traffic state, and a BCMC flow identifier including BCMC program identifier and BCMC flow identifier is transmitted from the base station to the mobile station through an overhead message such as BSPM (S21). At this time, to represent each BCMC flow, a plurality of BCMC flow identifiers including a BCMC program identifier and a BCMC flow identifier are transmitted. That is, as shown in Fig. 2, information of (BCMC program identifier x, BCMC flow identifier i), (BCMC program identifier x, BCMC flow identifier j), (BCMC program identifier x, BCMC flow identifier k) is transmitted to the mobile station. Is sent.

If the mobile station decides to release the BCMC program among BCMC and P2P in the current traffic state, the mobile station transmits information on the BCMC flow to be released to the base station using the RRRM (S22). In this case, as shown in FIG. 2, to indicate each BCMC flow to be released, a plurality of BCMC flow identifiers including a BCMC program identifier and a BCMC flow identifier are transmitted. That is, as shown in FIG. 2, information of (BCMC program identifier x, BCMC flow identifier i), (BCMC program identifier x, BCMC flow identifier j), (BCMC program identifier x, BCMC flow identifier k) is transmitted to the base station. Is sent.

When the base station receives the RRRM transmitted from the mobile station and decides to release the BCMC program, the base station transmits information on the BCMC flow to be released using the ERM to the base station (S23). In this case, as shown in FIG. 2, to indicate each BCMC flow to be released, a plurality of BCMC flow identifiers including a BCMC program identifier and a BCMC flow identifier are transmitted. That is, as shown in FIG. 2, information of (BCMC program identifier x, BCMC flow identifier i), (BCMC program identifier x, BCMC flow identifier j), (BCMC program identifier x, BCMC flow identifier k) is transmitted to the base station. Is sent.

The mobile station transmits the extended release response message (ERRM) hereinafter for acknowledging the ERM to the base station (S24), thereby releasing the BCMC program and maintaining only the P2P traffic state (S25).

In fact, in the case of BCMC service, the service will be started in most BCMC program units and end in BCMC program units. Therefore, in this case, the service release procedure can be performed more efficiently. Hereinafter, a process of releasing BCMC on a program basis will be described in detail.

3 is a flowchart of a second embodiment showing a process of releasing a BCMC program. Referring to FIG. 3, the mobile station is in BCMC or P2P traffic state, and a BCMC flow identifier including a BCMC program identifier and a BCMC flow identifier is transmitted from the base station to the mobile station through an overhead message such as BSPM (S31).

At this time, to represent each BCMC flow, a plurality of BCMC flow identifiers including a BCMC program identifier and a BCMC flow identifier are transmitted. That is, as shown in FIG. 3, the information of (BCMC program identifier x, BCMC flow identifier i), (BCMC program identifier x, BCMC flow identifier j), (BCMC program identifier x, BCMC flow identifier k) is transmitted to the mobile station. Is sent to.

If the mobile station decides to release the BCMC program among BCMC and P2P in the current traffic state, the mobile station transmits information on the BCMC program to be released to the base station using the RRRM (S32). When releasing a BCMC program, it is common to release the current program itself rather than releasing each of the flows constituting the BCMC program. Therefore, when releasing the program itself, the BCMC flow identifier including only the BCMC program identifier representing the program can be transmitted without the BCMC flow identifier constituting the BCMC program. Also, by adding an indicator (ALL_BCMC_FLOW_DISCRIMINATOR) having a length of 1 bit to the RRRM and setting the indicator to a specific value (for example, '1'), information indicating that all flows constituting a specific program are to be transmitted is transmitted. Can be.

Table 1 shows an example of the RRRM.

Field Length (bits) GATING_DISCONNECT_IND One CON_REF 0 or 8 PURGE_SERVICE 0 or 1 ADD_CON_REF_INCL 0 or 1 NUM_ADD_CON_REF 0 or 3 {(NUM_ADD_CON_REF + 1) ADD_CON_REF 8 ADD_PURGE_SERVICE One } (NUM_ADD_CON_REF + 1) BCMC_INFO_INCL One NUM_BCMC_PROGRAMS 0 or 6 0 or NUM_BCMC_PROGRAMS occurrences of the following variable length record: {(0 or NUM_BCMC_PROGRAMS) BCMC_PROGRAM_ID_LEN 5 BCMC_PROGRAM_ID Variable (Value of BCMC_PROGRAM_ID_LEN + 1) ALL_BCMC_FLOW_DISCRIMINATOR One BCMC_FLOW_DISCRIMINATOR_LEN 0 or 3 NUM_FLOW_DISCRIMINATOR 0 or BCMC_FLOW_DISCRIMINATOR_LEN NUM_FLOW_DISCRIMINATOR + 1, 0, or 1 occurrences of the following variable length record: {(NUM_FLOW_DISCRIMINATOR + 1), 0, or 1 BCMC_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN } (NUM_FLOW_DISCRIMINATOR + 1), 0, or 1 } (0 or NUM_BCMC_PROGRAMS)

In the example of Table 1, the ALL_BCMC_FLOW_DISCRIMINATOR field is a field to indicate to release all BCMC flows included in the BCMC program corresponding to the BCMC_PROGRAM_ID. In this case, the BCMC_FLOW_DISCRIMINATOR_LEN field, the NUM_BCMC_FLOW_DISCRIMINATOR field, and the BCMC_FLOW_DISCRIMINATOR, which should be transmitted through the RRRM, may be omitted to request the release for each BCMC flow.

When the base station receives the RRRM transmitted from the mobile station and decides to release the BCMC program, the base station transmits information about the BCMC flow to be released using the ERM to the mobile station (S33). At this time, when releasing the program itself, the BCMC flow identifier including only the BCMC program identifier indicating the program can be transmitted without the BCMC flow identifier constituting the BCMC program. In addition, by adding an indicator (ALL_BCMC_FLOW_DISCRIMINATOR) having a length of 1 bit to the ERM and setting the indicator to a specific value (for example, '1'), it is possible to transmit information indicating that all flows constituting a specific program are released. have.

Table 2 shows an example of ERM.

Field Length (bits) NUM_FSCH 0 or 3 NUM_BCMC_PROGRAMS 0 or 6 If NUM_FSCH field is included, then NUM_FSCH plus one occurrences of the following variable length record: {(NUM_FSCH + 1) FSCH_RECORD_LEN 8 FSCH_CODE_CHAN 11 FSCH_MUX_OPTION 16 FSCH_RC 5 FSCH_CODING One FSCH_OUTERCODE_INCL One FSCH_OUTERCODE_RATE 0 or 3 FSCH_OUTERCODE_OFFSET 0 or 6 FSCH_RATE 4 FSCH_FRAME_40_USED One FSCH_FRAME_80_USED One FSCH_RECORD_RESERVED 0-7 (as needed) } (NUM_FSCH + 1) If NUM_BCMC_PROGRAMS field is included, then NUM_BCMC_PROGRAMS plus one occurrences of the following variable length record: {(NUM_BCMC_PROGRAMS + 1) BCMC_PROGRAM_ID_LEN 5 BCMC_PROGRAM_ID BCMC_PROGRAM_ID_LEN + 1 ALL_BCMC_FLOW_DISCRIMINATOR One BCMC_FLOW_DISCRIMINATOR_LEN 0 or 3 NUM_FLOW_DISCRIMINATOR 0 or BCMC_FLOW_DISCRIMINATOR_LEN NUM_FLOW_DISCRIMINATOR + 1, 0, or 1 occurrences of the following variable length record: {(NUM_FLOW_DISCRIMINATOR + 1), 0, or 1 BCMC_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN NUM_LPM_ENTRIES 3 NUM_LPM_ENTRIES plus one occurrences of the following variable-length record: {(NUM_LPM_ENTRIES + 1) FSCH_ID 7 BSR_ID 3 } (NUM_LPM_ENTRIES + 1)} (NUM_FLOW_DISCRIMINATOR + 1) or 1} (NUM_BCMC_PROGRAMS + 1)

When releasing all BCMC flows included in one BCMC program, the ERM may include a specific field indicating this. In the example of Table 2, the ALL_BCMC_FLOW_DISCRIMINATOR field is a field to indicate to release all BCMC flows included in the BCMC program corresponding to the BCMC_PROGRAM_ID. In this case, as in the example of the RRRM, the BCMC_FLOW_DISCRIMINATOR_LEN field, the NUM_BCMC_FLOW_DISCRIMINATOR field, and the BCMC_FLOW_DISCRIMINATOR, which should be transmitted through ERM, may be omitted for each BCMC flow.

The mobile station transmits the ERRM for acknowledging the ERM to the base station (S34), so that the BCMC program is released and only the P2P traffic state is maintained (S35).

4 is a flowchart of a third embodiment showing a process of releasing a BCMC program. Referring to FIG. 4, the mobile station is in BCMC or P2P traffic state, and a BCMC flow identifier including a BCMC program identifier and a BCMC flow identifier is transmitted from the base station to the mobile station through an overhead message such as BSPM (S41).

At this time, to represent each BCMC flow, a plurality of BCMC flow identifiers including a BCMC program identifier and a BCMC flow identifier are transmitted. That is, as shown in Fig. 4, information of (BCMC program identifier x, BCMC flow identifier i), (BCMC program identifier x, BCMC flow identifier j), (BCMC program identifier x, BCMC flow identifier k) is transmitted to the mobile station. Is sent.

If the mobile station decides to release the BCMC program among BCMC and P2P in the current traffic state, the mobile station transmits information about the BCMC program to be released to the base station using the RRRM (S42). When the program itself is released, the BCMC flow identifier including only the BCMC program identifier representing the program may be transmitted without the BCMC flow identifier constituting the BCMC program. In addition, by setting the BCMC_FLOW_DISCRIMINATOR_LEN field included in the RRRM to '000', information indicating that all flows constituting a specific program are released.

Table 3 shows an example of the RRRM.

Field Length (bits) GATING_DISCONNECT_IND One CON_REF 0 or 8 PURGE_SERVICE 0 or 1 ADD_CON_REF_INCL 0 or 1 NUM_ADD_CON_REF 0 or 3 {(NUM_ADD_CON_REF + 1) ADD_CON_REF 8 ADD_PURGE_SERVICE One } (NUM_ADD_CON_REF + 1) BCMC_INFO_INCL One NUM_BCMC_PROGRAMS 0 or 6 0 or NUM_BCMC_PROGRAMS occurrences of the following variable length record: {(0 or NUM_BCMC_PROGRAMS) BCMC_PROGRAM_ID_LEN 5 BCMC_PROGRAM_ID Variable (Value of BCMC_PROGRAM_ID_LEN + 1) BCMC_FLOW_DISCRIMINATOR_LEN 3 NUM_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN NUM_FLOW_DISCRIMINATOR + 1 or 1 occurrences of the following variable length record: {(NUM_FLOW_DISCRIMINATOR + 1) or 1 BCMC_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN } (NUM_FLOW_DISCRIMINATOR + 1) or 1 } (0 or NUM_BCMC_PROGRAMS)

In the example of Table 3, when the BCMC_FLOW_DISCRIMINATOR_LEN field is set to '000', the NUM_BCMC_FLOW_DISCRIMINATOR field and BCMC_FLOW_DISCRIMINATOR, which should be transmitted through RRRM, may be omitted to request the release for each BCMC flow.

When the base station receives the RRRM transmitted from the mobile station and decides to release the BCMC program, the base station transmits information on the BCMC flow to be released using the ERM to the mobile station (S43). At this time, when releasing the program itself, the BCMC flow identifier including only the BCMC program identifier indicating the program can be transmitted without the BCMC flow identifier constituting the BCMC program. Also, by setting the BCMC_FLOW_DISCRIMINATOR_LEN field included in the ERM to '000', information indicating that all flows constituting the specific program are released.

Table 4 shows an example of ERM.

Field Length (bits) NUM_FSCH 0 or 3 NUM_BCMC_PROGRAMS 0 or 6 If NUM_FSCH field is included, then NUM_FSCH plus one occurrences of the following variable length record: {(NUM_FSCH + 1) FSCH_RECORD_LEN 8 FSCH_CODE_CHAN 11 FSCH_MUX_OPTION 16 FSCH_RC 5 FSCH_CODING One FSCH_OUTERCODE_INCL One FSCH_OUTERCODE_RATE 0 or 3 FSCH_OUTERCODE_OFFSET 0 or 6 FSCH_RATE 4 FSCH_FRAME_40_USED One FSCH_FRAME_80_USED One FSCH_RECORD_RESERVED 0-7 (as needed) } (NUM_FSCH + 1) If NUM_BCMC_PROGRAMS field is included, then NUM_BCMC_PROGRAMS plus one occurrences of the following variable length record: {(NUM_BCMC_PROGRAMS + 1) BCMC_PROGRAM_ID_LEN 5 BCMC_PROGRAM_ID BCMC_PROGRAM_ID_LEN + 1 BCMC_FLOW_DISCRIMINATOR_LEN 3 NUM_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN NUM_FLOW_DISCRIMINATOR + 1 or 1 occurrences of the following variable length record: {(NUM_FLOW_DISCRIMINATOR + 1) or 1 BCMC_FLOW_DISCRIMINATOR BCMC_FLOW_DISCRIMINATOR_LEN NUM_LPM_ENTRIES 3 NUM_LPM_ENTRIES plus one occurrences of the following variable-length record: {(NUM_LPM_ENTRIES + 1) FSCH_ID 7 BSR_ID 3 } (NUM_LPM_ENTRIES + 1)} (NUM_FLOW_DISCRIMINATOR + 1) or 1} (NUM_BCMC_PROGRAMS + 1)

When releasing all BCMC flows included in one BCMC program, the ERM may include a specific field indicating this. In the example of Table 4, by setting the BCMC_FLOW_DISCRIMINATOR_LEN field to '000', information indicating that all flows constituting the specific program are released.

In this case, as in the example of the ERM, the NUM_BCMC_FLOW_DISCRIMINATOR field and BCMC_FLOW_DISCRIMINATOR, which should be transmitted through RRRM, may be omitted to request the release for each BCMC flow.

The mobile station transmits the ERRM for acknowledging the ERM to the base station (S44), whereby the BCMC program is released and only the P2P traffic state is maintained (S45).

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

The present invention has the effect that can effectively release the BCMC service.

Claims (12)

A method for releasing the broadcast / multicast flow in a mobile station receiving a broadcast / multicast (BCMC) flow, Sending a batch release request for all broadcast / multicast flows corresponding to a particular broadcast / multicast program to the base station; And Receiving information regarding the batch release of the broadcast / multicast flows from the base station Broadcast / multicast program release method comprising a. The method of claim 1, The batch release request for the broadcast / multicast flows is transmitted through a Resource Release Request Message (RRRM). The method of claim 2, When the field indicating the length of the broadcast / multicast flow identifier included in the resource release request message has a value of '000', it indicates a batch release request for the broadcast / multicast flows. How to disable cast / multicast programs. The method of claim 3, wherein The field indicating the length of the broadcast / multicast flow identifier is a BCMC_FLOW_DISCRIMINATOR_LEN field. The method of claim 2, And the resource release request message has a field indicating a bulk release request for the broadcast / multicast flows. The method of claim 5, If a field indicating a batch release request for the broadcast / multicast flows is set, each broadcast / multicast flow identifier (BCMC) corresponding to the broadcast / multicast program of the resource release request message is set. Flow Discriminator) information is omitted, the broadcast / multicast program release method. The method of claim 1, The information on the bulk release of the broadcast / multicast flows, the broadcast / multicast program release method characterized in that it is received via an Extended Release Message (ERM). The method of claim 7, wherein If the field indicating the length of the broadcast / multicast flow identifier included in the resource release request message has a value of '000', it indicates a batch release request for the broadcast / multicast flows. How to disable cast / multicast programs. The method of claim 8, The field indicating the length of the broadcast / multicast flow identifier is a BCMC_FLOW_DISCRIMINATOR_LEN field. The method of claim 7, wherein The resource release message, the broadcast / multicast program release method characterized in that it has a field indicating the collective release for the broadcast / multicast flows. The method of claim 10, If a field indicating a collective release for the broadcast / multicast flows is set, each broadcast / multicast flow delimiter corresponding to the broadcast / multicast program of the resource release message (BCMC Flow Discriminator) ) Information is omitted broadcast / multicast program release method. The method of claim 7, wherein And transmitting an extended release response message (ERRM) to the base station to confirm receipt of the extended release message.

Images