+

WO2019196000A1 - Procédés et système pour réaliser une communication par chemin rapide de petites données - Google Patents

Procédés et système pour réaliser une communication par chemin rapide de petites données Download PDF

Info

Publication number
WO2019196000A1
WO2019196000A1 PCT/CN2018/082439 CN2018082439W WO2019196000A1 WO 2019196000 A1 WO2019196000 A1 WO 2019196000A1 CN 2018082439 W CN2018082439 W CN 2018082439W WO 2019196000 A1 WO2019196000 A1 WO 2019196000A1
Authority
WO
WIPO (PCT)
Prior art keywords
fast path
small data
data fast
access network
radio access
Prior art date
Application number
PCT/CN2018/082439
Other languages
English (en)
Inventor
Fei Lu
Jinguo Zhu
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to CN201880091212.1A priority Critical patent/CN111869310A/zh
Priority to PCT/CN2018/082439 priority patent/WO2019196000A1/fr
Publication of WO2019196000A1 publication Critical patent/WO2019196000A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure is related generally to wireless networks and, more particularly, to methods and systems for establishing a fast path for small data transmission.
  • FIG. 1 is a block diagram of a system in which various embodiments of the disclosure are implemented.
  • FIG. 2 shows an example hardware architecture of a communication device.
  • FIG. 3 is a block diagram of a network environment in which, according to various embodiments, the devices depicted in FIG. 1 and FIG. 2 may be deployed.
  • FIG. 4 is an example of how small data fast path communication is established using currently-existing techniques.
  • FIG. 5 and FIG. 6 are communication flow diagrams showing an example of a currently-existing procedure for establishing small data fast path communication in the context of the network environment of FIG. 3.
  • FIG. 7, FIG. 8, FIG. 9, and FIG. 10 are communication flow diagrams showing examples of procedures for establishing small data fast path communication in the context of the network environment of FIG. 3, according to different embodiments.
  • a method for carrying out small data fast path communication for a wireless communication device moving from a first radio access network to a second radio access network involves the second radio access network carrying out the following actions: receiving small data fast path parameters and a connection resume identifier from the wireless communication device during a radio resource control connection establishment procedure; deriving the first radio access network from the resume identifier; transmitting, to the first radio access network, a connection request including the small data fast path parameters and a tunnel endpoint identifier for small data fast path downlink data; and receiving, from the first radio access network, a tunnel endpoint identifier for small data fast path uplink data.
  • a method for carrying out small data fast path communication for a wireless communication device moving from a first radio access network to a second radio access network involves the second radio access network carrying out the following actions: receiving small data fast path parameters and a connection resume identifier from the wireless communication device during a radio resource control connection establishment procedure; deriving the first radio access network from the resume identifier; receiving small data fast path uplink data from the wireless communication device; and transmitting the small data fast path uplink data to the first radio access network.
  • a method for carrying out small data fast path communication for a wireless communication device moving from a first radio access network to a second radio access network involves the second radio access network carrying out the following actions: receiving small data fast path parameters from the wireless communication device during a radio resource control connection establishment procedure; identifying a user plane function based on the small data fast path parameters; transmitting, to the user plane function, a request for the establishment of a tunnel for a small data fast path connection, wherein the request includes the small data fast path parameters and a tunnel endpoint identifier for small data fast path downlink data; and receiving, from the user plane function, a tunnel establishment response message that includes a tunnel endpoint identifier for the user plane function to be used for small data fast path uplink data.
  • a method for carrying out small data fast path communication for a wireless communication device moving from a first radio access network to a second radio access network involves the second radio access network carrying out the following actions: receiving small data fast path parameters from the wireless communication device during a radio resource control connection establishment procedure; identifying a first user plane function based on the small data fast path parameters; receiving small data fast path uplink data from the wireless communication device; transmitting the small data fast path uplink data, the small data fast path parameters, and a tunnel endpoint identifier for downlink data to the first user plane function.
  • the method also involves the first user plane function deriving the second user plane function from the small data fast path parameters; and transmitting the small data fast path uplink data, the small data fast path parameters, and downlink tunnel information for a small data fast path session to the second user plane function.
  • FIG. 1 depicts a communication system 100 in which the various embodiments described herein may be implemented.
  • the communication system 100 includes several wireless communication devices ( “wireless communication device” will sometimes be shortened herein to “communication device” or “device” for convenient reference) .
  • the communication devices depicted are a first communication device 102 (depicted as a user equipment ( “UE” ) ) , a second communication device 104 (depicted as a base station) , and a third communication device 106 (depicted as a UE) .
  • UE user equipment
  • FIG. 1 the wireless communication system 100 has many other components that are not depicted in FIG.
  • wireless communication devices include any device capable of wireless communication, such as a smartphone, tablet, laptop computer, and non-traditional devices (e.g., household appliances or other parts of the “Internet of Things” ) .
  • a wireless communication device When operating as part of a wireless communication system (e.g., part of a radio access network) , a wireless communication device may be referred to as a “wireless network node. ”
  • a wireless communication device communicates primarily by transmitting and receiving wireless signals.
  • the second communication device 104 operates as a node of a RAN (such as a “Node B” of a fourth generation or fifth generation RAN) 108.
  • the RAN 108 is communicatively linked to a CN 110.
  • the CN 110 carries are many functions in support of the RAN 108 and has many components.
  • FIG. 2 illustrates a basic hardware architecture implemented by each of the wireless communication devices of FIG. 1, according to an embodiment.
  • the elements of FIG. 1 may have other components as well.
  • the hardware architecture depicted in FIG. 2 includes logic circuitry 202, memory 204, transceiver 206, and one or more antennas represented by antenna 208 (including transmit antennas and/or receive antennas) .
  • the memory 204 may be or include a buffer that, for example, holds incoming transmissions until the logic circuitry is able to process the transmission.
  • Each of these elements is communicatively linked to one another via one or more data pathways 210. Examples of data pathways include wires, conductive pathways on a microchip, and wireless connections.
  • the hardware architecture of FIG. 2 may also be referred to herein as a “computing device. ”
  • logic circuitry means a circuit (a type of electronic hardware) designed to perform complex functions defined in terms of mathematical logic. Examples of logic circuitry include a microprocessor, a controller, or an application-specific integrated circuit. When the present disclosure refers to a device carrying out an action, it is to be understood that this can also mean that logic circuitry integrated with the device is, in fact, carrying out the action.
  • the network environment includes the RAN 108, the wireless communication device 102, and the CN 110.
  • the network environment further includes a data network ( “DN” ) 302.
  • the CN 110 includes a unified data management server ( “UDM” ) 304, an access and mobility management function ( “AMF” ) 306, a session management function ( “SMF” ) 308, and a user plane function ( “UPF” ) 310.
  • UDM unified data management server
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • the AMF 306 provides the following services: registration management, connection management, reachability management, and mobility management.
  • the AMF also carries out access authentication and access authorization.
  • the AMF 306 acts as the non-access stratum ( “NAS” ) security termination and relays the session management ( “SM” ) NAS between a UE and an SMF.
  • NAS non-access stratum
  • SM session management
  • the SMF 308 provides the following services: session Management (e.g., session establishment, modify and release) , UE internet protocol ( “IP” ) address allocation and management (including optional authorization) , selection and control of user plane ( “UP” ) functions, and downlink ( “DL” ) data notification.
  • session Management e.g., session establishment, modify and release
  • IP internet protocol
  • UP user plane
  • DL downlink
  • the UPF 310 provides the following services: serving an anchor point for Intra-/Inter-radio access technology ( “RAT” ) mobility, packet routing and forwarding, traffic usage reporting, quality of service ( “QoS” ) handling for the user plane, DL packet buffering, and DL data notification triggering.
  • RAT Intra-/Inter-radio access technology
  • QoS quality of service
  • the devices of FIG. 3 have names that end in “function” or “entity, ” they are, in fact, computing devices that carry out functions (e.g., under the control of software) .
  • the UPF 310 is a computing device (or multiple computing devices working in concert) that carries out functions described herein.
  • the various devices in FIG. 3 communicate with one another in various ways, including the well-known interfaces shown with the lines labeled ‘Nx’ . Also, each of the devices depicted in FIG. 3 are meant to be representative. For example, there may be many SMFs and UPFs in the CN 110, and there may be multiple RANs, which the device 102 may encounter when in moves from location to location.
  • small data refers to a block of data that is less than 200 bytes in size.
  • fast path refers to a data transmission technique in which certain intermediate steps are skipped as compared to regular data transmissions.
  • a regular data transmission procedure may involve a device (e.g., a UE) first sending a service request message to an AMF and requesting the network (e.g., RAN) to set up the user plane for the data transmission.
  • the SDFP is established by providing the relevant UPF (UPF 310 in this example) or protocol data unit ( “PDU” ) session related information to the wireless communication device (device 102 in this example) from the SMF, which the wireless communication device would later provide to the RAN (RAN 108 in this example) .
  • the UPF or PDU session relevant information allows the RAN to derive the path (e.g., over interface N3) to the UPF.
  • the wireless communication device passes the data, together with the UPF or PDU session relevant information, to the RAN.
  • the RAN forwards the data (e.g., on the N3 interface) . Since all info required to forward the data is received from the wireless communication device, the RAN does not need to signal to the AMF or have any context information regarding the wireless communication device (e.g., UE context) stored.
  • the device 102 sends an UL NAS TRANSPORT message to the AMF 306.
  • This message includes single network slice selection assistance information ( “S-NSSAI” ) , data network name ( “DNN” ) , PDU session identifier ( “ID” ) , request type, and an N1 SM container (PDU Session Establishment Request) .
  • the request type indicates “initial request” if the PDU Session Establishment is a request to establish a new PDU Session.
  • the device 102 should provide an indication that it wants to establish a SDFP PDU session in the UL NAS TRANSPORT message.
  • the AMF 306 selects an SMF that supports the SDFP (SMF 308 in this example) .
  • the AMF 306 also generates a SDFP security context.
  • the AMF 306 sends Nsmf_PDUSession_CreateSMContext Request (which includes a subscriber permanent identifier ( “SUPI” ) , DNN, S-NSSAI, PDU Session ID, AMF ID, request type, N1 SM container (PDU Session Establishment Request) , user location information, access type, and an SDFP indication) to the SMF 308.
  • Nsmf_PDUSession_CreateSMContext Request which includes a subscriber permanent identifier ( “SUPI” ) , DNN, S-NSSAI, PDU Session ID, AMF ID, request type, N1 SM container (PDU Session Establishment Request) , user location information, access type, and an SDFP indication
  • the SMF 308 responds with the Nsmf_PDUSession_CreateSMContext Response (SMF context Identifier) message.
  • SMSF context Identifier Nsmf_PDUSession_CreateSMContext Response
  • the SMF 308 selects a UPF that supports the SDFP (UPF 310 in this example) .
  • the SMF 308 sends the N4 Session Establishment request message to the UPF 310 and provides packet detection, enforcement and reporting rules to be installed on the UPF 310 for this PDU Session. If CN Tunnel Info is allocated by the SMF 308, the CN Tunnel Info is provided to the UPF 310 in this step. Also during this step, the SMF 308 will set up the SDFP security context in the UPF 310.
  • the UPF 310 acknowledges that by sending an N4 Session Establishment/Modification Response. If CN Tunnel Info is allocated by the UPF 310, the CN Tunnel Info is provided to the SMF 308 in this step.
  • the SMF 308 transmits to the AMF 306: Namf_Communication_N1N2MessageTransfer (including PDU Session ID, access type, N2 SM information (PDU Session ID, QoS flow identifier (s) ( “QFI (s) ” ) , QoS profile (s) , CN Tunnel Info, S-NSSAI, Session-aggregate maximum bit-rate ( “AMBR” ) , PDU Session Type) , N1 SM container (PDU Session Establishment Accept (QoS Rule (s) , S-NSSAI, allocated IP address, Session-AMBR, and selected PDU Session Type) ) ) ) .
  • the PDU session establishment accept will also include the UPF information for this PDU session.
  • the AMF 306 responds with the Namf_Communication_N1N2MessageTransfer ACK.
  • the AMF 306 transmits to the RAN 108: N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept) ) ) .
  • the AMF 306 sends the NAS message containing a PDU Session ID and PDU Session Establishment Accept targeted to the device 102 and the N2 SM information received from the SMF 308 within the N2 PDU Session Request to the RAN 108.
  • the RAN 108 and device 102 engage in access network ( “AN” ) specific signaling exchange that is related to the information received from SMF.
  • the RAN 108 also allocates RAN N3 tunnel information ( “Info” ) for the PDU Session.
  • the AN Tunnel Info includes a tunnel endpoint for the involved RAN node.
  • the RAN 108 forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept) ) provided in step 508 to the device 102.
  • the RAN 108 only provides the NAS message to the device 102 if the necessary RAN resources are established and the allocation of RAN tunnel information is successful.
  • the RAN 108 transmits to the AMF 306: N2 PDU Session Response (PDU Session ID, Cause, N2 SM information (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI (s) ) ) .
  • the AN Tunnel Info corresponds to the access network address of the N3 tunnel corresponding to the PDU Session.
  • the AMF 306 transmits to the SMF 308: Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, Request Type) .
  • N2 SM information N2 SM information, Request Type
  • the AMF 306 forwards the N2 SM information received from RAN to the SMF 308. If the list of rejected QFI (s) is included in N2 SM information, the SMF 308 releases the rejected QFI (s) associated QoS profiles.
  • the SMF 308 initiates an N4 Session Modification procedure with the UPF 310.
  • the SMF 308 provides AN Tunnel Info to the UPF 310 as well as the corresponding forwarding rules.
  • the UPF 310 provides an N4 Session Modification Response to the SMF 308.
  • the SMF 308 transmits to the AMF 306: Nsmf_PDUSession_UpdateSMContext Response (Cause) .
  • FIG. 6 an example of a currently-existing procedure for establishing SDFP communication will now be described in the context of the network environment of FIG. 3.
  • the device 102 establishes a radio resource control ( “RRC” ) connection for SDFP transfer. In doing so, the device 102 passes parameters for selection of a UPF for the PDU Session for the device 102 to the RAN 108.
  • RRC radio resource control
  • the device 102 encrypts and integrity protects an UL data PDU and passes it to the RAN 108.
  • the RAN 108 forwards the UL data PDU to the selected UPF (UPF 310 in this case) .
  • the RAN 108 selects the UPF based on the SDFP information provided by the device 102.
  • the RAN 108 will also provide the UPF 310 with RAN N3 DL Tunnel Info for the SDFP session.
  • the UPF 310 checks integrity protection and decrypts the UL data PDU. If the check is passed, the UPF 310 forwards the UL data on the N6/N9 interface. In addition, the UPF 310 enables subsequent DL data transmissions to the RAN node it received the UP data PDU from.
  • a method for carrying out small data fast path communication addresses these issues with the following procedure:
  • the wireless communication device e.g., UE
  • the wireless communication device moves from a first RAN to a second RAN
  • the wireless communication device connects to the second RAN.
  • This second RAN will establish the Xn connectivity for the SDFP with the first RAN and the first RAN will send the small data to the UPF; or
  • the second RAN will connect to a new UPF (second UPF) and this new UPF will send the small data to the old UPF (first UPF) .
  • FIG. 7 a procedure carried for carrying out SDFP communication according to an embodiment will now be described in the context of the network environment of FIG. 3.
  • the device 102 had connected to the first RAN 108a, it carried out many of the procedures of FIG. 5, including step 509, and that the RAN 108a had given the device 102 a resume ID.
  • the wireless communication device establishes an RRC for SDFP transfer.
  • the device 102 passes parameters for selection of a UPF for the PDU Session for the device 102 to the second RAN 108b.
  • the second RAN 108b cannot connect to the UPF, although it can derive the UPF address.
  • the device 102 includes the resume ID in its communication to the second RAN 108b.
  • the device 102 derives the first RAN using the resume ID.
  • the SDFP information includes an identifier of the first RAN.
  • the first RAN can be derived from the SDFP information.
  • the first RAN 108a will include its RAN ID in the message that it passes to the AMF 306, which the AMF 306 will forward to the SMF 308 in step 502.
  • the SMF 308 will combine the RAN ID with the SDFP information that is sent to the device 102 as defined in the step 506 in the N1 SM container (PDU Session Establishment Accept) .
  • the second RAN 108 transmits a request to the first RAN 108a to establish Xn connectivity to the first RAN 108a.
  • the second RAN 108b may use the resume ID and the SDFP information (or use just the SDFP information if it contains the RAN ID) to derive the first RAN 108a (e.g., determine the identity, etc. of the first RAN 108a) .
  • the second RAN 108b also includes the SDFP information and the tunnel endpoint identifier ( “TEID” ) for SDFP DL data.
  • the first RAN 108a responds with an Xn connectivity response.
  • the first RAN 108a includes the old RAN TEID for SDFP UL data.
  • the device 102 encrypts and integrity protects an UL data PDU and transmits it to the second RAN 108b.
  • the second RAN 108b forwards the UL data PDU to the derived first RAN 108a.
  • the first RAN 108a forwards the UL data PDU to the selected UPF (UPF 310 in this example) .
  • the first RAN 108a selects the UPF based on the SDFP information provided by the device 102.
  • the first RAN 108a will also provide the UPF 310 with RAN N3 DL Tunnel Info for the SDFP session.
  • the UPF 310 checks integrity protection and decrypts the UL data PDU. If the check is passed, the UPF 310 forwards the UL data on the N6 interface. In addition, the UPF 310 enables subsequent DL data transmissions to the RAN node it received the UL data PDU from.
  • FIG. 8 a procedure carried for carrying out SDFP communication according to another embodiment will now be described in the context of the network environment of FIG. 3. As in the previous example, it may be assumed that, when the device 102 had connected to the first RAN 108a, it carried out many of the procedures of FIG. 5, including step 509, and that the RAN 108a had given the device 102 a resume ID.
  • the device 102 establishes an RRC for SDFP transfer. Parameters for selection of the UPF for the PDU Session for the device are passed to the second RAN 108b. The device 102 provides the resume ID to the second RAN 108b. Then, the device 102 derives the first RAN 108a using the resume ID.
  • the device 102 encrypts, and integrity protects an UL data PDU and passes it to the second RAN 108b.
  • the second RAN 108b cannot connect to the UPF, although it can derive the UPF address.
  • the device 102 includes the resume ID in its communication to the second RAN 108b. Then, the device 102 derives the first RAN using the resume ID.
  • the second RAN 108b derives the information of the first RAN 108a based on the SDFP information and forwards the UL data PDU to the first RAN 108a. In the data, the second RAN 108b also provides the first RAN 108a with Xn DL Tunnel Info for the SDFP session.
  • the first RAN 108a forwards the UL data PDU to the selected UPF (UPF 310 in this example) .
  • the first RAN 108a selects the UPF based on the SDFP information provided by the device 102.
  • the first RAN 108a will also provide the UPF 310 with RAN N3 DL Tunnel Info for the SDFP session.
  • the UPF 310 checks integrity protection and decrypts the UL data PDU. If the check is passed, the UPF 310 forwards the UL data on the N6 interface. In addition, the UPF 310 enables subsequent DL data transmissions to the RAN node it received the UP data PDU from.
  • FIG. 9 a procedure carried for carrying out SDFP communication according to yet another embodiment will now be described in the context of the network environment of FIG. 3, with the following addition: there is an initial UPF (first UPF 310a) and a new UPF (second UPF 310b) .
  • the device 102 establishes an RRC for SDFP transfer. Parameters for selection of a UPF for the PDU Session for the device 102 are passed to the second RAN 108b.
  • the RAN 108 cannot connect to the UPF, although it can derive the UPF address.
  • the RAN 108 selects a UPF (UPF 310b in this example) and requests to establish an N3 Tunnel with the UPF.
  • the RAN 108 may derive the second UPF 310b based on the SDFP information. In some embodiments, this UPF can also be a default UPF configured at the RAN 108 for SDFP transmissions) .
  • the RAN 108 also includes the SDFP information and the RAN TEID for SDFP DL data.
  • the second UPF 310b responds with the N4 tunnel establishment response.
  • the second UPF 310b includes its UPF TEID for SDFP UL data.
  • the second UPF 310b requests to establish an N9 Tunnel with the first UPF 310a.
  • the second UPF 310b may use the SDFP information to derive the first UPF 310a.
  • the second UPF 310b also includes the SDFP information and the N9 UPF TEID for SDFP DL data.
  • the first UPF 310a responds with an N9 tunnel establishment response.
  • the first UPF 310a includes the new UPF TEID for SDFP UL data.
  • the device 102 encrypts and integrity protects an UL data PDU and passes it to the RAN 108.
  • the RAN 108 forwards the UL data PDU to the derived new UPF (UPF 310b in this example) .
  • the second UPF 310b forwards the UL data PDU to the old UPF (first UPF 310a) .
  • the second UPF 310b selects the first UPF based on the SDFP information provided by the device 102.
  • the second UPF 310b will also provide the first UPF 310a with UPF N9 DL Tunnel Info for the SDFP session.
  • the first UPF 310a checks integrity protection and decrypts the UL data PDU. If the check is passed, the first UPF 310a forwards the UL data on the N6 interface. In addition, the first UPF 310a enables subsequent DL data transmissions to the RAN node it received the UP data PDU from.
  • FIG. 10 an example of how a wireless communication device establishes an RRC connection for SDFP transfer in accordance with an embodiment will now be described.
  • the steps shown in FIG. 10 are depicted in the context of the networking environment of FIG. 3, with the following addition: there is an initial UPF (first UPF 310a) and a new UPF (second UPF 310b) .
  • Parameters for selection of UPF for the PDU Session for the UE are passed to the RAN.
  • the RAN 108 cannot connect to the UPF, although it can derive the UPF address.
  • the device 102 encrypts and integrity protects an UL data PDU and passes it to RAN 108.
  • the RAN 108 forwards the UL data PDU to the derived new UPF (the second UPF 310b) .
  • the RAN will include the RAN N3 TEID for DL data.
  • the RAN 108 derives the UPF based on the SDFP information provided by the device 102.
  • the second UPF 310b forwards the UL data PDU to the old UPF (first UPF 310a) .
  • the second UPF 310b derives the first UPF 310a based on the SDFP information provided by the device 1002.
  • the second UPF 310b will also provide the first UPF 310a with UPF N9 DL Tunnel Info for the SDFP session.
  • the first UPF 310a checks integrity protection and decrypts the UL data PDU. If the check is passed, the first UPF 310a forwards the UL data on the N6 interface. In addition, the first UPF 310a enables subsequent DL data transmissions to the RAN node it received the UP data PDU from.
  • any and all of the methods described herein are carried out by or on one or more computing devices. Furthermore, instructions for carrying out any or all of the methods described herein may be stored on a non-transitory, computer-readable medium, such as any of the various types of memory described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé destiné à réaliser une communication par chemin rapide de petites données pour un dispositif de communication sans fil se déplaçant d'un premier réseau d'accès radio à un second réseau d'accès radio, le second réseau d'accès radio effectuant les étapes consistant à: recevoir des paramètres de chemin rapide de petites données et un identifiant de reprise de connexion en provenance du dispositif de communication sans fil au cours d'une procédure d'établissement de connexion de gestion des ressources radioélectriques; déduire le premier réseau d'accès radio de l'identifiant de reprise; envoyer au premier réseau d'accès radio une demande de connexion comprenant les paramètres de chemin rapide de petites données et un identifiant de point d'extrémité de tunnel pour des données de liaison descendante de chemin rapide de petites données; et recevoir, en provenance du premier réseau d'accès radio, un identifiant de point d'extrémité de tunnel pour des données de liaison montante de chemin rapide de petites données.
