WO2023134563A1 - 用于寻呼的方法以及相关联的通信装置、介质和芯片 - Google Patents

用于寻呼的方法以及相关联的通信装置、介质和芯片 Download PDF

Info

Publication number
WO2023134563A1
WO2023134563A1 PCT/CN2023/070903 CN2023070903W WO2023134563A1 WO 2023134563 A1 WO2023134563 A1 WO 2023134563A1 CN 2023070903 W CN2023070903 W CN 2023070903W WO 2023134563 A1 WO2023134563 A1 WO 2023134563A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
terminal device
address
update information
Prior art date
Application number
PCT/CN2023/070903
Other languages
English (en)
French (fr)
Inventor
项弘禹
李秉肇
陈磊
李晨琬
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP23739906.8A priority Critical patent/EP4443999A1/en
Publication of WO2023134563A1 publication Critical patent/WO2023134563A1/zh
Priority to US18/770,599 priority patent/US20240365286A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/022—One-way selective calling networks, e.g. wide area paging
    • H04W84/027—One-way selective calling networks, e.g. wide area paging providing paging services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present disclosure relates to the field of communication, and more particularly, to a paging method and an associated communication device, medium and chip.
  • a radio resource control (Radio Resource Control, RRC) connection may be established between the terminal device and the access network device.
  • the state of the RRC connection includes an RRC connected (RRC_CONNECTED) state.
  • RRC_CONNECTED Radio Resource Control
  • the terminal device When the terminal device is in the RRC_CONNECTED state, the terminal device has established an RRC context, and all the parameters necessary for establishing communication between the terminal device and the network are known to both communication parties.
  • the RRC context is a key parameter for establishing communication between the terminal device and the network, specifically including security context, user equipment (User Equipment, UE) capability information, and the like.
  • the state of the RRC connection also includes an RRC idle (RRC_IDLE) state.
  • the terminal equipment When the terminal equipment is in the RRC_IDLE state, it is characterized in that the terminal equipment does not retain the RRC context.
  • a new RRC state is introduced, that is, the RRC inactive state (RRC_INACTIVE).
  • the RRC_INACTIVE state can only be changed from RRC_CONNECTED through the RRC release message.
  • the network device When the terminal device is released from the RRC_CONNECTED state to the RRC_INACTIVE state, the network device will assign the terminal device an identifier Inactive Radio Network Temporary Identity (I-RNTI) ), and store the context of the UE with this identifier.
  • I-RNTI Inactive Radio Network Temporary Identity
  • This network device is also called the last serving (Last Serving) next generation Node B (Next Generation Node B, gNB) of the terminal device, and is sometimes recorded as the anchor point gNB (Anchor gNB ).
  • the terminal device requests to resume the previously suspended RRC connection or to update the Radio Access Network (RAN) Notification Area (RNA)
  • the terminal device sends a message to the current network device.
  • the terminal device can also establish a signaling connection with the core network device.
  • the terminal device may establish a signaling connection with an Access and Mobility Management Function (AMF) entity.
  • AMF Access and Mobility Management Function
  • the connection state between the terminal device and the AMF may be referred to as a connection management (Connection Management, CM) state.
  • the CM state may include a CM connected (CM_CONNECTED) state and a CM idle (CM_IDLE) state.
  • CM_CONNECTED CM connected
  • CM_IDLE CM idle
  • a discontinuous reception (Discontinuous Reception, DRX) mechanism is proposed.
  • the DRX mechanism allows the terminal device to periodically enter the sleep state (sleep mode) at certain times, not to monitor the downlink control channel, but when it needs to monitor, it wakes up from the sleep state (wake up), so that it can Make the terminal equipment achieve the purpose of power saving.
  • the terminal device is in the sleep state, transmission failure may occur. For example, when the terminal device is in the CM_CONNECTED state and the RRC_INACTIVE state, since the terminal device is in the CM_CONNECTED state, the core network device needs to start the retransmission related to the terminal device after sending data.
  • the terminal device since the terminal device is also in the RRC_INACTIVE state, the terminal device will enter the sleep state and will not monitor the downlink control channel, which will cause the terminal device to be unable to monitor the downlink control channel before the retransmission timer expires, thus Resulting in data transmission failure.
  • Example embodiments of the present disclosure provide a scheme for paging in a communication system.
  • a method for communication includes that the access network equipment sends update information to the core network equipment.
  • the update information includes the address of the access network device and the inactive wireless network temporary identifier I-RNTI of the terminal device.
  • the method further includes the access network equipment receiving a paging message corresponding to the terminal equipment from the core network equipment.
  • the method further includes the access network device sending a wireless access network paging message to the terminal device.
  • the radio access network paging message includes the I-RNTI. That is to say, the first aspect of the present disclosure proposes that the terminal device can be in the CM_IDLE and RRC_INACTIVE states.
  • the first aspect of the present disclosure proposes that a new paging procedure for terminal equipment can realize paging for terminal equipment in CN_IDLE and RRC_INACTIVE states.
  • the access network device determines that the RRC state of the terminal device needs to be updated, the access network device sends update information to the core network device, thereby triggering an update of the CM state of the terminal device at the core network device.
  • the core network device After updating the CM state of the terminal device, the core network device sends a paging message for the terminal device to the access network device according to the corresponding relationship between the access network device and the terminal device indicated in the update information. The access network device then sends a radio access network paging message instead of a core network paging message to the terminal device.
  • the access network device can apply the method provided in this application to page the terminal device, avoiding the data transmission failure caused by the expiration of the retransmission timer of the core network device, And, further, the core network device can also determine the paging area according to the address of the access network device to realize the wireless access network paging of the terminal device, thereby improving the efficiency of paging, so that the terminal device can quickly access to the communication network. It can be understood that the paging process proposed in the first aspect of the present disclosure can also be applied to terminal devices in other states, not limited to terminal devices in CM_IDLE and RRC_INACTIVE states.
  • the paging message corresponding to the terminal device includes an I-RNTI.
  • the core network device reduces the paging area according to the address of the access network device, and enables the terminal device to start the RRC connection recovery process, and retrieves the UE context stored in the access network device according to the I-RNTI, so that the terminal The device was able to quickly restore the connection.
  • the update information is used to instruct the core network device to update the connection management state of the terminal device. In this manner, the core network device can update the connection management status of the terminal device in a timely manner.
  • the method further includes the access network device sending a radio resource control release message to the terminal device.
  • the radio resource control release message includes I-RNTI.
  • the access network device notifies the terminal device of the identifier assigned to the terminal device by the access network device. In this way, a terminal device can monitor paging messages corresponding to the terminal device.
  • the radio resource control release message further includes at least one of the following: a discontinuous reception cycle (extended discontinuous reception (extended discontinuous reception, eDRX) cycle and/or DRX cycle), paging time window (Page Time Window, PTW) length, RNA information, RNA update period.
  • a discontinuous reception cycle extended discontinuous reception (extended discontinuous reception, eDRX) cycle and/or DRX cycle
  • paging time window Page Time Window, PTW
  • RNA information for example, eDRX cycle
  • RNA update period RNA update period
  • the address of the access network device is the IP address of the access network device, or the address of the wireless access network where the access network device is located. In this way, the core network device reduces the paging area according to the address of the access network device.
  • a method for communication includes that the access network equipment sends update information to the core network equipment, wherein the update information includes the address of the access network equipment.
  • the method further includes the access network device sending a request for terminal device identification to the core network device.
  • the method also includes the access network device receiving the response message from the core network device.
  • the response message includes a Temporary Mobile Subscriber Identity (TMSI) of the terminal device.
  • TMSI Temporary Mobile Subscriber Identity
  • the method further includes the access network equipment receiving a paging message corresponding to the terminal equipment from the core network equipment.
  • the paging message includes TMSI.
  • the method also includes the access network device sending a wireless access network paging message.
  • the radio access network paging message includes the inactive radio network temporary identifier I-RNTI of the terminal device. That is to say, if the access network device determines that the RRC state of the terminal device needs to be updated, the access network device sends update information to the core network device, thereby triggering an update of the CM state of the terminal device at the core network device. The access network device also requests the core network device for the identifier of the terminal device. The core network device sends a paging message for the terminal device to the access network device according to the update information and the requested terminal device identifier. After receiving the paging message from the core network device, the access network device sends the wireless access network paging message to the terminal device.
  • the core network device determines the paging area according to the address of the access network device, thereby improving the efficiency of paging, so that the terminal device can quickly access the communication network.
  • the method further includes the access network device determining the I-RNTI according to the first correspondence between the TMSI and the I-RNTI.
  • the paging message corresponding to the terminal device further includes: first indication information.
  • the first indication information instructs the access network device to page the terminal device through a wireless access network paging message.
  • the terminal device determines according to the first indication information that radio access network paging should be performed on the terminal device instead of core network paging.
  • the core network device reduces the paging area according to the address of the access network device, and enables the RRC connection recovery process of the UE terminal device, and retrieves the UE context stored in the access network device according to the I-RNTI, so that the UE Ability to restore connection quickly.
  • the method further includes: the access network device storing the first correspondence. In this manner, the core network device can implement paging in the wireless network notification area.
  • the update information is used to instruct the core network device to update the connection management state of the terminal device. In this manner, the core network device can update the connection management status of the terminal device in a timely manner.
  • the method further includes: the access network device sending a radio resource control release message to the terminal device.
  • the radio resource control release message at least includes I-RNTI, discontinuous reception DRX cycle, extended discontinuous reception eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the discontinuous reception period is greater than the predetermined length.
  • the access network device notifies the terminal device of the identifier assigned to the terminal device by the access network device. In this manner, the core network device can update the connection management status of the terminal device in a timely manner.
  • the address of the access network device is the IP address of the access network device, or the address of the wireless access network where the access network device is located. In this way, the core network device reduces the paging area according to the address of the access network device.
  • a method for communicating includes that the first access network device receives a radio resource control recovery request from a terminal device.
  • the radio resource control recovery request includes the first identifier allocated to the terminal device by the second network device.
  • the method further includes the first access network device sending a UE context retrieval request message to the second access network device.
  • the method further includes the first access network device sending update information or release instruction information to the core network device, the update information indicating at least one of the following: the address of the first access network device, or the address assigned to the terminal by the first access network device
  • the second identifier of the device, the release instruction information indicates the release of at least one of the following: the address of the second network device, TMSI or the first identifier, or an index value corresponding to the address of the second network device and/or the first identifier.
  • the method further includes the first access network device sending a radio resource control release message to the terminal device, where the radio resource control release message includes the second identifier.
  • the first access network device when the serving access network device of the terminal device changes from the second access network device to the first access network device, the first access network device notifies the core network device to update information or Release resources. For example, if the first access network device can also support eDRX, the first access network device notifies the core network device to store the information of the first access network device for subsequent paging. For example, if the first access network device cannot support eDRX, the first access network device notifies the core network device to delete the previous information about the second access network device. Thus, the core network equipment can update relevant information in time to be used in subsequent procedures, such as paging procedures.
  • the update information is carried in the path switch request. In this way, signaling overhead can be saved.
  • a method for communicating includes a core network device receiving update information from an access network device.
  • the update information includes at least the address of the access network device.
  • the method also includes updating the connection management state of the terminal device by the core network device according to the update information.
  • the method further includes the core network device sending a paging message corresponding to the terminal device to the access network device according to the address. That is to say, the core network device triggers the update of the CM state of the terminal device according to the update information from the access network device.
  • the core network device After updating the CM state of the terminal device, the core network device sends a paging message for the terminal device to the access network device according to the address information of the access network device included in the update information. In this way, the core network equipment reduces the paging area according to the address of the access network equipment, thereby reducing waste of resources.
  • the update information further includes an inactive radio network temporary identifier I-RNTI of the terminal device, and the paging message for the terminal device includes the I-RNTI.
  • the core network device reduces the paging area according to the address of the access network device, and enables the terminal device to start the RRC connection recovery process, and retrieves the UE context stored in the access network device according to the I-RNTI, so that the UE Ability to restore connection quickly.
  • the method further includes: the core network device receiving a request for the identification of the terminal device from the access network device.
  • the method also includes the core network equipment sending a paging message for the terminal equipment to the access network equipment.
  • the paging message includes TMSI.
  • the paging message for the terminal equipment includes: the temporary mobile station identifier TMSI of the terminal equipment, and indication information indicating that paging is performed within the notification area of the radio access network. In this manner, the access network device determines to perform radio access network notification paging for the terminal device according to the received paging information, thereby improving paging efficiency.
  • the method further includes: the address of the access network device is the IP address of the access network device, or the address of the wireless access network where the access network device is located. In this way, the core network device reduces the paging area according to the address of the access network device.
  • a method for communicating includes that the core network equipment receives update information or release instruction information from the first access network equipment.
  • the update information indicates at least one of the following: the address of the first access network device, or the second identifier assigned to the terminal device by the first access network device, and the release indication information indicates the release of at least one of the following: the address of the second network device , TMSI or the first identifier, or an index value corresponding to the address of the second network device and/or the first identifier.
  • the method further includes the core network device updating the connection management state of the terminal device according to the update information or the release indication information.
  • the core network device will notify the update information or release resources according to the relevant capabilities of the first access network device .
  • the first access network device can also support eDRX
  • the first access network device notifies the core network device to store the information of the first access network device for subsequent paging.
  • the first access network device cannot support eDRX
  • the first access network device notifies the core network device to delete the previous information about the second access network device.
  • the core network equipment can update relevant information in time to be used in subsequent procedures, such as paging procedures.
  • the update information is carried in the path switch request. In this way, signaling can be saved.
  • the address of the first access network device is the IP address of the first access network device, or the address of the wireless access network where the first access network device is located.
  • the first identifier and the second identifier are an inactive radio network temporary identifier I-RNTI.
  • a method for communication includes a terminal device receiving a radio resource control release message from an access network device.
  • the radio resource control release message includes that the radio resource control release message at least includes I-RNTI, discontinuous reception DRX cycle, extended discontinuous reception eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the radio resource control state between the terminal device and the access network device is a radio resource control inactive state.
  • the connection management state between the terminal device and the core network device is the connection management idle state.
  • the method also includes the terminal device receiving the radio access network paging message.
  • the radio access network paging message includes the I-RNTI. In this way, the terminal device can start the RRC connection recovery process, and retrieve the UE context stored in the access network device according to the I-RNTI, so that the connection can be quickly restored.
  • a chip in a seventh aspect of the present disclosure, includes a processor, and may further include a memory, the processor is coupled to the memory, and is used to execute computer programs or instructions stored in the memory, so that the chip implements the aforementioned A method in any possible implementation manner of any one of the first aspect to the sixth aspect.
  • a computer program product is provided.
  • the computer program product is tangibly stored on a computer-readable medium and includes computer-executable instructions.
  • the computer-executable instructions enable the device to implement any one of the possible functions according to any one of the first to sixth aspects above. The operation of the method in the implementation.
  • a computer readable storage medium stores instructions, and when the instructions are executed by the processor of the device, the device implements the method in any possible implementation manner according to any one of the first aspect to the sixth aspect above operation.
  • the present application further provides a communication device, which can implement the access network device described in any one of the methods provided in the first aspect, the second aspect, or the third aspect.
  • the communication device may be, for example, a base station, or a baseband device in a base station.
  • the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, where the processor is configured to support the communication device to perform corresponding functions of the access network device in the methods shown above.
  • the communication device may further include a memory, which may be coupled with the processor, and store necessary program instructions and data of the communication device.
  • the communication device further includes an interface circuit, where the interface circuit is used to support communication between the communication device and devices such as terminal equipment and core network equipment.
  • the communication device includes corresponding functional modules, respectively configured to implement the steps in the above method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the communication device includes a sending unit (sometimes also called a sending module) and a receiving unit (sometimes also called a receiving module), and these units can perform corresponding functions in the above method example, for example, when implementing the method provided in the first aspect , the sending unit is used to send update information to the core network equipment.
  • the update information includes the address of the access network device and the inactive wireless network temporary identifier I-RNTI of the terminal device.
  • the receiving unit is used for receiving the paging message corresponding to the terminal equipment from the core network equipment.
  • the sending unit is used for sending a wireless access network paging message to the terminal device.
  • the radio access network paging message includes the I-RNTI.
  • the present application further provides a communication device, which can implement the core network device described in any method provided in the fourth aspect or the fifth aspect.
  • the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, where the processor is configured to support the communication device to perform corresponding functions of the core network device in the methods shown above.
  • the communication device may further include a memory, which may be coupled with the processor, and store necessary program instructions and data of the communication device.
  • the communication device further includes an interface circuit, where the interface circuit is used to support communication between the communication device and devices such as terminal equipment and access network equipment.
  • the communication device includes corresponding functional modules, respectively configured to implement the steps in the above method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the communication device includes a sending unit (sometimes also called a sending module) and a receiving unit (sometimes also called a receiving module), and these units can perform corresponding functions in the above method example, for example, when implementing the method provided in the fourth aspect , the sending unit is used to send update information to the core network equipment.
  • the update information includes the address of the access network device.
  • the sending unit is used to send a request for terminal device identification to the core network device.
  • the receiving unit is used for receiving the response message from the core network equipment.
  • the response message includes the Temporary Mobile Station Identity TMSI of said terminal device.
  • the receiving unit is used for receiving the paging message corresponding to the terminal device from the core network device.
  • the paging message includes the TMSI.
  • the sending unit is used for sending the wireless access network paging message.
  • the radio access network paging message includes the inactive radio network temporary identifier I-RNTI of the terminal device.
  • a communication device is provided.
  • the present application also provides a communication device, which can implement the access network device described in any method provided in the sixth aspect.
  • the communication device may be, for example, a terminal device.
  • the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, where the processor is configured to support the communication device to execute corresponding functions of the terminal device in the methods shown above.
  • the communication device may further include a memory, which may be coupled with the processor, and store necessary program instructions and data of the communication device.
  • the communication device further includes an interface circuit, where the interface circuit is used to support communication between the communication device and equipment such as access network equipment and core network equipment.
  • the communication device includes corresponding functional modules, respectively configured to implement the steps in the above method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the communication device includes a sending unit (sometimes also called a sending module) and a receiving unit (sometimes also called a receiving module), and these units can perform corresponding functions in the above method example, for example, when implementing the method provided in the sixth aspect , the receiving unit is configured to receive a radio resource control recovery request from the terminal device.
  • the radio resource control recovery request includes the first identifier allocated to the terminal device by the second network device.
  • the sending unit is configured to send a UE context retrieval request message to the second access network device.
  • the UE context retrieval request message is used to request the context of the terminal equipment.
  • the sending unit is used to send update information or release instruction information to the core network equipment.
  • the update information indicates at least one of the following items: the address of the first access network device, or the second identifier assigned to the terminal device by the first access network device.
  • the release instruction information indicates to release at least one of the following: the address of the second network device, or the first identifier.
  • the sending unit is configured to send a radio resource control release message to the terminal device.
  • the radio resource control release message includes the second identifier.
  • Figure 1 shows a schematic block diagram of a communication system in which embodiments of the present disclosure may be implemented
  • FIG. 2 shows an interactive signaling diagram of a communication process according to some embodiments of the present disclosure
  • Fig. 3 shows an interactive signaling diagram of a communication process according to other embodiments of the present disclosure
  • 4A and 4B show interactive signaling diagrams of the communication process according to some other embodiments of the present disclosure
  • Fig. 5 shows a flowchart implemented at an access network device according to some embodiments of the present disclosure
  • Fig. 6 shows a flowchart implemented at an access network device according to other embodiments of the present disclosure
  • Fig. 7 shows a flow chart implemented at an access network device according to some other embodiments of the present disclosure.
  • Fig. 8 shows a flowchart implemented at a core network device according to some embodiments of the present disclosure
  • Fig. 9 shows a flowchart implemented at a core network device according to other embodiments of the present disclosure.
  • Fig. 10 shows a flowchart implemented at a terminal device according to some embodiments of the present disclosure
  • FIG. 11A to FIG. 11F respectively show schematic block diagrams of communication devices according to some embodiments of the present disclosure.
  • Figure 12 shows a simplified block diagram of an example device suitable for implementing embodiments of the present disclosure.
  • Embodiments of the present disclosure may be implemented according to any suitable communication protocol, including, but not limited to, cellular communication protocols such as Fourth Generation (4G) and Fifth Generation (5G), such as the Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) 802.11 and other wireless local area network communication protocols, and/or any other protocols currently known or developed in the future.
  • cellular communication protocols such as Fourth Generation (4G) and Fifth Generation (5G)
  • 4G Fourth Generation
  • 5G Fifth Generation
  • Institute of Electrical and Electronics Engineers Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) 802.11 and other wireless local area network communication protocols, and/or any other protocols currently known or developed in the future.
  • General Packet Radio Service General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD time division duplex
  • Universal Mobile Telecommunications Service Universal Mobile Telecommunications Service
  • NB-IoT narrowband Internet of Things
  • 5G fifth generation
  • NR New Radio
  • the 5G 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) communication system is used as the background to describe the embodiments of the present disclosure.
  • 3GPP 3rd Generation Partnership Project
  • the embodiments of the present disclosure are not limited to the 3GPP communication system applied to 5G, but can be applied to any communication system with similar problems, such as wireless local area network (Wireless Local Area Network, WLAN), wired communication system, or other communication systems developed in the future, etc.
  • WLAN Wireless Local Area Network
  • terminal device refers to any terminal device capable of wired or wireless communication with network devices.
  • the terminal equipment involved in this embodiment of the present application can also be referred to as a terminal, which can be a device with a wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as Ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal device may be user equipment (User Equipment, UE), where the UE includes a handheld device with a wireless communication function, a vehicle device, a wearable device, or a computing device.
  • UE User Equipment
  • the UE may be a mobile phone (Mobile Phone), a tablet computer or a computer with a wireless transceiver function.
  • Terminal devices can also be virtual reality (Virtual Reality, VR) terminal devices, augmented reality (Augmented Reality, AR) terminal devices, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, smart Wireless terminals in power grids, wireless terminals in Smart City, wireless terminals in Smart Home, etc.
  • the device for realizing the function of the terminal may be a terminal; it may also be a device capable of supporting the terminal to realize the function, such as a chip system, and the device may be installed in the terminal.
  • the system-on-a-chip may be composed of chips, and may also include chips and other discrete devices.
  • the technical solutions provided by the embodiments of the present application are described by taking the terminal as an example in which the device for realizing the functions of the terminal is a terminal and the terminal is a UE.
  • a base station may be a device deployed in a wireless access network and capable of performing wireless communication with a terminal.
  • the base station may have various forms, such as a macro base station, a micro base station, a relay station, and an access point.
  • the base station involved in this embodiment of the present application may be a base station in 5G or a base station in LTE, where the base station in 5G may also be called a transmission reception point (Transmission Reception Point, TRP) or gNB.
  • TRP Transmission Reception Point
  • the device for realizing the function of the network device may be a network device; it may also be a device capable of supporting the network device to realize the function, such as a chip system, and the device may be installed in the network device.
  • the technical solutions provided by the embodiments of the present application are described by taking the apparatus for realizing the functions of the network equipment as network equipment and taking the network equipment as a base station as an example.
  • core network (Core Network, CN) device used in this disclosure may mean that CN devices correspond to different devices in different systems.
  • CN devices correspond to different devices in different systems.
  • the serving support node Serving GPRS Support Node, SGSN
  • General Packet Radio Service General Packet Radio Service
  • GPRS General Packet Radio Service
  • Gateway GPRS Support Node Gateway GPRS Support Node, GGSN
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • 5G communication system it can correspond to the access and mobility management function (Access and Mobility Management Function, AMF), the session management function (Session Management Function, SMF) or the user plane function (User plane Function, UPF).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User plane Function
  • Wireless communication between communication devices may include: wireless communication between network devices and terminals, wireless communication between network devices and network devices, and wireless communication between terminals.
  • wireless communication may also be referred to as “communication” for short, and the term “communication” may also be described as "data transmission”, “information transmission” or “transmission”.
  • the state of RRC connection may include RRC_IDLE state, RRC_CONNECTED state and RRC_INACTIVE state.
  • the CM state may include a CM connected (CM_CONNECTED) state and a CM idle (CM_IDLE) state.
  • CM_CONNECTED CM connected
  • CM_IDLE CM idle
  • the terminal device when the terminal device is in the RRC_IDLE state (at this time the terminal device is in the CM_IDLE state), the terminal device needs to monitor the paging message from CN, and when the terminal device is in the RRC INACTIVE state, the terminal device still maintains the CM_CONNECTED state , and the terminal device can move within the Radio Access Network (RAN) Notification Area (RNA) without notifying NG-RAN, and the last gNB serving the terminal device saves the UE context, and communicates with the terminal The NG connection of the service AMF and UPF associated with the device.
  • RAN Radio Access Network
  • RNA Radio Access Network
  • a terminal device in the RRC_INACTIVE state is the same as a terminal device in the RRC_CONNECTED state.
  • the last gNB serving the terminal device first receives the above data or Signaling, and paging the terminal equipment in all cells of the RNA, that is, radio access network (Radio Access Network, RAN) paging. If the cell of the RNA belongs to other gNBs, a paging message is sent to the corresponding gNB through the Xn interface.
  • radio access network Radio Access Network, RAN
  • the terminal device Regardless of whether the terminal device is in the RRC_IDLE state or the RRC_INACTIVE state, the terminal device needs to monitor paging messages from the network, such as CN paging and RAN paging. This is because when service data arrives, the network needs the paging device to send data to the terminal device. In order to save power consumption, the terminal device will use DRX for paging monitoring in the RRC_IDLE and RRC_INACTIVE states. The terminal device monitors a paging occasion (Paging Occasion, PO) every DRX cycle. The paging message can be sent by the network to the terminal device at the monitoring opportunity, and the terminal device analyzes the corresponding paging downlink control information (DCI) through monitoring, and knows whether the terminal device is paged according to the content indicated by the DCI.
  • DCI downlink control information
  • the inactive eDRX cycle is configured to be greater than a predetermined value (for example, 10.24s)
  • a predetermined value for example, 10.24s
  • AMF will start the NAS retransmission timer, and send the NAS packet to the anchor gNB through the N2 interface, but because the terminal device may be in a dormant state, the message cannot be sent to the terminal device temporarily.
  • the sending of the message may not be completed within a long period of time, resulting in the timeout of the NAS retransmission timer, causing the NAS process to fail.
  • the traditional method includes extending the NAS retransmission timer, but there are disadvantages such as that the NAS process will take longer. Therefore, the CM_IDLE and (with) RRC_INACTIVE state can be introduced, so that the terminal device is in the CM-IDLE state.
  • the core network does not need to provide related services when CM-CONNECTED, but the terminal device is still in the RRC_INACTIVE state, and the anchor gNB saves the UE
  • the context enables the terminal device to return to the RRC_CONNECTED state more quickly.
  • paging messages from the network include CN paging and RAN paging.
  • the core network device sends a paging message to the access network device.
  • the paging message includes the (Temporary Mobile Subscriber Identity, TMSI) assigned by the core network to the UE, and paging configuration information (DRX cycle length, eDRX Period length, PTW length, tracking area (Tracking Area, TA) index list), according to traditional CN paging, because the core network equipment does not know the access network equipment where the terminal equipment resides, the core network equipment performs paging according to TA. In other words, core network equipment needs to perform paging in a large area.
  • CM_IDLE and RRC_INACTIVE state paging by the core network equipment in a large area will cause unnecessary delay and redundant signaling.
  • core network equipment directly transmits data to access network equipment serving terminal equipment.
  • the terminal equipment in the CM_IDLE and RRC_INACTIVE state has no connection with the core network, and the core network equipment cannot directly transmit data to the access network equipment.
  • the traditional communication flow is not applicable to terminal devices in newly introduced states (eg, CM_IDLE and RRC_INACTIVE states). Therefore, a new communication process needs to be proposed to optimize the communication of the terminal equipment. It can be understood that the embodiments of the present disclosure may also be applicable to other scenarios or communication processes, and are not limited to the paging process.
  • the access network device determines that the RRC state of the terminal device needs to be updated, the access network device sends update information to the core network device, thereby triggering an update of the CM state of the terminal device at the core network device. Since the update information can indicate the corresponding relationship between the access network device and the terminal device, the core network device can determine the access network device serving the terminal device. Therefore, even in the CM_IDLE state, the core network device can still determine the access network device where the terminal device resides, so as to perform wireless access network paging, avoiding unnecessary delay and redundant signaling.
  • FIG. 1 shows a schematic diagram of a communication system 100 in which embodiments of the present disclosure may be implemented.
  • the communication system 100 includes a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which may be collectively referred to as "terminal devices 110", where N is any positive integer.
  • the communication system 100 as a part of the communication network further includes an access network device 120-1 and an access network device 120-2.
  • the terminal device and the access network device can communicate with each other.
  • Terminal device 110 may also receive messages from core network devices.
  • entity used herein refers to a network element that can implement a specific function. As shown in FIG.
  • the terminal device 110 communicates with the access network device 120-1/access network device 120-2 (ie, via a Uu link).
  • the term "uplink (UL) data” used herein refers to data sent by a terminal device to a network device.
  • the term “downlink (Downlink, DL) data” used herein refers to data sent by a network device to a terminal device.
  • the access network device 120-1 is the current serving access network device of the terminal device 110-1 and the access network device 120-2 is the previous serving access network device of the terminal device 110-1.
  • the communication system 100 also includes a core network device 130, such as an AMF.
  • the terminal device 110 may establish a connection with the core network device 130 .
  • Communication system 100 may include any suitable number of devices and cells.
  • the terminal device 110 and the access network device can communicate data and control information with each other. It should be understood that the number of various devices and their connections shown in FIG. 1 are given for illustrative purposes and no limitation is suggested.
  • Communication system 100 may include any suitable number of devices and networks suitable for implementing embodiments of the present disclosure.
  • Figure 2 shows a signaling diagram of an interaction 200 of a communication process for paging according to some embodiments of the present disclosure.
  • the interaction 200 will be described below with reference to FIG. 1 .
  • interaction 200 involves terminal device 110 - 1 , access network device 120 - 1 and core network device 130 .
  • Step 2010 the access network device 120-1 determines (2010) to update the RRC state of the terminal device 110-1.
  • the access network device 120-1 may determine that the RRC state of the terminal device 110-1 may be updated to the RRC_INACTIVE state.
  • the access network device 120-1 may determine that the terminal device 110-1 may be updated from the RRC_CONNECTED state to the RRC_INACTIVE state.
  • the access network device 120-1 may determine to configure eDRX for the terminal device 110-1 if the access network device 120-1 can support the eDRX capability, the access network device 120-1 may determine to configure eDRX for the terminal device 110-1.
  • Step 2020 The access network device 120-1 sends (2020) update information to the core network device 130, and accordingly, the core network device 130 receives the update information from the access network device 120-1.
  • the update information may be used to instruct the core network device 130 to update the connection management state of the terminal device 110-1.
  • the update information may trigger the core network device 130 to update the connection management state of the terminal device 110-1.
  • the update information includes the address of the access network device 120-1.
  • the address of the access network device 120-1 is the IP address of the access network device 120-1 or the address of the wireless access network where the access network device 120-1 is located.
  • the update information may include the RNA code of the RNA where the access network device 120-1 is located.
  • the address of the access network device 120-1 may include TA information associated with the access network device 120-1. It can be understood that the address of the access network device 120-1 may be any suitable address information. In this way, the core network device 130 knows the address of the access network device 120-1 serving the terminal device 110-1.
  • the update information may include identification information of the terminal device 110-1, such as I-RNTI.
  • the core network device 130 can The identification information of -1 determines the corresponding relationship between the access network device 120-1 and the terminal device 110-1. Therefore, in the subsequent paging process, the core network device 130 can determine the serving access network device of the terminal device to be paged.
  • the core network device 130 may store the received address of the access network device 120-1 and the I-RNTI of the terminal device 110-1. In this way, the core network device obtains the address of the access network device, so that the paging area can be reduced based on the address in the subsequent paging process.
  • the update information may be used to instruct the core network device 130 to update the connection management status of the terminal device 110-1.
  • the core network device 130 updates the connection management state of the terminal device 110-1 according to the update information.
  • the update information can be regarded as an implicit indication, that is, after receiving the update information, the predefined or preconfigured core network device 130 will update the CM_CONNECTED state to the CM_IDLE state.
  • the core network device 130 may determine the TMSI of the terminal device based on the I-RNTI and the mapping relationship between the I-RNTI and the TMSI.
  • the core network device 130 may update the terminal device 110-1 from the CM_CONNECTED state to the CM_IDLE state.
  • step 2030 is also included: the access network device 120-1 sends (2030) an RRC release message to the terminal device 110-1, and correspondingly, the terminal device 110-1 receives the RRC release message from the access network device 120-1 information.
  • the RRC release message includes the I-RNTI of the terminal device 110-1.
  • the terminal device 110-1 may determine whether a subsequent paging message is associated with the terminal device 110-1 according to the I-RNTI.
  • the RRC release message may also include DRX configuration.
  • the DRX configuration further includes at least one of the following: DRX cycle or eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the access network device 120-1 may determine to configure eDRX for the terminal device 110-1, in this case, the RRC release message may indicate that the period of eDRX is greater than a predetermined length.
  • the terminal device 110-1 may update its RRC status. For example, the terminal device 110-1 may update from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, the terminal device 110-1 may be woken up based on the paging message. In this way, the terminal device can enter the CM_IDLE and RRC_INACTIVE states.
  • the order of sending (2020) the update information and sending (2030) the RRC release message is not limited to the order shown in FIG. 2, and may be any suitable order.
  • the access network device 120-1 may first send the update information and then send the RRC release message.
  • the access network device 120-1 may first send the RRC release message and then send the update information.
  • Step 2040 The core network device 130 sends (2040) a paging message for the terminal device 110-1 to the access network device 120-1.
  • the access network device 120-1 receives a paging message for the terminal device 110 from the core network device. -1 for paging messages.
  • the paging message may include the I-RNTI of the terminal device 110-1.
  • the core network device 130 may determine the I-RNTI of the terminal device 110-1 according to the temporary mobile station identity TMSI of the terminal device 110-1 and the stored correspondence between the I-RNTI and the TMSI. It can be understood that the core network device 130 may also store the correspondence between the TMSI and the I-RNTI of other terminal devices (for example, the terminal device 110-2).
  • the TMSI may include at least one of the following: 5G System Architecture Evolution (SAE) Temporary Mobile Station Identifier (5G SAE Temporary Mobile Station Identifier, 5G-S-TMSI), 5G-TMSI, 5G Global Unique Temporary UE Identifier ( 5G Globally Unique Temporary UE Identity, 5G-GUTI), the world's only temporary UE identity GUTI. 5G-S-TMSI is a shortened version of 5G-GUTI.
  • SAE System Architecture Evolution
  • 5G-S-TMSI 5G Global Unique Temporary UE Identifier
  • 5G Globally Unique Temporary UE Identity 5G Globally Unique Temporary UE Identity
  • EPS Evolved Packet System
  • the access network device 120-1 can determine which terminal device the received paging message is for based on the stored correspondence between the I-RNTI and the TMSI.
  • Step 2050 The access network device 120-1 sends (2050) a radio access network (RAN) paging message to the terminal device 110-1, and accordingly, the terminal device 110-1 receives the RAN paging message from the access network device 120-1 paging message.
  • the radio access network paging message includes the I-RNTI of the terminal device 110-1.
  • the terminal device 110-1 can monitor the wireless access network paging message from the access network device 120-1. If the radio access network paging message monitored by the terminal device 110-1 includes the I-RNTI of the terminal device 110-1, the terminal device 110-1 may determine that the paging message is intended for itself.
  • the terminal device 110-1 is in the RRC_INACTIVE state, and the terminal device 110-1 can be woken up based on the paging message to receive subsequent data or signaling from the access network device 120-1, or send a message to the access network
  • the device 120-1 initiates an RRC connection recovery process to establish an RRC connection.
  • the terminal device starts the RRC connection recovery process, and determines the UE context stored in the access network device according to the I-RNTI, so as to quickly restore the connection.
  • the access network device determines that the RRC state of the terminal device needs to be updated, the access network device sends update information to the core network device, thereby triggering the core network device to update the CM state of the terminal device. Further, the core network device may also send a paging message for the terminal device to the access network device according to the address information of the access network device included in the update information. In other words, the core network equipment clearly knows the access network equipment that serves the terminal equipment to be paged. Therefore, even if there is no CM connection between the core network equipment and the terminal equipment, the core network equipment still does not need to perform extensive core network paging.
  • the access network device sends the wireless access network paging message to the terminal device.
  • the core network equipment reduces the paging area according to the address of the access network equipment, thereby reducing waste of resources.
  • the terminal device can retrieve the UE context stored in the access network device according to the I-RNTI included in the paging message, so as to realize fast recovery of the RRC connection. In this way, the delay caused by the RRC recovery process can also be reduced, so that the access network device can provide services for the terminal device in time, improving user experience.
  • the update information from the access network device includes both the address of the access network device 120-1 and the I-RNTI of the terminal device 110-1.
  • the update information may include the address of the access network device 120-1 instead of the I-RNTI of the terminal device 110-1.
  • FIG. 3 shows a signaling diagram of an interaction 300 of a communication procedure for paging according to some embodiments of the present disclosure, wherein the update information does not include the I-RNTI of the terminal device 110-1.
  • the interaction 300 will be described below with reference to FIG. 1 .
  • interaction 300 involves terminal device 110 - 1 , access network device 120 - 1 , and core network device 130 .
  • Step 3010 The access network device 120-1 determines (3010) to update the RRC state of the terminal device 110-1. Step 3010 is similar to step 2010 described with reference to FIG. 2 , and will not be repeated here.
  • Step 3020 The access network device 120-1 sends (3020) update information to the core network device 130, and accordingly, the core network device 130 receives the update information from the access network device 120-1.
  • the update information may be used to instruct the core network device 130 to update the connection management state of the terminal device 110-1.
  • the update information may trigger the core network device 130 to update the connection management state of the terminal device 110-1.
  • the update information includes the address of the access network device 120-1.
  • the address of the access network device 120-1 is the IP address of the access network device 120-1 or the address of the wireless access network where the access network device 120-1 is located.
  • the update information may include the RNA code of the RNA where the access network device 120-1 is located.
  • the address of the access network device 120-1 may include TA information associated with the access network device 120-1. It can be understood that the address of the access network device 120-1 may be other suitable address information.
  • the update information may be used to instruct the core network device 130 to update the connection management status of the terminal device 110-1.
  • the core network device 130 updates the connection management state of the terminal device 110-1 according to the update information.
  • the update information can be regarded as an implicit indication, that is, after receiving the update information, the predefined or preconfigured core network device 130 will update the CM_CONNECTED state to the CM_IDLE state.
  • Step 3030 The access network device 120-1 sends (3030) a request for the identification of the terminal device 110-1 to the core network device 130, and correspondingly, the core network 120 receives a request for the identification of the terminal device 110-1 from the access network device 120-1. 1 identifies the request.
  • the request for the identification of the terminal device may be a first request, and the first request is used to request the identification of the terminal device.
  • the first request is used to request the TMSI of the terminal device, which may also be understood as the first request
  • a request is used to request the core network equipment to allocate a TMSI for the terminal equipment.
  • the request may include an identifier of a context (Context) of the terminal device 110-1.
  • the request for the identity of the terminal device 110-1 may be sent in the same or different message as the update information.
  • Context or "UE context” used herein includes information required by terminal equipment during communication, such as user identification, tracking area list and security algorithms during communication.
  • the request may include a Radio Access Network Notification Area User Equipment Next Generation Application Protocol Identity (RAN UE NGAP ID).
  • the RAN UENGAP ID uniquely identifies the terminal device 110-1 through the NG interface in the access network device 120-1.
  • the core network device 130 receives the RANUE NGAP ID, the core network device 130 will store the ID during the logical NG connection of the terminal device 110-1 associated with the terminal device 110-1.
  • the core network device 130 can know that the access network The corresponding relationship between the device 120-1 and the terminal device 110-1. Therefore, when the core network device 130 needs to page the terminal device 110-1, it may be determined that the serving access network device of the terminal device 110-1 is the access network device 120-1.
  • the core network device 130 can transfer the terminal device 110-1 from The CM_CONNECTED state is updated to the CM_IDLE state.
  • Step 3040 The core network device 130 sends (3040) a response message to the access network device 120-1, and the access network device 120-1 receives the response message from the core network device 130 accordingly.
  • the response message includes the temporary mobile station identity TMSI (eg, 5G-S-TMSI) of the terminal device 110-1.
  • TMSI temporary mobile station identity
  • the above request includes a context identifier, and in this case, the response message includes the TMSI of the terminal device 110-1 corresponding to the context identifier in the above request.
  • the above request includes RAN UENGAP ID.
  • the response The message includes the TMSI of the terminal device 110-1 corresponding to the RAN UE NGAP ID in the above request.
  • the access network device 120-1 may store the correspondence between the TMSI and the I-RNTI of the terminal device 110-1. In other embodiments, the access network device 120-1 may also store the correspondence between the TMSI and the I-RNTI of other terminal devices (for example, the terminal device 110-2).
  • step 3050 is also included: the access network device 120-1 sends (3050) an RRC release message to the terminal device 110-1, and correspondingly, the terminal device 110-1 receives the RRC release message.
  • the RRC release message includes the I-RNTI of the terminal device 110-1.
  • the RRC release message also includes DRX configuration.
  • the DRX configuration may include at least one of the following: DRX cycle or eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the access network device 120-1 may determine to configure eDRX for the terminal device 110-1, in this case, the RRC release message may indicate that the period of eDRX is greater than a predetermined length.
  • the terminal device 110-1 may update its RRC status. For example, the terminal device 110-1 may update from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, the terminal device 110-1 may be woken up based on the paging message. In this way, the terminal device can enter the CM_IDLE and RRC_INACTIVE states.
  • the order of sending (3020) the update information and sending (3050) the RRC release message is not limited to the order shown in FIG. 3 , and may be any suitable order.
  • the access network device 120-1 may first send the update information and then send the RRC release message.
  • the access network device 120-1 may first send the RRC release message and then send the update information.
  • Step 3060 The core network device 130 sends (3060) a paging message for the terminal device 110-1 to the access network device 120-1.
  • the access network device 120-1 receives a paging message for the terminal device 110 from the core network device. -1 for paging messages.
  • the paging message may include the TMSI of the terminal device 110-1.
  • the paging message also includes first indication information.
  • the first indication information instructs the access network device 120-1 to page the terminal device 110-1 through a wireless access network paging message.
  • the first indication information may be indicated by designing a new paging message, such as a new message type value.
  • the first indication information may also be adding a new information element (Information Element, IE) in the paging message.
  • the paging message may include a 1-bit indication, so that the access network equipment that supports this function, that is, the access network equipment that can recognize the 1-bit indication information, can understand that it is necessary to convert the received S-TMSI into I - RNTI followed by RAN paging.
  • the first indication information may be an implicit indication, for example, a new paging message format is used to indicate that paging is performed within the radio access network notification area.
  • the access network device 120-1 may determine the type of the received paging message according to the indication information.
  • step 3070 is also included: the access network device 120-1 may determine (3070) the I-RNTI of the terminal device 110-1 according to the correspondence between the TMSI and the I-RNTI.
  • the corresponding relationship may also include the corresponding relationship between multiple TMSIs and multiple I-RNTIs.
  • the correspondence may include the correspondence between the TMSI of the terminal device 110-1 and the I-RNTI and the correspondence between the TMSI and the I-RNTI of the terminal device 110-2.
  • the access network device 120-1 may determine the I-RNTI corresponding to the TMSI included in the paging message according to the correspondence.
  • Step 3080 The access network device 120-1 sends (3080) a radio access network (RAN) paging message to the terminal device 110-1, and accordingly, the terminal device 110-1 receives the RAN paging message from the access network device 120-1 paging message.
  • the radio access network paging message includes the I-RNTI of the terminal device 110-1.
  • the terminal device 110-1 can monitor the wireless access network paging message from the access network device 120-1. If the radio access network paging message monitored by the terminal device 110-1 includes the I-RNTI of the terminal device 110-1, the terminal device 110-1 may determine that the paging message is intended for itself.
  • the terminal device 110-1 is in the RRC_INACTIVE state, and the terminal device 110-1 can be woken up based on the paging message to receive subsequent data or signaling from the access network device 120-1. In this way, the terminal device starts the RRC connection recovery process, and determines the UE context stored in the access network device according to the I-RNTI, so as to quickly restore the connection.
  • the access network device determines that the RRC state of the terminal device needs to be updated, the access network device sends update information to the core network device, thereby triggering an update of the CM state of the terminal device at the core network device.
  • the access network device also requests the core network device for the identifier of the terminal device.
  • the access network device stores the correspondence between the identifier allocated to the terminal device by itself and the identifier allocated to the terminal device by the core network device.
  • the core network device sends a paging message including the identifier assigned to the terminal device by the core network device to the access network device.
  • the access network device determines the identifier assigned to the terminal device by itself according to the above correspondence and the received paging message, and sends a paging message including the identifier assigned to the terminal device by itself to the terminal device.
  • the core network device does not need to perform additional processing on the paging process of the core network, and the access network device independently completes the conversion from paging of the core network to paging of the wireless access network.
  • the core network device since the update information also includes the address of the access network device, the core network device reduces the paging area according to the address.
  • the terminal device can retrieve the UE context stored in the access network device according to the I-RNTI included in the paging message, so as to realize fast recovery of the RRC connection. In this way, the delay caused by the RRC recovery process can also be reduced, so that the access network device can provide services for the terminal device in time, improving user experience.
  • FIG. 4A shows a signaling diagram of an interaction 400 of a communication process for an RNA update, according to some embodiments of the present disclosure.
  • Interaction 400 will be described below with reference to FIG. 1 .
  • interaction 400 involves terminal device 110 - 1 , access network device 120 - 1 , access network device 120 - 2 and core network device 130 .
  • the terminal device 110-1 needs to update the RNA when the RNA update timer expires or detects that the RNA has changed. At this time, it is assumed that the access network device 120-2 is the last served access network device.
  • Step 4010 The terminal device 110-1 sends (4010) an RRC recovery request to the access network device 120-1 to perform RNA update, and accordingly, the access network device 120-1 receives the RRC recovery request from the terminal device 110-1.
  • the RRC resume request may be used to transition the terminal device 110-1 from the RRC_INACTIVE state to the RRC_CONNECTED state.
  • the RRC recovery request includes the I-RNTI allocated to the terminal device 110-1 by the access network device 120-2.
  • Step 4020 The access network device 120-1 sends (4020) a UE context retrieval request message to the access network device 120-2.
  • the access network device 120-2 receives a message from the access network device 120-1.
  • retrieve user equipment UE context request message The UE context retrieval request message is used to request the UE context for the terminal equipment 110-1.
  • Step 4030 The access network device 120-2 sends (4030) the UE context of the terminal device 110-1 to the access network device 120-1.
  • the access network device 120-1 receives the UE context from the access network device 120-1. 2 UE context of the terminal device 110-1.
  • the access network device 120-1 may determine to configure eDRX for the terminal device 110-1.
  • step 4040 the access network device 120-1 sends (4040) update information to the core network device 130, and accordingly, the core network device 130 receives the update information from the access network device 120-1.
  • the update information may be used to instruct the core network device 130 to update the connection management state of the terminal device 110-1.
  • the update information indicates the address of the access network device 120-1.
  • the address of the access network device 120-1 is the IP address of the access network device 120-1 or the address of the wireless access network where the access network device 120-1 is located.
  • the update information may include the RNA code of the RNA where the access network device 120-1 is located.
  • the update information may also indicate the I-RNTI allocated to the terminal device 110-1 by the access network device 120-1. In some embodiments, this updated information may be sent in new signaling. Optionally, the update information may be carried in the path switching request message.
  • the core network device 130 may determine, based on the update information, that the connection management state of the terminal device 110-1 is still in the CM_IDLE state.
  • the update information can be regarded as an implicit indication, that is, after receiving the update information, the predefined or preconfigured core network device 130 will update the CM_CONNECTED state to the CM_IDLE state.
  • the access network equipment notifies the updated information of the core network equipment, so that the core network equipment can update the anchor node information for paging the UE and the like in a timely manner.
  • step 4050 may also be included: the access network device 120-1 sends (4050) an RRC release message to the terminal device 110-1, and accordingly, the terminal device 110-1 receives an RRC release message from the access network device 120-1 release message.
  • the RRC release message also includes DRX configuration.
  • the DRX configuration may include DRX cycle, eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the access network device 120-1 may determine to configure eDRX for the terminal device 110-1, in this case, the RRC release message may indicate that the period of eDRX is greater than a predetermined length.
  • the terminal device 110-1 may determine that its state is the RRC_INACTIVE state. In this case, the terminal device 110-1 may be woken up based on the paging message. Thus, the terminal device can still be in the CM_IDLE and RRC_INACTIVE states.
  • the order of sending (4040) the update information and sending (4050) the RRC release message is not limited to the order shown in FIG. 4A, and it may be any suitable order.
  • the access network device 120-1 may first send the update information and then send the RRC release message.
  • the access network device 120-1 may first send the RRC release message and then send the update information.
  • the access network device 120-1 releases the terminal device 110-1 to the CM_IDLE and RRC_INACTIVE states. In other words, through the RRC release message, the terminal device 110-1 is released to the CM_IDLE and RRC_INACTIVE state.
  • the terminal device 110-1 After the terminal device 110-1 receives the RRC release message, the terminal device 110-1 obtains the above-mentioned DRX configuration, such as DRX cycle, eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • Step 4060 The access network device 120-1 notifies (4060) the access network device 120-2 to release the resources of the terminal device 110-1.
  • the serving access network device of the terminal device changes from access network device 120-2 to access network device 120-1
  • access network device 120-1 and access network device 120-2 have similar capabilities (for example, both support eDRX)
  • the access network device 120-1 notifies the core network device 130 to store the information of the access network device 120-1 for subsequent paging.
  • the core network equipment can update relevant information in time to be used in subsequent procedures, such as paging procedures.
  • the terminal equipment can still be in CM_IDLE and RRC_INACTIVE state.
  • both the access network device 120-1 and the access network device 120-2 support eDRX.
  • the DRX capabilities supported by the access network device 120-1 and the access network device may be different.
  • FIG. 4B shows a signaling diagram of an interaction 400 for an RNA update communication process according to some embodiments of the present disclosure, where the supported DRX capabilities of the access network device 120-1 and the access network device may be different. .
  • Interaction 400 will be described below with reference to FIG. 1 .
  • interaction 400 involves terminal device 110 - 1 , access network device 120 - 1 , access network device 120 - 2 and core network device 130 .
  • the terminal device 110-1 needs to update the RNA when the RNA update timer expires or detects that the RNA has changed. At this time, it is assumed that the access network device 120-2 is the last served access network device.
  • Step 4010 The terminal device 110-1 sends (4010) an RRC recovery request to the access network device 120-1 to perform RNA update.
  • the access network device 120-1 receives the RRC recovery request from the terminal device 110-1.
  • Step 4020 The access network device 120-1 sends (4020) a UE context retrieval request message to the access network device 120-2.
  • the UE context retrieval request message is used to request the context of the terminal device 110-1.
  • the access network device 120-2 receives the UE context retrieval request message from the access network device 120-1.
  • Step 4030 The access network device 120-2 sends (4030) the UE context of the terminal device 110-1 to the access network device 120-1.
  • the access network device 120-1 receives the UE context from the access network device 120-1. 2 UE context of the terminal device 110-1.
  • the above process is similar to that described with reference to FIG. 4A , and will not be repeated here.
  • the access network device 120-1 cannot support eDRX capability. Or, even though the access network device 120-1 can support the eDRX capability, the access network device 120-1 determines not to configure eDRX for the terminal device 110-1. In this case, step 4045: the access network device 120-1 sends (4045) release instruction information to the core network device 130.
  • the release instruction information may indicate to delete the address of the access network device 120-2.
  • the address of the access network device 120-2 may include the IP address of the access network device 120-2 or the address of the wireless access network where the access network device 120-1 is located.
  • the release instruction information may include the RNA code of the RNA where the access network device 120-1 is located.
  • the release instruction information may also indicate the I-RNTI allocated to the terminal device 110-1 by the access network device 120-2 or the TMSI allocated to the terminal device 110-1 by the core network device 130.
  • the release instruction information may also include an index value corresponding to the address of the second network device and/or the first identifier. For example, each set of ⁇ the address of the second network device, the first identifier ⁇ stored by the access network device 120-2 and the core network device 130 has a first index value.
  • the release indication information may include a corresponding index value, so that the core network device 130 may delete ⁇ the address of the second network device, the first identifier ⁇ associated with the index value.
  • the core network device 130 may determine that the connection management state of the terminal device 110-1 is updated from the CM_IDLE state to the CM_CONNECTED state.
  • the release instruction information may also indicate that the access network device 120-1 does not support eDRX, or that the access network device 120-1 is not configured with eDRX.
  • the release indication information can be regarded as an implicit indication, that is, the predefined or preconfigured core network device 130 will update the CM_IDL state to the CM_CONNECTEDE state after receiving the release indication information.
  • the release indication information indicates the identification information of the terminal device (for example, I-RNTI, TMSI or index value, etc.)
  • the core network device 130 may determine the terminal device 110-1 based on the identification information.
  • the core network device 130 may change the terminal device 110-1 from the CM_IDLE state to the CM_CONNECTED state. In this way, the access network device 120-1 notifies the core network device of the information that should be deleted, thereby deleting invalid information in time and releasing storage space.
  • step 4055 is also included: the access network device 120-1 sends (4055) an RRC release message to the terminal device 110-1, and correspondingly, the terminal device 110-1 receives the RRC release message from the access network device 120-1 information.
  • the RRC release message also includes DRX configuration.
  • the DRX configuration may include DRX cycle, eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • the access network device 120-1 may determine not to configure eDRX for the terminal device 110-1, in this case, the RRC release message may indicate that the DRX period is less than a predetermined length.
  • the terminal device 110-1 may determine that its state is the RRC_INACTIVE state. In this case, the terminal device 110-1 may be woken up based on the paging message. In this way, the terminal device can be updated to CM_CONNECTED and RRC_INACTIVE state.
  • the order of sending (4045) the release indication information and sending (4055) the RRC release message is not limited to the order shown in FIG. 4B, and it may be any suitable order.
  • the access network device 120-1 may first send the release indication information and then send the RRC release message.
  • the access network device 120-1 may first send the RRC release message and then send the release indication information.
  • the access network device 120-1 releases the terminal device 110-1 to the CM_CONNECTED and RRC_INACTIVE state.
  • the terminal device 110-1 is released to the CM_CONNECTED and RRC_INACTIVE state.
  • the terminal device 110-1 After the terminal device 110-1 receives the RRC release message, the terminal device 110-1 obtains the above-mentioned DRX configuration, such as DRX cycle, eDRX cycle, PTW length, RNA information, and RNA update cycle.
  • Step 4060 The access network device 120-1 notifies (4060) the access network device 120-2 to release the resources of the terminal device 110-1.
  • the access network device 120-1 when the service access network device of the terminal device changes from the access network device 120-2 to the access network device 120-1, if the capability of the access network device 120-1 is different from that of the access network device The access network device 120-2 (for example, the access network device 120-2 supports eDRX and the access network device 120-1 does not support eDRX), then the access network device 120-1 notifies the core network device 130 to delete the previous The information of network device 120-2 is used for subsequent paging. In this manner, the access network device 120-1 notifies the core network device of the information that should be deleted, thereby deleting invalid information in time and releasing storage space.
  • FIG. 5 shows a schematic diagram of the flow of an exemplary communication method 500 .
  • the method 500 is implemented at an access network device, for example, the access network device 120-1.
  • the access network device 120-1 may determine to update the RRC state of the terminal device 110-1. For example, the access network device 120-1 may determine that the RRC state of the terminal device 110-1 may be updated to the RRC_INACTIVE state. In some embodiments, if the access network device 120-1 can support the eDRX capability, the access network device 120-1 may determine to configure eDRX for the terminal device 110-1.
  • the access network device 120 - 1 sends update information to the core network device 130 .
  • the update information includes the address of the access network device 120-1.
  • the update information may be used to instruct the core network device 130 to update the connection management state of the terminal device 110-1.
  • the content included in the update information is similar to the update information sent (2020) described in FIG. 2 , and will not be repeated here.
  • the access network device 120-1 sends an RRC release message to the terminal device 110-1.
  • the RRC release message includes the I-RNTI of the terminal device 110-1.
  • the content included in the RRC release message is similar to the RRC release message described in FIG. 2 , and will not be repeated here.
  • the order of sending the update information and the sending of the RRC release message is not limited to the order shown in FIG. 5 , and may be any suitable order.
  • the access network device 120-1 may first send the update information and then send the RRC release message.
  • the access network device 120-1 may first send the RRC release message and then send the update information.
  • the access network device 120-1 receives a paging message corresponding to the terminal device 110-1 from the core network device.
  • the paging message may include the I-RNTI of the terminal device 110-1.
  • the content included in the paging message is similar to the paging message described in FIG. 2 , and will not be repeated here.
  • the access network device 120-1 sends a radio access network paging message to the terminal device 110-1.
  • the radio access network paging message includes the I-RNTI of the terminal device 110-1.
  • the content included in the radio access network paging message is similar to the radio access network paging message described in FIG. 2 , and will not be repeated here.
  • FIG. 6 shows a schematic diagram of the flow of an exemplary communication method 600 .
  • the method 600 is implemented at an access network device, for example, the access network device 120-1.
  • the access network device 120-1 determines to update the RRC state of the terminal device 110-1. For example, the access network device 120-1 may determine that the RRC state of the terminal device 110-1 may be updated to the RRC_INACTIVE state. In some embodiments, if the access network device 120-1 can support the eDRX capability, the access network device 120-1 may determine to configure eDRX for the terminal device 110-1.
  • the access network device 120 - 1 sends update information to the core network device 130 .
  • the update information includes the address of the access network device 120-1.
  • the content included in the update information is similar to the update information sent (3020) described in FIG. 3 , and will not be repeated here.
  • the update information may be used to instruct the core network device 130 to update the connection management state of the terminal device 110-1.
  • the access network device 120-1 sends a request to the core network device 130 for the identification of the terminal device 110-1.
  • the request may include an identification of the context of the terminal device 110-1.
  • the content included in the request is similar to the request for sending (3030) described in FIG. 3 , and will not be repeated here.
  • the access network device 120 - 1 receives a response message from the core network device 130 .
  • the response message includes the temporary mobile station identity TMSI (eg, 5G-S-TMSI) of the terminal device 110-1.
  • TMSI temporary mobile station identity
  • the access network device 120-1 may store the mapping relationship between the TMSI and the I-RNTI of the terminal device 110-1.
  • the response message is similar to the response message described in FIG. 3 , and will not be repeated here.
  • the access network device 120-1 sends an RRC release message to the terminal device 110-1.
  • the RRC release message includes the I-RNTI of the terminal device 110-1.
  • the content included in the RRC release message is similar to the RRC release message described in FIG. 3 , and will not be repeated here. It can be understood that the order of sending the update information and the sending of the RRC release message is not limited to the order shown in FIG. 3 , and may be any suitable order.
  • the access network device 120-1 may first send the update information and then send the RRC release message. In other embodiments, the access network device 120-1 may first send the RRC release message and then send the update information.
  • the access network device 120-1 receives from the core network device 130 a paging message corresponding to the terminal device 110-1.
  • the paging message is similar to the paging message described in FIG. 3 , and will not be repeated here.
  • the access network device 120-1 sends a radio access network paging message to the terminal device 110-1.
  • the radio access network paging message includes the I-RNTI of the terminal device 110-1.
  • the access network device 120-1 may determine the I-RNTI of the terminal device 110-1 according to the correspondence between the TMSI and the I-RNTI.
  • the radio access network paging message is similar to the radio access network paging message described in FIG. 3 , and will not be repeated here.
  • FIG. 7 shows a schematic diagram of the flow of an exemplary communication method 700 .
  • the method 700 is implemented at an access network device, for example, the access network device 120-1.
  • the access network device 120-1 receives an RRC recovery request from the terminal device 110-1 for RNA update.
  • the RRC recovery request includes the I-RNTI allocated to the terminal device 110-1 by the access network device 120-2.
  • the RRC recovery request is similar to the RRC recovery request described in FIG. 4A or FIG. 4B , and will not be repeated here.
  • the access network device 120-1 sends a Retrieve User Equipment UE Context Request message to the access network device 120-2.
  • the UE context retrieval request message is used to request the UE context of the terminal equipment 110-1.
  • Access network device 120-1 receives the UE context from access network device 120-2.
  • the UE context request is similar to the UE context request described in FIG. 4A or FIG. 4B , and will not be repeated here.
  • the access network device 120 - 1 sends update information or release indication information to the core network device 130 .
  • the update information or release indication information is similar to the RRC update information or release indication information described in FIG. 4A or FIG. 4B , and will not be repeated here.
  • the access network device 120-1 sends an RRC release message to the terminal device 110-1.
  • the RRC release message is similar to the RRC release message described in FIG. 4A or FIG. 4B , and will not be repeated here.
  • FIG. 8 shows a schematic diagram of the flow of an exemplary communication method 800 .
  • the method 800 is implemented at a core network device, for example, the core network device 130 .
  • the access network device 120 - 1 sends update information to the core network device 130 .
  • the content included in the update information is similar to the update information sent (2020) described in FIG. 2 , and will not be repeated here.
  • the content included in the update information is similar to the update information sent (3020) described in FIG. 3 , and will not be repeated here.
  • the core network device 130 updates the connection management state of the terminal device 110-1 according to the update information.
  • the core network device 130 may update the connection management state of the terminal device 110-1 to the CM_IDLE state.
  • the core network device 130 receives a request from the access network device 120-1 for the identification of the terminal device 110-1. This request is similar to the request for the identification of the terminal device 110-1 described with reference to FIG. 3 , and will not be repeated here.
  • the core network device 130 sends a paging message for the terminal device 110-1 to the access network device 120-1.
  • the paging message is similar to the paging message described with reference to FIG. 2 or FIG. 3 , and will not be repeated here.
  • FIG. 9 shows a schematic diagram of the flow of an exemplary communication method 900 .
  • the method 900 is implemented at a core network device, for example, the core network device 130 .
  • the core network device 130 receives update information or release indication information from the access network device 120-1.
  • the update information or release indication information is similar to the RRC update information or release indication information described in FIGS. 4A and 4B , and will not be repeated here.
  • the core network device 130 updates the connection management status of the terminal device 110-1. For example, if the core network device 130 receives update information, the core network device 130 updates the address of the access network device and the I-RNTI of the terminal device according to the update information. Optionally, if the core network device 130 receives the release indication information, the core network device 130 may delete the address of the access network device 120-2. The core network device 130 may also delete the I-RNTI of the terminal device.
  • FIG. 10 shows a schematic diagram of the flow of an exemplary communication method 1000 .
  • the method 1000 is implemented at a terminal device, for example, the terminal device 110-1.
  • the terminal device 110-1 receives an RRC release message from the access network device 120-1.
  • the RRC release message is similar to the RRC release message described with reference to FIG. 2 and FIG. 3 , and will not be repeated here.
  • the terminal device 110-1 receives a radio access network paging message.
  • the radio access network paging message includes the I-RNTI of the terminal device 110-1.
  • the paging message is similar to the paging message described with reference to FIG. 2 and FIG. 3 , and will not be repeated here.
  • FIG. 11A to 11F show schematic block diagrams of communication devices according to some embodiments of the present disclosure.
  • the communication means may be implemented as a device or a chip in a device, and the scope of the present disclosure is not limited in this respect.
  • a device 1100 includes a sending unit 1101 and a receiving unit 1102 .
  • the sending unit 1101 is configured to send update information to core network devices.
  • the update information includes the address of the access network device and the inactive wireless network temporary identifier I-RNTI of the terminal device.
  • the receiving unit 1102 is configured to receive a paging message corresponding to a terminal device from a core network device.
  • the sending unit 1101 is further configured to send a radio access network paging message to a terminal device.
  • the radio access network paging message includes the I-RNTI. It can be understood that the device 1100 may further include other units for implementing the method shown in FIG. 5 , such as a processing unit.
  • a device 1110 includes a sending unit 1111 and a receiving unit 1112 .
  • the sending unit 1111 is configured to send update information to core network devices.
  • the update information includes the address of the access network device.
  • the sending unit 1111 is also configured to send a request for terminal device identification to the core network device.
  • the receiving unit 1112 is configured to receive a response message from a core network device.
  • the response message includes the Temporary Mobile Station Identity TMSI of said terminal device.
  • the receiving unit 1112 is further configured to receive a paging message corresponding to the terminal device from the core network device.
  • the paging message includes the TMSI.
  • the sending unit 1111 is also configured to send a wireless access network paging message.
  • the radio access network paging message includes the inactive radio network temporary identifier I-RNTI of the terminal equipment. It can be understood that the device 1110 may further include other units for implementing the method shown in FIG. 6 , such as a processing unit.
  • the device 1120 includes a sending unit 1121 and a receiving unit 1122 .
  • the receiving unit 1122 is configured to receive a radio resource control recovery request from a terminal device.
  • the radio resource control recovery request includes the first identifier allocated to the terminal device by the second network device.
  • the sending unit 1121 is configured to send a UE context retrieval request message to the second access network device.
  • the UE context retrieval request message is used to request the context of the terminal equipment.
  • the sending unit 1121 is further configured to send update information or release indication information to the core network device.
  • the update information indicates at least one of the following items: the address of the first access network device, or the second identifier assigned to the terminal device by the first access network device.
  • the release instruction information indicates to release at least one of the following: the address of the second network device, or the first identifier.
  • the sending unit 1121 is further configured to send a radio resource control release message to the terminal device.
  • the radio resource control release message includes the second identifier. It can be understood that the device 1120 may further include other units for implementing the method shown in FIG. 7 , such as a processing unit.
  • the device 1130 includes a sending unit 1131 , a receiving unit 1132 and a processing unit 1133 .
  • the receiving unit 1132 is configured to receive update information from the access network device.
  • the update information includes at least the address of the access network device.
  • the processing unit 1133 is configured to update the connection management state of the terminal device according to the update information.
  • the sending unit 1131 is configured to send a paging message corresponding to the terminal device to the access network device according to the address. It can be understood that the device 1130 may also include other units for implementing the method shown in FIG. 8 .
  • the device 1140 includes a receiving unit 1142 and a processing unit 1143 .
  • the receiving unit 1142 is configured to receive update information or release instruction information from the first access network device.
  • the update information indicates at least one of the following items: the address of the first access network device, or the second identifier assigned to the terminal device by the first access network device.
  • the release instruction information indicates to release at least one of the following items: the address of the second network device, or the first identifier assigned to the terminal device by the second access network device.
  • the processing unit 1143 is configured to update the connection management state of the terminal device according to the update information or the release instruction information. It can be understood that the device 1140 may also include other units for implementing the method shown in FIG. 9 .
  • the device 1150 includes a receiving unit 1151 .
  • the receiving unit 1151 is configured to receive a radio resource control release message from an access network device.
  • the radio resource control release message includes the I-RNTI of the terminal device and the discontinuous reception configuration.
  • the discontinuous reception period is greater than a predetermined length.
  • the radio resource control state between the terminal device and the access network device is a radio resource control inactive state.
  • the connection management state between the terminal device and the core network device is the connection management idle state.
  • the receiving unit 1151 is also configured to receive radio access network paging messages.
  • the radio access network paging message includes the I-RNTI. It can be understood that the device 1150 may further include other units for implementing the method shown in FIG. 10 , such as a processing unit.
  • FIG. 12 is a simplified block diagram of an example device 1200 suitable for implementing embodiments of the present disclosure.
  • the device 1200 may be used to implement a terminal device, an access network device, or a core network device as shown in FIG. 1 .
  • device 1200 includes one or more processors 1210 , one or more memories 1220 coupled to processors 1210 , and communication module 1240 coupled to processors 1210 .
  • the communication module 1240 can be used for two-way communication.
  • the communication module 1240 may have at least one communication interface for communication.
  • Communication interfaces may include any interface necessary to communicate with other devices.
  • the processor 1210 can be any type suitable for the local technology network, and can include but not limited to at least one of the following: a general purpose computer, a special purpose computer, a microcontroller, a digital signal processor (Digital Signal Processor, DSP), or a control based One or more of the multi-core controller architectures of the processor.
  • Device 1200 may have multiple processors, such as application specific integrated circuit chips, that are time slaved to a clock that is synchronized to a main processor.
  • Memory 1220 may include one or more non-volatile memories and one or more volatile memories.
  • non-volatile memory include but are not limited to at least one of the following: read-only memory (Read-Only Memory, ROM) 1224, erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), flash memory, hard disk , Compact Disc (CD), Digital Video Disk (Digital Versatile Disc, DVD) or other magnetic and/or optical storage.
  • Examples of volatile memory include, but are not limited to, at least one of: Random Access Memory (RAM) 1222, or other volatile memory that does not persist for the duration of a power outage.
  • RAM Random Access Memory
  • the computer program 1230 comprises computer-executable instructions executed by the associated processor 1210 .
  • the program 1230 can be stored in the ROM 1220.
  • Processor 1210 may perform any suitable actions and processes by loading program 1230 into RAM 1220.
  • Embodiments of the present disclosure may be implemented by means of a program 1230 such that the device 1200 may perform any process as discussed with reference to FIGS. 2 to 10 .
  • Embodiments of the present disclosure can also be realized by hardware or by a combination of software and hardware.
  • program 1230 may be tangibly embodied on a computer-readable medium, which may be included in device 1200 (such as in memory 1220 ) or other storage device accessible by device 1200 .
  • Program 1230 may be loaded from a computer readable medium into RAM 1222 for execution.
  • the computer readable medium may include any type of tangible nonvolatile memory such as ROM, EPROM, flash memory, hard disk, CD, DVD, and the like.
  • the various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other pictorial representation, it should be understood that the blocks, devices, systems, techniques or methods described herein can be implemented as, without limitation, Exemplary, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium.
  • the computer program product comprises computer-executable instructions, eg included in program modules, which are executed in a device on a real or virtual processor of a target to perform the process/method as above with reference to FIGS. 2-10 .
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or divided as desired among the program modules.
  • Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.
  • Computer program codes for implementing the methods of the present disclosure may be written in one or more programming languages. These computer program codes can be provided to processors of general-purpose computers, special-purpose computers, or other programmable data processing devices, so that when the program codes are executed by the computer or other programmable data processing devices, The functions/operations specified in are implemented.
  • the program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
  • computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above.
  • carriers include signals, computer readable media, and the like.
  • signals may include electrical, optical, radio, sound, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
  • a computer readable medium may be any tangible medium that contains or stores a program for or related to an instruction execution system, apparatus, or device.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More detailed examples of computer-readable storage media include electrical connections with one or more wires, portable computer diskettes, hard disks, random storage access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash), optical storage, magnetic storage, or any suitable combination thereof.

