TW200803370A - Wireless communication method and system for activating multiple service bearers via efficient packet data protocol context activation procedures - Google Patents

Abstract

A method and apparatus for executing attachment procedures in a long term evolution (LTE) system to accommodate a single tunnel approach. Third Generation Partnership Program (3GPP) packet data protocol (PDP) context activation procedures are used for the allocation of an Internet protocol (IP) address and the establishment of tunneling between an evolved Node-B (eNodeB) and an anchor node, while allowing multiple radio access bearers (RABs) to be mapped to one PDP context for different quality of service (QoS) requirements. Thus, one PDP context is sufficient for a wireless transmit/receive unit (WTRU) within a single packet data network (PDN). Multiple PDP contexts can be established for special requirements, (e.g., bundled services), or when the WTRU connects to multiple PDNs.

Description

200803370 IX. DESCRIPTION OF THE INVENTION: TECHNICAL FIELD OF THE INVENTION The present invention is primarily related to wireless communication systems. More particularly, the present invention uses a single secondary packet data protocol in a 3rd Generation Partnership Project (3GPP) system (ie, General Packet Radio Service (GPRS) and Universal Mobile Telecommunications System) and Long Term Evolution (LTE) systems ( PDP) Context Initiator to initiate a method and apparatus for multiple service bearers. In GPRS and LTE systems, the program can be implemented in GPRS dual tunnel mode and through tunnel mode. [Prior Art] Usually 'cellular networks are designed only for voice services. GPRS supports certain types of data services, such as text messaging and email. However, more data services and multimedia services are currently being introduced as applications running on cellular networks, such as over the Internet Protocol Voice over IP (VoIP), Internet Protocol (IP) television (IPTV), etc. . Mobile phones are moving from voice service phones to integrated data center devices, and cellular networks are also targeting the next-generation all-ip network and packet services/becomings with IP Multimedia Sub-System (IMS) infrastructure. In addition to the need for a more data rate, cellular networks also need to implement the architecture to more effectively support the changes required for IP applications and packet-switched (PS) dirty tasks (ie, reducing the delays caused by the re-establishment of the eye-catching process). Delay in service data service due to excessive processing on different network nodes). 1 to 3 show the signal mode in the conventional wireless communication system, wherein the system 1 includes a wireless transmitting/receiving unit (wiu) 1〇5, a radio access network (RAN) 11〇 , bribe general packet radio return (GpRS) 6 200803370 support node (SGSN) 115 and gateway GPRS support node (ggSN) 12〇. For 3GPPPS services, a Packet Data Protocol (PDp) context is associated with a Radio Access Bearer (RAB). Therefore, as shown in Figures 1 to 3, in order to support multiple services, it is necessary to enable these services using a primary PDP context initiation and multiple secondary PDP context initiators, and this is done in 3GPP^ Specification (TS) 23.060. description. For example, for data users who want to connect to IMS-based services (ie, VoIP, multimedia, etc.) and start services such as Web browsing, email services, fax services, etc. at the same time, the user must Each service performs a separate PDp context startup. The user may wait a considerable amount of time before all services are running, which is similar to waiting for a computer boot. It is seen that for 3GPP PS services, a PDP context is associated with an RAB. Thus, as shown in Figures 1 and 2, in order to support multiple services, it is necessary to initiate a primary context and multiple secondary PDP contexts. In addition, in order

Supporting MS services, the primary PDP context for Session Initiation Protocol (SIP) signaling and the secondary context for each data service (to be started) are always required. SUMMARY OF THE INVENTION The present invention provides a method and apparatus for 3GPP system (ie, gprs, UMTS) and LTE systems, which can reduce service establishment and slave network due to multiple sequences. Over-the-counter rewards for different nodes in the road! 峨 Processing delay _. The present invention proposes a simplified auxiliary PDP context initiation procedure that can initiate several side tasks in a single sigma. The present invention also has the current 3GPP PDP context 200803370