PCT/CN2018/082439 2018-04-10 2018-04-10 Procédés et système pour réaliser une communication par chemin rapide de petites données WO2019196000A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880091212.1A CN111869310A (zh) 2018-04-10 2018-04-10 用于执行小数据快速路径通信的方法和系统
PCT/CN2018/082439 WO2019196000A1 (fr) 2018-04-10 2018-04-10 Procédés et système pour réaliser une communication par chemin rapide de petites données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/082439 WO2019196000A1 (fr) 2018-04-10 2018-04-10 Procédés et système pour réaliser une communication par chemin rapide de petites données

Publications (1)

Publication Number Publication Date
WO2019196000A1 true WO2019196000A1 (fr) 2019-10-17

Family

ID=68163439

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082439 WO2019196000A1 (fr) 2018-04-10 2018-04-10 Procédés et système pour réaliser une communication par chemin rapide de petites données

Country Status (2)

Country Link
CN (1) CN111869310A (fr)
WO (1) WO2019196000A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155940A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Initiation de tunnel dans un réseau de communication
WO2021155938A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Sélection de fonction de plan utilisateur dans un réseau de communication
WO2021155939A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Initiation de tunnel dans un réseau de communication
WO2022160077A1 (fr) * 2021-01-26 2022-08-04 Zte Corporation Procédé pour la transmission de petites données

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115484615A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 通信方法及通信装置
CN115988483B (zh) * 2022-12-29 2024-11-12 北京长焜科技有限公司 一种基于动态地址池的终端后路由方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945535A (zh) * 2013-01-18 2014-07-23 中兴通讯股份有限公司 寻呼优化的方法、装置、系统和快速路径释放方法、装置
WO2014181178A1 (fr) * 2013-05-10 2014-11-13 Alcatel Lucent Procédé et dispositif de transmission de données

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945535A (zh) * 2013-01-18 2014-07-23 中兴通讯股份有限公司 寻呼优化的方法、装置、系统和快速路径释放方法、装置
WO2014181178A1 (fr) * 2013-05-10 2014-11-13 Alcatel Lucent Procédé et dispositif de transmission de données

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP GROUP, 3GPP TR 23.724, no. V0.2.0, 31 March 2018 (2018-03-31), XP051450431 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155940A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Initiation de tunnel dans un réseau de communication
WO2021155938A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Sélection de fonction de plan utilisateur dans un réseau de communication
WO2021155939A1 (fr) * 2020-02-06 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Initiation de tunnel dans un réseau de communication
US20230042390A1 (en) * 2020-02-06 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Tunnel initiation in a communications network
WO2022160077A1 (fr) * 2021-01-26 2022-08-04 Zte Corporation Procédé pour la transmission de petites données