Landscapes

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

Abstract

本公开的实施例提供了用于寻呼的方法以及相关联的通信装置、介质和芯片。根据本公开的实施例，接入网设备向核心网设备发送包括该接入网设备的地址和终端设备标识的信息。核心网设备基于该接入网设备的地址来确定寻呼的区域，并且向接入网设备发送包括该终端设备标识的寻呼消息。该接入网设备向该终端设备发送无线接入网络寻呼消息。以此方式，可以减少核心网设备需要寻呼的区域，从而避免了不必要的寻呼资源浪费。

Description

用于寻呼的方法以及相关联的通信装置、介质和芯片 技术领域
本公开涉及通信领域，并且更具体地，涉及寻呼的方法以及相关联的通信装置、介质和芯片。
背景技术
终端设备与接入网络设备之间可以建立无线资源控制(Radio Resource Control，RRC)连接。RRC连接的状态包括RRC连接(RRC_CONNECTED)态。当终端设备处于RRC_CONNECTED状态时，终端设备已建立了RRC上下文，终端设备与网络之间建立通信所必需的全部参数均已为通信双方所知。RRC上下文是终端设备与网络之间建立通信的关键参数，具体包括安全上下文、用户设备(User Equipment，UE)能力信息等。RRC连接的状态还包括RRC空闲(RRC_IDLE)态。当终端设备处于RRC_IDLE状态时，其特征是终端设备未保留RRC上下文。在新无线电(New Radio，NR)系统引入了一种新的RRC状态，即RRC非激活态(RRC_INACTIVE)。RRC_INACTIVE态只能从RRC_CONNECTED通过RRC release消息转变，在终端设备从RRC_CONNECTED状态释放到RRC_INACTIVE状态时，网络设备会分配该终端设备一个标识非激活态无线网络临时标识(Inactive Radio Network Temporary Identity，I-RNTI)，并且以此标识存储UE的上下文，此网络设备也叫做终端设备的上一个服务(Last Serving)下一代节点B(Next Generation Node B，gNB)，有时也被记为锚点gNB(Anchor gNB)。当终端设备请求恢复之前挂起的RRC连接或者进行无线接入网络通知区域(Radio Access Network(RAN)Notification Area，RNA)更新时，终端设备发送消息给当前网络设备。终端设备也可以与核心网设备建立信令连接。例如，终端设备可以与接入和移动管理功能(Access and Mobility Management Function，AMF)实体建立信令连接。终端设备与AMF之间的连接状态可以被称为连接管理(Connection Management，CM)状态。CM状态可以包括CM连接(CM_CONNECTED)态以及CM空闲(CM_IDLE)态。根据传统的技术方案，当终端设备处于RRC_INACTIVE态和RRC_CONNECTED态时，终端设备和AMF之间的CM状态为CM_CONNECTED态，当终端设备处于RRC_IDLE态时，终端设备和AMF之间的CM状态为CM_IDLE态。
此外，为了节约终端设备的功率，提出了非连续接收(Discontinuous Reception，DRX)机制。DRX机制可以让终端设备周期性的在某些时候进入睡眠状态(sleep mode)，不去监听下行链路控制信道，而需要监听的时候，则从睡眠状态中唤醒(wake up)，这样就可以使终端设备达到省电的目的。而终端设备处于睡眠状态时可能会发生传输失败问题，例如，当终端设备处于CM_CONNECTED态且RRC_INACTIVE态时，由于终端设备处于CM_CONNECTED态，在发送数据后核心网设备需要开启与终端设备相关的重新传输定时器，然而由于终端设备也处于RRC_INACTIVE态，该终端设备会进入睡眠状态不去监听下行链路控制信道，这会造成终端设备在重新传输定时器期满前无法监听下行链路控制信道，从而导致数据的传输失败。
发明内容
本公开的示例实施例提供了在通信系统中寻呼的方案。
在本公开的第一方面，提供了一种用于通信的方法。该方法包括接入网设备向核心网设备发送更新信息。更新信息包括接入网设备的地址以及终端设备的非激活态无线网络临时标识I-RNTI。该方法还包括接入网设备接收来自核心网设备的对应于终端设备的寻呼消息。该方法还包括接入网设备向终端设备发送无线接入网络寻呼消息。无线接入网络寻呼消息包括I-RNTI。也就是说，本公开的第一方面提出了终端设备可以处于CM_IDLE且RRC_INACTIVE态。在这样的状态下，由于是CM_IDLE状态，因此核心网设备的重新传输定时器不会开启，即使终端设备处于睡眠状态而无法及时地接收数据，也不会导致因定时器期满的数据的传输失败。进一步地，本公开的第一方面提出了用于终端设备的新的寻呼过程可以实现对于CN_IDLE且RRC_INACTIVE态的终端设备的寻呼。在该寻呼过程中，如果接入网设备确定终端设备的RRC状态需要更新，接入网设备向核心网设备发送更新信息，从而触发核心网设备处终端设备的CM状态的更新。在更新终端设备的CM状态后，核心网设备根据更新信息中所指示的接入网设备和终端设备的对应关系向接入网设备发送对终端设备的寻呼消息。接入网设备继而向终端设备发送无线接入网络寻呼消息，而非核心网寻呼。由此，在终端设备处于CM_IDLE且RRC_INACTIVE态时，接入网设备可以应用本申请提供方法寻呼所述终端设备，避免了由于核心网设备的重新传输定时器期满而造成的数据传输失败，并且，进一步地，核心网设备还可以根据接入网设备的地址来确定寻呼的区域实现了对终端设备的无线接入网络寻呼，从而提高了寻呼的效率，使得终端设备可以快速地接入通信网络。可以理解，本公开的第一方面提出的寻呼过程还可以适用于处于其他状态的终端设备，不局限于处于CM_IDLE且RRC_INACTIVE态的终端设备。
在某些实施例中，对应于终端设备的寻呼消息包括I-RNTI。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域，并使能终端设备启动RRC连接恢复过程，根据I-RNTI取回存储在接入网设备的UE上下文，使得终端设备能够快速恢复连接。
在某些实施例中，更新信息用于指示核心网设备更新终端设备的连接管理状态。以此方式，核心网设备可以及时地更新终端设备地连接管理状态。
在某些实施例中，该方法还包括接入网设备向终端设备发送无线资源控制释放消息。该无线资源控制释放消息包括I-RNTI。换言之，接入网设备通知终端设备由该接入网设备分配给该终端设备的标识。以此方式，终端设备可以监测对应于该终端设备的寻呼消息。
在某些实施例中，无线资源控制释放消息还包括以下至少一项：非连续接收周期(扩展的非连续接收(extended Discontinuous Reception，eDRX)周期和/或DRX周期)，寻呼时间窗口(Page Time Window，PTW)长度，RNA信息，RNA更新周期。当非连续接收周期(例如，eDRX周期)大于预定长度。以此方式，终端设备可以进入CM_IDLE且RRC_INACTIVE态。
在某些实施例中，接入网设备的地址为接入网设备的IP地址、或接入网设备所在的无线接入网络的地址。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域。
在本公开的第二方面，提供了一种用于通信的方法。该方法包括接入网设备向核心网设备发送更新信息，其中更新信息包括接入网设备的地址。该方法还包括接入网设备向核心网设备发送对于终端设备标识的请求。该方法还包括接入网设备接收来自核心网设备的响应消息。响应消息包括终端设备的临时移动台标识(Temporary Mobile Subscriber Identity，TMSI)。 该方法还包括接入网设备接收来自核心网设备的对应于终端设备的寻呼消息。寻呼消息包括TMSI。该方法还包括接入网设备发送无线接入网络寻呼消息。无线接入网络寻呼消息包括终端设备的非激活态无线网络临时标识I-RNTI。也就是说，如果接入网设备确定终端设备的RRC状态需要更新，接入网设备向核心网设备发送更新信息，从而触发核心网设备处终端设备的CM状态的更新。接入网设备还向核心网设备请求该终端设备的标识。核心网设备根据更新信息以及所请求的终端设备标识来向接入网设备发送对终端设备的寻呼消息。在接收来自核心网设备的寻呼消息后，接入网设备向终端设备发送无线接入网络寻呼消息。由此，在终端设备处于CM_IDLE且RRC_INACTIVE态时，核心网设备根据接入网设备的地址来确定寻呼的区域，从而提高了寻呼的效率，使得终端设备可以快速地接入通信网络。
在某些实施例中，方法还包括接入网设备根据TMSI和I-RNTI的第一对应关系来确定I-RNTI。在本公开的某些方面，对应于终端设备的寻呼消息还包括：第一指示信息。该第一指示信息指示接入网设备通过无线接入网络寻呼消息寻呼该终端设备。终端设备根据该第一指示信息确定应该对终端设备进行无线接入网络寻呼，而非核心网寻呼。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域，并使能UE终端设备RRC连接恢复过程，根据I-RNTI取回存储在接入网设备的UE上下文，使得UE能够快速恢复连接。
在某些实施例中，方法还包括：接入网设备存储第一对应关系。以此方式，核心网设备可以实现在无线网络通知区域进行寻呼。
在某些实施例中，更新信息用于指示核心网设备更新终端设备的连接管理状态。以此方式，核心网设备可以及时地更新终端设备地连接管理状态。
在某些实施例中，方法还包括：接入网设备向终端设备发送无线资源控制释放消息。该无线资源控制释放消息至少包括I-RNTI、非连续接收DRX周期，扩展的非连续接收eDRX周期，PTW长度，RNA信息，RNA更新周期。当非连续接收周期大于预定长度。换言之，接入网设备通知终端设备由该接入网设备分配给该终端设备的标识。以此方式，核心网设备可以及时地更新终端设备地连接管理状态。
在某些实施例中，接入网设备的地址为接入网设备的IP地址、或接入网设备所在的无线接入网络的地址。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域。
在本公开的第三方面，提供了一种用于通信的方法。该方法包括第一接入网设备接收来自终端设备的无线资源控制恢复请求。无线资源控制恢复请求包括由第二网络设备分配给终端设备的第一标识。该方法还包括第一接入网设备向第二接入网设备发送取回用户设备UE上下文请求消息。该方法还包括第一接入网设备向核心网设备发送更新信息或释放指示信息，更新信息指示以下至少一项：第一接入网设备的地址，或由第一接入网设备分配给终端设备的第二标识，释放指示信息指示释放以下至少一项：第二网络设备的地址，TMSI或第一标识，或者与第二网络设备的地址，和/或第一标识对应的索引值。该方法还包括第一接入网设备向终端设备发送无线资源控制释放消息，其中无线资源控制释放消息包括第二标识。也就是说，当终端设备的服务接入网设备从第二接入网设备变为第一接入网设备时，第一接入网设备根据其自身的相关能力来通知核心网设备更新信息或释放资源。例如，如果第一接入网设备也能够支持eDRX，则第一接入网设备通知核心网设备存储该第一接入网设备的信息，以用于后续寻呼。例如，如果第一接入网设备不能够支持eDRX，则第一接入网设备通知核心网设备删除先前关于第二接入网设备的信息。由此，核心网设备能够及时地更新相关信息，以用于后续过程，例如寻呼过程等。
在某些实施例中，更新信息被承载在路径切换请求中。以此方式，可以节省信令开销。
在本公开的第四方面，提供了一种用于通信的方法。该方法包括核心网设备接收来自接入网设备的更新信息。更新信息至少包括接入网设备的地址。该方法还包括核心网设备根据更新信息来更新终端设备的连接管理状态。该方法还包括核心网设备根据地址向接入网设备发送对应于终端设备的寻呼消息。也就是说，核心网设备根据来自接入网设备的更新信息来触发终端设备的CM状态的更新。在更新终端设备的CM状态后，核心网设备根据更新信息中所包括的接入网设备的地址信息向接入网设备发送对终端设备的寻呼消息。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域，从而减少了资源浪费。
在某些实施例中，更新信息还包括终端设备的非激活态无线网络临时标识I-RNTI，以及针对终端设备的寻呼消息包括I-RNTI。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域，并使能终端设备启动RRC连接恢复过程，根据I-RNTI取回存储在接入网设备的UE上下文，使得UE能够快速恢复连接。
在某些实施例中，方法还包括：核心网设备接收来自接入网设备的针对终端设备的标识的请求。该方法还包括核心网设备向接入网设备发送针对终端设备的寻呼消息。寻呼消息包括TMSI。针对终端设备的寻呼消息包括：由终端设备的临时移动台标识TMSI、以及指示在无线接入网络通知区域内进行寻呼的指示信息。以此方式，接入网设备根据接收到的寻呼信息来确定对终端设备进行无线接入网络通知寻呼，从而提高了寻呼的效率。
在某些实施例中，方法还包括：接入网设备的地址为接入网设备的IP地址、或接入网设备所在的无线接入网络的地址。以此方式，核心网设备根据接入网设备的地址减少了寻呼的区域。
在本公开的第五方面，提供了一种用于通信的方法。该方法包括核心网设备接收来自第一接入网设备的更新信息或释放指示信息。更新信息指示以下至少一项：第一接入网设备的地址，或由第一接入网设备分配给终端设备的第二标识，释放指示信息指示释放以下至少一项：第二网络设备的地址，TMSI或第一标识，或者与第二网络设备的地址，和/或第一标识对应的索引值。该方法还包括核心网设备根据更新信息或释放指示信息来更新终端设备的连接管理状态。以此方式，当终端设备的服务接入网设备从第二接入网设备变为第一接入网设备时，核心网设备根据第一接入网设备的相关能力来通知更新信息或释放资源。例如，如果第一接入网设备也能够支持eDRX，则第一接入网设备通知核心网设备存储该第一接入网设备的信息，以用于后续寻呼。例如，如果第一接入网设备不能够支持eDRX，则第一接入网设备通知核心网设备删除先前关于第二接入网设备的信息。由此，核心网设备能够及时地更新相关信息，以用于后续过程，例如寻呼过程等。
在某些实施例中，更新信息被承载在路径切换请求中。以此方式，可以节省信令。
在某些实施例中，第一接入网设备的地址为第一接入网设备的IP地址、或第一接入网设备所在的无线接入网络的地址。在本公开的某些方面，第一标识和第二标识是非激活态无线网络临时标识I-RNTI。
在本公开的第六方面，提供了一种用于通信的方法。该方法包括终端设备接收来自接入网设备的无线资源控制释放消息。无线资源控制释放消息包括该无线资源控制释放消息至少包括I-RNTI、非连续接收DRX周期，扩展的非连续接收eDRX周期，PTW长度，RNA信息，RNA更新周期。终端设备与接入网设备之间的无线资源控制状态为无线资源控制非激活态。终端设备与核心网设备之间的连接管理状态为连接管理空闲态。该方法还包括终端设备接收 无线接入网络寻呼消息。无线接入网络寻呼消息包括I-RNTI。以此方式，终端设备能够启动RRC连接恢复过程，并且根据I-RNTI取回存储在接入网设备的UE上下文，从而能够快速恢复连接。
在本公开的第七方面，提供一种芯片，该芯片包括处理器，还可以包括存储器，所述处理器与存储器耦合，用于执行所述存储器中存储的计算机程序或指令，使得芯片实现前述第一方面至第六方面中任一方面的任意可能的实现方式中的方法。
在本公开的第八方面，提供了一种计算机程序产品。计算机程序产品被有形地存储在计算机可读介质上并且包括计算机可执行指令，计算机可执行指令在被执行时使设备实现根据上述第一方面至第六方面中任一方面的任意一种可能的实现方式中的方法的操作。
在本公开的第九方面，提供了一种计算机可读存储介质。该计算机可读存储介质上存储有指令，当该指令在被装置的处理器执行时，使得装置实现根据上述第一方面至第六方面中任一方面的任意一种可能的实现方式中的方法的操作。
在本公开的第十方面，本申请还提供一种通信装置，该通信装置可以实现上述第一方面或第二方面或第三方面提供的任一方法所述的接入网设备。所述通信装置可以例如为基站，或为基站中的基带装置。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中接入网设备的相应功能。可选地，该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与终端设备、核心网设备等设备之间的通信。在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，所述通信装置包括发送单元(有时也称为发送模块)和接收单元(有时也称为接收模块)，这些单元可以执行上述方法示例中相应功能，例如，在实现第一方面提供的方法时，该发送单元用于向核心网设备发送更新信息。更新信息包括接入网设备的地址以及终端设备的非激活态无线网络临时标识I-RNTI。该接收单元用于接收来自核心网设备的对应于终端设备的寻呼消息。该发送单元用于向终端设备发送无线接入网络寻呼消息。无线接入网络寻呼消息包括所述I-RNTI。具体参见第一方面或第二方面或第三方面提供的方法中的描述，此处不做赘述。
在本公开的第十一方面，本申请还提供一种通信装置，该通信装置可以实现上述第四方面或第五方面提供的任一方法所述的核心网设备。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中核心网设备的相应功能。可选地，该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与终端设备、接入网设备等设备之间的通信。在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，所述通信装置包括发送单元(有时也称为发送模块)和接收单元(有时也称为接收模块)，这些单元可以执行上述方法示例中相应功能，例如，在实现 第四方面提供的方法时，该发送单元用于向核心网设备发送更新信息。该更新信息包括所述接入网设备的地址。该发送单元用于向核心网设备发送对于终端设备标识的请求。接收单元用于接收来自核心网设备的响应消息。响应消息包括所述终端设备的临时移动台标识TMSI。接收单元用于接收来自所述核心网设备的对应于终端设备的寻呼消息。寻呼消息包括所述TMSI。发送单元用于发送无线接入网络寻呼消息。无线接入网络寻呼消息包括终端设备的非激活态无线网络临时标识I-RNTI。具体参见第四方面或第五方面提供的方法中的描述，此处不做赘述。
在本公开的第十二方面，提供了一种通信装置。本申请还提供一种通信装置，该通信装置可以实现上述第六面提供的任一方法所述的接入网设备。所述通信装置可以例如为终端设备。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中终端设备的相应功能。可选地，该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与接入网设备、核心网设备等设备之间的通信。在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，所述通信装置包括发送单元(有时也称为发送模块)和接收单元(有时也称为接收模块)，这些单元可以执行上述方法示例中相应功能，例如，在实现第六方面提供的方法时，接收单元用于接收来自终端设备的无线资源控制恢复请求。无线资源控制恢复请求包括由第二网络设备分配给所述终端设备的第一标识。发送单元用于向第二接入网设备发送取回用户设备UE上下文请求消息。该取回用户设备UE上下文请求消息用于请求终端设备的上下文。发送单元用于向核心网设备发送更新信息或释放指示信息。更新信息指示以下至少一项：第一接入网设备的地址，或由第一接入网设备分配给终端设备的第二标识。释放指示信息指示释放以下至少一项：第二网络设备的地址，或第一标识。发送单元用于向所述终端设备发送无线资源控制释放消息。无线资源控制释放消息包括第二标识。具体参见第六方面提供的方法中的描述，此处不做赘述。
附图说明
结合附图并参考以下详细说明，本公开各实现方式的特征、优点及其他方面将变得更加明显。在此以示例性而非限制性的方式示出了本公开的若干实现方式，在附图中：
图1示出了可以在其中实现本公开的实施例的通信系统的示意框图；
图2示出了根据本公开的一些实施例的通信过程的交互信令图；
图3示出了根据本公开的另一些实施例的通信过程的交互信令图；
图4A和图4B示出了根据本公开的又一些实施例的通信过程的交互信令图；
图5示出了根据本公开的一些实施例的在接入网设备处实现的流程图；
图6示出了根据本公开的另一些实施例的在接入网设备处实现的流程图；
图7示出了根据本公开的又一些实施例的在接入网设备处实现的流程图；
图8示出了根据本公开的一些实施例的在核心网设备处实现的流程图；
图9示出了根据本公开的另一些实施例的在核心网设备处实现的流程图；
图10示出了根据本公开的一些实施例的在终端设备处实现的流程图；
图11A至图11F分别示出了根据本公开的一些实施例的通信装置的示意框图；以及
图12示出了适合实现本公开的实施例的示例设备的简化框图。
在各个附图中，相同附图标记表示相同元素。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中显示了本公开的某些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
在本公开的实施例的描述中，术语“包括”及其类似用语应当理解为开放性包含，即“包括但不限于”。术语“根据”应当理解为“至少部分地根据”。术语“一个实施例”或“该实施例”应当理解为“至少一个实施例”。在本申请实施例中，对于一种技术特征，通过“第一”和“第二”等区分该种技术特征中的技术特征，该“第一”和“第二”描述的技术特征间无先后顺序或者大小顺序。下文还可能包括其他明确的和隐含的定义。
本公开的实施例可以根据任何适当的通信协议来实施，包括但不限于，第四代(Fourth Generation，4G)和第五代(Fifth Generation，5G)等蜂窝通信协议、诸如电气与电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)802.11等的无线局域网通信协议、和/或目前已知或者将来开发的任何其他协议。本公开实施例的技术方案应用于遵循任何适当的通信系统，例如：通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、频分双工(Frequency Division Duplex，FDD)系统、时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunications Service，UMTS)、窄带物联网(Narrowband Internet Of Things，NB-IoT)通信系统、未来的第五代(5G)系统或新无线(New Radio，NR)，等等。
出于说明的目的，下文中将5G的第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)通信系统为背景来描述本公开的实施例。然而，应当理解，本公开的实施例不限于被应用到5G的3GPP通信系统，而是可以被应用到任何存在类似问题的通信系统中，例如无线局域网(Wireless Local Area Network，WLAN)、有线通信系统、或者将来开发的其他通信系统等。
在本公开中使用的术语“终端设备”指能够与网络设备之间进行有线或无线通信的任何终端设备。本申请实施例涉及到的终端设备还可以称为终端，可以是一种具有无线收发功能的设备，其可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是用户设备(User Equipment，UE)，其中，UE包括具有无线通信功能的手持式设备、车载设备、可穿戴设备或计算设备。示例性地，UE可以是手机(Mobile Phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(Smart City)中的无线终端、智慧家庭(Smart Home)中的无线终端等等。本申请实施例中，用于实现终端的功能的装置可以是终端；也可以是能够支持终端实现该功能的装置，例如芯片系统，该装置可以被安装在终端中。本申请实施例中， 芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端的功能的装置是终端，以终端是UE为例，描述本申请实施例提供的技术方案。
在本公开中使用的术语“网络设备”是可以用于与终端设备通信的实体或节点。本申请实施例涉及到的网络设备包括接入网设备，例如基站可以是一种部署在无线接入网中能够和终端进行无线通信的设备。其中，基站可能有多种形式，比如宏基站、微基站、中继站和接入点等。示例性地，本申请实施例涉及到的基站可以是5G中的基站或LTE中的基站，其中，5G中的基站还可以称为发送接收点(Transmission Reception Point，TRP)或gNB。本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备，以网络设备是基站为例，描述本申请实施例提供的技术方案。
本公开中使用的术语“核心网(Core Network，CN)设备”可以为CN设备在不同的系统对应不同的设备。比如在第三代(Third Generation，3G)通信系统中可以对应通用分组无线服务技术(General Packet Radio Service，GPRS)的服务支持节点(Serving GPRS Support Node，SGSN)和/或GPRS的网关支持节点(Gateway GPRS Support Node，GGSN)。在4G通信系统中可以对应移动管理实体(Mobility Management Entity，MME)和/或服务网关(Serving Gateway，S-GW)。在5G通信系统中可以对应接入和移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)或者用户面功能(User plane Function，UPF)。
本申请实施例提供的技术方案可以应用于通信设备间的无线通信。通信设备间的无线通信可以包括：网络设备和终端间的无线通信、网络设备和网络设备间的无线通信以及终端和终端间的无线通信。其中，在本申请实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描述为“数据传输”、“信息传输”或“传输”。
如上所述，RRC连接的状态可以包括RRC_IDLE态、RRC_CONNECTED态以及RRC_INACTIVE态。CM状态可以包括CM连接(CM_CONNECTED)态以及CM空闲(CM_IDLE)态。根据传统的技术方案，当终端设备处于RRC_INACTIVE态和RRC_CONNECTED态时，终端设备和AMF之间的CM状态为CM_CONNECTED态，当终端设备处于RRC_IDLE态时，终端设备和AMF之间的CM状态为CM_IDLE态。
根据传统的技术方案，当终端设备处于RRC_IDLE状态(此时终端设备为CM_IDLE状态)时，终端设备需要监听来自CN的寻呼消息，而当终端设备处于RRC INACTIVE状态时，终端设备仍然保持CM_CONNECTED状态，且终端设备可以在无线接入网络通知区域(Radio Access Network(RAN)Notification Area，RNA)内移动而不用通知NG-RAN，并且最后一个服务该终端设备的gNB保存了UE上下文，以及与终端设备相关联的服务AMF和UPF的NG连接。因此在CN看来，处于RRC_INACTIVE态的终端设备与RRC_CONNECTED态的终端设备一样，当有来自UPF的下行数据或来自AMF的下行信令时，最后一个服务该终端设备的gNB首先收到上述数据或信令，并在所述的RNA的所有小区内寻呼终端设备，也即无线接入网络(Radio Access Network，RAN)寻呼。如果RNA的小区属于其他gNB，则通过Xn口给对应的gNB发送寻呼消息。
无论终端设备是处于RRC_IDLE态或者RRC_INACTIVE态时，终端设备都需要监听来 自网络的寻呼消息，例如CN寻呼和RAN寻呼。这是因为当有业务数据到达时，网络需要寻呼端设备才能发送数据给该终端设备。为了节省功耗，终端设备会在RRC_IDLE和RRC_INACTIVE态采用DRX进行寻呼监听。每DRX周期终端设备监听一个寻呼时机(Paging Occasion，PO)。寻呼消息可在该监听时机由网络发送给终端设备，终端设备通过监听解析相应寻呼下行链路控制信息(DCI)，根据DCI指示的内容获知该终端设备是否被寻呼。
根据传统的技术方案，当非激活的eDRX周期被配置为大于预定值时(例如，10.24s)，由于终端设备和核心网设备之间依旧处于CM_CONNECTED状态，当网络触发非接入层(Non-access Stratum，NAS)流程时，AMF会开启NAS重传定时器，并通过N2接口将NAS包发送给锚点gNB，但由于终端设备可能处于休眠状态，暂时无法将消息发给终端设备。然而，由于eDRX的周期大于预定值，可能使得较长时间内无法完成消息的发送，导致NAS重传定时器超时，使得NAS流程失败。传统的方法包括延长NAS重传定时器，但是存在会导致NAS过程耗时变长等缺点。因此，可以引入CM_IDLE且(with)RRC_INACTIVE状态，使得终端设备处于CM-IDLE态，此时核心网不需要提供CM-CONNECTED时的相关服务，但是终端设备依旧处于RRC_INACTIVE状态，锚点gNB保存了UE的上下文，使得终端设备能够更快速的回到RRC_CONNECTED状态。
如上所述，来自网络的寻呼消息包括CN寻呼和RAN寻呼。CN寻呼过程中，核心网设备向接入网设备发送寻呼消息，该寻呼消息包括核心网分配给UE的(Temporary Mobile Subscriber Identity，TMSI)，以及寻呼配置信息(DRX周期长度，eDRX周期长度，PTW长度，跟踪区域(Tracking Area，TA)索引列表)，根据传统的CN寻呼，由于核心网设备不清楚终端设备驻留的接入网设备，核心网设备根据TA进行寻呼。换言之，核心网设备需要在大的范围内进行寻呼。然而，处于CM_IDLE且RRC_INACTIVE态的终端设备在RNA内，核心网设备在大的范围内进行寻呼会造成不必要的延迟和多余的信令。根据传统的RAN寻呼，核心网设备直接将数据传输到为终端设备服务的接入网设备。然而，处于CM_IDLE且RRC_INACTIVE态的终端设备与核心网没有建立连接，核心网设备无法直接将数据传输到接入网设备。换言之，传统的通信流程不适用于处于新引入状态(例如，CM_IDLE且RRC_INACTIVE态)的终端设备。因此，需要提出新的通信流程，以优化终端设备的通信。可以理解，本公开的实施例还可以适用于其他场景或通信过程中，而不局限于寻呼过程。
根据本公开的实施例，如果接入网设备确定终端设备的RRC状态需要更新，接入网设备向核心网设备发送更新信息，从而触发核心网设备处终端设备的CM状态的更新。由于更新信息能够指示的接入网设备和终端设备的对应关系，核心网设备可以确定服务于该终端设备的接入网设备。由此，即使处于CM_IDLE态，核心网设备仍然可以确定终端设备驻留的接入网设备，从而进行无线接入网络寻呼，避免了不必要的延迟和多余的信令。
图1示出了可以在其中实现本公开的实施例的通信系统100的示意图。通信系统100包括终端设备110-1、终端设备110-2、......、终端设备110-N，其可以统称为“终端设备110”，其中N为任意正整数。作为通信网络的一部分的通信系统100还包括接入网设备120-1和接入网设备120-2。终端设备可以与接入网设备彼此通信。终端设备110还可以接收来自核心网设备的消息。本文中使用的术语“实体”是指可以实现特定功能的网元。如图1所示，终端设备110与接入网设备120-1/接入网设备120-2进行通信(即，通过Uu链路)。本文中使用的术语“上行链路(Uplink，UL)数据”指由终端设备向网络设备发送的数据。本文中使用的术语“下行链路(Downlink，DL)数据”指由网络设备向终端设备发送的数据。仅作为示例，接 入网设备120-1是终端设备110-1的当前服务接入网设备，而接入网设备120-2是终端设备110-1的先前服务接入网设备。通信系统100还包括核心网设备130，例如AMF。终端设备110可以与核心网设备130建立连接。
通信系统100可以包括任何合适数目的设备和小区。在通信系统100中，终端设备110和接入网设备可以彼此通信数据和控制信息。应当理解，图1所示的多种设备的数目及其连接是为了说明的目的而给出的，没有提出任何限制。通信系统100可以包括适合于实现本公开的实施例的任何合适数目的设备和网络。
下文将参考附图来具体讨论本公开的示例实施例。为便于讨论，将参考图1的示例通信系统来描述根据本公开示例实施例的寻呼的流程以及通信实体间信令交互。应理解，本公开的示例实施例可以类似应用于其他通信系统中。
图2示出了根据本公开的一些实施例的用于寻呼的通信过程的交互200的信令图。以下将结合图1对交互200进行描述。为了描述的目的，交互200涉及终端设备110-1、接入网设备120-1以及核心网设备130。
步骤2010：接入网设备120-1确定(2010)更新终端设备110-1的RRC状态。在某些实施例中，接入网设备120-1可以确定终端设备110-1的RRC状态可以更新为RRC_INACTIVE态。例如，接入网设备120-1可以确定终端设备110-1可以从RRC_CONNECTED态更新为RRC_INACTIVE态。在某些实施例中，如果接入网设备120-1能够支持eDRX能力，接入网设备120-1可以确定为终端设备110-1配置eDRX。
步骤2020：接入网设备120-1向核心网设备130发送(2020)更新信息，相应的，核心网设备130接收来自接入网设备120-1的更新信息。该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。换言之，该更新信息可以触发核心网设备130更新该终端设备110-1的连接管理状态。
该更新信息包括该接入网设备120-1的地址。具体的，所述接入网设备120-1的地址为接入网设备120-1的IP地址或接入网设备120-1所在的无线接入网络的地址。例如，在此情况下，该更新信息可以包括该接入网设备120-1所在的RNA的RNA码。在其他实施例中，接入网设备120-1的地址可以包括与该接入网设备120-1相关联的TA信息。可以理解，接入网设备120-1的地址可以是任意合适的地址信息。以此方式，核心网设备130知道了服务该终端设备110-1的接入网设备120-1的地址。在一种可能的实现中，该更新信息可以包括该终端设备110-1的标识信息，例如I-RNTI。在这种情况下，由于更新信息既包括接入网设备120-1的地址又包括终端设备110-1的标识信息，核心网设备130可以根据接入网设备120-1的地址以及终端设备110-1的标识信息确定接入网设备120-1和终端设备110-1之间的对应关系。因此，在后续的寻呼过程中，核心网设备130可以确定所要寻呼的终端设备的服务接入网设备。
核心网设备130可以存储接收到的接入网设备120-1的地址以及该终端设备110-1的I-RNTI。以此方式，核心网设备获得接入网设备的地址，从而可以在后续的寻呼过程中基于该地址来减少寻呼的区域。
如上所述，该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。在此情况下，核心网设备130根据该更新信息来更新该终端设备110-1的连接管理状态。该更新信息可以被看作是一种隐式的指示，即，预定义或预配置核心网设备130在接收到该更新信息后，要将CM_CONNECTED态更新为CM_IDLE态。例如，由于更新信息包括该终端设备的I-RNTI，核心网设备130可以基于该I-RNTI和I-RNTI与TMSI的映射关系来 确定该终端设备的TMSI。进而，核心网设备130可以将该终端设备110-1从CM_CONNECTED态更新为CM_IDLE态。
可选的，还包括步骤2030：接入网设备120-1向终端设备110-1发送(2030)RRC释放消息，相应的，终端设备110-1接收来自接入网设备120-1的RRC释放消息。该RRC释放消息包括该终端设备110-1的I-RNTI。该终端设备110-1可以根据该I-RNTI确定后续的寻呼消息是否与该终端设备110-1相关联。该RRC释放消息还可以包括DRX的配置。例如，DRX的配置还包括以下至少一项：DRX的周期或eDRX的周期，PTW长度，RNA信息，RNA更新周期。如上所述，接入网设备120-1可以确定为终端设备110-1配置eDRX，在此情况下，该RRC释放消息可以指示eDRX的周期大于预定长度。
在某些实施例中，在接收到RRC释放消息后，终端设备110-1可以更新其RRC状态。例如，终端设备110-1可以从RRC_CONNECTED态更新为RRC_INACTIVE态。在这种情况下，终端设备110-1可以基于寻呼消息被唤醒。以此方式，终端设备可以进入CM_IDLE且RRC_INACTIVE态。
可以理解，更新信息的发送(2020)和RRC释放消息的发送(2030)的顺序不限定于图2示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送更新信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送更新信息。
步骤2040：核心网设备130向接入网设备120-1发送(2040)针对终端设备110-1的寻呼消息，相应的，接入网设备120-1接收来自核心网设备的针对终端设备110-1的寻呼消息。该寻呼消息可以包括该终端设备110-1的I-RNTI。核心网设备130可以根据该终端设备110-1的临时移动台标识TMSI以及存储的I-RNTI和TMSI的之间的对应关系来确定该终端设备110-1的I-RNTI。可以理解，核心网设备130还可以存储其他终端设备(例如，终端设备110-2)的TMSI和I-RNTI的对应关系。该TMSI可以包括以下至少一项：5G系统架构演进(System Architecture Evolution，SAE)临时移动台标识(5G SAE Temporary Mobile Station Identifier，5G-S-TMSI)，5G-TMSI，5G全球唯一临时UE标识(5G Globally Unique Temporary UE Identity,5G-GUTI)，全球唯一临时UE标识GUTI。5G-S-TMSI是缩短版的5G-GUTI，例如，该5G-GUTI格式可以以如下方式表示：<5G-GUTI>＝<GUAMI><5G-TMSI>，其中，<GUAMI>＝<MCC><MNC><AMF Identifier>，而<AMF Identifier>＝<AMF Region ID><AMF Set ID><AMF Pointer>，而演进分组系统(Evolved Packet System，EPS)下使用的GUTI格式为：<GUTI>＝<MCC><MNC><MME Group ID><MME Code><M-TMSI>。以此方式，接入网设备120-1可以基于存储的I-RNTI和TMSI之间的对应关系来确定接收到的寻呼消息是用于哪个终端设备的。
步骤2050：接入网设备120-1向终端设备110-1发送(2050)无线接入网络(RAN)寻呼消息，相应的，终端设备110-1接收来自接入网设备120-1的RAN寻呼消息。该无线接入网络寻呼消息包括该终端设备110-1的I-RNTI。终端设备110-1可以监听来自接入网设备120-1的无线接入网络寻呼消息。如果终端设备110-1监听到的无线接入网络寻呼消息包括该终端设备110-1的I-RNTI，则终端设备110-1可以确定该寻呼消息是针对其本身的。如上所述，终端设备110-1处于RRC_INACTIVE态，该终端设备110-1可以基于该寻呼消息被唤醒，以接收来自接入网设备120-1的后续数据或信令，或者向接入网设备120-1发起RRC连接恢复过程，建立RRC连接。以此方式，终端设备启动RRC连接恢复过程，并且根据I-RNTI 确定存储在接入网设备的UE上下文，从而快速恢复连接。
根据图2所示的实施例，如果接入网设备确定终端设备的RRC状态需要更新，接入网设备向核心网设备发送更新信息，从而触发核心网设备更新终端设备的CM状态。进一步，核心网设备还可以根据更新信息中所包括的接入网设备的地址信息向接入网设备发送对终端设备的寻呼消息。换言之，核心网设备明确地知道服务要寻呼的终端设备的接入网设备，因此，即使核心网设备与终端设备之间没有建立CM连接，核心网设备仍无需进行大范围的核心网寻呼，只需向该接入网设备发送寻呼消息，避免了不必要的延迟和多余的信令。接入网设备向终端设备发送无线接入网络寻呼消息。由此，核心网设备根据接入网设备的地址减少了寻呼的区域，从而减少了资源浪费。此外，终端设备可根据寻呼消息中包括的I-RNTI来取回存储在接入网设备的UE上下文，从而实现快速恢复RRC连接。由此，也可以减少由RRC恢复过程造成的延迟，使得接入网设备能够及时地为终端设备提供服务，提高用户体验。
如图2所示的实施例中，来自接入网设备的更新信息既包括接入网设备120-1的地址又包括终端设备110-1的I-RNTI。可选的，在其他实施例中，该更新信息可以包括接入网设备120-1的地址而不包括终端设备110-1的I-RNTI。例如，图3示出了根据本公开的一些实施例的用于寻呼的通信过程的交互300的信令图，其中更新信息不包括终端设备110-1的I-RNTI。以下将结合图1对交互300进行描述。为了描述的目的，交互300涉及终端设备110-1、接入网设备120-1以及核心网设备130。
步骤3010：接入网设备120-1确定(3010)更新终端设备110-1的RRC状态。步骤3010与参考图2描述的步骤2010类似，在此不再赘述。
步骤3020：接入网设备120-1向核心网设备130发送(3020)更新信息，相应的，核心网设备130接收来自接入网设备120-1的更新信息。该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。换言之，该更新信息可以触发核心网设备130更新该终端设备110-1的连接管理状态。具体的更新过程将在下面描述。
该更新信息包括该接入网设备120-1的地址。具体的，该接入网设备120-1的地址为接入网设备120-1的IP地址或该接入网设备120-1所在的无线接入网络的地址。例如，在此情况下，该更新信息可以包括该接入网设备120-1所在的RNA的RNA码。在其他实施例中，接入网设备120-1的地址可以包括与该接入网设备120-1相关联的TA信息。可以理解，接入网设备120-1的地址可以是其他合适的地址信息。
如上所述，该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。在此情况下，核心网设备130根据该更新信息来更新该终端设备110-1的连接管理状态。该更新信息可以被看作是一种隐式的指示，即，预定义或预配置核心网设备130在接收到该更新信息后，要将CM_CONNECTED态更新为CM_IDLE态。
步骤3030：接入网设备120-1向核心网设备130发送(3030)对于终端设备110-1标识的请求，相应的，核心网120接收来自接入网设备120-1的对于终端设备110-1标识的请求。所述对于终端设备标识的请求可以为第一请求，所述第一请求用于请求终端设备的标识，具体的，所述第一请求用于请求终端设备的TMSI，也可以理解为所述第一请求用于请求核心网设备为所述终端设备分配TMSI。可选的，该请求可以包括该终端设备110-1的上下文(Context)的标识。可以理解，对于终端设备110-1标识的请求可以与更新信息在相同或不同的消息中发送。本文中使用的术语“上下文”或“UE上下文”包括终端设备在通信过程中所需要的信息，例如用户标识，跟踪区域列表和通信过程中的安全算法。
在其他实施例中，该请求可以包括无线接入网络通知区域用户设备下一代应用协议标识(Radio Access Network Notification Area User Equipment Next Generation Application Protocol Identity,RAN UE NGAP ID)。该RAN UENGAP ID在接入网设备120-1内通过NG接口唯一地标识该终端设备110-1。当核心网设备130接收到RAN UE NGAP ID时，核心网设备130将在该终端设备110-1的与终端设备110-1相关联的逻辑NG连接期间存储该ID。
在此情况下，由于上述更新信息包括接入网设备120-1的地址以及上述请求中包括终端设备110-1标识(例如，上下文标识或RAN UENGAP ID)，核心网设备130可以知道接入网设备120-1和终端设备110-1之间的对应关系。因此，当核心网设备130需要寻呼所述终端设备110-1时，可以确定所述终端设备110-1的服务接入网设备为接入网设备120-1。在这种情况下，由于上述更新信息包括接入网设备120-1的地址并且该接入网设备120-1请求终端设备110-1标识，核心网设备130可以将该终端设备110-1从CM_CONNECTED态更新为CM_IDLE态。
步骤3040：核心网设备130向接入网设备120-1发送(3040)响应消息，相应的，接入网设备120-1接收来自核心网设备130的响应消息。该响应消息包括该终端设备110-1的临时移动台标识TMSI(例如，5G-S-TMSI)。例如，如上所述，上述请求包括上下文标识，在此情况下，该响应消息包括与上述请求中的上下文标识相对应的该终端设备110-1的TMSI。在其他实施例中，如上所述，上述请求包括RAN UENGAP ID，在此情况下，由于核心网设备130维护了{AMF UE NGAP ID，RAN UE NGAP ID，TMSI}的映射关系，因此，该响应消息包括与上述请求中RAN UE NGAP ID相对应的该终端设备110-1的TMSI。接入网设备120-1可以存储终端设备110-1的TMSI和I-RNTI的对应关系。在其他实施例中，接入网设备120-1还可以存储其他终端设备(例如，终端设备110-2)的TMSI和I-RNTI的对应关系。
可选的，还包括步骤3050：接入网设备120-1向终端设备110-1发送(3050)RRC释放消息，相应的，终端设备110-1接收该RRC释放消息。该RRC释放消息包括该终端设备110-1的I-RNTI。该RRC释放消息还包括DRX的配置。例如，该DRX的配置可以包括以下至少一项：DRX的周期或eDRX的周期，PTW长度，RNA信息，RNA更新周期。如上所述，接入网设备120-1可以确定为终端设备110-1配置eDRX，在此情况下，该RRC释放消息可以指示eDRX的周期大于预定长度。
在某些实施例中，在接收到RRC释放消息后，终端设备110-1可以更新其RRC状态。例如，终端设备110-1可以从RRC_CONNECTED态更新为RRC_INACTIVE态。在这种情况下，终端设备110-1可以基于寻呼消息被唤醒。以此方式，终端设备可以进入CM_IDLE且RRC_INACTIVE态。
可以理解，更新信息的发送(3020)和RRC释放消息的发送(3050)的顺序不限定于图3示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送更新信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送更新信息。
步骤3060：核心网设备130向接入网设备120-1发送(3060)针对终端设备110-1的寻呼消息，相应的，接入网设备120-1接收来自核心网设备的针对终端设备110-1的寻呼消息。该寻呼消息可以包括该终端设备110-1的TMSI。该寻呼消息还包括第一指示信息。该第一指示信息指示接入网设备120-1通过无线接入网络寻呼消息寻呼该终端设备110-1。例如，第一指示信息可以是通过设计新的寻呼消息，比如新的消息类型值来指示。
在某些实施例中，第一指示信息也可以是在寻呼消息中添加新的信元(Information Element，IE)。例如，寻呼消息可以包括1比特指示，使得支持该功能的接入网设备，也就是能够识别出该1比特指示信息的接入网设备，能够明白需要将接收到的S-TMSI转化为I-RNTI，然后进行RAN寻呼。
在其他实施例中，第一指示信息可以是隐式指示，例如，通过新的寻呼消息格式来指示在无线接入网络通知区域内进行寻呼。接入网设备120-1可以根据指示信息来确定接收到的寻呼消息的类型。
可选的，还包括步骤3070：接入网设备120-1可以根据TMSI和I-RNTI的对应关系来确定(3070)该终端设备110-1的I-RNTI。该对应关系还可以包括多个TMSI和多个I-RNTI之间的对应关系。例如，该对应关系可以包括终端设备110-1的TMSI和I-RNTI的对应关系以及终端设备110-2的TMSI和I-RNTI的对应关系。在此情况下，接入网设备120-1可以根据该对应关系来确定寻呼消息包括的TMSI对应的I-RNTI。
步骤3080：接入网设备120-1向终端设备110-1发送(3080)无线接入网络(RAN)寻呼消息，相应的，终端设备110-1接收来自接入网设备120-1的RAN寻呼消息。该无线接入网络寻呼消息包括该终端设备110-1的I-RNTI。终端设备110-1可以监听来自接入网设备120-1的无线接入网络寻呼消息。如果终端设备110-1监听到的无线接入网络寻呼消息包括该终端设备110-1的I-RNTI，则终端设备110-1可以确定该寻呼消息是针对其本身的。如上所述，终端设备110-1处于RRC_INACTIVE态，该终端设备110-1可以基于该寻呼消息被唤醒，以接收来自接入网设备120-1的后续数据或信令。以此方式，终端设备启动RRC连接恢复过程，并且根据I-RNTI确定存储在接入网设备的UE上下文，从而快速恢复连接。
根据图3所示的实施例，如果接入网设备确定终端设备的RRC状态需要更新，接入网设备向核心网设备发送更新信息，从而触发核心网设备处终端设备的CM状态的更新。该接入网设备还向核心网设备请求该终端设备的标识。接入网设备存储其自身分配给终端设备的标识与核心网设备分配给该终端设备的标识之间的对应关系。核心网设备向接入网设备发送包括核心网设备分配给该终端设备的标识的寻呼消息。接入网设备根据上述对应关系和接收的寻呼消息确定其自身分配给终端设备的标识，并且向终端设备发送包括其自身分配给终端设备的标识的寻呼消息。换言之，不需要核心网设备对核心网寻呼过程进行额外的处理，接入网设备自主地完成从核心网寻呼到无线接入网络寻呼的转换。此外，由于更新信息也包括接入网设备的地址，核心网设备根据该地址减少了寻呼的区域。此外，终端设备可根据寻呼消息中包括的I-RNTI来取回存储在接入网设备的UE上下文，从而实现快速恢复RRC连接。由此，也可以减少由RRC恢复过程造成的延迟，使得接入网设备能够及时地为终端设备提供服务，提高用户体验。
在某些实施例中，终端设备在RNA更新定时器计时结束或者检测到RNA发生变更时，需要进行RNA更新。例如，图4A示出了根据本公开的一些实施例的用于RNA更新的通信过程的交互400的信令图。以下将结合图1对交互400进行描述。为了描述的目的，交互400涉及终端设备110-1、接入网设备120-1、接入网设备120-2以及核心网设备130。例如，终端设备110-1在RNA更新定时器计时结束或者检测到RNA发生变更时，需要进行RNA更新，此时，假设接入网设备120-2为最后服务的接入网设备。
如果接入网设备120-2支持eDRX，则终端设备110-1可以处于CM_IDLE且RRC_INACTIVE态。步骤4010：终端设备110-1向接入网设备120-1发送(4010)RRC恢复 请求来进行RNA更新，相应的，接入网设备120-1接收来自终端设备110-1的RRC恢复请求。该RRC恢复请求可以用于将终端设备110-1从RRC_INACTIVE态转换为RRC_CONNECTED态。该RRC恢复请求包括由接入网设备120-2分配给该终端设备110-1的I-RNTI。
步骤4020：接入网设备120-1向接入网设备120-2发送(4020)取回用户设备UE上下文请求消息，相应的，接入网设备120-2接收来自接入网设备120-1的取回用户设备UE上下文请求消息。该取回用户设备UE上下文请求消息用于请求对于该终端设备110-1的UE上下文。
步骤4030：接入网设备120-2向接入网设备120-1发送(4030)该终端设备110-1的UE上下文，相应的，接入网设备120-1接收来自接入网设备120-2的该终端设备110-1的UE上下文。
如果接入网设备120-1能够支持eDRX能力，接入网设备120-1可以确定为终端设备110-1配置eDRX。在此情况下，步骤4040：接入网设备120-1向核心网设备130发送(4040)更新信息，相应的，核心网设备130接收来自接入网设备120-1的更新信息。该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。
该更新信息指示接入网设备120-1的地址。具体的，接入网设备120-1的地址为接入网设备120-1的IP地址或该接入网设备120-1所在的无线接入网络的地址。例如，在此情况下，该更新信息可以包括该接入网设备120-1所在的RNA的RNA码。该更新信息还可以指示由接入网设备120-1分配给该终端设备110-1的I-RNTI。在某些实施例中，该更新信息可以在新的信令中被发送。可选的，该更新信息可以被承载在路径切换请求消息中。核心网设备130可以基于该更新信息来确定该终端设备110-1的连接管理状态仍为CM_IDLE态。换言之，该更新信息可以被看作是一种隐式的指示，即，预定义或预配置核心网设备130在接收到该更新信息后，要将CM_CONNECTED态更新为CM_IDLE态。以此方式，接入网设备通知了核心网设备的更新的信息，使得核心网设备能够及时地更新寻呼UE的锚节点信息等。
可选的，还可以包括步骤4050：接入网设备120-1向终端设备110-1发送(4050)RRC释放消息，相应的，终端设备110-1接收来自接入网设备120-1的RRC释放消息。该RRC释放消息还包括DRX的配置。例如，该DRX的配置可以包括DRX的周期，eDRX的周期，PTW长度，RNA信息，RNA更新周期。如上所述，接入网设备120-1可以确定为终端设备110-1配置eDRX，在此情况下，该RRC释放消息可以指示eDRX的周期大于预定长度。在接收到RRC释放消息后，终端设备110-1可以确定其状态为RRC_INACTIVE态。在这种情况下，终端设备110-1可以基于寻呼消息被唤醒。由此，终端设备可以依旧处于CM_IDLE且RRC_INACTIVE态。
可以理解，更新信息的发送(4040)和RRC释放消息的发送(4050)的顺序不限定于图4A示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送更新信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送更新信息。接入网设备120-1将终端设备110-1释放到CM_IDLE且RRC_INACTIVE态。换言之，通过RRC释放消息，终端设备110-1被释放到CM_IDLE且RRC_INACTIVE态。具体地，终端设备110-1接收到RRC释放消息后，该终端设备110-1获得上述的DRX配置，例如DRX的周期，eDRX的周期，PTW长度，RNA信息，RNA更新周期。
步骤4060：接入网设备120-1告知(4060)接入网设备120-2来释放终端设备110-1的 资源。
根据图4A所示的实施例，当终端设备的服务接入网设备从接入网设备120-2变为接入网设备120-1时，如果接入网设备120-1和接入网设备120-2具有类似的能力(例如，均支持eDRX)，则接入网设备120-1通知核心网设备130存储该接入网设备120-1的信息，以用于后续寻呼。由此，核心网设备能够及时地更新相关信息，以用于后续过程，例如寻呼过程等。此外，终端设备仍可以处于在CM_IDLE且RRC_INACTIVE态。
在图4A所示的实施例中，接入网设备120-1和接入网设备120-2均支持eDRX。可选的，在其他实施例中，接入网设备120-1和接入网设备的支持的DRX能力可以不同。例如，图4B示出了根据本公开的一些实施例的用于RNA更新的通信过程的交互400的信令图，其中接入网设备120-1和接入网设备的支持的DRX能力可以不同。以下将结合图1对交互400进行描述。为了描述的目的，交互400涉及终端设备110-1、接入网设备120-1、接入网设备120-2以及核心网设备130。例如，终端设备110-1在RNA更新定时器计时结束或者检测到RNA发生变更时，需要进行RNA更新，此时，假设接入网设备120-2为最后服务的接入网设备。
步骤4010：终端设备110-1向接入网设备120-1发送(4010)RRC恢复请求来进行RNA更新，相应的，接入网设备120-1接收来自终端设备110-1的RRC恢复请求。步骤4020：接入网设备120-1向接入网设备120-2发送(4020)取回用户设备UE上下文请求消息。取回用户设备UE上下文请求消息用于请求该终端设备110-1的上下文，相应的，接入网设备120-2接收来自接入网设备120-1的取回用户设备UE上下文请求消息。步骤4030：接入网设备120-2向接入网设备120-1发送(4030)该终端设备110-1的UE上下文，相应的，接入网设备120-1接收来自接入网设备120-2的该终端设备110-1的UE上下文。以上过程与参照图4A所描述的类似，在此不再赘述。
在某些实施例中，接入网设备120-1不能够支持eDRX能力。或者，即使接入网设备120-1能够支持eDRX能力，但接入网设备120-1确定不为终端设备110-1配置eDRX。在此情况下，步骤4045：接入网设备120-1向核心网设备130发送(4045)释放指示信息。该释放指示信息可以指示删除接入网设备120-2的地址。具体的，接入网设备120-2的地址可以包括接入网设备120-2的IP地址或该接入网设备120-1所在的无线接入网络的地址。例如，在此情况下，该释放指示信息可以包括该接入网设备120-1所在的RNA的RNA码。该释放指示信息还可以指示由接入网设备120-2分配给该终端设备110-1的I-RNTI或者核心网设备130分配给该终端设备110-1的TMSI。可选的，该释放指示信息还可以包括与第二网络设备的地址，和/或第一标识对应的索引值。例如，接入网设备120-2以及核心网设备130存储的每套{第二网络设备的地址，第一标识}都有具有第一个索引值。在此情况下，该释放指示信息可以包括相应的索引值，由此，核心网设备130可以删除与该索引值相关联的{第二网络设备的地址，第一标识}。核心网设备130可以确定该终端设备110-1的连接管理状态从CM_IDLE态更新为CM_CONNECTED态。该释放指示信息还可以指示接入网设备120-1不支持eDRX，或者该接入网设备120-1不配置eDRX。换言之，该释放指示信息可以被看作是一种隐式的指示，即，预定义或预配置核心网设备130在接收到该释放指示信息后，要将CM_IDL态更新为CM_CONNECTEDE态。例如，由于释放指示信息指示了终端设备的标识信息(例如，I-RNTI、TMSI或索引值等)，则核心网设备130可以基于该标识信息来确定该终端设备110-1。进而，核心网设备130可以将该终端设备110-1从CM_IDLE态转变为CM_CONNECTED态。以此 方式，接入网设备120-1通知了核心网设备的应该删除的信息，从而及时删除无效信息，释放存储空间。
可选的，还包括步骤4055：接入网设备120-1向终端设备110-1发送(4055)RRC释放消息，相应的，终端设备110-1接收来自接入网设备120-1的RRC释放消息。该RRC释放消息还包括DRX的配置。例如，该DRX的配置可以包括DRX的周期，eDRX的周期，PTW长度，RNA信息，RNA更新周期。如上所述，接入网设备120-1可以确定不为终端设备110-1配置eDRX，在此情况下，该RRC释放消息可以指示DRX的周期小于预定长度。在接收到RRC释放消息后，终端设备110-1可以确定其状态为RRC_INACTIVE态。在这种情况下，终端设备110-1可以基于寻呼消息被唤醒。以此方式，终端设备可以更新为CM_CONNECTED且RRC_INACTIVE态。
可以理解，释放指示信息的发送(4045)和RRC释放消息的发送(4055)的顺序不限定于图4B示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送释放指示信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送释放指示信息。接入网设备120-1将终端设备110-1释放到CM_CONNECTED且RRC_INACTIVE态。换言之，通过RRC释放消息，终端设备110-1被释放到CM_CONNECTED且RRC_INACTIVE态。具体地，终端设备110-1接收到RRC释放消息后，该终端设备110-1获得上述的DRX配置，例如DRX的周期，eDRX的周期，PTW长度，RNA信息，RNA更新周期。
步骤4060：接入网设备120-1告知(4060)接入网设备120-2来释放终端设备110-1的资源。
根据图4B所示的实施例，当终端设备的服务接入网设备从接入网设备120-2变为接入网设备120-1时，如果接入网设备120-1的能力不同于接入网设备120-2(例如，接入网设备120-2支持eDRX而接入网设备120-1不支持eDRX)，则接入网设备120-1备通知核心网设备130删除先前关于接入网设备120-2的信息，以用于后续寻呼。以此方式，接入网设备120-1通知了核心网设备的应该删除的信息，从而及时删除无效信息，释放存储空间。
可以理解，上述参照图2至图4B所描述的实施例可以以任意方式组合实现，或者独立地实现。本公开的实施例在此方面不受限制。
图5给出了一种示例的通信方法500的流程的示意图。方法500实现在接入网设备处，例如，接入网设备120-1。
在某些实施例中，接入网设备120-1可以确定更新终端设备110-1的RRC状态。例如，接入网设备120-1可以确定终端设备110-1的RRC状态可以更新为RRC_INACTIVE态。在某些实施例中，如果接入网设备120-1能够支持eDRX能力，接入网设备120-1可以确定为终端设备110-1配置eDRX。
在框510处，接入网设备120-1向核心网设备130发送更新信息。该更新信息包括该接入网设备120-1的地址。该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。该更新信息所包括的内容与参数图2描述的发送(2020)的更新信息类似，在此不再赘述。
在某些实施例中，接入网设备120-1向终端设备110-1发送RRC释放消息。该RRC释放消息包括该终端设备110-1的I-RNTI。该RRC释放消息所包括的内容与参数图2描述的RRC释放消息类似，在此不再赘述。
可以理解，更新信息的发送和RRC释放消息的发送的顺序不限定于图5示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送更新信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送更新信息。
在框530处，接入网设备120-1从核心网设备接收对应于终端设备110-1的寻呼消息。该寻呼消息可以包括该终端设备110-1的I-RNTI。该寻呼消息所包括的内容与参数图2描述的寻呼消息类似，在此不再赘述。
在框540处，接入网设备120-1向终端设备110-1发送无线接入网络寻呼消息。该无线接入网络寻呼消息包括该终端设备110-1的I-RNTI。该无线接入网络寻呼消息所包括的内容与参数图2描述的无线接入网络寻呼消息类似，在此不再赘述。
图6给出了一种示例的通信方法600的流程的示意图。方法600实现在接入网设备处，例如，接入网设备120-1。
在某些实施例中，接入网设备120-1确定更新终端设备110-1的RRC状态。例如，接入网设备120-1可以确定终端设备110-1的RRC状态可以更新为RRC_INACTIVE态。在某些实施例中，如果接入网设备120-1能够支持eDRX能力，接入网设备120-1可以确定为终端设备110-1配置eDRX。
在框610处，接入网设备120-1向核心网设备130发送更新信息。该更新信息包括该接入网设备120-1的地址。该更新信息所包括的内容与参数图3描述的发送(3020)的更新信息类似，在此不再赘述。该更新信息可以用于指示核心网设备130更新该终端设备110-1的连接管理状态。
在框620处，接入网设备120-1向核心网设备130发送对于终端设备110-1标识的请求。例如，该请求可以包括该终端设备110-1的上下文的标识。该请求所包括的内容与参数图3描述的发送(3030)的请求类似，在此不再赘述。
在框630处，接入网设备120-1接收来自核心网设备130的响应消息。该响应消息包括该终端设备110-1的临时移动台标识TMSI(例如，5G-S-TMSI)。在此情况下，接入网设备120-1可以存储终端设备110-1的TMSI和I-RNTI的映射关系。该响应消息与参数图3描述的响应消息类似，在此不再赘述。
在某些实施例中，接入网设备120-1向终端设备110-1发送RRC释放消息。该RRC释放消息包括该终端设备110-1的I-RNTI。该RRC释放消息所包括的内容与参数图3描述的RRC释放消息类似，在此不再赘述。可以理解，更新信息的发送和RRC释放消息的发送的顺序不限定于图3示出的顺序，其可以是任意合适的顺序。例如，接入网设备120-1可以先发送更新信息再发送RRC释放消息。在其他实施例中，接入网设备120-1可以先发送RRC释放消息再发送更新信息。
在框640处，接入网设备120-1从核心网设备130接收对应于终端设备110-1的寻呼消息。该寻呼消息与参数图3描述的寻呼消息类似，在此不再赘述。
在框650处，接入网设备120-1向终端设备110-1发送无线接入网络寻呼消息。该无线接入网络寻呼消息包括该终端设备110-1的I-RNTI。接入网设备120-1可以根据TMSI和I-RNTI的对应关系来确定该终端设备110-1的I-RNTI。该无线接入网络寻呼消息与参数图3描述的无线接入网络寻呼消息类似，在此不再赘述。
图7给出了一种示例的通信方法700的流程的示意图。方法700实现在接入网设备处，例如，接入网设备120-1。
在框710处，接入网设备120-1接收来自终端设备110-1的RRC恢复请求来进行RNA更新。该RRC恢复请求包括由接入网设备120-2分配给该终端设备110-1的I-RNTI。该RRC恢复请求与参数图4A或图4B描述的RRC恢复请求类似，在此不再赘述。
在框720处，接入网设备120-1向接入网设备120-2发送取回用户设备UE上下文请求消息。该取回用户设备UE上下文请求消息用于请求该终端设备110-1的UE上下文。接入网设备120-1接收来自接入网设备120-2的UE上下文。该UE上下文的请求与参数图4A或图4B描述的UE上下文的请求类似，在此不再赘述。
在框730处，接入网设备120-1向核心网设备130发送更新信息或释放指示信息。该更新信息或释放指示信息与参数图4A或图4B描述的RRC更新信息或释放指示信息类似，在此不再赘述。
在框740处，接入网设备120-1向终端设备110-1发送RRC释放消息。该RRC释放消息与参数图4A或图4B描述的RRC释放消息类似，在此不再赘述。
图8给出了一种示例的通信方法800的流程的示意图。方法800实现在核心网设备处，例如，核心网设备130。
在框810处，接入网设备120-1向核心网设备130发送更新信息。可选的，该更新信息所包括的内容与参数图2描述的发送(2020)的更新信息类似，在此不再赘述。在其他实施例中，更新信息所包括的内容与参数图3描述的发送(3020)的更新信息类似，在此不再赘述。
在框820处，核心网设备130根据该更新信息来更新该终端设备110-1的连接管理状态。例如，核心网设备130可以将该终端设备110-1的连接管理状态更新为CM_IDLE态。
在某些实施例中，核心网设备130接收来自接入网设备120-1的对终端设备110-1的标识的请求。该请求与参照图3描述的对终端设备110-1的标识的请求类似，在此不再赘述。
在框830处，核心网设备130向接入网设备120-1发送针对终端设备110-1的寻呼消息。该寻呼消息与参照图2或图3描述的寻呼消息类似，在此不再赘述。
图9给出了一种示例的通信方法900的流程的示意图。方法900实现在核心网设备处，例如，核心网设备130。
在框910，核心网设备130接收来自接入网设备120-1的更新信息或释放指示信息。该更新信息或释放指示信息与参数图4A和4B描述的RRC更新信息或释放指示信息类似，在此不再赘述。
在框920处，核心网设备130更新该终端设备110-1的连接管理状态。例如，如果核心网设备130接收到更新信息，则核心网设备130根据更新信息来更新接入网设备的地址以及终端设备的I-RNTI。可选的，如果核心网设备130接收到释放指示信息，则核心网设备130可以删除接入网设备120-2的地址。核心网设备130还可以删除终端设备的I-RNTI。
图10给出了一种示例的通信方法1000的流程的示意图。方法1000实现在终端设备处，例如，终端设备110-1。
在框1010处，终端设备110-1接收来自接入网设备120-1的RRC释放消息。该RRC释放消息与参照图2和图3所描述的RRC释放消息类似，在此不再赘述。
在框1020处，终端设备110-1接收无线接入网络寻呼消息。该无线接入网络寻呼消息包括该终端设备110-1的I-RNTI。该寻呼消息与参照图2和图3所描述的寻呼消息类似，在此不再赘述。
图11A至图11F示出了根据本公开的一些实施例的通信装置的示意框图。通信装置可以被实现为设备或者设备中的芯片，本公开的范围在此方面不受限制。
如图11A所示，设备1100包括发送单元1101和接收单元1102。该发送单元1101被配置为向核心网设备发送更新信息。更新信息包括所述接入网设备的地址以及终端设备的非激活态无线网络临时标识I-RNTI。该接收单元1102被配置为接收来自核心网设备的对应于终端设备的寻呼消息。该发送单元1101还被配置为向终端设备发送无线接入网络寻呼消息。无线接入网络寻呼消息包括所述I-RNTI。可以理解，设备1100还可以包括用于实现图5所示的方法的其他单元，例如处理单元。
如图11B所示，设备1110包括发送单元1111和接收单元1112。该发送单元1111被配置为向核心网设备发送更新信息。该更新信息包括所述接入网设备的地址。该发送单元1111还被配置为向核心网设备发送对于终端设备标识的请求。接收单元1112被配置为接收来自核心网设备的响应消息。响应消息包括所述终端设备的临时移动台标识TMSI。接收单元1112还被配置为接收来自所述核心网设备的对应于终端设备的寻呼消息。寻呼消息包括所述TMSI。发送单元1111还被配置为发送无线接入网络寻呼消息。无线接入网络寻呼消息包括终端设备的非激活态无线网络临时标识I-RNTI。可以理解，设备1110还可以包括用于实现图6所示的方法的其他单元，例如处理单元。
如图11C所示，设备1120包括发送单元1121和接收单元1122。接收单元1122被配置为接收来自终端设备的无线资源控制恢复请求。无线资源控制恢复请求包括由第二网络设备分配给所述终端设备的第一标识。发送单元1121被配置为向第二接入网设备发送取回用户设备UE上下文请求消息。该取回用户设备UE上下文请求消息用于请求终端设备的上下文。发送单元1121还被配置为向核心网设备发送更新信息或释放指示信息。更新信息指示以下至少一项：第一接入网设备的地址，或由第一接入网设备分配给终端设备的第二标识。释放指示信息指示释放以下至少一项：第二网络设备的地址，或第一标识。发送单元1121还被配置为向所述终端设备发送无线资源控制释放消息。无线资源控制释放消息包括第二标识。可以理解，设备1120还可以包括用于实现图7所示的方法的其他单元，例如处理单元。
如图11D所示，设备1130包括发送单元1131、接收单元1132以及处理单元1133。接收单元1132被配置为接收来自接入网设备的更新信息。该更新信息至少包括接入网设备的地址。处理单元1133被配置为根据更新信息来更新终端设备的连接管理状态。发送单元1131被配置为根据所述地址向接入网设备发送对应于终端设备的寻呼消息。可以理解，设备1130还可以包括用于实现图8所示的方法的其他单元。
如图11E所示，设备1140包括接收单元1142以及处理单元1143。接收单元1142被配置为接收来自第一接入网设备的更新信息或释放指示信息。更新信息指示以下至少一项：第一接入网设备的地址，或由第一接入网设备分配给终端设备的第二标识。释放指示信息指示释放以下至少一项：第二网络设备的地址，或由第二接入网设备分配给终端设备的第一标识。处理单元1143被配置为根据更新信息或释放指示信息来更新终端设备的连接管理状态。可以理解，设备1140还可以包括用于实现图9所示的方法的其他单元。
如图11F所示，设备1150包括接收单元1151。该接收单元1151被配置为接收来自接入网设备的无线资源控制释放消息。无线资源控制释放消息包括终端设备的I-RNTI以及非连续接收的配置。非连续接收周期大于预定长度。终端设备与接入网设备之间的无线资源控制状态为无线资源控制非激活态。终端设备与核心网设备之间的连接管理状态为连接管理空闲 态。该接收单元1151还被配置为接收无线接入网络寻呼消息。无线接入网络寻呼消息包括I-RNTI。可以理解，设备1150还可以包括用于实现图10所示的方法的其他单元，例如处理单元。
图12是适合于实现本公开的实施例的示例设备1200的简化框图。设备1200可以用于实现如图1所示的终端设备、接入网设备或核心网设备。如图所示，设备1200包括一个或多个处理器1210，耦合到处理器1210的一个或多个存储器1220，以及耦合到处理器1210的通信模块1240。
通信模块1240可以用于双向通信。通信模块1240可以具有用于通信的至少一个通信接口。通信接口可以包括与其他设备通信所必需的任何接口。
处理器1210可以是适合于本地技术网络的任何类型，并且可以包括但不限于以下至少一种：通用计算机、专用计算机、微控制器、数字信号处理器(Digital Signal Processor，DSP)、或基于控制器的多核控制器架构中的一个或多个。设备1200可以具有多个处理器，例如专用集成电路芯片，其在时间上从属于与主处理器同步的时钟。
存储器1220可以包括一个或多个非易失性存储器和一个或多个易失性存储器。非易失性存储器的示例包括但不限于以下至少一种：只读存储器(Read-Only Memory，ROM)1224、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、硬盘、光盘(Compact Disc，CD)、数字视频盘(Digital Versatile Disc,DVD)或其他磁存储和/或光存储。易失性存储器的示例包括但不限于以下至少一种：随机存取存储器(Random Access Memory，RAM)1222、或不会在断电持续时间中持续的其他易失性存储器。
计算机程序1230包括由关联处理器1210执行的计算机可执行指令。程序1230可以存储在ROM 1220中。处理器1210可以通过将程序1230加载到RAM 1220中来执行任何合适的动作和处理。
可以借助于程序1230来实现本公开的实施例，使得设备1200可以执行如参考图2至图10中所讨论的任何过程。本公开的实施例还可以通过硬件或通过软件和硬件的组合来实现。
在一些实施例中，程序1230可以有形地包含在计算机可读介质中，该计算机可读介质可以包括在设备1200中(诸如在存储器1220中)或者可以由设备1200访问的其他存储设备。可以将程序1230从计算机可读介质加载到RAM 1222以供执行。计算机可读介质可以包括任何类型的有形非易失性存储器，例如ROM、EPROM、闪存、硬盘、CD、DVD等。
通常，本公开的各种实施例可以以硬件或专用电路、软件、逻辑或其任何组合来实现。一些方面可以用硬件实现，而其他方面可以用固件或软件实现，其可以由控制器，微处理器或其他计算设备执行。虽然本公开的实施例的各个方面被示出并描述为框图，流程图或使用一些其他图示表示，但是应当理解，本文描述的框，装置、系统、技术或方法可以实现为，如非限制性示例，硬件、软件、固件、专用电路或逻辑、通用硬件或控制器或其他计算设备，或其某种组合。
本公开还提供有形地存储在非暂时性计算机可读存储介质上的至少一个计算机程序产品。该计算机程序产品包括计算机可执行指令，例如包括在程序模块中的指令，其在目标的真实或虚拟处理器上的设备中执行，以执行如上参考图2至图10的过程/方法。通常，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、库、对象、类、组件、数据结构等。在各种实施例中，可以根据需要在程序模块之间组合或分割程序模块的功能。用于程序模块的机器可执行指令可以在本地或分布式设备内执行。在分布式设备中，程序模块可 以位于本地和远程存储介质中。
用于实现本公开的方法的计算机程序代码可以用一种或多种编程语言编写。这些计算机程序代码可以提供给通用计算机、专用计算机或其他可编程的数据处理装置的处理器，使得程序代码在被计算机或其他可编程的数据处理装置执行的时候，引起在流程图和/或框图中规定的功能/操作被实施。程序代码可以完全在计算机上、部分在计算机上、作为独立的软件包、部分在计算机上且部分在远程计算机上或完全在远程计算机或服务器上执行。
在本公开的上下文中，计算机程序代码或者相关数据可以由任意适当载体承载，以使得设备、装置或者处理器能够执行上文描述的各种处理和操作。载体的示例包括信号、计算机可读介质、等等。信号的示例可以包括电、光、无线电、声音或其它形式的传播信号，诸如载波、红外信号等。
计算机可读介质可以是包含或存储用于或有关于指令执行系统、装置或设备的程序的任何有形介质。计算机可读介质可以是计算机可读信号介质或计算机可读存储介质。计算机可读介质可以包括但不限于电子的、磁的、光学的、电磁的、红外的或半导体系统、装置或设备，或其任意合适的组合。计算机可读存储介质的更详细示例包括带有一根或多根导线的电气连接、便携式计算机磁盘、硬盘、随机存储存取器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或闪存)、光存储设备、磁存储设备，或其任意合适的组合。
此外，尽管在附图中以特定顺序描述了本公开的方法的操作，但是这并非要求或者暗示必须按照该特定顺序来执行这些操作，或是必须执行全部所示的操作才能实现期望的结果。相反，流程图中描绘的步骤可以改变执行顺序。附加地或备选地，可以省略某些步骤，将多个步骤组合为一个步骤执行，和/或将一个步骤分解为多个步骤执行。还应当注意，根据本公开的两个或更多装置的特征和功能可以在一个装置中具体化。反之，上文描述的一个装置的特征和功能可以进一步划分为由多个装置来具体化。