The initiator is re-used to allocate ip addresses, initiate services, and establish tunneled transport between different elements within the network (ie, RAN, SGSN, GGSN, IMS, etc.). In addition, the present invention allows multiple PDP contexts to be initiated using a single step of assisted PDP context initiation, where each service is associated with a particular service bearer in the core network (CN) and a particular RAN in the RAN. In addition, the present invention also allows for the establishment of multiple RABs mapped to a PDp context for different QoS requirements. Multiple PDP contexts may be established either for a particular need (e. g., a homegrown service) or when the WTRU is connected to multiple PDNs. The present invention reduces the delay in assisting PDP context initiation and reduces the modifications that are required when more services are needed. For example, a user may configure a personal digital assistant (PDA) terminal to initiate a v〇ip service, video conferencing, email account, etc., when the pDA terminal is powered on. According to the current procedure in Ts 23〇6〇, the WTRU performs each procedure individually and sequentially. The present invention reduces the unnecessary steps used in initiating the secondary PDP context class. The WTRU may request an additional bearer by sending a request to the RAN (e.g., eN〇deB), which will then check the request for additional information. Whether the bearer is adapted or not has been _ current PDP on the T text (also transferred). # When an additional bearer can be added, the eNodeB forwards the request to the Mobility Management Entity (MME) for further inspection. The monthly shout type of the request determines if a secondary PDP context is required. The context provided by the different PDNs at different anchor nodes is required if the requested job is. If the requested lin is provided by the same _ node, the MME forwards the service request to the erroneous 200803370 point to allocate the necessary resources and the network layer service access point identifier requested by the WTRU. (NSAPI) maps to the new service bearer. The anchor node is then informed of the tunnel endpoint identification code (ΤΚΤΠ) of the supporting eNodeB in the process. After receiving the response, the other endpoint of the channel is established by sending a RAB setup request to the eNodeB, where the endpoint is updated with the anchor node. The MME then requests the WTRU to update its RAB resources. The WTRU then responds with a completion notification to the eNodeB, which in turn informs the MME that the process has completed successfully. If an error or timer expires on the MME, the MME will continue to release the previously allocated tunnels and resources. The reason why the present invention is superior to the prior art is that: 1) several bearers are allocated within the main PDP context; 2) single tunnel if establishes a dual tunnel (new architecture) relative to 3GPP (GPRS); 3) the number of steps is reduced ( The auxiliary PDP startup is merged with the RAB setup request). [Embodiment] As referred to hereinafter, the term "wireless transmitting/receiving unit (w^u), includes but not a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a mobile phone, Personal digital assistant (PDA), computer or any other type of user equipment capable of operating in a wireless environment. As mentioned below, the term "base station" includes but is not limited to a Node B state, but a site controller, An access point (AP) or any other type of peripheral device capable of operating in a wireless environment. In accordance with an embodiment of the present invention, FIG. 4 is shown in FIG. 4 including the 405, the eNodeB 410, the MME 415, and the anchor node 420. A procedure for PDP context initiation and argument allocation in the LIE system 400. For multiple service collections, 9 200803370, no additional auxiliary PDP context initiation is required. The new secret dynamic request is provided by the RB and is provided at Wim; Released between 405 and eN〇deB 41. Referring to Figure 4, in step 422, the WTRU 405 sends a Start PDP Context Request message to the MME 415. The content of the message includes NSAPI, Identification code (n), PDp type, pDp address (if static PDP address is requested), access point name (^pN), Q〇s, service list, etc. It should be noted that 'the meaning of the QoS request is Different from the current pDp context initiator. Currently, QoS is only applicable to such pDp contexts. The primary and secondary PDP contexts and their mapping respectively can have different QoS. According to the invention 'Q〇S is a pair for all attributions The RAB for the pDp context is all applicable to the range 'and the WTRU 405 is likely to have only one PDP context for one IP address. The service list is a new parameter that provides that the WTRU 405 is expected to rely on this PDP context. The scope of IP services established by the core network (CN).

