[go: up one dir, main page]

WO2022120632A1 - Procédé, dispositif et support de stockage informatique de communication - Google Patents

Procédé, dispositif et support de stockage informatique de communication Download PDF

Info

Publication number
WO2022120632A1
WO2022120632A1 PCT/CN2020/134870 CN2020134870W WO2022120632A1 WO 2022120632 A1 WO2022120632 A1 WO 2022120632A1 CN 2020134870 W CN2020134870 W CN 2020134870W WO 2022120632 A1 WO2022120632 A1 WO 2022120632A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
message
connection
terminal device
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/134870
Other languages
English (en)
Inventor
Da Wang
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to PCT/CN2020/134870 priority Critical patent/WO2022120632A1/fr
Publication of WO2022120632A1 publication Critical patent/WO2022120632A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication during a paging from one of networks of multi-universal subscriber identity module (USIM) .
  • USIM multi-universal subscriber identity module
  • a multi-USIM terminal device occupies a large market share.
  • a user may have both a personal and a business subscription in one device or has two personal subscriptions in one device for different services.
  • support for multi-USIM within a terminal device is currently handled in an implementation-specific manner without any support from third generation partnership project (3GPP) specifications, resulting in a variety of implementations and behaviors at the terminal device.
  • 3GPP third generation partnership project
  • a multi-USIM terminal device may establish a connection in a network A of USIM A and stay in an idle or inactive state in a network B of USIM B.
  • the terminal device may do not want to release the connection with the network A, for example, as traffic on the network A is more important.
  • the network B will continue paging the terminal device in a larger area. This will result in resource waste.
  • embodiments of the present disclosure provide methods, devices and computer storage media of communication during a paging from one of networks of multi-USIM.
  • a method of communication comprises: receiving, at a terminal device, a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmitting, to the network device, a first message via a common control channel (CCCH) , the first message comprising an indication that the connection with the network device is not resumed.
  • CCCH common control channel
  • a method of communication comprises: receiving, at a terminal device, a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmitting, to the network device and in the same uplink resource, a first message via a CCCH and a second message via a dedicated control channel (DCCH) , the second message comprising an indication that the connection with the network device is not resumed.
  • DCCH dedicated control channel
  • a method of communication comprises: receiving, at a terminal device, a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmitting, to the network device, a fourth message indicating that a resumption of a connection with a network device is completed, the fourth message comprising an indication that the connection is to be released, the indication being visible to the network device.
  • a method of communication comprises: receiving, at a network device, a first message via a CCCH, the first message comprising an indication that the connection with the network device is not resumed.
  • a method of communication comprises: receiving, at a network device and from a terminal device, a first message via a CCCH and a second message via a DCCH, the second message comprising an indication that the connection with the network device is not resumed.
  • a method of communication comprises: receiving, at a network device and from a terminal device, a fourth message indicating that a resumption of a connection with a network device is completed, the fourth message comprising an indication that the connection is to be released, the indication being visible to the network device.
  • a terminal device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the terminal device to perform the method according to the first to third aspects of the present disclosure.
  • a network device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the network device to perform the method according to the fourth to sixth aspects of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the first to third aspects of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the fourth to sixth aspects of the present disclosure.
  • FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a schematic diagram illustrating a process for communication during a paging from one of networks of multi-USIM according to some embodiments of the present disclosure
  • FIG. 3 illustrates a schematic diagram illustrating another process for communication during a paging from one of networks of multi-USIM according to some embodiments of the present disclosure
  • FIG. 4 illustrates a schematic diagram illustrating still another process for communication during a paging from one of networks of multi-USIM according to some embodiments of the present disclosure
  • FIG. 5 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates still another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 8 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 9 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • FIG. 10 illustrates still another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • FIG. 11 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • UE user equipment
  • PDAs personal digital assistants
  • IoT internet of things
  • IoE Internet of Everything
  • MTC machine type communication
  • X means pedestrian, vehicle, or infrastructure/network
  • image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • terminal device can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , a low power node such as a femto node, a pico node, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • a low power node such as a femto node, a pico node, and the like.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different RATs.
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • SIM subscriber identity module
  • USIM USIM
  • ISIM IP multimedia service identity module
  • a multi-USIM terminal device has established a connection in a network A of USIM A and stays in an idle or inactive state in a network B of USIM B
  • the terminal device may do not want to release the connection with the network A, for example, as traffic on the network A is more important.
  • the network B will continue paging the terminal device in a larger area. This will result in resource waste.
  • the terminal device in case that the terminal device receives the paging from the network B and judges the ongoing connection in the network A more important, the terminal device sends a busy indication as a non-access stratum (NAS) message to the network B as a response to the paging.
  • the busy indication indicates that the terminal device is not available for resuming or setting up a connection with the network B.
  • the busy indication is sent by the NAS message, and thus the busy indication is only allowed to be sent as early as in a message indicating that a resumption or setting up of a connection with a network device is completed, i.e., under a radio resource control (RRC) connected state.
  • RRC radio resource control
  • the network B only releases the terminal device later after receiving this message, i.e., after entering into a RRC connected state with the terminal device.
  • the network B is not able to be aware of the busy indication. Then the network B can only generate a RRCRelease message after the core network indicates to the network B to release the terminal device.
  • Embodiments of the present disclosure provide improved solutions of communication for transmission of the busy indication.
  • embodiments of the present disclosure provide a solution for transmitting the busy indication in a message via a CCCH.
  • signaling radio bearer 0 (SRB0) is used for transmission of the busy indication.
  • the busy indication can be transmitted to the network side in a shorter time compared with the conventional solution in which the busy indication is carried in NAS message.
  • embodiments of the present disclosure provide a solution for transmitting the busy indication in a message via a DCCH together with a message via a CCCH.
  • SRB1 or SRB2 is used for transmission of the busy indication.
  • the busy indication also can be transmitted to the network side in a shorter time as that in the first aspect. Additionally, the busy indication can be ciphered.
  • embodiments of the present disclosure provide a solution for transmitting the busy indication under a RRC connected state in a message indicating that a resumption of a connection with the network B is completed, and the busy indication is visible to the RAN.
  • the RAN can release a connection with the terminal device directly upon receipt of the busy indication without waiting for an instruction from the core network.
  • the busy indication also can be transmitted to the network side in a shorter time compared with the conventional solution in which the busy indication is carried in NAS message.
  • the busy indication can be ciphered for the terminal device in an inactive state.
  • this solution needs a less modification on the specification.
  • FIG. 1 illustrates a schematic diagram of an example communication network 100 in which embodiments of the present disclosure can be implemented.
  • the communication network 100 may include a network device 110, a terminal device 120 and a further network device 130.
  • the terminal device 120 may be in an idle or inactive state with the network device 110 and in a connected state with the further network device 130.
  • the terminal device 120 may carry a first USIM card 121 and a second USIM card 122.
  • the network device 110 may serve the first USIM card 121
  • the further network device 130 may serve the second USIM card 122.
  • the first and second USIM cards 121 and 122 may also be served by the same network device such as the network device 110 or the further network device 130.
  • the following description is made under the assumption that the first network device 110 serves the first USIM card 121 and the further network device 130 serves the second USIM card 122.
  • USIM cards are merely an example, the terminal device 120 may be associated with the network device 110 and the further network device 130 in any other suitable forms.
  • the first and second USIM cards 121 and 122 may conform same or different RATs which are existing now or to be developed in the future. It should be noted that the number of the USIM cards carried by the terminal device 120 is not limited to two, and more than two USIM cards also can be applied. For convenience, the following description is given by taking two USIM cards as an example.
  • the communication network 100 may further include a third network device 140.
  • Each of the network device 110, the further network device 130 and the third network device 140 may have at least one cell (not shown) .
  • the terminal device 120 is served by the third network device 140 in a connected state, and the third network device 140 maintains a context for the terminal device 120.
  • the third network device 140 may instruct the terminal device 120 to enter into an inactive state, and then the terminal device 120 may enter into the inactive state.
  • the terminal device 120 is moving toward the network device 110, the terminal device 120 is switched to be served by the network device 110.
  • the third network device 140 may be the last serving network device maintaining the context for the terminal device 120.
  • the network device 110 may be the last serving network device maintaining the context for the terminal device 120.
  • the following description is given by taking the third network device 140 as an example of the last serving network device.
  • the communication network 100 may further include a core network 150.
  • the core network 150 may comprise an access and mobility management function (AMF) , a session management function (SMF) or the like (not shown) .
  • AMF access and mobility management function
  • SMF session management function
  • the core network 150 may comprise any other suitable core network elements.
  • the terminal device 120 may communicate with the core network 150 via any of the network device 110, the further network device 130 and the third network device 140.
  • any of the network device 110, the further network device 130 and the third network device 140 may communicate with the terminal device 120 via a channel such as a wireless communication channel.
  • a channel such as a wireless communication channel.
  • an of the first USIM 121 and the second USIM 122 may communicate with any of the network device 110, the further network device 130 and the third network device 140.
  • the communication network 100 may include any suitable number of network devices and/or terminal devices adapted for implementing implementations of the present disclosure.
  • the communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • the communications may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.
  • the terminal device 120 may receive a paging from the network device 110.
  • the terminal device 120 may decide to resume or setup a connection between the USIM card 121 and the network device 110. In some embodiments, the terminal device 120 may maintain the connection between the USIM card 122 and the further network device 130, and turn to USIM card 121 to response the paging based on a scheduling gap during which no transmission is performed between the terminal device 120 and the further network device 130.
  • the terminal device 120 upon receipt of the paging from the network device 110, the terminal device 120 would not to resume the connection with the network device 110, for example, as the ongoing connection with the further network device 130 is more important.
  • Embodiments of the present disclosure provide improved solutions for these scenarios. This will be described in more detail with reference to FIGs. 2 to 4.
  • FIG. 2 shows a schematic diagram illustrating a process 200 for communication during a paging from one of networks of multi-USIM according to embodiments of the present disclosure.
  • the process 200 will be described with reference to FIG. 1.
  • the process 200 may involve the terminal device 120, the network device 110, the third network device 140 as the last serving network device, and the core network 150 as illustrated in FIG. 1.
  • the terminal device 120 receives 210 a paging from the network device 110.
  • the core network 150 may have traffic to be transmitted to the USIM card 121 of the terminal device 120 and instruct the network device 110 to page the USIM card 121 of the terminal device 120.
  • the terminal device 120 Upon receipt of the paging, the terminal device 120 determines 220 whether a connection with the network device 110 is to be resumed. In some embodiments, the terminal device 120 may perform the determination based on incoming traffic from the network device 110 and ongoing traffic from the further network device 130. For example, the terminal device 120 may perform the determination based on the types, amounts and priorities of the incoming and ongoing traffic. It is to be understood that any other suitable factors are also feasible to be used for the determination.
  • the terminal device 120 determines that the connection with the network device 110 is not resumed, the terminal device 120 transmits 230 a message (for convenience, also referred to as a first message here) via a CCCH.
  • a message for convenience, also referred to as a first message here
  • SRB0 signaling radio bearer 0
  • the first message comprises an indication (also referred to as a busy indication here) that the connection with the network device 110 is not resumed.
  • the first message may be a message for requesting a resumption of the connection with the network device 110.
  • the terminal device 120 may transmit the first message during a 4-step random access channel (RACH) procedure.
  • the 4-step RACH procedure may involve transmission of a message 1 (msg1) and a message 3 (msg3) from the terminal device 120 to the network device 110 and transmission of a message 2 (msg2) and a message 4 (msg4) from the network device 110 to the terminal device 120 as a response to the message 1 and 3 respectively.
  • the msg1 may comprise random access preamble transmission of the random access procedure for 4-step random access (RA) type.
  • the msg2 may comprise a random access response (RAR) .
  • the msg3 may comprise first scheduled transmission of the random access procedure.
  • the msg4 may consist of a response for one or more of contention resolution, fallback indication and backoff indication.
  • the first message may be the msg3.
  • the first message will be transmitted via a CCCH using signaling radio bearer 0 (SRB0) .
  • the first message may be a RRCResumeequest or RRCResumerequest1 message.
  • the terminal device 120 may transmit the first message during a 2-step RACH procedure.
  • the 2-step random access procedure may involve transmission of a message A (msgA) from the terminal device 120 to the network device 110 and transmission of a message B (msgB) from the network device 110 to the terminal device 120 as a response to the message A.
  • the msgA may comprise random access preamble transmission and physical uplink shared channel (PUSCH) payload transmission of the random access procedure for 2-step RA type.
  • the msgB may consist of a response for one or more of contention resolution, fallback indication and backoff indication.
  • the first message may be the msgA.
  • the first message will also be transmitted via a CCCH using SRB0.
  • the first message may be a RRCResumerequest or RRCResumerequest1 message.
  • the terminal device 120 may use one spare bit in the RRCResumerequest or RRCResumerequest1 message to indicate the busy indication. For example, if the terminal device 120 decides to not resume the RRC connection with the network device 110 upon receipt of the paging, the terminal device 120 may set the spare bit as true ( “1” ) . Otherwise, the spare bit is set as false ( “0” ) . Of course, any other suitable ways are also feasible. An example of a modification for a RRCResumerequest message is listed as below.
  • the terminal device 120 may use a resume cause for the busy indication. That is, a new resume cause may be introduced in the first message for the busy indication. For example, if the terminal device 120 decides to not resume the RRC connection with the network device 110 upon receipt of the paging, the NAS layer of the terminal device 120 may provide to the RAN layer of the terminal device 120 with a resume cause for the busy indication, for example, with a resume cause as “busy” .
  • a resume cause for the busy indication for example, with a resume cause as “busy” .
  • An example of a modification for the resume cause set in the RRCResumeRequest or RRCResumeRequest1 message is listed as below.
  • ResumeCause ENUMERATED ⁇ emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess, busy, spare4, spare3, spare2, spare1 ⁇
  • the terminal device 120 may transmit a dedicated message for the busy indication. In other words, a new SRB0 message may be introduced dedicatedly for the busy indication.
  • This message itself implies that the terminal device 120 would not resume the connection with the network device 110.
  • this message may be defined as a RRCRefuseRequest message. If the terminal device 120 decides to not resume the RRC connection with the network device 110 upon receipt of the paging, the terminal device 120 may transmit the RRCRefuseRequest message to the network device 110.
  • the dedicated message may comprise identity information of the terminal device 120, also referred to as resumeIdentity here.
  • the dedicated message may further comprise authentication information for the terminal device 120, also referred to as resumeMAC-I here.
  • the dedicated message may further comprise a period during which the terminal device 120 is not available for resuming the connection with the network device 110. For example, the period may be an expected time period that the terminal device 120 is going to be busy.
  • the dedicated message may further comprise a time point at which the terminal device 120 is available for resuming the connection with the network device 110. For example, the time point may be an expected time when the terminal device 120 is not busy.
  • the spare resume cause can be reserved for further traffic type.
  • the resume cause is not necessary in this new message, resulting in more remaining bits to carry more information, which is beneficial from forward compatibility.
  • the network device 110 may transmit 240 the busy indication comprised in the first message to the core network 150 via a NG interface.
  • the NG interface denotes an interface between the RAN and the core network existing or to be developed.
  • the network device 110 may forward 240’ the busy indication to the third network device 140.
  • the network device 110 may transmit the busy indication to the third network device 140 in a RETREIVE UE CONTEXT REQUEST message.
  • the further network device 140 may transmit 240” the busy indication to the core network 150.
  • the network device 110 may transmit 250, to the terminal device 120, a message (also referred to as a third message herein) for releasing the connection with the network device 110.
  • the third message may be a RRCRelease message.
  • the network device 110 may determine that the terminal device 110 would not resume the connection with the network device 110, and thus directly transmit a RRCRelease message to the terminal device 120 without waiting for any instruction from the core network 150.
  • the network device 110 may receive 260 an instruction from the core network 150 and upon receipt of the instruction, the network device may transmit 250’ the third message to the terminal device 120.
  • the instruction may be an indication about the releasing of the connection with the network device 110 from the core network 150, for example, from the AMF of the core network 150.
  • any other suitable instructions are also feasible.
  • the terminal device 120 may release the connection with the network device 110.
  • the terminal device 120 may initiate 270 the resume or set up of the connection with the network device 110. In this way, the service of the network device 110 can be started as soon as possible.
  • the terminal device 120 transmits the busy indication to the network device 110 according to the conventional solutions (i.e., via a NAS message transparent to the RAN) and then enters into an idle state with the further network device 130, if traffic on a connection with the further network device 130 ends, the terminal device 120 may initiate the resume or setup of the connection with the network device 110. In this way, the service of the network device 110 can be started as soon as possible.
  • the terminal device 120 may start a timer upon transmission of the first message, and stop the timer upon receipt of the third message.
  • the timer may be T319 timer.
  • any other suitable timer is also feasible.
  • the design of the scheduling gap is expected to be long enough to cover the whole busy indication procedure, but it is still possible that the procedure is not finished before the scheduling gap ends.
  • the timer will keep on running until the timer expiries, as the terminal device 120 will not able to monitor the network of the USIM card 121.
  • T319 timer expires, a terminal device will go to an idle state, and the NAS layer of the terminal device will perform a NAS recovery procedure, i.e., initiate a RRC setup procedure again. This is unexpected as this may further results in service interruption in network of the USIM card 122.
  • the terminal device 120 may remain in an inactive state.
  • the terminal device 120 may reset a media access control (MAC) entity of the terminal device 120, release default MAC cell group configuration, re-establish radio link control (RLC) entities for SRB1 and suspend SRB1 or all SRBs corresponding to the network device 110.
  • MAC media access control
  • RLC radio link control
  • the terminal device 120 may enter into an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • the release cause may be set as “other” . It is to be understood that any other suitable ways of the release cause are also feasible. In this way, the NAS recovery procedure will also not be triggered, and thus further service interruption of the USIM card 122 will also be avoided.
  • the terminal device 120 can response to the paging from one of networks of multi-USIM as earlier as possible, and resource waste is avoided.
  • the busy indication is sent by SRB0 message.
  • the network side can verify the terminal device, but the busy indication information is not ciphered, this information may be obtained by an eavesdropper.
  • embodiments of the present disclosure provide a solution of transmitting the busy indication by SRB1 or SRB2 message during a RRC resume procedure. This will be described with reference to FIG. 3 below.
  • FIG. 3 illustrates a schematic diagram illustrating another process 300 for communication during a paging from one of networks of multi-USIM according to embodiments of the present disclosure.
  • the process 300 will be described with reference to FIG. 1.
  • the process 300 may involve the terminal device 120, the network device 110, the third network device 140 as the last serving network device, and the core network 150 as illustrated in FIG. 1.
  • the terminal device 120 receives 310 a paging from the network device 110.
  • the core network 150 may have a traffic to be transmitted to the USIM card 121 of the terminal device 120 and instruct the network device 110 to page the USIM card 121 of the terminal device 120.
  • the terminal device 120 Upon receipt of the paging, the terminal device 120 determines 320 whether a connection with the network device 110 is to be resumed. In some embodiments, the terminal device 120 may perform the determination based on incoming traffic from the network device 110 and ongoing traffic from the further network device 130. For example, the terminal device 120 may perform the determination based on the types, amounts and priorities of the incoming and ongoing traffic. It is to be understood that any other suitable factors are also feasible to be used for the determination.
  • the terminal device 120 determines that the connection with the network device 110 is not resumed, the terminal device 120 transmits 330 a message (for convenience, also referred to as a first message herein) via a CCCH and a message (for convenience, also referred to as a second message herein) via a DCCH in the same uplink resource.
  • the second message comprises an indication (also referred to as a busy indication here) that the connection with the network device 110 is not resumed.
  • the first message may be a message for requesting a resumption of the connection with the network device 110.
  • the second message may be a RRC message.
  • the second message may be an existing RRC message using SRB1 or SRB2.
  • the second message may be a new RRC message using SRB1 or SRB2.
  • the terminal device 120 may resume SRB1 or SRB2, perform packet data convergence protocol (PDCP) reestablishment for SRB1 or SRB2, generate and send RRCResumeRequest or RRCResumeRequest1 message together with SRB1 or SRB2 RRC message comprising the busy indication.
  • PDCP packet data convergence protocol
  • the busy indication may be a NAS message carried in the RRC message. In some embodiments, the busy indication may be carried in the RRC message directly.
  • the first and second messages may be transmitted via a configured grant (CG) resource configured for the terminal device 120 in an inactive state. In some embodiments, the first and second messages may be transmitted in Msg3 for a 4-step RACH procedure. In some embodiments, the first and second messages may be transmitted in MsgA for a 2-step RACH procedure.
  • CG configured grant
  • the network device 110 may transmit 340 the busy indication comprised in the second message to the core network 150 via the NG interface.
  • the network device 110 may forward 340’ the busy indication to the third network device 140.
  • the network device 110 may transmit the busy indication to the third network device 140 in a RETREIVE UE CONTEXT REQUEST message.
  • the third network device 140 may transmit 340” the busy indication to the core network 150.
  • the network device 110 may transmit 350, to the terminal device 120, a message (also referred to as a third message herein) for releasing the connection with the network device 110.
  • the third message may be a RRCRelease message.
  • the network device 110 may determine that the terminal device 110 would not resume the connection with the network device 110, and thus directly transmit a RRCRelease message to the terminal device 120 without waiting for any instruction from the core network 150.
  • the network device 110 may receive 360 an instruction from the core network 150 and upon receipt of the instruction, the network device may transmit 350’ the third message to the terminal device 120.
  • the instruction may be an indication about the releasing of the connection with the network device 110 from the core network 150, for example, from the AMF of the core network 150.
  • any other suitable instructions are also feasible.
  • the terminal device 120 may release the connection with the network device 110.
  • the terminal device 120 may initiate 370 the resume or set up of the connection with the network device 110. In this way, the service of the network device 110 can be started as soon as possible.
  • the terminal device 120 transmits the busy indication to the network device 110 according to the conventional solutions (i.e., via a NAS message transparent to the RAN) and then enters into an idle state with the further network device 130, if traffic on a connection with the further network device 130 ends, the terminal device 120 may initiate the resume or setup of the connection with the network device 110. In this way, the service of the network device 110 can also be started as soon as possible.
  • the terminal device 120 may start a timer upon transmission of the first message, and stop the timer upon receipt of the third message.
  • the timer may be T319 timer.
  • any other suitable timer is also feasible.
  • the terminal device 120 may remain in an inactive state. In some embodiments, the terminal device 120 may reset a media access control (MAC) entity of the terminal device 120, release default MAC cell group configuration, re-establish radio link control (RLC) entities for SRB1 and suspend SRB1 or all SRBs corresponding to the network device 110. In this way, the NAS recovery procedure will not be triggered, and thus further service interruption of the USIM card 122 will be avoided.
  • MAC media access control
  • RLC radio link control
  • the terminal device 120 may enter into an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • the release cause may be set as “other” . It is to be understood that any other suitable ways of the release cause are also feasible. In this way, the NAS recovery procedure will also not be triggered, and thus further service interruption of the USIM card 122 will also be avoided.
  • the terminal device 120 can response to the paging from one of networks of multi-USIM as earlier as possible, and resource waste is avoided. Compared with that in FIG. 2, not only shorter time is needed for transmission of the busy indication, but also the busy indication can be ciphered.
  • FIG. 4 illustrates a schematic diagram illustrating still another process 400 for communication during a paging from one of networks of multi-USIM according to embodiments of the present disclosure.
  • the process 400 may involve the terminal device 120, the network device 110 and the core network 150 as illustrated in FIG. 1.
  • the terminal device 120 receives 410 a paging from the network device 110.
  • the core network 150 may have a traffic to be transmitted to the USIM card 121 of the terminal device 120 and instruct the network device 110 to page the USIM card 121 of the terminal device 120.
  • the terminal device 120 Upon receipt of the paging, the terminal device 120 determines 420 whether a connection with the network device 110 is to be resumed. In some embodiments, the terminal device 120 may perform the determination based on incoming traffic from the network device 110 and ongoing traffic from the further network device 130. For example, the terminal device 120 may perform the determination based on the types, amounts and priorities of the incoming and ongoing traffic. It is to be understood that any other suitable factors are also feasible to be used for the determination.
  • the terminal device 120 may transmit 430 a RRCResumeRequest message to the network device 110, and receive 440 a RRCResume message from the network device 110. Then, upon resume of the connection with the network device 110, the terminal device 120 transmits 450, to the network device 110, a message (for convenience, also referred to as a fourth message herein) indicating that the resume is completed.
  • the fourth message comprises an indication (also referred to as a busy indication herein) that the connection is to be released. The indication is visible to the network device 110. In other words, the fourth message enables the network device 110 to know that the terminal device 120 expects to release the connection with the network device 110.
  • the terminal device 120 may transmit the fourth message including an information element (IE) for the indication.
  • IE information element
  • the busy indication may be added as one IE in a RRC message.
  • the busy indication may be carried in a RRCResumeComplete or RRCSetupComplete message as an IE, and thus is visible to the RAN.
  • the terminal device 120 may transmit the fourth message including a NAS message dedicated for the indication. For example, if the terminal device 120 decides to not resume or set up a RRC connection, the NAS layer of the terminal device 120 may provide a NAS message to the RRC layer of the terminal device 120, and indicate that this is the special NAS message for the busy indication. In this case, the NAS message carrying the busy indication is contained in a dedicated NAS-message container which is used for busy indication transmission only. Thus, the busy indication will be visible to the network device 110.
  • the network device 110 upon receipt of the fourth message, can know that the terminal device 120 would release the connection with the network device 110. In this case, the network device 110 transmits 460, to the terminal device 120, a message (also referred to as a third message herein) for releasing the connection with the network device 110, without waiting for any instruction from the core network 150.
  • the third message may be a RRCRelease message or any other suitable message.
  • the network device 110 may transmit 470 the busy indication to the core network 150 (for example, AMF) via the NG interface.
  • the network device 110 may forward 470’ the dedicated NAS message to the core network 150 (for example, AMF) . In this way, no NG interface enhancement is needed.
  • the terminal device 120 may release the connection with the network device 110.
  • the terminal device 120 may initiate 480 the resume or set up of the connection with the network device 110. In this way, the service of the network device 110 can be started as soon as possible.
  • the terminal device 120 can transmit a message for releasing the connection with the network device 110 without waiting for an instruction from the core network 150.
  • a shorter latency can be achieved.
  • ciphering can be applied for a terminal device in an inactive state, and thus better security can be ensured.
  • this solution is applicable to a terminal device in an idle state or in an inactive state.
  • FIGs. 2 to 4 are not always necessary for implementing embodiments of the present disclosure, and more or less actions may be adapted as needed.
  • embodiments of the present disclosure provide methods of communication implemented at a terminal device and at a network device. These methods will be described below with reference to FIGs. 5 to 10.
  • FIG. 5 illustrates an example method 500 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 500 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 500 will be described with reference to FIG. 1. It is to be understood that the method 500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 receives a paging from the network device 110.
  • the terminal device 120 determines whether a connection with the network device 110 is to be resumed. If determining that the connection with the network device 110 is not resumed, the process proceeds to block 530.
  • the terminal device 120 transmits to the network device 110, a first message via a CCCH, the first message comprising an indication that the connection with the network device is not resumed.
  • the terminal device 120 may transmit the first message including a bit as the indication.
  • the terminal device 120 may transmit the first message including a resume cause as the indication.
  • the terminal device 120 may transmit a dedicated message for the indication.
  • the dedicated message may comprise at least one of the following: identity information of the terminal device 120; or authentication information for the terminal device 120. In some embodiments, the dedicated message may further comprise at least one of the following: a period during which the terminal device 120 is not available for resuming the connection; or a time point at which the terminal device 120 is available for resuming the connection.
  • the terminal device 120 may receive, from the network device 110, a third message for releasing the connection with the network device 110, the third message being transmitted by the network device 110 upon receipt of the first message without waiting for an instruction from the core network 150. In some alternative embodiments, the terminal device 120 may receive, from the network device 110, a third message for releasing the connection with the network device 110, the third message being transmitted by the network device 110 upon receipt of an instruction from the core network 150.
  • the terminal device 120 may initiate the connection resume or set up with the network device 110.
  • the terminal device 120 may start a timer upon transmission of the first message, and stop the timer upon receipt of the third message for releasing the connection with the network device 110. In some embodiments, if the timer expires, the terminal device 120 may remain in an inactive state. In some alternative embodiments, if the timer expires, the terminal device 120 may enter an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • FIG. 6 illustrates another example method 600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 600 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 600 will be described with reference to FIG. 1. It is to be understood that the method 600 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 receives a paging from the network device 110.
  • the terminal device 120 determines whether a connection with the network device 110 is to be resumed. If determining that the connection with the network device 110 is not resumed, the process proceeds to block 630.
  • the terminal device 120 transmits a first message via a CCCH and a second message via a DCCH to the network device 110, the second message comprising an indication that the connection with the network device 110 is not resumed.
  • the terminal device 120 may receive, from the network device 110, a third message for releasing the connection with the network device 110, the third message being transmitted by the network device 110 upon receipt of the second message without waiting for an instruction from the core network 150. In some alternative embodiments, the terminal device 120 may receive, from the network device 110, a third message for releasing the connection with the network device, the third message being transmitted by the network device 110 upon receipt of an instruction from the core network 150.
  • the terminal device 120 may initiate the connection resume or set up with the network device 110.
  • the terminal device 120 may start a timer upon transmission of the first message, and stop the timer upon receipt of the third message for releasing the connection with the network device 110. In some embodiments, if the timer expires, the terminal device 120 may remain in an inactive state. In some alternative embodiments, if the timer expires, the terminal device 120 may enter an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • FIG. 7 illustrates still another example method 700 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 700 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 700 will be described with reference to FIG. 1. It is to be understood that the method 700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 receives a paging from the network device 110.
  • the terminal device 120 determines whether a connection with the network device 110 is to be resumed. If determining that the connection with the network device 110 is not resumed, the process proceeds to block 730.
  • the terminal device 120 transmits a fourth message indicating that a resumption of a connection with the network device 110 is completed, the fourth message comprising an indication that the connection is to be released, the indication being visible to the network device 110.
  • the terminal device 120 may transmit the fourth message including an IE for the indication.
  • the terminal device 120 may transmit the fourth message including a NAS message dedicated for the indication.
  • the terminal device 120 may receive, from the network device 110, a third message for releasing the connection with the network device, the third message being transmitted by the network device 120 upon receipt of the fourth message without waiting for an instruction from the core network 150.
  • the terminal device 120 may initiate the connection resume or set up with the network device 110.
  • FIG. 8 illustrates an example method 800 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 800 may be performed at the network device 110 as shown in FIG. 1.
  • the method 800 will be described with reference to FIG. 1. It is to be understood that the method 800 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 110 receives, from the terminal device 120, a first message via a CCCH.
  • the first message comprises an indication that the connection with the network device 110 is not resumed.
  • the network device 110 may receive the first message including a bit as the indication.
  • the network device 110 may receive the first message including a resume cause as the indication.
  • the network device 110 may receive a dedicated message for the indication.
  • the dedicated message may comprise at least one of the following: identity information of the terminal device 120; or authentication information for the terminal device 120. In some embodiments, the dedicated message may further comprise at least one of the following: a period during which the terminal device 120 is not available for resuming the connection; or a time point at which the terminal device 120 is available for resuming the connection.
  • the network device 110 may transmit a third message for releasing the connection with the network device 110 upon receipt of the first message without waiting for an instruction from the core network 150. In some embodiments, the network device 110 may transmit the third message upon receipt of the instruction from the core network 150. In some embodiments, the network device 110 may transmit, to the core network 150 and via a NG interface, an indication for indicating that the terminal device 120 is not available, and receive the instruction from the core network 150.
  • the network device 110 may forward the indication to the third network device 140 for transmission to the core network 150, the third network device 140 being the last serving network device for the terminal device 120.
  • FIG. 9 illustrates another example method 900 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 900 may be performed at the network device 110 as shown in FIG. 1.
  • the method 900 will be described with reference to FIG. 1. It is to be understood that the method 900 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 110 receives, from the terminal device 120, a first message via a CCCH and a second message via a DCCH.
  • the second message comprises an indication that the connection with the network device 110 is not resumed.
  • the network device 110 may transmit a third message for releasing the connection with the network device 110 upon receipt of the second message without waiting for an instruction from the core network 150. In some embodiments, the network device 110 may transmit the third message upon receipt of the instruction from the core network 150. In some embodiments, the network device 110 may transmit, to the core network 150 and via a NG interface, an indication for indicating that the terminal device 120 is not available, and receive the instruction from the core network 150.
  • the network device 110 may forward the indication to the third network device 140 for transmission to the core network 150, the third network device 140 being the last serving network device for the terminal device 120.
  • FIG. 10 illustrates still another example method 1000 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 1000 may be performed at the network device 110 as shown in FIG. 1.
  • the method 1000 will be described with reference to FIG. 1. It is to be understood that the method 1000 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 110 may receive, from the terminal device 120, a fourth message indicating that a resumption of a connection with the network device 110 is completed.
  • the fourth message comprises an indication that the connection is to be released, the indication being visible to the network device 110.
  • the network device 110 may receive the fourth message including an information element for the indication.
  • the network device 110 may receive the fourth message including a NAS message dedicated for the indication.
  • the network device 110 may transmit the indication to the core network 150 via the NG interface. In some embodiments, the network device 110 may forward the NAS message to the core network 150. In some embodiments, the network device 110 may transmit, to the terminal device 120, a third message for releasing the connection with the network device 110 upon receipt of the fourth message without waiting for an instruction from the core network 150.
  • FIG. 11 is a simplified block diagram of a device 1100 that is suitable for implementing embodiments of the present disclosure.
  • the device 1100 can be considered as a further example implementation of the network device 110 or the terminal device 120 as shown in FIG. 1. Accordingly, the device 1100 can be implemented at or as at least a part of the network device 110 or the terminal device 120.
  • the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX/RX 1140.
  • the memory 1110 stores at least a part of a program 1130.
  • the TX/RX 1140 is for bidirectional communications.
  • the TX/RX 1140 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 1130 is assumed to include program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 10.
  • the embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware.
  • the processor 1110 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1110 and memory 1120 may form processing means 1150 adapted to implement various embodiments of the present disclosure.
  • the memory 1120 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100.
  • the processor 1110 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a terminal device comprises circuitry configured to: receive a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmit, to the network device, a first message via a CCCH, the first message comprising an indication that the connection with the network device is not resumed.
  • the circuitry may be configured to at least one of the following: transmit the first message including a bit as the indication, transmit the first message including a resume cause as the indication, or transmit a dedicated message for the indication.
  • the dedicated message may comprise at least one of the following: identity information of the terminal device; or authentication information for the terminal device.
  • the dedicated message may further comprises at least one of the following: a period during which the terminal device is not available for resuming the connection; or a time point at which the terminal device is available for resuming the connection.
  • the circuitry may be further configured to receive, from the network device, a third message for releasing the connection with the network device, the third message being transmitted by the network device upon receipt of the first message without waiting for an instruction from a core network, or receive, from the network device, a third message for releasing the connection with the network device, the third message being transmitted by the network device upon receipt of an instruction from a core network.
  • the circuitry may be further configured to: in accordance with a determination that traffic on a connection with a further network device ends, initiating the connection resume or setup with the network device, the network device being associated with a first subscriber identity module of the terminal device and the further network device being associated with a second subscriber identity module of the terminal device.
  • the circuitry may be further configured to start a timer upon transmission of the first message and stop the timer upon receipt of a third message for releasing the connection with the network device. In some embodiments, the circuitry may be further configured to: in accordance with a determination that the timer expires, remaining in an inactive state, or in accordance with a determination that the timer expires, entering an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • a terminal device comprises circuitry configured to: receive a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmit, to the network device and in the same uplink resource, a first message via a CCCH and a second message via a DCCH, the second message comprising an indication that the connection with the network device is not resumed.
  • the circuitry may be further configured to: receive, from the network device, a third message for releasing the connection with the network device, the third message being transmitted by the network device upon receipt of the second message without waiting for an instruction from a core network, or receive, from the network device, a third message for releasing the connection with the network device, the third message being transmitted by the network device upon receipt of an instruction from a core network.
  • the circuitry may be further configured to: in accordance with a determination that traffic on a connection with a further network device ends, initiating the connection resume or set up with the network device, the network device being associated with a first subscriber identity module of the terminal device and the further network device being associated with a second subscriber identity module of the terminal device.
  • the circuitry may be further configured to: start a timer upon transmission of the first message; and stop the timer upon receipt of a third message for releasing the connection with the network device. In some embodiments, the circuitry may be further configured to: in accordance with a determination that the timer expires, remaining in an inactive state, or in accordance with a determination that the timer expires, entering an idle state with a release cause indicating that no NAS recovery procedure is triggered.
  • a terminal device comprises circuitry configured to:receive a paging from a network device; and in accordance with a determination that a connection with the network device is not resumed, transmit, to the network device, a fourth message indicating that a resumption of a connection with a network device is completed, the fourth message comprising an indication that the connection is to be released, the indication being visible to the network device.
  • the circuitry may be configured to at least one of the following: transmit the fourth message including an information element for the indication, or transmit the fourth message including a NAS message dedicated for the indication.
  • the circuitry may be further configured to: receive, from the network device, a third message for releasing the connection with the network device, the third message being transmitted by the network device upon receipt of the fourth message without waiting for an instruction from a core network.
  • the circuitry may be further configured to: in accordance with a determination that traffic on a connection with the further network device ends, initiate the connection resume or set up with the network device.
  • a network device comprises circuitry configured to: receive a first message via a CCCH, the first message comprising an indication that a connection with the network device is not resumed.
  • the circuitry may be configured to at least one of the following: receive the first message including a bit as the indication, receive the first message including a resume cause as the indication, or receive a dedicated message for the indication.
  • the dedicated message may comprise at least one of the following: identity information of the terminal device; or authentication information for the terminal device.
  • the dedicated message may further comprise at least one of the following: a period during which the terminal device is not available for resuming the connection; or a time point at which the terminal device is available for resuming the connection.
  • the circuitry may be further configured to: transmit a third message for releasing the connection with the network device upon receipt of the first message without waiting for an instruction from a core network, or transmit the third message upon receipt of the instruction from the core network.
  • the circuitry may be further configured to: transmit, to the core network and via a NG interface, an indication for indicating that the terminal device is not available; and receive the instruction from the core network. In some embodiments, the circuitry may be further configured to: forward the indication to a third network device for transmission to the core network, the third network device being the last serving network device for the terminal device.
  • a network device comprises circuitry configured to: receive, from a terminal device, a first message via a CCCH and a second message via a DCCH, the second message comprising an indication that a connection with the network device is not resumed.
  • the circuitry may be configured to: transmit a third message for releasing the connection with the network device upon receipt of the second message without waiting for an instruction from a core network, or transmit the third message upon receipt of the instruction from the core network.
  • the circuitry may be further configured to: transmit, to the core network and via a NG interface, an indication for indicating that the terminal device is not available; and receive the instruction from the core network. In some embodiments, the circuitry may be configured to: forward the indication to a third network device for transmission to the core network, the third network device being a last serving network device for the terminal device.
  • a network device comprises circuitry configured to: receive, from a terminal device, a fourth message indicating that a resumption of a connection with a network device is completed, the fourth message comprising an indication that the connection is to be released, the indication being visible to the network device.
  • the circuitry may be configured to at least one of the following: receive the fourth message including an information element for the indication, or receive the fourth message including a NAS message dedicated for the indication. In some embodiments, the circuitry may be further configured to at least one of the following: transmit the indication to a core network via a NG interface, or forward the NAS message to the core network.
  • the circuitry may be configured to at least one of the following: transmit, to the terminal device, a third message for releasing the connection with the network device upon receipt of the fourth message without waiting for an instruction from a core network.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • 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 embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller 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 includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 2 to 10.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports lisibles par ordinateur pour la communication. Un procédé de communication consiste à recevoir, au niveau d'un dispositif terminal, un message de radiorecherche en provenance d'un dispositif de réseau ; et en fonction d'une détermination indiquant qu'une connexion avec le dispositif de réseau n'est pas reprise, à transmettre, au dispositif de réseau, un premier message via un canal de commande commun, le premier message comprenant une indication selon laquelle la connexion avec le dispositif de réseau n'est pas reprise. À réception du premier message, le dispositif de réseau peut indiquer au dispositif terminal de libérer la connexion avec le dispositif de réseau. Ainsi, une réponse au message de radiorecherche est envoyée le plus tôt possible, ce qui évite le gaspillage de ressources.
