JP2008503976A - Method for communicating data in a wireless mobile communication system - Google Patents

Abstract

According to the present invention, a data communication method in a wireless communication system is disclosed. In particular, the method includes transmitting a request by a mobile subscriber station (MSS) to the network entity through a de-registration request message for requesting the network entity to hold priority session information, and deregistering from the network entity. Receiving selected session information through a command response.
[Selection] Figure 1

Description

  The present invention relates to a data transmission / reception method, and more particularly to a method of communicating data in a wireless mobile communication system.

  In a broadband wireless access system, an MSS (Mobile Sub BScriber Station) allows an idle mode to be entered to reduce power. The MSS does not need to perform a handover procedure when moving between base stations in the same paging zone in idle mode. In general, performing a handover requires the MSS to transmit in the uplink direction while in idle mode. Therefore, power is reduced because the MSS does not need to transmit to the base station (BS).

  The MSS is located in a paging group composed of a plurality of base stations. The coverage area covered by the paging group is called the paging zone. Paging group base stations within a paging zone share the same paging cycle and paging offset value.

  The MSS transmits a request message to the BS requesting entry into the idle mode. Thereafter, the BS transmits a response message allowing the MSS to enter the idle mode. The BS includes a paging group identification, a paging cycle value, and a paging offset value in the response message. The request is made using a DREG-REQ (de-registration request) message.

  The BS provides a response message that allows the MSS to enter idle mode in response to the request. The response message includes the paging group identification, paging cycle and BS paging offset. The response is performed using a DREG-CMD (de-registration commnd) message.

  In addition, the BS provides the MAC (medium access group) address of the MSS entering the idle mode to the paging group, and the MSS can receive the paging message during the idle mode.

  The BS will send a message at a specific time interval (or referred to in the paging cycle) asking if the MSS wishes to maintain or exit idle mode during idle mode or if the MSS needs to perform a ranging operation. Broadcast. Further, the BS can transmit a paging message for notifying the MSS that there is MSS downlink data.

  The idle mode can be terminated by either one of the MSS or BS. If the MSS needs to transmit data in the uplink direction, the MSS can exit idle mode at any time. On the other hand, when there is downlink traffic from the BS, the BS notifies the MSS to end the idle mode through a paging message, and the MSS can receive the data. Also, if the MSS in the idle mode cannot receive the paging message from the BS in a specific time slot or paging cycle due to various reasons such as moving to another paging zone, the MSS ends the idle mode. To do.

  Here, the MSS in idle mode can roam freely within the boundaries of the paging zone without having to perform a handover, so that the MSS receives any downlink traffic or transmits data in the uplink direction. There is no need to do.

  If the MSS receives notification through the paging message from the BS that there is downlink traffic, it will exit idle mode and re-register / re-enter the network and received downlink data. Also, as part of performing the ranging operation, the MSS causes the BS to update the location of the MSS and an efficient MSS information list. On the other hand, if the MSS receives a command through the paging message so as not to perform any operation, the MSS remains in the idle mode.

  However, if the MSS needs to transmit data in the uplink direction, or if the MSS moves to another paging zone, the BS in the paging group will be in the other paging group and the MSS will be in the same paging zone. Since there is no more than that, the corresponding MSS is notified to be deleted from the list of MSS in the idle mode.

  If the MSS moves to another paging zone or transmission to the BS occurs during idle mode, the corresponding MSS needs to exit idle mode and register with the new BS in the new paging group. When registering with a new BS, the MSS needs to go through a registration process from the beginning, and this registration process is identical to the initial registration process for the previous network. Therefore, the MSS needs more power to register with the new network and takes longer to go through the registration process.

  In addition, after the MSS moves to a new paging group, if the MSS wishes to retain the previous paging group idle information, the MSS must request an idle mode through a MAC control message after registering with the new network. Thereafter, the BS of the new paging group responds to the request for idle mode. Furthermore, such a procedure results in an increase in MAC signals and increases power usage.

  FIG. 1 is a diagram illustrating an MSS that returns to a normal mode for downlink traffic received after exiting the idle mode. Here, the MSS enters the idle mode every time a request is made by the MSS to enter the idle mode. When the MSS enters the idle mode every time a command is sent from the BS, the MSS exits the idle mode and returns to the normal mode for the received downlink traffic.

  Referring to FIG. 1, the MSS cancels registration with the BS (BS1-host BS) through DREG-REQ and DREG-CMD (step S10). After the MSS enters the idle mode, the host BS notifies the other BSs in the same paging group that the MSS has entered the idle mode through the paging announcement (step S11). At the time of paging announcement, the host BS includes the MAC address of the MSS. Each BS that receives the paging announcement registers the MAC address of the MSS in its paging list. Such a paging list is shared by all BSs in the paging zone.

  In idle mode, data can be transmitted to the MSS. In order to receive this data, the MSS needs to exit idle mode. As a result, when there is downlink traffic, the host BS transmits a paging announcement to notify all BSs in the paging group to transmit data to the MSS (step S12). Accordingly, each BS transmits a paging message to the MSS using the MAC address provided from the host BS during the paging interval (step S13).

  The MSS receives a paging message from each BS in the paging group. If one of the BSs, ie, the action code received from BS # 3 is set to “10” indicating the initial network entity, the MSS performs the ranging operation and initial network entity procedure with BS # 3. Execute (Step S14, Step S15). Here, the ranging operation includes an RNG-REQ message from the MSS and an RNG-RSP message from the BS. After the MSS obtains the initial network entity, BS # 3 transmits downlink data to the MSS (step S16).

  Power reduction is not limited to idle mode. As another power reduction means other than the idle mode, the MSS can enter the sleep mode to reduce the power. Since the MSS enters the sleep mode, the MSS transmits a request for entering the sleep mode to the BS through a sleep request (MOB-SLP-REQ) message. The BS then transmits a response message that allows the MSS to enter sleep mode through a sleep response (MOB-SLP-RSP) message. The MOB-SLP-REQ and MOB-SLP-RSP messages include various information such as sleep mode start time, maximum / minimum sleeping interval (frame), and listening interval.

  At the end of the sleeping interval, the BS transmits a traffic indication (MOB-TRF-IND) message to inform the MSS which downlink traffic is present. If there is no downlink traffic for the receiving MSS, the MSS can return to sleep mode. However, if downlink data is present, the MSS returns to normal mode to receive downlink traffic.

  FIG. 2 illustrates an MSS that exits sleep mode and returns to normal mode to receive downlink traffic. Here, in order to enter the sleep mode, the MSS enters the sleep mode whenever requested by the MSS. When the MSS enters the idle mode every time a command is sent from the BS, the MSS exits the idle mode and returns to the normal mode in order to receive downlink traffic.

  Referring to FIG. 2, the MSS transmits a request for entering a sleep mode to the BS through a MOB-SLP-REQ message (step S2-0). In response, the BS transmits a MOB-SLP-RSP message to the MSS (step S2-1). The MOB-SLP-RSP message includes information such as sleep mode start time (M), maximum / minimum sleeping intervals (frames) (N1, N2), and listening intervals (L1).

  The MSS enters the sleep mode according to the maximum sleeping interval (N1) set in steps S20 and S21, and the BS transmits a MOB-TRF-IND message during the listening interval L1 (step S2-2). The BS informs the MSS through the (positive / negative) MOB-TRF-IND message whether there is any data to receive to the MSS. Also listen or activate from sleeping during L1 to check if any downlink data is present. As shown in 'Negative sign display', if there is no downlink data, the MSS returns to the sleep mode. However, after the listening interval, the sleeping interval or sleeping window size is doubled according to the scheduled sleep window setting method.

  If the BS receives data for transmission to the MSS during the sleeping interval, the BS stores the data in a specific storage space, and the next listening interval when the MSS is notified of the data through the MOB-TRF-IND message. (Step S2-3). Thereafter, the MSS activates the sleep mode and returns to the normal mode in order to receive data (step S2-4).

  In the normal mode, when an IP (Internet protocol) packet (data) is received by the MSS, the router transmits the IP packet to the MSS through the base station. The router uses ARP in IP version 4 (IPv4), and uses ND (neighbor discovery) in IP version 6 (IPv6). In other words, when transmitting an IP packet to the MSS, the router searches for a target link layer address (for example, a MAC address or an Ethernet (registered trademark) address) corresponding to the IP address of the MSS using the ARP and ND protocols. ARP is an IPv4 protocol used when an IP address is changed to a link layer address such as a MAC address or an Ethernet (registered trademark) address.

  The ND protocol is an IPv6 address used to determine a link layer address of a neighboring link. The address change is performed when an IP packet header and a link layer address header are generated. In this way, the address change is performed only on the output IP packet.

  In general, it is not clearly specified how the BS transmits or broadcasts a request or neighbor request to the MSS. In particular, the specific role or operation by the BS is not clearly defined when transmitting the request / neighbor solicitation to the MSS during the normal mode.

  Further, the MSS in any one of the sleep mode and the idle mode only receives signals at a specific interval / cycle. As a result, when the router needs to transmit the received data to the MSS, a problem occurs when the router is in the sleep mode or the idle mode because the MSS cannot respond to the ARP request or the neighbor request until the scheduled time. . As a result, the target MSS cannot transmit a response, resulting in a transmission failure. This problem may prevent the MSS from receiving data.

  As described above, a problem occurs in transmitting data from the router to the MSS. In particular, data received from a router due to power reduction in the sleep mode or idle mode of the MSS cannot be received by the MSS because the MSS cannot receive it until a specific time. Therefore, data is not always transmitted to the MSS.

  Accordingly, the present invention has been made to solve the problems of the prior art as described above, and its purpose is to enter the idle mode, update the location during the idle mode, and re-enter the network after the idle mode. It is to provide a method for communicating data between an MSS and a network entity to enter.

  According to an embodiment of the present invention, there is provided a method for communicating data to enter an idle mode, wherein a request by an MSS is sent through a deregistration request message requesting a network entity to hold priority session information. And receiving the selected session information from the network entity through a deregistration command response.

  In another aspect of the present invention, the method for updating the location of the MSS includes transmitting a request to the second network entity through an RNG-REQ message requesting the location update of the MSS from the first network entity. Receiving selected session information updated through a response message from the second network entity, and updating the session information after the location of the MSS is updated from the first network entity to the second network entity. Performing a network entity procedure for updating.

  In yet another aspect of the invention, a method for entering a network after idle mode is disclosed. In particular, the method selects as a step of transmitting a request to a second network entity through an RNG-REQ message, and a step of receiving selected session information from the second network entity through an RNG-RSP message. Received session information is received by the second network entity from the first network entity and entering the network of the second network entity.

  In yet another aspect of the present invention, a method for requesting a network entity to hold a network address of an MSS is disclosed. The method includes transmitting a request to maintain a network address through a request message to a first network entity, entering an idle mode after receiving a response message from the first network entity, Receiving a paging message from a second network entity during the mode, entering a network of the second network entity, and receiving an IP packet from the second network entity. .

  In still another aspect of the present invention, a method for requesting a network entity to hold CS (convergence subscriber) information is disclosed. The method includes transmitting a request to retain CS information to a first network entity through a request message, entering a idle mode after receiving a response message from the first network entity, Receiving a paging message from the second network entity during the mode, entering the network of the second network entity, and receiving a data packet from the second network entity. .

  The description of the means for solving the above-mentioned problems according to the present invention and the description of the embodiments to be described later are exemplary and for the purpose of explanation, and are intended to provide further description of the present invention. Should be understood.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals and numbers are used in common for the same components and parts as much as possible.

  When entering the idle mode, the MSS transmits MSS network entity session information through a request message. The network entity is a base station, a paging controller, an access gateway or a base station controller. Preferably, the session information is a list of MSS session information held by the network entity. In particular, the session information prioritized by the MSS relates to network re-entry related services and operation information for utilizing additional network re-entry from the idle mode.

  The request message includes a request for entering the idle mode by the MSS. For example, the request message is a DREG-REQ message. In addition, the request message includes priority session information that the MSS wishes the network entity to maintain. In particular, the session information includes information such as security information, IP address information, MSS capability, management connection identification, and information essential for maintaining network services.

  After receiving the priority session information (or session information list), the network entity selects the session information determined to be retained. Thereafter, the network entity notifies the MSS of the network entity selection session information through a response message. The selected session information is the same as, or different from, the combination of the priority session information transmitted from the MSS. Furthermore, the selected session information is composed of a list of network entity selection session information to be used for future MSS re-entry from the idle mode by holding arbitrary MSS service and operation information. Furthermore, the selected session information is used to ensure efficient service between the MSS and the network entity.

  The response message includes a response to a request for entering the idle mode by the MSS. For example, the request message is a DREG-CMD (de-registration command ND) message. In the response message, the network entity includes the selected session information.

  During idle mode, if there is downlink traffic for the MSS, the network entity transmits a paging message. The paging message includes selected session information for the MSS that receives the downlink data. Usually, paging messages can be transmitted periodically or at specific time intervals. Thereafter, network entities within the same paging group share with other selected session information through the backbone network. As a result, when the MSS exits idle mode and re-enters the network, the MSS can bypass some procedural steps required upon network re-entry. As described above, re-entry can be facilitated by maintaining selected session information by the network entity. The procedural steps include those that can be shared simultaneously with other network entities such as, for example, IP addresses and / or security information.

  When the MSS moves to another paging group and requests a location update, a new network entity in the other paging group receives session information selected from a network entity in the previous paging group. The network entity of the previous paging group is the network entity that holds the updated latest MSS session information. New network entities in other paging groups transmit selected session information previously received from the paging group to the MSS. In succession, upon MSS location update, the MSS re-enters the new network to update the information. In summary, the location update of the MSS can be done with a paging zone identification based on the environment where the update is done only when the MSS moves from one paging zone identification to another paging zone identification, for example.

  Also, MSS location updates can be performed on a time basis. In other words, the timer-based location update includes a scheduler and the MSS and network perform location updates. For example, if a timer based location update schedule is set between the MSS and the network entity at 10 second intervals, the location of the MSS will be at 10 second intervals based on previous location updates regardless of whether the MSS moves. Updated.

  When the MSS receives multiple paging group identifications through a paging message, the MSS requests a location update for the corresponding network entity. When updating the location, the MSS transmits to the network entity the identity of the network entity that previously allowed idle mode entry in the paging group and the paging group identity of the paging group that the MSS will leave in idle mode. Thereafter, the corresponding network entity transmits information such as paging group identification, paging cycle value and paging offset value to the location update request through a response message, and the MSS leaves in idle mode after moving to another paging group. Is acceptable.

  Table 1 shows an example of a message parameter of MSS session information.

