WO2019196746A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2019196746A1
WO2019196746A1 PCT/CN2019/081548 CN2019081548W WO2019196746A1 WO 2019196746 A1 WO2019196746 A1 WO 2019196746A1 CN 2019081548 W CN2019081548 W CN 2019081548W WO 2019196746 A1 WO2019196746 A1 WO 2019196746A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
information
core network
network device
terminal
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/CN2019/081548
Other languages
English (en)
French (fr)
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
Priority to JP2020551532A priority Critical patent/JP7125041B2/ja
Priority to EP19784604.1A priority patent/EP3771285B1/en
Priority to KR1020207030403A priority patent/KR20200134293A/ko
Priority to BR112020020888-4A priority patent/BR112020020888A2/pt
Publication of WO2019196746A1 publication Critical patent/WO2019196746A1/zh
Priority to US17/066,927 priority patent/US11470671B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • 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
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • 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/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/326—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by proximity to another entity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
  • a fifth-generation (fifth-generation, 5G) wireless communication system for a radio resource control (RRC) connection state, the connection state is inactive, access and mobility management functions (core access and mobility)
  • RRC radio resource control
  • the state of the terminal stored on the management function (AMF) is the CM-Connected state, and the location information in the context of the terminal that the AMF considers to be the terminal is the current location information of the terminal.
  • the terminal does not have a cell handover, if the terminal is from a radio access network (RAN) 1 node (in the service area of the user plane function (UPF) 1) After the coverage moves to the coverage of the RAN2 node (not in the service area of UPF1), the location information in the context of the terminal saved on the AMF is still information indicating that the terminal is located within the coverage of the RAN1 node. But in fact the terminal has moved to the coverage of the RAN2 node. If the effective area of the downlink information of the terminal is consistent with the service area of the UPF, the AMF judges that the terminal is located in the effective area of the downlink information according to the location information in the context of the saved terminal is erroneous. In this case, if the AMF sends the downlink information used to activate the PDU session to the RAN1 node, the PDU session activation fails.
  • RAN radio access network
  • UPF user plane function
  • the embodiment of the present application provides a communication method and apparatus for solving the problem that a PDU session activation failure of a terminal in an inactive state is failed.
  • a communication method is provided, the method being applied to a scenario in which a terminal in which an RRC connection state is in an inactive state moves from a coverage of a first RAN node to a coverage of a second RAN node, where the method includes The first core network device sends first downlink information to the first RAN node; the first core network device receives indication information from the first RAN node; the first core network device according to the indication information Sending second downlink information to the second RAN node.
  • the indication information may be used to indicate that the first RAN node fails to process the first downlink information.
  • the method receives the first RAN through the first core network device.
  • the indication information sent by the node after the processing of the first downlink information fails, and the second downlink information is sent to the second RAN node according to the indication information, so that the second downlink information can be successfully processed by the second RAN node, for example,
  • the two RAN nodes are the RAN nodes currently serving the terminal, and thus the second downlink information can be successfully processed.
  • the first downlink information is used by the first RAN node to activate a PDU session of the terminal, where the PDU session is in a deactivated state;
  • the indication information is used to indicate that the PDU session activation fails;
  • the second downlink information is used by the second RAN node to activate the PDU session.
  • the first core network device is configured to send the second downlink information to the second RAN node and cause the second RAN node to activate the PDU session of the terminal according to the second downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully activate the PDU session of the terminal.
  • the first downlink information is used by the first RAN node to deactivate a PDU session of the terminal, where the PDU session is in an active state;
  • the indication information is used to indicate that the PDU session deactivation fails; and the second downlink information is used by the second RAN node to deactivate the PDU session. So that the first core network device sends the second downlink information to the second RAN node and causes the second RAN node to deactivate the PDU session of the terminal according to the second downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully deactivate the PDU session of the terminal.
  • the first downlink information is used by the first RAN node to update a PDU session of the terminal, where the PDU session is in an active state;
  • the indication information is used to indicate that the PDU session update fails;
  • the second downlink information is used by the second RAN node to update the PDU session. So that the first core network device sends the second downlink information to the second RAN node and causes the second RAN node to modify the PDU session of the terminal according to the second downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully modify the PDU session of the terminal.
  • the first downlink information is used by the first RAN node to release a PDU session of the terminal, where the PDU session is in an active state;
  • the indication information is used to indicate that the PDU session is released, and the second downlink information is used by the second RAN node to release the PDU session. So that the first core network device sends the second downlink information to the second RAN node and causes the second RAN node to release the PDU session of the terminal according to the second downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully release the PDU session of the terminal.
  • the first downlink information is downlink information that is sent to the terminal, and the indication information is used to indicate the first downlink information transmission. Failure, the second downlink information is the same as the first downlink information. So that the first core network device identifies that the first downlink information transmission fails according to the indication information, so that the second downlink information is sent to the second RAN node.
  • the method further includes: when the first core network device determines, according to current location information of the terminal, When the terminal is not located in the effective area of the first downlink information, the first core network device generates the second downlink information according to the current location information of the terminal.
  • the first downlink information may be valid for a device in an active area of the first downlink information.
  • the second downlink network information is generated by the first core network device as the terminal, and the current downlink location information of the terminal is the second RAN node location information, so the second downlink information is used for the second RAN node. It is valid and can be successfully processed by the second RAN node, thereby avoiding the processing failure caused by sending the invalid first downlink information to the second RAN node.
  • the first core network device determines, according to current location information of the terminal, that the terminal is located in the first When the downlink information is in the effective area, the second downlink information is the same as the first downlink information.
  • the first downlink information may be valid for a device in an active area of the first downlink information.
  • the method further includes: the first core network device from the first RAN
  • the node receives current location information of the terminal.
  • the first core network device obtains current location information of the terminal, so as to determine whether it is required to generate second downlink information different from the first downlink information for the terminal.
  • the indication information is a failure cause value.
  • the cause includes: the terminal initiates an RRC connection recovery from another RAN node other than the first RAN node Alternatively, the terminal is performing handover; or, the context is transferred; or the terminal is unreachable at the first RAN node; or the first downlink information is not transmitted. Therefore, the first core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the reason that the terminal initiates an RRC connection from another RAN node other than the first RAN node The recovery process, the first core network device sends the second downlink information to the second RAN node according to the indication information, including: the first core network device recovers in the RRC connection according to the indication information After the completion, the second downlink information is sent to the second RAN node. So that the first core network device sends the second downlink information to the second RAN node after the RRC connection recovery is completed, so that the second RAN node can successfully process the second downlink information.
  • the first core network device sends a second downlink to the second RAN node according to the indication information
  • the information includes: the first core network device starts a timer according to the indication information, and sends the second downlink information to the second RAN node after the timer expires. So that the first core network device sends the second downlink information to the second RAN node after the timer expires, so that the second RAN node can successfully process the second downlink information.
  • the method further includes: the first core network device to the second core network device Sending a subscription request message, the subscription request message is used to request the second core network device to send a notification message to the first core network device after the RRC connection recovery process is completed, where the notification message is used to notify the The RRC connection recovery is completed. So that the first core network device can send the second downlink information to the second RAN node after learning that the RRC connection recovery is completed, so that the second RAN node can successfully process the second downlink information.
  • the method further includes: the first core network device starts a timer according to the indication information; After the timer expires, the first core network device sends the second downlink information to the second RAN node.
  • the timer may be used to complete the RRC connection recovery process, for example, the timer timeout indicates that the RRC connection recovery process is complete. So that the first core network device sends the second downlink information to the second RAN node after the timer expires, so that the second RAN node can successfully process the second downlink information.
  • the reason includes: the terminal initiates an RRC connection from another RAN node other than the first RAN node The recovery process, the first core network device sends the second downlink information to the second RAN node according to the indication information, including: the first core network device recovers in the RRC connection according to the indication information After the path switching in the process is completed, the second downlink information is sent to the second RAN node. The second downlink information is sent to the second RAN node after the first core network device can complete the path switching in the RRC connection recovery procedure, so that the second RAN node can successfully process the second downlink information.
  • the method further includes: the first core network device sending a subscription request message to the second core network device
  • the subscription request message is used to request the second core network device to send a notification message to the first core network device after the path switch in the RRC connection recovery process is completed, where the notification message is used to notify the The path switch is completed.
  • the second downlink information is sent to the second RAN node after the path switching of the RRC connection recovery procedure is completed, so that the second RAN node can successfully process the second downlink information.
  • a communication method is provided, the method being applied to a scenario in which a terminal moves from a coverage of a first RAN node to a coverage of a second RAN node, the method comprising: the first RAN node
  • the first core network device receives the first downlink information of the terminal; when the RRC connection state of the terminal is in an inactive state, the first RAN node pages the terminal according to the first downlink information.
  • the first RAN node receives a context request of the terminal from the second RAN node; the first RAN node sends indication information to the first core network device according to the context request.
  • the indication information may be used to indicate that the first RAN node fails to process the first downlink information.
  • the method passes the first RAN node to the first A core network device sends indication information to enable the first core network device to learn that the first downlink information is not successfully processed by the first RAN node.
  • the first downlink information is used to activate a PDU session of the terminal, where the PDU session is in a deactivated state; Indicates that the PDU session activation failed.
  • the first RAN node to fail to activate the PDU session due to the terminal moving from the coverage of the first RAN node to the coverage of the second RAN node, such that the first core network device is in accordance with the indication
  • the information is learned that the PDU session activation failed.
  • the first downlink information is used to deactivate a PDU session of the terminal, where the PDU session is in an active state; Indicates that the PDU session deactivation failed.
  • the first RAN node cannot deactivate the PDU session due to the terminal moving from the coverage of the first RAN node to the coverage of the second RAN node, so that the first core network device is The indication information is learned that the PDU session deactivation failed.
  • the first downlink information is used to update a PDU session of the terminal, and the PDU session is in an active state; the indication information is used to indicate The PDU session update failed.
  • the first downlink information is used to release a PDU session of the terminal, where the PDU session is in an active state; the indication information is used to indicate The PDU session release failed.
  • the first RAN node cannot release the PDU session due to the terminal moving from the coverage of the first RAN node to the coverage of the second RAN node, so that the first core network device according to the indication
  • the information is learned that the PDU session release failed.
  • the first downlink information is downlink information that is sent to the terminal, and the indication information is used to indicate the first downlink information transmission. failure. Therefore, in a case where the first RAN node cannot send the first downlink information of the terminal to the terminal due to the terminal moving from the coverage of the first RAN node to the coverage of the second RAN node, so that the first core is caused The network device learns that the first downlink information is not successfully sent to the terminal according to the indication information.
  • the indication information is a failure cause value. Therefore, the first core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the cause includes: the terminal initiates an RRC connection recovery from another RAN node other than the first RAN node Alternatively, the terminal is performing handover; or, the context is transferred; or the terminal is unreachable at the first RAN node; or the first downlink information is not transmitted. Therefore, the first core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the method further includes: the first RAN node to the first core network
  • the device sends current location information of the terminal.
  • the first core network device obtains the current location information of the terminal, so as to determine whether the terminal is located in the effective area of the first downlink information.
  • the first downlink information may be valid for a device in an active area of the first downlink information.
  • a third aspect provides a communication method, where the method is applied to a scenario in which a terminal in which an RRC connection state is inactive is moved from a coverage of a first RAN node to a coverage of a second RAN node, where the method includes
  • the second core network device receives the first downlink information from the first core network device, and sends the first downlink information to the first RAN node; the second core network device from the first RAN node Receiving the first message; the second core network device sending the first downlink information to the second RAN node according to the first message.
  • the first message may be used to indicate that the first RAN node fails to process the first downlink information.
  • the method is received by the second core network device.
  • the first downlink information is sent by the core network device, so that the second core network device receives the first downlink message after receiving the first message sent by the first RAN node to indicate that the first downlink information processing fails.
  • the information is sent to the second RAN node, so that the first downlink information can be successfully processed by the second RAN node. For example, since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully process the first downlink information.
  • the first downlink information is used to activate a PDU session of the terminal, where the PDU session is in a deactivated state; Instructing the PDU session activation to fail. So that the second core network device retransmits the first downlink information to the second RAN node and causes the second RAN node to activate the PDU session of the terminal according to the first downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully activate the PDU session of the terminal.
  • the first downlink information is used to deactivate a PDU session of the terminal, where the PDU session is in an active state; Instructing the PDU session to deactivate failed. So that the second core network device retransmits the first downlink information to the second RAN node and causes the second RAN node to deactivate the PDU session of the terminal according to the first downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully take the PDU session of the active terminal.
  • the first downlink information is used to update a PDU session of the terminal, where the PDU session is in an active state; Indicates that the PDU session update failed. So that the second core network device retransmits the first downlink information to the second RAN node and causes the second RAN node to modify the PDU session of the terminal according to the first downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully modify the PDU session of the terminal.
  • the first downlink information is used to release a PDU session of the terminal, where the PDU session is in an active state; Indicates that the PDU session release failed. So that the second core network device retransmits the first downlink information to the second RAN node and causes the second RAN node to release the PDU session of the terminal according to the first downlink information. Since the second RAN node is the RAN node currently serving the terminal, the second RAN node can successfully release the PDU session of the terminal.
  • the first downlink information is downlink information that is sent to the terminal, and the first message is used to indicate the first downlink information.
  • the second core network device according to the first message, to the second The RN node sends the first downlink information, where the second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is for The device in the effective area of the first downlink information is valid; when the second core network device determines, according to the current location information of the terminal and the effective area information of the first downlink information, the terminal is located in the valid The second core network device sends the first downlink information to the second RAN node according to the first message.
  • the second core network device determines that the current location of the terminal is located in the effective area of the first downlink information, thereby determining to send the first downlink information to the second RAN node, so that the first downlink information can be
  • the second RAN node successfully processes, thereby avoiding the processing failure caused by sending the invalid first downlink information to the second RAN node.
  • the sending, by the first RAN node, the first downlink information including
  • the second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is for the device in the effective area of the first downlink information.
  • Valid when the state of the terminal on the second core network device is a connection management connection state, and the second core network device determines according to the stored location information in the context of the terminal and the valid area information When the terminal is located in the active area, the second core network device sends the first downlink information to the first RAN node.
  • the second core network device determines that the location in the context of the terminal is located in the effective area of the first downlink information, thereby determining to send the first downlink information to the first RAN node, thereby enabling the first downlink information. Can be successfully processed by the first RAN node, thereby avoiding the processing failure caused by sending the invalid first downlink information to the first RAN node.
  • the message type or the message name of the first message is used to indicate that the PDU session activation fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session activation fails.
  • the message type or the message name of the first message is used to indicate that the PDU session deactivation fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session deactivation fails.
  • the message type or the message name of the first message is used to indicate that the PDU session update fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session update fails.
  • the message type or the message name of the first message is used to indicate that the PDU session release fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session release fails.
  • the message type or the message name of the first message is used to indicate that the first downlink information transmission fails;
  • the first message includes indication information, where the indication information is used to indicate that the first downlink information transmission fails. Therefore, the second core network device learns that the first RAN node fails to transmit the first downlink information.
  • the indication information is a failure cause value. Therefore, the second core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the cause includes: the terminal initiating RRC from another RAN node other than the first RAN node The connection recovery process; or the terminal is performing handover; or, the context transfer; or the terminal is unreachable at the first RAN node; or the first downlink information is not transmitted. Therefore, the second core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the cause comprises: the terminal initiating an RRC from another RAN node other than the first RAN node
  • the connection recovery process the second core network device sends the first downlink information to the second RAN node according to the first message, including:
  • the second core network device sends the first downlink information to the second RAN node after the RRC connection recovery is completed according to the first message; or the second core network device according to the The first message, after the path switching in the RRC connection recovery process is completed, sends the first downlink information to the second RAN node. So that the second core network device can send the second downlink information to the second RAN node after learning that the RRC connection recovery is completed or the path switching in the RRC connection recovery process is completed, so that the second RAN node can successfully process the second Downstream information.
  • the method further includes: the second core network device from the first The RAN node receives current location information of the terminal.
  • the second core network device is configured to learn the current location information of the terminal, so as to determine that the current location of the terminal is located in the effective area of the first downlink information, and then decide to send the first downlink information to the second RAN node, so that The first downlink information can be successfully processed by the second RAN node, thereby avoiding the processing failure caused by sending the invalid first downlink information to the second RAN node.
  • a fourth aspect provides a communication method, where the method is applied to a scenario in which a terminal in which an RRC connection state is inactive is moved from a coverage of a first RAN node to a coverage of a second RAN node, where the method includes
  • the second core network device receives the first downlink information from the first core network device, and sends the first downlink information to the first RAN node; the second core network device from the first RAN node Receiving the first message; the second core network device sending the indication information to the first core network device according to the first message.
  • the first message may be used to indicate that the processing of the first downlink information by the first RAN node fails.
  • the method passes the first RAN node to the second core.
  • the first downlink information is used to activate a PDU session of the terminal, where the PDU session is in a deactivated state; Instructing the PDU session activation to fail. And causing the second core network device to send the indication information to the first core network device, so that the first core network device learns that the PDU session activation fails.
  • the first downlink information is used to deactivate a PDU session of the terminal, where the PDU session is in an active state; Instructing the PDU session to deactivate failed. And causing the second core network device to send the indication information to the first core network device, so that the first core network device learns that the PDU session deactivation fails.
  • the first downlink information is used to update a PDU session of the terminal, where the PDU session is in an active state; Indicates that the PDU session update failed. And causing the second core network device to send the indication information to the first core network device, so that the first core network device learns that the PDU session modification fails.
  • the first downlink information is used to release a PDU session of the terminal, where the PDU session is in an active state or an inactive state;
  • a message is used to indicate that the PDU session release failed.
  • the second core network device to send the indication information to the first core network device, so that the first core network device learns that the PDU session release fails.
  • the first downlink information is downlink information that is sent to the terminal, and the first message is used to indicate the first downlink information.
  • the transfer failed.
  • the second core network device to send the indication information to the first core network device, so that the first core network device learns that the first downlink information transmission fails.
  • the second core network device according to the first message, to the first core
  • the network device sends the indication information, where the second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is for the first downlink
  • the device in the effective area of the information is valid; when the second core network device determines that the terminal is not located in the effective area according to the current location information of the terminal and the effective area information of the first downlink information,
  • the second core network device sends the indication information to the first core network device according to the first message.
  • the second core network device determines that the current location of the terminal is not located in the active area of the first downlink information, thereby determining to send the indication information to the first core network device, so that the first core network device generates the corresponding The second downlink information that is valid for the current location of the terminal is avoided, and the processing failure caused by the second core network device sending the invalid first downlink information to the second RAN node is avoided.
  • the sending, by the first RAN node, the first downlink information includes: The second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is valid for the device in the effective area of the first downlink information.
  • the state of the terminal on the second core network device is a connection management connection state
  • the second core network device determines, according to the stored location information in the context of the terminal and the valid area information.
  • the second core network device sends the first downlink information to the first RAN node.
  • the second core network device determines that the location in the context of the terminal is located in the effective area of the first downlink information, thereby determining to send the first downlink information to the first RAN node, thereby enabling the first downlink information. Can be successfully processed by the first RAN node, thereby avoiding the processing failure caused by sending the invalid first downlink information to the first RAN node.
  • the message type or the message name of the first message is used to indicate that the PDU session activation fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session activation fails.
  • the message type or the message name of the first message is used to indicate that the PDU session deactivation fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session deactivation fails.
  • the message type or the message name of the first message is used to indicate that the PDU session update fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session update fails.
  • the message type or the message name of the first message is used to indicate that the PDU session release fails; or
  • the first message includes indication information, where the indication information is used to indicate that the PDU session release fails.
  • the message type or the message name of the first message is used to indicate that the first downlink information transmission fails;
  • the first message includes indication information, where the indication information is used to indicate that the first downlink information transmission fails. Therefore, the second core network device learns that the first RAN node fails to transmit the first downlink information.
  • the indication information is a failure cause value. Therefore, the second core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the reason that: the terminal initiates an RRC from another RAN node other than the first RAN node The connection recovery process; or the terminal is performing handover; or, the context transfer; or the terminal is unreachable at the first RAN node; or the first downlink information is not transmitted. Therefore, the second core network device is informed of the reason why the first RAN node fails to process the first downlink information.
  • the method further includes: the second core network device from the first RAN The node receives current location information of the terminal.
  • the second core network device is configured to obtain the current location information of the terminal, so as to determine that the current location of the terminal is not located in the effective area of the first downlink information, thereby determining to send the indication information to the first core network device, thereby enabling
  • the first core network device generates the second downlink information that is valid for the current location of the terminal, and avoids the processing failure caused by the second core network device sending the invalid first downlink information to the second RAN node.
  • a fifth aspect provides a communication method, where the method is applied to a scenario in which a terminal in which an RRC connection state is inactive is moved from a coverage of a first RAN node to a coverage of a second RAN node, where the method includes
  • the second core network device obtains the first downlink information;
  • the second core network device sends a location request message to the first RAN node, where the location request message is used to request current location information of the terminal;
  • the second core network device receives current location information of the terminal from the first RAN node, and/or the second core network device receives the terminal from the first RAN node from the first RAN node
  • the other RAN node sends the indication information of the RRC connection recovery procedure;
  • the second core network device sends the first downlink information to the second RAN node; or the second core network device sends the The first core network device sends the indication information.
  • the method is received by the second core network device from the first RAN.
  • the information or the message of the node triggers the second core network device to send the first downlink information to the second RAN node, so that the first downlink information can be successfully geographed by the second RAN node; or trigger the second core network device to The first core network device sends the indication information, so that the first core network device learns that the first downlink information processing fails.
  • a communication method is provided, the method being applied to a scenario in which a terminal moves from a coverage of a first RAN node to a coverage of a second RAN node, the method comprising: the first RAN node from the second The core network device receives a location request message, where the location request message is used to request current location information of the terminal; when the RRC connection state of the terminal is inactive, the first RAN node according to the location request message Placing the terminal; the first RAN node receives a context request of the terminal from the second RAN node; the first RAN node sends the to the second core network device according to the context request The terminal initiates an indication of an RRC connection recovery procedure from other RAN nodes other than the first RAN node, and/or current location information of the terminal.
  • the method passes the first RAN node to the first core.
  • the network device sends information or a message to enable the second core network device to learn that the first downlink information is not successfully processed by the first RAN node.
  • a communication device having the function of implementing any one of the methods of the first to sixth aspects.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the device can exist in the form of a chip product.
  • a communication device comprising: a memory, a processor, at least one communication interface, and a communication bus; the memory is configured to store computer execution instructions, and the processor, the memory, and the at least one communication interface are connected by using a communication bus, The processor executes the memory stored computer to execute the instructions to cause the apparatus to implement any of the methods provided in any one of the first to sixth aspects.
  • the device can exist in the form of a chip product.
  • a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform any of the methods provided in any one of the first to sixth aspects.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the methods provided in any one of the first to sixth aspects.
  • FIG. 1 is a schematic structural diagram of a 5G network according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a service area of a UPF according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a location of a UPF according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of path switching according to an embodiment of the present application.
  • FIG. 7 to FIG. 12 are schematic flowcharts of a communication method according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the technical solution of the embodiment of the present application can be applied to various data processing communication systems, for example, code division multiple access (CDMA), time division multiple access (TDMA), and frequency division. Frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems.
  • the term "system" can be replaced with "network”.
  • the CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000.
  • UTRA may include wideband CDMA (WCDMA) technology and other CDMA variant technologies.
  • CDMA2000 can cover the interim standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards.
  • the TDMA system can implement a wireless technology such as a global system for mobile communication (GSM).
  • GSM global system for mobile communication
  • An OFDMA system can implement, for example, Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Wireless technologies such as Flash OFDMA.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Wireless technologies such as Flash OFDMA.
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • the various versions of 3GPP in Long Term Evolution (LTE) and LTE-based evolution are new versions of UMTS that use E-UTRA.
  • LTE Long Term Evolution
  • LTE-based evolution are new versions of UMTS that use E-UTRA.
  • the 5G communication system and the new radio (NR) are the next generation communication systems under study.
  • the communication system can also be applied to future-oriented communication technologies, and the technical solutions provided by the embodiments
  • the system architecture described in the embodiments of the present application is for the purpose of more clearly explaining the technical solutions of the embodiments of the present application, and does not constitute a limitation of the technical solutions provided by the embodiments of the present application. Those skilled in the art may know that with the evolution of the network architecture. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the method provided in the NR system or the 5G network is taken as an example for description.
  • the method provided by the embodiment of the present application can also be applied to other networks, for example, can be applied to an evolved packet system (EPS) network (that is, the so-called fourth generation (4th generation). , referred to as 4G) network).
  • EPS evolved packet system
  • 4G fourth generation
  • the network node that performs the method provided by the embodiment of the present application may be replaced by a network node having the same or corresponding function in the EPS network.
  • the method provided by the embodiment of the present application can be applied to a 5G network.
  • the 5G network may include multiple network functions (NF functions) entities: an authentication server function (authentication server function). , referred to as AUSF) entity, AMF entity, data network (DN), unified data management (UDM) entity, policy control function (PCF) entity, (wireless) access (radio access network, referred to as (R) AN) entity, UPF entity, user equipment (UE), application function (AF) entity, session management function (SMF) ) Entity, etc.
  • NF functions network functions
  • AUSF authentication server function
  • AMF authentication server function
  • DN data network
  • UDM unified data management
  • PCF policy control function
  • R wireless access network
  • UPF user equipment
  • AF application function
  • SMF session management function
  • FIG. 1 is only an exemplary architecture diagram.
  • the 5G network architecture may also include other functional entities, for example, an open network may also be included between the AF entity and the PCF entity.
  • Network exposure function (NEF) entity The entity may also be referred to as a network element or a device.
  • the UDM entity, the AUSF entity, the PCF entity, the AMF entity, and the SMF entity in FIG. 1 may also be collectively referred to as a control plane function (CPF) entity, which is not specifically limited in this embodiment of the present application.
  • CPF control plane function
  • the (R)AN is a network composed of a plurality of 5G-RAN nodes, and implements a physical layer function, a resource scheduling, a radio resource management, a radio access control, and a mobility management function.
  • the 5G-RAN node is connected to the UPF through the user plane interface N3, and is used to transmit data of the terminal.
  • the 5G-RAN node establishes a control plane signaling connection through the control plane interface N2 and the AMF, and is used to implement functions such as radio access bearer control.
  • AMF is mainly responsible for terminal authentication, terminal mobility management, network slice selection, and SMF selection.
  • the AMF serves as an anchor for the N1 and N2 signaling connections and provides routing of N1/N2 interface session management (SM) messages for the SMF; maintains and manages terminal status information.
  • SMF is mainly responsible for all control plane functions of terminal session management, including UPF selection, internet protocol (IP) address allocation, session quality of service (QoS) management, and acquisition of policies and calculations from PCF. Policy and charging control (PCC) strategy.
  • PDU packet data unit
  • the UPF is responsible for data packet filtering, data transmission/transmission, rate control, and generation of charging information for the terminal.
  • the (R) AN entity, the AMF entity, the SMF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity in FIG. 1 are only one name, and the name does not limit the entity itself.
  • the network elements or devices corresponding to the entities may be other names, which are not specifically limited in this embodiment of the present application.
  • the UDM entity may be replaced by a home subscriber server (HSS) or a user subscription database (USD) or a database entity, etc., and is uniformly described herein. Narration.
  • the method provided by the embodiment of the present application can also be applied to a network slice of a 5G network.
  • the network slicing technology cuts a physical network into multiple virtual end-to-end networks, and each virtual network includes devices in the network. Access technology, transmission paths, and core networks are logically independent.
  • Each network slice is instantiated by a separate network function or combination of functions with different functional characteristics for different needs and services. The separation of network slices enables different users and user groups to flexibly and dynamically define and customize network capabilities according to their different application scenarios and requirements without affecting each other.
  • a network slice includes a CPF entity and a UPF entity.
  • the CPF entity mainly completes access control and mobility management functions such as access authentication, security encryption, and location registration of the terminal, and session management functions such as establishment, release, and modification of the user plane transmission path, and the UPF entity mainly completes the user plane. Data routing and other functions.
  • the terminal involved in the embodiment of the present application may also be referred to as a UE (the terminal and the UE mentioned below are the same device).
  • a UE the terminal and the UE mentioned below are the same device.
  • it may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; and may also include a subscriber unit, a cellular phone, Smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld, laptop computer, cordless Cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • modem wireless modem
  • WLL cordless Cordless phone or wireless local loop (WLL) station
  • MTC machine type communication
  • MS mobile station
  • terminal device etc.
  • PDU session One or more service flow templates of a PDU session are saved in the UPF, and the PDU session is used to carry downlink data that matches the service flow template of the PDU session.
  • the UPF determines that PDU Session 1 is not activated, then PDU Session 1 needs to be activated to send the downlink data.
  • PDU Session 1 needs to be activated to send the downlink data.
  • Table 1 at this time, even if the PDU session 2 and the PDU session 3 are activated, since the service flow template corresponding to the PDU session 2 and the PDU session 3 does not match the downlink data, the UPF cannot adopt the PDU session 2 or the PDU session. 3 carries the downlink data.
  • SMF Serving Mobility Management Function
  • SMF Serving Mobility Management Function
  • the UPF provides services for the RAN nodes in its own service area (or the UPF provides services for UEs within its own service area; or, the UPF is a UE connected to the RAN node within its own service area) Provide services).
  • a RAN node located in a service area of a UPF can establish a data channel with the UPF to provide services for the terminal.
  • the UPF exists in a service area (for example, the service area of UPF1 in FIG. 2 is service area 1, and the service area of UPF2 is service area 2).
  • the RAN node in the service area of the UPF1 cannot establish a data channel with the UPF1. Therefore, the UPF1 can no longer provide services for the terminal.
  • the SMF selects a UPF (referred to as UPF2) for the RAN2 node, so that the RAN2 node establishes a data channel with the UPF2 as a terminal service.
  • the service area of the UPF is not considered.
  • the terminal moves within the RA, the terminal may have moved out of the service area of the UPF.
  • the SMF subscribes to the AMF's "area of interest" (corresponding to the service area 1 of the UPF1) in order to obtain information about whether the terminal has removed the service area of the UPF1. If the AMF determines that the terminal has moved out, Service area 1, then inform the SMF of this information so that the SMF selects the UPF for the RAN2 node.
  • the AMF determines, according to the location information in the context of the stored terminal, that the terminal is located in the effective area of the downlink information, and then sends downlink information to the RAN1 node, and how the RAN1 node processes the downlink information after receiving the downlink information.
  • the RAN1 node There is no corresponding processing mechanism in the technology.
  • RRC connection status may include an idle state, a connected state, and an inactive state.
  • the RRC connection state of the terminal is an idle state, which means that a non-access stratum (NAS) signaling connection is not established between the terminal and the AMF.
  • NAS non-access stratum
  • the RRC connection state of the terminal is a connection state, which may be that a NAS signaling connection is established between the terminal and the AMF, and an RRC connection is established with the RAN.
  • the inactive state of the RRC connection of the terminal may be that the NAS signaling connection is established between the terminal and the AMF, but the RRC connection is not established with the RAN.
  • the state of the terminal stored on the AMF is a connection management connection state.
  • the context of the terminal is also saved on the AMF, and the context information of the terminal is included in the context, and the location information of the terminal is reported in the process of the terminal initially accessing the network (ie, the registration process or the service request process) or the terminal is performing the cell handover process.
  • the location information of the terminal reported by the base station.
  • the location information of the terminal may be an identifier of the RAN node serving the terminal, and an evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (E-UTRAN cell) of the cell where the terminal is located.
  • E-UTRAN evolved universal terrestrial radio access network
  • E-UTRAN cell evolved universal terrestrial radio access network
  • the global identifier ECGI
  • the TA identity TAA
  • TAC TA code
  • RRC connection status of the terminal is inactive, it is also possible to store the specific RRC connection status (eg, inactive state) of the terminal in the AMF.
  • the state of the terminal stored on the AMF is the connection management connection state
  • the location information in the context of the terminal that the AMF considers to be the terminal is the current location information of the terminal.
  • the terminal does not have a cell handover, if the terminal moves from the coverage of the RAN1 node (the service area of the UPF1) to the coverage of the RAN2 node (not in the service area of the UPF1), the context of the terminal saved on the AMF
  • the location information is still information indicating that the terminal is within the coverage of the RAN1 node. But in fact the terminal has moved to the coverage of the RAN2 node.
  • the AMF judges that the terminal is located in the effective area of the downlink information according to the location information in the context of the saved terminal is erroneous. In this case, if the AMF sends the downlink information of the terminal to the RAN1 node, the downlink information processing fails.
  • FIG. 3 is a schematic diagram of the hardware structure of the communication device according to the embodiment of the present application.
  • the communication device may be the first core network device and the second Core network device, first RAN node or second RAN node.
  • the communication device 30 includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.
  • the processor 301 can be one or more general central processing units (CPUs), microprocessors, application-specific integrated circuits (ASICs), or one or more for controlling the present An integrated circuit for the execution of a program program.
  • CPUs general central processing units
  • ASICs application-specific integrated circuits
  • the communication bus 302 is configured to communicate between the above components to transmit information.
  • the communication interface 304 is configured to communicate with other devices or communication networks, and may use any device such as an Ethernet device, a RAN device, a wireless local area network (WLAN), or the like.
  • Ethernet device such as an Ethernet device, a RAN device, a wireless local area network (WLAN), or the like.
  • WLAN wireless local area network
  • the memory 303 is configured to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute computer-executed instructions stored in the memory 303 to implement the methods provided by the following embodiments of the present application.
  • the memory 303 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or a device that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical discs.
  • Memory 303 may be present independently and coupled to processor 301 via communication bus 302. The memory 303 can also be integrated with the processor 301.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 30 may include multiple processors, such as processor 301 and processor 308 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • communication device 30 may also include an output device 305 and an input device 306.
  • Output device 305 is in communication with processor 301 and can display information in a variety of ways.
  • Input device 306 is in communication with processor 301 and can receive user input in a variety of ways.
  • SMSF in Table 2 is an abbreviation for short messaging service function. SMS is short for short messaging service.
  • the first downlink information corresponding to the sequence numbers 1, 7, 8, 9 and 10 in Table 2 may be included in the N1 interface message N2 interface message transmission message (Namf_Communication_N1N2MessageTransfer) provided by the AMF.
  • the first downlink information corresponding to the sequence number 2 may be included in the access and mobility policy control update notification message (Npcf_AMPolicyControl UpdateNotify) provided by the PCF.
  • the first downlink information corresponding to the sequence number 5 may be included in the subscription data management notification message (Nudm_SDM_Notification) provided by the UDM.
  • the first downlink information corresponding to the sequence number 6 may be included in the trigger transmission request message (Nnef_Trigger_Deliveryrequest) provided by the NEF.
  • AM is an abbreviation for core access and mobility
  • SDM is an abbreviation for subscription data management.
  • An embodiment of the present application provides a communication method, where a UE that has an RRC connection state in an inactive state moves from a coverage of a first RAN node to a coverage of a second RAN node, as shown in FIG. 4, Methods include:
  • the first core network device sends the first downlink information to the first RAN node.
  • the first downlink information may be downlink information received by the first core network device from other network devices, or may be downlink information generated by the first core network device.
  • the first core network device may be an SMSF, a PCF, a UDM, a NEF, an AMF, an SMF, etc., and other network devices may be an AF.
  • the first core network device when the first downlink information is generated by the first core network device, if the first downlink information is information related to the PDU session of the UE (for example, a PDU session for activating/deactivating/modifying/releasing the UE) When the downlink information is), the first core network device may be an SMF. When the first downlink information is a short message sent to the UE, the first core network device may be an SMSF. When the first downlink information is information for updating access and mobility management parameters on the UE, the first core network device may be an AMF. For other cases, see Table 2, which is not listed here.
  • the first RAN node receives the first downlink information of the UE from the first core network device.
  • the first RAN node pages the UE according to the first downlink information.
  • the RRC connection status is included in the context of the UE stored in the first RAN node.
  • the UE may perform information interaction between the coverage of the first RAN node and the first RAN node. Therefore, the first RAN node does not page the UE when receiving the first downlink information.
  • the RRC connection status of the UE is in the connected state, if the first RAN node receives the first downlink information for activating the PDU session, the first RAN node may directly interact with the UE through RRC signaling to establish an air interface DRB data channel of the PDU session. Without paging the UE.
  • the RRC connection state of the UE is in an inactive state, the first RAN node pages the UE.
  • the first RAN node receives a context request of the UE from the second RAN node.
  • the first RAN node also notifies other RAN nodes (including the second RAN node) to page the UE when paging the UE.
  • the RAN node may broadcast a paging message to page the UE.
  • the UE since the UE is already in the coverage of the second RAN node at this time, the UE initiates an RRC connection recovery request to the second RAN node in response to the paging message broadcast by the second RAN node, where the second RAN node is After receiving the RRC connection recovery request of the UE, the context request is sent to the first RAN node, and the context request is used to request to acquire the context of the UE, so as to restore the RRC connection of the UE.
  • the first RAN node sends the indication information to the first core network device according to the context request.
  • the indication information may indicate that the first downlink information processing fails.
  • the indication information is used to instruct the first core network device to send the second downlink information to the second RAN node.
  • the first core network device receives the indication information from the first RAN node.
  • the first core network device sends the second downlink information to the second RAN node according to the indication information.
  • the first downlink information and the second downlink information may be partially or completely the same.
  • the role of the first downlink information, the second downlink information, and the indication information may be any one of the following situations:
  • the first downlink information is used by the first RAN node to activate the PDU session of the UE, the PDU session is in a deactivated state; the indication information is used to indicate that the PDU session activation fails; and the second downlink information is used for the second RAN node activation.
  • the first downlink information is the first downlink information corresponding to the sequence number 8 in Table 2.
  • the first downlink information may be N2 SM information.
  • the N2 interface SM information may be a QoS file (QoS profile(s), which may also be referred to as QoS configuration information) and a core network N3 interface tunnel information (CN N3 tunnel info, which may also be referred to as CN tunnel info).
  • the CN N3 tunnel info can be used for establishing an N3 interface data channel between the first RAN node and the first UPF.
  • the first UPF is a UPF that receives downlink data of the PDU session of the UE and sends a data notification to the first core network device, where the data notification is used to notify the first core network device that downlink data of the UE needs to be sent.
  • Case 2 The first downlink information is used by the first RAN node to deactivate the PDU session of the UE, the PDU session is in an active state; the indication information is used to indicate that the PDU session deactivation fails; and the second downlink information is used for the second RAN node. Deactivate the PDU session.
  • the second downlink information and the first downlink information may be the same.
  • the first downlink information may be the first downlink information corresponding to the sequence number 9 in Table 2.
  • the first downlink information may be an N2 interface SM information.
  • the N2 interface SM information can be identified as a PDU session.
  • Case 3 The first downlink information is used by the first RAN node to update the PDU session of the UE, where the PDU session is in an active state; the indication information is used to indicate that the PDU session update fails; and the second downlink information is used by the second RAN node to update the PDU session.
  • the second downlink information and the first downlink information may be the same.
  • the first downlink information may be the first downlink information corresponding to the sequence number 10 in Table 2.
  • the first downlink information may include: an N2 interface SM information and an N1 interface SM container.
  • the N2 interface SM information is used by the RAN node to update related parameters of the PDU session.
  • the N2 interface SM information can be QoS profile(s).
  • the N1 interface SM container is used by the UE to update related parameters of the PDU session.
  • the N1 interface SM container can be a QoS profile(s).
  • Case 4 The first downlink information is used by the first RAN node to release the PDU session of the UE, where the PDU session is in an active state or an inactive state; the indication information is used to indicate that the PDU session is released, and the second downlink information is used for the second The RAN node releases the PDU session.
  • the second downlink information and the first downlink information may be the same.
  • the first downlink information may be the first downlink information corresponding to the sequence number 11 in Table 2.
  • the first downlink information may include an N2 Resource Release request and/or an N1 interface SM container.
  • the N2 resource release request includes a related parameter for the first RAN node to release the PDU session
  • the N1 interface SM container includes related parameters for the UE to release the PDU session.
  • the PDU session identifier is included in both the N2 resource release request and the N1 interface SM container. If the PDU session is in an active state, the first downlink information includes an N2 resource release request and an N1 interface SM container; if the PDU session is in an inactive state, the first downlink information includes an N1 interface SM container.
  • the first downlink information is downlink information sent to the UE; the indication information is used to indicate that the first downlink information transmission fails, and the second downlink information is the same as the first downlink information.
  • the first downlink information may be the first downlink information corresponding to any one of the sequence number 1 and the sequence number 7 in Table 2. In either case 1 - case 4:
  • the first core network device can be an SMF.
  • the first core network device may directly send the first downlink information to the first RAN node.
  • the first core network device may also send the first downlink information to other devices, and forward the first downlink information to the first RAN node by using other devices.
  • Other devices may be control plane network elements, for example, AMF.
  • the SMF may send the first downlink information to the AMF, and forward the first downlink information to the first RAN node by using the AMF.
  • the first RAN node may receive the first downlink information from the first core network device.
  • the first core network device sends the first downlink information to the other device, and the first downlink information is forwarded to the first RAN node by the other device, the first RAN node may receive the first downlink information from the other device.
  • the first core network device may be a device that generates the first downlink information, or may be a device that forwards the first downlink information.
  • the first core network device may be an SMSF (a device that generates the first downlink information) or an AMF (a device that forwards the first downlink information).
  • the first downlink information, the second downlink information, and the indication information are the foregoing case 1, in the first implementation scenario:
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not activate the UE.
  • PDU session eg, does not trigger the establishment of a data channel for the air interface DRB between the UE and the first RAN node for the PDU session of the UE, does not trigger the establishment of the first RAN node and the first UPF for the PDU session of the UE
  • the data channel of the N3 interface the first RAN node sends indication information to the first core network device.
  • the first core network device may determine, according to the indication information, that the PDU session of the first RAN node to activate the UE fails, and then send the second downlink information to the second RAN node that is currently serving the UE.
  • the method further includes: when the first core network device determines that the UE is not located in the effective area of the first downlink information according to the current location information of the UE, the first core network device generates a second according to the current location information of the UE. Downstream information. Or, when the first core network device determines that the UE is located in the effective area of the first downlink information according to the current location information of the UE, the second downlink information is the same as the first downlink information.
  • the first core network device may compare the current location information of the UE with the effective area of the first downlink information, and determine whether the UE is currently located in the effective area of the first downlink information.
  • the first downlink information is valid for devices in the active area of the first downlink information.
  • the first downlink information includes the CN N3 tunnel info corresponding to the first UPF. Therefore, the first core network device may set the effective area of the first downlink information as the service area of the first UPF. That is, CN N3 tunnel info is only valid for the UE located in the service area of the first UPF (or CN N3 tunnel info is only valid for the RAN located in the service area of the first UPF; or CN N3 tunnel info is only for the pass-through
  • the UE in the service area of the first UPF is connected to the UE of the network.
  • the first core network device may further set the validity of the first downlink information according to other information, such as a service range of the first core network device, load information of the first UPF, load information of a base station currently serving the UE, and the like.
  • the method provided by the embodiment of the present application is exemplified by taking the same as the service area of the first UPF as an example.
  • the first core network device can determine the RAN node (ie, the second RAN node) that is currently serving the UE according to the current location information of the UE, and the first core network device selects the UPF (referred to as the second UPF) for the second RAN node.
  • the first core network device determines, according to the indication information, that the PDU session of the first RAN node to activate the UE fails, and The CN N3 tunnel info corresponding to the second UPF is included in the second downlink information and sent to the second RAN node, so that the second RAN node activates the PDU session of the UE.
  • the second UPF is an intermediate UPF (intermediate UPF) selected by the SMF, and is used to connect to the second RAN node to establish a data channel of the N3 interface for the PDU session.
  • the first RAN node is connected to the first UPF.
  • the second RAN node is connected to the second UPF.
  • the second UPF may be directly connected to the anchor UPF (see (b) in FIG. 5), or may be connected to the anchor UPF through the first UPF (see (d) in FIG. 5) (in this case, The first UPF and the second UPF are different UPFs).
  • the second UPF may also be an anchor UPF (see (c) in FIG. 5).
  • both the second RAN node and the first RAN node may be the PDU session of the UE.
  • the data channel of the N3 interface to the same UPF ie, the first UPF in the above
  • the first downlink information and the second downlink information may be the same information.
  • the second RAN node activates the PDU session of the UE according to the received second downlink information.
  • the second RAN node may activate the PDU session of the UE, where the second RAN node establishes a data channel between the UE and the second UPF for the PDU session of the UE, and the data channel between the UE and the second UPF includes: the UE and the second A data channel of the air interface DRB between the RAN nodes, and a data channel of the N3 interface between the second RAN node and the second UPF.
  • the first core network device when the first downlink information is used to activate the PDU session of the UE, if the first core network device receives the indication information, it indicates that the first RAN node fails to activate the PDU session.
  • the first core network device may send the second downlink information to the second RAN node currently serving the UE, so that the second RAN node activates the PDU session of the UE according to the second downlink information. Since the second RAN node is the RAN node currently serving the UE, the second RAN node can successfully activate the PDU session of the UE.
  • the first downlink information, the second downlink information, and the indication information are the foregoing case 2, in the second implementation scenario:
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not use the PDU.
  • the session is deactivated, but an indication message is sent to the first core network device.
  • the first core network device may determine, according to the indication information, that the PDU session of the first RAN node to deactivate the UE fails, and then send the second downlink information to the second RAN node that is currently serving the UE. Since the UE is currently located within the coverage of the second RAN node, the second RAN node can successfully deactivate the PDU session of the UE.
  • the first core network device can determine the deactivated PDU session by itself. For example, if a PDU session is a PDU session established for a local access data network (LADN), the first core network device finds that the UE has removed the service range of the LADN, and then determines to deactivate the PDU session. For another example, the UPF notifies the first core network device that a PDU session has no data transmission for a certain period of time, and the first core network device determines to deactivate the PDU session.
  • LADN local access data network
  • the second RAN node deactivates the PDU session of the UE according to the received second downlink information.
  • Deactivating the PDU session of the UE by the second RAN node may include: the second RAN node releasing the resources prepared for the PDU session corresponding to the PDU session identifier according to the PDU session identifier in the second downlink information.
  • the second RAN node may release the DRB resource prepared for the PDU session corresponding to the PDU session by performing RRC signaling interaction with the UE, such as RRC connection reconfiguration.
  • the second RAN node may also release the The data channel resource of the N3 interface of the PDU session (that is, the AN tunnel info and CN tunnel info of the PDU session are released).
  • the first core network device determines that the first RAN node fails to activate the PDU session.
  • the first core network device sends the second downlink information to the second RAN node currently serving the UE, so that the second RAN node deactivates the PDU session of the UE according to the second downlink information. Since the second RAN node is the RAN node currently serving the UE, the second RAN node can successfully deactivate the PDU session of the UE.
  • the first downlink information, the second downlink information, and the indication information are the foregoing case 3.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not update the The PDU session sends an indication message to the first core network device.
  • the first core network device may determine, according to the indication information, that the first RAN node fails to update the PDU session of the UE, and then sends the second downlink information to the second RAN node that is currently serving the UE. Since the UE is currently located within the coverage of the second RAN node, the second RAN node can successfully update the PDU session of the UE.
  • the second RAN node updates the PDU session of the UE according to the received second downlink information.
  • the second RAN node updating the PDU session of the UE may specifically include at least one of the following processes: updating the QoS Profile(s) of the PDU session stored by the second RAN node according to the QoS profile(s) in the N2 interface SM information; Sending an N1 SM container to the UE; performing RRC signaling (eg, RRC reconfiguration) interaction with the UE to renegotiate the DRB information corresponding to the PDU session according to the QoS profile(s) in the N2 interface SM information, and updating the PDU according to the negotiation result.
  • DRB information corresponding to the session may specifically include at least one of the following processes: updating the QoS Profile(s) of the PDU session stored by the second RAN node according to the QoS profile(s) in the N2 interface SM information; Sending an N1 SM container to the UE; performing RRC signaling (
  • the first core network device determines that the first RAN node fails to update the PDU session.
  • the first core network device sends the second downlink information to the second RAN node currently serving the UE, so that the second RAN node updates the PDU session of the UE according to the second downlink information. Since the second RAN node is the RAN node currently serving the UE, the second RAN node can successfully update the PDU session of the UE.
  • the first downlink information, the second downlink information, and the indication information are the foregoing case 4.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not release the The PDU session sends an indication message to the first core network device.
  • the first core network device may determine, according to the indication information, that the PDU session of the first RAN node releases the UE fails, and the first core network device sends the second RAN node that is currently serving the UE. Downstream information. Since the UE is currently located within the coverage of the second RAN node, the second RAN node can successfully release the PDU session of the UE.
  • the second RAN node releases the PDU session of the UE according to the received second downlink information.
  • the releasing, by the second RAN node, the PDU session of the UE may include: the second RAN node releasing the resource prepared for the PDU session corresponding to the PDU session identifier according to the PDU session identifier in the N2 resource release request.
  • the second RAN node may release the DRB resource prepared for the PDU session corresponding to the PDU session identifier by performing RRC signaling (eg, RRC reconfiguration) with the UE.
  • the second RAN node may also release the data channel resource of the N3 interface of the PDU session (ie, release AN tunnel info and CN tunnel info of the PDU session); send the N1 SM container to the UE.
  • the first core network device determines that the first RAN node fails to release the PDU session.
  • the first core network device sends the second downlink information to the second RAN node that is currently serving the UE, so that the second RAN node releases the PDU session of the UE according to the second downlink information. Since the second RAN node is the RAN node currently serving the UE, the second RAN node can successfully release the PDU session of the UE.
  • the first downlink information, the second downlink information, and the indication information are the foregoing case 5, in the fifth implementation scenario:
  • the first RAN node may determine that the UE is currently located in the coverage of the second RAN node, and the first RAN node cannot successfully send the UE to the UE. Send the first downlink information.
  • the first RAN node sends indication information to the first core network device.
  • the first core network device may determine that the first downlink information transmission fails, because the UE is currently located in the coverage of the second RAN node. Therefore, the first core network device sends the first downlink information to the second RAN node, so that the second RAN node sends the first downlink information to the UE.
  • the first core network device may perform step 401 if it is determined that the RRC connection state of the stored UE is the connection management connection state.
  • the first core network device may also perform step 401 if the RRC connection status of the stored UE is the connection management connection state, and the location information in the context of the stored UE indicates that the UE is in the coverage of the first RAN node. .
  • the first downlink information may also have a valid area.
  • the first core network device determines that the UE is located in the active area of the first downlink information according to the current location information of the UE, the first core network device performs step 407. If the first core network device determines that the UE is not located in the effective area of the first downlink information according to the current location information of the UE, the first core network device discards the first downlink information.
  • the description is equally applicable to the case 5 of the second embodiment and the third embodiment, and the second embodiment and the third embodiment are not described again.
  • the first core network device sends the first downlink information to the first RAN node
  • the first RAN node sends the first downlink to the UE.
  • the information failed.
  • the first core network device sends the first downlink information to the second RAN node that is currently serving the UE, so that the second RAN node sends the first downlink information to the UE, because the UE is located at the second RAN node. Within the coverage, the second RAN node can successfully send the first downlink information.
  • the foregoing method may further include: the first RAN node sends the current location information of the UE to the first core network device, where the first core network device receives the current location information of the UE from the first RAN node.
  • the first core network device may determine, according to current location information of the UE, a RAN node (ie, a second RAN node) that is currently serving the UE.
  • the current location information of the UE may be the identifier of the RAN node currently serving the UE, the ECGI of the cell currently located by the UE, or the TAI or TAC of the TA currently located by the UE.
  • the indication information is a failure cause value (or a cause value).
  • the reason includes: the UE initiates an RRC connection recovery procedure from other RAN nodes except the first RAN node. Further, the reason includes: the UE initiates an RRC connection recovery process from the second RAN node, and in this case, the indication information may include an identifier of the second RAN node.
  • the reason may further include: the UE is performing handover; or, the context transfer; or the UE is unreachable at the first RAN node; or the first downlink information is not transmitted.
  • step 407 when the UE initiates an RRC connection recovery process from other RAN nodes other than the first RAN node, step 407 can be performed in the following two situations:
  • the step 407 may include: the first core network device sends the second downlink information to the second RAN node after the path switching in the RRC connection recovery process is completed according to the indication information.
  • the path switching refers to switching the transmission path of the control plane signaling of the UE and the transmission path of the user plane data on the first RAN node of the UE to the second RAN node.
  • the path switching includes two parts, one part is to switch the transmission path between the RAN1 and the AMF for transmitting the control plane signaling of the UE to between the RAN2 and the AMF, and the other part is to transmit the UE between the RAN1 and the UPF1.
  • the transmission path of the user plane data is switched between RAN2 and UPF2.
  • the method may further include: the first core network device sends a subscription request message to the second core network device, where the subscription request message is used to request the second core network device to complete the path switching in the RRC connection recovery process.
  • a core network device sends a notification message, the notification message is used to notify that the path switch is completed; the second core network device receives the subscription request from the first core network device; and the second core network device completes the path switch in the RRC connection recovery process
  • a core network device sends a notification message. For example, after the N2 interface path switch request response message is sent (refer to step 914), the second core network device may determine that the RRC connection recovery is complete or the path switch completion in the RRC connection recovery process is completed.
  • the step 407 may include: the first core network device sends the second downlink information to the second RAN node after the RRC connection recovery is completed according to the indication information.
  • the first core network device may also directly send the second downlink information to the second RAN node after the RRC connection recovery is completed.
  • the first core network device sends a subscription request message to the second core network device, where the subscription request message is used to request the second core network device to send a notification message to the first core network device after the RRC connection recovery process is completed, and the notification message is sent.
  • the second core network device receives the subscription request from the first core network device, and the second core network device sends the notification message to the first core network device after the RRC connection recovery is completed.
  • the first core network device sends the second downlink information to the second RAN node after the path switching is completed, so that the second RAN node can correctly receive the second downlink information. It can be understood that if the first core network device sends the second downlink information to the second RAN node before the path switching is completed, the second downlink information sent by the AMF to the second RAN node fails to be sent, or is still sent to On the first RAN node connected to itself.
  • the first core network device may send the second downlink information to the second RAN node after receiving the indication information for a preset time (which may also be referred to as a preset time period).
  • the preset time can be set by a guard timer.
  • the first core network device starts a timer according to the indication information, and sends the second downlink information to the second RAN node after the timer expires.
  • the preset time of the timer is the preset time.
  • the preset time may be set to a time required for the UE's RRC connection recovery process to complete.
  • the information transmitted between the first core network device and the first RAN node in Embodiment 1 can also be perceived by the second core network device.
  • the embodiment of the present application further provides two communication methods, which are applied to a scenario in which the UE with the RRC connection state is inactive is moved from the coverage of the first RAN node to the coverage of the second RAN node.
  • FIG. 7 includes two schemes, the first scheme including steps 701-707 and 708a, and the second scheme including steps 701-707 and 708b.
  • One solution is a communication method. Specifically include:
  • the first core network device sends the first downlink information to the second core network device.
  • the first downlink information in the first core network device may be downlink information received by the first core network device from other core network devices, or may be downlink information generated by the first core network device.
  • the first downlink information is downlink information of the UE.
  • the first core network device when the first downlink information is information related to a PDU session of the UE, the first core network device may be an SMF, and the second core network device may be an AMF.
  • the first core network device When the first downlink information is a short message sent to the UE, the first core network device may be an SMSF, and the second core network device may be an AMF.
  • Table 2 which is not listed here.
  • the second core network device receives the first downlink information from the first core network device, and sends the first downlink information to the first RAN node.
  • the first RAN node receives the first downlink information of the UE from the second core network device.
  • the first RAN node pages the UE according to the first downlink information.
  • step 704 For the description related to step 704, refer to step 403, and details are not described herein again.
  • the first RAN node receives a context request of the UE from the second RAN node.
  • step 705 For a description related to step 705, refer to step 404, and details are not described herein again.
  • the first RAN node sends a first message to the second core network device according to the context request.
  • the first message may indicate that the first downlink information processing fails.
  • the second core network device receives the first message from the first RAN node.
  • the second core network device sends the first downlink information to the second RAN node according to the first message.
  • the foregoing method may further include: the first RAN node sends the current location information of the UE to the second core network device, and the second core network device receives the current location information of the UE from the first RAN node.
  • the second core network device may determine, according to the current location information of the UE, the RAN node (ie, the second RAN node) that is currently serving the UE, and send the first downlink information to the second RAN node according to the first message.
  • the current location information of the UE may be the identifier of the RAN node currently serving the UE, the ECGI of the cell currently located by the UE, or the TAI or TAC of the TA currently located by the UE.
  • the second core network device sends the indication information to the first core network device according to the first message.
  • the role of the first downlink information, the second downlink information, and the first message may be any one of the following cases 1-5:
  • the first downlink information is used by the first RAN node to activate the PDU session of the UE, and the PDU session is in a deactivated state; the first message is used to indicate that the PDU session activation fails.
  • the PDU session activation failure may be indicated by the message type or the message name of the first message.
  • the first message may be used to indicate that the PDU session activation fails.
  • the PDU session activation failure may also be indicated by adding an indication information to the first message, and a related description about the indication information may be referred to in the following description.
  • the second core network device may determine, according to the first message, that the PDU session of the first RAN node to activate the UE fails.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not activate the UE.
  • PDU session eg, does not trigger the establishment of a data channel for the air interface DRB between the UE and the first RAN node for the PDU session of the UE, does not trigger the establishment of the first RAN node and the first UPF for the PDU session of the UE
  • the data channel of the N3 interface, and the first message is sent to the second core network device.
  • the method may further include: the second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is valid for the device in the effective area of the first downlink information. .
  • the valid area information of the first downlink information and the first downlink information may be included in the same message.
  • step 708a when the second core network device determines that the UE is located in the effective area according to the current location information of the UE and the effective area information of the first downlink information, step 708a is performed; when the second core network device is configured according to the UE When the current location information and the valid area information of the first downlink information determine that the UE is not located in the active area, step 708b is performed.
  • the second core network device determines that the UE is located in the active area according to the current location information of the UE and the effective area information of the first downlink information
  • the first The first downlink information sent by the RAN node and the downlink information sent to the second RAN node may be the same. Therefore, the second core network device may directly send the first downlink information to the second RAN node.
  • a core network device sends indication information, and the first core network device sends the first downlink information to the second RAN node.
  • the second core network device may send the indication information to the first core network device, so that the first core network device constructs the second downlink information that is sent to the second RAN node. That is to say, after step 708b, the process of "the first core network device sends the second downlink information to the second RAN node" in step 407 can be performed.
  • the implementation of the process can be referred to above, and details are not described herein again.
  • the first core network device sends the first downlink information or the second downlink information to the second RAN node according to the determination result that the UE is located in the effective area.
  • the direct configuration may be The second downlink information sent by the second RAN node does not need to determine whether the UE is located in the active area.
  • the AMF determines that the UE is located in the effective area according to the current location information of the UE and the effective area information of the first downlink information
  • step 708b is performed.
  • step 708a is performed.
  • the PDU session of the UE in an active state does not include the PDU session rejected by the second RAN node.
  • the AMF reports the PDU session to be updated to the SMF1, and the updated PDU session is the UE and is accepted by the second RAN node.
  • the PDU session in the active state for example, PDU session 2 and PDU session 3
  • the first downlink information sent by SMF1 to the AMF is used to activate the PDU session of the UE, which is in a deactivated state (ie, a PDU session) 1).
  • the AMF needs to send an indication message to SMF1 indicating that the PDU session activation failed. Otherwise, when the SMF1 receives the PDU session that needs to be updated by the AMF, the SMF1 does not know how to perform the subsequent steps because the SMF1 does not receive the feedback of the PDU session 1 state. Therefore, in this case, the second core network device can perform step 708b.
  • the second core network device can perform step 708a.
  • the second core network device may be in a connection management connection state on the second core network device, and the second core network device is configured according to the location information in the context of the stored UE. And when the effective area information of the first downlink information determines that the UE is located in the effective area of the first downlink information, the second core network device sends the first downlink information to the first RAN node.
  • the second core network device when the RRC connection state of the UE is the connected state or the inactive state, stores the context of the UE, where the context includes the location information of the UE, and the second core network device considers the location in the context.
  • the information is the current location information of the UE. Therefore, the second core network device determines that the UE is located in the effective area of the first downlink information according to the location information in the context of the stored UE and the effective area information of the first downlink information.
  • the first downlink information is valid for the UE, and the second core network device sends the first downlink information to the first RAN node.
  • Case 2 The first downlink information is used by the first RAN node to deactivate the PDU session of the UE, and the PDU session is in an active state; the first message is used to indicate that the PDU session deactivation fails.
  • the PDU session deactivation may be indicated by the message type or the message name of the first message.
  • the first message may be used to indicate that the PDU session is deactivated. failure.
  • the PDU session deactivation failure may also be indicated by adding an indication information to the first message, and a related description about the indication information may be referred to in the following description.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not deactivate. In the PDU session, the first RAN node sends a first message to the second core network device.
  • Case 3 The first downlink information is used by the first RAN node to update the PDU session of the UE, and the PDU session is in an active state; the first message is used to indicate that the PDU session update fails.
  • the PDU session update failure may be indicated by the message type or the message name of the first message.
  • the message type is a failure message or a rejection message
  • the first message may be used to indicate that the PDU session update fails.
  • the PDU session update failure may also be indicated by adding an indication information to the first message, and a related description about the indication information may be referred to in the following description.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not update the In the PDU session, the first RAN node sends a first message to the second core network device.
  • Case 4 The first downlink information is used by the first RAN node to release the PDU session of the UE, and the PDU session is in an active state; the first message is used to indicate that the PDU session release fails.
  • the PDU session release failure may be indicated by the message type or the message name of the first message.
  • the message type is a failure message or a rejection message
  • the first message may be used to indicate that the PDU session release fails.
  • the PDU session release failure may also be indicated by adding an indication information to the first message, and a related description about the indication information may be referred to in the following description.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and the first RAN node does not release the In the PDU session, the first RAN node sends a first message to the second core network device.
  • the first core network device may be an SMF
  • the second core network device may be an AMF
  • the first downlink information is downlink information sent to the UE, and the first message is used to indicate that the first downlink information transmission fails.
  • the first downlink information transmission failure may be indicated by the message type or the message name of the first message.
  • the first message may be used to indicate the first Downstream information transmission failed.
  • the first downlink information transmission failure may also be indicated by adding an indication information to the first message, and a related description about the indication information may be referred to in the following description.
  • the first core network device may be a device that generates the first downlink information
  • the second core network device may be a device that forwards the first downlink information.
  • the first core network device may be an SMSF (a device that generates the first downlink information)
  • the second core network device may be an AMF (forwarding the first Downstream information device).
  • the first RAN node may determine that the UE is currently located in the coverage of the second RAN node, and the first RAN node cannot successfully send the UE to the UE. Sending the first downlink information, the first RAN node sends the first message to the second core network device.
  • the second core network device may determine that the first downlink information fails to be sent. Because the UE is currently located in the coverage of the second RAN node, the second core network device sends the first to the second RAN node. Downlink information, such that the second RAN node sends the first downlink information to the UE. Certainly, the second core network device may also send indication information to the first core network device, so that the first core network device sends the first downlink information to the second RAN node.
  • the indication information is a failure cause value (or a cause value).
  • the reason includes: the UE initiates an RRC connection recovery procedure from other RAN nodes except the first RAN node. Further, the reason includes: the UE initiates an RRC connection recovery process from the second RAN node, and in this case, the indication information may include an identifier of the second RAN node.
  • the reason may further include: the UE is performing handover; or, the context transfer; or the UE is unreachable at the first RAN node; or the first downlink information is not transmitted.
  • the step 708a may be performed after the RRC connection recovery initiated by the UE is completed, that is, the step 708a may include: the second core network device sends, according to the first message, the second RAN node after the RRC connection recovery is completed.
  • a downlink message may be performed after the path switching in the RRC connection recovery procedure initiated by the UE is completed, that is, step 708a may include: after the second core network device completes the path switching in the RRC connection recovery process according to the first message, The second RAN node sends the first downlink information. For example, after the N2 interface path switch request response message is sent (refer to step 914), the second core network device may determine that the RRC connection recovery is complete or the path switch completion in the RRC connection recovery process is completed.
  • the second core network device may send the first downlink information to the second RAN node or send the indication information to the first core network device after the preset time of receiving the first message.
  • the preset time can be set by the protection timer.
  • the second core network device starts a timer according to the first message, and sends the first downlink information to the second RAN node after the timer expires.
  • the second core network device starts a timer according to the first message, and sends the indication information to the first core network device after the timer expires.
  • the preset time of the timer is the preset time. Exemplarily, the preset time may be set to the time required for the UE's RRC connection recovery procedure to complete.
  • the first downlink information is used to activate the PDU session
  • the second core network device may determine that the PDU session activation of the UE fails according to the first message, and may notify the first core network device that the PDU session activation fails.
  • the second core network device may directly send the indication information in the first message to the first core network device, or generate another indication according to the indication information, when the indication information in the first message indicates that the PDU session activation fails.
  • the information is sent to the first core network device, and the other indication information is also used to indicate that the PDU session activation failed.
  • the second node may generate the indication information to be sent to the first core network device.
  • the first core network device may perform the first downlink device to send the second downlink to the second RAN node in step 407 in the first embodiment. information".
  • the second downlink information is the same as the first downlink information.
  • the embodiment of the present application also provides a communication method.
  • the second core network device acquires the current location information of the UE, and processes the first downlink information according to the current location information of the UE.
  • the method is applied to a scenario in which a UE in which an RRC connection state is inactive is moved from a coverage of a first RAN node to a coverage of a second RAN node.
  • Two schemes are included in FIG. 8, the first scheme including steps 801-807 and 808a, and the second scheme including steps 801-807 and 808b.
  • One solution is a communication method.
  • the second core network device acquires the first downlink information.
  • the first downlink information may be downlink information received by the second core network device from the first core network device, or may be downlink information generated by the second core network device.
  • the second core network device may be an AMF, and the first downlink information may be downlink information received by the AMF from the SMF.
  • the first downlink information is a short message sent to the UE
  • the second core network device may be an AMF
  • the first downlink information may be downlink information received by the AMF from the SMSF.
  • the first downlink information is the access and mobility management parameters on the updated UE
  • the second core network device may be an AMF
  • the first downlink information may be downlink information generated by the AMF.
  • the second core network device sends a location request message to the first RAN node, where the location request message is used to request current location information of the UE.
  • the second core network device Since the second core network device determines that the RAN node serving as the UE is the first RAN node according to the location information in the context of the stored UE, the second core network device sends a location request message to the first RAN node.
  • the first RAN node receives a location request message from the second core network device.
  • the first RAN node pages the UE according to the location request message.
  • step 403 For a description of the paging of the UE by the first RAN node, refer to step 403 in the above, and details are not described herein again.
  • the first RAN node receives a context request of the UE from the second RAN node.
  • step 805 For a description of the step 805, refer to the step 404 in the above, and details are not described herein again.
  • the first RAN node sends, to the second core network device, indication information that the UE initiates an RRC connection recovery procedure from other RAN nodes other than the first RAN node according to the context request, and/or current location information of the UE.
  • the first RAN node may determine that the UE is currently located within the coverage of the second RAN node. Therefore, the first RAN node may send, to the second core network device, indication information that the UE initiates an RRC connection recovery procedure from other RAN nodes other than the first RAN node, and/or current location information of the UE. Since the RAN node serving the UE at this time is the second RAN node, the current location information of the UE may indicate that the RAN node currently serving the UE is the second RAN node.
  • the second core network device receives the current location information of the UE from the first RAN node, and/or the second core network device receives, from the first RAN node, the UE initiates an RRC connection recovery from other RAN nodes except the first RAN node. Instructions for the process.
  • the second core network device receives from the first RAN node.
  • the indication information when the first RAN node sends the current location information of the UE to the second core network device, the second core network device receives the current location information of the UE from the first RAN node.
  • the first RAN node sends the indication information of the RRC connection recovery procedure and the current location information of the UE from the RAN node other than the first RAN node to the second core network device, the second core network device from the first RAN node The indication information and current location information of the UE are received.
  • step 808a or 808b may be performed, when the first downlink information of the UE is sent to When the information of the UE is used, step 808a may be performed.
  • the second core network device sends the first downlink information to the second RAN node.
  • the second core network device sends the indication information to the first core network device.
  • the first downlink information may be any one of the following cases 1-5:
  • the first downlink information is used by the first RAN node to activate the PDU session of the UE, and the PDU session is in a deactivated state.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node, and then the first RAN node The second core network device sends indication information and/or current location information of the UE. The specific reasons can be seen above.
  • the method may further include: the second core network device receives the effective area information of the first downlink information from the first core network device, where the first downlink information is valid for the device in the effective area of the first downlink information. .
  • the valid area information of the first downlink information and the first downlink information may be included in the same message.
  • step 808a when the second core network device determines that the UE is located in the effective area according to the current location information of the UE and the effective area information of the first downlink information, step 808a is performed; when the second core network device is configured according to the UE When the current location information and the valid area information of the first downlink information determine that the UE is not located in the active area, step 808b is performed.
  • the second core network device determines that the UE is located in the active area according to the current location information of the UE and the effective area information of the first downlink information
  • the first The first downlink information sent by the RAN node and the downlink information sent to the second RAN node may be the same. Therefore, the second core network device may directly send the first downlink information to the second RAN node.
  • a core network device sends indication information, and the first core network device sends the first downlink information to the second RAN node.
  • the second core network device may send the indication information to the first core network device, so that the first core network device constructs the second downlink information that is sent to the second RAN node. That is, after step 808b, the process of "the first core network device sends the second downlink information to the second RAN node" in step 407 may be performed.
  • the implementation of the process can be referred to above, and details are not described herein again.
  • the first core network device sends the first downlink information or the second downlink information to the second RAN node according to the determination result that the UE is located in the effective area.
  • the direct configuration may be The second downlink information sent by the second RAN node does not need to determine whether the UE is located in the active area.
  • the AMF determines that the UE is located in the effective area according to the current location information of the UE and the effective area information of the first downlink information
  • step 808b is performed.
  • step 808a is performed.
  • the PDU session of the UE in an active state does not include the PDU session rejected by the second RAN node.
  • the first downlink information is used by the first RAN node to deactivate the PDU session of the UE.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node. Therefore, the first RAN node does not deactivate the PDU session, and the first RAN node sends the indication information and/or the current location information of the UE to the second core network device.
  • Case 3 The first downlink information is used by the first RAN node to update the PDU session of the UE.
  • an exemplary implementation of step 806 after receiving the context request sent by the second RAN node, the first RAN node may determine that the UE initiates an RRC connection to the second RAN node. Restore the request. Therefore, the first RAN node does not update the PDU session, and the first RAN node sends the indication information and/or the current location information of the UE to the second core network device.
  • Case 4 The first downlink information is used by the first RAN node to release the PDU session of the UE.
  • the first RAN node may determine that the UE initiates an RRC connection recovery request to the second RAN node. Therefore, the first RAN node does not release the PDU session, and the first RAN node sends the indication information and/or the current location information of the UE to the second core network device.
  • the first core network device may be an SMF
  • the second core network device may be an AMF
  • the first downlink information is downlink information sent to the UE.
  • the first core network device may be a device that generates the first downlink information
  • the second core network device may be a device that forwards the first downlink information.
  • the first core network device may be an SMSF (a device that generates the first downlink information)
  • the second core network device may be an AMF (forwarding the first Downstream information device).
  • the second core network device may also be a device that generates the first downlink information.
  • the first RAN node may determine that the UE is currently located in the coverage of the second RAN node. Therefore, the first RAN node cannot successfully send the first downlink information to the UE, and the first RAN node sends the indication information and/or the current location information of the UE to the second core network device.
  • the second core network device may determine that the first downlink information transmission fails. Because the UE is currently located in the coverage of the second RAN node, the second core network device The second RAN node sends the first downlink information, so that the second RAN node sends the first downlink information to the UE. Certainly, the second core network device may also send indication information to the first core network device, so that the first core network device sends the first downlink information to the second RAN node.
  • the step 808a may be performed after the RRC connection recovery initiated by the UE is complete, that is, the step 808a may include: the second core network device sends the first downlink information to the second RAN node after the RRC connection recovery is completed.
  • the step 808a may be performed after the path switching in the RRC connection recovery process initiated by the UE is completed, that is, the step 808a may include: after the path switching in the RRC connection recovery process is completed, the second core network device sends the second RAN node to the second RAN node.
  • a downlink message For example, after the N2 interface path switch request response message is sent (refer to step 914), the second core network device may determine that the RRC connection recovery is complete or the path switch completion in the RRC connection recovery process is completed.
  • the second core network device may send the first downlink information to the second RAN node or to the first core network after receiving the preset information of the indication information and/or the current location information of the UE.
  • the device sends an indication message.
  • the preset time can be set by the protection timer.
  • the second core network device starts a timer, and sends the first downlink information to the second RAN node after the timer expires.
  • the second core network device starts a timer, and sends the indication information to the first core network device after the timer expires.
  • the preset time of the timer is the preset time.
  • the preset time may be set to a time required for the UE's RRC connection recovery process to complete.
  • the first downlink information is used to activate the PDU session
  • the second core network device determines, according to the indication information and/or the current location information of the UE, that the PDU session activation of the UE fails, and the information about the failure of the PDU session activation may be notified.
  • a core network device followed by a decision performed by the first core network device.
  • the second core network device may directly send the indication information to the first core network device, or generate another indication information according to the indication information, and send the indication information to the first core network device, and An indication message is also used to indicate that the PDU session activation failed.
  • the first core network device may perform, in step 407 in the first embodiment, the first core network device sends the second downlink to the second RAN node. information".
  • the second downlink information is the same as the first downlink information.
  • the core network device acquiring the current location information of the UE from the first RAN node is only an example of acquiring the current location information of the UE by the core network device.
  • the core network device may also adopt other The method obtains current location information of the UE, for example, the current location information of the UE may be acquired from the second RAN node.
  • the granularity of the effective area of the first downlink information may be TA granularity, base station granularity, cell granularity, slice granularity, slice instance granularity, UPF granularity, SMF granularity, PLMN granularity, and the like. That is, the first downlink information is valid for devices in the PLMN in the service area of the SMF in the coverage area of the base within the TA, within the intra-cell, within the intra-slice, and in the service area of the SMF.
  • the indication information is used to indicate that the PDU session activation fails.
  • the indication information is used to indicate that the first core network device re-initiates the PDU session activation process.
  • the indication information is used to indicate that the PDU session is deactivated. It can also be described as "instruction information is used to indicate that the first core network device re-initiates the PDU session deactivation process"; “instruction information is used to indicate that the PDU session update fails" may also be described as "instruction information is used to indicate the first core network”
  • the device re-initiates the PDU session update procedure.
  • the indication information is used to indicate that the PDU session release fails.
  • the indication information is used to indicate that the first core network device re-initiates the PDU session release procedure.
  • the method provided in the embodiment of the present application is exemplarily illustrated by using the foregoing method in a 5G network as an example.
  • the UE has two PDU sessions, which are a first PDU session and a second PDU session, the first PDU session is in a deactivated state, and the second PDU session is in an active state, serving the first PDU session and the second PDU session.
  • the SMFs are SMF1 and SMF2 respectively.
  • the first downlink information is used to activate the first PDU session of the UE.
  • the first core network device is SMF1
  • the second core network device is AMF.
  • the following method is applied to a scenario in which the UE moves from the coverage of RAN1 to the coverage within the coverage of RAN2.
  • the UPF serving the UE accessing the RAN1 is UPF1
  • the UPF serving the UE accessing the RAN2 is UPF2.
  • the AMF sends indication information to the SMF1, where the indication information is used to indicate that the first PDU session activation of the UE fails.
  • the method includes:
  • UPF1 sends a data notification to SMF1.
  • the UPF1 After receiving the downlink data of the UE, the UPF1 sends a data notification to the SMF serving the PDU session if the PDU session for carrying the downlink data is determined to be in a deactivated state, and the data notification is used for notification.
  • SMF1 has downlink data of the UE to be transmitted.
  • the PDU session carrying the downlink data is taken as an example of the first PDU session.
  • the network device 1 transmits a message to the network device 2, and accordingly, the network device 2 receives the information from the network device 1.
  • UPF1 sends a data notification to SMF1
  • SMF1 receives a data notification from UPF1.
  • the actions received by the network device 2 are not described.
  • the SMF1 sends the first downlink information and the effective area of the first downlink information to the AMF (hereinafter referred to as an effective area).
  • the method may further include: the SMF1 may determine, according to the N4 interface session identifier corresponding to the identifier of the first PDU session included in the data notification, the PDU session to be activated.
  • the first downlink information is information generated by SMF1 for the first PDU session.
  • the effective area of the first downlink information and the first downlink information may be included in an N1 interface message N2 interface message transmission request message (Namf_Communication_N1N2MessageTransfer) provided by the AMF.
  • N1 interface message N2 interface message transmission request message Namf_Communication_N1N2MessageTransfer
  • the AMF determines that the state of the UE is a connection management connection state.
  • the state of the UE is included in the context of the UE stored in the AMF.
  • Step 902 is an optional step.
  • Step 903 may be directly performed after step 902. Step 903 may also be performed when the AMF further determines that the UE is located in the active area according to the location information and the valid area in the context of the stored UE.
  • the AMF sends the first downlink information to the RAN1.
  • the first downlink information may be included in an N2 interface request (N2request) message.
  • N2request N2 interface request
  • the RAN1 pages the UE.
  • Step 904 may be performed when RAN1 determines that the RRC connected state of the UE is in an inactive state.
  • the AMF may also send an N1 interface message N2 interface message transmission response message (Namf_Communication_N1N2MessageTransfer response) provided by the AMF to the SMF1, where the AMF may be configured to indicate that the AMF successfully receives the first downlink information and the first downlink information. Information about the effective area.
  • N1 interface message N2 interface message transmission response message Namf_Communication_N1N2MessageTransfer response
  • the method may further include the following steps:
  • the UE sends an RRC connection resume request to the RAN2.
  • the RAN2 acquires a UE context from the RAN1.
  • the RAN2 sends a context request (retrieve UE context request) to the RAN1, where the identifier of the UE is included (for example, an RRC inactive-tempo network temporary identity (I-in- RNTI).
  • RAN1 sends a UE context response (Retrieve UE context response) to RAN2, which contains the context of the UE.
  • the RAN1 sends an indication information to the AMF.
  • the indication information may be included in an N2 interface request response (N2request ack) message.
  • the indication information is used to indicate that the first PDU session of the RAN1 to activate the UE fails.
  • the indication information reference may be made to the above, and no further details are provided herein.
  • the RAN1 may also send a message to the AMF to indicate that the RAN1 fails to activate the first PDU session of the UE.
  • the message For the explanation of the message, reference may be made to the above, and details are not described herein again.
  • the AMF sends an indication message to the SMF1.
  • the indication information may be included in a session context update request (Nsmf_PDUSession_UpdateSMContextRequest) of the PDU session provided by the SMF1.
  • Nsmf_PDUSession_UpdateSMContextRequest a session context update request of the PDU session provided by the SMF1.
  • the indication information sent by the AMF to the SMF1 is used by the SMF1 to determine that the first PDU session activation failed.
  • the SMF1 determines to send the second downlink information to the RAN2 after the preset time.
  • the SMF1 sends the second downlink information to the RAN2 after determining that the path switching completion of the UE or the RRC connection recovery procedure is completed.
  • the start time of the preset time in the embodiment and the following embodiments may be the time when the indication information is received, or may be other time, which is not specifically limited in the embodiment of the present application.
  • the SMF1 sends an indication information response to the AMF, where the indication information response is used to indicate that the SMF1 successfully receives the indication information.
  • the indication information response may be included in the session context update response (Nsmf_PDUSession_UpdateSMContextResponse) of the PDU session provided by SMF1.
  • Step 910 is an optional step. For the convenience of description, this step is not reflected in the following embodiments.
  • 911 and RAN2 send an N2 interface switch request to the AMF.
  • the N2 interface path switching request is used to request path switching of the UE.
  • path switching For a description of the path switching, refer to the above, and no further details are provided here.
  • the AMF sends a session context update request (Nsmf_PDUSession_UpdateSMContextRequest) of the PDU session provided by the SMF2 to the SMF2.
  • Nsmf_PDUSession_UpdateSMContextRequest a session context update request of the PDU session provided by the SMF2 to the SMF2.
  • the session context update request for the PDU session is used to request to update the context of the second PDU session.
  • the RAN2 accepts the second PDU session as an example for description.
  • the SMF2 sends a session context update response (Nsmf_PDUSession_UpdateSMContextResponse) of the PDU session provided by the SMF2 to the AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse a session context update response of the PDU session provided by the SMF2 to the AMF.
  • the AMF sends an N2 interface path switch request response (N2 path switch ack) to the RAN2.
  • N2 path switch ack N2 interface path switch request response
  • step 911 to step 914 The purpose of step 911 to step 914 is to switch the PDU session of the UE in an active state to RAN2. This process can also be performed before step 907, in which case step 909 may not be performed.
  • the RAN2 sends an RRC connection resume message to the UE.
  • Steps 905 to 915 are an RRC connection recovery procedure between the UE and the RAN.
  • Step 915 can also be performed between step 906 and step 911.
  • the SMF1 sends the second downlink information to the RAN2.
  • the SMF1 may send the second downlink information to the RAN2 through the AMF.
  • the first downlink information and the second downlink information may be the same or different. For details, refer to the related description in the foregoing.
  • the AMF may not perceive information transmitted between the SMF and the RAN, that is, the AMF transparently transmits information between the SMF and the RAN.
  • step 907a may also be included between step 907 and step 908.
  • Step 907a may be: AMF determines that the UE initiates an RRC connection recovery procedure from other RAN nodes than RAN1.
  • the AMF determines whether to send the indication information to the SMF1 according to whether the SMF (ie, SMF2) serving the second PDU session is the same as the SMF1.
  • the method provided by this embodiment includes:
  • the AMF acquires current location information of the UE.
  • the AMF may receive current location information of the UE sent by the RAN1.
  • the current location information of the UE indicates that the UE is located within the coverage of RAN2.
  • the AMF determines, according to the current location information of the UE and the valid area, whether the UE is located in the valid area, and whether the SMF (ie, SMF2) serving the PDU session of the UE in the active state is the same as the SMF1.
  • steps 1010a-1017a are performed.
  • the AMF sends an indication message to the SMF1.
  • the indication information may be included in a session context update request of the PDU session provided by the SMF1.
  • the indication information sent by the AMF to the SMF1 is used by the SMF1 to determine that the first PDU session activation failed.
  • the SMF1 determines to send the first downlink information to the RAN2 after the preset time.
  • the SMF1 sends the first downlink information to the RAN2 after determining that the path switching completion of the UE or the RRC connection recovery procedure is completed.
  • the preset time, the path switching, and the RRC connection recovery procedure reference may be made to the above, and details are not described herein again.
  • the SMF1 sends the first downlink information to the RAN2.
  • the SMF1 Since the UE is located in the active area at this time, the SMF1 sends the same downlink information to the RAN1 and the RAN2. Specifically, the SMF1 may send the first downlink information to the RAN2 through the AMF.
  • steps 1010b-1016b are performed.
  • the AMF determines, according to the indication information, that the first downlink information is sent to the RAN2 after the preset time.
  • the AMF sends the first downlink information to the RAN2 after determining that the path switching completion of the UE or the RRC connection recovery procedure is completed.
  • the AMF sends the first downlink information to the RAN2.
  • the AMF Since the UE is located in the active area at this time, the AMF sends the same downlink information to RAN1 and RAN2.
  • the SMF1 can determine the downlink information (the first downlink information or the second downlink information) sent to the RAN2 by determining whether the UE is currently located in the effective area.
  • the method provided by this embodiment includes:
  • step 1108 is the same as step 1010a.
  • the SMF1 determines whether the UE is in the valid area according to the current location information of the UE and the valid area. If yes, determine to send the first downlink information to the RAN2 after the preset time, and if not, generate the second downlink according to the current location information of the UE. Information, and determining to send the second downlink information to the RAN2 after the preset time.
  • step 1109 when the SMF1 determines that the UE is in the active area according to the current location information of the UE and the effective area, the SMF1 may further send the first to the RAN2 after determining that the path switching of the UE is completed or the RRC connection recovery process is completed. Downstream information.
  • the SMF1 may further send the second downlink information to the RAN2 after determining that the path switching of the UE is completed or the RRC connection recovery procedure is completed.
  • the preset time, the path switching, and the RRC connection recovery procedure reference may be made to the above, and details are not described herein again.
  • steps 911-915 are the same as steps 911-915, respectively.
  • step 1115 is performed after step 1114, and if the UE is not located in the active area, step 1116 is performed after step 1114.
  • the SMF1 sends the first downlink information to the RAN2.
  • the SMF1 may send the first downlink information to the RAN2 through the AMF.
  • the SMF1 sends the second downlink information to the RAN2.
  • the SMF1 may send the second downlink information to the RAN2 through the AMF.
  • the AMF obtains the current location information of the UE, and performs subsequent operations according to the current location information of the UE. Among them, the AMF may not perceive the information transmitted between the RAN and the SMF.
  • the RRC connection state of the UE stored in the AMF is an inactive state or the RRC connection state of the UE is not stored in the AMF.
  • the method provided by this embodiment includes:
  • 1200-1201 is the same as steps 900-901 respectively.
  • the AMF determines that the RRC connection status of the UE is an inactive state or that the RRC connection status of the UE is not stored in the AMF.
  • the AMF sends a location report control message to the RAN1.
  • the location report control message is the location request message above.
  • the RAN1 pages the UE.
  • step 1204 For a description of the step 1204, refer to step 904, and details are not described herein again.
  • steps 1205-1216 may be performed after step 1204.
  • the indication information in step 1207 may be included in a location report failure message.
  • the current location information of the UE may also be included in step 1207.
  • the AMF can determine whether the UE is within the active area.
  • the AMF sends the first downlink information to the RAN2 (for example, steps 1010b-1016b can be performed).
  • step 1209 may be replaced by: SMF1 generates second downlink information according to current location information of the UE, and determines to send second downlink information to RAN2 after a preset time; step 1215 does not execute.
  • the RAN1 may send a location report message to the AMF.
  • the location report message includes current location information of the UE.
  • the RAN1 can activate the first PDU session according to the first downlink information, and therefore, the AMF sends the first downlink information to the RAN1.
  • the communication device includes corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function module into the communication device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • the embodiment of the present application provides a communication device, which can be seen in FIG.
  • the apparatus 130 may be applied to a scenario in which a terminal in which an RRC connection state is in an inactive state moves from a coverage of a first RAN node to a coverage of a second RAN node.
  • the device 130 may be configured to perform the actions of the first core network device (the first core network device may be SMF1 in FIG. 9-12 in each of the foregoing method embodiments).
  • the device 130 may be a first core network device, or may be a chip or a system on chip, and is not limited.
  • the device 130 may include a communication unit 1302 and a processing unit 1301.
  • the processing unit 1301 is configured to send, by using the communication unit 1302, first downlink information to the first RAN node, where the first downlink information is used by the first RAN node to activate a packet data unit PDU session of the terminal, The PDU session is in a deactivated state;
  • the processing unit 1301 is further configured to receive, by using the communication unit 1302, the indication information from the first RAN node, where the indication information is used to indicate that the PDU session activation fails;
  • the processing unit 1301 is further configured to send, according to the indication information, second downlink information to the second RAN node by using the communication unit, where the second downlink information is used by the second RAN node to activate the terminal. PDU session.
  • processing unit 1301 is further configured to:
  • processing unit 1301 is further configured to:
  • the processing unit 1301 is further configured to receive, by using the communication unit 1302, current location information of the terminal from the first RAN node.
  • the indication information is a failure cause value
  • the failure cause value is used to indicate a reason why the PDU session activation fails.
  • the embodiment of the present application provides a communication device, which can be seen in FIG.
  • the apparatus 130 may be applied to a scenario in which a terminal whose RRC connection state is inactive is moved from coverage of the first RAN node to coverage of the second RAN node.
  • the apparatus 130 may be configured to perform the actions of the first RAN node (in FIG. 9-12, the first RAN node may be RAN1) in the foregoing method embodiments.
  • the device 130 may be a first RAN node, or may be a chip or a system on chip, and is not limited.
  • the device 130 includes a communication unit 1302 and a processing unit 1301.
  • the communication unit 1302 is configured to receive, by the first core network device, first downlink information of the terminal, where the first downlink information is used by the device to activate a packet data unit PDU session of the terminal, where the PDU session In the deactivated state;
  • the processing unit 1301 is configured to: when the RRC connection status of the terminal is in an inactive state, page the terminal according to the first downlink information;
  • the communication unit 1302 is further configured to receive a context request of the terminal from the second RAN node;
  • the communication unit 1302 is further configured to send, according to the context request, indication information to the first core network device, where the indication information is used to indicate that the PDU session activation fails.
  • the communication unit 1302 is further configured to send the current location information of the terminal to the first core network device.
  • the indication information is a failure cause value, where the failure reason value is used to indicate a reason why the PDU session activation fails.
  • the embodiment of the present application provides a communication device, which can be seen in FIG.
  • the apparatus 130 may be applied to a scenario in which a terminal whose RRC connection state is inactive is moved from coverage of the first RAN node to coverage of the second RAN node.
  • the device 130 can be used to perform related actions of the second core network device in the foregoing method embodiments.
  • the device 130 may be a second core network device, or may be a chip or a system on chip, and is not limited.
  • the device 130 includes a communication unit 1302 and a processing unit 1301.
  • the processing unit 1301 is configured to receive, by using the communication unit 1302, first downlink information from the first core network device, and send the first downlink information to the first RAN node, where the first downlink information is used for activation.
  • a packet data unit PDU session of the terminal, the PDU session is in a deactivated state;
  • the processing unit 1301 is further configured to receive, by the communication unit, a message, from the first RAN node, that is used to indicate that the PDU session activation fails;
  • the processing unit 1301 is further configured to send the first downlink information to the second RAN node by using the communication unit 1302 according to the message.
  • processing unit 1301 is further configured to:
  • the terminal When the terminal is located in the effective area according to the current location information of the terminal and the effective area information of the first downlink information, according to the message, to the second RAN node by using the communication unit. Sending the first downlink information.
  • processing unit 1301 is further configured to:
  • the communication unit sends the first downlink information to the first RAN node.
  • the processing unit 1301 is further configured to receive, by using the communication unit 1302, current location information of the terminal from the first RAN node.
  • the message type or the message name of the message is used to indicate that the PDU session activation fails; or the message includes indication information, where the indication information is a failure cause value, and the failure cause value is used to indicate The reason why the PDU session activation failed.
  • the embodiment of the present application provides a communication device, which can be seen in FIG.
  • the apparatus 130 may be applied to a scenario in which a terminal whose RRC connection state is inactive is moved from coverage of the first RAN node to coverage of the second RAN node.
  • the apparatus 130 may be configured to perform related actions of the second core network device (in FIG. 9-12, the second core network device may be an AMF) in the foregoing method embodiments.
  • the device 130 may be a second core network device, or may be a chip or a system on chip, and is not limited.
  • the device 130 includes a communication unit 1302 and a processing unit 1301.
  • the processing unit 1301 is configured to receive, by using the communication unit 1302, first downlink information from the first core network device, and send the first downlink information to the first RAN node, where the first downlink information is used for activation.
  • a packet data unit PDU session of the terminal, the PDU session is in a deactivated state;
  • the processing unit 1301 is further configured to receive, by the communication unit 1302, a message, from the first RAN node, that is used to indicate that the PDU session is failed to be activated;
  • the processing unit 1301 is further configured to send, by using the communication unit 1302, the indication information to the first core network device according to the message, where the indication information is used to indicate that the PDU session activation fails.
  • processing unit 1301 is further configured to:
  • the network device sends the indication information.
  • processing unit 1301 is further configured to:
  • the communication unit sends the first downlink information to the first RAN node.
  • the processing unit 1301 is further configured to receive, by using the communication unit 1302, current location information of the terminal from the first RAN node.
  • the indication information is a failure cause value, where the failure reason value is used to indicate a reason why the PDU session activation fails.
  • the embodiment of the present application further provides a computer readable storage medium, including instructions, when executed on a computer, causing a computer to execute the first core network device or the second core network device or the first RAN in the foregoing method embodiments.
  • the action of the node is not limited to:
  • the embodiment of the present application further provides a computer program product comprising instructions, when executed on a computer, causing a computer to execute the first core network device or the second core network device or the first RAN node in the foregoing method embodiments action.
  • the embodiment of the present application further provides a communication system, including the first core network device and the first RAN node in the foregoing embodiment.
  • system further includes: the foregoing second core network device, and may refer to the embodiment shown in FIG. 7 or FIG. 8.
  • the system further includes: the foregoing second RAN node, which may be referred to the embodiment shown in FIG. 6 or FIG. 7 or FIG. 8.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program 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 application 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 Transmission to another website site, computer, server or data center via wired (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 that includes one or more servers, data centers, etc. that can be integrated with the 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)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

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

Abstract

本申请提供了一种通信方法及装置，用于解决处于非激活态的终端的PDU会话激活失败的问题。该方法包括：第一核心网设备向第一RAN节点发送第一下行信息，第一下行信息用于第一RAN节点激活终端的PDU会话，PDU会话处于去激活态；第一核心网设备从第一RAN节点接收指示信息，指示信息用于指示PDU会话激活失败；第一核心网设备根据指示信息，向第二RAN节点发送第二下行信息，第二下行信息用于第二RAN节点激活终端的PDU会话。本申请涉及通信技术领域。

Description

通信方法及装置
本申请要求于2018年04月10日提交中国专利局、申请号为201810317648.X、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在第五代(fifth-generation，简称5G)无线通信系统中，对于无线资源控制(radio resource control，简称RRC)连接状态为非激活态的终端，接入和移动性管理功能(core access and mobility management function，简称AMF)上存储的终端的状态为连接管理连接(CM-Connected)态，AMF认为保存的终端的上下文中的位置信息是终端的当前位置信息。在终端未发生小区切换的情况下，若终端从无线接入网(radio access network，简称RAN)1节点(在用户面功能(user plane function，简称UPF)1的服务区域(serving area))的覆盖范围移动到RAN2节点(不在UPF1的服务区域)的覆盖范围后，AMF上保存的终端的上下文中的位置信息仍然为指示终端位于RAN1节点的覆盖范围内的信息。但实际上终端已经移动到RAN2节点的覆盖范围内。若终端的下行信息的有效区域与UPF的服务区域一致，则AMF根据保存的终端的上下文中的位置信息判断终端位于下行信息的有效区域内的判断结果是错误的。该情况下，若AMF将用于激活PDU会话的下行信息发给RAN1节点，会导致PDU会话激活失败。
发明内容
本申请实施例提供了一种通信方法及装置，用于解决处于非激活态的终端的PDU会话激活失败的问题。
第一方面，提供了一种通信方法，所述方法应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：第一核心网设备向所述第一RAN节点发送第一下行信息；所述第一核心网设备从所述第一RAN节点接收指示信息；所述第一核心网设备根据所述指示信息，向所述第二RAN节点发送第二下行信息。其中，该指示信息可以用于指示第一RAN节点处理第一下行信息失败。在由终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致的第一RAN节点无法处理第一下行信息的情况下，该方法通过第一核心网设备接收第一RAN节点在对第一下行信息处理失败后发送的指示信息，并根据该指示信息向第二RAN节点发送第二下行信息，进而使得第二下行信息能够被第二RAN节点成功处理，例如，第二RAN节点为当前为终端服务的RAN节点，因此能够成功处理第二下行信息。
结合第一方面，在第一方面的第一种可实施方式中，所述第一下行信息用于所述第一RAN节点激活所述终端的PDU会话，所述PDU会话处于去激活态；所述指示信息用于指示所述PDU会话激活失败；所述第二下行信息用于所述第二RAN节点激活所述PDU会话。以使得第一核心网设备向第二RAN节点发送第二下行信息并使得第 二RAN节点根据第二下行信息激活终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功激活终端的PDU会话。
结合第一方面，在第一方面的第二种可实施方式中，所述第一下行信息用于所述第一RAN节点去激活所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话去激活失败；所述第二下行信息用于所述第二RAN节点去激活所述PDU会话。以使得第一核心网设备向第二RAN节点发送第二下行信息并使得第二RAN节点根据第二下行信息去激活终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功去激活终端的PDU会话。
结合第一方面，在第一方面的第三种可实施方式中，所述第一下行信息用于所述第一RAN节点更新所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话更新失败；所述第二下行信息用于所述第二RAN节点更新所述PDU会话。以使得第一核心网设备向第二RAN节点发送第二下行信息并使得第二RAN节点根据第二下行信息修改终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功修改终端的PDU会话。
结合第一方面，在第一方面的第四种可实施方式中，所述第一下行信息用于所述第一RAN节点释放所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话释放失败；所述第二下行信息用于所述第二RAN节点释放所述PDU会话。以使得第一核心网设备向第二RAN节点发送第二下行信息并使得第二RAN节点根据第二下行信息释放终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功释放终端的PDU会话。
结合第一方面，在第一方面的第五种可实施方式中，所述第一下行信息为发往所述终端的下行信息；所述指示信息用于指示所述第一下行信息传输失败，所述第二下行信息与所述第一下行信息相同。以使得第一核心网设备根据所述指示信息识别所述第一下行信息传输失败，从而向第二RAN节点发送第二下行信息。
结合第一方面的第一种可实施方式，在第一方面的第六种可实施方式中，所述方法还包括：当所述第一核心网设备根据所述终端的当前位置信息确定所述终端不位于所述第一下行信息的有效区域内时，所述第一核心网设备根据所述终端的当前位置信息生成所述第二下行信息。其中，所述第一下行信息可以针对所述第一下行信息的有效区域内的设备有效。以使得第一核心网设备为终端生成与终端的当前位置信息对应的有效的第二下行信息，由于终端的当前位置信息即为第二RAN节点位置信息，所以第二下行信息对于第二RAN节点有效并能被第二RAN节点成功处理，从而避免了将无效的第一下行信息发给第二RAN节点所导致的处理失败。
结合第一方面的第一种可实施方式，在第一方面的第七种可实施方式中，当所述第一核心网设备根据所述终端的当前位置信息确定所述终端位于所述第一下行信息的有效区域内时，所述第二下行信息与所述第一下行信息相同。其中，所述第一下行信息可以针对所述第一下行信息的有效区域内的设备有效。
结合第一方面，或第一方面的上述任一种可实施方式，在第一方面的第八种可实施方式中，所述方法还包括：所述第一核心网设备从所述第一RAN节点接收所述终端 的当前位置信息。以使得第一核心网设备获取所述终端的当前位置信息，从而决定是否需要为终端生成与第一下行信息不同的第二下行信息。
结合第一方面，或第一方面的上述任一种可实施方式，在第一方面的第九种可实施方式中，所述指示信息为失败原因值。
结合第一方面的第九种可实施方式，在第一方面的第十种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程；或者，所述终端正在进行切换；或者，上下文转移；或者，所述终端在所述第一RAN节点不可达；或者，所述第一下行信息没有被传输。从而使得第一核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第一方面的第十种可实施方式，在第一方面的第十一种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程，所述第一核心网设备根据所述指示信息，向所述第二RAN节点发送第二下行信息，包括：所述第一核心网设备根据所述指示信息，在所述RRC连接恢复完成后向所述第二RAN节点发送所述第二下行信息。以使得第一核心网设备在所述RRC连接恢复完成后向所述第二RAN节点发送所述第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
结合第一方面的第十种可实施方式，在第一方面的第十二种可实施方式中，所述第一核心网设备根据所述指示信息，向所述第二RAN节点发送第二下行信息，包括：所述第一核心网设备根据所述指示信息，启动定时器，并在定时器超时后向所述第二RAN节点发送所述第二下行信息。以使得第一核心网设备在定时器到期后向所述第二RAN节点发送所述第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
结合第一方面的第十一或第十二种可实施方式，在第一方面的第十三种可实施方式中，所述方法还包括：所述第一核心网设备向第二核心网设备发送订阅请求消息，所述订阅请求消息用于请求所述第二核心网设备在所述RRC连接恢复流程完成后向所述第一核心网设备发送通知消息，所述通知消息用于通知所述RRC连接恢复完成。以使得第一核心网设备能够在获知所述RRC连接恢复完成之后才向第二RAN节点发送第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
结合第一方面的第十一种可实施方式，在第一方面的第十四种可实施方式中，所述方法还包括：所述第一核心网设备根据指示信息，启动定时器；所述第一核心网设备在所述定期器超时后，向所述第二RAN节点发送所述第二下行信息。其中，所述定时器可以用于所述RRC连接恢复流程完成，例如定时器超时表明所述RRC连接恢复流程完成。以使得第一核心网设备在定时器到期后向所述第二RAN节点发送所述第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
结合第一方面的第十种可实施方式，在第一方面的第十五种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程，所述第一核心网设备根据所述指示信息，向所述第二RAN节点发送第二下行信息，包括：所述第一核心网设备根据所述指示信息，在所述RRC连接恢复流程中的路径切换完成后向所述第二RAN节点发送所述第二下行信息。以使得第一核心网设备能够在所述RRC连接恢复流程中的路径切换完成之后才向第二RAN节点发送第二下行 信息，从而第二RAN节点能够成功处理第二下行信息。
结合第一方面的第十四种可实施方式，在第一方面的第十六种可实施方式中，所述方法还包括：所述第一核心网设备向第二核心网设备发送订阅请求消息，所述订阅请求消息用于请求所述第二核心网设备在所述RRC连接恢复流程中的路径切换完成后向所述第一核心网设备发送通知消息，所述通知消息用于通知所述路径切换完成。以使得第一核心网设备能够在获知所述RRC连接恢复流程中的路径切换完成之后才向第二RAN节点发送第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
第二方面，提供了一种通信方法，所述方法应用于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：所述第一RAN节点从第一核心网设备接收所述终端的第一下行信息；当所述终端的RRC连接状态为非激活态时，所述第一RAN节点根据所述第一下行信息，寻呼所述终端；所述第一RAN节点从所述第二RAN节点接收所述终端的上下文请求；所述第一RAN节点根据所述上下文请求向所述第一核心网设备发送指示信息。其中，该指示信息可以用于指示第一RAN节点对第一下行信息处理失败。使得在由终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致的第一RAN节点无法处理第一下行信息的情况下，该方法通过第一RAN节点向所述第一核心网设备发送指示信息，以使得第一核心网设备能够获知第一下行信息没有被第一RAN节点成功处理。
结合第二方面，在第二方面的第一种可实施方式中，所述第一下行信息用于激活所述终端的PDU会话，所述PDU会话处于去激活态；所述指示信息用于指示所述PDU会话激活失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法激活所述PDU会话的情况下，以使得所述第一核心网设备根据所述指示信息获知所述PDU会话激活失败。
结合第二方面，在第二方面的第二种可实施方式中，所述第一下行信息用于去激活所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话去激活失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法去激活所述PDU会话的情况下，以使得所述第一核心网设备根据所述指示信息获知所述PDU会话去激活失败。
结合第二方面，在第二方面的第三种可实施方式中，所述第一下行信息用于更新所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话更新失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法修改所述PDU会话的情况下，以使得所述第一核心网设备根据所述指示信息获知所述PDU会话修改失败。
结合第二方面，在第二方面的第四种可实施方式中，所述第一下行信息用于释放所述终端的PDU会话，所述PDU会话处于激活态；所述指示信息用于指示所述PDU会话释放失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法释放所述PDU会话的情况下，以使得所述第一核心网设备根据所述指示信息获知所述PDU会话释放失败。
结合第二方面，在第二方面的第五种可实施方式中，所述第一下行信息为发往所述终端的下行信息；所述指示信息用于指示所述第一下行信息传输失败。从而在由于 终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法将终端的第一下行信息发给终端的情况下，以使得所述第一核心网设备根据所述指示信息获知第一下行信息没有成功发送给终端。
结合第二方面，或第二方面的上述任一种可实施方式，在第二方面的第六种可实施方式中，所述指示信息为失败原因值。从而使得第一核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第二方面的第六种可实施方式，在第二方面的第七种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程；或者，所述终端正在进行切换；或者，上下文转移；或者，所述终端在所述第一RAN节点不可达；或者，所述第一下行信息没有被传输。从而使得第一核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第二方面，或第二方面的上述任一种可实施方式，在第二方面的第八种可实施方式中，所述方法还包括：所述第一RAN节点向所述第一核心网设备发送所述终端的当前位置信息。以使得第一核心网设备获取所述终端的当前位置信息，从而决定终端是否位于第一下行信息的有效区域内。其中，所述第一下行信息可以针对所述第一下行信息的有效区域内的设备有效。
第三方面，提供了一种通信方法，所述方法应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：第二核心网设备从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息；所述第二核心网设备从所述第一RAN节点接收第一消息；所述第二核心网设备根据所述第一消息，向所述第二RAN节点发送所述第一下行信息。其中，第一消息可以用于指示第一RAN节点对第一下行信息处理失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致的第一RAN节点无法处理第一下行信息的情况下，该方法通过第二核心网设备接收来自第一核心网设备发送第一下行信息，以使得第二核心网设备在接收到第一RAN节点发送的用于指示其对第一下行信息处理失败的第一消息后，将第一下行信息发送给第二RAN节点，进而使得第一下行信息可以被第二RAN节点成功处理。例如，由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功处理第一下行信息。
结合第三方面，在第三方面的第一种可实施方式中，所述第一下行信息用于激活所述终端的PDU会话，所述PDU会话处于去激活态；所述第一消息用于指示所述PDU会话激活失败。以使得第二核心网设备将第一下行信息重新发送给第二RAN节点并使得第二RAN节点根据第一下行信息激活终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功激活终端的PDU会话。
结合第三方面，在第三方面的第二种可实施方式中，所述第一下行信息用于去激活所述终端的PDU会话，所述PDU会话处于激活态；所述第一消息用于指示所述PDU会话去激活失败。以使得第二核心网设备将第一下行信息重新发送给第二RAN节点并使得第二RAN节点根据第一下行信息去激活终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功取激活终端的PDU会话。
结合第三方面，在第三方面的第三种可实施方式中，所述第一下行信息用于更新所述终端的PDU会话，所述PDU会话处于激活态；所述第一消息用于指示所述PDU会话更新失败。以使得第二核心网设备将第一下行信息重新发送给第二RAN节点并使得第二RAN节点根据第一下行信息修改终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功修改终端的PDU会话。
结合第三方面，在第三方面的第四种可实施方式中，所述第一下行信息用于释放所述终端的PDU会话，所述PDU会话处于激活态；所述第一消息用于指示所述PDU会话释放失败。以使得第二核心网设备将第一下行信息重新发送给第二RAN节点并使得第二RAN节点根据第一下行信息释放终端的PDU会话。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功释放终端的PDU会话。
结合第三方面，在第三方面的第五种可实施方式中，所述第一下行信息为发往所述终端的下行信息；所述第一消息用于指示所述第一下行信息传输失败。以使得第二核心网设备将第一下行信息重新发送给第二RAN节点并使得第二RAN节点将所述第一下行信息发送给终端。由于第二RAN节点为当前为终端服务的RAN节点，因此，第二RAN节点能够成功地将所述第一下行信息发送给终端。
结合第三方面，或第三方面的上述任一种可实施方式，在第三方面的第六种可实施方式中，所述第二核心网设备根据所述第一消息，向所述第二RAN节点发送所述第一下行信息，包括：所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息，所述第一下行信息针对所述第一下行信息的有效区域内的设备有效；当所述第二核心网设备根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备根据所述第一消息，向所述第二RAN节点发送所述第一下行信息。以使得第二核心网设备确定所述终端的当前位置位于所述第一下行信息的有效区域内，从而决定向第二RAN节点发送第一下行信息，进而使得第一下行信息能够被第二RAN节点成功处理，从而避免了将无效的第一下行信息发给第二RAN节点所导致的处理失败。
结合第三方面，或第三方面的上述任一种可实施方式，在第三方面的第七种可实施方式中，所述向所述第一RAN节点发送所述第一下行信息，包括：所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息，所述第一下行信息针对所述第一下行信息的有效区域内的设备有效；当所述终端在所述第二核心网设备上的状态为连接管理连接态，且所述第二核心网设备根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备向所述第一RAN节点发送所述第一下行信息。以使得第二核心网设备确定所述终端的上下文中的位置位于所述第一下行信息的有效区域内，从而决定向第一RAN节点发送第一下行信息，进而使得第一下行信息能够被第一RAN节点成功处理，从而避免了将无效的第一下行信息发给第一RAN节点所导致的处理失败。
结合第三方面的第一种可实施方式，在第三方面的第八种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话激活失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话激活失败。从而使得第二核心网设备获知第一RAN节点激活所述PDU会话失败。
结合第三方面的第二种可实施方式，在第三方面的第九种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话去激活失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话去激活失败。从而使得第二核心网设备获知第一RAN节点去激活所述PDU会话失败。
结合第三方面的第三种可实施方式，在第三方面的第十种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话更新失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话更新失败。从而使得第二核心网设备获知第一RAN节点修改所述PDU会话失败。
结合第三方面的第四种可实施方式，在第三方面的第十一种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话释放失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话释放失败。从而使得第二核心网设备获知第一RAN节点释放所述PDU会话失败。
结合第三方面的第五种可实施方式，在第三方面的第十二种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述第一下行信息传输失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述第一下行信息传输失败。从而使得第二核心网设备获知第一RAN节点传输第一下行信息失败。
结合第三方面，或第三方面的上述任一种可实施方式，在第三方面的第十三种可实施方式中，所述指示信息为失败原因值。从而使得第二核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第三方面的第十三种可实施方式，在第三方面的第十四种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程；或者，所述终端正在进行切换；或者，上下文转移；或者，所述终端在所述第一RAN节点不可达；或者，所述第一下行信息没有被传输。从而使得第二核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第三方面的第十四种可实施方式，在第三方面的第十五种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程，所述第二核心网设备根据所述第一消息，向所述第二RAN节点发送所述第一下行信息，包括：
所述第二核心网设备根据所述第一消息，在所述RRC连接恢复完成后向所述第二RAN节点发送所述第一下行信息；或者，所述第二核心网设备根据所述第一消息，在所述RRC连接恢复流程中的路径切换完成后向所述第二RAN节点发送所述第一下行信息。以使得第二核心网设备能够在获知所述RRC连接恢复完成后或RRC连接恢复流程中的路径切换完成之后才向第二RAN节点发送第二下行信息，从而第二RAN节点能够成功处理第二下行信息。
结合第三方面，或第三方面的上述任一种可实施方式，在第三方面的第十六种可实施方式中，所述方法还包括：所述第二核心网设备从所述第一RAN节点接收所述终端的当前位置信息。以使得第二核心网设备获知终端的当前位置信息，从而确定所述终端的当前位置位于所述第一下行信息的有效区域内，进而决定向第二RAN节点发送第一下行信息，使得第一下行信息能够被第二RAN节点成功处理，从而避免了将无效 的第一下行信息发给第二RAN节点所导致的处理失败。
第四方面，提供了一种通信方法，所述方法应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：第二核心网设备从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息；所述第二核心网设备从所述第一RAN节点接收第一消息；所述第二核心网设备根据所述第一消息，向所述第一核心网设备发送指示信息。其中，第一消息可以用于指示第一RAN节点对第一下行信息的处理失败。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法处理第一下行信息情况下，该方法通过所述第一RAN节点向第二核心网设备发送的第一消息，使得第二核心网设备向所述第一核心网设备发送指示信息，从而使得第一核心网设备获知所述第一下行信息处理失败。
结合第四方面，在第四方面的第一种可实施方式中，所述第一下行信息用于激活所述终端的PDU会话，所述PDU会话处于去激活态；所述第一消息用于指示所述PDU会话激活失败。使得第二核心网设备向所述第一核心网设备发送指示信息，进而使得第一核心网设备获知所述PDU会话激活失败。
结合第四方面，在第四方面的第二种可实施方式中，所述第一下行信息用于去激活所述终端的PDU会话，所述PDU会话处于激活态；所述第一消息用于指示所述PDU会话去激活失败。使得第二核心网设备向所述第一核心网设备发送指示信息，进而使得第一核心网设备获知所述PDU会话去激活失败。
结合第四方面，在第四方面的第三种可实施方式中，所述第一下行信息用于更新所述终端的PDU会话，所述PDU会话处于激活态；所述第一消息用于指示所述PDU会话更新失败。使得第二核心网设备向所述第一核心网设备发送指示信息，进而使得第一核心网设备获知所述PDU会话修改失败。
结合第四方面，在第四方面的第四种可实施方式中，所述第一下行信息用于释放所述终端的PDU会话，所述PDU会话处于激活态或非激活态；所述第一消息用于指示所述PDU会话释放失败。使得第二核心网设备向所述第一核心网设备发送指示信息，进而使得第一核心网设备获知所述PDU会话释放失败。
结合第四方面，在第四方面的第五种可实施方式中，所述第一下行信息为发往所述终端的下行信息；所述第一消息用于指示所述第一下行信息传输失败。使得第二核心网设备向所述第一核心网设备发送指示信息，进而使得第一核心网设备获知所述第一下行信息传输失败。
结合第四方面或第四方面的上述任一种可实施方式，在第四方面的第六种可实施方式中，所述第二核心网设备根据所述第一消息，向所述第一核心网设备发送指示信息，包括：所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息，所述第一下行信息针对所述第一下行信息的有效区域内的设备有效；当所述第二核心网设备根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端不位于所述有效区域内时，所述第二核心网设备根据所述第一消息，向所述第一核心网设备发送所述指示信息。以使得第二核心网设备确定所述终端的当前位置不位于所述第一下行信息的有效区域内，从而决定向第一核心网设备发送指示信 息，进而使得第一核心网设备生成对于所述终端的当前位置有效的第二下行信息，同时避免了第二核心网设备将无效的第一下行信息发给第二RAN节点所导致的处理失败。
结合第四方面或第四方面的上述任一种可实施方式，在第四方面的第七种可实施方式中，所述向所述第一RAN节点发送所述第一下行信息，包括：所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息，所述第一下行信息针对所述第一下行信息的有效区域内的设备有效；当所述终端在所述第二核心网设备上的状态为连接管理连接态，且所述第二核心网设备根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备向所述第一RAN节点发送所述第一下行信息。以使得第二核心网设备确定所述终端的上下文中的位置位于所述第一下行信息的有效区域内，从而决定向第一RAN节点发送第一下行信息，进而使得第一下行信息能够被第一RAN节点成功处理，从而避免了将无效的第一下行信息发给第一RAN节点所导致的处理失败。
结合第四方面的第一种可实施方式，在第四方面的第八种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话激活失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话激活失败。从而使得第二核心网设备获知第一RAN节点激活所述PDU会话失败。
结合第四方面的第二种可实施方式，在第四方面的第九种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话去激活失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话去激活失败。从而使得第二核心网设备获知第一RAN节点去激活所述PDU会话失败。
结合第四方面的第三种可实施方式，在第四方面的第十种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话更新失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话更新失败。从而使得第二核心网设备获知第一RAN节点修改所述PDU会话失败。
结合第四方面的第四种可实施方式，在第四方面的第十一种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述PDU会话释放失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述PDU会话释放失败。从而使得第二核心网设备获知第一RAN节点释放所述PDU会话失败。
结合第四方面的第五种可实施方式，在第四方面的第十二种可实施方式中，所述第一消息的消息类型或消息名称用于指示所述第一下行信息传输失败；或者，所述第一消息中包括指示信息，所述指示信息用于指示所述第一下行信息传输失败。从而使得第二核心网设备获知第一RAN节点传输第一下行信息失败。
结合第四方面的第八种至第十二种中任一种可实施方式，在第四方面的第十三种可实施方式中，所述指示信息为失败原因值。从而使得第二核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第四方面的第十三种可实施方式，在第四方面的第十四种可实施方式中，所述原因包括：所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程；或者，所述终端正在进行切换；或者，上下文转移；或者，所述终端在所述 第一RAN节点不可达；或者，所述第一下行信息没有被传输。从而使得第二核心网设备获知第一RAN节点处理第一下行信息失败的原因。
结合第四方面或第四方面的上述任一种可实施方式，在第四方面的第十五种可实施方式中，所述方法还包括：所述第二核心网设备从所述第一RAN节点接收所述终端的当前位置信息。以使得第二核心网设备获知终端的当前位置信息，从而确定所述终端的当前位置不位于所述第一下行信息的有效区域内，从而决定向第一核心网设备发送指示信息，进而使得第一核心网设备生成对于所述终端的当前位置有效的第二下行信息，同时避免了第二核心网设备将无效的第一下行信息发给第二RAN节点所导致的处理失败。
第五方面，提供了一种通信方法，所述方法应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：第二核心网设备获取第一下行信息；所述第二核心网设备向所述第一RAN节点发送位置请求消息，所述位置请求消息用于请求所述终端的当前位置信息；所述第二核心网设备从所述第一RAN节点接收所述终端的当前位置信息，和/或，所述第二核心网设备从所述第一RAN节点接收所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息；所述第二核心网设备向所述第二RAN节点发送所述第一下行信息；或者，所述第二核心网设备向所述第一核心网设备发送所述指示信息。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法处理第一下行信息情况下，该方法通过第二核心网设备接收来自第一RAN节点的信息或消息，触发第二核心网设备将第一下行信息发送给第二RAN节点，进而使得第一下行信息可以被第二RAN节点成功地理；或者触发第二核心网设备向所述第一核心网设备发送指示信息，从而使得第一核心网设备获知所述第一下行信息处理失败。
第六方面，提供了一种通信方法，所述方法应用于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：第一RAN节点从第二核心网设备接收位置请求消息，所述位置请求消息用于请求所述终端的当前位置信息；当所述终端的RRC连接状态为非激活态时，所述第一RAN节点根据所述位置请求消息，寻呼所述终端；所述第一RAN节点从所述第二RAN节点接收所述终端的上下文请求；所述第一RAN节点根据所述上下文请求向所述第二核心网设备发送所述终端从所述第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息，和/或，所述终端的当前位置信息。从而在由于终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围而导致第一RAN节点无法处理第一下行信息情况下，该方法通过第一RAN节点向所述第一核心网设备发送信息或消息，以使得第二核心网设备获知第一下行信息没有被第一RAN节点成功处理。
第七方面，提供了一种通信装置，该装置具有实现第一方面至第六方面提供的任意一种方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该装置可以以芯片的产品形态存在。
第八方面，提供了一种通信装置，该装置包括：存储器、处理器、至少一个通信 接口和通信总线；存储器用于存储计算机执行指令，处理器、存储器和至少一个通信接口通过通信总线连接，处理器执行存储器存储的计算机执行指令，以使该装置实现第一至第六任一方面提供的任意一种方法。该装置可以以芯片的产品形态存在。
第九方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第一至第六任一方面提供的任意一种方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第一至第六任一方面提供的任意一种方法。
第七方面至第十方面中任一种设计方式所带来的技术效果可参见第一方面至第六方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种5G网络的架构示意图；
图2为本申请实施例提供的一种UPF的服务区域的示意图；
图3为本申请实施例提供的一种通信装置的硬件结构示意图；
图4为本申请实施例提供的一种通信方法的流程示意图；
图5为本申请实施例提供的一种UPF的位置示意图；
图6为本申请实施例提供的一种路径切换示意图；
图7-图12分别为本申请实施例提供的一种通信方法的流程示意图；
图13为本申请实施例提供的一种通信装置的组成示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例的技术方案可以应用于各种数据处理的通信系统，例如：码分多址(code division multiple access，简称CDMA)、时分多址(time division multiple access，简称TDMA)、频分多址(frequency division multiple access，简称FDMA)、正交频分多址(orthogonal frequency-division multiple access，简称OFDMA)、单载波频分多址(single carrier FDMA，简称SC-FDMA)和其它系统等。术语“系统”可以和“网络”相互替换。CDMA系统可以实现例如通用无线陆地接入(universal terrestrial radio access，简称UTRA)、CDMA2000等无线技术。UTRA可以包括宽带CDMA(wideband CDMA，简称WCDMA)技术和其它CDMA变形的技术。CDMA2000可以覆盖过渡标准(interim standard，简称IS)2000(IS-2000)，IS-95和IS-856标准。TDMA系统可以实现例如全球移动通信系统(global system for mobile communication，简称GSM)等无线技术。OFDMA系统可以实现诸如演进通用无线陆地接入(evolved UTRA，简称E-UTRA)、超级移动宽带(ultra mobile broadband，简称UMB)、 IEEE 802.11(Wi-Fi)，IEEE 802.16(WiMAX)，IEEE 802.20，Flash OFDMA等无线技术。UTRA和E-UTRA是UMTS以及UMTS演进版本。3GPP在长期演进(long term evolution，简称LTE)和基于LTE演进的各种版本是使用E-UTRA的UMTS的新版本。5G通信系统、新空口(new radio，简称NR)是正在研究当中的下一代通信系统。此外，所述通信系统还可以适用于面向未来的通信技术，都适用本申请实施例提供的技术方案。
本申请实施例描述的系统架构是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。但是需要说明的是，本申请实施例提供的方法也可以应用于其他网络中，比如，可以应用在演进分组系统(evolved packet system，简称EPS)网络(即通常所说的第四代(4th generation，简称4G)网络)中。相应的，当本申请实施例提供的方法应用在EPS网络中时，执行本申请实施例提供的方法的网络节点替换为EPS网络中的具备相同或相应功能的网络节点即可。
示例性的，本申请实施例提供的方法可以应用于5G网络中，参见图1，该5G网络可以包括下述多个网络功能(network functions，简称NF)实体：鉴权服务器功能(authentication server function，简称AUSF)实体、AMF实体、数据网络(data network，简称DN)、统一数据管理(unified data management，简称UDM)实体、策略控制功能(policy control function，简称PCF)实体、(无线)接入网((radio)access network，简称(R)AN)实体、UPF实体、用户设备(user equipment，简称UE)、应用功能(application function，简称AF)实体、会话管理功能(session management function，简称SMF)实体等。
可以理解的是，图1仅为示例性架构图，除图1所示功能实体之外，该5G网络架构还可以包括其他功能实体，例如，在AF实体和PCF实体之间还可能包括网络开放功能(network exposure function，简称NEF)实体。其中，实体也可以称为网元或设备等。
图1中的UDM实体、AUSF实体、PCF实体、AMF实体和SMF实体也可以统称为控制面功能(control plane function，简称CPF)实体，本申请实施例对此不作具体限定。
具体的，(R)AN是由多个5G-RAN节点组成的网络，实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能。5G-RAN节点通过用户面接口N3和UPF相连，用于传送终端的数据。5G-RAN节点通过控制面接口N2和AMF建立控制面信令连接，用于实现无线接入承载控制等功能。AMF主要负责终端的认证，终端移动性管理，网络切片(network slice)选择，SMF选择等功能。AMF作为N1和N2信令连接的锚点并为SMF提供N1/N2接口会话管理(session management，简称SM)消息的路由；维护和管理终端的状态信息。SMF主要负责终端会话管理的所有控制面功能，包括UPF选择，网络互连协议(internet protocol，简称IP)地址分配，会话的服务质量(quality of service，简称QoS)管理，从PCF获取策略与计费控制(policy and charging control，简称PCC)策略等。UPF作为分组数据单元(packet data unit，简称PDU)会话连接的锚定点，负责对终端的数据报文过滤、数据传输/转发、速率控制、生成计费信息等。
需要说明的是，图1中的(R)AN实体、AMF实体、SMF实体、AUSF实体、UDM实体、UPF实体和PCF实体等仅是一个名字，名字对实体本身不构成限定。在5G网络以及未来其它的网络中，这些实体所对应的网元或设备也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM实体还有可能被替换为用户归属服务器(home subscriber server，简称HSS)或者用户签约数据库(user subscription database，简称USD)或者数据库实体，等等，在此进行统一说明，以下不再赘述。
本申请实施例提供的方法还可以应用在5G网络的网络切片中，网络切片技术是将一个物理网络切割成多个虚拟的端到端的网络，每个虚拟网络之间，包括网络内的设备、接入技术、传输路径和核心网，是逻辑独立的。每个网络切片由一个独立的网络功能或功能组合实例化构成，具备不同的功能特点，面向不同的需求和服务。网络切片的分离使得不同用户、用户组可以根据其不同应用场景和需求灵活、动态的定义和定制网络能力，而相互间不影响。
一个网络切片包括CPF实体和UPF实体。其中，CPF实体主要完成终端的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能，以及用户面传输路径的建立、释放和更改等会话管理功能，UPF实体主要完成用户面数据的路由转发等功能。
可选的，本申请实施例中所涉及到的终端(terminal)还可以称为UE(下文中提到的终端和UE为同一设备)。具体可以为包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，简称PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，简称WLL)台、机器类型通信(machine type communication，简称MTC)终端、移动台(mobile station，简称MS)，终端设备(terminal device)等。
为了方便理解本申请实施例的技术方案，首先将与本申请相关的内容作简要介绍。
PDU会话：在UPF中会保存一个PDU会话的一个或多个业务流模版，PDU会话用于承载与PDU会话的业务流模版匹配的下行数据。
也就是说，在UPF接收到下行数据后，会将下行数据和业务流模版进行匹配，与下行数据匹配成功的业务流模版对应的PDU会话即承载该下行数据的PDU会话(假设为PDU会话1)。若UPF确定PDU会话1未激活，则需要将PDU会话1激活以发送该下行数据。参见表1，此时，即使PDU会话2和PDU会话3是激活的，由于PDU会话2和PDU会话3对应的业务流模版与下行数据不匹配，因此，UPF也无法采用PDU会话2或PDU会话3承载该下行数据。
其中，为一个PDU会话服务的SMF只有一个，为不同PDU会话服务的SMF可能相同也可能不同。例如，参见表1，为PDU会话1服务的SMF为SMF1，为PDU会话2和PDU会话3服务的SMF为SMF2。
表1
Figure PCTCN2019081548-appb-000001
Figure PCTCN2019081548-appb-000002
UPF的服务区域：UPF为自己的服务区域内的RAN节点提供服务(或者说，UPF为自己的服务区域内的UE提供服务；或者说，UPF为连接到自己的服务区域内的RAN节点的UE提供服务)。位于一个UPF的服务区域内的RAN节点可以与该UPF建立数据通道，从而为终端提供服务。
如图2所示，UPF存在服务区域(例如，图2中的UPF1的服务区域为服务区域1，UPF2的服务区域为服务区域2)。示例性的，当终端移出了UPF1的服务区域时，由于UPF1的服务区域内的、且为终端服务的RAN节点无法与UPF1建立数据通道，因此，UPF1无法再为终端提供服务。此时，若当前为终端服务的RAN节点为RAN2节点，SMF会为RAN2节点选择一个UPF(记为UPF2)，从而使得RAN2节点与UPF2建立数据通道为终端服务。
由于AMF为终端分配跟踪区(registration area，简称RA)时不会考虑UPF的服务区域。当终端在RA内移动时，终端可能已经移出了UPF的服务区域。在5G网络中，SMF为了获取到终端是否移出了UPF1的服务区域的信息，会向AMF订阅“感兴趣的区域(area of interest)”(对应UPF1的服务区域1)，AMF如果确定终端移出了服务区域1，则将该信息通知SMF，以便SMF为RAN2节点选择UPF。
另外，现有技术中AMF根据存储的终端的上下文中的位置信息判断终端位于下行信息的有效区域后，向RAN1节点发送下行信息，RAN1节点在接收到下行信息后，如何处理下行信息，目前现有技术中也没有相应的处理机制。
RRC连接状态：可以包括空闲态，连接态，非激活态。
终端的RRC连接状态为空闲态可以指：终端与AMF之间未建立非接入层(non-access stratum，简称NAS)信令连接。
终端的RRC连接状态为连接态可以指：终端与AMF之间已建立NAS信令连接、且与RAN已建立RRC连接。
终端的RRC连接状态为非激活态可以指：终端与AMF之间已建立NAS信令连接、但未与RAN建立RRC连接。
对于处于连接态或非激活态的终端，AMF上存储的终端的状态为连接管理连接态。并且，AMF上还保存终端的上下文，上下文中包括终端的位置信息，该终端的位置信息为终端初始接入网络的过程(即注册流程或服务请求流程)中上报的或终端在进行小区切换过程中由基站上报的终端的位置信息。终端的位置信息可以为为终端服务的RAN节点的标识、终端所处小区的演进型通用陆地无线接入网(evolved universal terrestrial radio access network，简称E-UTRAN)小区全局标识符(E-UTRAN cell global identifier，简称ECGI)，或终端所处的TA的TA标识(TA identity，简称TAI)或TA码(TA code，简称TAC)。
需要说明的是，当终端的RRC连接状态为非激活态时，AMF中也有可能存储终端的具体的RRC连接状态(比如，非激活态)。
在5G无线通信系统中，对于RRC连接状态为非激活态的终端，AMF上存储的终端的状态为连接管理连接态，AMF认为保存的终端的上下文中的位置信息是终端的当 前位置信息。在终端未发生小区切换的情况下，若终端从RAN1节点(在UPF1的服务区域)的覆盖范围移动到RAN2节点(不在UPF1的服务区域)的覆盖范围后，AMF上保存的终端的上下文中的位置信息仍然为指示终端位于RAN1节点的覆盖范围内的信息。但实际上终端已经移动到RAN2节点的覆盖范围内。若终端的下行信息的有效区域与UPF的服务区域一致，则AMF根据保存的终端的上下文中的位置信息判断终端位于下行信息的有效区域内的判断结果是错误的。该情况下，若AMF将终端的下行信息发给RAN1节点，会导致该下行信息处理失败。
为了解决该问题，本申请实施例提供了一种通信装置，图3所示为本申请实施例提供的通信装置的硬件结构示意图，该通信装置可以为下文中的第一核心网设备、第二核心网设备、第一RAN节点或第二RAN节点。该通信装置30包括至少一个处理器301，通信总线302，存储器303以及至少一个通信接口304。
处理器301可以是一个或多个通用中央处理器(central processing unit，简称CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，简称ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线302，用于在上述组件之间通信，以传送信息。
通信接口304，用于与其他设备或通信网络通信，可以使用任何收发器一类的装置，如以太网、RAN设备、无线局域网(wireless local area networks，简称WLAN)等。
存储器303，用于存储执行本申请方案的计算机执行指令，并由处理器301来控制执行。处理器301用于执行存储器303中存储的计算机执行指令，从而实现本申请下述实施例提供的方法。存储器303可以是只读存储器(read-only memory，简称ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，简称RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，简称EEPROM)、只读光盘(compact disc read-only memory，简称CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器303可以是独立存在，通过通信总线302与处理器301相连接。存储器303也可以和处理器301集成在一起。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
作为一种实施例，通信装置30可以包括多个处理器，例如图3中的处理器301和处理器308。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
作为一种实施例，通信装置30还可以包括输出设备305和输入设备306。输出设备305和处理器301通信，可以以多种方式来显示信息。输入设备306和处理器301 通信，可以以多种方式接收用户的输入。
为了更好的理解下文中提供的实施例，在此对下文中的第一下行信息进行说明，具体可参见表2。
表2
Figure PCTCN2019081548-appb-000003
表2中的SMSF为短消息服务功能(short messaging service function)的简称。SMS为短消息服务(short messaging service)的简称。
表2中的序号1，7，8，9和10对应的第一下行信息可以包含在AMF提供的N1接口消息N2接口消息传输消息(Namf_Communication_N1N2MessageTransfer)中传输。序号2对应的第一下行信息可以包含在PCF提供的接入和移动性策略控制更新通知消息(Npcf_AMPolicyControl UpdateNotify)中传输。序号5对应的第一下行信息可以包含在UDM提供的签约数据管理通知消息(Nudm_SDM_Notification)中传输。序号6对应的第一下行信息可以包含在NEF提供的触发传输请求消息 (Nnef_Trigger_Deliveryrequest)中传输。其中，AM为接入和移动性(core access and mobility)的简称，SDM为签约数据管理(subscription data management)的简称。
实施例一
本申请实施例提供了一种通信方法，应用于RRC连接状态为非激活态的UE从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，如图4所示，该方法包括：
401、第一核心网设备向第一RAN节点发送第一下行信息。
其中，第一下行信息可以为第一核心网设备从其他网络设备接收到的下行信息，也可以为第一核心网设备生成的下行信息。示例性的，第一核心网设备可以为SMSF、PCF、UDM、NEF、AMF、SMF等，其他网络设备可以为AF。
示例性的，第一下行信息由第一核心网设备生成时，若第一下行信息为与UE的PDU会话相关的信息(例如，用于激活/去激活/修改/释放UE的PDU会话的下行信息)时，第一核心网设备可以为SMF。当第一下行信息为向UE发送的短消息时，第一核心网设备可以为SMSF。当第一下行信息为用于更新UE上的接入和移动性管理参数的信息时，第一核心网设备可以为AMF。其他情况可参见表2，在此不再一一罗列。
402、第一RAN节点从第一核心网设备接收UE的第一下行信息。
403、当UE的RRC连接状态为非激活态时，第一RAN节点根据第一下行信息，寻呼UE。
在一个示例中，第一RAN节点中存储的UE的上下文中包括RRC连接状态。当该RRC连接状态为连接态时，UE在第一RAN节点的覆盖范围内、且与第一RAN节点之间可以进行信息交互。因此，第一RAN节点在接收到第一下行信息时，不寻呼UE。例如，当UE的RRC连接状态为连接态时，若第一RAN节点接收到用于激活PDU会话的第一下行信息，可以直接与UE通过RRC信令交互以建立PDU会话的空口DRB数据通道，而不需要寻呼UE。当UE的RRC连接状态为非激活态时，第一RAN节点寻呼UE。
404、第一RAN节点从第二RAN节点接收UE的上下文请求。
其中，第一RAN节点在寻呼UE时，也会通知其他RAN节点(包括第二RAN节点)寻呼UE。RAN节点可以通过广播方式发送寻呼(Paging)消息以寻呼UE。
在一个示例中，由于UE此时已经处于第二RAN节点的覆盖范围内，因此，UE向第二RAN节点发起RRC连接恢复请求，以响应第二RAN节点广播的paging消息，第二RAN节点在接收到UE的RRC连接恢复请求后，向第一RAN节点发送上下文请求，上下文请求用于请求获取UE的上下文，以便恢复UE的RRC连接。
405、第一RAN节点根据上下文请求，向第一核心网设备发送指示信息。
可选的，指示信息可以指示第一下行信息处理失败。或者说，指示信息用于指示第一核心网设备向第二RAN节点发送第二下行信息。
406、第一核心网设备从第一RAN节点接收指示信息。
407、第一核心网设备根据指示信息，向第二RAN节点发送第二下行信息。
其中，第一下行信息和第二下行信息可以部分或全部相同。
其中，第一下行信息、第二下行信息以及指示信息的作用可以为以下几种情况中 的任意一种情况：
情况1、第一下行信息用于第一RAN节点激活UE的PDU会话，该PDU会话处于去激活态；指示信息用于指示该PDU会话激活失败；第二下行信息用于第二RAN节点激活该PDU会话。该第一下行信息为表2中的序号8对应的第一下行信息。
其中，第一下行信息可以为N2接口SM信息(N2 SM information)。N2接口SM信息可以为QoS文件(QoS profile(s)，也可以称为QoS配置信息)和核心网N3接口隧道信息(CN N3 tunnel info，也可以记为CN tunnel info)。其中，CN N3 tunnel info可以用于第一RAN节点建立和第一UPF之间的N3接口数据通道。其中，第一UPF为接收到UE的该PDU会话的下行数据且向第一核心网设备发送数据通知的UPF，数据通知用于向第一核心网设备通知有UE的下行数据需要发送。
情况2、第一下行信息用于第一RAN节点去激活UE的PDU会话，该PDU会话处于激活态；指示信息用于指示该PDU会话去激活失败；第二下行信息用于第二RAN节点去激活该PDU会话。该情况下，第二下行信息与第一下行信息可以相同。
第一下行信息可以为表2中的序号9对应的第一下行信息。
示例性的，第一下行信息可以为N2接口SM信息。N2接口SM信息可以为PDU会话标识。
情况3、第一下行信息用于第一RAN节点更新UE的PDU会话，该PDU会话处于激活态；指示信息用于指示该PDU会话更新失败；第二下行信息用于第二RAN节点更新该PDU会话。该情况下，第二下行信息与第一下行信息可以相同。
第一下行信息可以为表2中的序号10对应的第一下行信息。
第一下行信息可以包括：N2接口SM信息和N1接口SM容器。N2接口SM信息用于RAN节点更新该PDU会话的相关参数。N2接口SM信息可以为QoS profile(s)。N1接口SM容器用于UE更新该PDU会话的相关参数。N1接口SM容器可以为QoS profile(s)。
情况4、第一下行信息用于第一RAN节点释放UE的PDU会话，该PDU会话处于激活态或非激活态；指示信息用于指示该PDU会话释放失败；第二下行信息用于第二RAN节点释放该PDU会话。该情况下，第二下行信息与第一下行信息可以相同。
第一下行信息可以为表2中的序号11对应的第一下行信息。
示例性的，第一下行信息可以包括N2资源释放请求(N2 Resource Release request)和/或N1接口SM容器。N2资源释放请求中包括用于第一RAN节点释放该PDU会话的相关参数，N1接口SM容器中包括用于UE释放该PDU会话的相关参数。N2资源释放请求中和N1接口SM容器中均包括PDU会话标识。若该PDU会话处于激活态，第一下行信息包括N2资源释放请求和N1接口SM容器；若该PDU会话处于非激活态，第一下行信息包括N1接口SM容器。
情况5、第一下行信息为发往UE的下行信息；指示信息用于指示第一下行信息传输失败，第二下行信息与第一下行信息相同。
第一下行信息可以为表2中的序号1-序号7中的任意一个序号对应的第一下行信息。在情况1-情况4中的任一种情况中：
第一核心网设备可以为SMF。其中，第一核心网设备可以直接向第一RAN节点 发送第一下行信息。第一核心网设备也可以向其他设备发送第一下行信息，通过其他设备将第一下行信息转发至第一RAN节点。其他设备可以为控制面网元，例如，AMF。示例性的，第一核心网设备为SMF时，SMF可以向AMF发送第一下行信息，通过AMF将第一下行信息转发至第一RAN节点。
当第一核心网设备直接向第一RAN节点发送第一下行信息时，第一RAN节点可以从第一核心网设备接收第一下行信息。当第一核心网设备向其他设备发送第一下行信息，通过其他设备将第一下行信息转发至第一RAN节点时，第一RAN节点可以从其他设备接收第一下行信息。
在情况5中：第一核心网设备可以为生成第一下行信息的设备，也可以为转发第一下行信息的设备。示例性的，当第一下行信息为发往UE的短消息时，第一核心网设备可以为SMSF(生成第一下行信息的设备)或AMF(转发第一下行信息的设备)。
下面结合上述五种情况，分别以不同的实施场景来对上述实施例进行进一步地说明，具体如下。
可选地，在上述实施例的第一种实施场景下，第一下行信息、第二下行信息以及指示信息为上述情况1，在第一种实施场景下：
步骤405的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不激活UE的PDU会话(例如，不触发为UE的该PDU会话建立UE和第一RAN节点之间的空口DRB的数据通道，不触发为UE的该PDU会话建立第一RAN节点和第一UPF之间的N3接口的数据通道)，第一RAN节点向第一核心网设备发送指示信息。
步骤407的一种示例性的实现方式，第一核心网设备可以根据指示信息确定第一RAN节点激活UE的PDU会话失败，则向当前为UE服务的第二RAN节点发送第二下行信息。
可选的，上述方法还包括：当第一核心网设备根据UE的当前位置信息确定UE不位于第一下行信息的有效区域内时，第一核心网设备根据UE的当前位置信息生成第二下行信息。或者，当第一核心网设备根据UE的当前位置信息确定UE位于第一下行信息的有效区域内时，第二下行信息与第一下行信息相同。
第一核心网设备可以将UE的当前位置信息与第一下行信息的有效区域进行比对，确定UE当前是否位于第一下行信息的有效区域内。第一下行信息针对第一下行信息的有效区域内的设备有效。
其中，第一下行信息包含与第一UPF对应的CN N3 tunnel info，因此，第一核心网设备可以将第一下行信息的有效区域设置为第一UPF的服务区域。即CN N3 tunnel info只对位于第一UPF的服务区域内的UE有效(或者说，CN N3 tunnel info只对位于第一UPF的服务区域内的RAN有效；或者，CN N3 tunnel info只对通过位于第一UPF的服务区域内的RAN连接到网络的UE有效)。当然，第一核心网设备还可以根据其它信息(比如第一核心网设备的服务范围，第一UPF的负载信息，当前为UE服务的基站的负载信息等)来设置第一下行信息的有效区域，下文中以第一下行信息的有效区域与第一UPF的服务区域相同为例对本申请实施例提供的方法作示例性说明。
当UE当前不位于第一下行信息的有效区域内(或者说，第二RAN节点不位于第一下行信息的有效区域内)时，意味着UE已经离开了第一UPF的服务区域，第一UPF无法再为UE服务。因此，第一核心网设备可以根据UE的当前位置信息确定当前为UE服务的RAN节点(即第二RAN节点)，第一核心网设备为第二RAN节点选择UPF(记为第二UPF)。在UE当前不位于第一下行信息的有效区域内的情况下，步骤407的一种示例性的实现方式，第一核心网设备根据指示信息确定第一RAN节点激活UE的PDU会话失败，并将与第二UPF对应的CN N3 tunnel info包含在第二下行信息中向第二RAN节点发送，从而使得第二RAN节点激活UE的PDU会话。
第二UPF为SMF选择的中间UPF(intermediate UPF)，用于与第二RAN节点连接，为该PDU会话建立N3接口的数据通道。示例性的，参见图5中的(a)，第一RAN节点与第一UPF连接。参见图5中的(b)、(c)和(d)，第二RAN节点与第二UPF连接。具体的，第二UPF可以直接与锚点UPF连接(参见图5中的(b))，也可以通过第一UPF与锚点UPF连接(参见图5中的(d))(该情况下，第一UPF与第二UPF为不同的UPF)。第二UPF也可以为锚点UPF(参见图5中的(c))。
当UE当前位于第一下行信息的有效区域内(或者说，第二RAN节点位于第一下行信息的有效区域内)时，第二RAN节点和第一RAN节点都可以为UE的PDU会话建立到同一个UPF(即上文中的第一UPF)的N3接口的数据通道，因此，第一下行信息与第二下行信息可以为相同的信息。
在步骤407之后，第二RAN节点根据接收到的第二下行信息激活UE的PDU会话。第二RAN节点激活UE的PDU会话具体可以包括：第二RAN节点为UE的PDU会话建立UE和第二UPF之间的数据通道，UE和第二UPF之间的数据通道包括：UE和第二RAN节点之间的空口DRB的数据通道，以及，第二RAN节点和第二UPF之间的N3接口的数据通道。
在第一种实施场景下，当第一下行信息用于激活UE的PDU会话时，若第一核心网设备接收到指示信息，则说明第一RAN节点激活PDU会话失败。第一核心网设备可以向当前为UE服务的第二RAN节点发送第二下行信息，以使得第二RAN节点根据第二下行信息激活UE的PDU会话。由于第二RAN节点为当前为UE服务的RAN节点，因此，第二RAN节点能够成功激活UE的PDU会话。
可选地，在上述实施例的第二种实施场景下，第一下行信息、第二下行信息以及指示信息为上述情况2，在第二种实施场景下：
步骤405的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不对该PDU会话去激活，而是向第一核心网设备发送指示信息。
步骤407的一种示例性的实现方式，第一核心网设备可以根据指示信息确定第一RAN节点去激活UE的PDU会话失败，则向当前为UE服务的第二RAN节点发送第二下行信息。由于UE当前位于第二RAN节点的覆盖范围内，因此，第二RAN节点可以成功去激活UE的PDU会话。
第一核心网设备可以自己确定去激活的PDU会话。例如，若一个PDU会话是为本地接入数据网(local access data network，简称LADN)建立的PDU会话，第一核 心网设备发现UE移出了该LADN的服务范围，则确定去激活该PDU会话。再例如，UPF通知第一核心网设备一个PDU会话在一定时间内没有数据传输，第一核心网设备确定去激活该PDU会话。
在步骤407之后，第二RAN节点根据接收到的第二下行信息去激活UE的PDU会话。第二RAN节点去激活UE的PDU会话具体可以包括：第二RAN节点根据第二下行信息中的PDU会话标识，释放为该PDU会话标识对应的PDU会话准备的资源。例如，第二RAN节点可以通过与UE进行RRC信令交互(例如RRC连接重配置(RRC connection reconfiguration)，释放为该PDU会话标识对应的PDU会话准备的DRB资源。第二RAN节点还可以释放该PDU会话的N3接口的数据通道资源(即释放该PDU会话的AN tunnel info和CN tunnel info)。
第二种实施场景下，当第一下行信息用于去激活UE的PDU会话时，若第一核心网设备接收到指示信息，第一核心网设备确定第一RAN节点去激活PDU会话失败。第一核心网设备向当前为UE服务的第二RAN节点发送第二下行信息，以使得第二RAN节点根据第二下行信息去激活UE的PDU会话。由于第二RAN节点为当前为UE服务的RAN节点，因此，第二RAN节点能够成功去激活UE的PDU会话。
可选地，在上述实施例的第三种实施场景下，第一下行信息、第二下行信息以及指示信息为上述情况3，在第三种实施场景下：
步骤405的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不更新该PDU会话，而是向第一核心网设备发送指示信息。
步骤407的一种示例性的实现方式，第一核心网设备可以根据指示信息确定第一RAN节点更新UE的PDU会话失败，则向当前为UE服务的第二RAN节点发送第二下行信息。由于UE当前位于第二RAN节点的覆盖范围内，因此，第二RAN节点可以成功更新UE的PDU会话。
在步骤407之后，第二RAN节点根据接收到的第二下行信息更新UE的PDU会话。第二RAN节点更新UE的PDU会话具体可以包括以下过程中的至少一个过程：根据N2接口SM信息中的QoS profile(s)，更新第二RAN节点存储的该PDU会话的QoS Profile(s)；向UE发送N1 SM container；根据N2接口SM信息中的QoS profile(s)，与UE进行RRC信令(例如RRC重配置)交互重新协商该PDU会话对应的DRB信息，并根据协商结果更新该PDU会话对应的DRB信息。
第三种实施场景下，当第一下行信息用于更新UE的PDU会话时，若第一核心网设备接收到指示信息，第一核心网设备确定第一RAN节点更新PDU会话失败。第一核心网设备向当前为UE服务的第二RAN节点发送第二下行信息，以使得第二RAN节点根据第二下行信息更新UE的PDU会话。由于第二RAN节点为当前为UE服务的RAN节点，因此，第二RAN节点能够成功更新UE的PDU会话。
可选地，在上述实施例的第四种实施场景下，第一下行信息、第二下行信息以及指示信息为上述情况4，在第四种实施场景下：
步骤405的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN 节点不释放该PDU会话，而是向第一核心网设备发送指示信息。
步骤407的一种示例性的实现方式，第一核心网设备可以根据指示信息确定第一RAN节点释放UE的PDU会话失败，第一核心网设备向当前为UE服务的第二RAN节点发送第二下行信息。由于UE当前位于第二RAN节点的覆盖范围内，因此，第二RAN节点可以成功释放UE的PDU会话。
在步骤407之后，第二RAN节点根据接收到的第二下行信息释放UE的PDU会话。第二RAN节点释放UE的PDU会话具体可以包括：第二RAN节点根据N2资源释放请求中的PDU会话标识，释放为该PDU会话标识对应的PDU会话准备的资源。例如，第二RAN节点可以通过与UE进行RRC信令(例如，RRC重配置)交互，释放为该PDU会话标识对应的PDU会话准备的DRB资源。第二RAN节点还可以释放该PDU会话的N3接口的数据通道资源(即释放PDU会话的AN tunnel info和CN tunnel info)；向UE发送N1 SM container。
第四种实施场景下，当第一下行信息用于释放UE的PDU会话时，若第一核心网设备接收到指示信息，第一核心网设备确定第一RAN节点释放PDU会话失败。第一核心网设备向当前为UE服务的第二RAN节点发送第二下行信息，以使得第二RAN节点根据第二下行信息释放UE的PDU会话。由于第二RAN节点为当前为UE服务的RAN节点，因此，第二RAN节点能够成功释放UE的PDU会话。
可选地，在上述实施例的第五种实施场景下，第一下行信息、第二下行信息以及指示信息为上述情况5，在第五种实施场景下：
步骤405的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE当前位于第二RAN节点的覆盖范围内，第一RAN节点无法成功向UE发送第一下行信息。第一RAN节点向第一核心网设备发送指示信息。
第一核心网设备接收到指示信息后，可以确定第一下行信息发送失败，由于UE当前位于第二RAN节点的覆盖范围内。因此，第一核心网设备向第二RAN节点发送第一下行信息，以使得第二RAN节点将第一下行信息向UE发送。
可选的，当第一核心网设备为AMF时，第一核心网设备可以在确定存储的UE的RRC连接状态为连接管理连接态的情况下，执行步骤401。第一核心网设备也可以在确定存储的UE的RRC连接状态为连接管理连接态，且存储的UE的上下文中的位置信息指示UE是在第一RAN节点的覆盖范围的情况下，执行步骤401。
第一下行信息也可能存在有效区域，该情况下，若第一核心网设备根据UE的当前位置信息确定UE位于第一下行信息的有效区域时，第一核心网设备执行步骤407。若第一核心网设备根据UE的当前位置信息确定UE不位于第一下行信息的有效区域时，第一核心网设备丢弃第一下行信息。该描述同样适用于实施例二和实施例三的情况5中，实施例二和实施例三中不再进行赘述。
第五种实施场景下，第一核心网设备在向第一RAN节点发送第一下行信息后，若接收到第一RAN节点反馈的指示信息，说明第一RAN节点向UE发送第一下行信息失败。则第一核心网设备将第一下行信息向当前为UE服务的第二RAN节点发送，以使得第二RAN节点将第一下行信息向UE发送，由于此时UE位于第二RAN节点的覆盖范围内，则第二RAN节点能够成功发送第一下行信息。
在上述五种实施场景中：
可选的，上述方法还可以包括：第一RAN节点向第一核心网设备发送UE的当前位置信息，第一核心网设备从第一RAN节点接收UE的当前位置信息。第一核心网设备可以根据UE的当前位置信息确定当前为UE服务的RAN节点(即第二RAN节点)。UE的当前位置信息可以为当前为UE服务的RAN节点的标识，UE当前所处小区的ECGI，或UE当前所处的TA的TAI或TAC等。
可选的，指示信息为失败原因值(或称为原因值)。
可选的，原因包括：UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程。进一步的，原因包括：UE从第二RAN节点发起RRC连接恢复流程，该情况下，指示信息中可以包括第二RAN节点的标识。
原因还可以包括：UE正在进行切换；或者，上下文转移；或者，UE在第一RAN节点不可达；或者，第一下行信息没有传输。
一种可能的实现方式，当原因包括：UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程时，步骤407在具体实现时，可以在以下两种情况下执行：
情况(1)、在RRC连接恢复流程中的路径切换完成的情况下
该情况下，步骤407在具体实现时可以包括：第一核心网设备根据指示信息，在RRC连接恢复流程中的路径切换完成后向第二RAN节点发送第二下行信息。
其中，路径切换是指将UE的第一RAN节点上与核心网的控制面信令的传输路径和用户面数据的传输路径切换至第二RAN节点上。其中，参见图6，若第一RAN节点为RAN1，第二RAN节点为RAN2，第一UPF为UPF1，第二UPF为UPF2。则路径切换包括两部分，一部分是将RAN1和AMF之间的用于传输UE的控制面信令的传输路径切换至RAN2和AMF之间，另一部分是将RAN1和UPF1之间的用于传输UE的用户面数据的传输路径切换至RAN2和UPF2之间。
该情况下，上述方法还可以包括：第一核心网设备向第二核心网设备发送订阅请求消息，订阅请求消息用于请求第二核心网设备在RRC连接恢复流程中的路径切换完成后向第一核心网设备发送通知消息，通知消息用于通知路径切换完成；第二核心网设备从第一核心网设备接收订阅请求；第二核心网设备在RRC连接恢复流程中的路径切换完成后向第一核心网设备发送通知消息。示例性的，第二核心网设备可以在发送N2接口路径切换请求应答消息(可参见步骤914)后，确定RRC连接恢复完成或RRC连接恢复流程中的路径切换完成。
情况(2)、在RRC连接恢复完成的情况下
该情况下，步骤407在具体实现时可以包括：第一核心网设备根据指示信息，在RRC连接恢复完成后向第二RAN节点发送第二下行信息。
由于RRC连接恢复流程中包括路径切换过程，因此，第一核心网设备也可以直接在RRC连接恢复完成后向第二RAN节点发送第二下行信息。
该情况下，第一核心网设备向第二核心网设备发送订阅请求消息，订阅请求消息用于请求第二核心网设备在RRC连接恢复流程完成后向第一核心网设备发送通知消息，通知消息用于通知RRC连接恢复完成；第二核心网设备从第一核心网设备接收订阅请求；第二核心网设备在RRC连接恢复完成后向第一核心网设备发送通知消息。
上述两种情况，第一核心网设备均在路径切换完成后向第二RAN节点发送第二下行信息，可以保证第二RAN节点正确接收到第二下行信息。可以理解的是，若第一核心网设备在路径切换完成前向第二RAN节点发送第二下行信息，AMF向第二RAN节点发送的第二下行信息要不发送失败，要不仍然会发送到与自己连接的第一RAN节点上。
另一种可能的实现方式，第一核心网设备可以在接收到指示信息后的预设时间(也可以称为预设时间段)之后，向第二RAN节点发送第二下行信息。可选的，预设时间可以通过保护定时器(guard timer)设置。该情况下，步骤407的一种示例性的实现方式，第一核心网设备根据指示信息，启动定时器，并在定时器到期后向第二RAN节点发送第二下行信息。定时器所预定的时长即预设时间。示例性的，预设时间可以设置为UE的RRC连接恢复流程执行完成所需要的时间。
实施例二
实施例一中的第一核心网设备和第一RAN节点之间传输的信息也可以被第二核心网设备感知。该情况下，本申请实施例还提供了两种通信方法，应用于RRC连接状态为非激活态的UE从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。如图7所示，图7中包括两个方案，第一个方案包括步骤701-707和708a，第二个方案包括步骤701-707和708b。一个方案为一种通信方法。具体包括：
701、第一核心网设备向第二核心网设备发送第一下行信息。
其中，第一核心网设备中的第一下行信息可以为第一核心网设备从其他核心网设备接收到的下行信息，也可以为第一核心网设备生成的下行信息。第一下行信息为UE的下行信息。
示例性的，当第一下行信息为与UE的PDU会话相关的信息时，第一核心网设备可以为SMF，第二核心网设备可以为AMF。当第一下行信息为向UE发送的短消息时，第一核心网设备可以为SMSF，第二核心网设备可以为AMF。其他情况可参见表2，在此不再一一罗列。
702、第二核心网设备从第一核心网设备接收第一下行信息，并向第一RAN节点发送第一下行信息。
703、第一RAN节点从第二核心网设备接收UE的第一下行信息。
704、当UE的RRC连接状态为非激活态时，第一RAN节点根据第一下行信息，寻呼UE。
与步骤704相关的描述可以参见步骤403，在此不再赘述。
705、第一RAN节点从第二RAN节点接收UE的上下文请求。
与步骤705相关的描述可以参见步骤404，在此不再赘述。
706、第一RAN节点根据上下文请求向第二核心网设备发送第一消息。
可选的，该第一消息可以指示第一下行信息处理失败。
707、第二核心网设备从第一RAN节点接收第一消息。
708a、第二核心网设备根据第一消息，向第二RAN节点发送第一下行信息。
可选的，上述方法还可以包括：第一RAN节点向第二核心网设备发送UE的当前位置信息，第二核心网设备从第一RAN节点接收UE的当前位置信息。第二核心网设 备可以根据UE的当前位置信息确定当前为UE服务的RAN节点(即第二RAN节点)，并根据第一消息，向第二RAN节点发送第一下行信息。UE的当前位置信息可以为当前为UE服务的RAN节点的标识，UE当前所处小区的ECGI，或UE当前所处的TA的TAI或TAC等。
708b、第二核心网设备根据第一消息，向第一核心网设备发送指示信息。
其中，第一下行信息、第二下行信息以及第一消息的作用可以为以下情况1-5中的任意一种情况：
情况1、第一下行信息用于第一RAN节点激活UE的PDU会话，PDU会话处于去激活态；第一消息用于指示PDU会话激活失败。
关于第一下行信息以及第二RAN节点如何激活PDU会话的相关描述可以参见实施例一中的情况1部分的相应描述，在此不再赘述。
在情况1下，该实施例中：
该实施例中可以通过第一消息的消息类型或消息名称指示PDU会话激活失败，比如，当消息类型为失败消息或拒绝消息时，该第一消息可以用于指示PDU会话激活失败。该实施例中也可以通过在第一消息中添加一个指示信息指示PDU会话激活失败，关于该指示信息的相关的描述可参见下文中的描述。第二核心网设备可以根据该第一消息确定第一RAN节点激活UE的PDU会话失败。
步骤706的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不激活UE的PDU会话(例如，不触发为UE的该PDU会话建立UE和第一RAN节点之间的空口DRB的数据通道，不触发为UE的该PDU会话建立第一RAN节点和第一UPF之间的N3接口的数据通道)，而向第二核心网设备发送第一消息。
可选的，上述方法还可以包括：第二核心网设备从第一核心网设备接收第一下行信息的有效区域信息，第一下行信息针对第一下行信息的有效区域内的设备有效。其中，第一下行信息的有效区域信息和第一下行信息可以包含在同一消息中。
该情况下，可选的，当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，执行步骤708a；当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE不位于有效区域内时，执行步骤708b。
根据实施例一中的关于UE是否位于有效区域部分的描述可知，当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，向第一RAN节点发送的第一下行信息和向第二RAN节点发送的下行信息可以相同，因此，第二核心网设备可以直接将第一下行信息向第二RAN节点发送，当然，也可以向第一核心网设备发送指示信息，第一核心网设备将第一下行信息向第二RAN节点发送。
当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE不位于有效区域内时，向第二RAN节点发送的下行信息和向第一RAN节点发送的第一下行信息不同。因此，第二核心网设备可以向第一核心网设备发送指示信息，从而使得第一核心网设备构造向第二RAN节点发送的第二下行信息。也就是说，在步 骤708b之后，可以执行步骤407中的“第一核心网设备向第二RAN节点发送第二下行信息”的过程。该过程的实现可以参见上文，在此不再赘述。
需要说明的是，在上述步骤407执行的过程中，第一核心网设备会根据UE是否位于有效区域内的判断结果向第二RAN节点发送第一下行信息或第二下行信息。在该实施例中，由于在确定执行步骤708a或708b的过程中，第二核心网设备已经判断过UE是否位于有效区域内，因此，若第一核心网设备接收到指示信息，可以直接构造向第二RAN节点发送的第二下行信息，不用去判断UE是否位于有效区域内。
可选的，当第一核心网设备为SMF，第二核心网设备为AMF，且AMF根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，进一步的，若SMF与UE的处于激活态的PDU会话(或者说，第二RAN节点在路径切换过程中上报的PDU会话)对应的SMF相同时，执行步骤708b。若SMF与UE的处于激活态的PDU会话对应的SMF不同时，执行步骤708a。此处的“UE的处于激活态的PDU会话”不包括被第二RAN节点拒绝的PDU会话。
需要说明的是，以表1为例，在上文中所示的路径切换过程中，AMF会向SMF1上报需要更新的PDU会话，需要更新的PDU会话为UE的、且被第二RAN节点接受的处于激活态的PDU会话(例如，PDU会话2和PDU会话3)，而SMF1在之前向AMF发送的第一下行信息用于激活UE的PDU会话，该PDU会话处于去激活态(即PDU会话1)。
若SMF1与SMF2为同一个SMF，则AMF需要向SMF1发送指示信息，指示PDU会话激活失败。否则当SMF1接收到AMF上报的需要更新的PDU会话后，由于SMF1没有接收到PDU会话1状态的反馈，SMF1不知道该如何执行后续步骤。因此，该情况下，第二核心网设备可以执行步骤708b。
若SMF1与SMF2为不同的SMF，SMF1不会接收到AMF上报的需要更新的PDU会话，因此，第二核心网设备可以执行步骤708a。
可选的，步骤702在具体实现时，第二核心网设备可以在UE在第二核心网设备上的状态为连接管理连接态，且第二核心网设备根据存储的UE的上下文中的位置信息和第一下行信息的有效区域信息确定UE位于第一下行信息的有效区域内时，第二核心网设备向第一RAN节点发送第一下行信息。
根据上文中的描述，当UE的RRC连接状态为连接态或非激活态时，第二核心网设备会存储UE的上下文，上下文中包括UE的位置信息，第二核心网设备认为上下文中的位置信息为UE的当前位置信息，因此，第二核心网设备根据存储的UE的上下文中的位置信息和第一下行信息的有效区域信息确定UE位于第一下行信息的有效区域内时，认为第一下行信息对UE有效，则第二核心网设备向第一RAN节点发送第一下行信息。
情况2、第一下行信息用于第一RAN节点去激活UE的PDU会话，PDU会话处于激活态；第一消息用于指示PDU会话去激活失败。
该情况下，关于第一下行信息以及第二RAN节点如何去激活PDU会话的相关描述可以参见实施例一中的情况2部分的相应描述，在此不再赘述。
在情况2下，该实施例中：
具体的，该实施例中可以通过第一消息的消息类型或消息名称指示PDU会话去激活失败，比如，当消息类型为失败消息或拒绝消息时，该第一消息可以用于指示PDU会话去激活失败。该实施例中也可以通过在第一消息中添加一个指示信息指示PDU会话去激活失败，关于该指示信息的相关的描述可参见下文中的描述。
步骤706的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不去激活该PDU会话，则第一RAN节点向第二核心网设备发送第一消息。
情况3、第一下行信息用于第一RAN节点更新UE的PDU会话，PDU会话处于激活态；第一消息用于指示PDU会话更新失败。
该情况下，关于第一下行信息以及第二RAN节点如何更新PDU会话的相关描述可以参见实施例一中的情况3部分的相应描述，在此不再赘述。
在情况3下，该实施例中：
该实施例中可以通过第一消息的消息类型或消息名称指示PDU会话更新失败，比如，当消息类型为失败消息或拒绝消息时，该第一消息可以用于指示PDU会话更新失败。该实施例中也可以通过在第一消息中添加一个指示信息指示PDU会话更新失败，关于该指示信息的相关的描述可参见下文中的描述。
步骤706的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不更新该PDU会话，则第一RAN节点向第二核心网设备发送第一消息。
情况4、第一下行信息用于第一RAN节点释放UE的PDU会话，PDU会话处于激活态；第一消息用于指示PDU会话释放失败。
该情况下，关于第一下行信息以及第二RAN节点如何释放PDU会话的相关描述可以参见实施例一中的情况4部分的相应描述，在此不再赘述。
在情况4下，该实施例中：
具体的，该实施例中可以通过第一消息的消息类型或消息名称指示PDU会话释放失败，比如，当消息类型为失败消息或拒绝消息时，该第一消息可以用于指示PDU会话释放失败。该实施例中也可以通过在第一消息中添加一个指示信息指示PDU会话释放失败，关于该指示信息的相关的描述可参见下文中的描述。
步骤706的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，第一RAN节点不释放该PDU会话，则第一RAN节点向第二核心网设备发送第一消息。
在情况1-情况4中的任一种情况下：
第一核心网设备可以为SMF，第二核心网设备可以为AMF。
情况5、第一下行信息为发往UE的下行信息；第一消息用于指示第一下行信息传输失败。
该情况下，关于第一下行信息的相关描述可以参见实施例一中的情况5部分的相应描述，在此不再赘述。
在情况5下，该实施例中：
具体的，该实施例中可以通过第一消息的消息类型或消息名称指示第一下行信息 传输失败，比如，当消息类型为失败消息或拒绝消息时，该第一消息可以用于指示第一下行信息传输失败。该实施例中也可以通过在第一消息中添加一个指示信息指示第一下行信息传输失败，关于该指示信息的相关的描述可参见下文中的描述。
其中，第一核心网设备可以为生成第一下行信息的设备，第二核心网设备可以为转发第一下行信息的设备。示例性的，当第一下行信息为发往UE的短消息时，第一核心网设备可以为SMSF(生成第一下行信息的设备)，第二核心网设备可以为AMF(转发第一下行信息的设备)。
步骤706的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE当前位于第二RAN节点的覆盖范围内，第一RAN节点无法成功向UE发送第一下行信息，则第一RAN节点向第二核心网设备发送第一消息。
第二核心网设备接收到第一消息后，可以确定第一下行信息发送失败，由于UE当前位于第二RAN节点的覆盖范围内，因此，第二核心网设备向第二RAN节点发送第一下行信息，以使得第二RAN节点将第一下行信息向UE发送。当然，第二核心网设备也可以向第一核心网设备发送指示信息，使得第一核心网设备向第二RAN节点发送第一下行信息。
在情况1-情况5中的任一种情况下：
可选的，指示信息为失败原因值(或称为原因值)。
可选的，原因包括：UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程。进一步的，原因包括：UE从第二RAN节点发起RRC连接恢复流程，该情况下，指示信息中可以包括第二RAN节点的标识。
原因还可以包括：UE正在进行切换；或者，上下文转移；或者，UE在第一RAN节点不可达；或者，第一下行信息没有传输。
一种可能的实现方式，步骤708a可以在UE发起的RRC连接恢复完成后执行，即步骤708a可以包括：第二核心网设备根据第一消息，在RRC连接恢复完成后向第二RAN节点发送第一下行信息。或者，步骤708a可以在UE发起的RRC连接恢复流程中的路径切换完成后执行，即步骤708a可以包括：第二核心网设备根据第一消息，在RRC连接恢复流程中的路径切换完成后向第二RAN节点发送第一下行信息。示例性的，第二核心网设备可以在发送N2接口路径切换请求应答消息(可参见步骤914)后，确定RRC连接恢复完成或RRC连接恢复流程中的路径切换完成。
关于路径切换以及该种可能的实现方式的有益效果的相关描述可参见实施例一中的相关部分，在此不再赘述。
另一种可能的实现方式，第二核心网设备可以在接收到第一消息的预设时间之后，向第二RAN节点发送第一下行信息或向第一核心网设备发送指示信息。可选的，预设时间可以通过保护定时器设置。该情况下，步骤708a的一种示例性的实现方式，第二核心网设备根据第一消息，启动定时器，并在定时器到期后向第二RAN节点发送第一下行信息。步骤708b的一种示例性的实现方式，第二核心网设备根据第一消息，启动定时器，并在定时器到期后向第一核心网设备发送指示信息。定时器所预定的时长即预设时间。示例性的，预设时间可以设置为UE的RRC连接恢复流程执行完成所需要 的时间。
以第一下行信息用于激活PDU会话为例，第二核心网设备根据第一消息可以确定UE的PDU会话激活失败，此时可以将PDU会话激活失败的信息通知第一核心网设备，由第一核心网设备决策执行的后续动作。其中，当通过第一消息中的指示信息指示PDU会话激活失败时，第二核心网设备可以直接将第一消息中的指示信息向第一核心网设备发送，或者根据该指示信息生成另一个指示信息向第一核心网设备发送，另一个指示信息同样用于指示PDU会话激活失败。当通过第一消息的消息类型或消息名称指示PDU会话激活失败时，第二节点可以生成指示信息向第一核心网设备发送。
在情况2-情况5中的任意一种情况下，在步骤708b之后，第一核心网设备可以执行实施例一中的步骤407中的“第一核心网设备向第二RAN节点发送第二下行信息”。此时，第二下行信息与第一下行信息相同。
实施例二中情况1-情况5的有益效果可以参见实施例一中的对应情况的有益效果。
实施例三
本申请实施例还提供了一种通信方法。该方法中，第二核心网设备获取到第一下行信息后，获取UE的当前位置信息，根据UE的当前位置信息对第一下行信息进行处理。该方法应用于RRC连接状态为非激活态的UE从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。图8中包括两个方案，第一个方案包括步骤801-807和808a，第二个方案包括步骤801-807和808b。一个方案为一种通信方法。
具体包括：
801、第二核心网设备获取第一下行信息。
其中，第一下行信息可以为第二核心网设备从第一核心网设备接收到的下行信息，也可以为第二核心网设备生成的下行信息。
示例性的，当第一下行信息为与UE的PDU会话相关的信息时，第二核心网设备可以为AMF，第一下行信息可以为AMF从SMF接收到的下行信息。当第一下行信息为向UE发送的短消息时，第二核心网设备可以为AMF，第一下行信息可以为AMF从SMSF接收到的下行信息。当第一下行信息为更新的UE上的接入和移动性管理参数时，第二核心网设备可以为AMF，第一下行信息可以为AMF生成的下行信息。其他情况可参见表2，在此不再赘述。
802、第二核心网设备向第一RAN节点发送位置请求消息，位置请求消息用于请求UE的当前位置信息。
由于第二核心网设备根据存储的UE的上下文中的位置信息确定为UE服务的RAN节点为第一RAN节点，因此，第二核心网设备向第一RAN节点发送位置请求消息。
803、第一RAN节点从第二核心网设备接收位置请求消息。
804、当UE的RRC连接状态为非激活态时，第一RAN节点根据位置请求消息，寻呼UE。
关于第一RAN节点寻呼UE的相关描述可参见上文中的步骤403，在此不再赘述。
805、第一RAN节点从第二RAN节点接收UE的上下文请求。
关于步骤805的相关描述可参见上文中的步骤404，在此不再赘述。
806、第一RAN节点根据上下文请求向第二核心网设备发送UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息，和/或，UE的当前位置信息。
第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE当前位于第二RAN节点的覆盖范围内。因此，第一RAN节点可以向第二核心网设备发送UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息，和/或，UE的当前位置信息。由于此时为UE服务的RAN节点为第二RAN节点，因此，UE的当前位置信息可以指示当前为UE服务的RAN节点为第二RAN节点。
807、第二核心网设备从第一RAN节点接收UE的当前位置信息，和/或，第二核心网设备从第一RAN节点接收UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息。
可以理解的是，当第一RAN节点向第二核心网设备发送UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息时，第二核心网设备从第一RAN节点接收该指示信息。当第一RAN节点向第二核心网设备发送UE的当前位置信息时，第二核心网设备从第一RAN节点接收UE的当前位置信息。当第一RAN节点向第二核心网设备发送UE从第一RAN节点之外的其它RAN节点发起RRC连接恢复流程的指示信息和UE的当前位置信息时，第二核心网设备从第一RAN节点接收该指示信息和UE的当前位置信息。
在步骤807之后，当UE的第一下行信息为用于激活/去激活/更新/释放UE的PDU会话的信息时，可以执行步骤808a或808b，当UE的第一下行信息为发往UE的信息时，可以执行步骤808a。
808a、第二核心网设备向第二RAN节点发送第一下行信息。
808b、第二核心网设备向第一核心网设备发送指示信息。
其中，第一下行信息可以为以下情况1-5中的任意一种情况：
情况1、第一下行信息用于第一RAN节点激活UE的PDU会话，PDU会话处于去激活态。
该情况下，关于第一下行信息以及第二RAN节点如何激活PDU会话的相关描述可以参见实施例一中的情况1部分的相应描述，在此不再赘述。
在情况1下，该实施例中：
步骤806的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求，则第一RAN节点向第二核心网设备发送指示信息和/或UE的当前位置信息。具体原因可参见上文。
可选的，上述方法还可以包括：第二核心网设备从第一核心网设备接收第一下行信息的有效区域信息，第一下行信息针对第一下行信息的有效区域内的设备有效。其中，第一下行信息的有效区域信息和第一下行信息可以包含在同一消息中。
该情况下，可选的，当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，执行步骤808a；当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE不位于有效区域内时，执 行步骤808b。
根据实施例一中的关于UE是否位于有效区域部分的描述可知，当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，向第一RAN节点发送的第一下行信息和向第二RAN节点发送的下行信息可以相同，因此，第二核心网设备可以直接将第一下行信息向第二RAN节点发送，当然，也可以向第一核心网设备发送指示信息，第一核心网设备将第一下行信息向第二RAN节点发送。
当第二核心网设备根据UE的当前位置信息和第一下行信息的有效区域信息确定UE不位于有效区域内时，向第二RAN节点发送的下行信息和向第一RAN节点发送的第一下行信息不同，因此，第二核心网设备可以向第一核心网设备发送指示信息，从而使得第一核心网设备构造向第二RAN节点发送的第二下行信息。也就是说，在步骤808b之后，可以执行步骤407中的“第一核心网设备向第二RAN节点发送第二下行信息”的过程。该过程的实现可以参见上文，在此不再赘述。
需要说明的是，在上述步骤407执行的过程中，第一核心网设备会根据UE是否位于有效区域内的判断结果向第二RAN节点发送第一下行信息或第二下行信息。在该实施例中，由于在确定执行步骤808a或808b的过程中，第二核心网设备已经判断过UE是否位于有效区域内，因此，若第一核心网设备接收到指示信息，可以直接构造向第二RAN节点发送的第二下行信息，不用去判断UE是否位于有效区域内。
可选的，当第一核心网设备为SMF，第二核心网设备为AMF，且AMF根据UE的当前位置信息和第一下行信息的有效区域信息确定UE位于有效区域内时，进一步的，若SMF与UE的处于激活态的PDU会话(或者说，第二RAN节点在路径切换过程中上报的PDU会话)对应的SMF相同时，执行步骤808b。若SMF与UE的处于激活态的PDU会话对应的SMF不同时，执行步骤808a。此处的“UE的处于激活态的PDU会话”不包括被第二RAN节点拒绝的PDU会话。关于该可选的方法的有益效果可参见上文，在此不再赘述。
情况2、第一下行信息用于第一RAN节点去激活UE的PDU会话。
该情况下，关于第一下行信息以及第二RAN节点如何去激活PDU会话的相关描述可以参见实施例一中的情况2部分的相应描述，在此不再赘述。
在情况2下，该实施例中：
步骤806的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求。因此，第一RAN节点不去激活该PDU会话，则第一RAN节点向第二核心网设备发送指示信息和/或UE的当前位置信息。
情况3、第一下行信息用于第一RAN节点更新UE的PDU会话。
该情况下，关于第一下行信息以及第二RAN节点如何更新PDU会话的相关描述可以参见实施例一中的情况3部分的相应描述，在此不再赘述。
在情况3下，该实施例中：步骤806的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求。因此，第一RAN节点不更新该PDU会话，则第一RAN节点向第二 核心网设备发送指示信息和/或UE的当前位置信息。
情况4、第一下行信息用于第一RAN节点释放UE的PDU会话。
该情况下，关于第一下行信息以及第二RAN节点如何释放PDU会话的相关描述可以参见实施例一中的情况4部分的相应描述，在此不再赘述。
在情况4下，该实施例中：
步骤806的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE向第二RAN节点发起了RRC连接恢复请求。因此，第一RAN节点不释放该PDU会话，则第一RAN节点向第二核心网设备发送指示信息和/或UE的当前位置信息。
在情况1-情况4中的任一种情况下：
第一核心网设备可以为SMF，第二核心网设备可以为AMF。
情况5、第一下行信息为发往UE的下行信息。其中，第一核心网设备可以为生成第一下行信息的设备，第二核心网设备可以为转发第一下行信息的设备。示例性的，当第一下行信息为发往UE的短消息时，第一核心网设备可以为SMSF(生成第一下行信息的设备)，第二核心网设备可以为AMF(转发第一下行信息的设备)。
第二核心网设备也可以为生成第一下行信息的设备。
该情况下，关于第一下行信息的相关描述可以参见实施例一中的情况5部分的相应描述，在此不再赘述。
在情况5下，该实施例中：
步骤806的一种示例性的实现方式，第一RAN节点在接收到第二RAN节点发送的上下文请求后，可以确定UE当前位于第二RAN节点的覆盖范围内。因此，第一RAN节点无法成功向UE发送第一下行信息，则第一RAN节点向第二核心网设备发送指示信息和/或UE的当前位置信息。
第二核心网设备接收到指示信息和/或UE的当前位置信息后，可以确定第一下行信息发送失败，由于UE当前位于第二RAN节点的覆盖范围内，因此，第二核心网设备向第二RAN节点发送第一下行信息，以使得第二RAN节点将第一下行信息向UE发送。当然，第二核心网设备也可以向第一核心网设备发送指示信息，使得第一核心网设备向第二RAN节点发送第一下行信息。
一种可能的实现方式，步骤808a可以在UE发起的RRC连接恢复完成后执行，即步骤808a可以包括：第二核心网设备在RRC连接恢复完成后向第二RAN节点发送第一下行信息。或者，步骤808a可以在UE发起的RRC连接恢复流程中的路径切换完成后执行，即步骤808a可以包括：第二核心网设备在RRC连接恢复流程中的路径切换完成后向第二RAN节点发送第一下行信息。示例性的，第二核心网设备可以在发送N2接口路径切换请求应答消息(可参见步骤914)后，确定RRC连接恢复完成或RRC连接恢复流程中的路径切换完成。
关于路径切换以及该种可能的实现方式的有益效果的相关描述可参见实施例一中的相关部分，在此不再赘述。
另一种可能的实现方式，第二核心网设备可以在接收到指示信息和/或UE的当前位置信息的预设时间之后，向第二RAN节点发送第一下行信息或向第一核心网设备发 送指示信息。可选的，预设时间可以通过保护定时器设置。该情况下，步骤808a的一种示例性的实现方式，第二核心网设备启动定时器，并在定时器到期后向第二RAN节点发送第一下行信息。步骤808b的一种示例性的实现方式，第二核心网设备启动定时器，并在定时器到期后向第一核心网设备发送指示信息。定时器所预定的时长即预设时间。示例性的，预设时间可以设置为UE的RRC连接恢复流程执行完成所需要的时间。
以第一下行信息用于激活PDU会话为例，第二核心网设备根据指示信息和/或UE的当前位置信息确定UE的PDU会话激活失败，此时可以将PDU会话激活失败的信息通知第一核心网设备，由第一核心网设备决策执行的后续动作。其中，当通过指示信息指示PDU会话激活失败时，第二核心网设备可以直接将指示信息向第一核心网设备发送，或者根据该指示信息生成另一个指示信息向第一核心网设备发送，另一个指示信息同样用于指示PDU会话激活失败。
在情况2-情况5中的任意一种情况下，在步骤808b之后，第一核心网设备可以执行实施例一中的步骤407中的“第一核心网设备向第二RAN节点发送第二下行信息”。此时，第二下行信息与第一下行信息相同。
实施例三中情况1-情况5的有益效果可以参见实施例一中的对应情况的有益效果。
上述实施例提供的方法，核心网设备从第一RAN节点获取UE的当前位置信息仅仅是对核心网设备获取UE的当前位置信息的一种示例，在实际实现时，核心网设备还可以通过其他方式获取UE的当前位置信息，例如，可以从第二RAN节点获取UE的当前位置信息。上述实施例中，第一下行信息的有效区域的粒度可以是TA粒度、基站粒度、小区粒度、切片粒度、切片实例粒度、UPF粒度、SMF粒度、PLMN粒度等等。即第一下行信息对于TA内的、基站的覆盖范围内的、小区内的、切片内的、UPF的服务区域内的、SMF的服务区域内的、PLMN内的设备有效。
上述实施例中，“指示信息用于指示PDU会话激活失败”也可以描述为“指示信息用于指示第一核心网设备重新发起PDU会话激活流程”；“指示信息用于指示PDU会话去激活失败”也可以描述为“指示信息用于指示第一核心网设备重新发起PDU会话去激活流程”；“指示信息用于指示PDU会话更新失败”也可以描述为“指示信息用于指示第一核心网设备重新发起PDU会话更新流程”；“指示信息用于指示PDU会话释放失败”也可以描述为“指示信息用于指示第一核心网设备重新发起PDU会话释放流程”。
本申请下述实施例中以上述方法应用在5G网络中为例对本申请实施例提供的方法进行示例性说明。其中，假设UE有2个PDU会话，分别为第一PDU会话和第二PDU会话，第一PDU会话处于去激活态，第二PDU会话处于激活态，为第一PDU会话和第二PDU会话服务的SMF分别为SMF1和SMF2。第一下行信息用于激活UE的第一PDU会话。第一核心网设备为SMF1，第二核心网设备为AMF。以下方法应用于UE从RAN1的覆盖范围移动至RAN2的覆盖范围内的场景中。为接入RAN1的UE服务的UPF为UPF1，为接入RAN2的UE服务的UPF为UPF2。
实施例1
该实施例中，AMF向SMF1发送指示信息，指示信息用于指示UE的第一PDU会话激活失败。参见图9，该方法包括：
900、UPF1向SMF1发送数据通知(data notification)。
其中，UPF1在接收到UE的下行数据(downlink data)后，若确定用于承载该下行数据的PDU会话处于去激活态，则向为该PDU会话服务的SMF发送数据通知，数据通知用于通知SMF1有UE的下行数据需要发送。该实施例以及下文中的实施例中以承载该下行数据的PDU会话为第一PDU会话为例进行说明。
网络设备1向网络设备2发送一个信息，相应的，网络设备2会从网络设备1接收该信息。例如，UPF1向SMF1发送数据通知，SMF1从UPF1接收数据通知。在本申请实施例中，为了方便描述，不再对网络设备2接收的动作进行说明。
901、SMF1向AMF发送第一下行信息和第一下行信息的有效区域(下文中简称为有效区域)。
在步骤901之前，该方法还可以包括：SMF1可以根据数据通知中包含的与第一PDU会话的标识相对应的N4接口会话标识确定需要激活的PDU会话。第一下行信息为SMF1为第一PDU会话生成的信息。
第一下行信息和第一下行信息的有效区域可以包含在AMF提供的N1接口消息N2接口消息传输请求消息(Namf_Communication_N1N2MessageTransfer)中。
902、AMF确定UE的状态为连接管理连接态。
其中，UE的状态包含在AMF中存储的UE的上下文中。
步骤902为可选步骤。
在步骤902后可以直接执行步骤903，也可以在AMF根据存储的UE的上下文中的位置信息和有效区域进一步确定UE位于有效区域内时执行步骤903。
903、AMF向RAN1发送第一下行信息。
第一下行信息可以包含在N2接口请求(N2request)消息中。
904、RAN1寻呼UE。
步骤904可以在RAN1确定UE的RRC连接状态为非激活态时执行。
在步骤904之前，AMF还可以向SMF1发送AMF提供的N1接口消息N2接口消息传输响应消息(Namf_Communication_N1N2MessageTransfer response)，其中可以包括用于指示AMF成功接收到第一下行信息和第一下行信息的有效区域的信息。
若UE当前位于RAN2的覆盖范围内，该方法还可以包括以下步骤：
905、UE向RAN2发送RRC连接恢复请求(RRC connection resume request)。
906、RAN2从RAN1获取UE的上下文(UE context)。
步骤906在具体实现时，RAN2向RAN1发送UE的上下文请求(retrieve UE context request)，其中包含UE的标识(例如，RRC非激活态-无线网络临时标识(inactive-radio network temporary identity，简称I-RNTI)。RAN1向RAN2发送UE上下文响应(retrieve UE context response)，其中包含UE的上下文。
907、RAN1向AMF发送指示信息。
其中，指示信息可以包含在N2接口请求应答(N2request ack)消息中。
指示信息用于指示RAN1激活UE的第一PDU会话失败。关于指示信息的其他描述可参见上文，在此不再赘述。
步骤907的另一种实现方式，RAN1还可以向AMF发送用于指示RAN1激活UE 的第一PDU会话失败的消息，关于该消息的解释可参见上文，在此不再赘述。
908、AMF向SMF1发送指示信息。
其中，指示信息可以包含在SMF1提供的PDU会话的会话上下文更新请求(Nsmf_PDUSession_UpdateSMContextRequest)中。
AMF向SMF1发送的指示信息用于SMF1确定第一PDU会话激活失败。
909、SMF1确定在预设时间之后向RAN2发送第二下行信息。
步骤909的另一种实现方式，SMF1在确定UE的路径切换完成或RRC连接恢复流程完成后向RAN2发送第二下行信息。关于预设时间、路径切换和RRC连接恢复流程的相关描述可以参见上文，在此不再赘述。
该实施例以及下述实施例中的预设时间的起始时间可以为接收到指示信息的时间，也可以为其他时间，本申请实施例对此不作具体限定。
910、SMF1向AMF发送指示信息响应，指示信息响应用于指示SMF1成功接收到指示信息。
指示信息响应可以包含在SMF1提供的PDU会话的会话上下文更新响应(Nsmf_PDUSession_UpdateSMContextResponse)中。
步骤910为可选步骤，为了描述方便，在下述实施例中不再体现该步骤。
911、RAN2向AMF发送N2接口路径切换请求(N2 path switch request)。
N2接口路径切换请求用于请求进行UE的路径切换。关于路径切换的相关描述参见上文，在此不再赘述。
912、AMF向SMF2发送SMF2提供的PDU会话的会话上下文更新请求(Nsmf_PDUSession_UpdateSMContextRequest)。
PDU会话的会话上下文更新请求用于请求更新第二PDU会话的上下文。该实施例以及下文中的实施例中以RAN2接受第二PDU会话为例进行说明。
913、SMF2向AMF发送SMF2提供的PDU会话的会话上下文更新响应(Nsmf_PDUSession_UpdateSMContextResponse)。
914、AMF向RAN2发送N2接口路径切换请求应答(N2 path switch ack)。
步骤911至步骤914的目的是将UE的处于激活态的PDU会话切换至RAN2上。该过程也可以执行在步骤907之前，该情况下，步骤909可以不执行。
915、RAN2向UE发送RRC连接恢复(RRC connection resume)消息。
步骤905至步骤915为UE和RAN之间的RRC连接恢复流程。
步骤915还可以执行在步骤906和步骤911之间。
916、SMF1向RAN2发送第二下行信息。
具体的，SMF1可以通过AMF向RAN2发送第二下行信息。
其中，第一下行信息和第二下行信息可以相同也可以不同，具体可参见上文中的相关描述。
该实施例中，AMF可以不感知SMF和RAN之间传输的信息，即AMF透传SMF和RAN之间的信息。在AMF感知SMF和RAN之间传输的信息的情况下，在步骤907和步骤908之间还可以包括步骤907a。步骤907a可以为：AMF确定UE从RAN1之外的其他RAN节点发起RRC连接恢复流程。
实施例2
该实施例中，AMF根据为第二PDU会话服务的SMF(即SMF2)与SMF1是否相同从而判断是否向SMF1发送指示信息。
参见图10，该实施例提供的方法包括：
1000-1007、分别与步骤900-907相同。
1008、AMF获取UE的当前位置信息。
具体的，AMF可以接收RAN1发送的UE的当前位置信息。UE的当前位置信息指示UE位于RAN2的覆盖范围内。
1009、AMF根据UE的当前位置信息和有效区域确定UE是否位于有效区域内、且为UE的处于激活态的PDU会话服务的SMF(即SMF2)与SMF1是否相同。
若AMF根据UE的当前位置信息和有效区域确定UE位于有效区域内、且SMF1与SMF2为相同的SMF，执行步骤1010a-1017a。
1010a、AMF向SMF1发送指示信息。
其中，指示信息可以包含在SMF1提供的PDU会话的会话上下文更新请求中。
AMF向SMF1发送的指示信息用于SMF1确定第一PDU会话激活失败。
1011a、SMF1确定在预设时间之后向RAN2发送第一下行信息。
步骤1011a的另一种实现方式，SMF1在确定UE的路径切换完成或RRC连接恢复流程完成后向RAN2发送第一下行信息。关于预设时间、路径切换和RRC连接恢复流程的相关描述可以参见上文，在此不再赘述。
1012a-1016a，与步骤911-915分别相同。
1017a、SMF1向RAN2发送第一下行信息。
由于此时UE位于有效区域内，因此，SMF1向RAN1和RAN2发送的为同一个下行信息。具体的，SMF1可以通过AMF向RAN2发送第一下行信息。
若AMF根据UE的位置信息和有效区域确定UE位于有效区域内、且SMF1与SMF2为不同的SMF，执行步骤1010b-1016b。
1010b、AMF根据指示信息确定在预设时间之后向RAN2发送第一下行信息。
步骤1010b的另一种实现方式，AMF在确定UE的路径切换完成或RRC连接恢复流程完成后向RAN2发送第一下行信息。关于预设时间、路径切换和RRC连接恢复流程的相关描述可以参见上文，在此不再赘述。
1011b-1015b，与步骤911-915分别相同。
1016b、AMF向RAN2发送第一下行信息。
由于此时UE位于有效区域内，因此，AMF向RAN1和RAN2发送的为同一个下行信息。
实施例3
该实施例中，SMF1可以通过判断UE当前是否位于有效区域内，从而判断向RAN2发送的下行信息(第一下行信息或第二下行信息)。
参见图11，该实施例提供的方法包括：
1100-1107、分别与步骤900-907相同。
1108、与步骤1010a相同。
1109、SMF1根据UE的当前位置信息和有效区域确定UE是否在有效区域内，若是，确定在预设时间后向RAN2发送第一下行信息，若否，根据UE的当前位置信息生成第二下行信息，并确定在预设时间后向RAN2发送第二下行信息。
步骤1109的另一种实现方式，当SMF1根据UE的当前位置信息和有效区域确定UE在有效区域内时，SMF1还可以在确定UE的路径切换完成或RRC连接恢复流程完成后向RAN2发送第一下行信息。当SMF1根据UE的当前位置信息和有效区域确定UE不在有效区域内时，SMF1还可以在确定UE的路径切换完成或RRC连接恢复流程完成后向RAN2发送第二下行信息。关于预设时间、路径切换和RRC连接恢复流程的相关描述可以参见上文，在此不再赘述。
1110-1114，与步骤911-915分别相同。
若UE位于有效区域内，在步骤1114之后执行步骤1115，若UE不位于有效区域内，在步骤1114之后执行步骤1116。
1115、SMF1向RAN2发送第一下行信息。
具体的，SMF1可以通过AMF向RAN2发送第一下行信息。
1116、SMF1向RAN2发送第二下行信息。
具体的，SMF1可以通过AMF向RAN2发送第二下行信息。
实施例4、
该实施例中，AMF获取UE的当前位置信息，根据UE的当前位置信息执行后续操作。其中，AMF可以不感知RAN和SMF之间传输的信息。AMF中存储的UE的RRC连接状态为非激活态或AMF中未存储UE的RRC连接状态。
参见图12，该实施例提供的方法包括：
1200-1201、与步骤900-901分别相同。
1202、AMF确定UE的RRC连接状态为非激活态或AMF中未存储UE的RRC连接状态。
1203、AMF向RAN1发送位置报告控制(location report control)消息。
位置报告控制消息即上文中的位置请求消息。
1204、RAN1寻呼UE。
步骤1204的相关描述可参见步骤904，在此不再赘述。
由于UE当前位于RAN2的覆盖范围内，因此，步骤1204之后可以执行步骤1205-1216。
1205-1216、分别与步骤1105-1116相同。
其中，步骤1207中的指示信息可以包含在位置报告失败(location report failure)消息中。
该实施例中，步骤1207中还可以包括UE的当前位置信息。该情况下，AMF可以判断UE是否在有效区域内。
若是，AMF向RAN2发送第一下行信息(例如，可以执行步骤1010b-1016b)。
若否，AMF向SMF1发送指示信息。此时，步骤1209可以替换为：SMF1根据UE的当前位置信息生成第二下行信息，并确定在预设时间后向RAN2发送第二下行信息；步骤1215不执行。
需要说明的是，在UE还未移动到RAN2的情况下，若UE处于RAN1的覆盖范围内，RAN1可以向AMF发送位置报告(location report)消息。位置报告消息中包括UE的当前位置信息。由于此时，RAN1可以根据第一下行信息激活第一PDU会话，因此，AMF向RAN1发送第一下行信息。
上述主要从方法角度对本申请实施例提供的方案进行了介绍。可以理解的是，通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
本申请实施例提供了一种通信装置，可以参见图13。该装置130可以应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。装置130可以用于执行上述各方法实施例中第一核心网设备(图9-图12中，第一核心网设备可以为SMF1)的动作。该装置130可以是第一核心网设备，也可以是芯片或片上系统，不予限制。
具体地，装置130可以包括：通信单元1302和处理单元1301。
处理单元1301，用于通过通信单元1302向所述第一RAN节点发送第一下行信息，所述第一下行信息用于所述第一RAN节点激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
处理单元1301，还用于通过通信单元1302从所述第一RAN节点接收指示信息，所述指示信息用于指示所述PDU会话激活失败；
处理单元1301，还用于根据所述指示信息，通过所述通信单元向所述第二RAN节点发送第二下行信息，所述第二下行信息用于所述第二RAN节点激活所述终端的PDU会话。
可选地，处理单元1301还用于：
当根据所述终端的当前位置信息确定所述终端不位于所述第一下行信息的有效区域内时，根据所述终端的当前位置信息生成所述第二下行信息。
可选地，处理单元1301还用于：
根据所述终端的当前位置信息确定所述终端位于所述第一下行信息的有效区域内，所述第一下行信息与所述第二下行信息为相同的信息。
可选地，处理单元1301，还用于通过通信单元1302从所述第一RAN节点接收所述终端的当前位置信息。
可选地，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激 活失败的原因。
本申请实施例提供了一种通信装置，可以参见图13。装置130可以应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。装置130可以用于执行上述各方法实施例中第一RAN节点(在图9-图12中，第一RAN节点可以为RAN1)的动作。该装置130可以是第一RAN节点，也可以是芯片或片上系统，不予限制。
具体地，装置130包括：通信单元1302和处理单元1301。
通信单元1302，用于从第一核心网设备接收所述终端的第一下行信息，所述第一下行信息用于所述装置激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
处理单元1301，用于当所述终端的RRC连接状态为非激活态时，根据所述第一下行信息，寻呼所述终端；
通信单元1302，还用于从所述第二RAN节点接收所述终端的上下文请求；
通信单元1302，还用于根据所述上下文请求，向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
可选地，通信单元1302，还用于向所述第一核心网设备发送所述终端的当前位置信息。
可选地，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
本申请实施例提供了一种通信装置，可以参见图13。装置130可以应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。该装置130可以用于执行上述各方法实施例中第二核心网设备的相关动作。装置130可以是第二核心网设备，也可以是芯片或片上系统，不予限制。
具体地，装置130包括：通信单元1302和处理单元1301。
处理单元1301，用于通过通信单元1302从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
处理单元1301，还用于通过所述通信单元从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
处理单元1301，还用于根据所述消息，通过通信单元1302向所述第二RAN节点发送所述第一下行信息。
可选地，处理单元1301还用于：
通过通信单元1302从所述第一核心网设备接收所述第一下行信息的有效区域信息；
当根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端位于所述有效区域内时，根据所述消息，通过所述通信单元向所述第二RAN节点发送所述第一下行信息。
可选地，处理单元1301还用于：
通过通信单元1302从所述第一核心网设备接收所述第一下行信息的有效区域信 息；
当所述终端在所述装置上的状态为连接管理连接态，且根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，通过所述通信单元向所述第一RAN节点发送所述第一下行信息。
可选地，处理单元1301，还用于通过通信单元1302从所述第一RAN节点接收所述终端的当前位置信息。
可选地，所述消息的消息类型或消息名称用于指示所述PDU会话激活失败；或者，所述消息中包括指示信息，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
本申请实施例提供了一种通信装置，可以参见图13。装置130可以应用于RRC连接状态为非激活态的终端从第一RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中。该装置130可以用于执行上述各方法实施例中第二核心网设备(在图9-图12中，第二核心网设备可以为AMF)的相关动作。装置130可以是第二核心网设备，也可以是芯片或片上系统，不予限制。
具体地，装置130包括：通信单元1302和处理单元1301。
处理单元1301，用于通过通信单元1302从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
处理单元1301，还用于通过通信单元1302从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
处理单元1301，还用于根据所述消息，通过通信单元1302向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
可选地，处理单元1301还用于：
通过所述通信单元从所述第一核心网设备接收所述第一下行信息的有效区域信息；
当根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端不位于所述有效区域内时，根据所述消息，通过所述通信单元向所述第一核心网设备发送所述指示信息。
可选地，处理单元1301还用于：
通过通信单元1302从所述第一核心网设备接收所述第一下行信息的有效区域信息；
当所述终端在所述装置上的状态为连接管理连接态，且根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，通过所述通信单元向所述第一RAN节点发送所述第一下行信息。
可选地，处理单元1301，还用于通过通信单元1302从所述第一RAN节点接收所述终端的当前位置信息。
可选地，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述各方法实施例中第一核心网设备或第二核心网设备或第一 RAN节点的动作。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方法实施例中第一核心网设备或第二核心网设备或第一RAN节点的动作。
本申请实施例还提供了一种通信系统，包括上述实施例中的第一核心网设备和第一RAN节点。
可选地，该系统还包括：上述第二核心网设备，可以参见图7或图8所示的实施例。
可选地，该系统还包括：上述第二RAN节点，可以参见图6或图7或图8所示的实施例。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，简称SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (36)

  1. 一种通信方法，其特征在于，所述方法应用于无线资源控制RRC连接状态为非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：
    第一核心网设备向所述第一RAN节点发送第一下行信息，所述第一下行信息用于所述第一RAN节点激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述第一核心网设备从所述第一RAN节点接收指示信息，所述指示信息用于指示所述PDU会话激活失败；
    所述第一核心网设备根据所述指示信息，向所述第二RAN节点发送第二下行信息，所述第二下行信息用于所述第二RAN节点激活所述终端的PDU会话。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述第一核心网设备根据所述终端的当前位置信息确定所述终端不位于所述第一下行信息的有效区域内时，所述第一核心网设备根据所述终端的当前位置信息生成所述第二下行信息。
  3. 根据权利要求1所述的方法，其特征在于，当所述第一核心网设备根据所述终端的当前位置信息确定所述终端位于所述第一下行信息的有效区域内时，所述第一下行信息与所述第二下行信息为相同的信息。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备从所述第一RAN节点接收所述终端的当前位置信息。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  6. 一种通信方法，其特征在于，所述方法应用于终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：
    所述第一RAN节点从第一核心网设备接收所述终端的第一下行信息，所述第一下行信息用于所述第一RAN节点激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    当所述终端的无线资源控制RRC连接状态为非激活态时，所述第一RAN节点根据所述第一下行信息，寻呼所述终端；
    所述第一RAN节点从所述第二RAN节点接收所述终端的上下文请求；
    所述第一RAN节点根据所述上下文请求，向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一RAN节点向所述第一核心网设备发送所述终端的当前位置信息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  9. 一种通信方法，其特征在于，所述方法应用于无线资源控制RRC连接状态为非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：
    第二核心网设备从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述第二核心网设备从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
    所述第二核心网设备根据所述消息，向所述第二RAN节点发送所述第一下行信息。
  10. 根据权利要求9所述的方法，其特征在于，所述第二核心网设备根据所述消息，向所述第二RAN节点发送所述第一下行信息，包括：
    所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当所述第二核心网设备根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备根据所述消息，向所述第二RAN节点发送所述第一下行信息。
  11. 根据权利要求9所述的方法，其特征在于，所述向所述第一RAN节点发送所述第一下行信息，包括：
    所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当所述终端在所述第二核心网设备上的状态为连接管理连接态，且所述第二核心网设备根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备向所述第一RAN节点发送所述第一下行信息。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述方法还包括：
    所述第二核心网设备从所述第一RAN节点接收所述终端的当前位置信息。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，所述消息的消息类型或消息名称用于指示所述PDU会话激活失败；或者，所述消息中包括指示信息，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  14. 一种通信方法，其特征在于，所述方法应用于无线资源控制RRC连接状态为非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述方法包括：
    第二核心网设备从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述第二核心网设备从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
    所述第二核心网设备根据所述消息，向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
  15. 根据权利要求14所述的方法，其特征在于，所述第二核心网设备根据所述消息，向所述第一核心网设备发送指示信息，包括：
    所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信 息；
    当所述第二核心网设备根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端不位于所述有效区域内时，所述第二核心网设备根据所述消息，向所述第一核心网设备发送所述指示信息。
  16. 根据权利要求14所述的方法，其特征在于，所述向所述第一RAN节点发送所述第一下行信息，包括：
    所述第二核心网设备从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当所述终端在所述第二核心网设备上的状态为连接管理连接态，且所述第二核心网设备根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，所述第二核心网设备向所述第一RAN节点发送所述第一下行信息。
  17. 根据权利要求14-16任一项所述的方法，其特征在于，所述方法还包括：
    所述第二核心网设备从所述第一RAN节点接收所述终端的当前位置信息。
  18. 根据权利要求14-17任一项所述的方法，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  19. 一种通信装置，其特征在于，所述装置应用于无线资源控制RRC连接状态为非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述装置包括：通信单元和处理单元；
    所述处理单元，用于通过所述通信单元向所述第一RAN节点发送第一下行信息，所述第一下行信息用于所述第一RAN节点激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收指示信息，所述指示信息用于指示所述PDU会话激活失败；
    所述处理单元，还用于根据所述指示信息，通过所述通信单元向所述第二RAN节点发送第二下行信息，所述第二下行信息用于所述第二RAN节点激活所述终端的PDU会话。
  20. 根据权利要求19所述的装置，其特征在于，所述处理单元还用于：
    当根据所述终端的当前位置信息确定所述终端不位于所述第一下行信息的有效区域内时，根据所述终端的当前位置信息生成所述第二下行信息。
  21. 根据权利要求19所述的装置，其特征在于，所述处理单元还用于：
    根据所述终端的当前位置信息确定所述终端位于所述第一下行信息的有效区域内，所述第一下行信息与所述第二下行信息为相同的信息。
  22. 根据权利要求19-21任一项所述的装置，其特征在于，所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收所述终端的当前位置信息。
  23. 根据权利要求19-22任一项所述的装置，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  24. 一种通信装置，其特征在于，所述装置应用于终端从所述装置的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述装置包括：通信单元和处理单元；
    所述通信单元，用于从第一核心网设备接收所述终端的第一下行信息，所述第一下行信息用于所述装置激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述处理单元，用于当所述终端的无线资源控制RRC连接状态为非激活态时，根据所述第一下行信息，寻呼所述终端；
    所述通信单元，还用于从所述第二RAN节点接收所述终端的上下文请求；
    所述通信单元，还用于根据所述上下文请求，向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
  25. 根据权利要求24所述的装置，其特征在于，
    所述通信单元，还用于向所述第一核心网设备发送所述终端的当前位置信息。
  26. 根据权利要求24或25所述的装置，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  27. 一种通信装置，其特征在于，所述装置应用于无线资源控制RRC连接状态为非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述装置包括：通信单元和处理单元；
    所述处理单元，用于通过所述通信单元从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
    所述处理单元，还用于根据所述消息，通过所述通信单元向所述第二RAN节点发送所述第一下行信息。
  28. 根据权利要求27所述的装置，其特征在于，所述处理单元还用于：
    通过所述通信单元从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端位于所述有效区域内时，根据所述消息，通过所述通信单元向所述第二RAN节点发送所述第一下行信息。
  29. 根据权利要求27所述的装置，其特征在于，所述处理单元还用于：
    通过所述通信单元从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当所述终端在所述装置上的状态为连接管理连接态，且根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，通过所述通信单元向所述第一RAN节点发送所述第一下行信息。
  30. 根据权利要求27-29任一项所述的装置，其特征在于，
    所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收所述终端的当前位置信息。
  31. 根据权利要求27-30任一项所述的装置，其特征在于，所述消息的消息类型或消息名称用于指示所述PDU会话激活失败；或者，所述消息中包括指示信息，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
  32. 一种通信装置，其特征在于，所述装置应用于无线资源控制RRC连接状态为 非激活态的终端从第一无线接入网RAN节点的覆盖范围移动至第二RAN节点的覆盖范围的场景中，所述装置包括：通信单元和处理单元；
    所述处理单元，用于通过所述通信单元从第一核心网设备接收第一下行信息，并向所述第一RAN节点发送所述第一下行信息，所述第一下行信息用于激活所述终端的分组数据单元PDU会话，所述PDU会话处于去激活态；
    所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收用于指示所述PDU会话激活失败的消息；
    所述处理单元，还用于根据所述消息，通过所述通信单元向所述第一核心网设备发送指示信息，所述指示信息用于指示所述PDU会话激活失败。
  33. 根据权利要求32所述的装置，其特征在于，所述处理单元还用于：
    通过所述通信单元从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当根据所述终端的当前位置信息和所述第一下行信息的有效区域信息确定所述终端不位于所述有效区域内时，根据所述消息，通过所述通信单元向所述第一核心网设备发送所述指示信息。
  34. 根据权利要求32所述的装置，其特征在于，所述处理单元还用于：
    通过所述通信单元从所述第一核心网设备接收所述第一下行信息的有效区域信息；
    当所述终端在所述装置上的状态为连接管理连接态，且根据存储的所述终端的上下文中的位置信息和所述有效区域信息确定所述终端位于所述有效区域内时，通过所述通信单元向所述第一RAN节点发送所述第一下行信息。
  35. 根据权利要求32-34任一项所述的装置，其特征在于，
    所述处理单元，还用于通过所述通信单元从所述第一RAN节点接收所述终端的当前位置信息。
  36. 根据权利要求32-35任一项所述的装置，其特征在于，所述指示信息为失败原因值，所述失败原因值用于指示所述PDU会话激活失败的原因。
PCT/CN2019/081548 2018-04-10 2019-04-04 通信方法及装置 Ceased WO2019196746A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2020551532A JP7125041B2 (ja) 2018-04-10 2019-04-04 通信方法及び通信装置
EP19784604.1A EP3771285B1 (en) 2018-04-10 2019-04-04 Communication method and apparatus for reliable communication
KR1020207030403A KR20200134293A (ko) 2018-04-10 2019-04-04 통신 방법 및 장치
BR112020020888-4A BR112020020888A2 (pt) 2018-04-10 2019-04-04 método de comunicação, aparelho de comunicações, sistema de comunicação, e mídia de armazenamento legível por computador
US17/066,927 US11470671B2 (en) 2018-04-10 2020-10-09 Activating a packet data unit (PDU) session using downlink information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810317648.X 2018-04-10
CN201810317648.XA CN110366270B (zh) 2018-04-10 2018-04-10 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/066,927 Continuation US11470671B2 (en) 2018-04-10 2020-10-09 Activating a packet data unit (PDU) session using downlink information

Publications (1)

Publication Number Publication Date
WO2019196746A1 true WO2019196746A1 (zh) 2019-10-17

Family

ID=68163922

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/081548 Ceased WO2019196746A1 (zh) 2018-04-10 2019-04-04 通信方法及装置

Country Status (7)

Country Link
US (1) US11470671B2 (zh)
EP (1) EP3771285B1 (zh)
JP (1) JP7125041B2 (zh)
KR (1) KR20200134293A (zh)
CN (1) CN110366270B (zh)
BR (1) BR112020020888A2 (zh)
WO (1) WO2019196746A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114301967A (zh) * 2021-12-29 2022-04-08 中国电信股份有限公司 窄带物联网控制方法、装置及设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11172459B2 (en) * 2017-06-14 2021-11-09 Lg Electronics Inc. Method for managing session, and SMF node for performing method
US12538144B2 (en) * 2018-10-31 2026-01-27 Apple Inc. Performance measurements related to PDU session and N4 session management
CN111954269B (zh) * 2019-05-15 2022-11-01 华为技术有限公司 一种承载修改方法及接入网设备
WO2021089811A1 (en) * 2019-11-08 2021-05-14 Nokia Technologies Oy Detection and triggering for ue-to-ue p2p traffic flow routing optimization
CN113498138B (zh) * 2020-04-07 2023-07-07 华为技术有限公司 通信方法和通信装置
CN113473371B (zh) * 2021-08-31 2022-01-25 阿里巴巴达摩院(杭州)科技有限公司 无线通信方法、直播数据的处理方法、amf及ran
CN116456411B (zh) * 2023-05-09 2026-01-30 中国电信股份有限公司广东研究院 基站切换方法、接入网络、网元、装置和存储介质
CN117042069B (zh) * 2023-09-28 2024-02-27 新华三技术有限公司 应用于5g核心网中的路径切换方法、装置及电子设备
WO2025072153A1 (en) * 2023-09-29 2025-04-03 Ofinno, Llc Signaling using multiple accesses

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094096A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 一种演进网络架构下的移动性管理方法
WO2011002244A2 (en) * 2009-07-02 2011-01-06 Lg Electronics Inc. A method to facilitate user equipment (ue) handoff within a packet data communication system
CN102124778A (zh) * 2008-06-18 2011-07-13 捷讯研究有限公司 用于第三代合作伙伴计划多个网络间服务质量连续性的机制
CN107846703A (zh) * 2016-09-21 2018-03-27 电信科学技术研究院 一种数据传输方法及装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8032359B2 (en) * 2007-02-14 2011-10-04 Mindspeed Technologies, Inc. Embedded silence and background noise compression
WO2011120222A1 (zh) * 2010-03-31 2011-10-06 华为技术有限公司 优先级业务激活、去激活方法、装置和系统
EP3570629B1 (en) * 2012-03-27 2021-01-06 BlackBerry Limited Handling a connection in a wireless communication system
JP6397819B2 (ja) * 2012-08-23 2018-09-26 インターデイジタル パテント ホールディングス インコーポレイテッド ワイヤレスシステムにおける複数のスケジューラによる動作
US9247528B2 (en) * 2012-10-12 2016-01-26 Cisco Technology, Inc. System and method for reducing paging in UTRAN/GERAN/E-UTRAN networks when idle signaling reduction is active
CN103987092B (zh) * 2013-02-08 2018-09-21 华为终端（东莞）有限公司 切换过程中选择网络设备的方法和装置
US9271135B2 (en) * 2013-03-15 2016-02-23 T-Mobile Usa, Inc. Local network alert system for mobile devices using an IMS session and Wi-Fi access point
US9444746B2 (en) * 2013-06-25 2016-09-13 Qualcomm Incorporated Selectively transferring high-priority non-audio data over a quality of service channel
CN105472668A (zh) * 2014-08-12 2016-04-06 芯讯通无线科技（上海）有限公司 移动终端及小区重选方法
US10575360B2 (en) * 2015-04-03 2020-02-25 Samsung Electronics Co., Ltd. Apparatus and method for providing multi-connection using different wireless connection technologies in wireless communication system
EP3297382B1 (en) * 2015-05-15 2021-01-20 Samsung Electronics Co., Ltd. Methods and devices for transmitting or receiving scheduling request in mobile communication system
WO2018058437A1 (zh) * 2016-09-29 2018-04-05 华为技术有限公司 一种通信方法、设备和系统
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备
CN107040340A (zh) * 2017-05-05 2017-08-11 电信科学技术研究院 一种系统消息传输方法及装置
EP3481139B1 (en) * 2017-06-21 2022-10-12 LG Electronics Inc. Method and device for performing service request procedure in wireless communication system
US10524189B2 (en) * 2017-09-08 2019-12-31 Kt Corporation Method and apparatus for performing access control in next generation wireless network
CN107770828B (zh) * 2017-11-10 2020-07-03 重庆邮电大学 一种基于本地移动性切换管理方法
WO2019160376A1 (ko) * 2018-02-18 2019-08-22 엘지전자 주식회사 무선 통신 시스템에서 smf의 신호 송수신 방법 및 이를 위한 장치
US10506506B2 (en) * 2018-04-30 2019-12-10 Ofinno, Llc 5G policy control for restricted local operator services
US11399304B2 (en) * 2018-09-28 2022-07-26 Ofinno, Llc Packet duplication by core network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094096A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 一种演进网络架构下的移动性管理方法
CN102124778A (zh) * 2008-06-18 2011-07-13 捷讯研究有限公司 用于第三代合作伙伴计划多个网络间服务质量连续性的机制
WO2011002244A2 (en) * 2009-07-02 2011-01-06 Lg Electronics Inc. A method to facilitate user equipment (ue) handoff within a packet data communication system
CN107846703A (zh) * 2016-09-21 2018-03-27 电信科学技术研究院 一种数据传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3771285A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114301967A (zh) * 2021-12-29 2022-04-08 中国电信股份有限公司 窄带物联网控制方法、装置及设备

Also Published As

Publication number Publication date
CN110366270A (zh) 2019-10-22
EP3771285A4 (en) 2021-06-02
BR112020020888A2 (pt) 2021-02-23
EP3771285A1 (en) 2021-01-27
EP3771285B1 (en) 2023-01-04
JP2021517769A (ja) 2021-07-26
US20210029770A1 (en) 2021-01-28
KR20200134293A (ko) 2020-12-01
CN110366270B (zh) 2021-08-13
US11470671B2 (en) 2022-10-11
JP7125041B2 (ja) 2022-08-24

Similar Documents

Publication Publication Date Title
WO2019196746A1 (zh) 通信方法及装置
US11805394B2 (en) Context management method and apparatus
CN108605269B (zh) 一种会话管理方法及装置
US11202338B2 (en) Session establishment method and apparatus
US11265936B2 (en) Handling QoS flow description and EPS bearer operation errors in 4G 5G systems
KR20210123434A (ko) 통신 방법, 소스 기지국, 타깃 기지국, 코어 네트워크 장치 및 단말 장치
US12035174B2 (en) Rate control method, apparatus, and system
WO2019158093A1 (zh) 一种确定ssc模式的方法及装置
CN110944361B (zh) 用于负载均衡的方法与网元
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2023077948A1 (zh) 一种通信的方法和装置
WO2022160861A1 (zh) 通信方法及装置
WO2023273767A1 (zh) 通信方法、接入和移动管理功能实体、无线接入网设备、和计算机可读存储介质
CN116250363A (zh) 一种双终端设备进行数据传输的方法及装置
WO2020052463A1 (zh) 通信方法和网元
WO2022206007A1 (zh) 中继通信方法及装置、存储介质、中继设备
US12101851B2 (en) Methods, network function nodes and computer readable media for contents communication management
TW202333530A (zh) 無線通信方法和相應的用戶設備
CN115134948A (zh) 恢复承载的方法、装置、核心网网元及存储介质
CN121694027A (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: 19784604

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020551532

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020020888

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20207030403

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019784604

Country of ref document: EP

Effective date: 20201023

ENP Entry into the national phase

Ref document number: 112020020888

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20201009