Claims (44)

  1. 一种通信方法，其特征在于，所述方法包括：
    接入网设备向核心网设备发送更新信息，其中所述更新信息包括所述接入网设备的地址以及终端设备的非激活态无线网络临时标识I-RNTI；
    所述接入网设备接收来自所述核心网设备的对应于所述终端设备的寻呼消息；以及
    所述接入网设备向所述终端设备发送无线接入网络寻呼消息，所述无线接入网络寻呼消息包括所述I-RNTI。
  2. 根据权利要求1所述的方法，其特征在于，所述对应于所述终端设备的寻呼消息包括所述I-RNTI。
  3. 根据权利要求1或2所述的方法，其特征在于，所述更新信息用于指示所述核心网设备更新所述终端设备的连接管理状态。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述I-RNTI。
  5. 根据权利要求4所述的方法，其特征在于，所述无线资源控制释放消息还包括非连续接收的配置信息，所述非连续接收周期大于预定长度。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  7. 一种通信方法，其特征在于，所述方法包括：
    接入网设备向核心网设备发送更新信息，其中所述更新信息包括所述接入网设备的地址；
    所述接入网设备向所述核心网设备发送对于终端设备标识的请求；
    所述接入网设备接收来自所述核心网设备的响应消息，所述响应消息包括所述终端设备的临时移动台标识TMSI；
    所述接入网设备接收来自所述核心网设备的对应于所述终端设备的寻呼消息，所述寻呼消息包括所述TMSI；以及
    所述接入网设备发送无线接入网络寻呼消息，所述无线接入网络寻呼消息包括所述终端设备的非激活态无线网络临时标识I-RNTI。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述接入网设备根据所述TMSI和所述I-RNTI的第一对应关系来确定所述I-RNTI。
  9. 根据权利要求7或8所述的方法，其特征在于，所述对应于所述终端设备的寻呼消息还包括：第一指示信息，所述第一指示信息指示所述接入网设备通过无线接入网络寻呼消息寻呼所述终端设备。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述接入网设备存储所述第一对应关系。
  11. 根据权利要求7-10任一项所述的方法，其特征在于，所述更新信息用于指示所述核心网设备更新所述终端设备的连接管理状态。
  12. 根据权利要求7-11中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述I-RNTI以及非连续接收的配置信息，所述非连续接收周期大于预定长度。
  13. 根据权利要求7-12中任一项所述的方法，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  14. 一种通信方法，其特征在于，所述方法包括：
    第一接入网设备接收来自终端设备的无线资源控制恢复请求，所述无线资源控制恢复请求包括由第二网络设备分配给所述终端设备的第一标识；
    所述第一接入网设备向所述第二接入网设备发送取回用户设备UE上下文请求消息，所述取回UE上下文请求消息用于请求所述终端设备的上下文信息；
    所述接入网设备向核心网设备发送更新信息或释放指示信息，所述更新信息指示以下至少一项：所述第一接入网设备的地址，或由所述第一接入网设备分配给所述终端设备的第二标识，所述释放指示信息指示释放所述第二网络设备的地址，所述终端设备的临时移动台标识或所述第一标识，或者指示释放与所述第二网络设备的地址和所述第一标识对应的索引值；以及
    所述第一接入网设备向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述第二标识。
  15. 根据权利要求14所述的方法，其特征在于，如果所述第一接入网设备向所述核心网设备发送所述更新信息，则所述无线资源控制释放消息包括非连续接收配置信息，其中所述非连续接收配置信息用于配置非连续接收周期大于预定长度。
  16. 根据权利要求14或15所述的方法，其特征在于，所述更新信息被承载在路径切换请求中。
  17. 根据权利要求14-16中任一项所述的方法，其特征在于，所述第一标识和所述第二标识是非激活态无线网络临时标识I-RNTI。
  18. 一种用于通信的方法，其特征在于，所述方法包括：
    核心网设备接收来自接入网设备的更新信息，其中所述更新信息至少包括所述接入网设备的地址；
    所述核心网设备根据所述更新信息来更新终端设备的连接管理状态；以及
    所述核心网设备根据所述地址向所述接入网设备发送对应于所述终端设备的寻呼消息。
  19. 根据权利要求18所述的方法，其特征在于，所述更新信息还包括所述终端设备的非激活态无线网络临时标识I-RNTI，以及
    所述针对所述终端设备的寻呼消息包括所述I-RNTI。
  20. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收来自所述接入网设备的取回用户设备UE上下文请求消息，所述取回UE上下文请求消息用于请求所述终端设备的上下文信息；
    所述核心网设备向所述接入网设备发送针对所述终端设备的寻呼消息，所述寻呼消息包括所述TMSI，其中，所述针对所述终端设备的寻呼消息包括：由所述终端设备的临时移动台标识TMSI、以及指示在无线接入网络通知区域内进行寻呼的指示信息。
  21. 根据权利要求18-20中任一项所述的方法，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  22. 一种通信装置，所述通信装置包括：
    发送单元，用于向核心网设备发送更新信息，其中所述更新信息包括接入网设备的地址以及终端设备的非激活态无线网络临时标识I-RNTI；
    接收单元，用于接收来自所述核心网设备的对应于所述终端设备的寻呼消息；以及
    所述发送单元还用于向所述终端设备发送无线接入网络寻呼消息，所述无线接入网络寻呼消息包括所述I-RNTI。
  23. 根据权利要求22所述的装置，其特征在于，所述对应于所述终端设备的寻呼消息包括所述I-RNTI。
  24. 根据权利要求22或23所述的装置，其特征在于，所述更新信息用于指示所述核心网设备更新所述终端设备的连接管理状态。
  25. 根据权利要求22-24中任一项所述的装置，其特征在于，所述发送单元还用于：
    向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述I-RNTI。
  26. 根据权利要求25所述的装置，其特征在于，所述无线资源控制释放消息还包括非连续接收的配置信息，所述非连续接收周期大于预定长度。
  27. 根据权利要求22-26中任一项所述的装置，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  28. 一种通信装置，所述通信装置包括：
    发送单元，用于向核心网设备发送更新信息，其中所述更新信息包括接入网设备的地址；
    所述发送单元还用于向所述核心网设备发送对于终端设备标识的请求；
    接收单元，用于接收来自所述核心网设备的响应消息，所述响应消息包括所述终端设备的临时移动台标识TMSI；
    所述接收单元还用于接收来自所述核心网设备的对应于所述终端设备的寻呼消息，所述寻呼消息包括所述TMSI；以及
    所述发送单元还用于发送无线接入网络寻呼消息，所述无线接入网络寻呼消息包括所述终端设备的非激活态无线网络临时标识I-RNTI。
  29. 根据权利要求28所述的装置，其特征在于，所述装置还包括：
    用于根据所述TMSI和所述I-RNTI的第一对应关系来确定所述I-RNTI的单元。
  30. 根据权利要求28或29所述的装置，其特征在于，所述对应于所述终端设备的寻呼消息还包括：第一指示信息，所述第一指示信息指示所述接入网设备通过无线接入网络寻呼消息寻呼所述终端设备。
  31. 根据权利要求29或30所述的装置，其特征在于，所述装置还包括：
    用于存储所述第一对应关系的单元。
  32. 根据权利要求28-31任一项所述的装置，其特征在于，所述更新信息用于指示所述核心网设备更新所述终端设备的连接管理状态。
  33. 根据权利要求28-32中任一项所述的装置，其特征在于，所述发送单元还用于：
    向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述I-RNTI以及非连续接收的配置信息，所述非连续接收周期大于预定长度。
  34. 根据权利要求28-33中任一项所述的装置，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  35. 一种通信装置，所述通信装置包括：
    接收单元，接收来自终端设备的无线资源控制恢复请求，所述无线资源控制恢复请求包括由第二网络设备分配给所述终端设备的第一标识；
    发送单元，用于向第二接入网设备发送取回用户设备UE上下文请求消息，所述取回UE上下文请求消息用于请求所述终端设备的上下文信息；
    所述发送单元还用于向核心网设备发送更新信息或释放指示信息，所述更新信息指示以下至少一项：第一接入网设备的地址，或由所述第一接入网设备分配给所述终端设备的第二标识，所述释放指示信息指示释放所述第二网络设备的地址，所述终端设备的临时移动台标识或所述第一标识，或者指示释放与所述第二网络设备的地址和所述第一标识对应的索引值；以及
    所述发送单元还用于向所述终端设备发送无线资源控制释放消息，其中所述无线资源控制释放消息包括所述第二标识。
  36. 根据权利要求35所述的装置，其特征在于，如果所述发送单元向所述核心网设备发送所述更新信息，则所述无线资源控制释放消息包括非连续接收配置信息，其中所述非连续接收配置信息用于配置非连续接收周期大于预定长度。
  37. 根据权利要求35或36所述的装置，其特征在于，所述更新信息被承载在路径切换请求中。
  38. 根据权利要求35-37中任一项所述的装置，其特征在于，所述第一标识和所述第二标识是非激活态无线网络临时标识I-RNTI。
  39. 一种通信装置，所述通信装置包括：
    接收单元，用于接收来自接入网设备的更新信息，其中所述更新信息至少包括所述接入网设备的地址；
    处理单元，用于根据所述更新信息来更新终端设备的连接管理状态；以及
    发送单元，用于根据所述地址向所述接入网设备发送对应于所述终端设备的寻呼消息。
  40. 根据权利要求39所述的装置，其特征在于，所述更新信息还包括所述终端设备的非激活态无线网络临时标识I-RNTI，以及
    所述针对所述终端设备的寻呼消息包括所述I-RNTI。
  41. 根据权利要求39所述的装置，其特征在于，
    所述接收单元还用于接收来自所述接入网设备的取回用户设备UE上下文请求消息，所述取回UE上下文请求消息用于请求所述终端设备的上下文信息；
    所述发送单元还用于向所述接入网设备发送针对所述终端设备的寻呼消息，所述寻呼消息包括所述TMSI，其中，所述针对所述终端设备的寻呼消息包括：由所述终端设备的临时移动台标识TMSI、以及指示在无线接入网络通知区域内进行寻呼的指示信息。
  42. 根据权利要求39-41中任一项所述的装置，其特征在于，所述接入网设备的地址为所述接入网设备的IP地址、或所述接入网设备所在的无线接入网络的地址。
  43. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现根据权利要求1至6中任一项或权利要求7至13中任一项或权利要求14至17中任一项的方法所述的操作。
  44. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现根据权利要求18至21中任一项的方法所述的操作。