表１のメッセージパラメーターは、ＴＬＶフォーマットのメッセージに含まれ、アイドルモードを終了する時にバイパスできるネットワーク登録手続きはビットマップフォーマットで表現できる。本発明の実施形態において、このような動作は、“Ｅｘｐｅｄｉｔｅｄ ｎｅｔｗｏｒｋ ｓｅｔｕｐ＿ｆｌａｇ”で表示される。

The message parameters in Table 1 are included in the TLV format message, and a network registration procedure that can be bypassed when exiting the idle mode can be expressed in a bitmap format. In the embodiment of the present invention, such an operation is indicated by “Expanded network setup_flag”.

  FIG. 3 illustrates a signaling process when MSS bound downlink traffic occurs during idle mode according to an embodiment of the present invention. FIG. 3 shows the procedure for the MSS to exit idle mode when there is downlink traffic.

  The MSS transmits a request message requesting to enter the idle mode through the DREG-REQ message to the first network entity (step S10). The request message is MSS priority session information that the MSS prioritizes for the facilitated future re-entry into the network. As described above, the network entity is a base station, paging controller, access gateway or base station controller. Such MSS priority session information includes information such as security information, IP address information, MSS capability, management connection identification, and information essential for maintaining network services. The priority session information message has a format similar to the message in Table 1.

  For illustrative purposes, the network entity that receives priority session information from the MSS is identified as the first network entity. The second network entity can also be identified as a network entity seeking to re-enter the MSS from idle mode. After receiving the solicitation message, the first network entity broadcasts a notification over the backbone channel to at least one or all other network entities having the same paging identity in the paging group, so that the corresponding MSS receives the paging group. Are added to each network entity (step S20). Thereafter, the first network entity transmits the selected session information to the corresponding MSS through the DREG-REQ-CMD in response to the request message (step S30). Selected session information includes any MSS service and operational information useful for facilitating future MSS network re-entry from idle mode. The selected session information is a list of selected session information that is the same as, or different from, or a combination of the priority session information requested by the MSS. Also, other information such as paging cycle, paging offset and paging identification may be included in the transmission of DREG-CMD. DREG-CMD is a command or message that allows the MSS to enter the requested idle mode.

  When receiving DREG-CMD from the first network entity, the MSS enters idle mode. During the idle mode, the MSS may receive a paging message at a specific time slot or interval from the first network entity (step S40). The paging message includes various information such as when there is any downlink traffic or exiting idle mode.

  While in idle mode, the MSS can move to another network entity (hereinafter “second network entity”) within a paging group with the same paging group identity or within a paging group with multiple paging group identity It is. If the MSS moves to a second network entity in the same paging group with the same paging identity (step S50), the MSS from the second network entity and the first network entity in the same paging cycle. The received paging offset is received (step S60).

  When downlink traffic reaches the first network entity and when the first network entity notifies the downlink traffic to the MSS (step S70), the first network entity is down through the backbone network. Session information along with the presence of link traffic is transmitted to other network entities in the paging group (step S80).

  After receiving the selected session information from the first network entity, the second network entity transmits a paging message including the selected session information and the presence of downlink traffic to the MSS (step S90). The MSS transmits the identification of the first network entity that allows the MSS to enter the idle mode to the second network entity through the RNG-REQ message (step S100).

  After receiving the identification of the first network entity, the second network entity has a corresponding MSS session in which the MSS is located in the coverage area and the first entity is held by the first network entity. The first network entity is notified that information transmission is requested (step S110).

  The first network entity responds to the request by transmitting the session information held through the backbone channel (step S120). Also, the second network entity transmits a list of session information currently held by the second network entity to the MSS through the RNG-RSP message (step S130). As a result, any procedural steps required for re-entry into the network can be skipped when the MSS performs re-entry into the network. In other words, since the second network entity holds arbitrary MSS service and operational information, the same information is not required upon re-entry into the network. At the same time, the MSS receives via the RNG-RSP message a procedural step that can be skipped by the MSS when the network re-enters.

  Based on the information provided from the second network entity, a network entity or re-entry procedure is performed (step S140). The network registration procedure stage may include, for example, MSS capability negotiation procedures, security procedures, registration procedures, IP address acquisition procedures, and the like. In addition, in order to establish a connection for receiving data, the MSS performs necessary procedures in combination with the network entry procedure. After the procedures for network entry (or re-entry) and data reception are completed, the second network entity transmits the downlink data received from the first network to the MSS (step S150).

  Steps S10 to S150 describe the operation in the network when downlink traffic exists during idle mode. If uplink traffic occurs for the MSS in idle mode, the optional steps S70, S80, S90, S150 are excluded from operation.

  FIG. 4 shows a signaling process when the MSS requests to enter the idle mode and requests the network entity to hold the session information. FIG. 4 illustrates, as another embodiment of the present invention, a process associated with updating the location of the MSS in idle mode after the MSS has moved to another paging group.

  Referring to FIG. 4, the MSS transmits a request for entering the idle mode through the DREG-REQ message to the first network entity (step S210). The request message includes MSS priority session information in which the MSS prioritizes the network entity being retained for facilitated future re-entry into the network. The network entity is a BS or a paging controller. As described above, the network entity is a base station, paging controller, access gateway or base station controller. The MSS priority session information includes information such as security information, IP address information, MSS capability, management connection identification, and information essential for maintaining network service. The priority session information message has a format similar to the message in Table 1.

  As described above, the identification of the first network entity and the second network entity has been described with reference to FIG. After receiving the solicitation message, the first network entity broadcasts a notification over the backbone channel to all other network entities having the same paging identity in the paging group, thereby sending the corresponding MSS in each paging group. To the network entity (step S220). Thereafter, the first network entity transmits the selected session information to the corresponding MSS through the DREG-CMD in response to the request message (step S230). Selected session information includes any MSS service and operational information useful for facilitating future MSS network re-entry from idle mode. The selected session information is a list of selected session information that is the same as, or different from, or a combination of the priority session information requested by the MSS. Also, when transmitting DREG-CMD, other information such as paging cycle, paging offset and paging identification may be included. DREG-CMD is a command or message that allows the MSS to enter the requested idle mode.

  When receiving DREG-CMD from the first network entity, the MSS enters idle mode. During the idle mode, the MSS can receive a paging message at a specific time slot or interval from the first network entity (step S240). The paging message includes various information such as when there is any downlink traffic or exiting idle mode.

  While in idle mode, the MSS can move to another network entity (hereinafter “second network entity”) within a paging group with the same paging group identity or within a paging group with multiple paging group identity It is. If the MSS moves to a second network entity in the same paging group having the same paging identity (step S250), the MSS from the paging message and the first network entity in the same paging cycle from the second network entity. The received paging offset is received (step S260).

  If the cell coverage area is designed so that a network entity only belongs to one paging group, a network entity that moves to a paging group having one or more paging group identifications, for example, between two paging groups Mentioned in network entities at the time of transition.

  The MSS also learns that the second network entity belongs to a second paging group having a different paging group identification than the first paging group. The second network entity transmits a paging group identification corresponding to the paging group to which it belongs through a paging message. If the cell coverage area is designed such that the network entity belongs to only one paging group, it is possible to transmit the paging group identification of neighboring paging groups, for example.

  After receiving a paging message with a different paging group identification, the MSS requests a location update from the second network entity through an RNG-REQ message (step S270). In addition to the location update request, the RNG-REQ message may be used to identify the first network entity that allows MSS to enter idle mode, the paging group identification of the second paging group, a predetermined paging cycle, etc. Other information can be included. If the cell coverage area is designed so that a network entity only belongs to one paging group, the MSS cannot receive paging messages through the previous paging information when moving to another paging group, for example new Request a location update for a network entity.

  After receiving the location update request from the MSS, the second network entity transmits a request to the first network entity to transmit the selected session information currently held by the first network entity. (Step S280). The first network entity transmits the currently held selected session information to the second network entity at every request (step S290).

  The second network entity transmits the list of session information held by the MSS through the RNG-RSP message even after the location of the MSS is updated (step S300). The RNG-RSP message has other information such as the second paging group identification and the corresponding paging cycle and paging offset value. As a result, the corresponding MSS can receive the paging message with the second paging group identification. Further, the second network entity transmits the session information currently held by the second network entity to the MSS through the RNG-RSP message. As a result, when the MSS performs a re-entry into the network, any procedural steps required for re-entry into the network can be skipped. In other words, since the second network entity holds arbitrary MSS service and operational information, the same information is not required upon re-entry into the network. At the same time, the MSS receives via the RNG-RSP message a procedural step that can be skipped by the MSS when the network re-enters.

  After receiving the session information held from the first network entity through the RNG-RSP message, the MSS may perform the network entry procedure necessary to update information that is no longer valid or updated. Yes (step S310). The second network entity notifies the other network entities of the first paging group using the backbone network that the MSS will be reassigned to another paging group, and deletes information about the MSS (steps). S320). At the same time, the second network entity informs the network entity of the second network paging group that it has added information associated with the MSS through the backbone network. In the MSS, the MSS receives a paging message at a specific interval from the second paging group and maintains the idle mode (step S330).

  As described above, when the location of the MSS is updated from the first network entity to the second network entity, downlink data destined for the MSS is received by the second network entity, and the first network Update the location of MSS that are not entities.

  FIG. 5 illustrates a signaling process according to another embodiment of the present invention. Here, the downlink traffic exists in the environment where the MSS enters as a result of the command by the network entity to the MSS for the MSS to enter the idle mode through the DREG-CMD message.

  In this embodiment, the network entity instructs the MSS to enter the idle mode, unlike the previous embodiment in which the MSS transmits a request for the network entity to enter the idle mode. Here, the command for entering the idle mode is transmitted through the DREG-CMD message. The DREG-CMD includes an action code set at 0x05 and a required duration (REQ-duration) that specifies the time for the MSS to enter idle mode.

  In particular, the first network entity requests the MSS to transmit MSS priority session information through a DREG-CMD message. The DREG-REQ includes a specific time for transmitting the requested message by the MSS. After receiving the DREG-CMD from the first network entity, the MSS transmits MSS priority session information requested at a specific time for the first network to the network entity through a DREG-REQ message (step S420). The MSS priority session information includes information such as security information, IP address information, MSS capability, management connection identification, and information essential for maintaining network service. MSS priority session information is a list of session information that the MSS prioritizes that the network entity retains for facilitated future re-entry into the network.

  As described above, the identification of the first network entity and the second network entity has been described with reference to FIG. After receiving the solicitation message, the first network entity broadcasts a notification through the backbone channel to all other network entities having the same paging identity in the paging group, thereby sending the corresponding MSS in each paging group. To the network entity (step S430). Thereafter, in response to the request message, the first network entity transmits the selected session information through the DREG-CMD to the corresponding MSS (step S440). Selected session information includes any MSS service and operational information useful for facilitating future MSS network re-entry from idle mode. The selected session information is a list of selected session information that is the same as, or different from, or a combination of the priority session information requested by the MSS. Also, other information such as paging cycle, paging offset and paging identification may be included in the transmission of DREG-CMD. DREG-CMD is a command or message that allows the MSS to enter the requested idle mode.

  When the MSS receives the DREG-CMD from the second network entity, it enters the idle mode. During the idle mode, the MSS can receive a paging message at a specific time slot or interval from the first network entity (step S450). The paging message includes various information such as whether there is any downlink traffic or when exiting idle mode.

  While in idle mode, the MSS can move to another network entity (hereinafter “second network entity”) within a paging group with the same paging group identity or within a paging group with multiple paging group identity It is. If the MSS moves to a second network entity in the same paging group with the same paging identity (step S460), the MSS from the paging message and the first network entity in the same paging cycle from the second network entity. The received paging offset is received (step S470).

  When downlink traffic reaches the first network entity and when the first network entity notifies the downlink traffic to the MSS (step S480), the first network entity is down through the backbone network. Session information together with the presence of link traffic is transmitted to other network entities in the paging group (step S490). Here, the selected session information transmitted to the other network entities in the paging group through the backbone channel is a list of the selected session information.

  After receiving the selected session information from the first network entity, the second network entity transmits a paging message including the selected session information and the presence of downlink traffic to the MSS (step S550). The MSS transmits the identification of the first network entity that allows the MSS to enter the idle mode to the second network entity through the RNG-REQ message (step S510).

  After the second network entity receives the identification of the first network entity, the corresponding MSS session in which the MSS is located in the coverage area and the first entity is held by the first network entity The first network entity is notified that information transmission is requested (step S520).

  The first network entity responds to the request by transmitting the session information held through the backbone channel (step S530). Also, the second network entity transmits a list of session information currently held by the second network entity to the MSS through the RNG-RSP message (step S540). As a result, any procedural steps required for re-entry into the network can be skipped when the MSS performs re-entry into the network. In other words, the same information is not required for re-entry into the network because the second network entity holds any MSS service and operational information. At the same time, the MSS receives via the RNG-RSP message a procedural step that can be skipped by the MSS when the network re-enters.

  Based on the information provided by the second network entity, a network entity or re-entry procedure is performed (step S550). The network registration procedure stage includes, for example, MSS capability negotiation procedures, security procedures, registration procedures, IP address acquisition procedures, and the like. In addition, in order to establish a connection for receiving data, the MSS performs necessary procedures in combination with the network entry procedure. After the procedures for network entry (or re-entry) and data reception are completed, the second network entity transmits the downlink data received from the first network to the MSS (step S560).

  Steps S410-S560 describe the operation in the network when downlink traffic exists during idle mode. If uplink traffic occurs for the MSS in idle mode, the optional steps S480, S490, S500, and S560 are excluded from operation.

  FIG. 6 illustrates a signaling process according to another embodiment of the present invention. Here, the downlink traffic exists in the environment where the MSS enters as a result of the command by the network entity to the MSS in order for the MSS to enter the idle mode through the DREG-CMD message. This embodiment also describes the process associated with updating the location of the MSS in idle mode after the MSS has moved to another paging group.

  In this embodiment, the network entity instructs the MSS to enter the idle mode, unlike the previous embodiment in which the MSS transmits a request for the network entity to enter the idle mode. Here, the command for entering the idle mode is transmitted through the DREG-CMD message. The DREG-CMD includes an action code set at 0x05 and a required duration (REQ-duration) that specifies the time for the MSS to enter idle mode.

  In particular, the first network entity requests the MSS to transmit MSS priority session information through a DREG-CMD message. The DREG-REQ includes a specific time for transmitting the requested message by the MSS. After receiving the DREG-CMD from the first network entity, the MSS transmits the MSS priority session information requested at a specific time for the first network to the network entity through the DREG-REQ message (step S620). The MSS priority session information includes information such as security information, IP address information, MSS capability, management connection identification, and information essential for maintaining network services. MSS priority session information is a list of session information that the MSS prioritizes that the network entity retains for facilitated future re-entry into the network.

  As described above, the identification of the first network entity and the second network entity has been described with reference to FIG. After receiving the solicitation message, the first network entity broadcasts a notification through the backbone channel to all other network entities having the same paging identity in the paging group, thereby sending the corresponding MSS in each paging group. To the network entity (step S630). Thereafter, the first network entity transmits the selected session information through the DREG-CMD to the corresponding MSS in response to the request message (step S640). Selected session information includes any MSS service and operational information useful for facilitating future MSS network re-entry from idle mode. The selected session information is a list of selected session information that is the same as, or different from, or a combination of the priority session information requested by the MSS. Also, when transmitting DREG-CMD, other information such as paging cycle, paging offset and paging identification may be included. DREG-CMD is a command or message that allows the MSS to enter the requested idle mode.

  When receiving DREG-CMD from the first network entity, the MSS enters idle mode. During the idle mode, the MSS may receive a paging message at a specific time slot or interval from the first network entity (step S650). The paging message includes various information such as whether there is any downlink traffic or when exiting idle mode.

  While in idle mode, the MSS can move to another network entity (hereinafter “second network entity”) within a paging group with the same paging group identity or within a paging group with multiple paging group identity It is. If the MSS moves to a second network entity in the same paging group with the same paging identity (step S660), the MSS from the paging message and the first network entity from the second network entity in the same paging cycle. The received paging offset is received (step S670).

  If the cell coverage area is designed so that a network entity only belongs to one paging group, the network entity that moves to a paging group that includes one or more paging group identifications, for example, between two paging groups Refers to network entities when transitioning in.

  The MSS also learns that the second network entity belongs to a second paging group having a different paging group identification than the first paging group. The second network entity transmits a paging group identification corresponding to the paging group to which it belongs through the paging message. If the cell coverage area is designed such that the network entity belongs to only one paging group, it is possible to transmit the paging group identification of neighboring paging groups, for example.

  After receiving a paging message with a different paging group identification, the MSS requests a location update from the second network entity through an RNG-REQ message (step S680). In addition to the location update request, the RNG-REQ message can be used to identify the first network entity that allows the MSS to enter idle mode, the paging group identification of the second paging group, a predetermined paging cycle, etc. Other information can be included. If the cell coverage area is designed so that the network entity belongs to only one paging group, the MSS cannot receive paging messages through the previous paging information when moving to other paging groups, for example, new Request a location update for a network entity.

  After receiving the location update request from the MSS, the second network entity transmits a request to the first network entity to transmit the selected session information currently held by the first network entity. (Step S690). The first network entity transmits the currently held selected session information to the second network entity at each request (step S700).

  The second network entity transmits the list of session information held by the MSS through the RNG-RSP message even after the location of the MSS is updated (step S710). There is other information in the RNG-RSP message such as the second paging group identification, the corresponding paging cycle and paging offset value. As a result, the corresponding MSS can receive the paging message with the second paging group identification. In addition, the second network entity transmits the session information currently held by the second network entity to the MSS through the RNG-RSP message. As a result, when the MSS performs a re-entry into the network, any procedural steps required for re-entry into the network can be skipped. In other words, the same information is not required for re-entry into the network because the second network entity holds any MSS service and operational information. At the same time, the MSS receives via the RNG-RSP message a procedural step that can be skipped by the MSS when the network re-enters.

  After receiving the session information held from the second network entity through the RNG-RSP message, the MSS can perform the necessary network entry procedure to update the information that is no longer valid or not updated. (Step S720). The second network entity notifies the other network entities of the first paging group using the backbone network that the MSS will be reassigned to the other paging group and deletes the information related to the MSS. (Step S730). At the same time, the second network entity informs the network entity of the second network paging group that it has added information associated with the MSS through the backbone network. In the MSS, the MSS receives a paging message from the second paging group at a specific interval and maintains the idle mode (step S740).

  As described above, when the location of the MSS is updated from the first network entity to the second network entity, downlink data destined for the MSS is received by the second network entity and the first network entity is Update the location of the non-tee MSS.

  The above description relates to network entities and MSS operations / procedures during network entry for idle mode, including updated session information that facilitates MSS re-entry from idle mode. Hereinafter, an operation of the MSS before entering the idle mode for efficiently receiving downlink traffic during the idle mode will be described.

  During normal mode, the MSS link layer address (eg, MAC address or Ethernet address) is searched to transmit data to the MSS using the router destination or target IP address. To accomplish this, a router address request is transmitted to the network entity. Here, the router transmits an ARP request using IP version 4 (IPv4), and transmits a neighbor solicitation using IP version 6 (IPv6).

  In one embodiment of the present invention, after the network entity receives the address solicitation message from the router, the network entity broadcasts to multiple MSSs or transmits the address solicitation message to each MSS individually. Thereafter, the network entity receives a response message from the MSS, eg, an ARP response message or a neighbor advertisement response message, and transmits the response message to the router. The address request message includes, for example, a MAC address or an Ethernet (registered trademark) address. The MAC or Ethernet (registered trademark) address of the MSS can be matched with the MAC or Ethernet (registered trademark) address included in the address request message from a plurality of MSSs that receive the address request message. The MSS with the matched MAC address transmits a response message to the network entity through a secondary management connection or a general data burst.

  Also, in one embodiment of the present invention, the network entity may transmit the MSS proxy ARP response message (or proxy neighbor notification) to the router in sleep / idle mode. In other words, the network entity can immediately respond to the request by the router, for example as an agent of the MSS. At the network entity that responds to the router, the MSS includes its IP address in a MOB-SLP-REQ message or DREG-REQ message and transmits it to the network entity. The MSS also provides its IP address to the network entity before entering sleep / idle mode when entry to sleep / idle mode is requested by the network entity. The embodiment of the present invention is not limited to IPv4 but can be applied to IPv6 using the ND protocol.

  In an embodiment of the present invention, the network entity has data transmitted to the network entity while the MSS is in sleep mode or idle mode using a proxy ARP or proxy ND protocol. As described above, the network entity is a base station, paging controller, access gateway or base station controller. In the drawing, a base station (BS) is used as an example of a network entity for explaining the embodiment. In previous embodiments, the network entity transmits an ARP or ND related message to the MSS. In the process, data cannot reach the destination MSS if the MSS is in sleep or idle mode. However, in this embodiment, the network entity can directly respond to the ARP request or the neighbor request from the router. To that end, the network entity must handle the MSS IP address and link layer address (MAC address or Ethernet address).

  The network entity obtains the MSSIP address and the link layer address when registering with the network entity to own the address, for the MSS to enter sleep or idle mode, or by retrieving the MSSIP address configuration can do. In particular, the network entity can obtain an IP address by receiving the IP address directly from the MSS when the MSS transmits the IP address through the request message. In addition, the network entity can obtain an IP address by an MSS that requests use of the IP address currently held by the network entity. In other words, the MSS maintains the IP address held by the network entity without transmitting the IP address. The network entity can also obtain information by directly requesting the MSS for IP and link layer addresses.

  FIG. 7 illustrates the router link layer address acquisition process when the MSS voluntarily enters sleep mode. Referring to FIG. 7, the MSS transmits a MOB-SLP-REQ message to the network entity to request entry into the sleep mode (step S3-0). The MSS includes in its solicitation message its IP address that allows it to respond to possible future ARP solicitations from the router. In response to the request, the network entity transmits a MOB-SLP-RSP message to the MSS (step S3-1).

  When receiving a response message from the network entity, the MSS enters sleep mode for the duration specified in the MOB-SLP-RSP message. After the sleeping interval, the MSS wakes up for the listening interval (L1) and receives a MOB-TRF-IND message from the network entity to determine whether any downlink data is received. If no downlink data is received, the MSS re-enters sleep mode for an increased sleeping interval (2 * N1). Here, the sleeping interval increases by a specific amount (ie, twice the previous sleeping interval) after the listening interval.

  FIG. 8 illustrates the router link layer address acquisition process when the MSS enters sleep mode as a result of a command from a network entity. Referring to FIG. 8, this process is similar to FIG. However, in FIG. 8, the MSS IP address is not provided through the request message, but the MSS IP address is transmitted through the information message because the entry to the sleep mode is determined by the network entity. After the MSS receives the DREG-CMD message to enter idle mode, the process of transmitting the DREG-REQ message and the DREG-RSP message can be repeated. In this case, the MSS IP address is transmitted through a DREG-REQ message.

  FIG. 9 shows the router link layer address acquisition process when the MSS voluntarily enters idle mode. In FIG. 9, the MSS transmits a DREG-REQ message to the first network entity to enter the idle mode, and the first network entity transmits a DREG-CMD message in response to the MSS. Is allowed to enter the sleep mode (step S4-0). The MSS includes the IP address for the first network entity in the DREG-REQ message so that the BS can respond to the router's ARP request without referring to the MSS when in the idle mode.

  After the MSS is deregistered from the first network entity (or host BS), the first network entity broadcasts to all other BSs in the same paging zone where the MSS enters idle mode (step S4). -1). A BS receiving a broadcast adds MSS information to its paging list.

  When the router receives the IP packet, the router transmits an ARP request to the host BS to determine the MAC access of the destination IP address of the MSS (step S4-2). When responding, since the host BS has the essential IP address information of the MSS, it transmits an ARP response message to the MSS router (step S4-3).

  When receiving the ARP reply message, the router transmits the IP packet to the host BS. Thereafter, the host BS transmits a paging announcement notifying that there is downlink data for the MSS to all BSs in the paging zone (step S4-4). After receiving the paging announcement, the BS having the MSS in the cell coverage area transmits a paging message to the MSS in a specific paging cycle (step 4-5).

  FIG. 10 shows another embodiment of the present invention. FIG. 10 illustrates the router link layer address acquisition process when the MSS enters sleep mode as a result of a command from the network entity. Referring to FIG. 10, the process of communicating between the MSS and the network entity is similar to FIG. However, in FIG. 10, the MSSIP address is transmitted through the information message because the network entity determines the entry into the sleep mode without providing the MSSIP address through the request message. It is possible to repeat the process of transmitting the DREG-REQ message and the DREG-RSP message after the MSS receives the DREG-CMD message in order to enter idle mode. In this case, the MSSIP address is transmitted through a DREG-REQ message.

  In another embodiment of the present invention, the MSS makes a request to the network entity to maintain CS (Convergence Sublayer) information. CS is a two layer protocol responsible for collecting and forming higher layer information that can typically be processed by the lower layer.

  FIG. 11 illustrates another embodiment of the router link layer address acquisition process when the MSS voluntarily enters idle mode. Referring to FIG. 11, the operation and process of the present embodiment are similar to the process of FIG. Therefore, the description regarding the same process as the embodiment of FIG. 9 is omitted.

  In this embodiment, the MSS transmits a DREG-REQ message to the first network entity to enter the idle mode, and the first network entity responds by causing the MSS to enter the sleep mode. A DREG-CMD message is transmitted so as to allow entry (step S5-0). The MSS includes a request for holding CS (convergence subscriber) information in the DREG-REQ message. Since the first network entity holds the CS information, the first network entity does not need to contact the MSS in the idle mode in connection with the downlink traffic, so that it can respond to the request from the router. it can. In fact, downlink traffic can be transmitted more efficiently and network resources can be better utilized. As described above, the other processes are the same as those in FIG.

  FIG. 12 shows another embodiment of the present invention. In this embodiment, a router link layer address acquisition process is shown when the MSS enters sleep mode as a result of a command from a network entity. Referring to FIG. 12, the process of communicating between the MSS and the network entity is similar to the process of FIG. However, in FIG. 12, without providing the MSS IP address through the request message, the MSS transmits the request message to the first network entity and holds the CS information. Such a request can be transmitted through an information message or a DREG-REQ message. The other processes are the same as in FIG.

  Although the present invention has been described in connection with specific embodiments, various changes in form and detail depart from the spirit and scope of the invention as defined by the appended claims. It is clear to those having ordinary knowledge in the art that it can be done without doing so. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be determined based on the description of the scope of claims and equivalents thereof.

