[go: up one dir, main page]

WO2018233451A1 - Procédé, appareil et système de communication - Google Patents

Procédé, appareil et système de communication Download PDF

Info

Publication number
WO2018233451A1
WO2018233451A1 PCT/CN2018/088540 CN2018088540W WO2018233451A1 WO 2018233451 A1 WO2018233451 A1 WO 2018233451A1 CN 2018088540 W CN2018088540 W CN 2018088540W WO 2018233451 A1 WO2018233451 A1 WO 2018233451A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
delay
information
delay information
terminal device
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/088540
Other languages
English (en)
Chinese (zh)
Inventor
应江威
杨艳梅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2018233451A1 publication Critical patent/WO2018233451A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters

Definitions

  • the present invention relates to communication systems, and more particularly to a communication method, apparatus and system.
  • the core network mainly includes a control plane function (CPF) and a user plane function (UPF).
  • CPF mainly includes access control and mobility management function (AMF) and session management function (SMF).
  • AMF access control and mobility management function
  • SMF session management function
  • the AMF entity is used to complete access authentication, security encryption, location registration, etc. of the terminal device;
  • the SMF entity is used for establishment, release and modification of the user plane transmission path, and session related processing.
  • the UPF entity mainly performs functions such as routing and forwarding of user plane data.
  • the AMF entity and the SMF entity belong to the core network device, and may be two entities that are physically merged but logically independent, or two entities that are physically independent.
  • the AMF entity notifies the SMF entity that maintains the session of the terminal device.
  • the device has switched so that the SMF entity determines whether to allow the session of the terminal device to switch to the target access network node.
  • the AMF entity may set a handover delay timer, which is a HO delay time. If the AMF entity receives all SMF entities that maintain the session of the terminal device before the timer expires, the AMF entity returns a HO delay time. If the result is determined, an N2 message (carrying mobile management related information and session management related information) is sent to the target access network node.
  • the size of the handover delay affects the service of the terminal device. For example, if the handover delay value is too small, many session handover failures may occur, resulting in service interruption or poor service quality. If the handover delay value is too large, it may result in The switching of some low-latency-required sessions cannot meet the low-latency requirements, which leads to service interruption. Therefore, how to determine the handover delay value becomes an urgent problem to be solved.
  • the embodiment of the invention provides a communication method, device and system, which can determine the handover delay value of the terminal device and improve the handover success rate of the session.
  • a communication method including: acquiring, by a core network device, information related to a session of a terminal device; and determining, by the core network device, delay information of the session according to the information associated with the session.
  • the delay information of the session is used to determine a handover delay value of the terminal device, so as to improve the handover success rate of the session.
  • the session-related information includes at least one of the following: a QoS attribute QoS profile of the quality of service QoS flow of the session, the session Corresponding data network name DNN, a single network slice selection auxiliary information S-NSSAI corresponding to the session, auxiliary information provided by the terminal device, and a session continuity mode SSC mode of the session.
  • the core network device determines, according to information related to the session, time delay information of the session, The determining, by the core network device, the delay information of the session according to the data packet delay in the QoS profile; or determining, by the core network device, the retention priority ARP according to the QoS profile, determining the session Delay information; or, the core network device determines a delay tolerance type of the session according to at least one of the DNN and the S-NSSAI, and determines the session according to a delay tolerance type of the session.
  • the delay information of the session is determined by the core network device according to the correspondence between the DNN and the delay information and the DNN corresponding to the session; or the core network device is based on the S- Determining the delay information of the session by the correspondence between the NSSAI and the delay information and the S-NSSAI corresponding to the session; or the auxiliary information provided by the core device by the core network device,
  • the determining, by the core network device, the delay information of the session according to the data packet delay in the QoS profile including: Determining, by the core network device, a minimum value of a packet delay value in a QoS profile of all QoS flows of the session; determining, by the core network device, a delay priority corresponding to the minimum value or the minimum value, determining The delay information for the session.
  • the core network device determines, according to the QoS profile, a retention priority ARP, and determines a delay information of the session, including The core network device obtains the highest priority of the ARP in the QoS profile of all the QoS flows of the session; the core network device sets the delay value corresponding to the highest priority or the delay corresponding to the highest priority Priority, determined as the delay information of the session.
  • the core network device acquires information related to a session of the terminal device, including: the core network device Receiving a session establishment request sent by the terminal device, and acquiring information related to the session according to the session establishment request; or
  • the core network device Determining the delay information of the session according to the information associated with the session, the core network device determining that the information associated with the session is changed, and according to the changed session The associated information determines the latency information for the session.
  • the delay information of the session can be updated in time to further update the handover delay value of the terminal device, thereby avoiding unreasonable handover failure.
  • the method when the core network device is an SMF entity, the method further includes: the SMF entity The AMF entity sends the delay information of the session; or, when the core network device is an AMF entity, the method further includes: determining, by the AMF entity, the handover of the terminal device according to the delay information of the session Delay value. The AMF entity determines the handover delay value according to the delay information of the session, so that the handover delay value is more appropriate and the handover success rate is improved.
  • a second aspect provides a communication method, including: receiving, by an AMF entity, delay information of a session of a terminal device from an SMF entity; and determining, by the AMF entity, a handover delay of the terminal device according to the delay information of the session value.
  • the AMF entity determines the handover delay value according to the delay information of the session, so that the handover delay value is more appropriate and the handover success rate is improved.
  • the method further includes: the AMF entity saving an identifier of the session, delay information of the session, and association between the SMF entities relationship.
  • the AMF entity when the delay information is a delay priority, the AMF entity is configured according to the session And determining the handover delay value of the terminal device, where the AMF entity determines the delay value of the session according to the delay priority of the session and the handover policy of the terminal device; The entity determines a handover delay value of the terminal device according to the delay value of the session.
  • the AMF entity determines, according to a delay value of the session, a handover delay value of the terminal device, including: When the number of sessions of the terminal device is 1, the handover delay value of the terminal device is a delay value of the session; or, when the number of sessions of the terminal device is greater than 1, the terminal device The handover delay value is the minimum of the delay values of all sessions of the terminal device.
  • the method further includes: the AMF entity saves an identifier of the session, and the session time a delay value and an association relationship between the SMF entities; or, the AMF entity saves an identifier of the session, a delay value of the session, a delay priority of the session, and a relationship between the SMF entities connection relation.
  • a core network device comprising means or means for performing the various steps of any of the methods of the above first aspect.
  • a core network device comprising a processor and a memory, the memory is for storing a program, and the processor calls a program stored in the memory to perform any of the methods of the above first aspect.
  • a core network device comprising at least one processing element or chip for performing any of the methods of the above first aspect.
  • a computer readable storage medium comprising the program of the ninth aspect is provided.
  • an AMF entity comprising means or means for performing the various steps of any of the methods of the above second aspect.
  • an AMF entity comprising a processor and a memory, the memory for storing a program, and the processor calling a program stored in the memory to perform any of the methods of the above second aspect.
  • an AMF entity comprising at least one processing element or chip for performing any of the methods of the above second aspect.
  • a program for performing any of the methods of the second aspect above when executed by a processor.
  • a computer readable storage medium comprising the program of the fourteenth aspect is provided.
  • Figure 1 is a network structure diagram
  • FIG. 2 is a flowchart of a communication method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of another communication method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of still another communication method according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an AMF entity according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of hardware of a core network device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of hardware of an AMF entity according to an embodiment of the present invention.
  • Figure 1 provides a network structure that can be applied to next generation communication systems, such as 5G systems.
  • next generation communication systems such as 5G systems.
  • Terminal device may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and various forms of terminals, mobile stations (mobile stations, MS), user equipment (UE), soft terminal, etc., such as water meters, electricity meters, sensors, and the like.
  • MS mobile stations
  • UE user equipment
  • soft terminal etc., such as water meters, electricity meters, sensors, and the like.
  • Access network (AN) node similar to the 3GPP base station or non-3GPP access point (AP) in the traditional network, providing the access function for authorized users in a specific area, and according to the level of the user,
  • the service requirements and the like use different quality transmission tunnels, for example, 5G radio access network (5G-RAN) or next generation radio access network (NG-RAN) equipment.
  • the AN node can manage radio resources and provide access services for the terminal devices, thereby completing the forwarding of control signals and user data between the terminal devices and the core network.
  • the AN node may be connected to the user plane function (UPF) entity through the user plane interface N3 for transmitting data of the terminal device; the AN node establishes a control plane signaling connection through the control plane interface N2 and the AMF entity, To implement functions such as radio access bearer control.
  • UPF user plane function
  • AMF entity mainly responsible for terminal device authentication, mobility management, network slice selection, and SMF entity selection; as an anchor for N1 and N2 signaling connections, providing N1 or N2 session management for SMF entities (session management, SM ) routing of messages; maintaining and managing state information of terminal devices.
  • SMF entity The control plane function that is mainly responsible for the session management of the terminal device, for example, UPF entity selection, IP address allocation, session quality of service (QoS) management, session establishment, modification, and release, acquisition strategy and accounting Policy and Charging Control (PCC) rules, which generate corresponding QoS attributes (QoS profiles) for sessions or QoS flows according to PCC rules.
  • UPF entity selection IP address allocation
  • QoS session quality of service
  • PCC Policy and Charging Control
  • the UPF entity is used as an anchor point for session connection and is responsible for data packet filtering, data transmission or forwarding, rate control, and generation of accounting information for the user equipment.
  • PCF Policy Control Function
  • DN Data network
  • Application function (AF) entity Provides application layer services.
  • each of the above components communicates through a next generation (NG) path, for example, an access network node communicates with a UPF entity over an NG3 path.
  • NG next generation
  • the SMF entity and the AMF entity may be integrated into one physical device, or may be distributed on different physical devices, which is not specifically limited in this application.
  • an embodiment of the present invention provides a communication method, which is specifically as follows.
  • the core network device acquires information related to a session of the terminal device.
  • the core network device may be an AMF entity or an SMF entity.
  • the session-associated information may include at least one of the following information: a QoS profile, a data network name (DNN) corresponding to the session, and a single network slice selection assistance information corresponding to the session. , S-NSSAI), auxiliary information provided by the terminal device, and service and session continuity mode (SSC mode) of the session.
  • a QoS profile a QoS profile
  • DNN data network name
  • S-NSSAI auxiliary information provided by the terminal device
  • SSC mode service and session continuity mode
  • the auxiliary information provided by the terminal device may include delay tolerance, recommended delay value or recommended delay priority.
  • the delay tolerance may be used to indicate the maximum delay that the terminal device or the session can support, which may be a delay value or a delay priority.
  • the recommended delay value and the recommended delay priority may be used. Indicates the delay recommended by the terminal device.
  • the recommended delay value may be a value or a value identifier. For example, a identifies a delay of 0.1 ms.
  • the recommended delay priority may be a priority level. For example, priority 1, priority 2, or The identifier of the priority level, for example, a represents the highest priority.
  • the auxiliary information may be auxiliary information of the terminal device or auxiliary information of the session.
  • the QoS profile may be a QoS profile of the QoS flow of the session, and may specifically include a packet delay, an allocation and retention priority (ARP), a priority level, and a 5QI value. At least one.
  • a session can correspond to multiple QoS flows, and each QoS flow can correspond to a QoS profile.
  • the QoS profile may be pre-stored on the core network device, or may be obtained from unified data management (UDM) or to a policy control function (PCF).
  • UDM unified data management
  • PCF policy control function
  • the core network device is an SMF entity
  • the SMF entity obtains the PCC rule of the session from the PCF entity, and the PCC rule contains the QoS profile of all QoS flows of the session.
  • the SMF entity may also obtain the SM subscription information of the terminal device from the UDM, where the SM subscription information includes a default QoS profile.
  • the DNN corresponding to the session refers to the data used by the session to transmit the DN indicated by the DNN.
  • the S-NSSAI corresponding to the session refers to the information of the slice corresponding to the session, that is, the session is established through the resources of the slice.
  • the slice can be based on several major technical groups such as cloud computing, virtualization, software-defined network, distributed cloud architecture, etc., through the unified programming of the upper layer, the network has the ability to manage and coordinate, thereby implementing a general-purpose physical network infrastructure.
  • a slice can provide the same type of service, or it can be provided to a tenant.
  • the car network is a DN that can be assigned to the car network to service one or more slices.
  • the carrier network assigns an S-NSSAI to each slice.
  • the SSC mode is used to indicate the service and session continuity mode of the session.
  • the SSC mode1 is used to indicate that the anchor point of the IP address is unchanged, and the service continuity is supported.
  • the SSC mode2 is used to indicate that the anchor point of the IP address is variable. The old session is released, and then the terminal device is notified to establish a new session; SSC mode 3 is used to indicate that a new session is established for the terminal device, and then the old session is released.
  • the SSC mode may be carried in a session establishment request sent by the terminal device.
  • the core network device can also obtain the authorized SSC mode of the terminal device from the UDM.
  • the core network device obtains the SM subscription information of the terminal device from the UDM, and the SM subscription information includes the authorized SSC mode.
  • the SSC mode in the session establishment request may belong to the authorized SSC mode in the SM subscription information.
  • the core network device determines, according to the information associated with the session, the delay information of the session.
  • the delay information of the session may be used to indicate a maximum delay that the session can tolerate during the handover process.
  • the maximum time interval from the time when the core network device sends a message (for example, N11, PDU switching request) through the session to the time when the core network device stops waiting for the response of the message is the maximum delay, for example,
  • the AMF entity sends a PDU handover request to the SMF entity, and the AMF entity waits for the SMF entity to respond to the request message for the longest time.
  • the delay information may include a delay value or a delay value range or a delay priority or a delay category.
  • the delay value may be a value or an identifier of the value;
  • the delay value range may be a value interval or a set, or may be an identification interval or set of values;
  • the delay priority may be a delay priority level, for example Priority 1, priority 2, or an identifier of the priority level.
  • a represents the highest priority, and a delay priority may correspond to a delay value or a delay value range;
  • the delay category may be a delay.
  • the identifier of the category may specifically include a high delay category and a low delay category.
  • b represents a low delay category, and a delay category may correspond to a delay value or a range of delay values.
  • the step 202 can be implemented in the following manners:
  • Method 1 The core network device determines the delay information of the session according to the packet delay budget in the QoS profile.
  • the core network device obtains a minimum value of the packet delay value in the QoS profile of all QoS flows of the session, and determines the delay priority corresponding to the minimum value or the minimum value as the delay information of the session.
  • the delay information corresponding to the packet delay value in the default QoS profile may be determined as the delay information of the session.
  • Manner 2 The core network device determines the delay information of the session according to the priority ARP assigned in the QoS profile.
  • the core network device obtains the highest priority of the ARP in the QoS profile of all the QoS flows of the session, and determines the delay value corresponding to the highest priority or the delay priority corresponding to the highest priority as the time of the session. Extended information.
  • the delay information corresponding to the ARP in the default QoS profile may be determined as the delay information of the session.
  • the third network device determines the delay tolerance type of the session according to at least one of the DNN corresponding to the session and the S-NSSAI corresponding to the session, and determines the delay information of the session according to the delay tolerance type of the session.
  • determining the delay information of the session according to the delay tolerance type of the session includes: determining the session according to a correspondence between a preset delay tolerance type and delay information, and a delay tolerance type of the session.
  • Delay information The correspondence between the preset delay tolerance type and the delay information may include: low delay tolerance corresponding to the first delay information, and high delay tolerance corresponding to the second delay information; wherein, the first delay information and the first delay information
  • the second delay information is a delay value, and the first delay information is smaller than the second delay information; or the first delay information and the second delay information are delay priorities, and the first delay The information is higher than the second delay information.
  • the delay tolerance type may include high latency tolerance and low latency tolerance, high latency tolerance refers to a maximum delay that the session can tolerate; low latency tolerance refers to a maximum delay that the session can tolerate. small.
  • the core network device determines the delay information of the session according to the correspondence between the DNN and the delay information and the DNN corresponding to the session.
  • the correspondence between the DNN and the delay information may include: one DNN corresponding to a preset delay information; or a type of DNN corresponding to a preset delay information, which is not limited.
  • the core network device determines the delay information of the session according to the correspondence between the S-NSSAI and the delay information and the S-NSSAI corresponding to the session.
  • the correspondence between the S-NSSAI and the delay information may be that one S-NSSAI corresponds to a preset delay information.
  • the correspondence between the foregoing S-NSSAI and the delay information may be replaced by the correspondence between the network type to which the S-NSSAI belongs and the delay information.
  • the S-NSSAI corresponding to the session is a slice of the Internet of Vehicles, and the Internet of Vehicles corresponds to a preset delay information, and the delay information corresponding to the Internet of Vehicles can be determined as the delay information of the session.
  • the core network device determines the delay information of the session according to the correspondence between the preset SSC mode and the delay information and the SSC mode of the session.
  • the corresponding relationship between the SSC mode and the delay information may include: SSC mode1 or SSC mode3 corresponding to the first delay information, and SSC mode2 corresponding to the second delay information; wherein, the first delay information and the first
  • the second delay information may be a delay value.
  • the first delay information is smaller than the second delay information.
  • the first delay information and the second delay information may all be delay priorities. The first delay information is higher than the second delay information.
  • the core network device determines the auxiliary information provided by the terminal device as the delay information of the session. For example, when the auxiliary information is the recommended delay value or the recommended delay priority of the session, the recommended delay value or the recommended delay priority may be determined as the delay information of the session.
  • Manner 8 Determine the delay information of the session according to the priority level in the QoS profile.
  • the core network device obtains the minimum value of the priority level in the QoS profile of all the QoS flows of the session, and determines the delay information corresponding to the minimum value as the delay information of the session.
  • the core network device may be pre-configured with the correspondence between the priority level and the delay information, or may dynamically obtain the correspondence from other devices, and is not limited.
  • the delay information of all QoS flows may be determined according to the correspondence between the priority level and the delay information, and a delay information is selected in the delay information of all QoS flows (for example, the highest priority, or time)
  • the delay value is the limit information of the session, and is not limited.
  • Manner 9 Determine the delay information of the session according to the 5QI value in the QoS profile.
  • a 5QI value may indicate a packet delay budget and a priority level.
  • the core network device may determine delay information of the QoS flow according to the packet delay budget and the priority level indicated by the 5QI value. Specifically, there may be a corresponding relationship between the packet delay budget and the delay information, and the relationship between the priority level and the delay information may also be determined, and two delay information are determined according to the two parameters and the two correspondences respectively, and One delay information (for example, the highest priority or the smallest delay value) is taken as the delay information of the QoS flow in the two delay information. Further, a delay information (for example, the highest priority or the smallest delay value) is taken as the delay information of the session in the delay information of all the QoS flows of the session.
  • the delay information determined according to the packet delay budget and the priority level is different; assuming the priority level is different, the packet delay budget is the same, according to the packet delay budget and the The delay information determined by the priority level is also different.
  • the mode 9 may be replaced by: determining the delay information of the session according to the priority level and the packet delay budget in the QoS profile.
  • the core network device may determine the session according to any one of the foregoing manners 1 to 6. The delay information, if the determined delay information exceeds the delay tolerance of the session, the delay tolerance of the terminal device is used as the delay information of the session, and is not enumerated.
  • the core network device determines the delay information of the session according to the information associated with the session of the terminal device, so as to further determine the handover delay value of the terminal device according to the delay information of the session (that is, the AMF in the handover process)
  • the entity can wait for the maximum waiting time from the SMF entity to ensure that the session is switched to meet the specific delay requirement, so that the data service corresponding to the session continues, and the session success rate is improved.
  • the delay information of the session in the embodiments of the present invention can be applied not only in the handover process but also in other processes, including: a service request procedure or a registration procedure. ), or a radio access network (RAN) side UE context release in the AN procedure, or a UE initiated packet data unit (PDU) session establishment procedure (UE-requested) Message interaction between AMF entities and SMF entities in PDU Session Establishment).
  • the AMF entity sends an N11 message (carrying the PDU session ID, UE location information) to the SMF entity, and can use the delay information of the session as the waiting SMF entity to send the N11 message (carrying the N1 session management information (PDU session).
  • the AMF entity entity sends an N11 request message to the SMF entity, and the session delay information may be used as the time for waiting for the SMF entity to send the N11 response to the AMF entity.
  • the AMF entity sends an N11 PDU session deactivation request to the SMF entity, and the session delay information may be used as the waiting SMF entity to send the N11 PDU session deactivation request (N11 PDU). Session deactivation Response) The time given to the AMF entity.
  • the step 201 may include: receiving, by the core network device, a session establishment request sent by the terminal device, and acquiring information related to the session according to the session establishment request.
  • the NAS message sent by the terminal device carries a session establishment request
  • the session establishment request may include at least one of an SSC mode and an auxiliary information provided by the terminal device, where the NAS message may also carry the DNN, and the S-NSSAI At least one of them.
  • the NAS message carries a session establishment request, DNN, and S-NSSAI.
  • the core network device is an AMF entity
  • the session associated information may be obtained from the NAS message;
  • the AMF entity may obtain a session establishment request from the NAS message, and establish the session.
  • the request is sent to the SMF entity.
  • the AMF entity further carries at least one of the DNN and the S-NSSAI
  • the AMF entity also sends at least one of the DNN and the S-NSSAI to the SMF entity.
  • the session establishment request is a trigger condition for the core network device to acquire information associated with the session.
  • the default QoS profile of the terminal device obtained from the UDM when the core network device receives the session establishment request sent by the terminal device.
  • the core network device acquires the PCC rule of the session from the PCF entity.
  • the SMF entity acquires the S-NSSAI of the session from the AMF entity when receiving the session establishment request sent by the terminal device.
  • the core network device can receive the session establishment request sent by the terminal device indirectly through other network side devices, and is not limited.
  • the core network device acquires session-related information during session establishment to further determine session delay information.
  • the step 202 includes: determining, by the core network device, that the information associated with the session is changed, and determining the delay information of the session according to the information associated with the changed session.
  • the core network device determines the delay information of the session according to the information associated with the changed session.
  • the delay information determined according to the changed session associated information may also change. Assuming that the minimum value becomes smaller, the maximum delay indicated by the delay information also becomes smaller; assuming that the minimum value becomes larger, the maximum delay indicated by the delay information also becomes larger.
  • the maximum delay indicated by the delay information becomes smaller; the highest priority among the ARPs of all QoS flows in the QoS profile becomes lower. , the maximum delay indicated by the delay information will become larger.
  • the delay information of the session is determined according to the information related to the changed session, and may be implemented by using the foregoing manners one to nine, and details are not described herein.
  • the core network device can update the delay information of the session in time, so that the core network device (for example, the AMF entity) timely updates the handover delay value (for example, the AMF entity in the handover process can wait for the maximum response from the SMF entity. Waiting time), so as to ensure that the switching of the session can meet the specific delay requirement, and avoid the session switching failure caused by the unsuccessful update of the handover delay value.
  • the core network device for example, the AMF entity
  • the handover delay value for example, the AMF entity in the handover process can wait for the maximum response from the SMF entity. Waiting time
  • the core network device is an AMF entity
  • the foregoing method further includes:
  • the AMF entity determines, according to the delay information of the session, a handover delay value of the terminal device.
  • step 203 can include steps 2031-2032.
  • the AMF entity determines the delay value of the session according to the delay priority of the session and the handover policy of the terminal device.
  • the switching policy of the terminal device may include a correspondence between the delay priority and the delay value, and the switching policy may be obtained from the PCF entity, and is not restricted.
  • the switching policy in step 2031 can be replaced with a correspondence between the preset delay priority and the delay value, which is not limited.
  • the AMF entity determines, according to the delay value of the session, a handover delay value of the terminal device.
  • the delay value corresponding to the delay priority is obtained.
  • the step 2032 may determine the handover delay value of the terminal device according to the delay information of all the sessions of the terminal device, or determine or update the handover delay value of the terminal device for each session delay information, and may also During the session switching process of the terminal device, the handover delay value of the terminal device is updated according to the delay information of the session.
  • step 2032 includes:
  • the handover delay value of the terminal device is a delay value of the session
  • the handover delay of the terminal device is a minimum value of delay values of all sessions of the terminal device.
  • the AMF entity updates the handover delay value of the terminal device according to the delay information of the session.
  • the method in the above example can be used to determine the handover delay value of the terminal device, when the AMF entity obtains
  • the delay information of the other session for example, the session 2 of the terminal device
  • the handover delay value of the terminal device may be updated according to the delay information of the session 1 and the session 2; when the AMF entity obtains the delay information of the session 3,
  • the handover delay value of the terminal device may be updated according to the delay information of session 1, session 2, and session 3.
  • the handover delay value of the terminal device is dynamically updated, so that the session of the terminal device can satisfy the handover delay value as much as possible, and the success rate of the session handover is improved.
  • the handover delay value is updated or determined according to the success of the session handover.
  • session 1 is maintained by SMF1, corresponding to a delay value of 1, such as 10 ms
  • session 2 is maintained by SMF2, corresponding to a delay value of 2, such as 20 ms
  • session 3 is maintained by SMF3, corresponding to a delay value of 3
  • the AMF entity can determine the handover delay value according to the delay values of the four sessions as follows:
  • Mode 1 the AMF entity simultaneously sends a session switch request to SMF1, SMF2, SMF3, and SMF4, and starts a timer, starting from 0.
  • the AMF entity receives the handover response message of the session 1, and the timer does not exceed the delay value of the session 1 by 10 ms, for example, when the timer is 3 ms, the handover delay of the terminal device can be updated according to the delay value of the session 1.
  • the AMF entity receives the handover response message of session 2 the delay value, and the timer count does not exceed the delay value of session 2 by 20 ms.
  • the handover delay value is 10 ms; when the AMF entity receives the handover response message of the session 3, the timer does not exceed the current handover delay value, and the timer does not exceed the delay value of the session 3.
  • the handover delay value is kept unchanged, that is, the handover delay value is 10ms.
  • the AMF entity When the timing of the timer reaches the handover delay value (10 ms), if the handover response message of the session 4 has not been received yet, the AMF entity immediately sends an N2 interface handover request message to the target base station. Of course, when the AMF entity receives the handover response message of all sessions, the AMF entity immediately sends an N2 interface handover request message to the target base station even if the timer has not reached the current handover delay value.
  • Mode 2 The AMF entity simultaneously sends a session switch request to SMF1, SMF2, SMF3, and SMF4, and starts the timer to start timing from 0.
  • the AMF entity receives the session 2 response response message, the timer does not exceed the current switch.
  • the delay value, and the timer of the timer does not exceed the delay value of the session 2 by 20 ms.
  • the handover delay value of the terminal device may be updated according to the delay value of the session 2 (for example, the time of the session 2)
  • the handover delay is continued.
  • the AMF entity immediately sends an N2 interface handover request message to the target base station.
  • the AMF entity receives the handover response message of all sessions, even if the Timer does not reach the handover delay value, the AMF entity immediately sends an N2 interface handover request message to the target base station.
  • the handover delay value of the terminal device is dynamically updated, so that the session of the terminal device can satisfy the handover delay value as much as possible, and the success rate of the session handover is improved.
  • the AMF entity may obtain the delay information of the session in the session establishment process, or temporarily obtain the delay information of the session during the handover process, for example, the SMF entity will session the session in the session handover response.
  • the delay information is sent to the AMF entity.
  • step 203 is step 2032, and details are not described herein.
  • the above method further includes:
  • the AMF entity saves the identifier of the session, the delay information of the session, and the association relationship between the SMF entities of the session.
  • the SMF entity in the foregoing association relationship may be embodied by an identifier, and is not described herein.
  • the AMF entity determines the delay value of the terminal device according to the delay information of the session, so as to ensure successful handover of all sessions of the terminal device.
  • the core network device is an SMF entity
  • the foregoing method further includes:
  • the SMF entity sends the delay information of the session to the AMF entity.
  • the delay information of the session may be carried in a session request request acknowledgement (SM request ack) message and sent to the AMF entity.
  • SM request ack session request request acknowledgement
  • the delay information of the above session may also be carried in any message (for example, a session switch response message) sent by the SMF entity to the AMF entity in the HO process.
  • the AMF entity may further determine the handover delay value of the terminal device according to the delay information, which may be implemented by using the method provided in step 203, or may be implemented as follows:
  • the AMF entity updates the handover delay value of the terminal device according to the received delay information of the session. For example, if the terminal device has three sessions, the method in step 2032 above may be used to determine the handover delay value of the terminal device after the AMF entity receives the delay information of any session (for example, session 1).
  • the AMF entity receives the delay information of the other session (eg, session 2) of the terminal device
  • the handover delay value of the terminal device may be updated according to the delay information of the session 1 and the session 2; when the AMF entity receives the session 3
  • the handover delay value of the terminal device may be updated according to the delay information of the session 1, the session 2, and the session 3.
  • the handover delay value of the terminal device is dynamically changed, so that the session of the terminal device can satisfy the handover delay value as much as possible, and the success rate of the session handover is improved.
  • the SMF entity sends the delay information of the session to the AMF entity, so that the AMF entity further determines the handover delay value of the terminal device according to the delay information of the session.
  • an embodiment of the present invention provides another communication method, which is specifically as follows.
  • the SMF entity acquires information related to a session of the terminal device.
  • the SMF entity determines, according to the information associated with the session, the delay information of the session.
  • the SMF entity sends the delay information of the session to the AMF entity.
  • steps 301 and 302 reference may be made to the related description of the steps 201-202 in the embodiment shown in FIG. 2, and the step 303 may be referred to the step 203', and details are not described herein.
  • the AMF entity receives the delay information of the session of the terminal device from the SMF entity.
  • the AMF entity determines, according to the delay information of the session, the handover delay value of the terminal device.
  • the delay information may include a delay value or a delay priority.
  • the handover delay value is used to indicate the maximum waiting time that the AMF entity can wait for the response from the SMF entity in the handover process, so as to ensure that the handover of the session can meet the specific delay requirement, thereby ensuring that the corresponding data service of the session can continue.
  • step 203 For details, refer to the related description of step 203, and details are not described herein again.
  • the foregoing method further includes:
  • the AMF entity saves the identifier of the session, the delay information of the session, and the association relationship between the SMF entities.
  • the foregoing method further includes:
  • the AMF entity saves the identifier of the session, the delay value of the session, and the association relationship between the SMF entities; or
  • the AMF entity stores the identifier of the session, the delay value of the session, the delay priority of the session, and the association relationship between the SMF entities.
  • the SMF entity determines the delay information of the session according to the information associated with the session of the terminal device, and sends the delay information of the session to the AMF entity, where the AMF entity determines the terminal according to the delay information of the session.
  • the switch delay value of the device is used to ensure that the session is switched to meet the specific delay requirement, so that the data service corresponding to the session continues, and the session success rate is improved.
  • the sessions mentioned in the foregoing method embodiments may all be PDU sessions, and are not predefined.
  • the PDU session is taken as an example for description.
  • the embodiment of the present invention provides another communication method, which is specifically as follows.
  • the terminal device sends a PDU session establishment request to the AMF entity.
  • the PDU session establishment request may be carried in the NAS signaling, where the NAS signaling may be mobility management (MM) NAS signaling, and the NAS signaling may further include an S-NSSAI corresponding to the PDU session.
  • the PDU session establishment request may carry a PDU type (PDU Type), which is used to indicate an IP address type of the PDU session, for example, IPv4 or IPv6; and may also carry an SSC mode, and may also carry auxiliary information, for example: Suggested delay time.
  • PDU Type PDU type
  • SSC mode SSC mode
  • auxiliary information for example: Suggested delay time
  • the AMF entity selects an SMF entity for the PDU session according to the PDU session establishment request.
  • the PDU session establishment request is carried in the NAS message, and the NAS message may also carry the S-NSSAI and the DNN.
  • the AMF entity may select the SMF entity according to the S-NSSAI and the DNN obtained from the NAS message, and belongs to the prior art. ,No longer.
  • the AMF entity sends a PDU session establishment request to the selected SMF entity.
  • the PDU session establishment request may be sent to the SMF entity through a session management request (SM request) message.
  • SM request session management request
  • the step 403 further includes: the AMF entity sending the S-NSSAI and/or the DNN to the SMF entity.
  • the SMF entity acquires the SM subscription information of the terminal device from the UDM.
  • the SM subscription information may be related to the SM subscription information, for example, an authorized PDU type, an authorized SSC mode, and a default QoS profile.
  • the SMF entity acquires PCC rules of the PDU session from the PCF entity.
  • the PCC rules may include a QoS profile of the PDU session.
  • the SMF entity initiates a PDU-CAN Session Establishment procedure to the PCF entity, during which the PCF entity may send the PCC rules to the SMF entity.
  • steps 404-405 are optional steps. If the SSM entity selected in step 403 does not store the SM subscription information of the terminal device, step 404 is performed.
  • the SMF entity determines, according to the information associated with the PDU session, delay information of the PDU session.
  • the information associated with the PDU session may include at least one of the following: a QoS profile, a DNN, an S-NSSAI, an assistant information, and an SSC mode.
  • the QoS profile may be the default QoS profile in step 404, the QoS profile in the PCC rules in step 405, or a combination of the two.
  • the SSC mode may be the SSC mode in the step 401, or the authorized SSC mode in the step 404, or a combination of the two, and is not limited.
  • the DNN For the delay information and the QoS profile, the DNN, the S-NSSAI, the assistant information, and the SSC mode, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein.
  • the SMF entity sends the delay information of the PDU session to the AMF entity.
  • the delay information of the PDU session may be sent to the AMF entity by being carried in the SM request ACK message.
  • the AMF entity saves an association between an ID of the SMF entity, an ID of the PDU session, and delay information.
  • the association relationship saved in step 408 may also be the ID of the SMF entity, the ID of the PDU session, the delay priority of the PDU session, and the association between the delay values corresponding to the delay priority. relationship.
  • step 408 is optional, that is, the AMF entity may not save the delay information of the session.
  • the AMF entity determines, according to the delay information of the PDU session, a handover delay value of the terminal device.
  • step 409 refer to the related description of step 203, and details are not described herein.
  • step 409 may be performed after the PDU session establishment process ends; when the terminal device has at least two sessions, step 409 may collect all the terminal devices in the AMF entity. The delay information of the session is executed afterwards and is not restricted.
  • step 409 may be performed after steps 409, which is not limited.
  • the SMF entity determines the delay information of the session according to the information associated with the session of the terminal device, and sends the delay information of the session to the AMF entity, where the AMF entity determines the terminal according to the delay information of the session.
  • the switch delay value of the device is used to ensure that the session is switched to meet the specific delay requirement, so that the data service corresponding to the session continues, and the session success rate is improved.
  • the foregoing method further includes:
  • the SMF entity determines the update delay information of the PDU session according to the information related to the changed session, and sends the update delay information of the PDU session to the AMF entity.
  • the update delay information of the PDU session may be sent to the AMF entity by using an N11 message.
  • the AMF entity updates the handover delay of the terminal device according to the update delay information of the PDU session.
  • the method may further include: the AMF entity updating the association relationship in step 408 according to the update delay information of the PDU session.
  • an embodiment of the present invention provides another communication method, which is specifically as follows.
  • the terminal device sends a PDU session establishment request to the AMF entity.
  • the AMF entity acquires information associated with the PDU session.
  • the PDU session establishment request is carried in the NAS message, and the NAS message may also carry the S-NSSAI and the DNN.
  • the AMF entity may select the SMF entity according to the S-NSSAI and the DNN obtained from the NAS message, and belongs to the prior art. ,No longer.
  • the AMF entity determines, according to the information associated with the PDU session, delay information of the PDU session.
  • step 503 refer to the related description of step 202, and details are not described herein.
  • the AMF entity selects an SMF entity for the PDU session according to the PDU session establishment request.
  • the AMF entity may select an SMF entity according to the S-NSSAI and DNN obtained in the NAS message, which belongs to the prior art and will not be described again.
  • steps 503 and 504 may be interchanged and is not limited.
  • the AMF entity sends the PDU session establishment request to the selected SMF entity.
  • the PDU session establishment request may be sent to the SMF entity through a session management request (SM request) message.
  • SM request session management request
  • the SMF entity receives the PDU session establishment request, and selects a UPF entity for the PDU session.
  • the SMF entity sends a PDU session establish accept to the AMF entity.
  • the PDU session establishment acceptance may be carried in the SM request ack message.
  • the AMF entity saves an association between an SMF entity ID, a PDU session ID, and a delay information.
  • the association relationship saved in step 508 may also be an association between an SMF entity ID, a PDU session ID, a delay priority of the PDU session, and a delay value corresponding to the delay priority.
  • the AMF entity determines, according to the delay information of the PDU session, a handover delay value of the terminal device.
  • the step is optional, that is, the AMF entity may not save the delay information of the session.
  • step 509 refer to the related description of step 203, and details are not described herein.
  • step 509 may be performed after the PDU session establishment process ends; when the terminal device has at least two sessions, step 509 may collect all the terminal devices in the AMF entity. The delay information of the session is executed afterwards and is not restricted.
  • the AMF entity determines the delay information of the session according to the information associated with the session of the terminal device, and determines the handover delay value of the terminal device according to the delay information of the session, so as to ensure that the session switching meets the specific
  • the delay requirement requires that the data service corresponding to the session continues, and the success rate of the session is improved.
  • the foregoing method further includes:
  • the AMF entity determines the update delay information of the PDU session according to the information associated with the changed session.
  • the information about the update delay of the PDU session is determined according to the information related to the changed session. For details, refer to the related description in step 202, and details are not described herein.
  • the AMF entity updates the handover delay of the terminal device according to the update delay information of the PDU session.
  • the method may further include: the AMF entity updating the association relationship in step 508 according to the update delay information of the PDU session.
  • the embodiment of the present invention provides a core network device 600, where the core network device 600 includes an obtaining unit 601 and a determining unit 602.
  • the obtaining unit 601 is configured to acquire information related to the session of the terminal device.
  • the determining unit 602 is configured to determine delay information of the session according to the information associated with the session acquired by the obtaining unit 601.
  • the session-related information includes at least one of the following information: a QoS profile of the QoS flow of the session, a DNN corresponding to the session, an S-NSSAI corresponding to the session, auxiliary information provided by the terminal device, and an SSC mode of the session.
  • the delay information may include a delay value or a delay priority.
  • the QoS profile, the DNN, the S-NSSAI, the auxiliary information provided by the terminal device, the delay value, the delay priority, and the SSC mode can be referred to the related description in the embodiment shown in FIG. 2, and details are not described herein.
  • the method for determining the delay information of the session according to the information associated with the session may be performed by using the method of the method provided in the step 202, and may be a combination of the modes.
  • the delay information of the session is determined according to the priority level in the QoS profile.
  • the SSC mode 1 or the SSC mode 3 corresponds to the first time delay information
  • the SSC mode 2 corresponds to the second time delay information
  • the first delay information and the second delay information are both delay values, and the first delay information is smaller than the second delay information; or the first delay information and the second delay information are both delay priority. Level, and the first delay information is higher than the second delay information.
  • the foregoing determining the delay information of the session according to the data packet delay in the QoS profile includes:
  • the delay priority corresponding to the minimum or minimum value is determined as the delay information of the session.
  • determining the delay information of the session according to the ARP in the QoS profile including:
  • the delay value corresponding to the highest priority or the delay priority corresponding to the highest priority is determined as the delay information of the session.
  • the foregoing determining the delay information of the session according to the delay tolerance type of the session includes:
  • the delay information of the session is determined according to the correspondence between the preset delay tolerance type and the delay information and the delay tolerance type of the session.
  • the correspondence between the preset delay tolerance type and the delay information includes: low delay tolerance corresponding to the first delay information, and high delay tolerance corresponding to the second delay information.
  • the first delay information and the second delay information are both delay values, and the first delay information is smaller than the second delay information; or the first delay information and the second delay information are both delay priority. Level, and the first delay information is higher than the second delay information.
  • the obtaining the session-related information of the terminal device includes: receiving a session establishment request sent by the terminal device, and acquiring the session-related information according to the session establishment request.
  • determining the delay information of the session according to the information associated with the session including: determining that the information associated with the session is changed, and determining the delay information of the session according to the information associated with the changed session.
  • the core network device 600 may be an AMF entity or an SMF entity.
  • the core network device 600 may further include:
  • the sending unit 603 is configured to send the delay information of the session to the AMF entity.
  • the determining unit 602 is further configured to determine a handover delay value of the terminal device according to the delay information of the session.
  • the core network device 600 may be used to perform the steps of the core network device in the method embodiment shown in FIG. 2, or the steps of the SMF entity in the embodiment shown in FIG. 3 or 4, or in the embodiment shown in FIG.
  • steps of the AMF entity related steps or nouns, refer to the method embodiments above, and no further details are provided.
  • the core network device determines the delay information of the session according to the information associated with the session of the terminal device, so as to further determine the handover delay value of the terminal device according to the delay information of the session, so as to ensure that the session switching is satisfied.
  • the specific time delay requirement is that the data service corresponding to the session continues, and the success rate of the session is improved.
  • an embodiment of the present invention provides an AMF entity 700, which includes a receiving unit 701 and a determining unit 602.
  • the receiving unit 701 is configured to receive, from the SMF entity, delay information of the session of the terminal device.
  • the determining unit 702 is configured to determine a handover delay value of the terminal device according to the delay information of the session received by the receiving unit 701.
  • the delay information may include a delay value or a delay priority.
  • the AMF entity 700 further includes:
  • the first saving unit 703 is configured to save the identifier of the session, the delay information of the session, and the association relationship between the SMF entities.
  • the foregoing determining the handover delay value of the terminal device according to the delay information of the session includes:
  • the handover delay value of the terminal device is determined according to the delay value of the session.
  • determining, according to the delay value of the session, the handover delay value of the terminal device including:
  • the handover delay value of the terminal device is the delay value of the session
  • the handover delay of the terminal device is the minimum value of the delay values of all sessions of the terminal device.
  • the AMF entity 700 further includes:
  • the second saving unit 704 is configured to save the identifier of the session, the delay value of the session, and the association relationship between the SMF entities; or save the identifier of the session, the delay value of the session, the delay priority of the session, and the SMF entity. The relationship between the two.
  • AMF entity 700 can be used to perform the steps of the AMF entity in the embodiment shown in FIG. 3 or 5.
  • steps or nouns refer to the foregoing method embodiments, and details are not described herein.
  • the AMF entity provided by the foregoing embodiment receives the delay information of the session sent by the SMF entity, and determines the handover delay value of the terminal device according to the delay information of the session, so as to ensure that the session switching meets a specific delay requirement, so that the The data service corresponding to the session continues, and the success rate of the session is improved.
  • an embodiment of the present invention provides another core network device 800, which may be an SMF entity or an AMF entity.
  • the core network device 800 includes a memory 801, a processor 802, and a communication interface 803.
  • the processor 802 is configured to execute the program stored in the memory 801 to implement the action of the core network device in the method embodiment shown in FIG. 2, or the action of the SMF entity in the embodiment shown in FIG. 3 or 4, or the implementation shown in FIG. The action of the AMF entity in the example.
  • the processor 802 may be one or more, and is not limited.
  • the embodiment of the present invention provides another core network device, where the core network device may include at least one chip, and the at least one chip is used to perform the action of the core network device in the method embodiment shown in FIG. 2, or FIG. 3 or FIG.
  • an embodiment of the present invention provides another AMF entity 900, which includes a memory 901, a processor 902, and a communication interface 903.
  • the processor 902 is configured to execute a program stored in the memory 901 to implement an action of the AMF entity in the embodiment shown in FIG. 3 or 5.
  • the processor 902 may be one or more, and is not limited.
  • the embodiment of the present invention provides another AMF entity, which may include at least one chip, and the at least one chip is used to perform an action of the AMF entity in the embodiment shown in FIG. 3 or 5.
  • the embodiment of the present invention further provides a communication system, which includes an SMF entity and an AMF entity.
  • the SMF entity may refer to the core network device shown in FIG. 6 or 8.
  • the AMF entity may refer to FIG. 7 or 9. AMF entity.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé, un appareil et un système de communication. Le procédé comporte les étapes suivantes: un dispositif de réseau central obtient des informations associées à une session d'un dispositif terminal; le dispositif de réseau central détermine des informations de retard de la session d'après les informations associées à la session. Selon le procédé, une valeur de retard de transfert d'un dispositif terminal peut être déterminée d'après des informations de retard d'une session; ainsi, le taux de réussite des transferts de session est amélioré.