In step 424, the MME 415 verifies the initiating pdp context request using the PDP type, PDP address, and APN provided by the WTRU 405. The MME 415 can limit the requested QoS attributes given the capabilities and current load. The MME 415 sends a PDP context request message (PDP type, PDP address, APN, negotiated QoS, TEID, NSAPI, Mobile Station International Integrated Services Digital Network (ISDN) number to the affected anchor node 420. (MSISDN), etc.) (step 426). In step 428, anchor node 420 will create a PDP entry for the valid PDP context request. Associated with each service requested is a different PDP. In this case, if all services are provided via/by the same gateway (i.e., pin node 420), then 200803370 there will be an ip address and multiple apostrophes. Each apostrophe is associated with the service being started. In addition, in step 428, anchor node 420 also creates billing information for a valid PDP context request. Each service will be charged separately according to different rules. For example, the cost of a video call can be different from the cost of a text message. Therefore, each service will have a different billing Π>. The anchor node 420 then sends a Create PDP Context Response message to the MME 415 (step 430). In steps 432, 434, 436 and 438, the RAB allocation/RB setup procedure performs RAB setup as is currently done. The parent switched QoS between the RAN (e.g., eNodeB 510) and (3) is for a particular RAB, and the Q〇S should be within the negotiated q〇s of the PDP context. The identity of the PDP context associated with this RAg will be passed to wtru 4〇5. If the Q〇s are degraded from the negotiated q〇s of the PDP context, then since more RABs/RBs can be allocated for the same service when more resources are available, there is no need to modify the PDP context at this time. . If all of the above steps are successfully performed, the MME 415 will return a start pdp context accept message (pdp type, pdp iih address 'Ή, negotiated Q〇s, radio priority order, etc.) to the WTRU 405 (step 440). A first rb associated with the PDP context and a GPRS Tunneling Protocol (GIP) tunnel between the anchor node 42A and eNodB 410 are then established (steps 442, 444) 0 as shown in routine 450 of FIG. 4, for For each new service requested at the WTRU 405, it is necessary to establish a new RB/RAB for each of these services, step 452). The WTRU 405 sends a message to the eNodeB 410 to request a new RB for the new service (step 454). The Q〇S related to the service, please π 200803370 can be passed along with the message. The eNodeB 410 checks the availability of the resource (step 456), and if there are not enough resources, it can reject the request. The eNodeB 410 will forward this request to 415 to request a new RAB (step 458). Since the WTRU 405 is aware of the NSAPI established from the first RAB (i.e., the _ established in the primary PDP context initiator), the MME 415 will know which pDp context the request should be associated with. The MME 415 informs the anchor node 420 that there is a new RAB established for a certain commission pdp context (step 460). The anchor node 420 allocates the necessary resources, updates the charging and routing information for the service at the end of the tunnel, and sends back a response to the MMg (step 462). The RAB allocation and RB setup procedures (steps 464, 466, 468, and 470) are performed in a conventional manner. These steps 464, 466, 468, and 470 can be performed in parallel with steps 460 and 462, which can reduce the delay. When a new service is requested at step 452, the steps of program 450 will be repeated. Figure 5 shows a PDP context initiation procedure performed in an lxe system 5A in accordance with another embodiment of the present invention, wherein the system 5 includes 505, eNodeB 510, MME 515, and pin node 520. In the proposed procedure, multiple sets of services do not require additional secondary PDP context initiation. The dynamic request for the new service is provided by the RB establishment and is released between the stomach 5〇5 and the eNodeB 510. Referring to Figure 5, the WTRU 505 sends a Start PDP context request message to the MME 515 (step 525). A list of NSApi, services, and corresponding q〇s requirements is specified in this request. It should be noted that, unlike the traditional PDP context initiator that gives an NSAPI and an APN only 12 200803370, the proposed program will have an NSAPI, service and information to be negotiated and established in a PDP context initiator. A list of APNs. If a different service request occurs later, then an additional PDP context initiator will no longer be needed, thus limiting signal passing between the WTRU 505 and the eNodeB 510. Still referring to FIG. 5, in step 530, the MME 530 verifies the initiating PDP context request, selects at least one APN, maps the APN to the anchor node 520, and determines the GTP(R) and the NSAPI list. The WTRU 505 will use the APN list to list all services that need to be started. Each service is tagged with a different NSAPI and QoS specific file. In step 535, 515 sends a Create PDP Context Request message to anchor node 520. In step 54, the 'wrong node 520' will create a pdp entry for a valid PDP context request. Different PDPs are associated with each of the requested services. In this case, if all services are provided via/by the same gateway (ie, anchor node 52), then an IP address will exist. And multiple apostrophes. Each apostrophe is associated with the service being started. In addition, in step 540, anchor node 52 will also create billing information for a valid PDP context request. Each side is charged separately according to different rules. For example, the cost of calling a call can be different from the cost of a text message. Therefore, each service has a different billing ω. At this point, the PDP context initiator will be completed on the anchor node 520. The anchor node 520 then initiates the response phase of the operation by generating a pDp context response message back to the μμε 515 (step 545), which ensures that the second (e.g., eNodeB 510) knows that multiple tunnels are being initiated (step 55). 〇13 200803370 The MME will send information about the number of services being activated and the associated ASAPI, PDP address, gateway TEID, WTRUID (temporary ED) so that each traffic can be routed accordingly. The RAN (e.g., eNodeB 510) will then initiate the RAB for each service and map each flow to the associated ID (step 555) to establish a tunnel (step 560) (through tunnel or traditional GPRS dual tunnel (11) ^^ and (}1?)). In step 565, the MME 515 may end the launch procedure by notifying the WTRU 505 that the boot process was successful. The MME 515 will send a list of all successfully launched services. For a service, the MME 515 will indicate the failed service and the reason for the failure. In step 570, the WTRU 505 and/or the RAN (e.g., eNodeB 510) can initiate/deactivate the entity RB based on the availability of the data flow to be transmitted. For the more scams that need to be established later, the above procedure will be limited to only the rb establishment between the WTRU 505 and the eNodeB 510. In the procedure to start the PDP context, and (3) will be negotiated. The Q〇s parameters for the PDP context, such as the maximum bit rate, guaranteed bit rate, maximum delay, etc. HQ〇S specific files are passed to the RAN'·consulting pDp context in the random g-slot sequence. Riding has to say 'its QoS The requirement should be within the context of (10). Figure 6 shows multiple PDP contexts established for multiple pDNs in a wireless communication system. The system includes WTRUs 6〇5, eN〇秘, 咖6丨5, anchor node 62G and Na bribe ~ coffee. If the new APN is required for the new service and thus a new access gateway is needed, then the ^ 615 must be paged on the eNodeB 610 and the new access ramp. Allocating a new tunnel. Jia Milk 200803370 605 is likely to get a different positive address from each pDN. This will establish a different PDP context. For the turn of the PDP context, the program is above The procedure described is the same. With the proposed PDP context procedure, a Ρ) context is already a full-fee for multiple services that a π> address for the WTRU 605 has. For example, if an operator wishes to bind certain services with a secondary PDP context, then establishing a secondary PDP context may be optional. The processing of the auxiliary pDp context is the same as the processing currently performed. Multiple RABs/RBs can be established and associated with the pdp context. As long as there is no reverse bit rate and delay budget, the eN〇deB 610 should be able to accommodate multiple radio bearers for the evening stream. If the additional bearer request from gjv, je (jeB violates the QoS restrictions, then the eNodeB 610 informs the WTRU 605 that the existing request needs to modify the PDP context and/or initiate the secondary PDP context. The number of parallel flows allowed by the PDP context is definable. If ujyj 605 has exhausted the allowable service, its request will be rejected. Currently, there is a one-to-one relationship between: NSAPI, RAB, and ?0? context. There are also RBs in the packet domain. One-to-one relationship of the identity. It is necessary to establish a new mapping for the proposed PDP context procedure change. The meaning of NSAPI remains unchanged. In WTRU 605, NSAPI can identify the PDP service access point (SAP). In MME 615 and anchor node 62, NSAPI may identify a pDp context associated with a mobility management (mm) context, where the MM context indicates the state of WTRU 605. mm context has to operate with the network All information about the WTRU 605, such as QoS, poor security information, etc. rab π) should have both NSApi 15 200803370 (that is, the PDP associated with the RAB) Below) as well as the unique ID information of the RAB. Therefore, each one is mapped to a PDP context. How to form a RAB ID is being implemented. For RB m, it can be the same as the RABID. Example

1' A method in a long term evolution (lie) communication system, the system comprising a wireless transmit/receive unit (WTRU), an evolved Node-B, a mobility management entity (MME), and an anchor node, The method comprises: (8) establishing a first radio bearer between the anchor node and the evolved Node-B, the first radio bearer and packet data protocol (PDP) context and a universal packet radio service (GPRS) tunneling protocol (GTP) Corresponding; (9) The WTRU sends a message to the evolved Node-B to request a new radio bearer (RB) for a new service; (c) the evolved Node-B forwards the message to]V0V[E, where MME Mapping the access point name (apN) to the anchor node, determining the GTP tunnel endpoint identification code (xeh) and a network layer service access point identification code (NSAPI) list; and (d) the MME notifying the wrong node A specific pdp context establishes a new radio access bearer. 2. The method of embodiment 1, wherein the anchor node allocates the necessary resources for the service at the end of the tunnel, updates the charging and routing information, and sends a response back. The method of any one of embodiments 1 to 2 wherein a service related quality of service (QoS) request is communicated with the message. 4. The method according to any one of embodiments 1 to 3, wherein the evolved type

Node-B checks the availability of resources. 5. The method of embodiment 4 wherein the progressive Node-B rejects the message if there are not enough resources. A Long Term Evolution (LTE) communication system comprising: (a) an evolved Node-B; (b) a wireless transmit/receive unit (WTRU) configured to send a message for a new service Requesting a new radio bearer (RB); (c) an anchor node configured to establish a first radio bearer between the anchor node and the evolved Node-B, wherein the first radio bearer and the packet data protocol (PDP) Context associated with a General Packet Radio Service (GPRS) Tunneling Protocol (GTP); and (Φ a Mobility Management Entity (MME) configured to map an Access Point Name (APN) to an anchor node, determine GTP with the dot identification code (ΤΕΠ) and a network layer service access point identification code (NSAPI) list, and inform the anchor node to establish a new radio access bearer (RAB) for a specific PDP context.

The system of embodiment 6 wherein the anchor node allocates the necessary resources for the service at the end of the track, updates the charging and routing information, and sends a response back to the MME 17 200803370. 8. The system of any one of embodiments 6 and 7, wherein a service related quality of service (QoS) request is communicated with the message. The system of any one of embodiments 6 to 8, wherein the evolved type

Node-B checks the availability of resources. 10. The system of embodiment 9, wherein the evolved Node-B rejects the message if there are not enough resources.

11. A method in a long term evolution (m) communication system, the system comprising a wireless transmit/receive unit (WTRU), an evolved N〇de-B, a mobility management entity (MME), and a wrong node, The method includes: (8) the WTRU sends a Startup Packet Data Protocol (PDP) Context Request message to the MME, the Initiated pDp Context Request message including a Network Layer Service Access Point Identifier to be negotiated and established in a single PDP Context Initiator (NSAPI), a list of services and access point names (apn); (b) the MME verifies the initiating PDP context request and sends a Create PDP Context Request message to the anchor node; (c) The wrong node creates a new PDP An entry and a charging identifier; (d) the anchor node sends a Create PDP Context Response message to the MME; (e) establishes a Radio Access Bearer (RAB) between the evolved Node-B and the MME; and 18 200803370 2 in the WTRU A radio bearer (RB) is established between the face and the chest (10). 12. The method of embodiment 11, wherein the MME maps the APN to the anchor node, determines a General Packet Radio Service (GPRS) Tracking Protocol (GTP) Channel Endpoint Identification Code (ΤΕΠ), and an NSApi list, and The MME informs the anchor node to establish a new RAB for a particular pDp context. 13. The method of embodiment 12, wherein the wrong node allocates the necessary resources for the month at the end of the track. The method of any one of embodiments 11 to 13, wherein a service-related quality of service (QoS) request is transmitted to the MME with the start packet PDP context request message. * As in Embodiment 11~ The method of any of the embodiments 14, wherein the evolved Node-B checks the availability of the resource. 10 16 · A Long Term Evolution (LIE) communication system, comprising: (8) an evolved Node-B; (9) a wireless transmit/receive unit (WTRU) configured to send a start packet data protocol (PDP) context request message, The initiating PDP context request message includes a list of network layer service access point identifiers (NSAPIs), services, and access point names (APNs) to be negotiated and established in a single PDP context initiator; (c) An anchor node configured to receive for the anchor node

Creating a PDP context request message, creating a new PDP 19 200803370 entry and charging identifier, and transmitting a Create PDP Context Response message, and (Φ a Mobility Management Entity (MME) configured to receive the creation PDP context response message.

17. The system of embodiment 16 wherein the radio access bearer is established between the evolved Node-B and the MME and the radio bearer (RB) is established between the WTRU and the evolved Node_B. The system of embodiment 17, wherein the MME maps the APN to the anchor node, determines an overnight packet radio service (GPRS) tunneling protocol (GIP) channel endpoint identification code (ΤΕΠ), and an NSApi list, and The MME informs the anchor node to establish a new RAB for a particular pdp context. The system of embodiment 18 wherein the anchor node allocates the necessary resources for the service at the end of the track. The system of any one of embodiments 16 to 19, wherein a service-related quality of service (Q〇S) request is delivered to the MME along with the initiating packet pDp context request message. The system of any one of embodiments 16 to 20, wherein the evolved Node-B checks the availability of the resource. Although the present invention has been described in terms of specific ', σ - in the preferred embodiment, the solid features or components may be in the scale and tree without the preferred embodiment. 11: The other features and components combined with Lai Taiming are used in various situations: for = 20 200803370 The method or flowchart can be implemented in a computer program, soft one or firmware executed by a general purpose computer or processor. The software or the firmware is included in the computer readable storage medium, and the computer readable storage medium includes a read only memory (ROM), a random access memory (RAM), and a temporary storage device. = buffer memory, semiconductor memory device, internal hard disk and removable disk

Magnetic media, magneto-optical media, and optical media such as CI>R0M discs and digital versatile discs (DVDs). For example, 'appropriate processors include: general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a Dsp core, Controller, microcontroller, dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuit, any integrated circuit and/or state machine. The processor associated with the software can be used to implement a radio frequency transceiver, used in a (WTRU), a device, a terminal, a base station, a radio network controller, or any host computer. The WTRU can be used in conjunction with modules implemented in hardware and/or software, such as camera 'camera modules, video phones, speaker phones, vibration devices, speakers, microphones, TV transceivers, hands-free headsets, keyboards, Bluetooth 8 Module, frequency modulation (FM) radio unit, liquid crystal display (LCD) display unit, organic light emitting diode (OLED) display unit, digital music player, media player, video game board set, internet browser and / or any kind of wireless local area network (WLAN) module. 21 200803370 [Simultaneous Description of the Drawings] k The following description of the preferred embodiments of the present invention can be understood in more detail. The preferred embodiments are provided as examples and are understood in connection with the drawings. , wherein: Figure 1 shows a conventional master PDP context initiator for a ratio mode in a conventional wireless communication system:

2 is a conventional auxiliary PDP context initiation procedure for an instant mode in a conventional wireless communication system. FIG. 3 is a flowchart of a conventional pDp context initiation procedure in a conventional wireless communication system;

4 is a signal flow diagram of a pDp context initiation procedure performed in an LTE system according to an embodiment of the present invention; FIG. 5 is a signal flow of a PDP context initiation procedure performed in an LTE system according to another embodiment of the present invention. Figure; and Figure ό shows the establishment of a multi-commission pDp context for multiple PDNs. [Main component symbol description] 100 - 600 110 115 120 400, 500 105, 405, 505, 605 410, 510, 610 415, 515, 615 420, 520, 620 Wireless communication system (RAN) support Node (SGSN) Support Node (GGSN) Long Term Evolution (LIE) System Wireless Transmit/Receive Unit (WTRU) Evolved Node B (eNodeB) Mobility Management Entity (MME) Pin Node 22

Claims (1)

200803370 X. Patent Application Range·· h A method in a Long Term Evolution (LIE) communication system including a wireless transmit/receive unit (wmu), an evolved b-node (Node-B), and a mobility A management entity (MMe) and an anchor node, the method comprising: (8) establishing between the anchor node and the evolved Node B (Node-B) a first radio bearer associated with a Packet Data Protocol (PDP) context and a General Packet Radio Service (GPRS) Tunneling Protocol (GTP); (b) the WTRU to the evolved Node B (Node) - Β) send a message 'to request a new radio bearer (RB) for a new service; (c) the evolved Node-B forwards the message to the MME, where the MME will access the name of the access point ^) mapping to the anchor node, determining a GTP Tunnel Endpoint Identifier (TEU) and a Network Layer Service Access Point Identifier (NSAPI) list; and (Φ the MME informing the anchor node to establish a PDP context) A new radio access bearer (RAB). The method of claim 2, wherein the wrong node allocates necessary resources for the service at the end of the channel, updates charging and routing information, and sends back to the MME. A response as described in claim 1, wherein a service-related quality of service (QoS) request is communicated with the message. 4. The method of claim 1, wherein The evolutionary type] B node 23 200803370 (NodeA) checks the availability of resources. 5. The method of claim 4, wherein if there is not enough resources, the evolved node (10) also rejects the message. (LIE) communication system comprising: (a) an evolved Node B (Node-B); (b) a wireless transmit/receive unit (WTRU) configured to send a message to request a new service a new radio bearer (RB); (c) an anchor node configured to establish a first radio bearer between the anchor node and the evolved Node B (Node-B), wherein the first radio bearer Associated with a Packet Data Protocol (pDp) context and a General Packet Radio Service (GPRS) Tunneling Protocol (GTP); and (Φ a Mobility Management Entity (MME) configured to place an Access Point Name (APN) Mapping to the anchor node, determining a GTp Tunnel Endpoint Identifier (TEID) and a Network Layer Liner Access Point Identifier (NSAPI) list, and informing the pin node to establish a new radio access bearer for a pDp context ( RAB). 7. Apply The system and system described in item 6, wherein the wrong node allocates necessary resources for the service at the end of the tunnel, updates charging and routing information, and sends a response back to the MME. δ. The system of claim 6 wherein the quality of service (QoS) request that was first seen in January is transmitted with the message. The system of claim 6, wherein the evolved Node B 24 200803370 (Node- B) Check the availability of resources. The system of claim 9, wherein the evolved Node B (Node-B) rejects the message if there is insufficient resources. 11. A method in a long term decision (LTE) communication system, the communication system comprising a wireless transmit/receive unit (WTRU), an evolved Node B (Node-B), a mobility management entity (MME), and An anchor node, the method comprising: (a) the WTRU transmitting a Start Packet Data Protocol (PDP) Context Request message to the MME, the Initiating pDp Context Request message including a network to be negotiated and established in a single PDP context initiator a list of Layer 2 Service Access Point Identifier (NSAPI), Service and Access Point Name (APN); (b) the MME verifies the Initiate PDP Context Request and sends a Create PDP Context Request message to the anchor node; (c) the anchor node creates a new PDP entry and a charging identifier; (Φ the wrong node sends a Create PDP Context Response message to the MME; (e) at the evolved Node B (Node-B) Establishing a radio access bearer (RAB) between the MMEs; and establishing a radio bearer (RB) between the WTRU and the evolved type N. The method of claim 11, wherein the method ^^Map APN to this The node establishes a list of overnight packet radio service (GPRS) tunneling protocol (GTP) tunnel endpoint identification code (TRTD) and an NSAPI 25 PDP context, and the MME informs the anchor node that it is a new RAB. The method of item 12, wherein the end of the scale point is to allocate a necessary resource for the service. The method of item n, wherein the __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ The request message is passed to the MME. V. The method of claim 11, wherein the evolved Node-B checks the availability of resources. A Long Term Evolution (LTE) communication system, including (8) an evolution Type B Node (Node-B); (9) A Wireless Transmit/Receive Unit (WTRU) configured to transmit a Startup Packet Data Protocol (PDP) Context Request message containing the desired to be negotiated and in a single A list of network layer service access point identifiers (NSAPIs), services, and access point names (APNs) established in the PDP context initiator; (c) an anchor node configured to receive Creating a PDP context request message to the anchor node, creating a new PDP entry and a charging identifier, and transmitting a create PDP context response message; and (Φ - Mobility Management Entity (MME) configured to receive The system for creating a PDP context response message, such as the system of claim 16, wherein the radio access bearer 200803370 (RAB) is established between the evolved Node B and the radio bearer (RB) is The W^U is established with an evolved Node B (Node-B). 18. The system of claim π, wherein the mapping is mapped to the anchor node, determining a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) Tunnel Endpoint Identifier (TFJD), and An NSAPI list 'and the MME informs the anchor node to establish a new RAB for a particular pDp context. The system of claim 18, wherein the anchor node allocates the necessary resources for the service at the end of the tunnel. 20. The system of claim 17, wherein a service-related quality of service (QoS) request is transmitted to the MME along with the initiation packet request context request message. The system of clause 17, wherein the evolved 3-node (Node-B) checks the availability of resources.