FIG. 6 is a diagram illustrating an MSS that returns to a normal mode in order to end idle mode and receive downlink traffic. FIG. 6 is a diagram illustrating an MSS that returns to a normal mode in order to end a sleep mode and receive downlink traffic. FIG. 5 shows a signaling process when MSS bound downlink traffic occurs during idle mode. FIG. 6 is a diagram illustrating a signaling process when an MSS requests to enter an idle mode and requests a network entity to hold session information. FIG. 7 is a diagram illustrating a signaling process when a network entity instructs an MSS to enter an idle mode and the MSS requests a network entity to hold session information. FIG. 6 is a diagram illustrating a signaling process of location update from one paging group to another paging group by MSS. FIG. 6 is a diagram illustrating a router link layer address acquisition process when an MSS voluntarily enters a sleep mode. FIG. 7 illustrates a router link layer address acquisition process when an MSS enters sleep mode as a result of a command from a network entity. FIG. 6 is a diagram illustrating a router link layer address acquisition process when an MSS voluntarily enters an idle mode. FIG. 7 illustrates a router link layer address acquisition process when an MSS enters sleep mode as a result of a command from a network entity. FIG. 7 is a diagram illustrating a router link layer address acquisition process when an MSS voluntarily enters an idle mode according to another embodiment of the present invention. FIG. 7 is a diagram illustrating a router link layer address acquisition process when an MSS enters a sleep mode as a result of a command from a network entity according to another embodiment of the present invention;