Also Published As

Publication number Publication date
CN111869310A (zh) 2020-10-30

Similar Documents

Publication Publication Date Title
US11683723B2 (en) Methods and system for offloading data traffic
RU2731121C1 (ru) Способ регистрации, способ установки сеанса, оконечное устройство и объект функции управления доступом и мобильностью
US11490257B2 (en) Method and computing device for carrying out data integrity protection
US20210022063A1 (en) Data transmission method and apparatus
US11533610B2 (en) Key generation method and related apparatus
WO2019196000A1 (fr) Procédés et système pour réaliser une communication par chemin rapide de petites données
WO2019184651A1 (fr) Procédé et dispositif de communication
CN110662308B (zh) 一种通信方法及装置
CN108684073A (zh) 一种注册及会话建立的方法、终端和amf实体
US20170164256A9 (en) Service offloading method and base station
US11483744B2 (en) Methods and computing device for splitting traffic across multiple accesses
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
CN105873241B (zh) 建立通话连接的方法及装置
KR20200125970A (ko) 상이한 액세스 네트워크들 간에 모바일 통신 디바이스의 핸드오버를 수행하기 위한 방법 및 시스템
US20210014720A1 (en) Relocation Method and Apparatus
CN113746585A (zh) 授时方法和通信装置
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
CN107277882B (zh) 一种数据路由方法、装置和基站
WO2018082070A1 (fr) Procédé de traitement de paquets de données, élément de réseau de plan de commande et élément de réseau de plan d'utilisateur
CN112970284B (zh) 使用多个分组数据单元会话的超可靠通信
WO2019238050A1 (fr) Procédé et appareil de communication
CN115706995A (zh) 通信方法及装置、计算机可读存储介质
WO2020034343A1 (fr) Communication ultra fiable à l'aide d'une seule session d'unité de données par paquets
WO2012129997A1 (fr) Procédé et dispositif pour traiter une connexion d'accès à un réseau local

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18914784

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05.02.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18914784

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载