PCT/CN2018/088540 2017-06-19 2018-05-26 Procédé, appareil et système de communication Ceased WO2018233451A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710465300.0 2017-06-19
CN201710465300.0A CN109150808B (zh) 2017-06-19 2017-06-19 通信方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2018233451A1 true WO2018233451A1 (fr) 2018-12-27

Family

ID=64735482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088540 Ceased WO2018233451A1 (fr) 2017-06-19 2018-05-26 Procédé, appareil et système de communication

Country Status (2)

Country Link
CN (1) CN109150808B (fr)
WO (1) WO2018233451A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113630816A (zh) * 2020-05-06 2021-11-09 华为技术有限公司 一种数据传输方法及装置
WO2022021317A1 (fr) * 2020-07-31 2022-02-03 Zte Corporation Temps de survie pour relâchement des exigences de qualité de service
EP3952437A4 (fr) * 2019-04-02 2022-06-01 Tencent Technology (Shenzhen) Company Limited Procédé et appareil de communication, support lisible par ordinateur et dispositif électronique

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115988579A (zh) 2019-01-10 2023-04-18 华为技术有限公司 实现业务连续性的方法、装置及系统
CN111436160B (zh) * 2019-01-15 2022-04-29 华为技术有限公司 一种局域网通信方法、装置及系统
CN114747192B (zh) * 2019-12-06 2024-09-24 索尼集团公司 控制设备、基站设备、控制方法和连接方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119581A (zh) * 2006-08-04 2008-02-06 华为技术有限公司 演进网络中传递服务质量信息的方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001184A (zh) * 2006-01-09 2007-07-18 华为技术有限公司 一种接入分组数据网络的方法
CN101043414B (zh) * 2006-03-20 2010-05-12 华为技术有限公司 一种保证无线局域网和封包数据网关的服务质量配置一致性的方法
CN101159969B (zh) * 2007-11-19 2011-04-27 电子科技大学 一种异构无线环境下基于目录的接入网融合方法
CN102281290B (zh) * 2011-07-18 2014-06-11 北京邮电大学 一种PaaS云平台的仿真系统及方法
CN103987092B (zh) * 2013-02-08 2018-09-21 华为终端（东莞）有限公司 切换过程中选择网络设备的方法和装置
CN105704753B (zh) * 2014-11-26 2018-09-07 电信科学技术研究院 一种进行数据传输的方法、系统和设备
CN105760324B (zh) * 2016-05-11 2019-11-15 北京比特大陆科技有限公司 数据处理装置和服务器
CN106851856B (zh) * 2016-12-23 2019-04-09 电信科学技术研究院有限公司 一种基于移动中继的无线通信建立方法及网络设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119581A (zh) * 2006-08-04 2008-02-06 华为技术有限公司 演进网络中传递服务质量信息的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"23.502: Update of Handover without Xn Interface", SA WG2 MEETING #121, S2-173265, 19 May 2017 (2017-05-19), XP051268720 *
"TS 23.502: Updates to Inter NG-RAN Node HO Procedure (Section 4.9.1.2.2)", SA WG2 MEETING #121, S2-173348, 19 May 2017 (2017-05-19), XP051268798 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3952437A4 (fr) * 2019-04-02 2022-06-01 Tencent Technology (Shenzhen) Company Limited Procédé et appareil de communication, support lisible par ordinateur et dispositif électronique
US12075286B2 (en) 2019-04-02 2024-08-27 Tencent Technology (Shenzhen) Company Limited Communication method and apparatus, computer-readable medium and electronic device
CN113630816A (zh) * 2020-05-06 2021-11-09 华为技术有限公司 一种数据传输方法及装置
WO2022021317A1 (fr) * 2020-07-31 2022-02-03 Zte Corporation Temps de survie pour relâchement des exigences de qualité de service