Claims (86)

A method of communicating data to enter idle mode,
Transmitting a request by mobile sub BScriber station (MSS) to the network entity through a deregistration request message for requesting the network entity, and maintaining priority session information;
Receiving selected session information through a deregistration command response from the network entity;
A method comprising the steps of:   The method of claim 1, wherein the priority session information is a list of priority session information.   The method of claim 1, wherein the network entity is a base station that seeks the MSS to enter idle mode.   The method of claim 1, wherein the network entity is a serving base station.   The method of claim 4, wherein the serving base station transmits the selected session information to a plurality of base stations or paging controllers in a paging group.   The method of claim 4, wherein the serving base station performs the idle mode activity for the MSS.   The method of claim 4, wherein the paging controller performs the idle mode activity for the MSS.   The method of claim 1, wherein the network entity is a paging controller.   The method of claim 8, wherein the paging controller transmits the selected session information to a plurality of network entities in the paging group.   The method of claim 9, wherein the plurality of network entities are a plurality of base stations.   The method of claim 8, wherein the paging controller performs the idle mode activity for the MSS.   The method of claim 1, wherein the deregistration request message includes a request by the MSS to exit normal mode and enter idle mode.   The method of claim 1, wherein the selected session information includes session information selected by the network entity.   The method of claim 13, wherein the selected session information is a list of session information maintained by the MSS and the network entity in idle mode.   The method of claim 1, further comprising receiving a deregistration command message from the network entity.   The method of claim 15, wherein the deregistration command message includes a request to transmit the deregistration request message to the MSS.   The method of claim 16, wherein the request indicates a specific time for the MSS to transmit the deregistration request message. A method of communicating data to enter idle mode,
Receiving a request from the MSS through a de-registration request message requesting the network entity and retaining priority session information;
Transmitting selected session information through a deregistration command response from the network entity;
A method comprising the steps of: Transmitting a request by the MSS to a network entity through a deregistration request message requesting the network entity to hold priority session information;
The method of claim 18, further comprising receiving selected session information from the network entity through a deregistration command response.   The method of claim 18, further comprising receiving a deregistration command message from the network entity. A communication system,
An MSS (mobile sub BScriber station) that transmits a request to the network entity through a de-registration request message for requesting a network entity, retains priority session information, and receives selected session information from the network entity through a de-registration command. The communication system characterized by including. Further including a network entity,
The network entity receives a request from the MSS through a deregistration request message requesting the network entity, holds priority session information, and transmits selected session information from the network entity through a deregistration command response. The communication system according to claim 21. A method of communicating with a network entity to update the location of an MSS, comprising:
Transmitting a request from the first network entity to the second network entity through an RNG-REQ (Ranging-Request) message requesting location update of the MSS;
Receiving selected session information updated through a response message from the second network entity;
Performing a network entity procedure to update session information after the location of the MSS is updated from the first network entity to the second network entity;
A method comprising the steps of:   The method of claim 23, wherein the first network entity is a network entity in which the MSS enters an idle mode.   The method of claim 23, wherein the first network entity and the second network entity are base stations or paging controllers.   The method of claim 23, further comprising transmitting an RNG-REQ message to the second network entity by the MSS.   27. The method of claim 26, wherein the RNG-REQ message includes an identification of the first network entity that the MSS enters idle mode.   The method of claim 23, wherein the selected session information is displayed by a list of session information.   29. The method of claim 28, wherein the session information is updated by the MSS and the second network entity.   The method of claim 28, wherein the second network entity is a base station or a paging controller.   29. The method of claim 28, wherein the session information list includes a network entry procedure for the MSS to enter a network.   The method of claim 31, wherein the network entry procedure includes updating the selected session information and the first network entity held in the MSS.   The method of claim 23, further comprising receiving a paging message from the second network entity.   The method of claim 33, wherein the paging message includes an identification of the MSS.   The method of claim 34, wherein the paging message further comprises an action code of the MSS that causes the MSS to perform a location update. A method of communicating with the MSS to update the location of the MSS, comprising:
Receiving a request from the MSS to the second network entity through an RNG-REQ message requesting an update of the location of the MSS from the first network entity;
Transmitting selected session information updated through a response message from the second network entity to the MSS;
Performing a network entry to update session information after the location of the MSS is updated from the first network entity to the second network entity;
A method comprising the steps of: A communication system including an MSS,
The MSS transmits a request to the second network entity through an RNG-REQ message requesting an update of the location of the MSS from the first network entity;
Receiving selected session information updated through a response message from the second network entity;
A communication system, wherein after the location of the MSS is updated from the first network entity to the second network entity, a network entry is performed to update session information. Further comprising at least one network entity;
The network entity receives a request from the MSS to the second network entity through an RNG-REQ message requesting the location update of the MSS from the first network entity;
Transmitting selected session information updated through a response message from the second network entity to the MSS;
38. The record of claim 37, wherein after the location of the MSS is updated from the first network entity to the second network entity, a network entry is performed to update session information. Communication system. A method of communicating with a network entity to enter a network,
Transmitting the request to the second network entity through an RNG-REQ message;
Receiving the selected session information through a RNG-RSP (Ranging-Response) message from a second network entity, wherein the selected session information is transmitted from the first network entity to the second network entity; Steps received by
Entering the network of the second network entity;
A method comprising the steps of:   The method of claim 39, wherein the first network entity maintains the latest updated session information of the MSS.   40. The method of claim 39, wherein the first network entity and the second network entity are base stations or paging controllers.   40. The method of claim 39, wherein the second network entity is a base station or a paging controller.   40. The method of claim 39, wherein the second network entity is a network entity that pursues the MSS to enter idle mode.   40. The method of claim 39, wherein the RNG-REQ message includes an identification of the first network entity that the MSS enters idle mode.   40. The method of claim 39, wherein the selected session information is displayed by a list of session information.   The method of claim 45, wherein the session information is updated by the MSS and the second network entity.   The method of claim 45, wherein the second network entity is a base station or a paging controller.   The method of claim 45, wherein the session information list includes a network entry procedure for the MSS to enter a network.   49. The method of claim 48, wherein the network entry procedure includes updating the selected session information and the second network entity held in the MSS.   40. The method of claim 39, further comprising receiving a paging message from the second network entity.   40. The method of claim 39, wherein the paging message includes an identification of the MSS.   52. The method of claim 51, wherein the paging message further includes an action code for the MSS that causes the MSS to perform a location update. A method of communicating with an MSS to enter a network,
Receiving a request from the MSS through an RNG-REQ message;
Transmitting the selected session information to the MSS through an RNG-RSP message, wherein the selected session information is received by the second network entity from a first network entity;
Allowing the MSS to enter the network of the second network entity;
A method comprising the steps of: A communication system including an MSS,
The MSS transmits a request to the second network entity through an RNG-REQ message;
Receiving selected session information from a second network entity through an RNG-RSP message, wherein the selected session information is received by the second network entity from a first network entity;
When entering the network of the second network entity,
A communication system comprising: Further comprising at least one network entity;
The network entity receives a request from the MSS through an RNG-REQ message;
Transmitting selected session information to the MSS through an RNG-RSP message, wherein the selected session information is received by the second network entity from a first network entity;
55. The communication system according to claim 54, wherein the MSS is allowed to enter the network of the second network entity. Was a method of communicating data in a wireless broadband communication system,
Transmitting a request to retain a network address through a request message to a first network entity;
Entering an idle mode after receiving a response message from the first network entity;
Receiving a paging message from a second network entity during idle mode;
Entering the network of the second network entity;
Receiving an IP packet from the second network entity;
A method comprising the steps of:   57. The method of claim 56, wherein the network address is an IP address.   The method of claim 56, wherein the request message is a DREG-REQ (de-registration request) message.   The method of claim 56, wherein the request message includes a request by the MSS to enter idle mode.   The method of claim 56, wherein the request message includes an IP address of the MSS for providing directly to the first network entity.   57. The method of claim 56, wherein the request message includes a request for the first network entity to hold an IP address of the MSS.   57. The method of claim 56, wherein the response message is a DREG-CMD (de-registration commnd) message.   The method of claim 56, wherein the response message includes a command for the MSS to enter idle mode.   The method of claim 56, wherein the paging message notifies the MSS of downlink data.   The method of claim 64, wherein the downlink data is the IP packet.   57. The method of claim 56, wherein at least one of the first network entity and the second network entity is a base station, a paging controller, an access gateway, or a base station controller. the method of.   The method of claim 66, wherein the paging controller maintains any MSS service and operational information useful in facilitating future MSS network re-entry from idle mode.   57. The method of claim 56, further comprising a first network entity that communicates with a router to communicate the IP packet to the first network entity.   69. The method of claim 68, wherein the destination address of the IP packet is an MSS IP address held in the first network entity.   The router transmits an ARP (address resolution protocol) request for obtaining a link layer address of an IP packet destination to the first network entity, and in response thereto, the first network entity transmits the MSS. 69. The method of claim 68, wherein an ARP response to is transmitted to the router.   The router transmits a neighbor solicitation to the first network entity to obtain a link layer address of an IP packet destination, and the first network entity transmits a neighbor advertisement for the MSS to the router. 69. The method of claim 68.   69. The method of claim 68, wherein the first network entity broadcasts the MSS ARP response to a plurality of network entities.   The method of claim 68, wherein the first network entity broadcasts the MSS neighbor advertisement to a plurality of network entities.   74. A method according to claim 72 or claim 73, wherein at least one of the network entities is a base station, a paging controller, an access gateway, or a base station controller.   The method of claim 74, wherein the paging controller maintains any MSS service and operational information useful in facilitating future MSS network re-entry from idle mode. A method for communicating data in a wireless broadband communication system, comprising:
Receiving from the MSS a request to retain a network address through a request message to a first network entity;
Allowing the MSS to enter idle mode by transmitting a response message from the first network entity to the MSS;
Transmitting a paging message from the second network entity during idle mode;
Allowing the MSS to enter the network of the second network entity;
Transmitting an IP packet from the second network entity to the MSS;
A method comprising the steps of: A wireless broadband communication system including MSS,
The MSS transmits a request for holding a network address to the first network entity through a request message;
After receiving a response message from the first network entity, enter idle mode;
Receiving a paging message from the second network entity during idle mode;
Entering the network of the second network entity,
A communication system, wherein an IP packet is received from the second network entity. Receiving a request from the MSS to retain the network address through the request message to the first network entity;
Allowing the MSS to enter idle mode by transmitting a response message from the first network entity to the MSS;
Transmitting a paging message from the second network entity during idle mode;
Allowing the MSS to enter the network of the second network entity;
Transmitting an IP packet from the second network entity to the MSS;
The communication system of claim 77, further comprising at least one network entity. A method for communicating data in a wireless broadband communication system, comprising:
Transmitting a request to hold CS (convergence subscriber) information to the first network entity through a request message;
Entering an idle mode after receiving a response message from the first network entity;
Receiving a paging message from the second network entity while in idle mode;
Entering the network of the second network entity;
Receiving a data packet from the second network entity;
A method comprising the steps of:   The method of claim 79, wherein the CS information includes an IP address.   80. The method of claim 79, wherein the CS information includes service flow related information.   The method of claim 81, wherein the service flow related information includes a priority service flow for the MSS received during idle mode.   80. The method of claim 79, wherein the data packet corresponds to the CS information held in the first network entity. A method for communicating data in a wireless broadband communication system, comprising:
Receiving a request for holding CS (convergence subscriber) information from the MSS to the first network entity through a request message;
Allowing entry into idle mode after transmitting a response message from the first network entity to the MSS;
Transmitting a paging message from a second network entity to the MSS during idle mode;
Allowing the MSS to enter the network of the second network entity;
Transmitting a data packet from the second network entity to the MSS;
A method comprising the steps of: A wireless broadband communication system including MSS,
The MSS transmits a request for holding CS information to the first network entity through a request message;
After receiving a response message from the first network entity, allowing entry into idle mode;
Receiving a paging message from the second network entity during idle mode;
Entering the network of the second network entity,
A communication system, wherein a data packet is received from the second network entity. Receiving a request from the MSS to hold the CS information through the request message to the first network entity;
Allowing to enter idle mode after transmitting a response message from the first network entity to the MSS;
Transmitting a paging message from the second network entity to the MSS during idle mode;
Allowing the MSS to enter the network of the second network entity;
86. The communication system of claim 85, further comprising at least one network entity that transmits data packets from the second network entity to the MSS.

Images