PCT/CN2023/070903 2022-01-14 2023-01-06 用于寻呼的方法以及相关联的通信装置、介质和芯片 WO2023134563A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23739906.8A EP4443999A1 (en) 2022-01-14 2023-01-06 Paging method, associated communication apparatus, medium, and chip
US18/770,599 US20240365286A1 (en) 2022-01-14 2024-07-11 Paging method, and associated communication apparatus, medium, and chip

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210044685.4A CN116489769A (zh) 2022-01-14 2022-01-14 用于寻呼的方法以及相关联的通信装置、介质和芯片
CN202210044685.4 2022-01-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/770,599 Continuation US20240365286A1 (en) 2022-01-14 2024-07-11 Paging method, and associated communication apparatus, medium, and chip

Publications (1)

Publication Number Publication Date
WO2023134563A1 true WO2023134563A1 (zh) 2023-07-20

Family

ID=87225560

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/070903 WO2023134563A1 (zh) 2022-01-14 2023-01-06 用于寻呼的方法以及相关联的通信装置、介质和芯片

Country Status (4)

Country Link
US (1) US20240365286A1 (zh)
EP (1) EP4443999A1 (zh)
CN (1) CN116489769A (zh)
WO (1) WO2023134563A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110832917A (zh) * 2017-02-12 2020-02-21 鸿颖创新有限公司 用于无线资源控制未致能状态之用户设备之移动管理
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
US20210259040A1 (en) * 2020-02-13 2021-08-19 Alireza Babaei Wireless Device and Wireless Network Processes in Inactive State
CN113647151A (zh) * 2019-03-28 2021-11-12 诺基亚技术有限公司 用于执行无线电接入通知区域更新的装置、方法和计算机程序

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110832917A (zh) * 2017-02-12 2020-02-21 鸿颖创新有限公司 用于无线资源控制未致能状态之用户设备之移动管理
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
CN113647151A (zh) * 2019-03-28 2021-11-12 诺基亚技术有限公司 用于执行无线电接入通知区域更新的装置、方法和计算机程序
US20210259040A1 (en) * 2020-02-13 2021-08-19 Alireza Babaei Wireless Device and Wireless Network Processes in Inactive State