Also Published As

Publication number Publication date
CN109150808A (zh) 2019-01-04
CN109150808B (zh) 2021-11-09

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
US12356491B2 (en) Session management method, apparatus, and system
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US11381961B2 (en) Method, apparatus, network device, and system for releasing IP address
CN111684774B (zh) 移动边缘计算(mec)中的服务质量(qos)控制方法、系统
CN110731099B (zh) 用于用户平面功能分配的技术
CN113507730B (zh) 会话管理的方法、装置、设备及系统
EP4024956A1 (fr) Procédé, appareil et système de communication
US12004264B2 (en) Session management method, device, and system
JP7706535B2 (ja) リロケーション時にエッジアプリケーションサーバへのシームレスなサービス継続性を調整するためのメカニズム
KR102820270B1 (ko) 브로드캐스트 서비스 및 관련 기기의 모드 스위칭 방법
WO2019033796A1 (fr) Procédé de traitement de session, et dispositif associé
WO2018233451A1 (fr) Procédé, appareil et système de communication
WO2019158093A1 (fr) Procédé et dispositif de détermination de mode ssc
CN112954768A (zh) 通信方法、装置及系统
WO2022052875A1 (fr) Procédé de communication inter-région de terminal, dispositif d'élément de réseau, et support de stockage
WO2019238050A1 (fr) Procédé et appareil de communication
CN117981393A (zh) 用于进行网络切片替换的方法、设备和系统
WO2021115429A1 (fr) Appareil et procédé de communication
CN110708727B (zh) 搬迁管理方法及装置
CN117062019A (zh) 一种策略协同方法、网络功能和计算机可读存储介质
WO2021138784A1 (fr) Procédé, appareil et système d'accès au réseau
WO2023061207A1 (fr) Procédé de communication, appareil de communication et système de communication
CN118803602A (zh) 通信方法、装置及电子设备

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: 18821047

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18821047

Country of ref document: EP

Kind code of ref document: A1