PCT/CN2020/134870 2020-12-09 2020-12-09 Procédé, dispositif et support de stockage informatique de communication Ceased WO2022120632A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/134870 WO2022120632A1 (fr) 2020-12-09 2020-12-09 Procédé, dispositif et support de stockage informatique de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/134870 WO2022120632A1 (fr) 2020-12-09 2020-12-09 Procédé, dispositif et support de stockage informatique de communication

Publications (1)

Publication Number Publication Date
WO2022120632A1 true WO2022120632A1 (fr) 2022-06-16

Family

ID=81974112

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/134870 Ceased WO2022120632A1 (fr) 2020-12-09 2020-12-09 Procédé, dispositif et support de stockage informatique de communication

Country Status (1)

Country Link
WO (1) WO2022120632A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019056308A1 (fr) * 2017-09-22 2019-03-28 北京小米移动软件有限公司 Procédé de mise en œuvre, dispositif, équipement utilisateur et station de base pour une mise à jour de zone de localisation
US20200100207A1 (en) * 2017-03-23 2020-03-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Paging method and paging appartus
US20200120749A1 (en) * 2017-08-04 2020-04-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data processing method and related device
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200100207A1 (en) * 2017-03-23 2020-03-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Paging method and paging appartus
US20200120749A1 (en) * 2017-08-04 2020-04-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data processing method and related device
WO2019056308A1 (fr) * 2017-09-22 2019-03-28 北京小米移动软件有限公司 Procédé de mise en œuvre, dispositif, équipement utilisateur et station de base pour une mise à jour de zone de localisation
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Early data transmission for User plane CIoT optimisation", 3GPP DRAFT; R2-1709307, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, 20 August 2017 (2017-08-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051319068 *

Similar Documents

Publication Publication Date Title
JP7540502B2 (ja) 端末装置及び基地局
US20240306147A1 (en) Method, device and computer storage medium of communication
JP7704446B2 (ja) 端末デバイスによって実行される方法、及び端末デバイス
JP7750398B2 (ja) 第１のネットワーク装置、端末装置、及びそれらにより実行される方法
JP7616382B2 (ja) 方法、ｍｕｓｉｍ端末装置及びマスタノード（ｍｎ）
WO2021232305A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
CN114830799A (zh) 时间同步方法、终端设备和网络设备
WO2021147030A1 (fr) Procédés, dispositifs, et support de communication
JP7697597B2 (ja) 端末装置、通信装置及び端末装置の方法
WO2022056693A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022120632A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023051366A1 (fr) Procédé de commande de transmission, et appareil associé
CN117917175A (zh) 连接控制方法、终端设备和网络设备
US12507306B2 (en) Method, device and computer storage medium of communication
WO2024092574A1 (fr) Identification pour transmission de petites quantités de données
JP7712474B2 (ja) 小規模データ送信のための通信
WO2024087170A1 (fr) Procédé, dispositif et support de stockage informatique de communication

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20964576

Country of ref document: EP

Kind code of ref document: A1