Also Published As

Publication number Publication date
US20240365286A1 (en) 2024-10-31
EP4443999A1 (en) 2024-10-09
CN116489769A (zh) 2023-07-25

Similar Documents

Publication Publication Date Title
US10034327B2 (en) Method and apparatus in a telecommunication system
CN107113598B (zh) 演进分组系统中的移动台终止的通信的支持
US10484864B2 (en) Subscriber server, monitoring server, mobile terminal, methods related thereto, and computer readable medium
US11582828B2 (en) Method and device for controlling RRC state, and computer storage medium
WO2014161472A1 (zh) 一种进行寻呼的方法、装置及系统
CN107046714B (zh) 一种数据传输方法、装置和系统
EP3738355A1 (en) Rrc inactive state optimization
JPWO2016009580A1 (ja) 通信管理のための方法および装置
US20150382298A1 (en) Method and network node for setting a mobile communication terminal in an idle mode
US20230038417A1 (en) Data transmission method and apparatus
US20240224217A1 (en) Communication method, communication apparatus, and communication system
EP3525495A1 (en) Method for sending downlink data, network device and user plane device
CN113950146B (zh) 一种寻呼方法和通信装置
WO2017076156A1 (zh) 释放ue上下文及其控制方法及装置、寻呼方法及装置
WO2023134563A1 (zh) 用于寻呼的方法以及相关联的通信装置、介质和芯片
WO2021012188A1 (zh) 通信处理方法及相关设备
TW202241112A (zh) 用以處理非小資料傳輸(non-sdt)資料之方法、裝置及媒體
US11109345B2 (en) Paging for downlink data transfer in connectionless mode in a mobile system
KR20190052465A (ko) 페이징 처리 장치 및 방법
WO2017133282A1 (zh) 一种支持机器类通信设备数据传输的方法和装置
US11653307B2 (en) Modifying idle mode DRX on wireless devices
JP7098016B1 (ja) 通信システム、情報処理装置、情報処理装置の制御方法、及び通信装置
WO2023213204A1 (zh) 通信方法和装置
WO2024067502A1 (zh) 一种数据传输方法及装置
CN117641521A (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: 23739906

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023739906

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023739906

Country of ref document: EP

Effective date: 20240705

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024014199

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112024014199

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240710